-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Yesterday on the train, I converted part of the "Using GPG" portion of the Security Guide. I get an error when I try to "make" the book now.
The error is:
junk after document element at line 11, column 0, byte 739: </para> </section> <section id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> ^ <title>Creating GPG Keys in GNOME</title> <para> at /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/XML/Parser.pm line 187 make: *** [xml-en-US] Error 4
I've compared the file to other files that I have and I can't see any differences. Does anyone have any ideas?
Thanks, Eric Christensen E-Mail: sparks@fedoraproject.org GPG Key: BD0C14C1
On Thu, Jan 01, 2009 at 10:24:28AM -0500, Eric Christensen wrote:
<section id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> ^
There could be an invisible (to the eye) character. You might also try forcing it to be one line, although that shouldn't be a problem. But it might be interpreting an invisible character in there, and making it all one line and re-inserting spaces.
- Karsten
On Thu, 2009-01-01 at 10:24 -0500, Eric Christensen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Yesterday on the train, I converted part of the "Using GPG" portion of the Security Guide. I get an error when I try to "make" the book now.
The error is:
junk after document element at line 11, column 0, byte 739:
</para> </section> <section id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> ^ <title>Creating GPG Keys in GNOME</title> <para> at /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/XML/Parser.pm line 187 make: *** [xml-en-US] Error 4
I've compared the file to other files that I have and I can't see any differences. Does anyone have any ideas?
Thanks, Eric Christensen E-Mail: sparks@fedoraproject.org GPG Key: BD0C14C1
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAklc4CkACgkQfQTSQL0MFME9DACgi4e0+tilap7jwCBAF60Oq2Sv qcQAoNFpKTfM+P2BuCnpXvJMXjwGSh2p =Ip0i -----END PGP SIGNATURE-----
Sorry it took a while to reply. Attached is my patch, it shouts about the <pre> tag being possibly broken but completes and builds clean on my box.
-Jason
Hi Jason and Eric,
On Thu, Jan 01, 2009 at 04:09:11PM -0500, Jason Taylor wrote:
On Thu, 2009-01-01 at 10:24 -0500, Eric Christensen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Yesterday on the train, I converted part of the "Using GPG" portion of the Security Guide. I get an error when I try to "make" the book now.
The error is:
junk after document element at line 11, column 0, byte 739:
</para> </section> <section id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> ^ <title>Creating GPG Keys in GNOME</title> <para> at /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/XML/Parser.pm line 187 make: *** [xml-en-US] Error 4
I've compared the file to other files that I have and I can't see any differences. Does anyone have any ideas?
Could this be a size limit to the @id attribute? I don't think these values are supposed to exceed 64 characters, and even that seems extraordinarily long so I'd recommend shortening this to see what happens.
Sorry it took a while to reply. Attached is my patch, it shouts about the <pre> tag being possibly broken but completes and builds clean on my box.
-Jason
Some comments below...
Index: en-US/Using_GPG.wiki
--- en-US/Using_GPG.wiki (revision 18) +++ en-US/Using_GPG.wiki (working copy) @@ -2,14 +2,17 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]>
+<chapter id="Encryption_Using_GPG"> +<title>Encryption Using GPG</title>
<section id="sect-Security_Guide-Encryption-Using_GPG"> <title>Using GNU Privacy Guard (GnuPG)</title> <para> GPG is used to identify yourself and authenticate your communications, including those with people you don't know. GPG allows anyone reading a GPG-signed email to verify its authenticity. In other words, GPG allows someone to be reasonably certain that communications signed by you actually are from you. GPG is useful because it helps prevent third parties from altering code or intercepting conversations and altering the message. </para> </section> -<section id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> - <title>Creating GPG Keys in GNOME</title> +<section id="sect-Security_Guide-Encryption-Using_GPG-Creating_Keys_in_GNOME"> + <title>Creating GPG Keys in GNOME</title>
I note this brings the character count for the @id attribute below 64... hm.
<para> Install the Seahorse utility, which makes GPG key management easier. From the main menu, select <code>System > Administration > Add/Remove Software</code> and wait for PackageKit to start. Enter <code>Seahorse</code> into the text box and select the Find. Select the checkbox next to the ''seahorse'' package and select ''Apply'' to add the software. You can also install '''Seahorse''' at the command line with the command <code>su -c "yum install seahorse"</code>. </para> @@ -105,17 +108,16 @@ <para> Finally, <code>gpg</code> generates random data to make your key as unique as possible. Move your mouse, type random keys, or perform other tasks on the system during this step to speed up the process. Once this step is finished, your keys are complete and ready to use: <pre> -pub 1024D/1B2AFA1C 2005-03-31 John Q. Doe (Fedora Docs Project) <jqdoe@example.com> +pub 1024D/1B2AFA1C 2005-03-31 John Q. Doe (Fedora Docs Project) jqdoe@example.com
You shouldn't eliminate the < and > characters as such, because that's what the user will see. In a parsed area like this you must represent them with < and > to avoid them being interpreted as delimiters for an element tag.
I'd also recommend substituting something more appropriate than <pre> here, like this:
<screen><computeroutput>content line 1 content line 2 content line 3</computeroutput></screen>
On Fri, Jan 2, 2009 at 11:17 AM, Murray McAllister murray.mcallister@gmail.com wrote:
<screen><computeroutput>content line 1 content line 2 content line 3</computeroutput></screen>
Be careful when using multiple lines. If you use <computeroutput> inside screen, you may find
1 2 3
is displayed as "1 2 3" in HTML.
Cheers.
Actually, I believe this only happens if you use <screen><command></command></screen>
Last reply, I promise ;)
If you build with Publican, the "1.2. Pull-quote Conventions" section displays how output looks. As far as I know the examples use <screen></screen>, so examples in your books will differ.
Is there any need to fill <screen> tags up with more tags?
B1;1704;0cOn Fri, Jan 02, 2009 at 11:17:53AM +1000, Murray McAllister wrote:
<screen><computeroutput>content line 1 content line 2 content line 3</computeroutput></screen>
Be careful when using multiple lines. If you use <computeroutput> inside screen, you may find
1 2 3
is displayed as "1 2 3" in HTML.
Is that also true when using CDATA sections? I usually do:
<screen><![CDATA[blah foo bar]]></screen>
On Fri, Jan 2, 2009 at 11:28 AM, Paul W. Frields stickster@gmail.com wrote:
B1;1704;0cOn Fri, Jan 02, 2009 at 11:17:53AM +1000, Murray McAllister wrote:
<screen><computeroutput>content line 1 content line 2 content line 3</computeroutput></screen>
Be careful when using multiple lines. If you use <computeroutput> inside screen, you may find
1 2 3
is displayed as "1 2 3" in HTML.
Is that also true when using CDATA sections? I usually do:
<screen><![CDATA[blah foo bar]]></screen>
CDATA is fine. Just don't let jfearn see you using it ;-)
If you want to include XML examples, I would place the example as a text file in in en_US/extras/, then:
<screen> <xi:include href="extras/blah.xmlt" parse="text"> </screen>
I think you need to use an extension other than ".xml", otherwise it is parsed?
<xi:include href="extras/blah.xmlt" parse="text">
That should be:
<xi:include href="extras/runconf_javaops.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude%22%3E</xi:include>
On Thu, Jan 1, 2009 at 9:21 PM, Murray McAllister murray.mcallister@gmail.com wrote:
<xi:include href="extras/blah.xmlt" parse="text">
That should be:
<xi:include href="extras/runconf_javaops.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude%22%3E</xi:include>
-- fedora-docs-list mailing list fedora-docs-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
Thanks for the pointers!
-Jason
On Fri, Jan 02, 2009 at 08:08:31AM -0500, Jason Taylor wrote:
On Thu, Jan 1, 2009 at 9:21 PM, Murray McAllister murray.mcallister@gmail.com wrote:
<xi:include href="extras/blah.xmlt" parse="text">
That should be:
<xi:include href="extras/runconf_javaops.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude%22%3E</xi:include>
Thanks for the pointers!
Ooo, me likey!
docs@lists.stg.fedoraproject.org