From maillist at diffingo.com Thu Jul 1 19:06:03 2010 From: maillist at diffingo.com (Stewart Adam) Date: Thu, 01 Jul 2010 15:06:03 -0400 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML Message-ID: <4C2CE71B.50209@diffingo.com> Hi, I started working with Publican yesterday and I think it's awesome, it has been so much easier and cleaner to work with it instead of hacking together Makefiles and coding everything by hand. There's been one minor issue that I've noticed when I compare the PDF to the HTML output: On any note, warning or important there seems to be a bug in the way padding is rendered in the PDF output. The HTML output looks normal (with a 1em border all around and the image positioned 1em away, both x & y) but the in the PDF the text runs right up until the rectangle border in some cases and the image is stuck to the far left. I've attached screenshots that demonstrate what I mean. Thanks, Stewart -------------- next part -------------- A non-text attachment was scrubbed... Name: html.png Type: image/png Size: 24545 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pdf.png Type: image/png Size: 35361 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: html-safari-inspect.png Type: image/png Size: 24875 bytes Desc: not available URL: From maillist at diffingo.com Thu Jul 1 19:14:33 2010 From: maillist at diffingo.com (Stewart Adam) Date: Thu, 01 Jul 2010 15:14:33 -0400 Subject: [publican-list] Brand licensing Message-ID: <4C2CE919.3030100@diffingo.com> Hi, If I have understood correctly from the user guide (at jfearn.fedorapeople.org/Publican), the "common" Publican brand is included in when building any content and then the override.css from the book or article's selected brand is applied to make any modifications. Does this cause licensing issues for brands that wish to use alternative licenses such as CC-BY-SA? I'm wondering because I like the default publican brand but I would like to make a few minor modifications (header/link color & adding my software's logos) and have the brand licensed under CC-BY-SA 3.0... Thanks, Stewart From jfearn at redhat.com Thu Jul 1 22:54:33 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 02 Jul 2010 08:54:33 +1000 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML In-Reply-To: <4C2CE71B.50209@diffingo.com> References: <4C2CE71B.50209@diffingo.com> Message-ID: <4C2D1CA9.80003@redhat.com> Hi Stewart, welcome to the list :) Stewart Adam wrote: > Hi, > > I started working with Publican yesterday and I think it's awesome, it > has been so much easier and cleaner to work with it instead of hacking > together Makefiles and coding everything by hand. > > There's been one minor issue that I've noticed when I compare the PDF to > the HTML output: On any note, warning or important there seems to be a > bug in the way padding is rendered in the PDF output. The HTML output > looks normal (with a 1em border all around and the image positioned 1em > away, both x & y) but the in the PDF the text runs right up until the > rectangle border in some cases and the image is stuck to the far left. > I've attached screenshots that demonstrate what I mean. I think the mailing list ate the images, I'll try and find some time to take a look at this issue. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Thu Jul 1 22:55:02 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 02 Jul 2010 08:55:02 +1000 Subject: [publican-list] Brand licensing In-Reply-To: <4C2CE919.3030100@diffingo.com> References: <4C2CE919.3030100@diffingo.com> Message-ID: <4C2D1CC6.9030903@redhat.com> Hi Stewart, Stewart Adam wrote: > Hi, > > If I have understood correctly from the user guide (at > jfearn.fedorapeople.org/Publican), the "common" Publican brand is > included in when building any content and then the override.css from the > book or article's selected brand is applied to make any modifications. > Does this cause licensing issues for brands that wish to use alternative > licenses such as CC-BY-SA? > > I'm wondering because I like the default publican brand but I would like > to make a few minor modifications (header/link color & adding my > software's logos) and have the brand licensed under CC-BY-SA 3.0... The common brand materials are licensed under CC0, which is the most permissive CC license. It allows relicensing to more restrictive licenses, such as CC-BY-SA, including non-free or non-open licenses. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From hertzog at debian.org Fri Jul 2 06:01:43 2010 From: hertzog at debian.org (Raphael Hertzog) Date: Fri, 2 Jul 2010 08:01:43 +0200 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML In-Reply-To: <4C2D1CA9.80003@redhat.com> References: <4C2CE71B.50209@diffingo.com> <4C2D1CA9.80003@redhat.com> Message-ID: <20100702060143.GA3223@rivendell> On Fri, 02 Jul 2010, Jeffrey Fearn wrote: > >There's been one minor issue that I've noticed when I compare the > >PDF to the HTML output: On any note, warning or important there > >seems to be a bug in the way padding is rendered in the PDF > >output. The HTML output looks normal (with a 1em border all around > >and the image positioned 1em away, both x & y) but the in the PDF > >the text runs right up until the rectangle border in some cases > >and the image is stuck to the far left. I've attached screenshots > >that demonstrate what I mean. > > I think the mailing list ate the images, I'll try and find some time > to take a look at this issue. I got the images, so it's not the ML but something on your own mail servers. Cheers, -- Rapha?l Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ From jwulf at redhat.com Fri Jul 2 06:04:42 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Fri, 02 Jul 2010 08:04:42 +0200 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML In-Reply-To: <20100702060143.GA3223@rivendell> References: <4C2CE71B.50209@diffingo.com> <4C2D1CA9.80003@redhat.com> <20100702060143.GA3223@rivendell> Message-ID: <4C2D817A.1010508@redhat.com> On 07/02/2010 08:01 AM, Raphael Hertzog wrote: > On Fri, 02 Jul 2010, Jeffrey Fearn wrote: > >>> There's been one minor issue that I've noticed when I compare the >>> PDF to the HTML output: On any note, warning or important there >>> seems to be a bug in the way padding is rendered in the PDF >>> output. The HTML output looks normal (with a 1em border all around >>> and the image positioned 1em away, both x& y) but the in the PDF >>> the text runs right up until the rectangle border in some cases >>> and the image is stuck to the far left. I've attached screenshots >>> that demonstrate what I mean. >>> >> I think the mailing list ate the images, I'll try and find some time >> to take a look at this issue. >> > I got the images, so it's not the ML but something on your own mail > servers. > > Cheers, > I got the images, from the same server that does Jeff's mail, so it's not the server. From maillist at diffingo.com Fri Jul 2 07:42:33 2010 From: maillist at diffingo.com (Stewart Adam) Date: Fri, 02 Jul 2010 03:42:33 -0400 Subject: [publican-list] Brand licensing In-Reply-To: <4C2D1CC6.9030903@redhat.com> References: <4C2CE919.3030100@diffingo.com> <4C2D1CC6.9030903@redhat.com> Message-ID: <4C2D9869.6060704@diffingo.com> On 2010/07/01 6:55 PM, Jeffrey Fearn wrote: > Hi Stewart, > Stewart Adam wrote: >> Hi, >> >> If I have understood correctly from the user guide (at >> jfearn.fedorapeople.org/Publican), the "common" Publican brand is included >> in when building any content and then the override.css from the book or >> article's selected brand is applied to make any modifications. Does this >> cause licensing issues for brands that wish to use alternative licenses >> such as CC-BY-SA? >> >> I'm wondering because I like the default publican brand but I would like >> to make a few minor modifications (header/link color & adding my >> software's logos) and have the brand licensed under CC-BY-SA 3.0... > > The common brand materials are licensed under CC0, which is the most > permissive CC license. It allows relicensing to more restrictive licenses, > such as CC-BY-SA, including non-free or non-open licenses. > > Cheers, Jeff. Thanks for clearing that up! Section 4.1 of the guide [1] describes "common" as GNU FDL with comment "GPL compatible license. No options". Perhaps we should change that to CC0 with a comment somewhere along the lines of "Sub-licensing permitted"? Regards, Stewart [1] http://jfearn.fedorapeople.org/Publican/chap-Users_Guide-Branding.html#sect-Users_Guide-Installing_a_brand From maillist at diffingo.com Fri Jul 2 07:49:18 2010 From: maillist at diffingo.com (Stewart Adam) Date: Fri, 02 Jul 2010 03:49:18 -0400 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML In-Reply-To: <4C2D1CA9.80003@redhat.com> References: <4C2CE71B.50209@diffingo.com> <4C2D1CA9.80003@redhat.com> Message-ID: <4C2D99FE.4020407@diffingo.com> On 2010/07/01 6:54 PM, Jeffrey Fearn wrote: > Hi Stewart, welcome to the list :) Thanks! > I think the mailing list ate the images, I'll try and find some time to take > a look at this issue. > > Cheers, Jeff. I'm not sure what happened, but I've also uploaded them to my fedorapeople page: http://firewing.fedorapeople.org/publican-screenshots/ Cheers, Stewart From jfearn at redhat.com Sun Jul 4 22:58:25 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Mon, 05 Jul 2010 08:58:25 +1000 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML In-Reply-To: <4C2D99FE.4020407@diffingo.com> References: <4C2CE71B.50209@diffingo.com> <4C2D1CA9.80003@redhat.com> <4C2D99FE.4020407@diffingo.com> Message-ID: <4C311211.6050809@redhat.com> Stewart Adam wrote: > On 2010/07/01 6:54 PM, Jeffrey Fearn wrote: >> Hi Stewart, welcome to the list :) > Thanks! > >> I think the mailing list ate the images, I'll try and find some time >> to take >> a look at this issue. >> >> Cheers, Jeff. > I'm not sure what happened, but I've also uploaded them to my > fedorapeople page: http://firewing.fedorapeople.org/publican-screenshots/ Hi, I've added 1em left padding to the icon and 1em right margin to the content block. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY -------------- next part -------------- A non-text attachment was scrubbed... Name: pdf.png Type: image/png Size: 63799 bytes Desc: not available URL: From jfearn at redhat.com Sun Jul 4 23:01:41 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Mon, 05 Jul 2010 09:01:41 +1000 Subject: [publican-list] Brand licensing In-Reply-To: <4C2D9869.6060704@diffingo.com> References: <4C2CE919.3030100@diffingo.com> <4C2D1CC6.9030903@redhat.com> <4C2D9869.6060704@diffingo.com> Message-ID: <4C3112D5.4060301@redhat.com> Stewart Adam wrote: > On 2010/07/01 6:55 PM, Jeffrey Fearn wrote: >> Hi Stewart, >> Stewart Adam wrote: >>> Hi, >>> >>> If I have understood correctly from the user guide (at >>> jfearn.fedorapeople.org/Publican), the "common" Publican brand is >>> included >>> in when building any content and then the override.css from the book or >>> article's selected brand is applied to make any modifications. Does this >>> cause licensing issues for brands that wish to use alternative licenses >>> such as CC-BY-SA? >>> >>> I'm wondering because I like the default publican brand but I would like >>> to make a few minor modifications (header/link color & adding my >>> software's logos) and have the brand licensed under CC-BY-SA 3.0... >> >> The common brand materials are licensed under CC0, which is the most >> permissive CC license. It allows relicensing to more restrictive >> licenses, >> such as CC-BY-SA, including non-free or non-open licenses. >> >> Cheers, Jeff. > Thanks for clearing that up! > > Section 4.1 of the guide [1] describes "common" as GNU FDL with comment > "GPL compatible license. No options". Perhaps we should change that to > CC0 with a comment somewhere along the lines of "Sub-licensing permitted"? > > Regards, > Stewart > > [1] > http://jfearn.fedorapeople.org/Publican/chap-Users_Guide-Branding.html#sect-Users_Guide-Installing_a_brand This section is pretty confusing, I'll sit down with Rudi and get it rewritten. Thanks for the heads up :) Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From maillist at diffingo.com Mon Jul 5 02:09:13 2010 From: maillist at diffingo.com (Stewart Adam) Date: Sun, 04 Jul 2010 22:09:13 -0400 Subject: [publican-list] Borders and image placement different of note/warning/important in PDF vs HTML In-Reply-To: <4C311211.6050809@redhat.com> References: <4C2CE71B.50209@diffingo.com> <4C2D1CA9.80003@redhat.com> <4C2D99FE.4020407@diffingo.com> <4C311211.6050809@redhat.com> Message-ID: <4C313EC9.1080004@diffingo.com> On 2010/07/04 6:58 PM, Jeffrey Fearn wrote: > Stewart Adam wrote: >> On 2010/07/01 6:54 PM, Jeffrey Fearn wrote: >>> Hi Stewart, welcome to the list :) >> Thanks! >> >>> I think the mailing list ate the images, I'll try and find some time to take >>> a look at this issue. >>> >>> Cheers, Jeff. >> I'm not sure what happened, but I've also uploaded them to my fedorapeople >> page: http://firewing.fedorapeople.org/publican-screenshots/ > > Hi, I've added 1em left padding to the icon and 1em right margin to the > content block. Great! Thanks for taking a look at this. Stewart From bugzilla at redhat.com Mon Jul 5 04:01:24 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 5 Jul 2010 00:01:24 -0400 Subject: [publican-list] [Bug 592823] should not break a paragraph for translation In-Reply-To: References: Message-ID: <201007050401.o6541Oqs028484@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=592823 Ruediger Landmann changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(ccheng at redhat.com | |) --- Comment #12 from Ruediger Landmann 2010-07-05 00:01:23 EDT --- Confirmed that Publican 1.99.t135 doesn't break the string. Given this XML: This is a test paragraph paragraph in a section the resulting PO file entry is: #. Tag: para #, no-c-format msgid "This is a test paragraph paragraph in a section" msgstr "" Chester, could you please confirm that this is suitable? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 5 04:04:15 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 5 Jul 2010 00:04:15 -0400 Subject: [publican-list] [Bug 592823] should not break a paragraph for translation In-Reply-To: References: Message-ID: <201007050404.o6544FsV029028@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=592823 Chester Cheng changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|needinfo?(ccheng at redhat.com | |) | --- Comment #13 from Chester Cheng 2010-07-05 00:04:14 EDT --- Hi Rudi, Yes, it is suitable. Cheers, Chester (In reply to comment #12) > Confirmed that Publican 1.99.t135 doesn't break the string. > > Given this XML: > > > This is a test paragraph paragraph in > a section > > > the resulting PO file entry is: > > #. Tag: para > #, no-c-format > msgid "This is a test paragraph > paragraph in a section" > msgstr "" > > > Chester, could you please confirm that this is suitable? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From jwulf at redhat.com Mon Jul 5 04:17:12 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 05 Jul 2010 06:17:12 +0200 Subject: [publican-list] Dual color highlighting of remarks Message-ID: <4C315CC8.7020100@redhat.com> Currently we can call out changed content via the tag, which applies highlighting. Could we use an attribute of remark to have a primary and secondary color? I have some requests for yellow for "changed since last release" and orange for "changed since last review". - Josh From jfearn at redhat.com Tue Jul 6 03:09:09 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 06 Jul 2010 13:09:09 +1000 Subject: [publican-list] Dual color highlighting of remarks In-Reply-To: <4C315CC8.7020100@redhat.com> References: <4C315CC8.7020100@redhat.com> Message-ID: <4C329E55.3050307@redhat.com> Joshua Wulf wrote: > Currently we can call out changed content via the tag, which > applies highlighting. > > Could we use an attribute of remark to have a primary and secondary > color? I have some requests for yellow for "changed since last release" > and orange for "changed since last review". You can do this in the brand: 1: set the role to something 2: for HTML add an entry to the bottom of the brand css file 3: for override and change the xsl:use-attribute-sets based on role. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Tue Jul 6 03:11:30 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 06 Jul 2010 13:11:30 +1000 Subject: [publican-list] Dual color highlighting of remarks In-Reply-To: <4C329E55.3050307@redhat.com> References: <4C315CC8.7020100@redhat.com> <4C329E55.3050307@redhat.com> Message-ID: <4C329EE2.7010801@redhat.com> Jeffrey Fearn wrote: > Joshua Wulf wrote: >> Currently we can call out changed content via the tag, which >> applies highlighting. >> >> Could we use an attribute of remark to have a primary and secondary >> color? I have some requests for yellow for "changed since last >> release" and orange for "changed since last review". > > You can do this in the brand: > > 1: set the role to something > 2: for HTML add an entry to the bottom of the brand css file > 3: for override and change the ^ PDF From bugzilla at redhat.com Tue Jul 6 04:44:21 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 00:44:21 -0400 Subject: [publican-list] [Bug 592823] should not break a paragraph for translation In-Reply-To: References: Message-ID: <201007060444.o664iLeG020330@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=592823 Lawrence Lim changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|llim at redhat.com |ecs-bugs at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 04:53:18 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 00:53:18 -0400 Subject: [publican-list] [Bug 486050] Publican Website In-Reply-To: References: Message-ID: <201007060453.o664rItX022965@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=486050 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anross at redhat.com QAContact|llim at redhat.com |ecs-bugs at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 04:53:39 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 00:53:39 -0400 Subject: [publican-list] [Bug 604255] Problem with callouts In-Reply-To: References: Message-ID: <201007060453.o664rdvv021877@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=604255 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anross at redhat.com QAContact|llim at redhat.com |ecs-bugs at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 04:54:26 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 00:54:26 -0400 Subject: [publican-list] [Bug 475684] Find solution for using Glossaries with publican In-Reply-To: References: Message-ID: <201007060454.o664sQCt021962@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=475684 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anross at redhat.com QAContact|jwulf at redhat.com |ecs-bugs at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 04:54:07 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 00:54:07 -0400 Subject: [publican-list] [Bug 595564] RFE: can xref links to formalpara go to the actual formalpara, rather than top of the page? In-Reply-To: References: Message-ID: <201007060454.o664s7ve021918@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=595564 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anross at redhat.com QAContact|desktop-bugs at redhat.com |ecs-bugs at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 06:00:43 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 02:00:43 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007060600.o6660hj1003818@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #3 from Fedora Update System 2010-07-06 02:00:43 EDT --- publican-2.0-0.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/publican-2.0-0.fc13 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 06:01:22 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 02:01:22 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007060601.o6661MSK003963@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #4 from Fedora Update System 2010-07-06 02:01:22 EDT --- publican-2.0-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/publican-2.0-0.fc12 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From jhradile at redhat.com Tue Jul 6 16:50:18 2010 From: jhradile at redhat.com (Jaromir Hradilek) Date: Tue, 06 Jul 2010 18:50:18 +0200 Subject: [publican-list] A dead link to the Users Guide at the homepage Message-ID: <4C335ECA.7070802@redhat.com> Hi, I have noticed that the link to the Users Guide at the Publican's homepage (pointing to [1]) does not work anymore, as I am getting "404 Not Found" instead. Did the documentation move somewhere else by any chance? Thanks! [1] http://jfearn.fedorapeople.org/Publican/ Regards, -- Jaromir Hradilek Associate Content Author Engineering Content Services Red Hat Czech s. r. o. Purkynova 99, 612 45 Brno Phone: +420 532 294 326 From bugzilla at redhat.com Tue Jul 6 17:18:43 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 13:18:43 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007061718.o66HIhHs009069@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 Fedora Update System changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |ON_QA --- Comment #5 from Fedora Update System 2010-07-06 13:18:42 EDT --- publican-2.0-0.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update publican'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/publican-2.0-0.fc12 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 6 17:20:08 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 13:20:08 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007061720.o66HK8Fe025072@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #6 from Fedora Update System 2010-07-06 13:20:08 EDT --- publican-2.0-0.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update publican'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/publican-2.0-0.fc13 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From r.landmann at redhat.com Tue Jul 6 21:12:33 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 07 Jul 2010 07:12:33 +1000 Subject: [publican-list] A dead link to the Users Guide at the homepage In-Reply-To: <4C335ECA.7070802@redhat.com> References: <4C335ECA.7070802@redhat.com> Message-ID: <4C339C41.8010406@redhat.com> On 07/07/2010 02:50 AM, Jaromir Hradilek wrote: > Hi, > > I have noticed that the link to the Users Guide at the Publican's > homepage (pointing to [1]) does not work anymore, as I am getting "404 > Not Found" instead. Did the documentation move somewhere else by any > chance? Yes, sorry -- this is the new link: http://jfearn.fedorapeople.org From jfearn at redhat.com Tue Jul 6 23:10:42 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 07 Jul 2010 09:10:42 +1000 Subject: [publican-list] A dead link to the Users Guide at the homepage In-Reply-To: <4C339C41.8010406@redhat.com> References: <4C335ECA.7070802@redhat.com> <4C339C41.8010406@redhat.com> Message-ID: <4C33B7F2.1070300@redhat.com> Ruediger Landmann wrote: > On 07/07/2010 02:50 AM, Jaromir Hradilek wrote: >> Hi, >> >> I have noticed that the link to the Users Guide at the Publican's >> homepage (pointing to [1]) does not work anymore, as I am getting "404 >> Not Found" instead. Did the documentation move somewhere else by any >> chance? > > Yes, sorry -- this is the new link: http://jfearn.fedorapeople.org I made a symlink ... lucky there are no sys-admin on this list to beat me up over it :D Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From bugzilla at redhat.com Wed Jul 7 03:13:23 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 23:13:23 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007070313.o673DN61024888@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #7 from Fedora Update System 2010-07-06 23:13:22 EDT --- publican-2.1-0.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/publican-2.1-0.fc13 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 03:14:00 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 6 Jul 2010 23:14:00 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007070314.o673E0tm021417@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #8 from Fedora Update System 2010-07-06 23:13:59 EDT --- publican-2.1-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/publican-2.1-0.fc12 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From r.landmann at redhat.com Wed Jul 7 05:47:55 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 07 Jul 2010 15:47:55 +1000 Subject: [publican-list] Announcement: Publican 2 released Message-ID: <4C34150B.30206@redhat.com> Publican 2 is finally finished and released. The most significant update is the incorporation of the web-publishing component that was previously used stand-alone by Red Hat internally and, more recently, has been used by the Fedora Documentation Project to build the Fedora documentation suite.[0] With web publishing built in, Publican can handle the whole publication process from raw XML to a live website. The new feature is documented in a new chapter in the Users' Guide.[1] Apart from this major new feature, Publican 2 also includes fixes for several bugs; most notably: xrefs to various elements that didn't work, problems with for translators, and various presentation flaws. No changes are required to documents created with (or updated with) Publican 1.x to make them build in Publican 2. The "publican old2new" command remains available to update documents created with Publican 0.x so that they will build in Publican 2. Publican 2 is not yet available as a Fedora update; however, you can download builds from the Fedora build system (Koji) for testing[2]. If Publican 2 works for you, help make it available for others. Visit the Fedora update system (Bodhi),[3] log in with your Fedora ID, and give positive Karma to the package. Note that if you do not log in to Bodhi, your feedback will not count. For users of other operating systems, the source tarball is available from Fedorahosted.[4] Cheers, Rudi Changelog: - Add Publican::Website. - Add web_*_label params for web menus. - Add underscores to cleanset, installbrand, and printtree. BZ #581090 - Update docs with Website content - Update brand license text. - Fix different log jar path on F14+ - Add constraint to help_config output. - Fix segfault when indexterm has no leading content. BZ #592666 - Fix inline indexterm. BZ #592823 - Translate productname tag. BZ #592669 - Fix formalpara missing ID. BZ #595564 - Add dummy lang.css to avoid 404's. BZ #595799 - Improve validation error message. BZ #593887 - Fix qandaentry ID. BZ #593892 - Fix Icon non-conformance. BZ #593890 - Fix admonitions splitting across pages. BZ #596257 - Fix HTML simple list border. BZ #599258 - Fix formal object IDs. BZ #601363 - Fix Revision History layout. BZ #559787 #598828 #598833 - Remove title color from term in HTML. BZ #592822 - Fix highlight breaking callouts. BZ #590933 - Add support for LineColumn coords in area tag. - Update font requires for F12 and F13. - Fix clean_ids adding newline to verbatim. BZ #604465 - Fix index missing ID. BZ #606418 - Fix files dir being missed. BZ #609345 - Adjust admonition layout. [0] http://docs.fedoraproject.org [1] "Chapter 6. Building a website with Publican", available online at http://jfearn.fedorapeople.org/en-US/Publican/2.0/html/Users_Guide/sect-Users_Guide-Website.html [2] http://kojipkgs.fedoraproject.org/packages/publican/2.1/0.fc13/noarch/publican-2.1-0.fc13.noarch.rpm for Fedora 13 or http://kojipkgs.fedoraproject.org/packages/publican/2.1/0.fc12/noarch/publican-2.1-0.fc12.noarch.rpm for Fedora 12 [3] https://admin.fedoraproject.org/updates/publican-2.1-0.fc13 for Fedora 13 or https://admin.fedoraproject.org/updates/publican-2.1-0.fc12 for Fedora 12 [4] https://fedorahosted.org/releases/p/u/publican/Publican-2.1.tar.gz From jwulf at redhat.com Wed Jul 7 06:35:51 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 07 Jul 2010 08:35:51 +0200 Subject: [publican-list] Announcement: Publican 2 released In-Reply-To: <4C34150B.30206@redhat.com> References: <4C34150B.30206@redhat.com> Message-ID: <4C342047.2070309@redhat.com> Congratulations! Publican is becoming an even more awesome open source publishing tool chain. On 07/07/2010 07:47 AM, Ruediger Landmann wrote: > Publican 2 is finally finished and released. The most significant > update is the incorporation of the web-publishing component that was > previously used stand-alone by Red Hat internally and, more recently, > has been used by the Fedora Documentation Project to build the Fedora > documentation suite.[0] With web publishing built in, Publican can > handle the whole publication process from raw XML to a live website. > The new feature is documented in a new chapter in the Users' Guide.[1] > > Apart from this major new feature, Publican 2 also includes fixes for > several bugs; most notably: xrefs to various elements that didn't > work, problems with for translators, and various > presentation flaws. > > No changes are required to documents created with (or updated with) > Publican 1.x to make them build in Publican 2. The "publican old2new" > command remains available to update documents created with Publican > 0.x so that they will build in Publican 2. > > Publican 2 is not yet available as a Fedora update; however, you can > download builds from the Fedora build system (Koji) for testing[2]. If > Publican 2 works for you, help make it available for others. Visit the > Fedora update system (Bodhi),[3] log in with your Fedora ID, and give > positive Karma to the package. Note that if you do not log in to > Bodhi, your feedback will not count. > > For users of other operating systems, the source tarball is available > from Fedorahosted.[4] > > Cheers, > Rudi > > > Changelog: > - Add Publican::Website. > - Add web_*_label params for web menus. > - Add underscores to cleanset, installbrand, and printtree. BZ #581090 > - Update docs with Website content > - Update brand license text. > - Fix different log jar path on F14+ > - Add constraint to help_config output. > - Fix segfault when indexterm has no leading content. BZ #592666 > - Fix inline indexterm. BZ #592823 > - Translate productname tag. BZ #592669 > - Fix formalpara missing ID. BZ #595564 > - Add dummy lang.css to avoid 404's. BZ #595799 > - Improve validation error message. BZ #593887 > - Fix qandaentry ID. BZ #593892 > - Fix Icon non-conformance. BZ #593890 > - Fix admonitions splitting across pages. BZ #596257 > - Fix HTML simple list border. BZ #599258 > - Fix formal object IDs. BZ #601363 > - Fix Revision History layout. BZ #559787 #598828 #598833 > - Remove title color from term in HTML. BZ #592822 > - Fix highlight breaking callouts. BZ #590933 > - Add support for LineColumn coords in area tag. > - Update font requires for F12 and F13. > - Fix clean_ids adding newline to verbatim. BZ #604465 > - Fix index missing ID. BZ #606418 > - Fix files dir being missed. BZ #609345 > - Adjust admonition layout. > > [0] http://docs.fedoraproject.org > > [1] "Chapter 6. Building a website with Publican", available online at > http://jfearn.fedorapeople.org/en-US/Publican/2.0/html/Users_Guide/sect-Users_Guide-Website.html > > > [2] > http://kojipkgs.fedoraproject.org/packages/publican/2.1/0.fc13/noarch/publican-2.1-0.fc13.noarch.rpm > for Fedora 13 or > http://kojipkgs.fedoraproject.org/packages/publican/2.1/0.fc12/noarch/publican-2.1-0.fc12.noarch.rpm > for Fedora 12 > > [3] https://admin.fedoraproject.org/updates/publican-2.1-0.fc13 for > Fedora 13 or > https://admin.fedoraproject.org/updates/publican-2.1-0.fc12 for Fedora 12 > > [4] https://fedorahosted.org/releases/p/u/publican/Publican-2.1.tar.gz > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > > From bugzilla at redhat.com Wed Jul 7 17:35:34 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:35:34 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007071735.o67HZYts021276@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #9 from Fedora Update System 2010-07-07 13:35:34 EDT --- publican-2.1-0.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:35:16 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:35:16 -0400 Subject: [publican-list] [Bug 592823] should not break a paragraph for translation In-Reply-To: References: Message-ID: <201007071735.o67HZGGq008521@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=592823 --- Comment #14 from Fedora Update System 2010-07-07 13:35:15 EDT --- publican-2.1-0.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:39:50 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:39:50 -0400 Subject: [publican-list] [Bug 592823] should not break a paragraph for translation In-Reply-To: References: Message-ID: <201007071739.o67HdoG8009211@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=592823 --- Comment #15 from Fedora Update System 2010-07-07 13:39:49 EDT --- publican-2.1-0.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:35:25 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:35:25 -0400 Subject: [publican-list] [Bug 595564] RFE: can xref links to formalpara go to the actual formalpara, rather than top of the page? In-Reply-To: References: Message-ID: <201007071735.o67HZP6G008553@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=595564 --- Comment #6 from Fedora Update System 2010-07-07 13:35:24 EDT --- publican-2.1-0.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:36:07 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:36:07 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007071736.o67Ha742008674@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 Fedora Update System changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |publican-2.1-0.fc12 Resolution| |ERRATA -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:40:08 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:40:08 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007071740.o67He8bd022392@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 --- Comment #10 from Fedora Update System 2010-07-07 13:40:07 EDT --- publican-2.1-0.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:40:43 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:40:43 -0400 Subject: [publican-list] [Bug 593887] Terse validity error messages make troubleshooting XML structure issues difficult. In-Reply-To: References: Message-ID: <201007071740.o67HehOT010081@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=593887 Fedora Update System changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|publican-2.1-0.fc12 |publican-2.1-0.fc13 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 7 17:39:59 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 7 Jul 2010 13:39:59 -0400 Subject: [publican-list] [Bug 595564] RFE: can xref links to formalpara go to the actual formalpara, rather than top of the page? In-Reply-To: References: Message-ID: <201007071739.o67HdxNw009269@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=595564 --- Comment #7 from Fedora Update System 2010-07-07 13:39:58 EDT --- publican-2.1-0.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 12 03:48:33 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 11 Jul 2010 23:48:33 -0400 Subject: [publican-list] [Bug 559787] duplicate Revision History headings In-Reply-To: References: Message-ID: <201007120348.o6C3mXrc004941@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=559787 Ruediger Landmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Resolution| |ERRATA --- Comment #4 from Ruediger Landmann 2010-07-11 23:48:31 EDT --- Confirmed fixed in 2.1 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From jwulf at redhat.com Tue Jul 13 22:27:37 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 14 Jul 2010 06:27:37 +0800 Subject: [publican-list] Publican Website docs Message-ID: <4C3CE859.3060106@redhat.com> I built a Publican website the other day, and took the notes below on the user docs. Anyone else tried to follow them and noticed similar things? - Josh Notes on section 6.2 in the Publican User Guide: 1. Should be a procedure, rather than an orderedlist. 2. Step 8 fails with "langs is a mandatory argument" 3. Adding --langs=en-US, fails with "Beginning work on en-US Cannot locate main XML file: 'JBoss_Enterprise_Application_Platform.xml' at /usr/bin/publican line 622" - this is caused by editing Article_Info.xml in accordance with step 3 Instruction should be given: mv en-US/Home_Page.xml en-US/<title>.xml mv en-US/Home_Page.ent en-US/<title>.ent Where <title> is the value you entered in Article_Info.xml 4. Step 4 covers two completely different things - web_home, and search. Should be split up From r.landmann at redhat.com Wed Jul 14 00:11:51 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 14 Jul 2010 10:11:51 +1000 Subject: [publican-list] Publican Website docs In-Reply-To: <4C3CE859.3060106@redhat.com> References: <4C3CE859.3060106@redhat.com> Message-ID: <4C3D00C7.6050305@redhat.com> On 07/14/2010 08:27 AM, Joshua Wulf wrote: > I built a Publican website the other day, and took the notes below on > the user docs. > Thanks Josh for the detailed feedback! I've created the following bug to track my work as I rectify these problems: https://bugzilla.redhat.com/show_bug.cgi?id=614259 Cheers Rudi From jwulf at redhat.com Wed Jul 14 22:26:19 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Thu, 15 Jul 2010 08:26:19 +1000 Subject: [publican-list] Off-line website on user's machine Message-ID: <4C3E398B.1030905@redhat.com> Eclipse has a help system where eclipse plugins can integrate their help, providing a user with a single view of all their help files at their finger tips. What possibilities are there that we could provide a similar setup with Publican, using the off-line website? My idea is that the publican website could be a cross-platform Yelp, where we would have a single database and as new products are installed their documentation would be added to the same place, rather than having multiple publican websites on a single machine. From bugzilla at redhat.com Mon Jul 19 17:23:02 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 19 Jul 2010 13:23:02 -0400 Subject: [publican-list] [Bug 616112] New: certain element IDs do not cause anchors to be generated, even if xref'd to Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: certain element IDs do not cause anchors to be generated, even if xref'd to https://bugzilla.redhat.com/show_bug.cgi?id=616112 Summary: certain element IDs do not cause anchors to be generated, even if xref'd to Product: Red Hat Enterprise Linux 5 Version: 5.7 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: publican AssignedTo: mhideo at redhat.com ReportedBy: dhensley at redhat.com QAContact: ecs-bugs at redhat.com CC: publican-list at redhat.com Classification: Red Hat Target Release: --- Description of problem: setting the ID of an important admonition does not cause an anchor to be generated for that element, even if it is referenced via an xref. The xref does generate an href anchor that, however, is missing from the target. This is probably similar to bug 595564. Version-Release number of selected component (if applicable): version=2.1 How reproducible: Steps to Reproduce: 1. xref to the ID of an important admonition 2. publican build (html-single in this case) 3. open document, click on link to admonition, no jump Actual results: nothing Expected results: jump to link Additional info: Generated link HTML is: Smart package group removal Generated target HTML is:

Smart package group removal

-- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 19 17:42:37 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 19 Jul 2010 13:42:37 -0400 Subject: [publican-list] [Bug 616112] certain element IDs do not cause anchors to be generated, even if xref'd to In-Reply-To: References: Message-ID: <201007191742.o6JHgbYm015146@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=616112 --- Comment #1 from Douglas Silas 2010-07-19 13:42:36 EDT --- Perhaps the creation of anchors for indexing overrides or affects the generated anchors? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 22 21:07:55 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 22 Jul 2010 17:07:55 -0400 Subject: [publican-list] [Bug 616112] certain element IDs do not cause anchors to be generated, even if xref'd to In-Reply-To: References: Message-ID: <201007222107.o6ML7tjf018137@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=616112 --- Comment #2 from Douglas Silas 2010-07-22 17:07:54 EDT --- Note: this problem also occurs when linking to varlistentry elements. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Jul 25 23:59:03 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 25 Jul 2010 19:59:03 -0400 Subject: [publican-list] [Bug 604255] Problem with callouts In-Reply-To: References: Message-ID: <201007252359.o6PNx30x030106@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=604255 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC|anross at redhat.com | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Jul 25 23:57:49 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 25 Jul 2010 19:57:49 -0400 Subject: [publican-list] [Bug 486050] Publican Website In-Reply-To: References: Message-ID: <201007252357.o6PNvnIs029558@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=486050 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC|anross at redhat.com | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Jul 25 23:58:13 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 25 Jul 2010 19:58:13 -0400 Subject: [publican-list] [Bug 475684] Find solution for using Glossaries with publican In-Reply-To: References: Message-ID: <201007252358.o6PNwDG0029739@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=475684 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC|anross at redhat.com | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Jul 25 23:56:14 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 25 Jul 2010 19:56:14 -0400 Subject: [publican-list] [Bug 595564] RFE: can xref links to formalpara go to the actual formalpara, rather than top of the page? In-Reply-To: References: Message-ID: <201007252356.o6PNuEUl028838@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=595564 Andrew Ross changed: What |Removed |Added ---------------------------------------------------------------------------- CC|anross at redhat.com | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From jfearn at redhat.com Mon Jul 26 01:20:12 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 26 Jul 2010 11:20:12 +1000 Subject: [publican-list] Off-line website on user's machine In-Reply-To: <4C3E398B.1030905@redhat.com> References: <4C3E398B.1030905@redhat.com> Message-ID: <1280107212.2487.53.camel@localhost> On Thu, 2010-07-15 at 08:26 +1000, Joshua Wulf wrote: > Eclipse has a help system where eclipse plugins can integrate their > help, providing a user with a single view of all their help files at > their finger tips. > > What possibilities are there that we could provide a similar setup with > Publican, using the off-line website? My idea is that the publican > website could be a cross-platform Yelp, where we would have a single > database and as new products are installed their documentation would be > added to the same place, rather than having multiple publican websites > on a single machine. I think you just need everyone to agree on where the default DB is located on a particular OS ...Is there anything you think needs to be coded? Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY Sure our competitors can rebuild the source but can they engage the customer the same way? -wmealing From dhensley at redhat.com Tue Jul 27 00:10:16 2010 From: dhensley at redhat.com (Douglas Silas) Date: Tue, 27 Jul 2010 02:10:16 +0200 Subject: [publican-list] [Bug 616123] New: RFE: more fine-grained control over main and division TOC levels Message-ID: <4C4E23E8.8070601@redhat.com> https://bugzilla.redhat.com/show_bug.cgi?id=616123 Description of problem: Two settings controlling TOC creation are: generate_section_toc_level: 0 # controls the section depth at which Publican will generate a table of contents. At the default value of 0, Publican will generate tables of contents at the start of the document and in parts, chapters, and appendixes, but not in sections. If (for example) the value is set to 1, tables of contents also appear in each "level 1" section, such as sections 1.1, 1.2, 2.1, and 2.2. If set to 2, tables of contents also appear in "level 2" sections, such as sections 1.1.1, 1.1.2, and 1.2.1. toc_section_depth: 2 # controls the depth of sections that Publican includes in the main table of contents. By default, this value is set to 2. With the default setting, sections 1.1 and 1.1.1 will appear in the main table of contents, but section 1.1.1.1 will not. (Note that the first digit in these examples represents a chapter, not a section). Note that the combination of these does not, for example, allow for setting the main TOC to have a level of 1, while chapters/sections have a level of 2. It would be both logical and useful for a (large, long) book's TOC to have a shallow section depth (, while the chapter or section's TOC is more detailed. My proposal is to have separate "main_toc_section_depth" and "division_toc_section_depth" directives that control the initial and all later TOC section depths, respectively, thus allowing for more fine-grained control over navigation, appearance and organization. Note: the description for toc_section_depth reads "controls the depth of sections that Publican includes in the main table of contents". Is there a (hidden) option to control the TOC depth of other divisions, or does this need to be revised? toc_section_depth affects all TOCs. Version-Release number of selected component (if applicable): version=2.1 -- Douglas Silas Technical Writer | Red Hat, Inc. Purky?ova 99 | Brno, Czech Republic Office Direct Dial?62116 Brno Office?(+420) 532 294 111 ext. 10718 From dhensley at redhat.com Tue Jul 27 00:11:40 2010 From: dhensley at redhat.com (Douglas Silas) Date: Tue, 27 Jul 2010 02:11:40 +0200 Subject: [publican-list] [Bug 616142] New: RFC: building only part of a book by altering xrefs Message-ID: <4C4E243C.9090106@redhat.com> https://bugzilla.redhat.com/show_bug.cgi?id=616142 I have a request for consideration for a controversial feature that has two important and related use cases: * I have a very large book to publish, but due to (various) reasons, only want to publish part of it. The content is all interlinked with xrefs, though, so I cannot build the book unless I manually change all of them. * I am working on a single chapter of a very large book that takes up to 2 minutes or more to build (with publican 1/2+, which is still a huge improvement), and to view my work (to review as a draft, or to check the formatting), I would like to build a single chapter. However, due to the rigor inherited by xrefs, I cannot. The best (and completely hypothetical) solution for these cases would be if xrefs were more like xi:includes: For more information about firewalls, refer to some_unique_id the Firewalls section of the Red Hat Enterprise Linux Security Guide. I suppose technically that the mix of inline and block-level elements there wouldn't work, but that's the idea. In lieu of such a useful construct, I am wondering if: * there is any interest on behalf of others in building only part of a book; * there are any suggestions for what to replace xrefs to nonexistent targets with; and, * this is a good idea or a bad one. This feature could be abused by users saying, "Well, if the book doesn't build because of broken xrefs, just turn on directive ignore_xrefs in publican.cfg." If this were a feature, publican could warn that it converted linkends A, B and C in X and Y chapters into ____ elements. Perhaps this could be a feature that could only be enabled on the command line, and thus could not set for entire books. I think its utility is undeniable, though, as it would save many of us time and effort. I currently cannot publish completed chapters of an overall 500+ page book I am editing (that is interlinked heavily with xrefs) without either changing all the xrefs manually in a publication branch, or writing a hack of a script that replaces these xrefs with s or some other element. I've done the latter out of necessity, but it is almost certainly better if this problem is discussed on the list, where we could perhaps come up with a single band-aid instead of many individual ones :-) -- Douglas Silas Technical Writer | Red Hat, Inc. Purky?ova 99 | Brno, Czech Republic Office Direct Dial?62116 Brno Office?(+420) 532 294 111 ext. 10718 From jfearn at redhat.com Tue Jul 27 01:41:23 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 27 Jul 2010 11:41:23 +1000 Subject: [publican-list] [Bug 616142] New: RFC: building only part of a book by altering xrefs In-Reply-To: <4C4E243C.9090106@redhat.com> References: <4C4E243C.9090106@redhat.com> Message-ID: <4C4E3943.4020704@redhat.com> Douglas Silas wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=616142 > > I have a request for consideration for a controversial feature that has two > important and related use cases: > > * I have a very large book to publish, but due to (various) reasons, > only want > to publish part of it. The content is all interlinked with xrefs, > though, so I > cannot build the book unless I manually change all of them. > > * I am working on a single chapter of a very large book that takes up to 2 > minutes or more to build (with publican 1/2+, which is still a huge > improvement), and to view my work (to review as a draft, or to check the > formatting), I would like to build a single chapter. However, due to the > rigor > inherited by xrefs, I cannot. > > The best (and completely hypothetical) solution for these cases would be if > xrefs were more like xi:includes: > > For more information about firewalls, refer to > some_unique_id > the Firewalls > section of > the Red Hat Enterprise Linux Security > Guide. > > I suppose technically that the mix of inline and block-level elements there > wouldn't work, but that's the idea. > > In lieu of such a useful construct, I am wondering if: > > * there is any interest on behalf of others in building only part of a > book; > > * there are any suggestions for what to replace xrefs to nonexistent > targets > with; and, > > * this is a good idea or a bad one. > > This feature could be abused by users saying, "Well, if the book doesn't > build > because of broken xrefs, just turn on directive ignore_xrefs in > publican.cfg." > If this were a feature, publican could warn that it converted linkends > A, B and > C in X and Y chapters into ____ elements. Perhaps this could be a > feature that > could only be enabled on the command line, and thus could not set for > entire > books. I think its utility is undeniable, though, as it would save many > of us > time and effort. I currently cannot publish completed chapters of an > overall > 500+ page book I am editing (that is interlinked heavily with xrefs) > without > either changing all the xrefs manually in a publication branch, or > writing a > hack of a script that replaces these xrefs with s or some other > element. I've done the latter out of necessity, but it is almost certainly > better if this problem is discussed on the list, where we could perhaps > come up > with a single band-aid instead of many individual ones :-) > You could probably use conditions to achieve this. e.g. ... chapter1.xml chapter one See chapter2.xml chapter two If life serves you lemons, make me dessert! ... Then in your publican.cfg you just set the conditions for the chapters you want included. If you REALLY want to have an alternative text, then have two conditions, e.g. chapter2 to use if chapter two is set and not_chapter2 for when chapter 2 isn't set. You could specify every chapter in the cfg file and prepend 'not_' to the chapters you want excluded. e.g. chapter1.xml chapter one See Link deliberately omitted for this build Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY