[SCM] live-manual branch, debian, updated. debian/3.0_a10-1-39-g216427c
chals
chals at altorricon.com
Tue Apr 3 07:21:41 UTC 2012
The following commit has been merged in the debian branch:
commit 343a660be8c3705762416fd5f1f9da4fa703a5be
Author: chals <chals at altorricon.com>
Date: Sat Feb 11 16:55:34 2012 +0100
Adding Appendix:Style guide, thanks to my co-translator jlz.
diff --git a/manual/de/about_manual.ssi b/manual/de/about_manual.ssi
index d01ce5b..44aa15e 100644
--- a/manual/de/about_manual.ssi
+++ b/manual/de/about_manual.ssi
@@ -279,7 +279,7 @@ code{
}code
-3~ Translation
+3~translation Translation
To submit a translation for a new language, follow these three steps:
diff --git a/manual/de/live-manual.ssm b/manual/de/live-manual.ssm
index 84d2856..c89135d 100644
--- a/manual/de/live-manual.ssm
+++ b/manual/de/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Dieses Programm ist freie Software. Sie können es unter den Bedingungen der GNU General Public License, wie von der Free Software Foundation veröffentlicht, weitergeben und/oder modifizieren, entweder gemäss Version 3 der Lizenz oder (nach Ihrer Option) jeder späteren Version.<br><br>Die Veröffentlichung dieses Programms erfolgt in der Hoffnung, dass es Ihnen von Nutzen sein wird, aber OHNE IRGENDEINE GARANTIE, sogar ohne die implizite Garantie der MARKTREIFE oder der VERWENDBARKEIT FÜR EINEN BESTIMMTEN ZWECK. Details finden Sie in der GNU General Public License.<br><br>Sie sollten ein Exemplar der GNU General Public License zusammen mit diesem Programm erhalten haben. Falls nicht, siehe <http://www.gnu.org/licenses/>.<br><br>Der komplette Text der GNU General Public License kann in der Datei /usr/share/common-licenses/GPL-3 gefunden werden.
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Projekt <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Beispiele
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/de/style_guide.ssi b/manual/de/style_guide.ssi
new file mode 100644
index 0000000..3fe12c1
--- /dev/null
+++ b/manual/de/style_guide.ssi
@@ -0,0 +1,313 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account
+when writing technical documentation for live-manual. They are divided into
+linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native
+speakers. So as a general rule try to use short, meaningful sentences,
+followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a
+suggestion to try to avoid, as much as possible, complex subordinate
+sentences that make the text difficult to understand for non-native
+speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it
+is very likely that most authors will use either one or the other. In a
+collaborative environment, the ideal variety would be "International
+English" but it is very difficult, not to say impossible, to decide on which
+variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating
+misunderstandings but in general terms you should try to be coherent and
+before deciding on using British, American or any other English flavour at
+your discretion, please take a look at how other people write and try to
+imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely
+unrelated to live-manual. Technical writing should be as neutral as
+possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make
+references to the third person singular preferably use "they" rather than
+"he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much
+information as necessary but do not give more information than necessary,
+this is to say, do not explain unnecessary details. Your readers are
+intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several
+other languages. This implies that a number of people will have to do an
+extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative
+document into a perfectly unified whole. However, every effort on your side
+to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and
+unambiguous. (Text-forming devices are linguistic markers such as
+connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than
+merely using a number of sentences in a typical "changelog" style. Describe
+it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not
+know how to express certain concepts in English. But keep in mind that a
+dictionary can either be your best friend or can turn into your worst enemy
+if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million
+words). Many of these words are borrowings from other languages. When
+looking up the meaning of words in a bilingual dictionary the tendency of a
+non-native speaker is to choose the one that sounds more similar in their
+mother tongue. This often turns into an excessively formal discourse which
+does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms,
+it is a good advice to choose the first word proposed by the dictionary. If
+in doubt, choosing words of Germanic origin (Usually monosyllabic words) is
+often the right thing to do. Be warned that these two techniques might
+produce a rather informal discourse but at least your choice of words will
+be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely
+helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search
+engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign
+language you cannot help falling from time to time in the trap of the so
+called "false friends", words that look similar in two languages but whose
+meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may
+convey a completely different meaning from what their individual words seem
+to mean. Sometimes, idioms are difficult to understand even for native
+speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical
+writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand
+and above all contractions that try to imitate the spoken language. Not to
+mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to
+live-manual to ensure that everything works as described. Testing on a clean
+chroot or VM can be a good starting point. Besides, it would be ideal if the
+tests were then carried out on different machines with different hardware to
+spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is,
+after all, just an example.
+
+It is often better to use a line that only applies to an specific case than
+using abstractions that may confuse your readers. In this case you can
+provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some
+potentially dangerous commands that, if misused, may cause data loss or
+other similar undesirable effects. In this case you should provide a
+thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those
+sites is crucial when it comes to understanding a special point. Even so,
+try to use links to external sites as sparsely as possible. Internet links
+are likely to change from time to time resulting in broken links and leaving
+your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to
+follow those links.
+
+_* /{Avoid branding and things that violate the license under which the
+manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other
+downstream projects might make use of the documentation you write. So you
+are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications
+that apply to the distribution of the material (of any kind, including
+copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of
+events.
+
+Once you have somehow organized those ideas in your mind write a first
+draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1,
+1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup
+below.
+
+If you have to enumerate a series of steps or stages in your description,
+you can also use ordinal numbers: First, second, third ... or First, Then,
+After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to
+process the text files and produce a multiple format output. It is
+recommended to take a look at {SiSU's
+manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar
+with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account
+when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the
+translation rules that apply to their specific languages. Usually
+translation groups and mailing lists provide information on how to produce
+translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the
+meaning of words, sentences, paragraphs and texts as written by the original
+authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of
+information of their own. If they want to add a comment for other
+translators working on the same documents, they can leave it in the space
+reserved for that. That is, the header of the strings in the *{po}* files
+preceded by a number sign *{#}*. Most graphical translation programs can
+automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in
+brackets in the translated text if, and only if, that makes the meaning of a
+difficult word or expression clearer to the reader. Inside the brackets the
+translator should make evident that the addition was theirs using the
+abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form
+"you". In some other languages that do not share this characteristic, this
+might give the false impression that the original texts are directly
+addressing the reader when they are actually not doing so. Translators must
+be aware of that fact and reflect it in their language as accurately as
+possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to
+translators. Double check the meaning of suspicious false friends if in
+doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}*
+files will find many markup features in the strings. They can translate the
+text anyway but it is extremely important that they use exactly the same
+markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the
+original texts. Be careful to press the "Enter" key or type *{\n}* if they
+appear in the original files. These new lines often appear, for instance, in
+the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have
+the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in
+ /{live-manual.ssm.po}/ because it changes every time live-manual is
+ updated.
+
+ * Links
+
+ * Paths
diff --git a/manual/en/about_manual.ssi b/manual/en/about_manual.ssi
index 966b3f3..ff430e7 100644
--- a/manual/en/about_manual.ssi
+++ b/manual/en/about_manual.ssi
@@ -199,7 +199,7 @@ code{
}code
-3~ Translation
+3~translation Translation
To submit a translation for a new language, follow these three steps:
diff --git a/manual/en/live-manual.ssm b/manual/en/live-manual.ssm
index 485e4aa..9ce345f 100644
--- a/manual/en/live-manual.ssm
+++ b/manual/en/live-manual.ssm
@@ -9,7 +9,7 @@
:license: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file.
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Project <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Examples
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/en/style_guide.ssi b/manual/en/style_guide.ssi
new file mode 100644
index 0000000..603f9b7
--- /dev/null
+++ b/manual/en/style_guide.ssi
@@ -0,0 +1,191 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account when writing technical documentation for live-manual. They are divided into linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native speakers. So as a general rule try to use short, meaningful sentences, followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a suggestion to try to avoid, as much as possible, complex subordinate sentences that make the text difficult to understand for non-native speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it is very likely that most authors will use either one or the other. In a collaborative environment, the ideal variety would be "International English" but it is very difficult, not to say impossible, to decide on which variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating misunderstandings but in general terms you should try to be coherent and before deciding on using British, American or any other English flavour at your discretion, please take a look at how other people write and try to imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely unrelated to live-manual. Technical writing should be as neutral as possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make references to the third person singular preferably use "they" rather than "he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much information as necessary but do not give more information than necessary, this is to say, do not explain unnecessary details. Your readers are intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several other languages. This implies that a number of people will have to do an extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative document into a perfectly unified whole. However, every effort on your side to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and unambiguous. (Text-forming devices are linguistic markers such as connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than merely using a number of sentences in a typical "changelog" style. Describe it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not know how to express certain concepts in English. But keep in mind that a dictionary can either be your best friend or can turn into your worst enemy if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million words). Many of these words are borrowings from other languages. When looking up the meaning of words in a bilingual dictionary the tendency of a non-native speaker is to choose the one that sounds more similar in their mother tongue. This often turns into an excessively formal discourse which does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms, it is a good advice to choose the first word proposed by the dictionary. If in doubt, choosing words of Germanic origin (Usually monosyllabic words) is often the right thing to do. Be warned that these two techniques might produce a rather informal discourse but at least your choice of words will be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign language you cannot help falling from time to time in the trap of the so called "false friends", words that look similar in two languages but whose meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may convey a completely different meaning from what their individual words seem to mean. Sometimes, idioms are difficult to understand even for native speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand and above all contractions that try to imitate the spoken language. Not to mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to live-manual to ensure that everything works as described. Testing on a clean chroot or VM can be a good starting point. Besides, it would be ideal if the tests were then carried out on different machines with different hardware to spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is, after all, just an example.
+
+It is often better to use a line that only applies to an specific case than using abstractions that may confuse your readers. In this case you can provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some potentially dangerous commands that, if misused, may cause data loss or other similar undesirable effects. In this case you should provide a thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those sites is crucial when it comes to understanding a special point. Even so, try to use links to external sites as sparsely as possible. Internet links are likely to change from time to time resulting in broken links and leaving your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to follow those links.
+
+_* /{Avoid branding and things that violate the license under which the manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other downstream projects might make use of the documentation you write. So you are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications that apply to the distribution of the material (of any kind, including copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of events.
+
+Once you have somehow organized those ideas in your mind write a first draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1, 1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup below.
+
+If you have to enumerate a series of steps or stages in your description, you can also use ordinal numbers: First, second, third ... or First, Then, After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to process the text files and produce a multiple format output. It is recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the translation rules that apply to their specific languages. Usually translation groups and mailing lists provide information on how to produce translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the meaning of words, sentences, paragraphs and texts as written by the original authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of information of their own. If they want to add a comment for other translators working on the same documents, they can leave it in the space reserved for that. That is, the header of the strings in the *{po}* files preceded by a number sign *{#}*. Most graphical translation programs can automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in brackets in the translated text if, and only if, that makes the meaning of a difficult word or expression clearer to the reader. Inside the brackets the translator should make evident that the addition was theirs using the abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form "you". In some other languages that do not share this characteristic, this might give the false impression that the original texts are directly addressing the reader when they are actually not doing so. Translators must be aware of that fact and reflect it in their language as accurately as possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to translators. Double check the meaning of suspicious false friends if in doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}* files will find many markup features in the strings. They can translate the text anyway but it is extremely important that they use exactly the same markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the original texts. Be careful to press the "Enter" key or type *{\n}* if they appear in the original files. These new lines often appear, for instance, in the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in /{live-manual.ssm.po}/ because it changes every time live-manual is updated.
+
+ * Links
+
+ * Paths
diff --git a/manual/es/about_manual.ssi b/manual/es/about_manual.ssi
index 604b69f..b76da95 100644
--- a/manual/es/about_manual.ssi
+++ b/manual/es/about_manual.ssi
@@ -312,7 +312,7 @@ code{
}code
-3~ Traducciones
+3~translation Translation
Para enviar una traducción para un nuevo idioma, se deben seguir los
siguientes pasos:
diff --git a/manual/es/live-manual.ssm b/manual/es/live-manual.ssm
index d2f142a..b7df49a 100644
--- a/manual/es/live-manual.ssm
+++ b/manual/es/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Este programa es software libre: puede ser redistribuido y/o modificado bajo los términos de la GNU General Public License publicada por la Free Software Foundation, bien de la versión 3 de la Licencia, o (a su elección) cualquier versión posterior. <br><br> Este programa se distribuye con la esperanza de que sea útil, pero SIN NINGUNA GARANTÍA, incluso sin la garantía implícita de COMERCIALIZACIÓN o IDONEIDAD PARA UN PROPÓSITO PARTICULAR. Consulte la GNU General Public License para más detalles. <br><br> Debería haber recibido una copia de la General Public License GNU junto con este programa. Si no, vea http://www.gnu.org/licenses/. <br><br> El texto completo de la GNU Licencia Pública General se pueden encontrar en /usr/share/common-licenses/GPL-3
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Project <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Ejemplos
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/es/style_guide.ssi b/manual/es/style_guide.ssi
new file mode 100644
index 0000000..3fe12c1
--- /dev/null
+++ b/manual/es/style_guide.ssi
@@ -0,0 +1,313 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account
+when writing technical documentation for live-manual. They are divided into
+linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native
+speakers. So as a general rule try to use short, meaningful sentences,
+followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a
+suggestion to try to avoid, as much as possible, complex subordinate
+sentences that make the text difficult to understand for non-native
+speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it
+is very likely that most authors will use either one or the other. In a
+collaborative environment, the ideal variety would be "International
+English" but it is very difficult, not to say impossible, to decide on which
+variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating
+misunderstandings but in general terms you should try to be coherent and
+before deciding on using British, American or any other English flavour at
+your discretion, please take a look at how other people write and try to
+imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely
+unrelated to live-manual. Technical writing should be as neutral as
+possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make
+references to the third person singular preferably use "they" rather than
+"he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much
+information as necessary but do not give more information than necessary,
+this is to say, do not explain unnecessary details. Your readers are
+intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several
+other languages. This implies that a number of people will have to do an
+extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative
+document into a perfectly unified whole. However, every effort on your side
+to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and
+unambiguous. (Text-forming devices are linguistic markers such as
+connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than
+merely using a number of sentences in a typical "changelog" style. Describe
+it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not
+know how to express certain concepts in English. But keep in mind that a
+dictionary can either be your best friend or can turn into your worst enemy
+if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million
+words). Many of these words are borrowings from other languages. When
+looking up the meaning of words in a bilingual dictionary the tendency of a
+non-native speaker is to choose the one that sounds more similar in their
+mother tongue. This often turns into an excessively formal discourse which
+does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms,
+it is a good advice to choose the first word proposed by the dictionary. If
+in doubt, choosing words of Germanic origin (Usually monosyllabic words) is
+often the right thing to do. Be warned that these two techniques might
+produce a rather informal discourse but at least your choice of words will
+be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely
+helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search
+engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign
+language you cannot help falling from time to time in the trap of the so
+called "false friends", words that look similar in two languages but whose
+meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may
+convey a completely different meaning from what their individual words seem
+to mean. Sometimes, idioms are difficult to understand even for native
+speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical
+writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand
+and above all contractions that try to imitate the spoken language. Not to
+mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to
+live-manual to ensure that everything works as described. Testing on a clean
+chroot or VM can be a good starting point. Besides, it would be ideal if the
+tests were then carried out on different machines with different hardware to
+spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is,
+after all, just an example.
+
+It is often better to use a line that only applies to an specific case than
+using abstractions that may confuse your readers. In this case you can
+provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some
+potentially dangerous commands that, if misused, may cause data loss or
+other similar undesirable effects. In this case you should provide a
+thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those
+sites is crucial when it comes to understanding a special point. Even so,
+try to use links to external sites as sparsely as possible. Internet links
+are likely to change from time to time resulting in broken links and leaving
+your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to
+follow those links.
+
+_* /{Avoid branding and things that violate the license under which the
+manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other
+downstream projects might make use of the documentation you write. So you
+are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications
+that apply to the distribution of the material (of any kind, including
+copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of
+events.
+
+Once you have somehow organized those ideas in your mind write a first
+draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1,
+1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup
+below.
+
+If you have to enumerate a series of steps or stages in your description,
+you can also use ordinal numbers: First, second, third ... or First, Then,
+After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to
+process the text files and produce a multiple format output. It is
+recommended to take a look at {SiSU's
+manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar
+with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account
+when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the
+translation rules that apply to their specific languages. Usually
+translation groups and mailing lists provide information on how to produce
+translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the
+meaning of words, sentences, paragraphs and texts as written by the original
+authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of
+information of their own. If they want to add a comment for other
+translators working on the same documents, they can leave it in the space
+reserved for that. That is, the header of the strings in the *{po}* files
+preceded by a number sign *{#}*. Most graphical translation programs can
+automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in
+brackets in the translated text if, and only if, that makes the meaning of a
+difficult word or expression clearer to the reader. Inside the brackets the
+translator should make evident that the addition was theirs using the
+abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form
+"you". In some other languages that do not share this characteristic, this
+might give the false impression that the original texts are directly
+addressing the reader when they are actually not doing so. Translators must
+be aware of that fact and reflect it in their language as accurately as
+possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to
+translators. Double check the meaning of suspicious false friends if in
+doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}*
+files will find many markup features in the strings. They can translate the
+text anyway but it is extremely important that they use exactly the same
+markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the
+original texts. Be careful to press the "Enter" key or type *{\n}* if they
+appear in the original files. These new lines often appear, for instance, in
+the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have
+the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in
+ /{live-manual.ssm.po}/ because it changes every time live-manual is
+ updated.
+
+ * Links
+
+ * Paths
diff --git a/manual/fr/about_manual.ssi b/manual/fr/about_manual.ssi
index 6afd52d..3a9acdd 100644
--- a/manual/fr/about_manual.ssi
+++ b/manual/fr/about_manual.ssi
@@ -290,7 +290,7 @@ code{
}code
-3~ Traduction
+3~translation Translation
Pour soumettre une traduction pour une nouvelle langue, suivez ces trois
étapes:
diff --git a/manual/fr/live-manual.ssm b/manual/fr/live-manual.ssm
index 776d785..2225f0e 100644
--- a/manual/fr/live-manual.ssm
+++ b/manual/fr/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Ce programme est un logiciel libre; vous pouvez le redistribuer ou le modifier suivant les termes de la Licence Générale Publique GNU telle que publiée par la Free Software Foundation: soit la version 3 de cette licence, soit (à votre gré) toute version ultérieure.<br><br>Ce programme est distribué dans l’espoir qu’il vous sera utile, mais SANS AUCUNE GARANTIE: sans même la garantie implicite de COMMERCIALISABILITÉ ni d’ADÉQUATION À UN OBJECTIF PARTICULIER. Consultez la Licence Générale Publique GNU pour plus de détails.<br><br>Vous devriez avoir reçu une copie de la Licence Générale Publique GNU avec ce programme ; si ce n’est pas le cas, consultez http://www.gnu.org/licenses/. <br><br>Le texte complet de la Licence Générale Publique GNU peut être trouvé dans le fichier / usr/share/common-licenses/GPL-3
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Project <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Exemples
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/fr/style_guide.ssi b/manual/fr/style_guide.ssi
new file mode 100644
index 0000000..3fe12c1
--- /dev/null
+++ b/manual/fr/style_guide.ssi
@@ -0,0 +1,313 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account
+when writing technical documentation for live-manual. They are divided into
+linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native
+speakers. So as a general rule try to use short, meaningful sentences,
+followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a
+suggestion to try to avoid, as much as possible, complex subordinate
+sentences that make the text difficult to understand for non-native
+speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it
+is very likely that most authors will use either one or the other. In a
+collaborative environment, the ideal variety would be "International
+English" but it is very difficult, not to say impossible, to decide on which
+variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating
+misunderstandings but in general terms you should try to be coherent and
+before deciding on using British, American or any other English flavour at
+your discretion, please take a look at how other people write and try to
+imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely
+unrelated to live-manual. Technical writing should be as neutral as
+possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make
+references to the third person singular preferably use "they" rather than
+"he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much
+information as necessary but do not give more information than necessary,
+this is to say, do not explain unnecessary details. Your readers are
+intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several
+other languages. This implies that a number of people will have to do an
+extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative
+document into a perfectly unified whole. However, every effort on your side
+to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and
+unambiguous. (Text-forming devices are linguistic markers such as
+connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than
+merely using a number of sentences in a typical "changelog" style. Describe
+it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not
+know how to express certain concepts in English. But keep in mind that a
+dictionary can either be your best friend or can turn into your worst enemy
+if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million
+words). Many of these words are borrowings from other languages. When
+looking up the meaning of words in a bilingual dictionary the tendency of a
+non-native speaker is to choose the one that sounds more similar in their
+mother tongue. This often turns into an excessively formal discourse which
+does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms,
+it is a good advice to choose the first word proposed by the dictionary. If
+in doubt, choosing words of Germanic origin (Usually monosyllabic words) is
+often the right thing to do. Be warned that these two techniques might
+produce a rather informal discourse but at least your choice of words will
+be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely
+helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search
+engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign
+language you cannot help falling from time to time in the trap of the so
+called "false friends", words that look similar in two languages but whose
+meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may
+convey a completely different meaning from what their individual words seem
+to mean. Sometimes, idioms are difficult to understand even for native
+speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical
+writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand
+and above all contractions that try to imitate the spoken language. Not to
+mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to
+live-manual to ensure that everything works as described. Testing on a clean
+chroot or VM can be a good starting point. Besides, it would be ideal if the
+tests were then carried out on different machines with different hardware to
+spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is,
+after all, just an example.
+
+It is often better to use a line that only applies to an specific case than
+using abstractions that may confuse your readers. In this case you can
+provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some
+potentially dangerous commands that, if misused, may cause data loss or
+other similar undesirable effects. In this case you should provide a
+thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those
+sites is crucial when it comes to understanding a special point. Even so,
+try to use links to external sites as sparsely as possible. Internet links
+are likely to change from time to time resulting in broken links and leaving
+your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to
+follow those links.
+
+_* /{Avoid branding and things that violate the license under which the
+manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other
+downstream projects might make use of the documentation you write. So you
+are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications
+that apply to the distribution of the material (of any kind, including
+copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of
+events.
+
+Once you have somehow organized those ideas in your mind write a first
+draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1,
+1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup
+below.
+
+If you have to enumerate a series of steps or stages in your description,
+you can also use ordinal numbers: First, second, third ... or First, Then,
+After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to
+process the text files and produce a multiple format output. It is
+recommended to take a look at {SiSU's
+manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar
+with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account
+when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the
+translation rules that apply to their specific languages. Usually
+translation groups and mailing lists provide information on how to produce
+translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the
+meaning of words, sentences, paragraphs and texts as written by the original
+authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of
+information of their own. If they want to add a comment for other
+translators working on the same documents, they can leave it in the space
+reserved for that. That is, the header of the strings in the *{po}* files
+preceded by a number sign *{#}*. Most graphical translation programs can
+automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in
+brackets in the translated text if, and only if, that makes the meaning of a
+difficult word or expression clearer to the reader. Inside the brackets the
+translator should make evident that the addition was theirs using the
+abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form
+"you". In some other languages that do not share this characteristic, this
+might give the false impression that the original texts are directly
+addressing the reader when they are actually not doing so. Translators must
+be aware of that fact and reflect it in their language as accurately as
+possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to
+translators. Double check the meaning of suspicious false friends if in
+doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}*
+files will find many markup features in the strings. They can translate the
+text anyway but it is extremely important that they use exactly the same
+markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the
+original texts. Be careful to press the "Enter" key or type *{\n}* if they
+appear in the original files. These new lines often appear, for instance, in
+the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have
+the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in
+ /{live-manual.ssm.po}/ because it changes every time live-manual is
+ updated.
+
+ * Links
+
+ * Paths
diff --git a/manual/it/about_manual.ssi b/manual/it/about_manual.ssi
index 24321dc..d96756a 100644
--- a/manual/it/about_manual.ssi
+++ b/manual/it/about_manual.ssi
@@ -286,7 +286,7 @@ code{
}code
-3~ Traduzione
+3~translation Translation
Per inviare una traduzione per una nuova lingua, seguire questi tre passi:
diff --git a/manual/it/live-manual.ssm b/manual/it/live-manual.ssm
index b4bce8a..4f417a0 100644
--- a/manual/it/live-manual.ssm
+++ b/manual/it/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Questo programma è software libero: è possibile ridistribuirlo e modificarlo secondo i termini della GNU General Public License come pubblicata dalla Free Software Foundation, sia la versione 3 della licenza o (a scelta) una versione successiva.<br><br>Questo programma è distribuito nella speranza che possa essere utile, ma SENZA ALCUNA GARANZIA, nemmeno la garanzia implicita di COMMERCIABILITÀ o IDONEITÀ PER UN PARTICOLARE SCOPO. Vedere la GNU General Public License per ulteriori dettagli.<br><br>Si dovrebbe aver ricevuto una copia della GNU General Public License con questo programma. In caso contrario, vedere http://www.gnu.org/licenses/. <br><br>Il testo completo della GNU General Public License può essere trovato nel file /usr/share/common-licenses/GPL-3.
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Project <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Esempi
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/it/style_guide.ssi b/manual/it/style_guide.ssi
new file mode 100644
index 0000000..3fe12c1
--- /dev/null
+++ b/manual/it/style_guide.ssi
@@ -0,0 +1,313 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account
+when writing technical documentation for live-manual. They are divided into
+linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native
+speakers. So as a general rule try to use short, meaningful sentences,
+followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a
+suggestion to try to avoid, as much as possible, complex subordinate
+sentences that make the text difficult to understand for non-native
+speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it
+is very likely that most authors will use either one or the other. In a
+collaborative environment, the ideal variety would be "International
+English" but it is very difficult, not to say impossible, to decide on which
+variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating
+misunderstandings but in general terms you should try to be coherent and
+before deciding on using British, American or any other English flavour at
+your discretion, please take a look at how other people write and try to
+imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely
+unrelated to live-manual. Technical writing should be as neutral as
+possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make
+references to the third person singular preferably use "they" rather than
+"he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much
+information as necessary but do not give more information than necessary,
+this is to say, do not explain unnecessary details. Your readers are
+intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several
+other languages. This implies that a number of people will have to do an
+extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative
+document into a perfectly unified whole. However, every effort on your side
+to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and
+unambiguous. (Text-forming devices are linguistic markers such as
+connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than
+merely using a number of sentences in a typical "changelog" style. Describe
+it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not
+know how to express certain concepts in English. But keep in mind that a
+dictionary can either be your best friend or can turn into your worst enemy
+if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million
+words). Many of these words are borrowings from other languages. When
+looking up the meaning of words in a bilingual dictionary the tendency of a
+non-native speaker is to choose the one that sounds more similar in their
+mother tongue. This often turns into an excessively formal discourse which
+does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms,
+it is a good advice to choose the first word proposed by the dictionary. If
+in doubt, choosing words of Germanic origin (Usually monosyllabic words) is
+often the right thing to do. Be warned that these two techniques might
+produce a rather informal discourse but at least your choice of words will
+be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely
+helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search
+engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign
+language you cannot help falling from time to time in the trap of the so
+called "false friends", words that look similar in two languages but whose
+meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may
+convey a completely different meaning from what their individual words seem
+to mean. Sometimes, idioms are difficult to understand even for native
+speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical
+writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand
+and above all contractions that try to imitate the spoken language. Not to
+mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to
+live-manual to ensure that everything works as described. Testing on a clean
+chroot or VM can be a good starting point. Besides, it would be ideal if the
+tests were then carried out on different machines with different hardware to
+spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is,
+after all, just an example.
+
+It is often better to use a line that only applies to an specific case than
+using abstractions that may confuse your readers. In this case you can
+provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some
+potentially dangerous commands that, if misused, may cause data loss or
+other similar undesirable effects. In this case you should provide a
+thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those
+sites is crucial when it comes to understanding a special point. Even so,
+try to use links to external sites as sparsely as possible. Internet links
+are likely to change from time to time resulting in broken links and leaving
+your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to
+follow those links.
+
+_* /{Avoid branding and things that violate the license under which the
+manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other
+downstream projects might make use of the documentation you write. So you
+are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications
+that apply to the distribution of the material (of any kind, including
+copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of
+events.
+
+Once you have somehow organized those ideas in your mind write a first
+draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1,
+1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup
+below.
+
+If you have to enumerate a series of steps or stages in your description,
+you can also use ordinal numbers: First, second, third ... or First, Then,
+After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to
+process the text files and produce a multiple format output. It is
+recommended to take a look at {SiSU's
+manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar
+with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account
+when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the
+translation rules that apply to their specific languages. Usually
+translation groups and mailing lists provide information on how to produce
+translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the
+meaning of words, sentences, paragraphs and texts as written by the original
+authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of
+information of their own. If they want to add a comment for other
+translators working on the same documents, they can leave it in the space
+reserved for that. That is, the header of the strings in the *{po}* files
+preceded by a number sign *{#}*. Most graphical translation programs can
+automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in
+brackets in the translated text if, and only if, that makes the meaning of a
+difficult word or expression clearer to the reader. Inside the brackets the
+translator should make evident that the addition was theirs using the
+abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form
+"you". In some other languages that do not share this characteristic, this
+might give the false impression that the original texts are directly
+addressing the reader when they are actually not doing so. Translators must
+be aware of that fact and reflect it in their language as accurately as
+possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to
+translators. Double check the meaning of suspicious false friends if in
+doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}*
+files will find many markup features in the strings. They can translate the
+text anyway but it is extremely important that they use exactly the same
+markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the
+original texts. Be careful to press the "Enter" key or type *{\n}* if they
+appear in the original files. These new lines often appear, for instance, in
+the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have
+the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in
+ /{live-manual.ssm.po}/ because it changes every time live-manual is
+ updated.
+
+ * Links
+
+ * Paths
diff --git a/manual/po/de/about_manual.ssi.po b/manual/po/de/about_manual.ssi.po
index 11139d2..e77853c 100644
--- a/manual/po/de/about_manual.ssi.po
+++ b/manual/po/de/about_manual.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2011-04-23 14:15+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -318,17 +318,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -390,17 +391,18 @@ msgstr ""
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -629,7 +631,7 @@ msgstr ""
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr ""
#. type: Plain text
diff --git a/manual/po/de/live-manual.ssm.po b/manual/po/de/live-manual.ssm.po
index 8c56e88..cb8a7a2 100644
--- a/manual/po/de/live-manual.ssm.po
+++ b/manual/po/de/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2011-04-23 14:15+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -48,7 +48,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -173,6 +173,18 @@ msgid ":B~ Examples"
msgstr ":B~ Beispiele"
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr "<< user_examples.ssi"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+#, fuzzy
+#| msgid "<< user_overview.ssi"
+msgid "<< style_guide.ssi"
+msgstr "<< user_overview.ssi"
diff --git a/manual/po/de/style_guide.ssi.po b/manual/po/de/style_guide.ssi.po
new file mode 100644
index 0000000..03fd647
--- /dev/null
+++ b/manual/po/de/style_guide.ssi.po
@@ -0,0 +1,792 @@
+# German translations for live-manual package
+# Copyright (C) 2012 Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# Automatically generated, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: 2012-02-11 16:42+0100\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: de\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+msgid "3~ Procedures"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+#, fuzzy
+#| msgid ":B~ Examples"
+msgid "_* /{Examples}/"
+msgstr ":B~ Beispiele"
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+msgid "3~ Translation hints"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/po/es/about_manual.ssi.po b/manual/po/es/about_manual.ssi.po
index 87a723a..614f941 100644
--- a/manual/po/es/about_manual.ssi.po
+++ b/manual/po/es/about_manual.ssi.po
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: live-manual\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2012-02-05 17:36+0100\n"
"Last-Translator: José Luis Zabalza and Carlos Zuferri «chals» "
"<jlz.3008 at gmail.com> <chals at altorricon.com>\n"
@@ -443,17 +443,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -515,17 +516,18 @@ msgstr "$ git clone git://live.debian.net/git/live-manual.git"
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -796,7 +798,9 @@ msgstr " $ git push\n"
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+#, fuzzy
+#| msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr "3~ Traducciones"
#. type: Plain text
diff --git a/manual/po/es/live-manual.ssm.po b/manual/po/es/live-manual.ssm.po
index f788ace..3c1bf4f 100644
--- a/manual/po/es/live-manual.ssm.po
+++ b/manual/po/es/live-manual.ssm.po
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2011-03-12 08:00-0000\n"
"Last-Translator: José Luis Zabalza and Carlos Zuferri «chals» "
"<jlz.3008 at gmail.com> <chals at altorricon.com\n"
@@ -53,7 +53,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -178,6 +178,18 @@ msgid ":B~ Examples"
msgstr ":B~ Ejemplos"
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr "<< user_examples.ssi"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+#, fuzzy
+#| msgid "<< user_overview.ssi"
+msgid "<< style_guide.ssi"
+msgstr "<< user_overview.ssi"
diff --git a/manual/po/es/style_guide.ssi.po b/manual/po/es/style_guide.ssi.po
new file mode 100644
index 0000000..a0f644b
--- /dev/null
+++ b/manual/po/es/style_guide.ssi.po
@@ -0,0 +1,796 @@
+# Spanish translations for live-manual package
+# Copyright (C) 2012 Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# Automatically generated, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: 2012-02-11 16:42+0100\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: es\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr "code{"
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr "}code"
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+#, fuzzy
+#| msgid "B~ Procedures"
+msgid "3~ Procedures"
+msgstr "B~ Procedimientos"
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+#, fuzzy
+#| msgid ":B~ Examples"
+msgid "_* /{Examples}/"
+msgstr ":B~ Ejemplos"
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+#, fuzzy
+#| msgid "3~ Translation"
+msgid "3~ Translation hints"
+msgstr "3~ Traducciones"
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/po/fr/about_manual.ssi.po b/manual/po/fr/about_manual.ssi.po
index 3186556..467273c 100644
--- a/manual/po/fr/about_manual.ssi.po
+++ b/manual/po/fr/about_manual.ssi.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2012-02-05 17:57+0100\n"
"Last-Translator: Carlos Zuferri «chals» <chals at altorricon.com>\n"
"Language-Team: <debian-live at lists.debian.org>\n"
@@ -417,17 +417,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -489,17 +490,18 @@ msgstr ""
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -751,7 +753,9 @@ msgstr ""
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+#, fuzzy
+#| msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr "3~ Traduction"
#. type: Plain text
diff --git a/manual/po/fr/live-manual.ssm.po b/manual/po/fr/live-manual.ssm.po
index 93e3054..28cf96f 100644
--- a/manual/po/fr/live-manual.ssm.po
+++ b/manual/po/fr/live-manual.ssm.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2011-06-19 16:32+0200\n"
"Last-Translator: Carlos Zuferri «chals» <chals at altorricon.com>\n"
"Language-Team: <debian-live at lists.debian.org>\n"
@@ -49,7 +49,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -169,6 +169,16 @@ msgid ":B~ Examples"
msgstr ":B~ Exemples"
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+msgid "<< style_guide.ssi"
+msgstr ""
diff --git a/manual/po/fr/style_guide.ssi.po b/manual/po/fr/style_guide.ssi.po
new file mode 100644
index 0000000..ba5e1d5
--- /dev/null
+++ b/manual/po/fr/style_guide.ssi.po
@@ -0,0 +1,796 @@
+# French translations for live-manual package
+# Copyright (C) 2012 Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# Automatically generated, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: 2012-02-11 16:42+0100\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: fr\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr "code{"
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr "}code"
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+#, fuzzy
+#| msgid "B~ Procedures"
+msgid "3~ Procedures"
+msgstr "B~ Procédures"
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+#, fuzzy
+#| msgid ":B~ Examples"
+msgid "_* /{Examples}/"
+msgstr ":B~ Exemples"
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+#, fuzzy
+#| msgid "3~ Translation"
+msgid "3~ Translation hints"
+msgstr "3~ Traduction"
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/po/it/about_manual.ssi.po b/manual/po/it/about_manual.ssi.po
index ec4968a..b6b4c72 100644
--- a/manual/po/it/about_manual.ssi.po
+++ b/manual/po/it/about_manual.ssi.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2012-02-06 18:49+0100\n"
"Last-Translator: skizzhg <skizzhg at gmx.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -408,17 +408,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -480,17 +481,18 @@ msgstr "$ git clone git://live.debian.net/git/live-manual.git"
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -745,7 +747,9 @@ msgstr ""
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+#, fuzzy
+#| msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr "3~ Traduzione"
#. type: Plain text
diff --git a/manual/po/it/live-manual.ssm.po b/manual/po/it/live-manual.ssm.po
index d3d6240..659b284 100644
--- a/manual/po/it/live-manual.ssm.po
+++ b/manual/po/it/live-manual.ssm.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2011-03-11 10:33+0100\n"
"Last-Translator: skizzhg <skizzhg at gmx.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -49,7 +49,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -169,6 +169,16 @@ msgid ":B~ Examples"
msgstr ":B~ Esempi"
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+msgid "<< style_guide.ssi"
+msgstr ""
diff --git a/manual/po/it/style_guide.ssi.po b/manual/po/it/style_guide.ssi.po
new file mode 100644
index 0000000..68f06e2
--- /dev/null
+++ b/manual/po/it/style_guide.ssi.po
@@ -0,0 +1,796 @@
+# Italian translations for live-manual package
+# Copyright (C) 2012 Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# Automatically generated, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: 2012-02-11 16:42+0100\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: it\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr "code{"
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr "}code"
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+#, fuzzy
+#| msgid "B~ Procedures"
+msgid "3~ Procedures"
+msgstr "B~ Procedure"
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+#, fuzzy
+#| msgid ":B~ Examples"
+msgid "_* /{Examples}/"
+msgstr ":B~ Esempi"
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+#, fuzzy
+#| msgid "3~ Translation"
+msgid "3~ Translation hints"
+msgstr "3~ Traduzione"
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/po/pt_BR/about_manual.ssi.po b/manual/po/pt_BR/about_manual.ssi.po
index a95f572..4b9b565 100644
--- a/manual/po/pt_BR/about_manual.ssi.po
+++ b/manual/po/pt_BR/about_manual.ssi.po
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2010-10-22 18:16-0300\n"
"Last-Translator: Bruno Gurgel <bruno.gurgel at gmail.com>\n"
"Language-Team: none\n"
@@ -369,17 +369,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -441,17 +442,18 @@ msgstr "$ git clone git://live.debian.net/git/live-manual.git"
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -706,7 +708,7 @@ msgstr ""
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr ""
#. type: Plain text
diff --git a/manual/po/pt_BR/live-manual.ssm.po b/manual/po/pt_BR/live-manual.ssm.po
index e29e0b9..d5dc43b 100644
--- a/manual/po/pt_BR/live-manual.ssm.po
+++ b/manual/po/pt_BR/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2010-10-22 07:52-0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -45,7 +45,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -165,6 +165,16 @@ msgid ":B~ Examples"
msgstr ""
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+msgid "<< style_guide.ssi"
+msgstr ""
diff --git a/manual/po/pt_BR/style_guide.ssi.po b/manual/po/pt_BR/style_guide.ssi.po
new file mode 100644
index 0000000..b649734
--- /dev/null
+++ b/manual/po/pt_BR/style_guide.ssi.po
@@ -0,0 +1,790 @@
+# Portuguese translations for live-manual package
+# Copyright (C) 2012 Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# Automatically generated, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: 2012-02-11 16:42+0100\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: pt_BR\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr "code{"
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr "}code"
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+msgid "3~ Procedures"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+msgid "_* /{Examples}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+msgid "3~ Translation hints"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/po/ro/about_manual.ssi.po b/manual/po/ro/about_manual.ssi.po
index 26b3a1c..3e4cb77 100644
--- a/manual/po/ro/about_manual.ssi.po
+++ b/manual/po/ro/about_manual.ssi.po
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2010-10-23 10:34-0200\n"
"Last-Translator: Eugen Paiuc <linux51 at bluewin.ch>\n"
"Language-Team: none\n"
@@ -369,17 +369,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -441,17 +442,18 @@ msgstr "$ git clone git://live.debian.net/git/live-manual.git"
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -702,7 +704,7 @@ msgstr ""
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr ""
#. type: Plain text
diff --git a/manual/po/ro/live-manual.ssm.po b/manual/po/ro/live-manual.ssm.po
index 011c22d..c7ebb99 100644
--- a/manual/po/ro/live-manual.ssm.po
+++ b/manual/po/ro/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: 2010-10-23 00:04+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -46,7 +46,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -166,6 +166,16 @@ msgid ":B~ Examples"
msgstr ""
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+msgid "<< style_guide.ssi"
+msgstr ""
diff --git a/manual/po/ro/style_guide.ssi.po b/manual/po/ro/style_guide.ssi.po
new file mode 100644
index 0000000..bac980f
--- /dev/null
+++ b/manual/po/ro/style_guide.ssi.po
@@ -0,0 +1,791 @@
+# Romanian translations for live-manual package
+# Copyright (C) 2012 Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# Automatically generated, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: 2012-02-11 16:42+0100\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ro\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < "
+"20)) ? 1 : 2;\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr "code{"
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr "}code"
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+msgid "3~ Procedures"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+msgid "_* /{Examples}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+msgid "3~ Translation hints"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/po4a.cfg b/manual/po4a.cfg
index b09d7e4..d033996 100644
--- a/manual/po4a.cfg
+++ b/manual/po4a.cfg
@@ -6,6 +6,7 @@
[type: text] en/project_bugs.ssi $lang:$lang/project_bugs.ssi
[type: text] en/project_coding-style.ssi $lang:$lang/project_coding-style.ssi
[type: text] en/project_procedures.ssi $lang:$lang/project_procedures.ssi
+[type: text] en/style_guide.ssi $lang:$lang/style_guide.ssi
[type: text] en/user_basics.ssi $lang:$lang/user_basics.ssi
[type: text] en/user_customization-binary.ssi $lang:$lang/user_customization-binary.ssi
[type: text] en/user_customization-contents.ssi $lang:$lang/user_customization-contents.ssi
diff --git a/manual/pot/about_manual.ssi.pot b/manual/pot/about_manual.ssi.pot
index 3168cab..807e694 100644
--- a/manual/pot/about_manual.ssi.pot
+++ b/manual/pot/about_manual.ssi.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-02-05 17:13+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -318,17 +318,18 @@ msgstr ""
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
-#: en/project_procedures.ssi:58 en/user_basics.ssi:32 en/user_basics.ssi:42
-#: en/user_basics.ssi:58 en/user_basics.ssi:73 en/user_basics.ssi:108
-#: en/user_basics.ssi:116 en/user_basics.ssi:128 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:160 en/user_basics.ssi:168
-#: en/user_basics.ssi:184 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:218 en/user_basics.ssi:226 en/user_basics.ssi:236
-#: en/user_basics.ssi:254 en/user_basics.ssi:282 en/user_basics.ssi:298
-#: en/user_basics.ssi:306 en/user_basics.ssi:326 en/user_basics.ssi:351
-#: en/user_customization-binary.ssi:16 en/user_customization-binary.ssi:27
-#: en/user_customization-contents.ssi:26 en/user_customization-contents.ssi:35
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:66
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
#: en/user_customization-installer.ssi:32
#: en/user_customization-installer.ssi:44
#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
@@ -390,17 +391,18 @@ msgstr ""
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
-#: en/project_procedures.ssi:131 en/user_basics.ssi:36 en/user_basics.ssi:46
-#: en/user_basics.ssi:64 en/user_basics.ssi:77 en/user_basics.ssi:112
-#: en/user_basics.ssi:120 en/user_basics.ssi:134 en/user_basics.ssi:144
-#: en/user_basics.ssi:156 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:188 en/user_basics.ssi:198 en/user_basics.ssi:206
-#: en/user_basics.ssi:222 en/user_basics.ssi:230 en/user_basics.ssi:240
-#: en/user_basics.ssi:274 en/user_basics.ssi:286 en/user_basics.ssi:302
-#: en/user_basics.ssi:310 en/user_basics.ssi:337 en/user_basics.ssi:376
-#: en/user_customization-binary.ssi:23 en/user_customization-binary.ssi:33
-#: en/user_customization-contents.ssi:31 en/user_customization-contents.ssi:46
-#: en/user_customization-contents.ssi:58 en/user_customization-contents.ssi:70
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
#: en/user_customization-installer.ssi:38
#: en/user_customization-installer.ssi:49
#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
@@ -629,7 +631,7 @@ msgstr ""
#. type: Plain text
#: en/about_manual.ssi:203
-msgid "3~ Translation"
+msgid "3~translation Translation"
msgstr ""
#. type: Plain text
diff --git a/manual/pot/live-manual.ssm.pot b/manual/pot/live-manual.ssm.pot
index 165f81a..733b096 100644
--- a/manual/pot/live-manual.ssm.pot
+++ b/manual/pot/live-manual.ssm.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-02-06 18:57+0100\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -45,7 +45,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-02-06\n"
+" :published: 2012-02-11\n"
msgstr ""
#. type: Plain text
@@ -165,6 +165,16 @@ msgid ":B~ Examples"
msgstr ""
#. type: Plain text
-#: en/live-manual.ssm:62
+#: en/live-manual.ssm:63
msgid "<< user_examples.ssi"
msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/live-manual.ssm:66
+msgid "<< style_guide.ssi"
+msgstr ""
diff --git a/manual/pot/style_guide.ssi.pot b/manual/pot/style_guide.ssi.pot
new file mode 100644
index 0000000..128c11d
--- /dev/null
+++ b/manual/pot/style_guide.ssi.pot
@@ -0,0 +1,790 @@
+# SOME DESCRIPTIVE TITLE
+# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the live-manual package.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: live-manual VERSION\n"
+"POT-Creation-Date: 2012-02-11 16:42+0100\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=CHARSET\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. type: Plain text
+#: en/live-manual.ssm:65 en/style_guide.ssi:2
+msgid ":B~ Appendix"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
+#: en/about_manual.ssi:108 en/about_manual.ssi:116 en/about_manual.ssi:124
+#: en/about_manual.ssi:136 en/about_manual.ssi:149 en/about_manual.ssi:162
+#: en/about_manual.ssi:173 en/about_manual.ssi:181 en/about_manual.ssi:189
+#: en/about_manual.ssi:197 en/project_bugs.ssi:60
+#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
+#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
+#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
+#: en/project_coding-style.ssi:110 en/project_coding-style.ssi:121
+#: en/project_procedures.ssi:12 en/project_procedures.ssi:46
+#: en/project_procedures.ssi:58 en/style_guide.ssi:124 en/user_basics.ssi:32
+#: en/user_basics.ssi:42 en/user_basics.ssi:58 en/user_basics.ssi:73
+#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:128
+#: en/user_basics.ssi:140 en/user_basics.ssi:152 en/user_basics.ssi:160
+#: en/user_basics.ssi:168 en/user_basics.ssi:184 en/user_basics.ssi:194
+#: en/user_basics.ssi:202 en/user_basics.ssi:218 en/user_basics.ssi:226
+#: en/user_basics.ssi:236 en/user_basics.ssi:254 en/user_basics.ssi:282
+#: en/user_basics.ssi:298 en/user_basics.ssi:306 en/user_basics.ssi:326
+#: en/user_basics.ssi:351 en/user_customization-binary.ssi:16
+#: en/user_customization-binary.ssi:27 en/user_customization-contents.ssi:26
+#: en/user_customization-contents.ssi:35 en/user_customization-contents.ssi:54
+#: en/user_customization-contents.ssi:66
+#: en/user_customization-installer.ssi:32
+#: en/user_customization-installer.ssi:44
+#: en/user_customization-packages.ssi:14 en/user_customization-packages.ssi:22
+#: en/user_customization-packages.ssi:40 en/user_customization-packages.ssi:54
+#: en/user_customization-packages.ssi:67 en/user_customization-packages.ssi:81
+#: en/user_customization-packages.ssi:101
+#: en/user_customization-packages.ssi:127
+#: en/user_customization-packages.ssi:140
+#: en/user_customization-packages.ssi:150
+#: en/user_customization-packages.ssi:160
+#: en/user_customization-packages.ssi:170
+#: en/user_customization-packages.ssi:184
+#: en/user_customization-packages.ssi:201
+#: en/user_customization-packages.ssi:211
+#: en/user_customization-packages.ssi:276
+#: en/user_customization-packages.ssi:288
+#: en/user_customization-packages.ssi:298
+#: en/user_customization-packages.ssi:316
+#: en/user_customization-packages.ssi:333
+#: en/user_customization-packages.ssi:341 en/user_customization-runtime.ssi:14
+#: en/user_customization-runtime.ssi:27 en/user_customization-runtime.ssi:47
+#: en/user_customization-runtime.ssi:57 en/user_customization-runtime.ssi:66
+#: en/user_customization-runtime.ssi:74 en/user_customization-runtime.ssi:83
+#: en/user_customization-runtime.ssi:104 en/user_customization-runtime.ssi:114
+#: en/user_customization-runtime.ssi:122 en/user_examples.ssi:14
+#: en/user_examples.ssi:30 en/user_examples.ssi:40 en/user_examples.ssi:54
+#: en/user_examples.ssi:67 en/user_examples.ssi:83 en/user_examples.ssi:93
+#: en/user_examples.ssi:107 en/user_examples.ssi:117 en/user_examples.ssi:127
+#: en/user_examples.ssi:141 en/user_examples.ssi:149 en/user_examples.ssi:157
+#: en/user_examples.ssi:165 en/user_examples.ssi:181 en/user_examples.ssi:193
+#: en/user_examples.ssi:209 en/user_examples.ssi:223 en/user_examples.ssi:232
+#: en/user_examples.ssi:250 en/user_examples.ssi:258 en/user_examples.ssi:267
+#: en/user_examples.ssi:277 en/user_installation.ssi:38
+#: en/user_installation.ssi:46 en/user_installation.ssi:56
+#: en/user_installation.ssi:64 en/user_installation.ssi:74
+#: en/user_installation.ssi:82 en/user_installation.ssi:90
+#: en/user_installation.ssi:114 en/user_installation.ssi:129
+#: en/user_installation.ssi:146 en/user_managing_a_configuration.ssi:24
+#: en/user_managing_a_configuration.ssi:35
+#: en/user_managing_a_configuration.ssi:47
+#: en/user_managing_a_configuration.ssi:56 en/user_overview.ssi:36
+#: en/user_overview.ssi:48 en/user_overview.ssi:56
+msgid "code{"
+msgstr ""
+
+#. type: Plain text
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:145 en/about_manual.ssi:158 en/about_manual.ssi:167
+#: en/about_manual.ssi:177 en/about_manual.ssi:185 en/about_manual.ssi:193
+#: en/about_manual.ssi:201 en/project_bugs.ssi:64
+#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
+#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
+#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
+#: en/project_coding-style.ssi:117 en/project_coding-style.ssi:128
+#: en/project_procedures.ssi:16 en/project_procedures.ssi:54
+#: en/project_procedures.ssi:131 en/style_guide.ssi:128 en/user_basics.ssi:36
+#: en/user_basics.ssi:46 en/user_basics.ssi:64 en/user_basics.ssi:77
+#: en/user_basics.ssi:112 en/user_basics.ssi:120 en/user_basics.ssi:134
+#: en/user_basics.ssi:144 en/user_basics.ssi:156 en/user_basics.ssi:164
+#: en/user_basics.ssi:172 en/user_basics.ssi:188 en/user_basics.ssi:198
+#: en/user_basics.ssi:206 en/user_basics.ssi:222 en/user_basics.ssi:230
+#: en/user_basics.ssi:240 en/user_basics.ssi:274 en/user_basics.ssi:286
+#: en/user_basics.ssi:302 en/user_basics.ssi:310 en/user_basics.ssi:337
+#: en/user_basics.ssi:376 en/user_customization-binary.ssi:23
+#: en/user_customization-binary.ssi:33 en/user_customization-contents.ssi:31
+#: en/user_customization-contents.ssi:46 en/user_customization-contents.ssi:58
+#: en/user_customization-contents.ssi:70
+#: en/user_customization-installer.ssi:38
+#: en/user_customization-installer.ssi:49
+#: en/user_customization-packages.ssi:18 en/user_customization-packages.ssi:26
+#: en/user_customization-packages.ssi:46 en/user_customization-packages.ssi:59
+#: en/user_customization-packages.ssi:71 en/user_customization-packages.ssi:85
+#: en/user_customization-packages.ssi:105
+#: en/user_customization-packages.ssi:132
+#: en/user_customization-packages.ssi:146
+#: en/user_customization-packages.ssi:156
+#: en/user_customization-packages.ssi:166
+#: en/user_customization-packages.ssi:176
+#: en/user_customization-packages.ssi:189
+#: en/user_customization-packages.ssi:207
+#: en/user_customization-packages.ssi:216
+#: en/user_customization-packages.ssi:280
+#: en/user_customization-packages.ssi:292
+#: en/user_customization-packages.ssi:302
+#: en/user_customization-packages.ssi:329
+#: en/user_customization-packages.ssi:337
+#: en/user_customization-packages.ssi:346 en/user_customization-runtime.ssi:21
+#: en/user_customization-runtime.ssi:31 en/user_customization-runtime.ssi:51
+#: en/user_customization-runtime.ssi:62 en/user_customization-runtime.ssi:70
+#: en/user_customization-runtime.ssi:79 en/user_customization-runtime.ssi:88
+#: en/user_customization-runtime.ssi:108 en/user_customization-runtime.ssi:118
+#: en/user_customization-runtime.ssi:127 en/user_examples.ssi:20
+#: en/user_examples.ssi:34 en/user_examples.ssi:44 en/user_examples.ssi:61
+#: en/user_examples.ssi:71 en/user_examples.ssi:89 en/user_examples.ssi:103
+#: en/user_examples.ssi:111 en/user_examples.ssi:121 en/user_examples.ssi:133
+#: en/user_examples.ssi:145 en/user_examples.ssi:153 en/user_examples.ssi:161
+#: en/user_examples.ssi:169 en/user_examples.ssi:189 en/user_examples.ssi:205
+#: en/user_examples.ssi:213 en/user_examples.ssi:228 en/user_examples.ssi:236
+#: en/user_examples.ssi:254 en/user_examples.ssi:263 en/user_examples.ssi:273
+#: en/user_examples.ssi:291 en/user_installation.ssi:42
+#: en/user_installation.ssi:50 en/user_installation.ssi:60
+#: en/user_installation.ssi:70 en/user_installation.ssi:78
+#: en/user_installation.ssi:86 en/user_installation.ssi:94
+#: en/user_installation.ssi:119 en/user_installation.ssi:136
+#: en/user_installation.ssi:149 en/user_managing_a_configuration.ssi:31
+#: en/user_managing_a_configuration.ssi:43
+#: en/user_managing_a_configuration.ssi:52
+#: en/user_managing_a_configuration.ssi:60 en/user_overview.ssi:42
+#: en/user_overview.ssi:52 en/user_overview.ssi:60
+msgid "}code"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:4
+msgid "1~style-guide Style guide"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:6
+msgid "2~ Guidelines for authors"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:8
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when writing technical documentation for live-manual. They are divided into "
+"linguistic features and recommended procedures."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:10
+#, no-wrap
+msgid "*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:12
+msgid "3~ Linguistic features"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:14
+msgid "_* /{Use plain English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:16
+msgid ""
+"Keep in mind that a high percentage of your readers are not native speakers. "
+"So as a general rule try to use short, meaningful sentences, followed by a "
+"full stop."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:18
+msgid ""
+"This does not mean that you have to use a simplistic, naive style. It is a "
+"suggestion to try to avoid, as much as possible, complex subordinate "
+"sentences that make the text difficult to understand for non-native speakers."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:20
+msgid "_* /{Variety of English}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:22
+msgid ""
+"The most widely spread varieties of English are British and American so it "
+"is very likely that most authors will use either one or the other. In a "
+"collaborative environment, the ideal variety would be \"International English"
+"\" but it is very difficult, not to say impossible, to decide on which "
+"variety among all the existing ones, is the best to use."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:24
+msgid ""
+"We expect that different varieties may mix without creating "
+"misunderstandings but in general terms you should try to be coherent and "
+"before deciding on using British, American or any other English flavour at "
+"your discretion, please take a look at how other people write and try to "
+"imitate them."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:26
+msgid "_* /{Be balanced}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:28
+msgid ""
+"Do not be biased. Avoid including references to ideologies completely "
+"unrelated to live-manual. Technical writing should be as neutral as "
+"possible. It is in the very nature of scientific writing."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:30
+msgid "_* /{Be politically correct}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:32
+msgid ""
+"Try to avoid sexist language as much as possible. If you need to make "
+"references to the third person singular preferably use \"they\" rather than "
+"\"he\" or \"she\" or awkward inventions such as \"s/he\", \"s(he)\" and the "
+"like."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:34
+msgid "_* /{Be concise}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:36
+msgid ""
+"Go straight to the point and do not wander around aimlessly. Give as much "
+"information as necessary but do not give more information than necessary, "
+"this is to say, do not explain unnecessary details. Your readers are "
+"intelligent. Presume some previous knowledge on their part."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:38
+msgid "_* /{Minimize translation work}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:40
+msgid ""
+"Keep in mind that whatever you write will have to be translated into several "
+"other languages. This implies that a number of people will have to do an "
+"extra work if you add useless or redundant information."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:42
+msgid "_* /{Be coherent}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:44
+msgid ""
+"As suggested before, it is almost impossible to standardize a collaborative "
+"document into a perfectly unified whole. However, every effort on your side "
+"to write in a coherent way with the rest of the authors will be appreciated."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:46
+msgid "_* /{Be cohesive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:48
+msgid ""
+"Use as many text-forming devices as necessary to make your text cohesive and "
+"unambiguous. (Text-forming devices are linguistic markers such as "
+"connectors)."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:50
+msgid "_* /{Be descriptive}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:52
+msgid ""
+"It is preferable to describe the point in one or several paragraphs than "
+"merely using a number of sentences in a typical \"changelog\" style. "
+"Describe it! Your readers will appreciate it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:54
+msgid "_* /{Dictionary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:56
+msgid ""
+"Look up the meaning of words in a dictionary or encyclopedia if you do not "
+"know how to express certain concepts in English. But keep in mind that a "
+"dictionary can either be your best friend or can turn into your worst enemy "
+"if you do not know how to use it correctly."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:58
+msgid ""
+"English has the largest vocabulary that exists (With over one million "
+"words). Many of these words are borrowings from other languages. When "
+"looking up the meaning of words in a bilingual dictionary the tendency of a "
+"non-native speaker is to choose the one that sounds more similar in their "
+"mother tongue. This often turns into an excessively formal discourse which "
+"does not sound quite natural in English."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:60
+msgid ""
+"As a general rule, if a concept can be expressed using different synonyms, "
+"it is a good advice to choose the first word proposed by the dictionary. If "
+"in doubt, choosing words of Germanic origin (Usually monosyllabic words) is "
+"often the right thing to do. Be warned that these two techniques might "
+"produce a rather informal discourse but at least your choice of words will "
+"be of wide use and generally accepted."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:62
+msgid ""
+"Using a dictionary of collocations is recommended. They are extremely "
+"helpful when it comes to know which words usually occur together."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:64
+msgid ""
+"Again it is a good practice to learn from the work of others. Using a search "
+"engine to check how other authors use certain expressions may help a lot."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:66
+msgid "_* /{False friends, idioms and other idiomatic expressions}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:68
+msgid ""
+"Watch out for false friends. No matter how proficient you are in a foreign "
+"language you cannot help falling from time to time in the trap of the so "
+"called \"false friends\", words that look similar in two languages but whose "
+"meanings or uses might be completely different."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:70
+msgid ""
+"Try to avoid idioms as much as possible. \"Idioms\" are expressions that may "
+"convey a completely different meaning from what their individual words seem "
+"to mean. Sometimes, idioms are difficult to understand even for native "
+"speakers!"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:72
+msgid "_* /{Avoid slang, abbreviations, contractions...}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:74
+msgid ""
+"Even though you are encouraged to use plain, everyday English, technical "
+"writing belongs to the formal register of the language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:76
+msgid ""
+"Try to avoid slang, unusual abbreviations that are difficult to understand "
+"and above all contractions that try to imitate the spoken language. Not to "
+"mention typical irc and family friendly expressions."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:78
+msgid "3~ Procedures"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:80
+msgid "_* /{Test before write}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:82
+msgid ""
+"It is important that authors test their examples before adding them to live-"
+"manual to ensure that everything works as described. Testing on a clean "
+"chroot or VM can be a good starting point. Besides, it would be ideal if the "
+"tests were then carried out on different machines with different hardware to "
+"spot possible problems that may arise."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:84
+msgid "_* /{Examples}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:86
+msgid ""
+"When providing an example try to be as specific as you can. An example is, "
+"after all, just an example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:88
+msgid ""
+"It is often better to use a line that only applies to an specific case than "
+"using abstractions that may confuse your readers. In this case you can "
+"provide a brief explanation of the effects of the proposed example."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:90
+msgid ""
+"There may be some exceptions when the example suggests using some "
+"potentially dangerous commands that, if misused, may cause data loss or "
+"other similar undesirable effects. In this case you should provide a "
+"thorough explanation of the possible side effects."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:92
+msgid "_* /{External links}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:94
+msgid ""
+"Links to external sites should only be used when the information on those "
+"sites is crucial when it comes to understanding a special point. Even so, "
+"try to use links to external sites as sparsely as possible. Internet links "
+"are likely to change from time to time resulting in broken links and leaving "
+"your arguments in an incomplete state."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:96
+msgid ""
+"Besides, people who read the manual offline will not have the chance to "
+"follow those links."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:98
+msgid ""
+"_* /{Avoid branding and things that violate the license under which the "
+"manual is published}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:100
+msgid ""
+"Try to avoid branding as much as possible. Keep in mind that other "
+"downstream projects might make use of the documentation you write. So you "
+"are complicating things for them if you add certain specific material."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:102
+msgid ""
+"live-manual is licensed under the GNU GPL. This has a number of implications "
+"that apply to the distribution of the material (of any kind, including "
+"copyrighted graphics or logos) that is published with it."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:104
+msgid "_* /{Write a first draft, revise, edit, improve, redo if necessary}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:106
+msgid ""
+"Brainstorm!. You need to organize your ideas first in a logical sequence of "
+"events."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:108
+msgid ""
+"Once you have somehow organized those ideas in your mind write a first draft."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:110
+msgid "Revise grammar, syntax and spelling."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:112
+msgid "Improve your statements and redo any part if necessary."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:114
+msgid "_* /{Chapters}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:116
+msgid ""
+"Use the conventional numbering system for chapters and subtitles. e.g. 1, "
+"1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup "
+"below."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:118
+msgid ""
+"If you have to enumerate a series of steps or stages in your description, "
+"you can also use ordinal numbers: First, second, third ... or First, Then, "
+"After that, Finally ... Alternatively you can use bulleted items."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:120 en/style_guide.ssi:158
+msgid "_* /{Markup}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:122
+msgid ""
+"And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to "
+"process the text files and produce a multiple format output. It is "
+"recommended to take a look at {SiSU's manual}http://www.sisudoc.org/sisu/"
+"sisu_manual/markup.html to get familiar with its markup, or else type:"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:126
+#, no-wrap
+msgid " $ sisu --help markup\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:130
+msgid "2~ Guidelines for translators"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:132
+msgid ""
+"This section deals with some general considerations to be taken into account "
+"when translating the contents of live-manual."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:134
+msgid ""
+"As a general recommendation, translators should have read and understood the "
+"translation rules that apply to their specific languages. Usually "
+"translation groups and mailing lists provide information on how to produce "
+"translated work that complies with Debian quality standards."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:136
+#, no-wrap
+msgid "*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation\n"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:138
+msgid "3~ Translation hints"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:140
+msgid "_* /{Comments}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:142
+msgid ""
+"The role of the translator is to convey as faithfully as possible the "
+"meaning of words, sentences, paragraphs and texts as written by the original "
+"authors into their target language."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:144
+msgid ""
+"So they should refrain from adding personal comments or extra bits of "
+"information of their own. If they want to add a comment for other "
+"translators working on the same documents, they can leave it in the space "
+"reserved for that. That is, the header of the strings in the *{po}* files "
+"preceded by a number sign *{#}*. Most graphical translation programs can "
+"automatically handle those types of comments."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:146
+msgid "_* /{TN, Translator's Note}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:148
+msgid ""
+"It is perfectly acceptable however, to include a word or an expression in "
+"brackets in the translated text if, and only if, that makes the meaning of a "
+"difficult word or expression clearer to the reader. Inside the brackets the "
+"translator should make evident that the addition was theirs using the "
+"abbreviation \"TN\" or \"Translator's Note\"."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:150
+msgid "_* /{Impersonal sentences}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:152
+msgid ""
+"Documents written in English make an extensive use of the impersonal form "
+"\"you\". In some other languages that do not share this characteristic, this "
+"might give the false impression that the original texts are directly "
+"addressing the reader when they are actually not doing so. Translators must "
+"be aware of that fact and reflect it in their language as accurately as "
+"possible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:154
+msgid "_* /{False friends}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:156
+msgid ""
+"The trap of \"false friends\" explained before especially applies to "
+"translators. Double check the meaning of suspicious false friends if in "
+"doubt."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:160
+msgid ""
+"Translators working initially with *{pot}* files and later on with *{po}* "
+"files will find many markup features in the strings. They can translate the "
+"text anyway but it is extremely important that they use exactly the same "
+"markup as the original English version."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:162
+msgid "_* /{Code blocks}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:164
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:166
+msgid ""
+"Include the code blocks if you want to score a 100% complete translation."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:168
+msgid ""
+"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."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:170
+msgid ""
+"Leave the code blocks empty (they will be automatically added then) if you "
+"want to make your translation easier to maintain."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:172
+msgid "_* /{New lines}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:174
+msgid ""
+"The translated texts need to have the exact same new lines (\\n) as the "
+"original texts. Be careful to press the \"Enter\" key or type *{\\n}* if "
+"they appear in the original files. These new lines often appear, for "
+"instance, in the code blocks."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:176
+msgid ""
+"Make no mistake, this does not mean that the translated text needs to have "
+"the same length as the English version. That is nearly impossible."
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:178
+msgid "_* /{Untranslatable strings}/"
+msgstr ""
+
+#. type: Plain text
+#: en/style_guide.ssi:180
+msgid "Translators should never translate:"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:182
+msgid "The code names of releases"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:184
+msgid "The names of programs"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:186
+msgid "The commands given as examples"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:188
+msgid ""
+"Metadata (often between colons *{:metadata:}*) especially the date in /{live-"
+"manual.ssm.po}/ because it changes every time live-manual is updated."
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:190
+msgid "Links"
+msgstr ""
+
+#. type: Bullet: ' * '
+#: en/style_guide.ssi:191
+msgid "Paths"
+msgstr ""
diff --git a/manual/pt_BR/about_manual.ssi b/manual/pt_BR/about_manual.ssi
index bff4e4c..7fa9e4c 100644
--- a/manual/pt_BR/about_manual.ssi
+++ b/manual/pt_BR/about_manual.ssi
@@ -283,7 +283,7 @@ code{
}code
-3~ Translation
+3~translation Translation
To submit a translation for a new language, follow these three steps:
diff --git a/manual/pt_BR/live-manual.ssm b/manual/pt_BR/live-manual.ssm
index 485e4aa..9ce345f 100644
--- a/manual/pt_BR/live-manual.ssm
+++ b/manual/pt_BR/live-manual.ssm
@@ -9,7 +9,7 @@
:license: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file.
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Project <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Examples
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/pt_BR/style_guide.ssi b/manual/pt_BR/style_guide.ssi
new file mode 100644
index 0000000..3fe12c1
--- /dev/null
+++ b/manual/pt_BR/style_guide.ssi
@@ -0,0 +1,313 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account
+when writing technical documentation for live-manual. They are divided into
+linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native
+speakers. So as a general rule try to use short, meaningful sentences,
+followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a
+suggestion to try to avoid, as much as possible, complex subordinate
+sentences that make the text difficult to understand for non-native
+speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it
+is very likely that most authors will use either one or the other. In a
+collaborative environment, the ideal variety would be "International
+English" but it is very difficult, not to say impossible, to decide on which
+variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating
+misunderstandings but in general terms you should try to be coherent and
+before deciding on using British, American or any other English flavour at
+your discretion, please take a look at how other people write and try to
+imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely
+unrelated to live-manual. Technical writing should be as neutral as
+possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make
+references to the third person singular preferably use "they" rather than
+"he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much
+information as necessary but do not give more information than necessary,
+this is to say, do not explain unnecessary details. Your readers are
+intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several
+other languages. This implies that a number of people will have to do an
+extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative
+document into a perfectly unified whole. However, every effort on your side
+to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and
+unambiguous. (Text-forming devices are linguistic markers such as
+connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than
+merely using a number of sentences in a typical "changelog" style. Describe
+it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not
+know how to express certain concepts in English. But keep in mind that a
+dictionary can either be your best friend or can turn into your worst enemy
+if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million
+words). Many of these words are borrowings from other languages. When
+looking up the meaning of words in a bilingual dictionary the tendency of a
+non-native speaker is to choose the one that sounds more similar in their
+mother tongue. This often turns into an excessively formal discourse which
+does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms,
+it is a good advice to choose the first word proposed by the dictionary. If
+in doubt, choosing words of Germanic origin (Usually monosyllabic words) is
+often the right thing to do. Be warned that these two techniques might
+produce a rather informal discourse but at least your choice of words will
+be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely
+helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search
+engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign
+language you cannot help falling from time to time in the trap of the so
+called "false friends", words that look similar in two languages but whose
+meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may
+convey a completely different meaning from what their individual words seem
+to mean. Sometimes, idioms are difficult to understand even for native
+speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical
+writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand
+and above all contractions that try to imitate the spoken language. Not to
+mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to
+live-manual to ensure that everything works as described. Testing on a clean
+chroot or VM can be a good starting point. Besides, it would be ideal if the
+tests were then carried out on different machines with different hardware to
+spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is,
+after all, just an example.
+
+It is often better to use a line that only applies to an specific case than
+using abstractions that may confuse your readers. In this case you can
+provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some
+potentially dangerous commands that, if misused, may cause data loss or
+other similar undesirable effects. In this case you should provide a
+thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those
+sites is crucial when it comes to understanding a special point. Even so,
+try to use links to external sites as sparsely as possible. Internet links
+are likely to change from time to time resulting in broken links and leaving
+your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to
+follow those links.
+
+_* /{Avoid branding and things that violate the license under which the
+manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other
+downstream projects might make use of the documentation you write. So you
+are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications
+that apply to the distribution of the material (of any kind, including
+copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of
+events.
+
+Once you have somehow organized those ideas in your mind write a first
+draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1,
+1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup
+below.
+
+If you have to enumerate a series of steps or stages in your description,
+you can also use ordinal numbers: First, second, third ... or First, Then,
+After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to
+process the text files and produce a multiple format output. It is
+recommended to take a look at {SiSU's
+manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar
+with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account
+when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the
+translation rules that apply to their specific languages. Usually
+translation groups and mailing lists provide information on how to produce
+translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the
+meaning of words, sentences, paragraphs and texts as written by the original
+authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of
+information of their own. If they want to add a comment for other
+translators working on the same documents, they can leave it in the space
+reserved for that. That is, the header of the strings in the *{po}* files
+preceded by a number sign *{#}*. Most graphical translation programs can
+automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in
+brackets in the translated text if, and only if, that makes the meaning of a
+difficult word or expression clearer to the reader. Inside the brackets the
+translator should make evident that the addition was theirs using the
+abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form
+"you". In some other languages that do not share this characteristic, this
+might give the false impression that the original texts are directly
+addressing the reader when they are actually not doing so. Translators must
+be aware of that fact and reflect it in their language as accurately as
+possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to
+translators. Double check the meaning of suspicious false friends if in
+doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}*
+files will find many markup features in the strings. They can translate the
+text anyway but it is extremely important that they use exactly the same
+markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the
+original texts. Be careful to press the "Enter" key or type *{\n}* if they
+appear in the original files. These new lines often appear, for instance, in
+the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have
+the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in
+ /{live-manual.ssm.po}/ because it changes every time live-manual is
+ updated.
+
+ * Links
+
+ * Paths
diff --git a/manual/ro/about_manual.ssi b/manual/ro/about_manual.ssi
index a4bbbda..a541395 100644
--- a/manual/ro/about_manual.ssi
+++ b/manual/ro/about_manual.ssi
@@ -278,7 +278,7 @@ code{
}code
-3~ Translation
+3~translation Translation
To submit a translation for a new language, follow these three steps:
diff --git a/manual/ro/live-manual.ssm b/manual/ro/live-manual.ssm
index 485e4aa..9ce345f 100644
--- a/manual/ro/live-manual.ssm
+++ b/manual/ro/live-manual.ssm
@@ -9,7 +9,7 @@
:license: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file.
@date:
- :published: 2012-02-06
+ :published: 2012-02-11
@publisher: Debian Live Project <debian-live at lists.debian.org>
@@ -60,3 +60,7 @@
:B~ Examples
<< user_examples.ssi
+
+:B~ Appendix
+
+<< style_guide.ssi
diff --git a/manual/ro/style_guide.ssi b/manual/ro/style_guide.ssi
new file mode 100644
index 0000000..3fe12c1
--- /dev/null
+++ b/manual/ro/style_guide.ssi
@@ -0,0 +1,313 @@
+:B~ Appendix
+
+1~style-guide Style guide
+
+2~ Guidelines for authors
+
+This section deals with some general considerations to be taken into account
+when writing technical documentation for live-manual. They are divided into
+linguistic features and recommended procedures.
+
+*{Note:}* Authors should first read {Contributing to this document}#how-to-contribute
+
+3~ Linguistic features
+
+_* /{Use plain English}/
+
+Keep in mind that a high percentage of your readers are not native
+speakers. So as a general rule try to use short, meaningful sentences,
+followed by a full stop.
+
+This does not mean that you have to use a simplistic, naive style. It is a
+suggestion to try to avoid, as much as possible, complex subordinate
+sentences that make the text difficult to understand for non-native
+speakers.
+
+_* /{Variety of English}/
+
+The most widely spread varieties of English are British and American so it
+is very likely that most authors will use either one or the other. In a
+collaborative environment, the ideal variety would be "International
+English" but it is very difficult, not to say impossible, to decide on which
+variety among all the existing ones, is the best to use.
+
+We expect that different varieties may mix without creating
+misunderstandings but in general terms you should try to be coherent and
+before deciding on using British, American or any other English flavour at
+your discretion, please take a look at how other people write and try to
+imitate them.
+
+_* /{Be balanced}/
+
+Do not be biased. Avoid including references to ideologies completely
+unrelated to live-manual. Technical writing should be as neutral as
+possible. It is in the very nature of scientific writing.
+
+_* /{Be politically correct}/
+
+Try to avoid sexist language as much as possible. If you need to make
+references to the third person singular preferably use "they" rather than
+"he" or "she" or awkward inventions such as "s/he", "s(he)" and the like.
+
+_* /{Be concise}/
+
+Go straight to the point and do not wander around aimlessly. Give as much
+information as necessary but do not give more information than necessary,
+this is to say, do not explain unnecessary details. Your readers are
+intelligent. Presume some previous knowledge on their part.
+
+_* /{Minimize translation work}/
+
+Keep in mind that whatever you write will have to be translated into several
+other languages. This implies that a number of people will have to do an
+extra work if you add useless or redundant information.
+
+_* /{Be coherent}/
+
+As suggested before, it is almost impossible to standardize a collaborative
+document into a perfectly unified whole. However, every effort on your side
+to write in a coherent way with the rest of the authors will be appreciated.
+
+_* /{Be cohesive}/
+
+Use as many text-forming devices as necessary to make your text cohesive and
+unambiguous. (Text-forming devices are linguistic markers such as
+connectors).
+
+_* /{Be descriptive}/
+
+It is preferable to describe the point in one or several paragraphs than
+merely using a number of sentences in a typical "changelog" style. Describe
+it! Your readers will appreciate it.
+
+_* /{Dictionary}/
+
+Look up the meaning of words in a dictionary or encyclopedia if you do not
+know how to express certain concepts in English. But keep in mind that a
+dictionary can either be your best friend or can turn into your worst enemy
+if you do not know how to use it correctly.
+
+English has the largest vocabulary that exists (With over one million
+words). Many of these words are borrowings from other languages. When
+looking up the meaning of words in a bilingual dictionary the tendency of a
+non-native speaker is to choose the one that sounds more similar in their
+mother tongue. This often turns into an excessively formal discourse which
+does not sound quite natural in English.
+
+As a general rule, if a concept can be expressed using different synonyms,
+it is a good advice to choose the first word proposed by the dictionary. If
+in doubt, choosing words of Germanic origin (Usually monosyllabic words) is
+often the right thing to do. Be warned that these two techniques might
+produce a rather informal discourse but at least your choice of words will
+be of wide use and generally accepted.
+
+Using a dictionary of collocations is recommended. They are extremely
+helpful when it comes to know which words usually occur together.
+
+Again it is a good practice to learn from the work of others. Using a search
+engine to check how other authors use certain expressions may help a lot.
+
+_* /{False friends, idioms and other idiomatic expressions}/
+
+Watch out for false friends. No matter how proficient you are in a foreign
+language you cannot help falling from time to time in the trap of the so
+called "false friends", words that look similar in two languages but whose
+meanings or uses might be completely different.
+
+Try to avoid idioms as much as possible. "Idioms" are expressions that may
+convey a completely different meaning from what their individual words seem
+to mean. Sometimes, idioms are difficult to understand even for native
+speakers!
+
+_* /{Avoid slang, abbreviations, contractions...}/
+
+Even though you are encouraged to use plain, everyday English, technical
+writing belongs to the formal register of the language.
+
+Try to avoid slang, unusual abbreviations that are difficult to understand
+and above all contractions that try to imitate the spoken language. Not to
+mention typical irc and family friendly expressions.
+
+3~ Procedures
+
+_* /{Test before write}/
+
+It is important that authors test their examples before adding them to
+live-manual to ensure that everything works as described. Testing on a clean
+chroot or VM can be a good starting point. Besides, it would be ideal if the
+tests were then carried out on different machines with different hardware to
+spot possible problems that may arise.
+
+_* /{Examples}/
+
+When providing an example try to be as specific as you can. An example is,
+after all, just an example.
+
+It is often better to use a line that only applies to an specific case than
+using abstractions that may confuse your readers. In this case you can
+provide a brief explanation of the effects of the proposed example.
+
+There may be some exceptions when the example suggests using some
+potentially dangerous commands that, if misused, may cause data loss or
+other similar undesirable effects. In this case you should provide a
+thorough explanation of the possible side effects.
+
+_* /{External links}/
+
+Links to external sites should only be used when the information on those
+sites is crucial when it comes to understanding a special point. Even so,
+try to use links to external sites as sparsely as possible. Internet links
+are likely to change from time to time resulting in broken links and leaving
+your arguments in an incomplete state.
+
+Besides, people who read the manual offline will not have the chance to
+follow those links.
+
+_* /{Avoid branding and things that violate the license under which the
+manual is published}/
+
+Try to avoid branding as much as possible. Keep in mind that other
+downstream projects might make use of the documentation you write. So you
+are complicating things for them if you add certain specific material.
+
+live-manual is licensed under the GNU GPL. This has a number of implications
+that apply to the distribution of the material (of any kind, including
+copyrighted graphics or logos) that is published with it.
+
+_* /{Write a first draft, revise, edit, improve, redo if necessary}/
+
+Brainstorm!. You need to organize your ideas first in a logical sequence of
+events.
+
+Once you have somehow organized those ideas in your mind write a first
+draft.
+
+Revise grammar, syntax and spelling.
+
+Improve your statements and redo any part if necessary.
+
+_* /{Chapters}/
+
+Use the conventional numbering system for chapters and subtitles. e.g. 1,
+1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup
+below.
+
+If you have to enumerate a series of steps or stages in your description,
+you can also use ordinal numbers: First, second, third ... or First, Then,
+After that, Finally ... Alternatively you can use bulleted items.
+
+_* /{Markup}/
+
+And last but not least, live-manual uses {SiSU}http://www.sisudoc.org to
+process the text files and produce a multiple format output. It is
+recommended to take a look at {SiSU's
+manual}http://www.sisudoc.org/sisu/sisu_manual/markup.html to get familiar
+with its markup, or else type:
+
+code{
+
+ $ sisu --help markup
+
+}code
+
+2~ Guidelines for translators
+
+This section deals with some general considerations to be taken into account
+when translating the contents of live-manual.
+
+As a general recommendation, translators should have read and understood the
+translation rules that apply to their specific languages. Usually
+translation groups and mailing lists provide information on how to produce
+translated work that complies with Debian quality standards.
+
+*{Note:}* Translators should also read {Contributing to this document}#how-to-contribute. In particular the section {Translation}#translation
+
+3~ Translation hints
+
+_* /{Comments}/
+
+The role of the translator is to convey as faithfully as possible the
+meaning of words, sentences, paragraphs and texts as written by the original
+authors into their target language.
+
+So they should refrain from adding personal comments or extra bits of
+information of their own. If they want to add a comment for other
+translators working on the same documents, they can leave it in the space
+reserved for that. That is, the header of the strings in the *{po}* files
+preceded by a number sign *{#}*. Most graphical translation programs can
+automatically handle those types of comments.
+
+_* /{TN, Translator's Note}/
+
+It is perfectly acceptable however, to include a word or an expression in
+brackets in the translated text if, and only if, that makes the meaning of a
+difficult word or expression clearer to the reader. Inside the brackets the
+translator should make evident that the addition was theirs using the
+abbreviation "TN" or "Translator's Note".
+
+_* /{Impersonal sentences}/
+
+Documents written in English make an extensive use of the impersonal form
+"you". In some other languages that do not share this characteristic, this
+might give the false impression that the original texts are directly
+addressing the reader when they are actually not doing so. Translators must
+be aware of that fact and reflect it in their language as accurately as
+possible.
+
+_* /{False friends}/
+
+The trap of "false friends" explained before especially applies to
+translators. Double check the meaning of suspicious false friends if in
+doubt.
+
+_* /{Markup}/
+
+Translators working initially with *{pot}* files and later on with *{po}*
+files will find many markup features in the strings. They can translate the
+text anyway but it is extremely important that they use exactly the same
+markup as the original English version.
+
+_* /{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.
+
+_* /{New lines}/
+
+The translated texts need to have the exact same new lines (\n) as the
+original texts. Be careful to press the "Enter" key or type *{\n}* if they
+appear in the original files. These new lines often appear, for instance, in
+the code blocks.
+
+Make no mistake, this does not mean that the translated text needs to have
+the same length as the English version. That is nearly impossible.
+
+_* /{Untranslatable strings}/
+
+Translators should never translate:
+
+ * The code names of releases
+
+ * The names of programs
+
+ * The commands given as examples
+
+ * Metadata (often between colons *{:metadata:}*) especially the date in
+ /{live-manual.ssm.po}/ because it changes every time live-manual is
+ updated.
+
+ * Links
+
+ * Paths
--
live-manual
More information about the debian-live-changes
mailing list