[SCM] live-manual branch, debian-next, updated. debian/3.0_a14-1-6-g8227199

[chals]

The following commit has been merged in the debian-next branch:
commit 82271998429a88c1ed72ade4a44936c4b3a257a1
Author: chals <chals at altorricon.com>
Date:   Tue Jul 31 22:29:29 2012 +0200

    Insisting on the fact that achieving a 100% translation is important in respect to code blocks.

diff --git a/manual/en/style_guide.ssi b/manual/en/style_guide.ssi
index b7b4092..7ba27de 100644
--- a/manual/en/style_guide.ssi
+++ b/manual/en/style_guide.ssi
@@ -216,13 +216,7 @@ Translators working initially with *{pot}* files and later on with *{po}* files
 
 _* /{Code blocks}/
 
-Some translators decide to include the code blocks in the translated files because it is easier for them to identify what has already been translated and what has not by looking at the percentages if they use a graphical translation program.
-
-Include the code blocks if you want to score a 100% complete translation.
-
-On the other hand some translators prefer to leave the code blocks "untranslated" (i.e. not including them). This makes the translation easier to maintain once finished because it does not require translators intervention if the code changes.
-
-Leave the code blocks empty (they will be automatically added then) if you want to make your translation easier to maintain.
+Even though the code blocks are usually untranslatable, including them in the translation is the only way to score a 100% complete translation. And even though it means more work at first because it requires the intervention of the translators if the code changes, it is the best way, in the long run, to identify what has already been translated and what has not when checking the integrity of the .po files.
 
 _* /{Newlines}/
 

-- 
live-manual