diff options
author | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2008-05-08 00:04:27 +0000 |
---|---|---|
committer | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2008-05-08 00:04:27 +0000 |
commit | 549dc41033bb29a516cf953b2eddbab63ea0b787 (patch) | |
tree | cdc73895f6680dc014bfa67420b3eaad322e6de6 /DOCS/tech | |
parent | 20d3bb5709a338b49cb917ab5a961c83c9996dcf (diff) | |
download | mpv-549dc41033bb29a516cf953b2eddbab63ea0b787.tar.bz2 mpv-549dc41033bb29a516cf953b2eddbab63ea0b787.tar.xz |
Move some blocks around for better text structuring.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@26687 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS/tech')
-rw-r--r-- | DOCS/tech/translations.txt | 70 |
1 files changed, 35 insertions, 35 deletions
diff --git a/DOCS/tech/translations.txt b/DOCS/tech/translations.txt index 3e5126682f..9783555556 100644 --- a/DOCS/tech/translations.txt +++ b/DOCS/tech/translations.txt @@ -8,6 +8,16 @@ in order to be useful. Otherwise they quickly get outdated and become obsolete, useless cruft. That said, we would be happy if you could maintain a new documentation translation. +Experience shows that translations work best when done by teams. Not only +can the workload be shared, but there is also the chance to review the +translation. So if possible try to find more people to help out with +translating. + +Furthermore, if you take over an unmaintained translation, bring the existing +parts up-to-date before translating new ones. Outdated information is worse +than missing information. For console messages and the XML documentation, +missing parts are automatically replaced by the English versions. + Documentation related discussions happen on the MPlayer-DOCS mailing list, while documentation translation related discussions happen on the MPlayer-translations mailing list. If you want to maintain a translation @@ -21,16 +31,6 @@ http://lists.mplayerhq.hu/mailman/listinfo/mplayer-translations Send updates and patches to this mailing list or directly to the translation coordination maintainer, see DOCS/tech/MAINTAINERS for details. -Experience shows that translations work best when done by teams. Not only -can the workload be shared, but there is also the chance to review the -translation. So if possible try to find more people to help out with -translating. - -Furthermore, if you take over an unmaintained translation, bring the existing -parts up-to-date before translating new ones. Outdated information is worse -than missing information. For console messages and the XML documentation, -missing parts are automatically replaced by the English versions. - Translations of MPlayer documentation consist of 3 parts in descending order of importance: @@ -41,6 +41,31 @@ order of importance: Please note that only doing 1) or 1) + 2) is perfectly fine. +general: +~~~~~~~~ + +Please note that the help_mp files and the XML documentation are both encoded +in UTF-8. Editing these files in a program which uses a different encoding +will result in breaking console messages and HTML. + +Translations are for documentation what porting is for code. Many more eyes +see it and get to find mistakes. If you stumble over mistakes, inaccuracies, +clumsy wording, spelling/grammar errors or if you notice that something is +incomplete, please let us know, we'll fix it. Patches are more than welcome, +of course. Do not, however, change the translation first, please get your +update into the English version first. + +If you have Subversion write access and commit a translation update, use +something like "synced with rXXX" as first line of the commit message so +that it is possible to tell with a glance at the Subversion log or ViewVC +if the translation is outdated and which revision of the English master +file it is equivalent to. + +If you make (spelling/wording/consistency/etc) changes to a file without +adapting parts that changed in the English master file, leave the sync +tag as it is. + + console messages: ~~~~~~~~~~~~~~~~~ @@ -85,31 +110,6 @@ translation is in sync with. This way we can easily tell if the translation is up to date or not. -general: -~~~~~~~~ - -Please note that the help_mp files and the XML documentation are both encoded -in UTF-8. Editing these files in a program which uses a different encoding -will result in breaking console messages and HTML. - -Translations are for documentation what porting is for code. Many more eyes -see it and get to find mistakes. If you stumble over mistakes, inaccuracies, -clumsy wording, spelling/grammar errors or if you notice that something is -incomplete, please let us know, we'll fix it. Patches are more than welcome, -of course. Do not, however, change the translation first, please get your -update into the English version first. - -If you have Subversion write access and commit a translation update, -use something like "synced with rXXX" as first line of the commit message -so that it is possible to tell with a glance at the Subversion log or ViewVC -if the translation is outdated and which revision of the English master file -it is equivalent to. - -If you make (spelling/wording/consistency/etc) changes to a file without -adapting parts that changed in the English master file, leave the sync -tag as it is. - - XML documentation: ~~~~~~~~~~~~~~~~~~ |