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. :)) May 5, 2019 at 13:22
  • 4
    @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, 2019 at 13:28
  • 1
    Related: my comment from two and half months ago. May 5, 2019 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, 2019 at 15:37
  • 1
    What are you really asking here? You've tagged this as both discussion and support neither of which seem appropriate. As a support question your question would be read as something like "As a user of this site, is there any way for me to change the source code process or force the developers to do X?" The obvious answer to that is "No". It's so obvious that it seems nonsensical to ask as a support question.
    – Makyen
    May 26 at 13:27
  • 1
    As a discussion, this question would be something like "Given the entire development process that SE uses, is it possible to establish a part of the process such that no untranslatable strings are permitted in the code?" This, again, seems very strange to be asking, because it really is asking users here to speculate on SE's development process and what changes might be able to be made to it. It's really not a productive discussion to have here without substantially more visibility into SE's development process.
    – Makyen
    May 26 at 13:30
  • 2
    On the other hand, something similar to this as a feature-request asking SE to establish, as a part of the development process, checks to ensure that the code (or at least new code) doesn't have strings which are untranslatable. Such a feature request would actually be useful.
    – Makyen
    May 26 at 13:34


You must log in to answer this question.

Browse other questions tagged .