3 ms·
I understand why he did it, having just done l10n myself for a client, our application is now harder to work with, and harder to just even find things, for exam
by mattmanser 9y ago
I understand why he did it, having just done l10n myself for a client, our application is now harder to work with, and harder to just even find things, for example if you search for a phrase you can see on the screen, you get taken to the string file, instead of the string location. It's just an extra step, but it's a little mental drain that you wish you didn't have to deal with. You can't even scan the html anymore very easily as it's filled with all these hard-to-quickly-parse ids instead of human readable text.
Another big problem with using existing strings for ids is that if you notice a typo or tweak the phrasing of a particular string, boom, there goes your placeholder.
- watwut 9y agoOr you can do it the way front-end does and create a 'localizeText(id, default_translation)' function which you will use to print texts. Best of the two worlds.
- mattmanser 9y agoNot without problems. If you change you default translation, you must also change the one you have sitting in your file for your translator.
- watwut 9y agoThe point is to not have another translation in the file. English will be default. We used static file analysis to extract default (English) strings into files.