gnopernicus string freeze breakage - preferred action?

[Bill Haneman <Bill Haneman Sun COM>]

Hi:

I see that the fix for http://bugzilla.gnome.org/show_bug.cgi?id=135242 
introduced a new string, "switch to". 

This is partly my fault, as I reviewed this patch and marked it 'commit' 
on Tuesday, but I was reading for code suitability and I forgot about 
the XML file localization issue.  Sorry about that, thanks Christian for 
catching it.

It doesn't look as though gnopernicus has been re-dist'ed since the 
string change.  I see three fixes:

(1) retroactively approve the new string and re-dist as soon as possible;
(2) un-mark the string for localization;
(3) revise the fix to avoid the introduction of a new string.

#1 inconveniences translators but is straightforward.  #2 doesn't break 
freeze, but will result in an unlocalized spoken message for gnopernicus 
users [1].  #3 would avoid the problem altogether, but might result in a 
less-optimal user experience.

Which do you want to do? 

- Bill


[1] unfortunately we don't have many non-English voices in current use - 
this will mostly impact some Spanish gnopernicus users.