Comments on: 44 locales in 4 days http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/ localization and community at mozilla Fri, 20 Nov 2009 20:49:29 -0800 http://wordpress.org/?v=2.8.6 hourly 1 By: Tomer Cohen http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/comment-page-1/#comment-125925 Tomer Cohen Sat, 23 Aug 2008 09:50:00 +0000 http://blog.mozilla.com/seth/?p=218#comment-125925 I've opened a bug about issues we found in Hebrew. Please note that at least some of the issues can be solved. You are welcome to CC yourself. https://bugzilla.mozilla.org/show_bug.cgi?id=451830 I’ve opened a bug about issues we found in Hebrew. Please note that at least some of the issues can be solved. You are welcome to CC yourself.

https://bugzilla.mozilla.org/show_bug.cgi?id=451830

]]> By: Mike Beltzner http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/comment-page-1/#comment-125825 Mike Beltzner Fri, 22 Aug 2008 21:39:40 +0000 http://blog.mozilla.com/seth/?p=218#comment-125825 Hey Tomer - the width of the element in the upgrade dialogs depends on a bunch of factors, primarily OS and locale: On OSX... - the window width is defined in em by window.macWidth: http://mxr.mozilla.org/l10n-mozilla1.8/search?string=window.macWidth&find=updates.dtd&findi=&filter=^[^]*%24&hitlimit=&tree=l10n-mozilla1.8 - the box is centered between 23px of padding on either side On Windows and Linux... - the window width is defined in em by window.width: http://mxr.mozilla.org/l10n-mozilla1.8/search?string=window.width&find=updates.dtd&findi=&filter=^[^]*%24&hitlimit=&tree=l10n-mozilla1.8 - the box is centered between 44px of padding on either side Sadly, em reacts to the default font size on the user's computer, but I don't think there's a lot we can do about that. Localizers should be able to test the Major Update now by installing Firefox 2.0.0.16 and setting it to use the beta channel (or installing the Release Channel Switching add-on) Hey Tomer – the width of the element in the upgrade dialogs depends on a bunch of factors, primarily OS and locale:

On OSX…
- the window width is defined in em by window.macWidth:
http://mxr.mozilla.org/l10n-mozilla1.8/search?string=window.macWidth&find=updates.dtd&findi=&filter=^[^]*%24&hitlimit=&tree=l10n-mozilla1.8
- the box is centered between 23px of padding on either side

On Windows and Linux…
- the window width is defined in em by window.width:
http://mxr.mozilla.org/l10n-mozilla1.8/search?string=window.width&find=updates.dtd&findi=&filter=^[^]*%24&hitlimit=&tree=l10n-mozilla1.8
- the box is centered between 44px of padding on either side

Sadly, em reacts to the default font size on the user’s computer, but I don’t think there’s a lot we can do about that.

Localizers should be able to test the Major Update now by installing Firefox 2.0.0.16 and setting it to use the beta channel (or installing the Release Channel Switching add-on)

]]> By: seth bindernagel http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/comment-page-1/#comment-125823 seth bindernagel Fri, 22 Aug 2008 21:32:59 +0000 http://blog.mozilla.com/seth/?p=218#comment-125823 @Tomer: I am trying to dig it up myself. I guess I should have made it clear in my post that we (the l10n-ers) were not given that information initially and many are still in search of it. I'll post the answer when I find it...have already pinged people about the issue. Apologies... @Tomer: I am trying to dig it up myself. I guess I should have made it clear in my post that we (the l10n-ers) were not given that information initially and many are still in search of it.

I’ll post the answer when I find it…have already pinged people about the issue. Apologies…

]]> By: Tomer Cohen http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/comment-page-1/#comment-125818 Tomer Cohen Fri, 22 Aug 2008 21:12:22 +0000 http://blog.mozilla.com/seth/?p=218#comment-125818 If you mention the iframe size issue - I want to admit that some of us, including me, are still looking to that information, in order to make sure our layout won't break in the update dialog. I've asked people on #l10n and they have no clue. Please advice. If you mention the iframe size issue – I want to admit that some of us, including me, are still looking to that information, in order to make sure our layout won’t break in the update dialog. I’ve asked people on #l10n and they have no clue.

Please advice.

]]> By: seth bindernagel http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/comment-page-1/#comment-125806 seth bindernagel Fri, 22 Aug 2008 20:23:48 +0000 http://blog.mozilla.com/seth/?p=218#comment-125806 Good point, Asa. Another way to look at it would be that the development and marketing team has to have everything ready before we do a major release...including strings that need to be translated that relate to a major update. Translating a few more strings may not be a hard task to add to the translation process. But, asking localizers to turn around quick translations for a major update certainly is not easy to coordinate or all that fair to the lives of our localizers. Good point, Asa.

Another way to look at it would be that the development and marketing team has to have everything ready before we do a major release…including strings that need to be translated that relate to a major update. Translating a few more strings may not be a hard task to add to the translation process. But, asking localizers to turn around quick translations for a major update certainly is not easy to coordinate or all that fair to the lives of our localizers.

]]> By: Asa Dotzler http://blog.mozilla.com/seth/2008/08/22/44-locales-in-4-days/comment-page-1/#comment-125800 Asa Dotzler Fri, 22 Aug 2008 19:43:41 +0000 http://blog.mozilla.com/seth/?p=218#comment-125800 This is just amazing. It already came up somewhere, I think, but I think it should be noted here as well. We should add "localize the Major Update billboard strings" to the checklist of things that must be translated when we ship a new version in a particular locale. Not sure if I worded that quite right but the idea is that when we ship Firefox 3.1, part of the process, and a go/no-go checklist item, should be: "did you translate the 3.0 -> 3.1 Major Update Billboard?" - A This is just amazing.

It already came up somewhere, I think, but I think it should be noted here as well.

We should add “localize the Major Update billboard strings” to the checklist of things that must be translated when we ship a new version in a particular locale.

Not sure if I worded that quite right but the idea is that when we ship Firefox 3.1, part of the process, and a go/no-go checklist item, should be: “did you translate the 3.0 -> 3.1 Major Update Billboard?”

- A

]]>