7 The dgit source package contains dgit and git-debrebase.
8 These are useful for a variety of different users and in different
9 situations. So there are various documents aimed at various users.
11 * dgit and git-debrebase both support message translation.
13 * Documentation translation is handled via po4a, in the po4a
14 directory. The documeents are all manpages.
16 * git-debrebase is currently mostly useful within the Debian project,
17 but this will change and its document translations will then be more
20 The en_US message translation is slightly special. It is used for
21 testing the translation machinery, and since the source native
22 language is en_GB, there is not much other need for the en_US
26 Translatation priorities
27 ------------------------
31 po4a/dgit-user_1.pot How to use dgit to as a downstream or user
35 po/messages.pot All the messages for both programs
38 po4a/dgit-downstream-dsc_7
39 po4a/dgit-sponshorship_7
44 po4a/dgit-maint-* } For work within the Debian project
45 po4a/dgit-nmu-simple_7 } (where one needs good English anyway)
47 po4a/git-debrebase_* Currently low priority but this will change
50 Translation organisation
51 ------------------------
53 po/messages.pot all messages from both dgit and git-debrebase
54 po/LANG.po translations of those
55 po/mo output directory, do not look here
57 po4a/MAN_S.pot paragraphs from manpage MAN in section S
58 po4a/MAN_S.LANG.po translation of manpage MAN(S) into LANG
59 po4a/po4a.cfg config file for po4a
60 po4a/LANG.preview preview for you, see below
61 po4a/translated/ output directory, do not look here
67 git-debrebase has a fairly complex underlying model, which is defined
70 It is importnt when translating both documents and messages for
71 git-derebase, that consistent translations are used for the words
72 defined in `TERMINOLOGY' and `BRANCH CONTENTS'.
74 You may want to start by reading git-debrebase(5).
76 When translating git-debrebaase(5) itself, please add the English term
77 after the definining use of each word. For example
78 Your-word-for-pseudomerge (Pseudomerge)
79 translation of the definition
80 This will be useful because some of these words appear in
81 necessarily-untranslated but user-visible protocol elements
82 (eg sometimes in annotations in autogenerated git commit messages)
92 2. edit LANGUAGE.po to add translations.
96 1. edit po4a.cfg to add your language to [po4a_langs]
99 3. edit each MANPAGE_SECTION.LANG.po to add translations.
102 Important commands for translators
103 ----------------------------------
107 make LANGUAGE.po Creates or updates messages.pot and LANGUAGE.po.
109 make pofiles Updates messages.pot from all the sources,
110 with new messages, and merges them into
111 all the language-specific .po files
113 make check Updates everything and then checks everything,
114 printing translation statistics.
118 po4a po4a.cfg Updates all pot and po files
120 make preview.LANG Makes a directory preview.LANG containing
121 translated and compiled manpages which can
122 be previewed with `man -l', and prints a
123 list of appropriate `man -l' commands.