From bugzilla at redhat.com Thu May 7 02:28:55 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 07 May 2015 02:28:55 +0000 Subject: [publican-list] [Bug 1219316] New: Mark source language files for translation Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1219316 Bug ID: 1219316 Summary: Mark source language files for translation Product: Fedora Version: 21 Component: publican Severity: medium Priority: low Assignee: r.landmann at redhat.com Reporter: lbailey at redhat.com QA Contact: extras-qa at fedoraproject.org CC: jfearn at redhat.com, jwulf at redhat.com, lcarlon at redhat.com, me at petetravis.com, mhideo at redhat.com, mmcallis at redhat.com, mospina at redhat.com, publican-list at redhat.com, r.landmann at redhat.com Depends On: 545698 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=545698 [Bug 545698] Publican creates unnecessary POT files -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xHNmAQCdEk&a=cc_unsubscribe From bugzilla at redhat.com Thu May 7 02:28:55 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 07 May 2015 02:28:55 +0000 Subject: [publican-list] [Bug 545698] Publican creates unnecessary POT files In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=545698 Laura Bailey changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1219316 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219316 [Bug 1219316] Mark source language files for translation -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=zFKfC8Y4cy&a=cc_unsubscribe From bugzilla at redhat.com Thu May 7 02:44:29 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 07 May 2015 02:44:29 +0000 Subject: [publican-list] [Bug 1219316] Mark source language files for translation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1219316 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed| |2015-05-06 22:44:29 --- Comment #1 from Jeff Fearn --- This is why trans_drop exists, it should be a simple matter to style it's use for individual teams work flows. $ publican trans_drop --help trans_drop Snapshot the source language for use in translation. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fVty3jeN3M&a=cc_unsubscribe From bugzilla at redhat.com Thu May 7 03:02:11 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 07 May 2015 03:02:11 +0000 Subject: [publican-list] [Bug 1219316] Mark source language files for translation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1219316 David O'Brien changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daobrien at redhat.com --- Comment #2 from David O'Brien --- There's also info here about trans_drop: https://jfearn.fedorapeople.org/en-US/Publican/4.0/html-single/Users_Guide/index.html#sect-Publican-Users_Guide-Preparing_a_document_for_translation -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9ylKsxdFYf&a=cc_unsubscribe From jfearn at redhat.com Thu May 7 03:02:41 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 07 May 2015 13:02:41 +1000 Subject: [publican-list] Publican 4.3.0 released Message-ID: <554AD5D1.7020306@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Publican 4.3.0 has been released. Files available at https://fedorahosted.org/releases/p/u/publican/ Here is the change log: 4.3.0 Tue May 5 2015 - - Fix web site templates to be more flexable. - - Tweak default website styles. - - Remove all FOP customisations. BZ #1168765 - - Use FontAwesome for aswesomeness. - - Switch DocBook-5 HTML to highlight.js. - - Change splash page group publish directory structure so it can be used directly. BZ #1186990 - - Fix duplicate link in Website docs. BZ #1188384 - - Fix PDF builds ignoring overrides.css and lang.css. BZ #1165005 - - Pulled in new/updated translations. BZ #1169605 - - Removed duplicate IDs from PUG. BZ #1197523 - - Removed the titlepage.xsl import from html-single due to breaking the xsl precedence. BZ #1187728 - - Fix Publican doesn't fallback to base_brand xsl files. BZ #1185127 - - Fix
elements being stripped in drupal-book builds. BZ #1158747 - - Fix malformed HTML/Drupal XML Feed for DocBook 5 content. BZ #1158740 - - Fix incorrect missing image warnings for drupal builds. BZ #1158725 - - Fix articles not building when using the drupal-book format. BZ #1164640 - - Fix initial title page content being skipped when a user defines a custom bookinfo id. BZ #1165482 - - Fix invalid XML being generated for drupal-book, when titles contain reserved chars. BZ #1165438 - - Changed the drupal feed field to use the url value instead of the title. BZ #1165724 - - Fix publican.cfg values are used in the feed page tag. BZ #1172402 - - Fix drupal content is dropped, if the element that is chunked has no id. BZ #1173421 - - Adjusted the XML output so anchors to something in the same page doesn't include the page url. - - Make legalnotice chunk in a similar way as chapters for drupal builds, so it's included in the feed. - - Enable section.label.includes.component.label for common-db5. BZ #1205952 - - Fix formalpara ids being dropped for DocBook 4.5. BZ #1209344 - - Add --no_clean option to allow custom entity files. BZ #1208069 Cheers, Jeff. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJVStXRAAoJELs3R4zxGZvKQ7YIAKIxsQCsL2b5/EhaBo5N1dHa m3+TvANkLKQY7F2LgmwnoRBpB0b1kxZLCUpRA3ilBq3Vym3e/icfrLzEDu68Nt02 RHxSwJpSq0RwgfLI5vuYFI2fIgtUqsF6ZIDBXgWvna2gskq5LAztP5pqGILjpA1T EngpRmeprWmhVNKQncLo9Iqvw8mWOJsOwLFDt8nwCWwqc0jJlUZiDcgm/CBZSx7k jAc1luDIeaiVwG1vrv4bGOP0cIn4Xst+4JqwUHNrC5e72ZrnEawxNqR1BZhc1RRt ipuz4laxQ4CZSnfOiApuVPAzZ+tAIEZhXKxxIzwyHSvNcm6QWXEwlaA4s8OEzNU= =rAfO -----END PGP SIGNATURE----- From herrold at owlriver.com Thu May 7 18:12:33 2015 From: herrold at owlriver.com (R P Herrold) Date: Thu, 7 May 2015 14:12:33 -0400 (EDT) Subject: [publican-list] looking forward; was: Publican 4.3.0 released In-Reply-To: <554AD5D1.7020306@redhat.com> References: <554AD5D1.7020306@redhat.com> Message-ID: <alpine.LRH.2.03.1505071353400.31785@bjyevire.pbz> On Thu, 7 May 2015, Jeff Fearn wrote: congratulations In looking through the release notice, it seems development matters are largely driven off of bugzilla entries. I don't know that these 'nits' have been expressly filed, nor indeed if the RHEL documentation is produced via Publican, but here goes: Problem 1: Kerning causes 'scrapes' off of a PDF to have embedded white space -- an example is as follows: http://gallery.herrold.com/stuff/source-kerning.png and http://gallery.herrold.com/stuff/result-kerning.png Problem 2: Page numbers are not 'hot links' in the PDF 'table of contents' rendering (compare contra PDF's generated in a some LaTeX markup / DVi / PS / PDF chains) -- the 'circled' page number in an index, when clicked, does nothing http://gallery.herrold.com/stuff/dead-page-numbers.png I built a quick example of a large set of documentation (in part machine generated) -- see pg 4 ff of the PDF http://gallery.herrold.com/stuff/commands.pdf Question: Are these 'interesting' bugs that I should file, and would a fix in Publican flow into later versions of RHT documentation? Thanks - Russ herrold From Sascha.Manns at bdvb.de Thu May 7 20:27:25 2015 From: Sascha.Manns at bdvb.de (Sascha Manns) Date: Thu, 07 May 2015 22:27:25 +0200 Subject: [publican-list] Announcement: PublicanCreators Message-ID: <554BCAAD.7020808@bdvb.de> Hello list, i'm pleased to announce a small tool which uses publican. The Story around is very simple. I'm using publican the whole day to produce new documentations in my company. So i wrote PublicanCreators, a RubyGem which simplifies the work a little bit. It has two keys: 1.) a configuration file. There you can handle different brands. Like one for work, one for private and one for other things. In my case i'm using a different brand for my homework for my distance learning school. The directory for each case can be customized in the config. 2.) a yad based GUI which asks what you want to create: A article or a book, for work or private and if you want to write homeworks. I also have a different category "Reports". That are article based documentations which have a different structure (smaller and with a legal notice on another place). It grows with my daily work, but maybe it is useful for you. After running the setup it links the "binary" to /usr/bin and it places a .desktop file in .local/share/applications, so you can run the tool everywhere. PublicanCreators replaces the default entries in Author_Group and Revision_History with your choosen Name in the config. So you can start directly. While running PublicanCreators it produces a build.sh in your $tiltle/$lang/ directory. So you can run the script like build.sh -pdf to produce a pdf output. It also starts a PDF-Editor for checking the result. I also implemented some stuff for people who having XFC from the XMLmind producers to create a docx, odt or other output. But just now i have seen it's actually in german. Sorry i will fix it at weekend :-) Actually the documentation is also that one in Rubydocs and the comments in the configuration file. It's planned to write a whole documentation on the weekend (sure with publican ;-)) Finally i would like to say that i'm no programmer, just a documentation guy. So the program works, but maybe i can do things better. So don't hesitate to file bugreports and feature requests on: http://saigkill.ddns.net:8112/dashboard. Codereviews can be done there: http://saigkill.ddns.net:8080/publicancreators/view. And the Startpoint for PublicanCreators is on: https://github.com/saigkill/PublicanCreators. Pull Requests are also welcome :-) So guys. Good night. Sascha -- Yours sincerly Sascha Manns (bdvb) Maifeldstra?e 10 56727 Mayen Phone: +49-1573-9242730 Email: Sascha.Manns at bdvb.de Web: http://saigkill.ddns.net/wordpress Jabber: saigkill at jabber.org From jfearn at redhat.com Thu May 7 22:07:46 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Fri, 08 May 2015 08:07:46 +1000 Subject: [publican-list] looking forward; was: Publican 4.3.0 released In-Reply-To: <alpine.LRH.2.03.1505071353400.31785@bjyevire.pbz> References: <554AD5D1.7020306@redhat.com> <alpine.LRH.2.03.1505071353400.31785@bjyevire.pbz> Message-ID: <554BE232.2050207@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day, On 05/08/2015 04:12 AM, R P Herrold wrote: > On Thu, 7 May 2015, Jeff Fearn wrote: > > congratulations > > In looking through the release notice, it seems development > matters are largely driven off of bugzilla entries. I don't > know that these 'nits' have been expressly filed, nor indeed > if the RHEL documentation is produced via Publican, but here > goes: > > Problem 1: > Kerning causes 'scrapes' off of a PDF to have embedded white > space -- an example is as follows: > > http://gallery.herrold.com/stuff/source-kerning.png > and > http://gallery.herrold.com/stuff/result-kerning.png > This seems to be dependant on the combination of PDF generator and font being used. See https://bugzilla.redhat.com/show_bug.cgi?id=1141312 for how it occurs in wkhtmltopdf. There are some upstream bugs related to kerning issues that have been addressed by banging on the font configuration. e.g. see https://github.com/wkhtmltopdf/wkhtmltopdf/issues/45#issuecomment-34543222 for an example of how tweaking the font config helped on Debian. > Problem 2: > > Page numbers are not 'hot links' in the PDF 'table of > contents' rendering (compare contra PDF's generated in a some > LaTeX markup / DVi / PS / PDF chains) -- the 'circled' page > number in an index, when clicked, does nothing I've not looked at these tools chains in quite some time and Publican has no direct support for them. If you can provide your full work flow I can take a poke a round and see if it's an easy fix. I'm assuming there is an upstream template somewhere that needs tweaking. > http://gallery.herrold.com/stuff/dead-page-numbers.png > > I built a quick example of a large set of documentation (in > part machine generated) -- see pg 4 ff of the PDF > > http://gallery.herrold.com/stuff/commands.pdf > > > Question: > > Are these 'interesting' bugs that I should file, Yeah, while I wont say we are "happy" to get bugs we do encourage people to open them if they are getting annoyed by something :) > and would a > fix in Publican flow into later versions of RHT documentation? It depends on the change, Red Hat have a brand that customises a lot of stuff so it's quite possible some changes will never get to their output, but of course a lot do. Cheers, Jeff. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJVS+IyAAoJELs3R4zxGZvKQ+4H/jU7sKygGdP8wuDWMF7YmQA1 cX2S2h2cTUI9RXz1ajyWLzhsXVF3F0ctlgxJHuJKbfUy+Av5O4qqn+c6nIKkvxc3 MkBdVCKYkfgTAu8MOnSrLUbThDbZxjhxhbC1+FjG0fNo1FJO7H4FyUZbv1gl2JTs 27VnT5qJiu2nDoxrh4Vz9QZkvCqhGxaZqbeGOhUhMFvWNXOVtAPYpsoJYbaGq0lX b1lnBqyDZHJQIOqUrFMMZzhawK/VUb5m5bFnsAE5P+LnCIsc1Veakqui5TRPeqXd 2Jpz6uPbQM9dLESG4/cSTOyCoLaMitDBO7KMNYH6vAf+rM4J4y16V+Oi/ih58/4= =oEIr -----END PGP SIGNATURE----- From haug.buerger at zalando.de Mon May 18 11:28:28 2015 From: haug.buerger at zalando.de (Haug =?ISO-8859-1?Q?B=FCrger?=) Date: Mon, 18 May 2015 13:28:28 +0200 Subject: [publican-list] Entities Message-ID: <1431948508.2890.8.camel@ZALANDO-4732.corp.ad.zalando.net> I wonder if it is possible to load the entities from different locations. We want to create several books using the same entities. But also use book specific entities. I wonder if this is possible because everything I tried failed with errors. For example the following fails with: FATAL ERROR: parser:27 in Book_Info.xml on line 9: Entity 'PROJECT_NAME' not defined at /usr/bin/publican line 1223. Where PROJECT_NAME is defined in global.ent. Any ideas? <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY PRODUCT "Documentation"> <!ENTITY BOOKID "MyBook"> <!ENTITY YEAR "2015"> <!ENTITY HOLDER "| You need to change the HOLDER entity in the en-US/MyBook.ent file |"> <!ENTITY % GLOBAL_ENTITIES SYSTEM "global.ent"> %GLOBAL_ENTITIES; ]> global.ent: <!ENTITY PROJECT_NAME "MyProjectName"> From jfearn at redhat.com Mon May 18 22:03:33 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Tue, 19 May 2015 08:03:33 +1000 Subject: [publican-list] Entities In-Reply-To: <1431948508.2890.8.camel@ZALANDO-4732.corp.ad.zalando.net> References: <1431948508.2890.8.camel@ZALANDO-4732.corp.ad.zalando.net> Message-ID: <555A61B5.8010902@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/18/2015 09:28 PM, Haug B?rger wrote: > I wonder if it is possible to load the entities from different > locations. We want to create several books using the same entities. But > also use book specific entities. I wonder if this is possible because > everything I tried failed with errors. > > For example the following fails with: > FATAL ERROR: parser:27 in Book_Info.xml on line 9: Entity 'PROJECT_NAME' > not defined > at /usr/bin/publican line 1223. > > Where PROJECT_NAME is defined in global.ent. > > Any ideas? https://bugzilla.redhat.com/show_bug.cgi?id=1208069 You need to upgrade to 4.3.0, ensure all your source XML is fully legit , and use --no-clean option. Cheers, Jeff. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJVWmG1AAoJELs3R4zxGZvKy/AIALICCUCItp1FMcvXZffFjxMd GsoW+1himVTjYyHxH6YA5kaGckfKbb5EAt2RirmD+4N/3zz/2r8FlRkkazRfJGFD +qV32dCGHGGN5efMClL0kMZYYAOfL5096K1oL71hETtHihODTa8YgENkI1SeXKG1 qd9j5D6GuB9Z18XF93t69ZedpBVyrmHEnWJFEsj0YodZpCRW3akmpYY7gQAeJSyX c8WVh8Zvj7M7hJiJKY5b+qhb/QHBc634MY1ze75tfln8oVY5TwHRUdrP8n+46Drk 9cAlqay3NIoMxswtq/8hkgui9n1llLiEI4ZqiImntPUObZ+yfVWtV/rSDv2M2r0= =bw9z -----END PGP SIGNATURE----- From Sascha.Manns at bdvb.de Wed May 20 19:09:22 2015 From: Sascha.Manns at bdvb.de (Sascha Manns) Date: Wed, 20 May 2015 21:09:22 +0200 Subject: [publican-list] Announcement: PublicanCreators 0.4.4.0 Message-ID: <555CDBE2.2090509@bdvb.de> Hello List, i'm pleased to announce version 0.4.4.0 of PublicanCreators. Now a full documentation is available. The newest feature is that RevisionCreator adds a revision with publican, and sets the productversion and edition in Article_Info.xml or Book_Info.xml. If publican now uses <personname> by adding revisions in DB5 projects it would be great :-) -- Yours sincerly Sascha Manns (bdvb) Maifeldstra?e 10 56727 Mayen Phone: +49-1573-9242730 Email: Sascha.Manns at bdvb.de Web: http://saigkill.ddns.net/wordpress Jabber: saigkill at jabber.org From Sascha.Manns at bdvb.de Sun May 24 20:25:02 2015 From: Sascha.Manns at bdvb.de (Sascha Manns) Date: Sun, 24 May 2015 22:25:02 +0200 Subject: [publican-list] PublicanCreators 0.4.6 released Message-ID: <5562339E.8030608@bdvb.de> Hello List, i'm pleased to announce PublicanCreators 0.4.6. What is PublicanCreators? PublicanCreators are a small tool for daily DocBook writers who are using the Redhat publican tool [fedorahosted.org/publican <https://fedorahosted.org/publican>/]. PublicanCreators asks after launching which title, type and environment should be used. Then it starts publican with that settings and works then with the produced files. It will work inside the Article_Info.xml, Book_Info.xml, TITLE.ent, Author_Group.xml and Revision_History.xml and will replace the default values with your name, your company, your company_divison and your private or your business email address, depending on your chosen environment. Also you can set inside your config file that you want to remove the Title Logo or the Legal Notice. As a feature it ships a build script for each project. Project home: https://github.com/saigkill/PublicanCreators Code documentation: http://www.rubydoc.info/gems/PublicanCreators/0.4.6.0 User documentation (en): http://saigkill.github.io/docs/publicancreators/en-US/html User documentation (de): http://saigkill.github.io/docs/publicancreators/de-DE/html Bug tracker: http://saigkill.ddns.net:8112/dashboard Review code: http://saigkill.ddns.net:8080/publicancreators/view -- Yours sincerly Sascha Manns (bdvb) Maifeldstra?e 10 56727 Mayen Phone: +49-1573-9242730 Email: Sascha.Manns at bdvb.de Web: http://saigkill.ddns.net/wordpress Jabber: saigkill at jabber.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/publican-list/attachments/20150524/2e00cd3a/attachment.htm>