Mercurial > mplayer.hg
annotate DOCS/tech/translations.txt @ 12110:a34dc5a369ca
restrictions to ensure that O(log n) seeking and error recovery is possible
author | michael |
---|---|
date | Sat, 03 Apr 2004 13:23:44 +0000 |
parents | c67c28e4992e |
children | 052d0e73a3a8 |
rev | line source |
---|---|
11809 | 1 ________________________________________ |
2 HOW TO DO A GOOD TRANSLATION FOR MPLAYER | |
3 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
4 | |
5 We always welcome new translations, but please be aware that | |
6 translations are not just one time jobs. They have to be maintained | |
7 in order to be useful. Otherwise they quickly get outdated and become | |
8 obsolete, useless cruft. That said, we would be happy if you could | |
9 maintain a new documentation translation. | |
10 | |
11 Documentation related discussions happen on the MPlayer-DOCS mailing list. | |
12 If you want to maintain a translation you should subscribe there, as all | |
13 documentation CVS changelogs are also sent there, which you need to keep | |
14 the translation up to date. You can subscribe here: | |
15 | |
16 http://mplayerhq.hu/mailman/listinfo/mplayer-docs | |
17 | |
18 Send updates and patches to this mailing list or directly to the documentation | |
19 or console message maintainers, see DOCS/tech/MAINTAINERS for details. | |
20 | |
21 Translations of MPlayer documentation consist of 3 parts in descending | |
22 order of importance: | |
23 | |
24 1) console messages (help/help_mp-XX.h) | |
25 2) man page | |
26 3) XML documentation | |
27 | |
28 Please note that only doing 1) or 1) + 2) is perfectly fine. | |
29 | |
30 You can find the latest versions of the help_mp-XX.h files in CVS or | |
31 here: | |
32 | |
33 http://www.mplayerhq.hu/cgi-bin/cvsweb.cgi/main/help/ | |
34 | |
35 help_mp-en.h is the master file that you should use as a base for translations. | |
36 If you are adopting an already existing translation, please check it from top | |
37 to bottom once. Later it should suffice to just translate missing messages. If | |
38 you want to check for untranslated messages the help/help-diff.sh script comes | |
39 in handy: | |
40 | |
41 help_diff.sh help_mp-XX.h < help_mp-en.h | |
42 | |
43 will print untranslated messages to the screen, just substitute XX with your | |
44 language code. Additionally, please make sure that your translated messages fit | |
45 on an 80 character wide display to avoid overflowing output. | |
46 | |
12091
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
47 If you do not translate all messages at once, please do not leave untranslated |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
48 messages in your translated file, just leave them out instead. The MPlayer |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
49 build system automatically checks for missing messages and uses the English |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
50 ones instead. This has the added advantage of providing the latest versions of |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
51 the English messages, since English messages in translations may be outdated. |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
52 Furthermore, running help_diff.sh on your translated file will immediately show |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
53 missing messages, which eases further translation. |
c67c28e4992e
How to handle incomplete translations of message files.
diego
parents:
11809
diff
changeset
|
54 |
11809 | 55 Translations are for documentation what porting is for code. Many more eyes |
56 see it and get to find mistakes. If you stumble over mistakes, inaccuracies, | |
57 clumsy wording, spelling/grammar errors or if you notice that something is | |
58 incomplete, please let us know, we'll fix it. Patches are more than welcome, | |
59 of course. |