[http://sematild.qsh.eu/sitemap.htm map] [http://bukgetert.0lx.net/article-1512.htm kryptonite bicycle lock video] [http://betheres.qsh.eu/comment-233.htm indian lesbian movie] [http://fispruil.qsh.eu/news677.html super club video tron] [http://flheddin.qsh.eu/enlabobas-456.html nude video of kasumi]  

[http://sematild.qsh.eu/sitemap.htm map] [http://bukgetert.0lx.net/article-1512.htm kryptonite bicycle lock video] [http://betheres.qsh.eu/comment-233.htm indian lesbian movie] [http://fispruil.qsh.eu/news677.html super club video tron] [http://flheddin.qsh.eu/enlabobas-456.html nude video of kasumi]  

[http://tacataca.strefa.pl/comment-890.htm sample movie gbf archive] [http://hencnac4t.is-the-boss.com/news-jimmy-crack-corn-2008-12-28.html jimmy crack corn history] [http://varpasz.is-the-boss.com/article123.htm nine inch nails discography torrent] [http://qasletop.is-the-boss.com/getrop.html intellisync crack serial] [http://tarobasal.strefa.pl/article1521.htm musice video girls]  

[http://tacataca.strefa.pl/comment-890.htm sample movie gbf archive] [http://hencnac4t.is-the-boss.com/news-jimmy-crack-corn-2008-12-28.html jimmy crack corn history] [http://varpasz.is-the-boss.com/article123.htm nine inch nails discography torrent] [http://qasletop.is-the-boss.com/getrop.html intellisync crack serial] [http://tarobasal.strefa.pl/article1521.htm musice video girls]  

{{stub}}

{{stub}}

MozLCDB is a tool made for localization of various Mozilla (Gecko) based products. It is designed to resolve issues introduced since Mozilla Firefox 1.0 branch, and a replacement for MozillaTranslator.<br>

MozLCDB is a tool made for localization of various Mozilla (Gecko) based products. It is designed to resolve issues introduced since Mozilla Firefox 1.0 branch, and a replacement for MozillaTranslator.<br>

<br>

<br>

by [[User:Milo|Milo]]

by [[User:Milo|Milo]]

This is Hung-Te Lin, maintainer of Traditional Chinese Mozilla Localization and the famous "mozip" (a tool to make Win32 localized builds).

This is Hung-Te Lin, maintainer of Traditional Chinese Mozilla Localization and the famous "mozip" (a tool to make Win32 localized builds).

<br /><br />

<br /><br />

<br /><br />

<br /><br />

I have been using MozillaTranslator for years (whether the official builds or my own tweaked versions) since Mozilla M14 (Milestone 14, not 1.4. The M series are older than Mozilla 0.6). During these years MT works O.K although more and more extra works have to be done because Mozilla locale structure changes all the time.

I have been using MozillaTranslator for years (whether the official builds or my own tweaked versions) since Mozilla M14 (Milestone 14, not 1.4. The M series are older than Mozilla 0.6). During these years MT works O.K although more and more extra works have to be done because Mozilla locale structure changes all the time.

<br /><br />

<br /><br />

<br /><br />

<br /><br />

Since the landing of Mozilla Firefox 1.0PR, localizers of Mozilla* suffered from the huge changes in Mozilla locale structure and new CVS requirements. Unfortunately, MozillaTranslator does not work anymore. Although MT has released new versions to solve issues, after trying MT5.04 I think it's time to develop a new tool which is more robust or I have to manually do many extra work for all versions. With my experience in localization, I proposed what I need and made a new tool, named MozLCDB. This name is a little weird because the better name 'MLDB' is already taken by others. Hmmm. Maybe MLD?

Since the landing of Mozilla Firefox 1.0PR, localizers of Mozilla* suffered from the huge changes in Mozilla locale structure and new CVS requirements. Unfortunately, MozillaTranslator does not work anymore. Although MT has released new versions to solve issues, after trying MT5.04 I think it's time to develop a new tool which is more robust or I have to manually do many extra work for all versions. With my experience in localization, I proposed what I need and made a new tool, named MozLCDB. This name is a little weird because the better name 'MLDB' is already taken by others. Hmmm. Maybe MLD?

I'm not an perl guru so this script is not perfect nor elegant now, but it helped me to generate a working Firefox 1.0PR locale without too much effort (in comparision to fight with MozillaTranslator).

I'm not an perl guru so this script is not perfect nor elegant now, but it helped me to generate a working Firefox 1.0PR locale without too much effort (in comparision to fight with MozillaTranslator).

<br /><br /><br /><br />

<br /><br /><br /><br />

<br /><br />

<br /><br />

by [[User:tszkin|tszkin]], modded by [[User:Kourge|Kourge]]

by [[User:tszkin|tszkin]], modded by [[User:Kourge|Kourge]]

MozLCDB is focused to Mozilla Localization. In comparsion to MozillaTranslator, you'll notice that:

MozLCDB is focused to Mozilla Localization. In comparsion to MozillaTranslator, you'll notice that:

* MozLCDB is just a perl script with command line only, no GUI.<br>

* MozLCDB is just a perl script with command line only, no GUI.<br>

* Easily modified if you understand Perl.<br>

* Easily modified if you understand Perl.<br>

<br>

<br>

by a guest on the forums

by a guest on the forums

You need these stuff:

You need these stuff:

* (optional) Knowledge of Perl if you got problems or want to modify it  

* (optional) Knowledge of Perl if you got problems or want to modify it  

<br />

<br />

by [[User:Josesun|Jose Sun]]

by [[User:Josesun|Jose Sun]]

Get these files:

Get these files:

**Version 0.1 (a little buggy)

**Version 0.1 (a little buggy)

by [[User:Josesun|Jose Sun]]

by [[User:Josesun|Jose Sun]]

This section explains the basic idea about MozLCDB. It helps you to understand it more although you may use it without knowing anything explained here. Yes, you can go to "Usage:" sections if you are in a hurry. However it is highly recommended to get things clear before you start.

This section explains the basic idea about MozLCDB. It helps you to understand it more although you may use it without knowing anything explained here. Yes, you can go to "Usage:" sections if you are in a hurry. However it is highly recommended to get things clear before you start.

<br /><br />

<br /><br />

I'm trying to explain the workflow of MozLCDB here. Don't worry about the terms quoted, they will be explained in following subsections.

I'm trying to explain the workflow of MozLCDB here. Don't worry about the terms quoted, they will be explained in following subsections.

<br /><br />

<br /><br />

<br /><br />

<br /><br />

MozLCDB tries to record everything in a text file named 'mozlcdb.txt'. It is saved in perl Dump format, however it is still readble ( if you know a little perl) and also called as the 'glossary' (due to MT) or 'database'. And there's another format of input that MozLCDB can read: the input (editing) table. It is more human readble and looks like DOS/WIN INI or GNU PO format. The default file name of this kind file is 'current.txt'. When importing from and exporting to Mozilla locale directories, currently MozLCDB recognizes only DTD and ".properties" files.

MozLCDB tries to record everything in a text file named 'mozlcdb.txt'. It is saved in perl Dump format, however it is still readble ( if you know a little perl) and also called as the 'glossary' (due to MT) or 'database'. And there's another format of input that MozLCDB can read: the input (editing) table. It is more human readble and looks like DOS/WIN INI or GNU PO format. The default file name of this kind file is 'current.txt'. When importing from and exporting to Mozilla locale directories, currently MozLCDB recognizes only DTD and ".properties" files.

<br /><br />

<br /><br />

import means to read locales from Mozilla files into the database.<br />

import means to read locales from Mozilla files into the database.<br />

export means to write locales from database into real Mozilla files.<br />

export means to write locales from database into real Mozilla files.<br />

update means to read locales from an input (editing table) into the database.<br /><br />

update means to read locales from an input (editing table) into the database.<br /><br />

Mozilla locale is stored in a hierarchical directory structure, also refered as chrome node. So you will see a very long path like "locale/en-US/global/global.dtd" in the directory you pulled from CVS or extracted from a language pack. MozLCDB mostly runs with the level just after where 'en-US' sits, so whether you're working with CVS or language pack, you must move directories (or move mozlcdb program and files) and assign correct ROOT path to fit thie rule. Then it can be called as a 'prepared directory'. (P.S: Actually, you can run in any level of directories. But you may get problems if you work in that way.)

Mozilla locale is stored in a hierarchical directory structure, also refered as chrome node. So you will see a very long path like "locale/en-US/global/global.dtd" in the directory you pulled from CVS or extracted from a language pack. MozLCDB mostly runs with the level just after where 'en-US' sits, so whether you're working with CVS or language pack, you must move directories (or move mozlcdb program and files) and assign correct ROOT path to fit thie rule. Then it can be called as a 'prepared directory'. (P.S: Actually, you can run in any level of directories. But you may get problems if you work in that way.)

<br /><br />

<br /><br />

=== ROOT ===

=== ROOT ===

What's the ROOT? It's a PATH to help MozLCDB find corresponding locale path. For example, if my current directory is D:\Mozilla\LC (Win) or /home/moz/lc (UNIX) and my locale is in full path of D:\Mozilla\LC\locale\en-US\global\... or /home/moz/lc/locale/en-US/global/..., then you have to use ROOT as locale/en-US.

What's the ROOT? It's a PATH to help MozLCDB find corresponding locale path. For example, if my current directory is D:\Mozilla\LC (Win) or /home/moz/lc (UNIX) and my locale is in full path of D:\Mozilla\LC\locale\en-US\global\... or /home/moz/lc/locale/en-US/global/..., then you have to use ROOT as locale/en-US.

<br /><br />

<br /><br />

What really happened when you 'import'? MozLCDB will scan and walk through all files inside the 'prepared directory' assigned by ROOT. Currently, only *.dtd and *.properties will be processed. All other files will be ignored.

What really happened when you 'import'? MozLCDB will scan and walk through all files inside the 'prepared directory' assigned by ROOT. Currently, only *.dtd and *.properties will be processed. All other files will be ignored.

<br /><br />

<br /><br />