Contribute to the Slint project

../extra/aspell-words-lists/<packages for your language> for spelling checks

../kdei/<package kde-l10n for your language> to localize UI of Lokalize if you use it

Please register on Transifex, even if you don’t use its on line editor, then check all notification settings, as it makes easier to keep all contributors informed at once of anything of general interest. Please indicate you full name, even if you use a nickname.

We strongly suggest that you subscribe to slint-translators mailing-list. This will allow you to ask and answer questions, participate in discussions, make suggestions and proposals.

Be ready to provide an email address allowing your team’s coordinator and Slint’s maintainer to reach you.

You can also use the Discussion feature available on Transifex in your language’s page of the Slint project.

You can also follow this thread in Slackware forum of LinuxQuestions.org. For that, register to LQ and either post a message in the thread, or display it then click Thread Tools ⇒ Subscribe to this Thread (in the dark blue stripe just above the first message displayed).

Depending on the amount of work needed and available resources, there can be one translator or a team of translators per target language. In all cases, I recommend that at least one person be responsible for organizing the team’s work, checking the translations and transmitting the checked PO file to the maintainer(s). Let’s call this person the team coordinator.

Don’t feel obliged to translate verbatim. Not only is this rarely the best way to convey the meaning, but in addition this often leads to sentences too long to fit in allowed space.

Use a specialized PO editor, not a general text editor. This will not only prevent inadvertently editing msgid strings but also facilitate their work and automatize additional checks, as the presence of a variable in the translation with the same spelling as in the original.

While translating, choose a serif fixed width (or "monospaced") font, like Courier. That allow to visually distinguish characters that otherwise would look the same, and check line’s length when that matters.

If possible, check the layout of the messages. You could do that looking at the context in the relevant source file. Even better, simply run the translated script. This is especially important if you are translating dialog boxes. In particular, take care not to write too long sentences on one single line if it appears that the text can’t flow on next one.

Bear in mind that in VGA mode (used in text installers, in particular), line’s width is limited theoretically to 80 characters, but practically often to 74.

Do not add question marks that are not present in the original message.

If the message refers to tags (text on the buttons) of dialog boxes, like "OK", "Yes", "NO", "Continue", "Cancel", check how theses tags are translated in your language in dialog’s interface and use the same words.

Avoid colloquialisms and technical slang.

To "cut" (or end) a line inside a "dialog" box you should type \n: pressing [Enter] will not insert a "new line" character in the text viewed by user.

If a word beginning with a dollar sign is included in the original text it should be present in the translation with exactly the same spelling (case matters).

The translation text should include a "new line" character (or line feed, represented by "\n") at the beginning or at the end, exactly as the original text does. Conversely, if the original text doesn’t have the character, then the translation shouldn’t have it.

A single backslash character "\" is not allowed in the translation.