From rajsekhar.kunnampally at citrix.com Thu Jul 2 19:10:47 2015 From: rajsekhar.kunnampally at citrix.com (Rajsekhar Kunnampally) Date: Thu, 2 Jul 2015 19:10:47 +0000 Subject: [publican-list] Error while creating PDF - Need help Message-ID: <02C41964046D5942A6DE3EAAB2063A5D01423271@SINPEX01CL02.citrite.net> Hi, All, I need an urgent help from you. I get the following error message when I run the publican build --config=publican-gsg.cfg --formats=pdf --langs=en-US command to generate the PDF output of one of my guides: Beginning work on en-US DTD Validation OK Starting pdf Using XML::LibXSLT on C:/Program Files (x86)/Publican/xsl/pdf.xsl No such file or directoryI/O warning : failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/fo/footnote.xsl" compilation error: file file:///C:/Program%20Files%20(x86)/Publican/xsl/pdf.xsl element include xsl:include : unable to load http://docbook.sourceforge.net/release/xsl/current/fo/footnote.xsl at Publican/Builder.pm line 1290 This command was working fine a couple of hours back. Can you please help me resolve this problem? Thanks in advance for your help. Thanks, Rajsekhar -------------- next part -------------- An HTML attachment was scrubbed... URL: From swadeley at redhat.com Thu Jul 2 19:44:12 2015 From: swadeley at redhat.com (Stephen Wadeley) Date: Thu, 2 Jul 2015 21:44:12 +0200 Subject: [publican-list] Error while creating PDF - Need help In-Reply-To: <02C41964046D5942A6DE3EAAB2063A5D01423271@SINPEX01CL02.citrite.net> References: <02C41964046D5942A6DE3EAAB2063A5D01423271@SINPEX01CL02.citrite.net> Message-ID: <5595948C.6030300@redhat.com> On 07/02/2015 09:10 PM, Rajsekhar Kunnampally wrote: > Hi, All, > > I need an urgent help from you. > > I get the following error message when I run the *publican build > --config=publican-gsg.cfg --formats=pdf --langs=en-US* command to > generate the PDF output of one of my guides: > > Beginning work on en-US > > DTD Validation OK > > Starting pdf > > Using XML::LibXSLT on C:/Program Files (x86)/Publican/xsl/pdf.xsl > > No such file or directoryI/O warning : failed to load external entity > "http://docbook.sourceforge.net/release/xsl/current/fo/footnote.xsl" > > compilation error: file > file:///C:/Program%20Files%20(x86)/Publican/xsl/pdf.xsl element include > > xsl:include : unable to load > http://docbook.sourceforge.net/release/xsl/current/fo/footnote.xsl > > at Publican/Builder.pm line 1290 > > This command was working fine a couple of hours back. Can you please > help me resolve this problem? > > Thanks in advance for your help. > > Thanks, > > Rajsekhar > > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > Could it be a temporary network problem between you and the sourceforge server? I can open that page in my browser OK. Can you view this page: http://docbook.sourceforge.net/release/xsl/current/fo/footnote.xsl From rf at q-leap.de Thu Jul 9 15:07:48 2015 From: rf at q-leap.de (Roland Fehrenbacher) Date: Thu, 9 Jul 2015 17:07:48 +0200 Subject: [publican-list] xlink:show Message-ID: <21918.36420.232508.313451@gargle.gargle.HOWL> Hi, publican 4.3 with docbook 5 doen't seem to support xlink:show. How is one supposed to create a link that opens a new tab/window in the browser? Thanks, Roland ------- http://www.q-leap.com / http://qlustar.com --- HPC / Storage / Cloud Linux Cluster OS --- From jfearn at redhat.com Fri Jul 10 00:31:32 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Fri, 10 Jul 2015 10:31:32 +1000 Subject: [publican-list] xlink:show In-Reply-To: <21918.36420.232508.313451@gargle.gargle.HOWL> References: <21918.36420.232508.313451@gargle.gargle.HOWL> Message-ID: <559F1264.1060605@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/10/2015 01:07 AM, Roland Fehrenbacher wrote: > Hi, > > publican 4.3 with docbook 5 doen't seem to support xlink:show. How is one supposed to create a link that opens a new tab/window in the browser? This wasn't deliberately broken, but since this behavior is a pet hate of mine it's never going to be supported in Publican. If I want the link to open in another window or tab *I* will decide to do that and click the appropriate mouse button. Cheers, Jeff. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVnxJkAAoJELs3R4zxGZvKcxMIAIlC9X/6H+HbVYT2KpFVZ1s3 PymFgppGT+/mska+b9c0VDQzDv/jPTdtsWP7AKko5qU48ZMSJtboc+COet/g8QsR qoUMAa5XPwMX6BR/4PYfOKIJ3aAyucrMnWvG7VEgwkiX5eueGDL46JgeC+T1sQkx 0SsMNDxx/f9cputAF1vdvGDdT1zKmwlY33LfmUK22QRWBQFqPnzWAi2ffiyaB7GR tEe03+PuLqAdldmuWpAYcNZoIgcz9dansxR6muxO69XRvjd8Z/btaVyF1sb9DpZ8 UGpN5zsPP0/7GR3Xfkt41iRsc2OLa13Mwp7eUP5s/gfzwrwExXDKEnvZjWt/C4c= =x2nm -----END PGP SIGNATURE----- From haug.buerger at zalando.de Mon Jul 13 14:58:11 2015 From: haug.buerger at zalando.de (Haug =?ISO-8859-1?Q?B=FCrger?=) Date: Mon, 13 Jul 2015 16:58:11 +0200 Subject: [publican-list] Sizing of images Message-ID: <1436799491.7154.13.camel@ZALANDO-4732.corp.ad.zalando.net> I tried to size images but it doesn't seem to work with HTML. PDF seems to work. Any hints how to size SVG images for HTML? ...
My title
... From lists at murrell.ca Sat Jul 18 21:23:44 2015 From: lists at murrell.ca (Alan Murrell) Date: Sat, 18 Jul 2015 14:23:44 -0700 Subject: [publican-list] Create Brand: Cannot change header colours Message-ID: <55AAC3E0.5000204@murrell.ca> Hello, I am running Publican 3.2. I created and installed a new brand. Prior to building and installing the new brand, I edited the 'overrides.cfg' file in the 'css' folder so all the headings, chapter titles, etc. would be green instead of the default. I replaced the existing CSS codes of "#a70000" with "#00cc00". After I built and installed the brand, I created a test article using the new brand, but the section headers, title, etc. still come out as the default colours. I appear to have missed something, but I am not sure what? Thanks, in advance, for your help and pointers. -Alan From lists at murrell.ca Sun Jul 19 17:14:14 2015 From: lists at murrell.ca (Alan Murrell) Date: Sun, 19 Jul 2015 10:14:14 -0700 Subject: [publican-list] Create Brand: Cannot change header colours In-Reply-To: <55AAC3E0.5000204@murrell.ca> References: <55AAC3E0.5000204@murrell.ca> Message-ID: <55ABDAE6.402@murrell.ca> Just by way of update... It seems that the "overrides.css" file is not being honoured when building PDF. If I build HTML, my colour scheme is honoured. Is there another file I need to edit/update for my colours to carry over to PDF builds? I am running this on CentOS 7. On 18/07/15 02:23 PM, Alan Murrell wrote: > Hello, > > I am running Publican 3.2. I created and installed a new brand. Prior > to building and installing the new brand, I edited the 'overrides.cfg' > file in the 'css' folder so all the headings, chapter titles, etc. would > be green instead of the default. I replaced the existing CSS codes of > "#a70000" with "#00cc00". > > After I built and installed the brand, I created a test article using > the new brand, but the section headers, title, etc. still come out as > the default colours. > > I appear to have missed something, but I am not sure what? > > Thanks, in advance, for your help and pointers. > > -Alan > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From lists at murrell.ca Sun Jul 19 18:32:00 2015 From: lists at murrell.ca (Alan Murrell) Date: Sun, 19 Jul 2015 11:32:00 -0700 Subject: [publican-list] Create Brand: Cannot change header colours In-Reply-To: <55AAC3E0.5000204@murrell.ca> References: <55AAC3E0.5000204@murrell.ca> Message-ID: <55ABED20.4030301@murrell.ca> OK, I figured it out. In the "root" directory for my brand, I created a folder called 'xsl'. I copied the 'pdf.xsl' file from the RedHat brand and changed the "title" colour reference from "#a70000" to "#00cc00". When I build the PDF, the title colurs are now how I expected (the green is a little too bright, so I will need play around with that, but that's a different issue,and one I can sort out on my own :-) ) On 18/07/15 02:23 PM, Alan Murrell wrote: > Hello, > > I am running Publican 3.2. I created and installed a new brand. Prior > to building and installing the new brand, I edited the 'overrides.cfg' > file in the 'css' folder so all the headings, chapter titles, etc. would > be green instead of the default. I replaced the existing CSS codes of > "#a70000" with "#00cc00". > > After I built and installed the brand, I created a test article using > the new brand, but the section headers, title, etc. still come out as > the default colours. > > I appear to have missed something, but I am not sure what? > > Thanks, in advance, for your help and pointers. > > -Alan > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From Norman at dunbar-it.co.uk Sun Jul 19 18:36:05 2015 From: Norman at dunbar-it.co.uk (Norman Dunbar) Date: Sun, 19 Jul 2015 19:36:05 +0100 Subject: [publican-list] Create Brand: Cannot change header colours In-Reply-To: <55ABED20.4030301@murrell.ca> References: <55AAC3E0.5000204@murrell.ca> <55ABED20.4030301@murrell.ca> Message-ID: <55ABEE15.3030408@dunbar-it.co.uk> Evening Alan, On 19/07/15 19:32, Alan Murrell wrote: > OK, I figured it out. In the "root" directory for my brand, I created a > folder called 'xsl'. I copied the 'pdf.xsl' file from the RedHat brand > and changed the "title" colour reference from "#a70000" to "#00cc00". > When I build the PDF, the title colurs are now how I expected (the green > is a little too bright, so I will need play around with that, but that's > a different issue,and one I can sort out on my own :-) ) > For a list of 140 Web Safe colours, have a look here - http://www.w3schools.com/html/html_colornames.asp - very useful, I have found. Saves you having to experiment with "50 shades of Green". ;-) Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: 27a Lidget Hill Pudsey West Yorkshire United Kingdom LS28 7LG Company Number: 05132767 From lists at murrell.ca Thu Jul 23 05:43:39 2015 From: lists at murrell.ca (Alan Murrell) Date: Wed, 22 Jul 2015 22:43:39 -0700 Subject: [publican-list] Create book without version Message-ID: <55B07F0B.9090103@murrell.ca> Hi, I have a template in Word that I use for client network documentation. I am wanting to "convert" this template into Publican. When I created the book I will be using to create the template in Publican, I used "COMPANY NAME" for the "--name" and "Network Documentation" for the "--title". The problem is I have to have a "version", and when I build the PDF, it shows like the following (if "--version" is "1"): COMPANY NAME 1 Network Documentation If I try to leave '' blank or put in any value except a number, I get an error when I build the documentation about the version not being able to be anything but a number. Is there any way I can be able to omit the version for the documentation? Thanks! :-) -Alan From jfearn at redhat.com Thu Jul 23 06:24:04 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 23 Jul 2015 16:24:04 +1000 Subject: [publican-list] Create book without version In-Reply-To: <55B07F0B.9090103@murrell.ca> References: <55B07F0B.9090103@murrell.ca> Message-ID: <55B08884.7010501@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/23/2015 03:43 PM, Alan Murrell wrote: > Hi, > > I have a template in Word that I use for client network documentation. I am wanting to "convert" this template into Publican. When I created the book I will be using to create the template in Publican, I used > "COMPANY NAME" for the "--name" and "Network Documentation" for the "--title". The problem is I have to have a "version", and when I build the PDF, it shows like the following (if "--version" is "1"): > > COMPANY NAME 1 > > Network Documentation > > If I try to leave '' blank or put in any value except a number, I get an error when I build the documentation about the version not being able to be anything but a number. > > Is there any way I can be able to omit the version for the documentation? Set the version in the book's config file and remove the version tag entirely from the info file. Cheers, Jeff. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVsIiEAAoJELs3R4zxGZvKG/QH/3/FVfLtN+CY6nXprt1JsNnA xAGSuDa3gXeQWIWxZ/NRiGpInmgC/UHwJ5z3qB8fmJRtZell4zUIL+vIf2XUCCO3 u8kkJNZSJ7Ue/93pG3J/x1HXcJGeuiajfj/20dpnx+CYcsgiLwnI15mkpA+PFgwL 0IShXhCIJ3k4XHqTcEc2dBDF9hxi+IKe4xur+5pKazGKZZwQix2RFzxx6GTK20Ws B9JFT76B8lL9SqN5XzTodEaF3ihCTf63+C72cxdK3TVXlwrzPhdN5258siSqxZx7 W4EaOmZ742HV/YKI0K5mNQHU22bFmXR0uJYZGC43WOBIB2zK73LpdnQVJ60H/O4= =xhom -----END PGP SIGNATURE----- From lists at murrell.ca Thu Jul 23 22:49:19 2015 From: lists at murrell.ca (Alan Murrell) Date: Thu, 23 Jul 2015 15:49:19 -0700 Subject: [publican-list] Create book without version In-Reply-To: <55B08884.7010501@redhat.com> References: <55B07F0B.9090103@murrell.ca> <55B08884.7010501@redhat.com> Message-ID: <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> Hi Jeff, Quoting "Jeff Fearn" : > Set the version in the book's config file and remove the version tag > entirely from the info file. That did the trick! Perfect! And I can still produce/build versioned documentation :-) Now I am going to see if I can make tables work (I saw some posts in the archives about it not working as it should, but we'll see!) On a side note, I am wanting to setup some sort of version control system; what is your recommendation? I see subversion and git mentioned the most, but then others suggest that they may be overkill, as you wouldn't need the features like "trunks", "branches", etc. What does Red Hat use for version control of documents? Thanks! :-) -Alan From jfearn at redhat.com Thu Jul 23 23:30:59 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Fri, 24 Jul 2015 09:30:59 +1000 Subject: [publican-list] Create book without version In-Reply-To: <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> References: <55B07F0B.9090103@murrell.ca> <55B08884.7010501@redhat.com> <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> Message-ID: <55B17933.8060504@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/24/2015 08:49 AM, Alan Murrell wrote: > Hi Jeff, > > Quoting "Jeff Fearn" : > >> Set the version in the book's config file and remove the version tag entirely from the info file. > > That did the trick! Perfect! And I can still produce/build versioned documentation :-) > > Now I am going to see if I can make tables work (I saw some posts in the archives about it not working as it should, but we'll see!) > > On a side note, I am wanting to setup some sort of version control system; what is your recommendation? I see subversion and git mentioned the most, but then others suggest that they may be overkill, as you wouldn't > need the features like "trunks", "branches", etc. > > What does Red Hat use for version control of documents? Most of the stuff was in SVN and is migrating to GIT. I'm not sure either is great for docs as the docs life cycle is not similar to source code's life cycle. I've never had time to poke around the CMSs and documentation management systems enough to be able to recommend one. Cheers, Jeff. - -- Jeff Fearn Senior Software Engineer PnT - DevOps - Development Red Hat Asia Pacific Pty Ltd http://dilbert.com/fast/2004-08-17/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVsXkzAAoJELs3R4zxGZvK0h4H/3QoPgY9Y6iuj/9PjX6YNost 1yui6FDAaNx1Hw9M8ATvnFrnqn9emgI5446euidUSKUoM+NHVIZPh6WA+dq1WLf5 9RnYpThUQz24vGtO8v7UJfWo954Mqofd/GLVB2dNpq9XWQHyoJkSgTo7LTCqpw9G uj885nh+rmC5Lbg1PsFC8/XD9inVSHDK280tQycXJnVOoNE2gt54Oo7xJFnO6wBy 9re0itCDoL0Uc334nWR3ZAvH2GGoujmelEziSo511xrVgv2ZPN5+lxAf+ndS1ygd NnPM11bhSG/m6DdIgj1X+P7RkU/gUuP0dX12yS+aBUvkwrAUxNiAA1wzKgNSJus= =Mt3H -----END PGP SIGNATURE----- From norman at dunbar-it.co.uk Fri Jul 24 07:43:28 2015 From: norman at dunbar-it.co.uk (Norman Dunbar) Date: Fri, 24 Jul 2015 08:43:28 +0100 Subject: [publican-list] Create book without version In-Reply-To: <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> References: <55B07F0B.9090103@murrell.ca> <55B08884.7010501@redhat.com> <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> Message-ID: Morning Alan, I've been using subversive to version control my docs. It's true that branches are not really required, but that's not a problem. I kept my report on a small usb thumb drive (Crucial 256mb!) so that I could carry it around. Obviously svn was required wherever I was working. That worked fine for me. HTH Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity and any "auto corrections" that are just wrong! -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at murrell.ca Fri Jul 24 09:57:59 2015 From: lists at murrell.ca (Alan Murrell) Date: Fri, 24 Jul 2015 02:57:59 -0700 Subject: [publican-list] Create book without version In-Reply-To: References: <55B07F0B.9090103@murrell.ca> <55B08884.7010501@redhat.com> <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> Message-ID: <55B20C27.70604@murrell.ca> Norman, Jeff. Thanks for your responses re: document versioning control. I imagine you would setup each document as a "project", and then check out/in each "project" as you update it. -Alan From lists at murrell.ca Fri Jul 24 10:12:45 2015 From: lists at murrell.ca (Alan Murrell) Date: Fri, 24 Jul 2015 03:12:45 -0700 Subject: [publican-list] Versioning control Message-ID: <55B20F9D.4000804@murrell.ca> Sorry, I had one other question regarding versioning control. I know it is not strictly Publican-related, but I think it is semi-related, and I didn't want to completely "pollute" my other thread. My company services several clients for whom we maintain documentation. I see that both SVN and git can do "sub-projects", though they both seem to have their own pros/cons with how they manage it. Would it be better to setup each client as a "project" with each set of documentation as a sub project, like this: |--CLIENT1 | |--Network_Documentation | |--Business_Continuity_Plan | `--Some_Other_Document |--CLIENT2 | |--Document1 | |--Document2 | `--Document3 Or would it be better all-around to do something like this: |--CLIENT1_NAME-Network_Documentation |--CLIENT2_NAME-Document1 |--CLIENT1_NAME-Business_Continuity_Plan |--etc. In the second instance, is it possible to sort the projects by name, so the documents for specific clients? I imagine this would be more a feature of the web-based respository browser? Thanks! I think that's really the only other thing I was wondering before jumping in to it myself :-) -Alan From lists at murrell.ca Fri Jul 24 10:22:34 2015 From: lists at murrell.ca (Alan Murrell) Date: Fri, 24 Jul 2015 03:22:34 -0700 Subject: [publican-list] Versioning control In-Reply-To: <55B20F9D.4000804@murrell.ca> References: <55B20F9D.4000804@murrell.ca> Message-ID: <55B211EA.7030404@murrell.ca> I think I found my own answers... I would probably want to setup each client as their own repository with their specific documents setup as seperate projects within that repository. OK, I think I am ready to jump in. :-) -Alan On 24/07/2015 3:12 AM, Alan Murrell wrote: > Sorry, I had one other question regarding versioning control. I know it > is not strictly Publican-related, but I think it is semi-related, and I > didn't want to completely "pollute" my other thread. > > My company services several clients for whom we maintain documentation. > I see that both SVN and git can do "sub-projects", though they both > seem to have their own pros/cons with how they manage it. > > Would it be better to setup each client as a "project" with each set of > documentation as a sub project, like this: > > |--CLIENT1 > | |--Network_Documentation > | |--Business_Continuity_Plan > | `--Some_Other_Document > |--CLIENT2 > | |--Document1 > | |--Document2 > | `--Document3 > > Or would it be better all-around to do something like this: > > |--CLIENT1_NAME-Network_Documentation > |--CLIENT2_NAME-Document1 > |--CLIENT1_NAME-Business_Continuity_Plan > |--etc. > > In the second instance, is it possible to sort the projects by name, so > the documents for specific clients? I imagine this would be more a > feature of the web-based respository browser? > > Thanks! I think that's really the only other thing I was wondering > before jumping in to it myself :-) > > -Alan > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From norman at dunbar-it.co.uk Fri Jul 24 15:03:48 2015 From: norman at dunbar-it.co.uk (Norman Dunbar) Date: Fri, 24 Jul 2015 16:03:48 +0100 Subject: [publican-list] Create book without version In-Reply-To: <55B20C27.70604@murrell.ca> References: <55B07F0B.9090103@murrell.ca> <55B08884.7010501@redhat.com> <20150723154919.97826wuly0vml20w@remote.van.murrell.ca> <55B20C27.70604@murrell.ca> Message-ID: On 24 July 2015 10:57:59 BST, Alan Murrell wrote: >Norman, Jeff. > >Thanks for your responses re: document versioning control. I imagine >you would setup each document as a "project", and then check out/in >each >"project" as you update it. > >-Alan > >_______________________________________________ >publican-list mailing list >publican-list at redhat.com >https://www.redhat.com/mailman/listinfo/publican-list >Wiki: https://fedorahosted.org/publican Hi Alan, Yes, that's exactly what I have been doing. Each document, or brand, is checked in as a separate project. Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity and any "auto corrections" that are just wrong! -------------- next part -------------- An HTML attachment was scrubbed... URL: From norman at dunbar-it.co.uk Fri Jul 24 15:06:14 2015 From: norman at dunbar-it.co.uk (Norman Dunbar) Date: Fri, 24 Jul 2015 16:06:14 +0100 Subject: [publican-list] Versioning control In-Reply-To: <55B211EA.7030404@murrell.ca> References: <55B20F9D.4000804@murrell.ca> <55B211EA.7030404@murrell.ca> Message-ID: <64339583-3E5C-4CEC-8EA2-24D155F87D03@dunbar-it.co.uk> On 24 July 2015 11:22:34 BST, Alan Murrell wrote: >I think I found my own answers... > >I would probably want to setup each client as their own repository with > >their specific documents setup as seperate projects within that >repository. > >OK, I think I am ready to jump in. :-) > >-Alan > > >On 24/07/2015 3:12 AM, Alan Murrell wrote: >> Sorry, I had one other question regarding versioning control. I know >it >> is not strictly Publican-related, but I think it is semi-related, and >I >> didn't want to completely "pollute" my other thread. >> >> My company services several clients for whom we maintain >documentation. >> I see that both SVN and git can do "sub-projects", though they both >> seem to have their own pros/cons with how they manage it. >> >> Would it be better to setup each client as a "project" with each set >of >> documentation as a sub project, like this: >> >> |--CLIENT1 >> | |--Network_Documentation >> | |--Business_Continuity_Plan >> | `--Some_Other_Document >> |--CLIENT2 >> | |--Document1 >> | |--Document2 >> | `--Document3 >> >> Or would it be better all-around to do something like this: >> >> |--CLIENT1_NAME-Network_Documentation >> |--CLIENT2_NAME-Document1 >> |--CLIENT1_NAME-Business_Continuity_Plan >> |--etc. >> >> In the second instance, is it possible to sort the projects by name, >so >> the documents for specific clients? I imagine this would be more a >> feature of the web-based respository browser? >> >> Thanks! I think that's really the only other thing I was wondering >> before jumping in to it myself :-) >> >> -Alan >> >> _______________________________________________ >> publican-list mailing list >> publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list >> Wiki: https://fedorahosted.org/publican > >_______________________________________________ >publican-list mailing list >publican-list at redhat.com >https://www.redhat.com/mailman/listinfo/publican-list >Wiki: https://fedorahosted.org/publican This is what I would do too. Separate clients get separate repositories. Mask, snorkel, fins and a bottle of cider at the ready....now dive in! :-) Have fun. Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity and any "auto corrections" that are just wrong! -------------- next part -------------- An HTML attachment was scrubbed... URL: From lnewson at redhat.com Tue Jul 28 06:54:11 2015 From: lnewson at redhat.com (Lee Newson) Date: Tue, 28 Jul 2015 02:54:11 -0400 (EDT) Subject: [publican-list] Publican 4.3.2 hot fix released In-Reply-To: <1186354131.1803532.1438066339142.JavaMail.zimbra@redhat.com> Message-ID: <1668073276.1804854.1438066451900.JavaMail.zimbra@redhat.com> Hi all, Publican 4.3.2 has been released. Files available at https://fedorahosted.org/releases/p/u/publican/ Here is the change log: * Tue Jul 28 2015 - Do not replace non-breaking spaces by spaces in msgid of POT files. BZ #1233202 - Fixed Unwanted line breaks around images. BZ #1222067 - Fixed EPUB output of db5 brands can't be viewed. BZ #1241348 Cheers Lee -------------- next part -------------- An HTML attachment was scrubbed... URL: