* Please note that InfoSiAL is not responsible for the accuracy of the translations.
Current translation processes
These are the current language branches for translating
Abanq:
Do you want to collaborate?
- If your language is not currently listed, you can start the translation process explained below. Just contact us and we will open a translation branch for your language and you'll be in charge of it.
- If your language is currently under development, contact the responsible and offer her/him your help.
- If your have tested some of the translations and have found errors or lacks, please inform us.
First steps
All the texts and phrases that a
Abanq user sees in the application can be translated to any language. This is possible by the
translation files, or
.ts files.
The content of these files is plain text in XML format. It is a set of phrases in the original language (spanish) plus the translation phrase to the corresponding language. There is a .ts file for every language and for every Abanq module, plus a file for the base application.
The translation files are name following the rule module_name.language_code.ts
Example: flfactppal.en.ts: Translation file to english (en) for the main (ppal) module of the Invoicing (fact) area.
The base application (the core program of Abanq, which hosts the modules) has its own translation file (sys), for english it is the sys.en.ts.
The .ts files can be found in
facturalux-modules-dir/area-name/module-name/translations
for example:
/home/your-name/modulos/contabilidad/principal/translations
When Abanq is launched, the content of the translation files for the local system language is charged, and all the phrases appear in the local language. If a translation file does not exist or is incomplete, the phrases will show in the original language (spanish). The local system language can be set by the command
export LANG=yourLanguage_yourZone, for example:
export LANG=en_US
How to translate
For translating the only thing you need is to use the qt translation program: "linguist", that is installed with
Abanq. You'll find it in
facturalux-dir/lite-instalacion/bin/linguist
The complete guide to this program for translators:
http://doc.trolltech.com/4.0/linguist-translators.html
What you have to do is open the .ts files in linguist, and translate all the phrases. To test the translations:
- Install the last version of the base application of Abanq.
- In a console, type: export LANG=your-zone_your-language (example: export LANG=en_US);
- Then, in the console, launch Abanq: fllite
- Reload the modules for which you made the translations.
Read this before translating!
When translating, please take into account this:
The translation process consists in translating lots of strings contained
in .ts and other files. These strings may come from several sources, but
mainly from tables and forms. Translating the tables is not a problem as all
the strings are contained in the function QT_TRANSLATE_NOOP().
The forms (.ui files) are different. The program in charge of this job is not
working properly extracting the strings. Fortunately, it extracts more (not
less) than necessary. It is extracting not only the few strings belonging to
a form: tab titles, groupbox titles, etc. It is also extracting the name of
the fields assigned to a control in the form.
For example:
- We have the table clientes.mtd (for the clients). In this table we have the
field "descripcion", and the title (or alias) property of this field is
"Descripcion". This is the string you need to translate.
- Besides, we have the form clientes.ui associated to the table, and somewhere
within the form is the control with the name of the field "descripcion". This
string also appears in the .ts file but it must not be traslanted.
The problem you reported happens when you translate the name of a field, as
you did with "descripcion".
How can you distinguish between the aliases and the name of the fields?
First, check the context. The gross part of the strings to translate are in
the Metadata context, that is, the tables. Contexts such as "formXXXX" or
"co_i_xxxx" are normally forms.
Second, the strings of the field names, not to be translated, are in lower
case and always in one only word: "descripcion", "tipo_iva",
"co_i_desdecampo".., while the descriptions are always description-looking
such as "Nombre del cliente", "Descripci�"...
Just ignore the field names and translate the aliases. If in doubt, leave the
string untranslated. Whe you finish, launch Abanq. If you find something
untranslates, reopen the linguist tool and try to find the string (menu
edit/find)
This is something to be resolved in the future.
política de privacidad
·
términos de uso
·
webmaster
InfoSiAL S.L. C/ San Antonio 88 · 02640 Almansa (Albacete) · España - Spain · CIF: B02352961
Todos los logos y marcas son propiedad de sus respectivos dueños. Comentarios propiedad de su autor, el resto © 2008 InfoSiAL, S.L.
Diseño web y programación de InfoSiAL, S.L.