--- /dev/null
+<html>
+<head>
+ <title>Mozilla Dev Meeting Europe 2002</title>
+</head>
+<body>
+
+<h1>Outliner of Chrome - L10n/Themes talk</h1>
+<h2>by Robert Kaiser <KaiRo@KaiRo.at></h2>
+
+<outliner id="<b>chrome_l10n_themes_talk</b>" flex="until 18:00">
+<br> <outlinercols>
+<br> <outlinercol id="WhatChrome" label="<b>What is this chrome stuff anyway?</b>">
+<br> <outlinercol id="MozChrome" label="<b>What is chrome in Mozilla?</b>">
+<br> <outlinercol id="ChromeURLs" label="<b>How can content find its locale and skin files?</b>">
+<br> <outlinercol id="ChromeRegistry" label="<b>How does Mozilla know what/where chrome is installed?</b>">
+<br> <outlinercol id="contents.rdf" label="<b>How can chrome packs give their info to chrome registry?</b>">
+<br> </outlinercols>
+<br> <outlinerchildren id="<b>discussion</b>"/>
+<br></outliner>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+<!-- <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="index.html" title="Previous page"> -->
+ <link rel="next" href="l10ntalk_01.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>Localization (L10n): Achievements and Future Directions</h1>
+
+<div class="explanation">
+This talk will give a short insight of
+<ul>
+ <li>How to make the Mozilla UI localizable (entities, string bundles)</li>
+ <li>How Mozilla can switch to different languages (chrome URIs, chrome registry)</li>
+ <li>How we do the actual localization work (MozillaTranslator)</li>
+ <li><a href="l10ntalk_10.html">Current problems</a> (localeVersion updates etc.)</li>
+ <li>Useful resources for localization (l10ntools etc.)</li>
+</ul>
+There will be enough time for discussion of this between slides and after the presentation.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Speaker: Robert Kaiser <KaiRo@KaiRo.at></p>
+<div class="samplecontent">
+<ul class="smalltree">
+ <li>Living in Steyr, Upper Austria, and attending Vienna University to become a Chemistry and Physics teacher</li>
+ <li>Known as "KaiRo" on IRC</li>
+ <li>Maintainer of the Mozilla German Project (<a href="http://mozilla.kairo.at/">http://mozilla.kairo.at/</a>,
+ sometimes called "German (Austria)" because of it's internal name of "de-AT")
+ since late 1999, first German Mozilla version was M12, released at 2000-01-01.
+ Counting Download numbers of ftp.mozilla.org, Mozilla German seems to be the most-used Mozilla Localization.</li>
+ <li>Creator of EarlyBlue and LCARStrek themes</li>
+ <li>Recently contributing some smaller things to main Mozilla trunk, like
+ resolving breakage of language switching pref panel, localeVersion updates,
+ making about:plugins themable ("make it look better") and localizable</li>
+</ul>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">The slides</p>
+<div class="samplecontent">
+This presentation was created for the <a href="http://eu.mozdev.org/Brussels2003/">European Mozilla Developer Meeting 2003</a> at
+<a href="http://www.fosdem.org/">FOSDEM</a> in Brussels.
+<br>The slides for this talk are written in HTML 4.01 Strict and CSS.
+<br>You need to turn on Mozilla's "Site Navigation Bar" for navigating through the slides.
+Click "Next" to start with the first slide from this index page. "Start" will take you back to this index from all the slides.
+<br>There's now an <a href="l10ntalk_overview.html">overview page</a> that allows access of all slides without the navigation bar
+ - and remember to <b>look at <a href="l10ntalk_10.html">the problems slide</a>!</b>
+<br>All slides and images © 02/2003 Robert Kaiser.
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+/* styles fpr L10n talk slides */
+
+body {
+ margin: 0px;
+ padding: 3px;
+ border: 0px;
+ font-family: Arial,Helvetica,sans-serif;
+ font-size: 16px;
+ color: black;
+ background-color: white;
+
+}
+
+h1 {
+ margin: 0.5em;
+ font-size: 32px;
+ font-weight: bold;
+ text-align: center;
+}
+
+h2 {
+ margin: 0.5em;
+ font-size: 28px;
+ font-weight: bold;
+ text-align: center;
+}
+
+h3 {
+ margin: 0.5em;
+ font-size: 24px;
+ font-weight: bold;
+ text-align: center;
+}
+
+h4 {
+ margin: 0.5em;
+ font-size: 19px;
+ font-weight: bold;
+ text-align: left;
+}
+
+div.explanation {
+ margin: 1em;
+ padding: 0.5em;
+ border: 1px solid grey;
+ background-color: #FFFFF8;
+}
+
+div.sample {
+ margin: 1em;
+ padding: 0px;
+ border: 1px solid grey;
+ background-color: #FFF8F8;
+}
+
+div.samplecontent {
+ margin: 0px;
+ padding: 0.5em;
+ border: 0px;
+ border-top: 1px solid grey;
+ background-color: #F8F8FF;
+}
+
+p.sampledesc {
+ margin: 0.5em;
+ font-weight: bold;
+}
+
+span.hilite {
+ font-weight: bold;
+ color: #FF8080;
+}
+
+ul.filetree {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+ margin: 0px 0px 0px 16px;
+ font-size: 0.8em;
+}
+
+ul.filetree ul {
+ margin: 0px 0px 0px 16px;
+ padding: 0px;
+ border: 0px;
+}
+ul.filetree li {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+ list-style-image:url(folder-open.gif)
+}
+
+ul.filetree li.file {
+ list-style-image:url(file.gif)
+}
+
+ul.filetree li.dirclosed {
+ list-style-image:url(folder-closed.gif)
+}
+
+ul.filetree *|*:-moz-list-bullet {
+ margin-right: 3px;
+}
+
+ul.rdftree {
+ list-style-type: none;
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+ margin: 0px 0px 0px 0px;
+ font-size: 0.8em;
+}
+
+ul.rdftree ul {
+ list-style-type: none;
+ margin: 0px 0px 0px 16px;
+ padding: 0px;
+ border: 0px;
+}
+
+ul.rdftree li {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+}
+
+ul.rdftree > li.starttag {
+ margin: 0.5em 0px 0px 0px;
+}
+
+ul.smalltree {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+ margin: 0px 0px 0px 15px;
+ font-size: 0.8em;
+}
+
+ul.smalltree > li {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+}
+
+span.treespacer {
+ width: 1em;
+}
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+<!-- <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="index.html" title="Previous page"> -->
+ <link rel="next" href="l10ntalk_02.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>used terms in this talk</h1>
+
+<div class="explanation">
+A rough list of special terms that will be used here and/or are commonly used in the L10n area:
+<ul>
+ <li><b>L10n</b>: Localization (an "L", followed by 10 characters, then an "n"): Customizing Software for a specific local area (mainly translation)</li>
+ <li><b>i18n</b>: Internationalization (an "i", followed by 18 characters, then an "n"): Making Software internationally useable (e.g. support input with Asian keyboards etc.)</li>
+ <li><b>L12y</b>: Localizability (available as a bugzilla.mozilla.org keyword, added for bugs that block L10n of some feature)</li>
+ <li><b>locale</b>: a set/package of locally customized items (e.g. a "language pack")</li>
+ <li><b>theme</b>: In Mozilla terms, a theme is a set of CSS files and images (perhaps even some XBL), sometimes also called "skin"</li>
+ <li><b>XUL</b>: "XML User interface Language" (pronounced "zool"), an XML dialect used by Mozilla to describe its UI (User Interface)</li>
+ <li><b>XPI</b>: "X(cross)-Platform install": cross-platform file format for installation of projects within the Mozilla framework. The XPI file is a zip-format file that contains a JavaScript installation script (install.js)</li>
+ <li><b>JAR</b>: This file type that originates from "Java Archive Resources" is a compressed format used for Mozilla's chrome. It's basically a zip format file, containing chrome files and RDF files that describe the content and can be fed into chrome registry (contents.rdf).</li>
+</ul>
+Terms like XML, XML entity, DTD, URI, etc. should be known by most people attending this talk, I think...
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_01.html" title="Previous page">
+ <link rel="next" href="l10ntalk_03.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>a sample XUL file</h1>
+
+<div class="explanation">
+<b>XUL</b> - as we all know, the "XML User interface Language" - is an <b>XML file format</b>.
+<br>All UI includes some <b>text</b>, and so do XUL files.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample XUL: openLocation.xul</p>
+<div class="samplecontent">
+<?xml version="1.0"?>
+<br><dialog ... title="<span class="hilite">Mozilla - Open Web Location</span>">
+<br>...
+<br><description><span class="hilite">Enter the web location (URL), or specify the local file you would like to open:</span></description>
+<br>...
+<br></dialog>
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_02.html" title="Previous page">
+ <link rel="next" href="l10ntalk_04.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>adding a DTD file</h1>
+
+<div class="explanation">
+To be able to localize all that text, we need to declare general (text) <b>entities</b> for
+all locale sensitive resources in an <b>external DTD</b> (Document Type Definition) subset and use an
+<b>XML entity reference</b>, "<span class="hilite">&entity_name;</span>", to reference them.
+<br>The DTD file is placed in an appropriate "locale" directory of our project.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample XUL: openLocation.xul</p>
+<div class="samplecontent">
+<?xml version="1.0"?>
+<br><!DOCTYPE dialog SYSTEM "chrome://communicator/<b>locale/openLocation.dtd</b>">
+<br><dialog ... title="<span class="hilite">&caption.label;</span>">
+<br>...
+<br><description><span class="hilite">&enter.label;</span></description>
+<br>...
+<br></dialog>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample DTD: openLocation.dtd</p>
+<div class="samplecontent">
+<!ENTITY <span class="hilite">caption.label</span> "Mozilla - Open Web Location">
+<br><!ENTITY <span class="hilite">enter.label</span> "Enter the web location (URL), or specify the local file you would like to open:">
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_03.html" title="Previous page">
+ <link rel="next" href="l10ntalk_05.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>using more than one DTD file</h1>
+
+<div class="explanation">
+If we need more than one DTD file for one XUL file, we're using <b>external entities
+inside the XUL file's DOCTYPE</b> declaration.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample XUL: openLocation.xul</p>
+<div class="samplecontent">
+<?xml version="1.0"?>
+<br><!DOCTYPE dialog [
+<br> <!ENTITY % brandDTD SYSTEM "chrome://global/locale/<b>brand.dtd</b>" >
+<br> %brandDTD;
+<br> <!ENTITY % openDialogDTD SYSTEM "chrome://communicator/locale/<b>openLocation.dtd</b>" >
+<br> %openDialogDTD;
+<br>]>
+<br><dialog ... title="<span class="hilite">&brandShortName;</span> - <span class="hilite">&caption.label;</span>">
+<br>...
+<br><description><span class="hilite">&enter.label;</span></description>
+<br>...
+<br> <menuitem value="0" id="currentWindow" label="<span class="hilite">&topWindow.label;</span>"/>
+<br>...
+<br></dialog>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample DTD: openLocation.dtd</p>
+<div class="samplecontent">
+<!ENTITY <span class="hilite">caption.label</span> "Open Web Location">
+<br><!ENTITY <span class="hilite">enter.label</span> "Enter the web location (URL), or specify the local file you would like to open:">
+<br><!ENTITY <span class="hilite">topWindow.label</span> "Current Navigator window">
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample DTD: brand.dtd</p>
+<div class="samplecontent">
+<!ENTITY <span class="hilite">brandShortName</span> "Mozilla">
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_04.html" title="Previous page">
+ <link rel="next" href="l10ntalk_06.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>using JavaScript to display text</h1>
+
+<div class="explanation">
+Sometimes we have to display text dynamically in the UI though, which XUL alone can't do.
+Most times JavaScript is used for that. C++ is sometimes used as well, it uses a similar technique for
+displaying localized content though, and it uses the same type of files for localization.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample XUL: openLocation.xul, calling some JS code</p>
+<div class="samplecontent">
+<?xml version="1.0"?>
+<br><!DOCTYPE dialog SYSTEM "chrome://communicator/locale/openLocation.dtd">
+<br><dialog id="openLocation" ... title="&caption.label;" <b>onLoad="onLoad();"</b>>
+<br><script type="application/x-javascript" src="chrome://communicator/<b>content/openLocation.js</b>"/>
+<br>...
+<br> <menuitem value="0" id="currentWindow" label="&topWindow.label;"/>
+<br>...
+<br></dialog>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample JavaScript: openLocation.js</p>
+<div class="samplecontent">
+...
+<br>function onLoad()
+<br>{
+<br> dialog.main = document.getElementById("openLocation");
+<br> dialog.openTopWindow = document.getElementById("currentWindow");
+<br> if (!browser) {
+<br> // No browser supplied - we are calling from Composer
+<br> // Change string to make more sense for Composer
+<br> dialog.openTopWindow.setAttribute("label", "<span class="hilite">Existing Navigator window</span>");
+<br> // change title to 'Open Location with Mozilla'
+<br> dialog.open.setAttribute("title", "<span class="hilite">Open Location with Mozilla</span>");
+<br> }
+<br>}
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_05.html" title="Previous page">
+ <link rel="next" href="l10ntalk_07.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>using string bundles with JavaScript</h1>
+
+<div class="explanation">
+For localization of text that gets displayed with JavaScript, there are <b>multiple techniques</b>.
+First, we could use <b><data>&some.text;</data></b> constructs (which don't get displayed in the UI),
+read their values from JS and use them for displaying. This isn't a very elegant solution though.
+<br>The normal solution for this situation is to use <b>string bundles</b>, which are saved in
+Java-style <b>.properties</b> files. String bundles can be accessed in two ways: First, they can be read by a XUL
+<b><stringbundle></b> element:
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample XUL: openLocation.xul, calling some JS code</p>
+<div class="samplecontent">
+<?xml version="1.0"?>
+<br><!DOCTYPE dialog SYSTEM "chrome://communicator/locale/openLocation.dtd">
+<br><dialog id="openLocation" ... title="&caption.label;" onLoad="onLoad();">
+<br><script type="application/x-javascript" src="chrome://communicator/content/openLocation.js"/>
+<br><<b>stringbundle id="openLocationBundle"</b> src="chrome://communicator/<b>locale/openLocation.properties</b>"/>
+<br>...
+<br> <menuitem value="0" id="currentWindow" label="&topWindow.label;"/>
+<br>...
+<br></dialog>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample JavaScript: openLocation.js</p>
+<div class="samplecontent">
+...
+<br>function onLoad()
+<br>{
+<br> dialog.main = document.getElementById("openLocation");
+<br> dialog.openTopWindow = document.getElementById("currentWindow");
+<br> <b>dialog.bundle = document.getElementById("openLocationBundle");</b>
+<br> if (!browser) {
+<br> // No browser supplied - we are calling from Composer
+<br> // Change string to make more sense for Composer
+<br> dialog.openTopWindow.setAttribute("label", <b>dialog.bundle.getString</b>("<span class="hilite">existingNavigatorWindow</span>"));
+<br> // change title to 'Open Location with Mozilla'
+<br> dialog.open.setAttribute("title", <b>dialog.bundle.getString</b>("<span class="hilite">caption2.label</span>"));
+<br> }
+<br>}
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample string bundle: openLocation.properties</p>
+<div class="samplecontent">
+<span class="hilite">existingNavigatorWindow</span>=Existing Navigator window
+<br><span class="hilite">caption2.label</span>=Open Location with Mozilla
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_06.html" title="Previous page">
+ <link rel="next" href="l10ntalk_08.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>using the string bundle service</h1>
+
+<div class="explanation">
+The second way to access string bundles is to call the <b>string bundle service</b> directly from JavaScript
+(the string bundle doesn't have to be refrenced in the XUL file, and stays outside the DOM tree):
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample XUL: openLocation.xul, calling some JS code</p>
+<div class="samplecontent">
+<?xml version="1.0"?>
+<br><!DOCTYPE dialog SYSTEM "chrome://communicator/locale/openLocation.dtd">
+<br><dialog id="openLocation" ... title="&caption.label;" onLoad="onLoad();">
+<br><script type="application/x-javascript" src="chrome://communicator/content/openLocation.js"/>
+<br>...
+<br> <menuitem value="0" id="currentWindow" label="&topWindow.label;"/>
+<br>...
+<br></dialog>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample JavaScript: openLocation.js</p>
+<div class="samplecontent">
+...
+<br>function onLoad()
+<br>{
+<br> dialog.main = document.getElementById("openLocation");
+<br> dialog.openTopWindow = document.getElementById("currentWindow");
+<br> var <b>strBundleService</b> = Components.classes["@mozilla.org/intl/stringbundle;1"]<b>.getService</b>(Components.interfaces.nsIStringBundleService);
+<br> var brandbundle = strBundleService<b>.createBundle</b>("chrome://global/locale/brand.properties");
+<br> var dialogbundle = strBundleService<b>.createBundle</b>("chrome://communicator/locale/openLocation.properties");
+<br> if (!browser) {
+<br> // No browser supplied - we are calling from Composer
+<br> // Change string to make more sense for Composer
+<br> dialog.openTopWindow.setAttribute("label", <b>dialogbundle.GetStringFromName</b>("<span class="hilite">existingNavigatorWindow</span>"));
+<br> // change title to 'Open Location with Mozilla'
+<br> var brandShortName = brandbundle.GetStringFromName("<span class="hilite">brandShortName</span>");
+<br> dialog.open.setAttribute("title", <b>dialogbundle.getFormattedString</b>("<span class="hilite">caption2.label</span>", brandShortName));
+<br> }
+<br>}
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample string bundle: openLocation.properties</p>
+<div class="samplecontent">
+<span class="hilite">existingNavigatorWindow</span>=Existing Navigator window
+<br><span class="hilite">caption2.label</span>=Open Location with %S
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample string bundle: brand.properties</p>
+<div class="samplecontent">
+<span class="hilite">brandShortName</span>=Mozilla
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_07.html" title="Previous page">
+ <link rel="next" href="l10ntalk_09.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>chrome URIs / chrome registry</h1>
+
+<div class="explanation">
+The DTD file is referenced by a <b>chrome URI</b>, e.g. "chrome://communicator/locale/openLocation.dtd".
+<br>All chrome URIs have the form of <b>chrome://<package>/{content|locale|skin}/<path-to-file></b>.
+<br>To which file on disk (or in a .jar package) this URI resolves, is determined by the <b>chrome registry</b>:
+The chrome registry knows which <b>locales</b> (e.g. en-US, de-AT, it-IT) are installed for which <b>packages</b>
+(e.g. communicator, navigator, messenger), and which locale is selected for those packages.
+<br>As a side note, the chrome registry stores the same information for themes as well.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Example directory tree with files</p>
+<div class="samplecontent">
+<ul class="filetree">
+ <li>mozilla
+ <ul>
+ <li>chrome
+ <ul>
+ <li>comm
+ <ul>
+ <li>content
+ <ul>
+ <li>communicator
+ <ul>
+ <li class="file">openLocation.xul</li>
+ </ul>
+ </li>
+ <li class="dirclosed">navigator</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li class="file">en-US.jar
+ <ul>
+ <li>locale
+ <ul>
+ <li>en-US
+ <ul>
+ <li>communicator
+ <ul>
+ <li class="file">openLocation.dtd</li>
+ <li class="file">openLocation.properties</li>
+ </ul>
+ </li>
+ <li>global
+ <ul>
+ <li class="file">brand.dtd</li>
+ <li class="file">brand.properties</li>
+ </ul>
+ </li>
+ <li class="dirclosed">navigator</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li class="file">de-AT.jar
+ <ul>
+ <li>communicator
+ <ul>
+ <li class="file">openLocation.dtd</li>
+ <li class="file">openLocation.properties</li>
+ </ul>
+ </li>
+ <li>global
+ <ul>
+ <li class="file">brand.dtd</li>
+ <li class="file">brand.properties</li>
+ </ul>
+ </li>
+ <li class="dirclosed">navigator</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+</ul>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Sample chrome registry (main chrome.rdf + profile's chrome.rdf)</p>
+<div class="samplecontent">
+<ul class="rdftree">
+ <li>...</li>
+ <li class="starttag"><RDF:Seq about="urn:mozilla<b>:package:root</b>">
+ <ul>
+ <li><RDF:li resource="urn:mozilla:package:communicator"/></li>
+ <li><RDF:li resource="urn:mozilla:package:global"/></li>
+ <li>...</li>
+ </ul>
+ </li>
+ <li></RDF:Seq>
+ <li class="starttag"><RDF:Description about="urn:mozilla:package:communicator" c:baseURL="<b>resource:/chrome/comm/content/communicator/</b>" c:localeVersion="1.3b" ...>
+ <ul>
+ <li><c:<b>selectedLocale</b> resource="urn:mozilla:locale:<b>de-AT:communicator</b>"/></li>
+ </ul>
+ </li>
+ <li></RDF:Description>
+ <li class="starttag"><RDF:Description about="urn:mozilla:package:global" c:baseURL="<b>jar:</b>resource:/chrome/<b>toolkit.jar!</b>/content/global/" c:localeVersion="1.3b" ...>
+ <ul>
+ <li><c:selectedLocale resource="urn:mozilla:locale:de-AT:global"/></li>
+ </ul>
+ </li>
+ <li></RDF:Description>
+ <li class="starttag"><RDF:Seq about="urn:mozilla<b>:locale:root</b>">
+ <ul>
+ <li><RDF:li resource="urn:mozilla:locale:de-AT"/></li>
+ <li><RDF:li resource="urn:mozilla:locale:AT"/></li>
+ <li><RDF:li resource="urn:mozilla:locale:en-US"/></li>
+ <li><RDF:li resource="urn:mozilla:locale:US"/></li>
+ </ul>
+ </li>
+ <li></RDF:Seq>
+ <li class="starttag"><RDF:Description about="urn:mozilla:locale:<b>en-US:communicator</b>" c:baseURL="jar:resource:/chrome/<b>en-US.jar!/locale/en-US/communicator/</b>" c:localeVersion="1.3b">
+ <ul>
+ <li><c:package resource="urn:mozilla:package:communicator"/></li>
+ </ul>
+ </li>
+ <li></RDF:Description>
+ <li class="starttag"><RDF:Description about="urn:mozilla:locale:en-US:global" c:baseURL="jar:resource:/chrome/en-US.jar!/locale/en-US/global/" c:localeVersion="1.3b">
+ <ul>
+ <li><c:package resource="urn:mozilla:package:global"/></li>
+ </ul>
+ </li>
+ <li></RDF:Description>
+ <li class="starttag"><RDF:Description about="urn:mozilla:locale:<b>de-AT:communicator</b>" c:baseURL="jar:resource:/chrome/<b>de-AT.jar!/communicator/</b>" c:localeVersion="1.3b">
+ <ul>
+ <li><c:package resource="urn:mozilla:package:communicator"/></li>
+ </ul>
+ </li>
+ <li></RDF:Description>
+ <li class="starttag"><RDF:Description about="urn:mozilla:locale:de-AT:global" c:baseURL="jar:resource:/chrome/de-AT.jar!/global/" c:localeVersion="1.3b">
+ <ul>
+ <li><c:package resource="urn:mozilla:package:global"/></li>
+ </ul>
+ </li>
+ <li></RDF:Description>
+</ul>
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_08.html" title="Previous page">
+ <link rel="next" href="l10ntalk_10.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>translating with MozillaTranslator</h1>
+
+<div class="explanation">
+MozillaTranslator (<a href="http://www.mozillatranslator.org/">http://www.mozillatranslator.org/</a>) is a <b>L10n tool</b>
+created by a Mozilla L10n contributor, <b>Henrik Lynggaard</b>, from Denmark.
+<br>The tool is a <b>Java application</b>, version 5 and up need at least Sun JRE 1.4.x to run.
+<br>Sometimes it's a bit <b>hard to configure</b>, but once set up it's nice and easy to maintain the L10n.
+It reads the files <b>directly from the .jar</b>, and is able to detect just the changes since the last update, so you only have
+to look at the really changed texts. It can <b>export .jar</b> files again, and even create ready-to-install <b>XPI files</b>.
+It's also capable of maintaining multiple products within one MozillaTranslator installation.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Example window: updating a product (yes, that's Mozilla calendar)</p>
+<div class="samplecontent">
+<img src="MT502_update.png" alt="MozillaTranslator 5.02 update view">
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Example window: chrome view of a file (openLocation.dtd)</p>
+<div class="samplecontent">
+<img src="MT502_chromeview.png" alt="MozillaTranslator 5.02 chrome view">
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_09.html" title="Previous page">
+ <link rel="next" href="l10ntalk_11.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>current problems with L10n work (helpwanted!)</h1>
+
+<div class="explanation">
+As always, there are some more or less big problems in current Mozilla L10n:
+<ul>
+ <li><b>Hardcoded content</b>: Some projects still have hardcoded un-localizable code in their UI files,
+ e.g. Calendar and ChatZilla - but also Browser and MailNews have a bunch of those left.
+ A big part of this is low-hanging fruit for contributors and blocks L10n severily sometimes.
+ <br>All relevant bugs (should) have the "L12y" keyword set.
+ Query for <a href="http://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=L12y&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">All bugs with L12y keyword set</a>
+ (44 bugs found as of Fri Feb 7 06:30:17 PST 2003).</li>
+ <li><b>Ignorance</b>: Many US programmers think "It works for me and my collegues, and so it's alright" -
+ and they forget about i18n issues or things like locale switching altogether.
+ <br>I had to fix breakage of the pref panel four times from 2002-03-31 to 2002-08-26 -
+ the FastLoad workaround (see below) is the fith issue that broke it during that time span!
+ See <a href="http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/extensions/content-packs/resources/content/pref-contentpacks.xul">CVS Log of the pref panel</a>.</li>
+ <li><b>Content packs</b>: Content packs (a.k.a. "region" packs) were a somehow interesting idea, but they
+ aren't used by anyone. 99.999999% of our users only use one language pack and one content pack together.
+ They should get re-merged into one pack again, the files should stay seperate though, as it's quite good
+ to have all URLs that are used in the UI seperated from the other content.
+ <br>It looks as even Netscape, who had originally created that split-up has no interest any more in those
+ content packs. It even blocks me from renaming the generic German language pack to a simple "de.jar".
+ <li><b>localeVersion updates</b>: locale packs from different Mozilla versions are incompatible because of
+ changed, added or removed texts in the UI. Quite some time ago, we introduced a localeVersion attribute
+ in chrome registry that has to fit, so that Mozilla knows it has a working set of chrome files.
+ <br>So far, so good. Lots of contents.rdf files in the tree carry that information, which is hardcoded
+ there, and it's a <b>big pain to update</b> them for every version.
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=175853" title="Update localeVersion strings for 1.2 final - and do it correctly!">bug 175853</a>,
+ <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=185698" title="localeVersion update for 1.3b on trunk">bug 185698</a>
+ and <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=154927" title="automate localeVersion updates based on milestone.txt">bug 154927</a>.</li>
+ <li><b>no fallback mechanism</b>: If people would try to use some non-fitting locale packs, they get crashes
+ and XML errors because we have no fallback if lookup for a locale string fails somewhere (string or file not found).
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=71797" title="Mozilla fails to fallback to another skin or locale if the preferences point to a non-existant one">bug 71797</a>.</li>
+ <li><b>XUL FastLoad problems</b>: XUL FastLoad fails to update the strings after a locale switch.
+ There is a workaround in place, which also fails sometimes, and was promised to be replaced by a fix for 1.1 final.
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=142623" title="No reload of Language strings due to XUL FastLoad">bug 142623</a>.</li>
+ <li><b>XPI installation problems - error -239</b>: This bug is a really strange thing, and does hurt us mainly on unix.
+ When installing an XPI on most unix systems and some other systems as well, it fails with
+ error -239 (CHROME_REGISTRY_ERROR) for no obvious reason.
+ <br>We're using a workaround for unix, but this workaround prohibits installing a new locale into the
+ profile directory, which would be needed for non-root users in the common case.
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=109044" title="Install error -239 registering chrome on some systems">bug 109044</a>.</li>
+ <li><b>No stringbundles from non-privileged files</b>: This started to hurt me when trying to make about:plugins
+ localizable (see <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=56863" title="make about:plugins localizable">bug 56863</a>).
+ In fact, I had to give about:plugins full chrome privileges just to access stringbundles - this opened
+ a potential security issue though. Even if about:plugins might go a different way now (HTML created by C++),
+ this is a potential issue for other areas.
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=98298" title="do not have stringbundle access from about:plugins">bug 98298</a>.</li>
+ <li><b>Resources</b>: Currently, there's no single collection of documentation, tools, etc. for L10n people.
+ We're currently working on getting such a thing up and running now though.
+ See <a href="http://l10ntools.mozdev.org/">l10ntools.mozdev.org</a>.</li>
+</ul>
+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...
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_10.html" title="Previous page">
+ <link rel="next" href="l10ntalk_12.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page">
+</head>
+<body>
+
+<h1>useful resources for L10n work</h1>
+
+<div class="explanation">
+There are a few places to look for Mozilla L10n resources currently:
+<ul>
+ <li><b>MLP</b>: The <a href="http://www.mozilla.org/projects/l10n/">Mozilla Localization Project</a>
+ is hosted on mozilla.org and contains a list of all major contributors to all languages supported on any
+ Mozilla version. There's a small howto, a page with various locale packs available for Mozilla, and
+ <a href="ftp://ftp.mozilla.org/pub/mozilla/l10n/lang/">ftp.mozilla.org</a>
+ hosts downloads for locale packs and localized Mozilla binaries.
+ (There are currently 89 L10n projects [excluding en-US] registered, 10 projects have released 1.3a versions,
+ 30 have 1.2.1 available).</li>
+ <li><b>MozillaTranslator</b>: The <a href="http://www.mozillatranslator.org/">MozillaTranslator</a> tool
+ has its own website, with a mini-howto (contributors to the documentation wanted!), downloads of
+ the tool itself as well as its source code, and a download page for language packs
+ (often a bit outdated though).</li>
+ <li><b>Creating Applications with Mozilla</b>: <a href="http://books.mozdev.org/chapters/ch11.html">Chapter 11</a>
+ of the book about creating Mozilla applications (this chapter was written by Brian King)
+ is worth a look as well, esp. if you're writing your own application using the Mozilla framework
+ (I haven't come around to read it though).</li>
+ <li><b>l10ntools</b>: Finally, the new <a href="http://l10ntools.mozdev.org/">l10ntools MozDev project</a>
+ is currently built up and should contain a bunch of tools to deal with L10n work, some docs, and some
+ link to those other resources.
+ <br>One subproject is <b>mozpotools</b>, which allows converting Mozilla's locale files to the GNU gettext
+ .po format, use the common translation tools for that format (KBabel etc.), and then convert the files back
+ to Mozilla's format.
+ <br>l10ntools will also provide <b>XPI install scripts</b> for use in a locale's installable XPI language packs,
+ <b>scripts for creating XPI packs</b> from the .jar files that get exported by MozillaTranslator, and even
+ <b>scripts for creating localized binaries</b> from the XPI file created above and an existing .tar.gz or .zip
+ binary Mozilla build, as well as <b>some documentation</b> about those tools and prbably general L10n issues.
+ Other useful tools will probably be added if people give them to us.</li>
+</ul>
+In the future, <b>l10ntools</b> should have link to all those resources (or host them theirselves).
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_11.html" title="Previous page">
+<!-- <link rel="next" href="l10ntalk_12.html" title="Next page">
+ <link rel="last" href="l10ntalk_12.html" title="Last page"> -->
+</head>
+<body>
+
+<h1>open discussion</h1>
+
+<div class="explanation">
+We now have some time for discussion.
+<ul>
+ <li>Any open questions?</li>
+ <li>Any unmentioned issues?</li>
+ <li>Anyone wanting to help us?</li>
+ <li>Anything I forgot to mention?</li>
+</ul>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Thank you</p>
+<div class="samplecontent">
+<span style="font-size:3em;">
+<span style="color:#8080FF;" title="english">Thanks for your attention.</span>
+<span style="color:#FF8080;" title="german">Danke für Ihre Aufmerksamkeit.</span>
+<span style="color:#FF80FF;" title="french">Merci de votre attention.</span>
+<span style="color:#80FF80;" title="spanish">Gracias por su atención.</span>
+<span style="color:#808080;" title="dutch">Bedankt voor uw aandacht.</span>
+<span style="color:#80CCFF;" title="swedish">Tack för er uppmärksamhet.</span>
+<span style="color:#FFCC80;" title="italian">Grazie per la sua attenzione<span style="display:none;">confidenza</span>.</span>
+</span>
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+</head>
+<body>
+
+<h1>Overview/Contents: Localization (L10n) Talk</h1>
+
+<div class="explanation">
+The following slides can be found in that presentation:
+<ul>
+ <li><a href="index.html">Introduction</a></li>
+ <li><a href="l10ntalk_01.html">used terms in this talk</a></li>
+ <li><a href="l10ntalk_02.html">a sample XUL file</a></li>
+ <li><a href="l10ntalk_03.html">adding a DTD file</a></li>
+ <li><a href="l10ntalk_04.html">using more than one DTD file</a></li>
+ <li><a href="l10ntalk_05.html">using JavaScript to display text</a></li>
+ <li><a href="l10ntalk_06.html">using string bundles with JavaScript</a></li>
+ <li><a href="l10ntalk_07.html">using the string bundle service</a></li>
+ <li><a href="l10ntalk_08.html">chrome URIs / chrome registry</a></li>
+ <li><a href="l10ntalk_09.html">translating with MozillaTranslator</a></li>
+ <li><a href="l10ntalk_10.html">current problems with L10n work (helpwanted!)</a></li>
+ <li><a href="l10ntalk_11.html">useful resources for L10n work</a></li>
+ <li><a href="l10ntalk_12.html">open discussion</a></li>
+</ul>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+<!-- <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="xxx.html" title="Previous page"> -->
+ <link rel="next" href="l10ntalk_01.html" title="Next page">
+ <link rel="last" href="l10ntalk_end.html" title="Last page">
+</head>
+<body>
+
+<h1>Mozilla Localization (L10n) Status Update</h1>
+
+<div class="explanation">
+Localization seems to get a more important topic in Mozilla development.
+<br>I'll give an update about
+<ul>
+ <li>what the MLP is,</li>
+ <li>what has happened in the last year in this area,</li>
+ <li>where we are now (using the German project as an example),</li>
+ <li>and where are the problems for L10n currently / where we'd need help from other developers.</li>
+</ul>
+I hope there will be enough time left for discussion of this between slides and after the presentation.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Speaker: Robert Kaiser <KaiRo@KaiRo.at></p>
+<div class="samplecontent">
+<ul class="smalltree">
+ <li>Living in Steyr, Upper Austria, and attending Vienna University to become a Chemistry and Physics teacher</li>
+ <li>Known as "KaiRo" on IRC</li>
+ <li>Maintainer of the Mozilla German Project (<a href="http://mozilla.kairo.at/">http://mozilla.kairo.at/</a>,
+ sometimes called "German (Austria)" because of it's internal name of "de-AT")
+ since late 1999, first German Mozilla version was M12, released at 2000-01-01.
+ Counting Download numbers of ftp.mozilla.org, Mozilla German seems to be the most-used Mozilla Localization.</li>
+ <li>Creator of EarlyBlue and LCARStrek themes</li>
+ <li>Contributing some smaller things to main Mozilla trunk, like
+ resolving breakage of language switching pref panel, localeVersion updates (and automating them),
+ making about:plugins themable ("make it look better") and localizable - recently even breaking tinderboxen...</li>
+</ul>
+</div>
+</div>
+
+<div class="sample">
+<p class="sampledesc">The slides</p>
+<div class="samplecontent">
+This presentation was created for the <a href="http://www.fosdem.org/2004/index/dev_room_mozilla">European Mozilla Developer Meeting 2004</a> at
+<a href="http://www.fosdem.org/">FOSDEM</a> in Brussels.
+<br>The slides for this talk are written in HTML 4.01 Strict and CSS.
+<br>You need to turn on Mozilla's "Site Navigation Bar" for navigating through the slides.
+Click "Next" to start with the first slide from this index page. "Top" will take you back to this index from all the slides.
+<br>An <a href="l10ntalk_overview.html">overview page</a> that allows access of all slides without the navigation bar
+is available, as well an a <a href="l10ntalk_glossary.html">glossary page</a> explaining some common terms used.</b>
+<br>If you want to look through them later, see <a href="http://kairo.mozdev.org/slides/fosdem2004/">http://kairo.mozdev.org/slides/fosdem2004/</a>.
+<br>All slides and images © 02/2004 Robert Kaiser.
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+/* styles fpr L10n talk slides */
+
+body {
+ margin: 0px;
+ padding: 3px;
+ border: 0px;
+ font-family: Arial,Helvetica,sans-serif;
+ font-size: 16px;
+ color: black;
+ background-color: white;
+
+}
+
+h1 {
+ margin: 0.5em;
+ font-size: 32px;
+ font-weight: bold;
+ text-align: center;
+}
+
+h2 {
+ margin: 0.5em;
+ font-size: 28px;
+ font-weight: bold;
+ text-align: center;
+}
+
+h3 {
+ margin: 0.5em;
+ font-size: 24px;
+ font-weight: bold;
+ text-align: center;
+}
+
+h4 {
+ margin: 0.5em;
+ font-size: 19px;
+ font-weight: bold;
+ text-align: left;
+}
+
+div.explanation {
+ margin: 1em;
+ padding: 0.5em;
+ border: 1px solid grey;
+ background-color: #FFFFF8;
+}
+
+div.sample {
+ margin: 1em;
+ padding: 0px;
+ border: 1px solid grey;
+ background-color: #FFF8F8;
+}
+
+div.samplecontent {
+ margin: 0px;
+ padding: 0.5em;
+ border: 0px;
+ border-top: 1px solid grey;
+ background-color: #F8F8FF;
+}
+
+p.sampledesc {
+ margin: 0.5em;
+ font-weight: bold;
+}
+
+span.hilite {
+ font-weight: bold;
+ color: #FF8080;
+}
+
+pre.border {
+ border: 1px solid #FF8080;
+ padding: 0.5em;
+}
+
+ul {
+ padding-left: 1.2em;
+}
+li.plus {
+ list-style-image:url("plus.png");
+ margin: 0.5em 0;
+}
+li.minus {
+ list-style-image:url("minus.png");
+ margin: 0.5em 0;
+}
+
+ul.bugs > li {
+ list-style-image:url("bug.png");
+ margin: 0.5em 0;
+}
+
+ul.smalltree {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+ margin: 0px 0px 0px 15px;
+ font-size: 0.8em;
+}
+
+ul.smalltree > li {
+ margin: 0px;
+ padding: 0px;
+ border: 0px;
+}
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <!-- <link rel="previous" href="l10ntalk_01.html" title="Previous page"> -->
+ <link rel="next" href="l10ntalk_02.html" title="Next page">
+ <link rel="last" href="l10ntalk_end.html" title="Last page">
+</head>
+<body>
+
+<h1>MLP - The Mozilla L10n Project</h1>
+
+<div class="explanation">
+The <a href="http://www.mozilla.org/projects/l10n/">Mozilla Localization Project</a> (MLP),
+hosted on mozilla.org, "tries to help and ease the availability of mozilla.org products
+toward different world cultures and languages through the support of the open source community."
+
+<br><br>The main goal is to encourage people to <span class="hilite">contribute localizations</span>,
+make them available to users, and provide communication channels for the contributors (we have the
+<a href="news://netscape.public.mozilla.l10n" title="netscape.public.mozilla.l10n">n.p.m.l10n</a> newsgroup,
+an own product at <a href="http://bugzilla.mozilla.org/">Bugzilla</a>, and the IRC Channel <a href="irc://irc.mozilla.org:6667/mozl10n">#mozl10n</a>
+as the most important resources for that).
+<br>The second important goal is to <span class="hilite">make and keep the software localizable</span>.
+Again, Bugzilla is a great help there (the best tool for bugging developers - I guess that's where the name
+comes from). More about that later.
+</div>
+
+<div class="sample">
+<p class="sampledesc">Localization projects</p>
+<div class="samplecontent">
+All Mozilla L10n projects are volunteer efforts by relatively small groups of people or single persons.
+<br>The MLP web pages contain lists of all registered L10n projects and their major contributors,
+as well as their available builds. Currently, projects are listed for
+<a href="http://www.mozilla.org/projects/l10n/mlp_status.html">Seamonkey</a>
+as well as <a href="http://www.mozilla.org/projects/l10n/mlp_otherproj.html#firefox">Firefox</a> and
+<a href="http://www.mozilla.org/projects/l10n/mlp_otherproj.html#thunderbird">Thunderbird</a>.
+<br>Seamonkey counts <span class="hilite">100 L10n projects</span>, Firefox has 39 and Thunderbird 22 listed
+(as of 2004-02-19).
+Not all of them have current build though. Mozilla 1.6 is available in 26 languages (plus en-US)
+to this date, Firefox 0.8 was translated to 12 languages in the less than two weeks since its release,
+Thunderbird 0.5 got up to 10 localizations in the same time. We can expect those three numbers to still
+grow a bit, as we had 37 languages for Mozilla 1.5[.1], 24 for Firebird 0.7[.1], and 13 for Thunderbird 0.4.
+<br><br>All packs and builds (sometimes a bit delayed though) available at
+<a href="ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/l10n/lang/">ftp.mozilla.org</a>
+(older builds are on <a href="http://archive.mozilla.org/pub/mozilla/l10n/lang/">archive.mozilla.org</a>)
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_01.html" title="Previous page">
+ <link rel="next" href="l10ntalk_03.html" title="Next page">
+ <link rel="last" href="l10ntalk_end.html" title="Last page">
+</head>
+<body>
+
+<h1>diff -D 02/2003 -D 02/2004 mozilla-l10n</h1>
+
+<div class="explanation">
+<pre>--- mozilla-l10n 2003-02-FOSDEM
++++ mozilla-l10n 2004-02-FOSDEM
+@@ -a,b +x,y @@</pre>
+Well, let's make it a small bit less geeky ;-). So what has happened in the last year of Mozilla L10n?
+<ul>
+ <li class="minus"><b>big manual localeVersion change patches</b>: locale packs from different Mozilla versions are incompatible because of
+ changed, added or removed texts in the UI. To avoid crashes or other side-effects, we have internal
+ versioning of locale in chrome registry, fed into it by contents.rdf files.
+ <br>Those were <span class="hilite">previously hardcoded</span> 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
+ (<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=154927">bug 154927</a>),
+ I was told we should use the <span class="hilite">XUL preprocessor</span>. I made that change recently
+ (<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=232011">bug 232011</a>)
+ and set tinderboxen on fire (as some of you may remember)...
+ <br>After some help from tinderbox admins and bsmedberg (who had to fix make-jars.pl for a bug I triggered),
+ we show now be have that long-standing bug finally resolved (and themes will follow that way soon -
+ <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=234014">bug 234014</a>).
+ <br>BTW, all chrome version strings are now defined in
+ <a href="http://lxr.mozilla.org/mozilla/source/config/chrome-versions.sh">mozilla/config/chrome-versions.sh</a>.</li>
+ <li class="minus"><b>XPI error -239</b>: When installing our <span class="hilite">locale XPI files</span>, 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 (<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=109044">bug 109044</a>),
+ and noone had an idea why that happened, when it started magically disappearing in some cases last summer.
+ <br>DocWilco then <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=109044#c64">filed a patch</a>
+ for a case where he was still seeing (and which was "a tough one to crack"), and we didn't hear a lot about
+ that error again. He also <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=221994">improved reporting</a>
+ of what happens when it still hits a -239 in a followup.
+ <br>Another nasty <span class="hilite">problem is history now</span>.</li>
+ <li class="plus"><b>more attention to L10n</b>: Starting with last December, L10n got more attention of
+ mozilla.org staff than in previous times. It all started with a staff meeting on 2003-12-08 (see the
+ <a href="http://groups.google.com/groups?as_umsgid=3FDB8346.9010004@mozilla.org">"minutes" posting</a>):
+ <pre class="border">
+ *Localisation packs*
+
+- Quarterly/monthly <span class="hilite">IRC meetings</span> for l10n (blizzard, bart)
+- What is our end goal for internationalization?
+- <span class="hilite">Goal: 5 or 6 languages we ship pretty regularly</span>, of reasonable to good
+ quality
+- Start incrementally
+
+- Agreed: <span class="hilite">translations need to be in CVS</span>; too separated from release
+ process
+
+- chofmann to write a message to l10n newsgroup:
+ - 1) Tell people how to nominate bugs to drivers
+ - 2) Mention monthly IRC chat, hosted by chofmann
+ (gerv query: what time to have this? Hard to pick one which is
+ good for everyone, because of timezone issues)
+ - 3) If you have a localised version ready 1 week after 1.6, let us
+ know now (or then) and we'll try and get it on the CD.
+ - 4) There will be a <span class="hilite">string freeze after beta</span> - it's a done deal
+ - 5) We want your localisation by 1 week after our planned release
+ date (But CD gets burned 2 days before we release)
+
+- We need a simple post-freeze string change process - Bugzilla keyword,
+ post to newsgroup etc.</pre>
+ 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,
+ <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=57878">bug 57878</a> that still doesn't have much attention, as well as the one for
+ getting German L10n into CVS (<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=179949">bug 179949</a>).
+ <br>Let's hope the positive movement of December can be carried on into the future.</li>
+ <li class="plus"><b>Mozilla Europe</b>: Just last week, the <a href="http://www.mozilla-europe.org/">Mozilla Foundation Europe</a>
+ has been launched, having a <span class="hilite">multi-language web site</span>, and that probably will
+ <span class="hilite">attract even more users</span> to localized versions of Mozilla and its derivates.
+ <br>We'll see what this means to our L10n projects...</li>
+</ul>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_02.html" title="Previous page">
+ <link rel="next" href="l10ntalk_04.html" title="Next page">
+ <link rel="last" href="l10ntalk_end.html" title="Last page">
+</head>
+<body>
+
+<h1>Where We Are Now</h1>
+
+<div class="explanation">
+L10n projects can get real big attention from users. For volunteer projects of private people,
+that may turn out to bring some problems with growing user interest.
+On the other hand, especially as a private volunteer contributor, it can make you even more fond of that
+project seeing the little baby of yours grow and grow.
+</div>
+
+<div class="sample">
+<p class="sampledesc">An Example: The Mozilla German Project</p>
+<div class="samplecontent">
+In late 1999, working with M11, I discovered that XUL has nice text/code seperation, and tried to dig into it
+by changing some strings to German equivalents - <span class="hilite">just for fun</span>. Being the first one
+to do this for that language, I stumbled into being the leader of the German L10n project and released
+M12 German on 2000-01-01.
+<br>A lot has happened since then. The small HTML page I made up for downloading that build turned into a
+<span class="hilite">heavily accessed web site</span>, now residing at
+<a href="http://mozilla.kairo.at/">mozilla.kairo.at</a>.
+<br>In January 2004, that site was accessed by over 740000 different hosts, hitting the main page
+just under one million times, the support page (default home page of German builds) had almost 800000 hits.
+With 44000 visits of people per day (average), the site produced 20 GB of HTML traffic.
+<br>As a student, I'd have some problems paying for the server that hosts all that alone,
+and affording visiting FOSDEM as well on my cost would also be not too easy. I'd like to
+<span class="hilite">thank all donators</span> of the Mozilla German project for making it possible
+to keep the site up and attend here, and my parents as well for supporting me to come here and spend some time
+on Mozilla next to studying.
+<br>The downloads are hosted by mozilla.org, universities and my student home, and I don't have reliable
+download counters for those, so I can't tell any download numbers. From ftp.mozilla.org numbers alone,
+it seems to be the <span class="hilite">most-used localization</span> by far though.
+<br>The German localization of Mozilla gets included in all CDs of the big German magazine PC-WELT,
+the German XPI pack is on the mozilla.org 1.6 CD (AFAIK), SUSE LINUX does include German packs for Mozilla,
+and probably it's shipped in various other ways as well.
+<br>Two other contributors are shipping translated version of Firefox and Thunderbird based on that work,
+and the German Mozilla newsgroup de.comm.software.mozilla has been split into a hierarchy of 4 newsgroups
+because one group couldn't handle the traffic of currently 4000 postings a month.
+<br>Recently, I've given an interview for a German SAP magazine, and an Austrian computer magazine asked
+me for one as well. It's pretty astonishing...
+<br>On the other hand, I'm spending some hours a week answering mails telling users that I'm just a
+translator, and I can't do support, pointing them to FAQs and newsgroups.
+<br>There are still other problems left in Mozilla itself that bug us L10n people...
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_03.html" title="Previous page">
+ <link rel="next" href="l10ntalk_end.html" title="Next page">
+ <link rel="last" href="l10ntalk_end.html" title="Last page">
+</head>
+<body>
+
+<h1>Current Problems In L10n Area (helpwanted!)</h1>
+
+<div class="explanation">
+<ul class="bugs">
+ <li><b>no fallback mechanism</b>: If people would try to use some non-fitting locale packs, they get
+ <span class="hilite">crashes and XML errors</span> because we have no fallback if lookup for
+ a locale string fails somewhere (string or file not found).
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=71797" title="Mozilla fails to fallback to another skin or locale if the preferences point to a non-existant one">bug 71797</a>.</li>
+ <li><b>XUL FastLoad problems</b>: XUL FastLoad fails to update the strings
+ <span class="hilite">after a locale switch</span>. 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 <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=142623" title="No reload of Language strings due to XUL FastLoad">bug 142623</a>.</li>
+ <li><b>Hardcoded content</b>: 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.
+ <br>All relevant bugs (should) have <a href="http://bugzilla.mozilla.org/describekeywords.cgi#l12y">the "L12y" keyword</a> set.
+ Query for <a href="http://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=L12y&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">All bugs with L12y keyword set</a>
+ <small>(50 bugs found as of Thu Feb 19 18:26:44 PST 2004,
+ 35 of them in <a href="http://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=L12y&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Browser">[Seamonkey] Browser product</a>,
+ 13 of them in <a href="http://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=L12y&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=MailNews">[Seamonkey] MailNews product</a>,
+ 1 of them ("Localize FE") in <a href="http://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=L12y&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Firefox">Firefox product</a>,
+ 0 of them in <a href="http://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=L12y&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Thunderbird">Thunderbird product</a>,
+ the other one is in PSM)</small>.</li>
+ <li><b>Ignorance</b>: Still some programmers think "It works for me and my collegues, and so it's alright" -
+ and they forget about i18n issues or things like locale switching altogether.
+ <br>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 <a href="http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/extensions/content-packs/resources/content/pref-contentpacks.xul">CVS Log of the pref panel</a>.</li>
+ <li><b>No stringbundles from non-privileged files</b>: This started to hurt me when trying to make about:plugins
+ localizable (see <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=56863" title="make about:plugins localizable">bug 56863</a>).
+ In fact, I had to give about:plugins full chrome privileges just to access stringbundles - this opened
+ a potential security issue though.
+ See <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=98298" title="do not have stringbundle access from about:plugins">bug 98298</a>.</li>
+ <li><b>Content packs</b>: 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.</li>
+</ul>
+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...
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="l10ntalk_01.html" title="First page">
+ <link rel="previous" href="l10ntalk_04.html" title="Previous page">
+<!-- <link rel="next" href="l10ntalk_end.html" title="Next page">
+ <link rel="last" href="l10ntalk_end.html" title="Last page"> -->
+</head>
+<body>
+
+<h1>Open Discussion</h1>
+
+<div class="explanation">
+We now have some time for discussion.
+<ul>
+ <li>Any open questions?</li>
+ <li>Any unmentioned issues?</li>
+ <li>Anyone wanting to help us?</li>
+ <li>Anything I forgot to mention?</li>
+</ul>
+</div>
+
+<div class="sample">
+<p class="sampledesc">Thank you</p>
+<div class="samplecontent">
+<span style="font-size:3em;">
+<span style="color:#8080FF;" title="english">Thanks for your attention.</span>
+<span style="color:#FF8080;" title="german">Danke für Ihre Aufmerksamkeit.</span>
+<span style="color:#FF80FF;" title="french">Merci de votre attention.</span>
+<span style="color:#80FF80;" title="spanish">Gracias por su atención.</span>
+<span style="color:#808080;" title="dutch">Bedankt voor uw aandacht.</span>
+<span style="color:#80CCFF;" title="swedish">Tack för er uppmärksamhet.</span>
+<span style="color:#FFCC80;" title="italian">Grazie per la sua attenzione<span style="display:none;">confidenza</span>.</span>
+</span>
+</div>
+</div>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2003 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="glossary" href="l10ntalk_glossary.html" title="Glossary">
+ <link rel="start" href="index.html" title="Start">
+</head>
+<body>
+
+<h1>Common terms used in Mozilla L10n (glossary)</h1>
+
+<div class="explanation">
+A rough list of special terms that will be used here and/or are commonly used in the L10n area:
+<ul>
+ <li><b>L10n</b>: Localization (an "L", followed by 10 characters, then an "n"): Customizing Software for a specific local area (mainly translation)</li>
+ <li><b>i18n</b>: Internationalization (an "i", followed by 18 characters, then an "n"): Making Software internationally useable (e.g. support input with Asian keyboards etc.)</li>
+ <li><b>L12y</b>: Localizability (available as a bugzilla.mozilla.org keyword, added for bugs that block L10n of some feature)</li>
+ <li><b>locale</b>: a set/package of locally customized items (e.g. a "language pack")</li>
+ <li><b>theme</b>: In Mozilla terms, a theme is a set of CSS files and images (perhaps even some XBL), sometimes also called "skin"</li>
+ <li><b>XUL</b>: "XML User interface Language" (pronounced "zool"), an XML dialect used by Mozilla to describe its UI (User Interface)</li>
+ <li><b>XPI</b>: "X(cross)-Platform install": cross-platform file format for installation of projects within the Mozilla framework. The XPI file is a zip-format file that contains a JavaScript installation script (install.js)</li>
+ <li><b>JAR</b>: This file type that originates from "Java Archive Resources" is a compressed format used for Mozilla's chrome. It's basically a zip format file, containing chrome files and RDF files that describe the content and can be fed into chrome registry (contents.rdf).</li>
+</ul>
+Terms like XML, XML entity, DTD, URI, etc. should be known by most people attending this talk, I think...
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>L10n talk - FOSDEM 2004 - Mozilla Meeting</title>
+ <link rel="stylesheet" type="text/css" href="l10ntalk.css">
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="l10ntalk_overview.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+</head>
+<body>
+
+<h1>Overview/Contents: Localization (L10n) Talk</h1>
+
+<div class="explanation">
+The following slides can be found in that presentation:
+<ul>
+ <li><a href="index.html">Introduction</a></li>
+ <li><a href="l10ntalk_01.html">MLP - The Mozilla L10n Project</a></li>
+ <li><a href="l10ntalk_02.html">diff -D 02/2003 -D 02/2004 mozilla-l10n</a></li>
+ <li><a href="l10ntalk_03.html">Where We Are Now</a></li>
+ <li><a href="l10ntalk_04.html">Current Problems In L10n Area (helpwanted!)</a></li>
+ <li><a href="l10ntalk_end.html">Open Discussion</a></li>
+ <li><a href="l10ntalk_glossary.html">Glossary</a></li>
+</ul>
+</div>
+
+</body>
+</html>
--- /dev/null
+
+<!-- ***************** INFO/NEWS *************** -->
+<div id="infoTabs">
+<div class="infoTab" id="whats-new">
+<h5 class="infoHeader">What's New</h5>
+<ul>
+<li>Aug 24: Project started</li>
+</ul>
+</div>
+
+<div class="infoTab" id="other-stuff">
+<h5 class="infoHeader">Other Stuff</h5>
+<ul>
+<li><a href="http://resources.kairo.at/">some resource filess from me</a></li>
+<li><a href="http://www.kairo.at/">www.KaiRo.at - my home</a></li>
+</ul>
+</div>
+
+</div>
+<!-- ***************** INFO/NEWS *************** -->
+
+<!-- MAIN CONTENT -->
+<p>This is the <strong><?php echo $project; ?></strong> project @ mozdev.org.</p>
+
+<p>The project contains some scripts and smaller OSS programs by me (Robert Kaiser, a.k.a. "KaiRo").</p>
+
+<p>Most of those scripts and/or programs have some connection to
+<a href="http://www.mozilla.org/">Mozilla</a>, but I'll eventually also provide some software that
+has no direct connection to my favourite browser.</p>
+
+<p>For wishes and comments about the project and software please use Bugzilla, I'm already overburdened
+with personal mail, so I perhaps won't get to answer that sooner or later, but I'll look at Bugzilla
+often enough to work at open bug reports.
+<br>See the "bugs" link in the navigation line above.</p>
+
+<!--
+<p><strong>Note:</strong> If you want to add an area for user feedback to any of your pages, take a look at the <a href="notes.html">notes.html</a>
+template.</p>
+-->
projects / slides.git / commitdiff
