Big +1 for what Martin and Mikhel have said about matching existing
translations and not losing the ability to translate to different
targets depending on the context.
If there is going to be wholesale re-organisation as to how the strings
are presented for translation, two other considerations also spring to
mind which I didn't see on the list:
1) Plurals? I think LO still doesn't do plurals properly (but I may be
confusing projects here, apologies if it does). This would also tie in
with the 1 source string » multiple target strings issue.
2) Turning en-US into a to-be-translated locale and making the source
strings just en or some fake locale? That way, en-US can change case,
correct en-US typos and other such stuff which is English specific to
its heart's content without hitting all the other locales at the same time.
Michael
--
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
