remove local.conf files (mozdev artifact)
[slides.git] / fosdem2005 / 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 2005 - 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>SeaMonkey vs. Aviary</b>: The differences between SeaMonkey and the "aviary" applications based on the new toolkit
28 make work difficult sometimes for getting source L10n to work correctly.
29 <br>L10n work for the two product lines is getting <span class="hilite">more and more different</span>,
30 though the source files are similar or identical on both sides.
31 <br>This situation would get much better if we
32 <a href="">port seamonkey to "new toolkit"/xulrunner</a>,
33 we'd still need volunteers for that effort (this is not strictly L10n, but it affects us a lot, and we still have quite a lot of SeaMonkey L10n work happening out there).
34 <li><b>MLP web pages are a mess</b>: We (MLP staff) know about that, and we are <span class="hilite">working on it</span>. See
35 <a href="">MozillaWiki - L10n:MLP_page_structure</a>.
36 <li><b>L12y bugs</b>: Just as a reminder, we have some <span class="hilite">localizability problems</span> left in Mozilla code.
37 <br>All relevant bugs (should) have <a href="">the "L12y" keyword</a> set.
38 Query for <a href=";keywords=L12y&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">All bugs with L12y keyword set</a>
39 <small>(<span class="hilite">87 bugs found</span> as of Wed Feb 23 12:56:11 PST 2005,
40 48 of them in <a href=";keywords=L12y&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Core">Core product</a>,
41 14 of them in <a href=";keywords=L12y&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Mozilla+Application+Suite">"Mozilla Application Suite" (Seamonkey) product</a>,
42 13 of them in <a href=";keywords=L12y&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Firefox">Firefox product</a>,
43 6 of them in <a href=";keywords=L12y&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Thunderbird">Thunderbird product</a>,
44 the other 6 in PSM, Update,</small>.</li>
45 <li><b>No stringbundles from non-privileged files</b>: This started to hurt me when trying to make about:plugins
46 localizable (see <a href="" title="make about:plugins localizable">bug 56863</a>).
47 In fact, I had to give about:plugins full chrome privileges just to access stringbundles - this opened
48 a <span class="hilite">potential security issue</span> though.
49 See <a href="" title="do not have stringbundle access from about:plugins">bug 98298</a>.</li>
50 <li><b>XUL FastLoad problems</b>: XUL FastLoad fails to update the strings
51 <span class="hilite">after a locale switch</span>. There is a workaround in place (killing the FastLoad file),
52 which also fails sometimes, and was promised to be replaced by a fix for 1.1 final (!).
53 See <a href="" title="No reload of Language strings due to XUL FastLoad">bug 142623</a>.</li>
55This should be some points to start for contributors who want to help us, and an overview what's bugging us
56most currently. I'm sure the list is not complete, but it's what came to my mind when writing the slides...
59<p class="forward"><a href="l10ntalk_end.html">next</a></p>