Switch from he.xtb to iw.xtb because the translation console is

Switch from he.xtb to iw.xtb because the translation console is
deprecating 'he' in favor of 'iw'.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=42713

[tony, 2010-03-25 09:30:47]

Chromium side changes for switching from he.xtb to iw.xtb.  The perforce side
change is one line, will send that soon.

[tony, 2010-03-25 23:53:37]

adding jungshik

[Mark Larson (Google), 2010-03-26 00:32:42]

LGTM. 

There are other .grd files that we've never translated so far. 

chrome/trunk/src/chrome/app/chromium_strings.grd
chrome/trunk/src/webkit/glue/devtools_strings.grd
chrome/trunk/src/webkit/glue/inspector_strings.grd

Shouldn't hold up this CL, but it would be good to update those so that if we
ever _do_ try to translate them, the failure to generate he.dll isn't a mystery.

http://codereview.chromium.org/1332001/diff/3001/4007
File tools/grit/grit/node/io.py (right):

http://codereview.chromium.org/1332001/diff/3001/4007#newcode54
tools/grit/grit/node/io.py:54: (lang == 'iw' and self.attrs['lang'] == 'he')),
('The XTB file you '
We don't do this for lang=='nb'. Should we?

[tony, 2010-03-26 01:09:21]

On 2010/03/26 00:32:42, Mark Larson (Google) wrote:
> LGTM. 
> 
> There are other .grd files that we've never translated so far. 
> 
> chrome/trunk/src/chrome/app/chromium_strings.grd
> chrome/trunk/src/webkit/glue/devtools_strings.grd
> chrome/trunk/src/webkit/glue/inspector_strings.grd
> 
> Shouldn't hold up this CL, but it would be good to update those so that if we
> ever _do_ try to translate them, the failure to generate he.dll isn't a
mystery.

These files currently don't have xtb files checked in, so there's nothing to
update in them.

> http://codereview.chromium.org/1332001/diff/3001/4007
> File tools/grit/grit/node/io.py (right):
> 
> http://codereview.chromium.org/1332001/diff/3001/4007#newcode54
> tools/grit/grit/node/io.py:54: (lang == 'iw' and self.attrs['lang'] == 'he')),
> ('The XTB file you '
> We don't do this for lang=='nb'. Should we?

That's a good question.  Unfortunately, our handling of no/nb is different from
our handling of he/iw.

for no/nb:
translation console: no
within chrome code: no
locale dll: nb

for he/iw
translation console: iw
within chrome code: he
locale dll: he

Because of the difference here, we don't need to change the assert in grit.