2009/9/18 Ain Vagula <avag...@gmail.com>: > hcshared22 also introduced a lot of needed changes about new or > changed features in 3.1, so we cannot use older source here.
This is something I proposed here but my idea was not accepted well. I proposed that help changes would come in smaller packages that would be easier to control. Now I can give this idea an even clearer form. The help CWS' could be divided to two or more sorts - new strings adding new functionality descriptions, automatic source changes (like tags and icons, done automatically on localization teams SDF's) and editing of English strings. Namely, I have seen that also changes in English strings are a bit frustrating for us non-English localizers - in English strings sometimes just fixing a typo makes the string in your language fuzzy, but actually your translation should be just fine. But you want to make it sure what changed and if translation is ok etc. and you lose precious time. If one knew that a typo and English content changing CWS is coming one would go translating through it in a different way compared to an new strings CWS. But I guess having several CWS' in this way would make a hell to documentation writers who would have to split changes to two different CWS even in the same string and that would really be stupid. However, could English language (en-US) become just one of translation/localization languages? That way when typos would be changed the main SDF would not get changed, just the en-US translation of the SDF? The localizers would get the changes to translate only when there would be new strings and when editing of existing strings would change or clear their meaning. LP, m. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
