forked from RapidSVN/RapidSVN
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTRANSLATIONS
70 lines (48 loc) · 1.97 KB
/
TRANSLATIONS
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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
Creating translations for RapidSVN.
The directory structure for the user interface
translations is as follows:
rapidsvn
+-src
+-locale
+-rapidsvn.pot This is a template file
| containing all the strings
| used in RapidSVN.
+-de This is a directory that
| contains the files
| necessary for the
| German translation
+-rapidsvn.po This file contains a plain-text
| German translation
+-rapidsvn.mo Binary message catalog, that
will be used by RapidSVN to
display the translated user
interface.
Whenever a new text string in the RapidSVN source code
is added, updating the translation template rapidsvn.pot and
all the translated rapidsvn.po files is necessary.
Since there are not too many changes to the user interface
between subsequent releases of RapidSVN it is sufficient to
update that translation a week or two before creating a new
release.
The following steps have to be performed for updating the
translation:
1. Recreate the template file and merge the old translations and the new strings
To extract all the strings in the cpp source code files
(only strings that should be translated are marked by
_("my string")), open a shell and chdir to "src/locale";
now run:
./update.sh
2. Update the translations
This step has to be performed for every language.
The most easy way to check and update a translation is
to use the tool poEdit:
poedit rapidsvn.po
3. Compile the translations
Change to the directory "src/locale" and
compile the translations:
./fmt.sh
4. Check the result in RapidSVN
Change to "src".
Set the appropriate locale:
export LANG=<locale> (e.g. de_DE, en_US)
Run rapidsvn and check the user interface.