Italian translations and broken links
Hi Jon, just one question about how do you prefer us to proceed. We are translating the process directory. My idea was to complete it and then push it. This because the documents in here have links to other documents in the same directory. In order to cleanly build it I wanted to translate the full directory and then propose a patch. Since there are many documents, this take time and perhaps we can already push the ones which are ready. My big dilemma is (which is more general): what about broken references? Do we keep broken links which we know they will be correct in the future? Or, do we remove all broken links and we add them back only when they work (if we remember)? Thanks :)
Re: Italian translations and broken links
Answer to this email address, I did a mistake :) On Friday, August 24, 2018 1:51:18 PM CEST Federico Vaga wrote: > Hi Jon, > > just one question about how do you prefer us to proceed. We are translating > the process directory. > My idea was to complete it and then push it. This because the documents in > here have links to other documents in the same directory. In order to > cleanly build it I wanted to translate the full directory and then propose > a patch. > > Since there are many documents, this take time and perhaps we can already > push the ones which are ready. > > My big dilemma is (which is more general): what about broken references? Do > we keep broken links which we know they will be correct in the future? Or, > do we remove all broken links and we add them back only when they work (if > we remember)? > > Thanks :)
Re: doc: Italian translation
On Monday, 28 May 2018 15:08:28 CEST Jonathan Corbet wrote: > On Sun, 27 May 2018 16:55:55 +0200 > > Federico Vaga <federico.v...@vaga.pv.it> wrote: > > here the doc-guide translated in Italian. This set of patches > > includes some minor changes to the main one. The idea of this > > first set of patches is also to adjust the structure and our > > expectations. > > I've only done a quick scan so far. It looks reasonable, but I have > a couple of requests: > > - Please include a proper changelog with each patch describing what > the patch does and why. Otherwise I'll have to fill them in, and > that makes me grumpy...:) Ok > - You might as well add a MAINTAINERS entry. The other > translations don't have them, but they should. Ok > - For extra credit: it's time to move the translations out of the >top-level index into an index.rst in the translations directory. > Then the top-level file can have a single pointer to the > translations. I completely agree on this point. I can prepare a patch that does it. > > We tried to translate everything in **Italian**; which means that > > we avoided imported English words wherever there is the > > possibility to use the Italian ones. Of course, this is not > > always possible, or worst doing the translation make it less > > clear, for example the word "file". > > "We"? Is there somebody else's work represented here too? If so, > they should appear in the signoff chain (or as a Co-developed-by > credit). I did, in patch 3/5 and 4/5 there is Alessia as "signed-off" (in CC here). > > Another point. I noticed that the disclaimer for other > > translations is in English, so I did the same. But actually > > shouldn't be in Italian, since that page will be read by Italian > > speakers? > > Perhaps, though part of the idea is to give the English speakers, > too, some vague clue of what they're looking at. Make sense. I will keep it like this then. Thanks > > Thanks, > > jon -- Federico Vaga http://www.federicovaga.it/ -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 4/5] doc:it_IT: add doc-guide translation
Signed-off-by: Federico Vaga <federico.v...@vaga.pv.it>
Signed-off-by: Alessia Mantegazza <amantega...@vaga.pv.it>
---
.../translations/it_IT/doc-guide/hello.dot | 3 +
.../translations/it_IT/doc-guide/index.rst | 24 ++
.../translations/it_IT/doc-guide/kernel-doc.rst| 402 ++
.../translations/it_IT/doc-guide/parse-headers.rst | 196 +
.../translations/it_IT/doc-guide/sphinx.rst| 455 +
.../translations/it_IT/doc-guide/svg_image.svg | 1 +
Documentation/translations/it_IT/index.rst | 8 +
7 files changed, 1089 insertions(+)
create mode 100644 Documentation/translations/it_IT/doc-guide/hello.dot
create mode 100644 Documentation/translations/it_IT/doc-guide/index.rst
create mode 100644 Documentation/translations/it_IT/doc-guide/kernel-doc.rst
create mode 100644 Documentation/translations/it_IT/doc-guide/parse-headers.rst
create mode 100644 Documentation/translations/it_IT/doc-guide/sphinx.rst
create mode 12 Documentation/translations/it_IT/doc-guide/svg_image.svg
diff --git a/Documentation/translations/it_IT/doc-guide/hello.dot
b/Documentation/translations/it_IT/doc-guide/hello.dot
new file mode 100644
index ..eee1e5864b3e
--- /dev/null
+++ b/Documentation/translations/it_IT/doc-guide/hello.dot
@@ -0,0 +1,3 @@
+graph G {
+ Ciao -- Mondo
+}
diff --git a/Documentation/translations/it_IT/doc-guide/index.rst
b/Documentation/translations/it_IT/doc-guide/index.rst
new file mode 100644
index ..7a6562b547ee
--- /dev/null
+++ b/Documentation/translations/it_IT/doc-guide/index.rst
@@ -0,0 +1,24 @@
+.. include:: ../disclaimer-ita.rst
+
+.. note:: Per leggere la documentazione originale in inglese:
+ :ref:`Documentation/doc-guide/index.rst `
+
+.. _it_doc_guide:
+
+==
+Come scrivere la documentazione del kernel
+==
+
+.. toctree::
+ :maxdepth: 1
+
+ sphinx.rst
+ kernel-doc.rst
+ parse-headers.rst
+
+.. only:: subproject and html
+
+ Indices
+ ===
+
+ * :ref:`genindex`
diff --git a/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
b/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
new file mode 100644
index ..77f6ec7aa38d
--- /dev/null
+++ b/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
@@ -0,0 +1,402 @@
+.. include:: ../disclaimer-ita.rst
+
+.. note:: Per leggere la documentazione originale in inglese:
+ :ref:`Documentation/doc-guide/index.rst `
+
+Includere i commenti di tipo kernel-doc
+===
+
+I sorgenti del kernel Linux possono contenere commenti strutturati per
+la documentazione, oppure commenti di tipo kernel-doc che descrivono
+le funzioni, i tipi e la struttura del codice. I commenti di documentazione
+possono essere aggiunti ad un qualsiasi documento reStructuredtext
+utilizzando l'apposita estensione Sphinx per le direttive kernel-doc.
+
+Le direttive kernel-doc sono nel formato::
+
+ .. kernel-doc:: source
+ :option:
+
+Il campo *source* è il percorso ad un file sorgente, relativo alla cartella
+principale dei sorgenti del kernel. La direttiva supporta le seguenti opzioni:
+
+
+export: *[source-pattern ...]*
+ Include la documentazione per tutte le funzioni presenti nel file sorgente
+ (*source*) che sono state esportate utilizzando ``EXPORT_SYMBOL`` o
+ ``EXPORT_SYMBOL_GPL`` in *source* o in qualsiasi altro *source-pattern*
+ specificato.
+
+ Il campo *source-patter* è utile quando i commenti kernel-doc sono stati
+ scritti nei file d'intestazione, mentre ``EXPORT_SYMBOL`` e
+ ``EXPORT_SYMBOL_GPL`` si trovano vicino alla definizione delle funzioni.
+
+ Esempi::
+
+.. kernel-doc:: lib/bitmap.c
+ :export:
+
+.. kernel-doc:: include/net/mac80211.h
+ :export: net/mac80211/*.c
+
+internal: *[source-pattern ...]*
+ Include la documentazione per tutte le funzioni ed i tipi presenti nel file
+ sorgente (*source*) che **non** sono stati esportati utilizzando
+ ``EXPORT_SYMBOL`` o ``EXPORT_SYMBOL_GPL`` né in *source* né in qualsiasi
+ altro *source-pattern* specificato.
+
+ Esempio::
+
+.. kernel-doc:: drivers/gpu/drm/i915/intel_audio.c
+ :internal:
+
+doc: *title*
+ Include la documentazione per il paragrafo ``DOC:`` identificato dal titolo
+ (*title*) all'interno del file sorgente (*source*). Gli spazi in *title* sono
+ permessi; non virgolettate *title*. Il campo *title* è utilizzato per
+ identificare un paragrafo e per questo non viene incluso nella documentazione
+ finale. Verificate d'avere l'intestazione appropriata nei documenti
+ reStructuredText.
+
+ Esempio::
+
+.. kernel-doc:: drivers/gpu/drm/i915/intel_audio.c
+ :doc: High Definition Audio over HDMI and Display Port
+
+functions: *function* *[...]*
+ Dal file sorgente (*source*) include la documentazione per le funzioni
elencate
+ (*function*).
[PATCH 3/5] doc: add Italian translation skeleton
Signed-off-by: Federico Vaga <federico.v...@vaga.pv.it> Signed-off-by: Alessia Mantegazza <amantega...@vaga.pv.it> --- Documentation/index.rst| 8 ++ .../translations/it_IT/disclaimer-ita.rst | 11 +++ Documentation/translations/it_IT/index.rst | 101 + 3 files changed, 120 insertions(+) create mode 100644 Documentation/translations/it_IT/disclaimer-ita.rst create mode 100644 Documentation/translations/it_IT/index.rst diff --git a/Documentation/index.rst b/Documentation/index.rst index 8f11fccb9744..e6075bdacbbd 100644 --- a/Documentation/index.rst +++ b/Documentation/index.rst @@ -113,6 +113,14 @@ Japanese translations translations/ja_JP/index +Italian translations +- + +.. toctree:: + :maxdepth: 1 + + translations/it_IT/index + Indices and tables == diff --git a/Documentation/translations/it_IT/disclaimer-ita.rst b/Documentation/translations/it_IT/disclaimer-ita.rst new file mode 100644 index ..0c439117ed7f --- /dev/null +++ b/Documentation/translations/it_IT/disclaimer-ita.rst @@ -0,0 +1,11 @@ +:orphan: + +.. note:: + This document is maintained by Federico Vaga <federico.v...@vaga.pv.it>. + If you find any difference between this document and the original file or a + problem with the translation, please contact the maintainer of this file. + +.. warning:: + The purpose of this file is to be easier to read and understand for Italian + speakers and is not intended as a fork. So, if you have any comments or + updates for this file please try to update the original English file first. diff --git a/Documentation/translations/it_IT/index.rst b/Documentation/translations/it_IT/index.rst new file mode 100644 index ..e688c06fd9a4 --- /dev/null +++ b/Documentation/translations/it_IT/index.rst @@ -0,0 +1,101 @@ +.. _it_linux_doc: + +=== +Traduzione italiana +=== + +L'obiettivo di questa traduzione è di rendere più facile la lettura e +la comprensione per chi preferisce leggere in lingua italiana. +Tenete presente che la documentazione di riferimento rimane comunque +quella in lingua inglese: :ref:`linux_doc` + +Questa traduzione cerca di essere il più fedele possibile all'originale ma +è ovvio che alcune frasi vadano trasformate: non aspettatevi una traduzione +letterale. Quando possibile, si eviteranno gli inglesismi ed al loro posto +verranno utilizzate le corrispettive parole italiane. + +Se notate che la traduzione non è più aggiornata potete contattare +direttamente il manutentore della traduzione italiana. + +Se notate che la documentazione contiene errori o dimenticanze, allora +verificate la documentazione di riferimento in lingua inglese. Se il problema +è presente anche nella documentazione di riferimento, contattate il suo +manutentore. Se avete problemi a scrivere in inglese, potete comunque +riportare il problema al manutentore della traduzione italiana. + +Manutentore della traduzione italiana: Federico Vaga <federico.v...@vaga.pv.it> + +La documentazione del kernel Linux +== + +Questo è il livello principale della documentazione del kernel in +lingua italiana. La traduzione è incompleta, noterete degli avvisi +che vi segnaleranno la mancanza di una traduzione o di un gruppo di +traduzioni. + +Più in generale, la documentazione, come il kernel stesso, sono in +costante sviluppo; particolarmente vero in quanto stiamo lavorando +alla riorganizzazione della documentazione in modo più coerente. +I miglioramenti alla documentazione sono sempre i benvenuti; per cui, +se vuoi aiutare, iscriviti alla lista di discussione linux-doc presso +vger.kernel.org. + +Documentazione per gli utenti +- + +I seguenti manuali sono scritti per gli *utenti* del kernel - ovvero, +coloro che cercano di farlo funzionare in modo ottimale su un dato sistema + +.. warning:: + +TODO ancora da tradurre + +Documentazione per gli sviluppatori di applicazioni +--- + +Il manuale delle API verso lo spazio utente è una collezione di documenti +che descrivono le interfacce del kernel viste dagli sviluppatori +di applicazioni. + +.. warning:: + +TODO ancora da tradurre + + +Introduzione allo sviluppo del kernel +- + +Questi manuali contengono informazioni su come contribuire allo sviluppo +del kernel. +Attorno al kernel Linux gira una comunità molto grande con migliaia di +sviluppatori che contribuiscono ogni anno. Come in ogni grande comunità, +sapere come le cose vengono fatte renderà il processo di integrazione delle +vostre modifiche molto più semplice + +.. warning:: + +TODO ancora da tradurre + +Documentazione della API del kernel +--- + +Questi manuali forniscono dettagli su come funzionano i sottosistemi del +kernel dal punto di
[PATCH 2/5] doc: add chapter labels
The idea is to make it easier to create references (doc-guide does the same). Signed-off-by: Federico Vaga <federico.v...@vaga.pv.it> --- Documentation/index.rst| 2 ++ Documentation/kernel-hacking/index.rst | 2 ++ 2 files changed, 4 insertions(+) diff --git a/Documentation/index.rst b/Documentation/index.rst index 331da87c82c8..8f11fccb9744 100644 --- a/Documentation/index.rst +++ b/Documentation/index.rst @@ -3,6 +3,8 @@ You can adapt this file completely to your liking, but it should at least contain the root `toctree` directive. +.. _linux_doc: + The Linux Kernel documentation == diff --git a/Documentation/kernel-hacking/index.rst b/Documentation/kernel-hacking/index.rst index fcb0eda3cca3..f53027652290 100644 --- a/Documentation/kernel-hacking/index.rst +++ b/Documentation/kernel-hacking/index.rst @@ -1,3 +1,5 @@ +.. _kernel_hacking: + = Kernel Hacking Guides = -- 2.14.3 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 1/5] doc: typos and minor fixes
Signed-off-by: Federico Vaga <federico.v...@vaga.pv.it> --- Documentation/doc-guide/kernel-doc.rst| 2 +- Documentation/doc-guide/parse-headers.rst | 4 ++-- Documentation/doc-guide/sphinx.rst| 4 ++-- Documentation/index.rst | 2 +- Documentation/sphinx/parse-headers.pl | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Documentation/doc-guide/kernel-doc.rst b/Documentation/doc-guide/kernel-doc.rst index 0268335414ce..d322367f70d7 100644 --- a/Documentation/doc-guide/kernel-doc.rst +++ b/Documentation/doc-guide/kernel-doc.rst @@ -262,7 +262,7 @@ comment block. The kernel-doc data structure comments describe each member of the structure, in order, with the ``@member:`` descriptions. The ``@member:`` descriptions must -begin on the very next line following the opening brief function description +begin on the very next line following the opening brief structure description line, with no intervening blank comment lines. The ``@member:`` descriptions may span multiple lines. The continuation lines may contain indentation. diff --git a/Documentation/doc-guide/parse-headers.rst b/Documentation/doc-guide/parse-headers.rst index 96a0423d5dba..cbfbd1748f8f 100644 --- a/Documentation/doc-guide/parse-headers.rst +++ b/Documentation/doc-guide/parse-headers.rst @@ -32,7 +32,7 @@ SYNOPSIS \ **parse_headers.pl**\ [] [] -Where can be: --debug, --help or --man. +Where can be: --debug, --usage or --help. OPTIONS @@ -133,7 +133,7 @@ For both statements, \ **type**\ can be either one of the following: \ **symbol**\ - The ignore or replace statement will apply to the name of enum statements + The ignore or replace statement will apply to the name of enum values at C_FILE. For replace statements, \ **new_value**\ will automatically use :c:type: diff --git a/Documentation/doc-guide/sphinx.rst b/Documentation/doc-guide/sphinx.rst index a2417633fdd8..8d789a117a4f 100644 --- a/Documentation/doc-guide/sphinx.rst +++ b/Documentation/doc-guide/sphinx.rst @@ -28,7 +28,7 @@ The ReST markups currently used by the Documentation/ files are meant to be built with ``Sphinx`` version 1.3 or upper. If you're desiring to build PDF outputs, it is recommended to use version 1.4.6 or upper. -There's a script that checks for the Spinx requirements. Please see +There's a script that checks for the Sphinx requirements. Please see :ref:`sphinx-pre-install` for further details. Most distributions are shipped with Sphinx, but its toolchain is fragile, @@ -266,7 +266,7 @@ some additional features: * row-span: with the role ``rspan`` a cell can be extended through additional rows -* auto span rightmost cell of a table row over the missing cells on the right +* auto-span: rightmost cell of a table row over the missing cells on the right side of that table-row. With Option ``:fill-cells:`` this behavior can changed from *auto span* to *auto fill*, which automatically inserts (empty) cells instead of spanning the last cell. diff --git a/Documentation/index.rst b/Documentation/index.rst index cb7f1ba5b3b1..331da87c82c8 100644 --- a/Documentation/index.rst +++ b/Documentation/index.rst @@ -33,7 +33,7 @@ the kernel interface as seen by application developers. .. toctree:: :maxdepth: 2 - userspace-api/index + userspace-api/index Introduction to kernel development diff --git a/Documentation/sphinx/parse-headers.pl b/Documentation/sphinx/parse-headers.pl index a958d8b5e99d..27117194d41f 100755 --- a/Documentation/sphinx/parse-headers.pl +++ b/Documentation/sphinx/parse-headers.pl @@ -344,7 +344,7 @@ enums and defines and create cross-references to a Sphinx book. B [] [] -Where can be: --debug, --help or --man. +Where can be: --debug, --help or --usage. =head1 OPTIONS -- 2.14.3 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
doc: Italian translation
Ciao Jonathan, here the doc-guide translated in Italian. This set of patches includes some minor changes to the main one. The idea of this first set of patches is also to adjust the structure and our expectations. We tried to translate everything in **Italian**; which means that we avoided imported English words wherever there is the possibility to use the Italian ones. Of course, this is not always possible, or worst doing the translation make it less clear, for example the word "file". Another point. I noticed that the disclaimer for other translations is in English, so I did the same. But actually shouldn't be in Italian, since that page will be read by Italian speakers? -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Documentation/translations: Italian
On Tuesday, 22 May 2018 01:00:35 CEST Jonathan Corbet wrote: > On Mon, 21 May 2018 22:54:18 +0200 > > Federico Vaga <federico.v...@vaga.pv.it> wrote: > > I'm writing you because I would like to start an effort to > > translate the Documentation in Italian. I would like also to > > express the idea of providing guide lines for translations. > > Mi sembra un'ottima idea! :) Siamo sulla stessa lunghezza d'onda :) > > I know that there are already translations for Asian languages but > > I am not able to find the history of them. I do not know if > > translations in European languages are going to be accepted > > (perhaps there is the assumption that everyone knows English in > > the European continent and it is a waste of energy to do > > translations[?]). For example, even if French and Germans are > > quite active there are not translations yet in their language: is > > there a particular reason or simply nobody did it? > > Nobody has done it. There certainly is no policy against > translations to any specific language - that would be hard to > justify, to say the least. > > OK, I might draw the line at Klingon. But the discussion of error > handling in Klingon could actually be a lot of fun. > > I'm happy to accept new translations of stuff in the documentation > directory. In general, I've had two concerns about translations: > they are generally impossible for me to review, and there needs to > be somebody committed to keeping the translations current as the > documentation changes. For Italian, the first problem doesn't > exist, but the second is always there. What are your intentions for > maintaining the translations in the long term? I can maintain the Italian translation. > > If you agree with the need to support different translations, I > > would like to do the Italian one. But first I would like to open > > a little discussion about translations "how to write > > translations"; this discussion should produce a document (in > > English) with guide lines for translator (e.g. Documentation/ > > translation/howto.rst): what to translate first, what to NOT > > translate, how to structure it. > > Once this is defined I will start the Italian translation (I > > already have some documents translated). > > This can be a fine plan, assuming we're convinced that the > guidelines document is really needed. I guess I'm not yet > convinced of that. But you might also consider gaining some > experience in writing, merging, and maintaining a translation > before trying to lay down rules for everybody else. In other > words, I think you might want to do things in the opposite order. You are right, probably I was over-engineering this thing :) > > > How to do translations (IMHO) > > - > > Here my personal guide lines for translations > > > > - Translate only sphinx-ready documents, do not translate > > documents which are not yet sphinx. We should avoid useless > > double work; at some point, I guess, everything will be sphinx. > > I wouldn't insist on that. But a better idea in any case would be: > if a document you want to translate isn't yet in RST, just do the > conversion. The amount of work required is usually quite small. ok > > - Include in all documents a disclaimer saying that English is the > > main reference (use sphinx directive 'include' to include it). > > - Include in all documents a reference to the English version. So > > it will be easy jump to the original document. > > Remember that the docs need to be readable *without* Sphinx > processing. Better to just name the source document in a quick line > at the top, IMO. ok > > - Translate in order: non-technical documents (they are stable, > > useful for a wider group of people (developers and managers): > > process/, doc-guide/ ), technical documents about key concepts > > (they are stable, and important for new-comers), subsystems (the > > big picture is stable, typically they do not describe all little > > details that may change), and then other documents > If you want to work in that order, that is more than fine. Others > have agreed - the process docs tend to get translated first. But > if somebody else wants to start elsewhere, I wouldn't try to tell > them not to. > > Anyway, thanks for wanting to help improve the documentation! If > you have some of this work already done, you might want to consider > going ahead and posting some patches. I will review them and push something in the next days -- Federico Vaga http://www.federicovaga.it/ -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Documentation/translations: Italian
Hello, I'm writing you because I would like to start an effort to translate the Documentation in Italian. I would like also to express the idea of providing guide lines for translations. A looked a bit in the archive but I did not find anything about these two topics (Italian translation, guide lines for translations). I know that there are already translations for Asian languages but I am not able to find the history of them. I do not know if translations in European languages are going to be accepted (perhaps there is the assumption that everyone knows English in the European continent and it is a waste of energy to do translations[?]). For example, even if French and Germans are quite active there are not translations yet in their language: is there a particular reason or simply nobody did it? Why === There is nothing better for understanding than our own mother tongue, and reading Documentation is one of those activities where it is important to understand its message rather than learning a different language (there are dedicated books and courses for that). This is especially true for young developers and new-comers who are really focused on understanding Linux and a different language can be an obstacle sometimes. I personally had a couple of experiences where I pointed people to the documentation and I had to explain English rather than Linux. Very competent people but they were not used to use English every day. I put myself in this list of people who prefer the mother tongue language when it is time to really understand something. I work for an international organization in a country that is not mine with people coming from all around the European continent and our common tongue is bad-English with all its dialects and accents: true-English (with its own dialects), spaghetti-English, kartoffel-English, paella-English, formage-English and more. Misunderstanding is not rare, and sometimes express ourselves takes more time than needed. This is another reason why I believe that for understanding purposes is good to read in our own mother tongue. Plan If you agree with the need to support different translations, I would like to do the Italian one. But first I would like to open a little discussion about translations "how to write translations"; this discussion should produce a document (in English) with guide lines for translator (e.g. Documentation/ translation/howto.rst): what to translate first, what to NOT translate, how to structure it. Once this is defined I will start the Italian translation (I already have some documents translated). How to do translations (IMHO) - Here my personal guide lines for translations - Translate only sphinx-ready documents, do not translate documents which are not yet sphinx. We should avoid useless double work; at some point, I guess, everything will be sphinx. - Include in all documents a disclaimer saying that English is the main reference (use sphinx directive 'include' to include it). - Include in all documents a reference to the English version. So it will be easy jump to the original document. - Translate in order: non-technical documents (they are stable, useful for a wider group of people (developers and managers): process/, doc-guide/ ), technical documents about key concepts (they are stable, and important for new-comers), subsystems (the big picture is stable, typically they do not describe all little details that may change), and then other documents - avoid scattered translations: try to finish one "topic" before translating something else Probably there is much more, that's why I would like to have a little discussion about it. Thanks for reading everything :) -- Federico Vaga http://www.federicovaga.it/ -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
