From bugzilla at redhat.com Thu Apr 1 00:30:55 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 31 Mar 2010 20:30:55 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010030.o310UtRK023944@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=578366 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfearn at redhat.com AssignedTo|mhideo at redhat.com |jfearn 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 Thu Apr 1 03:11:51 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 31 Mar 2010 23:11:51 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010311.o313Bp4d028960@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=578366 --- Comment #1 from Ruediger Landmann 2010-03-31 23:11:46 EDT --- --quiet and --nocolours options tested and working in 1.6.1-0.t29 -- 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 Apr 1 04:40:01 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 00:40:01 -0400 Subject: [publican-list] [Bug 578691] New: SVG images don't work when embedded in a document. Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: SVG images don't work when embedded in a document. https://bugzilla.redhat.com/show_bug.cgi?id=578691 Summary: SVG images don't work when embedded in a document. Product: Red Hat Enterprise Linux 5 Version: 5.4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: publican AssignedTo: mhideo at redhat.com ReportedBy: ccurran at redhat.com QAContact: desktop-bugs at redhat.com CC: publican-list at redhat.com Classification: Red Hat Target Release: --- Description of problem: SVGs are breaking PDF builds. Version-Release number of selected component (if applicable): 1.6.1, RHEL and Fedora. How reproducible: 100% Steps to Reproduce: 1. Use the attached image anywhere. 2. PDF breaks Actual results: Publican completes with errors but does not create a PDF Expected results: Publican can build with SVG Additional info: -- 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 Apr 1 04:41:57 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 00:41:57 -0400 Subject: [publican-list] [Bug 578691] SVG images don't work when embedded in a document. In-Reply-To: References: Message-ID: <201004010441.o314fvLb003988@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=578691 --- Comment #2 from Christopher Curran 2010-04-01 00:41:53 EDT --- Created an attachment (id=403871) --> (https://bugzilla.redhat.com/attachment.cgi?id=403871) SVG image -- 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 Apr 1 04:41:27 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 00:41:27 -0400 Subject: [publican-list] [Bug 578691] SVG images don't work when embedded in a document. In-Reply-To: References: Message-ID: <201004010441.o314fRt2003932@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=578691 --- Comment #1 from Christopher Curran 2010-04-01 00:41:22 EDT --- Created an attachment (id=403869) --> (https://bugzilla.redhat.com/attachment.cgi?id=403869) the error output -- 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 Apr 1 04:53:28 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 00:53:28 -0400 Subject: [publican-list] [Bug 578691] SVG images don't work when embedded in a document. In-Reply-To: References: Message-ID: <201004010453.o314rSVu017265@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=578691 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |jfearn at redhat.com Resolution| |NOTABUG --- Comment #3 from Jeff Fearn 2010-04-01 00:53:26 EDT --- You are asking Batik to handle SVG components it apparently can't handle, you will need to open an RFE upstream. -- 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 Apr 1 05:01:50 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 01:01:50 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010501.o3151oIt019078@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=578366 Ruediger Landmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_DEV Fixed In Version| |1.6.2 -- 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 Apr 1 05:15:19 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 01:15:19 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010515.o315FJtO022636@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=578366 --- Comment #2 from Fedora Update System 2010-04-01 01:15:16 EDT --- publican-1.6.2-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/publican-1.6.2-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 Thu Apr 1 05:15:46 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 01:15:46 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010515.o315FkG2022733@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=578366 --- Comment #3 from Fedora Update System 2010-04-01 01:15:41 EDT --- publican-1.6.2-0.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/publican-1.6.2-0.fc11 -- 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 Apr 1 05:16:09 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 01:16:09 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010516.o315G9rr011534@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=578366 --- Comment #4 from Fedora Update System 2010-04-01 01:16:08 EDT --- publican-1.6.2-0.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/publican-1.6.2-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 Thu Apr 1 05:29:42 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Thu, 01 Apr 2010 15:29:42 +1000 Subject: [publican-list] Publican 1.6.2 released Message-ID: <4BB42F46.3010506@redhat.com> Hi all -- Publican 1.6.2 is now built and released. This release fixes a number of bugs related to localization issues, and adds a couple of requested features. - Fix hyphenate.verbatim running out of depth. BZ #577095 - Fix UTF8 error in translations. BZ #576771 - Add surname and othername to translatable tag list. BZ #578343 - No fuzzy strings in merged XML. BZ #578337 - Allow clean_ids to add entity reference. BZ #576462 - Added --quiet and --nocolours. BZ #578366 Thanks Jeff! I know that the UTF8 ended up being quite a pain :( Cheers Rudi From bugzilla at redhat.com Thu Apr 1 07:29:35 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 1 Apr 2010 03:29:35 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004010729.o317TZOW001337@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=578366 --- Comment #5 from Sean Flanigan 2010-04-01 03:29:32 EDT --- Thanks Jeff; it looks good, and I'm glad to see colour spelt better than I had dared hope! Just a few minor things: 1. The descriptions of the new options don't line up with the other global options, at least on my terminal: ie: -v Display the version of Publican --config Use a nonstandard config file --nocolours Disable ANSI colourisation of logging --quiet Disable all logging This is purely cosmetic, but it might bother some people. 2. Also, I found that these new options had to be entered after the action, eg publican build --quiet not publican --quiet build The usage help (and the Publican documentation) seem to assume that global options never appear together with an action, but my experience with other command line tools does lead me to expect that global options will precede actions, eg: svn --non-interactive update 3. The Publican documentation hasn't been updated to describe these options, but I don't know if that's significant at this point. Thanks for the quick turnaround! -- 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 Sat Apr 3 04:39:54 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 3 Apr 2010 00:39:54 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004030439.o334dsNI023242@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=578366 --- Comment #6 from Fedora Update System 2010-04-03 00:39:51 EDT --- publican-1.6.2-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 Sat Apr 3 04:50:32 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 3 Apr 2010 00:50:32 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004030450.o334oW3g027168@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=578366 --- Comment #7 from Fedora Update System 2010-04-03 00:50:30 EDT --- publican-1.6.2-0.fc11 has been pushed to the Fedora 11 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 Tue Apr 6 02:00:53 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 5 Apr 2010 22:00:53 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004060200.o3620rrM013441@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=578366 --- Comment #8 from Jeff Fearn 2010-04-05 22:00:50 EDT --- This was confusing so I renamed and reordered the options and the help texts. Mainly because there are 3 kinds of options and only 2 were appearing in the helps texts >_< Renamed 'Global Options' to 'Command Options' these apply only to the publican command, not to actions. Renamed 'Options' to 'Action Options' these apply only to actions not to the publican command. Displayed 'Common Options', common_config, nocolour etc, as part of the action help text. $ bin/publican --help Usage: publican publican Command Options --help Display help message --man Display the man page --help_actions Display a list of valid actions -v Display the version of Publican Run: 'publican --help' for details on action usage Valid actions are: build Transform XML to other formats (pdf, html, html-single, etc) ... $ bin/publican build --help build Transform XML to other formats (pdf, html, html-single, etc) Options: --help Display help message --config=s Use a nonstandard config file --common_config=s Override path to Common_Config directory --common_content=s Override path to Common_Content directory --nocolours Disable ANSI colourisation of logging. --quiet Disable all logging. --formats= Comma-separated list of formats, for example: html,pdf,html-single,html-desktop,txt,epub --langs= Comma-separated list of languages, for example: en-US,de-DE,all ... Will begin bugging Rudi to update docs :) -- 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 josh.kayse at gtri.gatech.edu Tue Apr 6 11:59:07 2010 From: josh.kayse at gtri.gatech.edu (Josh Kayse) Date: Tue, 6 Apr 2010 07:59:07 -0400 Subject: [publican-list] cannot build with publican > 1.6.1 Message-ID: <4BBB220B.6070607@gtri.gatech.edu> After upgrading from 1.3 to 1.6.2 I can no longer build any documents with publican. runtime error: file file:///usr/share/sgml/docbook/xsl-stylesheets-1.75.2/fo/verbatim.xsl line 413 element param xsltApplyXSLTTemplate: A potential infinite template recursion was detected. You can adjust xsltMaxDepth (--maxdepth) in order to raise the maximum number of nested template calls and variables/params (currently set to 1000). Is the error I am receiving. I have tried with different brands with the same result. Any recommendations? Thanks, -josh From pmorgan at redhat.com Tue Apr 6 12:51:52 2010 From: pmorgan at redhat.com (Paul Morgan) Date: Tue, 6 Apr 2010 08:51:52 -0400 Subject: [publican-list] cannot build with publican > 1.6.1 In-Reply-To: <4BBB220B.6070607@gtri.gatech.edu> References: <4BBB220B.6070607@gtri.gatech.edu> Message-ID: <20100406125152.GA3020@redhat.com> On Tue, Apr 06, 2010 at 07:59:07AM -0400, Josh Kayse wrote: > After upgrading from 1.3 to 1.6.2 I can no longer build any > documents with publican. > > runtime error: file > file:///usr/share/sgml/docbook/xsl-stylesheets-1.75.2/fo/verbatim.xsl > line 413 element param > xsltApplyXSLTTemplate: A potential infinite template recursion was detected. > You can adjust xsltMaxDepth (--maxdepth) in order to raise the > maximum number of nested template calls and variables/params > (currently set to 1000). > > Is the error I am receiving. > > I have tried with different brands with the same result. > > Any recommendations? > > Thanks, > -josh I'm getting the same error while attempting to rebuild a document I haven't changed since upgrading. My doc has 335 pages, though smaller docs build fine. -paul -- Paul Morgan RHCE, RHCX, RHCDS, RHCVA, RHCSS, RHCA Voice: 317-jumanji (317-586-2654) GPG Public Key ID: 0xf59e77c2 Fingerprint = 3248 D0C8 4B42 2F7C D92A AEA0 7D20 6D66 F59E 77C2 From josh.kayse at gtri.gatech.edu Tue Apr 6 13:55:55 2010 From: josh.kayse at gtri.gatech.edu (Josh Kayse) Date: Tue, 6 Apr 2010 09:55:55 -0400 Subject: [publican-list] cannot build with publican >= 1.6.1 In-Reply-To: <20100406125152.GA3020@redhat.com> References: <4BBB220B.6070607@gtri.gatech.edu> <20100406125152.GA3020@redhat.com> Message-ID: <4BBB3D6B.8000808@gtri.gatech.edu> On 04/06/2010 08:51 AM, Paul Morgan wrote: > On Tue, Apr 06, 2010 at 07:59:07AM -0400, Josh Kayse wrote: >> After upgrading from 1.3 to 1.6.2 I can no longer build any >> documents with publican. >> >> runtime error: file >> file:///usr/share/sgml/docbook/xsl-stylesheets-1.75.2/fo/verbatim.xsl >> line 413 element param >> xsltApplyXSLTTemplate: A potential infinite template recursion was detected. >> You can adjust xsltMaxDepth (--maxdepth) in order to raise the >> maximum number of nested template calls and variables/params >> (currently set to 1000). >> >> Is the error I am receiving. >> >> I have tried with different brands with the same result. >> >> Any recommendations? >> >> Thanks, >> -josh > > I'm getting the same error while attempting to rebuild a document > I haven't changed since upgrading. My doc has 335 pages, though > smaller docs build fine. > > -paul > Confirmed that shortening my document allows me to build. Updated the subject to reflect that it started with 1.6.1, not 1.6.2 -josh -- A: No. Q: Should I include quotations after my reply? Don't top post: see http://www.caliburn.nl/topposting.html for more. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2687 bytes Desc: S/MIME Cryptographic Signature URL: From josh.kayse at gtri.gatech.edu Tue Apr 6 14:09:42 2010 From: josh.kayse at gtri.gatech.edu (Josh Kayse) Date: Tue, 6 Apr 2010 10:09:42 -0400 Subject: [publican-list] cannot build with publican >= 1.6.1 In-Reply-To: <4BBB3D6B.8000808@gtri.gatech.edu> References: <4BBB220B.6070607@gtri.gatech.edu> <20100406125152.GA3020@redhat.com> <4BBB3D6B.8000808@gtri.gatech.edu> Message-ID: <4BBB40A6.5070400@gtri.gatech.edu> On 04/06/2010 09:55 AM, Josh Kayse wrote: > On 04/06/2010 08:51 AM, Paul Morgan wrote: >> On Tue, Apr 06, 2010 at 07:59:07AM -0400, Josh Kayse wrote: >>> After upgrading from 1.3 to 1.6.2 I can no longer build any >>> documents with publican. >>> >>> runtime error: file >>> file:///usr/share/sgml/docbook/xsl-stylesheets-1.75.2/fo/verbatim.xsl >>> line 413 element param >>> xsltApplyXSLTTemplate: A potential infinite template recursion was detected. >>> You can adjust xsltMaxDepth (--maxdepth) in order to raise the >>> maximum number of nested template calls and variables/params >>> (currently set to 1000). >>> >>> Is the error I am receiving. >>> >>> I have tried with different brands with the same result. >>> >>> Any recommendations? >>> >>> Thanks, >>> -josh >> >> I'm getting the same error while attempting to rebuild a document >> I haven't changed since upgrading. My doc has 335 pages, though >> smaller docs build fine. >> >> -paul >> > > Confirmed that shortening my document allows me to build. Updated the > subject to reflect that it started with 1.6.1, not 1.6.2 > > -josh > Changing line 704 of /usr/lib/perl5/vendor_perl/5.10.0/Publican/Builder.pm from 1000 to 10000 allows me to build my 400+ page document. I don't know that it is the correct action, but it will work for me for now. -josh -- A: No. Q: Should I include quotations after my reply? Don't top post: see http://www.caliburn.nl/topposting.html for more. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2687 bytes Desc: S/MIME Cryptographic Signature URL: From pmorgan at redhat.com Tue Apr 6 15:11:52 2010 From: pmorgan at redhat.com (Paul Morgan) Date: Tue, 6 Apr 2010 11:11:52 -0400 Subject: [publican-list] cannot build with publican >= 1.6.1 In-Reply-To: <4BBB40A6.5070400@gtri.gatech.edu> References: <4BBB220B.6070607@gtri.gatech.edu> <20100406125152.GA3020@redhat.com> <4BBB3D6B.8000808@gtri.gatech.edu> <4BBB40A6.5070400@gtri.gatech.edu> Message-ID: <20100406151152.GA8465@redhat.com> On Tue, Apr 06, 2010 at 10:09:42AM -0400, Josh Kayse wrote: > On 04/06/2010 09:55 AM, Josh Kayse wrote: >> On 04/06/2010 08:51 AM, Paul Morgan wrote: >>> On Tue, Apr 06, 2010 at 07:59:07AM -0400, Josh Kayse wrote: >>>> After upgrading from 1.3 to 1.6.2 I can no longer build any >>>> documents with publican. >>>> >>>> runtime error: file >>>> file:///usr/share/sgml/docbook/xsl-stylesheets-1.75.2/fo/verbatim.xsl >>>> line 413 element param >>>> xsltApplyXSLTTemplate: A potential infinite template recursion was detected. >>>> You can adjust xsltMaxDepth (--maxdepth) in order to raise the >>>> maximum number of nested template calls and variables/params >>>> (currently set to 1000). >>>> >>>> Is the error I am receiving. >>>> >>>> I have tried with different brands with the same result. >>>> >>>> Any recommendations? >>>> >>>> Thanks, >>>> -josh >>> >>> I'm getting the same error while attempting to rebuild a document >>> I haven't changed since upgrading. My doc has 335 pages, though >>> smaller docs build fine. >>> >>> -paul >>> >> >> Confirmed that shortening my document allows me to build. Updated the >> subject to reflect that it started with 1.6.1, not 1.6.2 >> >> -josh >> > Changing line 704 of > /usr/lib/perl5/vendor_perl/5.10.0/Publican/Builder.pm from 1000 to > 10000 allows me to build my 400+ page document. > > I don't know that it is the correct action, but it will work for me for now. > > -josh Thanks, Josh. Your workaround works for me, too. I've created BZ: https://bugzilla.redhat.com/show_bug.cgi?id=579786 -paul From sherringham at gmail.com Tue Apr 6 19:59:51 2010 From: sherringham at gmail.com (Alastair Sherringham) Date: Tue, 6 Apr 2010 20:59:51 +0100 Subject: [publican-list] Creating a custom brand - can't get working Message-ID: Hello, Forgive me if I'm doing something wrong - I probably am. Publican 1.6.2 Ubuntu 9.10 I am trying to use a custom brand but cannot seem to get it working. None of my image branding is appearing, only the stock "common" images. Where am I going wrong? I have a brand created via : publican create_brand --name=Acme --> publican-Acme/ I edited some files (SETUP), modified some CSS and one or two images : publican-Acme/en-US/css/overrides.css publican-Acme/en-US/images/ Copy brand folder to be under Common_Content : cp -r publican-Acme /usr/share/publican/Common_Content/ Now - test using the brand in a manual I am writing : Add line to "publican.cfg" : brand: publican-Acme Build : publican build --formats=html --langs=en-US I get the CSS changes, but not the images in : tmp/en-US/html/Common_Content/images/ What am I doing wrong? Cheers, -- Alastair Sherringham http://www.sherringham.net From jfearn at redhat.com Tue Apr 6 23:29:36 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 07 Apr 2010 09:29:36 +1000 Subject: [publican-list] cannot build with publican >= 1.6.1 In-Reply-To: <20100406151152.GA8465@redhat.com> References: <4BBB220B.6070607@gtri.gatech.edu> <20100406125152.GA3020@redhat.com> <4BBB3D6B.8000808@gtri.gatech.edu> <4BBB40A6.5070400@gtri.gatech.edu> <20100406151152.GA8465@redhat.com> Message-ID: <4BBBC3E0.80404@redhat.com> Paul Morgan wrote: > On Tue, Apr 06, 2010 at 10:09:42AM -0400, Josh Kayse wrote: >> On 04/06/2010 09:55 AM, Josh Kayse wrote: >>> On 04/06/2010 08:51 AM, Paul Morgan wrote: >>>> On Tue, Apr 06, 2010 at 07:59:07AM -0400, Josh Kayse wrote: >>>>> After upgrading from 1.3 to 1.6.2 I can no longer build any >>>>> documents with publican. >>>>> >>>>> runtime error: file >>>>> file:///usr/share/sgml/docbook/xsl-stylesheets-1.75.2/fo/verbatim.xsl >>>>> line 413 element param >>>>> xsltApplyXSLTTemplate: A potential infinite template recursion was detected. >>>>> You can adjust xsltMaxDepth (--maxdepth) in order to raise the >>>>> maximum number of nested template calls and variables/params >>>>> (currently set to 1000). >>>>> >>>>> Is the error I am receiving. >>>>> >>>>> I have tried with different brands with the same result. >>>>> >>>>> Any recommendations? >>>>> >>>>> Thanks, >>>>> -josh >>>> I'm getting the same error while attempting to rebuild a document >>>> I haven't changed since upgrading. My doc has 335 pages, though >>>> smaller docs build fine. >>>> >>>> -paul >>>> >>> Confirmed that shortening my document allows me to build. Updated the >>> subject to reflect that it started with 1.6.1, not 1.6.2 >>> >>> -josh >>> >> Changing line 704 of >> /usr/lib/perl5/vendor_perl/5.10.0/Publican/Builder.pm from 1000 to >> 10000 allows me to build my 400+ page document. >> >> I don't know that it is the correct action, but it will work for me for now. >> >> -josh > > Thanks, Josh. Your workaround works for me, too. > > I've created BZ: https://bugzilla.redhat.com/show_bug.cgi?id=579786 This is actually caused by enabling hyphenation on the PDF build, it has been disabled in the SVN repo in both trunk and the 1.6 branch. We will push 1.6.3 in the next week or so to disable this. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Wed Apr 7 05:02:51 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 07 Apr 2010 15:02:51 +1000 Subject: [publican-list] Creating a custom brand - can't get working In-Reply-To: References: Message-ID: <4BBC11FB.8070202@redhat.com> Hi Alastair, Alastair Sherringham wrote: > Hello, > > Forgive me if I'm doing something wrong - I probably am. > > Publican 1.6.2 > Ubuntu 9.10 > > I am trying to use a custom brand but cannot seem to get it working. > None of my image branding is appearing, only the stock "common" > images. Where am I going wrong? > > I have a brand created via : > > publican create_brand --name=Acme > > --> publican-Acme/ > > I edited some files (SETUP), modified some CSS and one or two images : > > publican-Acme/en-US/css/overrides.css > publican-Acme/en-US/images/ > > > Copy brand folder to be under Common_Content : > > cp -r publican-Acme /usr/share/publican/Common_Content/ The correct process here is: $ cd publican-Acme $ publican build --formats xml --langs all --publish $ sudo publican installbrand --path /usr/share/publican/Common_Content Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From sherringham at gmail.com Wed Apr 7 06:54:32 2010 From: sherringham at gmail.com (Alastair Sherringham) Date: Wed, 7 Apr 2010 07:54:32 +0100 Subject: [publican-list] Creating a custom brand - can't get working In-Reply-To: <4BBC11FB.8070202@redhat.com> References: <4BBC11FB.8070202@redhat.com> Message-ID: On 7 April 2010 06:02, Jeffrey Fearn wrote: > The correct process here is: > > $ cd publican-Acme > $ publican build --formats xml --langs all --publish > $ sudo publican installbrand --path /usr/share/publican/Common_Content Thanks Jeff. The Users Guide (built in 1.6.2) is not clear here (Chapter 4. Branding). The section on installing a brand (4.1) says "you must place the brand files in a subdirectory of the Publican Common Content directory." Nothing I can see about build/publish or installbrand. I tried "installbrand" once before but got errors (maybe due to missing build/publish step). Unfortunately, it is still not working. I did the above commands for the brand. I now have a brand directory and structure : /usr/share/publican/Common_Content/Acme/ and my image files are present. My manual publican.cfg file contains : xml_lang: en-US type: Book brand: Acme I now clean and build my manual : publican clean publican build --formats=html --langs=en-US The directory is populated : tmp/en-US/html/Common_Content/images/ does *not* contain the "Acme" images. The manual is not custom branded. What am I missing now? Cheers, -- Alastair Sherringham http://www.sherringham.net From jfearn at redhat.com Thu Apr 8 03:31:25 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 08 Apr 2010 13:31:25 +1000 Subject: [publican-list] Creating a custom brand - can't get working In-Reply-To: References: <4BBC11FB.8070202@redhat.com> Message-ID: <1270697485.3198.34.camel@localhost> Hi Alastair, On Wed, 2010-04-07 at 07:54 +0100, Alastair Sherringham wrote: > On 7 April 2010 06:02, Jeffrey Fearn wrote: > > The correct process here is: > > > > $ cd publican-Acme > > $ publican build --formats xml --langs all --publish > > $ sudo publican installbrand --path /usr/share/publican/Common_Content > > Thanks Jeff. > > The Users Guide (built in 1.6.2) is not clear here (Chapter 4. > Branding). The section on installing a brand (4.1) says "you must > place the brand files in a subdirectory of the Publican Common Content > directory." Nothing I can see about build/publish or installbrand. I > tried "installbrand" once before but got errors (maybe due to missing > build/publish step). I'm sure Rudi will get right on this ... Rudi ... mate ;) > Unfortunately, it is still not working. > > I did the above commands for the brand. I now have a brand directory > and structure : > > /usr/share/publican/Common_Content/Acme/ > > and my image files are present. > > My manual publican.cfg file contains : > > xml_lang: en-US > type: Book > brand: Acme > > I now clean and build my manual : > > publican clean > publican build --formats=html --langs=en-US > > The directory is populated : > > tmp/en-US/html/Common_Content/images/ > > does *not* contain the "Acme" images. The manual is not custom branded. > > What am I missing now? This looks correct to me. Try running 'publican clean' in your book, regenerate the HTML, and see if the content in tmp/en-US/html is correct. If it's not then try enabling debug in the books publican.cfg and see if any messages related to the commmon content are generated. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From bugzilla at redhat.com Thu Apr 8 19:01:54 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 8 Apr 2010 15:01:54 -0400 Subject: [publican-list] [Bug 571633] Publican delete the new lines on the screen Tags when creating POTs In-Reply-To: References: Message-ID: <201004081901.o38J1s2k025193@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=571633 Douglas Silas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dhensley at redhat.com --- Comment #10 from Douglas Silas 2010-04-08 15:01:51 EDT --- I agree with the spirit of the change in comment 1. However, this change is causing problems with the Deployment Guide. There are a lot of instances where is used inside , and I am fixing them (so that I can run update_pot). But because of para's complex content model, it can be very difficult to see where this occurs. For example, I have the following nested tags in the LDAP chapter: a (with several siblings, which are not the problem, but complicate seeing it) inside a inside an inside a . (Don't ask me why someone did that...). Also, these same instances will exist in all 5.x branches of the DG, making them all, AFAIK, unable to update their POT files. Publican tells me which file the nesting problem occurs in, but doesn't provide any information about where it occurred. Would it be possible to output either a line number (of the file itself), or the content model that is causing the problem? Alternatively, you can find these by doing the following: install xmlstarlet: yum install xmlstarlet in the repo: xmlstarlet sel -t -v "//para/screen" my_chapter.xml If screen is nested directly inside a para, the screen's content will be output, providing you with a clue of where to look. (xmlstarlet is basically running an XPATH query on my_chapter.xml.) For deeper nests such as the one described above, I had to do this: temp!Deployment_Guide.git/tmp/en-US/xml_tmp *> xmlstarlet sel -t -v "//para/screen" Lightweight_Directory_Access_Protocol_LDAP.xml temp!Deployment_Guide.git/tmp/en-US/xml_tmp *> xmlstarlet sel -t -v "//para/*/screen" Lightweight_Directory_Access_Protocol_LDAP.xml temp!Deployment_Guide.git/tmp/en-US/xml_tmp *> xmlstarlet sel -t -v "//para/*/*/screen" Lightweight_Directory_Access_Protocol_LDAP.xml passwd: files ldap shadow: files ldap group: files ldap ...which finally showed the offending screen's content. If this change causes problems in lots of books, I think that this approach to finding the problems could be (bash-)scripted. Should I reopen this bug/file a new one? Thanks, Silas -- 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 Apr 8 19:41:40 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 8 Apr 2010 15:41:40 -0400 Subject: [publican-list] [Bug 571633] Publican delete the new lines on the screen Tags when creating POTs In-Reply-To: References: Message-ID: <201004081941.o38Jfe3p000382@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=571633 --- Comment #11 from Douglas Silas 2010-04-08 15:41:35 EDT --- Created an attachment (id=405388) --> (https://bugzilla.redhat.com/attachment.cgi?id=405388) This script finds screen elements nested inside para elements up to 5 deep -- 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 Apr 8 19:44:27 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 8 Apr 2010 15:44:27 -0400 Subject: [publican-list] [Bug 571633] Publican delete the new lines on the screen Tags when creating POTs In-Reply-To: References: Message-ID: <201004081944.o38JiRb8030266@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=571633 --- Comment #12 from Douglas Silas 2010-04-08 15:44:27 EDT --- After writing the comment 10 and then the script in comment 11, it turned out that there were only a few more to fix in all the files in the Deployment Guide. So it was not as big a problem as I had feared. The attached script is useful for finding screen-para nesting errors; perhaps someone else will be able to use it. -- Silas -- 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 Apr 8 21:48:16 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 8 Apr 2010 17:48:16 -0400 Subject: [publican-list] [Bug 571633] Publican delete the new lines on the screen Tags when creating POTs In-Reply-To: References: Message-ID: <201004082148.o38LmG2V024448@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=571633 --- Comment #13 from Jeff Fearn 2010-04-08 17:48:13 EDT --- You could optimise the search to: xmlstarlet sel -t -v "//screen/ancestor::para" There has been a bug opened at https://bugzilla.redhat.com/show_bug.cgi?id=580360 Cheers, Jeff. -- 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 Fri Apr 9 02:13:05 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 8 Apr 2010 22:13:05 -0400 Subject: [publican-list] [Bug 580774] New: Screenshots are rendered too small to be readable Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Screenshots are rendered too small to be readable https://bugzilla.redhat.com/show_bug.cgi?id=580774 Summary: Screenshots are rendered too small to be readable Product: Red Hat Enterprise Linux 5 Version: 5.7 Platform: All OS/Version: Linux Status: NEW Severity: high Priority: low Component: publican AssignedTo: mhideo at redhat.com ReportedBy: sburgess at redhat.com QAContact: desktop-bugs at redhat.com CC: publican-list at redhat.com Classification: Red Hat Target Release: --- Description of problem: Screenshots, particularly of complete screens, are rendered too small to be of use to the readers, in the html version. (PDF versions are ok). Version-Release number of selected component (if applicable): How reproducible: Create a screenshot of a full screen, and add to a document. Steps to Reproduce: 1. Create screenshot, save as png, add to document. 2. Publish document 3. Screenshot in the html version is forced into a 400 Pixel (maybe, Im guessing) display. Actual results: Screenshot in the html version is forced into a 400 Pixel (maybe, Im guessing) display. Screenshot in the pdf is okay. Expected results: Screenshot in the html version should be reproduced at the size that the writer specified, either by scaling the image prior to saving, or by using the docbook parameters. Additional info: This is user feedback. Getting very negative feedback from reviewers about the screenshots "ugliness" and unreadability. RHEV has a mandatory resolution of 1024x768, so I don't think users will be reading the docs on a lower resolution. Also, it is necessary to show the full screen on many occasions, as the user needs the context of the portal. -- 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 Fri Apr 9 02:29:01 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 8 Apr 2010 22:29:01 -0400 Subject: [publican-list] [Bug 580774] Screenshots are rendered too small to be readable In-Reply-To: References: Message-ID: <201004090229.o392T1sr016296@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=580774 David Jorm changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djorm at redhat.com --- Comment #1 from David Jorm 2010-04-08 22:28:57 EDT --- For me, the PDF images are also of a very poor resolution, and the way in which they scale is much less readable to the scaling to a similar resolution in GIMP. -- 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 Fri Apr 9 04:21:58 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 9 Apr 2010 00:21:58 -0400 Subject: [publican-list] [Bug 580774] Screenshots are rendered too small to be readable In-Reply-To: References: Message-ID: <201004090421.o394Lwva010687@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=580774 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfearn at redhat.com --- Comment #2 from Jeff Fearn 2010-04-09 00:21:57 EDT --- (In reply to comment #0) > Screenshot in the html version is forced into a 400 Pixel (maybe, Im guessing) > display. Screenshot in the pdf is okay. The 444 pixel limitation is at the request of ECS, you will need management sign off to change it. (In reply to comment #1) > For me, the PDF images are also of a very poor resolution, and the way in which > they scale is much less readable to the scaling to a similar resolution in > GIMP. In PDF the entire bitmap is embedded and the view port size is set, it is then up to the PDF viewer to scale the image. If you are unhappy with the scaling you will either need to scale the image yourself, which is what should happen anyway, or you need to open a bug against the viewer to get their scaling improved. Cheers, Jeff. -- 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 Fri Apr 9 04:27:59 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 9 Apr 2010 00:27:59 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004090427.o394Rxk4005476@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=578366 --- Comment #9 from Fedora Update System 2010-04-09 00:27:57 EDT --- publican-1.6.2-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 jfearn at redhat.com Fri Apr 9 21:54:14 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Sat, 10 Apr 2010 07:54:14 +1000 Subject: [publican-list] Should verbatim tags be translated? Message-ID: <1270850054.2641.2.camel@localhost> from https://bugzilla.redhat.com/show_bug.cgi?id=580360#6 FWIW I'm questioning the position that verbatim tags aren't translatable. You'd put the output of a command in a screen, lots of commands have localised output, surely if localised is available it should be translated? e.g. wget --help VS. LANG=ja_JP wget --help Maybe the position that verbatim tags aren't translatable is flat out wrong? Discuss! Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From bugzilla at redhat.com Sat Apr 10 01:57:39 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 9 Apr 2010 21:57:39 -0400 Subject: [publican-list] [Bug 578366] Quiet mode to disable ANSI codes in log files In-Reply-To: References: Message-ID: <201004100157.o3A1vdsV023713@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=578366 --- Comment #10 from Jeff Fearn 2010-04-09 21:57:33 EDT --- FYI I opened https://bugzilla.redhat.com/show_bug.cgi?id=581090 to address the naming issue in the next major version, since I think it's too disruptive for a minor version. -- 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 mospina at redhat.com Sun Apr 11 23:14:30 2010 From: mospina at redhat.com (Manuel Ospina) Date: Mon, 12 Apr 2010 09:14:30 +1000 Subject: [publican-list] Should verbatim tags be translated? In-Reply-To: <1270850054.2641.2.camel@localhost> References: <1270850054.2641.2.camel@localhost> Message-ID: <4BC257D6.1020706@redhat.com> +1 Localized output should be translated. Jeff Fearn wrote: > from https://bugzilla.redhat.com/show_bug.cgi?id=580360#6 > > FWIW I'm questioning the position that verbatim tags aren't > translatable. > > You'd put the output of a command in a screen, lots of commands have localised > output, surely if localised is available it should be translated? > > e.g. > > wget --help > > VS. > > LANG=ja_JP wget --help > > Maybe the position that verbatim tags aren't translatable is flat out wrong? > > Discuss! > > Cheers, Jeff. > > -- Manuel Ospina Supervisor, Localization Services Red Hat Asia-Pacific Phone: +61 7 3514 8112 Mobile: +61 413 228 601 From r.landmann at redhat.com Sun Apr 11 23:16:19 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 12 Apr 2010 09:16:19 +1000 Subject: [publican-list] Should verbatim tags be translated? In-Reply-To: <1270850054.2641.2.camel@localhost> References: <1270850054.2641.2.camel@localhost> Message-ID: <4BC25843.4050605@redhat.com> On 04/10/2010 07:54 AM, Jeff Fearn wrote: > Maybe the position that verbatim tags aren't translatable is flat out wrong? > I think the position is wrong, for the following reasons: 1. some applications might have localised output, as you've already demonstrated. This means that translatable content could easily appear in tags. It's also certainly possible that some command-line applications might have localised input as well, although I can't name any specific examples. Maybe someone else here can think of one? 2. examples of CLI usage are often (or even usually) presented in tags in documentation. These examples frequently include content, for example, path_to_iso_image. This kind of replaceable content is certainly translatable. 3. comments in code are translatable content; in fact, since the purpose of the comments is to explain what's happening in the code, then it's reasonable to translate those comments. Comments in a language that you can't read is no better than having no comments at all. Therefore, s could contain translatable content as well. That said, these are probably the exception rather than the norm. I wonder whether pre-filling some msgstrs while updating PO files makes sense? For example, if no existing msgstr exists for the msgid of verbatim content in the PO file, Publican could pre-fill the msgstr with the content of the mgsid and tag it "fuzzy"? Obviously, even assuming that's possible, we would need input from translators to see if that's desirable... Cheers Rudi From bugzilla at redhat.com Tue Apr 13 02:24:59 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 12 Apr 2010 22:24:59 -0400 Subject: [publican-list] [Bug 580774] Screenshots are rendered too small to be readable In-Reply-To: References: Message-ID: <201004130224.o3D2OxkH006083@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=580774 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(mhideo 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 Tue Apr 13 02:46:32 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Tue, 13 Apr 2010 12:46:32 +1000 Subject: [publican-list] Should verbatim tags be translated? In-Reply-To: <4BC25843.4050605@redhat.com> References: <1270850054.2641.2.camel@localhost> <4BC25843.4050605@redhat.com> Message-ID: <1271126792.2584.83.camel@localhost> On Mon, 2010-04-12 at 09:16 +1000, Ruediger Landmann wrote: > That said, these are probably the exception rather than the norm. I > wonder whether pre-filling some msgstrs while updating PO files makes > sense? For example, if no existing msgstr exists for the msgid of > verbatim content in the PO file, Publican could pre-fill the msgstr with > the content of the mgsid and tag it "fuzzy"? Obviously, even assuming > that's possible, we would need input from translators to see if that's > desirable... I don't see any point in pre-filling in this way. The translators will see it as untranslated and, AIUI, all the GUI tools have options to copy the msgid to the msgstr. 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 mhideo at redhat.com Tue Apr 13 03:14:52 2010 From: mhideo at redhat.com (Mike Hideo) Date: Tue, 13 Apr 2010 13:14:52 +1000 Subject: [publican-list] Should verbatim tags be translated? In-Reply-To: <1271126792.2584.83.camel@localhost> References: <1270850054.2641.2.camel@localhost> <4BC25843.4050605@redhat.com> <1271126792.2584.83.camel@localhost> Message-ID: <4BC3E1AC.4090204@redhat.com> On 04/13/2010 12:46 PM, Jeff Fearn wrote: > On Mon, 2010-04-12 at 09:16 +1000, Ruediger Landmann wrote: >> That said, these are probably the exception rather than the norm. I >> wonder whether pre-filling some msgstrs while updating PO files makes >> sense? For example, if no existing msgstr exists for the msgid of >> verbatim content in the PO file, Publican could pre-fill the msgstr with >> the content of the mgsid and tag it "fuzzy"? Obviously, even assuming >> that's possible, we would need input from translators to see if that's >> desirable... > > I don't see any point in pre-filling in this way. The translators will > see it as untranslated and, AIUI, all the GUI tools have options to copy > the msgid to the msgstr. +1, I agree. The translator's should do this at their own discretion. - Mike From raphael at ouaza.com Wed Apr 14 14:10:29 2010 From: raphael at ouaza.com (Raphael Hertzog) Date: Wed, 14 Apr 2010 16:10:29 +0200 Subject: [publican-list] Quick intro, small patch, and one question Message-ID: <20100414141029.GA29687@rivendell> Hi, I discovered publican recently (via LWN.net) and have started using it for my book (http://ouaza.com/livre/admin-debian/) that I plan to translate to English. In the process I find out bugs and filled them on the bugzilla. Since I'm also a Debian developer and since the publican package was out of date in sid, I started co-maintaining the package and just uploaded 1.6.2 to Debian unstable. In the process, one of our QA tool spotted a typo in the POD documentation, a small patch is attached, please apply it. http://packages.qa.debian.org/p/publican.html And to finish this mail, is it possible for brands to further override/extend the XSL ? I have many (i.e. without content) that I would like to see formatted as block (with a small sign in front) instead of inline and wondered if such customization could be made with a custom brand. 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/ -------------- next part -------------- Description: Fix a typo in the POD documentation Author: Rapha??l Hertzog Forwarded: no --- a/lib/Publican.pm +++ b/lib/Publican.pm @@ -681,7 +681,7 @@ sub help_config { =head2 dir_list -list all the files in a director, and it's subdirectories, matching the suplied regex. +list all the files in a directory, and its subdirectories, matching the supplied regex. =cut From jfearn at redhat.com Wed Apr 14 23:52:13 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Thu, 15 Apr 2010 09:52:13 +1000 Subject: [publican-list] Quick intro, small patch, and one question In-Reply-To: <20100414141029.GA29687@rivendell> References: <20100414141029.GA29687@rivendell> Message-ID: <4BC6552D.5070809@redhat.com> Hi Raphael, welcome :) Raphael Hertzog wrote: > Hi, > > I discovered publican recently (via LWN.net) and have started using it > for my book (http://ouaza.com/livre/admin-debian/) that I plan to translate > to English. In the process I find out bugs and filled them on the bugzilla. > > Since I'm also a Debian developer and since the publican package was out > of date in sid, I started co-maintaining the package and just uploaded > 1.6.2 to Debian unstable. In the process, one of our QA tool spotted a > typo in the POD documentation, a small patch is attached, please apply it. Thanks, applied. > http://packages.qa.debian.org/p/publican.html > > And to finish this mail, is it possible for brands to further > override/extend the XSL ? > > I have many (i.e. without content) that I would like to > see formatted as block (with a small sign in front) instead of inline and > wondered if such customization could be made with a custom brand. Brands can override the XSL in anyway. The easiest way is to copy the original template from the Publican or DocBook XSL in to you brands html/pdf/html-single xsl file and then change it to match your requirements. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jaredsmith at jaredsmith.net Thu Apr 15 13:00:50 2010 From: jaredsmith at jaredsmith.net (Jared Smith) Date: Thu, 15 Apr 2010 09:00:50 -0400 Subject: [publican-list] Quick intro, small patch, and one question In-Reply-To: <20100414141029.GA29687@rivendell> References: <20100414141029.GA29687@rivendell> Message-ID: <1271336450.3198.26.camel@localhost.localdomain> On Wed, 2010-04-14 at 16:10 +0200, Raphael Hertzog wrote: > Since I'm also a Debian developer and since the publican package was out > of date in sid, I started co-maintaining the package and just uploaded > 1.6.2 to Debian unstable. Thanks you for doing this! I'm normally not much of a Debian user, but for one particular work project I've been fighting getting Publican to pass all its tests when compiling on Debian, and was about to throw my hands in the air when your post came through. Thanks for saving me from my self-induced headache! -- Jared Smith From hertzog at debian.org Thu Apr 15 13:58:08 2010 From: hertzog at debian.org (Raphael Hertzog) Date: Thu, 15 Apr 2010 15:58:08 +0200 Subject: [publican-list] Quick intro, small patch, and one question In-Reply-To: <4BC6552D.5070809@redhat.com> References: <20100414141029.GA29687@rivendell> <4BC6552D.5070809@redhat.com> Message-ID: <20100415135808.GA32352@rivendell> Hi, On Thu, 15 Apr 2010, Jeffrey Fearn wrote: > >Since I'm also a Debian developer and since the publican package was out > >of date in sid, I started co-maintaining the package and just uploaded > >1.6.2 to Debian unstable. In the process, one of our QA tool spotted a > >typo in the POD documentation, a small patch is attached, please apply it. > > Thanks, applied. Not completety, you hand-applied it and missed that the patch was fixing 3 typos on the same line (the one spotted by lintian was s/suplied/supplied/ and I also fixed s/it's/its/). > >I have many (i.e. without content) that I would like to > >see formatted as block (with a small sign in front) instead of inline and > >wondered if such customization could be made with a custom brand. > > Brands can override the XSL in anyway. The easiest way is to copy > the original template from the Publican or DocBook XSL in to you > brands html/pdf/html-single xsl file and then change it to match > your requirements. Glad to hear that, I will look into it, thanks. 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 jfearn at redhat.com Thu Apr 15 23:25:28 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 16 Apr 2010 09:25:28 +1000 Subject: [publican-list] Quick intro, small patch, and one question In-Reply-To: <20100415135808.GA32352@rivendell> References: <20100414141029.GA29687@rivendell> <4BC6552D.5070809@redhat.com> <20100415135808.GA32352@rivendell> Message-ID: <4BC7A068.2090101@redhat.com> Raphael Hertzog wrote: > Hi, > > On Thu, 15 Apr 2010, Jeffrey Fearn wrote: >>> Since I'm also a Debian developer and since the publican package was out >>> of date in sid, I started co-maintaining the package and just uploaded >>> 1.6.2 to Debian unstable. In the process, one of our QA tool spotted a >>> typo in the POD documentation, a small patch is attached, please apply it. >> Thanks, applied. > > Not completety, you hand-applied it and missed that the patch was fixing 3 > typos on the same line (the one spotted by lintian was s/suplied/supplied/ > and I also fixed s/it's/its/). OK, so I ran podspell over all the pm files and the publican command and fixed all the spelling errors ... there were quite a few! Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From bugzilla at redhat.com Tue Apr 27 06:16:45 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 27 Apr 2010 02:16:45 -0400 Subject: [publican-list] [Bug 585115] Internal PDF table borders not the same weight as external borders. In-Reply-To: References: Message-ID: <201004270616.o3R6Gjpw030393@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=585115 Jared Morgan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |publican-list at redhat.com Summary|Internal PDF table borders |Internal PDF table borders |not the same weight as |not the same weight as |external borders. HTML |external borders. |internal borders missing. | -- 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 Apr 27 06:18:56 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 27 Apr 2010 02:18:56 -0400 Subject: [publican-list] [Bug 585115] Internal PDF table borders not the same weight as external borders. In-Reply-To: References: Message-ID: <201004270618.o3R6Iu7H029732@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=585115 --- Comment #6 from Ruediger Landmann 2010-04-27 02:18:54 EDT --- (collision) The output in both formats seems to vary considerably depending on the web browser and PDF viewer in question. HTML -- internal borders are visible in Firefox and Dillo, but are missing in Chromium, Konqueror, and Internet Explorer 6. PDF -- I can't see a difference in weight between internal and external borders in Okular, XPDF, or Adobe Reader unless I zoom in greater than about 300%; while in Evince I see the same, large difference in weights as in the screenshot that Jared attached. -- 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 Apr 27 06:23:35 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 27 Apr 2010 02:23:35 -0400 Subject: [publican-list] [Bug 585115] Internal PDF table borders not the same weight as external borders. In-Reply-To: References: Message-ID: <201004270623.o3R6NZjh030354@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=585115 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_DEV Fixed In Version| |1.6.3 --- Comment #7 from Jeff Fearn 2010-04-27 02:23:30 EDT --- Added a tweak to the CSS for webkit browsers, upped PDF cell border width to match table border. -- 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 Apr 27 06:42:44 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 27 Apr 2010 02:42:44 -0400 Subject: [publican-list] [Bug 585115] Internal PDF table borders not the same weight as external borders. In-Reply-To: References: Message-ID: <201004270642.o3R6gimw001041@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=585115 Darrin Mison changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmison at redhat.com --- Comment #8 from Darrin Mison 2010-04-27 02:42:40 EDT --- Just confirming that the reported behaviour of no internal borders also manifests on IE8 on Win7 and Safari 4.0.5 on OSX 10.6.3 The internal borders are visible in Firefox 3.5.8 on OSX My 2 cents: I'd prefer the internal borders be very slightly fainter than the external ones. -- 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 ersin.er at gmail.com Tue Apr 27 11:15:12 2010 From: ersin.er at gmail.com (Ersin Er) Date: Tue, 27 Apr 2010 14:15:12 +0300 Subject: [publican-list] New language support Message-ID: Hi, Can you please explain the steps in order to add support for a new language in Publican? (I particularly want to have support for Turkish, tr_TR.) Thanks. -- Ersin Er -------------- next part -------------- An HTML attachment was scrubbed... URL: From r.landmann at redhat.com Tue Apr 27 23:54:41 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 28 Apr 2010 09:54:41 +1000 Subject: [publican-list] New language support In-Reply-To: References: Message-ID: <4BD77941.9030306@redhat.com> On 04/27/2010 09:15 PM, Ersin Er wrote: > Can you please explain the steps in order to add support for a new language > in Publican? (I particularly want to have support for Turkish, tr_TR.) > Hi Ersin Publican already has basic support for any language for which a DocBook locale stylesheet exists, including Turkish.[0] Therefore, if you have a document in English, you can run: publican update_pot publican update_po --langs=tr-TR to create a tr-TR folder that contains PO files ready for translation, or you can create a new document with (for example): publican create --name=Name_of_Document --lang=tr-TR to create a new book where the XML files will be authored in Turkish and then perhaps translated to other languages later. In either case, building the book will already include Turkish translations for common headings like "Chapter", "Appendix", "Legal Notice" and similar. However, by default, it will include a "Document Conventions" section in the Preface in English. We'd love to add support so that the default preface displays in Turkish for documents in Turkish. To do that, we need the two PO files attached here translated. If you could please help us with that and return them to me by email, it would be very much appreciated![1] If you haven't worked with PO files before, please contact me off-list and I can help you get started. Cheers Rudi [0] the locale for Turkish is about 85% complete and needs only about another 30 words or so to finish it; please let me know if you'd like to help with this. [1] members of the Fedora Localization Project can contribute translations through Fedora's Transifex interface here: https://translate.fedoraproject.org/projects/p/publican/c/common_content/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Conventions.po Type: text/x-gettext-translation Size: 9098 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Feedback.po Type: text/x-gettext-translation Size: 536 bytes Desc: not available URL: From bugzilla at redhat.com Fri Apr 30 02:41:36 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 29 Apr 2010 22:41:36 -0400 Subject: [publican-list] [Bug 587489] Add new build target for Eclipse In-Reply-To: References: Message-ID: <201004300241.o3U2faRo031033@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=587489 Isaac Rooskov changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mhideo at redhat.com |jfearn 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 Fri Apr 30 02:39:24 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 29 Apr 2010 22:39:24 -0400 Subject: [publican-list] [Bug 587489] New: Add new build target for Eclipse Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Add new build target for Eclipse https://bugzilla.redhat.com/show_bug.cgi?id=587489 Summary: Add new build target for Eclipse Product: Red Hat Enterprise Linux 5 Version: 5.7 Platform: All OS/Version: Linux Status: NEW Severity: urgent Priority: low Component: publican AssignedTo: mhideo at redhat.com ReportedBy: irooskov at redhat.com QAContact: desktop-bugs at redhat.com CC: publican-list at redhat.com Classification: Red Hat Target Release: --- Description of problem: Currently in the JBoss Developer Studio project, whenever we want to convert documentation into "Eclipse Help" formatted content we specify an "eclipse" format plugin in the Maven build phase. Since it is our desire (from a content services standpoint) to build everything with Publican it would be advantagous to our cause to have this ability in Publican as well. Version-Release number of selected component (if applicable): N/A How reproducible: N/A Steps to Reproduce: 1. 2. 3. N/A Actual results: Doesn't have a build target that generates a plug-in for Eclipse to be intergrated into the Eclipse help system. Expected results: Would have a build target that generates a plug-in for Eclipse to be intergrated into the Eclipse help system. Additional info: contact Isaac Rooskov: irooskov at redhat.com or contact Ben Clare: bclare 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 Fri Apr 30 03:19:41 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 29 Apr 2010 23:19:41 -0400 Subject: [publican-list] [Bug 587489] Add new build target for Eclipse In-Reply-To: References: Message-ID: <201004300319.o3U3Jf8H017201@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=587489 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jfearn at redhat.com |mhideo 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.