# Translating Grisbi

### Copyright © 2001-2003 Daniel Cartron

#### English translation: Daniel Cartron

#### Proof reading: Sébastien Blondeel AKA SBI

### Last update: 2003-04-02

Grisbi needs your help for translations. If you can do some translations in a language not yet implemented, please feel free to send a mail to Daniel explaining in which language you can translate. Then it's really important to subscribe to the translation mailing list by sending this mail.

# The files to translate

There are several kinds of files to translate. We'll check all of them. All these files will be avaliable on the Grisbi's site in the section Download/Translation. However, if you want to work on the latest issues of the files, you should ask us for Git and FTP access.

## The website

Not the more usefull for the programm but the more usefull for advertising and finding some help. The files to translate are :

- grisbi-block-contact-C.txt
- grisbi-contact-C.txt
- grisbi-home-C.txt
- grisbi-infos-C.txt
- grisbi-mainmenu-C.txt
- grisbi-mirrors-C.txt
- grisbi-title-C.txt
- grisbi-version-C.txt
Once the files are translated you have to rename them with your 2 letter ISO-639 language code e.g. grisbi-home-en.txt for English or grisbi-home-fr.txt for French.

## The programm

You just have to translate the grisbi.pot file. Then rename it with your 2 letter ISO-639 language code and .po, e.g. en.po for English or fr.po for French.

## The help files

There are three HTML files and a text file:

- quickstart.html;
- grisbi-manuel.html;
- translation.html;
- topic.dat.

## The user's guide

The user's guide is made of several .tex files, a Makefile, an image directory and a tool directory. The image directory contains all the screenshots and the icons in two separate sub-directories. We will soon provide you some scripts to make the screenshots automatically. We'll also provide you a script that will warn you as soon as a .po change implies a new screenshot. But for the moment you'll have to do it by yourself. Sorry for the inconvenience. The tool directory contains the scripts (mainly in Perl) that will help you to compile the sources. The .tex files will be soon connected to the .po files, so you won't have to translate any text that appears in the GUI.

# How to translate

We'll give you some advice that you are not abliged to follow. Only the result matters...

## The website

As they are HTML files, you can use any editor you want. You can use a text editor or an editor dedicated to the HTML as Bluefish or Quanta+.

## The program

The .po file can be translated easily with Kbabel, Emacs, or even some VI clone... Choose the one you want. If you are not used to any of these programs, Kbabel will certainly be the easiest one for you.

## The help files

As they are HTML and text files, you can use any editor you want for translating them. Just be careful not to translate the tags, only the text :-) For the topic.dat you must only translate the second term of each line (which is the label of the entry in the help menu) but not the first one (which is the name of the related file).

## The user's guide

The user's guide is written in LaTeX, including macros which will help to compile the source in two differents types, text-only or illustrated. We therefore advise you to keep this format. If you are not used with LaTeX, you should try Kile, which is a LaTeX-editor dedicated to KDE. If you really want another file format, let us know, but you'll probably have difficulties to maintain two differents types at the same time...

# How to verify

Before commiting your translations it's your duty to control they will work.

## The website

As the website uses text files with the HTML tags you just have to write them with an HTML editor and then copy the text part between tne body and /body tags and it should work. Anyway, if it doesn't, it's easy to see on the site, so you just have to correct.

## The program

You should be able to compile the program on your box. If you never do such a thing don't panic we'll help you. You just have to install the needed libraries then compile as it's explained in the user's guide.

## The help files

They are HTML and TXT files, so it's easy to see if they work. And if you copy them in the right location on your box you can see imediately if it's correct. The directory of your language is /usr/share/gnome/help/grisbi/lang where lang is the 2 letters code for your language.

## The user's guide

If you use the LaTeX files you just have to compile them with the tools provided, and then control the result either in HTML or PDF format.

# How to commit

Once you are satisfied, you have to commit your work in order to let the community use it.

## The website

The best way is to ask our webmasters to give you an access just for your language, so you can add or modify the texts as you want. Send a mail to the webmasters to ask for such an access.

## The programm

This file have to be commited in the code sources, so if you're a lone translator, you just can send the .po file to Daniel who will commit it for you. If you work in a team it's more efficient that one of you asks for the rights to commit the .po and doc files, so you just have to deal with him (or her) for the commits.

## The help files

See above.

## The user's guide

The scripts to publish the guide are in the makefile (make transfer). You will need the config files, so just ask to Daniel the needed files.