7

Being a part of "Stack Overflow in Russian" translation team I'm wondering why do some new strings not able to translate due to the lack in translation database?

As far as I know for the string surrounding it with the function like tr("english string that needs to be translated") is enough to make it translatable (i.e. automatically placed as a source string into Transifex database). Hence, it should be not too hard to detect such strings on code review stage or even by auto-check before merging new commit into working branch.

Is there a way to prevent appearance of untranslatable strings (which should be translatable for localized sites) in SE code base?

  • 1
    Think it's something for the developers to discuss internally, doubt we can/should have active part in it. (Of course, when such string appear, it's fine to report the text that can't be translated. :)) – Shadow The Curly Braced Wizard May 5 at 13:22
  • 2
    @ShadowWizard since I'm not fluent in English as I would like and Russian is more convenient for me, I can't agree with you. If open discussion will help to improve the internal localization process I think it's useful to be here. Less untranslatable strings - less bug reports about them :) – αλεχολυτ May 5 at 13:28
  • 1
    Related: my comment from two and half months ago. – Sebastian Simon May 5 at 14:17
  • @Rob nope. My question is about minimizing untranslatable string in site's engine, suggested by you is about translation (for translatable strings) before rolling out the actual build. – αλεχολυτ May 5 at 15:37

You must log in to answer this question.

Browse other questions tagged .