Timwi (timwi) wrote in lj_dev,



I would like to bring forward a few points about English-stripping which are rather important to translators, but not obvious to most of the developers.

Firstly: If you're English-stripping, please strip everything. Do not leave parentheses, brackets, punctuation, etc. hard-coded. Some languages use their special characters for these, e.g. Arabic and Japanese, and some need them treated specially.

Secondly: Do not, like, ever, split sentences. Do not construct sentences from smaller bits. Not only does this confuse translators, it unnecessarily limits them in their freedom. You never know what grammatical quirks a language can have, so whenever you do this, you could potentially make a grammatically correct translation impossible. For example: "Paid user" and "Paid user, previously an Early Adopter" should be separate strings. Most translators know how to use Copy & Paste, so don't worry about increasing their workload. (I'll fix the Account Types English-stripping patch in a minute, so don't worry whoever made it.)

Thirdly and lastly, please document unconventional things using the |notes= directive in your translation files. I believe that's what it's for. It confuses translators a lot when they don't know where things go or how things are put together. Take, for example, the recently created Actionlink string. There's nothing there which gives a clue as to what it's for, what it does, how it works.

Sorry if some of this sounds like complaining or ranting. It's not supposed to. It is my advice as a translator. Thank you for your attention.

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded