Comments for Yet Another Tech Blog http://www.yetanothertechblog.com l10n, Mozilla and other stuff Mon, 30 Jan 2012 18:25:26 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on l10n Memo for the Next Meeting by flod http://www.yetanothertechblog.com/2012/01/29/l10n-memo-for-the-next-meeting/comment-page-1/#comment-26942 flod Mon, 30 Jan 2012 18:25:26 +0000 http://www.yetanothertechblog.com/?p=103#comment-26942 Hi Robert, thanks for the explanation. Honestly I understand that something like that can happen and backing out that change was the only solution, still I believe it's being managed badly: according to bsmedberg's <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=716945#c17" rel="nofollow">last comment</a> we'll have another break in Aurora's string freeze when this bug is fixed, which seems quite silly. Hi Robert, thanks for the explanation.
Honestly I understand that something like that can happen and backing out that change was the only solution, still I believe it’s being managed badly: according to bsmedberg’s last comment we’ll have another break in Aurora’s string freeze when this bug is fixed, which seems quite silly.

]]> Comment on l10n Memo for the Next Meeting by Robert Kaiser http://www.yetanothertechblog.com/2012/01/29/l10n-memo-for-the-next-meeting/comment-page-1/#comment-26937 Robert Kaiser Mon, 30 Jan 2012 16:02:10 +0000 http://www.yetanothertechblog.com/?p=103#comment-26937 You may know that I've been a localizer for ages (well, back to 1999, which is an eternity in Mozilla terms). Also, yes, if you look into the bug, I'm probably to blame for this backout. Also, if you look there, you'll see that Axel was involved before the backout happened. Still, yes, I probably should have put more pressure on investigating this way earlier, but it looked like something had been *fixed* not like, as we found out very late now, that something actually had been *broken*. This means that Firefox 10 will ship without us being able to reasonably find out if plugin crashes or hangs are getting worse or better - in the end, *because of the L10n impact*, we agreed that we will not be able to reasonably diagnose *any* plugin/Flash crash/hang problem with Firefox 10 unless they're really really really bad - for any not world-changing issues, we'll just not have the data to even realize they're there. If we wouldn't have done this backout on Aurora - which, as you note, didn't *break* everything, even though it might look bad, and where localizers still have 6 weeks of beta to make it completely OK - then we also wouldn't be able to diagnose those things for Firefox 11. It's bad enough to be in that situation for one release, it's unacceptable for two, I hope you agree with me there. Yes, we messed up, and I'm somewhat to blame because I didn't insist earlier that we investigate this. Unfortunately I believed it wasn't a bug, but a feature, which was a mistake, in hindsight. Even as a localizer, I thought it would be better to have one sentence in a plugin crash message not translated than to miss 80-90% of all plugin crash/hang reports. I hope with that explanation, you can agree with this as well. You may know that I’ve been a localizer for ages (well, back to 1999, which is an eternity in Mozilla terms). Also, yes, if you look into the bug, I’m probably to blame for this backout. Also, if you look there, you’ll see that Axel was involved before the backout happened.
Still, yes, I probably should have put more pressure on investigating this way earlier, but it looked like something had been *fixed* not like, as we found out very late now, that something actually had been *broken*. This means that Firefox 10 will ship without us being able to reasonably find out if plugin crashes or hangs are getting worse or better – in the end, *because of the L10n impact*, we agreed that we will not be able to reasonably diagnose *any* plugin/Flash crash/hang problem with Firefox 10 unless they’re really really really bad – for any not world-changing issues, we’ll just not have the data to even realize they’re there. If we wouldn’t have done this backout on Aurora – which, as you note, didn’t *break* everything, even though it might look bad, and where localizers still have 6 weeks of beta to make it completely OK – then we also wouldn’t be able to diagnose those things for Firefox 11. It’s bad enough to be in that situation for one release, it’s unacceptable for two, I hope you agree with me there.
Yes, we messed up, and I’m somewhat to blame because I didn’t insist earlier that we investigate this. Unfortunately I believed it wasn’t a bug, but a feature, which was a mistake, in hindsight. Even as a localizer, I thought it would be better to have one sentence in a plugin crash message not translated than to miss 80-90% of all plugin crash/hang reports.
I hope with that explanation, you can agree with this as well.

]]> Comment on l10n Memo for the Next Meeting by Jeferson Hltmnn http://www.yetanothertechblog.com/2012/01/29/l10n-memo-for-the-next-meeting/comment-page-1/#comment-26867 Jeferson Hltmnn Sun, 29 Jan 2012 19:37:43 +0000 http://www.yetanothertechblog.com/?p=103#comment-26867 Thanks for the head up. It seems I'll have to update my "green" locale. :-| Thanks for the head up. It seems I’ll have to update my “green” locale. :-|

]]> Comment on l10n Memo for the Next Meeting by flod http://www.yetanothertechblog.com/2012/01/29/l10n-memo-for-the-next-meeting/comment-page-1/#comment-26842 flod Sun, 29 Jan 2012 13:03:35 +0000 http://www.yetanothertechblog.com/?p=103#comment-26842 <blockquote>just TWO repositories!? Oh I see, it’s just AURORA FX you are talking about. Thunderbird, Beta, 3.1x etc are outside the context. </blockquote> Wrong, I just meant 2 repositories (l10n-central and mozilla-aurora) ;-)

just TWO repositories!? Oh I see, it’s just AURORA FX you are talking about. Thunderbird, Beta, 3.1x etc are outside the context.

Wrong, I just meant 2 repositories (l10n-central and mozilla-aurora) ;-)

]]> Comment on l10n Memo for the Next Meeting by smo http://www.yetanothertechblog.com/2012/01/29/l10n-memo-for-the-next-meeting/comment-page-1/#comment-26841 smo Sun, 29 Jan 2012 12:58:17 +0000 http://www.yetanothertechblog.com/?p=103#comment-26841 Hi Flod: "Working on two different repositories"... just TWO repositories!? Oh I see, it's just AURORA FX you are talking about. Thunderbird, Beta, 3.1x etc are outside the context. Coming out: in my cygwin subdirectory there's 11 (eleven) folders starting on HG. Even after discounting for my personal messy factor, the Mozilla l10n phase space encompasses more than just two repositories. It is a hell of a job for the localizers (median group size = 1) to stay abreast. As the Red Queen said: "It takes all the running to stay in the same place". Regards smo Hi Flod:

“Working on two different repositories”… just TWO repositories!? Oh I see, it’s just AURORA FX you are talking about. Thunderbird, Beta, 3.1x etc are outside the context.

Coming out: in my cygwin subdirectory there’s 11 (eleven) folders starting on HG. Even after discounting for my personal messy factor, the Mozilla l10n phase space encompasses more than just two repositories. It is a hell of a job for the localizers (median group size = 1) to stay abreast. As the Red Queen said: “It takes all the running to stay in the same place”.

Regards

smo

]]> Comment on Native Localized Android Build by Axel Hecht http://www.yetanothertechblog.com/2011/12/26/native-localized-android-build/comment-page-1/#comment-23768 Axel Hecht Tue, 27 Dec 2011 14:51:13 +0000 http://www.yetanothertechblog.com/?p=89#comment-23768 I was pretty sure we published somewhere that the native UI was moving along with 11, but I can't find any traces of it. The l10n side of it didn't go as planned often, that's why there's been few announcement. What good do they do if they get revised the next day. I was pretty sure we published somewhere that the native UI was moving along with 11, but I can’t find any traces of it.

The l10n side of it didn’t go as planned often, that’s why there’s been few announcement. What good do they do if they get revised the next day.

]]> Comment on Native Localized Android Build by flod http://www.yetanothertechblog.com/2011/12/26/native-localized-android-build/comment-page-1/#comment-23749 flod Tue, 27 Dec 2011 11:14:30 +0000 http://www.yetanothertechblog.com/?p=89#comment-23749 Now I'm even more confused. The discussion can be found in the mailing list: Alex Keybl answered to my question that Firefox 11 will be released as a native build, being Firefox 11 on Aurora right now my conclusion was "Ok, so we'll start localizing Firefox from aurora instead of central". Now I’m even more confused.

The discussion can be found in the mailing list: Alex Keybl answered to my question that Firefox 11 will be released as a native build, being Firefox 11 on Aurora right now my conclusion was “Ok, so we’ll start localizing Firefox from aurora instead of central”.

]]> Comment on Native Localized Android Build by Axel Hecht http://www.yetanothertechblog.com/2011/12/26/native-localized-android-build/comment-page-1/#comment-23743 Axel Hecht Tue, 27 Dec 2011 10:53:32 +0000 http://www.yetanothertechblog.com/?p=89#comment-23743 Who said that localization would start on aurora? I didn't know, for sure, and I wouldn't phrase it like that. Anywho, I don't know when and how we'll do a post-mortem on fennec l10n, but now is a bad time, and this is probably a bad place, so I'll not go into it. Who said that localization would start on aurora?

I didn’t know, for sure, and I wouldn’t phrase it like that.

Anywho, I don’t know when and how we’ll do a post-mortem on fennec l10n, but now is a bad time, and this is probably a bad place, so I’ll not go into it.

]]> Comment on Native Localized Android Build by Native Localized Android Build @ Yet Another Tech Blog | Tech Unleashed http://www.yetanothertechblog.com/2011/12/26/native-localized-android-build/comment-page-1/#comment-23723 Native Localized Android Build @ Yet Another Tech Blog | Tech Unleashed Tue, 27 Dec 2011 07:21:49 +0000 http://www.yetanothertechblog.com/?p=89#comment-23723 [...] Taken from: Native Localized Android Build @ Yet Another Tech Blog [...] [...] Taken from: Native Localized Android Build @ Yet Another Tech Blog [...]

]]> Comment on Dear reviewer, by Roxanna http://www.yetanothertechblog.com/2011/10/21/dear-reviewer/comment-page-1/#comment-22306 Roxanna Mon, 12 Dec 2011 20:45:30 +0000 http://www.yetanothertechblog.com/?p=87#comment-22306 I'm gratfuel you made the post. It's cleared the air for me. I’m gratfuel you made the post. It’s cleared the air for me.

]]>