-
- Kickstart File is Automatically Created
-
- The Kickstart file /root/anaconda-ks.cfg
- contains the settings for your system. The &FED; installation
- process automatically creates this file.
-
-
- To install an application to create and edit Kickstart files,
- use the package system-config-kickstart. To
- load this Kickstart file editor, choose
- ApplicationsSystem
- ToolsKickstart.
- Alternatively, you may edit Kickstart files with a text editor.
-
-
-
- You may also write Web applications to generate Kickstart files.
- To use a Web application to provide a Kickstart file, specify
- the URL of the application with the option.
- If you add the option , the request
- also sends HTTP headers to the Web application. Your application
- may use these headers to identify the computer. For example,
- this line sends a request with headers to the application
+ To obtain a Kickstart file from a script or application on a Web
+ server, specify the URL of the application with the
+ option. If you add the option
+ , the request also sends HTTP headers
+ to the Web application. Your application may use these headers
+ to identify the computer. This line sends a request with headers
+ to the application
http://server.example.com/kickstart.cgi:
@@ -471,173 +533,341 @@
- Hardware Compatibility Options
+ Hardware Support
- By default, &FED; detects and configures all of the components
- of your computer. To override the automatic hardware detection,
- use the following options:
+ By default, &FED; attempts to automatically detect and configure
+ support for all of the components of your computer. &FED;
+ supports the majority of hardware in common use with the
+ software drivers that are included with
+ the operating system. To enable a &FED; system to support more
+ devices you may supply additional drivers during the
+ installation process, or at a later time.
-
+
+
+ Adding Hardware Support with Driver Disks
+
+
+ The installation system may load drivers from disks, pen
+ drives, or network servers to configure support for new
+ devices. After the installation is complete, remove any driver
+ disks and store them for later use.
+
+
+
+ Hardware manufacturers may supply driver disks for &FED; with
+ the device, or provide image files to prepare the disks. To
+ obtain the latest drivers, download the correct file from the
+ website of the manufacturer.
+
+
+
+ Driver Disks Supplied as Zipped Files
+
+
+ Driver disk images may be distributed as compressed
+ archives, or zip files. For identification, the names of zip
+ files include the extensions .zip, or
+ .tar.gz. To extract the contents of a
+ zipped file with a &FED; system, choose
+ ApplicationsSystem
+ ToolsArchive
+ Manager.
+
+
+
+
+ To format a disk or pen drive with an image file, use the
+ dd utility. For example, to prepare a
+ diskette with the image file drivers.img,
+ enter this command in a terminal window:
+
+
+ dd if=drivers.img of=/dev/fd0
+
+
+ To use a driver disk in the installation process, specify the
+ option at the
+ boot:
+ prompt:
+
+
+ linux dd
+
+
+ When prompted, select Yes to provide a
+ driver disk. Choose the drive that holds the driver disk from
+ the list on the Driver Disk Source text
+ screen.
+
+
+
+ The installation system may also read drivers from disk images
+ that are held on network servers. Refer to
+ for the supported sources
+ of driver image files.
+
+
+
+
+
+ Overriding Automatic Hardware Detection
+
+
+ For some models of device automatic hardware configuration may
+ fail, or cause instability. In these cases, you may need to
+ disable automatic configuration for that type of device, and
+ take additional steps to manually configure the device after
+ the installation process is complete.
+
+
+ Check the Release Notes
+
+ Refer to the Release Notes for information on known issues
+ with specific devices.
+
+
+
+ To override the automatic hardware detection, use one or more
+ of the following options:
+
+
+
+
Performing a Memory (RAM) Test
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- fedora-install-guide-en.xml 11 Jan 2006 22:40:26 -0000 1.37
+++ fedora-install-guide-en.xml 16 Jan 2006 00:23:00 -0000 1.38
@@ -6,17 +6,19 @@
-
-
+
+
+
-
-
+
+
@@ -40,204 +42,8 @@
]>
-
- &FC; &FCLOCALVER; &IG; - BETA
-
-
- 2006
- &FORMAL-RHI;
- Stuart Ellis
- Paul W. Frields
-
-
-
- Ellis
- Stuart
-
-
- Frields
- Paul
- W.
-
-
- &LEGALNOTICE;
-
-
- 0.6.2
- 2005-04-30
- StuartEllis
- PaulWFrields
-
-
- First commission to CVS, plus very minor parent file edits
-
-
-
-
- 0.6.3
- 2005-05-10
- PaulWFrields
- StuartEllis
-
-
- Style editing, removed "nextsteps" from build
-
-
-
-
- 0.7
- 2005-05-15
- StuartEllis
- PaulWFrields
-
-
- Additional style editing and indexing
-
-
-
-
- 1.0rc1
- 2005-06-08
- KarstenWade
-
-
- Publication edit and declaration of release candidate
-
-
-
-
- 1.0
- 2005-06-10
- KarstenWade
-
-
- Release version
-
-
-
-
- 1.0.1rc1
- 2005-11-20
- PaulWFrields
-
-
- Reorganization of introductory material
-
-
-
-
- 1.0.2
- 2005-11-25
- PaulWFrields
-
-
- Additional reorganization for clarity; information on
- /home partition
-
-
-
-
- 1.0.3
- 2005-12-04
- StuartEllis
-
-
- Reorganized to match anaconda screens.
-
-
-
-
- 1.0.4
- 2005-12-06
- StuartEllis
-
-
- Added material on updating the new installation.
-
-
-
-
- 1.0.5
- 2005-12-08
- StuartEllis
-
-
- Updated partitioning section.
-
-
-
-
- 1.0.6
- 2005-12-10
- StuartEllis
-
-
- Updated sections on installation methods.
-
-
-
-
- 1.0.7
- 2005-12-12
- StuartEllis
-
-
- Added Management Options section.
-
-
-
-
- 1.0.8
- 2005-12-14
- StuartEllis
-
-
- Added Technical References section.
-
-
-
-
- 1.0.9
- 2005-12-22
- StuartEllis
-
-
- Updated Management Options section.
-
-
-
-
- 1.1
- 2005-12-22
- StuartEllis
-
-
- Amended Management Options section.
-
-
-
-
- 1.11
- 2006-01-09
- StuartEllis
-
-
- Expanded Technical References section.
-
-
-
-
- 1.12
- 2006-01-11
- StuartEllis
-
-
- Minor fixes to Boot Options.
-
-
-
-
-
+
+ &FDP-INFO;
&INTRODUCTION;
From fedora-docs-commits at redhat.com Mon Jan 16 01:58:19 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 15 Jan 2006 20:58:19 -0500
Subject: docs-common/bin fdpsh,NONE,1.1
Message-ID: <200601160158.k0G1wJpk032547@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32530
Added Files:
fdpsh
Log Message:
Fedora Documention Project Shell, a wrapper for the "fdp-functions"
functionality that works very much like the original BASH shell.
--- NEW FILE fdpsh ---
#!/bin/bash
########################################################################
# Fedora Documentation Project Interactive Shell
#
# Runs BASH after first sourcing the "docs-common/bin/fdp-functions"
# file.
#
# If the "-c cmd" switch is used, exactly one "cmd" is executed.
# Without a "-c" switch, any file given on the command line is executed.
# With neither a "-c" switch or command line arguments, commands are
# accepted from stdin.
########################################################################
ME=$(basename $0)
MYDIR=$(dirname $0)
USAGE="usage: ${ME} [-c cmd] [file [arg..]]"
. ${MYDIR}/fdp-functions
CMD=
while getopts c: c
do
case "${c}" in
c) CMD="${OPTARG}";;
*) echo "${USAGE}" >&2; exit 1;;
esac
done
if [ "${CMD}" ]; then
${CMD}
results=$?
elif [ $# -gt 0 ]; then
$@
results=$?
else
while :
do
echo -n "${ME}> " >&2
read -e cmd
if [ "${cmd}" ]; then
${cmd}
results=$?
if [ ${results} -gt 0 ]; then
echo "Status = ${results}" >&2
fi
fi
done
fi
exit ${results}
From fedora-docs-commits at redhat.com Mon Jan 16 05:49:30 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 16 Jan 2006 00:49:30 -0500
Subject: docs-common/bin fdpsh,1.1,1.2
Message-ID: <200601160549.k0G5nU3x008290@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8270
Modified Files:
fdpsh
Log Message:
1) Make compatible with Bourne shell, bash, korn shell, and Z-Shell.
2) Redirections now work correctly in all modes. So do pipes, (),
and the like.
3) Set ${SHELL} environment parameter so that subshells inherit the
". fdp-functions" environment.
Index: fdpsh
===================================================================
RCS file: /cvs/docs/docs-common/bin/fdpsh,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fdpsh 16 Jan 2006 01:58:12 -0000 1.1
+++ fdpsh 16 Jan 2006 05:49:23 -0000 1.2
@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/bin/sh
########################################################################
# Fedora Documentation Project Interactive Shell
#
@@ -10,10 +10,16 @@
# With neither a "-c" switch or command line arguments, commands are
# accepted from stdin.
########################################################################
-ME=$(basename $0)
-MYDIR=$(dirname $0)
+ME=`basename $0`
+FDPBINDIR=`dirname $0`
USAGE="usage: ${ME} [-c cmd] [file [arg..]]"
-. ${MYDIR}/fdp-functions
+#
+PATH=${FDPBINDIR}:${PATH} export PATH
+FDPDIR=${FDPBINDIR}/../.. export FDPDIR
+SHELL=${FDPBINDIR}/${ME} export SHELL
+#
+. ${FDPBINDIR}/fdp-functions
+#
CMD=
while getopts c: c
do
@@ -23,10 +29,10 @@
esac
done
if [ "${CMD}" ]; then
- ${CMD}
+ eval ${CMD}
results=$?
elif [ $# -gt 0 ]; then
- $@
+ eval $@
results=$?
else
while :
@@ -34,7 +40,7 @@
echo -n "${ME}> " >&2
read -e cmd
if [ "${cmd}" ]; then
- ${cmd}
+ eval ${cmd}
results=$?
if [ ${results} -gt 0 ]; then
echo "Status = ${results}" >&2
From fedora-docs-commits at redhat.com Mon Jan 16 13:15:40 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 08:15:40 -0500
Subject: docs-common/bin xmlformat-fdp.conf,1.11,1.12
Message-ID: <200601161315.k0GDFen4025418@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25400/docs-common/bin
Modified Files:
xmlformat-fdp.conf
Log Message:
No need for this section in CVS, duh
Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- xmlformat-fdp.conf 15 Jan 2006 23:20:35 -0000 1.11
+++ xmlformat-fdp.conf 16 Jan 2006 13:15:33 -0000 1.12
@@ -3,10 +3,6 @@
# code is still code, so it's not really that important. (Down, inner
# stickler...)
#
-# ChangeLog:
-# * Jun 26 2005 Paul W. Frields <stickster at gmail.com>
-# - Initial version.
-#
*DEFAULT
format = block
From fedora-docs-commits at redhat.com Mon Jan 16 13:54:51 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 08:54:51 -0500
Subject: docs-common/bin insert-colophon,1.1,1.2
Message-ID: <200601161354.k0GDspPp025642@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25624/docs-common/bin
Modified Files:
insert-colophon
Log Message:
Make OTHERNAME setting scriptable
Index: insert-colophon
===================================================================
RCS file: /cvs/docs/docs-common/bin/insert-colophon,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- insert-colophon 15 Jan 2006 23:25:31 -0000 1.1
+++ insert-colophon 16 Jan 2006 13:54:43 -0000 1.2
@@ -15,8 +15,10 @@
read FIRSTNAME
done
-echo -n "Enter contributor's middle initial/name (leave blank for NONE): "
-read OTHERNAME
+if ! ( set | grep "^OTHERNAME" >/dev/null ); then
+ echo -n "Enter contributor's middle initial/name (leave blank for NONE): "
+ read OTHERNAME
+fi
while test -z "$SURNAME"; do
echo -n "Enter contributor's surname: "
From fedora-docs-commits at redhat.com Mon Jan 16 14:21:30 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 09:21:30 -0500
Subject: docs-common/common legalnotice-opl-en.xml, NONE,
1.1 fedora-entities-en.ent, 1.11, 1.12 opl.xml, 1.3, 1.4
Message-ID: <200601161421.k0GELUjf027412@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27391
Modified Files:
fedora-entities-en.ent opl.xml
Added Files:
legalnotice-opl-en.xml
Log Message:
Add appropriate wrapper and entity support for OPL licensing
--- NEW FILE legalnotice-opl-en.xml ---
&LEGALNOTICE-OPL-CONTENT;
Index: fedora-entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- fedora-entities-en.ent 24 Oct 2005 13:56:48 -0000 1.11
+++ fedora-entities-en.ent 16 Jan 2006 14:21:22 -0000 1.12
@@ -47,6 +47,7 @@
+
Index: opl.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/opl.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- opl.xml 26 Oct 2005 00:22:25 -0000 1.3
+++ opl.xml 16 Jan 2006 14:21:22 -0000 1.4
@@ -9,7 +9,6 @@
]>
-->
-
Permission is granted to copy, distribute, and/or modify this
@@ -216,4 +215,3 @@
holder.' to the license reference or copy.
-
From fedora-docs-commits at redhat.com Mon Jan 16 14:53:30 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Mon, 16 Jan 2006 09:53:30 -0500
Subject: docs-common/bin xmlformat-fdp.conf,1.12,1.13
Message-ID: <200601161453.k0GErUF2027496@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27478
Modified Files:
xmlformat-fdp.conf
Log Message:
Need to mark the table's entry out separately, because it is not possible to predict what is needed. The parser looks to the existence of any whitespace after the as an indication of inline v. block markup, and there is no way to tell with xmlformat. It is better to leave this alone and to the discretion of the author to solve. The problem to solve next is, what happens when xmlformat encounters content on the same line as . I'll test later.
Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- xmlformat-fdp.conf 16 Jan 2006 13:15:33 -0000 1.12
+++ xmlformat-fdp.conf 16 Jan 2006 14:53:22 -0000 1.13
@@ -65,6 +65,11 @@
screen programlisting
format = verbatim
+# is special because a linebreak has meaning, best leave the
+# decisions up to the experts
+entry
+ format = verbatim
+
command application filename option userinput computeroutput replaceable
format = inline
From fedora-docs-commits at redhat.com Mon Jan 16 15:27:39 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 10:27:39 -0500
Subject: docs-common/packaging info2rpminfo.xsl,1.8,1.9
Message-ID: <200601161527.k0GFRdkL029380@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29362/docs-common/packaging
Modified Files:
info2rpminfo.xsl
Log Message:
Make spacing more properly XMLish
Index: info2rpminfo.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/info2rpminfo.xsl,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- info2rpminfo.xsl 7 Jan 2006 23:31:44 -0000 1.8
+++ info2rpminfo.xsl 16 Jan 2006 15:27:31 -0000 1.9
@@ -1,5 +1,5 @@
-
+
@@ -10,6 +10,7 @@
+ CHECK LICENSING BELOWGNU FDL1.0
@@ -29,8 +30,10 @@
+ PLEASE ADD EMAIL ADDRESSES AND ENSURE
+ "id" ATTRIBUTES MATCH "worker" ATTRIBUTES
+ IN "changelog/author ELEMENTS.Only author|editor|othercredit processed.
- PLEASE ADD EMAIL ADDRESSES.You may remove these comments after editing.
@@ -51,7 +54,7 @@
-
+
@@ -65,7 +68,7 @@
- PLEASE ADD BOOK/ARTICLE DESCRIPTION TO RPM-INFO
+ PLEASE ADD BOOK/ARTICLE DESCRIPTION TO RPM-INFO
From fedora-docs-commits at redhat.com Mon Jan 16 15:28:55 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 10:28:55 -0500
Subject: docs-common/common opl.xml,1.4,1.5
Message-ID: <200601161528.k0GFStpt029409@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29391/docs-common/common
Modified Files:
opl.xml
Log Message:
Make OPL content render correctly by demoting opening paragraph, which is not really part of the license content
Index: opl.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/opl.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- opl.xml 16 Jan 2006 14:21:22 -0000 1.4
+++ opl.xml 16 Jan 2006 15:28:48 -0000 1.5
@@ -9,13 +9,11 @@
]>
-->
-
-
- Permission is granted to copy, distribute, and/or modify this
- document under the terms of the Open Publication Licence, Version
- 1.0, or any later version. The terms of the OPL are set out below.
-
-
+
+ Permission is granted to copy, distribute, and/or modify this
+ document under the terms of the Open Publication Licence, Version
+ 1.0, or any later version. The terms of the OPL are set out below.
+ REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS
From fedora-docs-commits at redhat.com Mon Jan 16 16:05:33 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 11:05:33 -0500
Subject: docs-common/packaging bookinfo.xsl,1.12,1.13
Message-ID: <200601161605.k0GG5XQF031288@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31267/docs-common/packaging
Modified Files:
bookinfo.xsl
Log Message:
Allow proper choice of OPL for license... probably need additional checks
Index: bookinfo.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/bookinfo.xsl,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- bookinfo.xsl 14 Jan 2006 23:16:42 -0000 1.12
+++ bookinfo.xsl 16 Jan 2006 16:05:13 -0000 1.13
@@ -41,7 +41,6 @@
select="@worker"/>
- &LEGALNOTICE;
@@ -64,7 +63,14 @@
- &LEGALNOTICE;
+
+
+ &LEGALNOTICE-OPL;
+
+
+ &LEGALNOTICE;
+
+
From fedora-docs-commits at redhat.com Mon Jan 16 20:06:12 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 15:06:12 -0500
Subject: docs-common Makefile.common,1.30,1.31
Message-ID: <200601162006.k0GK6CvP008315@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8295/docs-common
Modified Files:
Makefile.common
Log Message:
Use new fdpsh, 'cause it's kewl
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- Makefile.common 15 Jan 2006 23:25:37 -0000 1.30
+++ Makefile.common 16 Jan 2006 20:05:43 -0000 1.31
@@ -214,8 +214,7 @@
# Make a new changelog entry for an existing rpm-info.xml file.
clog:: $(RPMINFO)
- @XMLFORMAT="$(XMLFORMAT)" XSLTPROC="$(XSLTPROC)" \
- ${FDPBIN}/insert-changelog $(RPMINFO).clog
+ @${FDPBIN}/fdpsh -c insert-changelog $(RPMINFO).clog
mv -b $(RPMINFO).clog $(RPMINFO)
#
@@ -223,8 +222,7 @@
# Make a new colophon entry for an existing rpm-info.xml file.
colophon:: $(RPMINFO)
- @XMLFORMAT="$(XMLFORMAT)" XSLTPROC="$(XSLTPROC)" \
- ${FDPBIN}/insert-colophon $(RPMINFO).worker
+ @${FDPBIN}/fdpsh -c insert-colophon $(RPMINFO).worker
mv -b $(RPMINFO).worker $(RPMINFO)
#
From fedora-docs-commits at redhat.com Mon Jan 16 20:33:11 2006
From: fedora-docs-commits at redhat.com (Scott Glaser (sonarguy))
Date: Mon, 16 Jan 2006 15:33:11 -0500
Subject: install-guide rpm-info.xml, NONE,
1.1.2.1 fedora-install-guide-intro-en.xml, 1.24.2.5, 1.24.2.6
Message-ID: <200601162033.k0GKXB7e008559@cvs-int.fedora.redhat.com>
Author: sonarguy
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8538
Modified Files:
Tag: FC5_SAG
fedora-install-guide-intro-en.xml
Added Files:
Tag: FC5_SAG
rpm-info.xml
Log Message:
Updated to include rpm-info.xml
--- NEW FILE rpm-info.xml ---
GNU FDL1.02005Red Hat, Inc.Stuart EllisPaul W. FrieldsFedora Core 5 Installation Guide - BETAEdited Install Guide per RFE 173735 to include new flow.Amended Management Options section.Updated Management Options section.Added Technical References section.Added Management Options section.Updated sections on installation methods.Updated partitioning section.Added material on updating the new installation.Reorganized to match anaconda screens.Additional reorganization for clarity; information on /home partitionReorganization of introductory materialRelease versionPublication edit and declaration of release candidateAdditional style editing and indexingStyle editing, removed "nextsteps" from buildFirst commission to CVS, plus very minor parent file edits
Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.24.2.5
retrieving revision 1.24.2.6
diff -u -r1.24.2.5 -r1.24.2.6
--- fedora-install-guide-intro-en.xml 15 Jan 2006 13:47:26 -0000 1.24.2.5
+++ fedora-install-guide-intro-en.xml 16 Jan 2006 20:33:03 -0000 1.24.2.6
@@ -655,7 +655,7 @@
DVD Installation Media: Below is a list of the images
required for the DVD installation method based on architecture. The images are
- available at fedora.redhat.com.
+ available at Fedora Mirrors.
Alternatively, you can Join the Torrent.
Once you have downloaded the images specific to your architecture proceed to
.
From fedora-docs-commits at redhat.com Mon Jan 16 22:01:47 2006
From: fedora-docs-commits at redhat.com (Andrew Martynov (andrmart))
Date: Mon, 16 Jan 2006 17:01:47 -0500
Subject: release-notes Makefile,1.15,1.16
Message-ID: <200601162201.k0GM1lua013821@cvs-int.fedora.redhat.com>
Author: andrmart
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13797
Modified Files:
Makefile
Log Message:
add RU to build. Content is completed yet but suitable to test2
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- Makefile 13 Jan 2006 15:33:03 -0000 1.15
+++ Makefile 16 Jan 2006 22:01:39 -0000 1.16
@@ -10,7 +10,7 @@
#
# Document-specific definitions.
#
-LANGUAGES = en it ja_JP zh_CN #ja_JP ru
+LANGUAGES = en it ja_JP zh_CN ru #ja_JP
# uncomment languages when you have all the same
# fies localized as are listed in XMLEXTRAFILES
DOCBASE = RELEASE-NOTES
From fedora-docs-commits at redhat.com Mon Jan 16 23:07:47 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 18:07:47 -0500
Subject: docs-common/bin insert-changelog,1.4,1.5
Message-ID: <200601162307.k0GN7mGi016704@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16670/docs-common/bin
Modified Files:
insert-changelog
Log Message:
clog target and XSL stylesheet should be able to figure out if this is the first package for a document revision
Index: insert-changelog
===================================================================
RCS file: /cvs/docs/docs-common/bin/insert-changelog,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- insert-changelog 15 Jan 2006 23:26:25 -0000 1.4
+++ insert-changelog 16 Jan 2006 23:07:33 -0000 1.5
@@ -22,6 +22,7 @@
if test $ROLE = "rpm"; then
REVDATE=`date +"%a %b %d %Y"`
ZEROREV=0
+ NUMBER=1
REVDESC="an integer release number"
elif test $ROLE = "doc"; then
REVDATE=`date +"%Y-%M-%d"`
From fedora-docs-commits at redhat.com Mon Jan 16 23:07:35 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 18:07:35 -0500
Subject: docs-common/packaging doc-version.xsl,1.3,1.4
Message-ID: <200601162308.k0GN8LEX016707@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16670/docs-common/packaging
Modified Files:
doc-version.xsl
Log Message:
clog target and XSL stylesheet should be able to figure out if this is the first package for a document revision
Index: doc-version.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/doc-version.xsl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- doc-version.xsl 15 Jan 2006 17:43:20 -0000 1.3
+++ doc-version.xsl 16 Jan 2006 23:07:06 -0000 1.4
@@ -11,6 +11,22 @@
-
+
+
+
+
+ 0
+
+
+
+
+
+
+
+
+
+
From fedora-docs-commits at redhat.com Tue Jan 17 01:12:52 2006
From: fedora-docs-commits at redhat.com (Scott Glaser (sonarguy))
Date: Mon, 16 Jan 2006 20:12:52 -0500
Subject: install-guide fedora-install-guide-intro-en.xml,1.24.2.6,1.24.2.7
Message-ID: <200601170112.k0H1CqTP020821@cvs-int.fedora.redhat.com>
Author: sonarguy
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20803
Modified Files:
Tag: FC5_SAG
fedora-install-guide-intro-en.xml
Log Message:
Updated Section 8 Getting the Installation Media with the preliminary text
Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.24.2.6
retrieving revision 1.24.2.7
diff -u -r1.24.2.6 -r1.24.2.7
--- fedora-install-guide-intro-en.xml 16 Jan 2006 20:33:03 -0000 1.24.2.6
+++ fedora-install-guide-intro-en.xml 17 Jan 2006 01:12:33 -0000 1.24.2.7
@@ -344,7 +344,7 @@
You are downloading an entire operating system, and in most cases,
you are then going to install the operating system on your computer.
If you are connected to the Internet via a slow connection, like a
- modem, then downloading Fedora Core will be an extremely
+ modem, then downloading &FC; will be an extremely
time-consuming process. The time it takes to download the installation
files for &FC; depends greatly upon your connection speed to the Internet.
For example, if you are downloading the installation disk images (called ISOs),
@@ -613,7 +613,7 @@
CD Installation Media: Below is a list of the images
required for CD installation method based on architecture. The images are
- available at fedora.redhat.com.
+ available at http://fedora.redhat.com/download/.
Alternatively, you can Join the Torrent.
Once you have downloaded the images specific to your architecture proceed to
.
@@ -655,7 +655,7 @@
DVD Installation Media: Below is a list of the images
required for the DVD installation method based on architecture. The images are
- available at Fedora Mirrors.
+ available at http://fedora.redhat.com/download/mirrors.html.
Alternatively, you can Join the Torrent.
Once you have downloaded the images specific to your architecture proceed to
.
@@ -689,37 +689,209 @@
- USB Installation Media:
+ USB Installation Media: Below is a list of the images
+ required for the USB installation method based on architecture. The images are
+ available at http://fedora.redhat.com/download/mirrors.html.
+ Alternatively, you can Join the Torrent.
+ Once you have downloaded the images specific to your architecture proceed to
+ .
-
+
+
+
+ i386 Media - The following images will needed to complete
+ a USB installation: FC5-i386-DVD.iso and SHA1SUM, of if you are utilizing
+ bittorrent the image would be FC5-binary-i386.torrent.
+
+
+
+
+
+ x86_64 Media - The following images will needed to complete
+ a USB installation: FC5-x86_64-DVD.iso and SHA1SUM, of if you are utilizing
+ bittorrent the image would be FC5-binary-x86_64.torrent.
+
+
+
+
+
+ ppc Media- The following images will needed to complete
+ a USB installation: FC5-ppc-DVD.iso and SHA1SUM, of if you are utilizing
+ bittorrent the image would be FC5-binary-ppc.torrent.
+
+
+
+
- Hard Drive Installation Media:
+ Hard Drive Installation Media: Below is a list of the images
+ required for the Hard Drive installation method based on architecture. The images are
+ available at http://fedora.redhat.com/download/mirrors.html.
+ Alternatively, you can Join the Torrent.
+ Once you have downloaded the images specific to your architecture proceed to
+ .
+
+
+
+ i386 Media - The following images will needed to complete
+ a Hard Drive installation: FC5-i386-DVD.iso and SHA1SUM, of if you are utilizing
+ bittorrent the image would be FC5-binary-i386.torrent.
+
+
+
+
+
+ x86_64 Media - The following images will needed to complete
+ a Hard Drive installation: FC5-x86_64-DVD.iso and SHA1SUM, of if you are utilizing
+ bittorrent the image would be FC5-binary-x86_64.torrent.
+
+
+
+
+
+ ppc Media- The following images will needed to complete
+ a Hard Drive installation: FC5-ppc-DVD.iso and SHA1SUM, of if you are utilizing
+ bittorrent the image would be FC5-binary-ppc.torrent.
+
+
+
+
-
-
+
+
Network Installation Media
- HTTP Installation Media:
+ HTTP Installation Media: Below is a list of the images
+ required for the HTTP installation method based on architecture. The images are
+ available at http://fedora.redhat.com/download/
+ or http://fedora.redhat.com/download/mirrors.html.
+ Alternatively, you can Join the Torrent.
+ Once you have downloaded the images specific to your architecture proceed to
+ .
+
+
+
+ i386 Media - Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/i386/os/images/
+
+
+
+
+
+ x86_64 Media - Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/x86_64/os/images/
+
+
+
+
+
+ ppc Media- Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/ppc/os/images/
+
+
+
- FTP Installation Media:
+ FTP Installation Media: Below is a list of the images
+ required for the FTP installation method based on architecture. The images are
+ available at http://fedora.redhat.com/download/
+ or http://fedora.redhat.com/download/mirrors.html.
+ Alternatively, you can Join the Torrent.
+ Once you have downloaded the images specific to your architecture proceed to
+ .
+
+
+
+ i386 Media - Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/i386/os/images/
+
+
+
+
+
+ x86_64 Media - Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/x86_64/os/images/
+
+
+
+
+
+ ppc Media- Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/ppc/os/images/
+
+
+
- NFS Installation Media:
+ NFS Installation Media: Below is a list of the images
+ required for the NFS installation method based on architecture. The images are
+ available at http://fedora.redhat.com/download/
+ or http://fedora.redhat.com/download/mirrors.html.
+ Alternatively, you can Join the Torrent.
+ Once you have downloaded the images specific to your architecture proceed to
+ .
+
+
+
+ i386 Media - Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/i386/os/images/
+
+
+
+
+
+ x86_64 Media - Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/x86_64/os/images/
+
+
+
+
+
+ ppc Media- Depending on the method with which you boot for
+ your installation you will either need the boot.iso for booting from a CD, or you
+ will need the diskboot.img if you plan on booting from a USB device. Both
+ images are located in the following location at both the Fedora Servers or
+ the Mirror Servers: /pub/fedora/linux/core/5/ppc/os/images/
+
+
+
@@ -730,7 +902,19 @@
Purchased Media
- Insert text about Purchased Media.
+ Just because we are discussing purchased media, does not mean one needs to purchase
+ the media. It is just a reference that covers purchase or prepared media that you
+ the user does not need to download. The purchased media can come from numerous
+ sources, one option is your local Linux Users Group or LUG as they are known in
+ the community. A quick search on Google
+ will usually reveal a multitude of groups. These groups typically are more than
+ willing to provide a set of &FC; disks at little or no cost. Another option
+ would be your local Book Store, several publishers produce books about the latest
+ release of &FC; that are very informative and typically includes installation
+ media as part of the purchase. These books are are well written and include loads
+ of information about the &FC; operating system. The ultimate choice of
+ which media you go is up to you the user and what you wish to do to get the Fedora
+ Core operating system.
@@ -799,7 +983,7 @@
-
+ Preparing FTP Installation Media
From fedora-docs-commits at redhat.com Tue Jan 17 02:02:30 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 16 Jan 2006 21:02:30 -0500
Subject: docs-common/bin move-if-change,NONE,1.1
Message-ID: <200601170202.k0H22U5I022874@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22813
Added Files:
move-if-change
Log Message:
Conditionally move source file to target if, and only if, their
content differs. This can help avoid unnecessary rebuilds when
working with derived files.
--- NEW FILE move-if-change ---
#!/bin/sh
# Copyright (C) 1996 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
if
test -r $2
then
if
cmp $1 $2 > /dev/null
then
echo $2 is unchanged
rm -f $1
else
mv -f $1 $2
fi
else
mv -f $1 $2
fi
From fedora-docs-commits at redhat.com Tue Jan 17 02:12:22 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 16 Jan 2006 21:12:22 -0500
Subject: docs-common/bin move-if-change,1.1,1.2
Message-ID: <200601170212.k0H2CM8j022934@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22901/bin
Modified Files:
move-if-change
Log Message:
Automatically create a backup, similar to "mv -b", if we replace
a file.
Index: move-if-change
===================================================================
RCS file: /cvs/docs/docs-common/bin/move-if-change,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- move-if-change 17 Jan 2006 02:02:13 -0000 1.1
+++ move-if-change 17 Jan 2006 02:12:00 -0000 1.2
@@ -16,6 +16,9 @@
# along with this program; if not, write to the Free Software
# Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+# Modified by , for the Fedora Documentation
+# Project, to automatically create a backup of any file we touch.
+
if
test -r $2
then
@@ -25,8 +28,8 @@
echo $2 is unchanged
rm -f $1
else
-mv -f $1 $2
+mv -f -b $1 $2
fi
else
-mv -f $1 $2
+mv -f -b $1 $2
fi
From fedora-docs-commits at redhat.com Tue Jan 17 02:12:40 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 21:12:40 -0500
Subject: release-notes rpm-info.xml,NONE,1.1
Message-ID: <200601170212.k0H2CeZ1022951@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22923
Added Files:
rpm-info.xml
Log Message:
Built tonight in a hurry; this needs to have translations added for the desc elements, plus a real colophon built from the wiki
--- NEW FILE rpm-info.xml ---
GNU FDL1.02006Red Hat, Inc.Fedora Core 5 test2 Release NotesImportant information about this release of Fedora CoreFedora Core 5 test2 ????????????Note di rilascio per Fedora Core 5 test2Fedora Core 5 test2 ?????????????????? ?? ??????????????Fedora core 5 test2 ?????????????????????????????????
From fedora-docs-commits at redhat.com Tue Jan 17 02:14:56 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 16 Jan 2006 21:14:56 -0500
Subject: docs-common Makefile.common,1.31,1.32
Message-ID: <200601170214.k0H2Eupj023008@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22941
Modified Files:
Makefile.common
Log Message:
Select "fdpsh" as the shell used by make(1). This lets us avoid
ugly "${FDPBIN}/foo" in preference to a lovely, lonely, "foo".
Also, replace unconditional mv(1) commands with "move-if-change"
to help avoid needlessly touching a file, thus triggering a
useless rebuild. Don't know if this happens here, but its a
best practices thing.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- Makefile.common 16 Jan 2006 20:05:43 -0000 1.31
+++ Makefile.common 17 Jan 2006 02:14:49 -0000 1.32
@@ -64,6 +64,10 @@
XMLFORMAT=$(FDPDIR)/docs-common/bin/xmlformat
XMLFOPTS=-f $(FDPDIR)/docs-common/bin/xmlformat-fdp.conf
#########################################################################
+# Use our very own "docs-common/bin/fdpsh" as the command interpreter
+# This automatically has ${FDPBIN} as first in the ${PATH}
+SHELL =${FDPBIN}/fdpsh
+#########################################################################
# PUT NO TARGETS BEFORE THIS ONE, not even in your base Makefile
# In a properly-constructed Makefile, this will be the default target
@@ -97,7 +101,7 @@
cp ${HTMLCSS} $(DOCBASE)-$(1)/fedora.css
[ -z "${HTMLCSSEXTRA}" ] || \
cp ${HTMLCSSEXTRA} $(DOCBASE)-$(1)/watermark.png
- [ ! -d figs ] || ${FDPBIN}/copy-figs -v -f '*.png' \
+ [ ! -d figs ] || copy-figs -v -f '*.png' \
-l ${LANG} figs $(DOCBASE)-$(1)
endef
#
@@ -159,6 +163,7 @@
$(foreach LANG,${LANGUAGES},$(eval $(call CLEAN_template,${LANG})))
#
clean:: $(foreach LANG,${LANGUAGES},${DOCBASE}-${LANG}-clean)
+ ${RM} *.tmp
#########################################################################
define DISTCLEAN_template
${DOCBASE}-$(1)-distclean:: ${DOCBASE}-$(1)-clean
@@ -188,7 +193,7 @@
DIFFS =-u
diff::
- ${FDPBIN}/xmldiff ${DIFFS} ${OLD} ${NEW}
+ xmldiff ${DIFFS} ${OLD} ${NEW}
#
#########################################################################
# The "fdp-info-${LANG}.xml" file contains the or
@@ -214,16 +219,16 @@
# Make a new changelog entry for an existing rpm-info.xml file.
clog:: $(RPMINFO)
- @${FDPBIN}/fdpsh -c insert-changelog $(RPMINFO).clog
- mv -b $(RPMINFO).clog $(RPMINFO)
+ insert-changelog $(RPMINFO).tmp && \
+ move-if-change $(RPMINFO).tmp $(RPMINFO)
#
#########################################################################
# Make a new colophon entry for an existing rpm-info.xml file.
colophon:: $(RPMINFO)
- @${FDPBIN}/fdpsh -c insert-colophon $(RPMINFO).worker
- mv -b $(RPMINFO).worker $(RPMINFO)
+ insert-colophon $(RPMINFO).tmp && \
+ move-if-change $(RPMINFO).tmp $(RPMINFO)
#
#########################################################################
From fedora-docs-commits at redhat.com Tue Jan 17 02:25:56 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 Jan 2006 21:25:56 -0500
Subject: docs-common/common fedora-entities-en.ent, 1.12,
1.13 fedora-entities-it.ent, 1.2, 1.3
Message-ID: <200601170225.k0H2PuDc023211@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23191
Modified Files:
fedora-entities-en.ent fedora-entities-it.ent
Log Message:
Argggh, why were these not changed earlier?
Index: fedora-entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- fedora-entities-en.ent 16 Jan 2006 14:21:22 -0000 1.12
+++ fedora-entities-en.ent 17 Jan 2006 02:25:49 -0000 1.13
@@ -30,8 +30,8 @@
-
-
+
+
Index: fedora-entities-it.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/fedora-entities-it.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-entities-it.ent 24 Dec 2005 14:22:06 -0000 1.2
+++ fedora-entities-it.ent 17 Jan 2006 02:25:49 -0000 1.3
@@ -30,8 +30,8 @@
-
-
+
+
From fedora-docs-commits at redhat.com Tue Jan 17 21:08:05 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 17 Jan 2006 16:08:05 -0500
Subject: example-tutorial example-tutorial-en.xml,1.19,1.20
Message-ID: <200601172108.k0HL85qA001942@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1924
Modified Files:
example-tutorial-en.xml
Log Message:
Define and use "&FDP-INFO;" entity.
Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- example-tutorial-en.xml 28 Dec 2005 22:19:04 -0000 1.19
+++ example-tutorial-en.xml 17 Jan 2006 21:07:56 -0000 1.20
@@ -12,13 +12,13 @@
-
+
]>
-
+&FDP-INFO;
Some Section
From fedora-docs-commits at redhat.com Tue Jan 17 21:11:22 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 17 Jan 2006 16:11:22 -0500
Subject: example-tutorial Makefile,1.25,1.26
Message-ID: <200601172111.k0HLBMqU001976@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1956
Modified Files:
Makefile
Log Message:
Moved all the packaging stuff to "docs-common/Makefile.common".
Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- Makefile 30 Dec 2005 16:56:39 -0000 1.25
+++ Makefile 17 Jan 2006 21:11:02 -0000 1.26
@@ -17,141 +17,6 @@
LANGUAGES = en de
DOCBASE = example-tutorial
#
-DOCTITLE-en = Example Tutorial
-XMLEXTRAFILES-en= fdp-info-en.xml
-#
-DOCTITLE-de = Beispiel Tutorial
-XMLEXTRAFILES-de= fdp-info-de.xml
-#
######################################################
include ../docs-common/Makefile.common
######################################################
-#
-# If you want to add additional steps to any of the
-# targets defined in "Makefile.common", be sure to use
-# a double-colon in your rule here. For example, to
-# print the message "FINISHED AT LAST" after building
-# the HTML document version, uncomment the following
-# line:
-#${DOCBASE}-en/index.html::
-# echo FINISHED AT LAST
-
-######################################################
-#
-######################################################
-
-######################################################
-# Some packaging specific vars
-
-# These are obviated by new standard
-DATE=$(shell grep DOCID $(DOCBASE)-en.xml | sed 's/.\+(//' | sed 's/).\+//')
-VERSION=$(shell grep " DOCVERSION" $(DOCBASE)-en.xml | sed 's/.\+"\([0-9\.]\+\)".\+/\1/' )
-NOW=$(shell date +"%a %b %e %Y")
-
-XMLFORMAT=$(FDPDIR)/docs-common/bin/xmlformat
-XMLFOPTS=-f $(FDPDIR)/docs-common/bin/xmlformat-fdp.conf
-######################################################
-# Some RPM flags...
-######################################################
-RPMFLAGS=--define "docbase $(DOCBASE)" --define "version $(VERSION)" --define "_topdir $(PWD)" --define "_rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm" --define "_sourcedir $(PWD)" --define "_rpmdir $(PWD)" --define "_srcrpmdir $(PWD)" --define "_specdir $(PWD)" --define "fdpdir $(FDPDIR)"
-
-SPECFILE=$(PWD)/fedora-doc-$(DOCBASE).spec
-ifeq (${RPMDEBUG},1)
-RPMDFLAG = -vv
-endif
-######################################################
-
-
-clean::
- ${RM} -rf fedora-doc-$(DOCBASE)*.rpm
- ${RM} -rf $(DOCBASE)-$(VERSION)*.src.tar.gz
- ${RM} -rf BUILD/ $(DOCBASE)-$(VERSION)/
- ${RM} -f *omf *desktop $(SPECFILE)
- ${RM} -f fdp-info-*.xml
- sed -i 's@^\( *[^<]*&FDP-INFO;.*\)@\@\&FDP-INFO;@g' $(DOCBASE)-$(1).xml
-endef
-
-fdp-info:: $(foreach LANG,${LANGUAGES},fdp-info-$(LANG).xml)
-
-$(foreach LANG,${LANGUAGES},$(eval $(call fdp-info_template,${LANG})))
-
-
-spec::
- $(XSLTPROC) ../docs-common/packaging/spec.xsl rpm-info.xml > \
- $(SPECFILE)
-
-
-gnome.desktop::
- $(XSLTPROC) ../docs-common/packaging/gnome-desktop.xsl rpm-info.xml > \
- fedora-doc-$(DOCBASE)-gnome.desktop
-
-
-kde.desktop::
- $(XSLTPROC) ../docs-common/packaging/kde-desktop.xsl rpm-info.xml > \
- fedora-doc-$(DOCBASE)-kde.desktop
-
-
-khelp.desktop::
- $(XSLTPROC) ../docs-common/packaging/khelpcenter-plugin.xsl \
- rpm-info.xml > fedora-doc-$(DOCBASE)-khelp.desktop
-
-
-define omf_template
-omf-$(1)::
-# xmllint is part of libxml2
- ${XSLTPROC} ../docs-common/packaging/omf.xsl rpm-info.xml | \
- $(XMLFORMAT) $(XMLFOPTS) > fedora-doc-$(DOCBASE)-$(1).omf
-endef
-
-omf:: $(foreach LANG,${LANGUAGES},omf-$(LANG))
-# correct lang=en for scrollkeeper document
- mv fedora-doc-$(DOCBASE)-en.omf fedora-doc-$(DOCBASE)-C.omf
-
-$(foreach LANG,${LANGUAGES},$(eval $(call omf_template,${LANG})))
-
-
-$(DOCBASE)-$(VERSION).src.tar.gz:: clean fdp-info gnome.desktop kde.desktop khelp.desktop omf
- mkdir $(DOCBASE)-$(VERSION)
- find . -maxdepth 1 -type f ! \( -name '*~' \
- -o -name '#*' \
- -o -name '$(DOCBASE)*.tar.gz' \
- -o -name '.*' \) \
- | cpio -pamdv $(DOCBASE)-$(VERSION)
- find . -maxdepth 1 -type d ! \( -name '$(DOCBASE)-$(VERSION)' \
- -o -name 'CVS' \
- -o -name '*~' \
- -o -name '$(DOCBASE)*' \) \
- | cpio -pamdv $(DOCBASE)-$(VERSION)
- tar -zcvf $(DOCBASE)-$(VERSION).src.tar.gz $(DOCBASE)-$(VERSION)/
- rm -rf $(DOCBASE)-$(VERSION)/
- sed -i 's@^\( *[^<]*&FDP-INFO;.*\)@\
+
+
+ Added initial empty RPM revision to test packaging.
+ Added information on driver disks.
@@ -74,11 +85,11 @@
Reorganization of introductory material
-
+ Release version
-
+ Publication edit and declaration of release candidate
From fedora-docs-commits at redhat.com Tue Jan 17 23:04:43 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 17 Jan 2006 18:04:43 -0500
Subject: install-guide rpm-info.xml,1.2,1.3
Message-ID: <200601172304.k0HN4hoE006770@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6749
Modified Files:
rpm-info.xml
Log Message:
Dates must be in ctime(3) format, not ISO format.
TODO: We need an XSL magic to translate the dates if they have dashes.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.xml 17 Jan 2006 22:49:29 -0000 1.2
+++ rpm-info.xml 17 Jan 2006 23:04:15 -0000 1.3
@@ -28,7 +28,7 @@
-
+ Added initial empty RPM revision to test packaging.
From fedora-docs-commits at redhat.com Wed Jan 18 06:32:23 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 01:32:23 -0500
Subject: translation-quick-start-guide - New directory
Message-ID: <200601180632.k0I6WN4f022885@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22870/translation-quick-start-guide
Log Message:
Directory /cvs/docs/translation-quick-start-guide added to the repository
From fedora-docs-commits at redhat.com Wed Jan 18 06:41:41 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 18 Jan 2006 01:41:41 -0500
Subject: docs-common/bin fdp-functions,1.2,1.3
Message-ID: <200601180641.k0I6ffPg022945@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22922
Modified Files:
fdp-functions
Log Message:
Added helper function 'iso2date' to convert YYYY-MM-DD into ctime(3)
format, as neded by the attributes.
Also added more error checking and usage hints.
Index: fdp-functions
===================================================================
RCS file: /cvs/docs/docs-common/bin/fdp-functions,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fdp-functions 15 Jan 2006 23:26:25 -0000 1.2
+++ fdp-functions 18 Jan 2006 06:41:34 -0000 1.3
@@ -1,7 +1,8 @@
-#!/bin/sh
+########################################################################
#
# Some common functions for use in other FDP scripts
#
+########################################################################
FDPDIR=${FDPDIR:-".."}
@@ -15,26 +16,63 @@
get_all_workers()
{
- # Return list of workers, in format "email:wholename"
- ${XSLTPROC} "${FDPPKGDIR}/get-all-workers.xsl" \
- "$RPMINFO" | sed 's/^ \+//g' | grep -v '^$' | cat -n
+ # Return list of workers, in format "email:wholename"
+ if [ ! -f "${RPMINFO}" ]; then
+ echo "$0: File '${RPMINFO}' missing." >&2
+ return 1
+ fi
+ ${XSLTPROC} "${FDPPKGDIR}/get-all-workers.xsl" \
+ "${RPMINFO}" | sed 's/^ \+//g' | grep -v '^$' | cat -n
}
get_worker_attribute()
{
- # Return an attribute for a specific worker
- if [ ! -z "$2" ]; then POS=$2 ; fi
- if [ ! -z "$1" ]; then ATT="$1" ; fi
- ${XSLTPROC} --stringparam att "$ATT" --param pos $POS \
- "${FDPPKGDIR}/get-worker.xsl" "$RPMINFO"
+ # Return an attribute for a specific worker
+ if [ ! -f "${RPMINFO}" ]; then
+ echo "$0: File '${RPMINFO}' missing." >&2
+ return 1
+ fi
+ if [ ! -z "$2" ]; then POS=$2 ; fi
+ if [ ! -z "$1" ]; then ATT="$1" ; fi
+ ${XSLTPROC} --stringparam att "${ATT}" --param pos $POS \
+ "${FDPPKGDIR}/get-worker.xsl" "${RPMINFO}"
}
-get_latest_revision()
+version()
{
- # Return latest revision for an optional role argument
- if [ ! -z "$1" ]; then
- OPTS="--stringparam role $1"
- fi
- ${XSLTPROC} ${OPTS} "${FDPPKGDIR}/doc-version.xsl" "$RPMINFO"
+ # Return latest revision for an optional role argument
+ # Don't gumble if we cannot find ${RPMINF}, because it
+ # may not have been created yet.
+ if [ ! -z "$1" ]; then
+ OPTS="--stringparam role $1"
+ fi
+ if [ -f "${RPMINFO}" ]; then
+ ${XSLTPROC} ${OPTS} "${FDPPKGDIR}/doc-version.xsl" "$RPMINFO"
+ else
+ echo -n XXX
+ fi
+ # The stylesheet doesn't put a NL at the end.
+ echo
+}
+
+iso2date() {
+ # Convert ISO format date (YYYY-MM-DD) to ctime(3)
+ # format, which is needed by the "rpm-info.xml"
+ case "$#" in
+ 0 ) echo -e "usage: iso2date YYYY-MM-DD ..." >&2
+ echo -e "\tiso2date YYYY-MM-DD" >&2
+ echo -e "\tiso2date today" >&2
+ return 1
+ ;;
+ 1 ) multi=0;;
+ * ) multi=1;;
+ esac
+ for x in $@
+ do
+ if [ ${multi} -eq 1 ]; then
+ echo -ne "${x}\t"
+ fi
+ date -d 2006-01-18 +'%a %b %d %Y'
+ done
}
From fedora-docs-commits at redhat.com Wed Jan 18 06:42:26 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 01:42:26 -0500
Subject: translation-quick-start-guide Makefile,NONE,1.1
Message-ID: <200601180642.k0I6gQF5022969@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22952
Added Files:
Makefile
Log Message:
trans-quick
--- NEW FILE Makefile ---
###############################################################################
# Makefile for RHLP docs project
# Created by: Tammy Fox
# Last edited by: Tommy Reynolds
# WARNING: need passivetex 1.24 for pdf generation to work
# License: GPL
# Copyright 2003 Tammy Fox, Red Hat, Inc.
# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
LANGUAGES = en es
DOCBASE = translation-quick-start
XMLEXTRAFILES-en =
######################################################
include ../docs-common/Makefile.common
######################################################
# If you want to add additional steps to any of the
# targets defined in "Makefile.common", be sure to use
# a double-colon in your rule here. For example, to
# print the message "FINISHED AT LAST" after building
# the HTML document version, uncomment the following
# line:
#${DOCNAME}/index.html::
# echo FINISHED AT LAST
From fedora-docs-commits at redhat.com Wed Jan 18 06:43:47 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 01:43:47 -0500
Subject: translation-quick-start-guide translation-quick-start-en.xml, NONE,
1.1
Message-ID: <200601180643.k0I6hl00023005@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22988
Added Files:
translation-quick-start-en.xml
Log Message:
trans-quick
--- NEW FILE translation-quick-start-en.xml ---
%FEDORA-ENTITIES-EN;
]>
Translation Quick Start Guide2005&FORMAL-RHI;Manuel OspinaOspinaManuel
&LEGALNOTICE;
Introduction
This guide intends to be a fast, simple step by step set of instructions to
start contributing with the translation of Fedora Project's software and
documents. Those interested in getting a better understanding of the
translation process involved can see the Translation guide or refer to the
manual of the specific translation tool.
Accounts and subscriptions
To participate in the Fedora Project as a translator you need an account.
You can apply for an account at
http://i18n.redhat.com/cgi-bin/i18n-signup/. You need to provide a
username (login), an e-mail address, a target language -most likely your
native language-, and the public part of your ssh key.
If you do not have a ssh key yet, you can generate one using the following steps:
1. Type in a comand line:
ssh-keygen -t dsa
Accept the default location (~/.ssh/id_dsa) and enter a passphrase.
Note
Do not forget this passphrase as you will need it to access to the CVS
repository.
2. Copy the key to the appropiate file:
cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
3. Change permissions to your key and .ssh directory:
chmod 755 ~/.sshchmod 644 ~/.ssh/authorized_keys
Next, copy and paste the ssh key in the space provided in order to complete the
account application.
There are also two lists where you can discuss translation issues.
fedora-trans-list is a general list to discuss problems that affect all
languages; the second is the language-specific list (ex. fedora-trans-es for
Spanish language) to discuss issues that affect only the individual community of
translators. It is also useful to subscribe to fedora-doc-list to be informed of issues concerning the general documentation.
Translating software
The translatable part of a software package is available in one or more po files. Fedora
Project stores these files in a CVS repository under the directory /translate.
Once your account has been approved, you can download this directory typing the
following instructions in a command line:
export CVS_RSH=sshexport CVSROOT=:ext:[username]@i18.redhat.com:/usr/local/CVScvs -z9 co translate/
All the modules and po files will be downloaded to your machine following the
same hierarchy of the repository. Each directory contains a pot file
(ex. anaconda.pot) and the po files for each language (af.po, de.po, es.po,
etc).
You can check the status of the translations at
http://i18n.redhat.com/cgi-bin/i18n-status.
Choose your language in the dropdown menu or check the
overall status. You can click on each package to view the maintainer and the name
of the last translator of this module. If you want to translate a module,
contact your language-specific list and let your community know you are working
on that module. Afterwards, press [take] in the status page. The
module will be assigned to you. When asked for a password, enter the one you
have received via e-mail after applying for the account.
You can now start translating:
1. Go to the directory of the package you have taken.
cd ~/translate/[package_name]
2. Update the files with the command:
cvs up
3. Translate the po file of your language in a po editor like KBabel,
gtranslator, etc. For example, to open the po file for Spanish in kbabel, type:
kbabel es.po
4. When you finish your work, commit your changes back to the repository:
cvs commit -m 'comments' [lang].po
5. As a last step, release the module in the status page clicking on the
[release] link so other people can work on it.
If you want to proofread your translation as part of the software, follow these steps:
1. Go to the directory of the package you want to proofread:
cd ~/translate/[package_name]
2. Convert the .po file in .mo file with msgfmt:
msgfmt [lang].po
3. Overwrite the existing .mo file in /usr/share/locale/[lang]/LC_MESSAGES/ .
Firstly, make sure to back up the existing file:
cp /usr/share/locale/[lang]/LC_MESSAGES/[package_name].mo [package_name].mo-backupmv [package_name].mo /usr/share/locale/[lang]/LC_MESSAGES/
4. Proofread the package with the translated strings as part of the application:
LANG=[lang] rpm -qi [package_name]
The application related to the translated package will run with the translated strings.
Translating documentation
The Fedora documentation is also stored in a CVS repository under the directory /docs. The
process to download the documentation is similar to the one used to download po
files:
export CVSROOT=:ext:[username]@cvs.fedora.redhat.com:/cvs/docscvs co docs
This will download all the current documents in the directory. If you want to
download only the document you are interested to translate, list the current
documents in the repository and then check out the directory containing the
document you want:
cvs co -ccvs co example-tutorial
The documents are written in xml format (docBook to be precise) and named using
the specific-language locale: example-tutorial-en.xml. If you are planning to
translate directly from the original xml file, you should create the document for your
language; for instance:
cp example-tutorial-en.xml example-tutorial-es.xml
Afterwards you can work on the new copy.
You can also convert the xml files into po files and work with a po editor
like KBabel o gtranslator. To do so, follow these steps:
1. In a terminal, go to the directory of the document you
want to translate:
cd ~/docs/example-tutorial
2. Extract the translatable strings with xml2pot:
xml2pot example-tutorial-en.xml > [lang].po
3. Now you can translate the file using the same application used to translate
software:
kbabel [lang].po
4. Once you finish, it is necessary to convert the translated .po file to .xml file in the target
language with po2xml:
po2xml example-tutorial-en.xml [lang].po > example-tutorial-[lang].xml
As the filter (xml2po) does not include entities in the .po file, you have to
change the language of the document from English:
<article id="example-tutorial" lang="en">to your language:<article id="example-tutorial" lang="es">
When the translated file is ready, add it to the repository:
cvs add example-tutorial-[lang].xmlcvs commit -m 'any comment' example-tutorial-[lang].xml
As a final step, you may have to change the Makefile so the document can be
built in HTML and PDF formats.
Note:
Please advise fedora-doc-list and fedora-trans-[locale] that you are modifying
the Makefile. You should tell your community that you are working on the
translation of this document before you start translating to avoid that
different people work on the same file.
1. In the text editor of your preference, open the Makefile.
vi Makefile
2. Add the locale of the new translation after the other languages as in the
following example:
LANGUAGES = en de [lang]
3. Include also the following lines:
DOCTITLE-[lang] = [name of tutorial]
XMLEXTRAFILES-[lang]=
4. Commit the Makefile
cvs commit -m 'any comment' Makefile
Then, you can build the document in your machine by typing:
make
From fedora-docs-commits at redhat.com Wed Jan 18 06:50:58 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 01:50:58 -0500
Subject: translation-quick-start-guide Makefile, 1.1,
NONE translation-quick-start-en.xml, 1.1, NONE
Message-ID: <200601180650.k0I6ow19023065@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23049
Removed Files:
Makefile translation-quick-start-en.xml
Log Message:
test
--- Makefile DELETED ---
--- translation-quick-start-en.xml DELETED ---
From fedora-docs-commits at redhat.com Wed Jan 18 06:58:27 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 01:58:27 -0500
Subject: translation-quick-start-guide - Imported sources
Message-ID: <200601180658.k0I6wRC1023098@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23083
Log Message:
Status:
Vendor Tag: trans-guide
Release Tags: start
C translation-quick-start-guide/translation-quick-start-en.xml
C translation-quick-start-guide/Makefile
2 conflicts created by this import.
Use the following command to help the merge:
cvs checkout -jtrans-guide:yesterday -jtrans-guide translation-quick-start-guide
From fedora-docs-commits at redhat.com Wed Jan 18 07:19:32 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 02:19:32 -0500
Subject: translation-quick-start-guide Makefile, 1.2,
1.3 translation-quick-start-en.xml, 1.2, 1.3
Message-ID: <200601180719.k0I7JWaK024952@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24927
Added Files:
Makefile translation-quick-start-en.xml
Log Message:
re-adding
Index: Makefile
===================================================================
RCS file: Makefile
diff -N Makefile
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ Makefile 18 Jan 2006 07:19:25 -0000 1.3
@@ -0,0 +1,26 @@
+###############################################################################
+# Makefile for RHLP docs project
+# Created by: Tammy Fox
+# Last edited by: Tommy Reynolds
+# WARNING: need passivetex 1.24 for pdf generation to work
+# License: GPL
+# Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
+###############################################################################
+
+LANGUAGES = en
+DOCBASE = translation-quick-start
+XMLEXTRAFILES-en =
+
+######################################################
+include ../docs-common/Makefile.common
+######################################################
+
+# If you want to add additional steps to any of the
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here. For example, to
+# print the message "FINISHED AT LAST" after building
+# the HTML document version, uncomment the following
+# line:
+#${DOCNAME}/index.html::
+# echo FINISHED AT LAST
Index: translation-quick-start-en.xml
===================================================================
RCS file: translation-quick-start-en.xml
diff -N translation-quick-start-en.xml
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ translation-quick-start-en.xml 18 Jan 2006 07:19:25 -0000 1.3
@@ -0,0 +1,331 @@
+
+
+ %FEDORA-ENTITIES-EN;
+
+
+
+
+
+
+
+
+
+
+ ]>
+
+
+
+ Translation Quick Start Guide
+
+ 2005
+ &FORMAL-RHI;
+ Manuel Ospina
+
+
+
+ Ospina
+ Manuel
+
+
+ &LEGALNOTICE;
+
+
+
+ Introduction
+
+
+ This guide intends to be a fast, simple step by step set of instructions to
+ start contributing with the translation of Fedora Project's software and
+ documents. Those interested in getting a better understanding of the
+ translation process involved can see the Translation guide or refer to the
+ manual of the specific translation tool.
+
+
+
+
+
+ Accounts and subscriptions
+
+
+ To participate in the Fedora Project as a translator you need an account.
+ You can apply for an account at
+ http://i18n.redhat.com/cgi-bin/i18n-signup/. You need to provide a
+ username (login), an e-mail address, a target language -most likely your
+ native language-, and the public part of your ssh key.
+
+
+
+ If you do not have a ssh key yet, you can generate one using the following steps:
+
+
+ 1. Type in a comand line:
+
+
+ ssh-keygen -t dsa
+
+
+ Accept the default location (~/.ssh/id_dsa) and enter a passphrase.
+
+
+Note
+
+Do not forget this passphrase as you will need it to access to the CVS
+repository.
+
+
+
+2. Copy the key to the appropiate file:
+
+
+cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
+
+
+3. Change permissions to your key and .ssh directory:
+
+
+chmod 755 ~/.ssh
+chmod 644 ~/.ssh/authorized_keys
+
+
+Next, copy and paste the ssh key in the space provided in order to complete the
+account application.
+
+
+There are also two lists where you can discuss translation issues.
+fedora-trans-list is a general list to discuss problems that affect all
+languages; the second is the language-specific list (ex. fedora-trans-es for
+Spanish language) to discuss issues that affect only the individual community of
+translators. It is also useful to subscribe to fedora-doc-list to be informed of issues concerning the general documentation.
+
+
+
+
+Translating software
+
+
+The translatable part of a software package is available in one or more po files. Fedora
+Project stores these files in a CVS repository under the directory /translate.
+Once your account has been approved, you can download this directory typing the
+following instructions in a command line:
+
+
+export CVS_RSH=ssh
+export CVSROOT=:ext:[username]@i18.redhat.com:/usr/local/CVS
+cvs -z9 co translate/
+
+
+All the modules and po files will be downloaded to your machine following the
+same hierarchy of the repository. Each directory contains a pot file
+(ex. anaconda.pot) and the po files for each language (af.po, de.po, es.po,
+etc).
+
+
+You can check the status of the translations at
+http://i18n.redhat.com/cgi-bin/i18n-status.
+Choose your language in the dropdown menu or check the
+overall status. You can click on each package to view the maintainer and the name
+of the last translator of this module. If you want to translate a module,
+contact your language-specific list and let your community know you are working
+on that module. Afterwards, press [take] in the status page. The
+module will be assigned to you. When asked for a password, enter the one you
+have received via e-mail after applying for the account.
+
+
+You can now start translating:
+
+
+1. Go to the directory of the package you have taken.
+
+
+cd ~/translate/[package_name]
+
+
+2. Update the files with the command:
+
+
+cvs up
+
+
+3. Translate the po file of your language in a po editor like KBabel,
+gtranslator, etc. For example, to open the po file for Spanish in kbabel, type:
+
+
+kbabel es.po
+
+
+4. When you finish your work, commit your changes back to the repository:
+
+
+cvs commit -m 'comments' [lang].po
+
+
+5. As a last step, release the module in the status page clicking on the
+[release] link so other people can work on it.
+
+
+If you want to proofread your translation as part of the software, follow these steps:
+
+
+1. Go to the directory of the package you want to proofread:
+
+
+cd ~/translate/[package_name]
+
+
+2. Convert the .po file in .mo file with msgfmt:
+
+
+msgfmt [lang].po
+
+
+3. Overwrite the existing .mo file in /usr/share/locale/[lang]/LC_MESSAGES/ .
+Firstly, make sure to back up the existing file:
+
+
+cp /usr/share/locale/[lang]/LC_MESSAGES/[package_name].mo [package_name].mo-backup
+mv [package_name].mo /usr/share/locale/[lang]/LC_MESSAGES/
+
+
+4. Proofread the package with the translated strings as part of the application:
+
+
+LANG=[lang] rpm -qi [package_name]
+
+
+The application related to the translated package will run with the translated strings.
+
+
+
+
+Translating documentation
+
+
+The Fedora documentation is also stored in a CVS repository under the directory /docs. The
+process to download the documentation is similar to the one used to download po
+files:
+
+
+export CVSROOT=:ext:[username]@cvs.fedora.redhat.com:/cvs/docs
+cvs co docs
+
+
+This will download all the current documents in the directory. If you want to
+download only the document you are interested to translate, list the current
+documents in the repository and then check out the directory containing the
+document you want:
+
+
+cvs co -c
+cvs co example-tutorial
+
+
+The documents are written in xml format (docBook to be precise) and named using
+the specific-language locale: example-tutorial-en.xml. If you are planning to
+translate directly from the original xml file, you should create the document for your
+language; for instance:
+
+
+cp example-tutorial-en.xml example-tutorial-es.xml
+
+
+Afterwards you can work on the new copy.
+
+
+You can also convert the xml files into po files and work with a po editor
+like KBabel o gtranslator. To do so, follow these steps:
+
+
+1. In a terminal, go to the directory of the document you
+want to translate:
+
+
+cd ~/docs/example-tutorial
+
+
+2. Extract the translatable strings with xml2pot:
+
+
+xml2pot example-tutorial-en.xml > [lang].po
+
+
+3. Now you can translate the file using the same application used to translate
+software:
+
+
+kbabel [lang].po
+
+
+4. Once you finish, it is necessary to convert the translated .po file to .xml file in the target
+language with po2xml:
+
+
+po2xml example-tutorial-en.xml [lang].po > example-tutorial-[lang].xml
+
+
+As the filter (xml2po) does not include entities in the .po file, you have to
+change the language of the document from English:
+
+<article id="example-tutorial" lang="en">
+to your language:
+<article id="example-tutorial" lang="es">
+
+
+When the translated file is ready, add it to the repository:
+
+
+cvs add example-tutorial-[lang].xml
+cvs commit -m 'any comment' example-tutorial-[lang].xml
+
+
+As a final step, you may have to change the Makefile so the document can be
+built in HTML and PDF formats.
+
+
+Note:
+
+Please advise fedora-doc-list and fedora-trans-[locale] that you are modifying
+the Makefile. You should tell your community that you are working on the
+translation of this document before you start translating to avoid that
+different people work on the same file.
+
+
+
+1. In the text editor of your preference, open the Makefile.
+
+
+vi Makefile
+
+
+2. Add the locale of the new translation after the other languages as in the
+following example:
+
+
+LANGUAGES = en de [lang]
+
+
+3. Include also the following lines:
+
+
+DOCTITLE-[lang] = [name of tutorial]
+XMLEXTRAFILES-[lang]=
+
+
+4. Commit the Makefile
+
+
+cvs commit -m 'any comment' Makefile
+
+
+Then, you can build the document in your machine by typing:
+
+
+make
+
+
+
From fedora-docs-commits at redhat.com Wed Jan 18 07:52:01 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 18 Jan 2006 02:52:01 -0500
Subject: docs-common/packaging info2rpminfo.xsl,1.9,1.10
Message-ID: <200601180752.k0I7q1ti025088@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25070
Modified Files:
info2rpminfo.xsl
Log Message:
Changed from standalone="yes" to standalone="no" because
we are using an external DTD.
Index: info2rpminfo.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/info2rpminfo.xsl,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- info2rpminfo.xsl 16 Jan 2006 15:27:31 -0000 1.9
+++ info2rpminfo.xsl 18 Jan 2006 07:51:53 -0000 1.10
@@ -1,6 +1,6 @@
-
From fedora-docs-commits at redhat.com Wed Jan 18 08:24:44 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 18 Jan 2006 03:24:44 -0500
Subject: docs-common/bin copy-figs,1.4,1.5
Message-ID: <200601180824.k0I8OiVP026999@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26978
Modified Files:
copy-figs
Log Message:
Use better heuristics to include non-conforming figs/ filenames.
Now, files are rejected as not matching the language selection if
they have the pattern "*-??.*" or "*-??_??.*" -- in other words, if
the last dashed comonpent of the filename is either a two-letter
language code or a two-letter language code with a two-letter country
code.
Index: copy-figs
===================================================================
RCS file: /cvs/docs/docs-common/bin/copy-figs,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- copy-figs 13 Dec 2005 16:45:47 -0000 1.4
+++ copy-figs 18 Jan 2006 08:24:37 -0000 1.5
@@ -189,15 +189,15 @@
# language neutral
copyIt=${haveManifest}
case "${bn}" in
- *-${targetLang}.* )
- # Has matching language
- copyIt=yes
- ;;
*-*-* )
# Multiple dashes imply ambiguous filename
copyIt=yes
;;
- *-* )
+ *-${targetLang}.* )
+ # Has matching language
+ copyIt=yes
+ ;;
+ *-??.* | *-??_??.* )
# Doesn't match target language
;;
* )
From fedora-docs-commits at redhat.com Wed Jan 18 08:37:36 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 18 Jan 2006 03:37:36 -0500
Subject: docs-common/bin copy-figs,1.5,1.6
Message-ID: <200601180837.k0I8baYW027072@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27054
Modified Files:
copy-figs
Log Message:
With the "-v" switch, output a note if we find a manifest file.
Index: copy-figs
===================================================================
RCS file: /cvs/docs/docs-common/bin/copy-figs,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- copy-figs 18 Jan 2006 08:24:37 -0000 1.5
+++ copy-figs 18 Jan 2006 08:37:29 -0000 1.6
@@ -140,6 +140,8 @@
fi
)
[ "${DEBUG}" ] || echo >&2 "haveManifest=|${haveManifest}|"
+[ "${VERBOSE}" -a "${haveManifest}" = "yes" ] ||
+ echo >&2 "Using manifest to get file names"
(
if [ "${haveManifest}" = "yes" ]; then
From fedora-docs-commits at redhat.com Wed Jan 18 18:09:39 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 18 Jan 2006 13:09:39 -0500
Subject: docs-common/packaging info2rpminfo.xsl,1.10,1.11
Message-ID: <200601181809.k0II9dBh016463@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16434
Modified Files:
info2rpminfo.xsl
Log Message:
Inserted dummy element at the right place, just after the
colophon. Since it references a dummy "FIXME" worker, the document
will not validate yet, and this is a GOOD thing because it needs
more editing.
Added 'order="newest-first"' attribute to the element,
so that the generated document will have the correct structure.
Index: info2rpminfo.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/info2rpminfo.xsl,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- info2rpminfo.xsl 18 Jan 2006 07:51:53 -0000 1.10
+++ info2rpminfo.xsl 18 Jan 2006 18:09:10 -0000 1.11
@@ -10,6 +10,9 @@
+
+ FIXME
+ CHECK LICENSING BELOWGNU FDL
@@ -22,6 +25,9 @@
+
+ newest-first
+
@@ -71,7 +77,7 @@
PLEASE ADD BOOK/ARTICLE DESCRIPTION TO RPM-INFO
-
+
@@ -105,7 +111,7 @@
-
+GNU FDL1.02005Red Hat, Inc.Manuel OspinaTranslation Quick Start GuideDummy RPM InfoDummy entry
Index: translation-quick-start-en.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- translation-quick-start-en.xml 18 Jan 2006 07:19:25 -0000 1.3
+++ translation-quick-start-en.xml 19 Jan 2006 01:34:20 -0000 1.4
@@ -15,24 +15,13 @@
+
+
]>
-
+
-
- Translation Quick Start Guide
-
- 2005
- &FORMAL-RHI;
- Manuel Ospina
-
-
-
- Ospina
- Manuel
-
-
- &LEGALNOTICE;
-
+
+ &FDP-INFO;
Introduction
@@ -56,7 +45,7 @@
url="http://i18n.redhat.com/cgi-bin/i18n-signup/">
http://i18n.redhat.com/cgi-bin/i18n-signup/. You need to provide a
username (login), an e-mail address, a target language -most likely your
- native language-, and the public part of your ssh key.
+ native language-, and the public part of your ssh key.
@@ -134,7 +123,7 @@
contact your language-specific list and let your community know you are working
on that module. Afterwards, press [take] in the status page. The
module will be assigned to you. When asked for a password, enter the one you
-have received via e-mail after applying for the account.
+have received via e-mail after applying for the account.
You can now start translating:
@@ -228,7 +217,7 @@
The documents are written in xml format (docBook to be precise) and named using
the specific-language locale: example-tutorial-en.xml. If you are planning to
translate directly from the original xml file, you should create the document for your
-language; for instance:
+language; for instance:
cp example-tutorial-en.xml example-tutorial-es.xml
@@ -292,7 +281,7 @@
Please advise fedora-doc-list and fedora-trans-[locale] that you are modifying
the Makefile. You should tell your community that you are working on the
translation of this document before you start translating to avoid that
-different people work on the same file.
+different people work on the same file.
From fedora-docs-commits at redhat.com Thu Jan 19 03:04:31 2006
From: fedora-docs-commits at redhat.com (Manuel Ospina (mospina))
Date: Wed, 18 Jan 2006 22:04:31 -0500
Subject: translation-quick-start-guide rpm-info.xml,1.1,1.2
Message-ID: <200601190304.k0J34WBx002309@cvs-int.fedora.redhat.com>
Author: mospina
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2291
Modified Files:
rpm-info.xml
Log Message:
updated
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-info.xml 19 Jan 2006 01:34:20 -0000 1.1
+++ rpm-info.xml 19 Jan 2006 03:04:01 -0000 1.2
@@ -9,7 +9,8 @@
-
+
@@ -26,7 +27,8 @@
Translation Quick Start Guide
-
+ Quick start guide to start contributing with the translation of Fedora
+ Project.
@@ -34,11 +36,11 @@
- Dummy RPM Info
+ First draft
- Dummy entry
+ First draft
From fedora-docs-commits at redhat.com Thu Jan 19 14:48:42 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 19 Jan 2006 09:48:42 -0500
Subject: docs-common/bin fdp-functions,1.3,1.4
Message-ID: <200601191448.k0JEmgU3025514@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25496/docs-common/bin
Modified Files:
fdp-functions
Log Message:
Provide working alias
Index: fdp-functions
===================================================================
RCS file: /cvs/docs/docs-common/bin/fdp-functions,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fdp-functions 18 Jan 2006 06:41:34 -0000 1.3
+++ fdp-functions 19 Jan 2006 14:48:34 -0000 1.4
@@ -76,3 +76,7 @@
date -d 2006-01-18 +'%a %b %d %Y'
done
}
+
+get_latest_revision() {
+ version $@
+}
From fedora-docs-commits at redhat.com Thu Jan 19 15:31:49 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 19 Jan 2006 10:31:49 -0500
Subject: docs-common/bin copy-figs,1.6,1.7
Message-ID: <200601191531.k0JFVnL9027387@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27369
Modified Files:
copy-figs
Log Message:
Simplify testing through re-ordering.
Index: copy-figs
===================================================================
RCS file: /cvs/docs/docs-common/bin/copy-figs,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- copy-figs 18 Jan 2006 08:37:29 -0000 1.6
+++ copy-figs 19 Jan 2006 15:31:41 -0000 1.7
@@ -140,8 +140,10 @@
fi
)
[ "${DEBUG}" ] || echo >&2 "haveManifest=|${haveManifest}|"
-[ "${VERBOSE}" -a "${haveManifest}" = "yes" ] ||
- echo >&2 "Using manifest to get file names"
+if [ "${haveManifest}" = "yes" ]; then
+ [ "${VERBOSE}" ] ||
+ echo >&2 "Using manifest to get ${targetLang} file names"
+fi
(
if [ "${haveManifest}" = "yes" ]; then
@@ -191,10 +193,6 @@
# language neutral
copyIt=${haveManifest}
case "${bn}" in
- *-*-* )
- # Multiple dashes imply ambiguous filename
- copyIt=yes
- ;;
*-${targetLang}.* )
# Has matching language
copyIt=yes
From fedora-docs-commits at redhat.com Thu Jan 19 17:30:14 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 19 Jan 2006 12:30:14 -0500
Subject: docs-common/bin doctype,NONE,1.1
Message-ID: <200601191730.k0JHUEg1031531@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31510/bin
Added Files:
doctype
Log Message:
Moved from "packaging/" to "bin/" directory.
--- NEW FILE doctype ---
#!/bin/sh
########################################################################
# Script to print the document type, without needing the XML document
# to validate. Get the document type from the first argument to the
# element, which should be either "book" or "article".
#
# Use it like this:
# doctype file.xml
#
# If you know the XML file WILL VALIDATE, you may use the "doctype.xsl"
# script instead. If not, use this one
########################################################################
egrep '^[[:space:]]*
Author: jtr
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31510/packaging
Removed Files:
doctype
Log Message:
Moved from "packaging/" to "bin/" directory.
--- doctype DELETED ---
From fedora-docs-commits at redhat.com Thu Jan 19 19:50:13 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 19 Jan 2006 14:50:13 -0500
Subject: docs-common/packaging fedora-doc-common.spec, 1.5,
1.6 fedora-doc.spec.in.common, 1.2, 1.3
Message-ID: <200601191950.k0JJoDET004004@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3874/docs-common/packaging
Modified Files:
fedora-doc-common.spec fedora-doc.spec.in.common
Log Message:
First cut a integrating the RPM packaging stuff with the
"docs-common/Makefile.common" infrastructure. While this appears to
work *somewhat* with the "example-tutorial", it is certainly not
ready for prime time yet.
TODO:
1) Verify that all generated RPM's have the necessary files inside.
2) Mangle the "../docs-common" strings in Makefiles, *.xml, to
reference the "/usr/share/fedora/doc" ${FDPDIR} so that we don't
need to bugger the RPM checksums of the files by altering them at
RPM install time.
3) Buy a beer all round.
Index: fedora-doc-common.spec
===================================================================
RCS file: /cvs/docs/docs-common/packaging/fedora-doc-common.spec,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-doc-common.spec 30 Dec 2005 07:11:22 -0000 1.5
+++ fedora-doc-common.spec 19 Jan 2006 19:50:05 -0000 1.6
@@ -32,12 +32,12 @@
%install
rm -rf $RPM_BUILD_ROOT
install -d -m 755 $RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/bin/
-for i in xmlformat xmldiff copy-figs bulkbuild tidy-bowl
+for i in xmlformat xmldiff copy-figs tidy-bowl fdpsh doctype
do
install -m 755 $RPM_BUILD_DIR/%{name}-%{release}/bin/${i} \
$RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/bin/
done
-for i in xmlformat-fdp.conf xmldiff.pl active
+for i in xmlformat-fdp.conf xmldiff.pl active fdp-functions
do
install -m 644 $RPM_BUILD_DIR/%{name}-%{release}/bin/${i} \
$RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/bin/
Index: fedora-doc.spec.in.common
===================================================================
RCS file: /cvs/docs/docs-common/packaging/fedora-doc.spec.in.common,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-doc.spec.in.common 21 Nov 2005 00:37:58 -0000 1.2
+++ fedora-doc.spec.in.common 19 Jan 2006 19:50:05 -0000 1.3
@@ -25,9 +25,12 @@
%prep
%setup -q -n %{docbase}-%{version}
+# FIXME: Need to do this remapping in the RPM build section, since it
+# causes "rpm -V foo" to fail, even if it's done immediately after an
+# install...
for i in $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}*.xml
do
- %{__sed} -i 's!../docs-common/!../../docs-common/!' "$i"
+ %{__sed} -i 's!../docs-common/!/usr/share/fedora/doc/docs-common/!' "$i"
done
From fedora-docs-commits at redhat.com Thu Jan 19 19:49:56 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 19 Jan 2006 14:49:56 -0500
Subject: docs-common Makefile.common,1.32,1.33
Message-ID: <200601191950.k0JJoQaZ004018@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3874/docs-common
Modified Files:
Makefile.common
Log Message:
First cut a integrating the RPM packaging stuff with the
"docs-common/Makefile.common" infrastructure. While this appears to
work *somewhat* with the "example-tutorial", it is certainly not
ready for prime time yet.
TODO:
1) Verify that all generated RPM's have the necessary files inside.
2) Mangle the "../docs-common" strings in Makefiles, *.xml, to
reference the "/usr/share/fedora/doc" ${FDPDIR} so that we don't
need to bugger the RPM checksums of the files by altering them at
RPM install time.
3) Buy a beer all round.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- Makefile.common 17 Jan 2006 02:14:49 -0000 1.32
+++ Makefile.common 19 Jan 2006 19:49:48 -0000 1.33
@@ -22,6 +22,8 @@
# providing additional rules, also marked with double-colons, in the
# document Makefile.
#########################################################################
+# N.B.: Don't use "$@" in a template. It doesn't work. I tried ;-(
+#########################################################################
# Allow client document to provide "Make.paths" file to locate our files
# This is a "silent include", so if it's missing there is no problem.
# This file, if present, must be in the DOCUMENT directory, not here in
@@ -49,8 +51,8 @@
ifeq (${HTMLCSS},)
HTMLCSS = ${FDPDIR}/docs-common/css/fedora-draft.css
endif
-ifeq (${HTMLCSSEXTRA},)
-HTMLCSSEXTRA = ${FDPDIR}/docs-common/images/watermark-${LANG}.png
+ifeq (${DRAFT},)
+DRAFT = yes
endif
ifeq (${RPMINFO},)
RPMINFO = ${PWD}/rpm-info.xml
@@ -61,13 +63,34 @@
XMLTO =xmlto
# Let's also do this for xsltproc(1).
XSLTPROC=xsltproc
-XMLFORMAT=$(FDPDIR)/docs-common/bin/xmlformat
+XMLFORMAT=xmlformat
XMLFOPTS=-f $(FDPDIR)/docs-common/bin/xmlformat-fdp.conf
#########################################################################
# Use our very own "docs-common/bin/fdpsh" as the command interpreter
# This automatically has ${FDPBIN} as first in the ${PATH}
SHELL =${FDPBIN}/fdpsh
#########################################################################
+VERSION:=$(shell version doc)
+RELEASE:=$(shell version rpm)
+PWD :=$(shell /bin/pwd)
+#########################################################################
+RPMFLAGS=--define "docbase $(DOCBASE)" \
+ --define "version $(VERSION)" \
+ --define "_topdir $(PWD)/rpm" \
+ --define "fdpdir $(FDPDIR)"
+
+SPECFILE=fedora-doc-$(DOCBASE).spec
+ifeq (${RPMDEBUG},1)
+RPMDFLAG = -vv
+endif
+RPMJUNK = \
+ --define "_sourcedir $(PWD)" \
+ --define "_rpmdir $(PWD)" \
+ --define "_srcrpmdir $(PWD)" \
+ --define "_specdir $(PWD)" \
+ --define "_rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm" \
+ FIXME
+#########################################################################
# PUT NO TARGETS BEFORE THIS ONE, not even in your base Makefile
# In a properly-constructed Makefile, this will be the default target
@@ -99,10 +122,11 @@
mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
cp ${HTMLCSS} $(DOCBASE)-$(1)/fedora.css
- [ -z "${HTMLCSSEXTRA}" ] || \
- cp ${HTMLCSSEXTRA} $(DOCBASE)-$(1)/watermark.png
+ifeq (${DRAFT},"yes")
+ cp ${FDPDIR}/docs-common/images/watermark-$(1).png
+endif
[ ! -d figs ] || copy-figs -v -f '*.png' \
- -l ${LANG} figs $(DOCBASE)-$(1)
+ -l $(1) figs $(DOCBASE)-$(1)
endef
#
$(foreach LANG,${LANGUAGES},$(eval $(call HTML_template,${LANG})))
@@ -128,16 +152,17 @@
html-nochunks:: $(foreach LANG,${LANGUAGES},html-nochunks-$(LANG))
#
#########################################################################
-# For each language in ${LANGUAGES}, build a tarball of the HTML files.
+# For each language in ${LANGUAGES}, build a tarball of the HTML and
+# image files. Any ".eps" files are ignored.
#
-define TAR_template
+define HTMLTAR_template
${DOCBASE}-$(1).tar.gz:: ${DOCBASE}-$(1)/index.html
tar -zc --exclude '*.eps' -f ${DOCBASE}-$(1).tar.gz ${DOCBASE}-$(1)
endef
#
tarball:: $(foreach LANG,${LANGUAGES},$(DOCBASE)-$(LANG).tar.gz)
-$(foreach LANG,${LANGUAGES},$(eval $(call TAR_template,${LANG})))
+$(foreach LANG,${LANGUAGES},$(eval $(call HTMLTAR_template,${LANG})))
#
#########################################################################
# For each language in ${LANGUAGES}, generate an Adobe Portable Document
@@ -157,7 +182,6 @@
define CLEAN_template
${DOCBASE}-$(1)-clean::
${RM} fdp-info-$(1).xml
- ${RM} fedora.css watermark-${LANG}.png watermark.png
endef
#
$(foreach LANG,${LANGUAGES},$(eval $(call CLEAN_template,${LANG})))
@@ -171,6 +195,9 @@
${RM} -r ${DOCBASE}-$(1).html stylesheet-images
${RM} -r ${DOCBASE}-$(1).pdf
${RM} -r ${DOCBASE}-$(1).tar.gz
+ ${RM} *-$(1).omf
+ ${RM} *-$(1).desktop
+ ${RM} fedora.css watermark-${LANG}.png watermark.png
endef
#
$(foreach LANG,${LANGUAGES},$(eval $(call DISTCLEAN_template,${LANG})))
@@ -198,17 +225,17 @@
#########################################################################
# The "fdp-info-${LANG}.xml" file contains the or
# stanza. It is automatically generated from data in the
-# "rpm-info.xml" file.
+# "rpm-info.xml" file whenever that file changes.
#
define fdp-info_template
fdp-info-$(1).xml:: $(RPMINFO)
${XSLTPROC} --stringparam lang $(1) \
--stringparam doctype $(shell \
- ${FDPDIR}/docs-common/packaging/doctype \
- $(DOCBASE)-$(1).xml \
+ doctype $(DOCBASE)-$(1).xml \
) ${FDPDIR}/docs-common/packaging/bookinfo.xsl \
$(RPMINFO) | \
- $(XMLFORMAT) $(XMLFOPTS) > fdp-info-$(1).xml
+ $(XMLFORMAT) $(XMLFOPTS) > fdp-info-$(1).xml.tmp && \
+ move-if-change fdp-info-$(1).xml.tmp fdp-info-$(1).xml
endef
#
$(foreach LANG,${LANGUAGES},$(eval $(call fdp-info_template,${LANG})))
@@ -234,3 +261,111 @@
#########################################################################
# End of Makefile.common
#########################################################################
+
+
+clean::
+ ${RM} $(DOCBASE)-$(VERSION)*.src.tar.gz
+ ${RM} -r $(DOCBASE)-$(VERSION)/
+ ${RM} *.omf *.desktop $(SPECFILE)
+ ${RM} *~
+
+distclean::
+ ${RM} -r rpm
+ ${RM} *.rpm
+ ${RM} *.omf
+ ${RM} *.desktop
+ ${RM} *.spec
+ ${RM} *.src.tar.gz
+
+spec:: ${SPECFILE}
+
+${SPECFILE}:: ${RPMINFO}
+ $(XSLTPROC) --stringparam docbase "${DOCBASE}" \
+ ../docs-common/packaging/spec.xsl ${RPMINFO} \
+ >$@.tmp && move-if-change $@.tmp $@
+
+
+gnome.desktop:: fedora-doc-${DOCBASE}-gnome.desktop
+
+fedora-doc-${DOCBASE}-gnome.desktop:: ${RPMINFO}
+ $(XSLTPROC) ../docs-common/packaging/gnome-desktop.xsl \
+ ${RPMINFO} >$@.tmp && move-if-change $@.tmp $@
+
+kde.desktop:: fedora-doc-${DOCBASE}-kde.desktop
+
+fedora-doc-${DOCBASE}-kde.desktop:: ${RPMINFO}
+ $(XSLTPROC) ../docs-common/packaging/kde-desktop.xsl \
+ ${RPMINFO} >$@.tmp && move-if-change $@.tmp $@
+
+khelp.desktop:: fedora-doc-${DOCBASE}-khelp.desktop
+
+fedora-doc-${DOCBASE}-khelp.desktop:: ${RPMINFO}
+ $(XSLTPROC) ../docs-common/packaging/khelpcenter-plugin.xsl \
+ ${RPMINFO} >$@.tmp && move-if-change $@.tmp $@
+
+
+define omf_template
+omf-$(1):: fedora-doc-${DOCBASE}-$(1).omf
+
+fedora-doc-${DOCBASE}-$(1).omf:: ${RPMINFO}
+ ${XSLTPROC} --stringparam docbase "${DOCBASE}" \
+ ../docs-common/packaging/omf.xsl ${RPMINFO} | \
+ $(XMLFORMAT) $(XMLFOPTS) >fedora-doc-${DOCBASE}-$(1).omf.tmp && \
+ move-if-change fedora-doc-${DOCBASE}-$(1).omf.tmp fedora-doc-${DOCBASE}-$(1).omf
+endef
+
+fedora-doc-${DOCBASE}-C.omf:: fedora-doc-${DOCBASE}-en.omf
+ cp fedora-doc-$(DOCBASE)-en.omf $@
+
+$(foreach LANG,${LANGUAGES},$(eval $(call omf_template,${LANG})))
+
+omf:: $(foreach LANG,${LANGUAGES},omf-$(LANG)) fedora-doc-${DOCBASE}-C.omf
+
+
+$(DOCBASE)-$(VERSION).src.tar.gz::
+ ${MAKE} fdp-info
+ ${MAKE} gnome.desktop
+ ${MAKE} kde.desktop
+ ${MAKE} khelp.desktop
+ ${MAKE} omf
+ mkdir $(DOCBASE)-$(VERSION)
+ find * '(' \
+ -name '.*' \
+ -o -name 'CVS' \
+ -o -name 'rpm' \
+ -o -name '*.rpm' \
+ -o -name '#*' \
+ -o -name '*~' \
+ -o -name '*.tar.gz' \
+ -o -name '*.tmp' \
+ -o -name '${DOCBASE}-${VERSION}' \
+ ')' -prune -o -print | cpio -pamdv $(DOCBASE)-$(VERSION)
+ tar -zcvf $@ $(DOCBASE)-$(VERSION)/
+ ${RM} -r $(DOCBASE)-$(VERSION)
+
+package-prep::
+ ${MAKE} distclean
+ ${MAKE} ${DOCBASE}-${VERSION}.src.tar.gz
+ ${MAKE} ${SPECFILE}
+ ${MAKE} omf
+ ${MAKE} kde.desktop
+ ${MAKE} khelp.desktop
+ ${RM} -r rpm
+ mkdir -p rpm/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
+ mkdir -p rpm/RPMS/{i386,i486,i586,i686,noarch,ppc,x86_64}
+ cp -f $(DOCBASE)-$(VERSION).src.tar.gz rpm/SOURCES/
+ cp -f ${SPECFILE} rpm/SPECS
+ cp -f *.omf *.desktop rpm/SOURCES
+
+rpm::
+ ${RM} *.rpm
+ ${MAKE} package-prep
+ rpmbuild -ba $(RPMDFLAG) $(RPMFLAGS) rpm/SPECS/$(SPECFILE)
+ ln rpm/SRPMS/*.rpm rpm/RPMS/noarch/*.rpm .
+ ls *.rpm
+
+
+showvars::
+ @echo "VERSION=$(VERSION)"
+ @echo "RELEASE=$(RELEASE)"
+ @echo "PWD=$(PWD)"
From fedora-docs-commits at redhat.com Thu Jan 19 19:50:01 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 19 Jan 2006 14:50:01 -0500
Subject: docs-common/bin db2rpm-info,1.2,1.3
Message-ID: <200601191950.k0JJoVQl004031@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3874/docs-common/bin
Modified Files:
db2rpm-info
Log Message:
First cut a integrating the RPM packaging stuff with the
"docs-common/Makefile.common" infrastructure. While this appears to
work *somewhat* with the "example-tutorial", it is certainly not
ready for prime time yet.
TODO:
1) Verify that all generated RPM's have the necessary files inside.
2) Mangle the "../docs-common" strings in Makefiles, *.xml, to
reference the "/usr/share/fedora/doc" ${FDPDIR} so that we don't
need to bugger the RPM checksums of the files by altering them at
RPM install time.
3) Buy a beer all round.
Index: db2rpm-info
===================================================================
RCS file: /cvs/docs/docs-common/bin/db2rpm-info,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- db2rpm-info 6 Jan 2006 17:40:57 -0000 1.2
+++ db2rpm-info 19 Jan 2006 19:49:54 -0000 1.3
@@ -1,8 +1,23 @@
-#!/bin/sh
-BINDIR=`dirname $0`
+#!/bin/zsh
+ME=$(basename $0)
+BINDIR=$(dirname $0)
+USAGE="usage: ${ME} [-o ofile] document.xml"
+ofile=
+while getopts o: c
+do
+ case "${c}" in
+ o) ofile="${OPTARG}";;
+ *) echo "${USAGE}" >&2; exit 1;;
+ esac
+done
+shift $(expr ${OPTIND} - 1)
if [ $# -ne 1 ]; then
- echo "usage: `basename $0` docfile.xml" >&2
+ echo "${USAGE}" >&2
exit 1
fi
+if [ "${ofile}" ]; then
+ rm -f "${ofile}"
+ exec >"${ofile}"
+fi
xsltproc ${BINDIR}/../packaging/info2rpminfo.xsl $1 |
${BINDIR}/xmlformat -f ${BINDIR}/xmlformat-fdp.conf
From fedora-docs-commits at redhat.com Thu Jan 19 19:50:07 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 19 Jan 2006 14:50:07 -0500
Subject: docs-common/common fedora-entities-en.ent,1.13,1.14
Message-ID: <200601191950.k0JJobWZ004035@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3874/docs-common/common
Modified Files:
fedora-entities-en.ent
Log Message:
First cut a integrating the RPM packaging stuff with the
"docs-common/Makefile.common" infrastructure. While this appears to
work *somewhat* with the "example-tutorial", it is certainly not
ready for prime time yet.
TODO:
1) Verify that all generated RPM's have the necessary files inside.
2) Mangle the "../docs-common" strings in Makefiles, *.xml, to
reference the "/usr/share/fedora/doc" ${FDPDIR} so that we don't
need to bugger the RPM checksums of the files by altering them at
RPM install time.
3) Buy a beer all round.
Index: fedora-entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- fedora-entities-en.ent 17 Jan 2006 02:25:49 -0000 1.13
+++ fedora-entities-en.ent 19 Jan 2006 19:49:59 -0000 1.14
@@ -1,8 +1,8 @@
-
-
+
+
-
-
@@ -23,298 +21,454 @@
&FDP-INFO;
-
+ Introduction
-
+
- This guide intends to be a fast, simple step by step set of instructions to
- start contributing with the translation of Fedora Project's software and
- documents. Those interested in getting a better understanding of the
- translation process involved can see the Translation guide or refer to the
- manual of the specific translation tool.
+ This guide is a fast, simple, step-by-step set of instructions for
+ translating &FP; software and documents. If you are interested in
+ better understanding the translation process involved, refer to
+ the Translation guide or the manual of the specific translation
+ tool.
+
+
-
-
-
+ Accounts and subscriptions
- To participate in the Fedora Project as a translator you need an account.
- You can apply for an account at
- http://i18n.redhat.com/cgi-bin/i18n-signup/. You need to provide a
- username (login), an e-mail address, a target language -most likely your
- native language-, and the public part of your ssh key.
+ To participate in the &FP; as a translator you need an account.
+ You can apply for an account at . 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.
- If you do not have a ssh key yet, you can generate one using the following steps:
-
-
- 1. Type in a comand line:
-
-
- ssh-keygen -t dsa
-
-
- Accept the default location (~/.ssh/id_dsa) and enter a passphrase.
+ If you do not have a SSH key yet, you can generate one using the
+ following steps:
-
-Note
-
-Do not forget this passphrase as you will need it to access to the CVS
-repository.
-
-
-
-2. Copy the key to the appropiate file:
-
+
+
+
+
+ Type in a comand line:
+
+
+
+ssh-keygen -t dsa
+
+
+
+ Accept the default location
+ (~/.ssh/id_dsa) and enter a passphrase.
+
+
+ Note
+
+ Do not forget this passphrase as you will need it to access
+ to the CVS repository.
+
+
+
+
+
+
+
+
+
+ Change permissions to your key and .ssh
+ directory:
+
+
chmod 755 ~/.ssh
-chmod 644 ~/.ssh/authorized_keys
+
-
-Next, copy and paste the ssh key in the space provided in order to complete the
-account application.
-
-
-There are also two lists where you can discuss translation issues.
-fedora-trans-list is a general list to discuss problems that affect all
-languages; the second is the language-specific list (ex. fedora-trans-es for
-Spanish language) to discuss issues that affect only the individual community of
-translators. It is also useful to subscribe to fedora-doc-list to be informed of issues concerning the general documentation.
-
-
-
-
-Translating software
-
-
-The translatable part of a software package is available in one or more po files. Fedora
-Project stores these files in a CVS repository under the directory /translate.
-Once your account has been approved, you can download this directory typing the
-following instructions in a command line:
-
+
+
+
+
+ Copy and paste the ssh key in the space provided in order to
+ complete the account application.
+
+
+
+
+ There are also two lists where you can discuss translation issues.
+ The first is fedora-trans-list, a general
+ list to discuss problems that affect all languages. Refer to
+
+ for more information. The second is the language-specific list,
+ such as fedora-trans-es for Spanish
+ translators, to discuss issues that affect only the individual
+ community of translators.
+
+
+ You may also find it useful to subscribe to
+ fedora-docs-list to stay informed about
+ general documentation issues.
+
+
+
+
+ Translating software
+
+
+ The translatable part of a software package is available in one or
+ more po files. The &FP; stores these files in
+ a CVS repository under the directory
+ translate/. Once your account has been
+ approved, download this directory typing the following
+ instructions in a command line:
+
+
export CVS_RSH=ssh
-export CVSROOT=:ext:[username]@i18.redhat.com:/usr/local/CVS
+export CVSROOT=:ext:username@i18.redhat.com:/usr/local/CVScvs -z9 co translate/
-
-All the modules and po files will be downloaded to your machine following the
-same hierarchy of the repository. Each directory contains a pot file
-(ex. anaconda.pot) and the po files for each language (af.po, de.po, es.po,
-etc).
-
-
-You can check the status of the translations at
-http://i18n.redhat.com/cgi-bin/i18n-status.
-Choose your language in the dropdown menu or check the
-overall status. You can click on each package to view the maintainer and the name
-of the last translator of this module. If you want to translate a module,
-contact your language-specific list and let your community know you are working
-on that module. Afterwards, press [take] in the status page. The
-module will be assigned to you. When asked for a password, enter the one you
-have received via e-mail after applying for the account.
-
-
-You can now start translating:
-
-
-1. Go to the directory of the package you have taken.
-
-
-cd ~/translate/[package_name]
-
-
-2. Update the files with the command:
-
+
+
+ These commands download all the modules and
+ .po files to your machine following the same
+ hierarchy of the repository. Each directory contains a
+ .pot file, such as
+ anaconda.pot, and the
+ .po files for each language, such as
+ zh_CN.po, de.po, and so
+ forth.
+
+
+ You can check the status of the translations at . Choose your
+ language in the dropdown menu or check the overall status. Select
+ a package to view the maintainer and the name of the last
+ translator of this module. If you want to translate a module,
+ contact your language-specific list and let your community know
+ you are working on that module. Afterwards, select
+ take in the status page. The module is then
+ assigned to you. At the password prompt, enter the one you
+ received via e-mail when you applied for your account.
+
+
+ You can now start translating.
+
+
+
+
+ Go to the directory of the package you have taken.
+
+
+
+cd ~/translate/package_name
+
+
+
+
+
+ Update the files with the following command:
+
+
cvs up
-
-3. Translate the po file of your language in a po editor like KBabel,
-gtranslator, etc. For example, to open the po file for Spanish in kbabel, type:
-
+
+
+
+
+ Translate the po file of your language in a po editor such as
+ KBabel or
+ gtranslator. For example, to open
+ the .po file for Spanish in
+ KBabel, type:
+
+
kbabel es.po
-
-4. When you finish your work, commit your changes back to the repository:
-
-
-cvs commit -m 'comments' [lang].po
-
-
-5. As a last step, release the module in the status page clicking on the
-[release] link so other people can work on it.
-
-
-If you want to proofread your translation as part of the software, follow these steps:
-
-
-1. Go to the directory of the package you want to proofread:
-
-
-cd ~/translate/[package_name]
-
-
-2. Convert the .po file in .mo file with msgfmt:
-
-
-msgfmt [lang].po
-
-
-3. Overwrite the existing .mo file in /usr/share/locale/[lang]/LC_MESSAGES/ .
-Firstly, make sure to back up the existing file:
-
-
-cp /usr/share/locale/[lang]/LC_MESSAGES/[package_name].mo [package_name].mo-backup
-mv [package_name].mo /usr/share/locale/[lang]/LC_MESSAGES/
-
-
-4. Proofread the package with the translated strings as part of the application:
-
-
-LANG=[lang] rpm -qi [package_name]
-
-
-The application related to the translated package will run with the translated strings.
-
-
-
-
-Translating documentation
-
-
-The Fedora documentation is also stored in a CVS repository under the directory /docs. The
-process to download the documentation is similar to the one used to download po
-files:
-
+
+
+
+
+ When you finish your work, commit your changes back to the
+ repository:
+
+
+
+cvs commit -m 'comments' lang.po
+
+
+
+
+
+ As a last step, click the release link on
+ the status page to release the module so other people can work
+ on it.
+
+
+
+
+ If you want to proofread your translation as part of the software,
+ follow these steps:
+
+
+
+
+ Go to the directory of the package you want to proofread:
+
+
+
+cd ~/translate/package_name
+
+
+
+
+
+ Convert the .po file in
+ .mo file with msgfmt:
+
+
-export CVSROOT=:ext:[username]@cvs.fedora.redhat.com:/cvs/docs
+msgfmt lang.po
+
+
+
+
+
+ Overwrite the existing .mo file in
+ /usr/share/locale/lang/LC_MESSAGES/.
+ First, back up the existing file:
+
+
+
+cp /usr/share/locale/lang/LC_MESSAGES/package_name.mo package_name.mo-backup
+mv package_name.mo /usr/share/locale/lang/LC_MESSAGES/
+
+
+
+
+
+ Proofread the package with the translated strings as part of
+ the application:
+
+
+
+LANG=lang rpm -qi package_name
+
+
+
+
+
+ The application related to the translated package will run with
+ the translated strings.
+
+
+
+
+ Translating documentation
+
+
+ The Fedora documentation is also stored in a CVS repository under
+ the directory docs/. The process to download
+ the documentation is similar to the one used to download
+ .po files:
+
+
+
+export CVSROOT=:ext:username@cvs.fedora.redhat.com:/cvs/docscvs co docs
-
-This will download all the current documents in the directory. If you want to
-download only the document you are interested to translate, list the current
-documents in the repository and then check out the directory containing the
-document you want:
-
+
+
+ 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 docs-common module to
+ check document validity for building.
+
+
cvs co -c
-cvs co example-tutorial
+cvs co example-tutorial docs-common
+
+
+
+ The documents are written in DocBook XML format and named using
+ the specific-language locale, such as
+ example-tutorial-en.xml. If you plan to
+ translate directly from the original XML file, you should create
+ the document for your language:
+
+
+
+cp example-tutorial-en.xml example-tutorial-es.xml
-
-The documents are written in xml format (docBook to be precise) and named using
-the specific-language locale: example-tutorial-en.xml. If you are planning to
-translate directly from the original xml file, you should create the document for your
-language; for instance:
-
-
-cp example-tutorial-en.xml example-tutorial-es.xml
-
-
-Afterwards you can work on the new copy.
-
-
-You can also convert the xml files into po files and work with a po editor
-like KBabel o gtranslator. To do so, follow these steps:
-
-
-1. In a terminal, go to the directory of the document you
-want to translate:
-
+
+
+ Afterwards you can work on the new copy.
+
+
+ You can also convert the XML files into .po
+ files and work with a .po editor like
+ KBabel or
+ gtranslator. To do so, follow these
+ steps:
+
+
+
+
+ In a terminal, go to the directory of the document you want to
+ translate:
+
+
cd ~/docs/example-tutorial
-
-2. Extract the translatable strings with xml2pot:
-
-
-xml2pot example-tutorial-en.xml > [lang].po
-
-
-3. Now you can translate the file using the same application used to translate
-software:
-
-
-kbabel [lang].po
-
-
-4. Once you finish, it is necessary to convert the translated .po file to .xml file in the target
-language with po2xml:
-
-
-po2xml example-tutorial-en.xml [lang].po > example-tutorial-[lang].xml
-
-
-As the filter (xml2po) does not include entities in the .po file, you have to
-change the language of the document from English:
-
-<article id="example-tutorial" lang="en">
-to your language:
-<article id="example-tutorial" lang="es">
-
-
-When the translated file is ready, add it to the repository:
-
-
-cvs add example-tutorial-[lang].xml
-cvs commit -m 'any comment' example-tutorial-[lang].xml
-
-
-As a final step, you may have to change the Makefile so the document can be
-built in HTML and PDF formats.
-
-
-Note:
-
-Please advise fedora-doc-list and fedora-trans-[locale] that you are modifying
-the Makefile. You should tell your community that you are working on the
-translation of this document before you start translating to avoid that
-different people work on the same file.
-
-
-
-1. In the text editor of your preference, open the Makefile.
-
+
+
+
+
+ Extract the translatable strings with xml2pot:
+
+
+
+xml2pot example-tutorial-en.xml > lang.po
+
+
+
+
+
+ Now you can translate the file using the same application used
+ to translate software:
+
+
+
+kbabel lang.po
+
+
+
+
+
+ Once you finish, it is necessary to convert the translated
+ .po file to .xml
+ file in the target language with po2xml:
+
+
+
+po2xml example-tutorial-en.xml lang.po > example-tutorial-lang.xml
+
+
+
+
+
+ The xml2po filter does not include entities
+ in the .po file. You must change the
+ language of the document. Locate a line like the following near
+ the top of the document:
+
+
+
+<article id="example-tutorial" lang="en">
+
+
+ Change the attribute to your language:
+
+
+<article id="example-tutorial" lang="es">
+
+
+
+ When the translated file is ready, add it to the repository:
+
+
+
+cvs add example-tutorial-lang.xml
+cvs commit -m 'Any comment' example-tutorial-lang.xml
+
+
+
+ You may have to change the Makefile so the
+ document can be built in HTML and PDF formats.
+
+
+ Note:
+
+ Please advise the community through fedora-doc-list and
+ fedora-trans-locale that you are
+ modifying the Makefile. 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.
+
+
+
+
+
+
+ In the text editor of your preference, open the
+ Makefile.
+
+
vi Makefile
-
-2. Add the locale of the new translation after the other languages as in the
-following example:
-
-
-LANGUAGES = en de [lang]
-
-
-3. Include also the following lines:
-
-
-DOCTITLE-[lang] = [name of tutorial]
-XMLEXTRAFILES-[lang]=
-
-
-4. Commit the Makefile
-
-
-cvs commit -m 'any comment' Makefile
-
-
-Then, you can build the document in your machine by typing:
-
+
+
+
+ Add the locale of the new translation after the other
+ languages as in the following example:
+
+
+
+LANGUAGES = en de lang
+
+
+
+
+
+ Commit the Makefile.
+
+
-make
+cvs commit -m 'Any comment' Makefile
-
+
+
+
+
+ Then, you can build the document in your langugage by typing:
+
+
+
+make html-lang
+
+
+
+
+
+
+
+
+
From fedora-docs-commits at redhat.com Sat Jan 21 02:37:34 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Fri, 20 Jan 2006 21:37:34 -0500
Subject: translation-quick-start-guide translation-quick-start-en.xml, 1.5,
1.6
Message-ID: <200601210237.k0L2bYE7004315@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4297
Modified Files:
translation-quick-start-en.xml
Log Message:
Fix a couple goofs on my part and retag for clarity
Index: translation-quick-start-en.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/translation-quick-start-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- translation-quick-start-en.xml 21 Jan 2006 02:35:00 -0000 1.5
+++ translation-quick-start-en.xml 21 Jan 2006 02:37:27 -0000 1.6
@@ -390,7 +390,7 @@
Change the attribute to your language:
-<article id="example-tutorial" lang="es">
+<article id="example-tutorial" lang="es">
@@ -436,7 +436,7 @@
-LANGUAGES = en de lang
+LANGUAGES = en de lang
From fedora-docs-commits at redhat.com Sat Jan 21 02:48:05 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Fri, 20 Jan 2006 21:48:05 -0500
Subject: docs-common/bin insert-changelog,1.5,1.6
Message-ID: <200601210248.k0L2m5AP004366@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4348/docs-common/bin
Modified Files:
insert-changelog
Log Message:
Heh, maybe we mean month instead of minute here...
Index: insert-changelog
===================================================================
RCS file: /cvs/docs/docs-common/bin/insert-changelog,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- insert-changelog 16 Jan 2006 23:07:33 -0000 1.5
+++ insert-changelog 21 Jan 2006 02:47:58 -0000 1.6
@@ -25,7 +25,7 @@
NUMBER=1
REVDESC="an integer release number"
elif test $ROLE = "doc"; then
- REVDATE=`date +"%Y-%M-%d"`
+ REVDATE=`date +"%Y-%m-%d"`
ZEROREV=0.0 # unlikely, but you never know
REVDESC="a decimal version number"
else
From fedora-docs-commits at redhat.com Sat Jan 21 02:48:26 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Fri, 20 Jan 2006 21:48:26 -0500
Subject: translation-quick-start-guide rpm-info.xml,1.2,1.3
Message-ID: <200601210248.k0L2mQXI004391@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4373
Modified Files:
rpm-info.xml
Log Message:
Update rpm-info
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.xml 19 Jan 2006 03:04:01 -0000 1.2
+++ rpm-info.xml 21 Jan 2006 02:48:19 -0000 1.3
@@ -1,46 +1,41 @@
-
-
-
-
-
-
-
-
-
-
+
+
-
+ GNU FDL1.02005
+ 2006Red Hat, Inc.Manuel Ospina
+
+ 2006
+ Paul W. Frields
+ Translation Quick Start Guide
- Quick start guide to start contributing with the translation of Fedora
- Project.
+ Quick start guide to providing translations on the Fedora Project.
-
-
- First draft
+
+
+ First round of editing.
-
+
- First draft
+ First draft
From fedora-docs-commits at redhat.com Sat Jan 21 05:21:41 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 21 Jan 2006 00:21:41 -0500
Subject: docs-common/css fedora-draft.css,1.1,1.2 fedora-plain.css,1.1,1.2
Message-ID: <200601210521.k0L5LfJa010100@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10080
Modified Files:
fedora-draft.css fedora-plain.css
Log Message:
Unclutter procedures that include screen elements per step
Index: fedora-draft.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora-draft.css,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-draft.css 23 Nov 2005 06:37:03 -0000 1.1
+++ fedora-draft.css 21 Jan 2006 05:21:33 -0000 1.2
@@ -133,6 +133,9 @@
/* prevent inheritance */
margin-bottom: 0em;
}
+.procedure ol li pre {
+ margin-bottom: 1em;
+}
.itemizedlist ul li {
margin-bottom: 0.5em;
Index: fedora-plain.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora-plain.css,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-plain.css 1 Dec 2005 21:10:57 -0000 1.1
+++ fedora-plain.css 21 Jan 2006 05:21:33 -0000 1.2
@@ -135,7 +135,9 @@
/* prevent inheritance */
margin-bottom: 0em;
}
-
+.procedure ol li pre {
+ margin-bottom: 1em;
+}
.itemizedlist ul li {
margin-bottom: 0.5em;
}
From fedora-docs-commits at redhat.com Sat Jan 21 14:30:34 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 21 Jan 2006 09:30:34 -0500
Subject: docs-common/bin fdp-functions,1.5,1.6
Message-ID: <200601211430.k0LEUZw6028454@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28436
Modified Files:
fdp-functions
Log Message:
De-bungle the date(1) command within the for-loop to actually use
the date from the command line. Oh, well, it was late at night...
Index: fdp-functions
===================================================================
RCS file: /cvs/docs/docs-common/bin/fdp-functions,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fdp-functions 20 Jan 2006 17:36:37 -0000 1.5
+++ fdp-functions 21 Jan 2006 14:30:26 -0000 1.6
@@ -73,7 +73,7 @@
if [ ${multi} -eq 1 ]; then
echo -ne "${x}\t"
fi
- date -d 2006-01-18 +'%a %b %d %Y'
+ date -d "${x}" +'%a %b %d %Y'
done
}
From fedora-docs-commits at redhat.com Sat Jan 21 18:47:27 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 21 Jan 2006 13:47:27 -0500
Subject: docs-common/bin tidy-bowl,1.4,1.5
Message-ID: <200601211847.k0LIlR8P006360@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6342
Modified Files:
tidy-bowl
Log Message:
These additional languages should be fine to reformat as well
Index: tidy-bowl
===================================================================
RCS file: /cvs/docs/docs-common/bin/tidy-bowl,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- tidy-bowl 6 Nov 2005 08:51:27 -0000 1.4
+++ tidy-bowl 21 Jan 2006 18:47:19 -0000 1.5
@@ -45,7 +45,7 @@
for fn in $@
do
case "${fn}" in
- *-de.xml | *-en.xml | *-fr-xml | *-it.xml )
+ *-de.xml | *-en.xml | *-fr-xml | *-it.xml | *-es.xml | *-ru.xml )
# Make sure we can find the input file
# /bin/echo "$0: XML file ${fn} prettyprinted."
if [ ! -f "${fn}" ]; then
From fedora-docs-commits at redhat.com Sat Jan 21 19:14:11 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 21 Jan 2006 14:14:11 -0500
Subject: docs-common/bin xmlformat-fdp.conf,1.13,1.14
Message-ID: <200601211914.k0LJEB0E008241@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8220/docs-common/bin
Modified Files:
xmlformat-fdp.conf
Log Message:
Jigger indexterm formatting for readability
Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- xmlformat-fdp.conf 16 Jan 2006 14:53:22 -0000 1.13
+++ xmlformat-fdp.conf 21 Jan 2006 19:14:03 -0000 1.14
@@ -79,7 +79,7 @@
normalize = yes
indexterm
- format = inline
+ format = block
normalize = no
primary secondary
From fedora-docs-commits at redhat.com Sat Jan 21 19:29:49 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 21 Jan 2006 14:29:49 -0500
Subject: example-tutorial example-tutorial-de.xml, 1.5,
1.6 example-tutorial-en.xml, 1.20, 1.21 rpm-info.xml, 1.14, 1.15
Message-ID: <200601211929.k0LJTnXY008315@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8289
Modified Files:
example-tutorial-de.xml example-tutorial-en.xml rpm-info.xml
Log Message:
Shameless bump to test prettyprinting, to 0.14.1
Index: example-tutorial-de.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-de.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- example-tutorial-de.xml 28 Dec 2005 22:19:04 -0000 1.5
+++ example-tutorial-de.xml 21 Jan 2006 19:29:41 -0000 1.6
@@ -1,4 +1,5 @@
+
-
-
+
+
@@ -15,42 +16,42 @@
]>
+
-
+
-
Some Section
-
Index term
-
- This is an example section. You should not use sect1, sect2, etc., since
- those tags will make sections less modular, i.e., harder to
+ This is an example section. You should not use sect1, sect2, etc.,
+ since those tags will make sections less modular, i.e., harder to
relocate without changing a lot of other markup.
+
- Keep text within the title tags on the same line as the
- tags. Nesting the title on a separate line from the enclosing tags results
- in extra spaces in HTML rendering.
+ Keep text within the title tags on the same
+ line as the tags. Nesting the title on a separate line from the
+ enclosing tags results in extra spaces in HTML rendering.
Warning
+
Example of an admonition.
- This paragraph illustrates the use of command syntax to accomplish a
- task. Note that specific filenames denoting versions should be
+ This paragraph illustrates the use of command syntax to accomplish
+ a task. Note that specific filenames denoting versions should be
avoided. To install any RPM package, use the following syntax:
@@ -58,11 +59,11 @@
Notice that the screen section is entirely
- left-justified with no preceding indent. This is necessary to ensure
- proper rendering in PDFs. Also notice that the entire
+ left-justified with no preceding indent. This is necessary to
+ ensure proper rendering in PDFs. Also notice that the entire
command has been surrounded by
- userinput since the user types this
- command. Computer output would be enclosed in
+ userinput since the user types this command.
+ Computer output would be enclosed in
computeroutput tags, as in the following
sample.
@@ -72,42 +73,42 @@
Lines should be broken exactly as they are
- on-screen. Also, note that spaces inside screen tags
- are automatically treated as non-breaking.
+ on-screen. Also, note that spaces inside screen
+ tags are automatically treated as non-breaking.
Fill modes and <command>screen</command> tags
- Using automatic or manual fill commands in Emacs/PSGML will sometimes
- mangle screen sections. Use care when performing fill
- operations, and check the results.
+ Using automatic or manual fill commands in Emacs/PSGML will
+ sometimes mangle screen sections. Use care
+ when performing fill operations, and check the results.
Callout Example
-
+
Line 1
Line 2
Line 3
Line 4
-
-
-
- Here is a callout.
-
-
-
-
- The second callout.
-
-
-
+
+
+
+ Here is a callout.
+
+
+
+
+ The second callout.
+
+
+
-
+
-
+
+
@@ -27,8 +27,8 @@
This is an example section. You should not use sect1, sect2, etc.,
- since those tags will make sections less modular, i.e.,
- harder to relocate without changing a lot of other markup.
+ since those tags will make sections less modular, i.e., harder to
+ relocate without changing a lot of other markup.
@@ -106,16 +106,31 @@
Deeply nested sections
- Early to bed, early to rise
+
+
+ Early to bed, early to rise
+
+
Second Level
- Is the curse of the working class
+
+
+ Is the curse of the working class
+
+
Third Level
- He who can, does
+
+
+ He who can, does
+
+
Fourth Level
- He who cannot, manages.
+
+
+ He who cannot, manages.
+
@@ -123,19 +138,23 @@
Procedure Test
-
- First step
+
+ First step
+
- Second step
+
+ Second step
+
- Third step
+
+ Third step
+
-
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/rpm-info.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- rpm-info.xml 7 Jan 2006 04:54:53 -0000 1.14
+++ rpm-info.xml 21 Jan 2006 19:29:41 -0000 1.15
@@ -1,7 +1,7 @@
-
+
-
+
@@ -17,7 +17,7 @@
2003, 2004, 2005
-
+
Tammy Fox
@@ -31,33 +31,37 @@
+
+
+ A shameless bump to test prettyprinting
+
- A later RPM release
+ A later RPM release
- A matching RPM release
+ A matching RPM release
- Make sure version matches what's in DOCVERSION
+ Make sure version matches what's in DOCVERSION
-
+
- Minor changes for testing purposes
+ Minor changes for testing purposes
- Some rpm-only changes
+ Some rpm-only changes
- Initial RPM version
+ Initial RPM version
-
+
- Add revision history
+ Add revision historyaddierte Neuausgabengeschichte
From fedora-docs-commits at redhat.com Sat Jan 21 19:32:12 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 21 Jan 2006 14:32:12 -0500
Subject: example-tutorial example-tutorial-de.xml, 1.6,
1.7 example-tutorial-en.xml, 1.21, 1.22
Message-ID: <200601211932.k0LJWCQV008349@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8324
Modified Files:
example-tutorial-de.xml example-tutorial-en.xml
Log Message:
Minor change to flush left a CDATA section, make sure prettyprinting leaves it alone
Index: example-tutorial-de.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-de.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- example-tutorial-de.xml 21 Jan 2006 19:29:41 -0000 1.6
+++ example-tutorial-de.xml 21 Jan 2006 19:32:04 -0000 1.7
@@ -93,7 +93,7 @@
Line 2
Line 3
Line 4
-
+
Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- example-tutorial-en.xml 21 Jan 2006 19:29:41 -0000 1.21
+++ example-tutorial-en.xml 21 Jan 2006 19:32:04 -0000 1.22
@@ -89,7 +89,7 @@
Line 2
Line 3
Line 4
-
+
From fedora-docs-commits at redhat.com Sun Jan 22 20:26:16 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 22 Jan 2006 15:26:16 -0500
Subject: docs-common/packaging insert-changelog.xsl, 1.2,
1.3 insert-colophon.xsl, 1.2, 1.3
Message-ID: <200601222026.k0MKQGPF031613@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31591/docs-common/packaging
Modified Files:
insert-changelog.xsl insert-colophon.xsl
Log Message:
Make sure we output our XML declaration and DOCTYPE when rewriting rpm-info
Index: insert-changelog.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/insert-changelog.xsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- insert-changelog.xsl 15 Jan 2006 22:33:03 -0000 1.2
+++ insert-changelog.xsl 22 Jan 2006 20:26:09 -0000 1.3
@@ -16,7 +16,9 @@
-
+
Index: insert-colophon.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/insert-colophon.xsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- insert-colophon.xsl 15 Jan 2006 23:27:34 -0000 1.2
+++ insert-colophon.xsl 22 Jan 2006 20:26:09 -0000 1.3
@@ -18,7 +18,9 @@
-
+
From fedora-docs-commits at redhat.com Mon Jan 23 21:30:22 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Mon, 23 Jan 2006 16:30:22 -0500
Subject: release-notes ArchSpecificx86-it.xml, 1.3, 1.4 Desktop-it.xml, 1.2,
1.3 DevelopmentToolsGCC-it.xml, 1.3,
1.4 DevelopmentToolsJava-it.xml, 1.3, 1.4 I18n-it.xml, 1.2,
1.3 Kernel-it.xml, 1.2, 1.3 Multimedia-it.xml, 1.2,
1.3 Networking-it.xml, 1.3, 1.4 OverView-it.xml, 1.3,
1.4 PackageChanges-it.xml, 1.2, 1.3 PackageNotes-it.xml, 1.3,
1.4 ProjectOverview-it.xml, 1.2, 1.3 Samba-it.xml, 1.2,
1.3 Security-it.xml, 1.2, 1.3 WebServers-it.xml, 1.2,
1.3 Welcome-it.xml, 1.4, 1.5 Xorg-it.xml, 1.1, 1.2
Message-ID: <200601232130.k0NLUMS0019443@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19405/release-notes
Modified Files:
ArchSpecificx86-it.xml Desktop-it.xml
DevelopmentToolsGCC-it.xml DevelopmentToolsJava-it.xml
I18n-it.xml Kernel-it.xml Multimedia-it.xml Networking-it.xml
OverView-it.xml PackageChanges-it.xml PackageNotes-it.xml
ProjectOverview-it.xml Samba-it.xml Security-it.xml
WebServers-it.xml Welcome-it.xml Xorg-it.xml
Log Message:
Some minor bug corrections...
Index: ArchSpecificx86-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/ArchSpecificx86-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ArchSpecificx86-it.xml 11 Jan 2006 07:17:52 -0000 1.3
+++ ArchSpecificx86-it.xml 23 Jan 2006 21:30:15 -0000 1.4
@@ -70,7 +70,7 @@
Note sull'installazione x86La schermata di selezione dell'installer ?? stata
ridisegnata nella versione di sviluppo di &FED;. &FC; &LOCALVER;
- non fornisce un opzione per selezionare il modo d'istallazione tipo
+ non fornisce un opzione per selezionare il modo d'installazione tipo
Desktop Personale, Workstation, Server e personalizzata.
Index: Desktop-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/Desktop-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Desktop-it.xml 15 Jan 2006 00:07:01 -0000 1.2
+++ Desktop-it.xml 23 Jan 2006 21:30:15 -0000 1.3
@@ -81,7 +81,7 @@
L'utilit?? di configurazione
system-config-mouse ?? stata scartata
- da questa release poich?? synaptic e la configurazione del mouse a 3 bottoni
+ da questa release poich?? synaptic e la configurazione del mouse a 3 bottoni
viene fatta automaticamente durante l'installazione. I mouse seriali sono
formalmente non pi?? supportati da &FC;.
Index: DevelopmentToolsGCC-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/DevelopmentToolsGCC-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- DevelopmentToolsGCC-it.xml 11 Jan 2006 07:17:52 -0000 1.3
+++ DevelopmentToolsGCC-it.xml 23 Jan 2006 21:30:15 -0000 1.4
@@ -42,7 +42,7 @@
Il file specs non ?? pi?? installato su
- molti systems. Gli utenti comunit non lo noteranno, ma gli sviluppatori
+ molti systems. Gli utenti comuni non lo noteranno, ma gli sviluppatori
che debbono alterare il file possono usare l'opzione -dumpspecs per generare il file
per l'editing.
@@ -72,7 +72,7 @@
Un attributo sentinel ?? stato aggiunto
- affinch?? il compilatore possa inviare un messaggio di avvertimento se una
+ affinch?? il compilatore possa inviare un messaggio di avvertimento se una
funzione tipo execl(char *path, const char *arg,
...), che richiede un terminatore di lista
NULL
Index: DevelopmentToolsJava-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/DevelopmentToolsJava-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- DevelopmentToolsJava-it.xml 11 Jan 2006 07:17:52 -0000 1.3
+++ DevelopmentToolsJava-it.xml 23 Jan 2006 21:30:15 -0000 1.4
@@ -25,12 +25,12 @@
url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ
- Java Development
+ Sviluppo Java
- Per evitare conflitti sui nomi:
+ Per evitare conflitti sui nomi i seguenti sono stati rinominati:
Index: I18n-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/I18n-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- I18n-it.xml 11 Jan 2006 07:17:52 -0000 1.2
+++ I18n-it.xml 23 Jan 2006 21:30:15 -0000 1.3
@@ -10,7 +10,7 @@
vari linguaggi in &DISTRO;.
- IIIMF replaced
+ IIIMF sostituito
SCIM ha sostituito IIIMF in questa release di &FC;.
Index: Kernel-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/Kernel-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Kernel-it.xml 11 Jan 2006 07:17:52 -0000 1.2
+++ Kernel-it.xml 23 Jan 2006 21:30:15 -0000 1.3
@@ -31,7 +31,7 @@
rpm -qpl kernel-<version>.src.rpm
-
+ Changelog
@@ -279,7 +279,7 @@
amministrazione. Di conseguenza, per rimuovere un simile kernel, ad esempio dopo un
aggiornamento, non puoi semplicemente usare il comando rpm -e
kernel-version come
- nelle precedenti distribuzioni poich?? questi pacchetti in user space
+ nelle precedenti distribuzioni poich?? questi pacchetti in user space
dipendono dal pacchetto del kernel.
Index: Multimedia-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/Multimedia-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Multimedia-it.xml 11 Jan 2006 07:17:52 -0000 1.2
+++ Multimedia-it.xml 23 Jan 2006 21:30:15 -0000 1.3
@@ -7,7 +7,7 @@
- Multimedia Players
+ Lettori multimedialiPer impostazione predefinita, &FC; viene installata con
rhythmbox, totem,
@@ -56,7 +56,7 @@
MP3 & Supporto DVD&FC; e &FEX; non possono includere il supporto per il playback o la
- registrazione degli MP3 o DVD, perch?? i formati MP3 e MPEG (DVD) sono
+ registrazione degli MP3 o DVD, perch?? i formati MP3 e MPEG (DVD) sono
protetti da copyright, ed i proprietari dei brevetti non forniscono le
necessarie licenze. Per maggiori informazioni, fate riferimento a .
Index: Networking-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/Networking-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Networking-it.xml 12 Jan 2006 06:56:15 -0000 1.3
+++ Networking-it.xml 23 Jan 2006 21:30:15 -0000 1.4
@@ -172,7 +172,7 @@
- Userspace Tools
+ Strumenti utente
L'algoritmo di cancellazione indirizzo IPv4 address non prendeva la lunghezza
del prefisso in conto fino al kernel versione 2.6.12. Da quando ci?? ??
@@ -198,7 +198,7 @@
Non ?? stato possibile dire se un interfaccia ?? spenta
- a scopo amministrativo o perch?? non c'?? linea (cavo
+ a scopo amministrativo o perch?? non c'?? linea (cavo
staccato). Il flag NO-CARRIER
?? stato introdotto per mostrare un link flag se il link ??
amministrativamente su ma non viene trovata linea.
Index: OverView-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/OverView-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- OverView-it.xml 14 Jan 2006 23:53:47 -0000 1.3
+++ OverView-it.xml 23 Jan 2006 21:30:15 -0000 1.4
@@ -84,13 +84,13 @@
- Il kernel 2.6.14 ?? incluso. Il suspend software ?? abilitato
+ Il kernel 2.6.14 ?? incluso. La sospensione software ?? abilitata
in questa versione.
- Pup, un updater grafico che usa yum, ?? disponibile in
+ Pup, un software di aggiornamento pacchetti grafico che usa yum, ?? disponibile in
questa versione.
Index: PackageChanges-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/PackageChanges-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PackageChanges-it.xml 12 Jan 2006 06:16:24 -0000 1.2
+++ PackageChanges-it.xml 23 Jan 2006 21:30:15 -0000 1.3
@@ -1046,13 +1046,13 @@
Note
L'utilit?? di configurazione system-config-mouse
- ?? stata scartata in questa release poich?? synaptic e la configurazione
+ ?? stata scartata in questa release poich?? synaptic e la configurazione
dei mouse a 3 bottoni viene fatta automaticamente ed i mouse
seriali non sono supportati.
Gli screensavers, per impostazione predefinita non sono pi?? installati? Spieghiamo
- il perch?? e forniamo i comandi per installarli.
+ il perch?? e forniamo i comandi per installarli.
- Appendix: Management Options
+ Appendix: Boot Options
The &FED; installation system includes a range of options and
- functions for administrators.
+ functions for administrators. To use boot options, enter
+ linux option at
+ the
+ boot:
+ prompt.
-
- Boot Options
+
+ If you specify more than one option, separate each of the options by
+ a single space. For example:
+
+
+linux option1option2option3
+
+
+ Configuring the Installation System
- To use boot options, enter linux
- option at the
+ You may configure the installation system without affecting the
+ final &FED; system. The
boot:
- prompt.
+ prompt enables you to specify a number of settings for the
+ installation system. These include:
+
+
+
+ Display resolution
+
+
+
+
+ Interface type
+
+
+
+
+ Installation method
+
+
+
+
+ Network settings
+
+
+
+
- If you specify more than one option, separate each of the options
- by a single space. For example:
+ You may force the installation system to use the lowest possible
+ screen resolution (640x480) with the
+ option. To use a specific display resolution, enter
+ as
+ a boot option. For example, to set the display resolution to
+ 1024x768, enter:
-linux option1option2option3
-
-
- Booting Your Computer with Rescue Mode
-
-
- 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.
-
-
-
- To load the rescue mode, enter:
-
-
- linux rescue
-
-
- Specify the language, keyboard layout and network settings for
- the rescue system with the screens that follow.
-
-
-
- Add a note that the boot and rescue CDs also have this facility.
-
-
-
-
-
- Configuring the Installation System
-
-
- You may configure the installation system without affecting the
- final &FED; system. The
- boot:
- prompt enables you to specify a number of settings for the
- installation system. These include:
-
-
-
-
-
- Display resolution
-
-
-
-
- Interface type
-
-
-
-
- Installation method
-
-
-
-
- Network settings
-
-
-
-
-
- You may force the installation system to use the lowest possible
- screen resolution (640x480) with the
- option. To use a specific display resolution, enter
-
- as a boot option. For example, to set the display resolution to
- 1024x768, enter:
-
-linux resolution=1024x768
-
- To run the installation process in mode,
- enter:
-
+
+ To run the installation process in mode,
+ enter:
+ linux text
-
- To enable support for a serial console, enter
- as an additional option.
-
+
+ To enable support for a serial console, enter
+ as an additional option.
+
-
- Use the 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
- boot:
- prompt itself.
-
+
+ Use the 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
+ boot:
+ prompt itself.
+
-
- To specify the installation method from the
- boot:
- prompt, use the option. Refer to
- for the supported
- installation methods.
-
-
- Installation Methods
-
-
-
-
-
- Installation Method
- Option Format
-
-
-
-
-
+
+ To specify the installation method from the
+ boot:
+ prompt, use the option. Refer to
+ for the supported installation
+ methods.
+
+
+ Installation Methods
+
+
+
+
+
+Installation Method
+Option Format
+
+
+
+
+
CD or DVD drive
-
+
-
-
-
+
+
+
Hard Drive
-
+
-
-
-
+
+
+
HTTP Server
-
+
-
-
-
+
+
+
FTP Server
-
+
-
-
-
+
+
+
NFS Server
-
+
-
-
-
-
-
- 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
- Configure TCP/IP screen, or at the
- boot:
- prompt. You may specify the address,
- , , and
- server settings for the installation system
- at the prompt. If you specify the network configuration at the
- boot:
- prompt, these settings are used for the installation process,
- and the Configure TCP/IP screen does not
- appear.
-
+
+
+
+
+
+ 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
+ Configure TCP/IP screen, or at the
+ boot:
+ prompt. You may specify the address,
+ , , and
+ server settings for the installation system
+ at the prompt. If you specify the network configuration at the
+ boot:
+ prompt, these settings are used for the installation process, and
+ the Configure TCP/IP screen does not appear.
+
-
- This example configures the network settings for an installation
- system that uses the IP address 192.168.1.10:
-
+
+ This example configures the network settings for an installation
+ system that uses the IP address
+ 192.168.1.10:
+ linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.2,192.168.1.3
-
-
-
- Enabling Remote Access to the Installation System
+
+
+ Enabling Remote Access to the Installation System
+
+ You may access either graphical or text interfaces for the
+ installation system from any other system. Access to a text mode
+ display requires telnet, which is installed by
+ default on &FED; systems. To remotely access the graphical display
+ of an installation system, use client software that supports the
+ VNC (Virtual Network Computing) display protocol. A number of
+ providers offer VNC clients for Microsoft Windows and Mac OS, as
+ well as UNIX-based systems.
+
+
+ Installing a VNC Client on &FED;
- You may access either graphical or text interfaces for the
- installation system from any other system. Access to a text mode
- display requires telnet, which is installed
- by default on &FED; systems. To remotely access the graphical
- display of an installation system, use client software that
- supports the VNC (Virtual Network Computing) display protocol. A
- number of providers offer VNC clients for Microsoft Windows and
- Mac OS, as well as UNIX-based systems.
-
-
- Installing a VNC Client on &FED;
-
- &FED; includes vncviewer, the
- client provided by the developers of VNC. To obtain
- vncviewer, install the
- vnc package.
-
-
-
- The installation system supports two types of VNC connection.
- You may either start the installation and manually login to the
- graphical display with a VNC client on another system, or
- configure the installation system to automatically connect to a
- VNC client on the network that is running in
- listening mode.
+ &FED; includes vncviewer, the client
+ provided by the developers of VNC. To obtain
+ vncviewer, install the
+ vnc package.
+
+
+ The installation system supports two types of VNC connection. You
+ may either start the installation and manually login to the
+ graphical display with a VNC client on another system, or
+ configure the installation system to automatically connect to a
+ VNC client on the network that is running in
+ listening mode.
+
-
- To enable remote graphical access to the installation system,
- enter two options at the prompt:
-
+
+ To enable remote graphical access to the installation system,
+ enter two options at the prompt:
+ linux vnc vncpassword=qwerty
-
- The option enables the VNC service. The
- option sets a password for remote
- access. The example shown above sets the password as
- qwerty.
-
-
-
- VNC Passwords
+
+ The option enables the VNC service. The
+ option sets a password for remote
+ access. The example shown above sets the password as
+ qwerty.
+
-
- The VNC password must be at least six characters long.
-
-
+
+ VNC Passwords
- Specify the language, keyboard layout and network settings for
- the installation system with the screens that follow. You may
- then access the graphical interface through a VNC client. The
- installation system displays the correct connection setting for
- the VNC client:
+ The VNC password must be at least six characters long.
+
+
+
+ Specify the language, keyboard layout and network settings for the
+ installation system with the screens that follow. You may then
+ access the graphical interface through a VNC client. The
+ installation system displays the correct connection setting for
+ the VNC client:
+ for a shell]]>
-
- You may then login to the installation system with a VNC client.
- To run the vncviewer client on &FED;,
- choose Applications
- AccessoriesVNC
- Viewer, or type the command
- vncviewer in a terminal window. Enter
- the server and display number in the VNC
- Server dialog. For the example above, the
- VNC Server is
- computer.mydomain.com:1.
-
+
+ You may then login to the installation system with a VNC client.
+ To run the vncviewer client on &FED;,
+ choose Applications
+ AccessoriesVNC
+ Viewer, or type the command
+ vncviewer in a terminal window. Enter
+ the server and display number in the VNC
+ Server dialog. For the example above, the VNC
+ Server is
+ computer.mydomain.com:1.
+
-
- To have the installation system automatically connect to a VNC
- client, first start the client in listening mode. On &FED;
- systems, use the option to run
- vncviewer as a listener. In a
- terminal window, enter the command:
-
+
+ To have the installation system automatically connect to a VNC
+ client, first start the client in listening mode. On &FED;
+ systems, use the option to run
+ vncviewer as a listener. In a terminal
+ window, enter the command:
+ vncviewer -listen
-
- Firewall Reconfiguration Required
-
-
- By default, the vncviewer utility
- listens on TCP port 5500. To update
- the &FED; firewall configuration to permit connections to this
- port from other systems, choose
- System
- AdministrationSecurity
- Level and Firewall, enter
- 5500:tcp in the Other
- ports: field, and select OK.
-
-
+
+ Firewall Reconfiguration Required
- Once the listening client is active, start the installation
- system and set the VNC options at the
- boot:
- prompt. In addition to and
- options, use the
- option to specify the name or IP
- address of the system that has the listening client. To specify
- the TCP port for the listener, add a colon and the port number
- to the name of the system.
+ By default, the vncviewer utility
+ listens on TCP port 5500. To update the
+ &FED; firewall configuration to permit connections to this port
+ from other systems, choose
+ System
+ AdministrationSecurity
+ Level and Firewall, enter
+ 5500:tcp in the Other
+ ports: field, and select OK.
+
-
- For example, to connect to a VNC client on the system
-
+ Once the listening client is active, start the installation system
+ and set the VNC options at the
+ boot:
+ prompt. In addition to and
+ options, use the
+ option to specify the name or IP
+ address of the system that has the listening client. To specify
+ the TCP port for the listener, add a colon and the port number to
+ the name of the system.
+
+
+
+ For example, to connect to a VNC client on the system
+ desktop.mydomain.com
- on the port 5500, enter the following
- at the
- boot:
- prompt:
-
+ on the port 5500, enter the following at
+ the
+ boot:
+ prompt:
+ linux vnc vncpassword=qwerty vncconnect=desktop.mydomain.com:5500
-
- To enable remote access to a text mode installation, use the
- option at the
- boot:
- prompt:
-
+
+ To enable remote access to a text mode installation, use the
+ option at the
+ boot:
+ prompt:
+ linux telnet
-
- You may then connect to the installation system with the
- telnet utility. The telnet
- command requires the name or IP address of the installation
- system:
-
+
+ You may then connect to the installation system with the
+ telnet utility. The telnet
+ command requires the name or IP address of the installation
+ system:
+ telnet computer.mydomain.com
-
- No password option for telnet ?
+
+ No password option for telnet ?
-
-
-
-
- Automating the Installation with Kickstart
+
+
+
+ Automating the Installation with Kickstart
+
+ A Kickstart file specifies settings for an
+ installation. Once booted, the installation system may read a
+ Kickstart file and carry out the installation process without
+ requiring any further input from a user.
+
+
+ Every Installation Produces a Kickstart File
- A Kickstart file specifies settings for
- an installation. Once booted, the installation system may read a
- Kickstart file and carry out the installation process without
- requiring any further input from a user.
-
-
- Every Installation Produces a Kickstart File
-
- The &FED; installation process automatically writes a
- Kickstart file that contains the settings for the installed
- system. This file is always saved as
- /root/anaconda-ks.cfg. You may use this
- file to repeat the installation with identical settings, or
- modify copies to specify settings for other systems.
-
-
-
- &FED; includes a graphical application that enables you to
- create and modify Kickstart files by selecting the options that
- you require. Use the package
- system-config-kickstart to install this
- utility. To load the &FED; Kickstart editor, choose
- ApplicationsSystem
- ToolsKickstart.
+ The &FED; installation process automatically writes a Kickstart
+ file that contains the settings for the installed system. This
+ file is always saved as
+ /root/anaconda-ks.cfg. You may use this
+ file to repeat the installation with identical settings, or
+ modify copies to specify settings for other systems.
+
+
+ &FED; includes a graphical application that enables you to create
+ and modify Kickstart files by selecting the options that you
+ require. Use the package
+ system-config-kickstart to install this
+ utility. To load the &FED; Kickstart editor, choose
+ ApplicationsSystem
+ ToolsKickstart.
+
-
- Kickstart files list installation settings in plain-text, with
- one option per line. This format enables you to modify your
- Kickstart files with any text editor, and write scripts or
- applications that generate custom Kickstart files for your
- systems.
-
+
+ Kickstart files list installation settings in plain-text, with one
+ option per line. This format enables you to modify your Kickstart
+ files with any text editor, and write scripts or applications that
+ generate custom Kickstart files for your systems.
+
-
- To automate the installation process with a Kickstart file, use
- the option to specify the name and location
- of the file:
-
+
+ To automate the installation process with a Kickstart file, use
+ the option to specify the name and location of
+ the file:
+ linux ks=location/kickstart-file.cfg
-
- You may use Kickstart files that are held on either removable
- storage, or a hard drive, or located on a network server. Refer
- to for the supported Kickstart
- sources.
-
-
- Kickstart Sources
-
-
-
-
-
- Kickstart Source
- Option Format
-
-
-
-
-
+
+ You may use Kickstart files that are held on either removable
+ storage, or a hard drive, or located on a network server. Refer to
+ for the supported Kickstart
+ sources.
+
+
+ Kickstart Sources
+
+
+
+
+
+Kickstart Source
+Option Format
+
+
+
+
+
CD or DVD drive
-
+
-
-
-
+
+
+
Hard Drive
-
+
-
-
-
+
+
+
Other Device
-
+
-
-
-
+
+
+
HTTP Server
-
+
-
-
-
+
+
+
FTP Server
-
+
-
-
-
+
+
+
NFS Server
-
+
-
-
-
-
-
- To obtain a Kickstart file from a script or application on a Web
- server, specify the URL of the application with the
- option. If you add the option
- , the request also sends HTTP headers
- to the Web application. Your application may use these headers
- to identify the computer. This line sends a request with headers
- to the application
- http://server.example.com/kickstart.cgi:
-
+
+
+
+
+
+ To obtain a Kickstart file from a script or application on a Web
+ server, specify the URL of the application with the
+ option. If you add the option
+ , the request also sends HTTP headers to
+ the Web application. Your application may use these headers to
+ identify the computer. This line sends a request with headers to
+ the application
+ http://server.example.com/kickstart.cgi:
+ linux ks=http://server.mydomain.com/kickstart.cgi kssendmac
-
+
+
+ Enhancing Hardware Support
-
- Hardware Support
+
+ By default, &FED; attempts to automatically detect and configure
+ support for all of the components of your computer. &FED; supports
+ the majority of hardware in common use with the software
+ drivers that are included with the
+ operating system. To enable a &FED; system to support more devices
+ you may supply additional drivers during the installation process,
+ or at a later time.
+
+
+ Adding Hardware Support with Driver Disks
+
- By default, &FED; attempts to automatically detect and configure
- support for all of the components of your computer. &FED;
- supports the majority of hardware in common use with the
- software drivers that are included with
- the operating system. To enable a &FED; system to support more
- devices you may supply additional drivers during the
- installation process, or at a later time.
+ The installation system may load drivers from disks, pen drives,
+ or network servers to configure support for new devices. After
+ the installation is complete, remove any driver disks and store
+ them for later use.
-
- Adding Hardware Support with Driver Disks
-
-
- The installation system may load drivers from disks, pen
- drives, or network servers to configure support for new
- devices. After the installation is complete, remove any driver
- disks and store them for later use.
-
-
-
- Hardware manufacturers may supply driver disks for &FED; with
- the device, or provide image files to prepare the disks. To
- obtain the latest drivers, download the correct file from the
- website of the manufacturer.
-
-
-
- Driver Disks Supplied as Zipped Files
+
+ Hardware manufacturers may supply driver disks for &FED; with
+ the device, or provide image files to prepare the disks. To
+ obtain the latest drivers, download the correct file from the
+ website of the manufacturer.
+
-
- Driver disk images may be distributed as compressed
- archives, or zip files. For identification, the names of zip
- files include the extensions .zip, or
- .tar.gz. To extract the contents of a
- zipped file with a &FED; system, choose
- ApplicationsSystem
- ToolsArchive
- Manager.
-
-
+
+ Driver Disks Supplied as Zipped Files
- To format a disk or pen drive with an image file, use the
- dd utility. For example, to prepare a
- diskette with the image file drivers.img,
- enter this command in a terminal window:
+ Driver disk images may be distributed as compressed archives,
+ or zip files. For identification, the names of zip files
+ include the extensions .zip, or
+ .tar.gz. To extract the contents of a
+ zipped file with a &FED; system, choose
+ ApplicationsSystem
+ ToolsArchive
+ Manager.
+
+
+
+ To format a disk or pen drive with an image file, use the
+ dd utility. For example, to prepare a
+ diskette with the image file drivers.img,
+ enter this command in a terminal window:
+ dd if=drivers.img of=/dev/fd0
-
- To use a driver disk in the installation process, specify the
- option at the
- boot:
- prompt:
-
+
+ To use a driver disk in the installation process, specify the
+ option at the
+ boot:
+ prompt:
+ linux dd
-
- When prompted, select Yes to provide a
- driver disk. Choose the drive that holds the driver disk from
- the list on the Driver Disk Source text
- screen.
-
+
+ When prompted, select Yes to provide a
+ driver disk. Choose the drive that holds the driver disk from
+ the list on the Driver Disk Source text
+ screen.
+
-
- The installation system may also read drivers from disk images
- that are held on network servers. Refer to
- for the supported sources
- of driver image files.
-
-
- Driver Disk Image Sources
-
-
-
-
-
- Image Source
- Option Format
-
-
-
-
-
+
+ The installation system may also read drivers from disk images
+ that are held on network servers. Refer to
+ for the supported sources of
+ driver image files.
+
+
+ Driver Disk Image Sources
+
+
+
+
+
+Image Source
+Option Format
+
+
+
+
+
Select a drive or device
-
+
-
-
-
+
+
+
HTTP Server
-
+
-
-
-
+
+
+
FTP Server
-
+
-
-
-
+
+
+
NFS Server
-
+
-
-
-
-
-
+
+
+
+
+
-
- Overriding Automatic Hardware Detection
+
+ Overriding Automatic Hardware Detection
+
+ For some models of device automatic hardware configuration may
+ fail, or cause instability. In these cases, you may need to
+ disable automatic configuration for that type of device, and
+ take additional steps to manually configure the device after the
+ installation process is complete.
+
+
+ Check the Release Notes
- For some models of device automatic hardware configuration may
- fail, or cause instability. In these cases, you may need to
- disable automatic configuration for that type of device, and
- take additional steps to manually configure the device after
- the installation process is complete.
-
-
- Check the Release Notes
-
- Refer to the Release Notes for information on known issues
- with specific devices.
-
-
-
- To override the automatic hardware detection, use one or more
- of the following options:
+ Refer to the Release Notes for information on known issues
+ with specific devices.
-
- Hardware Options
-
-
-
-
-
- Compatibility Setting
- Option
-
-
-
-
-
+
+
+ To override the automatic hardware detection, use one or more of
+ the following options:
+
+
+
+
+
+ Using the Maintenance Boot Modes
+
+
+ Memory (RAM) Testing Mode
+
+
+ Faults in memory modules may cause your system to freeze or
+ crash unpredictably. In some cases, memory faults may only cause
+ errors with particular combinations of software. For this
+ reason, you should test the memory of a computer before you
+ install &FED; for the first time, even if it has previously run
+ other operating systems.
+
+
+
+ To boot your computer in memory testing mode, enter
+ memtest86 at the
+ boot:
+ prompt. The first test starts immediately. By default,
+ memtest86 carries out a total of ten tests.
+
+
+
+ To halt the tests and reboot your computer, enter
+ Esc at any time.
+
+
+
+
+ Booting Your Computer with Rescue Mode
+
+
+ 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.
+
+
+
+ To load the rescue mode, enter:
+
+
+ linux rescue
+
+
+ Specify the language, keyboard layout and network settings for
+ the rescue system with the screens that follow.
+
+
+
+ Add a note that the boot and rescue CDs also have this facility.
+
+
-
- Performing a Memory (RAM) Test
-
-
- Faults in memory modules may cause your system to freeze or crash
- unpredictably. In some cases, memory faults may only cause errors
- with particular combinations of software. For this reason, you
- should test the memory of a computer before you install &FED; for
- the first time, even if it has previously run other operating
- systems.
-
-
-
- To load the memtest86 memory test utility,
- enter memtest86 at the
- boot:
- prompt. The utility immediately starts the first test. By default,
- memtest86 carries out a total of ten tests.
-
-
-
- To halt testing and reboot your computer, enter
- Esc at any time.
-
-
-
- Accessing the Consoles
-
-
- In addition to the main interface, or
- console, the installation process provides
- three other consoles. The shell console enables you to access the
- command-line of the installation system. The two other consoles
- display events as the installation proceeds. You may find these
- consoles useful for diagnosing errors in the installation process.
-
-
-
- To switch between the consoles of installation process, press the
- key combinations shown below:
-
-
-
-
- Aborting the Installation
-
-
- To abort the installation process at any time before the
- Installing Packages screen, either press
- CtrlAltDel
-
- or power off the computer with the power switch. &FED; makes no
- changes to your computer until package installation begins.
-
-
-
-
+
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- fedora-install-guide-firstboot-en.xml 8 Dec 2005 00:27:16 -0000 1.16
+++ fedora-install-guide-firstboot-en.xml 23 Jan 2006 23:24:09 -0000 1.17
@@ -43,10 +43,12 @@
This screen displays the overall licensing terms for &FC;. Each
software package in &FC; is covered by its own license which has
- been approved by the
- OSI (Open Source Initiative)
- Open Source Initiative (OSI). For more information
- about the OSI, refer to
+ been approved by the
+
+ OSI (Open Source Initiative)
+
+ Open Source Initiative (OSI). For more information about the OSI,
+ refer to
http://www.opensource.org/.
@@ -75,20 +77,22 @@
Firewall
- The
- firewall
- firewall built into &FC;
- checks every incoming and outgoing network connection on your
- machine against a set of rules. These rules specify which types of
- connections are permitted and which are denied.
+ The
+
+ firewall
+
+ firewall built into &FC; checks every
+ incoming and outgoing network connection on your machine against a
+ set of rules. These rules specify which types of connections are
+ permitted and which are denied.
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
- block incoming connections from other systems. You may make
- changes on this screen to allow access to specific network
- services on your &FED; system.
+ permit only Secure SHell (SSH) connections from other systems. You
+ may make changes on this screen to allow access to specific
+ network services on your &FED; system.
@@ -97,20 +101,46 @@
- To enable access to services listed on this screen, click the
- check box next to the service name. After installation is
- complete, you can enable access to other services as well.
+ To enable access to the services listed on this screen, click the
+ check box next to the service name.
+
+
+
+ SSH Remote Access
+
+
+ All &FED; systems automatically run the SSH remote access
+ service. The default firewall configuration allows connections
+ to this service, to ensure that administrators have immediate
+ remote access to new systems.
+
+
+
+
+ To enable access to other services, enter the required ports in
+ the Other ports: field. For each port,
+ specify the port number followed by the connection type, in the
+ format
+ portnumber:type.
+ The majority of services use TCP ports.
+
+
+
+ For example, to allow other systems to access mail with the
+ IMAP protocol, which may
+ use both TCP port 143 and TCP port 993, enter 143:tcp,
+ 993:tcp.
- Avoid disabling the firewall. If you believe it is necessary to do
- so, select No firewall.
+ Avoid disabling the firewall. If you believe that it is necessary
+ to do so, select No firewall.
Changing the Firewall Settings
- To change these settings later, choose
- System
+ To change these settings later, choose
+ SystemAdministrationSecurity
Level and Firewall.
@@ -125,15 +155,16 @@
- The
- &SEL;
- &SEL; (Security Enhanced
- Linux) framework is part of &FC;. &SEL; limits the actions of both
- users and programs by enforcing security policies throughout the
- operating system. Without &SEL;, software bugs or configuration
- changes may render a system more vulnerable. The restrictions
- imposed by &SEL; policies provide extra security against
- unauthorized access.
+ The
+
+ &SEL;
+
+ &SEL; (Security Enhanced Linux) framework
+ is part of &FC;. &SEL; limits the actions of both users and
+ programs by enforcing security policies throughout the operating
+ system. Without &SEL;, software bugs or configuration changes may
+ render a system more vulnerable. The restrictions imposed by &SEL;
+ policies provide extra security against unauthorized access.
@@ -147,7 +178,7 @@
- Active
+ Enforcing
Select this mode to use the targeted &SEL; policy on your
@@ -176,8 +207,7 @@
If you choose this mode for &SEL;, &FED; does not configure
the access control system at all. To make &SEL; active
- later, select
- System
+ later, select SystemAdministrationSecurity Level and Firewall.
@@ -185,18 +215,21 @@
-
+
- To adjust &SEL;, choose Modify SELinux Policy. To exempt a service from &SEL;, select the service from the list, and choose the Remove SELinux protection option.
+ To adjust &SEL;, choose Modify SELinux
+ Policy. To exempt a key service from &SEL;
+ restrictions, select the service from the list, and choose the
+ Remove SELinux protection option. The
+ SELinux Service Protection item on the list
+ includes options for additional services.
-
Changing the &SEL; policy
&SEL; is unique in that it cannot be bypassed, even by the
system administrators. To change the behavior of &SEL; after
- installation, choose
- System
+ installation, choose SystemAdministrationSecurity
Level and Firewall.
@@ -208,10 +241,12 @@
If your system does not have Internet access or a network time
server, manually set the date and time for your system on this
- screen. Otherwise, use
- NTP (Network Time Protocol)
- NTP (Network Time Protocol)
- servers to maintain the accuracy of the clock. NTP provides time
+ screen. Otherwise, use
+
+ NTP (Network Time Protocol)
+
+ NTP (Network Time Protocol) servers to
+ maintain the accuracy of the clock. NTP provides time
synchronization service to computers on the same network. The
Internet contains many computers that offer public NTP services.
@@ -243,8 +278,8 @@
Setting the Clock
- To change these settings later, choose
- System
+ To change these settings later, choose
+ SystemAdministrationDate &
Time.
@@ -365,8 +400,8 @@
Resetting the display
- To reconfigure your system after the installation has completed, choose
- System
+ To reconfigure your system after the installation has completed,
+ choose SystemAdministrationDisplay.
@@ -407,8 +442,8 @@
Creating extra user accounts
To add additional user accounts to your system after the
- installation is complete, choose
- System
+ installation is complete, choose
+ SystemAdministrationUsers &
Groups.
@@ -417,9 +452,6 @@
To configure &FC; to use network services for authentication or
user information, select Use Network
Login....
-
@@ -452,14 +484,20 @@
Click Play Test Sound to check the sound
- card configuration. If the configuration is correct, &FC; plays a
+ card configuration. If the configuration is correct, &FED; plays a
sound sequence. If your sound card is identified, but you do not
- hear the sound, check your speakers and try again.
-
-
-
- Explain the option to Use only the hardware device
-
+ hear the sound, check your speakers and try again. In some cases,
+ you may need to alter the additional settings to obtain the best
+ sound quality.
+
+
+
+ Sound cards may act as multiple audio devices. To change the
+ Default PCM device, select a new option from
+ the drop-down list. By default, audio applications connect to a
+ software mixer that manages the PCM devices. To enable
+ applications to bypass the software mixer, select the option to
+ Use only the hardware device.
@@ -470,10 +508,9 @@
Changing the Sound Card
- &FC; will automatically attempt to detect a new sound card if
+ &FED; will automatically attempt to detect a new sound card if
you add one to your system. If you need to launch the detection
- process manually, choose
- System
+ process manually, choose SystemAdministrationSoundcard
Detection.
Index: fedora-install-guide-nextsteps-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-nextsteps-en.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-nextsteps-en.xml 12 Dec 2005 02:21:54 -0000 1.10
+++ fedora-install-guide-nextsteps-en.xml 23 Jan 2006 23:24:09 -0000 1.11
@@ -3,11 +3,11 @@
Your Next Steps
- &FC; provides you with a complete operating system with a vast range
- of capabilities, supported by a large community.
+ &FED; provides you with a complete operating system with a vast
+ range of capabilities, supported by a large community.
- Updating Your &FED; System
+ Updating Your System
The &FP; releases updated software packages for &FC; throughout
@@ -24,14 +24,15 @@
To update your system with the latest packages, use the
- Package Updater
- Package Updater:
+ Package Updater
+
+ Package Updater:
- Choose System
- AdministrationPackage
+ Choose Applications
+ System ToolsPackage
Updater.
@@ -43,10 +44,9 @@
- Review the list of updated packages. If your system uses a
- slow network connection the Package
- Updater may require several seconds to download
- the information for all of the updated packages.
+ Review the list of updated packages. The package list displays
+ a double arrow next to any updates that require a system
+ reboot to take effect.
@@ -57,22 +57,21 @@
- Restart any active programs or network services listed in the
- update window. If the updates include a
- kernel package, restart your system as
- soon as possible to load the new kernel.
+ If one or more updates require a system reboot, the update
+ process displays a dialog with the option to Reboot
+ Now. Either select this option to reboot the
+ system immediately, or Cancel it and
+ reboot the system at a more convenient time.
- Check this procedure on test2
-
-
-
- To update packages from the command-line, use the
- yum
- yum utility. Type this command to
- begin a full update of your system with yum:
+ To update packages from the command-line, use the
+
+ yum
+
+ yum utility. Type this command to begin a full
+ update of your system with yum:
su -c 'yum update'
@@ -140,41 +139,81 @@
Announcements with the keyword
[SECURITY] in the title identify
- package updates that remove security vulnerabilities.
+ package updates that resolve security vulnerabilities.
- Finding Documentation on the Web
+ Finding Documentation and Support
- Documentation for &FC; is available from the &FP; Website:
-
-
-
-
+ Members of the &FED; community provides support through mailing
+ lists, web forums and Linux User Groups (LUGs) across the world.
- The Linux Documentation Project (LDP) produces books and
- tutorials:
+ The Website for the official forums is:
+ url="http://forums.fedoraforum.org/"/>
- For many parts of &FC;, you may find the &RHEL; documentation
- useful:
+ The following resources provide information on many aspects of
+ &FED;:
-
-
+
+
+ The FAQ on the &FP; website
+
+
+
+
+
+
+
+
+
+
+ The documents available from the &FDP; website
+
+
+
+
+
+
+
+
+
+
+ The Linux Documentation Project (LDP)
+
+
+
+
+
+
+
+
+
+
+ The &RHEL; documentation, much of which also applies to &FED;
+
+
+
+
-
+
+
+
+
Many other organizations and individuals also provide tutorials
@@ -187,23 +226,6 @@
url="http://www.google.com/linux/"/>
-
- Getting Community Support
-
-
- Members of the &FED; community provides support through mailing
- lists, web forums and Linux User Groups (LUGs) across the world.
-
-
-
- The Website for the official forums is:
-
-
-
-
-
- Joining The &FED; Community
Index: fedora-install-guide-techref-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-techref-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-techref-en.xml 9 Jan 2006 23:56:29 -0000 1.4
+++ fedora-install-guide-techref-en.xml 23 Jan 2006 23:24:09 -0000 1.5
@@ -106,8 +106,7 @@
&FED; uses the netfilter framework. The
- Netfilter project website provides documentation for
- netfilter, and the
+ Netfilter project website provides documentation for both netfilter, and the
iptables administration facilities:
.
Index: fedora-install-guide-timezone-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-timezone-en.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-timezone-en.xml 27 May 2005 22:15:15 -0000 1.10
+++ fedora-install-guide-timezone-en.xml 23 Jan 2006 23:24:09 -0000 1.11
@@ -2,16 +2,14 @@
Time Zone Selection
-
This screen allows you to specify the correct time zone for the
- location of your computer. Specify a time zone even if you plan to
+ location of your computer. Specify a time zone even if you plan to
use
- NTP (Network Time Protocol)
+ NTP (Network Time Protocol) NTP (Network Time Protocol) to maintain the accuracy of
the system clock.
-
Selecting a Time Zone
@@ -19,76 +17,72 @@
&FED; displays on the screen two methods for selecting the time
zone.
-
Time Zone Selection Screen
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
Time zone selection screen.
-
+
-
- To select a time zone using the map, select the yellow dot that
- represents the city nearest to your location. When you place the
- arrow on a dot, &FED; displays the name of the city below the map.
- Once you select a dot, it becomes a red X to
- indicate your selection.
+ To select a time zone using the map, first place your mouse
+ pointer over your region on the map. Click once to magnify that
+ region on the map. Next, select the yellow dot that represents the
+ city nearest to your location. Once you select a dot, it becomes a
+ red X to indicate your selection.
To select a time zone using the list, select the name of the city
- nearest to your location. The cities are listed in alphabetical
+ nearest to your location. The cities are listed in alphabetical
order.
-
-
Universal Co-ordinated Time (UTC)
- UTC (Universal Co-ordinated time)
+ UTC (Universal Co-ordinated time) Universal Co-ordinated Time is also known as
- GMT (Greenwich Mean Time)
- UTC
+ GMT (Greenwich Mean Time)
+ UTC Greenwich Mean Time (GMT).
If &FC; is the only operating system on your computer, select
- System clock uses UTC. The system clock is a
- piece of hardware on your computer system. &FC; uses the timezone
+ System clock uses UTC. The system clock is a
+ piece of hardware on your computer system. &FC; uses the timezone
setting to determine the offset between the local time and UTC on
- the system clock. This behavior is standard for UNIX-like
+ the system clock. This behavior is standard for UNIX-like
operating systems.
Windows and the System Clock
+
- Do not enable the System clock uses UTC
- option if your machine also runs Microsoft Windows. Microsoft
- operating systems change the BIOS clock to match local time
- rather than UTC. This may cause unexpected behavior under &FC;.
+ Do not enable the System clock uses UTC
+ option if your machine also runs Microsoft Windows. Microsoft
+ operating systems change the BIOS clock to match local time
+ rather than UTC. This may cause unexpected behavior under &FC;.
Select Next to proceed.
-
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.xml 17 Jan 2006 23:04:15 -0000 1.3
+++ rpm-info.xml 23 Jan 2006 23:24:09 -0000 1.4
@@ -1,6 +1,6 @@
-
+
-
+
@@ -28,9 +28,14 @@
+
+
+
+ Updated for FC5 test2.
+
- Added initial empty RPM revision to test packaging.
+ Added initial empty RPM revision to test packaging.
From fedora-docs-commits at redhat.com Tue Jan 24 21:29:53 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 24 Jan 2006 16:29:53 -0500
Subject: install-guide fedora-install-guide-zh_CN.xml,1.3,1.4
Message-ID: <200601242129.k0OLTr3E008715@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8697
Modified Files:
fedora-install-guide-zh_CN.xml
Log Message:
Fix bad entity
Index: fedora-install-guide-zh_CN.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-zh_CN.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-zh_CN.xml 17 Dec 2005 12:22:01 -0000 1.3
+++ fedora-install-guide-zh_CN.xml 24 Jan 2006 21:29:45 -0000 1.4
@@ -6,7 +6,7 @@
-
+
From fedora-docs-commits at redhat.com Tue Jan 24 22:02:06 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 24 Jan 2006 17:02:06 -0500
Subject: release-notes Makefile,1.16,1.17
Message-ID: <200601242202.k0OM26j4010543@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10502
Modified Files:
Makefile
Log Message:
Removed "make rpm" cruft.
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- Makefile 16 Jan 2006 22:01:39 -0000 1.16
+++ Makefile 24 Jan 2006 22:01:51 -0000 1.17
@@ -12,19 +12,34 @@
#
LANGUAGES = en it ja_JP zh_CN ru #ja_JP
# uncomment languages when you have all the same
- # fies localized as are listed in XMLEXTRAFILES
+ # files localized as are listed in XMLEXTRAFILES
DOCBASE = RELEASE-NOTES
define XMLEXTRAFILES_template
-XMLEXTRAFILES-$(1)=ArchSpecific-$(1).xml ArchSpecificPPC-$(1).xml ArchSpecificx86_64-$(1).xml ArchSpecificx86-$(1).xml BackwardsCompatibility-$(1).xml Colophon-$(1).xml DatabaseServers-$(1).xml Desktop-$(1).xml DevelopmentTools-$(1).xml DevelopmentToolsGCC-$(1).xml DevelopmentToolsJava-$(1).xml Entertainment-$(1).xml Feedback-$(1).xml FileServers-$(1).xml FileSystems-$(1).xml I18n-$(1).xml Installer-$(1).xml Introduction-$(1).xml Kernel-$(1).xml Legacy-$(1).xml Multimedia-$(1).xml Networking-$(1).xml OverView-$(1).xml PackageChanges-$(1).xml PackageNotes-$(1).xml PackageNotesJava-$(1).xml Printing-$(1).xml ProjectOverview-$(1).xml RELEASE-NOTES-$(1).xml Samba-$(1).xml Security-$(1).xml SecuritySELinux-$(1).xml ServerTools-$(1).xml SystemDaemons-$(1).xml WebServers-$(1).xml Welcome-$(1).xml Xorg-$(1).xml
+XMLEXTRAFILES-$(1)=ArchSpecific-$(1).xml ArchSpecificPPC-$(1).xml \
+ ArchSpecificx86-$(1).xml ArchSpecificx86_64-$(1).xml \
+ BackwardsCompatibility-$(1).xml Colophon-$(1).xml \
+ DatabaseServers-$(1).xml Desktop-$(1).xml \
+ DevelopmentTools-$(1).xml DevelopmentToolsGCC-$(1).xml \
+ DevelopmentToolsJava-$(1).xml Entertainment-$(1).xml \
+ Feedback-$(1).xml FileServers-$(1).xml FileSystems-$(1).xml \
+ I18n-$(1).xml Installer-$(1).xml Introduction-$(1).xml \
+ Kernel-$(1).xml Legacy-$(1).xml Multimedia-$(1).xml \
+ Networking-$(1).xml OverView-$(1).xml PackageChanges-$(1).xml \
+ PackageNotes-$(1).xml PackageNotesJava-$(1).xml \
+ Printing-$(1).xml ProjectOverview-$(1).xml \
+ RELEASE-NOTES-$(1).xml Samba-$(1).xml Security-$(1).xml \
+ SecuritySELinux-$(1).xml ServerTools-$(1).xml \
+ SystemDaemons-$(1).xml WebServers-$(1).xml Welcome-$(1).xml \
+ Xorg-$(1).xml
endef
$(foreach LANG,${LANGUAGES},$(eval $(call XMLEXTRAFILES_template,${LANG})))
#
-######################################################
+########################################################################
include ../docs-common/Makefile.common
-######################################################
+########################################################################
#
# If you want to add additional steps to any of the
# targets defined in "Makefile.common", be sure to use
@@ -34,68 +49,4 @@
# line:
#${DOCBASE}-en/index.html::
# echo FINISHED AT LAST
-######################################################
-# Some packaging specific vars
-VERSION=$(shell grep BOOKID $(DOCBASE)-en.xml | sed 's/ - $(VERSION)-1\n- Update to version $(VERSION)\n/' \
- $(SPECIN) > $(DOCSPEC)
-#
-# Fill in files
-# FIXME: Needs to be multiplexed for LANGUAGES (see above)
- cp $(OMFIN) $(DOCOMF)
- cp $(DESKTOPIN) $(DOCDESKTOP)
- sed -i 's/@VERSION@/$(VERSION)/g' $(DOCOMF)
- sed -i 's/@DATE@/$(DATE)/g' $(DOCOMF)
- sed -i 's/@TITLE@/$(TITLE)/g' $(DOCOMF)
- sed -i 's/@DOCBASE@/$(DOCBASE)/g' $(DOCOMF)
- sed -i 's/@VERSION@/$(VERSION)/g' $(DOCDESKTOP)
- sed -i 's/@DATE@/$(DATE)/g' $(DOCDESKTOP)
- sed -i 's/@TITLE@/$(TITLE)/g' $(DOCDESKTOP)
- sed -i 's/@DOCBASE@/$(DOCBASE)/g' $(DOCDESKTOP)
-#
-# Do the build...
-#
- rpmbuild -bb $(RPMFLAGS) $(DOCSPEC)
- mv RPMS/noarch/*.rpm .
- rpmbuild --clean --rmsource $(RPMFLAGS) $(DOCSPEC)
- rm -rf {BUILD,RPMS,SOURCES,SPECS,SRPMS}
- rm -rf $(DOCBASE)-$(VERSION)
+########################################################################
From fedora-docs-commits at redhat.com Tue Jan 24 22:05:34 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 24 Jan 2006 17:05:34 -0500
Subject: release-notes rpm-info.xml,1.1,1.2
Message-ID: <200601242205.k0OM5YgP010593@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10575
Modified Files:
rpm-info.xml
Log Message:
Fleshed out to allow RPM building to work.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/release-notes/rpm-info.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-info.xml 17 Jan 2006 02:12:20 -0000 1.1
+++ rpm-info.xml 24 Jan 2006 22:05:25 -0000 1.2
@@ -1,4 +1,4 @@
-
+
@@ -6,7 +6,9 @@
+
+ GNU FDL1.0
@@ -38,5 +40,14 @@
-
+
+
+
+ Dummy entry to make rpm building work; please remove
+
+
+
+ Dummy entry to make rpm building work; please remove
+
+
From fedora-docs-commits at redhat.com Tue Jan 24 22:10:48 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 24 Jan 2006 17:10:48 -0500
Subject: release-notes RELEASE-NOTES-en.xml, 1.17, 1.18 RELEASE-NOTES-it.xml,
1.8, 1.9 RELEASE-NOTES-ja_JP.xml, 1.4,
1.5 RELEASE-NOTES-pa.xml, 1.1, 1.2 RELEASE-NOTES-ru.xml, 1.4,
1.5 RELEASE-NOTES-zh_CN.xml, 1.6, 1.7
Message-ID: <200601242210.k0OMAmBE010628@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10603
Modified Files:
RELEASE-NOTES-en.xml RELEASE-NOTES-it.xml
RELEASE-NOTES-ja_JP.xml RELEASE-NOTES-pa.xml
RELEASE-NOTES-ru.xml RELEASE-NOTES-zh_CN.xml
Log Message:
Changed to use information from "rpm-info.xml" instead of depricated
in-line or elements.
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- RELEASE-NOTES-en.xml 10 Jan 2006 21:51:56 -0000 1.17
+++ RELEASE-NOTES-en.xml 24 Jan 2006 22:10:39 -0000 1.18
@@ -47,6 +47,8 @@
+
+
@@ -58,21 +60,15 @@
-
+
]>
-
- &FC; &LOCALVER; Release Notes
-
- 2006
- &FORMAL-RHI;
-
- &LEGALNOTICE-RELNOTES;
-
+
+ &FDP-INFO;
&WELCOME;
&OVERVIEW;
Index: RELEASE-NOTES-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- RELEASE-NOTES-it.xml 12 Jan 2006 06:16:24 -0000 1.8
+++ RELEASE-NOTES-it.xml 24 Jan 2006 22:10:39 -0000 1.9
@@ -47,6 +47,8 @@
+
+
@@ -65,14 +67,8 @@
]>
-
- Note di rilascio per &FC; &LOCALVER;
-
- 2006
- &FORMAL-RHI;
-
- &LEGALNOTICE-RELNOTES;
-
+
+ &FDP-INFO;
&WELCOME;
&OVERVIEW;
Index: RELEASE-NOTES-ja_JP.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ja_JP.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- RELEASE-NOTES-ja_JP.xml 11 Jan 2006 16:05:00 -0000 1.4
+++ RELEASE-NOTES-ja_JP.xml 24 Jan 2006 22:10:39 -0000 1.5
@@ -47,6 +47,8 @@
+
+
@@ -64,15 +66,8 @@
]>
-
- &FC; &LOCALVER; ?????????????????????????????????
-
- 2006
- &FORMAL-RHI;
-
- &LEGALNOTICE-RELNOTES;
-
-
+
+ &FDP-INFO;
&WELCOME;
&OVERVIEW;
Index: RELEASE-NOTES-pa.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-pa.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RELEASE-NOTES-pa.xml 9 Jan 2006 10:10:16 -0000 1.1
+++ RELEASE-NOTES-pa.xml 24 Jan 2006 22:10:39 -0000 1.2
@@ -47,6 +47,8 @@
+
+
@@ -71,18 +73,8 @@
]>
-
- &DISTRO; &DISTROVER; ???????????? ??????????????? (????????????)
-
- 2005
- &FORMAL-RHI;
-
- &LEGALNOTICE-RELNOTES;
-
-
+
+ &FDP-INFO;
&WELCOME;
&OVERVIEW;
Index: RELEASE-NOTES-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ru.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- RELEASE-NOTES-ru.xml 15 Jan 2006 15:59:25 -0000 1.4
+++ RELEASE-NOTES-ru.xml 24 Jan 2006 22:10:39 -0000 1.5
@@ -47,6 +47,8 @@
+
+
@@ -65,14 +67,8 @@
]>
-
- &FC; &LOCALVER; ?????????????????? ?? ??????????????
-
- 2006
- &FORMAL-RHI;
-
- &LEGALNOTICE-RELNOTES;
-
+
+ &FDP-INFO;
&WELCOME;
&OVERVIEW;
Index: RELEASE-NOTES-zh_CN.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-zh_CN.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- RELEASE-NOTES-zh_CN.xml 13 Jan 2006 15:31:37 -0000 1.6
+++ RELEASE-NOTES-zh_CN.xml 24 Jan 2006 22:10:39 -0000 1.7
@@ -42,7 +42,11 @@
%FEDORA-ENTITIES-EN;
-
+
+
+
+
+
@@ -57,11 +61,7 @@
]>
-
- &FC; &LOCALVER; ????????????
-
- 2006
- &FORMAL-RHI;
-
- &LEGALNOTICE-RELNOTES;
- &WELCOME; &OVERVIEW; &LEGALNOTICE-SECTION; &FEEDBACK; &INTRO; &INSTALLER; &ARCH-SPECIFIC; &NETWORKING; &PACKAGE-NOTES; &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW;
+
+ &FDP-INFO;
+
+ &WELCOME; &OVERVIEW; &LEGALNOTICE-SECTION; &FEEDBACK; &INTRO; &INSTALLER; &ARCH-SPECIFIC; &NETWORKING; &PACKAGE-NOTES; &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW;
From fedora-docs-commits at redhat.com Wed Jan 25 20:11:58 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 25 Jan 2006 15:11:58 -0500
Subject: owners owners.list,1.10,1.11
Message-ID: <200601252011.k0PKBwu2027415@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/owners
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27397/owners
Modified Files:
owners.list
Log Message:
Adding new guide for bugzilla component.
Index: owners.list
===================================================================
RCS file: /cvs/docs/owners/owners.list,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- owners.list 9 Nov 2005 21:17:45 -0000 1.10
+++ owners.list 25 Jan 2006 20:11:48 -0000 1.11
@@ -30,6 +30,8 @@
# fdr at eln.fastmail.fm
# relnotes at fedoraproject.org
# sarahs at redhat.com
+# cchang at redhat.com
+# aalam at redhat.com
#
# Global FDP components
@@ -63,6 +65,7 @@
Fedora Documentation|toolchain-devel|For bugs and requests of the documentation tools.|kwade at redhat.com|mjohnson at redhat.com|Tommy.Reynolds at MegaCoder.com
Fedora Documentation|translation-guide|The canonical reference for translating all aspects of the Fedora Project.|sarahs at redhat.com|tfox at redhat.com|kwade at redhat.com
Fedora Documentation|translation-guide-windows|Tutorial for translators working in a Microsoft Windows environment.|sarahs at redhat.com|tfox at redhat.com|
+Fedora Documentation|translation-quick-start-guide|Helping new translators get started quickly with Fedora translations.|mospina at redhat.com|aalam at redhat.com|stickster at gmail.com
Fedora Documentation|updates|Tutorial for keeping a system up-to-date.|tfox at redhat.com|kwade at redhat.com|
Fedora Documentation|usb-hotplug|Using USB and hotplug.|stickster at gmail.com|fdr at eln.fastmail.fm|
Fedora Documentation|xml-normalize|Development of XML normalization tools.|Tommy.Reynolds at MegaCoder.com|stickster at gmail.com|
From fedora-docs-commits at redhat.com Thu Jan 26 00:15:47 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 25 Jan 2006 19:15:47 -0500
Subject: 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
Message-ID: <200601260015.k0Q0FlKk003289@cvs-int.fedora.redhat.com>
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 @@
Appendix: Boot Options
- 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
linux option at
the
boot:
@@ -17,6 +17,16 @@
linux option1option2option3
+
+ Rescue Mode
+
+
+ The &FED; installation and rescue discs may
+ either boot with rescue mode , or load the
+ installation system. For more information on rescue discs and
+ rescue mode, refer to .
+
+ Configuring the Installation System
@@ -31,6 +41,11 @@
+ Language
+
+
+
+
Display resolution
@@ -50,59 +65,80 @@
-
-
- You may force the installation system to use the lowest possible
- screen resolution (640x480) with the
- option. To use a specific display resolution, enter
- as
- a boot option. For example, to set the display resolution to
- 1024x768, enter:
-
+
+
+ Specifying the Language
+
+
+ To set the language for the installation process screens,
+ specify the ISO code for that language with the
+ option. For example, the ISO code
+ fr identifies the French language:
+
+
+linux lang=fr
+
+
+
+
+ Configuring the Interface
+
+
+ You may force the installation system to use the lowest possible
+ screen resolution (640x480) with the
+ option. To use a specific display resolution, enter
+
+ as a boot option. For example, to set the display resolution to
+ 1024x768, enter:
+ linux resolution=1024x768
-
- To run the installation process in mode,
- enter:
-
+
+ To run the installation process in mode,
+ enter:
+ linux text
-
- To enable support for a serial console, enter
- as an additional option.
-
+
+ To enable support for a serial console, enter
+ as an additional option.
+
+
-
- Use the 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
- boot:
- prompt itself.
-
+
+ Specifying the Installation Method
-
- To specify the installation method from the
- boot:
- prompt, use the option. Refer to
- for the supported installation
- methods.
-
-
- Installation Methods
-
-
-
-
-
+
+ Use the 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
+ boot:
+ prompt itself.
+
+
+
+ To specify the installation method from the
+ boot:
+ prompt, use the option. Refer to
+ for the supported
+ installation methods.
+
+
+ Installation Methods
+
+
+
+
+ Installation MethodOption Format
-
-
-
-
+
+
+
+
CD or DVD drive
@@ -113,8 +149,8 @@
-
-
+
+
Hard Drive
@@ -125,8 +161,8 @@
-
-
+
+
HTTP Server
@@ -137,8 +173,8 @@
-
-
+
+
FTP Server
@@ -149,8 +185,8 @@
-
-
+
+
NFS Server
@@ -161,37 +197,44 @@
-
-
-
-
-
- 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
- Configure TCP/IP screen, or at the
- boot:
- prompt. You may specify the address,
- , , and
- server settings for the installation system
- at the prompt. If you specify the network configuration at the
- boot:
- prompt, these settings are used for the installation process, and
- the Configure TCP/IP screen does not appear.
-
+
+
+
+
+
-
- This example configures the network settings for an installation
- system that uses the IP address
- 192.168.1.10:
-
+
+ Manually Configuring the Network Settings
+
+
+ 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
+ Configure TCP/IP screen, or at the
+ boot:
+ prompt. You may specify the address,
+ , , and
+ server settings for the installation system
+ at the prompt. If you specify the network configuration at the
+ boot:
+ prompt, these settings are used for the installation process,
+ and the Configure TCP/IP screen does not
+ appear.
+
+
+
+ This example configures the network settings for an installation
+ system that uses the IP address
+ 192.168.1.10:
+ linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.2,192.168.1.3
+ Enabling Remote Access to the Installation System
-
+
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 @@
boot:
prompt:
+
-linux telnet
+linux text telnet
You may then connect to the installation system with the
@@ -337,10 +381,16 @@
telnet computer.mydomain.com
-
- No password option for telnet ?
-
-
+
+ Telnet Access Requires No Password
+
+
+ To ensure the security of the installation process, only use the
+ option to install systems on networks
+ with restricted access.
+
+
+
Automating the Installation with Kickstart
@@ -509,7 +559,7 @@
Adding Hardware Support with Driver Disks
-
+
The installation system may load drivers from disks, pen drives,
or network servers to configure support for new devices. After
@@ -731,7 +781,7 @@
- Disable Direct Memory Access (DMA) for storage
+ Disable Direct Memory Access (DMA) for IDE drives
@@ -845,7 +895,7 @@
Using the Maintenance Boot Modes
- Memory (RAM) Testing Mode
+ Loading the Memory (RAM) Testing Mode
Faults in memory modules may cause your system to freeze or
@@ -871,51 +921,36 @@
- Booting Your Computer with Rescue Mode
+ Booting Your Computer with the Rescue Mode
- 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.
- 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:
linux rescue
Specify the language, keyboard layout and network settings for
- the rescue system with the screens that follow.
-
-
-
- Add a note that the boot and rescue CDs also have this facility.
-
-
-
-
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 @@
-
-
+
+
-
+
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 @@
To enable access to other services, enter the required ports in
- the Other ports: field. For each port,
- specify the port number followed by the connection type, in the
- format
+ the Other ports: field. For each port, you
+ must specify the port as TCP or UDP, in addition to the port
+ number. Use the format
portnumber:type.
The majority of services use TCP ports.
- For example, to allow other systems to access mail with the
- IMAP protocol, which may
- use both TCP port 143 and TCP port 993, enter 143:tcp,
- 993:tcp.
+ For example, enter 143:tcp, 993:tcp to
+ allow users to access mail from other systems with the IMAP
+ protocol, which may use both TCP port 143 and TCP port 993.
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 @@
Package Selection
-
- Obsolete
-
-
- &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.
-
-
- &FED; uses the installation type to select a set of software
- packages for your system. Refer to
- for more information. You can
- accept this default set of packages, or customize it to fit your
- preferences. If you choose the Custom
- installation type, &FED; displays the screen for Package
- Group Selection 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.
+
+
+ &FED; divides included software into
+
+ package groups
+
+ package groups. For ease of use, this screen
+ displays the package groups in six categories:
+
+
+ Package Group Selection Screen
+
+
+
+
+
+
+
+
+
+ Package group selection screen.
+
+
+
+
+
+ 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.
+
+
+ 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.
+ None of the packages from a group will be
+ installed unless the checkbox for that group is selected.
+
+ 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
+ Optional Packages button under the
+ description of the group. Change the selection of
+ Optional Packages by using the checkbox next
+ to the name of the individual package.
+
+
+ Package Group Details Dialog
+
+
+
+
+
+
+
+
+
+ Package group details dialog.
+
+
+
+ Changing Your Mind
- The installation type and packages that you select are not
- permanent. After you boot your system, use the
- Package Management tool to make
+ The packages that you select are not permanent. After you boot
+ your system, use the pirut tool to make
different software selections for your system. To run this tool,
- from the main menu, select System
- AdministrationAdd/Remove
- Applications.
+ from the main menu, select
+ ApplicationsSystem
+ ToolsAdd/Remove Software
+ .
-
- Package Installation Defaults
-
-
- A summary of the default package selection is displayed.
-
-
- Package Installation Defaults Screen
-
-
-
-
-
-
-
-
-
- Package installation defaults screen.
-
-
-
-
-
- To accept the default package selection, select Install
- the default software packages. Select
- Next to continue, and proceed to
- .
-
-
-
- To view or change the packages, select Customize
- software packages to be installed. Select
- Next to continue, and proceed to
- .
-
-
-
- Package Group Selection
-
-
- &FC; divides included software into
- package groups
- package groups that make
- software selection easier.
-
-
- Package Group Selection Screen
-
-
-
-
-
-
-
-
-
- Package group selection screen.
-
-
-
-
-
- The default groups for the chosen installation type are already
- selected. Select or remove any group of packages as desired.
- None of the packages from a group will be
- installed unless the checkbox next to the group is selected.
-
-
-
- To change which packages within a selected group will be
- installed, select the Details link next to
- the name of the group. &FC; automatically installs Base
- Packages of a group if the group is selected. Change
- the selection of Optional Packages by using
- the checkbox next to the name of the individual package.
-
-
-
- &FC; lists with each group the number of packages currently
- selected for installation, and the total number of packages within
- that group.
-
-
- Package Group Details Dialog
-
-
-
-
-
-
-
-
-
- Package group details dialog.
-
-
-
-
- Additional Language Support
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 Language Support package
- group.
+ support for additional languages, select the package group for
+ those languages from the Languages category.
@@ -155,50 +100,12 @@
-
- <guilabel>Everything</guilabel> or <guilabel>Minimal</guilabel>
- Installations
-
-
- Two of the groups under the heading of
- Miscellaneous are incompatible with the
- others. If you select either of these groups, your other group
- selections become invalid.
-
-
-
- If you select Everything, &FC; installs
- all 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.
-
-
-
- Storage Requirements
-
-
- The Everything 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.
-
-
-
-
- The Minimal package group provides only the
- essential packages to create a bootable system. This package group
- provides no graphical interface.
-
-
-
- After you choose the desired packages, select
- Next to proceed. &FC; checks your selection,
- and automatically adds any extra packages required to use the
- software you select.
-
-
+
+ After you choose the desired packages, select
+ Next to proceed. &FC; checks your selection,
+ and automatically adds any extra packages required to use the
+ software you select.
+
+
+
+
+ Updated Package Selection screen for test2.
+
- Updated for FC5 test2.
+ Updated for FC5 test2.
From fedora-docs-commits at redhat.com Thu Jan 26 06:11:17 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Thu, 26 Jan 2006 01:11:17 -0500
Subject: translation-quick-start-guide translation-quick-start-it.xml, NONE,
1.1 Makefile, 1.3, 1.4
Message-ID: <200601260611.k0Q6BH0E014313@cvs-int.fedora.redhat.com>
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 ---
%FEDORA-ENTITIES-IT;
]>
&FDP-INFO;
Introduzione
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.
Accounts e sottoscrizioni
Per partecipare al &FP; come traduttore hai bisogno di un account.
Puoi sottoscrivere un account su . 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.
Se non hai ancora una chiave SSH, puoi generarne una compiendo i
seguenti passi:
Scrivi in una linea di comando:
ssh-keygen -t dsa
Accetta la posizione predefinita
(~/.ssh/id_dsa) ed immetti una passphrase.
Nota
Non dimenticare questa passphrase di cui avrai bisogno per accedere
al repositorio CVS.
Cambia i permessi alla tua chiave ed alla tua directory
.ssh:
chmod 755 ~/.ssh
Copia ed incolla la chiave ssh nello spazio fornito per poter
completare la sottoscrizione all'account.
Ci sono anche due liste su cui puoi discutere i problemi di traduzione.
La prima ?? fedora-trans-list, una lista
generale per discutere i problemi che affliggono tutti i linguaggi. Fa riferimento a
per maggiori informazioni. La seconda ?? la lista specifica per la tua lingua,
tipo fedora-trans-es per i traduttori
Spagnoli, per discutere problematiche inerenti solo la comunit??
di traduttori individuale.
Potrai anche trovare utile sottoscriverti alla
fedora-docs-list per rimanere informato sulle
problematiche generali della documentazione.
Tradurre il software
La parte traducibile di un pacchetto software ?? disponibile in uno o
pi?? files po. Il &FP; immagazzina questi files in
un repositorio CVS sotto la directory
translate/. Una volta che il tuo account ?? stato
approvato, scarica questa directory scrivendo le seguenti
istruzioni in una linea di comando:
export CVS_RSH=sshexport CVSROOT=:ext:username@i18.redhat.com:/usr/local/CVScvs -z9 co translate/
Questi comandi scaricheranno tutti i moduli e files
.po sulla tua macchina seguendo la medesima
gerarchia del repositorio. Ogni directory contiene un
file .pot, tipo
anaconda.pot, ed il
file .po per ogni linguaggio, tipo
zh_CN.po, de.po, e cos??
via.
Puoi controllare lo status delle traduzioni su . 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
take 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.
Ora puoi cominciare a tradurre.
Vai nella directory del pacchetto che hai preso.
cd ~/translate/package_name
Aggiorna i files con il seguente comando:
cvs up
Traduci il file po del tuo linguaggio un un editor per po come
KBabel o
gtranslator. Per esempio, per aprire
il file .po per lo Spagnolo in
KBabel, scrivi:
kbabel es.po
Quando hai finito il tuo lavoro, esegui il commit dei tuoi cambiamenti al
repositorio:
cvs commit -m 'comments' lang.po
Come ultimo passo, clicca il link release sulla
pagina status per rilasciare il modulo affinch?? altre persone possano lavorarci
sopra.
Se vuoi leggere la bozza della tua traduzione come parte integrante del software,
segui i seguenti passi:
Vai alla directory del pacchetto che vuoi testare:
cd ~/translate/package_name
Converti il file .po in file
.mo con msgfmt:
msgfmt lang.po
Sovrascrivi il file .mo esistente in
/usr/share/locale/lang/LC_MESSAGES/.
Prima, fa un back up del file esistente:
cp /usr/share/locale/lang/LC_MESSAGES/package_name.mo package_name.mo-backupmv package_name.mo /usr/share/locale/lang/LC_MESSAGES/
Leggi la tua bozza del pacchetto con le stringhe tradotte
nell'applicazione:
LANG=lang rpm -qi package_name
L'applicazione relativa al pacchetto tradotto verr?? eseguita con
le stringhe tradotte.
Tradurre la documentazione
Anche la documentazione Fedora ?? immagazzinata in un repositorio CVS sotto
la directory docs/. Il processo per scaricare
la documentazione ?? similare a quello utilizzato per scaricare
i files .po:
export CVSROOT=:ext:username@cvs.fedora.redhat.com:/cvs/docscvs co docs
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 docs-common per
controllare la validit?? del tuo documento per la compilazione.
cvs co -ccvs co example-tutorial docs-common
I documenti sono scritti nel formato DocBook XML e nominati usando
lo specifico linguaggio di localizzazione, tipo
example-tutorial-en.xml. Se pianifichi di
tradurre direttamente dai files XML originali, dovrai creare
il documento per il tuo linguaggio:
cp example-tutorial-en.xml example-tutorial-es.xml
Quindi potrai lavorare sulla nuova copia.
Puoi anche convertire i files XML in .po
files e lavorare con un .po editor come
KBabel o
gtranslator. Per farlo compi i seguenti
passi:
In un terminale, vai alla directory del documento che vuoi
tradurre:
cd ~/docs/example-tutorial
Estrai le stringhe traducibili con xml2pot:
xml2pot example-tutorial-en.xml > lang.po
Adesso puoi tradurre il file usando la stessa applicazione usata
per tradurre il software:
kbabel lang.po
Una volta terminato, ?? necessario convertire il file
.po tradotto nel corrispondente file .xml
di linguaggio con po2xml:
po2xml example-tutorial-en.xml lang.po > example-tutorial-lang.xml
Il filtro xml2po non include le entities
nel file .po. Dovrai cambiare il
linguaggio del documento. Trova la linea tipo la seguente in prossimit??
della cima del documento:
<article id="example-tutorial" lang="en">Cambia gli attributi con quelli del tuo linguaggio:<article id="example-tutorial" lang="es">
Quando il file tradotto ?? pronto, aggiungilo al repository:
cvs add example-tutorial-lang.xmlcvs commit -m 'Any comment' example-tutorial-lang.xml
Potresti dover cambiare il Makefile affinch??
il documento possa essere compilato nei formati HTML e PDF.
Nota:
Sei pregato di avvisare la comunit?? attraverso la fedora-doc-list e
fedora-trans-locale che stai
modificando il Makefile. Informa la
comunit?? che stai lavorando alla traduzione del
documento prima di cominciare, per evitare conflitti tra traduttori
lavorando sullo stesso file.
Nel text editor di tua preferenza, apri il
Makefile.
vi Makefile
Aggiungi il locale della nuova traduzione dopo gli altri
linguaggi come nell'esempio seguente:
LANGUAGES = en de lang
Esegui il commit del Makefile.
cvs commit -m 'Any comment' Makefile
Quindi, potrai compilare il document nel tuo linguaggio scrivendo:
make html-lang
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 =
From fedora-docs-commits at redhat.com Thu Jan 26 06:21:36 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 26 Jan 2006 01:21:36 -0500
Subject: translation-quick-start-guide translation-quick-start-en.xml, 1.6,
1.7 rpm-info.xml, 1.3, 1.4
Message-ID: <200601260621.k0Q6Lad9014390@cvs-int.fedora.redhat.com>
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;
-
-
+
+
@@ -21,7 +21,7 @@
&FDP-INFO;
-
+ Introduction
@@ -34,16 +34,16 @@
-
- Accounts and subscriptions
+
+ Accounts and Subscriptions
To participate in the &FP; as a translator you need an account.
You can apply for an account at . 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.
@@ -66,10 +66,10 @@
(~/.ssh/id_dsa) and enter a passphrase.
- Note
+ Don't Forget Your Passphrase!
- 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.
@@ -96,15 +96,18 @@
directory:
+
+
+
+
-chmod 755 ~/.ssh
-
+chmod 700 ~/.ssh
- 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.
@@ -119,15 +122,18 @@
translators, to discuss issues that affect only the individual
community of translators.
-
- You may also find it useful to subscribe to
- fedora-docs-list to stay informed about
- general documentation issues.
-
+
+ General Documentation Issues
+
+ You may also find it useful to subscribe to
+ fedora-docs-list to stay informed about
+ general documentation issues.
+
+
-
- Translating software
+
+ Translating Software
The translatable part of a software package is available in one or
@@ -169,91 +175,101 @@
You can now start translating.
-
-
-
- Go to the directory of the package you have taken.
-
+
+
+ Translating Strings
+
+
+
+
+ Change directory to the location of the package you have
+ taken.
+ cd ~/translate/package_name
-
-
-
- Update the files with the following command:
-
+
+
+
+ Update the files with the following command:
+ cvs up
-
-
-
- Translate the po file of your language in a po editor such as
- KBabel or
- gtranslator. For example, to open
- the .po file for Spanish in
- KBabel, type:
-
+
+
+
+ Translate the .po file of your language
+ in a .po editor such as
+ KBabel or
+ gtranslator. For example, to open
+ the .po file for Spanish in
+ KBabel, type:
+ kbabel es.po
-
-
-
- When you finish your work, commit your changes back to the
- repository:
-
+
+
+
+ When you finish your work, commit your changes back to the
+ repository:
+
-cvs commit -m 'comments' lang.po
+cvs commit -m 'comments' lang.po
-
-
-
- As a last step, click the release link on
- the status page to release the module so other people can work
- on it.
-
-
-
-
- If you want to proofread your translation as part of the software,
- follow these steps:
-
-
-
-
- Go to the directory of the package you want to proofread:
-
+
+
+
+ Click the release link on the status page
+ to release the module so other people can work on it.
+
+
+
+
+
+
+ Proofreading
+
+
+ If you want to proofread your translation as part of the
+ software, follow these steps:
+
+
+
+
+ Go to the directory of the package you want to proofread:
+ cd ~/translate/package_name
-
-
-
- Convert the .po file in
- .mo file with msgfmt:
-
+
+
+
+ Convert the .po file in
+ .mo file with msgfmt:
+ msgfmt lang.po
-
-
-
- Overwrite the existing .mo file in
- /usr/share/locale/lang/LC_MESSAGES/.
- First, back up the existing file:
+
+
+
+ Overwrite the existing .mo file in
+ /usr/share/locale/lang/LC_MESSAGES/.
+ First, back up the existing file:
@@ -261,206 +277,237 @@
mv package_name.mo /usr/share/locale/lang/LC_MESSAGES/
-
-
-
- Proofread the package with the translated strings as part of
- the application:
-
+
+
+
+ Proofread the package with the translated strings as part of
+ the application:
+ LANG=lang rpm -qi package_name
-
-
-
- The application related to the translated package will run with
- the translated strings.
-
+
+
+
+ The application related to the translated package will run with
+ the translated strings.
+
+
+
-
- Translating documentation
+
+ Translating Documentation
The Fedora documentation is also stored in a CVS repository under
- the directory docs/. The process to download
- the documentation is similar to the one used to download
- .po files:
+ the directory docs/.
+
+ Downloading Documentation
+
+
+ The process to download the documentation is similar to the one
+ used to download .po files:
+
+
export CVSROOT=:ext:username@cvs.fedora.redhat.com:/cvs/docscvs co docs
-
- 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 docs-common module to
- check document validity for building.
-
+
+ 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
+ docs-common module to check document
+ validity for building.
+ cvs co -ccvs co example-tutorial docs-common
-
- The documents are written in DocBook XML format and named using
- the specific-language locale, such as
- example-tutorial-en.xml. If you plan to
- translate directly from the original XML file, you should create
- the document for your language:
-
+
+ The documents are written in DocBook XML format and named using
+ the specific-language locale, such as
+ example-tutorial-en.xml. If you plan to
+ translate directly from the original XML file, you should create
+ the document for your language:
+ cp example-tutorial-en.xml example-tutorial-es.xml
-
- Afterwards you can work on the new copy.
-
-
- You can also convert the XML files into .po
- files and work with a .po editor like
- KBabel or
- gtranslator. To do so, follow these
- steps:
-
-
-
-
- In a terminal, go to the directory of the document you want to
- translate:
-
+
+ Afterwards you can work on the new copy.
+
+
+
+
+ Using Translation Applications
+
+
+ You can also convert the XML files into .po
+ files and work with a .po editor like
+ KBabel or
+ gtranslator. To do so, follow these
+ steps:
+
+
+
+
+ In a terminal, go to the directory of the document you want
+ to translate:
+
+
cd ~/docs/example-tutorial
-
-
-
- Extract the translatable strings with xml2pot:
-
+
+
+
+ Extract the translatable strings with
+ xml2pot:
+ xml2pot example-tutorial-en.xml > lang.po
-
-
-
- Now you can translate the file using the same application used
- to translate software:
-
-
+
+
+
+ Now you can translate the file using the same application
+ used to translate software:
+
+
kbabel lang.po
-
-
-
- Once you finish, it is necessary to convert the translated
- .po file to .xml
- file in the target language with po2xml:
-
+
+
+
+ Once you finish, you must convert the translated
+ .po file to .xml
+ file in the target language with po2xml:
+ po2xml example-tutorial-en.xml lang.po > example-tutorial-lang.xml
-
-
-
- The xml2po filter does not include entities
- in the .po file. You must change the
- language of the document. Locate a line like the following near
- the top of the document:
-
+
+
+
+ The xml2pot filter does not include
+ entities in the .po file. You must
+ change the language of the document. Locate a line like the
+ following near the top of the document:
+ <article id="example-tutorial" lang="en">
- Change the attribute to your language:
+
+
+ Change the attribute to your language:
-<article id="example-tutorial" lang="es">
+<article id="example-tutorial" lang="es">
-
- When the translated file is ready, add it to the repository:
-
+
+
+
+ When the translated file is ready, add it to the repository:
+ cvs add example-tutorial-lang.xmlcvs commit -m 'Any comment' example-tutorial-lang.xml
-
- You may have to change the Makefile so the
- document can be built in HTML and PDF formats.
-
-
- Note:
+
+
+
+
+
+
+ Changing the <filename>Makefile</filename>
+
- Please advise the community through fedora-doc-list and
- fedora-trans-locale that you are
- modifying the Makefile. 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 Makefile so the
+ document can be built in HTML and PDF formats.
-
-
-
-
+
+ Avoid Translation Conflicts
- In the text editor of your preference, open the
- Makefile.
+ Please advise the community through fedora-doc-list and
+ fedora-trans-locale that you are
+ modifying the Makefile. 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.
+
+
+
+
+
+ In the text editor of your preference, open the
+ Makefile.
+ vi Makefile
-
-
-
- Add the locale of the new translation after the other
- languages as in the following example:
-
+
+
+
+ Add the locale of the new translation after the other
+ languages as in the following example:
+
-LANGUAGES = en de lang
+LANGUAGES = en de lang
-
-
-
- Commit the Makefile.
-
+
+
+
+ Commit the Makefile.
+ cvs commit -m 'Any comment' Makefile
-
-
-
- Then, you can build the document in your langugage by typing:
-
+
+
+
+ Then, you can build the document in your langugage by
+ typing:
+ make html-lang
-
-
+
+
+
+
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 @@
+
+
+
+
@@ -29,7 +33,12 @@
-
+
+
+ Additional style editing, division of procedures into more readable
+ sections
+
+ First round of editing.
From fedora-docs-commits at redhat.com Thu Jan 26 06:27:22 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 26 Jan 2006 01:27:22 -0500
Subject: translation-quick-start-guide translation-quick-start-en.xml, 1.7,
1.8
Message-ID: <200601260627.k0Q6RMWL014433@cvs-int.fedora.redhat.com>
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 @@
-
+ Accounts and Subscriptions
@@ -132,7 +132,7 @@
-
+ Translating Software
@@ -298,7 +298,7 @@
-
+ Translating Documentation
From fedora-docs-commits at redhat.com Fri Jan 27 00:50:25 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Thu, 26 Jan 2006 19:50:25 -0500
Subject: translation-quick-start-guide translation-quick-start-it.xml, 1.1,
1.2
Message-ID: <200601270050.k0R0oPUu023641@cvs-int.fedora.redhat.com>
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;
-
-
+
+
@@ -21,7 +21,7 @@
&FDP-INFO;
-
+ Introduzione
@@ -95,10 +95,13 @@
Cambia i permessi alla tua chiave ed alla tua directory
.ssh:
+
+
+
+
-chmod 755 ~/.ssh
-
+chmod 755 ~/.ssh
@@ -119,11 +122,14 @@
Spagnoli, per discutere problematiche inerenti solo la comunit??
di traduttori individuale.
-
- Potrai anche trovare utile sottoscriverti alla
- fedora-docs-list per rimanere informato sulle
- problematiche generali della documentazione.
-
+
+ Problematiche generali della documentazione
+
+ Potrai anche trovare utile sottoscriverti alla
+ fedora-docs-list per rimanere informato sulle
+ problematiche generali della documentazione.
+
+
@@ -169,11 +175,16 @@
Ora puoi cominciare a tradurre.
-
-
-
- Vai nella directory del pacchetto che hai preso.
-
+
+
+ Tradurre le stringhe
+
+
+
+
+ Vai nella directory del pacchetto che hai
+ preso.
+ cd ~/translate/package_name
@@ -192,7 +203,8 @@
- Traduci il file po del tuo linguaggio un un editor per po come
+ Traduci il file .po del tuo linguaggio
+ un un editor per .po come
KBabel o
gtranslator. Per esempio, per aprire
il file .po per lo Spagnolo in
@@ -211,19 +223,23 @@
-cvs commit -m 'comments' lang.po
+cvs commit -m 'comments' lang.po
- Come ultimo passo, clicca il link release sulla
- pagina status per rilasciare il modulo affinch?? altre persone possano lavorarci
- sopra.
+ Come ultimo passo, clicca il link release sulla pagina status
+ per rilasciare il modulo affinch?? altre persone possano lavorarci sopra.
-
+
+
+
+ Controllare la leggibilit??
+
+
Se vuoi leggere la bozza della tua traduzione come parte integrante del software,
segui i seguenti passi:
@@ -278,16 +294,24 @@
L'applicazione relativa al pacchetto tradotto verr?? eseguita con
le stringhe tradotte.
+
+
Tradurre la documentazione
-
+
Anche la documentazione Fedora ?? immagazzinata in un repositorio CVS sotto
- la directory docs/. Il processo per scaricare
- la documentazione ?? similare a quello utilizzato per scaricare
- i files .po:
+ la directory docs/.
+
+
+
+ Scaricare la documentazione
+
+
+ Il processo per scaricare la documentazione ?? similare a quello
+ utilizzato per scaricare i files .po:
@@ -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 docs-common per
+ anche eseguire il check out del modulo
+ docs-common per
controllare la validit?? del tuo documento per la compilazione.
@@ -322,8 +347,14 @@
Quindi potrai lavorare sulla nuova copia.
-
-
+
+
+
+
+
+ Usare le applicazioni per la traduzione
+
+
Puoi anche convertire i files XML in .po
files e lavorare con un .po editor come
KBabel o
@@ -344,7 +375,8 @@
- Estrai le stringhe traducibili con xml2pot:
+ Estrai le stringhe traducibili con
+ xml2pot:
@@ -374,26 +406,30 @@
po2xml example-tutorial-en.xml lang.po > example-tutorial-lang.xml
-
-
-
- Il filtro xml2po non include le entities
- nel file .po. Dovrai cambiare il
- linguaggio del documento. Trova la linea tipo la seguente in prossimit??
- della cima del documento:
-
+
+
+
+ Il filtro xml2po non include le entities
+ nel file .po. Dovrai cambiare il
+ linguaggio del documento. Trova la linea tipo la seguente in prossimit??
+ della cima del documento:
+ <article id="example-tutorial" lang="en">
- Cambia gli attributi con quelli del tuo linguaggio:
+
+
+ Cambia gli attributi con quelli del tuo linguaggio:
-<article id="example-tutorial" lang="es">
+<article id="example-tutorial" lang="es">
-
+
+
+
Quando il file tradotto ?? pronto, aggiungilo al repository:
@@ -402,21 +438,29 @@
cvs commit -m 'Any comment' example-tutorial-lang.xml
-
+
+
+
+
+
+
+ Modificare il <filename>Makefile</filename>
+
+
Potresti dover cambiare il Makefile affinch??
il documento possa essere compilato nei formati HTML e PDF.
-
- Nota:
-
+
+ Evitare conflitti di traduzione
+
Sei pregato di avvisare la comunit?? attraverso la fedora-doc-list e
fedora-trans-locale che stai
modificando il Makefile. Informa la
comunit?? che stai lavorando alla traduzione del
documento prima di cominciare, per evitare conflitti tra traduttori
lavorando sullo stesso file.
-
-
+
+
@@ -436,7 +480,7 @@
-LANGUAGES = en de lang
+LANGUAGES = en de lang
@@ -452,15 +496,18 @@
- Quindi, potrai compilare il document nel tuo linguaggio scrivendo:
+ Quindi, potrai compilare il document nel tuo linguaggio
+ scrivendo:
make html-lang
-
-
+
+
+
+
From fedora-docs-commits at redhat.com Fri Jan 27 23:16:04 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 27 Jan 2006 18:16:04 -0500
Subject: docs-common/bin fdpsh,1.2,1.3
Message-ID: <200601272316.k0RNG5Rx007416@cvs-int.fedora.redhat.com>
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
From fedora-docs-commits at redhat.com Sat Jan 28 07:10:03 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 28 Jan 2006 02:10:03 -0500
Subject: translation-quick-start-guide rpm-info.xml,1.4,1.5
Message-ID: <200601280710.k0S7A33Q023881@cvs-int.fedora.redhat.com>
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.
+
+ Guida rapida alle traduzioni
+
+ Guida rapida per fornire traduzioni rapide nel Fedora Project.
+
+
@@ -37,14 +43,18 @@
Additional style editing, division of procedures into more readable
sections
+ Ulteriori aggiunte di stile, divisioni delle procedure in sezioni pi??
+ leggibiliFirst round of editing.
+ Primo round di editing.First draft
-
+ Prima bozza
+
From fedora-docs-commits at redhat.com Sat Jan 28 07:58:16 2006
From: fedora-docs-commits at redhat.com (Patrick Barnes (nman64))
Date: Sat, 28 Jan 2006 02:58:16 -0500
Subject: infrastructure/build-docs Makefile,1.1,1.2
Message-ID: <200601280758.k0S7wGZc024069@cvs-int.fedora.redhat.com>
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
From fedora-docs-commits at redhat.com Sat Jan 28 08:00:12 2006
From: fedora-docs-commits at redhat.com (Patrick Barnes (nman64))
Date: Sat, 28 Jan 2006 03:00:12 -0500
Subject: infrastructure/build-docs build-docs.spec,1.1,1.2
Message-ID: <200601280800.k0S80CHa024103@cvs-int.fedora.redhat.com>
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
+- Fixed potentially nasty typo in Makefile (only affects non-rpm installs)
+- Incremented version to 0.0.4
+
* Sat Dec 17 2005 Patrick Barnes
- Renamed package to build-docs
- Updated script now allows -k flag
From fedora-docs-commits at redhat.com Sat Jan 28 18:34:18 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 28 Jan 2006 13:34:18 -0500
Subject: docs-common/packaging omf.xsl,1.4,1.5
Message-ID: <200601281834.k0SIYItO014250@cvs-int.fedora.redhat.com>
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 @@
-
+
+
+
+
From fedora-docs-commits at redhat.com Sat Jan 28 20:41:52 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 28 Jan 2006 15:41:52 -0500
Subject: docs-common/bin db2rpm-info,1.3,1.4
Message-ID: <200601282041.k0SKfqXq018562@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18544/docs-common/bin
Modified Files:
db2rpm-info
Log Message:
No presumed shell on contributors' machines but bash
Index: db2rpm-info
===================================================================
RCS file: /cvs/docs/docs-common/bin/db2rpm-info,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- db2rpm-info 19 Jan 2006 19:49:54 -0000 1.3
+++ db2rpm-info 28 Jan 2006 20:41:45 -0000 1.4
@@ -1,4 +1,4 @@
-#!/bin/zsh
+#!/bin/bash
ME=$(basename $0)
BINDIR=$(dirname $0)
USAGE="usage: ${ME} [-o ofile] document.xml"
From fedora-docs-commits at redhat.com Sun Jan 29 15:38:54 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 29 Jan 2006 10:38:54 -0500
Subject: docs-common/bin db2rpm-info,1.4,1.5
Message-ID: <200601291538.k0TFcsr3030668@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30650/bin
Modified Files:
db2rpm-info
Log Message:
Allow *any* modern shell.
Index: db2rpm-info
===================================================================
RCS file: /cvs/docs/docs-common/bin/db2rpm-info,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- db2rpm-info 28 Jan 2006 20:41:45 -0000 1.4
+++ db2rpm-info 29 Jan 2006 15:38:45 -0000 1.5
@@ -1,6 +1,6 @@
-#!/bin/bash
-ME=$(basename $0)
-BINDIR=$(dirname $0)
+#!/bin/sh
+ME=`basename $0`
+BINDIR=`dirname $0`
USAGE="usage: ${ME} [-o ofile] document.xml"
ofile=
while getopts o: c
@@ -10,7 +10,7 @@
*) echo "${USAGE}" >&2; exit 1;;
esac
done
-shift $(expr ${OPTIND} - 1)
+shift `expr ${OPTIND} - 1`
if [ $# -ne 1 ]; then
echo "${USAGE}" >&2
exit 1
From fedora-docs-commits at redhat.com Sun Jan 29 20:38:03 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 29 Jan 2006 15:38:03 -0500
Subject: install-guide fedora-install-guide-adminoptions-en.xml, 1.8,
1.9 fedora-install-guide-bootloader-en.xml, 1.13,
1.14 fedora-install-guide-en.xml, 1.40,
1.41 fedora-install-guide-firstboot-en.xml, 1.18,
1.19 fedora-install-guide-packageselection-en.xml, 1.17,
1.18 fedora-install-guide-techref-en.xml, 1.5,
1.6 rpm-info.xml, 1.5, 1.6
Message-ID: <200601292038.k0TKc3hS008223@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8184
Modified Files:
fedora-install-guide-adminoptions-en.xml
fedora-install-guide-bootloader-en.xml
fedora-install-guide-en.xml
fedora-install-guide-firstboot-en.xml
fedora-install-guide-packageselection-en.xml
fedora-install-guide-techref-en.xml rpm-info.xml
Log Message:
- Updated indexing.
- Added SSH to Tech Ref section.
- Package Selection is still subject to change at this point.
Index: fedora-install-guide-adminoptions-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-adminoptions-en.xml 26 Jan 2006 00:15:39 -0000 1.8
+++ fedora-install-guide-adminoptions-en.xml 29 Jan 2006 20:37:55 -0000 1.9
@@ -22,17 +22,18 @@
The &FED; installation and rescue discs may
- either boot with rescue mode , or load the
+ either boot with rescue mode, or load the
installation system. For more information on rescue discs and
rescue mode, refer to .
- Configuring the Installation System
+ Configuring the Installation System at the
+ <prompt>boot:</prompt>
+ Prompt
- You may configure the installation system without affecting the
- final &FED; system. The
+ The
boot:
prompt enables you to specify a number of settings for the
installation system. These include:
@@ -70,8 +71,8 @@
Specifying the Language
- To set the language for the installation process screens,
- specify the ISO code for that language with the
+ To set the language for both the installation process and the
+ final system, specify the ISO code for that language with the
option. For example, the ISO code
fr identifies the French language:
@@ -95,16 +96,35 @@
linux resolution=1024x768
- To run the installation process in mode,
- enter:
+ To run the installation process in
+
+ text interface
+
+ mode, enter:
linux text
- To enable support for a serial console, enter
- as an additional option.
+ To enable support for a
+
+ serial console
+
+ serial console, enter as an additional
+ option.
+
+
+ Configuring the Installed System
+
+
+ The installed system runs the Setup Agent the first time that
+ it boots. Use the Setup Agent to configure the display
+ settings for the new system. Refer to
+ for more information on
+ configuring the display with the Setup Agent.
+
+
@@ -230,6 +250,16 @@
linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.2,192.168.1.3
+
+ Configuring the Installed System
+
+
+ Use the Network Configuration screen to specify the network
+ settings for the new system. Refer to
+ for more information on
+ configuring the network settings for the installed system.
+
+
@@ -241,6 +271,9 @@
display requires telnet, which is installed by
default on &FED; systems. To remotely access the graphical display
of an installation system, use client software that supports the
+
+ VNC (Virtual Network Computing)
+
VNC (Virtual Network Computing) display protocol. A number of
providers offer VNC clients for Microsoft Windows and Mac OS, as
well as UNIX-based systems.
@@ -248,6 +281,10 @@
Installing a VNC Client on &FED;
+
+ VNC (Virtual Network Computing)
+ installing client
+
&FED; includes vncviewer, the client
provided by the developers of VNC. To obtain
vncviewer, install the
@@ -259,11 +296,15 @@
may either start the installation and manually login to the
graphical display with a VNC client on another system, or
configure the installation system to automatically connect to a
- VNC client on the network that is running in
- listening mode.
+ VNC client on the network that is running in listening
+ mode.
+
+ VNC (Virtual Network Computing)
+ enabling
+
To enable remote graphical access to the installation system,
enter two options at the prompt:
@@ -314,10 +355,14 @@
To have the installation system automatically connect to a VNC
- client, first start the client in listening mode. On &FED;
- systems, use the option to run
- vncviewer as a listener. In a terminal
- window, enter the command:
+ client, first start the client in
+
+ VNC (Virtual Network Computing)
+ listening mode
+
+ listening mode. On &FED; systems, use the
+ option to run vncviewer as a listener.
+ In a terminal window, enter the command:
vncviewer -listen
@@ -364,6 +409,9 @@
To enable remote access to a text mode installation, use the
+
+ Telnet
+
option at the
boot:
prompt:
@@ -396,7 +444,11 @@
Automating the Installation with Kickstart
- A Kickstart file specifies settings for an
+ A
+
+ Kickstart
+
+ Kickstart file specifies settings for an
installation. Once booted, the installation system may read a
Kickstart file and carry out the installation process without
requiring any further input from a user.
@@ -568,10 +620,13 @@
- Hardware manufacturers may supply driver disks for &FED; with
- the device, or provide image files to prepare the disks. To
- obtain the latest drivers, download the correct file from the
- website of the manufacturer.
+ Hardware manufacturers may supply
+
+ driver disks
+
+ driver disks for &FED; with the device, or provide image files
+ to prepare the disks. To obtain the latest drivers, download the
+ correct file from the website of the manufacturer.
@@ -618,7 +673,7 @@
The installation system may also read drivers from disk images
that are held on network servers. Refer to
for the supported sources of
- driver image files.
+ driver disk image files.
Driver Disk Image Sources
@@ -907,8 +962,12 @@
- To boot your computer in memory testing mode, enter
- memtest86 at the
+ To boot your computer in
+
+ memory testing mode
+
+ memory testing mode, enter memtest86 at
+ the
boot:
prompt. The first test starts immediately. By default,
memtest86 carries out a total of ten tests.
@@ -922,11 +981,16 @@
Booting Your Computer with the Rescue Mode
-
-
- 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
+
+ rescue mode
+
+
+ You may boot a command-line Linux system from either a
+
+ rescue discs
+
+ 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.
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- fedora-install-guide-bootloader-en.xml 9 Jun 2005 22:36:07 -0000 1.13
+++ fedora-install-guide-bootloader-en.xml 29 Jan 2006 20:37:55 -0000 1.14
@@ -1,39 +1,40 @@
+
Boot Loader
-
A boot loader is a small program that reads
and launches the operating system. &FC; uses the
- GRUB boot loader by default. If you have
+
+ GRUB
+ configuring
+ boot loader
+
+ GRUB boot loader by default. If you have
multiple operating systems, the boot loader determines which one to
boot, usually by offering a menu.
-
- You may have a boot loader installed on your system already. An
+ You may have a boot loader installed on your system already. An
operating system may install its own preferred boot loader, or you
may have installed a third-party boot loader.If your boot loader
does not recognize Linux partitions, you may not be able to boot
- &FC;. Use GRUB as your boot loader to
- boot Linux and most other operating systems. Follow the directions
+ &FC;. Use GRUB as your boot loader to
+ boot Linux and most other operating systems. Follow the directions
in this section to install GRUB.
-
Installing GRUB
+
If you install GRUB, it may overwrite your existing boot loader.
-
The following screen displays boot loader configuration options.
-
- Boot Loader Configuration Screen
-
+ Boot Loader Configuration Screen
@@ -46,18 +47,19 @@
-
Keeping Your Existing Boot Loader Settings
+
By default, the installation program installs GRUB in the
- master boot record,
- master boot record
- or MBR, of the device for the root
- file system. To change or decline installation of a new boot
- loader, select the Change boot loader
- button. The dialog shown in
- allows you to avoid
+ master boot record,
+
+ master boot record
+
+ or MBR, of the device for the root file system.
+ To change or decline installation of a new boot loader, select the
+ Change boot loader button. The dialog shown
+ in allows you to avoid
installing or changing your existing boot loader settings.
@@ -75,69 +77,67 @@
- Boot Loader Required
+ Boot Loader Required
+
- Your computer must have GRUB or another boot loader installed
- in order to start, unless you create a separate startup
- disk to boot from.
-
-
- Booting Additional Operating Systems
-
+ Booting Additional Operating Systems
+
If you have other operating systems already installed, &FC;
attempts to automatically detect and configure
- GRUB to boot them. You may manually
+ GRUB to boot them. You may manually
configure any additional operating systems if
- GRUB does not detect them. To
- add, remove, or change the detected operating system settings,
- use the options provided.
+ GRUB does not detect them. To add,
+ remove, or change the detected operating system settings, use the
+ options provided.
+
-
- Add
-
+ Add
- Press the Add button to include an
- additional operating system in GRUB. &FC; displays the
- dialog shown in Add button to include an
+ additional operating system in GRUB. &FC; displays the
+ dialog shown in
+ .
-
+
- Select the disk partition which contains the bootable
- operating system from the drop-down list and give the entry
- a label. GRUB displays this
- label in its boot menu.
-
+ Select the disk partition which contains the bootable
+ operating system from the drop-down list and give the entry
+ a label. GRUB displays this label
+ in its boot menu.
+
+
-
- Edit
-
-
-
- To change an entry in the GRUB boot menu, select the entry
- and then select Edit.
-
+ Edit
+
+
+ To change an entry in the GRUB boot menu, select the entry
+ and then select Edit.
+
+
-
- Delete
-
+ Delete
- To remove an entry from the GRUB boot menu, select the entry
- and then select Delete.
-
+ To remove an entry from the GRUB boot menu, select the entry
+ and then select Delete.
+
@@ -156,42 +156,40 @@
-
-
- Setting a Boot Loader Password
-
+ Setting a Boot Loader Password
+
GRUB reads many file systems without
- the help of an operating system. An operator can interrupt the
+ the help of an operating system. An operator can interrupt the
booting sequence to choose a different operating system to boot,
- change boot options, or recover from a system error. However, these
- functions may introduce serious security risks in some
- environments. You can add a password to
+ change boot options, or recover from a system error. However,
+ these functions may introduce serious security risks in some
+ environments. You can add a password to
GRUB so that the operator must enter
the password to interrupt the normal boot sequence.
GRUB Passwords Not Required
- You may not require a GRUB password
- if your system only has trusted operators, or is physically
- secured with controlled console access.
+ You may not require a GRUB password
+ if your system only has trusted operators, or is physically
+ secured with controlled console access.
- However, if there is a chance someone can get physical access to
- the keyboard and monitor of your computer, that person can
- reboot the system and access GRUB.
- This is where a password is helpful.
+ However, if there is a chance someone can get physical access to
+ the keyboard and monitor of your computer, that person can
+ reboot the system and access GRUB.
+ This is where a password is helpful.
To set a boot password, select the Use a boot loader
- password checkbox. The Change
- password button will become active. Select
+ password checkbox. The Change
+ password button will become active. Select
Change password to display the dialog
- below. Type the desired password, and then confirm it by typing
- it again in the spaces provided.
+ below. Type the desired password, and then confirm it by typing it
+ again in the spaces provided.
Entering A Boot Password
@@ -211,84 +209,94 @@
Choose a Good Password
Choose a password that is easy for you to remember but hard for
- others to guess.
+ others to guess.
Forgotten <application>GRUB</application> Passwords
+
GRUB stores the password in encrypted
- form, so it cannot be read or recovered. If
- you forget the boot password, boot the system normally and then
- change the password entry in the
- /boot/grub/grub.conf file. If you cannot
- boot, you may be able to use the "rescue" mode on the first &FC;
- installation disc to reset the GRUB password.
+ form, so it cannot be read or recovered. If
+ you forget the boot password, boot the system normally and then
+ change the password entry in the
+ /boot/grub/grub.conf file. If you cannot
+ boot, you may be able to use the "rescue" mode on the first &FC;
+ installation disc to reset the GRUB password.
+
If you do need to change the GRUB
- password, use the grub-md5-crypt utility. For
+ password, use the grub-md5-crypt utility. For
information on using this utility, use the command man
- grub-md5-crypt in a terminal window to read the manual
+ grub-md5-crypt in a terminal window to read the manual
pages.
-
-
- Advanced Boot loader Options
-
+ Advanced Boot loader Options
+
- The default boot options are adequate for most situations. The
+ The default boot options are adequate for most situations. The
installation program writes the GRUB
boot loader in the
- master boot record
- master boot record (MBR),
- overwriting any existing boot loader.
+ master boot record
+
+ master boot record (MBR), overwriting any
+ existing boot loader.
+
Tto keep your current boot loader in the MBR, use
the advanced settings to place GRUB in
the first sector of the partition holding the Linux root file
system.
+
You may also need the advanced options if your
BIOS enumerates your disk devices differently
- than &FC; expects. On a few systems, &FC; may not configure the
+ than &FC; expects. On a few systems, &FC; may not configure the
disk drive geometry for large disks correctly because of a broken
- BIOS. To work around this problem, mark the
+ BIOS. To work around this problem, mark the
Force LBA32 checkbox.
+
The Linux kernel usually auto-detects its environment correctly,
- and no additional kernel parameters are needed. However, you may provide
- any needed kernel parameter using the advanced boot
- loader options.
+ and no additional kernel parameters are needed. However, you may
+ provide any needed kernel parameter using the advanced boot loader
+ options.
+
- Kernel Parameters
+ Kernel Parameters
+
For a partial list of the kernel command line parameters, type
- the following command in a terminal window: man
- bootparam. For a comprehensive and authoritative
- list, refer to the documentation provided in the kernel sources.
+ the following command in a terminal window: man
+ bootparam. For a comprehensive and authoritative
+ list, refer to the documentation provided in the kernel sources.
+
To alter any of these settings, mark the Configure
- advanced boot loader options checkbox. Select
- Next and the menu shown in checkbox. Select
+ Next and the menu shown in
+ appears.
+
- Optional Menu
+ Optional Menu
+
&FC; displays the following advanced boot options menu
- only if the advanced configuration checkbox
- described above has been selected.
+ only if the advanced configuration checkbox
+ described above has been selected.
@@ -305,9 +313,7 @@
-
-
-
+
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- fedora-install-guide-firstboot-en.xml 26 Jan 2006 00:15:39 -0000 1.18
+++ fedora-install-guide-firstboot-en.xml 29 Jan 2006 20:37:55 -0000 1.19
@@ -3,8 +3,12 @@
First Boot
- The Setup Agent launches the first time
- that you start a new &FC; system. Use Setup
+ The
+
+ Setup Agent
+
+ Setup Agent launches the first time that
+ you start a new &FC; system. Use Setup
Agent to configure the system for use before you log
in.
@@ -80,6 +84,7 @@
The
firewall
+ configuringfirewall built into &FC; checks every
incoming and outgoing network connection on your machine against a
@@ -90,9 +95,14 @@
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
- permit only Secure SHell (SSH) connections from other systems. You
- may make changes on this screen to allow access to specific
- network services on your &FED; system.
+ permit only
+
+ SSH (Secure SHell)
+ firewall configuration
+
+ SSH (Secure SHell) connections from other systems. You may make
+ changes on this screen to allow access to specific network
+ services on your &FED; system.
@@ -157,6 +167,7 @@
The
&SEL;
+ configuring&SEL; (Security Enhanced Linux) framework
is part of &FC;. &SEL; limits the actions of both users and
@@ -195,7 +206,7 @@
breach of security policies only causes an error message to
appear. No activities are actually prohibited when &SEL; is
installed in this mode. You may change the &SEL; mode to
- Active at any time after booting.
+ Enforcing at any time after booting.
Index: fedora-install-guide-packageselection-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- fedora-install-guide-packageselection-en.xml 26 Jan 2006 00:15:39 -0000 1.17
+++ fedora-install-guide-packageselection-en.xml 29 Jan 2006 20:37:55 -0000 1.18
@@ -2,9 +2,10 @@
Package Selection
+ TEXT SUBJECT TO CHANGE: The package selection screen is still being developed.
By default, the &FED; installation process loads a selection of
- software that is suitable for a desktop system. This screen enables
+ software that is suitable for a desktop system. The package selection screen enables
you to customize the set of software to match your requirements.
@@ -80,6 +81,13 @@
.
+
+ Core Software
+
+ Mention some base stuff that is part of every &FC; system: SMTP, SSH, CUPS, NFS, Python and yum...
+
+
+
Additional Language Support
Index: fedora-install-guide-techref-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-techref-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-techref-en.xml 23 Jan 2006 23:24:09 -0000 1.5
+++ fedora-install-guide-techref-en.xml 29 Jan 2006 20:37:55 -0000 1.6
@@ -5,6 +5,9 @@
This document provides a reference for using the &FED; installation
software, known as anaconda. To learn more about
+
+ Anaconda
+ anaconda, visit the project webpage:
.
@@ -18,7 +21,12 @@
Boot Loader
- &FED; uses the GRUB boot loader. Refer to
+ &FED; uses the
+
+ GRUB
+ documentation
+
+ GRUB boot loader. Refer to
for more
information.
@@ -40,9 +48,13 @@
Audio Support
- The Linux kernel used by &FED; incorporates ALSA (Advanced
- Linux Sound Architecture). For more information about ALSA,
- refer to the project website:
+ The Linux kernel used by &FED; incorporates
+
+ ALSA (Advanced
+ Linux Sound Architecture)
+
+ ALSA (Advanced Linux Sound Architecture). For more information
+ about ALSA, refer to the project website:
.
@@ -53,6 +65,9 @@
Both the installation system and &FED; itself use the
+
+ Xorg
+ Xorg suite to provide graphical
capabilities. Components of Xorg manage the
display, keyboard and mouse for the desktop environments that
@@ -66,9 +81,14 @@
Remote Displays
- &FC; and anaconda include VNC to enable
- remote access to graphical displays. For more information
- about VNC, refer to the documentation on the RealVNC website:
+ &FC; and anaconda include
+
+ VNC (Virtual Network Computing)
+ documentation
+
+ VNC (Virtual Network Computing) software to enable remote
+ access to graphical displays. For more information about VNC,
+ refer to the documentation on the RealVNC website:
.
@@ -90,9 +110,42 @@
+ Remote System Access
+
+
+ &FC; incorporates the
+
+ OpenSSH
+ SSH
+
+ OpenSSH suite to provide remote access to the system. The SSH
+
+ SSH (Secure SHell)
+ documentation
+
+ service enables a number of functions, which include access to
+ the command-line from other systems, remote command execution,
+ and network file transfers. During the installation process
+ anaconda may use the scp
+
+ scp
+ SSH
+
+ feature of OpenSSH to transfer crash reports to remote
+ systems. Refer to the OpenSSH website for more information:
+ .
+
+
+
+
+ Access Control
+
+ &SEL;
+ documentation
+
&SEL; provides Mandatory Access Control (MAC) capabilities
that supplement the standard Linux security features. Refer to
the &SEL; FAQ for more information:
@@ -105,8 +158,14 @@
Firewall
- &FED; uses the netfilter framework. The
- Netfilter project website provides documentation for both netfilter, and the
+ The Linux kernel used by &FED; incorporates the
+ netfilter framework to provide
+
+ firewall
+ documentation
+
+ firewall features. The Netfilter project website provides
+ documentation for both netfilter, and the
iptables administration facilities:
.
@@ -117,8 +176,13 @@
Software Installation
- &FED; uses yum to manage the RPM packages
- that make up the system. Refer to
+ &FED; uses
+
+ yum
+ documentation
+
+ yum to manage the RPM packages that make up
+ the system. Refer to
for more
information.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-info.xml 26 Jan 2006 00:15:39 -0000 1.5
+++ rpm-info.xml 29 Jan 2006 20:37:55 -0000 1.6
@@ -28,10 +28,15 @@
+
+
+
+ Updated indexing.
+
- Updated Package Selection screen for test2.
+ Updated Package Selection screen for test2.
From fedora-docs-commits at redhat.com Mon Jan 30 00:29:13 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Sun, 29 Jan 2006 19:29:13 -0500
Subject: release-notes/xmlbeats wikixml2fdpxml,NONE,1.1
Message-ID: <200601300029.k0U0TD65019477@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes/xmlbeats
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19460
Added Files:
wikixml2fdpxml
Log Message:
This script does some of what is needed, but not all, it needs a language such as perl or python to do some kung-fu. It is also not a modular script or otherwise well written, it's just a hack to get started.
--- NEW FILE wikixml2fdpxml ---
#!/bin/bash
#
# This file can be completely replaced with a better tool written in
# $LANGUAGE of someone's choice
#
# Original shell script - 29-Jan-2005
# kwade at redhat.com
# Manually rename some files to include their wiki namespace
mv Beats/x86_64.xml Beats/ArchSpecificx86_64.xml
mv Beats/x86.xml Beats/ArchSpecificx86.xml
mv Beats/GCC.xml Beats/DevelToolsGCC.xml
mv Beats/SELinux.xml Beats/SecuritySELinux.xml
# Add the base language extension to the files
ls Beats/ > xmlfiles
for i in `cat xmlfiles`;
do
echo $i | sed 's/.xml/-en.xml/g' > newfilename;
mv Beats/$i Beats/`cat newfilename`;
done
rm xmlfiles newfilename
echo "done"
# Right here is where we want to call perl-fu or python-fu
# to follow this pseudo-code
#
# for each();
# do
# get(contents of ) == $title;
# replace(" " with "-") == $idattrib;
# insert($idattrib) -> ;
# done
From fedora-docs-commits at redhat.com Mon Jan 30 00:36:13 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Sun, 29 Jan 2006 19:36:13 -0500
Subject: release-notes RELEASE-NOTES-en.xml, 1.18, 1.19 RELEASE-NOTES-it.xml,
1.9, 1.10 RELEASE-NOTES-ja_JP.xml, 1.5,
1.6 RELEASE-NOTES-pa.xml, 1.2, 1.3 RELEASE-NOTES-ru.xml, 1.5,
1.6 RELEASE-NOTES-zh_CN.xml, 1.7, 1.8
Message-ID: <200601300036.k0U0aDRw019581@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19553
Modified Files:
RELEASE-NOTES-en.xml RELEASE-NOTES-it.xml
RELEASE-NOTES-ja_JP.xml RELEASE-NOTES-pa.xml
RELEASE-NOTES-ru.xml RELEASE-NOTES-zh_CN.xml
Log Message:
Adding colophon for all languages. Very sorry that this did not happen for test2, it was a mistake. This is included now forevermore. A big personal thanks to all release notes contributors.
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- RELEASE-NOTES-en.xml 24 Jan 2006 22:10:39 -0000 1.18
+++ RELEASE-NOTES-en.xml 30 Jan 2006 00:36:05 -0000 1.19
@@ -82,4 +82,5 @@
&LEGACY;
&PACKAGE-CHANGES;
&PROJECT-OVERVIEW;
+ &COLOPHON;
Index: RELEASE-NOTES-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- RELEASE-NOTES-it.xml 24 Jan 2006 22:10:39 -0000 1.9
+++ RELEASE-NOTES-it.xml 30 Jan 2006 00:36:05 -0000 1.10
@@ -82,4 +82,5 @@
&LEGACY;
&PACKAGE-CHANGES;
&PROJECT-OVERVIEW;
+ &COLOPHON;
Index: RELEASE-NOTES-ja_JP.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ja_JP.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- RELEASE-NOTES-ja_JP.xml 24 Jan 2006 22:10:39 -0000 1.5
+++ RELEASE-NOTES-ja_JP.xml 30 Jan 2006 00:36:05 -0000 1.6
@@ -81,6 +81,7 @@
&LEGACY;
&PACKAGE-CHANGES;
&PROJECT-OVERVIEW;
+ &COLOPHON;
+
+
+ Fix hostname error
+ Additional style editing, division of procedures into more readable
sectionsUlteriori aggiunte di stile, divisioni delle procedure in sezioni pi??
- leggibili
+ leggibili
@@ -54,7 +57,7 @@
First draft
- Prima bozza
-
+ Prima bozza
+
From fedora-docs-commits at redhat.com Mon Jan 30 19:11:31 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 30 Jan 2006 14:11:31 -0500
Subject: example-tutorial para-en.xml, NONE, 1.1 Makefile, 1.26,
1.27 example-tutorial-en.xml, 1.22, 1.23
Message-ID: <200601301911.k0UJBVau027250@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27221
Modified Files:
Makefile example-tutorial-en.xml
Added Files:
para-en.xml
Log Message:
Utilize the proper idiom to obtain the content of some
useless paragraph.
--- NEW FILE para-en.xml ---
This paragraph was obtained via an
<xi:include> element, just for an
example.
Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- Makefile 17 Jan 2006 21:11:02 -0000 1.26
+++ Makefile 30 Jan 2006 19:11:23 -0000 1.27
@@ -16,6 +16,7 @@
#
LANGUAGES = en de
DOCBASE = example-tutorial
+XMLEXTRAFILES-en= para-en.xml
#
######################################################
include ../docs-common/Makefile.common
Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- example-tutorial-en.xml 21 Jan 2006 19:32:04 -0000 1.22
+++ example-tutorial-en.xml 30 Jan 2006 19:11:23 -0000 1.23
@@ -18,7 +18,7 @@
-&FDP-INFO;
+ &FDP-INFO;
Some Section
@@ -30,7 +30,13 @@
since those tags will make sections less modular, i.e., harder to
relocate without changing a lot of other markup.
-
+
+
+
+ Could not find the para-en.xml file
+
+
+
Keep text within the title tags on the same
line as the tags. Nesting the title on a separate line from the
@@ -51,7 +57,8 @@
avoided. To install any RPM package, use the following syntax:
-rpm -ivh pkgname-version.arch.rpm
+rpm -ivh pkgname-version.arch.rpm
+
Notice that the screen section is entirely
@@ -64,7 +71,8 @@
sample.
-grep snmptrap /etc/services
+grep snmptrap /etc/services
+ snmptrap 162/udp snmp-trap # Traps for SNMP
@@ -157,6 +165,41 @@
+
+ Including External Files
+
+
+ An alternative to declaring and using system entities to obtain
+ the content from other files is to use an
+ XInclude reference. These work similarly to
+ include files in familiar programming languages. Using the
+ XInclude feature allows an entire file, or just a part of it, to
+ be copied into the current document. External files are referenced
+ using an URI so they may be located anywhere,
+ even across the Internet.
+
+
+
+ The official documentation for the XInclude feature may be found
+ at the web site. A
+ somewhat dated description at
+
+ may be a more readible starting reference.
+
+
+
+ Using the XInclude facility with DocBook requires a special
+ technique to allow the document to pass XML validation. Often
+ examples show adding the phrase
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ to a top-level element such as
+ <chapter>. Unfortunately this
+ causes the DocBook file to fail validation. The solution is to
+ place the namespace declaration directly in the <xi:include>
+ element:
+
+
+
From fedora-docs-commits at redhat.com Mon Jan 30 19:14:40 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 30 Jan 2006 14:14:40 -0500
Subject: example-tutorial para-en.xml,1.1,1.2
Message-ID: <200601301914.k0UJEedw027284@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27256
Modified Files:
para-en.xml
Log Message:
When using the construct to obtain content from an
external XML file, that file can include its own element.
Any entities defined in the external file must exactly match the same
entity declared in the main document, if any.
Entities defined in the external file are NOT visible in the
including document.
Index: para-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/para-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- para-en.xml 30 Jan 2006 19:11:23 -0000 1.1
+++ para-en.xml 30 Jan 2006 19:14:32 -0000 1.2
@@ -1,3 +1,12 @@
+
+
+
+
+]>
+
This paragraph was obtained via an
<xi:include> element, just for an
From fedora-docs-commits at redhat.com Mon Jan 30 19:17:13 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 30 Jan 2006 14:17:13 -0500
Subject: example-tutorial example-tutorial-en.xml,1.23,1.24
Message-ID: <200601301917.k0UJHDhO027352@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27328
Modified Files:
example-tutorial-en.xml
Log Message:
Oops, too quick to commit the good news; remove the
usage blurb since it doesn't belong here: just the usage is
appropriate.
Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- example-tutorial-en.xml 30 Jan 2006 19:11:23 -0000 1.23
+++ example-tutorial-en.xml 30 Jan 2006 19:17:05 -0000 1.24
@@ -165,41 +165,6 @@
-
- Including External Files
-
-
- An alternative to declaring and using system entities to obtain
- the content from other files is to use an
- XInclude reference. These work similarly to
- include files in familiar programming languages. Using the
- XInclude feature allows an entire file, or just a part of it, to
- be copied into the current document. External files are referenced
- using an URI so they may be located anywhere,
- even across the Internet.
-
-
-
- The official documentation for the XInclude feature may be found
- at the web site. A
- somewhat dated description at
-
- may be a more readible starting reference.
-
-
-
- Using the XInclude facility with DocBook requires a special
- technique to allow the document to pass XML validation. Often
- examples show adding the phrase
- xmlns:xi="http://www.w3.org/2001/XInclude"
- to a top-level element such as
- <chapter>. Unfortunately this
- causes the DocBook file to fail validation. The solution is to
- place the namespace declaration directly in the <xi:include>
- element:
-
-
-
From fedora-docs-commits at redhat.com Mon Jan 30 20:26:24 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Mon, 30 Jan 2006 15:26:24 -0500
Subject: translation-quick-start-guide rpm-info.xml,1.6,1.7
Message-ID: <200601302026.k0UKQO04030158@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30140/translation-quick-start-guide
Modified Files:
rpm-info.xml
Log Message:
updated italian string
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rpm-info.xml 30 Jan 2006 18:37:23 -0000 1.6
+++ rpm-info.xml 30 Jan 2006 20:26:17 -0000 1.7
@@ -41,6 +41,7 @@
Fix hostname error
+ Risolto errore hostname
From fedora-docs-commits at redhat.com Mon Jan 30 20:32:06 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Mon, 30 Jan 2006 15:32:06 -0500
Subject: translation-quick-start-guide rpm-info.xml,1.7,1.8
Message-ID: <200601302032.k0UKW6LB030274@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/translation-quick-start-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30256/translation-quick-start-guide
Modified Files:
rpm-info.xml
Log Message:
correction to details tag
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/rpm-info.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- rpm-info.xml 30 Jan 2006 20:26:17 -0000 1.7
+++ rpm-info.xml 30 Jan 2006 20:31:58 -0000 1.8
@@ -58,7 +58,7 @@
First draft
- Prima bozza
+ Prima bozza
From fedora-docs-commits at redhat.com Tue Jan 31 17:58:27 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 31 Jan 2006 12:58:27 -0500
Subject: docs-common Makefile.common,1.36,1.37
Message-ID: <200601311758.k0VHwRZe014344@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14321
Modified Files:
Makefile.common
Log Message:
Doh! Now the "make DRAFT=no html" or "make DRAFT=yes html" actually
work. Defaults to "make DRAFT=yes".
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- Makefile.common 30 Jan 2006 10:32:17 -0000 1.36
+++ Makefile.common 31 Jan 2006 17:58:20 -0000 1.37
@@ -33,28 +33,28 @@
#########################################################################
# Supply default values for the boilerplate files _unless_ the user has
# provided their own values.
-ifeq (${FDPDIR},)
+ifeq "${FDPDIR}" ""
FDPDIR = $(PWD)/..
endif
-ifeq (${FDPBIN},)
+ifeq "${FDPBIN}" ""
FDPBIN = ${FDPDIR}/docs-common/bin
endif
-ifeq (${XSLPDF},)
+ifeq "${XSLPDF}" ""
XSLPDF = ${FDPDIR}/docs-common/xsl/main-pdf.xsl
endif
-ifeq (${XSLHTML},)
+ifeq "${XSLHTML}" ""
XSLHTML = ${FDPDIR}/docs-common/xsl/main-html.xsl
endif
-ifeq (${XSLHTMLNOCHUNKS},)
+ifeq "${XSLHTMLNOCHUNKS}" ""
XSLHTMLNOCHUNKS = ${FDPDIR}/docs-common/xsl/main-html-nochunks.xsl
endif
-ifeq (${HTMLCSS},)
+ifeq "${HTMLCSS}" ""
HTMLCSS = ${FDPDIR}/docs-common/css/fedora-draft.css
endif
-ifeq (${DRAFT},)
+ifeq "${DRAFT}" ""
DRAFT = yes
endif
-ifeq (${RPMINFO},)
+ifeq "${RPMINFO}" ""
RPMINFO = ${PWD}/rpm-info.xml
endif
#########################################################################
@@ -122,8 +122,8 @@
mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
cp ${HTMLCSS} $(DOCBASE)-$(1)/fedora.css
-ifeq (${DRAFT},"yes")
- cp ${FDPDIR}/docs-common/images/watermark-$(1).png
+ifeq "${DRAFT}" "yes"
+ cp ${FDPDIR}/docs-common/images/watermark-$(1).png $(DOCBASE)-$(1)/watermark.png
endif
[ ! -d figs ] || copy-figs -v -f '*.png' \
-l $(1) figs $(DOCBASE)-$(1)