X-Git-Url: https://git-public.kairo.at/?p=slides.git;a=blobdiff_plain;f=fosdem2004%2Fl10ntalk_02.html;h=71f1dd6ce614067895a5ee14cab75a5d360fabd3;hp=a09a900683e66c08e5b7727a1cbb846b00dcb269;hb=c9fb8495499d62d433516837f067d8121e7f4770;hpb=0437d853893f45d5d1b9d6ef23ced0cca85ae59b;ds=sidebyside diff --git a/fosdem2004/l10ntalk_02.html b/fosdem2004/l10ntalk_02.html index a09a900..71f1dd6 100755 --- a/fosdem2004/l10ntalk_02.html +++ b/fosdem2004/l10ntalk_02.html @@ -29,18 +29,19 @@ Well, let's make it a small bit less geeky ;-). So what has happened in the last versioning of locale in chrome registry, fed into it by contents.rdf files.
Those were previously hardcoded and I did big manual patches to change them. After I found a way to insert the versions at build-time and patched the whole tree to do that using the C preprocessor - (bug 154927), + (bug 154927), I was told we should use the XUL preprocessor. I made that change recently - (bug 232011) + (bug 232011) and set tinderboxen on fire (as some of you may remember)...
After some help from tinderbox admins and bsmedberg (who had to fix make-jars.pl for a bug I triggered), we should now have that long-standing bug finally resolved (and themes will follow that way soon - - bug 234014). + bug 234014).
BTW, all chrome version strings are now defined in mozilla/config/chrome-versions.sh.
  • XPI error -239: When installing our locale XPI files, we often ran into XPInstall error -239 (CHROME_REGISTRY_ERROR), especially on unix machines. This had been happening quite - frequently for at least 18 months (bug 109044), + frequently for at least 18 months + (bug 109044), and noone had an idea why that happened, when it started magically disappearing in some cases last summer.
    DocWilco then filed a patch for a case where he was still seeing (and which was "a tough one to crack"), and we didn't hear a lot about @@ -78,8 +79,10 @@ Well, let's make it a small bit less geeky ;-). So what has happened in the last The first L10n IRC meeting was on 2003-12-15, The 1.6 CD shipped with a few important / finished-in-time localization XPI packs, we're still hoping further actions will happen. The first string freeze (1.7b -> 1.7) is still to happen, and getting translations into CVS is actually a quite old bug report, - bug 57878 that still doesn't have much attention, as well as the one for - getting German L10n into CVS (bug 179949). + bug 57878, + that still doesn't have much attention, as well as the one for + getting German L10n into CVS + (bug 179949).
    Let's hope the positive movement of December can be carried on into the future.
  • Mozilla Europe: Just last week, the Mozilla Foundation Europe has been launched, having a multi-language web site, and that probably will