From jfearn at redhat.com Wed Mar 11 21:40:29 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 12 Mar 2015 07:40:29 +1000 Subject: [publican-list] Profiling fo for color and bw In-Reply-To: <54EC52B8.4090106@xcom.de> References: <54EC52B8.4090106@xcom.de> Message-ID: <5500B64D.4050704@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/24/2015 08:30 PM, Sascha Manns wrote: > Hello list, > > the most time i'm generating documents with colors in fo output. But sometimes i know that the customers would print out the document. So i would like to place in the code a option to use the colored pictures or using > the black and white pendant instead. Maybe that could be done with a attribute role or so. Maybe anyone has done such thing? I've never done this so there might be a simpler way, but you could use conditionals for this. Put two imagedata in place, one with condition="colour", one with condition="greyscale" then set the condition in you publican.cfg. Cheers, Jeff. - -- Jeff Fearn Senior Software Engineer Hosted & Shared Services Red Hat Asia Pacific Pty Ltd http://dilbert.com/fast/2004-08-17/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVALZNAAoJELs3R4zxGZvKMPMH/0GfoM+uVQlBhXP4tI47l53A jQtoRh9yPIM6Vf+snLOuHcOvkW3N9z0Z7pptBne7H4aQySuewKrn09sKSl7u4+I5 nPqn9NXgM+1Xoro3Ou+1vvAaO1UpA1k3wH+9/8QVLvDDDn2jNBsRASDOq9mo0mvq /MiIwttCN9w/tJNwXe11ya4f5aM9I0tT1ILvRArTsNqCN+qmYy9YzepjVXBH1zfR vc9BAV1dfIv/67Zg3dy44M652GCr3QM4r/344S8X5we6Etn5JivGPAnXjG3Gt/QW b/O7NgPzUL0xHReqOJvvI9tI/dGldhkt0RVBqSIfW6gSZfcWeZpiY1Wjv21UVXg= =Cqv0 -----END PGP SIGNATURE----- From jfearn at redhat.com Wed Mar 11 21:44:11 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 12 Mar 2015 07:44:11 +1000 Subject: [publican-list] Profiling fo for color and bw In-Reply-To: <5500B64D.4050704@redhat.com> References: <54EC52B8.4090106@xcom.de> <5500B64D.4050704@redhat.com> Message-ID: <5500B72B.1050600@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/12/2015 07:40 AM, Jeff Fearn wrote: > On 02/24/2015 08:30 PM, Sascha Manns wrote: >> Hello list, > >> the most time i'm generating documents with colors in fo output. But sometimes i know that the customers would print out the document. So i would like to place in the code a option to use the colored pictures or >> using the black and white pendant instead. Maybe that could be done with a attribute role or so. Maybe anyone has done such thing? > > I've never done this so there might be a simpler way, but you could use conditionals for this. > > Put two imagedata in place, one with condition="colour", one with condition="greyscale" then set the condition in you publican.cfg. You can of course have two cfg files one for each and the use --config to control whic gets used. If colour is your default then if you set that in publican.cfg then you only need to supply --config for the black and white build. Cheers, Jeff. - -- Jeff Fearn Senior Software Engineer Hosted & Shared Services Red Hat Asia Pacific Pty Ltd http://dilbert.com/fast/2004-08-17/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVALcrAAoJELs3R4zxGZvKeqYH/RFMqQknr1CAN4KQRMnmxexJ J74Hr3xWSTK+jKV+EbvlAmqjV0PBX314s+srMEBBCn2Jb8de2hNOiPhKw1ckOMMK JBxHY4dfpfr3HWYQ0+txxqO2r4ZTRR5y5zsPe8tzD4y5rQzG0yQk1LPpiC7XTJZk hVn267Zpj+e4ZLUyAlv5P1UZ4yuDP8LEk5jbHw0UcLA5BYW/e4SJ53gGf+ZOOjj8 LjLjyf6LC22gjIblLFKQJM9j71AU9p2LAoG9TsA5GrKH6I5AOKxu90Lq4PfYMFEs FOcC5WyjJ1UCyplcsFBOub2Oo2bw2BilP7mzKwxh0irf7/ja4osqFsr2SOsgMgw= =xBpq -----END PGP SIGNATURE----- From bugzilla at redhat.com Wed Mar 25 03:51:37 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 25 Mar 2015 03:51:37 +0000 Subject: [publican-list] [Bug 701929] RFA: Customising brands section In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=701929 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Assignee|zdover at redhat.com |r.landmann at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=7v4rPIkwMB&a=cc_unsubscribe From daobrien at redhat.com Fri Mar 27 14:34:35 2015 From: daobrien at redhat.com (David O'Brien) Date: Sat, 28 Mar 2015 00:34:35 +1000 Subject: [publican-list] Inserting lines > 80 chars long? Message-ID: <55156A7B.9050307@redhat.com> Anyone know if it's possible to insert lines that are longer than 80 characters, and not have them wrap in the output? (I believe 80 chars is the max but not sure?) In this particular case I want to include an example config line for a kickstart file that you can copy/paste straight into the ks file, but the standard/normal output wraps the line. Apparently the ks file won't accept that. I've tried using and and futzed about with 80 chars long? In-Reply-To: <55156A7B.9050307@redhat.com> References: <55156A7B.9050307@redhat.com> Message-ID: <20150327145142.GF20192@sbonnevi.msp.redhat.com> On Sat, Mar 28, 2015 at 12:34:35AM +1000, David O'Brien wrote: > Anyone know if it's possible to insert lines that are longer than 80 > characters, and not have them wrap in the output? (I believe 80 chars is > the max but not sure?) > > In this particular case I want to include an example config line for a > kickstart file that you can copy/paste straight into the ks file, but > the standard/normal output wraps the line. Apparently the ks file won't > accept that. > > I've tried using and and futzed about with > or in a somewhere) and the XSL of your Publican brand. Typically, we're trying to deal with long lines by using explicit line wraps in the examples, for situations where that's accepted. For instance, we'll use \ line continuation for long shell commands or statements. I think that Kickstart directives may accept that too, but I haven't tested that recently myself. -- Steve -- Steven Bonneville Manager, Curriculum Development Red Hat | Red Hat Training Phone: +1-612-638-0507 gpg: 1024D/221D06FF 68B1 3E66 A351 6485 B9AF 24D8 3DF5 B50B 221D 06FF From daobrien at redhat.com Fri Mar 27 15:21:05 2015 From: daobrien at redhat.com (David O'Brien) Date: Sat, 28 Mar 2015 01:21:05 +1000 Subject: [publican-list] Inserting lines > 80 chars long? In-Reply-To: <20150327145142.GF20192@sbonnevi.msp.redhat.com> References: <55156A7B.9050307@redhat.com> <20150327145142.GF20192@sbonnevi.msp.redhat.com> Message-ID: <55157561.1080507@redhat.com> On 03/28/2015 12:51 AM, Steve Bonneville wrote: > On Sat, Mar 28, 2015 at 12:34:35AM +1000, David O'Brien wrote: >> Anyone know if it's possible to insert lines that are longer than 80 >> characters, and not have them wrap in the output? (I believe 80 chars is >> the max but not sure?) >> >> In this particular case I want to include an example config line for a >> kickstart file that you can copy/paste straight into the ks file, but >> the standard/normal output wraps the line. Apparently the ks file won't >> accept that. >> >> I've tried using and and futzed about with >> > ...may not be helpful, but I can tell that I'm used to rendering to > PDF as well as HTML, because my first reaction is that you're risking > running off the edge of the page by trying to suppress line wraps.... :) > > How far in the linewrap happens will depend on context (are you in a > or in a somewhere) and the XSL of your > Publican brand. > > Typically, we're trying to deal with long lines by using explicit line > wraps in the examples, for situations where that's accepted. For > instance, we'll use \ line continuation for long shell commands or > statements. I think that Kickstart directives may accept that too, > but I haven't tested that recently myself. > > -- Steve > Hi Steve I wondered about the PDF output as well, and thought I might have to just bite the bullet and warn the user to "enter all of the following on one line" or something, and then let the lines wrap where they will. The current example is in a block. We do what you suggested above for long shell commands, but I'm not set up to test what happens with ks files. I'm mostly going by other ppl's comments in that regard. cheers -- David From jfearn at redhat.com Sun Mar 29 23:12:04 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 30 Mar 2015 09:12:04 +1000 Subject: [publican-list] Inserting lines > 80 chars long? In-Reply-To: <55157561.1080507@redhat.com> References: <55156A7B.9050307@redhat.com> <20150327145142.GF20192@sbonnevi.msp.redhat.com> <55157561.1080507@redhat.com> Message-ID: <551886C4.5070508@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/28/2015 01:21 AM, David O'Brien wrote: > On 03/28/2015 12:51 AM, Steve Bonneville wrote: >> On Sat, Mar 28, 2015 at 12:34:35AM +1000, David O'Brien wrote: >>> Anyone know if it's possible to insert lines that are longer than 80 >>> characters, and not have them wrap in the output? It's not possible without modifying the CSS. >>> (I believe 80 chars is >>> the max but not sure?) In the Red Hat portal the content body is constrained to 970px. >>> In this particular case I want to include an example config line for a >>> kickstart file that you can copy/paste straight into the ks file, but >>> the standard/normal output wraps the line. Apparently the ks file won't >>> accept that. >>> >>> I've tried using and and futzed about with >>> > >> ...may not be helpful, but I can tell that I'm used to rendering to >> PDF as well as HTML, because my first reaction is that you're risking >> running off the edge of the page by trying to suppress line wraps.... :) >> >> How far in the linewrap happens will depend on context (are you in a >> or in a somewhere) and the XSL of your >> Publican brand. >> >> Typically, we're trying to deal with long lines by using explicit line >> wraps in the examples, for situations where that's accepted. For >> instance, we'll use \ line continuation for long shell commands or >> statements. I think that Kickstart directives may accept that too, >> but I haven't tested that recently myself. >> >> -- Steve >> > Hi Steve > > I wondered about the PDF output as well, Reading that on a mobile device would probably be a bad user experience. > and thought I might have to > just bite the bullet and warn the user to "enter all of the following on > one line" or something, and then let the lines wrap where they will. > > The current example is in a block. We do what you > suggested above for long shell commands, but I'm not set up to test what > happens with ks files. I'm mostly going by other ppl's comments in that > regard. You might consider having standalone kickstart file/s in the examples directory, link to it in the document body, and use text to describe what's in the file. Cheers, Jeff. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJVGIbEAAoJELs3R4zxGZvKQUUH/2VZtb2Wg4gCKk8HmBTs0Rf/ fMpvhjS6eIT/H5+OW+RCZM9mtOXBKmIwDsoCXQOs3gFbwC8a1wamTiLktRU3o/5Y +CjpRA2kvZsua5AuaC7AJU6H3AM9979iNtDPR4Wj0E7XEn3P5lqYRKLTQfs2BLSu pkl/ah3HupDywU3LeLTFCpmahCk1S753URIEu78EITXWHK8HYQCt8NhyNZ5WTXzu cMfGBlF7vi7IYUKN8L+XScdKKSz4ORmjEpcUEdSiqvw3qPDdrSMIPByghtWHMdck FGRpcsxRJDmDONWM9Xe+/FSLnV/sOYaWaostGCUkiBtGs+y6HFcFj/K4C/OkjuA= =z6SF -----END PGP SIGNATURE----- From daobrien at redhat.com Mon Mar 30 00:33:49 2015 From: daobrien at redhat.com (David O'Brien) Date: Mon, 30 Mar 2015 10:33:49 +1000 Subject: [publican-list] Inserting lines > 80 chars long? In-Reply-To: <551886C4.5070508@redhat.com> References: <55156A7B.9050307@redhat.com> <20150327145142.GF20192@sbonnevi.msp.redhat.com> <55157561.1080507@redhat.com> <551886C4.5070508@redhat.com> Message-ID: <551899ED.9050502@redhat.com> On 03/30/2015 09:12 AM, Jeff Fearn wrote: > On 03/28/2015 01:21 AM, David O'Brien wrote: >> On 03/28/2015 12:51 AM, Steve Bonneville wrote: >>> On Sat, Mar 28, 2015 at 12:34:35AM +1000, David O'Brien wrote: >>>> Anyone know if it's possible to insert lines that are longer than 80 >>>> characters, and not have them wrap in the output? > > It's not possible without modifying the CSS. Not my first choice, I have to say. Prefer to keep the standard brand as much as possible. > >>>> (I believe 80 chars is >>>> the max but not sure?) > > In the Red Hat portal the content body is constrained to 970px. > >>>> In this particular case I want to include an example config line for a >>>> kickstart file that you can copy/paste straight into the ks file, but >>>> the standard/normal output wraps the line. Apparently the ks file won't >>>> accept that. >>>> >>>> I've tried using and and futzed about with >>>> >> >>> ...may not be helpful, but I can tell that I'm used to rendering to >>> PDF as well as HTML, because my first reaction is that you're risking >>> running off the edge of the page by trying to suppress line wraps.... :) >>> >>> How far in the linewrap happens will depend on context (are you in a >>> or in a somewhere) and the XSL of your >>> Publican brand. >>> >>> Typically, we're trying to deal with long lines by using explicit line >>> wraps in the examples, for situations where that's accepted. For >>> instance, we'll use \ line continuation for long shell commands or >>> statements. I think that Kickstart directives may accept that too, >>> but I haven't tested that recently myself. >>> >>> -- Steve >>> >> Hi Steve > >> I wondered about the PDF output as well, > > Reading that on a mobile device would probably be a bad user experience. Yes, I wondered about that too and made a point of asking around, for this particular use case, how prevalent mobile devices were. At this point in time, not at all, but that could change at any time. > >> and thought I might have to >> just bite the bullet and warn the user to "enter all of the following on >> one line" or something, and then let the lines wrap where they will. > >> The current example is in a block. We do what you >> suggested above for long shell commands, but I'm not set up to test what >> happens with ks files. I'm mostly going by other ppl's comments in that >> regard. > > You might consider having standalone kickstart file/s in the examples > directory, link to it in the document body, and use text to describe > what's in the file. Also a possibility, and definitely on the list of things to consider. thanks David > > Cheers, Jeff. > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > From Sascha.Manns at xcom.de Mon Mar 30 10:28:41 2015 From: Sascha.Manns at xcom.de (Sascha Manns) Date: Mon, 30 Mar 2015 12:28:41 +0200 Subject: [publican-list] Automatic updating of version in Article_Info.xml Message-ID: <55192559.9040303@xcom.de> Hello List, if i'm using "publican add_revision" is there any qay to tell publican that it should update the version in Article_Info.xml aututomatically? Greetings Sascha -- Yours sincerly Sascha Manns --------------------------------- XCOM AG Qualit?tsmanagement Banksystem Backend Rechnungswesen, Meldewesen, Steuern Rennweg 60 Haus 2 56626 Andernach Telefon +49 2632 9899-158 Telefax +49 2632 9899-010 Sascha.Manns at xcom.de http://www.xcom.de *** XCOM AG Legal Disclaimer *** Diese E-Mail einschliesslich ihrer Anhaenge ist vertraulich und ist allein f?r den Gebrauch durch den vorgesehenen Empfaenger bestimmt. Dritten ist das Lesen, Verteilen oder Weiterleiten dieser E-Mail untersagt. Wir bitten, eine fehlgeleitete E-Mail unverzueglich vollstaendig zu loeschen und uns eine Nachricht zukommen zu lassen. This email may contain material that is confidential and for the sole use of the intended recipient. Any review, distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Hauptsitz: Allee 8, D-47877 Willich, USt-IdNr.: DE 812 885 664 Kommunikation: Telefon +49 2154 9209-70, Telefax +49 2154 9209-900, www.xcom.de Handelsregister: Amtsgericht Krefeld, HRB 10340 Vorstand: Dirk Franzmeyer, Marco Marty, Dirk Werner, Sascha Bochartz Vorsitzender des Aufsichtsrates: Stefan H. Tarach -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfearn at redhat.com Mon Mar 30 21:28:46 2015 From: jfearn at redhat.com (Jeff Fearn) Date: Tue, 31 Mar 2015 07:28:46 +1000 Subject: [publican-list] Automatic updating of version in Article_Info.xml In-Reply-To: <55192559.9040303@xcom.de> References: <55192559.9040303@xcom.de> Message-ID: <5519C00E.6060409@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/30/2015 08:28 PM, Sascha Manns wrote: > Hello List, > > if i'm using "publican add_revision" is there any qay to tell publican that it should update the version in Article_Info.xml aututomatically? > Hi Sascha, add_revision only updates the Revision History files and has no capability to edit any other files. 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 iQEcBAEBAgAGBQJVGcAOAAoJELs3R4zxGZvKi54H/0OAlb9dLugi27sLKURbPQdx wrFgDdDN7w5O/HGVyNNEkWT4Ro1ZzRsX/u46cgN8o0xIRqr3zvtd9T6VYMgwjo7k WojWB3TJRmL8fVqevg4F19M92ZckYydp/IBFlqF5W9e8/fedxnE7wu2yMn/IT/x3 2ga+rZOdFcxxQvoRxlVPCa3ZD50DB2TMvAKeq3z9nklwMByJnU1PecLHB9ZsfVZq pNV4Eo9nfAXAV1gRvPaXb53+VTlmJl8Rm+y03zSgeQI/tcBkRD5Nb+VYLltF7Afl 6oIraLVA9NotpQvBcyzTy7qlmz3KUsgbyQyXBd8PjEBmkb/Sr8KYEiAgl0pFjjs= =uAmg -----END PGP SIGNATURE-----