1JGMENU-I18N(1) JGMENU-I18N(1)
2
3
4
6 jgmenu-i18n - support translation of jgmenu flavoured CSV menu data
7
9 jgmenu_run i18n <translation-file>
10
11 jgmenu_run i18n --init [<translation-file>]
12
14 jgmenu_run i18n reads jgmenu flavoured CSV menu data from stdin and ei‐
15 ther translates it, or creates a po style translation file
16
17 The <translation-file> argument can be a file or directory. If it is
18 the latter, translation files will be searched for in this directory
19 based on the environment variable $LANG, which will be assumed to be in
20 the format ll_CC.UTF8 where ll is an ISO 639 two-letter language code
21 and CC is an ISO 3166 two-letter country code. Files named ll_CC and
22 ll will be used in said order.
23
25 --init Create a template po style translation file with blank msgid en‐
26 tries
27
29 Create translation file template for manual translation
30 Modules jgmenu-apps(1) and jgmenu-ob(1) have built-in i18n support. In
31 order to use this features, a translation file is required. Here fol‐
32 low examples of how a translation file can be created:
33
34 Example 1.
35
36 jgmenu_run ob | jgmenu_run i18n --init >sv
37
38 Example 2.
39
40 jgmenu_run i18n --init <prepend.csv >sv
41
42 The result of the above commands would be a skeleton translation file
43 (sv in this case) containing entries like this:
44
45 msgid "Web Browser"
46 msgstr ""
47
48 Manually translate the empty msgstr fields.
49
50 Use translation file
51 If using modules jgmenu-apps(1) or jgmenu-ob(1), just set csv_i18n in
52 jgmenurc to directly point to a translation-file or a directory con‐
53 taining translation files.
54
55 In special circumstances, you may wish to include i18n in command
56 plumbing. Here follow an example of how this could be constructed:
57
58 <csv-generating-command> \
59 | jgmenu_run i18n <translation-file> \
60 | jgmenu --vsimple
61
63 Johan Malm.
64
65
66
67 15 February, 2020 JGMENU-I18N(1)