docs-commits January 2006

docs-commits@lists.fedoraproject.org

1 participants
215 discussions

docs-common/packaging omf.xsl,1.4,1.5
by fedora-docs-commits＠redhat.com 28 Jan '06

28 Jan '06

Author: pfrields Update of /cvs/docs/docs-common/packaging In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14232/docs-common/packaging Modified Files: omf.xsl Log Message: Fix lang for English document OMFs Index: omf.xsl =================================================================== RCS file: /cvs/docs/docs-common/packaging/omf.xsl,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- omf.xsl 20 Jan 2006 02:05:15 -0000 1.4 +++ omf.xsl 28 Jan 2006 18:34:08 -0000 1.5 @@ -41,7 +41,10 @@ <identifier url="file:/usr/share/fedora/doc/fedora-doc-{$docbase}/{$lang}/{$docbase}-{$lang}.xml"/> </xsl:otherwise> </xsl:choose> - <language code="{$lang}"/> + <xsl:choose> + <xsl:when test="$lang='en'"><language code="C"/></xsl:when> + <xsl:otherwise><language code="$lang"/></xsl:otherwise> + </xsl:choose> <relation seriesid="7a5d3ea2-2a1e-11da-86a3-8ea47a4bb227"/> <rights type="GNU FDL" license.version="1.1" /> </resource>

1 0

infrastructure/build-docs build-docs.spec,1.1,1.2
by fedora-docs-commits＠redhat.com 28 Jan '06

28 Jan '06

Author: nman64 Update of /cvs/docs/infrastructure/build-docs In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24085 Modified Files: build-docs.spec Log Message: Updated spec Index: build-docs.spec =================================================================== RCS file: /cvs/docs/infrastructure/build-docs/build-docs.spec,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- build-docs.spec 5 Jan 2006 00:17:23 -0000 1.1 +++ build-docs.spec 28 Jan 2006 08:00:04 -0000 1.2 @@ -1,6 +1,6 @@ Summary: A simple script and cron job to build Fedora Documentation Name: build-docs -Version: 0.0.3 +Version: 0.0.4 Release: 1 URL: http://fedoraproject.org/wiki/DocsProject License: GPL @@ -47,6 +47,10 @@ %endif %changelog +* Sat Jan 28 2006 Patrick Barnes <nman64(a)n-man.com> +- Fixed potentially nasty typo in Makefile (only affects non-rpm installs) +- Incremented version to 0.0.4 + * Sat Dec 17 2005 Patrick Barnes <nman64(a)n-man.com> - Renamed package to build-docs - Updated script now allows -k flag

1 0

infrastructure/build-docs Makefile,1.1,1.2
by fedora-docs-commits＠redhat.com 28 Jan '06

28 Jan '06

Author: nman64 Update of /cvs/docs/infrastructure/build-docs In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24051 Modified Files: Makefile Log Message: Fix potentially nasty typo Index: Makefile =================================================================== RCS file: /cvs/docs/infrastructure/build-docs/Makefile,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Makefile 5 Jan 2006 00:17:23 -0000 1.1 +++ Makefile 28 Jan 2006 07:58:09 -0000 1.2 @@ -43,7 +43,7 @@ install-docs: @[ "x$(INSTROOT)" != "x" ] || echo -e "\nWARNING\nWARNING: Installation using make is discouraged, try RPMs instead!\nWARNING\n" mkdir -p $(INSTROOT)$(DOCDIR) - install README $(INSTROO)$(DOCDIR)/README + install README $(INSTROOT)$(DOCDIR)/README uninstall: @rm -fv $(INSTROOT)/etc/cron.hourly/$(PKGNAME).cron

1 0

translation-quick-start-guide rpm-info.xml,1.4,1.5
by fedora-docs-commits＠redhat.com 28 Jan '06

28 Jan '06

Author: tombo Update of /cvs/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23858 Modified Files: rpm-info.xml Log Message: Added italian description tags and data Index: rpm-info.xml =================================================================== RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- rpm-info.xml 26 Jan 2006 06:21:28 -0000 1.4 +++ rpm-info.xml 28 Jan 2006 07:09:54 -0000 1.5 @@ -30,6 +30,12 @@ Quick start guide to providing translations on the Fedora Project. </desc> </translation> + <translation lang="it"> + <title>Guida rapida alle traduzioni</title> + <desc> + Guida rapida per fornire traduzioni rapide nel Fedora Project. + </desc> + </translation>  </titles> <changelog order="newest-first"> @@ -37,14 +43,18 @@ <author worker="PaulWFrields"/> <details lang="en">Additional style editing, division of procedures into more readable sections</details> + <details lang="it">Ulteriori aggiunte di stile, divisioni delle procedure in sezioni pi�� + leggibili</details> </revision> <revision date="Fri Jan 20 2006" number="0.1" role="doc"> <author worker="PaulWFrields"/> <details lang="en">First round of editing.</details> + <details lang="it">Primo round di editing.</details> </revision> <revision date="Wed Jan 18 2006" number="0.0.1" role="doc"> <author worker="ManuelOspina"/> <details lang="en">First draft</details> - </revision> + <details lang="en">Prima bozza</details> +</revision> </changelog> </rpm-info>

1 0

docs-common/bin fdpsh,1.2,1.3
by fedora-docs-commits＠redhat.com 27 Jan '06

27 Jan '06

Author: jtr Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7398/bin Modified Files: fdpsh Log Message: Append commands to the log file "/tmp/fdpsh.log" if, and only if, it already exists. Index: fdpsh =================================================================== RCS file: /cvs/docs/docs-common/bin/fdpsh,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- fdpsh 16 Jan 2006 05:49:23 -0000 1.2 +++ fdpsh 27 Jan 2006 23:15:56 -0000 1.3 @@ -18,6 +18,8 @@ FDPDIR=${FDPBINDIR}/../.. export FDPDIR SHELL=${FDPBINDIR}/${ME} export SHELL # +FDPLOG=/tmp/fdpsh.log +# . ${FDPBINDIR}/fdp-functions # CMD= @@ -29,9 +31,11 @@ esac done if [ "${CMD}" ]; then + [ ! -f ${FDPLOG} ] || echo "${CMD}" >>${FDPLOG} eval ${CMD} results=$? elif [ $# -gt 0 ]; then + [ ! -f ${FDPLOG} ] || echo "${CMD}" >>${FDPLOG} eval $@ results=$? else @@ -40,6 +44,7 @@ echo -n "${ME}> " >&2 read -e cmd if [ "${cmd}" ]; then + [ ! -f ${FDPLOG} ] || echo "${CMD}" >>${FDPLOG} eval ${cmd} results=$? if [ ${results} -gt 0 ]; then

1 0

translation-quick-start-guide translation-quick-start-it.xml, 1.1, 1.2
by fedora-docs-commits＠redhat.com 26 Jan '06

26 Jan '06

Author: tombo Update of /cvs/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23623/translation-quick-start-guide Modified Files: translation-quick-start-it.xml Log Message: updated to new version Index: translation-quick-start-it.xml =================================================================== RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-it.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- translation-quick-start-it.xml 26 Jan 2006 06:10:31 -0000 1.1 +++ translation-quick-start-it.xml 27 Jan 2006 00:50:16 -0000 1.2 @@ -7,8 +7,8 @@ %FEDORA-ENTITIES-IT; <!ENTITY DOCNAME "translation-quick-start-guide"> - <!ENTITY DOCVERSION "0.1"> - <!ENTITY DOCDATE "2006-01-20"> + <!ENTITY DOCVERSION "0.2"> + <!ENTITY DOCDATE "2006-01-27"> <!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)"> <!ENTITY FCLOCALVER "4"> @@ -21,7 +21,7 @@ &FDP-INFO; - <section id="sn_intro"> + <section id="sn-intro"> <title>Introduzione</title> <para> @@ -95,10 +95,13 @@ Cambia i permessi alla tua chiave ed alla tua directory <filename>.ssh</filename>: </para> + + + + <screen> -<command>chmod 755 ~/.ssh</command> - +<command>chmod 755 ~/.ssh</command> </screen> </step> @@ -119,11 +122,14 @@ Spagnoli, per discutere problematiche inerenti solo la comunit�� di traduttori individuale. </para> - <para> - Potrai anche trovare utile sottoscriverti alla - <firstterm>fedora-docs-list</firstterm> per rimanere informato sulle - problematiche generali della documentazione. - </para> + <tip> + <title>Problematiche generali della documentazione</title> + <para> + Potrai anche trovare utile sottoscriverti alla + <firstterm>fedora-docs-list</firstterm> per rimanere informato sulle + problematiche generali della documentazione. + </para> + </tip> </section> <section id="sn_translating_software"> @@ -169,11 +175,16 @@ <para> Ora puoi cominciare a tradurre. </para> - <procedure> - <step> - <para> - Vai nella directory del pacchetto che hai preso. - </para> + + <section id="sn-translating-strings"> + <title>Tradurre le stringhe</title> + + <procedure> + <step> + <para> + Vai nella directory del pacchetto che hai + preso. + </para> <screen> <command>cd ~/translate/<replaceable>package_name</replaceable></command> @@ -192,7 +203,8 @@ </step> <step> <para> - Traduci il file po del tuo linguaggio un un editor per po come + Traduci il file <filename>.po</filename> del tuo linguaggio + un un editor per <filename>.po</filename> come <application>KBabel</application> o <application>gtranslator</application>. Per esempio, per aprire il file <filename>.po</filename> per lo Spagnolo in @@ -211,19 +223,23 @@ </para> <screen> -<command>cvs commit -m 'comments' <replaceable>lang</replaceable>.po</command> +<command>cvs commit -m '<replaceable>comments</replaceable>' <replaceable>lang</replaceable>.po</command> </screen> </step> <step> <para> - Come ultimo passo, clicca il link <literal>release</literal> sulla - pagina status per rilasciare il modulo affinch�� altre persone possano lavorarci - sopra. + Come ultimo passo, clicca il link <literal>release</literal> sulla pagina status + per rilasciare il modulo affinch�� altre persone possano lavorarci sopra. </para> </step> </procedure> - <para> + </section> + + <section id="sn-proofreading"> + <title>Controllare la leggibilit��</title> + + <para> Se vuoi leggere la bozza della tua traduzione come parte integrante del software, segui i seguenti passi: </para> @@ -278,16 +294,24 @@ L'applicazione relativa al pacchetto tradotto verr�� eseguita con le stringhe tradotte. </para> + </section> + </section> <section id="sn_translating_docs"> <title>Tradurre la documentazione</title> - + <para> Anche la documentazione Fedora �� immagazzinata in un repositorio CVS sotto - la directory <filename>docs/</filename>. Il processo per scaricare - la documentazione �� similare a quello utilizzato per scaricare - i files <filename>.po</filename>: + la directory <filename>docs/</filename>. + </para> + + <section id="sn-downloading-docs"> + <title>Scaricare la documentazione</title> + + <para> + Il processo per scaricare la documentazione �� similare a quello + utilizzato per scaricare i files <filename>.po</filename>: </para> <screen> @@ -299,7 +323,8 @@ Con questo passo verranno scaricati i documenti attuali nella directory. Per scaricare solo un singolo documento da tradurre, visualizza i moduli attuali nel repositorio quindi esegui il check out di quel modulo. Devi - anche eseguire il check out del modulo <filename>docs-common</filename> per + anche eseguire il check out del modulo + <filename>docs-common</filename> per controllare la validit�� del tuo documento per la compilazione. </para> @@ -322,8 +347,14 @@ <para> Quindi potrai lavorare sulla nuova copia. - </para> - <para> + </para> + + </section> + + <section id="sn-translating-with-apps"> + <title>Usare le applicazioni per la traduzione</title> + + <para> Puoi anche convertire i files XML in <filename>.po</filename> files e lavorare con un <replaceable>.po</replaceable> editor come <application>KBabel</application> o @@ -344,7 +375,8 @@ </step> <step> <para> - Estrai le stringhe traducibili con xml2pot: + Estrai le stringhe traducibili con + <command>xml2pot</command>: </para> <screen> @@ -374,26 +406,30 @@ <command>po2xml example-tutorial-en.xml <replaceable>lang</replaceable>.po > example-tutorial-<replaceable>lang</replaceable>.xml</command> </screen> - </step> - </procedure> - <para> - Il filtro <command>xml2po</command> non include le entities - nel file <filename>.po</filename>. Dovrai cambiare il - linguaggio del documento. Trova la linea tipo la seguente in prossimit�� - della cima del documento: - </para> + </step> + <step> + <para> + Il filtro <command>xml2po</command> non include le entities + nel file <filename>.po</filename>. Dovrai cambiare il + linguaggio del documento. Trova la linea tipo la seguente in prossimit�� + della cima del documento: + </para> <screen> <computeroutput><article id="example-tutorial" lang="en"></computeroutput> </screen> - <para>Cambia gli attributi con quelli del tuo linguaggio:</para> + </step> + <step> + <para>Cambia gli attributi con quelli del tuo linguaggio:</para> <screen> -<userinput><article id="example-tutorial" lang="<replaceable>es</replaceable>"></userinput> +<computeroutput><article id="example-tutorial" lang="<userinput><replaceable>es</replaceable></userinput>"></computeroutput> </screen> - <para> + </step> + <step> + <para> Quando il file tradotto �� pronto, aggiungilo al repository: </para> @@ -402,21 +438,29 @@ <command>cvs commit -m '<replaceable>Any comment</replaceable>' example-tutorial-<replaceable>lang</replaceable>.xml</command> </screen> - <para> + </step> + </procedure> + + </section> + + <section id="sn-changing-makefile"> + <title>Modificare il <filename>Makefile</filename></title> + + <para> Potresti dover cambiare il <filename>Makefile</filename> affinch�� il documento possa essere compilato nei formati HTML e PDF. </para> - <caution> - <title>Nota:</title> - <para> + <important> + <title>Evitare conflitti di traduzione</title> + <para> Sei pregato di avvisare la comunit�� attraverso la fedora-doc-list e fedora-trans-<replaceable>locale</replaceable> che stai modificando il <filename>Makefile</filename>. Informa la comunit�� che stai lavorando alla traduzione del documento prima di cominciare, per evitare conflitti tra traduttori lavorando sullo stesso file. - </para> - </caution> + </para> + </important> <procedure> <step> @@ -436,7 +480,7 @@ </para> <screen> -<userinput>LANGUAGES = en de <replaceable>lang</replaceable></userinput> +<computeroutput>LANGUAGES = en de <userinput><replaceable>lang</replaceable></userinput></computeroutput> </screen> </step> @@ -452,15 +496,18 @@ </step> <step> <para> - Quindi, potrai compilare il document nel tuo linguaggio scrivendo: + Quindi, potrai compilare il document nel tuo linguaggio + scrivendo: </para> <screen> <command>make html-<replaceable>lang</replaceable></command> </screen> - </step> - </procedure> + </step> + </procedure> + + </section> </section>

1 0

translation-quick-start-guide translation-quick-start-en.xml, 1.7, 1.8
by fedora-docs-commits＠redhat.com 26 Jan '06

26 Jan '06

Author: pfrields Update of /cvs/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14415 Modified Files: translation-quick-start-en.xml Log Message: Too much trouble to change these since already published Index: translation-quick-start-en.xml =================================================================== RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-en.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- translation-quick-start-en.xml 26 Jan 2006 06:21:28 -0000 1.7 +++ translation-quick-start-en.xml 26 Jan 2006 06:27:15 -0000 1.8 @@ -34,7 +34,7 @@ </section> - <section id="sn-accounts"> + <section id="sn_accounts"> <title>Accounts and Subscriptions</title> <para> @@ -132,7 +132,7 @@ </tip> </section> - <section id="sn-translating-software"> + <section id="sn_translating_software"> <title>Translating Software</title> <para> @@ -298,7 +298,7 @@ </section> - <section id="sn-translating-docs"> + <section id="sn_translating_docs"> <title>Translating Documentation</title> <para>

1 0

translation-quick-start-guide translation-quick-start-en.xml, 1.6, 1.7 rpm-info.xml, 1.3, 1.4
by fedora-docs-commits＠redhat.com 26 Jan '06

26 Jan '06

Author: pfrields Update of /cvs/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14371 Modified Files: translation-quick-start-en.xml rpm-info.xml Log Message: Additional style editing, division into more readable sections Index: translation-quick-start-en.xml =================================================================== RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-en.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- translation-quick-start-en.xml 21 Jan 2006 02:37:27 -0000 1.6 +++ translation-quick-start-en.xml 26 Jan 2006 06:21:28 -0000 1.7 @@ -7,8 +7,8 @@ %FEDORA-ENTITIES-EN; <!ENTITY DOCNAME "translation-quick-start-guide"> - <!ENTITY DOCVERSION "0.1"> - <!ENTITY DOCDATE "2006-01-20"> + <!ENTITY DOCVERSION "0.2"> + <!ENTITY DOCDATE "2006-01-26"> <!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)"> <!ENTITY FCLOCALVER "4"> @@ -21,7 +21,7 @@ &FDP-INFO; - <section id="sn_intro"> + <section id="sn-intro"> <title>Introduction</title> <para> @@ -34,16 +34,16 @@ </section> - <section id="sn_accounts"> - <title>Accounts and subscriptions</title> + <section id="sn-accounts"> + <title>Accounts and Subscriptions</title> <para> To participate in the &FP; as a translator you need an account. You can apply for an account at <ulink - url="http://i18n.redhat.com/cgi-bin/i18n-signup/"/>. You need to - provide a user name (login), an email address, a target language - — most likely your native language — and the public - part of your SSH key. + url="http://i18n.redhat.com/cgi-bin/i18n-signup/"/>. You need to + provide a user name, an email address, a target language — + most likely your native language — and the public part of + your SSH key. </para> <para> @@ -66,10 +66,10 @@ (<filename>~/.ssh/id_dsa</filename>) and enter a passphrase. </para> <caution> - <title>Note</title> + <title>Don't Forget Your Passphrase!</title> <para> - Do not forget this passphrase as you will need it to access - to the CVS repository. + You will need your passphrase to access to the CVS + repository. It cannot be recovered if you forget it. </para> </caution> </step> @@ -96,15 +96,18 @@ directory: </para> + + + + <screen> -<command>chmod 755 ~/.ssh</command> - +<command>chmod 700 ~/.ssh</command> </screen> </step> <step> <para> - Copy and paste the ssh key in the space provided in order to + Copy and paste the SSH key in the space provided in order to complete the account application. </para> </step> @@ -119,15 +122,18 @@ translators, to discuss issues that affect only the individual community of translators. </para> - <para> - You may also find it useful to subscribe to - <firstterm>fedora-docs-list</firstterm> to stay informed about - general documentation issues. - </para> + <tip> + <title>General Documentation Issues</title> + <para> + You may also find it useful to subscribe to + <firstterm>fedora-docs-list</firstterm> to stay informed about + general documentation issues. + </para> + </tip> </section> - <section id="sn_translating_software"> - <title>Translating software</title> + <section id="sn-translating-software"> + <title>Translating Software</title> <para> The translatable part of a software package is available in one or @@ -169,91 +175,101 @@ <para> You can now start translating. </para> - <procedure> - <step> - <para> - Go to the directory of the package you have taken. - </para> + + <section id="sn-translating-strings"> + <title>Translating Strings</title> + + <procedure> + <step> + <para> + Change directory to the location of the package you have + taken. + </para> <screen> <command>cd ~/translate/<replaceable>package_name</replaceable></command> </screen> - </step> - <step> - <para> - Update the files with the following command: - </para> + </step> + <step> + <para> + Update the files with the following command: + </para> <screen> <command>cvs up</command> </screen> - </step> - <step> - <para> - Translate the po file of your language in a po editor such as - <application>KBabel</application> or - <application>gtranslator</application>. For example, to open - the <filename>.po</filename> file for Spanish in - <application>KBabel</application>, type: - </para> + </step> + <step> + <para> + Translate the <filename>.po</filename> file of your language + in a <filename>.po</filename> editor such as + <application>KBabel</application> or + <application>gtranslator</application>. For example, to open + the <filename>.po</filename> file for Spanish in + <application>KBabel</application>, type: + </para> <screen> <command>kbabel es.po</command> </screen> - </step> - <step> - <para> - When you finish your work, commit your changes back to the - repository: - </para> + </step> + <step> + <para> + When you finish your work, commit your changes back to the + repository: + </para> <screen> -<command>cvs commit -m 'comments' <replaceable>lang</replaceable>.po</command> +<command>cvs commit -m '<replaceable>comments</replaceable>' <replaceable>lang</replaceable>.po</command> </screen> - </step> - <step> - <para> - As a last step, click the <literal>release</literal> link on - the status page to release the module so other people can work - on it. - </para> - </step> - </procedure> - <para> - If you want to proofread your translation as part of the software, - follow these steps: - </para> - <procedure> - <step> - <para> - Go to the directory of the package you want to proofread: - </para> + </step> + <step> + <para> + Click the <literal>release</literal> link on the status page + to release the module so other people can work on it. + </para> + </step> + </procedure> + </section> + + <section id="sn-proofreading"> + <title>Proofreading</title> + + <para> + If you want to proofread your translation as part of the + software, follow these steps: + </para> + <procedure> + <step> + <para> + Go to the directory of the package you want to proofread: + </para> <screen> <command>cd ~/translate/<replaceable>package_name</replaceable></command> </screen> - </step> - <step> - <para> - Convert the <filename>.po</filename> file in - <filename>.mo</filename> file with <command>msgfmt</command>: - </para> + </step> + <step> + <para> + Convert the <filename>.po</filename> file in + <filename>.mo</filename> file with <command>msgfmt</command>: + </para> <screen> <command>msgfmt <replaceable>lang</replaceable>.po</command> </screen> - </step> - <step> - <para> - Overwrite the existing <filename>.mo</filename> file in - <filename>/usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</filename>. - First, back up the existing file: + </step> + <step> + <para> + Overwrite the existing <filename>.mo</filename> file in + <filename>/usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</filename>. + First, back up the existing file: </para> <screen> @@ -261,206 +277,237 @@ <command>mv <replaceable>package_name</replaceable>.mo /usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</command> </screen> - </step> - <step> - <para> - Proofread the package with the translated strings as part of - the application: - </para> + </step> + <step> + <para> + Proofread the package with the translated strings as part of + the application: + </para> <screen> <command>LANG=<replaceable>lang</replaceable> rpm -qi <replaceable>package_name</replaceable></command> </screen> - </step> - </procedure> - <para> - The application related to the translated package will run with - the translated strings. - </para> + </step> + </procedure> + <para> + The application related to the translated package will run with + the translated strings. + </para> + </section> + </section> - <section id="sn_translating_docs"> - <title>Translating documentation</title> + <section id="sn-translating-docs"> + <title>Translating Documentation</title> <para> The Fedora documentation is also stored in a CVS repository under - the directory <filename>docs/</filename>. The process to download - the documentation is similar to the one used to download - <filename>.po</filename> files: + the directory <filename>docs/</filename>. </para> + <section id="sn-downloading-docs"> + <title>Downloading Documentation</title> + + <para> + The process to download the documentation is similar to the one + used to download <filename>.po</filename> files: + </para> + <screen> <command>export CVSROOT=:ext:<replaceable>username</replaceable>@cvs.fedora.redhat.com:/cvs/docs</command> <command>cvs co docs</command> </screen> - <para> - This step downloads all the current documents in the directory. To - download only a single document to translate, list the current - modules in the repository and then check out that module. You - must also check out the <filename>docs-common</filename> module to - check document validity for building. - </para> + <para> + This step downloads all the current documents in the directory. + To download only a single document to translate, list the + current modules in the repository and then check out that + module. You must also check out the + <filename>docs-common</filename> module to check document + validity for building. + </para> <screen> <command>cvs co -c</command> <command>cvs co example-tutorial docs-common</command> </screen> - <para> - The documents are written in DocBook XML format and named using - the specific-language locale, such as - <filename>example-tutorial-en.xml</filename>. If you plan to - translate directly from the original XML file, you should create - the document for your language: - </para> + <para> + The documents are written in DocBook XML format and named using + the specific-language locale, such as + <filename>example-tutorial-en.xml</filename>. If you plan to + translate directly from the original XML file, you should create + the document for your language: + </para> <screen> <command>cp example-tutorial-en.xml example-tutorial-<replaceable>es</replaceable>.xml</command> </screen> - <para> - Afterwards you can work on the new copy. - </para> - <para> - You can also convert the XML files into <filename>.po</filename> - files and work with a <replaceable>.po</replaceable> editor like - <application>KBabel</application> or - <application>gtranslator</application>. To do so, follow these - steps: - </para> - <procedure> - <step> - <para> - In a terminal, go to the directory of the document you want to - translate: - </para> + <para> + Afterwards you can work on the new copy. + </para> + + </section> + <section id="sn-translating-with-apps"> + <title>Using Translation Applications</title> + + <para> + You can also convert the XML files into <filename>.po</filename> + files and work with a <filename>.po</filename> editor like + <application>KBabel</application> or + <application>gtranslator</application>. To do so, follow these + steps: + </para> + <procedure> + <step> + <para> + In a terminal, go to the directory of the document you want + to translate: + </para> + <screen> <command>cd ~/docs/example-tutorial</command> </screen> - </step> - <step> - <para> - Extract the translatable strings with xml2pot: - </para> + </step> + <step> + <para> + Extract the translatable strings with + <command>xml2pot</command>: + </para> <screen> <command>xml2pot example-tutorial-en.xml > <replaceable>lang</replaceable>.po</command> </screen> - </step> - <step> - <para> - Now you can translate the file using the same application used - to translate software: - </para> - + </step> + <step> + <para> + Now you can translate the file using the same application + used to translate software: + </para> + <screen> <command>kbabel <replaceable>lang</replaceable>.po</command> </screen> - </step> - <step> - <para> - Once you finish, it is necessary to convert the translated - <filename>.po</filename> file to <filename>.xml</filename> - file in the target language with <command>po2xml</command>: - </para> + </step> + <step> + <para> + Once you finish, you must convert the translated + <filename>.po</filename> file to <filename>.xml</filename> + file in the target language with <command>po2xml</command>: + </para> <screen> <command>po2xml example-tutorial-en.xml <replaceable>lang</replaceable>.po > example-tutorial-<replaceable>lang</replaceable>.xml</command> </screen> - </step> - </procedure> - <para> - The <command>xml2po</command> filter does not include entities - in the <filename>.po</filename> file. You must change the - language of the document. Locate a line like the following near - the top of the document: - </para> + </step> + <step> + <para> + The <command>xml2pot</command> filter does not include + entities in the <filename>.po</filename> file. You must + change the language of the document. Locate a line like the + following near the top of the document: + </para> <screen> <computeroutput><article id="example-tutorial" lang="en"></computeroutput> </screen> - <para>Change the attribute to your language:</para> + </step> + <step> + <para>Change the attribute to your language:</para> <screen> -<userinput><article id="example-tutorial" lang="<replaceable>es</replaceable>"></userinput> +<computeroutput><article id="example-tutorial" lang="<userinput><replaceable>es</replaceable></userinput>"></computeroutput> </screen> - <para> - When the translated file is ready, add it to the repository: - </para> + </step> + <step> + <para> + When the translated file is ready, add it to the repository: + </para> <screen> <command>cvs add example-tutorial-<replaceable>lang</replaceable>.xml</command> <command>cvs commit -m '<replaceable>Any comment</replaceable>' example-tutorial-<replaceable>lang</replaceable>.xml</command> </screen> - <para> - You may have to change the <filename>Makefile</filename> so the - document can be built in HTML and PDF formats. - </para> - <caution> - <title>Note:</title> + </step> + </procedure> + + </section> + + <section id="sn-changing-makefile"> + <title>Changing the <filename>Makefile</filename></title> + <para> - Please advise the community through fedora-doc-list and - fedora-trans-<replaceable>locale</replaceable> that you are - modifying the <filename>Makefile</filename>. Inform the - community that you are working on the translation of this - document before you begin, to avoid conflict between translators - working on the same file. + You may have to change the <filename>Makefile</filename> so the + document can be built in HTML and PDF formats. </para> - </caution> - - <procedure> - <step> + <important> + <title>Avoid Translation Conflicts</title> <para> - In the text editor of your preference, open the - <filename>Makefile</filename>. + Please advise the community through fedora-doc-list and + fedora-trans-<replaceable>locale</replaceable> that you are + modifying the <filename>Makefile</filename>. Inform the + community that you are working on the translation of this + document before you begin, to avoid conflict between + translators working on the same file. </para> + </important> + + <procedure> + <step> + <para> + In the text editor of your preference, open the + <filename>Makefile</filename>. + </para> <screen> <command>vi Makefile</command> </screen> - </step> - <step> - <para> - Add the locale of the new translation after the other - languages as in the following example: - </para> + </step> + <step> + <para> + Add the locale of the new translation after the other + languages as in the following example: + </para> <screen> -<userinput>LANGUAGES = en de <replaceable>lang</replaceable></userinput> +<computeroutput>LANGUAGES = en de <userinput><replaceable>lang</replaceable></userinput></computeroutput> </screen> - </step> - <step> - <para> - Commit the <filename>Makefile</filename>. - </para> + </step> + <step> + <para> + Commit the <filename>Makefile</filename>. + </para> <screen> <command>cvs commit -m '<replaceable>Any comment</replaceable>' Makefile</command> </screen> - </step> - <step> - <para> - Then, you can build the document in your langugage by typing: - </para> + </step> + <step> + <para> + Then, you can build the document in your langugage by + typing: + </para> <screen> <command>make html-<replaceable>lang</replaceable></command> </screen> - </step> - </procedure> + </step> + </procedure> + + </section> </section> Index: rpm-info.xml =================================================================== RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- rpm-info.xml 21 Jan 2006 02:48:19 -0000 1.3 +++ rpm-info.xml 26 Jan 2006 06:21:28 -0000 1.4 @@ -1,3 +1,7 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> + +<!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd"> + <rpm-info> <colophon> <worker surname="Ospina" firstname="Manuel" id="ManuelOspina" email="mospina(a)redhat.com" wholename="Manuel Ospina" initials="MO"/> @@ -29,7 +33,12 @@  </titles> <changelog order="newest-first"> - <revision date="2006-01-20" number="0.1" role="doc"> + <revision date="2006-01-25" number="0.2" role="doc"> + <author worker="PaulWFrields"/> + <details lang="en">Additional style editing, division of procedures into more readable + sections</details> + </revision> + <revision date="Fri Jan 20 2006" number="0.1" role="doc"> <author worker="PaulWFrields"/> <details lang="en">First round of editing.</details> </revision>

1 0

translation-quick-start-guide translation-quick-start-it.xml, NONE, 1.1 Makefile, 1.3, 1.4
by fedora-docs-commits＠redhat.com 26 Jan '06

26 Jan '06

Author: tombo Update of /cvs/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14284/translation-quick-start-guide Modified Files: Makefile Added Files: translation-quick-start-it.xml Log Message: Added italian version --- NEW FILE translation-quick-start-it.xml ---  <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//IT" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ <!ENTITY % FEDORA-ENTITIES-IT SYSTEM "../docs-common/common/fedora-entities-it.ent"> %FEDORA-ENTITIES-IT; <!ENTITY DOCNAME "translation-quick-start-guide"> <!ENTITY DOCVERSION "0.1"> <!ENTITY DOCDATE "2006-01-20"> <!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)"> <!ENTITY FCLOCALVER "4"> <!ENTITY FDP-INFO SYSTEM "fdp-info-it.xml" > ]> <article id="translation-quickstart-guide" lang="it"> &FDP-INFO; <section id="sn_intro"> <title>Introduzione</title> <para> Questa guida �� un veloce, semplice, passo-passo insieme di istruzioni per trandurre software e documenti &FP;. Se sei interessato nel comprendere meglio il processo di traduzione impiegato, fa riferimento alla guida per la traduzione o al manuale dello specifico strumento di traduzione. </para> </section> <section id="sn_accounts"> <title>Accounts e sottoscrizioni</title> <para> Per partecipare al &FP; come traduttore hai bisogno di un account. Puoi sottoscrivere un account su <ulink url="http://i18n.redhat.com/cgi-bin/i18n-signup/"/>. Devi fornire un user name (login), un indirizzo email, una lingua di riferimento — in genere coincidente con la tua lingua nativa — e la parte pubblica della tua chiave SSH. </para> <para> Se non hai ancora una chiave SSH, puoi generarne una compiendo i seguenti passi: </para> <procedure> <step> <para> Scrivi in una linea di comando: </para> <screen> <command>ssh-keygen -t dsa</command> </screen> <para> Accetta la posizione predefinita (<filename>~/.ssh/id_dsa</filename>) ed immetti una passphrase. </para> <caution> <title>Nota</title> <para> Non dimenticare questa passphrase di cui avrai bisogno per accedere al repositorio CVS. </para> </caution> </step>    <step> <para> Cambia i permessi alla tua chiave ed alla tua directory <filename>.ssh</filename>: </para> <screen> <command>chmod 755 ~/.ssh</command>  </screen> </step> <step> <para> Copia ed incolla la chiave ssh nello spazio fornito per poter completare la sottoscrizione all'account. </para> </step> </procedure> <para> Ci sono anche due liste su cui puoi discutere i problemi di traduzione. La prima �� <firstterm>fedora-trans-list</firstterm>, una lista generale per discutere i problemi che affliggono tutti i linguaggi. Fa riferimento a <ulink url="http://www.redhat.com/archives/fedora-trans-list"/> per maggiori informazioni. La seconda �� la lista specifica per la tua lingua, tipo <firstterm>fedora-trans-es</firstterm> per i traduttori Spagnoli, per discutere problematiche inerenti solo la comunit�� di traduttori individuale. </para> <para> Potrai anche trovare utile sottoscriverti alla <firstterm>fedora-docs-list</firstterm> per rimanere informato sulle problematiche generali della documentazione. </para> </section> <section id="sn_translating_software"> <title>Tradurre il software</title> <para> La parte traducibile di un pacchetto software �� disponibile in uno o pi�� files <filename>po</filename>. Il &FP; immagazzina questi files in un repositorio CVS sotto la directory <filename>translate/</filename>. Una volta che il tuo account �� stato approvato, scarica questa directory scrivendo le seguenti istruzioni in una linea di comando: </para> <screen> <command>export CVS_RSH=ssh</command> <command>export CVSROOT=:ext:<replaceable>username</replaceable>@i18.redhat.com:/usr/local/CVS</command> <command>cvs -z9 co translate/</command> </screen> <para> Questi comandi scaricheranno tutti i moduli e files <filename>.po</filename> sulla tua macchina seguendo la medesima gerarchia del repositorio. Ogni directory contiene un file <filename>.pot</filename>, tipo <filename>anaconda.pot</filename>, ed il file <filename>.po</filename> per ogni linguaggio, tipo <filename>zh_CN.po</filename>, <filename>de.po</filename>, e cos�� via. </para> <para> Puoi controllare lo status delle traduzioni su <ulink url="http://i18n.redhat.com/cgi-bin/i18n-status"/>. Scegli il tuo linguaggio nel menu a discesa o seleziona overall status. Seleziona un pacchetto per vederne il maintainer ed il nome dell'ultimo traduttore di questo modulo. Se vuoi tradurre un modulo, contatta la tua lista per il linguaggio specifico e fa si che la tua comunit�� sappia che stai lavorando su quel modulo. Quindi, seleziona <literal>take</literal> nella pagina status. Il modulo �� quindi assegnato a te. Alla richiesta di password, immetti quella che hai ricevuto via e-mail quando hai richiesto la sottoscrizione al tuo account. </para> <para> Ora puoi cominciare a tradurre. </para> <procedure> <step> <para> Vai nella directory del pacchetto che hai preso. </para> <screen> <command>cd ~/translate/<replaceable>package_name</replaceable></command> </screen> </step> <step> <para> Aggiorna i files con il seguente comando: </para> <screen> <command>cvs up</command> </screen> </step> <step> <para> Traduci il file po del tuo linguaggio un un editor per po come <application>KBabel</application> o <application>gtranslator</application>. Per esempio, per aprire il file <filename>.po</filename> per lo Spagnolo in <application>KBabel</application>, scrivi: </para> <screen> <command>kbabel es.po</command> </screen> </step> <step> <para> Quando hai finito il tuo lavoro, esegui il commit dei tuoi cambiamenti al repositorio: </para> <screen> <command>cvs commit -m 'comments' <replaceable>lang</replaceable>.po</command> </screen> </step> <step> <para> Come ultimo passo, clicca il link <literal>release</literal> sulla pagina status per rilasciare il modulo affinch�� altre persone possano lavorarci sopra. </para> </step> </procedure> <para> Se vuoi leggere la bozza della tua traduzione come parte integrante del software, segui i seguenti passi: </para> <procedure> <step> <para> Vai alla directory del pacchetto che vuoi testare: </para> <screen> <command>cd ~/translate/<replaceable>package_name</replaceable></command> </screen> </step> <step> <para> Converti il file <filename>.po</filename> in file <filename>.mo</filename> con <command>msgfmt</command>: </para> <screen> <command>msgfmt <replaceable>lang</replaceable>.po</command> </screen> </step> <step> <para> Sovrascrivi il file <filename>.mo</filename> esistente in <filename>/usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</filename>. Prima, fa un back up del file esistente: </para> <screen> <command>cp /usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/<replaceable>package_name</replaceable>.mo <replaceable>package_name</replaceable>.mo-backup</command> <command>mv <replaceable>package_name</replaceable>.mo /usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</command> </screen> </step> <step> <para> Leggi la tua bozza del pacchetto con le stringhe tradotte nell'applicazione: </para> <screen> <command>LANG=<replaceable>lang</replaceable> rpm -qi <replaceable>package_name</replaceable></command> </screen> </step> </procedure> <para> L'applicazione relativa al pacchetto tradotto verr�� eseguita con le stringhe tradotte. </para> </section> <section id="sn_translating_docs"> <title>Tradurre la documentazione</title> <para> Anche la documentazione Fedora �� immagazzinata in un repositorio CVS sotto la directory <filename>docs/</filename>. Il processo per scaricare la documentazione �� similare a quello utilizzato per scaricare i files <filename>.po</filename>: </para> <screen> <command>export CVSROOT=:ext:<replaceable>username</replaceable>@cvs.fedora.redhat.com:/cvs/docs</command> <command>cvs co docs</command> </screen> <para> Con questo passo verranno scaricati i documenti attuali nella directory. Per scaricare solo un singolo documento da tradurre, visualizza i moduli attuali nel repositorio quindi esegui il check out di quel modulo. Devi anche eseguire il check out del modulo <filename>docs-common</filename> per controllare la validit�� del tuo documento per la compilazione. </para> <screen> <command>cvs co -c</command> <command>cvs co example-tutorial docs-common</command> </screen> <para> I documenti sono scritti nel formato DocBook XML e nominati usando lo specifico linguaggio di localizzazione, tipo <filename>example-tutorial-en.xml</filename>. Se pianifichi di tradurre direttamente dai files XML originali, dovrai creare il documento per il tuo linguaggio: </para> <screen> <command>cp example-tutorial-en.xml example-tutorial-<replaceable>es</replaceable>.xml</command> </screen> <para> Quindi potrai lavorare sulla nuova copia. </para> <para> Puoi anche convertire i files XML in <filename>.po</filename> files e lavorare con un <replaceable>.po</replaceable> editor come <application>KBabel</application> o <application>gtranslator</application>. Per farlo compi i seguenti passi: </para> <procedure> <step> <para> In un terminale, vai alla directory del documento che vuoi tradurre: </para> <screen> <command>cd ~/docs/example-tutorial</command> </screen> </step> <step> <para> Estrai le stringhe traducibili con xml2pot: </para> <screen> <command>xml2pot example-tutorial-en.xml > <replaceable>lang</replaceable>.po</command> </screen> </step> <step> <para> Adesso puoi tradurre il file usando la stessa applicazione usata per tradurre il software: </para> <screen> <command>kbabel <replaceable>lang</replaceable>.po</command> </screen> </step> <step> <para> Una volta terminato, �� necessario convertire il file <filename>.po</filename> tradotto nel corrispondente file <filename>.xml</filename> di linguaggio con <command>po2xml</command>: </para> <screen> <command>po2xml example-tutorial-en.xml <replaceable>lang</replaceable>.po > example-tutorial-<replaceable>lang</replaceable>.xml</command> </screen> </step> </procedure> <para> Il filtro <command>xml2po</command> non include le entities nel file <filename>.po</filename>. Dovrai cambiare il linguaggio del documento. Trova la linea tipo la seguente in prossimit�� della cima del documento: </para> <screen> <computeroutput><article id="example-tutorial" lang="en"></computeroutput> </screen> <para>Cambia gli attributi con quelli del tuo linguaggio:</para> <screen> <userinput><article id="example-tutorial" lang="<replaceable>es</replaceable>"></userinput> </screen> <para> Quando il file tradotto �� pronto, aggiungilo al repository: </para> <screen> <command>cvs add example-tutorial-<replaceable>lang</replaceable>.xml</command> <command>cvs commit -m '<replaceable>Any comment</replaceable>' example-tutorial-<replaceable>lang</replaceable>.xml</command> </screen> <para> Potresti dover cambiare il <filename>Makefile</filename> affinch�� il documento possa essere compilato nei formati HTML e PDF. </para> <caution> <title>Nota:</title> <para> Sei pregato di avvisare la comunit�� attraverso la fedora-doc-list e fedora-trans-<replaceable>locale</replaceable> che stai modificando il <filename>Makefile</filename>. Informa la comunit�� che stai lavorando alla traduzione del documento prima di cominciare, per evitare conflitti tra traduttori lavorando sullo stesso file. </para> </caution> <procedure> <step> <para> Nel text editor di tua preferenza, apri il <filename>Makefile</filename>. </para> <screen> <command>vi Makefile</command> </screen> </step> <step> <para> Aggiungi il locale della nuova traduzione dopo gli altri linguaggi come nell'esempio seguente: </para> <screen> <userinput>LANGUAGES = en de <replaceable>lang</replaceable></userinput> </screen> </step> <step> <para> Esegui il commit del <filename>Makefile</filename>. </para> <screen> <command>cvs commit -m '<replaceable>Any comment</replaceable>' Makefile</command> </screen> </step> <step> <para> Quindi, potrai compilare il document nel tuo linguaggio scrivendo: </para> <screen> <command>make html-<replaceable>lang</replaceable></command> </screen> </step> </procedure> </section> </article>  Index: Makefile =================================================================== RCS file: /cvs/docs/translation-quick-start-guide/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Makefile 18 Jan 2006 07:19:25 -0000 1.3 +++ Makefile 26 Jan 2006 06:10:31 -0000 1.4 @@ -8,7 +8,7 @@ # Copyright 2005 Tommy Reynolds, MegaCoder.com ############################################################################### -LANGUAGES = en +LANGUAGES = en it DOCBASE = translation-quick-start XMLEXTRAFILES-en =

1 0

install-guide fedora-install-guide-adminoptions-en.xml, 1.7, 1.8 fedora-install-guide-en.xml, 1.39, 1.40 fedora-install-guide-firstboot-en.xml, 1.17, 1.18 fedora-install-guide-packageselection-en.xml, 1.16, 1.17 rpm-info.xml, 1.4, 1.5
by fedora-docs-commits＠redhat.com 25 Jan '06

25 Jan '06

Author: elliss Update of /cvs/docs/install-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3265 Modified Files: fedora-install-guide-adminoptions-en.xml fedora-install-guide-en.xml fedora-install-guide-firstboot-en.xml fedora-install-guide-packageselection-en.xml rpm-info.xml Log Message: - Updated Package Selection section to match test2 screen. - Broke Boot Options section on configuring the installation system into subsections for clarity. - Amended Boot Options section to cover rescue discs. - Minor style edit of text describing firewall configuration. Index: fedora-install-guide-adminoptions-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- fedora-install-guide-adminoptions-en.xml 23 Jan 2006 23:24:09 -0000 1.7 +++ fedora-install-guide-adminoptions-en.xml 26 Jan 2006 00:15:39 -0000 1.8 @@ -3,8 +3,8 @@ <chapter id="ch-admin-options"> <title>Appendix: Boot Options</title> <para> - The &FED; installation system includes a range of options and - functions for administrators. To use boot options, enter + The &FED; installation system includes a range of functions and + options for administrators. To use boot options, enter <userinput>linux <replaceable>option</replaceable></userinput> at the <prompt>boot:</prompt> @@ -17,6 +17,16 @@ <screen> <userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput> </screen> + <note> + <title>Rescue Mode</title> + + <para> + The &FED; installation and <firstterm>rescue discs</firstterm> may + either boot with <firstterm>rescue mode</firstterm> , or load the + installation system. For more information on rescue discs and + rescue mode, refer to <xref linkend="sn-mode-rescue"/>. + </para> + </note> <section id="sn-bootoptions-installer"> <title>Configuring the Installation System</title> @@ -31,6 +41,11 @@ <itemizedlist> <listitem> <para> + Language + </para> + </listitem> + <listitem> + <para> Display resolution </para> </listitem> @@ -50,59 +65,80 @@ </para> </listitem> </itemizedlist> - - <para> - You may force the installation system to use the lowest possible - screen resolution (640x480) with the <option>lowres</option> - option. To use a specific display resolution, enter - <option>resolution=<replaceable>setting</replaceable></option> as - a boot option. For example, to set the display resolution to - 1024x768, enter: - </para> + + <section id="sn-boot-options-language"> + <title>Specifying the Language</title> + + <para> + To set the language for the installation process screens, + specify the ISO code for that language with the + <option>lang</option> option. For example, the ISO code + <userinput>fr</userinput> identifies the French language: + </para> +<screen> +<userinput>linux lang=<replaceable>fr</replaceable></userinput> +</screen> + </section> + + <section id="sn-boot-options-interface"> + <title>Configuring the Interface</title> + + <para> + You may force the installation system to use the lowest possible + screen resolution (640x480) with the <option>lowres</option> + option. To use a specific display resolution, enter + <option>resolution=<replaceable>setting</replaceable></option> + as a boot option. For example, to set the display resolution to + 1024x768, enter: + </para> <screen> <userinput>linux resolution=<replaceable>1024x768</replaceable></userinput> </screen> - <para> - To run the installation process in <option>text</option> mode, - enter: - </para> + <para> + To run the installation process in <option>text</option> mode, + enter: + </para> <screen> <userinput>linux text</userinput> </screen> - <para> - To enable support for a serial console, enter - <option>serial</option> as an additional option. - </para> + <para> + To enable support for a serial console, enter + <option>serial</option> as an additional option. + </para> + </section> - <para> - Use the <option>askmethod</option> option to display additional - menus that enable you to specify the installation method network - settings. You may also configure the installation method and - network settings at the - <prompt>boot:</prompt> - prompt itself. - </para> + <section id="sn-boot-options-installmethod"> + <title>Specifying the Installation Method</title> - <para> - To specify the installation method from the - <prompt>boot:</prompt> - prompt, use the <option>method</option> option. Refer to - <xref linkend="tb-installmethods"/> for the supported installation - methods. - </para> - <table id="tb-installmethods"> - <title>Installation Methods</title> - <tgroup cols="2"> - <colspec colnum="1" colname="Installation Method"/> - <colspec colnum="2" colname="Option Format"/> - <thead> - <row> + <para> + Use the <option>askmethod</option> option to display additional + menus that enable you to specify the installation method and + network settings. You may also configure the installation method + and network settings at the + <prompt>boot:</prompt> + prompt itself. + </para> + + <para> + To specify the installation method from the + <prompt>boot:</prompt> + prompt, use the <option>method</option> option. Refer to + <xref linkend="tb-installmethods"/> for the supported + installation methods. + </para> + <table id="tb-installmethods"> + <title>Installation Methods</title> + <tgroup cols="2"> + <colspec colnum="1" colname="Installation Method"/> + <colspec colnum="2" colname="Option Format"/> + <thead> + <row> <entry>Installation Method</entry> <entry>Option Format</entry> - </row> - </thead> - <tbody> - <row> + </row> + </thead> + <tbody> + <row> <entry> <para> CD or DVD drive @@ -113,8 +149,8 @@ <option>method=<replaceable>cdrom</replaceable></option> </para> </entry> - </row> - <row> + </row> + <row> <entry> <para> Hard Drive @@ -125,8 +161,8 @@ <option>method=<replaceable>hd://device/</replaceable></option> </para> </entry> - </row> - <row> + </row> + <row> <entry> <para> HTTP Server @@ -137,8 +173,8 @@ <option>method=<replaceable>http://server.example.com/directory/</replaceable></option> </para> </entry> - </row> - <row> + </row> + <row> <entry> <para> FTP Server @@ -149,8 +185,8 @@ <option>method=<replaceable>ftp://server.example.com/directory/</replaceable></option> </para> </entry> - </row> - <row> + </row> + <row> <entry> <para> NFS Server @@ -161,37 +197,44 @@ <option>method=<replaceable>nfs:server.example.com:/directory/</replaceable></option> </para> </entry> - </row> - </tbody> - </tgroup> - </table> - <para> - By default, the installation system uses DHCP to automatically - obtain the correct network settings. To manually configure the - network settings yourself, either enter them in the - <guilabel>Configure TCP/IP</guilabel> screen, or at the - <prompt>boot:</prompt> - prompt. You may specify the <option>ip</option> address, - <option>netmask</option>, <option>gateway</option>, and - <option>dns</option> server settings for the installation system - at the prompt. If you specify the network configuration at the - <prompt>boot:</prompt> - prompt, these settings are used for the installation process, and - the <guilabel>Configure TCP/IP</guilabel> screen does not appear. - </para> + </row> + </tbody> + </tgroup> + </table> + </section> - <para> - This example configures the network settings for an installation - system that uses the IP address - <systemitem class="ipaddress">192.168.1.10</systemitem>: - </para> + <section id="sn-boot-options-network"> + <title>Manually Configuring the Network Settings</title> + + <para> + By default, the installation system uses DHCP to automatically + obtain the correct network settings. To manually configure the + network settings yourself, either enter them in the + <guilabel>Configure TCP/IP</guilabel> screen, or at the + <prompt>boot:</prompt> + prompt. You may specify the <option>ip</option> address, + <option>netmask</option>, <option>gateway</option>, and + <option>dns</option> server settings for the installation system + at the prompt. If you specify the network configuration at the + <prompt>boot:</prompt> + prompt, these settings are used for the installation process, + and the <guilabel>Configure TCP/IP</guilabel> screen does not + appear. + </para> + + <para> + This example configures the network settings for an installation + system that uses the IP address + <systemitem class="ipaddress">192.168.1.10</systemitem>: + </para> <screen> <userinput>linux ip=<replaceable>192.168.1.10</replaceable> netmask=<replaceable>255.255.255.0</replaceable> gateway=<replaceable>192.168.1.1</replaceable> dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput> </screen> + </section> </section> <section id="sn-remote-installation"> <title>Enabling Remote Access to the Installation System</title> - + <para> You may access either graphical or text interfaces for the installation system from any other system. Access to a text mode @@ -325,8 +368,9 @@ <prompt>boot:</prompt> prompt: </para> + <screen> -<userinput>linux telnet</userinput> +<userinput>linux text telnet</userinput> </screen> <para> You may then connect to the installation system with the @@ -337,10 +381,16 @@ <screen> <userinput>telnet computer.mydomain.com</userinput> </screen> - <para> - <remark role="FIXME">No password option for telnet ? - </remark> - </para> + <caution> + <title>Telnet Access Requires No Password</title> + + <para> + To ensure the security of the installation process, only use the + <option>telnet</option> option to install systems on networks + with restricted access. + </para> + </caution> + </section> <section id="sn-automating-installation"> <title>Automating the Installation with Kickstart</title> @@ -509,7 +559,7 @@ <section id="sn-bootoptions-driverdisks"> <title>Adding Hardware Support with Driver Disks</title> - + <para> The installation system may load drivers from disks, pen drives, or network servers to configure support for new devices. After @@ -731,7 +781,7 @@ <row> <entry> <para> - Disable Direct Memory Access (DMA) for storage + Disable Direct Memory Access (DMA) for IDE drives </para> </entry> <entry> @@ -845,7 +895,7 @@ <title>Using the Maintenance Boot Modes</title> <section id="sn-memtest"> - <title>Memory (RAM) Testing Mode</title> + <title>Loading the Memory (RAM) Testing Mode</title> <para> Faults in memory modules may cause your system to freeze or @@ -871,51 +921,36 @@ </section> <section id="sn-mode-rescue"> - <title>Booting Your Computer with Rescue Mode</title> + <title>Booting Your Computer with the Rescue Mode</title> <para> - You may use the first installation disc to boot a command-line - Linux system, without installing &FED; on the computer. This - rescue system may access the drives on your computer. Rescue - mode enables you to use the utilities and functions of a running - system to modify or repair an installed system. + You may boot a command-line Linux system from either a rescue + disc or the first installation disc, without installing &FED; on + the computer. This enables you to use the utilities and + functions of a running Linux system to modify or repair an + installed system. </para> <para> - To load the rescue mode, enter: + The rescue disc starts the rescue mode system by default. To + load the rescue system with the first installation disc, enter: </para> <screen> <userinput>linux rescue</userinput> </screen> <para> Specify the language, keyboard layout and network settings for - the rescue system with the screens that follow. - </para> - - <para> - <remark role="FIXME">Add a note that the boot and rescue CDs also have this facility. - </remark> - </para> - </section> - </section> </chapter> Index: fedora-install-guide-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.39 retrieving revision 1.40 diff -u -r1.39 -r1.40 --- fedora-install-guide-en.xml 23 Jan 2006 23:24:09 -0000 1.39 +++ fedora-install-guide-en.xml 26 Jan 2006 00:15:39 -0000 1.40 @@ -6,14 +6,14 @@ <!ENTITY DOCNAME "fedora-install-guide"> <!ENTITY DOCLANG "en"> -<!ENTITY DOCVERSION "1.14"> -<!ENTITY DOCDATE "2006-01-23"> +<!ENTITY DOCVERSION "1.15"> +<!ENTITY DOCDATE "2006-01-26"> <!ENTITY DOCID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">  <!ENTITY BUG-NUM "129911"> <!ENTITY FCLOCALVER "5"> -<!ENTITY DOCLOCALVER "1.14">  +<!ENTITY DOCLOCALVER "1.15">  <!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" > <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml"> Index: fedora-install-guide-firstboot-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- fedora-install-guide-firstboot-en.xml 23 Jan 2006 23:24:09 -0000 1.17 +++ fedora-install-guide-firstboot-en.xml 26 Jan 2006 00:15:39 -0000 1.18 @@ -118,18 +118,17 @@ <para> To enable access to other services, enter the required ports in - the <guilabel>Other ports:</guilabel> field. For each port, - specify the port number followed by the connection type, in the - format + the <guilabel>Other ports:</guilabel> field. For each port, you + must specify the port as TCP or UDP, in addition to the port + number. Use the format <userinput><replaceable>portnumber</replaceable>:<replaceable>type</replaceable></userinput>. The majority of services use TCP ports. </para> <para> - For example, to allow other systems to access mail with the - <systemitem class="protocol">IMAP</systemitem> protocol, which may - use both TCP port 143 and TCP port 993, enter <userinput>143:tcp, - 993:tcp</userinput>. + For example, enter <userinput>143:tcp, 993:tcp</userinput> to + allow users to access mail from other systems with the IMAP + protocol, which may use both TCP port 143 and TCP port 993. </para> <para> Index: fedora-install-guide-packageselection-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- fedora-install-guide-packageselection-en.xml 4 Dec 2005 23:15:24 -0000 1.16 +++ fedora-install-guide-packageselection-en.xml 26 Jan 2006 00:15:39 -0000 1.17 @@ -2,147 +2,92 @@ <chapter id="ch-packageselection"> <title>Package Selection</title> - <warning> - <title>Obsolete</title> - - <para> - &FC; &FCLOCALVER; will have a new package selection interface. This - has not been completed for test1. The content in this section will - be replaced after test2. - </para> - </warning> <para> - &FED; uses the installation type to select a set of software - packages for your system. Refer to - <xref linkend="ch-installtypes" - /> for more information. You can - accept this default set of packages, or customize it to fit your - preferences. If you choose the <guilabel>Custom</guilabel> - installation type, &FED; displays the screen for <guilabel>Package - Group Selection</guilabel> automatically. + By default, the &FED; installation process loads a selection of + software that is suitable for a desktop system. This screen enables + you to customize the set of software to match your requirements. + </para> + <para> + &FED; divides included software into + <indexterm> + <primary>package groups</primary> + </indexterm> + <firstterm>package groups</firstterm>. For ease of use, this screen + displays the package groups in six categories: + </para> + <figure id="fig-package-selection"> + <title>Package Group Selection Screen</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="./figs/package-selection.eps" format="EPS"/> + </imageobject> + <imageobject> + <imagedata align="center" fileref="./figs/package-selection.png" format="PNG"/> + </imageobject> + <textobject> + <phrase> + Package group selection screen. + </phrase> + </textobject> + </mediaobject> + </figure> + <para> + To view the package groups for a category, select the category from + the list on the left. The list on the right displays the package + groups for the currently selected category. + </para> + <para> + To specify a package group for installation, select the checkbox + next to the group. The box at the bottom of the screen displays the + details of the package group that is currently highlighted. + <emphasis>None</emphasis> of the packages from a group will be + installed unless the checkbox for that group is selected. </para> + <para> + If you select a package group, &FED; automatically installs the base + and mandatory packages for that group. To change which optional + packages within a selected group will be installed, select the + <guibutton>Optional Packages</guibutton> button under the + description of the group. Change the selection of + <guibutton>Optional Packages</guibutton> by using the checkbox next + to the name of the individual package. + </para> + <figure id="fig-package-selection-details"> + <title>Package Group Details Dialog</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="./figs/package-selection-details.eps" format="EPS"/> + </imageobject> + <imageobject> + <imagedata align="center" fileref="./figs/package-selection-details.png" format="PNG"/> + </imageobject> + <textobject> + <phrase> + Package group details dialog. + </phrase> + </textobject> + </mediaobject> + </figure> <tip> <title>Changing Your Mind</title> <para> - The installation type and packages that you select are not - permanent. After you boot your system, use the - <application>Package Management</application> tool to make + The packages that you select are not permanent. After you boot + your system, use the <application>pirut</application> tool to make different software selections for your system. To run this tool, - from the main menu, select <menuchoice> <guimenu>System</guimenu> - <guisubmenu>Administration</guisubmenu> <guimenuitem>Add/Remove - Applications</guimenuitem> </menuchoice>. + from the main menu, select <menuchoice> + <guimenu>Applications</guimenu> <guisubmenu>System + Tools</guisubmenu> <guimenuitem>Add/Remove Software</guimenuitem> + </menuchoice>. </para> </tip> - <section id="sn-defaultpackages"> - <title>Package Installation Defaults</title> - - <para> - A summary of the default package selection is displayed. - </para> - <figure id="fig-package-default"> - <title>Package Installation Defaults Screen</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="./figs/package-default.eps" format="EPS"/> - </imageobject> - <imageobject> - <imagedata align="center" fileref="./figs/package-default.png" format="PNG"/> - </imageobject> - <textobject> - <phrase> - Package installation defaults screen. - </phrase> - </textobject> - </mediaobject> - </figure> - <para> - To accept the default package selection, select <guilabel>Install - the default software packages</guilabel>. Select - <guilabel>Next</guilabel> to continue, and proceed to - <xref - linkend="ch-abouttoinstall" />. - </para> - - <para> - To view or change the packages, select <guilabel>Customize - software packages to be installed</guilabel>. Select - <guilabel>Next</guilabel> to continue, and proceed to - <xref - linkend="sn-packagegroups" />. - </para> - </section> - <section id="sn-packagegroups"> - <title>Package Group Selection</title> - - <para> - &FC; divides included software into <indexterm> - <primary>package groups</primary> - </indexterm> <firstterm>package groups</firstterm> that make - software selection easier. - </para> - <figure id="fig-package-selection"> - <title>Package Group Selection Screen</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="./figs/package-selection.eps" format="EPS"/> - </imageobject> - <imageobject> - <imagedata align="center" fileref="./figs/package-selection.png" format="PNG"/> - </imageobject> - <textobject> - <phrase> - Package group selection screen. - </phrase> - </textobject> - </mediaobject> - </figure> - <para> - The default groups for the chosen installation type are already - selected. Select or remove any group of packages as desired. - <emphasis>None</emphasis> of the packages from a group will be - installed unless the checkbox next to the group is selected. - </para> - - <para> - To change which packages within a selected group will be - installed, select the <guilabel>Details</guilabel> link next to - the name of the group. &FC; automatically installs <guilabel>Base - Packages</guilabel> of a group if the group is selected. Change - the selection of <guilabel>Optional Packages</guilabel> by using - the checkbox next to the name of the individual package. - </para> - - <para> - &FC; lists with each group the number of packages currently - selected for installation, and the total number of packages within - that group. - </para> - <figure id="fig-package-selection-details"> - <title>Package Group Details Dialog</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="./figs/package-selection-details.eps" format="EPS"/> - </imageobject> - <imageobject> - <imagedata align="center" fileref="./figs/package-selection-details.png" format="PNG"/> - </imageobject> - <textobject> - <phrase> - Package group details dialog. - </phrase> - </textobject> - </mediaobject> - </figure> - </section> <section id="sn-lang-packages"> <title>Additional Language Support</title> <para> Your &FC; system automatically supports the language that you selected at the start of the installation process. To include - support for additional languages, select the packages for those - languages from the <guilabel>Language Support</guilabel> package - group. + support for additional languages, select the package group for + those languages from the <guilabel>Languages</guilabel> category. </para> <warning> @@ -155,50 +100,12 @@ </para> </warning> </section> - <section id="sn-extreme-packagegroups"> - <title><guilabel>Everything</guilabel> or <guilabel>Minimal</guilabel> - Installations</title> - - <para> - Two of the groups under the heading of - <guilabel>Miscellaneous</guilabel> are incompatible with the - others. If you select either of these groups, your other group - selections become invalid. - </para> - - <para> - If you select <guilabel>Everything</guilabel>, &FC; installs - <emphasis>all</emphasis> of the packages provided. Although &FC; - installs many additional network services in this package group, - some are not enabled after installation. This option may be useful - for some testing and development purposes. - </para> - - <caution> - <title>Storage Requirements</title> - - <para> - The <guilabel>Everything</guilabel> installation fills - approximately 6.9Gb of free disk space, and temporarily requires - an additional 175Mb of disk space during the installation - process. Refer to the Release Notes for more information about - storage requirements. - </para> - </caution> - - <para> - The <guilabel>Minimal</guilabel> package group provides only the - essential packages to create a bootable system. This package group - provides no graphical interface. - </para> - - <para> - After you choose the desired packages, select - <guilabel>Next</guilabel> to proceed. &FC; checks your selection, - and automatically adds any extra packages required to use the - software you select. - </para> - </section> + <para> + After you choose the desired packages, select + <guilabel>Next</guilabel> to proceed. &FC; checks your selection, + and automatically adds any extra packages required to use the + software you select. + </para> </chapter>  </titles> <changelog order="newest-first"> + <revision date="2006-01-26" number="1.15" role="doc"> + <author worker="StuartEllis"/> + + <details>Updated Package Selection screen for test2.</details> + </revision> <revision date="2006-01-23" number="1.14" role="doc"> <author worker="StuartEllis"/>  - <details>Updated for FC5 test2.</details> + <details lang="en">Updated for FC5 test2.</details> </revision> <revision date="Tue Jan 17 2006" number="0" role="rpm"> <author worker="megacoder"/>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits January 2006