...
This is a problem of design:
To make it easy for the average american software developer, the base
language to translate from is "English". Thus there are some limitations
where two words (or phrases) are equal in the base language but
different in the target language or vice versa.
The decision was actually made after numerous developers around
the world (including those in countries with gender-specific words)
suggested that English was the preferred language since they could
use their existing message catalogs as a basis for translation, and
fallback translations from a catalog of common words and phrases
might also be feasible - think on-the-fly translation of untranslated
PPD options.
> ...
A better design would use some artificial language as base and treat
english identical as all other target languages. Yes, this means a
little more effort when starting a new software project - but it will
pay out quickly, the more target languages (and thus different
grammatical cases) you use the sooner.
We've looked at using keywords as the message IDs, but they suffer
from the same problem since main keywords, option keywords, and
group keywords can be the same.
Supporting "English as a second language" so that you can use a
different base language is 100% doable, and all you need to do is
file a bug report here:
Please be specific about what you want to do differently -
constructive suggestions for improvement will ensure the fastest
and most useful response.
Thanks!
--
______________________________________________________________________
Michael R Sweet Senior Printing System Engineer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/printing/email@hidden
