Bugzilla:L10n:Guide

Thus guide is under construction bug 412654. Previous version is available.

Overview

This guide provides new localizers a step by step howto to localize Bugzilla in their own locale.

It also contains useful resources links to get the contribution done and to keep the localization up-to-date.

Getting Started

You should first look if somebody else is already working on localizing Bugzilla in your locale.
This page shows all the localized Bugzilla releases we aware of. If you cannot find the version of Bugzilla you want to localize on this page, that doesn't mean that this version is not currently handled. So, please contact the current maintainer or team to avoid duplicated effort. Current active locales can be found in this section.
Once you are sure that nobody is already working on your locale or when you have coordinated with the current team/owner, you can start with the localization.

Obtaining The Source Files

Unless you are sure about the release you want to localize, we advise you to start with the latest stable version. See the Release page to see the latest version and to download the tar.gz archive.
Uncompress the tarball with your favorite tool in an empty directory.
You should have the following tree structure (note: all subdirectories and files are not detailed here):

bugzilla-X.Y.Z (where X.Y.Z are the numbers for the release)
   --Bugzilla
   --contrib
   --docs
   |  --lib
   |  --pdf
   |  --txt
   |  --xml
   |  --html
   |  --images
   |
   --images
   --js
   --skins
   --t
   --templates
   |  --en
   |      --default
   |      --extensions
   .UPGRADING
   .UPGRADING-pre-2.8

The localizable contents are located under the following directories:
docs/xml
templates/en
The files UPGRADING and UPGRADING-pre-2.8 are also localizable.

You should focus first on the /templates directory, which contains all the files used to build the user interface.
First, remove all the /CVS subdirectories under the /templates directory:

GNU/Linux

$cd templates
$rm -rf `find . -name CVS`

Windows

TBD

Mac

TBD

Then, you should rename the /en subdirectory for your locale name.
For instance, you can use fr for French or ca for Catalan.
You can also use a four-letter locale code:
For instance, pt-BR for Brazilian Portuguese or zh-CN for Chinese (Simplified).
See page TBD for the locale code that best fit for your locale.

The task

Terminology

Before running into localizing the files, you should set up a terminology for the Bugzilla specific terms, in order to stick to it, that is to say, you will always use the same localization for a given term.
For instance, start thinking about the localization of some of these tricky terms:

• Whine/Whining
• Requestee
• Flags
• etc.

and create your localized Bugzilla glossary.

Resources

Current active locales and maintainers

Locale	Locale Code	Maintainer	Email	Site
العربية/Arabic	[ar]	محمد السباعي (Muhammad Alsebaeyie)	Email	Site
Беларуская/Belarusian	[be]	Сяргей (Siarhei)	Email	Site
Български език/Bulgarian	[bg]	Георги Д. Сотиров (Georgi D. Sotirov)	Email	Site
Čeština/Czech	[cs]	Norbert Volf	Email	Site
Deutsch/German	[de]	Marc Schumann	Email	Site
Français/French	[fr]	Cédric Corazza	<cedric.corazza at wanadoo.fr>	Frenchmozilla
Italiano/Italian	[it]	Marco Cucinato	Email	Site
한국어/Korean	[ko]	심우곤/WooGon Shim	Email	Site
Nederlandse/Dutch	[nl]	Hendrik Maryns	Email	Site
Polski/Polish	[pl-PL]	AviaryPL	Email	Site
Portugues (Brasil)/Brazilian Portuguese	[pt-BR]	Felipe Gaucho	Email	Site
Русский/Russian	[ru]	Vitaly Fedrushkov	Email	Site
Español (España)/Spanish (Spain)	[es-ES]	Oscar Manuel Gómez Senovilla	Email	Site
Español (México)/Spanish (Mexico)	[es-MX]	Javier Abdul Córdoba Gándara	Email	Site
Español (Paraguay)/Spanish (Paraguay)	[es-PY]	?	Email	Site
中文/Chinese (Simplified)	[zh-CN]	天下 (Hou Guangmin)/蒋艳 (jiangyanfeng)	Email	Site
繁體中文/Chinese (Traditional)	[zh-TW]	嘉利 (SMA)	Email	Site

Tools

WinMerge

WinMerge is an Open Source visual text file differencing and merging tool for Win32 platforms. With full UTF-8 support, it is highly useful for determing what has changed between project versions, and then merging changes between versions.