Name Date Size

..25-Oct-20244 KiB

bg.poH A D25-Oct-2024177.1 KiB

ca.poH A D25-Oct-2024177.7 KiB

ca@valencia.poH A D25-Oct-2024177.5 KiB

cs.poH A D25-Oct-2024156.3 KiB

da.poH A D25-Oct-2024157.6 KiB

de.poH A D25-Oct-2024171.7 KiB

en_GB.poH A D25-Oct-2024167.5 KiB

eo.poH A D25-Oct-2024162.1 KiB

es.poH A D25-Oct-2024166.1 KiB

fi.poH A D25-Oct-2024154.2 KiB

fr.poH A D25-Oct-2024177.6 KiB

gl.poH A D25-Oct-2024165.3 KiB

he.poH A D25-Oct-2024181 KiB

hu.poH A D25-Oct-2024133.5 KiB

it.poH A D25-Oct-2024176 KiB

ja.poH A D25-Oct-2024153 KiB

LINGUASH A D25-Oct-2024159

MakevarsH A D25-Oct-20242.2 KiB

nb.poH A D25-Oct-2024135.9 KiB

nl.poH A D25-Oct-2024171.6 KiB

pl.poH A D25-Oct-2024164.1 KiB

POTFILES.inH A D25-Oct-20241.7 KiB

pt.poH A D25-Oct-2024140 KiB

READMEH A D25-Oct-20242.9 KiB

ru.poH A D25-Oct-2024214.2 KiB

sv.poH A D25-Oct-2024165.8 KiB

uk.poH A D25-Oct-2024213.7 KiB

zh_CN.poH A D25-Oct-2024160.6 KiB

README

12003-02-06
2
3This directory contains translations for the options of the SANE backends.
4They are only used if the gettext tools are found by configure.
5You will need GNU gettext: xgettext, msgfmt and msgmerge. The translations
6are used at least by the frontends XSane and quiteinsane.
7
8
9Users: I want to just read the description of SANE options in my language
10-------------------------------------------------------------------------
11
12Use XSane (>=0.90) or your favourite frontend that supports translations, read
13the documentation and set the environment variable LANG to your local setting.
14Example for German: export LANG=de_DE ; xsane
15
16
17Translators: I want to update existing translations
18---------------------------------------------------
19
20* cd po ; make update-po
21* Edit $lang.po, add/change translations. (with $lang = your
22  language, e.g. "de"). You need an editor that is capable of using the
23  encoding UTF8 (unicode).
24* Add your name to the header. Update the "last translator" field.
25* make ; make install
26
27
28Translators: I want to add a new language
29-----------------------------------------
30
31* Add the language code to po/LINGUAS
32* ./config.status || ./configure
33* cp po/sane-backends.pot po/$lang.po
34  Replace $lang with the language code you added to po/LINGUAS.
35* Go ahead with "I want to update existing translations".
36
37
38Backend developers: I want to add internationalization support for my backend
39-----------------------------------------------------------------------------
40
41* Edit the source code of the backend and add SANE_I18N to the appropriate
42  strings. Mark the descriptions (desc) and titles of options with
43  SANE_I18N(). Do the same for string lists used in options. The name of
44  options must NOT be marked. Do NOT mark macros. Especially you don't need
45  to mark standard option strings like SANE_TITLE_NUM_OPTIONS as this is
46  already done in saneopts.h.
47  Examples: s->opt[5].title = SANE_I18N("Enhancement");
48            #define STANDARD_FORMAT SANE_I18N("a4 Paper")
49* Edit po/POTFILES.in. Add all source code files that contain strings marked
50  by SANE_I18N() to that file.
51* If you want to also add a new language, see above.
52* ./config.status || ./configure
53* See "Update existing translations" or "Add a new language".
54
55
56Frontend developers: I want to add internationalization support for my frontend
57-------------------------------------------------------------------------------
58
59* The Makefile installs files called "sane-backends.mo" in the directory
60  "$(prefix)/share/locale/lang/LC_MESSAGES/", e.g.:
61  "/usr/local/share/locale/de/LC_MESSAGES/sane-backends.mo". For every
62  language exactly one .mo file is installed. Earlier releases of
63  sane-backends installed one file per backend, e.g. sane-umax.mo. For
64  backward compatibility, frontends may want to check for these files, also.
65* As mentioned above, GNU gettext is used.
66* With other NLS implementations, converting the mo files may work.
67