correct index files (again)
[slides.git] / fosdem2004 / l10ntalk_04.html
... / ...
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
5 <meta name="Author" content="KaiRo - Robert Kaiser">
6 <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
7 <link rel="stylesheet" type="text/css" href="l10ntalk.css">
8 <link rel="contents" href="index.html" title="Contents">
9 <link rel="index" href="l10ntalk_overview.html" title="Overview">
10 <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
11 <link rel="start" href="index.html" title="Start">
12 <link rel="first" href="l10ntalk_01.html" title="First page">
13 <link rel="previous" href="l10ntalk_03.html" title="Previous page">
14 <link rel="next" href="l10ntalk_end.html" title="Next page">
15 <link rel="last" href="l10ntalk_end.html" title="Last page">
19<h1>Current Problems In L10n Area (helpwanted!)</h1>
21<div class="explanation">
22<ul class="bugs">
23 <li><b>no fallback mechanism</b>: If people would try to use some non-fitting locale packs, they get
24 <span class="hilite">crashes and XML errors</span> because we have no fallback if lookup for
25 a locale string fails somewhere (string or file not found).
26 See <a href="" title="Mozilla fails to fallback to another skin or locale if the preferences point to a non-existant one">bug 71797</a>.</li>
27 <li><b>XUL FastLoad problems</b>: XUL FastLoad fails to update the strings
28 <span class="hilite">after a locale switch</span>. There is a workaround in place (killing the FastLoad file),
29 which also fails sometimes, and was promised to be replaced by a fix for 1.1 final (!).
30 See <a href="" title="No reload of Language strings due to XUL FastLoad">bug 142623</a>.</li>
31 <li><b>Hardcoded content</b>: Yes, there's still some hardcoded un-localizable code in UI files left,
32 a big part of this is low-hanging fruit for contributors and blocks L10n severily sometimes.
33 <br>All relevant bugs (should) have <a href="">the "L12y" keyword</a> set.
34 Query for <a href="">All bugs with L12y keyword set</a>
35 <small>(50 bugs found as of Thu Feb 19 18:26:44 PST 2004,
36 35 of them in <a href="">[Seamonkey] Browser product</a>,
37 13 of them in <a href="">[Seamonkey] MailNews product</a>,
38 1 of them ("Localize FE") in <a href="">Firefox product</a>,
39 0 of them in <a href="">Thunderbird product</a>,
40 the other one is in PSM)</small>.</li>
41 <li><b>Ignorance</b>: Still some programmers think "It works for me and my collegues, and so it's alright" -
42 and they forget about i18n issues or things like locale switching altogether.
43 <br>I had to fix breakage of the locale switching pref panel four times from 2002-03-31 to 2002-08-26 -
44 the FastLoad workaround (see above) was the fith issue that broke it during that time span!
45 See <a href="">CVS Log of the pref panel</a>.</li>
46 <li><b>No stringbundles from non-privileged files</b>: This started to hurt me when trying to make about:plugins
47 localizable (see <a href="" title="make about:plugins localizable">bug 56863</a>).
48 In fact, I had to give about:plugins full chrome privileges just to access stringbundles - this opened
49 a potential security issue though.
50 See <a href="" title="do not have stringbundle access from about:plugins">bug 98298</a>.</li>
51 <li><b>Content packs</b>: We should investigate if we really need seperate packages for that content,
52 as the real idea never took off. Merging them back into normal localization content could ease a few things.</li>
54This should be some points to start for contributors who want to help us, and an overview what's bugging us
55most currently. I'm sure the list is not complete, but it's what came to my mind when writing the slides...
58<p class="forward"><a href="l10ntalk_end.html">next</a></p>