X-Git-Url: https://git-public.kairo.at/?p=slides.git;a=blobdiff_plain;f=fosdem2004%2Fl10ntalk_04.html;h=2008e1672a063253c398ac610b1b42a32a8ed376;hp=966bf902c09c3dd66a8e8febf5046e2ea297d162;hb=2d98aed10831424374dbe61b1e465c99f85cab16;hpb=0437d853893f45d5d1b9d6ef23ced0cca85ae59b 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...