From fred.itfm at gmail.com Fri Aug 15 19:53:52 2014 From: fred.itfm at gmail.com (Frederic Monestel) Date: Fri, 15 Aug 2014 21:53:52 +0200 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically Message-ID: Dear All, I have been working hard on some documentation and I have written a lot of xml chapter files in a *Publican Docbook structure* but I did not keep *Chapters id *nor *Sections id o**rganized*... Could someone* recommend some tools or scripts *to automatically get things sorted? Many thanks for your help and keep up the good work! Freddie -------------- next part -------------- An HTML attachment was scrubbed... URL: From daobrien at redhat.com Sun Aug 17 03:39:06 2014 From: daobrien at redhat.com (David O'Brien) Date: Sun, 17 Aug 2014 13:39:06 +1000 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: References: Message-ID: <53F023DA.7090004@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/16/2014 05:53 AM, Frederic Monestel wrote: > Dear All, > > I have been working hard on some documentation and I have written > a lot of xml chapter files in a *Publican Docbook structure* but I > did not keep *Chapters id *nor *Sections id o**rganized*... Could > someone* recommend some tools or scripts *to automatically get > things sorted? > > Many thanks for your help and keep up the good work! > > Freddie > > > > _______________________________________________ publican-list > mailing list publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list Wiki: > https://fedorahosted.org/publican > Freddie, Can you elaborate on what you mean by "organised"? Example? - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJT8CPZAAoJEDpAHQqWGp+3T5EH/R1vXSF+x4J60HvtS/B0aB4p jsVPgQixTvYZUYz4XOGHgQqRLnO1ydv63QiKh00H9G5CUGit3VArOj5fyexJ+Elw rG/2PiToUPwlqKw3xjzxn0ELdZjgCjvEPoDbN4dr/9mTZcqYYMXzi/0SXP9tL3sL x8ZvmEGQOp0EhpCJEPlxADIF7FmL+I94wx8drSAYy405iOxRB0IELIV3zqJyeycE /T/EID2wdFSPKa3Kp/flH7V5N8NieovlN4fcRg/LJFkPRMwI+3E2pDR8PTIIR6mT 4P1z9gkzCKvRhwKsFai6GhmcdQ2JLNMctmB5CHHN8MKGExGoOvn7D9jJotqiR1k= =R4tV -----END PGP SIGNATURE----- From fred.itfm at gmail.com Sun Aug 17 10:50:07 2014 From: fred.itfm at gmail.com (Frederic Monestel) Date: Sun, 17 Aug 2014 12:50:07 +0200 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: <53F023DA.7090004@redhat.com> References: <53F023DA.7090004@redhat.com> Message-ID: i mean that the book can be built and does not generate errors while you do publican build. i believe i have to modify all ids and relate them to the file names, chapters and sections names. is there any best practices to what names one should give to ids? is there a way (a script) that would modify all id names in each chapter files so your book will be built? my problem is that i have not modified any id names and they are all the them in my 60+ different chapter files, therefore i cannot build my book. i hope this make more sense? please let me know if i need to give more details. many thanks for your help and kind regards, freddie On Sunday, August 17, 2014, David O'Brien wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/16/2014 05:53 AM, Frederic Monestel wrote: > > Dear All, > > > > I have been working hard on some documentation and I have written > > a lot of xml chapter files in a *Publican Docbook structure* but I > > did not keep *Chapters id *nor *Sections id o**rganized*... Could > > someone* recommend some tools or scripts *to automatically get > > things sorted? > > > > Many thanks for your help and keep up the good work! > > > > Freddie > > > > > > > > _______________________________________________ publican-list > > mailing list publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list Wiki: > > https://fedorahosted.org/publican > > > Freddie, > > Can you elaborate on what you mean by "organised"? Example? > > - -- > > David > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iQEcBAEBAgAGBQJT8CPZAAoJEDpAHQqWGp+3T5EH/R1vXSF+x4J60HvtS/B0aB4p > jsVPgQixTvYZUYz4XOGHgQqRLnO1ydv63QiKh00H9G5CUGit3VArOj5fyexJ+Elw > rG/2PiToUPwlqKw3xjzxn0ELdZjgCjvEPoDbN4dr/9mTZcqYYMXzi/0SXP9tL3sL > x8ZvmEGQOp0EhpCJEPlxADIF7FmL+I94wx8drSAYy405iOxRB0IELIV3zqJyeycE > /T/EID2wdFSPKa3Kp/flH7V5N8NieovlN4fcRg/LJFkPRMwI+3E2pDR8PTIIR6mT > 4P1z9gkzCKvRhwKsFai6GhmcdQ2JLNMctmB5CHHN8MKGExGoOvn7D9jJotqiR1k= > =R4tV > -----END PGP SIGNATURE----- > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfearn at redhat.com Sun Aug 17 22:32:45 2014 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 18 Aug 2014 08:32:45 +1000 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: References: <53F023DA.7090004@redhat.com> Message-ID: <53F12D8D.2050108@redhat.com> On 08/17/2014 08:50 PM, Frederic Monestel wrote: > i mean that the book can be built and does not generate errors while you do publican build. i believe i have to modify all ids and relate them to the file names, chapters and sections names. You do not have to set IDs. If an ID is not set then a random ID is created during the build process. If you are having build issues it is unlikely to be related to the lack of ID. If you include the errors we could help debug your issue. Cheers, Jeff. -- Jeff Fearn Senior Software Engineer GSS Subscriber Platform Red Hat Pty Ltd From fred.itfm at gmail.com Mon Aug 18 13:09:26 2014 From: fred.itfm at gmail.com (Frederic Monestel) Date: Mon, 18 Aug 2014 15:09:26 +0200 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: <53F12D8D.2050108@redhat.com> References: <53F023DA.7090004@redhat.com> <53F12D8D.2050108@redhat.com> Message-ID: Thanks very much for this precision Jeff, Here you go this is the errors, I have: Many thanks for your help and kind regards, Fred Beginning work on en-US DTD Validation failed for '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': Chap_airport.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_airport.xml:16: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Debian.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Debian.xml:111: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_Fedora.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_compil_stellarium.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_compil_stellarium.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_compil_stellarium.xml:21: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_compil_stellarium.xml:32: validity error : Element listitem content does not follow the DTD, expecting (calloutlist | glosslist | bibliolist | itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | caution | important | note | tip | warning | literallayout | programlisting | programlistingco | screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | para | simpara | address | blockquote | graphic | graphicco | mediaobject | mediaobjectco | informalequation | informalexample | informalfigure | informaltable | equation | example | figure | table | msgset | procedure | sidebar | qandaset | task | anchor | bridgehead | remark | highlights | abstract | authorblurb | epigraph | indexterm | beginpage)+, got () Chap_lenovo_Q180.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_lenovo_Q180.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_lenovo_Q180.xml:21: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_audio_vids_conversion.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_audio_vids_conversion.xml:76: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_audio_vids_conversion.xml:138: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_publican_docbook_serna.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_publican_docbook_serna.xml:25: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_publican_docbook_serna.xml:76: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_sh_backup.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_sh_backup.xml:25: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_bash.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Clean_install.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_Clean_install.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Clean_install.xml:230: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined On Mon, Aug 18, 2014 at 12:32 AM, Jeff Fearn wrote: > On 08/17/2014 08:50 PM, Frederic Monestel wrote: > > i mean that the book can be built and does not generate errors while you > do publican build. i believe i have to modify all ids and relate them to > the file names, chapters and sections names. > > You do not have to set IDs. If an ID is not set then a random ID is > created during the build process. > > If you are having build issues it is unlikely to be related to the lack of > ID. > > If you include the errors we could help debug your issue. > > Cheers, Jeff. > > -- > Jeff Fearn > Senior Software Engineer > GSS Subscriber Platform > Red Hat Pty Ltd > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred.itfm at gmail.com Mon Aug 18 13:10:43 2014 From: fred.itfm at gmail.com (Frederic Monestel) Date: Mon, 18 Aug 2014 15:10:43 +0200 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: References: <53F023DA.7090004@redhat.com> <53F12D8D.2050108@redhat.com> Message-ID: Thanks very much for this precision Jeff, Here you go this is the errors I have, after: publican build --formats=html --langs=en-US Many thanks for your help and kind regards, Fred Beginning work on en-US DTD Validation failed for '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': Chap_airport.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_airport.xml:16: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Debian.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Debian.xml:111: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_Fedora.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_compil_stellarium.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_compil_stellarium.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_compil_stellarium.xml:21: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_compil_stellarium.xml:32: validity error : Element listitem content does not follow the DTD, expecting (calloutlist | glosslist | bibliolist | itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | caution | important | note | tip | warning | literallayout | programlisting | programlistingco | screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | para | simpara | address | blockquote | graphic | graphicco | mediaobject | mediaobjectco | informalequation | informalexample | informalfigure | informaltable | equation | example | figure | table | msgset | procedure | sidebar | qandaset | task | anchor | bridgehead | remark | highlights | abstract | authorblurb | epigraph | indexterm | beginpage)+, got () Chap_lenovo_Q180.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_lenovo_Q180.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_lenovo_Q180.xml:21: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_audio_vids_conversion.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_audio_vids_conversion.xml:76: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_audio_vids_conversion.xml:138: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_publican_docbook_serna.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_publican_docbook_serna.xml:25: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_publican_docbook_serna.xml:76: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined Chap_sh_backup.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_sh_backup.xml:25: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_bash.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Clean_install.xml:8: validity error : ID chap-linux_book-Test_Chapter already defined Chap_Clean_install.xml:13: validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 already defined Chap_Clean_install.xml:230: validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 already defined On Mon, Aug 18, 2014 at 3:09 PM, Frederic Monestel wrote: > Thanks very much for this precision Jeff, > > Here you go this is the errors, I have: > > Many thanks for your help and kind regards, > > Fred > > Beginning work on en-US > DTD Validation failed for > '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': > Chap_airport.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined > Chap_airport.xml:16: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_Debian.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined > Chap_Debian.xml:19: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_Debian.xml:111: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_Fedora.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined > Chap_Fedora.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_compil_stellarium.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_compil_stellarium.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_compil_stellarium.xml:21: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_compil_stellarium.xml:32: validity error : Element listitem content > does not follow the DTD, expecting (calloutlist | glosslist | bibliolist | > itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | > caution | important | note | tip | warning | literallayout | programlisting > | programlistingco | screen | screenco | screenshot | synopsis | > cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | > constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | > para | simpara | address | blockquote | graphic | graphicco | mediaobject | > mediaobjectco | informalequation | informalexample | informalfigure | > informaltable | equation | example | figure | table | msgset | procedure | > sidebar | qandaset | task | anchor | bridgehead | remark | highlights | > abstract | authorblurb | epigraph | indexterm | beginpage)+, got () > Chap_lenovo_Q180.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined > Chap_lenovo_Q180.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_lenovo_Q180.xml:21: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_audio_vids_conversion.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_audio_vids_conversion.xml:76: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_audio_vids_conversion.xml:138: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_publican_docbook_serna.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_publican_docbook_serna.xml:25: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_publican_docbook_serna.xml:76: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_sh_backup.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined > Chap_sh_backup.xml:25: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter already > defined > Chap_bash.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_Clean_install.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined > Chap_Clean_install.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_Clean_install.xml:230: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > > > On Mon, Aug 18, 2014 at 12:32 AM, Jeff Fearn wrote: > >> On 08/17/2014 08:50 PM, Frederic Monestel wrote: >> > i mean that the book can be built and does not generate errors while >> you do publican build. i believe i have to modify all ids and relate them >> to the file names, chapters and sections names. >> >> You do not have to set IDs. If an ID is not set then a random ID is >> created during the build process. >> >> If you are having build issues it is unlikely to be related to the lack >> of ID. >> >> If you include the errors we could help debug your issue. >> >> Cheers, Jeff. >> >> -- >> Jeff Fearn >> Senior Software Engineer >> GSS Subscriber Platform >> Red Hat Pty Ltd >> >> _______________________________________________ >> publican-list mailing list >> publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list >> Wiki: https://fedorahosted.org/publican >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daobrien at redhat.com Mon Aug 18 14:27:36 2014 From: daobrien at redhat.com (David O'Brien) Date: Tue, 19 Aug 2014 00:27:36 +1000 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: References: <53F023DA.7090004@redhat.com> <53F12D8D.2050108@redhat.com> Message-ID: <53F20D58.5010102@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fred, A couple of different error types there: 1. ID chap-linux_book-Test_Chapter already defined Errors like that mean you have more than one ID of the same value in the same book. IDs need to be unique. 2. Element listitem content does not follow the DTD Errors like that mean you haven't provided valid content for the xml tags that you've used. The most telling part of the message is often at the end, in this case "got ()" which means you used a tag but didn't put anything in it. To fix 1. you need to track down all your IDs and make sure they're unique. For my own part, I use "publican clean_ids" but that's quite invasive and not for everybody. It does, however, ensure all your IDs are unique (at least, it hasn't failed me). Read the doc before you use it, and maybe test on a backup copy. To fix 2. you need to make sure you use valid content in all your elements. Some editors can help with that if they do DTD validation for you. Hope this helps David On 08/18/2014 11:10 PM, Frederic Monestel wrote: > Thanks very much for this precision Jeff, > > Here you go this is the errors I have, after: publican build > --formats=html --langs=en-US > > Many thanks for your help and kind regards, > > Fred > > Beginning work on en-US DTD Validation failed for > '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': > Chap_airport.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined Chap_airport.xml:16: > validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > already defined Chap_Debian.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: > validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > already defined Chap_Debian.xml:111: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_Fedora.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: > validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 > already defined Chap_compil_stellarium.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_compil_stellarium.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_compil_stellarium.xml:21: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_compil_stellarium.xml:32: validity error : Element listitem > content does not follow the DTD, expecting (calloutlist | glosslist > | bibliolist | itemizedlist | orderedlist | segmentedlist | > simplelist | variablelist | caution | important | note | tip | > warning | literallayout | programlisting | programlistingco | > screen | screenco | screenshot | synopsis | cmdsynopsis | > funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis > | destructorsynopsis | methodsynopsis | formalpara | para | simpara > | address | blockquote | graphic | graphicco | mediaobject | > mediaobjectco | informalequation | informalexample | informalfigure > | informaltable | equation | example | figure | table | msgset | > procedure | sidebar | qandaset | task | anchor | bridgehead | > remark | highlights | abstract | authorblurb | epigraph | indexterm > | beginpage)+, got () Chap_lenovo_Q180.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_lenovo_Q180.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_lenovo_Q180.xml:21: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_audio_vids_conversion.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_audio_vids_conversion.xml:76: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_audio_vids_conversion.xml:138: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_publican_docbook_serna.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_publican_docbook_serna.xml:25: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_publican_docbook_serna.xml:76: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > Chap_sh_backup.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_sh_backup.xml:25: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter > already defined Chap_bash.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_Clean_install.xml:8: validity error : ID > chap-linux_book-Test_Chapter already defined > Chap_Clean_install.xml:13: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_1 already defined > Chap_Clean_install.xml:230: validity error : ID > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > > On Mon, Aug 18, 2014 at 3:09 PM, Frederic Monestel > wrote: > >> Thanks very much for this precision Jeff, >> >> Here you go this is the errors, I have: >> >> Many thanks for your help and kind regards, >> >> Fred >> >> Beginning work on en-US DTD Validation failed for >> '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': >> Chap_airport.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_airport.xml:16: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_Debian.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: >> validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 >> already defined Chap_Debian.xml:111: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_2 already defined >> Chap_Fedora.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: >> validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 >> already defined Chap_compil_stellarium.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_compil_stellarium.xml:13: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_compil_stellarium.xml:21: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_2 already defined >> Chap_compil_stellarium.xml:32: validity error : Element listitem >> content does not follow the DTD, expecting (calloutlist | >> glosslist | bibliolist | itemizedlist | orderedlist | >> segmentedlist | simplelist | variablelist | caution | important | >> note | tip | warning | literallayout | programlisting | >> programlistingco | screen | screenco | screenshot | synopsis | >> cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | >> constructorsynopsis | destructorsynopsis | methodsynopsis | >> formalpara | para | simpara | address | blockquote | graphic | >> graphicco | mediaobject | mediaobjectco | informalequation | >> informalexample | informalfigure | informaltable | equation | >> example | figure | table | msgset | procedure | sidebar | >> qandaset | task | anchor | bridgehead | remark | highlights | >> abstract | authorblurb | epigraph | indexterm | beginpage)+, got >> () Chap_lenovo_Q180.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_lenovo_Q180.xml:13: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_lenovo_Q180.xml:21: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_2 already defined >> Chap_audio_vids_conversion.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_audio_vids_conversion.xml:76: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_audio_vids_conversion.xml:138: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_2 already defined >> Chap_publican_docbook_serna.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_publican_docbook_serna.xml:25: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_publican_docbook_serna.xml:76: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_2 already defined >> Chap_sh_backup.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_sh_backup.xml:25: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter >> already defined Chap_bash.xml:13: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_Clean_install.xml:8: validity error : ID >> chap-linux_book-Test_Chapter already defined >> Chap_Clean_install.xml:13: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_1 already defined >> Chap_Clean_install.xml:230: validity error : ID >> sect-linux_book-Test_Chapter-Test_Section_2 already defined >> >> >> >> On Mon, Aug 18, 2014 at 12:32 AM, Jeff Fearn >> wrote: >> >>> On 08/17/2014 08:50 PM, Frederic Monestel wrote: >>>> i mean that the book can be built and does not generate >>>> errors while >>> you do publican build. i believe i have to modify all ids and >>> relate them to the file names, chapters and sections names. >>> >>> You do not have to set IDs. If an ID is not set then a random >>> ID is created during the build process. >>> >>> If you are having build issues it is unlikely to be related to >>> the lack of ID. >>> >>> If you include the errors we could help debug your issue. >>> >>> Cheers, Jeff. >>> >>> -- Jeff Fearn Senior Software Engineer GSS Subscriber Platform >>> Red Hat Pty Ltd >>> >>> _______________________________________________ publican-list >>> mailing list publican-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/publican-list Wiki: >>> https://fedorahosted.org/publican >>> >> >> > > > > _______________________________________________ publican-list > mailing list publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list Wiki: > https://fedorahosted.org/publican > - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJT8g1YAAoJEDpAHQqWGp+3yzYH/3LGQ7tLEr3alqpbOiGI00Le rkfcVfXtgXBCiVbUn5Qr5FqtiVUpe7oIWluCOzrvcYoccSbYdGzKTAC7mfVV0vfv 2MknWRqi5D6DYiEJElrYEycEXqZNiim5V4CrZ2vROvCFkg8Io+Z7WxX298qFTSKX 4oBbNqnkMNZUbyprjFcLcChae9bar4ARaA74dHYCLcBL0yWLhKrbqmBzv2J4JQAb vIona2PYnzhiSo+Drm9DyFUSYUK7cnLMlCpEh3FZ5DedpJKMBvlv3KBNzw+OWFen LnOsVHX82nzVqZILUV/vn9pboNt9t0D9CXpZOFEeVVX8bBkEzUTuK5/8V6Llx+A= =hPPw -----END PGP SIGNATURE----- From fred.itfm at gmail.com Mon Aug 18 15:26:57 2014 From: fred.itfm at gmail.com (Frederic Monestel) Date: Mon, 18 Aug 2014 17:26:57 +0200 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: <53F20D58.5010102@redhat.com> References: <53F023DA.7090004@redhat.com> <53F12D8D.2050108@redhat.com> <53F20D58.5010102@redhat.com> Message-ID: Hi David, Thank you so much, yes indeed this is of great help! Thanks again. Regards, Fred On Mon, Aug 18, 2014 at 4:27 PM, David O'Brien wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Fred, > > A couple of different error types there: > > 1. ID chap-linux_book-Test_Chapter already defined > > Errors like that mean you have more than one ID of the same value in > the same book. IDs need to be unique. > > 2. Element listitem content does not follow the DTD > > Errors like that mean you haven't provided valid content for the xml > tags that you've used. The most telling part of the message is often > at the end, in this case "got ()" which means you used a > tag but didn't put anything in it. > > To fix 1. you need to track down all your IDs and make sure they're > unique. For my own part, I use "publican clean_ids" but that's quite > invasive and not for everybody. It does, however, ensure all your IDs > are unique (at least, it hasn't failed me). Read the doc before you > use it, and maybe test on a backup copy. > > To fix 2. you need to make sure you use valid content in all your > elements. Some editors can help with that if they do DTD validation > for you. > > Hope this helps > David > > On 08/18/2014 11:10 PM, Frederic Monestel wrote: > > Thanks very much for this precision Jeff, > > > > Here you go this is the errors I have, after: publican build > > --formats=html --langs=en-US > > > > Many thanks for your help and kind regards, > > > > Fred > > > > Beginning work on en-US DTD Validation failed for > > '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': > > Chap_airport.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined Chap_airport.xml:16: > > validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > > already defined Chap_Debian.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: > > validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > > already defined Chap_Debian.xml:111: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_Fedora.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: > > validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 > > already defined Chap_compil_stellarium.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_compil_stellarium.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_compil_stellarium.xml:21: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_compil_stellarium.xml:32: validity error : Element listitem > > content does not follow the DTD, expecting (calloutlist | glosslist > > | bibliolist | itemizedlist | orderedlist | segmentedlist | > > simplelist | variablelist | caution | important | note | tip | > > warning | literallayout | programlisting | programlistingco | > > screen | screenco | screenshot | synopsis | cmdsynopsis | > > funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis > > | destructorsynopsis | methodsynopsis | formalpara | para | simpara > > | address | blockquote | graphic | graphicco | mediaobject | > > mediaobjectco | informalequation | informalexample | informalfigure > > | informaltable | equation | example | figure | table | msgset | > > procedure | sidebar | qandaset | task | anchor | bridgehead | > > remark | highlights | abstract | authorblurb | epigraph | indexterm > > | beginpage)+, got () Chap_lenovo_Q180.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_lenovo_Q180.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_lenovo_Q180.xml:21: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_audio_vids_conversion.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_audio_vids_conversion.xml:76: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_audio_vids_conversion.xml:138: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_publican_docbook_serna.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_publican_docbook_serna.xml:25: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_publican_docbook_serna.xml:76: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_sh_backup.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_sh_backup.xml:25: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter > > already defined Chap_bash.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_Clean_install.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_Clean_install.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_Clean_install.xml:230: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > > > > > On Mon, Aug 18, 2014 at 3:09 PM, Frederic Monestel > > wrote: > > > >> Thanks very much for this precision Jeff, > >> > >> Here you go this is the errors, I have: > >> > >> Many thanks for your help and kind regards, > >> > >> Fred > >> > >> Beginning work on en-US DTD Validation failed for > >> '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': > >> Chap_airport.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_airport.xml:16: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_Debian.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: > >> validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > >> already defined Chap_Debian.xml:111: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_Fedora.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: > >> validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 > >> already defined Chap_compil_stellarium.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_compil_stellarium.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_compil_stellarium.xml:21: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_compil_stellarium.xml:32: validity error : Element listitem > >> content does not follow the DTD, expecting (calloutlist | > >> glosslist | bibliolist | itemizedlist | orderedlist | > >> segmentedlist | simplelist | variablelist | caution | important | > >> note | tip | warning | literallayout | programlisting | > >> programlistingco | screen | screenco | screenshot | synopsis | > >> cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | > >> constructorsynopsis | destructorsynopsis | methodsynopsis | > >> formalpara | para | simpara | address | blockquote | graphic | > >> graphicco | mediaobject | mediaobjectco | informalequation | > >> informalexample | informalfigure | informaltable | equation | > >> example | figure | table | msgset | procedure | sidebar | > >> qandaset | task | anchor | bridgehead | remark | highlights | > >> abstract | authorblurb | epigraph | indexterm | beginpage)+, got > >> () Chap_lenovo_Q180.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_lenovo_Q180.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_lenovo_Q180.xml:21: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_audio_vids_conversion.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_audio_vids_conversion.xml:76: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_audio_vids_conversion.xml:138: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_publican_docbook_serna.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_publican_docbook_serna.xml:25: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_publican_docbook_serna.xml:76: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_sh_backup.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_sh_backup.xml:25: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter > >> already defined Chap_bash.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_Clean_install.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_Clean_install.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_Clean_install.xml:230: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> > >> > >> > >> On Mon, Aug 18, 2014 at 12:32 AM, Jeff Fearn > >> wrote: > >> > >>> On 08/17/2014 08:50 PM, Frederic Monestel wrote: > >>>> i mean that the book can be built and does not generate > >>>> errors while > >>> you do publican build. i believe i have to modify all ids and > >>> relate them to the file names, chapters and sections names. > >>> > >>> You do not have to set IDs. If an ID is not set then a random > >>> ID is created during the build process. > >>> > >>> If you are having build issues it is unlikely to be related to > >>> the lack of ID. > >>> > >>> If you include the errors we could help debug your issue. > >>> > >>> Cheers, Jeff. > >>> > >>> -- Jeff Fearn Senior Software Engineer GSS Subscriber Platform > >>> Red Hat Pty Ltd > >>> > >>> _______________________________________________ publican-list > >>> mailing list publican-list at redhat.com > >>> https://www.redhat.com/mailman/listinfo/publican-list Wiki: > >>> https://fedorahosted.org/publican > >>> > >> > >> > > > > > > > > _______________________________________________ publican-list > > mailing list publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list Wiki: > > https://fedorahosted.org/publican > > > > > - -- > > David > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iQEcBAEBAgAGBQJT8g1YAAoJEDpAHQqWGp+3yzYH/3LGQ7tLEr3alqpbOiGI00Le > rkfcVfXtgXBCiVbUn5Qr5FqtiVUpe7oIWluCOzrvcYoccSbYdGzKTAC7mfVV0vfv > 2MknWRqi5D6DYiEJElrYEycEXqZNiim5V4CrZ2vROvCFkg8Io+Z7WxX298qFTSKX > 4oBbNqnkMNZUbyprjFcLcChae9bar4ARaA74dHYCLcBL0yWLhKrbqmBzv2J4JQAb > vIona2PYnzhiSo+Drm9DyFUSYUK7cnLMlCpEh3FZ5DedpJKMBvlv3KBNzw+OWFen > LnOsVHX82nzVqZILUV/vn9pboNt9t0D9CXpZOFEeVVX8bBkEzUTuK5/8V6Llx+A= > =hPPw > -----END PGP SIGNATURE----- > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred.itfm at gmail.com Mon Aug 18 15:30:02 2014 From: fred.itfm at gmail.com (Frederic Monestel) Date: Mon, 18 Aug 2014 17:30:02 +0200 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: <53F20D58.5010102@redhat.com> References: <53F023DA.7090004@redhat.com> <53F12D8D.2050108@redhat.com> <53F20D58.5010102@redhat.com> Message-ID: One more question, please, What editors do DTD validation? And what editor would you recommend to write Publican Docbook materials? Many thanks for your help and keep up the good work! Fred On Mon, Aug 18, 2014 at 4:27 PM, David O'Brien wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Fred, > > A couple of different error types there: > > 1. ID chap-linux_book-Test_Chapter already defined > > Errors like that mean you have more than one ID of the same value in > the same book. IDs need to be unique. > > 2. Element listitem content does not follow the DTD > > Errors like that mean you haven't provided valid content for the xml > tags that you've used. The most telling part of the message is often > at the end, in this case "got ()" which means you used a > tag but didn't put anything in it. > > To fix 1. you need to track down all your IDs and make sure they're > unique. For my own part, I use "publican clean_ids" but that's quite > invasive and not for everybody. It does, however, ensure all your IDs > are unique (at least, it hasn't failed me). Read the doc before you > use it, and maybe test on a backup copy. > > To fix 2. you need to make sure you use valid content in all your > elements. Some editors can help with that if they do DTD validation > for you. > > Hope this helps > David > > On 08/18/2014 11:10 PM, Frederic Monestel wrote: > > Thanks very much for this precision Jeff, > > > > Here you go this is the errors I have, after: publican build > > --formats=html --langs=en-US > > > > Many thanks for your help and kind regards, > > > > Fred > > > > Beginning work on en-US DTD Validation failed for > > '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': > > Chap_airport.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined Chap_airport.xml:16: > > validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > > already defined Chap_Debian.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: > > validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > > already defined Chap_Debian.xml:111: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_Fedora.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: > > validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 > > already defined Chap_compil_stellarium.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_compil_stellarium.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_compil_stellarium.xml:21: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_compil_stellarium.xml:32: validity error : Element listitem > > content does not follow the DTD, expecting (calloutlist | glosslist > > | bibliolist | itemizedlist | orderedlist | segmentedlist | > > simplelist | variablelist | caution | important | note | tip | > > warning | literallayout | programlisting | programlistingco | > > screen | screenco | screenshot | synopsis | cmdsynopsis | > > funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis > > | destructorsynopsis | methodsynopsis | formalpara | para | simpara > > | address | blockquote | graphic | graphicco | mediaobject | > > mediaobjectco | informalequation | informalexample | informalfigure > > | informaltable | equation | example | figure | table | msgset | > > procedure | sidebar | qandaset | task | anchor | bridgehead | > > remark | highlights | abstract | authorblurb | epigraph | indexterm > > | beginpage)+, got () Chap_lenovo_Q180.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_lenovo_Q180.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_lenovo_Q180.xml:21: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_audio_vids_conversion.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_audio_vids_conversion.xml:76: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_audio_vids_conversion.xml:138: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_publican_docbook_serna.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_publican_docbook_serna.xml:25: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_publican_docbook_serna.xml:76: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > Chap_sh_backup.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_sh_backup.xml:25: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter > > already defined Chap_bash.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_Clean_install.xml:8: validity error : ID > > chap-linux_book-Test_Chapter already defined > > Chap_Clean_install.xml:13: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_1 already defined > > Chap_Clean_install.xml:230: validity error : ID > > sect-linux_book-Test_Chapter-Test_Section_2 already defined > > > > > > On Mon, Aug 18, 2014 at 3:09 PM, Frederic Monestel > > wrote: > > > >> Thanks very much for this precision Jeff, > >> > >> Here you go this is the errors, I have: > >> > >> Many thanks for your help and kind regards, > >> > >> Fred > >> > >> Beginning work on en-US DTD Validation failed for > >> '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': > >> Chap_airport.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_airport.xml:16: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_Debian.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined Chap_Debian.xml:19: > >> validity error : ID sect-linux_book-Test_Chapter-Test_Section_1 > >> already defined Chap_Debian.xml:111: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_Fedora.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined Chap_Fedora.xml:13: > >> validity error : ID sect-linux_book-Test_Chapter-Test_Section_2 > >> already defined Chap_compil_stellarium.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_compil_stellarium.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_compil_stellarium.xml:21: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_compil_stellarium.xml:32: validity error : Element listitem > >> content does not follow the DTD, expecting (calloutlist | > >> glosslist | bibliolist | itemizedlist | orderedlist | > >> segmentedlist | simplelist | variablelist | caution | important | > >> note | tip | warning | literallayout | programlisting | > >> programlistingco | screen | screenco | screenshot | synopsis | > >> cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | > >> constructorsynopsis | destructorsynopsis | methodsynopsis | > >> formalpara | para | simpara | address | blockquote | graphic | > >> graphicco | mediaobject | mediaobjectco | informalequation | > >> informalexample | informalfigure | informaltable | equation | > >> example | figure | table | msgset | procedure | sidebar | > >> qandaset | task | anchor | bridgehead | remark | highlights | > >> abstract | authorblurb | epigraph | indexterm | beginpage)+, got > >> () Chap_lenovo_Q180.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_lenovo_Q180.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_lenovo_Q180.xml:21: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_audio_vids_conversion.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_audio_vids_conversion.xml:76: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_audio_vids_conversion.xml:138: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_publican_docbook_serna.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_publican_docbook_serna.xml:25: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_publican_docbook_serna.xml:76: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> Chap_sh_backup.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_sh_backup.xml:25: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_bash.xml:8: validity error : ID chap-linux_book-Test_Chapter > >> already defined Chap_bash.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_Clean_install.xml:8: validity error : ID > >> chap-linux_book-Test_Chapter already defined > >> Chap_Clean_install.xml:13: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_1 already defined > >> Chap_Clean_install.xml:230: validity error : ID > >> sect-linux_book-Test_Chapter-Test_Section_2 already defined > >> > >> > >> > >> On Mon, Aug 18, 2014 at 12:32 AM, Jeff Fearn > >> wrote: > >> > >>> On 08/17/2014 08:50 PM, Frederic Monestel wrote: > >>>> i mean that the book can be built and does not generate > >>>> errors while > >>> you do publican build. i believe i have to modify all ids and > >>> relate them to the file names, chapters and sections names. > >>> > >>> You do not have to set IDs. If an ID is not set then a random > >>> ID is created during the build process. > >>> > >>> If you are having build issues it is unlikely to be related to > >>> the lack of ID. > >>> > >>> If you include the errors we could help debug your issue. > >>> > >>> Cheers, Jeff. > >>> > >>> -- Jeff Fearn Senior Software Engineer GSS Subscriber Platform > >>> Red Hat Pty Ltd > >>> > >>> _______________________________________________ publican-list > >>> mailing list publican-list at redhat.com > >>> https://www.redhat.com/mailman/listinfo/publican-list Wiki: > >>> https://fedorahosted.org/publican > >>> > >> > >> > > > > > > > > _______________________________________________ publican-list > > mailing list publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list Wiki: > > https://fedorahosted.org/publican > > > > > - -- > > David > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iQEcBAEBAgAGBQJT8g1YAAoJEDpAHQqWGp+3yzYH/3LGQ7tLEr3alqpbOiGI00Le > rkfcVfXtgXBCiVbUn5Qr5FqtiVUpe7oIWluCOzrvcYoccSbYdGzKTAC7mfVV0vfv > 2MknWRqi5D6DYiEJElrYEycEXqZNiim5V4CrZ2vROvCFkg8Io+Z7WxX298qFTSKX > 4oBbNqnkMNZUbyprjFcLcChae9bar4ARaA74dHYCLcBL0yWLhKrbqmBzv2J4JQAb > vIona2PYnzhiSo+Drm9DyFUSYUK7cnLMlCpEh3FZ5DedpJKMBvlv3KBNzw+OWFen > LnOsVHX82nzVqZILUV/vn9pboNt9t0D9CXpZOFEeVVX8bBkEzUTuK5/8V6Llx+A= > =hPPw > -----END PGP SIGNATURE----- > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daobrien at redhat.com Mon Aug 18 22:33:57 2014 From: daobrien at redhat.com (David O'Brien) Date: Tue, 19 Aug 2014 08:33:57 +1000 Subject: [publican-list] Publican Tools to organise Chapters and sections names automatically In-Reply-To: References: <53F023DA.7090004@redhat.com> <53F12D8D.2050108@redhat.com> <53F20D58.5010102@redhat.com> Message-ID: <53F27F55.9000304@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/19/2014 01:30 AM, Frederic Monestel wrote: > One more question, please, > > What editors do DTD validation? And what editor would you > recommend to write Publican Docbook materials? That's close to being one of those "which distro is best?" questions :-) I use Kate on Fedora with xml plug-ins. I know vi and Emacs have similar capabilities. Some ppl I know use Oxygen. Best bet would be to google, try a few, and find something that you like and that works for you. Good luck~! David > > Many thanks for your help and keep up the good work! > > Fred > > > > On Mon, Aug 18, 2014 at 4:27 PM, David O'Brien > wrote: > > Fred, > > A couple of different error types there: > > 1. ID chap-linux_book-Test_Chapter already defined > > Errors like that mean you have more than one ID of the same value > in the same book. IDs need to be unique. > > 2. Element listitem content does not follow the DTD > > Errors like that mean you haven't provided valid content for the > xml tags that you've used. The most telling part of the message is > often at the end, in this case "got ()" which means you used a > tag but didn't put anything in it. > > To fix 1. you need to track down all your IDs and make sure they're > unique. For my own part, I use "publican clean_ids" but that's > quite invasive and not for everybody. It does, however, ensure all > your IDs are unique (at least, it hasn't failed me). Read the doc > before you use it, and maybe test on a backup copy. > > To fix 2. you need to make sure you use valid content in all your > elements. Some editors can help with that if they do DTD > validation for you. > > Hope this helps David > > On 08/18/2014 11:10 PM, Frederic Monestel wrote: >>>> Thanks very much for this precision Jeff, >>>> >>>> Here you go this is the errors I have, after: publican build >>>> --formats=html --langs=en-US >>>> >>>> Many thanks for your help and kind regards, >>>> >>>> Fred >>>> >>>> Beginning work on en-US DTD Validation failed for >>>> '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': >>>> >>>> >>>> Chap_airport.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_airport.xml:16: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_Debian.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_Debian.xml:19: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_Debian.xml:111: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> Chap_Fedora.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_Fedora.xml:13: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> Chap_compil_stellarium.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_compil_stellarium.xml:13: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_compil_stellarium.xml:21: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> Chap_compil_stellarium.xml:32: validity error : Element >>>> listitem content does not follow the DTD, expecting >>>> (calloutlist | glosslist | bibliolist | itemizedlist | >>>> orderedlist | segmentedlist | simplelist | variablelist | >>>> caution | important | note | tip | warning | literallayout | >>>> programlisting | programlistingco | screen | screenco | >>>> screenshot | synopsis | cmdsynopsis | funcsynopsis | >>>> classsynopsis | fieldsynopsis | constructorsynopsis | >>>> destructorsynopsis | methodsynopsis | formalpara | para | >>>> simpara | address | blockquote | graphic | graphicco | >>>> mediaobject | mediaobjectco | informalequation | >>>> informalexample | informalfigure | informaltable | equation >>>> | example | figure | table | msgset | procedure | sidebar | >>>> qandaset | task | anchor | bridgehead | remark | highlights >>>> | abstract | authorblurb | epigraph | indexterm | >>>> beginpage)+, got () Chap_lenovo_Q180.xml:8: validity error : >>>> ID chap-linux_book-Test_Chapter already defined >>>> Chap_lenovo_Q180.xml:13: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_lenovo_Q180.xml:21: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> Chap_audio_vids_conversion.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_audio_vids_conversion.xml:76: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_audio_vids_conversion.xml:138: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> Chap_publican_docbook_serna.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_publican_docbook_serna.xml:25: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_publican_docbook_serna.xml:76: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> Chap_sh_backup.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_sh_backup.xml:25: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_bash.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_bash.xml:13: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_Clean_install.xml:8: validity error : ID >>>> chap-linux_book-Test_Chapter already defined >>>> Chap_Clean_install.xml:13: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>> Chap_Clean_install.xml:230: validity error : ID >>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>> >>>> >>>> On Mon, Aug 18, 2014 at 3:09 PM, Frederic Monestel >>>> wrote: >>>> >>>>> Thanks very much for this precision Jeff, >>>>> >>>>> Here you go this is the errors, I have: >>>>> >>>>> Many thanks for your help and kind regards, >>>>> >>>>> Fred >>>>> >>>>> Beginning work on en-US DTD Validation failed for >>>>> '/home/fred/Documents/IT/linux_book/tmp/en-US/xml/linux_book.xml': >>>>> >>>>> >>>>> Chap_airport.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_airport.xml:16: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_Debian.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_Debian.xml:19: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already >>>>> defined Chap_Debian.xml:111: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>>> Chap_Fedora.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_Fedora.xml:13: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already >>>>> defined Chap_compil_stellarium.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_compil_stellarium.xml:13: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_compil_stellarium.xml:21: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>>> Chap_compil_stellarium.xml:32: validity error : Element >>>>> listitem content does not follow the DTD, expecting >>>>> (calloutlist | glosslist | bibliolist | itemizedlist | >>>>> orderedlist | segmentedlist | simplelist | variablelist | >>>>> caution | important | note | tip | warning | literallayout >>>>> | programlisting | programlistingco | screen | screenco | >>>>> screenshot | synopsis | cmdsynopsis | funcsynopsis | >>>>> classsynopsis | fieldsynopsis | constructorsynopsis | >>>>> destructorsynopsis | methodsynopsis | formalpara | para | >>>>> simpara | address | blockquote | graphic | graphicco | >>>>> mediaobject | mediaobjectco | informalequation | >>>>> informalexample | informalfigure | informaltable | >>>>> equation | example | figure | table | msgset | procedure | >>>>> sidebar | qandaset | task | anchor | bridgehead | remark | >>>>> highlights | abstract | authorblurb | epigraph | indexterm >>>>> | beginpage)+, got () Chap_lenovo_Q180.xml:8: validity >>>>> error : ID chap-linux_book-Test_Chapter already defined >>>>> Chap_lenovo_Q180.xml:13: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_lenovo_Q180.xml:21: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>>> Chap_audio_vids_conversion.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_audio_vids_conversion.xml:76: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_audio_vids_conversion.xml:138: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>>> Chap_publican_docbook_serna.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_publican_docbook_serna.xml:25: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_publican_docbook_serna.xml:76: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already defined >>>>> Chap_sh_backup.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_sh_backup.xml:25: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_bash.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_bash.xml:13: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_Clean_install.xml:8: validity error : ID >>>>> chap-linux_book-Test_Chapter already defined >>>>> Chap_Clean_install.xml:13: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_1 already defined >>>>> Chap_Clean_install.xml:230: validity error : ID >>>>> sect-linux_book-Test_Chapter-Test_Section_2 already >>>>> defined >>>>> >>>>> >>>>> >>>>> On Mon, Aug 18, 2014 at 12:32 AM, Jeff Fearn >>>>> wrote: >>>>> >>>>>> On 08/17/2014 08:50 PM, Frederic Monestel wrote: >>>>>>> i mean that the book can be built and does not generate >>>>>>> errors while >>>>>> you do publican build. i believe i have to modify all >>>>>> ids and relate them to the file names, chapters and >>>>>> sections names. >>>>>> >>>>>> You do not have to set IDs. If an ID is not set then a >>>>>> random ID is created during the build process. >>>>>> >>>>>> If you are having build issues it is unlikely to be >>>>>> related to the lack of ID. >>>>>> >>>>>> If you include the errors we could help debug your >>>>>> issue. >>>>>> >>>>>> Cheers, Jeff. >>>>>> >>>>>> -- Jeff Fearn Senior Software Engineer GSS Subscriber >>>>>> Platform Red Hat Pty Ltd >>>>>> >>>>>> _______________________________________________ >>>>>> publican-list mailing list publican-list at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/publican-list >>>>>> Wiki: https://fedorahosted.org/publican >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> _______________________________________________ publican-list >>>> mailing list publican-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/publican-list Wiki: >>>> https://fedorahosted.org/publican >>>> > > >> >> _______________________________________________ publican-list >> mailing list publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list Wiki: >> https://fedorahosted.org/publican >> > - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJT8n9VAAoJEDpAHQqWGp+3OMQIAOEQTZINuwNf6vtWTIkH/2St xCIM4nBoIzVblmI8IoKUUWcrckhy37puJXqFjnZOyNNCqXBt60mJwCqxosej0gWA gbzKMWB1bgmXkLHZfHn3XZSA3CXlJDIkSgbIZJAMmbqcnpv5HHlsQnEP3ygTX+EF 5wnY+a/20W7kRmEJ0GHJ9dIoIQirsnbL4Asw/sIhTdmGjT2wkCStd320G0MGfKU/ fty1PzP9wDtdB3iH/OANPgwAdEnXrlo+yaAx0wvDb8PNYS4a2AlPumZO1S8nO5uv W4r7H9fapQ/BwSNRCd/4uZjk0pwBhd5YKnHzeLD8h4t42gCZ1a2hogt3FQRndaI= =/fMt -----END PGP SIGNATURE----- From w.david.ashley at gmail.com Wed Aug 20 20:38:37 2014 From: w.david.ashley at gmail.com (David Ashley) Date: Wed, 20 Aug 2014 15:38:37 -0500 Subject: [publican-list] Programlisting Language Attribute Message-ID: <1408567117.3072.6.camel@dhcp-9-41-90-229.austin.ibm.com> Is there a place in the Publican configuration where I can find the list of languages supported by the Programlisting tag? And if my language is not supported, is there a way to add my language? W. David Ashley From jfearn at redhat.com Wed Aug 20 22:54:48 2014 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 21 Aug 2014 08:54:48 +1000 Subject: [publican-list] Programlisting Language Attribute In-Reply-To: <1408567117.3072.6.camel@dhcp-9-41-90-229.austin.ibm.com> References: <1408567117.3072.6.camel@dhcp-9-41-90-229.austin.ibm.com> Message-ID: <53F52738.40600@redhat.com> Hi David, On 08/21/2014 06:38 AM, David Ashley wrote: > Is there a place in the Publican configuration where I can find the list of languages supported by the Programlisting tag? https://jfearn.fedorapeople.org/en-US/Publican/4.1/html/Users_Guide/chap-Publican-Users_Guide-Frequently_Asked_Questions.html#idm210026787408 > And if my language is not supported, is there a way to add my language? You would need to get the language added to Kate, then get the upstream perl module we used updated. Cheers, Jeff. -- Jeff Fearn Senior Software Engineer GSS Subscriber Platform Red Hat Pty Ltd From lbailey at redhat.com Wed Aug 20 23:58:09 2014 From: lbailey at redhat.com (Laura Bailey) Date: Wed, 20 Aug 2014 19:58:09 -0400 (EDT) Subject: [publican-list] Programlisting Language Attribute In-Reply-To: <1408567117.3072.6.camel@dhcp-9-41-90-229.austin.ibm.com> References: <1408567117.3072.6.camel@dhcp-9-41-90-229.austin.ibm.com> Message-ID: <1494707201.47505467.1408579089087.JavaMail.zimbra@redhat.com> Hi David, Syntax highlighting in Publican is provided by the Syntax::Highlight::Engine::Kate Perl module. As per the Publican User Guide FAQ [1], http://search.cpan.org/dist/Syntax-Highlight-Engine-Kate/lib/Syntax/Highlight/Engine/Kate.pm#PLUGINS has the full list of languages that Syntax::Highlight::Engine::Kate supports, including their expected capitalization and punctuation. Hope this helps! Cheers, Laura B [1] https://jfearn.fedorapeople.org/en-US/Publican/4.0/html/Users_Guide/chap-Publican-Users_Guide-Frequently_Asked_Questions.html#idm209995190704 ----- Original Message ----- From: "David Ashley" To: publican-list at redhat.com Sent: Thursday, 21 August, 2014 6:38:37 AM Subject: [publican-list] Programlisting Language Attribute Is there a place in the Publican configuration where I can find the list of languages supported by the Programlisting tag? And if my language is not supported, is there a way to add my language? W. David Ashley _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican -- Laura Bailey Senior Technical Writer Red Hat Customer Content Services BNE From bugzilla at redhat.com Mon Aug 25 02:10:19 2014 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 25 Aug 2014 02:10:19 +0000 Subject: [publican-list] [Bug 718717] enabling line numbering disables code highlighting In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=718717 publican-list changed: What |Removed |Added ---------------------------------------------------------------------------- CC|publican-list at redhat.com | Don Domingo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddomingo at redhat.com QA Contact|r.landmann at redhat.com |mlopes at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=gq1VTHYS5d&a=cc_unsubscribe From jfearn at redhat.com Thu Aug 28 01:19:21 2014 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 28 Aug 2014 11:19:21 +1000 Subject: [publican-list] Publican 4.2.0 release Message-ID: <53FE8399.30507@redhat.com> Hi, Publican 4.2.0 has been released, the full release notes are on the web [1]. The sources are in the usual place [2]. Important things I like to note are: 1: Markdown is now supported as an output format. 2: Some _really_ good changes for program listings, check out BZs #1088051 & #1092351 (Thanks for the ideas Josh!) 3: Some dependency versions have been bumped because all the patches we where carrying for deps now have an upstream release with the patches applied! List of changes (the release notes have explanations): - Add iframe video support to DocBook5 HTML5. BZ #752021 - Stop calculating column width if no width is set. BZ #1084860 - Simply styling of code, and admonitions in HTML5. BZ #1093498 - Added tip formatting. BZ #1033830 - Remove incorrect prompt. BZ #1096544 - Add "popper" to hide program listing after 4 lines. BZ #1088051 - Fix white space being removed from msgids when merging. BZ #1097090 - Add code language switching. BZ #1092351 - Fix CDATA support, bump XML::TreeBuilder dep to 5.3. BZ #1101050 - Add --showfuzzy to build options. - Move PO manipulation to Locale::PO. - Fix inline "\n" not working in verbatim. BZ #1097091 - Fix images for DB4 website callouts. BZ #1112899 - Remove newline after cdata. BZ #1110611 - Add Markdown output. BZ #1120455 - Bump Syntax::Highlight::Engine::Kate dep to 0.09. - Add external link support. BZ #1123193 - Add 'th' to translation block list. BZ #1127462 Cheers, Jeff. 1: https://jfearn.fedorapeople.org//en-US/Publican/4.2/html/Release_Notes/index.html 2: https://fedorahosted.org/publican/#Howtogetthesource -- Jeff Fearn Senior Software Engineer GSS Subscriber Platform Red Hat Pty Ltd