On 12. Nov 2007, at 22:05:49, Michael R Sweet wrote:
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.
That's why our company uses the fake "Esperanto" - which is in fact
english with unique identifiers. Those IDs assure we won't mix main,
option and group keywords. Especially, since we use the same
translation tables for our plugins also.
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.
Since we share the MacOS X PPDs with Windows and MacOS 9, we don't
need multi-language PPDS. Our translation is made on PCs with some
scripting code and not with the CUPS-DDK's PPD compiler.
But maybe the original poster likes to file a bug, since he had the
problem...
Marc
--
In a world without walls and fences,
who needs windows and gates?
_______________________________________________
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
