comparison DOCS/tech/translations.txt @ 12091:c67c28e4992e

How to handle incomplete translations of message files.
author diego
date Thu, 01 Apr 2004 13:53:10 +0000
parents 26d4ace59761
children 052d0e73a3a8
comparison
equal deleted inserted replaced
12090:837485aef2eb 12091:c67c28e4992e
42 42
43 will print untranslated messages to the screen, just substitute XX with your 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 44 language code. Additionally, please make sure that your translated messages fit
45 on an 80 character wide display to avoid overflowing output. 45 on an 80 character wide display to avoid overflowing output.
46 46
47 If you do not translate all messages at once, please do not leave untranslated
48 messages in your translated file, just leave them out instead. The MPlayer
49 build system automatically checks for missing messages and uses the English
50 ones instead. This has the added advantage of providing the latest versions of
51 the English messages, since English messages in translations may be outdated.
52 Furthermore, running help_diff.sh on your translated file will immediately show
53 missing messages, which eases further translation.
54
47 Translations are for documentation what porting is for code. Many more eyes 55 Translations are for documentation what porting is for code. Many more eyes
48 see it and get to find mistakes. If you stumble over mistakes, inaccuracies, 56 see it and get to find mistakes. If you stumble over mistakes, inaccuracies,
49 clumsy wording, spelling/grammar errors or if you notice that something is 57 clumsy wording, spelling/grammar errors or if you notice that something is
50 incomplete, please let us know, we'll fix it. Patches are more than welcome, 58 incomplete, please let us know, we'll fix it. Patches are more than welcome,
51 of course. 59 of course.