File: README.txt

package info (click to toggle)
lazarus 2.0.0%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 214,460 kB
  • sloc: pascal: 1,862,622; xml: 265,709; cpp: 56,595; sh: 3,008; java: 609; makefile: 535; perl: 297; sql: 222; ansic: 137
file content (32 lines) | stat: -rw-r--r-- 1,112 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
The <lazarusdir>/components/codetools/languages directory contains all the stuff
for internationalization of the codetools.

All text and messages used in the codetools should be placed into the unit
codetoolsstrconsts.pas. This unit uses a resourcestring section, so that the
compiler will create the
<lazarusdir>/components/units/codetoolsstrconsts.rst file.

The following is a in detail description of updating the language files for
the codetools. Normally you can just execute the <lazarusdir>/localize.sh
script.

Since this is a fpc-only format it must be converted with the rstconv program:

cd <lazarusdir>/components/codetools/languages
rstconv -i ../../units/codetoolsstrconsts.rst -o codetools.po

This will create the file codetools.po, which should be translated in all
required languages to a codetools.xx.po file. For the xx see the gettext unit
in the procedure TranslateResourceStrings.

german: codetools.de.po


After the translation, the codetools.xx.po file is converted to an .mo file
with the msgfmt program:

msgfmt -v -o codetools.xx.mo codetools.xx.po

where xx is the language id.