> Prior to this, the only way to push a translation below 100% was to add
> functionality to the product as a whole. Getting all that sorted out
> cleanly before a major release is bad enough.
>
> This is the first case where adding a *translation* would affect all the
> others. Imagine the maintenance headaches if the hypothetical Sioux
> translator shows up a week before 1.0 is ready to ship, and we have to get
> 48 other translators to fix that string. Ick. That's worse.
This is a misunderstanding of the 'language' issue. The language
list in UT_Language has *nothing* to do with existing translations
and locales, it is a list of languages that the user can use for
spellchecking. This list can be filled with any languages we want
immediately, without the need for localising AW interface for that
language (the Word 2000 language selection might be a good
starting point). If this is done, adding of a language in the future will
be a very rare occurence.
Tomas
