From c9fb8495499d62d433516837f067d8121e7f4770 Mon Sep 17 00:00:00 2001 From: robert Date: Fri, 20 Feb 2004 21:28:39 +0000 Subject: [PATCH 1/1] make fosdem2004 slides even better --- fosdem2004/l10ntalk_02.html | 15 +++++++++------ fosdem2004/l10ntalk_04.html | 8 +++++--- 2 files changed, 14 insertions(+), 9 deletions(-) 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 diff --git a/fosdem2004/l10ntalk_04.html b/fosdem2004/l10ntalk_04.html index 966bf90..2008e16 100755 --- a/fosdem2004/l10ntalk_04.html +++ b/fosdem2004/l10ntalk_04.html @@ -28,7 +28,7 @@ after a locale switch. There is a workaround in place (killing the FastLoad file), which also fails sometimes, and was promised to be replaced by a fix for 1.1 final (!). See bug 142623.
    • -
  • Hardcoded content: Yes, there's still some hardcoded un-localizable code in UI files left, +
  • Hardcoded content: Yes, there's still some hardcoded un-localizable code in UI files left, a big part of this is low-hanging fruit for contributors and blocks L10n severily sometimes.
    All relevant bugs (should) have the "L12y" keyword set. Query for All bugs with L12y keyword set @@ -42,14 +42,16 @@ and they forget about i18n issues or things like locale switching altogether.
    I had to fix breakage of the locale switching pref panel four times from 2002-03-31 to 2002-08-26 - the FastLoad workaround (see above) was the fith issue that broke it during that time span! - See CVS Log of the pref panel.
    • + See CVS Log of the pref panel. +
    BTW, locale switching is now broken once again (even in 1.7a): See bug 235058.
  • No stringbundles from non-privileged files: This started to hurt me when trying to make about:plugins localizable (see bug 56863). In fact, I had to give about:plugins full chrome privileges just to access stringbundles - this opened a potential security issue though. See bug 98298.
  • Content packs: We should investigate if we really need seperate packages for that content, - as the real idea never took off. Merging them back into normal localization content could ease a few things.
    • + as the real idea never took off (mainly Netscape had further plans with that). + Merging them back into normal localization content could ease a few things. This should be some points to start for contributors who want to help us, and an overview what's bugging us most currently. I'm sure the list is not complete, but it's what came to my mind when writing the slides... -- 2.35.3