Re: Re[2]: Bug #115289

[Shaun McCance <shaunm wolfram com>]

On Tue, 2003-08-26 at 21:49, Wang Jian wrote:
> Hello,
> 
> My personal opinion is that, _if_ the strings are user visible, then
> adding them to pot is a MUST. If you don't add them, they're visibly
> untranslated anyway. If you add them, they're visibly untranslated at
> the adding time, but every team has chance to make them visibly
> translated before release. In the worst case, if every team failed to
> update, the result is the same as not adding them. Which is better?
> 
> So, _if_ the strings are user visible, I suggest even aggressive
> solution: adding them at this time. It may break some team's perfect
> statistics number, but I think a team with perfect statistics number
> should have enough resource to do an urgent update. For those teams
> who have not so perfect statistics number, 100 strings makes no
> difference anyway.
> 
> Abel Cheung has repeated that it is rather UI bug than UI change, so I
> assume it is user visible. My stand is with Abel.

This argument is a bit flawed.  There is a translation mechanism in
place.  It just doesn't use intltool.  Most of the strings are actually
translated in this system for a number of languages.  With the new
system in place without any translations, there will be substantially
fewer translated strings.  Bear in mind that we got translations for
free by using Norm Walsh's stylesheet, and we will lose those.  We can,
of course, copy the translations into the po files, but that isn't a
zero-effort job.

I won't add this to 2.4.0.  Even if there were no concerns about the
strings, the XSLT change isn't entirely trivial, and I won't put that
kind of code change in, particularly after a hard code freeze.

--
Shaun