desktop-user-guide/FC-6 - New directory
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/desktop-user-guide/FC-6
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31970/desktop-user-guide/FC-6
Log Message:
Directory /cvs/docs/desktop-user-guide/FC-6 added to the repository
17 years, 2 months
desktop-user-guide - New directory
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/desktop-user-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31950/desktop-user-guide
Log Message:
Directory /cvs/docs/desktop-user-guide added to the repository
17 years, 2 months
documentation-guide/en_US writing-guidelines.xml,1.5,1.6
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/documentation-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26927
Modified Files:
writing-guidelines.xml
Log Message:
Some retagging and deconfusification
Index: writing-guidelines.xml
===================================================================
RCS file: /cvs/docs/documentation-guide/en_US/writing-guidelines.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- writing-guidelines.xml 18 Feb 2007 14:24:33 -0000 1.5
+++ writing-guidelines.xml 18 Feb 2007 22:59:19 -0000 1.6
@@ -46,18 +46,9 @@
<primary>naming conventions</primary>
</indexterm>
- <para>This section explains the ID naming convention. For
- example:</para>
-
- <screen><![CDATA[<chapter id="ch-unique-name-of-chapter">
-
-<section id="sn-install-make-disks">
-
-<figure id="fig-redhat-config-kickstart-basic">]]></screen>
-
- <para>IDs are unique identifiers, allowing DocBook XML to know where
- to cross-reference a section, chapter, or other element. The
- following general rules apply to IDs:</para>
+ <para>This section explains the ID naming convention. IDs are
+ unique identifiers that allow DocBook XML to cross-reference a
+ section, chapter, or other element.</para>
<indexterm>
<primary>XML tags</primary>
@@ -68,19 +59,40 @@
<primary>naming conventions</primary>
<secondary>rules for defining an ID</secondary>
</indexterm>
-
- <para>Keep it as short and simple as possible.</para>
- <para>Start the ID with the special short two-character label. This
- makes URLs and other references to this ID human readable, by
- self-identifying the XML container type.</para>
+ <para>The following general rules apply to IDs:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Keep an ID as short and simple as possible.</para>
+ </listitem>
+ <listitem>
+ <para>Start the ID with the special short two-character label.
+ This makes URLs and other references to this ID human
+ readable, by self-identifying the XML container type.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ <xref linkend="ex-id-usage"/> demonstrates some example ID
+ attributes used properly.
+ </para>
+
+ <example id="ex-id-usage">
+ <title>Proper ID Usage</title>
+ <screen><![CDATA[<chapter id="ch-unique-name-of-chapter">
+
+<section id="sn-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">]]></screen>
+ </example>
<table id="tb-id-two-char-naming-conventions">
<title>Two-Character Naming Conventions</title>
<tgroup cols="2">
- <colspec colnum="1" colname="tag" colwidth="100"/>
- <colspec colnum="2" colname="prefix" colwidth="100"/>
+ <colspec colnum="1" colname="tag"/>
+ <colspec colnum="2" colname="prefix"/>
<thead>
<row>
<entry>Tag</entry>
@@ -124,17 +136,13 @@
</tgroup>
</table>
- <para>Use the title of the item as the ID. If your title is not
- unique, there is either a problem you need to fix (titles should
- be unique within a document), or it is part of a template and
- should reflect the containing chapter/section of the template. For
- example:</para>
+ <para>Use the title of the item as the ID. Make your titles unique
+ within a document to prevent conflicts. For example:</para>
<screen><![CDATA[<chapter id="ch-how-to-fold-laundry">
-<title>How To Fold Laundry</title>]]></screen>
-
- <screen><![CDATA[<section id="sn-folding-shirts">
-<title>Folding Shirts</title>]]></screen>
+ <title>How To Fold Laundry</title>
+ <section id="sn-folding-shirts">
+ <title>Folding Shirts</title>]]></screen>
<indexterm>
<primary>xml tags</primary>
@@ -320,17 +328,25 @@
<tertiary>important</tertiary>
</indexterm>
- <para>There are five types of admonitions in DocBook: Caution,
- Important, Note, Tip, and Warning. All of the admonitions have
- the same structure: an optional Title followed by paragraph-level
+ <para>There are five types of admonitions in DocBook: <sgmltag
+ class="element">caution</sgmltag>, <sgmltag
+ class="element">important</sgmltag>, <sgmltag
+ class="element">note</sgmltag>, <sgmltag
+ class="element">tip</sgmltag>, and <sgmltag
+ class="element">warning</sgmltag>. All of the admonitions have
+ the same structure: an optional <sgmltag
+ class="element">title</sgmltag> followed by paragraph-level
elements. The DocBook DTD does not impose any specific semantics
on the individual admonitions. For example, DocBook does not
- mandate that Warnings be reserved for cases where bodily harm can
- result.</para>
+ mandate that a <sgmltag class="element">warning</sgmltag> is
+ reserved for cases where bodily harm can result.</para>
<section id="sn-xml-notesetc">
- <title>Creating Notes, Tips, Cautions, Importants, and
- Warnings</title>
+ <title>Creating a <sgmltag class="element">note</sgmltag>,
+ <sgmltag class="element">tip</sgmltag>, <sgmltag
+ class="element">caution</sgmltag>, <sgmltag
+ class="element">important</sgmltag>, or <sgmltag
+ class="element">warning</sgmltag></title>
<indexterm>
<primary>XML tags</primary>
@@ -358,24 +374,27 @@
</indexterm>
<para>There are several ways to bring attention to text within a
- document. A <emphasis>Note</emphasis> is used to bring
+ document. A <emphasis><sgmltag
+ class="element">note</sgmltag></emphasis> is used to bring
additional information to the users' attention. A
- <emphasis>Tip</emphasis> is used to show the user helpful
- information or another way to do something. A
- <emphasis>Caution</emphasis> is used to show the user they must
- be careful when attempting a certain step. An
- <emphasis>Important</emphasis> tag set can be used to show the
- user a piece of information that should not be overlooked. While
- this information may not change anything the user is doing, it
- should show the user that this piece of information could be
- vital. A <emphasis>Warning</emphasis> is used to show the reader
- that their current setup will change or be altered, such as
- files being removed, and they should not choose this operation
- unless they are alright with the consequences.</para>
-
- <para>The following lines of code will show the basic setup for
- each case as mentioned above, along with an example of how it
- would be displayed in the HTML.</para>
+ <emphasis><sgmltag class="element">tip</sgmltag></emphasis> is
+ used to show the user helpful information or another way to do
+ something. A <emphasis><sgmltag
+ class="element">caution</sgmltag></emphasis> is used to show
+ the user they must be careful when attempting a certain step. An
+ <emphasis><sgmltag
+ class="element">important</sgmltag></emphasis> tag set can
+ be used to show the user a piece of information that should not
+ be overlooked. While this information may not change anything
+ the user is doing, it should show the user that this piece of
+ information could be vital. A <emphasis><sgmltag
+ class="element">warning</sgmltag></emphasis> is used to show
+ the reader that their current setup will change or be altered,
+ such as files being removed, and they should not choose this
+ operation unless they are alright with the consequences.</para>
+
+ <para>The following lines of code show the basic setup for each
+ case mentioned above, along with its appearance in HTML.</para>
<screen><![CDATA[<note>
<title>Note</title>
@@ -547,39 +566,56 @@
<term>Text Screenshot</term>
<listitem>
<para>Textual screen information is also useful for readers.
- If you use a graphical screenshot to illustrate a function,
- and the textual mode has identical functions, you should not
- include both, unless omitting either would make your
- description unclear. You should make your information
- generic over specific. Omit the username and machine
- information, and separate what the user types from sample
- command output. Also, in <command>screen</command> tags,
- what the user types should be in
- <command>userinput</command> tags, and what the user is
- shown as output should be in
- <command>computeroutput</command> tags. For example, the
- usage in
- <xref linkend="ex-text-screenshot-bad"/> should look like
- <xref
- linkend="ex-text-screenshot-good"/>.
+ Follow these guidelines for textual screenshots:</para>
+ <itemizedlist>
+ <listitem>
+ <para>If you use a graphical screenshot to illustrate a
+ function, and the textual mode has identical functions,
+ do not include both, unless omitting either would make
+ your description unclear.</para>
+ </listitem>
+ <listitem>
+ <para>Make your information generic over specific, and
+ omit any username and machine information if possible.
+ Do not include the shell prompt unless it is vital to
+ the demonstration.</para>
+ </listitem>
+ <listitem>
+ <para>Separate what the user types from sample command
+ output.</para>
+ </listitem>
+ <listitem>
+ <para>When using <sgmltag class="element">screen</sgmltag>
+ to demonstrate a procedure, use <sgmltag
+ class="element">userinput</sgmltag> tags to show what
+ the user types, and use <sgmltag
+ class="element">computeroutput</sgmltag> tags to show
+ the resulting output.</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <xref linkend="ex-text-screenshot-good"/> is an example of
+ textual screenshot usage.
</para>
- <example id="ex-text-screenshot-bad">
- <title>Incorrect Textual Screenshot</title>
- <screen><userinput>ps ax | grep ssh</userinput>
-<computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
- 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
- 8235 ? S 0:00 ssh -Nf rocky(a)philadelphia.net -L 6667:localhost
-17223 pts/0 S 0:00 ssh rbalboa@core-router7
-17227 pts/2 S 0:10 ssh rbalboa@smbshare2
-21113 pts/7 S 1:19 ssh rocky(a)xxx.private</computeroutput></screen>
- </example>
<example id="ex-text-screenshot-good">
- <title>Correct Textual Screenshot</title>
+ <title>Correct Textual Screenshot (XML Source and
+ HTML)</title>
+ <screen><![CDATA[<example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot</title>
+ <para>To find all the currently active ssh sessions,
+ execute the following command:</para>
+ <screen><userinput>ps ax | grep ssh</userinput></screen>
+ <para>Output appears similar to the following:</para>
+ <screen><computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8032 pts/0 S 0:00 ssh user(a)host.example.com
+ 8032 pts/1 S 0:00 ssh root(a)backup.example.com</computeroutput></screen>
+</example>]]></screen>
<para>To find all the currently active ssh sessions, execute the
following command:</para>
- <screen><command>ps ax | grep ssh</command></screen>
+ <screen><userinput>ps ax | grep ssh</userinput></screen>
- <para>The output will appear similar to:</para>
+ <para>Output appears similar to the following:</para>
<screen><computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
17 years, 2 months
docs-common/css fedora-draft.css,1.4,1.5
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18534
Modified Files:
fedora-draft.css
Log Message:
Increase line height for readability - this is an EXPERIMENTAL feature (#170204)
Index: fedora-draft.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora-draft.css,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-draft.css 18 Feb 2007 20:26:08 -0000 1.4
+++ fedora-draft.css 18 Feb 2007 20:53:16 -0000 1.5
@@ -21,6 +21,10 @@
margin-right: 1.5em;
}
+p {
+ line-height: 140%;
+}
+
li p {
# display: inline;
}
17 years, 2 months
docs-common/css fedora-draft.css,1.3,1.4 fedora-plain.css,1.3,1.4
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18194
Modified Files:
fedora-draft.css fedora-plain.css
Log Message:
Make slight larger gutter for improved readability (#170204)
Index: fedora-draft.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora-draft.css,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-draft.css 4 Jun 2006 17:34:45 -0000 1.3
+++ fedora-draft.css 18 Feb 2007 20:26:08 -0000 1.4
@@ -17,6 +17,8 @@
background-image: url('watermark.png');
background-position: top center;
background-repeat: repeat;
+ margin-left: 1.5em;
+ margin-right: 1.5em;
}
li p {
Index: fedora-plain.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora-plain.css,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-plain.css 4 Jun 2006 17:34:45 -0000 1.3
+++ fedora-plain.css 18 Feb 2007 20:26:08 -0000 1.4
@@ -18,6 +18,8 @@
background-image: url('watermark.png');
background-position: top center;
background-repeat: repeat;
+ margin-left: 1.5em;
+ margin-right: 1.5em;
}
*/
17 years, 2 months
docs-common Makefile.common,1.143,1.144
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17713
Modified Files:
Makefile.common
Log Message:
OMF handling
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -r1.143 -r1.144
--- Makefile.common 17 Sep 2006 18:51:25 -0000 1.143
+++ Makefile.common 18 Feb 2007 20:04:04 -0000 1.144
@@ -196,7 +196,7 @@
# Explode the template from the doc-specific Makefile to get the
# XML files the author knows about.
$(foreach L,${LANGUAGES},$(eval $(call XMLFILES_template,${L})))
-# Append per-document dependancies
+# Append per-document dependencies
$(foreach L, ${LANGUAGES}, $(eval XMLDEPFILES-${L}+=${DOC_ENTITIES_ENT-${L}}))
$(foreach L, ${LANGUAGES}, $(eval XMLDEPFILES-${L}+=${L}/fdp-info.xml))
$(foreach L, ${LANGUAGES}, $(eval XMLDEPFILES-${L}+=${L}/${FDP_ENTITIES}))
@@ -333,6 +333,115 @@
#########################################################################
+###########
+#
+# Get or build OMF.
+#
+# If the per-doc Makefile provides a ${OMFINFILES} list, we use those.
+# If it does not:
+# 1. look for ${PRI_LANG}/*.omf.in and use those; or, failing that,
+# 2. if ${BUILDOMF} is defined, make one using XSLT and rpm-info data.
+#
+# The template OMF files are expected to use @VARNAME@ notation to
+# allow replacement of their content dynamically at build time. They
+# should retain this notation during PO/POT conversion so that
+# translators never have to worry about that content. Substitution
+# only occurs during the packaging process.
+#
+
+# FIXME: There may not be a need to have the ${PRI_LANG} prefixing
+# each entry in ${OMFINFILES}. Might be a good idea to take that out.
+
+# if OMFINFILES is empty, try and get the file list.
+# If it's still empty, and BUILDOMF is set, use that to populate the list.
+# Otherwise it stays empty. After all, we may not want them at all.
+
+ifeq "${OMFINFILES}" ""
+OMFINFILES=$(foreach F,$(wildcard ${PRI_LANG}/*.omf.in),$(shell basename ${F}))
+ifeq "${OMFINFILES}" ""
+ifdef BUILDOMF
+OMFINFILES=${PKGNAME}.omf.in
+${PRI_LANG}/${PKGNAME}.omf.in:: ${PRI_LANG}/${RPMINFO}
+ ${XSLTPROC} --stringparam lang ${PRI_LANG} \
+ --stringparam docbase ${PKGNAME} \
+ ${FDPDIR}/docs-common/packaging/omf-in.xsl \
+ $< > $@
+endif
+endif
+endif
+
+showvars::
+ @echo "OMFINFILES=\"${OMFINFILES}\""
+
+define OMFVAR_template
+$(foreach F,${OMFINFILES},$(eval OMFINFILES-${1}+=${1}/${F}))
+$(foreach F,${OMFINFILES},$(eval OMFFILES-${1}+=$(patsubst %.in,${1}/%,${F})))
+showvars-debug::
+ @echo "OMFFILES-${1}=\"${OMFFILES-${1}}\""
+endef
+
+$(foreach L,${LANGUAGES},$(eval $(call OMFVAR_template,${L})))
+
+define OMFIN_template
+.PHONY: omf-in-${1}
+omf-in-${1}:: ${OMFINFILES-${1}}
+# Treat .omf.in files just like XML... since they are!
+$(foreach F,${OMFINFILES},$(eval $(call XML_template,${1},${PRI_LANG}/${F})))
+
+clean::
+ ${RM} ${OMFINFILES-${1}}
+
+help::
+ @printf ${TFMT} 'omf-in-${1}' 'Make OMF input file for ${1}'
+
+endef
+
+$(foreach L,${OTHERS},$(eval $(call OMFIN_template,${L})))
+
+.PHONY: omf-in
+omf-in:: $(foreach L,${LANGUAGES},${OMFINFILES-${L}})
+
+help::
+ @printf ${TFMT} 'omf-in' 'Make all OMF input files'
+
+
+# To make the real OMF, just do a quick bit of sed processing.
+# The spacing in the second command is purposeful to ensure no extra
+# space appears in the sed command.
+#
+# Note the difference between @LANG@ and @LANGC@: the former is always
+# replaced by the locale name, whereas the latter is replaced by the
+# locale name *unless* the locale is en_US, in which case it is replaced
+# by "C", the fallback.
+%.omf: %.omf.in
+ sed -e 's!@RELEASE@!${VERSION}!g' $< > $@
+ sed -i 's!@DATE@!${REVDATE}!g' $@
+ sed -i 's!@LANG@!$(patsubst %/$(shell basename $<),%,$<)!g' $@
+ sed -i 's!@LANGC@!$(if $(findstring en_US,$(patsubst \
+ %/$(shell basename $<),%,$<)),C,$(patsubst \
+ %/$(shell basename $<),%,$<))!g' $@
+
+
+define OMF_template
+.PHONY: omf-${1}
+omf-${1}:: ${OMFFILES-${1}}
+
+clean::
+ ${RM} ${OMFFILES-${1}}
+
+help::
+ @printf ${TFMT} 'omf-${1}' 'Make all OMF files for ${1} locale'
+
+endef
+
+$(foreach L,${LANGUAGES},$(eval $(call OMF_template,${L})))
+
+.PHONY: omf
+omf:: $(foreach L,${LANGUAGES},${OMFFILES-${L}})
+help::
+ @printf ${TFMT} 'omf' 'Make all OMF files for all locales'
+# End of OMF ###############################
+
#########################################################################
# Rules to generate the "${LANG}/${DOC_ENTITIES}.ent" file, if used
define DOC_ENTITIES_template
17 years, 2 months
docs-common/common cvs-en.xml, 1.8, 1.9 cvs-it.xml, 1.5, 1.6 cvs-pt_BR.xml, 1.3, 1.4 cvs-pt.xml, 1.3, 1.4 cvs-zh_CN.xml, 1.3, 1.4
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17639
Modified Files:
cvs-en.xml cvs-it.xml cvs-pt_BR.xml cvs-pt.xml cvs-zh_CN.xml
Log Message:
Update translations viz. en_US version
Index: cvs-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-en.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- cvs-en.xml 5 Jan 2007 01:14:08 -0000 1.8
+++ cvs-en.xml 18 Feb 2007 20:01:41 -0000 1.9
@@ -213,7 +213,7 @@
Change the permissions of your <filename>~/.ssh</filename>
directory and your keys with the commands:
</para>
-<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
+<screen><prompt>$ </prompt><command>chmod 700 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</listitem>
</orderedlist>
Index: cvs-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-it.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- cvs-it.xml 5 Jan 2007 01:14:08 -0000 1.5
+++ cvs-it.xml 18 Feb 2007 20:01:41 -0000 1.6
@@ -211,7 +211,7 @@
Cambia i permessi della tua directory <filename>~/.ssh</filename>
e delle tue chiavi con i comandi:
</para>
-<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
+<screen><prompt>$ </prompt><command>chmod 700 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</listitem>
</orderedlist>
Index: cvs-pt_BR.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-pt_BR.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- cvs-pt_BR.xml 5 Jan 2007 01:14:08 -0000 1.3
+++ cvs-pt_BR.xml 18 Feb 2007 20:01:41 -0000 1.4
@@ -205,7 +205,7 @@
Mude as permiss��es do seu diret��rio <filename>~/.ssh</filename> e de
suas chaves com os comandos:
</para>
-<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
+<screen><prompt>$ </prompt><command>chmod 700 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</listitem>
</orderedlist>
Index: cvs-pt.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-pt.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- cvs-pt.xml 5 Jan 2007 01:14:08 -0000 1.3
+++ cvs-pt.xml 18 Feb 2007 20:01:41 -0000 1.4
@@ -176,7 +176,7 @@
<listitem>
<para>Mude as permiss��es da sua pasta <filename>~/.ssh</filename>
e das suas chaves com os comandos: </para>
-<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
+<screen><prompt>$ </prompt><command>chmod 700 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</listitem>
</orderedlist>
Index: cvs-zh_CN.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-zh_CN.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- cvs-zh_CN.xml 5 Jan 2007 01:14:08 -0000 1.3
+++ cvs-zh_CN.xml 18 Feb 2007 20:01:41 -0000 1.4
@@ -88,7 +88,7 @@
</listitem>
<listitem>
<para>��������������������������� <filename>~/.ssh</filename> ���������������������������������</para>
- <screen><prompt>$</prompt> <command>chmod 755 ~/.ssh</command>
+ <screen><prompt>$</prompt> <command>chmod 700 ~/.ssh</command>
<prompt>$</prompt> <command>chmod 644 ~/.ssh/authorized_keys</command> </screen>
</listitem>
</orderedlist>
17 years, 2 months
docs-common/common cvs-en_US.xml,1.3,1.4
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26232
Modified Files:
cvs-en_US.xml
Log Message:
Fix permissions on ~/.ssh directory.
Index: cvs-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-en_US.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- cvs-en_US.xml 5 Jan 2007 01:10:04 -0000 1.3
+++ cvs-en_US.xml 18 Feb 2007 14:33:05 -0000 1.4
@@ -212,7 +212,7 @@
Change the permissions of your <filename>~/.ssh</filename>
directory and your keys with the commands:
</para>
-<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
+<screen><prompt>$ </prompt><command>chmod 700 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</listitem>
</orderedlist>
17 years, 2 months
documentation-guide Makefile,1.12,1.13
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/documentation-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26051
Modified Files:
Makefile
Log Message:
Update list of XML files so document will validate and build
Index: Makefile
===================================================================
RCS file: /cvs/docs/documentation-guide/Makefile,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- Makefile 23 Nov 2006 02:24:37 -0000 1.12
+++ Makefile 18 Feb 2007 14:25:01 -0000 1.13
@@ -11,15 +11,16 @@
define XMLFILES_template
XMLFILES-${1}= ${1}/acknowledgments.xml \
- ${1}/docs-emacs-nxml.xml \
- ${1}/docs-emacs.xml \
- ${1}/docs-getting-files.xml \
- ${1}/docs-intro.xml \
- ${1}/docs-rh-guidelines.xml \
- ${1}/docs-style.xml \
- ${1}/docs-tutorial.xml \
- ${1}/docs-vim.xml \
- ${1}/docs-xml-tags.xml \
+ ${1}/emacs-nxml.xml \
+ ${1}/emacs.xml \
+ ${1}/getting-files.xml \
+ ${1}/intro.xml \
+ ${1}/module-struct.xml \
+ ${1}/writing-guidelines.xml \
+ ${1}/style.xml \
+ ${1}/tutorial.xml \
+ ${1}/vim.xml \
+ ${1}/xml-tags.xml \
${1}/documentation-guide.xml
endef
17 years, 2 months
documentation-guide/en_US documentation-guide.xml, 1.5, 1.6 writing-guidelines.xml, 1.4, 1.5
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/documentation-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26026/en_US
Modified Files:
documentation-guide.xml writing-guidelines.xml
Log Message:
Remove RH from this particular equation
Index: documentation-guide.xml
===================================================================
RCS file: /cvs/docs/documentation-guide/en_US/documentation-guide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- documentation-guide.xml 3 Feb 2007 22:21:58 -0000 1.5
+++ documentation-guide.xml 18 Feb 2007 14:24:33 -0000 1.6
@@ -30,7 +30,8 @@
xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- GUIDELINES -->
- <xi:include href="rh-guidelines.xml" xpointer="element(ch-rh-guidelines)"
+ <xi:include href="writing-guidelines.xml"
+ xpointer="element(ch-writing-guidelines)"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- EMACS -->
Index: writing-guidelines.xml
===================================================================
RCS file: /cvs/docs/documentation-guide/en_US/writing-guidelines.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- writing-guidelines.xml 5 Feb 2007 00:33:47 -0000 1.4
+++ writing-guidelines.xml 18 Feb 2007 14:24:33 -0000 1.5
@@ -7,7 +7,7 @@
]>
-<chapter id="ch-rh-guidelines">
+<chapter id="ch-writing-guidelines">
<title>&FED; Documentation Guidelines</title>
<indexterm>
17 years, 2 months