Debian Codegraph @

README.TRANSLATION

raw
1 (1) Prerequisites
2
3 Make sure that GNU gv has been installed if you want to test the translation.
4 In this case also make sure you have turned on international mode for GNU gv
5 (see README.I18N for details).
6
7 Otherwise compiling GNU gv and taking the generated file
8 "src/gv-update-userconfig" will be enough.
9 Also make sure that perl 5.8 or newer is working.
10
11
12
13 (2) File names of the translation file
14
15 The file has to be named "$LOCLAE.dat", where $LOCALE may be e. g. "de_AT.utf8"
16 for the austrian locale. See appendix "(B) Naming locales" for details.
17
18 If you do not have a translation file, start with an empty one, that is,
19 create one with "touch $LOCALE.dat".
20
21
22
23
24 (3) Getting the file to translate / Updating it
25
26 simply run "gv-update-userconfig -i $LOCALE.dat"
27
28 This command will add all strings that are not in the translation file to the
29 end of that file.
30
31
32
33 (4) Translating the strings
34
35 After (3) you will find in your $LOCALE.dat many lines like the followings:
36
37 GV*copyright.Label: Copyright
38 GV*miscmenuLabel.label: Misc Menu Entries
39 GV*optionsgv.Label: gv Options ...
40 GV*mark.Label: Mark
41 GV*dismiss.Label: Dismiss
42
43 Just overwrite the right hand side with your translation.
44
45
46
47 Important: Do not change the "GV.version" resource which may look like the
48 following:
49
50 GV.version: gv 3.6.7.90
51
52
53 (5) Testing your translation (optional)
54
55 Create a symlink "~/.gv-$LOCALE" to the rranslation file $LOCALE.dat unless you have already done so.
56
57 Just run gv, your symlink "~/.gv-$LOCALE" will ensure that your translation is
58 used instead of GNU gv's own strings.
59
60
61
62 (6) Submitting the translated files
63
64 See my job discription on http://sv.gnu.org/projects/gv for details.
65
66 I'll check if they are syntactically correct and copy them to "src/nls" in the
67 distribution tarball of GNU gv and update the src/nls/LANGUAGES file.
68
69
70
71
72
73
74
75
76
77 (A) What to do of more locales share the same translation strings?
78
79 src/nls/LANGUAGES can contain aliases for languages.
80 Assume "de_CH.utf8" uses the same translation strings as "de_AT.utf8".
81 "echo 'de_AT.utf8 -> de_CH.utf8' >> LANGUAGES" tells GNU gv to use the
82 strings from the locale "de_AT.utf8" for the locale "de_CH.utf8".
83
84
85
86
87 (B) Naming locales
88
89 A locale is named "language[_territory][.codeset][@modifier]".
90
91 If the complete locale does not match to one of the translations, the modifier
92 is removed. If this still does not match, the territory is removed.
93
94
95 IMPORTANT NOTE:
96 If international mode is turned off, the locale is prefixed with "noint:", e. g.
97 "noint:en_US". So locales are named "noint:language[_territory]".
98
99 Note that multibyte characters are not available in non-international mode.
100 For that reason it is wise not to use the translation from the international mode
101 for the non-international mode and codeset and modifier are not used to identify a
102 translation.
103 It's ok not to provide a translation for the non-international mode. But you can
104 provide one if you think that this is a good idea.
105
106
107
108
109
110 TODO: Which charset to use in non-international mode? 7-bit-ASCII might be a
111 good choice.