Timeline for How to organize localization string resources?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2016 at 3:43 | comment | added | carlossierra | I have worked translating several big applications from and to Spanish, and I can tell you that if you have the right translation tools, duplicates are not an issue (they are even desirable). See my answer for how to handle this effectively. | |
| Aug 2, 2016 at 11:12 | comment | added | RosieC | In which case I would store it once and reuse. A consideration perhaps outside the scope of what you are directly doing is the cost of a translator. We actually got our re-sellers around the world to fund that for themselves and also test the translation within the application. They most definitely wanted duplicates avoided. | |
| Aug 2, 2016 at 10:37 | comment | added | Daniel Wolf | I'm afraid that doesn't really address my question. I absolutely agree that sentences should never be broken up. However, most resources aren't sentences but simple labels (button texts, table headers, form labels etc.). | |
| Aug 2, 2016 at 9:38 | comment | added | Martin Ba | Exactly. We also do this. Never try to break up labels/sentences in translation. | |
| Aug 2, 2016 at 9:34 | history | answered | RosieC | CC BY-SA 3.0 |