One of the untold stories of Firefox is that localizing Firefox is something different. Inside our localization community, it is an often heard complaint that we're doing this while every other project in its sane mind does that. I have been...
I've been doing some investigation on localization architectures in the last two months or so, triggered by parts of the 50-2-100 thread in .l10n and .planning. In particular, I've been reading the archives of translate-i18n, which happens to be...
As a heads-up, I'm making some progress to use a single python process per jar.mn in bug 361583. AFAICT, I have all the odd ends figured out to merely run one python script per jar.mn, instead of starting a two perl processes per jar.mn, and one per …
As there were more people talking about this than I recall, here's the public correction on what I though would be true: I see no way to hook into expat to make it resolve an entity. See the XML_TOK_ENTITY_REF handling in xmlparse.c. We can...
I've spent the last few days catching up on years of archive of translate-i18n. It's been an interesting read so far, the challenges we face are the same in other places, and are pretty independent of the used technology. Given the recent...
During the l10n session today we came up with an request from dynamis for him to be able to not have a string argument show up in a formatted l10n string. We came up with the idea to specify zero width in the format, but it's actually precision 0. foo …
Not speaking Punjabi actually made me speak Chinese. Well, not really. The lesson to take away is, you may not be able to speak a language, but looking at a patch on a mac with Chinese fonts sure does catch some bugs. Looking at the bugzilla diff...
The short post I want to get out is "Thanks". I'll definitely try to get around and do the long post, but that requires me to have a dictionary by my side, it seems. Thanks to the localizers, thanks to the developers, thanks to the drivers,...
If you're a localizer, please look at my post in .l10n on what to do to sign off on your localization. As we've been doing quite a few QA and testing cycles so far, there should be very little work left to do but actually closing the bug....
One bug down, 38 to go.