translation-quick-start-guide rpm-info.xml,1.9,1.10
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22985
Modified Files:
rpm-info.xml
Log Message:
Add Hugo to contributors and copyrights
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- rpm-info.xml 2 Feb 2006 12:49:35 -0000 1.9
+++ rpm-info.xml 2 Feb 2006 13:50:59 -0000 1.10
@@ -6,9 +6,11 @@
<colophon>
<worker surname="Ospina" firstname="Manuel" id="ManuelOspina" email="mospina(a)redhat.com" wholename="Manuel Ospina" initials="MO"/>
<worker firstname="Paul" othername="W." surname="Frields" initials="PWF" email="stickster(a)gmail.com" wholename="Paul W. Frields" id="PaulWFrields"/>
+ <worker id="HugoCisneiros" wholename="Hugo Cisneiros" email="hugo(a)devin.com.br" surname="Cisneiros" firstname="Hugo" initials="HC"/>
</colophon>
<author worker="ManuelOspina"/>
<editor worker="PaulWFrields"/>
+ <translator worker="HugoCisneiros"/>
<license>
<rights>GNU FDL</rights>
<version>1.0</version>
@@ -23,6 +25,10 @@
<year>2006</year>
<holder>Paul W. Frields</holder>
</copyright>
+ <copyright>
+ <year>2006</year>
+ <holder>Hugo Cisneiros</holder>
+ </copyright>
<titles>
<translation lang="en">
<title>Translation Quick Start Guide</title>
18 years, 3 months
translation-quick-start-guide rpm-info.xml,1.8,1.9
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20344
Modified Files:
rpm-info.xml
Log Message:
Push version to 0.2.2.1; need translations of details and doc check
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- rpm-info.xml 30 Jan 2006 20:31:58 -0000 1.8
+++ rpm-info.xml 2 Feb 2006 12:49:35 -0000 1.9
@@ -38,6 +38,14 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-02-02" number="0.2.2.1" role="doc">
+ <author worker="PaulWFrields"/>
+ <details lang="en">Fix speling (#179717)</details>
+ </revision>
+ <revision date="2006-02-01" number="0.2.2" role="doc">
+ <author worker="PaulWFrields"/>
+ <details lang="en">Add entity for bug reporting</details>
+ </revision>
<revision date="2006-01-30" number="0.2.1" role="doc">
<author worker="PaulWFrields"/>
<details lang="en">Fix hostname error</details>
18 years, 3 months
translation-quick-start-guide translation-quick-start-it.xml, 1.3, 1.4
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20275
Modified Files:
translation-quick-start-it.xml
Log Message:
Fix chmod error in Italian instructions
Index: translation-quick-start-it.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- translation-quick-start-it.xml 30 Jan 2006 18:37:23 -0000 1.3
+++ translation-quick-start-it.xml 2 Feb 2006 12:48:23 -0000 1.4
@@ -101,7 +101,7 @@
<!-- private key. -->
<screen>
-<command>chmod 755 ~/.ssh</command><!-- SEE ABOVE... <command>chmod 644 ~/.ssh/authorized_keys</command> -->
+<command>chmod 700 ~/.ssh</command><!-- SEE ABOVE... <command>chmod 644 ~/.ssh/authorized_keys</command> -->
</screen>
</step>
@@ -453,7 +453,7 @@
<important>
<title>Evitare conflitti di traduzione</title>
<para>
- Sei pregato di avvisare la comunit�� attraverso la fedora-doc-list e
+ Sei pregato di avvisare la comunit�� attraverso la fedora-docs-list e
fedora-trans-<replaceable>locale</replaceable> che stai
modificando il <filename>Makefile</filename>. Informa la
comunit�� che stai lavorando alla traduzione del
18 years, 3 months
translation-quick-start-guide translation-quick-start-en.xml, 1.10, 1.11
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20174
Modified Files:
translation-quick-start-en.xml
Log Message:
Fix speling (#179717)
Index: translation-quick-start-en.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-en.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- translation-quick-start-en.xml 1 Feb 2006 17:54:42 -0000 1.10
+++ translation-quick-start-en.xml 2 Feb 2006 12:44:19 -0000 1.11
@@ -7,8 +7,8 @@
%FEDORA-ENTITIES-EN;
<!ENTITY DOCNAME "translation-quick-start-guide">
- <!ENTITY DOCVERSION "0.2.2">
- <!ENTITY DOCDATE "2006-02-01">
+ <!ENTITY DOCVERSION "0.2.2.1">
+ <!ENTITY DOCDATE "2006-02-02">
<!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)">
<!ENTITY FCLOCALVER "4">
@@ -455,7 +455,7 @@
<important>
<title>Avoid Translation Conflicts</title>
<para>
- Please advise the community through fedora-doc-list and
+ Please advise the community through fedora-docs-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
18 years, 3 months
docs-common/common bugreporting-pt_BR.xml, NONE, 1.1 fedora-entities-pt_BR.ent, NONE, 1.1
by fedora-docs-commits＠redhat.com
Author: eitch
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20037
Added Files:
bugreporting-pt_BR.xml fedora-entities-pt_BR.ent
Log Message:
added brazilian portuguese translation and entities
--- NEW FILE bugreporting-pt_BR.xml ---
<tip>
<title>Relatando Erros de Documento</title>
<para>
Para relatar erros ou omiss��es neste documento, preencha um relato de bug no
&BZ; em &BZ-URL;. Quando voc�� for preencher seu bug, selecione "&BZ-PROD;"
como seu <systemitem>Produto</systemitem>, e selecione o t��tulo deste
documento como o <systemitem>Component</systemitem>. As vers��o deste
documento �� &DOCID;.
</para>
<para>
Os mantenedores deste documento ir��o automaticamente receber seu relato de
bug. Em nome de toda a comunidade &FED;, obrigado por ajudar-nos a fazer
melhoramentos.
</para>
</tip>
--- NEW FILE fedora-entities-pt_BR.ent ---
<!--
These common entities are useful shorthand
terms and names, which may be subject to
change at anytime. This is an important
value the entity provides, a single location
to update terms and common names.
-->
<!-- *************** Fedora common entities *************** -->
<!ENTITY FED "Fedora"> <!-- Generic root term -->
<!ENTITY CORE "Core"> <!-- Generic root term -->
<!ENTITY FC "&FED; &CORE;"> <!-- Generic main project name -->
<!ENTITY DISTRO "&FC;"> <!-- Legacy entity -->
<!ENTITY FCX "FC"> <!-- Short project name -->
<!ENTITY FP "Projeto &FED;"> <!-- Generic overall project name -->
<!ENTITY FDP "Projeto de Documenta����o do &FED;"> <!-- Generic docs project name -->
<!ENTITY FDPX "Projeto &FED; Docs"> <!-- Short docs project name -->
<!ENTITY EX "Extras"> <!-- cf. Core -->
<!ENTITY FEX "&FED; &EX;"> <!-- cf. Fedora Core -->
<!ENTITY FP-URL "<ulink url='http://fedora.redhat.com/'>http://fedora.redhat.com/</ulink>"> <!-- Fedora Project URL -->
<!ENTITY FDP-URL "<ulink url='http://fedora.redhat.com/projects/docs/'>http://fedora.redhat.com/projects/docs/</ulink>"> <!-- Fedora Docs Project URL -->
<!ENTITY FDPDOCS-URL "<ulink url='http://fedora.redhat.com/docs/'>http://fedora.redhat.com/docs/</ulink>"> <!-- Fedora Documentation (repository) URL -->
<!ENTITY BZ "Bugzilla"> <!-- Bugzilla -->
<!ENTITY BZ-URL "<ulink url='http://bugzilla.redhat.com/'>http://bugzilla.redhat.com/</ulink>"> <!-- Bugzilla URL -->
<!ENTITY BZ-PROD "&FED; Documentation"> <!-- Bugzilla product for Fedora docs -->
<!-- *************** Fedora version numbers *************** -->
<!ENTITY FCVER "4"> <!-- Current release version of main project -->
<!ENTITY TESTVER "test2"> <!-- Current test number of main project -->
<!ENTITY FCTESTVER "5 &TESTVER;"> <!-- Current test version of main project -->
<!-- ************** other common names *********** -->
<!ENTITY RH "Red Hat"> <!-- The generic term "Red Hat" -->
<!ENTITY FORMAL-RHI "&RH;, Inc."> <!-- The generic term "Red Hat, Inc. -->
<!ENTITY RHL "&RH; Linux"> <!-- The generic term "Red Hat Linux" -->
<!ENTITY RHN "&RH; Network"> <!-- The generic term "Red Hat Network" -->
<!ENTITY RHEL "&RH; Enterprise Linux"> <!-- The generic term "Red Hat Enterprise Linux" -->
<!-- ************** technology terms *********** -->
<!ENTITY SEL "SELinux"> <!-- Generic technology term -->
<!-- ************** common doc files *********** -->
<!ENTITY LEGALNOTICE SYSTEM "./legalnotice-pt_BR.xml">
<!ENTITY LEGALNOTICE-CONTENT SYSTEM "./legalnotice-content-pt_BR.xml">
<!ENTITY LEGALNOTICE-OPL SYSTEM "./legalnotice-opl-pt_BR.xml">
<!ENTITY LEGALNOTICE-OPL-CONTENT SYSTEM "./opl.xml">
<!ENTITY LEGALNOTICE-RELNOTES SYSTEM "./legalnotice-relnotes-pt_BR.xml">
<!ENTITY LEGALNOTICE-SECTION SYSTEM "./legalnotice-section-pt_BR.xml">
<!ENTITY BUG-REPORTING SYSTEM "./bugreporting-pt_BR.xml">
<!-- ************** common applications? *********** -->
<!-- ************** required by build scripts *********** -->
<!ENTITY PROJECT "&FP;">
<!-- ************** tutorial titles ********** -->
<!ENTITY IG "Installation Guide">
<!ENTITY DOCG "Documentation Guide">
<!-- ************** tutorial URLs *********** -->
<!ENTITY IG-URL "<ulink url='http://fedora.redhat.com/docs/fedora-install-guide-en/'/>">
<!ENTITY DOCG-URL "<ulink url='http://fedora.redhat.com/participate/documentation-guide/'/>">
<!-- ************** status notices ************* -->
<!ENTITY DRAFTNOTICE SYSTEM "./draftnotice-pt_BR.xml">
<!ENTITY LEGACYNOTICE SYSTEM "./legacynotice-pt_BR.xml">
<!ENTITY OBSOLETENOTICE SYSTEM "./obsoletenotice-pt_BR.xml">
<!ENTITY DEPRECATEDNOTICE SYSTEM "./deprecatednotice-pt_BR.xml">
18 years, 3 months
docs-common/images watermark-pt_BR.png, NONE, 1.1 watermark-pt_BR.svg, NONE, 1.1 Makefile, 1.7, 1.8
by fedora-docs-commits＠redhat.com
Author: eitch
Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20006
Modified Files:
Makefile
Added Files:
watermark-pt_BR.png watermark-pt_BR.svg
Log Message:
added brazilian portuguese images
--- NEW FILE watermark-pt_BR.svg ---
<?xml version="1.0"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"[
<!ENTITY bgColor "rgb( 200, 200, 200 )" >
<!ENTITY fgColor "rgb( 255, 100, 100 )" >
]>
<svg viewBox="0 0 1023 767" xmlns="http://www.w3.org/2000/svg" version="1.1">
<title>Fedora Doc Project Watermark</title>
<desc>The word DRAFT rendered in grey at 45 degrees</desc>
<g fill="&bgColor;" font-family="Helvetica" font-size="1in" stroke="&bgColor;" stroke-width="10" text-anchor="start" transform="translate( 1, 1 )">
<g transform="translate( 512, 384 ) rotate( -45 )">
<text font-stretch="wider" text-anchor="middle" x="0" y="0">RASCUNHO</text>
<text fill="&fgColor;" font-size="0.6in" font-stretch="wider" font-variant="small-caps" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">N��O �� PARA REFER��NCIA</text>
</g>
</g>
</svg>
Index: Makefile
===================================================================
RCS file: /cvs/docs/docs-common/images/Makefile,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Makefile 11 Jan 2006 06:14:40 -0000 1.7
+++ Makefile 2 Feb 2006 12:20:08 -0000 1.8
@@ -7,8 +7,8 @@
${RSVG} ${RSVGOPTS} $< $@
SVGFILES=watermark-de.svg watermark-en.svg watermark-es.svg \
- watermark-it.svg watermark-ja_JP.svg watermark-ru.svg \
- watermark-zh_CN.svg
+ watermark-it.svg watermark-ja_JP.svg watermark-pt_BR.svg \
+ watermark-ru.svg watermark-zh_CN.svg
PNGFILES=${SVGFILES:.svg=.png}
all: ${PNGFILES}
18 years, 3 months
translation-quick-start-guide Makefile,1.4,1.5
by fedora-docs-commits＠redhat.com
Author: eitch
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19894
Modified Files:
Makefile
Log Message:
added brazilian portuguese translation
Index: Makefile
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/Makefile,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Makefile 26 Jan 2006 06:10:31 -0000 1.4
+++ Makefile 2 Feb 2006 12:12:24 -0000 1.5
@@ -8,7 +8,7 @@
# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-LANGUAGES = en it
+LANGUAGES = en it pt_BR
DOCBASE = translation-quick-start
XMLEXTRAFILES-en =
18 years, 3 months
translation-quick-start-guide translation-quick-start-pt_BR.xml, NONE, 1.1
by fedora-docs-commits＠redhat.com
Author: eitch
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19850
Added Files:
translation-quick-start-pt_BR.xml
Log Message:
added brazilian portuguese translation
--- NEW FILE translation-quick-start-pt_BR.xml ---
<!-- $Id: -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-PT_BR SYSTEM
"../docs-common/common/fedora-entities-pt_BR.ent">
%FEDORA-ENTITIES-PT_BR;
<!ENTITY DOCNAME "translation-quick-start-guide">
<!ENTITY DOCVERSION "0.2.1">
<!ENTITY DOCDATE "2006-01-30">
<!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)">
<!ENTITY FCLOCALVER "4">
<!ENTITY FDP-INFO SYSTEM "fdp-info-pt_BR.xml" >
]>
<article id="translation-quickstart-guide" lang="pt_BR">
&FDP-INFO;
<section id="sn-intro">
<title>Introdu����o</title>
<para>
Este guia apresenta uma s��rie de instru����es r��pidas, simples, e em
passo-a-passo para traduzir programas e documentos do &FP;. Se voc�� est��
interessado em entender melhor todo o processo de tradu����o, veja o
guia de Tradu����o ou o manual da ferramenta espec��fica de tradu����o.
</para>
</section>
<section id="sn_accounts">
<title>Contas e Inscri����es</title>
<para>
Para participar no &FP; como um tradutor voc�� precisa de uma conta. Voc��
pode se inscrever por uma conta em <ulink
url="http://i18n.redhat.com/cgi-bin/i18n-signup/"/>. Voc�� precisar��
fornecer um nome de usu��rio, um endere��o de e-mail, uma l��ngua alvo
— provavelmente sua l��ngua nativa — e a parte p��blica da sua
chave SSH.
</para>
<para>
Se voc�� ainda n��o tem uma chave SSH, voc�� pode gerar uma usando os
seguintes passos:
</para>
<procedure>
<step>
<para>
Digite em uma linha de comando:
</para>
<screen>
<command>ssh-keygen -t dsa</command>
</screen>
<para>
Aceite as localidades padr��es
(<filename>~/.ssh/id_dsa</filename>) e entre com uma frase-senha.
</para>
<caution>
<title>N��o se esque��a da sua Frase-senha!</title>
<para>
Voc�� precisar�� de sua frase-senha para acessar o reposit��rio CVS.
Ela n��o pode ser recuperada se voc�� esquec��-la.
</para>
</caution>
</step>
<!-- Are you sure this next step is necessary? My understanding is that -->
<!-- this step would only be useful for authorizing you to SSH in from -->
<!-- another host with your private key.
<step>
<para>
Copy the key to the appropiate file:
</para>
<screen>
<command>cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys</command>
</screen>
</step>
-->
<step>
<para>
Mude a permiss��o da sua chave e seu diret��rio
<filename>.ssh</filename>:
</para>
<!-- Why is this permission 755? The 700 mode is usually recommended -->
<!-- for ~/.ssh/ for extra protection, since it does house an SSH -->
<!-- private key. -->
<screen>
<command>chmod 700 ~/.ssh</command><!-- SEE ABOVE... <command>chmod 644 ~/.ssh/authorized_keys</command> -->
</screen>
</step>
<step>
<para>
Copie e cole a sua chave SSH no espa��o fornecido para que a inscri����o
de sua conta possa ser completada.
</para>
</step>
</procedure>
<para>
H�� tamb��m duas listas onde voc�� pode discutir sobre casos de tradu����es. A
primeira �� a <firstterm>fedora-trans-list</firstterm>, uma lista gen��rica
para discutir problemas que afetam todas as l��nguas. V�� �� <ulink
url="http://www.redhat.com/archives/fedora-trans-list"/> para mais
informa����es. A segunda �� uma lista de l��nguas espec��ficas, como a
<firstterm>fedora-trans-es</firstterm> para tradutores de Espanhol, para
discutir casos que afetam apenas esta comunidade individual de tradutores.
</para>
<tip>
<title>Problemas Gerais de Documenta����o</title>
<para>
Voc�� tamb��m pode achar ��til se inscrever na
<firstterm>fedora-docs-list</firstterm> para ficar informado sobre
problemas gerais de documenta����o.
</para>
</tip>
</section>
<section id="sn_translating_software">
<title>Traduzindo Programas</title>
<para>
A parte que pode ser traduzida de um programa est�� dispon��vel em um ou
mais arquivos <filename>po</filename>. O &FP; armazena estes arquivos em
um reposit��rio CVS dentro do diret��rio <filename>translate/</filename>.
Uma vez que sua conta tenha sido aprovada, fa��a download deste diret��rio
digitando o seguinte em uma linha de comando:
</para>
<screen>
<command>export CVS_RSH=ssh</command>
<command>export CVSROOT=:ext:<replaceable>usuario</replaceable>@i18n.redhat.com:/usr/local/CVS</command>
<command>cvs -z9 co translate/</command>
</screen>
<para>
Estes comandos fazem download de todos os m��dulos e arquivos
<filename>.po</filename> para a sua m��quina seguindo a mesma hierarquia do
reposit��rio. Cada diret��rio cont��m um arquivo <filename>.pot</filename>,
como por exemplo o <filename>anaconda.pot</filename>, e arquivos
<filename>.po</filename> para cada l��ngua, como por exemplo
<filename>zh_CN.po</filename>, <filename>de.po</filename>, e por a�� vai.
</para>
<para>
Voc�� pode verificar o status das tradu����es em <ulink
url="http://i18n.redhat.com/cgi-bin/i18n-status"/>. Escolha sua l��ngua nos
menus ou verifique o status geral. Selecione um pacote para ver o
mantenedor e o nome do ��ltimo tradutor para este m��dulo. Se voc�� quiser
traduzir um m��dulo, fa��a contato com sua lista de l��ngua-espec��fica e
deixe sua comunidade sabendo que voc�� est�� trabalhando naquele m��dulo.
Depois disso, selecione <literal>take</literal> na p��gina de status. O
m��dulo ent��o �� associado �� voc��. No di��logo de senha, digite a que voc��
recebeu via e-mail quando se inscreveu para sua conta.
</para>
<para>
Voc�� agora pode come��ar a traduzir.
</para>
<section id="sn-translating-strings">
<title>Traduzindo Strings</title>
<procedure>
<step>
<para>
Mude de diret��rio para o local do pacote que voc�� tomou conta.
</para>
<screen>
<command>cd ~/translate/<replaceable>nome_do_pacote</replaceable></command>
</screen>
</step>
<step>
<para>
Atualize os arquivos com o seguinte comando:
</para>
<screen>
<command>cvs up</command>
</screen>
</step>
<step>
<para>
Traduza o arquivo <filename>.po</filename> da sua l��ngua com um
editor de arquivos <filename>.po</filename> como por exemplo o
<application>KBabel</application> ou o
<application>gtranslator</application>. Por exemplo, para abrir o
arquivo <filename>.po</filename> do Espanhol no
<application>KBabel</application>, digite:
</para>
<screen>
<command>kbabel es.po</command>
</screen>
</step>
<step>
<para>
Quando voc�� acabar o seu trabalho, execute um commit nas suas
mudan��as de volta para o reposit��rio:
</para>
<screen>
<command>cvs commit -m '<replaceable>comentarios</replaceable>' <replaceable>lang</replaceable>.po</command>
</screen>
</step>
<step>
<para>
Clique no link de <literal>release</literal> na p��gina de status do
m��dulo para liber��-lo com o objetivo de outras pessoas poderem
trabalhar nele.
</para>
</step>
</procedure>
</section>
<section id="sn-proofreading">
<title>Verifica����o</title>
<para>
Se voc�� quiser verificar a sua tradu����o como parte do programa, siga
estes passos:
</para>
<procedure>
<step>
<para>
V�� ao diret��rio do pacote que voc�� quer verificar:
</para>
<screen>
<command>cd ~/translate/<replaceable>nome_do_pacote</replaceable></command>
</screen>
</step>
<step>
<para>
Converta o arquivo <filename>.po</filename> em um arquivo
<filename>.mo</filename> com o comando <command>msgfmt</command>:
</para>
<screen>
<command>msgfmt <replaceable>lang</replaceable>.po</command>
</screen>
</step>
<step>
<para>
Sobrescreva o arquivo <filename>.mo</filename> existente no
diret��rio
<filename>/usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</filename>.
Primeiro, fa��a backup do arquivo j�� existente:
</para>
<screen>
<command>cp /usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/<replaceable>nome_do_pacote</replaceable>.mo<replaceable>nome_do_pacote</replaceable>.mo-backup</command>
<command>mv <replaceable>nome_do_pacote</replaceable>.mo /usr/share/locale/<replaceable>lang</replaceable>/LC_MESSAGES/</command>
</screen>
</step>
<step>
<para>
Verifique o pacote com as strings traduzidas como parte da
aplica����o:
</para>
<screen>
<command>LANG=<replaceable>lang</replaceable> rpm -qi <replaceable>nome_do_pacote</replaceable></command>
</screen>
</step>
</procedure>
<para>
A aplica����o associada ao pacote traduzido ir�� rodar com as strings
traduzidas.
</para>
</section>
</section>
<section id="sn_translating_docs">
<title>Traduzindo Documenta����o</title>
<para>
A documenta����o do Fedora �� tamb��m armazenada no reposit��rio CVS dentro do
diret��rio <filename>docs/</filename>.
</para>
<section id="sn-downloading-docs">
<title>Fazendo Download da Documenta����o</title>
<para>
O processo de download da documenta����o �� parecida com a de fazer
download dos arquivos <filename>.po</filename>:
</para>
<screen>
<command>export CVSROOT=:ext:<replaceable>usuario</replaceable>@cvs.fedora.redhat.com:/cvs/docs</command>
<command>cvs co docs</command>
</screen>
<para>
Este passo faz download de todos os documentos atuais no diret��rio. Para
fazer download de apenas um ��nico documento para tradu����o, liste os
m��dulos atuais no reposit��rio e ent��o pegue apenas o m��dulo que quer.
Voc�� tamb��m precisar�� pegar o m��dulo <filename>docs-common</filename>
para poder verificar a validade dos documentos para constru����o.
</para>
<screen>
<command>cvs co -c</command>
<command>cvs co example-tutorial docs-common</command>
</screen>
<para>
Os documentos s��o escritos no formato DocBook XML e nomeados de acordo
com o locale da l��ngua espec��fica, como por exemplo
<filename>example-tutorial-en.xml</filename>. Se voc�� planeja traduzir
diretamente do arquivo XML original, voc�� dever�� criar um documento para
a sua l��ngua:
</para>
<screen>
<command>cp example-tutorial-en.xml example-tutorial-<replaceable>es</replaceable>.xml</command>
</screen>
<para>
Depois disto voc�� pode trabalhar na nova c��pia.
</para>
</section>
<section id="sn-translating-with-apps">
<title>Usando Aplica����es de Tradu����o</title>
<para>
Voc�� pode tamb��m converter os arquivos XML em arquivos
<filename>.po</filename> e trabalhar com um editor de arquivos
<filename>.po</filename> como o <application>KBabel</application> ou o
<application>gtranslator</application>. Para fazer isso, siga os
seguintes passos:
</para>
<procedure>
<step>
<para>
Em um terminal, v�� para o diret��rio do documento que voc�� deseja
traduzir:
</para>
<screen>
<command>cd ~/docs/example-tutorial</command>
</screen>
</step>
<step>
<para>
Extraia as strings traduz��veis com o comando
<command>xml2pot</command>:
</para>
<screen>
<command>xml2pot example-tutorial-en.xml > <replaceable>lang</replaceable>.po</command>
</screen>
</step>
<step>
<para>
Agora voc�� pode traduzir o arquivo usando a mesma aplica����o usada
para traduzir programas:
</para>
<screen>
<command>kbabel <replaceable>lang</replaceable>.po</command>
</screen>
</step>
<step>
<para>
Quando acabar, voc�� precisa converter o arquivo
<filename>.po</filename> traduzido para o arquivo
<filename>.xml</filename> na l��ngua alvo com o comando
<command>po2xml</command>:
</para>
<screen>
<command>po2xml example-tutorial-en.xml <replaceable>lang</replaceable>.po > example-tutorial-<replaceable>lang</replaceable>.xml</command>
</screen>
</step>
<step>
<para>
O filtro <command>xml2pot</command> n��o inclue as entidades do
arquivo <filename>.po</filename>. Voc�� precisa mudar a l��ngua no
documento. Localize no topo do documento uma linha parecida com
esta:
</para>
<screen>
<computeroutput><article id="example-tutorial" lang="en"></computeroutput>
</screen>
</step>
<step>
<para>Mude o atributo para a sua l��ngua:</para>
<screen>
<computeroutput><article id="example-tutorial" lang="<userinput><replaceable>es</replaceable></userinput>"></computeroutput>
</screen>
</step>
<step>
<para>
Quando o arquivo traduzido estiver pronto, adicione-o ao
reposit��rio:
</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>
</step>
</procedure>
</section>
<section id="sn-changing-makefile">
<title>Mudando o arquivo <filename>Makefile</filename></title>
<para>
Voc�� pode precisar mudar o arquivo <filename>Makefile</filename> para
que o documento possa ser contru��do nos formatos HTML e PDF.
</para>
<important>
<title>Evite Conflitos de Tradu����o</title>
<para>
Por favor avise a comunidade atrav��s das listas fedora-docs-list e
fedora-trans-<replaceable>locale</replaceable> que voc�� est��
modificando arquivo <filename>Makefile</filename>. Informe a
comunidade que voc�� est�� trabalhando na tradu����o deste documento antes
de come��ar, para evitar conflitos entre tradutores trabalhando em um
mesmo arquivo.
</para>
</important>
<procedure>
<step>
<para>
Em um editor de texto de sua prefer��ncia, abra o arquivo
<filename>Makefile</filename>.
</para>
<screen>
<command>vi Makefile</command>
</screen>
</step>
<step>
<para>
Adicione o locale da nova tradu����o depois das outras l��nguas como no
seguinte exemplo:
</para>
<screen>
<computeroutput>LANGUAGES = en de <userinput><replaceable>lang</replaceable></userinput></computeroutput>
</screen>
</step>
<step>
<para>
Fa��a um commit do <filename>Makefile</filename>.
</para>
<screen>
<command>cvs commit -m '<replaceable>Qualquer coment��rio</replaceable>' Makefile</command>
</screen>
</step>
<step>
<para>
Ent��o, voc�� pode construir o documento em sua l��ngua digitando:
</para>
<screen>
<command>make html-<replaceable>lang</replaceable></command>
</screen>
</step>
</procedure>
</section>
</section>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
18 years, 3 months
install-guide fedora-install-guide-acknowledgements-en.xml, 1.4, 1.5 fedora-install-guide-adminoptions-en.xml, 1.9, 1.10 fedora-install-guide-bootloader-en.xml, 1.14, 1.15 fedora-install-guide-diskpartitioning-en.xml, 1.16, 1.17 fedora-install-guide-en.xml, 1.41, 1.42 fedora-install-guide-packageselection-en.xml, 1.18, 1.19 rpm-info.xml, 1.6, 1.7
by fedora-docs-commits＠redhat.com
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21748
Modified Files:
fedora-install-guide-acknowledgements-en.xml
fedora-install-guide-adminoptions-en.xml
fedora-install-guide-bootloader-en.xml
fedora-install-guide-diskpartitioning-en.xml
fedora-install-guide-en.xml
fedora-install-guide-packageselection-en.xml rpm-info.xml
Log Message:
- Added section on new remote logging feature.
- Amended Disk Partitioning section to address hardware RAID vs. software RAID.
- Amended Boot Loader section to address bug #173582.
- Note: Package selection is complete for test2, but needs further updates to match post-test2 development.
Index: fedora-install-guide-acknowledgements-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-acknowledgements-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-acknowledgements-en.xml 15 May 2005 18:39:09 -0000 1.4
+++ fedora-install-guide-acknowledgements-en.xml 2 Feb 2006 00:12:55 -0000 1.5
@@ -2,12 +2,11 @@
<chapter id="ch-acknowledgements">
<title>Acknowledgements</title>
-
<para>
- Many useful comments and suggestions were provided by Rahul
- Sundaram and the Anaconda team.
+ Many useful comments and suggestions were provided by Rahul Sundaram
+ and the Anaconda team. David Neimi and Debra Deutsch contributed
+ additional information on boot loader and RAID configurations.
</para>
-
</chapter>
<!--
Index: fedora-install-guide-adminoptions-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-adminoptions-en.xml 29 Jan 2006 20:37:55 -0000 1.9
+++ fedora-install-guide-adminoptions-en.xml 2 Feb 2006 00:12:55 -0000 1.10
@@ -73,11 +73,17 @@
<para>
To set the language for both the installation process and the
final system, 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:
+ <option>lang</option> option. Use the <option>keymap</option>
+ option to configure the correct keyboard layout.
+ </para>
+
+ <para>
+ For example, the ISO codes <userinput>el_GR</userinput> and
+ <userinput>gr</userinput> identify the Greek language and the
+ Greek keyboard layout:
</para>
<screen>
-<userinput>linux lang=<replaceable>fr</replaceable></userinput>
+<userinput>linux lang=<replaceable>el_GR</replaceable> keymap=<replaceable>gr</replaceable></userinput>
</screen>
</section>
@@ -416,7 +422,7 @@
<prompt>boot:</prompt>
prompt:
</para>
-<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. Possibly a bug. -->
+<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. This is expected behavior. -->
<screen>
<userinput>linux text telnet</userinput>
</screen>
@@ -438,7 +444,99 @@
with restricted access.
</para>
</caution>
-<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. There is also a "syslog" option to route logging to a remote system. -->
+<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
+ </section>
+ <section id="sn-remote-logging">
+ <title>Logging to a Remote System</title>
+
+ <para>
+ By default, the installation system sends log messages to the
+ console. You may configure the system to log to a remote system
+ that runs a
+ <indexterm>
+ <primary>syslog</primary>
+ </indexterm>
+ <firstterm>syslog</firstterm> service.
+ </para>
+
+ <para>
+ To enable remote logging, specify the IP address of the remote
+ system with the <option>syslog</option> option. For example, to
+ connect to a <command>syslog</command> service on the system
+ <systemitem
+ class="ipaddress">192.168.1.20</systemitem>, enter
+ the following at the
+ <prompt>boot:</prompt>
+ prompt:
+ </para>
+<screen>
+<userinput>linux syslog=<replaceable>192.168.1.20</replaceable></userinput>
+</screen>
+ <para>
+ &FED; uses <command>syslogd</command> to provide a syslog service. The
+ default configuration of <command>syslogd</command> rejects
+ messages from remote systems.
+ </para>
+
+ <caution>
+ <title>Only Enable Remote Syslog Access on Secured Networks</title>
+
+ <para>
+ The <command>syslogd</command> service includes no security
+ measures. &FED; systems that enable remote access to this
+ service may be attacked by sending large quantities of log
+ messages. In addition, crackers may intercept or falsify
+ messages sent to the service.
+ </para>
+ </caution>
+
+ <para>
+ To enable remote systems to send log messages to a &FED; system,
+ edit the file <filename>/etc/sysconfig/syslog</filename>. Add the
+ <option>-r</option> to the <command>SYSLOGD_OPTIONS</command>.
+ </para>
+
+ <example>
+ <title>Syslogd Options Configuration</title>
+<screen>
+<computeroutput><![CDATA[
+SYSLOGD_OPTIONS="-m 0 -r"
+]]></computeroutput>
+</screen>
+ </example>
+
+ <para>
+ You must use <systemitem class="username">root</systemitem>
+ privileges to edit the file
+ <filename>/etc/sysconfig/syslog</filename>.
+ </para>
+
+ <para>
+ Restart the <command>syslogd</command> service to apply the
+ change:
+ </para>
+<screen>
+<userinput>su -c '/sbin/service syslog restart'</userinput>
+</screen>
+ <para>
+ Enter the <systemitem class="username">root</systemitem> password
+ when prompted.
+ </para>
+
+ <note>
+ <title>Firewall Reconfiguration Required</title>
+
+ <para>
+ By default, the syslog service listens on UDP port
+ <systemitem>514</systemitem>. To update the &FED; firewall
+ configuration to permit connections to this port from other
+ systems, choose <menuchoice> <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
+ Level and Firewall</guimenuitem> </menuchoice>, enter
+ <userinput>514:udp</userinput> in the <guilabel>Other
+ ports:</guilabel> field, and select <guilabel>OK</guilabel>.
+ </para>
+ </note>
</section>
<section id="sn-automating-installation">
<title>Automating the Installation with Kickstart</title>
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- fedora-install-guide-bootloader-en.xml 29 Jan 2006 20:37:55 -0000 1.14
+++ fedora-install-guide-bootloader-en.xml 2 Feb 2006 00:12:55 -0000 1.15
@@ -21,7 +21,7 @@
does not recognize Linux partitions, you may not be able to boot
&FC;. Use <application>GRUB</application> as your boot loader to
boot Linux and most other operating systems. Follow the directions
- in this section to install <application>GRUB</application>.
+ in this chapter to install <application>GRUB</application>.
</para>
<warning>
<title>Installing GRUB</title>
@@ -87,6 +87,16 @@
IG. - PWF. -->
</para>
</important>
+
+ <para>
+ You may need to customize the GRUB installation to correctly
+ support some hardware or system configurations. To specify
+ compatibility settings, select <guilabel>Configure advanced boot
+ loader options</guilabel>. This causes a second screen of options
+ to appear when you choose <guibutton>Next</guibutton>.
+ <xref linkend="sn-bootloader-advanced"/> explains the features of
+ the additional screen.
+ </para>
</section>
<section id="sn-bootloader-others">
<title>Booting Additional Operating Systems</title>
@@ -249,17 +259,23 @@
</para>
<para>
- Tto keep your current boot loader in the <abbrev>MBR</abbrev>, use
- the advanced settings to place <application>GRUB</application> in
- the first sector of the partition holding the Linux root file
- system.
+ To keep your current boot loader in the <abbrev>MBR</abbrev> and
+ install GRUB as a secondary boot loader, use the advanced settings
+ to place <application>GRUB</application> in the first sector of
+ the partition holding the Linux root file system.
</para>
<para>
You may also need the advanced options if your
- <abbrev>BIOS</abbrev> enumerates your disk devices differently
- than &FC; expects. On a few systems, &FC; may not configure the
- disk drive geometry for large disks correctly because of a broken
+ <abbrev>BIOS</abbrev> enumerates your drives or RAID arrays
+ differently than &FC; expects. If necessary, use the
+ <guibutton>Change Drive Order</guibutton> dialog to set the order
+ of the devices in &FC; to match your BIOS.
+ </para>
+
+ <para>
+ On a few systems, &FC; may not configure the disk drive geometry
+ for large disks correctly because of limitations within the
<abbrev>BIOS</abbrev>. To work around this problem, mark the
<guibutton>Force LBA32</guibutton> checkbox.
</para>
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- fedora-install-guide-diskpartitioning-en.xml 10 Dec 2005 17:51:38 -0000 1.16
+++ fedora-install-guide-diskpartitioning-en.xml 2 Feb 2006 00:12:55 -0000 1.17
@@ -5,11 +5,30 @@
<para>
&FC; creates and uses several <firstterm>partitions</firstterm> on
the available hard drives. You may customize both the partitions,
- and how the drives on your system are managed. On systems with more
- than one hard drive you may also configure &FC; to operate several
- drives as a group, or array, with RAID. Partitions and RAID arrays
- are explained in <xref linkend="sn-partitioning-general"/>, and
- <xref linkend="sn-disk-druid"/>.
+ and how the drives on your system are managed.
+ <xref linkend="sn-partitioning-general"/> explains drive partitions
+ in more detail.
+ </para>
+ <important>
+ <title>Configuring RAID Devices</title>
+
+ <para>
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>hardware</secondary>
+ </indexterm>
+ <firstterm>RAID</firstterm> facilities enable a group, or array,
+ of drives to act as a single device. Configure any RAID functions
+ provided by your mainboard, or attached controller cards, before
+ you install &FC;. Active RAID arrays appear as one drive.
+ </para>
+ </important>
+<!-- SE: Note that this chapter uses the term "Linux software RAID" to differentiate RAID provided by the kernel from the functions of ATA RAID controllers, which are often also called "software RAID". Unfortunately. -->
+ <para>
+ On systems with more than one hard drive you may configure &FC; to
+ operate several of the drives as a Linux RAID array without
+ requiring any additional hardware. Linux software RAID arrays are
+ explained in <xref linkend="sn-disk-druid"/>.
</para>
<note>
<title>Changing Your Mind</title>
@@ -129,33 +148,39 @@
</para>
<para>
- Data partitions have a <indexterm>
- <primary>mount point</primary>
- </indexterm> <firstterm>mount point</firstterm>. The mount point
- indicates the directory whose contents reside on that partition. A
- partition with no mount point is not accessible by users. Data not
- located on any other partition resides in the
- <filename>/</filename> (or <indexterm>
- <primary>partition</primary>
- <secondary>root</secondary>
- </indexterm> <firstterm>root</firstterm>) partition.
+ Data partitions have a
+ <indexterm>
+ <primary>mount point</primary>
+ </indexterm>
+ <firstterm>mount point</firstterm>. The mount point indicates the
+ directory whose contents reside on that partition. A partition
+ with no mount point is not accessible by users. Data not located
+ on any other partition resides in the <filename>/</filename> (or
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm>
+ <firstterm>root</firstterm>) partition.
</para>
<important>
<title>Root and <filename>/root</filename></title>
<para>
- The <filename>/</filename> (or <indexterm>
- <primary>partition</primary>
- <secondary>root</secondary>
- </indexterm> root) partition is the top of the directory
- structure. The <indexterm>
- <primary>partition</primary>
- <secondary><filename>/root</filename>
- </secondary>
- </indexterm> <filename>/root</filename> (sometimes pronounced
- "slash-root") directory is the home directory of the user
- account for system administration.
+ The <filename>/</filename> (or
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm>
+ root) partition is the top of the directory structure. The
+ <indexterm>
+ <primary>partition</primary>
+ <secondary><filename>/root</filename>
+ </secondary>
+ </indexterm>
+ <filename>/root</filename> (sometimes pronounced "slash-root")
+ directory is the home directory of the user account for system
+ administration.
</para>
</important>
@@ -205,25 +230,31 @@
<title>Partition Types</title>
<para>
- Every partition has a <indexterm>
- <primary>partition</primary>
- <secondary>type</secondary>
- <seealso>file system</seealso>
- </indexterm> <firstterm>partition type</firstterm>, to indicate
- the format of the <indexterm>
- <primary>file system</primary>
- </indexterm> <firstterm>file system</firstterm> on that
- partition. The file system enables Linux to organize, search,
- and retrieve files stored on that partition. Use the <indexterm>
- <primary><systemitem
+ Every partition has a
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>type</secondary>
+ <seealso>file system</seealso>
+ </indexterm>
+ <firstterm>partition type</firstterm>, to indicate the format of
+ the
+ <indexterm>
+ <primary>file system</primary>
+ </indexterm>
+ <firstterm>file system</firstterm> on that partition. The file
+ system enables Linux to organize, search, and retrieve files
+ stored on that partition. Use the
+ <indexterm>
+ <primary><systemitem
class="filesystem">ext3</systemitem>
- </primary>
- <see>file system</see>
- </indexterm><indexterm>
- <primary>file system</primary>
- <secondary
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary
sortas="filesystem"><systemitem>ext3</systemitem>
- </secondary>
+ </secondary>
</indexterm>
<systemitem
class="filesystem"><firstterm>ext3</firstterm></systemitem>
@@ -236,27 +267,32 @@
<section id="sn-partitioning-lvm">
<title>Understanding LVM</title>
<indexterm>
- <primary>LVM</primary>
- <secondary>understanding</secondary>
+ <primary>LVM</primary>
+ <secondary>understanding</secondary>
</indexterm>
<para>
LVM (Logical Volume Management) partitions provide a number of
advantages over standard partitions. LVM partitions are
- formatted as <indexterm>
- <primary>LVM</primary>
- <secondary>physical volume</secondary>
- </indexterm> <firstterm>physical volumes</firstterm>. One or
- more physical volumes are combined to form a <indexterm>
- <primary>LVM</primary>
- <secondary>volume group</secondary>
- </indexterm> <firstterm>volume group</firstterm>. Each volume
- group's total storage is then divided into one or more
+ formatted as
<indexterm>
- <primary>LVM</primary>
- <primary>logical volume</primary>
- </indexterm> <firstterm>logical volumes</firstterm>. The logical
- volumes function much like standard data partitions. They have a
- file system type, such as
+ <primary>LVM</primary>
+ <secondary>physical volume</secondary>
+ </indexterm>
+ <firstterm>physical volumes</firstterm>. One or more physical
+ volumes are combined to form a
+ <indexterm>
+ <primary>LVM</primary>
+ <secondary>volume group</secondary>
+ </indexterm>
+ <firstterm>volume group</firstterm>. Each volume group's total
+ storage is then divided into one or more
+ <indexterm>
+ <primary>LVM</primary>
+ <primary>logical volume</primary>
+ </indexterm>
+ <firstterm>logical volumes</firstterm>. The logical volumes
+ function much like standard data partitions. They have a file
+ system type, such as
<systemitem
class="filesystem">ext3</systemitem>, and a mount
point.
@@ -265,9 +301,9 @@
<para>
An administrator may grow or shrink logical volumes without
destroying data, unlike standard disk partitions. If the
- physical volumes in a volume group are on separate drives then
- administrators may also spread a logical volume across multiple
- disks and RAID arrays.
+ physical volumes in a volume group are on separate drives or
+ RAID arrays then administrators may also spread a logical volume
+ across the storage devices.
</para>
<note>
@@ -319,16 +355,22 @@
<para>
<indexterm>
- <primary>Disk Druid</primary>
- </indexterm> <application><firstterm>Disk
- Druid</firstterm></application> is an interactive program for
- editing disk partitions. Users run it only within the &FC;
- installation system. Disk Druid supports <indexterm>
- <primary>RAID</primary>
- </indexterm> <firstterm>RAID</firstterm> and <indexterm>
- <primary>LVM</primary>
- </indexterm> <firstterm>LVM</firstterm> to provide more extensible
- and reliable data storage.
+ <primary>Disk Druid</primary>
+ </indexterm>
+ <application><firstterm>Disk Druid</firstterm></application> is an
+ interactive program for editing disk partitions. Users run it only
+ within the &FC; installation system. Disk Druid enables you to
+ configure
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>Linux software</secondary>
+ </indexterm>
+ Linux software RAID and
+ <indexterm>
+ <primary>LVM</primary>
+ </indexterm>
+ <firstterm>LVM</firstterm> to provide more extensible and reliable
+ data storage.
</para>
<figure id="fig-disk-setup">
<title>Disk Setup Screen</title>
@@ -354,13 +396,15 @@
<term><guilabel>New</guilabel></term>
<listitem>
<para>
- Select this option to add a partition <indexterm>
- <primary>partition</primary>
- <secondary>adding</secondary>
- </indexterm> or LVM physical volume to the disk. In the
- <guilabel>Add partition</guilabel> dialog, choose a mount
- point and a partition type. If you have more than one disk
- on the system, choose which disks the partition may inhabit.
+ Select this option to add a partition
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>adding</secondary>
+ </indexterm>
+ or LVM physical volume to the disk. In the <guilabel>Add
+ partition</guilabel> dialog, choose a mount point and a
+ partition type. If you have more than one disk on the
+ system, choose which disks the partition may inhabit.
Indicate a size in megabytes for the partition.
</para>
<important>
@@ -368,9 +412,10 @@
<para>
<indexterm>
- <primary>partition</primary>
- <secondary>illegal</secondary>
- </indexterm> The <filename>/bin/</filename>,
+ <primary>partition</primary>
+ <secondary>illegal</secondary>
+ </indexterm>
+ The <filename>/bin/</filename>,
<filename>/dev/</filename>, <filename>/etc/</filename>,
<filename>/lib/</filename>, <filename>/proc/</filename>,
<filename>/root/</filename>, and
@@ -378,9 +423,10 @@
for separate partitions in <application>Disk
Druid</application>. These directories reside on the
<indexterm>
- <primary>partition</primary>
- <secondary>root</secondary>
- </indexterm> <filename>/</filename> (root) partition.
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm>
+ <filename>/</filename> (root) partition.
</para>
<para>
@@ -445,12 +491,12 @@
<para>
Select this option to edit an existing partition,
<indexterm>
- <primary>partition</primary>
- <secondary>editing</secondary>
- </indexterm> LVM volume group, or an LVM physical volume
- that is not yet part of a volume group. To change the size
- of a LVM physical volume partition, first remove it from any
- volume groups.
+ <primary>partition</primary>
+ <secondary>editing</secondary>
+ </indexterm>
+ LVM volume group, or an LVM physical volume that is not yet
+ part of a volume group. To change the size of a LVM physical
+ volume partition, first remove it from any volume groups.
</para>
<warning>
<title>Removing LVM Physical Volumes</title>
@@ -489,29 +535,32 @@
<para>
You may not label Windows partitions that use the
<indexterm>
- <primary><systemitem
+ <primary><systemitem
class="filesystem">NTFS</systemitem>
- </primary>
- <see>file system</see>
- </indexterm> <indexterm>
- <primary>file system</primary>
- <secondary><systemitem
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary><systemitem
class="filesystem">NTFS</systemitem>
- </secondary>
+ </secondary>
</indexterm>
<systemitem
class="filesystem">NTFS</systemitem> file
system with a mount point in the &FC; installer. You may
- label <indexterm>
- <primary><systemitem
+ label
+ <indexterm>
+ <primary><systemitem
class="filesystem">vfat</systemitem>
- </primary>
- <see>file system</see>
- </indexterm> <indexterm>
- <primary>file system</primary>
- <secondary><systemitem
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary><systemitem
class="filesystem">vfat</systemitem>
- </secondary>
+ </secondary>
</indexterm>
<systemitem
class="filesystem"><firstterm>vfat</firstterm></systemitem>
@@ -534,11 +583,12 @@
installation program allows you to erase or retain data on
specific partitions. If your user data is on a separate
<indexterm>
- <primary>partition</primary>
- <secondary><filename>/home</filename>
- </secondary>
- </indexterm> <filename>/home</filename> partition, you may
- retain that data while erasing system partitions such as
+ <primary>partition</primary>
+ <secondary><filename>/home</filename>
+ </secondary>
+ </indexterm>
+ <filename>/home</filename> partition, you may retain that
+ data while erasing system partitions such as
<filename>/boot</filename>.
</para>
</listitem>
@@ -550,11 +600,12 @@
<para>
Select this option to erase an existing partition
<indexterm>
- <primary>partition</primary>
- <secondary>deleting</secondary>
- </indexterm> or LVM physical volume. To delete an LVM
- physical volume, first delete any volume groups of which
- that physical volume is a member.
+ <primary>partition</primary>
+ <secondary>deleting</secondary>
+ </indexterm>
+ or LVM physical volume. To delete an LVM physical volume,
+ first delete any volume groups of which that physical volume
+ is a member.
</para>
<para>
If you make a mistake, use the <guilabel>Reset</guilabel>
@@ -578,9 +629,11 @@
<term><guilabel>RAID</guilabel></term>
<listitem>
<para>
- Select this button to set up software RAID <indexterm>
- <primary>RAID</primary>
- </indexterm> on your &FED; system.
+ Select this button to set up software RAID
+ <indexterm>
+ <primary>RAID</primary>
+ </indexterm>
+ on your &FED; system.
</para>
<variablelist>
<varlistentry>
@@ -627,11 +680,13 @@
<term><guilabel>LVM</guilabel></term>
<listitem>
<para>
- Select this button to set up LVM <indexterm>
- <primary>LVM</primary>
- </indexterm> on your &FED; system. First create at least one
- partition or software RAID device as an LVM physical volume,
- using the <application>New</application> dialog.
+ Select this button to set up LVM
+ <indexterm>
+ <primary>LVM</primary>
+ </indexterm>
+ on your &FED; system. First create at least one partition or
+ software RAID device as an LVM physical volume, using the
+ <application>New</application> dialog.
</para>
<para>
To assign one or more physical volumes to a volume group,
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- fedora-install-guide-en.xml 29 Jan 2006 20:37:55 -0000 1.41
+++ fedora-install-guide-en.xml 2 Feb 2006 00:12:55 -0000 1.42
@@ -6,14 +6,14 @@
<!ENTITY DOCNAME "fedora-install-guide">
<!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.16">
-<!ENTITY DOCDATE "2006-01-29">
+<!ENTITY DOCVERSION "1.17">
+<!ENTITY DOCDATE "2006-02-02">
<!ENTITY DOCID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "129911">
<!ENTITY FCLOCALVER "5">
-<!ENTITY DOCLOCALVER "1.16"> <!-- what's this for again? -->
+<!ENTITY DOCLOCALVER "1.17"> <!-- what's this for again? -->
<!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" >
<!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">
Index: fedora-install-guide-packageselection-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- fedora-install-guide-packageselection-en.xml 29 Jan 2006 20:37:55 -0000 1.18
+++ fedora-install-guide-packageselection-en.xml 2 Feb 2006 00:12:55 -0000 1.19
@@ -5,8 +5,9 @@
<remark role="FIXME">TEXT SUBJECT TO CHANGE: The package selection screen is still being developed.</remark>
<para>
By default, the &FED; installation process loads a selection of
- software that is suitable for a desktop system. The package selection screen enables
- you to customize the set of software to match your requirements.
+ software that is suitable for a desktop system. The package
+ selection screen enables you to customize the set of software to
+ match your requirements.
</para>
<para>
&FED; divides included software into
@@ -81,13 +82,59 @@
</menuchoice>.
</para>
</tip>
- <section id="sn-mandatory-packages">
- <title>Core Software</title>
- <para>
- <remark role="FIXME">Mention some base stuff that is part of every &FC; system: SMTP, SSH, CUPS, NFS, Python and <command>yum</command>...</remark>
- </para>
- </section>
+ <section id="sn-mandatory-services">
+ <title>Core Network Services</title>
+
+ <para>
+ All Fedora Core installations run the following network services:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ email through SMTP (Simple Mail Transfer Protocol)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network file sharing through NFS (Network File System)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ remote access through SSH (Secure SHell)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The default installation also includes:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ printing through CUPS (Common UNIX Printing System)
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Some automated processes on your Fedora system use the email
+ service to send reports and messages to the system administrator.
+ By default, the email and printing services do not accept
+ connections from other systems. Although Fedora connects to NFS
+ services on other systems, the NFS sharing component is disabled
+ by default. You may configure your Fedora system after
+ installation to offer email, NFS, or print services.
+ </para>
+
+ <para>
+ The SSH service is enabled by default. This enables administrators
+ to remotely access systems immediately after the installation
+ process completes.
+ </para>
+ </section>
<section id="sn-lang-packages">
<title>Additional Language Support</title>
@@ -107,13 +154,14 @@
difficult, and not recommended.
</para>
</warning>
+
+ <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>
<!--
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rpm-info.xml 29 Jan 2006 20:37:55 -0000 1.6
+++ rpm-info.xml 2 Feb 2006 00:12:55 -0000 1.7
@@ -28,10 +28,15 @@
<!--PLEASE ADD A TRANSLATION FOR EACH ADDITIONAL LANGUAGE.-->
</titles>
<changelog order="newest-first">
+ <revision date="2006-02-02" number="1.17" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Added section on remote logging.</details>
+ </revision>
<revision date="2006-01-29" number="1.16" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Updated indexing.</details>
+ <details lang="en">Updated indexing.</details>
</revision>
<revision date="2006-01-26" number="1.15" role="doc">
<author worker="StuartEllis"/>
18 years, 3 months
translation-quick-start-guide translation-quick-start-en.xml, 1.9, 1.10
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6028
Modified Files:
translation-quick-start-en.xml
Log Message:
Add bug reporting notice, bump to 0.2.2
Index: translation-quick-start-en.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- translation-quick-start-en.xml 30 Jan 2006 18:37:23 -0000 1.9
+++ translation-quick-start-en.xml 1 Feb 2006 17:54:42 -0000 1.10
@@ -7,8 +7,8 @@
%FEDORA-ENTITIES-EN;
<!ENTITY DOCNAME "translation-quick-start-guide">
- <!ENTITY DOCVERSION "0.2.1">
- <!ENTITY DOCDATE "2006-01-30">
+ <!ENTITY DOCVERSION "0.2.2">
+ <!ENTITY DOCDATE "2006-02-01">
<!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)">
<!ENTITY FCLOCALVER "4">
@@ -32,6 +32,8 @@
tool.
</para>
+ &BUG-REPORTING;
+
</section>
<section id="sn_accounts">
18 years, 3 months