From jfearn at redhat.com Fri Oct 1 05:03:38 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 01 Oct 2010 15:03:38 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CA519D6.8000703@redhat.com> References: <2061256393.884011285884239050.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> <4CA50B84.1090600@redhat.com> <4CA50DD6.60809@redhat.com> <4CA519D6.8000703@redhat.com> Message-ID: <4CA56BAA.9030805@redhat.com> Lana Brindley wrote: > On 10/01/2010 08:23 AM, Jeffrey Fearn wrote: >> A real example where you couldn't write around it would carry much more >> weight and prevent such responses. >> > > OK. > > file:///usr/share/doc/publican-doc-2.1/en-US/index.html#sect-Users_Guide-Building_a_document > > > "Note -- Customizing output" I think this is an example of poor use of admonitions. Option A: 1: Starting a section with an admonition is bad form. 2: The information in the admonition should be and optional step 5 in the 'To build a document' procedure. 3: There is now no need for the admonition to exist. Option B: 1: Make the note a formal para and move it after the procedure, there is no reason for it to be marked up for special attentions, it is just another command line option. The proceeding section, 3.5. Preparing a document for translation, has an example of poor use of important. 1: The information in the important 'set Project-Id-Version for packaging' should be inserted as step 5, with the current 5 becoming 6, in the procedure it references. 2: The important should actually be a warning that failing to follow step 5 will result in invalid packages or your build failing. 3: The new warning should be moved to after the procedure. Regardless of having no example of where this kind of layout isn't bad form, I still think it's a good idea not to break the output. Having said that "lighter, brighter, darker, less/more colourific" don't mean anything to me, so unless someone supplies some real input, like actual colors or something, this won't be fixed in a hurry. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From rlerch at redhat.com Sun Oct 3 21:46:05 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Mon, 04 Oct 2010 07:46:05 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CA56BAA.9030805@redhat.com> References: <2061256393.884011285884239050.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> <4CA50B84.1090600@redhat.com> <4CA50DD6.60809@redhat.com> <4CA519D6.8000703@redhat.com> <4CA56BAA.9030805@redhat.com> Message-ID: <4CA8F99D.80504@redhat.com> On 10/01/2010 03:03 PM, Jeffrey Fearn wrote: > > Having said that "lighter, brighter, darker, less/more colourific" > don't mean anything to me, so unless someone supplies some real input, > like actual colors or something, this won't be fixed in a hurry. +1 Mock-ups of intended layouts are our friend in this case. Feel free to create one (feel free to ping me if you need a hand to create a mockup) :) cheers, ryanlerch From misty at redhat.com Sun Oct 3 22:46:38 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Sun, 3 Oct 2010 18:46:38 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1551551902.453511285825764384.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <1689200496.751671286145998200.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> For the programlistings and screens inside admonitions, I vote for having them display the same as if they were not in the admonition (I think the background color is grey). For the note / info / warning, I think a thick border of the same color as the current boxes, with either a grey interior or a much lighter shade of the border color. I will try to come up with a mock-up of what I have in mind. Misty ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Publican discussions" > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > Hi Rudi, > > You can see it at > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > The background is black and the XML tags are navy blue. You can barely > see the blue if you squint at the screenshot. Some things would also > be marked up as red or what turns out to be dark green. It would all > be fine if the background were white. > > Also I think the rounded divs are a bit tiresome, but that may be > personal preference. > > Misty > > ----- "Ruediger Landmann" wrote: > > > From: "Ruediger Landmann" > > To: "Publican discussions" > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > 5. Programlistings inside of notes, warnings, or infos look > > terrible. > > > Screenshot attached. > > > > Hi Misty -- Could you please clarify this a little? It's the only > > point > > that I don't quite understand. > > > > Do you just mean having white text on a black background? The > strange > > > > formatting in your screenshot is probably a faithful representation > of > > > > the underlying XML. To reproduce something like it, I need to > > introduce > > extraneous whitespace and linebreaks into the . > > > > Cheers > > Rudi > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From oguzyilmazlist at gmail.com Mon Oct 4 13:53:39 2010 From: oguzyilmazlist at gmail.com (Oguz Yilmaz) Date: Mon, 4 Oct 2010 16:53:39 +0300 Subject: [publican-list] notification image does not shown in the pdf output Message-ID: Hi, I have successfully created my first document using publican. I have a simple pr?blem. Note, warning and important images are shown in the html output but not in pdf output. Sample is here: http://tinypic.com/r/14ttvk/7 What can be the problem? Best Regards, -- Oguz YILMAZ From r.landmann at redhat.com Tue Oct 5 02:21:13 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Tue, 05 Oct 2010 12:21:13 +1000 Subject: [publican-list] notification image does not shown in the pdf output In-Reply-To: References: Message-ID: <4CAA8B99.4060506@redhat.com> On 10/04/2010 11:53 PM, Oguz Yilmaz wrote: > Hi, > > I have successfully created my first document using publican. I have a > simple pr?blem. Note, warning and important images are shown in the > html output but not in pdf output. Sample is here: > > http://tinypic.com/r/14ttvk/7 > > What can be the problem? Hi Oguz; Did you create a brand for your document? Or are you using the common brand? If you created your own brand, make sure that you created important.svg, note.svg and warning.svg images for your admonitions, not only PNG images. If you are using the common brand for this document, let us know, and we can investigate further. Cheers Rudi From misty at redhat.com Tue Oct 5 23:36:21 2010 From: misty at redhat.com (misty at redhat.com) Date: Tue, 5 Oct 2010 19:36:21 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <109248763.1108701286321697892.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <347841399.1108731286321781714.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Attached are two mock-ups for admonitions. I really like the white, but I have a feeling the grey fits in more with our current styles. The only potential problem I see is that programlistings inside admonitions would be grey on grey (if I get my wish and we change the black to grey for programlistings and screens inside admonitions). If the block-level elements inside admonitions just have a 1px border, that problem is solved as well. Feedback is appreciated! Misty ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Misty Stanley-Jones" , "Publican discussions" > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > For the programlistings and screens inside admonitions, I vote for > having them display the same as if they were not in the admonition (I > think the background color is grey). > > For the note / info / warning, I think a thick border of the same > color as the current boxes, with either a grey interior or a much > lighter shade of the border color. I will try to come up with a > mock-up of what I have in mind. > > Misty > > ----- "Misty Stanley-Jones" wrote: > > > From: "Misty Stanley-Jones" > > To: "Publican discussions" > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > Hi Rudi, > > > > You can see it at > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > The background is black and the XML tags are navy blue. You can > barely > > see the blue if you squint at the screenshot. Some things would > also > > be marked up as red or what turns out to be dark green. It would > all > > be fine if the background were white. > > > > Also I think the rounded divs are a bit tiresome, but that may be > > personal preference. > > > > Misty > > > > ----- "Ruediger Landmann" wrote: > > > > > From: "Ruediger Landmann" > > > To: "Publican discussions" > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > 5. Programlistings inside of notes, warnings, or infos look > > > terrible. > > > > Screenshot attached. > > > > > > Hi Misty -- Could you please clarify this a little? It's the only > > > point > > > that I don't quite understand. > > > > > > Do you just mean having white text on a black background? The > > strange > > > > > > formatting in your screenshot is probably a faithful > representation > > of > > > > > > the underlying XML. To reproduce something like it, I need to > > > introduce > > > extraneous whitespace and linebreaks into the . > > > > > > Cheers > > > Rudi > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. -------------- next part -------------- A non-text attachment was scrubbed... Name: Admonitions_grey_bg.png Type: image/png Size: 36000 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Admonitions_white_bg.png Type: image/png Size: 35860 bytes Desc: not available URL: From jmorgan at redhat.com Tue Oct 5 23:52:30 2010 From: jmorgan at redhat.com (Jared Morgan) Date: Tue, 5 Oct 2010 19:52:30 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <6880990.24.1286322694284.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Message-ID: <31643511.27.1286322905728.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> I'm a big fan of the white background as well. You could then have a light grey or inside admonitions, which would remove the need for a 1px border. All you need to do now is work your mock-up magic on output, Misty. ;) Cheers Jared Morgan Content Author Red Hat Asia Pacific 1/193 North Quay BRISBANE QLD 4000 P: +61 7 3514 8242 M: +61 413 005 479 From: misty at redhat.com To: "Misty Stanley-Jones" Cc: "Publican discussions" Sent: Wednesday, October 6, 2010 9:36:21 AM Subject: Re: [publican-list] RFE for Publican Brands Attached are two mock-ups for admonitions. I really like the white, but I have a feeling the grey fits in more with our current styles. The only potential problem I see is that programlistings inside admonitions would be grey on grey (if I get my wish and we change the black to grey for programlistings and screens inside admonitions). If the block-level elements inside admonitions just have a 1px border, that problem is solved as well. Feedback is appreciated! Misty ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Misty Stanley-Jones" , "Publican discussions" > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > For the programlistings and screens inside admonitions, I vote for > having them display the same as if they were not in the admonition (I > think the background color is grey). > > For the note / info / warning, I think a thick border of the same > color as the current boxes, with either a grey interior or a much > lighter shade of the border color. I will try to come up with a > mock-up of what I have in mind. > > Misty > > ----- "Misty Stanley-Jones" wrote: > > > From: "Misty Stanley-Jones" > > To: "Publican discussions" > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > Hi Rudi, > > > > You can see it at > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > The background is black and the XML tags are navy blue. You can > barely > > see the blue if you squint at the screenshot. Some things would > also > > be marked up as red or what turns out to be dark green. It would > all > > be fine if the background were white. > > > > Also I think the rounded divs are a bit tiresome, but that may be > > personal preference. > > > > Misty > > > > ----- "Ruediger Landmann" wrote: > > > > > From: "Ruediger Landmann" > > > To: "Publican discussions" > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > 5. Programlistings inside of notes, warnings, or infos look > > > terrible. > > > > Screenshot attached. > > > > > > Hi Misty -- Could you please clarify this a little? It's the only > > > point > > > that I don't quite understand. > > > > > > Do you just mean having white text on a black background? The > > strange > > > > > > formatting in your screenshot is probably a faithful > representation > > of > > > > > > the underlying XML. To reproduce something like it, I need to > > > introduce > > > extraneous whitespace and linebreaks into the . > > > > > > Cheers > > > Rudi > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican -------------- next part -------------- An HTML attachment was scrubbed... URL: From leecarlon at redhat.com Tue Oct 5 23:57:37 2010 From: leecarlon at redhat.com (Lee Carlon) Date: Tue, 5 Oct 2010 19:57:37 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <31643511.27.1286322905728.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Message-ID: <1547328940.1435491286323057348.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> I prefer the grey background, but both are preferable to what we currently have. Lee ----- Original Message ----- From: "Jared Morgan" To: "Misty Stanley-Jones" , "Publican discussions" Sent: Wednesday, October 6, 2010 9:52:30 AM GMT +10:00 Brisbane Subject: Re: [publican-list] RFE for Publican Brands I'm a big fan of the white background as well. You could then have a light grey or inside admonitions, which would remove the need for a 1px border. All you need to do now is work your mock-up magic on output, Misty. ;) Cheers Jared Morgan Content Author Red Hat Asia Pacific 1/193 North Quay BRISBANE QLD 4000 P: +61 7 3514 8242 M: +61 413 005 479 From: misty at redhat.com To: "Misty Stanley-Jones" Cc: "Publican discussions" Sent: Wednesday, October 6, 2010 9:36:21 AM Subject: Re: [publican-list] RFE for Publican Brands Attached are two mock-ups for admonitions. I really like the white, but I have a feeling the grey fits in more with our current styles. The only potential problem I see is that programlistings inside admonitions would be grey on grey (if I get my wish and we change the black to grey for programlistings and screens inside admonitions). If the block-level elements inside admonitions just have a 1px border, that problem is solved as well. Feedback is appreciated! Misty ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Misty Stanley-Jones" , "Publican discussions" > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > For the programlistings and screens inside admonitions, I vote for > having them display the same as if they were not in the admonition (I > think the background color is grey). > > For the note / info / warning, I think a thick border of the same > color as the current boxes, with either a grey interior or a much > lighter shade of the border color. I will try to come up with a > mock-up of what I have in mind. > > Misty > > ----- "Misty Stanley-Jones" wrote: > > > From: "Misty Stanley-Jones" > > To: "Publican discussions" > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > Hi Rudi, > > > > You can see it at > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > The background is black and the XML tags are navy blue. You can > barely > > see the blue if you squint at the screenshot. Some things would > also > > be marked up as red or what turns out to be dark green. It would > all > > be fine if the background were white. > > > > Also I think the rounded divs are a bit tiresome, but that may be > > personal preference. > > > > Misty > > > > ----- "Ruediger Landmann" wrote: > > > > > From: "Ruediger Landmann" > > > To: "Publican discussions" > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > 5. Programlistings inside of notes, warnings, or infos look > > > terrible. > > > > Screenshot attached. > > > > > > Hi Misty -- Could you please clarify this a little? It's the only > > > point > > > that I don't quite understand. > > > > > > Do you just mean having white text on a black background? The > > strange > > > > > > formatting in your screenshot is probably a faithful > representation > > of > > > > > > the underlying XML. To reproduce something like it, I need to > > > introduce > > > extraneous whitespace and linebreaks into the . > > > > > > Cheers > > > Rudi > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. _______________________________________________ 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 -- Lee Carlon Content Author Red Hat Asia Pacific 1/193 North Quay Brisbane QLD 4000 P + 61 7 35148107 From serogers at redhat.com Wed Oct 6 00:06:31 2010 From: serogers at redhat.com (Sean Rogers) Date: Tue, 5 Oct 2010 20:06:31 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1547328940.1435491286323057348.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> Message-ID: <203333352.1383511286323591802.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I prefer the grey too, though programlistings would need a border. ----- "Lee Carlon" wrote: | I prefer the grey background, but both are preferable to what we | currently have. | | Lee | | | ----- Original Message ----- | From: "Jared Morgan" | To: "Misty Stanley-Jones" , "Publican discussions" | | Sent: Wednesday, October 6, 2010 9:52:30 AM GMT +10:00 Brisbane | Subject: Re: [publican-list] RFE for Publican Brands | | I'm a big fan of the white background as well. You could then have a | light grey or inside admonitions, which | would remove the need for a 1px border. | | All you need to do now is work your mock-up magic on output, | Misty. ;) | | Cheers | | Jared Morgan | Content Author | Red Hat Asia Pacific | 1/193 North Quay | BRISBANE QLD 4000 | | P: +61 7 3514 8242 | M: +61 413 005 479 | | | From: misty at redhat.com | To: "Misty Stanley-Jones" | Cc: "Publican discussions" | Sent: Wednesday, October 6, 2010 9:36:21 AM | Subject: Re: [publican-list] RFE for Publican Brands | | Attached are two mock-ups for admonitions. I really like the white, | but I have a feeling the grey fits in more with our current styles. | The only potential problem I see is that programlistings inside | admonitions would be grey on grey (if I get my wish and we change the | black to grey for programlistings and screens inside admonitions). If | the block-level elements inside admonitions just have a 1px border, | that problem is solved as well. | | Feedback is appreciated! | | Misty | | ----- "Misty Stanley-Jones" wrote: | | > From: "Misty Stanley-Jones" | > To: "Misty Stanley-Jones" , "Publican discussions" | | > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane | > Subject: Re: [publican-list] RFE for Publican Brands | > | > For the programlistings and screens inside admonitions, I vote for | > having them display the same as if they were not in the admonition | (I | > think the background color is grey). | > | > For the note / info / warning, I think a thick border of the same | > color as the current boxes, with either a grey interior or a much | > lighter shade of the border color. I will try to come up with a | > mock-up of what I have in mind. | > | > Misty | > | > ----- "Misty Stanley-Jones" wrote: | > | > > From: "Misty Stanley-Jones" | > > To: "Publican discussions" | > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane | | > > Subject: Re: [publican-list] RFE for Publican Brands | > > | > > Hi Rudi, | > > | > > You can see it at | > > https://bugzilla.redhat.com/attachment.cgi?id=450610. | > > | > > The background is black and the XML tags are navy blue. You can | > barely | > > see the blue if you squint at the screenshot. Some things would | > also | > > be marked up as red or what turns out to be dark green. It would | > all | > > be fine if the background were white. | > > | > > Also I think the rounded divs are a bit tiresome, but that may be | | > > personal preference. | > > | > > Misty | > > | > > ----- "Ruediger Landmann" wrote: | > > | > > > From: "Ruediger Landmann" | > > > To: "Publican discussions" | > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 | Brisbane | > > > Subject: Re: [publican-list] RFE for Publican Brands | > > > | > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: | > > > > 5. Programlistings inside of notes, warnings, or infos look | > > > terrible. | > > > > Screenshot attached. | > > > | > > > Hi Misty -- Could you please clarify this a little? It's the | only | > > > point | > > > that I don't quite understand. | > > > | > > > Do you just mean having white text on a black background? The | > > strange | > > > | > > > formatting in your screenshot is probably a faithful | > representation | > > of | > > > | > > > the underlying XML. To reproduce something like it, I need to | > > > introduce | > > > extraneous whitespace and linebreaks into the . | | > > > | > > > Cheers | > > > Rudi | > > > | > > > _______________________________________________ | > > > publican-list mailing list | > > > publican-list at redhat.com | > > > https://www.redhat.com/mailman/listinfo/publican-list | > > > Wiki: https://fedorahosted.org/publican | > > | > > -- | > > Misty Stanley-Jones | > > Content Author, ECS Brisbane | > > Ph: +61 7 3514 8105 | > > RHCT #60501081553354 | > > Purgamentum init, exit purgamentum. | > > | > > _______________________________________________ | > > publican-list mailing list | > > publican-list at redhat.com | > > https://www.redhat.com/mailman/listinfo/publican-list | > > Wiki: https://fedorahosted.org/publican | > | > -- | > Misty Stanley-Jones | > Content Author, ECS Brisbane | > Ph: +61 7 3514 8105 | > RHCT #60501081553354 | > Purgamentum init, exit purgamentum. | | -- | Misty Stanley-Jones | Content Author, ECS Brisbane | Ph: +61 7 3514 8105 | RHCT #60501081553354 | Purgamentum init, exit purgamentum. | | _______________________________________________ | 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 | | -- | Lee Carlon | Content Author | Red Hat Asia Pacific | 1/193 North Quay | Brisbane QLD 4000 | | P + 61 7 35148107 | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From djorm at redhat.com Wed Oct 6 00:20:23 2010 From: djorm at redhat.com (David Jorm) Date: Tue, 5 Oct 2010 20:20:23 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <347841399.1108731286321781714.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <123433801.1384751286324423958.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Both are good. I like the flexibility of the white, in that whatever we render inside it, such as programlistings, appear exactly as they would outside an admonition. ----- Original Message ----- From: misty at redhat.com To: "Misty Stanley-Jones" Cc: "Publican discussions" Sent: Wednesday, October 6, 2010 9:36:21 AM GMT +10:00 Brisbane Subject: Re: [publican-list] RFE for Publican Brands Attached are two mock-ups for admonitions. I really like the white, but I have a feeling the grey fits in more with our current styles. The only potential problem I see is that programlistings inside admonitions would be grey on grey (if I get my wish and we change the black to grey for programlistings and screens inside admonitions). If the block-level elements inside admonitions just have a 1px border, that problem is solved as well. Feedback is appreciated! Misty ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Misty Stanley-Jones" , "Publican discussions" > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > For the programlistings and screens inside admonitions, I vote for > having them display the same as if they were not in the admonition (I > think the background color is grey). > > For the note / info / warning, I think a thick border of the same > color as the current boxes, with either a grey interior or a much > lighter shade of the border color. I will try to come up with a > mock-up of what I have in mind. > > Misty > > ----- "Misty Stanley-Jones" wrote: > > > From: "Misty Stanley-Jones" > > To: "Publican discussions" > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > Hi Rudi, > > > > You can see it at > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > The background is black and the XML tags are navy blue. You can > barely > > see the blue if you squint at the screenshot. Some things would > also > > be marked up as red or what turns out to be dark green. It would > all > > be fine if the background were white. > > > > Also I think the rounded divs are a bit tiresome, but that may be > > personal preference. > > > > Misty > > > > ----- "Ruediger Landmann" wrote: > > > > > From: "Ruediger Landmann" > > > To: "Publican discussions" > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > 5. Programlistings inside of notes, warnings, or infos look > > > terrible. > > > > Screenshot attached. > > > > > > Hi Misty -- Could you please clarify this a little? It's the only > > > point > > > that I don't quite understand. > > > > > > Do you just mean having white text on a black background? The > > strange > > > > > > formatting in your screenshot is probably a faithful > representation > > of > > > > > > the underlying XML. To reproduce something like it, I need to > > > introduce > > > extraneous whitespace and linebreaks into the . > > > > > > Cheers > > > Rudi > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Wed Oct 6 03:15:56 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 06 Oct 2010 13:15:56 +1000 Subject: [publican-list] Publican 2.2 Released Message-ID: <4CABE9EC.6060608@redhat.com> Hi everybody! Publican 2.2 has been release! Brew and Koji builds have been started so updates will be coming to a repo near you. I'd like to give a shout out to all the Fedora users, please become familiar with the updates testing process and add some karma to bodhi so we can get updates out to the main repositories sooner! Rudi will be following up with links to the bohdi jobs. There are a couple of new technologies in 2.2 that are basically tech previews, OPDS support and man page output. Man page support is pretty raw and untested, but without a preview it's unlikely to get tested robustly, so we are shipping it as is. OPDS support is fully functional, but the final decision on how to segment content has not been been made. We believe the current layout is workable and definitely good enough for people to use it, and hopefully the feedback we receive from it's use will help us nail down the final structure. OPDS support has lead to some changes to the web database and relocation of some settings from the home page publican.cfg file to the site.cfg file. If you are running your own site here are the changes you need to apply: $ sqlite3 .db ALTER TABLE main.books ADD COLUMN subtitle text; ALTER TABLE main.books ADD COLUMN abstract text; drop table settings; The settings that have moved from the home page publican.cfg to the site.cfg are: 1: def_lang, same format and name. 2: web_search, same format, renamed to search. 3: web_host, same format, renamed to host. Also there is a new site config value, title, which replaces 'Documentation' on the main index, TOC, and Sitemap files. If you want to take a look at the OPDS output, surf you mobile to http://docs.fedoraproject.org/opds.xml Change log for 2.2: - Extend callout graphics to 40; adjust colour and font BZ #629804 - Make keycombo example consistent with RHEL6 behaviour. BZ #618735 - Restrict CSS style for edition to title pages to avoid applying to bibliographies - Fix images/icon.svg breaking rpm build. BZ #612515 - Fix empty term breaking PDF build. BZ #614728 - Fix footnote not catching modified para. BZ #565903 - Fix SRPM not including web labels. BZ #621036 - Update tocs when home page is updated. BZ #612027 - Don't display stats for unused languages. BZ #613500 - Fix admonitions/varlistentry not having IDs. BZ #616112 - Fix procedure/itemizedlist/orderedlist not having IDs. BZ #612817 - Catch invalid revision in translation. BZ #621721 - Limit index.html redirection to installed languages. BZ #612009 - Fix smaller width being overridden by max_image_width. BZ #613140 - Fix support for def_lang for web sites. BZ #622030 - Remove ant trails from selected links. - Add --novalid option to disable validation when building. BZ #616142 - Revert change to escaping ', ", >, <. BZ #628266 - Add support for product and version splash pages. BZ #613502 - Fix unused version breaking product hiding. - Add support for alerts for parameters. - Add bash completion. - Validate revnumber for changelog. BZ #628464 - Add basic man page support. BZ #632027 - Add basic support for line numbers. BZ #629463 - Add warning messages for out of date translations. - Add productname to IGNOREBLOCKS. BZ #625316 - Add OPDS support. BZ #615831 - Fix translated labels in web nav. BZ #631647 - Remove highlighting from output of prompt tag in html. BZ #618902 - Resize index title font to a sane size. BZ #624392 - Fix misapplied fonts for CJK. BZ #628786 - Fix attributes breaking translation merge. BZ #638816 - Fix entities missing from RPM description. BZ #626254 - Add bridgehead_in_toc parameter. BZ #616123 - Support '--lang all' for lang_stats. - Left align CJK in PDF. BZ #639811 - Fix constraint regex on docname and productname. BZ #640082 Special thanks to Rudi and Ryan who have, yet again, proven invaluable for getting another Publican release out the door! Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Wed Oct 6 04:29:18 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 06 Oct 2010 14:29:18 +1000 Subject: [publican-list] Publican 2.2 Released In-Reply-To: <4CABE9EC.6060608@redhat.com> References: <4CABE9EC.6060608@redhat.com> Message-ID: <4CABFB1E.2060902@redhat.com> Jeffrey Fearn wrote: > - Add support for product and version splash pages. BZ #613502 Hi again, it's not apparent from the above, but this feature included automation of the navigation area to display the current page. So if you send someone a link the navigation area pops down. e.g. if you visit http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/index.html then Fedora is expanded and version 14 is expanded. If you click "collapse all" and refresh the page the navigation will reopen to the same way. Unfortunately this feature requires books be rebuilt before it will work ... a mass rebuild is being scheduled for Fedora docs and Red Hat docs sites. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From r.landmann at redhat.com Wed Oct 6 05:10:46 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 06 Oct 2010 15:10:46 +1000 Subject: [publican-list] Publican 2.2 Released In-Reply-To: <4CABE9EC.6060608@redhat.com> References: <4CABE9EC.6060608@redhat.com> Message-ID: <4CAC04D6.20303@redhat.com> On 10/06/2010 01:15 PM, Jeffrey Fearn wrote: > Hi everybody! Publican 2.2 has been release! Brew and Koji builds have > been started so updates will be coming to a repo near you. > > I'd like to give a shout out to all the Fedora users, please become > familiar with the updates testing process and add some karma to bodhi > so we can get updates out to the main repositories sooner! Rudi will > be following up with links to the bohdi jobs. Thanks Jeff :) Anyone using Fedora 12 or Fedora 13 can download and install the package from Koji [0] If Publican 2.2 works for you on Fedora, please leave positive karma in Bodhi so that Publican 2.2 reaches the main Fedora repos sooner.[1] Note that you must be logged in, or your karma won't count. Cheers Rudi [0] Fedora 13 -- http://kojipkgs.fedoraproject.org/packages/publican/2.2/0.fc13/noarch/publican-2.2-0.fc13.noarch.rpm or Fedora 12 -- http://kojipkgs.fedoraproject.org/packages/publican/2.2/0.fc12/noarch/publican-2.2-0.fc12.noarch.rpm [1] Fedora 13 -- https://admin.fedoraproject.org/updates/publican-2.2-0.fc13 or Fedora 12 -- https://admin.fedoraproject.org/updates/publican-2.2-0.fc12 From misty at redhat.com Thu Oct 7 01:46:56 2010 From: misty at redhat.com (misty at redhat.com) Date: Wed, 6 Oct 2010 21:46:56 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1339798354.130471286416009582.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <1839842473.130491286416016372.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Here is a mock-up for examples. I've done the following: 1. Added a white inner div to hold the programlisting and any accompanying text. 2. Placed the title of the example at the top of the outer div rather than the bottom. 2a. Darkened the color of the example title text. I think this color would be better for section headings and wherever else it is used. 3. Added a darker grey border around the programlisting to make it stand out more against the white background. This is very sloppy and would be a 1px grey border ideally. 4. Made the width of the programlisting block (in theory) the same as the width of the text beneath it. I'm undecided on whether the programlisting box should have rounded edges or not. I've sort of left one corner rounded, and I'm looking for comment either way. The color codes used are: Example background: #dc9f2e (same as always) Inner div background: #ffffff Example title: #6c1313 Programlisting background: #eeeeee Programlisting background border: #c5c5c5 ----- misty at redhat.com wrote: > From: misty at redhat.com > To: "Misty Stanley-Jones" > Cc: "Publican discussions" > Sent: Wednesday, October 6, 2010 9:36:21 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > Attached are two mock-ups for admonitions. I really like the white, > but I have a feeling the grey fits in more with our current styles. > The only potential problem I see is that programlistings inside > admonitions would be grey on grey (if I get my wish and we change the > black to grey for programlistings and screens inside admonitions). If > the block-level elements inside admonitions just have a 1px border, > that problem is solved as well. > > Feedback is appreciated! > > Misty > > ----- "Misty Stanley-Jones" wrote: > > > From: "Misty Stanley-Jones" > > To: "Misty Stanley-Jones" , "Publican discussions" > > > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > For the programlistings and screens inside admonitions, I vote for > > having them display the same as if they were not in the admonition > (I > > think the background color is grey). > > > > For the note / info / warning, I think a thick border of the same > > color as the current boxes, with either a grey interior or a much > > lighter shade of the border color. I will try to come up with a > > mock-up of what I have in mind. > > > > Misty > > > > ----- "Misty Stanley-Jones" wrote: > > > > > From: "Misty Stanley-Jones" > > > To: "Publican discussions" > > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > Hi Rudi, > > > > > > You can see it at > > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > > > The background is black and the XML tags are navy blue. You can > > barely > > > see the blue if you squint at the screenshot. Some things would > > also > > > be marked up as red or what turns out to be dark green. It would > > all > > > be fine if the background were white. > > > > > > Also I think the rounded divs are a bit tiresome, but that may be > > > personal preference. > > > > > > Misty > > > > > > ----- "Ruediger Landmann" wrote: > > > > > > > From: "Ruediger Landmann" > > > > To: "Publican discussions" > > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 > Brisbane > > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > > 5. Programlistings inside of notes, warnings, or infos look > > > > terrible. > > > > > Screenshot attached. > > > > > > > > Hi Misty -- Could you please clarify this a little? It's the > only > > > > point > > > > that I don't quite understand. > > > > > > > > Do you just mean having white text on a black background? The > > > strange > > > > > > > > formatting in your screenshot is probably a faithful > > representation > > > of > > > > > > > > the underlying XML. To reproduce something like it, I need to > > > > introduce > > > > extraneous whitespace and linebreaks into the . > > > > > > > > Cheers > > > > Rudi > > > > > > > > _______________________________________________ > > > > publican-list mailing list > > > > publican-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/publican-list > > > > Wiki: https://fedorahosted.org/publican > > > > > > -- > > > Misty Stanley-Jones > > > Content Author, ECS Brisbane > > > Ph: +61 7 3514 8105 > > > RHCT #60501081553354 > > > Purgamentum init, exit purgamentum. > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. -------------- next part -------------- A non-text attachment was scrubbed... Name: examples_mockup.png Type: image/png Size: 45493 bytes Desc: not available URL: From jmorgan at redhat.com Thu Oct 7 03:30:26 2010 From: jmorgan at redhat.com (Jared Morgan) Date: Wed, 6 Oct 2010 23:30:26 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1839842473.130491286416016372.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <28120464.115.1286422384837.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> I really like the look of this for the Examples. The white inner div really breaks up the example box, and makes programlistings jump out. Looks great. Jared Morgan Content Author Red Hat Asia Pacific 1/193 North Quay BRISBANE QLD 4000 P: +61 7 3514 8242 M: +61 413 005 479 From: misty at redhat.com To: "Misty Stanley-Jones" Cc: "Publican discussions" Sent: Thursday, October 7, 2010 11:46:56 AM Subject: Re: [publican-list] RFE for Publican Brands Here is a mock-up for examples. I've done the following: 1. Added a white inner div to hold the programlisting and any accompanying text. 2. Placed the title of the example at the top of the outer div rather than the bottom. 2a. Darkened the color of the example title text. I think this color would be better for section headings and wherever else it is used. 3. Added a darker grey border around the programlisting to make it stand out more against the white background. This is very sloppy and would be a 1px grey border ideally. 4. Made the width of the programlisting block (in theory) the same as the width of the text beneath it. I'm undecided on whether the programlisting box should have rounded edges or not. I've sort of left one corner rounded, and I'm looking for comment either way. The color codes used are: Example background: #dc9f2e (same as always) Inner div background: #ffffff Example title: #6c1313 Programlisting background: #eeeeee Programlisting background border: #c5c5c5 ----- misty at redhat.com wrote: > From: misty at redhat.com > To: "Misty Stanley-Jones" > Cc: "Publican discussions" > Sent: Wednesday, October 6, 2010 9:36:21 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > Attached are two mock-ups for admonitions. I really like the white, > but I have a feeling the grey fits in more with our current styles. > The only potential problem I see is that programlistings inside > admonitions would be grey on grey (if I get my wish and we change the > black to grey for programlistings and screens inside admonitions). If > the block-level elements inside admonitions just have a 1px border, > that problem is solved as well. > > Feedback is appreciated! > > Misty > > ----- "Misty Stanley-Jones" wrote: > > > From: "Misty Stanley-Jones" > > To: "Misty Stanley-Jones" , "Publican discussions" > > > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > For the programlistings and screens inside admonitions, I vote for > > having them display the same as if they were not in the admonition > (I > > think the background color is grey). > > > > For the note / info / warning, I think a thick border of the same > > color as the current boxes, with either a grey interior or a much > > lighter shade of the border color. I will try to come up with a > > mock-up of what I have in mind. > > > > Misty > > > > ----- "Misty Stanley-Jones" wrote: > > > > > From: "Misty Stanley-Jones" > > > To: "Publican discussions" > > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > Hi Rudi, > > > > > > You can see it at > > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > > > The background is black and the XML tags are navy blue. You can > > barely > > > see the blue if you squint at the screenshot. Some things would > > also > > > be marked up as red or what turns out to be dark green. It would > > all > > > be fine if the background were white. > > > > > > Also I think the rounded divs are a bit tiresome, but that may be > > > personal preference. > > > > > > Misty > > > > > > ----- "Ruediger Landmann" wrote: > > > > > > > From: "Ruediger Landmann" > > > > To: "Publican discussions" > > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 > Brisbane > > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > > 5. Programlistings inside of notes, warnings, or infos look > > > > terrible. > > > > > Screenshot attached. > > > > > > > > Hi Misty -- Could you please clarify this a little? It's the > only > > > > point > > > > that I don't quite understand. > > > > > > > > Do you just mean having white text on a black background? The > > > strange > > > > > > > > formatting in your screenshot is probably a faithful > > representation > > > of > > > > > > > > the underlying XML. To reproduce something like it, I need to > > > > introduce > > > > extraneous whitespace and linebreaks into the . > > > > > > > > Cheers > > > > Rudi > > > > > > > > _______________________________________________ > > > > publican-list mailing list > > > > publican-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/publican-list > > > > Wiki: https://fedorahosted.org/publican > > > > > > -- > > > Misty Stanley-Jones > > > Content Author, ECS Brisbane > > > Ph: +61 7 3514 8105 > > > RHCT #60501081553354 > > > Purgamentum init, exit purgamentum. > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Fri Oct 8 00:47:55 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 7 Oct 2010 20:47:55 -0400 Subject: [publican-list] [Bug 494147] PDF: Articles do not include author information (orgdiv, orgname, etc) In-Reply-To: References: Message-ID: <201010080047.o980ltnM016671@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=494147 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|needinfo? | --- Comment #6 from Jeff Fearn 2010-10-07 20:47:54 EDT --- https://fedorahosted.org/publican/wiki/WishList#Differentformattingforarticlebasedonclass -- 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 lbrindle at redhat.com Sun Oct 10 08:04:33 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Sun, 10 Oct 2010 19:04:33 +1100 Subject: [publican-list] Fwd: Re: reading our docs on the Kindle Message-ID: <4CB17391.9080109@redhat.com> Forwarding to the Publican ML for further discussion. L -------- Original Message -------- Subject: Re: reading our docs on the Kindle Date: Fri, 08 Oct 2010 21:05:19 -0500 From: Will Benton To: mrg-grid-internal at redhat.com Sorry, I forgot to attach the converted-document screenshots from my Kindle. They're on this message. On 10/08/2010 09:03 PM, Will Benton wrote: > Hi all, > > I've been thinking about reading our documentation on the Kindle for a > while and, after talking with William about it on IRC today, decided to > do something about it. I'm sending out a note about my experience in > case it's generally useful. > > Of course, the PDFs we distribute are fine on the Kindle, but I > suspected that a native ebook format might be more successful on the > smaller screen of the third-generation Kindle. The epub files we > distribute are fine for many ebook readers; they look pretty good in > Stanza on the iPhone, for example (see stanza-epub-title-page.PNG and > stanza-epub-typefaces.PNG). Unfortunately, the Kindle cannot natively > display epub files. > > I tried a few options: > > 1. converting .epub files to Kindle ebooks using Amazon's free-beer > kindlegen application. This failed due to some bogus or missing metadata > in the table of contents for our epub docs. > > 2. emailing the .epub files to my @kindle.com email address and hoping > that Amazon would automatically convert them for me. This also failed; > Amazon's automatic converter doesn't handle epub files. > > 3. using the open-source Calibre application to convert .epub to .mobi > or .azw. This also failed, although it did so while cheerfully (but > hideously, as only a Java GUI application with custom icons can do) > giving the impression that it had actually converted the files. > Obviously, YMMV here if you can get it to work. > > 4. using the free-beer desktop version of Stanza to convert the files to > .azw or .mobi (I tried both). This actually resulted in something I > could use on the Kindle, but it stripped all but the barest of > formatting (including all fonts), which makes for pretty unpleasant > reading. (See kindle1.gif and kindle2.gif) > > None of these turned out to be particularly satisfactory. It is possible > to produce decent .mobi files that respect technical-documentation > conventions (the DRM-free .mobi ebooks from O'Reilly and the Pragmatic > Programmers are great on Kindle); I'm just not sure how to do it. > Perhaps there's a decent tool that goes straight from DocBook to mobi? > > > > best, > wb > -- William C. Benton Senior Software Engineer, Red Hat MRG -------------- next part -------------- A non-text attachment was scrubbed... Name: kindle1.gif Type: image/gif Size: 36688 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: kindle2.gif Type: image/gif Size: 31195 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: lbrindle.vcf Type: text/x-vcard Size: 976 bytes Desc: not available URL: From bugzilla at redhat.com Sun Oct 10 23:24:00 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:24:00 -0400 Subject: [publican-list] [Bug 604255] Problem with callouts In-Reply-To: References: Message-ID: <201010102324.o9ANO0b3025664@bzweb02.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=604255 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmcallis at redhat.com Component|publican |publican Version|5.7 |13 Product|Red Hat Enterprise Linux 5 |Fedora Target Milestone|rc |--- QAContact|ecs-bugs at redhat.com |extras-qa at fedoraproject.org -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:26:06 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:26:06 -0400 Subject: [publican-list] [Bug 604255] Problem with callouts In-Reply-To: References: Message-ID: <201010102326.o9ANQ6IU014449@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=604255 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Fixed In Version|2.2 |publican-2.2-0.fc13 Resolution| |ERRATA Last Closed| |2010-10-10 19:26:05 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:26:12 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:26:12 -0400 Subject: [publican-list] [Bug 638816] attributes in tags break translation merge In-Reply-To: References: Message-ID: <201010102326.o9ANQCdt014499@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=638816 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Fixed In Version| |publican-2.2-0.fc13 Resolution| |ERRATA Last Closed| |2010-10-10 19:26:12 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:26:10 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:26:10 -0400 Subject: [publican-list] [Bug 616112] IDs not set on admonitions or varlistentry In-Reply-To: References: Message-ID: <201010102326.o9ANQAqm014480@bzweb01.app.bz.hst.phx2.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=616112 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Fixed In Version|2.2 |publican-2.2-0.fc13 Resolution| |ERRATA Last Closed| |2010-10-10 19:26:09 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:26:11 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:26:11 -0400 Subject: [publican-list] [Bug 631647] Book titles appear in English even when other language is selected In-Reply-To: References: Message-ID: <201010102326.o9ANQB54014492@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=631647 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Fixed In Version| |publican-2.2-0.fc13 Resolution| |ERRATA Last Closed| |2010-10-10 19:26:11 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:26:09 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:26:09 -0400 Subject: [publican-list] [Bug 625316] publican break tags into separate paragraphs in .po files. In-Reply-To: References: Message-ID: <201010102326.o9ANQ9Me014473@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=625316 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Fixed In Version| |publican-2.2-0.fc13 Resolution| |ERRATA Last Closed| |2010-10-10 19:26:09 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:24:54 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:24:54 -0400 Subject: [publican-list] [Bug 638816] attributes in tags break translation merge In-Reply-To: References: Message-ID: <201010102324.o9ANOsjr025809@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=638816 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmcallis at redhat.com, | |r.landmann at redhat.com Component|publican |publican Version|5.5 |13 AssignedTo|mhideo at redhat.com |jfearn at redhat.com Product|Red Hat Enterprise Linux 5 |Fedora Target Milestone|rc |--- QAContact|ecs-bugs at redhat.com |extras-qa at fedoraproject.org -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:24:33 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:24:33 -0400 Subject: [publican-list] [Bug 631647] Book titles appear in English even when other language is selected In-Reply-To: References: Message-ID: <201010102324.o9ANOX8J025770@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=631647 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmcallis at redhat.com, | |r.landmann at redhat.com Component|publican |publican Version|5.5 |13 AssignedTo|mhideo at redhat.com |jfearn at redhat.com Product|Red Hat Enterprise Linux 5 |Fedora Target Milestone|rc |--- QAContact|ecs-bugs at redhat.com |extras-qa at fedoraproject.org -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Oct 10 23:24:11 2010 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 10 Oct 2010 19:24:11 -0400 Subject: [publican-list] [Bug 625316] publican break tags into separate paragraphs in .po files. In-Reply-To: References: Message-ID: <201010102324.o9ANOBAL025719@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=625316 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmcallis at redhat.com, | |r.landmann at redhat.com Component|publican |publican Version|5.5 |13 AssignedTo|mhideo at redhat.com |jfearn at redhat.com Product|Red Hat Enterprise Linux 5 |Fedora Target Milestone|rc |--- QAContact|ecs-bugs at redhat.com |extras-qa at fedoraproject.org -- 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 djorm at redhat.com Mon Oct 11 03:51:24 2010 From: djorm at redhat.com (David Jorm) Date: Sun, 10 Oct 2010 23:51:24 -0400 (EDT) Subject: [publican-list] Fwd: Re: reading our docs on the Kindle In-Reply-To: <1194220535.40201286768937827.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1438721434.40251286769084307.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> "On July 17, 2009, Amazon.com withdrew certain Kindle titles, Animal Farm and Nineteen Eighty-Four by George Orwell, from sale, refunded the cost to those who had purchased them, and remotely deleted these titles from purchasers' devices after discovering that the publisher lacked rights to publish the titles in question." Source: http://pogue.blogs.nytimes.com/2009/07/17/some-e-books-are-more-equal-than-others/ Just sayin'... ----- Original Message ----- From: "Lana Brindley" To: "publican" Cc: "Will Benton" Sent: Sunday, October 10, 2010 6:04:33 PM GMT +10:00 Brisbane Subject: [publican-list] Fwd: Re: reading our docs on the Kindle Forwarding to the Publican ML for further discussion. L -------- Original Message -------- Subject: Re: reading our docs on the Kindle Date: Fri, 08 Oct 2010 21:05:19 -0500 From: Will Benton To: mrg-grid-internal at redhat.com Sorry, I forgot to attach the converted-document screenshots from my Kindle. They're on this message. On 10/08/2010 09:03 PM, Will Benton wrote: > Hi all, > > I've been thinking about reading our documentation on the Kindle for a > while and, after talking with William about it on IRC today, decided to > do something about it. I'm sending out a note about my experience in > case it's generally useful. > > Of course, the PDFs we distribute are fine on the Kindle, but I > suspected that a native ebook format might be more successful on the > smaller screen of the third-generation Kindle. The epub files we > distribute are fine for many ebook readers; they look pretty good in > Stanza on the iPhone, for example (see stanza-epub-title-page.PNG and > stanza-epub-typefaces.PNG). Unfortunately, the Kindle cannot natively > display epub files. > > I tried a few options: > > 1. converting .epub files to Kindle ebooks using Amazon's free-beer > kindlegen application. This failed due to some bogus or missing metadata > in the table of contents for our epub docs. > > 2. emailing the .epub files to my @kindle.com email address and hoping > that Amazon would automatically convert them for me. This also failed; > Amazon's automatic converter doesn't handle epub files. > > 3. using the open-source Calibre application to convert .epub to .mobi > or .azw. This also failed, although it did so while cheerfully (but > hideously, as only a Java GUI application with custom icons can do) > giving the impression that it had actually converted the files. > Obviously, YMMV here if you can get it to work. > > 4. using the free-beer desktop version of Stanza to convert the files to > .azw or .mobi (I tried both). This actually resulted in something I > could use on the Kindle, but it stripped all but the barest of > formatting (including all fonts), which makes for pretty unpleasant > reading. (See kindle1.gif and kindle2.gif) > > None of these turned out to be particularly satisfactory. It is possible > to produce decent .mobi files that respect technical-documentation > conventions (the DRM-free .mobi ebooks from O'Reilly and the Pragmatic > Programmers are great on Kindle); I'm just not sure how to do it. > Perhaps there's a decent tool that goes straight from DocBook to mobi? > > > > best, > wb > -- William C. Benton Senior Software Engineer, Red Hat MRG _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From misty at redhat.com Mon Oct 11 03:57:01 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Sun, 10 Oct 2010 23:57:01 -0400 (EDT) Subject: [publican-list] Fwd: Re: reading our docs on the Kindle In-Reply-To: <1438721434.40251286769084307.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <240713534.60491286769421920.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> And Bezos' response to that: http://kindleworld.blogspot.com/2010/09/how-amazon-handled-recent-illegal-book.html ----- "David Jorm" wrote: > From: "David Jorm" > To: "Publican discussions" > Cc: "Will Benton" > Sent: Monday, October 11, 2010 1:51:24 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] Fwd: Re: reading our docs on the Kindle > > "On July 17, 2009, Amazon.com withdrew certain Kindle titles, Animal > Farm and Nineteen Eighty-Four by George Orwell, from sale, refunded > the cost to those who had purchased them, and remotely deleted these > titles from purchasers' devices after discovering that the publisher > lacked rights to publish the titles in question." > > Source: > http://pogue.blogs.nytimes.com/2009/07/17/some-e-books-are-more-equal-than-others/ > > Just sayin'... > > ----- Original Message ----- > From: "Lana Brindley" > To: "publican" > Cc: "Will Benton" > Sent: Sunday, October 10, 2010 6:04:33 PM GMT +10:00 Brisbane > Subject: [publican-list] Fwd: Re: reading our docs on the Kindle > > Forwarding to the Publican ML for further discussion. > > L > > -------- Original Message -------- > Subject: Re: reading our docs on the Kindle > Date: Fri, 08 Oct 2010 21:05:19 -0500 > From: Will Benton > To: mrg-grid-internal at redhat.com > > Sorry, I forgot to attach the converted-document screenshots from my > Kindle. They're on this message. > > On 10/08/2010 09:03 PM, Will Benton wrote: > > Hi all, > > > > I've been thinking about reading our documentation on the Kindle for > a > > while and, after talking with William about it on IRC today, decided > to > > do something about it. I'm sending out a note about my experience > in > > case it's generally useful. > > > > Of course, the PDFs we distribute are fine on the Kindle, but I > > suspected that a native ebook format might be more successful on > the > > smaller screen of the third-generation Kindle. The epub files we > > distribute are fine for many ebook readers; they look pretty good > in > > Stanza on the iPhone, for example (see stanza-epub-title-page.PNG > and > > stanza-epub-typefaces.PNG). Unfortunately, the Kindle cannot > natively > > display epub files. > > > > I tried a few options: > > > > 1. converting .epub files to Kindle ebooks using Amazon's free-beer > > kindlegen application. This failed due to some bogus or missing > metadata > > in the table of contents for our epub docs. > > > > 2. emailing the .epub files to my @kindle.com email address and > hoping > > that Amazon would automatically convert them for me. This also > failed; > > Amazon's automatic converter doesn't handle epub files. > > > > 3. using the open-source Calibre application to convert .epub to > .mobi > > or .azw. This also failed, although it did so while cheerfully (but > > hideously, as only a Java GUI application with custom icons can do) > > giving the impression that it had actually converted the files. > > Obviously, YMMV here if you can get it to work. > > > > 4. using the free-beer desktop version of Stanza to convert the > files to > > .azw or .mobi (I tried both). This actually resulted in something I > > could use on the Kindle, but it stripped all but the barest of > > formatting (including all fonts), which makes for pretty unpleasant > > reading. (See kindle1.gif and kindle2.gif) > > > > None of these turned out to be particularly satisfactory. It is > possible > > to produce decent .mobi files that respect technical-documentation > > conventions (the DRM-free .mobi ebooks from O'Reilly and the > Pragmatic > > Programmers are great on Kindle); I'm just not sure how to do it. > > Perhaps there's a decent tool that goes straight from DocBook to > mobi? > > > > > > > > best, > > wb > > > > > -- > William C. Benton > Senior Software Engineer, Red Hat MRG > > > _______________________________________________ > 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 -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From leecarlon at redhat.com Mon Oct 11 03:59:51 2010 From: leecarlon at redhat.com (leecarlon at redhat.com) Date: Sun, 10 Oct 2010 23:59:51 -0400 (EDT) Subject: [publican-list] Fwd: Re: reading our docs on the Kindle In-Reply-To: <1807743625.74051286769406098.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> Message-ID: <1775907573.74131286769591046.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> ----- "David Jorm" wrote: > "On July 17, 2009, Amazon.com withdrew certain Kindle titles, Animal > Farm and Nineteen Eighty-Four by George Orwell, from sale, refunded > the cost to those who had purchased them, and remotely deleted these > titles from purchasers' devices after discovering that the publisher > lacked rights to publish the titles in question." If only they'd done that on April 1st it would have been fantastic. Also, kinda cool if they did it after you'd finished reading the books. (full disclosure - I love my kindle) > > Source: > http://pogue.blogs.nytimes.com/2009/07/17/some-e-books-are-more-equal-than-others/ > > Just sayin'... > From misty at redhat.com Mon Oct 11 05:17:11 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Mon, 11 Oct 2010 01:17:11 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1839842473.130491286416016372.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <914586185.62151286774231031.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Jeff, now that we have given you a definite idea of what we would like to see, do you think this is something that you will be able to do, or show us how to do to the JBoss brand? I want to make sure this request doesn't go into a black hole. Thanks, Misty ----- misty at redhat.com wrote: > From: misty at redhat.com > To: "Misty Stanley-Jones" > Cc: "Publican discussions" > Sent: Thursday, October 7, 2010 11:46:56 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > Here is a mock-up for examples. I've done the following: > > 1. Added a white inner div to hold the programlisting and any > accompanying text. > 2. Placed the title of the example at the top of the outer div rather > than the bottom. > 2a. Darkened the color of the example title text. I think this color > would be better for section headings and wherever else it is used. > 3. Added a darker grey border around the programlisting to make it > stand out more against the white background. This is very sloppy and > would be a 1px grey border ideally. > 4. Made the width of the programlisting block (in theory) the same as > the width of the text beneath it. > > I'm undecided on whether the programlisting box should have rounded > edges or not. I've sort of left one corner rounded, and I'm looking > for comment either way. > > The color codes used are: > Example background: #dc9f2e (same as always) > Inner div background: #ffffff > Example title: #6c1313 > Programlisting background: #eeeeee > Programlisting background border: #c5c5c5 > > ----- misty at redhat.com wrote: > > > From: misty at redhat.com > > To: "Misty Stanley-Jones" > > Cc: "Publican discussions" > > Sent: Wednesday, October 6, 2010 9:36:21 AM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > Attached are two mock-ups for admonitions. I really like the white, > > but I have a feeling the grey fits in more with our current styles. > > The only potential problem I see is that programlistings inside > > admonitions would be grey on grey (if I get my wish and we change > the > > black to grey for programlistings and screens inside admonitions). > If > > the block-level elements inside admonitions just have a 1px border, > > that problem is solved as well. > > > > Feedback is appreciated! > > > > Misty > > > > ----- "Misty Stanley-Jones" wrote: > > > > > From: "Misty Stanley-Jones" > > > To: "Misty Stanley-Jones" , "Publican > discussions" > > > > > Sent: Monday, October 4, 2010 8:46:38 AM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > For the programlistings and screens inside admonitions, I vote > for > > > having them display the same as if they were not in the > admonition > > (I > > > think the background color is grey). > > > > > > For the note / info / warning, I think a thick border of the same > > > color as the current boxes, with either a grey interior or a much > > > lighter shade of the border color. I will try to come up with a > > > mock-up of what I have in mind. > > > > > > Misty > > > > > > ----- "Misty Stanley-Jones" wrote: > > > > > > > From: "Misty Stanley-Jones" > > > > To: "Publican discussions" > > > > Sent: Thursday, September 30, 2010 3:49:24 PM GMT +10:00 > Brisbane > > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > > > Hi Rudi, > > > > > > > > You can see it at > > > > https://bugzilla.redhat.com/attachment.cgi?id=450610. > > > > > > > > The background is black and the XML tags are navy blue. You can > > > barely > > > > see the blue if you squint at the screenshot. Some things would > > > also > > > > be marked up as red or what turns out to be dark green. It > would > > > all > > > > be fine if the background were white. > > > > > > > > Also I think the rounded divs are a bit tiresome, but that may > be > > > > personal preference. > > > > > > > > Misty > > > > > > > > ----- "Ruediger Landmann" wrote: > > > > > > > > > From: "Ruediger Landmann" > > > > > To: "Publican discussions" > > > > > Sent: Thursday, September 30, 2010 3:33:18 PM GMT +10:00 > > Brisbane > > > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > > > > > On 09/30/2010 03:16 PM, Misty Stanley-Jones wrote: > > > > > > 5. Programlistings inside of notes, warnings, or infos look > > > > > terrible. > > > > > > Screenshot attached. > > > > > > > > > > Hi Misty -- Could you please clarify this a little? It's the > > only > > > > > point > > > > > that I don't quite understand. > > > > > > > > > > Do you just mean having white text on a black background? The > > > > strange > > > > > > > > > > formatting in your screenshot is probably a faithful > > > representation > > > > of > > > > > > > > > > the underlying XML. To reproduce something like it, I need to > > > > > introduce > > > > > extraneous whitespace and linebreaks into the > . > > > > > > > > > > Cheers > > > > > Rudi > > > > > > > > > > _______________________________________________ > > > > > publican-list mailing list > > > > > publican-list at redhat.com > > > > > https://www.redhat.com/mailman/listinfo/publican-list > > > > > Wiki: https://fedorahosted.org/publican > > > > > > > > -- > > > > Misty Stanley-Jones > > > > Content Author, ECS Brisbane > > > > Ph: +61 7 3514 8105 > > > > RHCT #60501081553354 > > > > Purgamentum init, exit purgamentum. > > > > > > > > _______________________________________________ > > > > publican-list mailing list > > > > publican-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/publican-list > > > > Wiki: https://fedorahosted.org/publican > > > > > > -- > > > Misty Stanley-Jones > > > Content Author, ECS Brisbane > > > Ph: +61 7 3514 8105 > > > RHCT #60501081553354 > > > Purgamentum init, exit purgamentum. > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From jfearn at redhat.com Mon Oct 11 05:56:40 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 11 Oct 2010 15:56:40 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <914586185.62151286774231031.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <914586185.62151286774231031.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1286776600.2859.45.camel@captcha> On Mon, 2010-10-11 at 01:17 -0400, Misty Stanley-Jones wrote: > Jeff, now that we have given you a definite idea of what we would like to see, None of the people who have credibility in the layout area have given any feed back on your suggestions. Personally I wasn't that enamoured by them, but then again, I don't have much credibility in layout or design. > do you think this is something that you will be able to do, or show us how to do to the JBoss brand? I want to make sure this request doesn't go into a black hole. I had a chat with Rudi last week and he agreed to run a Lunch and learn on creating and customising brands. He assured me he would post details about it soon. Personally I'd love to see the brands removed from the publican repo, handed off to the teams responsible for the docs. Maybe a LnL will make that achievable. 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 misty at redhat.com Mon Oct 11 05:59:40 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Mon, 11 Oct 2010 01:59:40 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286776600.2859.45.camel@captcha> Message-ID: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Jeff Fearn" wrote: > > None of the people who have credibility in the layout area have given > any feed back on your suggestions. > Who are these people? -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From jfearn at redhat.com Mon Oct 11 06:02:58 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 11 Oct 2010 16:02:58 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1286776978.2859.47.camel@captcha> On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: > ----- "Jeff Fearn" wrote: > > > > > None of the people who have credibility in the layout area have given > > any feed back on your suggestions. > > > > Who are these people? Ryan, Brian, and Rudi ... I hear Brian has an excuse :( 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 jwulf at redhat.com Mon Oct 11 06:07:17 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 11 Oct 2010 16:07:17 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286776978.2859.47.camel@captcha> References: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286776978.2859.47.camel@captcha> Message-ID: <4CB2A995.3040200@redhat.com> On 10/11/2010 04:02 PM, Jeff Fearn wrote: > On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: >> ----- "Jeff Fearn" wrote: >> >>> >>> None of the people who have credibility in the layout area have given >>> any feed back on your suggestions. >>> >> >> Who are these people? > > Ryan, Brian, and Rudi ... I hear Brian has an excuse :( > > Cheers, Jeff. > "Brian" and "Ryan" are practically the same - the only difference is a single letter, "B". Rudi - another four letter name starting with "R". Coincidence - or conspiracy? From misty at redhat.com Mon Oct 11 06:13:05 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Mon, 11 Oct 2010 02:13:05 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286776978.2859.47.camel@captcha> Message-ID: <1415415735.63921286777585058.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> How do we go about getting someone in Middleware some credibility? Surely it is not such a scarce commodity that it can't be spread around a bit. I think we'd like a hand in the look and feel of our docs, if we can ever build up the credibility. Misty ----- "Jeff Fearn" wrote: > From: "Jeff Fearn" > To: "Misty Stanley-Jones" > Cc: "Publican discussions" > Sent: Monday, October 11, 2010 4:02:58 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: > > ----- "Jeff Fearn" wrote: > > > > > > > > None of the people who have credibility in the layout area have > given > > > any feed back on your suggestions. > > > > > > > Who are these people? > > Ryan, Brian, and Rudi ... I hear Brian has an excuse :( > > 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 -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From serogers at redhat.com Mon Oct 11 06:14:47 2010 From: serogers at redhat.com (Sean Rogers) Date: Mon, 11 Oct 2010 02:14:47 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CB2A995.3040200@redhat.com> Message-ID: <2068822009.43721286777687661.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> How does one achieve credibility in the layout area? ----- "Joshua Wulf" wrote: | On 10/11/2010 04:02 PM, Jeff Fearn wrote: | > On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: | >> ----- "Jeff Fearn" wrote: | >> | >>> | >>> None of the people who have credibility in the layout area have | given | >>> any feed back on your suggestions. | >>> | >> | >> Who are these people? | > | > Ryan, Brian, and Rudi ... I hear Brian has an excuse :( | > | > Cheers, Jeff. | > | | "Brian" and "Ryan" are practically the same - the only difference is | a | single letter, "B". Rudi - another four letter name starting with | "R". | Coincidence - or conspiracy? | | | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jwulf at redhat.com Mon Oct 11 06:16:45 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 11 Oct 2010 16:16:45 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286776978.2859.47.camel@captcha> References: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286776978.2859.47.camel@captcha> Message-ID: <4CB2ABCD.3040009@redhat.com> On 10/11/2010 04:02 PM, Jeff Fearn wrote: > On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: >> ----- "Jeff Fearn" wrote: >> >>> >>> None of the people who have credibility in the layout area have given >>> any feed back on your suggestions. >>> >> >> Who are these people? > > Ryan, Brian, and Rudi ... I hear Brian has an excuse :( > > Cheers, Jeff. > I thought it looked good. From jwulf at redhat.com Mon Oct 11 06:22:54 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 11 Oct 2010 16:22:54 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CB2ABCD.3040009@redhat.com> References: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286776978.2859.47.camel@captcha> <4CB2ABCD.3040009@redhat.com> Message-ID: <4CB2AD3E.7020103@redhat.com> On a more serious note, would this be related to: https://engineering.redhat.com/trac/ContentServices/wiki/FY11GoalPlan#Useability On 10/11/2010 04:16 PM, Joshua Wulf wrote: > On 10/11/2010 04:02 PM, Jeff Fearn wrote: >> On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: >>> ----- "Jeff Fearn" wrote: >>> >>>> >>>> None of the people who have credibility in the layout area have given >>>> any feed back on your suggestions. >>>> >>> >>> Who are these people? >> >> Ryan, Brian, and Rudi ... I hear Brian has an excuse :( >> >> Cheers, Jeff. >> > > I thought it looked good. > > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Mon Oct 11 06:31:12 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 11 Oct 2010 16:31:12 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1415415735.63921286777585058.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1415415735.63921286777585058.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1286778672.2859.63.camel@captcha> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones wrote: > How do we go about getting someone in Middleware some credibility? Surely it is not such a scarce commodity that it can't be spread around a bit. I think we'd like a hand in the look and feel of our docs, if we can ever build up the credibility. Credibility is earned not given, who in Middleware will stand up and earn some? How is it earned? I've never thought about it. It is an interesting question though, how does one earn credibility in a meritocracy? How did the people who have it get it? Has the fact that people earned it in a particular way made using that way less effective for new people? How do you avoid a meritocracy becoming and old boys (sic) club? 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 misty at redhat.com Mon Oct 11 06:32:50 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Mon, 11 Oct 2010 02:32:50 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286776600.2859.45.camel@captcha> Message-ID: <235450072.64581286778770012.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> I did not mean to imply that the discussion had fallen into a black hole. I was only trying to elicit more feedback, since emails do tend to fall to the bottom of people's inboxes. I apologize for that remark. Misty ----- "Jeff Fearn" wrote: > From: "Jeff Fearn" > To: "Misty Stanley-Jones" , "Publican discussions" > Sent: Monday, October 11, 2010 3:56:40 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > On Mon, 2010-10-11 at 01:17 -0400, Misty Stanley-Jones wrote: > > Jeff, now that we have given you a definite idea of what we would > like to see, > > None of the people who have credibility in the layout area have given > any feed back on your suggestions. > > Personally I wasn't that enamoured by them, but then again, I don't > have > much credibility in layout or design. > > > do you think this is something that you will be able to do, or show > us how to do to the JBoss brand? I want to make sure this request > doesn't go into a black hole. > > I had a chat with Rudi last week and he agreed to run a Lunch and > learn > on creating and customising brands. He assured me he would post > details > about it soon. > > Personally I'd love to see the brands removed from the publican repo, > handed off to the teams responsible for the docs. Maybe a LnL will > make > that achievable. > > 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 -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From jfearn at redhat.com Mon Oct 11 06:33:42 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 11 Oct 2010 16:33:42 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CB2A995.3040200@redhat.com> References: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286776978.2859.47.camel@captcha> <4CB2A995.3040200@redhat.com> Message-ID: <1286778822.2859.66.camel@captcha> On Mon, 2010-10-11 at 16:07 +1000, Joshua Wulf wrote: > On 10/11/2010 04:02 PM, Jeff Fearn wrote: > > On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: > >> ----- "Jeff Fearn" wrote: > >> > >>> > >>> None of the people who have credibility in the layout area have given > >>> any feed back on your suggestions. > >>> > >> > >> Who are these people? > > > > Ryan, Brian, and Rudi ... I hear Brian has an excuse :( > > > > Cheers, Jeff. > > > > "Brian" and "Ryan" are practically the same - the only difference is a > single letter, "B". Rudi - another four letter name starting with "R". > Coincidence - or conspiracy? They are also all white males who work for ECS in Brisbane! I say it's a conspiracy ... but I'm not quite sure why I'm not getting a kickback, conspiracies are all about the kick backs :( 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 jwulf at redhat.com Mon Oct 11 06:41:51 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 11 Oct 2010 16:41:51 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CB2AD3E.7020103@redhat.com> References: <137318445.63501286776780979.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286776978.2859.47.camel@captcha> <4CB2ABCD.3040009@redhat.com> <4CB2AD3E.7020103@redhat.com> Message-ID: <4CB2B1AF.90305@redhat.com> I like the Example title on top, because it gives the context before the content, which is an important mental flow for digestion. Otherwise, as an immediate example: I have a document that I'm working on where I transition from an imperative procedure to an example. The reader is lulled into a mental state of submissively following instructions by the terse imperative instruction of the procedure. As they succumb to the procedure's beacon of clear direction amidst an otherwise complex and uncertain world, the reader needs to do a mental context switch to process the information in the example as an *example*, rather than verbatim direction. Processing an example requires critical thinking, discrimination, and a level of abstract thinking that is antithetical to the surrendered trance-like state induced by empowered procedure construction. The better written the procedure is, the more pronounced the mental shift will need to be. Having the example title and the tag "Example" at the bottom causes the context switch to happen too late, and the reader has to go back and re-evaluate the example box contents. Writing an introductory note along the lines of "the following is an example" indicates that the "Example" identifier should precede the example itself. It will cause the reader to mentally shift gears to process the information that follows. It is the extreme case, but imagine a case where a particularly empowered procedure is read by a susceptible reader during just the right astrological conditions - if it is followed by an example that instructs the reader that they are a chicken, or demonstrates a command such as "rm -rf /", it might be too late by the time they reach the safe word "Example". I vote for "Example" in the title of an example, rather than beneath it. On 10/11/2010 04:22 PM, Joshua Wulf wrote: > On a more serious note, would this be related to: > > https://engineering.redhat.com/trac/ContentServices/wiki/FY11GoalPlan#Useability > > > On 10/11/2010 04:16 PM, Joshua Wulf wrote: >> On 10/11/2010 04:02 PM, Jeff Fearn wrote: >>> On Mon, 2010-10-11 at 01:59 -0400, Misty Stanley-Jones wrote: >>>> ----- "Jeff Fearn" wrote: >>>> >>>>> >>>>> None of the people who have credibility in the layout area have given >>>>> any feed back on your suggestions. >>>>> >>>> >>>> Who are these people? >>> >>> Ryan, Brian, and Rudi ... I hear Brian has an excuse :( >>> >>> Cheers, Jeff. >>> >> >> I thought it looked good. >> >> >> >> _______________________________________________ >> 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 From jfearn at redhat.com Mon Oct 11 06:51:59 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 11 Oct 2010 16:51:59 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <235450072.64581286778770012.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <235450072.64581286778770012.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1286779919.2859.84.camel@captcha> On Mon, 2010-10-11 at 02:32 -0400, Misty Stanley-Jones wrote: > I did not mean to imply that the discussion had fallen into a black hole. I was only trying to elicit more feedback, since emails do tend to fall to the bottom of people's inboxes. I apologize for that remark. I took it you were being proactive about something you cared about, not sure how anyone could take offence at it. It's raised some interesting points besides just brands though. Particularly how we go about letting new people in given the expanding community. It's easy to get a gauge on someone when there are only a few people in a community, when you start to get more people, informal ways can get pretty inefficient pretty quickly ... particularly when you only really have one "community" person. I'm sure we wouldn't have scaled to the current community size without Rudi beavering away, but I'm pretty sure that's not going to scale much further in it's current form, so we really need to start looking in to how we can make it easier for new contributors to get active and get some feedback on their input. What I like about a LnL for brands is instead of someone making a mock-up of the change they want, they can apply the change to a new brand and use that to build an existing document. You get a complete view of the change in situ, which is always going to give you a much better appreciation of the change, and is in fact a lot easier to do once you grok how to modify brands. So once we have documentation showing people how to make those kind of changes out side the current brands, it's then easy to create a more formal process for how to present changes for consideration. 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 serogers at redhat.com Mon Oct 11 07:10:44 2010 From: serogers at redhat.com (Sean Rogers) Date: Mon, 11 Oct 2010 03:10:44 -0400 (EDT) Subject: [publican-list] RFE for Publican Brands In-Reply-To: <452835811.46271286780889325.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1127241823.46351286781044305.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I agree this is a good way forward. Thanks, Jeff and Rudi. - Sean ----- "Jeff Fearn" wrote: | On Mon, 2010-10-11 at 02:32 -0400, Misty Stanley-Jones wrote: | > I did not mean to imply that the discussion had fallen into a black | hole. I was only trying to elicit more feedback, since emails do tend | to fall to the bottom of people's inboxes. I apologize for that | remark. | | I took it you were being proactive about something you cared about, | not | sure how anyone could take offence at it. | | It's raised some interesting points besides just brands though. | Particularly how we go about letting new people in given the | expanding | community. It's easy to get a gauge on someone when there are only a | few | people in a community, when you start to get more people, informal | ways | can get pretty inefficient pretty quickly ... particularly when you | only | really have one "community" person. | | I'm sure we wouldn't have scaled to the current community size | without | Rudi beavering away, but I'm pretty sure that's not going to scale | much | further in it's current form, so we really need to start looking in | to | how we can make it easier for new contributors to get active and get | some feedback on their input. | | What I like about a LnL for brands is instead of someone making a | mock-up of the change they want, they can apply the change to a new | brand and use that to build an existing document. You get a complete | view of the change in situ, which is always going to give you a much | better appreciation of the change, and is in fact a lot easier to do | once you grok how to modify brands. | | So once we have documentation showing people how to make those kind | of | changes out side the current brands, it's then easy to create a more | formal process for how to present changes for consideration. | | 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 | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From dmison at redhat.com Mon Oct 11 07:22:49 2010 From: dmison at redhat.com (Darrin Mison) Date: Mon, 11 Oct 2010 17:22:49 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286778672.2859.63.camel@captcha> References: <1415415735.63921286777585058.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286778672.2859.63.camel@captcha> Message-ID: <1286781769.27494.49.camel@dhcp-1-137.bne.redhat.com> On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: > On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones wrote: > > How do we go about getting someone in Middleware some credibility? Surely it is not such a scarce commodity that it can't be spread around a bit. I think we'd like a hand in the look and feel of our docs, if we can ever build up the credibility. > > Credibility is earned not given, who in Middleware will stand up and > earn some? > > How is it earned? I've never thought about it. It is an interesting > question though, how does one earn credibility in a meritocracy? AFAICT generally by contributing work, and having those with credibility accept your work. From jfearn at redhat.com Mon Oct 11 23:04:56 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 12 Oct 2010 09:04:56 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <1286781769.27494.49.camel@dhcp-1-137.bne.redhat.com> References: <1415415735.63921286777585058.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286778672.2859.63.camel@captcha> <1286781769.27494.49.camel@dhcp-1-137.bne.redhat.com> Message-ID: <4CB39818.6080606@redhat.com> Darrin Mison wrote: > > On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: >> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones wrote: >>> How do we go about getting someone in Middleware some credibility? Surely it is not such a scarce commodity that it can't be spread around a bit. I think we'd like a hand in the look and feel of our docs, if we can ever build up the credibility. >> Credibility is earned not given, who in Middleware will stand up and >> earn some? >> >> How is it earned? I've never thought about it. It is an interesting >> question though, how does one earn credibility in a meritocracy? > > AFAICT generally by contributing work, and having those with credibility > accept your work. Well true, but I would like to make sure we don't end up with a completely arbitrary environment, and the only way to do that is to get some processes or documentation in place about who to contribute for different things. e.g. If you have recommendations for a brand then make a new brand, apply your changes, build a book, maybe a set book, with the new brand and distribute for comment. If you have a suggestion for better release documentation, make a page on the wiki with an example of how it should be done. Maybe pick an existing release and document that. I'm sure there are heaps of other ways to contribute that people would find easy to join in if we documented them. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Mon Oct 11 23:07:28 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 12 Oct 2010 09:07:28 +1000 Subject: [publican-list] RFE for Publican Brands In-Reply-To: <4CB39818.6080606@redhat.com> References: <1415415735.63921286777585058.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <1286778672.2859.63.camel@captcha> <1286781769.27494.49.camel@dhcp-1-137.bne.redhat.com> <4CB39818.6080606@redhat.com> Message-ID: <4CB398B0.80703@redhat.com> Jeffrey Fearn wrote: > about who to contribute for different things. lol s/who/how, people will not be accepted as contributions. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From misty at redhat.com Tue Oct 12 05:14:44 2010 From: misty at redhat.com (misty at redhat.com) Date: Tue, 12 Oct 2010 01:14:44 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1277678538.218931286860436312.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <196447697.219021286860484294.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> I've modified the JBoss brand and attached the modified version. I'd love it if some of you could build books using it and let me know what you think. Extract it to /usr/share/publican/Common_Content and call it from publican.cfg as JBoss-misty. Just as the JBoss brand currently, the HTML versions do not currently sync with the PDF version. I didn't put too much effort into it (yet), because it obviously has not been a priority thus far. I'd like to get the changes synchronized to PDF, because I think they really help with printing. I've also included a .zip of a built book in HTML-single, so that you can see it in action without having to build your own book. If you get the Digest version of this mailing list and want to see the attachments, just ping me and I will send them to you individually. Thanks, Misty ----- "Jeffrey Fearn" wrote: > From: "Jeffrey Fearn" > To: "Publican discussions" > Sent: Tuesday, October 12, 2010 9:04:56 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFE for Publican Brands > > Darrin Mison wrote: > > > > On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: > >> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones wrote: > >>> How do we go about getting someone in Middleware some credibility? > Surely it is not such a scarce commodity that it can't be spread > around a bit. I think we'd like a hand in the look and feel of our > docs, if we can ever build up the credibility. > >> Credibility is earned not given, who in Middleware will stand up > and > >> earn some? > >> > >> How is it earned? I've never thought about it. It is an > interesting > >> question though, how does one earn credibility in a meritocracy? > > > > AFAICT generally by contributing work, and having those with > credibility > > accept your work. > > Well true, but I would like to make sure we don't end up with a > completely arbitrary environment, and the only way to do that is to > get > some processes or documentation in place about who to contribute for > different things. > > e.g. > > If you have recommendations for a brand then make a new brand, apply > your changes, build a book, maybe a set book, with the new brand and > distribute for comment. > > If you have a suggestion for better release documentation, make a page > > on the wiki with an example of how it should be done. Maybe pick an > existing release and document that. > > I'm sure there are heaps of other ways to contribute that people would > > find easy to join in if we documented them. > > Cheers, Jeff. > > -- > Jeff Fearn > Software Engineer > Engineering Operations > Red Hat, Inc > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. -------------- next part -------------- A non-text attachment was scrubbed... Name: JBoss-misty.zip Type: application/zip Size: 146721 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: html-single.zip Type: application/zip Size: 211299 bytes Desc: not available URL: From misty at redhat.com Tue Oct 12 05:22:15 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Tue, 12 Oct 2010 01:22:15 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <196447697.219021286860484294.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1179994602.219341286860935550.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Thanks (and credibility) go out to Sean for his helpful color and layout suggestions! ----- misty at redhat.com wrote: > From: misty at redhat.com > To: "Publican discussions" > Sent: Tuesday, October 12, 2010 3:14:44 PM GMT +10:00 Brisbane > Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > I've modified the JBoss brand and attached the modified version. I'd > love it if some of you could build books using it and let me know what > you think. Extract it to /usr/share/publican/Common_Content and call > it from publican.cfg as JBoss-misty. > > Just as the JBoss brand currently, the HTML versions do not currently > sync with the PDF version. I didn't put too much effort into it (yet), > because it obviously has not been a priority thus far. I'd like to get > the changes synchronized to PDF, because I think they really help with > printing. > > I've also included a .zip of a built book in HTML-single, so that you > can see it in action without having to build your own book. > > If you get the Digest version of this mailing list and want to see the > attachments, just ping me and I will send them to you individually. > > Thanks, > Misty > > ----- "Jeffrey Fearn" wrote: > > > From: "Jeffrey Fearn" > > To: "Publican discussions" > > Sent: Tuesday, October 12, 2010 9:04:56 AM GMT +10:00 Brisbane > > Subject: Re: [publican-list] RFE for Publican Brands > > > > Darrin Mison wrote: > > > > > > On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: > > >> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones wrote: > > >>> How do we go about getting someone in Middleware some > credibility? > > Surely it is not such a scarce commodity that it can't be spread > > around a bit. I think we'd like a hand in the look and feel of our > > docs, if we can ever build up the credibility. > > >> Credibility is earned not given, who in Middleware will stand up > > and > > >> earn some? > > >> > > >> How is it earned? I've never thought about it. It is an > > interesting > > >> question though, how does one earn credibility in a meritocracy? > > > > > > AFAICT generally by contributing work, and having those with > > credibility > > > accept your work. > > > > Well true, but I would like to make sure we don't end up with a > > completely arbitrary environment, and the only way to do that is to > > get > > some processes or documentation in place about who to contribute for > > > different things. > > > > e.g. > > > > If you have recommendations for a brand then make a new brand, apply > > > your changes, build a book, maybe a set book, with the new brand and > > > distribute for comment. > > > > If you have a suggestion for better release documentation, make a > page > > > > on the wiki with an example of how it should be done. Maybe pick an > > > existing release and document that. > > > > I'm sure there are heaps of other ways to contribute that people > would > > > > find easy to join in if we documented them. > > > > Cheers, Jeff. > > > > -- > > Jeff Fearn > > Software Engineer > > Engineering Operations > > Red Hat, Inc > > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From anross at redhat.com Tue Oct 12 05:32:19 2010 From: anross at redhat.com (Andrew Ross) Date: Tue, 12 Oct 2010 01:32:19 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1721996718.137041286861209585.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <918241435.137131286861539717.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> ----- "Misty Stanley-Jones" wrote: > Thanks (and credibility) go out to Sean for his helpful color and > layout suggestions! > Disclaimer: IANAD [1] Like: - border on Not so sure: -
text above image No opinion either way: - greyscale on screen tags inside notes (which IIRC was orig issue) HTH, Andrew [1] IANAD - I am not a designer > ----- misty at redhat.com wrote: > > > From: misty at redhat.com > > To: "Publican discussions" > > Sent: Tuesday, October 12, 2010 3:14:44 PM GMT +10:00 Brisbane > > Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for > Publican Brands) > > > > I've modified the JBoss brand and attached the modified version. > I'd > > love it if some of you could build books using it and let me know > what > > you think. Extract it to /usr/share/publican/Common_Content and > call > > it from publican.cfg as JBoss-misty. > > > > Just as the JBoss brand currently, the HTML versions do not > currently > > sync with the PDF version. I didn't put too much effort into it > (yet), > > because it obviously has not been a priority thus far. I'd like to > get > > the changes synchronized to PDF, because I think they really help > with > > printing. > > > > I've also included a .zip of a built book in HTML-single, so that > you > > can see it in action without having to build your own book. > > > > If you get the Digest version of this mailing list and want to see > the > > attachments, just ping me and I will send them to you individually. > > > > Thanks, > > Misty > > > > ----- "Jeffrey Fearn" wrote: > > > > > From: "Jeffrey Fearn" > > > To: "Publican discussions" > > > Sent: Tuesday, October 12, 2010 9:04:56 AM GMT +10:00 Brisbane > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > Darrin Mison wrote: > > > > > > > > On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: > > > >> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones wrote: > > > >>> How do we go about getting someone in Middleware some > > credibility? > > > Surely it is not such a scarce commodity that it can't be spread > > > around a bit. I think we'd like a hand in the look and feel of > our > > > docs, if we can ever build up the credibility. > > > >> Credibility is earned not given, who in Middleware will stand > up > > > and > > > >> earn some? > > > >> > > > >> How is it earned? I've never thought about it. It is an > > > interesting > > > >> question though, how does one earn credibility in a > meritocracy? > > > > > > > > AFAICT generally by contributing work, and having those with > > > credibility > > > > accept your work. > > > > > > Well true, but I would like to make sure we don't end up with a > > > completely arbitrary environment, and the only way to do that is > to > > > get > > > some processes or documentation in place about who to contribute > for > > > > > different things. > > > > > > e.g. > > > > > > If you have recommendations for a brand then make a new brand, > apply > > > > > your changes, build a book, maybe a set book, with the new brand > and > > > > > distribute for comment. > > > > > > If you have a suggestion for better release documentation, make a > > page > > > > > > on the wiki with an example of how it should be done. Maybe pick > an > > > > > existing release and document that. > > > > > > I'm sure there are heaps of other ways to contribute that people > > would > > > > > > find easy to join in if we documented them. > > > > > > Cheers, Jeff. > > > > > > -- > > > Jeff Fearn > > > Software Engineer > > > Engineering Operations > > > Red Hat, Inc > > > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Andrew Ross Quality Engineer, Content Services RHCE Red Hat Asia Pacific Phone: 3514 8331 E-mail: anross at redhat.com "Commander Cody, the time has come. Execute Order 66." - Darth Sidious Ep.III From anross at redhat.com Tue Oct 12 05:35:10 2010 From: anross at redhat.com (Andrew Ross) Date: Tue, 12 Oct 2010 01:35:10 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <918241435.137131286861539717.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <1769691500.137161286861710788.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> To completely shoot my cred in the foot... top posting ;) ----- "Andrew Ross" wrote: > Like: > - border on Forgot to add I like - title at top of From misty at redhat.com Tue Oct 12 05:44:10 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Tue, 12 Oct 2010 01:44:10 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <918241435.137131286861539717.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <1265465726.220061286862250584.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Andrew Ross" wrote: > Not so sure: > -
text above image Extremely negotiable. I did it to be consistent with examples and procedures. > > No opinion either way: > - greyscale on screen tags inside notes (which IIRC was orig issue) > The grey has been lightened considerably. It was dark grey almost black, making a lot of highlighted text inside programlistings unreadable. Here is a list of everything I actually changed: Admonitions: All have grey interior and white text, with thick color-coded borders. * Note: Dark grey border * Important: Orange border (same color as the whole box was before) * Warning: Red border (same color as the whole box was before) Programlistings and screens: *Light grey interior *Thin dark-grey border. *Consistent throughout the document, alone or within examples or admonitions. Examples: *Dark green border *White inner div (so paragraphs are black on white, instead of black on bright orange), *Title on top Figures: *Title on top Misty > HTH, > > Andrew > > [1] IANAD - I am not a designer > > > ----- misty at redhat.com wrote: > > > > > From: misty at redhat.com > > > To: "Publican discussions" > > > Sent: Tuesday, October 12, 2010 3:14:44 PM GMT +10:00 Brisbane > > > Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE > for > > Publican Brands) > > > > > > I've modified the JBoss brand and attached the modified version. > > I'd > > > love it if some of you could build books using it and let me know > > what > > > you think. Extract it to /usr/share/publican/Common_Content and > > call > > > it from publican.cfg as JBoss-misty. > > > > > > Just as the JBoss brand currently, the HTML versions do not > > currently > > > sync with the PDF version. I didn't put too much effort into it > > (yet), > > > because it obviously has not been a priority thus far. I'd like > to > > get > > > the changes synchronized to PDF, because I think they really help > > with > > > printing. > > > > > > I've also included a .zip of a built book in HTML-single, so that > > you > > > can see it in action without having to build your own book. > > > > > > If you get the Digest version of this mailing list and want to > see > > the > > > attachments, just ping me and I will send them to you > individually. > > > > > > Thanks, > > > Misty > > > > > > ----- "Jeffrey Fearn" wrote: > > > > > > > From: "Jeffrey Fearn" > > > > To: "Publican discussions" > > > > Sent: Tuesday, October 12, 2010 9:04:56 AM GMT +10:00 Brisbane > > > > Subject: Re: [publican-list] RFE for Publican Brands > > > > > > > > Darrin Mison wrote: > > > > > > > > > > On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: > > > > >> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones > wrote: > > > > >>> How do we go about getting someone in Middleware some > > > credibility? > > > > Surely it is not such a scarce commodity that it can't be > spread > > > > around a bit. I think we'd like a hand in the look and feel of > > our > > > > docs, if we can ever build up the credibility. > > > > >> Credibility is earned not given, who in Middleware will > stand > > up > > > > and > > > > >> earn some? > > > > >> > > > > >> How is it earned? I've never thought about it. It is an > > > > interesting > > > > >> question though, how does one earn credibility in a > > meritocracy? > > > > > > > > > > AFAICT generally by contributing work, and having those with > > > > credibility > > > > > accept your work. > > > > > > > > Well true, but I would like to make sure we don't end up with a > > > > > completely arbitrary environment, and the only way to do that > is > > to > > > > get > > > > some processes or documentation in place about who to > contribute > > for > > > > > > > different things. > > > > > > > > e.g. > > > > > > > > If you have recommendations for a brand then make a new brand, > > apply > > > > > > > your changes, build a book, maybe a set book, with the new > brand > > and > > > > > > > distribute for comment. > > > > > > > > If you have a suggestion for better release documentation, make > a > > > page > > > > > > > > on the wiki with an example of how it should be done. Maybe > pick > > an > > > > > > > existing release and document that. > > > > > > > > I'm sure there are heaps of other ways to contribute that > people > > > would > > > > > > > > find easy to join in if we documented them. > > > > > > > > Cheers, Jeff. > > > > > > > > -- > > > > Jeff Fearn > > > > Software Engineer > > > > Engineering Operations > > > > Red Hat, Inc > > > > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > > > > > > > _______________________________________________ > > > > publican-list mailing list > > > > publican-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/publican-list > > > > Wiki: https://fedorahosted.org/publican > > > > > > -- > > > Misty Stanley-Jones > > > Content Author, ECS Brisbane > > > Ph: +61 7 3514 8105 > > > RHCT #60501081553354 > > > Purgamentum init, exit purgamentum. > > > > > > _______________________________________________ > > > publican-list mailing list > > > publican-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/publican-list > > > Wiki: https://fedorahosted.org/publican > > > > -- > > Misty Stanley-Jones > > Content Author, ECS Brisbane > > Ph: +61 7 3514 8105 > > RHCT #60501081553354 > > Purgamentum init, exit purgamentum. > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > > Andrew Ross > Quality Engineer, Content Services > RHCE > Red Hat Asia Pacific > Phone: 3514 8331 > E-mail: anross at redhat.com > > > "Commander Cody, the time has come. Execute Order 66." - Darth Sidious > Ep.III > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From serogers at redhat.com Tue Oct 12 05:52:21 2010 From: serogers at redhat.com (Sean Rogers) Date: Tue, 12 Oct 2010 01:52:21 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1265465726.220061286862250584.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1472108465.201461286862741078.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I agree the position of the figure title is questionable. For example blocks, it certainly makes sense readability-wise for the titles to be at the top, while typically figure titles go underneath to act as a caption. So it's a matter of either having the titles at the tops of both examples and figures for consistency, or having titles at the bottom of figures like it is in most other publications. I think I'm probably inclined towards the latter. - Sean ----- "Misty Stanley-Jones" wrote: | ----- "Andrew Ross" wrote: | > Not so sure: | > -
text above image | | Extremely negotiable. I did it to be consistent with examples and | procedures. | | > | > No opinion either way: | > - greyscale on screen tags inside notes (which IIRC was orig | issue) | > | | The grey has been lightened considerably. It was dark grey almost | black, making a lot of highlighted text inside programlistings | unreadable. | | Here is a list of everything I actually changed: | | Admonitions: All have grey interior and white text, with thick | color-coded borders. | * Note: Dark grey border | * Important: Orange border (same color as the whole box was before) | * Warning: Red border (same color as the whole box was before) | | Programlistings and screens: | *Light grey interior | *Thin dark-grey border. | *Consistent throughout the document, alone or within examples or | admonitions. | | Examples: | *Dark green border | *White inner div (so paragraphs are black on white, instead of black | on bright orange), | *Title on top | | Figures: | *Title on top | | | Misty | | | > HTH, | > | > Andrew | > | > [1] IANAD - I am not a designer | > | > > ----- misty at redhat.com wrote: | > > | > > > From: misty at redhat.com | > > > To: "Publican discussions" | > > > Sent: Tuesday, October 12, 2010 3:14:44 PM GMT +10:00 Brisbane | > > > Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE | > for | > > Publican Brands) | > > > | > > > I've modified the JBoss brand and attached the modified | version. | > > I'd | > > > love it if some of you could build books using it and let me | know | > > what | > > > you think. Extract it to /usr/share/publican/Common_Content and | > > call | > > > it from publican.cfg as JBoss-misty. | > > > | > > > Just as the JBoss brand currently, the HTML versions do not | > > currently | > > > sync with the PDF version. I didn't put too much effort into it | > > (yet), | > > > because it obviously has not been a priority thus far. I'd like | > to | > > get | > > > the changes synchronized to PDF, because I think they really | help | > > with | > > > printing. | > > > | > > > I've also included a .zip of a built book in HTML-single, so | that | > > you | > > > can see it in action without having to build your own book. | > > > | > > > If you get the Digest version of this mailing list and want to | > see | > > the | > > > attachments, just ping me and I will send them to you | > individually. | > > > | > > > Thanks, | > > > Misty | > > > | > > > ----- "Jeffrey Fearn" wrote: | > > > | > > > > From: "Jeffrey Fearn" | > > > > To: "Publican discussions" | > > > > Sent: Tuesday, October 12, 2010 9:04:56 AM GMT +10:00 | Brisbane | > > > > Subject: Re: [publican-list] RFE for Publican Brands | > > > > | > > > > Darrin Mison wrote: | > > > > > | > > > > > On Mon, 2010-10-11 at 16:31 +1000, Jeff Fearn wrote: | > > > > >> On Mon, 2010-10-11 at 02:13 -0400, Misty Stanley-Jones | > wrote: | > > > > >>> How do we go about getting someone in Middleware some | > > > credibility? | > > > > Surely it is not such a scarce commodity that it can't be | > spread | > > > > around a bit. I think we'd like a hand in the look and feel | of | > > our | > > > > docs, if we can ever build up the credibility. | > > > > >> Credibility is earned not given, who in Middleware will | > stand | > > up | > > > > and | > > > > >> earn some? | > > > > >> | > > > > >> How is it earned? I've never thought about it. It is an | > > > > interesting | > > > > >> question though, how does one earn credibility in a | > > meritocracy? | > > > > > | > > > > > AFAICT generally by contributing work, and having those | with | > > > > credibility | > > > > > accept your work. | > > > > | > > > > Well true, but I would like to make sure we don't end up with | a | > | > > > > completely arbitrary environment, and the only way to do that | > is | > > to | > > > > get | > > > > some processes or documentation in place about who to | > contribute | > > for | > > > | > > > > different things. | > > > > | > > > > e.g. | > > > > | > > > > If you have recommendations for a brand then make a new | brand, | > > apply | > > > | > > > > your changes, build a book, maybe a set book, with the new | > brand | > > and | > > > | > > > > distribute for comment. | > > > > | > > > > If you have a suggestion for better release documentation, | make | > a | > > > page | > > > > | > > > > on the wiki with an example of how it should be done. Maybe | > pick | > > an | > > > | > > > > existing release and document that. | > > > > | > > > > I'm sure there are heaps of other ways to contribute that | > people | > > > would | > > > > | > > > > find easy to join in if we documented them. | > > > > | > > > > Cheers, Jeff. | > > > > | > > > > -- | > > > > Jeff Fearn | > > > > Software Engineer | > > > > Engineering Operations | > > > > Red Hat, Inc | > > > > Freedom ... courage ... Commitment ... ACCOUNTABILITY | > > > > | > > > > _______________________________________________ | > > > > publican-list mailing list | > > > > publican-list at redhat.com | > > > > https://www.redhat.com/mailman/listinfo/publican-list | > > > > Wiki: https://fedorahosted.org/publican | > > > | > > > -- | > > > Misty Stanley-Jones | > > > Content Author, ECS Brisbane | > > > Ph: +61 7 3514 8105 | > > > RHCT #60501081553354 | > > > Purgamentum init, exit purgamentum. | > > > | > > > _______________________________________________ | > > > publican-list mailing list | > > > publican-list at redhat.com | > > > https://www.redhat.com/mailman/listinfo/publican-list | > > > Wiki: https://fedorahosted.org/publican | > > | > > -- | > > Misty Stanley-Jones | > > Content Author, ECS Brisbane | > > Ph: +61 7 3514 8105 | > > RHCT #60501081553354 | > > Purgamentum init, exit purgamentum. | > > | > > _______________________________________________ | > > publican-list mailing list | > > publican-list at redhat.com | > > https://www.redhat.com/mailman/listinfo/publican-list | > > Wiki: https://fedorahosted.org/publican | > | > -- | > | > Andrew Ross | > Quality Engineer, Content Services | > RHCE | > Red Hat Asia Pacific | > Phone: 3514 8331 | > E-mail: anross at redhat.com | > | > | > "Commander Cody, the time has come. Execute Order 66." - Darth | Sidious | > Ep.III | > | > _______________________________________________ | > publican-list mailing list | > publican-list at redhat.com | > https://www.redhat.com/mailman/listinfo/publican-list | > Wiki: https://fedorahosted.org/publican | | -- | Misty Stanley-Jones | Content Author, ECS Brisbane | Ph: +61 7 3514 8105 | RHCT #60501081553354 | Purgamentum init, exit purgamentum. | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Tue Oct 12 06:41:42 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 12 Oct 2010 16:41:42 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <196447697.219021286860484294.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <196447697.219021286860484294.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB40326.2010309@redhat.com> misty at redhat.com wrote: > I've modified the JBoss brand and attached the modified version. I'd love it if some of you could build books using it and let me know what you think. Verbatim style: Like! Admonition Style: The borders aren't useful in differentiating the content. I think they could look better without them ... maybe new icons would help there? Example Style: The colored border just looks wrong, this one has always been the worst looking IMHO and the extra border was probably what was wrong with it. I think the title at the top is demarcation enough. Figure Style: The title looks wrong at the top. > Extract it to /usr/share/publican/Common_Content and call it from publican.cfg as JBoss-misty. We never tell people to manually copy files in to system areas, we have processes to install them properly so their systems don't become hard to upgrade, or recover, or report many errors when they validate their system ... also there are many, many, many people who will harass you endlessly about it :/ This is the correct process for duplicating a brand ... maybe the first of our "how to do stuff and look cool doing it" articles! # rename the directory when exporting $ svn export http://svn.fedorahosted.org/svn/publican/trunk/publican-jboss publican-jboss-misty $ cd publican-jboss-misty/ $ mv publican-jboss.spec publican-jboss-misty.spec $ sed -i -e's/publican-jboss/publican-jboss-misty/g' publican-jboss-misty.spec $ sed -i -e's/JBoss/JBoss-Misty/g' publican-jboss-misty.spec $ sed -i -e's/JBoss/JBoss-Misty/g' publican.cfg $ publican package --binary $ sudo rpm -Uvh tmp/rpm/noarch/publican-jboss-misty-2.2-0.el5.noarch.rpm # make changes to required css, xsl, etc files # update publican.cfg and spec file, and repackage Is the last step documented sufficiently in the PUG? > Just as the JBoss brand currently, the HTML versions do not currently sync with the PDF version. I didn't put too much effort into it (yet), because it obviously has not been a priority thus far. I'd like to get the changes synchronized to PDF, because I think they really help with printing. There was never any intention for the HTML and PDF to be exactly the same. One is for printing and one is for on screen reading, and apparently that requires different layout and colors and whatnot. But since Andy left we haven't had anyone active who really knew the subtleties in differentiating them. > I've also included a .zip of a built book in HTML-single, so that you can see it in action without having to build your own book. > > If you get the Digest version of this mailing list and want to see the attachments, just ping me and I will send them to you individually. You can put the zips on the publican wiki if you want, you just need to login with your FAS details. The wiki is pretty open and anyone with a FAS account can edit it. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From misty at redhat.com Tue Oct 12 22:41:24 2010 From: misty at redhat.com (misty at redhat.com) Date: Tue, 12 Oct 2010 18:41:24 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <544537632.368341286922215565.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <106324881.369121286923284803.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Jeffrey Fearn" wrote: > Verbatim style: Like! > > Admonition Style: The borders aren't useful in differentiating the > content. I think they could look better without them ... maybe new > icons > would help there? I think they need something besides the icons to differentiate them, especially the warning. At the same time, O'Reilly print documentation seems to use one icon for notice/tip/info and another one for warning/caution. No other differentiation. And they've sold a lot of books using this system. Any other thoughts on this? Maybe Sean has some thoughts (he is a usability expert after all). > > Example Style: The colored border just looks wrong, this one has > always > been the worst looking IMHO and the extra border was probably what was > > wrong with it. I think the title at the top is demarcation enough. I think I agree with you and would like to change it to just a 1px dark grey border, with white text inside. Thoughts? > > Figure Style: The title looks wrong at the top. We all agree and I have changed it in my working copy. > > We never tell people to manually copy files in to system areas, we > have > processes to install them properly so their systems don't become hard > to > upgrade, or recover[...] Fair enough. In my enthusiasm I had forgotten that Publican has a procedure for installing brands. > > You can put the zips on the publican wiki if you want, you just need > to > login with your FAS details. The wiki is pretty open and anyone with a > > FAS account can edit it. > > Cheers, Jeff. > > -- > Jeff Fearn > Software Engineer > Engineering Operations > Red Hat, Inc > Freedom ... courage ... Commitment ... ACCOUNTABILITY -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From misty at redhat.com Wed Oct 13 00:07:57 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Tue, 12 Oct 2010 20:07:57 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <106324881.369121286923284803.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> See https://fedorahosted.org/publican/wiki/JBossBrandChanges for screenshots and downloads. Thanks Jeff for the use of the Wiki! Misty ----- misty at redhat.com wrote: > From: misty at redhat.com > To: "Jeffrey Fearn" > Cc: "Misty Stanley-Jones" , "Publican discussions" > Sent: Wednesday, October 13, 2010 8:41:24 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > ----- "Jeffrey Fearn" wrote: > > > Verbatim style: Like! > > > > Admonition Style: The borders aren't useful in differentiating the > > content. I think they could look better without them ... maybe new > > icons > > would help there? > > I think they need something besides the icons to differentiate them, > especially the warning. At the same time, O'Reilly print documentation > seems to use one icon for notice/tip/info and another one for > warning/caution. No other differentiation. And they've sold a lot of > books using this system. Any other thoughts on this? Maybe Sean has > some thoughts (he is a usability expert after all). > > > > > Example Style: The colored border just looks wrong, this one has > > always > > been the worst looking IMHO and the extra border was probably what > was > > > > wrong with it. I think the title at the top is demarcation enough. > > I think I agree with you and would like to change it to just a 1px > dark grey border, with white text inside. Thoughts? > > > > > Figure Style: The title looks wrong at the top. > > We all agree and I have changed it in my working copy. > > > > > We never tell people to manually copy files in to system areas, we > > have > > processes to install them properly so their systems don't become > hard > > to > > upgrade, or recover[...] > > Fair enough. In my enthusiasm I had forgotten that Publican has a > procedure for installing brands. > > > > > You can put the zips on the publican wiki if you want, you just > need > > to > > login with your FAS details. The wiki is pretty open and anyone with > a > > > > FAS account can edit it. > > > > Cheers, Jeff. > > > > -- > > Jeff Fearn > > Software Engineer > > Engineering Operations > > Red Hat, Inc > > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From jwulf at redhat.com Wed Oct 13 00:29:51 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 10:29:51 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB4FD7F.8080503@redhat.com> Thin rounded border without a doubt. The current one has terrible contrast that reduces readability. Red on Orange? A huge orange blob on the page? ==Coloured vs non-coloured background== A coloured background reduces contrast, and hence readability, without creating more intelligibility. A border enhances intelligibility by allowing a reader to ascertain where the example starts and ends at a glance. Filling in that border with a colour adds no further value. Having a solid block of colour on a page, and multiples blocks of colour on a page as our docs currently do, reduces intelligibility. When looking at a page of this text the mind of the reader is pushed to switch modes. Picture and pattern processing is different from text stream processing. Visual cues should support the processing of the text information on the page, and not overload the reader. My vote goes to: Thin rounded border - elegant, understated, supportive, encapsulates the example. *Without* the border the natural tendency in the example you've given would be to consider the contents of the programlisting to be the whole example, as it is a bounded area that immediately follows the Example title. Having a border around the example clarifies this. The border also allows a user to quickly skip over an entire example and continue reading. ==Thick vs thin border:== The thick rounded border is too heavy-handed and draws the eye away from the content. ==Square vs rounded borders:== Incorporating circles into the user interface was pioneered by Steve Jobs while he was at NEXT. Prior to that user interfaces, although executed on monitors that could support it, were informed by metaphors and design principles that hadn't significantly changed since the tools of execution were hammers and chisels. ==Indentation vs border== Indentation is relative. As a visual cue its efficacy is lost when the text above disappears off the screen, or you turn the page. I'm given to understand that our current pdf processor doesn't support flow of indentation across pages anyway, so with our current implementation it's either ineffective or both ineffective and impossible. On 10/13/2010 10:07 AM, Misty Stanley-Jones wrote: > See https://fedorahosted.org/publican/wiki/JBossBrandChanges for screenshots and downloads. Thanks Jeff for the use of the Wiki! > > Misty > > ----- misty at redhat.com wrote: > >> From: misty at redhat.com >> To: "Jeffrey Fearn" >> Cc: "Misty Stanley-Jones" , "Publican discussions" >> Sent: Wednesday, October 13, 2010 8:41:24 AM GMT +10:00 Brisbane >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) >> >> ----- "Jeffrey Fearn" wrote: >> >>> Verbatim style: Like! >>> >>> Admonition Style: The borders aren't useful in differentiating the >>> content. I think they could look better without them ... maybe new >>> icons >>> would help there? >> >> I think they need something besides the icons to differentiate them, >> especially the warning. At the same time, O'Reilly print documentation >> seems to use one icon for notice/tip/info and another one for >> warning/caution. No other differentiation. And they've sold a lot of >> books using this system. Any other thoughts on this? Maybe Sean has >> some thoughts (he is a usability expert after all). >> >>> >>> Example Style: The colored border just looks wrong, this one has >>> always >>> been the worst looking IMHO and the extra border was probably what >> was >>> >>> wrong with it. I think the title at the top is demarcation enough. >> >> I think I agree with you and would like to change it to just a 1px >> dark grey border, with white text inside. Thoughts? >> >>> >>> Figure Style: The title looks wrong at the top. >> >> We all agree and I have changed it in my working copy. >> >>> >>> We never tell people to manually copy files in to system areas, we >>> have >>> processes to install them properly so their systems don't become >> hard >>> to >>> upgrade, or recover[...] >> >> Fair enough. In my enthusiasm I had forgotten that Publican has a >> procedure for installing brands. >> >>> >>> You can put the zips on the publican wiki if you want, you just >> need >>> to >>> login with your FAS details. The wiki is pretty open and anyone with >> a >>> >>> FAS account can edit it. >>> >>> Cheers, Jeff. >>> >>> -- >>> Jeff Fearn >>> Software Engineer >>> Engineering Operations >>> Red Hat, Inc >>> Freedom ... courage ... Commitment ... ACCOUNTABILITY >> >> -- >> Misty Stanley-Jones >> Content Author, ECS Brisbane >> Ph: +61 7 3514 8105 >> RHCT #60501081553354 >> Purgamentum init, exit purgamentum. > From serogers at redhat.com Wed Oct 13 00:29:59 2010 From: serogers at redhat.com (Sean Rogers) Date: Tue, 12 Oct 2010 20:29:59 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1399587917.326411286929710049.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1299741573.326461286929799007.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> ----- misty at redhat.com wrote: | ----- "Jeffrey Fearn" wrote: | | > Verbatim style: Like! | > | > Admonition Style: The borders aren't useful in differentiating the | > content. I think they could look better without them ... maybe new | > icons | > would help there? | | I think they need something besides the icons to differentiate them, | especially the warning. At the same time, O'Reilly print documentation | seems to use one icon for notice/tip/info and another one for | warning/caution. No other differentiation. And they've sold a lot of | books using this system. Any other thoughts on this? Maybe Sean has | some thoughts (he is a usability expert after all). I agree they need more than just an icon for accessibility. Since the title is configurable, and generally should not just say "Note", it can't be relied on. Colour is usually not a good way to differentiate things by itself, but in combination with the icon it is OK. I think admonitions need a border to separate them from any following text. This is why sections can't have following paras: without a border admonitions would essentially just become sections and following paras would not look right. | | > | > Example Style: The colored border just looks wrong, this one has | > always | > been the worst looking IMHO and the extra border was probably what | was | > | > wrong with it. I think the title at the top is demarcation enough. | | I think I agree with you and would like to change it to just a 1px | dark grey border, with white text inside. Thoughts? I admit I do like the look of the example without a border, but for the same reasons as above I think we need a border, even more so since they're typically longer than admonitions. Originally I thought that borderless could work since it works for procedures, but procedures are typically part of the flow of the content while examples often act as asides. 1px could possibly work but I feel a thicker one designates that as more of a separate block. Examples should be able to be skipped when reading, and a thicker border facilitates this easier than a thicker one for me. | | > | > Figure Style: The title looks wrong at the top. | | We all agree and I have changed it in my working copy. | | > | > We never tell people to manually copy files in to system areas, we | > have | > processes to install them properly so their systems don't become | hard | > to | > upgrade, or recover[...] | | Fair enough. In my enthusiasm I had forgotten that Publican has a | procedure for installing brands. | | > | > You can put the zips on the publican wiki if you want, you just | need | > to | > login with your FAS details. The wiki is pretty open and anyone with | a | > | > FAS account can edit it. | > | > Cheers, Jeff. | > | > -- | > Jeff Fearn | > Software Engineer | > Engineering Operations | > Red Hat, Inc | > Freedom ... courage ... Commitment ... ACCOUNTABILITY | | -- | Misty Stanley-Jones | Content Author, ECS Brisbane | Ph: +61 7 3514 8105 | RHCT #60501081553354 | Purgamentum init, exit purgamentum. | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Wed Oct 13 00:35:23 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 13 Oct 2010 10:35:23 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB4FECB.7050304@redhat.com> Misty Stanley-Jones wrote: > See https://fedorahosted.org/publican/wiki/JBossBrandChanges for screenshots and downloads. Thanks Jeff for the use of the Wiki! I'm going to split up this change set atm, in to the following two sections: 1: verbatim style and title locations 2: admonitions and examples I think number one is generally agreed upon as being good across the board and suitable for inclusion in the common brand and therefore application across all brands that don't override these things. I think number 2 needs a bit more discussion and may end up bing applied differently amongst the brands. If you disagree you'd better let me know before I commit a patch for number one! Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jwulf at redhat.com Wed Oct 13 00:50:20 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 10:50:20 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB4FECB.7050304@redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB4FECB.7050304@redhat.com> Message-ID: <4CB5024C.9040403@redhat.com> On 10/13/2010 10:35 AM, Jeffrey Fearn wrote: > Misty Stanley-Jones wrote: >> See https://fedorahosted.org/publican/wiki/JBossBrandChanges for screenshots and downloads. Thanks Jeff for the use of the Wiki! > > I'm going to split up this change set atm, in to the following two sections: > > 1: verbatim style and title locations > > 2: admonitions and examples > > I think number one is generally agreed upon as being good across the > board and suitable for inclusion in the common brand and therefore > application across all brands that don't override these things. > > I think number 2 needs a bit more discussion and may end up bing applied > differently amongst the brands. > > If you disagree you'd better let me know before I commit a patch for > number one! > > Cheers, Jeff. > Is there any guidance on the usage of important, warning, and note? From dmison at redhat.com Wed Oct 13 00:59:05 2010 From: dmison at redhat.com (Darrin Mison) Date: Wed, 13 Oct 2010 10:59:05 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1769691500.137161286861710788.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> References: <1769691500.137161286861710788.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <1286931545.2667.11.camel@dhcp-1-137.bne.redhat.com> I like the way the example is formatted in the DocBook guide. Title at the top, vertical bar down the left. http://www.docbook.org/tdg/en/html/example.html From jwulf at redhat.com Wed Oct 13 00:59:36 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 10:59:36 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <106324881.369121286923284803.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <106324881.369121286923284803.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB50478.3050401@redhat.com> For adminitions I vote thin-rounded borders, no colours. Right now the visual cueing in our docs doesn't help readers. They are frequently presented with a page with multiple blocks of colours. These are effectively flashing lights calling for their attention. When you have a bank of controls and one flashing red light, your attention is immediately directed there. When you have multiple flashing lights of various colours, you just throw your hands up and go: "wtf?" If there is one adminition in a book with a heavy-handed visual style, it really calls attention to itself. When there are multiple on a page the reader is fatigue, the effect is overused and ineffective. I think it's better that we rely on putting the reader into text processing mode. The icon is enough visual cueing - the border again allows them to understand (and optionally to skip over) the scope of the adminition. We should have a very clear and consistent guidelines on how we use the adminitions, so that reader expectation of their information role can be set and consistently reinforced. On 10/13/2010 08:41 AM, misty at redhat.com wrote: > > ----- "Jeffrey Fearn" wrote: > >> Verbatim style: Like! >> >> Admonition Style: The borders aren't useful in differentiating the >> content. I think they could look better without them ... maybe new >> icons >> would help there? > > I think they need something besides the icons to differentiate them, especially the warning. At the same time, O'Reilly print documentation seems to use one icon for notice/tip/info and another one for warning/caution. No other differentiation. And they've sold a lot of books using this system. Any other thoughts on this? Maybe Sean has some thoughts (he is a usability expert after all). > >> >> Example Style: The colored border just looks wrong, this one has >> always >> been the worst looking IMHO and the extra border was probably what was >> >> wrong with it. I think the title at the top is demarcation enough. > > I think I agree with you and would like to change it to just a 1px dark grey border, with white text inside. Thoughts? > >> >> Figure Style: The title looks wrong at the top. > > We all agree and I have changed it in my working copy. > >> >> We never tell people to manually copy files in to system areas, we >> have >> processes to install them properly so their systems don't become hard >> to >> upgrade, or recover[...] > > Fair enough. In my enthusiasm I had forgotten that Publican has a procedure for installing brands. > >> >> You can put the zips on the publican wiki if you want, you just need >> to >> login with your FAS details. The wiki is pretty open and anyone with a >> >> FAS account can edit it. >> >> Cheers, Jeff. >> >> -- >> Jeff Fearn >> Software Engineer >> Engineering Operations >> Red Hat, Inc >> Freedom ... courage ... Commitment ... ACCOUNTABILITY > From jwulf at redhat.com Wed Oct 13 01:12:06 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 11:12:06 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1286931545.2667.11.camel@dhcp-1-137.bne.redhat.com> References: <1769691500.137161286861710788.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> <1286931545.2667.11.camel@dhcp-1-137.bne.redhat.com> Message-ID: <4CB50766.1020104@redhat.com> On 10/13/2010 10:59 AM, Darrin Mison wrote: > I like the way the example is formatted in the DocBook > guide. > > Title at the top, vertical bar down the left. > > http://www.docbook.org/tdg/en/html/example.html > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > > Yes, I also like this. The vertical bar of the docbook styling is like indentation, but it's an absolute visual cue, rather than a relative one, so it doesn't have a problem with page flow. A complete border breaks the vertical flow of the document with a horizontal boundary. Both the vertical bar and the complete border clearly demark the scope; however, the complete border actually lends itself to readers skipping the unit. The subconscious reasoning is: "Since the unit has been completely encapsulated and separated from the text, it's obviously not necessary" SKIP The human mind is designed with many subconscious processors that discard information before it reaches the conscious mind. This makes every day existence possible. Without it information overload would occur within seconds. How many nerve endings are there in the human body, each sending tactile information to the brain? How much of that are we aware of from moment to moment? Generally only the flashing red lights. Once you get shot three or four times your brain starts to ignore those as well. We emulate the action of the subconscious mind, which aids us in processing information with scarce conscious attention resources, when we use mail filtering rules. So I would click "Like" on a vertical bar over the thin, rounded border; but there wasn't one on the options page. From serogers at redhat.com Wed Oct 13 01:14:21 2010 From: serogers at redhat.com (Sean Rogers) Date: Tue, 12 Oct 2010 21:14:21 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1242336197.328191286932111874.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1672382102.328501286932461713.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I don't think anyone is arguing in favour of the colour blocks we currently have. Yet your argument is mostly why I wanted a grey border for notes instead of the green they previously were: green made them stand out and flash, which is not really what notes are meant for. Warnings and Importants do need to stand out though, as it is usually essential for the reader to read them. We do have clear guidelines for the use of admonitions, it's what is listed in the Preface material. Overuse should be avoided for the reasons you state. I should also clarify my previous comment about not being able to use the titles for admonition differentiation: Ryan has reminded me that a while back when the admonition title discussion was had, the consensus was that titles should be specified, but they should include the type of admonition; for example: "Important: Don't forget to wear pants". In this case the title can be relied on. The more I think about it the colours aren't really necessary for admonitions, it just looks weird with them being all the same colour when they're next to each other, which they typically should not be in normal use. - Sean ----- "Joshua Wulf" wrote: | For adminitions I vote thin-rounded borders, no colours. | | Right now the visual cueing in our docs doesn't help readers. They | are | frequently presented with a page with multiple blocks of colours. | These | are effectively flashing lights calling for their attention. | | When you have a bank of controls and one flashing red light, your | attention is immediately directed there. When you have multiple | flashing | lights of various colours, you just throw your hands up and go: | "wtf?" | | If there is one adminition in a book with a heavy-handed visual | style, | it really calls attention to itself. | | When there are multiple on a page the reader is fatigue, the effect | is | overused and ineffective. | | I think it's better that we rely on putting the reader into text | processing mode. | | The icon is enough visual cueing - the border again allows them to | understand (and optionally to skip over) the scope of the adminition. | | We should have a very clear and consistent guidelines on how we use | the | adminitions, so that reader expectation of their information role can | be | set and consistently reinforced. | | | | On 10/13/2010 08:41 AM, misty at redhat.com wrote: | > | > ----- "Jeffrey Fearn" wrote: | > | >> Verbatim style: Like! | >> | >> Admonition Style: The borders aren't useful in differentiating the | | >> content. I think they could look better without them ... maybe new | >> icons | >> would help there? | > | > I think they need something besides the icons to differentiate them, | especially the warning. At the same time, O'Reilly print documentation | seems to use one icon for notice/tip/info and another one for | warning/caution. No other differentiation. And they've sold a lot of | books using this system. Any other thoughts on this? Maybe Sean has | some thoughts (he is a usability expert after all). | > | >> | >> Example Style: The colored border just looks wrong, this one has | >> always | >> been the worst looking IMHO and the extra border was probably what | was | >> | >> wrong with it. I think the title at the top is demarcation enough. | > | > I think I agree with you and would like to change it to just a 1px | dark grey border, with white text inside. Thoughts? | > | >> | >> Figure Style: The title looks wrong at the top. | > | > We all agree and I have changed it in my working copy. | > | >> | >> We never tell people to manually copy files in to system areas, we | >> have | >> processes to install them properly so their systems don't become | hard | >> to | >> upgrade, or recover[...] | > | > Fair enough. In my enthusiasm I had forgotten that Publican has a | procedure for installing brands. | > | >> | >> You can put the zips on the publican wiki if you want, you just | need | >> to | >> login with your FAS details. The wiki is pretty open and anyone | with a | >> | >> FAS account can edit it. | >> | >> Cheers, Jeff. | >> | >> -- | >> Jeff Fearn | >> Software Engineer | >> Engineering Operations | >> Red Hat, Inc | >> Freedom ... courage ... Commitment ... ACCOUNTABILITY | > | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jwulf at redhat.com Wed Oct 13 01:17:54 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 11:17:54 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB50766.1020104@redhat.com> References: <1769691500.137161286861710788.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> <1286931545.2667.11.camel@dhcp-1-137.bne.redhat.com> <4CB50766.1020104@redhat.com> Message-ID: <4CB508C2.1020004@redhat.com> When I read messages in Thunderbird with HTML view turned on, "responded to" text is indicated exactly the same way: with a vertical bar. I can, and do immediately skip over it (if I am already following the thread) to get to the reply text. It's a subtle visual cue that I wasn't even aware of consciously, but was subconsciously using all the time. It rose to conscious awareness after a subconscious processor flagged it as "recently discussed" and brought it to conscious attention. We want our visual styling to be *transparent*. That is: subconsciously processed, and invisible to the conscious mind. At the moment it's very much trying to grab conscious attention, and there is just not enough of that to go round. On 10/13/2010 11:12 AM, Joshua Wulf wrote: > On 10/13/2010 10:59 AM, Darrin Mison wrote: >> I like the way the example is formatted in the DocBook >> guide. >> >> Title at the top, vertical bar down the left. >> >> http://www.docbook.org/tdg/en/html/example.html >> >> >> _______________________________________________ >> publican-list mailing list >> publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list >> Wiki: https://fedorahosted.org/publican >> >> > > Yes, I also like this. > > The vertical bar of the docbook styling is like indentation, but it's an > absolute visual cue, rather than a relative one, so it doesn't have a > problem with page flow. > > A complete border breaks the vertical flow of the document with a > horizontal boundary. > > Both the vertical bar and the complete border clearly demark the scope; > however, the complete border actually lends itself to readers skipping > the unit. > > The subconscious reasoning is: > "Since the unit has been completely encapsulated and separated from the > text, it's obviously not necessary" SKIP > > The human mind is designed with many subconscious processors that > discard information before it reaches the conscious mind. This makes > every day existence possible. Without it information overload would > occur within seconds. How many nerve endings are there in the human > body, each sending tactile information to the brain? How much of that > are we aware of from moment to moment? Generally only the flashing red > lights. Once you get shot three or four times your brain starts to > ignore those as well. > > We emulate the action of the subconscious mind, which aids us in > processing information with scarce conscious attention resources, when > we use mail filtering rules. > > So I would click "Like" on a vertical bar over the thin, rounded border; > but there wasn't one on the options page. > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican > > From misty at redhat.com Wed Oct 13 01:30:26 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Tue, 12 Oct 2010 21:30:26 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB508C2.1020004@redhat.com> Message-ID: <391847620.374581286933426648.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Joshua Wulf" wrote: > From: "Joshua Wulf" > To: "Publican discussions" > Sent: Wednesday, October 13, 2010 11:17:54 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > When I read messages in Thunderbird with HTML view turned on, > "responded > to" text is indicated exactly the same way: with a vertical bar. I > can, > and do immediately skip over it (if I am already following the > thread) > to get to the reply text. So by that token, you would skip over the examples too. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From jwulf at redhat.com Wed Oct 13 01:57:33 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 11:57:33 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <391847620.374581286933426648.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <391847620.374581286933426648.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB5120D.50500@redhat.com> On 10/13/2010 11:30 AM, Misty Stanley-Jones wrote: > > ----- "Joshua Wulf" wrote: > >> From: "Joshua Wulf" >> To: "Publican discussions" >> Sent: Wednesday, October 13, 2010 11:17:54 AM GMT +10:00 Brisbane >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) >> >> When I read messages in Thunderbird with HTML view turned on, >> "responded >> to" text is indicated exactly the same way: with a vertical bar. I >> can, >> and do immediately skip over it (if I am already following the >> thread) >> to get to the reply text. > > So by that token, you would skip over the examples too. > If your conscious mind processes in the first couple of lines that it is irrelevant, your subconscious mind will help you to get to the end of it immediately *with no conscious processing*. From misty at redhat.com Wed Oct 13 02:13:38 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Tue, 12 Oct 2010 22:13:38 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB5120D.50500@redhat.com> Message-ID: <607870670.376651286936018891.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> I've added the left-hand-only border to the Wiki page for your comments. Again, the Wiki is at https://fedorahosted.org/publican/wiki/JBossBrandChanges ----- "Joshua Wulf" wrote: > From: "Joshua Wulf" > To: "Misty Stanley-Jones" , "Publican discussions" > Sent: Wednesday, October 13, 2010 11:57:33 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > On 10/13/2010 11:30 AM, Misty Stanley-Jones wrote: > > > > ----- "Joshua Wulf" wrote: > > > >> From: "Joshua Wulf" > >> To: "Publican discussions" > >> Sent: Wednesday, October 13, 2010 11:17:54 AM GMT +10:00 Brisbane > >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE > for Publican Brands) > >> > >> When I read messages in Thunderbird with HTML view turned on, > >> "responded > >> to" text is indicated exactly the same way: with a vertical bar. I > >> can, > >> and do immediately skip over it (if I am already following the > >> thread) > >> to get to the reply text. > > > > So by that token, you would skip over the examples too. > > > > If your conscious mind processes in the first couple of lines that it > is > irrelevant, your subconscious mind will help you to get to the end of > it > immediately *with no conscious processing*. -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From serogers at redhat.com Wed Oct 13 02:17:27 2010 From: serogers at redhat.com (Sean Rogers) Date: Tue, 12 Oct 2010 22:17:27 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB5120D.50500@redhat.com> Message-ID: <1455359342.331401286936247374.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I was unsure about just having the vertical line at first, as I thought it would be too subtle as a cue, but seeing it in action I'm coming around to it. ----- "Joshua Wulf" wrote: | On 10/13/2010 11:30 AM, Misty Stanley-Jones wrote: | > | > ----- "Joshua Wulf" wrote: | > | >> From: "Joshua Wulf" | >> To: "Publican discussions" | >> Sent: Wednesday, October 13, 2010 11:17:54 AM GMT +10:00 Brisbane | >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE | for Publican Brands) | >> | >> When I read messages in Thunderbird with HTML view turned on, | >> "responded | >> to" text is indicated exactly the same way: with a vertical bar. I | >> can, | >> and do immediately skip over it (if I am already following the | >> thread) | >> to get to the reply text. | > | > So by that token, you would skip over the examples too. | > | | If your conscious mind processes in the first couple of lines that it | is | irrelevant, your subconscious mind will help you to get to the end of | it | immediately *with no conscious processing*. | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Wed Oct 13 04:32:42 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 13 Oct 2010 14:32:42 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1455359342.331401286936247374.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> References: <1455359342.331401286936247374.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <4CB5366A.1040408@redhat.com> Sean Rogers wrote: > I was unsure about just having the vertical line at first, as I thought it would be too subtle as a cue, but seeing it in action I'm coming around to it. Same here, sounds not so good, but actually looks OK in HTML and PDF. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jwulf at redhat.com Wed Oct 13 05:13:48 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Wed, 13 Oct 2010 15:13:48 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1455359342.331401286936247374.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> References: <1455359342.331401286936247374.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <4CB5400C.4090501@redhat.com> On 10/13/2010 12:17 PM, Sean Rogers wrote: > I was unsure about just having the vertical line at first, as I thought it would be too subtle as a cue, but seeing it in action I'm coming around to it. > It's great that it uses a distinct visual cue from the one used by the programlisting. Distinct visual cues for distinct information elements facilitates reader assimilation. The brain has dedicated reflexive systems for visual cues. In contrast, words need to pass through more expensive parts of the brain. More information processing delegated to the reader's semi-automated visual processing mid-brain equals less tax on the precious cerebral cortex. We are consistent in mapping our visual vocabulary to information roles; readers quickly develop filters that optimize processing of our information. A rule of thumb: Things should look similar if they are processed similarly by the reader; otherwise they should look different. > ----- "Joshua Wulf" wrote: > > | On 10/13/2010 11:30 AM, Misty Stanley-Jones wrote: > | > > | > ----- "Joshua Wulf" wrote: > | > > | >> From: "Joshua Wulf" > | >> To: "Publican discussions" > | >> Sent: Wednesday, October 13, 2010 11:17:54 AM GMT +10:00 Brisbane > | >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE > | for Publican Brands) > | >> > | >> When I read messages in Thunderbird with HTML view turned on, > | >> "responded > | >> to" text is indicated exactly the same way: with a vertical bar. I > | >> can, > | >> and do immediately skip over it (if I am already following the > | >> thread) > | >> to get to the reply text. > | > > | > So by that token, you would skip over the examples too. > | > > | > | If your conscious mind processes in the first couple of lines that it > | is > | irrelevant, your subconscious mind will help you to get to the end of > | it > | immediately *with no conscious processing*. > | > | _______________________________________________ > | 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 > > From jfearn at redhat.com Wed Oct 13 07:21:17 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Wed, 13 Oct 2010 17:21:17 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB4FECB.7050304@redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB4FECB.7050304@redhat.com> Message-ID: <4CB55DED.7070700@redhat.com> Jeffrey Fearn wrote: > Misty Stanley-Jones wrote: >> See https://fedorahosted.org/publican/wiki/JBossBrandChanges for >> screenshots and downloads. Thanks Jeff for the use of the Wiki! > > I'm going to split up this change set atm, in to the following two > sections: > > 1: verbatim style and title locations > > 2: admonitions and examples > > I think number one is generally agreed upon as being good across the > board and suitable for inclusion in the common brand and therefore > application across all brands that don't override these things. > > I think number 2 needs a bit more discussion and may end up bing applied > differently amongst the brands. > > If you disagree you'd better let me know before I commit a patch for > number one! FYI I have checked a patch in to trunk for the common brand containing all of #1; for HTML and PDF. In the same patch I included a change for the wide bar on the left of the example, again for HTML and PDF. It seemed the most popular and I was testing it when people who use trunk were bugging me to check in the other changes. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From rlerch at redhat.com Wed Oct 13 21:20:42 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Thu, 14 Oct 2010 07:20:42 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB55DED.7070700@redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB4FECB.7050304@redhat.com> <4CB55DED.7070700@redhat.com> Message-ID: <4CB622AA.8030203@redhat.com> On 10/13/2010 05:21 PM, Jeffrey Fearn wrote: > Jeffrey Fearn wrote: >> Misty Stanley-Jones wrote: >>> See https://fedorahosted.org/publican/wiki/JBossBrandChanges for >>> screenshots and downloads. Thanks Jeff for the use of the Wiki! >> >> I'm going to split up this change set atm, in to the following two >> sections: >> >> 1: verbatim style and title locations >> >> 2: admonitions and examples >> >> I think number one is generally agreed upon as being good across the >> board and suitable for inclusion in the common brand and therefore >> application across all brands that don't override these things. >> >> I think number 2 needs a bit more discussion and may end up bing >> applied differently amongst the brands. >> >> If you disagree you'd better let me know before I commit a patch for >> number one! > > FYI I have checked a patch in to trunk for the common brand containing > all of #1; for HTML and PDF. > > In the same patch I included a change for the wide bar on the left of > the example, again for HTML and PDF. It seemed the most popular and I > was testing it when people who use trunk were bugging me to check in > the other changes. > > Cheers, Jeff. > I have added a build of the Publican User Guide (html-single and pdf formats) to my fedora people so people can "test"/view these changes http://ryanlerch.fedorapeople.org/Publican_User_Guide/ This version was built with publican-2.2-0.fc13.t22. cheers, ryanlerch From rlerch at redhat.com Wed Oct 13 21:26:30 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Thu, 14 Oct 2010 07:26:30 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1265465726.220061286862250584.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1265465726.220061286862250584.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB62406.1060901@redhat.com> On 10/12/2010 03:44 PM, Misty Stanley-Jones wrote: > > The grey has been lightened considerably. It was dark grey almost black, making a lot of highlighted text inside programlistings unreadable. > > Here is a list of everything I actually changed: > > Admonitions: All have grey interior and white text, with thick color-coded borders. > * Note: Dark grey border > * Important: Orange border (same color as the whole box was before) > * Warning: Red border (same color as the whole box was before) > I have added a new idea to the wikipage for admonitions. You can view a screenshot at the bottom of the admonitions ideas section -- https://fedorahosted.org/publican/wiki/JBossBrandChanges The screenshot is also attached to this email. cheers, ryanlerch -------------- next part -------------- A non-text attachment was scrubbed... Name: admonitions-with-titlebar.png Type: image/png Size: 33199 bytes Desc: not available URL: From dmison at redhat.com Thu Oct 14 00:09:38 2010 From: dmison at redhat.com (Darrin Mison) Date: Thu, 14 Oct 2010 10:09:38 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB622AA.8030203@redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB4FECB.7050304@redhat.com> <4CB55DED.7070700@redhat.com> <4CB622AA.8030203@redhat.com> Message-ID: <31BDD681-0F5D-401B-8591-95DE30DBF299@redhat.com> On 14/10/2010, at 7:20 AM, Ryan Lerch wrote: > I have added a build of the Publican User Guide (html-single and pdf formats) to my fedora people so people can "test"/view these changes > http://ryanlerch.fedorapeople.org/Publican_User_Guide/ > > This version was built with publican-2.2-0.fc13.t22. > The example css still has the border radius set. Is a little less noticeable in Firefox. http://ryanlerch.fedorapeople.org/Publican_User_Guide/html-single/#sect-Users_Guide-Files_in_the_book_directory-Doc_Name.xml Safari 4: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen shot 2010-10-14 at 10.06.07 AM.png Type: image/png Size: 23880 bytes Desc: not available URL: -------------- next part -------------- Firefox: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen shot 2010-10-14 at 10.06.18 AM.png Type: image/png Size: 9545 bytes Desc: not available URL: -------------- next part -------------- From jwulf at redhat.com Thu Oct 14 00:28:28 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Thu, 14 Oct 2010 10:28:28 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB62406.1060901@redhat.com> References: <1265465726.220061286862250584.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB62406.1060901@redhat.com> Message-ID: <4CB64EAC.6040209@redhat.com> Nice. Much more elegant that the existing ones. On 10/14/2010 07:26 AM, Ryan Lerch wrote: > On 10/12/2010 03:44 PM, Misty Stanley-Jones wrote: >> >> The grey has been lightened considerably. It was dark grey almost black, making a lot of highlighted text inside programlistings unreadable. >> >> Here is a list of everything I actually changed: >> >> Admonitions: All have grey interior and white text, with thick color-coded borders. >> * Note: Dark grey border >> * Important: Orange border (same color as the whole box was before) >> * Warning: Red border (same color as the whole box was before) >> > > > I have added a new idea to the wikipage for admonitions. You can view a > screenshot at the bottom of the admonitions ideas section -- > https://fedorahosted.org/publican/wiki/JBossBrandChanges > > The screenshot is also attached to this email. > > cheers, > ryanlerch > > > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From rlerch at redhat.com Thu Oct 14 02:10:47 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Thu, 14 Oct 2010 12:10:47 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <31BDD681-0F5D-401B-8591-95DE30DBF299@redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB4FECB.7050304@redhat.com> <4CB55DED.7070700@redhat.com> <4CB622AA.8030203@redhat.com> <31BDD681-0F5D-401B-8591-95DE30DBF299@redhat.com> Message-ID: <4CB666A7.9020808@redhat.com> On 10/14/2010 10:09 AM, Darrin Mison wrote: > The example css still has the border radius set. Is a little less noticeable in Firefox. > > http://ryanlerch.fedorapeople.org/Publican_User_Guide/html-single/#sect-Users_Guide-Files_in_the_book_directory-Doc_Name.xml Do we want a flat line here? I kinda liked the tapered effect i was getting in firefox. (even though it does not really add anything to it) cheers, ryanlerch From misty at redhat.com Thu Oct 14 02:54:51 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Wed, 13 Oct 2010 22:54:51 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB666A7.9020808@redhat.com> Message-ID: <136829642.544651287024891936.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> If we want a taper, we can use an image for the border, and get a more consistent effect. ----- "Ryan Lerch" wrote: > From: "Ryan Lerch" > To: "Publican discussions" > Sent: Thursday, October 14, 2010 12:10:47 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > On 10/14/2010 10:09 AM, Darrin Mison wrote: > > The example css still has the border radius set. Is a little less > noticeable in Firefox. > > > > > http://ryanlerch.fedorapeople.org/Publican_User_Guide/html-single/#sect-Users_Guide-Files_in_the_book_directory-Doc_Name.xml > > Do we want a flat line here? I kinda liked the tapered effect i was > getting in firefox. (even though it does not really add anything to > it) > > cheers, > ryanlerch > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From serogers at redhat.com Thu Oct 14 03:02:38 2010 From: serogers at redhat.com (Sean Rogers) Date: Wed, 13 Oct 2010 23:02:38 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <136829642.544651287024891936.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1247142314.493111287025358227.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I like the taper too, but I wouldn't use an image just to get the effect. - Sean ----- "Misty Stanley-Jones" wrote: | If we want a taper, we can use an image for the border, and get a more | consistent effect. | | ----- "Ryan Lerch" wrote: | | > From: "Ryan Lerch" | > To: "Publican discussions" | > Sent: Thursday, October 14, 2010 12:10:47 PM GMT +10:00 Brisbane | > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE | for Publican Brands) | > | > On 10/14/2010 10:09 AM, Darrin Mison wrote: | > > The example css still has the border radius set. Is a little | less | > noticeable in Firefox. | > > | > > | > | http://ryanlerch.fedorapeople.org/Publican_User_Guide/html-single/#sect-Users_Guide-Files_in_the_book_directory-Doc_Name.xml | > | > Do we want a flat line here? I kinda liked the tapered effect i was | | > getting in firefox. (even though it does not really add anything to | > it) | > | > cheers, | > ryanlerch | > | > _______________________________________________ | > publican-list mailing list | > publican-list at redhat.com | > https://www.redhat.com/mailman/listinfo/publican-list | > Wiki: https://fedorahosted.org/publican | | -- | Misty Stanley-Jones | Content Author, ECS Brisbane | Ph: +61 7 3514 8105 | RHCT #60501081553354 | Purgamentum init, exit purgamentum. | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From r.landmann at redhat.com Thu Oct 14 03:09:38 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Thu, 14 Oct 2010 13:09:38 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB666A7.9020808@redhat.com> References: <678108338.371631286928477474.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB4FECB.7050304@redhat.com> <4CB55DED.7070700@redhat.com> <4CB622AA.8030203@redhat.com> <31BDD681-0F5D-401B-8591-95DE30DBF299@redhat.com> <4CB666A7.9020808@redhat.com> Message-ID: <4CB67472.6000006@redhat.com> On 10/14/2010 12:10 PM, Ryan Lerch wrote: > On 10/14/2010 10:09 AM, Darrin Mison wrote: >> The example css still has the border radius set. Is a little less >> noticeable in Firefox. >> >> http://ryanlerch.fedorapeople.org/Publican_User_Guide/html-single/#sect-Users_Guide-Files_in_the_book_directory-Doc_Name.xml >> > > Do we want a flat line here? I kinda liked the tapered effect i was > getting in firefox. (even though it does not really add anything to it) > FWIW, I really don't like the taper, but it's not a deal-breaker for me and I admit that this is nothing but personal preference that I can't pass off as better or worse in any objective sense :) Cheers Rudi From serogers at redhat.com Thu Oct 14 03:14:57 2010 From: serogers at redhat.com (Sean Rogers) Date: Wed, 13 Oct 2010 23:14:57 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB67472.6000006@redhat.com> Message-ID: <1895001415.493761287026097609.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> >From a practical standpoint, I think the taper could be useful in indicating the beginning and end of a scope when it runs over a page break. In that it would be easy to see it was a complete block rather than two separate ones. - Sean ----- "Ruediger Landmann" wrote: | On 10/14/2010 12:10 PM, Ryan Lerch wrote: | > On 10/14/2010 10:09 AM, Darrin Mison wrote: | >> The example css still has the border radius set. Is a little less | | >> noticeable in Firefox. | >> | >> | http://ryanlerch.fedorapeople.org/Publican_User_Guide/html-single/#sect-Users_Guide-Files_in_the_book_directory-Doc_Name.xml | | >> | > | > Do we want a flat line here? I kinda liked the tapered effect i was | | > getting in firefox. (even though it does not really add anything to | it) | > | | FWIW, I really don't like the taper, but it's not a deal-breaker for | me | and I admit that this is nothing but personal preference that I can't | | pass off as better or worse in any objective sense :) | | Cheers | Rudi | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From r.landmann at redhat.com Thu Oct 14 03:25:40 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Thu, 14 Oct 2010 13:25:40 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1895001415.493761287026097609.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> References: <1895001415.493761287026097609.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <4CB67834.9000308@redhat.com> On 10/14/2010 01:14 PM, Sean Rogers wrote: > > From a practical standpoint, I think the taper could be useful in indicating the beginning and end of a scope when it runs over a page break. In that it would be easy to see it was a complete block rather than two separate ones. > Oh -- good point! Could we maybe have some kind of serif at the ends of the line instead then? I think that would look a lot better than a taper. Cheers Rudi From misty at redhat.com Thu Oct 14 03:28:32 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Wed, 13 Oct 2010 23:28:32 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB67834.9000308@redhat.com> Message-ID: <1401707729.545861287026912656.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Ruediger Landmann" wrote: > From: "Ruediger Landmann" > To: publican-list at redhat.com > Sent: Thursday, October 14, 2010 1:25:40 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > On 10/14/2010 01:14 PM, Sean Rogers wrote: > > > From a practical standpoint, I think the taper could be useful in > indicating the beginning and end of a scope when it runs over a page > break. In that it would be easy to see it was a complete block rather > than two separate ones. > > > Oh -- good point! Could we maybe have some kind of serif at the ends > of > the line instead then? I think that would look a lot better than a > taper. We could do that by making a very short (5px? 10px?) border at the bottom and top of the example. With the rounded edge it might look very nice. I'll play around and post some samples on the Wiki. > > Cheers > Rudi > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From misty at redhat.com Thu Oct 14 03:35:03 2010 From: misty at redhat.com (misty at redhat.com) Date: Wed, 13 Oct 2010 23:35:03 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <652312366.546151287027260966.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1062866685.546171287027303716.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> I'm retracting this. There is, sadly, no border length. We could do it by introducing a hr before and after the example, and specifying the length and position of that, but that is a bit clunky, and probably too much work for a little edge definition. ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Publican discussions" > Sent: Thursday, October 14, 2010 1:28:32 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > > We could do that by making a very short (5px? 10px?) border at the > bottom and top of the example. With the rounded edge it might look > very nice. I'll play around and post some samples on the Wiki. > > > > > Cheers > > Rudi > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From r.landmann at redhat.com Thu Oct 14 03:46:22 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Thu, 14 Oct 2010 13:46:22 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1895001415.493761287026097609.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> References: <1895001415.493761287026097609.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <4CB67D0E.8010104@redhat.com> On 10/14/2010 01:14 PM, Sean Rogers wrote: > > From a practical standpoint, I think the taper could be useful in indicating the beginning and end of a scope when it runs over a page break. In that it would be easy to see it was a complete block rather than two separate ones. It also occurs to me that running over a page break is only an issue in PDF and I don't know whether we can do this in XSL. Rudi From jfearn at redhat.com Thu Oct 14 03:46:32 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Thu, 14 Oct 2010 13:46:32 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1062866685.546171287027303716.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1062866685.546171287027303716.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB67D18.2050103@redhat.com> Can we get an update on which admonition styles are still in the running? Maybe update https://fedorahosted.org/publican/wiki/JBossBrandChanges by removing the ones no longer being considered from being embedded? May as well leave them attached for history. Are we all agreed upon 'Thick border left-hand side only' for Examples? If so we could un-embed ... is that a word ... the rest of them, maybe have "current" and "The Chosen One" embedded. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From serogers at redhat.com Thu Oct 14 04:57:50 2010 From: serogers at redhat.com (Sean Rogers) Date: Thu, 14 Oct 2010 00:57:50 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB67D0E.8010104@redhat.com> Message-ID: <1670601270.496481287032270360.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> That's a good point... I'd wager it can't be done. ----- "Ruediger Landmann" wrote: | On 10/14/2010 01:14 PM, Sean Rogers wrote: | > > From a practical standpoint, I think the taper could be useful in | indicating the beginning and end of a scope when it runs over a page | break. In that it would be easy to see it was a complete block rather | than two separate ones. | | It also occurs to me that running over a page break is only an issue | in | PDF and I don't know whether we can do this in XSL. | | Rudi | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From misty at redhat.com Thu Oct 14 05:21:24 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Thu, 14 Oct 2010 01:21:24 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB67D18.2050103@redhat.com> Message-ID: <1300842016.548651287033684103.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Jeffrey Fearn" wrote: > From: "Jeffrey Fearn" > To: "Publican discussions" > Sent: Thursday, October 14, 2010 1:46:32 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > Can we get an update on which admonition styles are still in the > running? > > Maybe update https://fedorahosted.org/publican/wiki/JBossBrandChanges > by > removing the ones no longer being considered from being embedded? May > as > well leave them attached for history. > > Are we all agreed upon 'Thick border left-hand side only' for > Examples? > If so we could un-embed ... is that a word ... the rest of them, maybe > > have "current" and "The Chosen One" embedded. > > Cheers, Jeff. > Done. I don't think we have any consensus at all on admonitions, or if any of them are even out of the running. So I left them alone. > -- > Jeff Fearn > Software Engineer > Engineering Operations > Red Hat, Inc > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From jfearn at redhat.com Thu Oct 14 23:35:13 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 15 Oct 2010 09:35:13 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1300842016.548651287033684103.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1300842016.548651287033684103.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB793B1.90108@redhat.com> Misty Stanley-Jones wrote: > ----- "Jeffrey Fearn" wrote: > >> From: "Jeffrey Fearn" >> To: "Publican discussions" >> Sent: Thursday, October 14, 2010 1:46:32 PM GMT +10:00 Brisbane >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) >> >> Can we get an update on which admonition styles are still in the >> running? >> >> Maybe update https://fedorahosted.org/publican/wiki/JBossBrandChanges >> by >> removing the ones no longer being considered from being embedded? May >> as >> well leave them attached for history. >> >> Are we all agreed upon 'Thick border left-hand side only' for >> Examples? >> If so we could un-embed ... is that a word ... the rest of them, maybe >> >> have "current" and "The Chosen One" embedded. >> >> Cheers, Jeff. >> > > Done. Thanks Misty. > I don't think we have any consensus at all on admonitions, or if any of them are even out of the running. So I left them alone. How about people vote for their favorite style and the brand they think it should be applied for? Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From rlerch at redhat.com Fri Oct 15 00:32:29 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Fri, 15 Oct 2010 10:32:29 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB793B1.90108@redhat.com> References: <1300842016.548651287033684103.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB793B1.90108@redhat.com> Message-ID: <4CB7A11D.3030907@redhat.com> On 10/15/2010 09:35 AM, Jeffrey Fearn wrote: > I don't think we have any consensus at all on admonitions, or if any > of them are even out of the running. So I left them alone. > > How about people vote for their favorite style and the brand they > think it should be applied for? > > Cheers, Jeff. > My Vote: Style - "Coloured Title bar, offset icon " Brand - Common cheers, ryanlerch From misty at redhat.com Fri Oct 15 00:38:47 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Thu, 14 Oct 2010 20:38:47 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7A11D.3030907@redhat.com> Message-ID: <1062741916.685391287103127328.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Ryan Lerch" wrote: > > > My Vote: > > Style - "Coloured Title bar, offset icon " > Brand - Common +1 Second choice: "Thick borders with colors" -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From sgordon at redhat.com Fri Oct 15 00:44:44 2010 From: sgordon at redhat.com (Stephen Gordon) Date: Fri, 15 Oct 2010 10:44:44 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1062741916.685391287103127328.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1062741916.685391287103127328.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB7A3FC.3070008@redhat.com> On 10/15/2010 10:38 AM, Misty Stanley-Jones wrote: > > ----- "Ryan Lerch" wrote: > >>> >> My Vote: >> >> Style - "Coloured Title bar, offset icon " >> Brand - Common > > +1 > > Second choice: "Thick borders with colors" > +1 for: Style - "Coloured Title bar, offset icon" Brand - Common With a second choice of "Thick borders with colors". From r.landmann at redhat.com Fri Oct 15 00:46:45 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Fri, 15 Oct 2010 10:46:45 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7A11D.3030907@redhat.com> References: <1300842016.548651287033684103.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB793B1.90108@redhat.com> <4CB7A11D.3030907@redhat.com> Message-ID: <4CB7A475.1090809@redhat.com> On 10/15/2010 10:32 AM, Ryan Lerch wrote: > On 10/15/2010 09:35 AM, Jeffrey Fearn wrote: >> I don't think we have any consensus at all on admonitions, or if any >> of them are even out of the running. So I left them alone. >> >> How about people vote for their favorite style and the brand they >> think it should be applied for? >> >> Cheers, Jeff. >> > My Vote: > > Style - "Coloured Title bar, offset icon " > Brand - Common +1 From misty at redhat.com Fri Oct 15 00:48:20 2010 From: misty at redhat.com (misty at redhat.com) Date: Thu, 14 Oct 2010 20:48:20 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <17838810.685681287103654993.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <2074434291.685761287103700925.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Laura's vote (she's not on the list, this was via IRC): #1. thick borders with colours #2. colour title bar ----- "Misty Stanley-Jones" wrote: > From: "Misty Stanley-Jones" > To: "Publican discussions" > Sent: Friday, October 15, 2010 10:38:47 AM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > ----- "Ryan Lerch" wrote: > > > > > > My Vote: > > > > Style - "Coloured Title bar, offset icon " > > Brand - Common > > +1 > > Second choice: "Thick borders with colors" > > -- > Misty Stanley-Jones > Content Author, ECS Brisbane > Ph: +61 7 3514 8105 > RHCT #60501081553354 > Purgamentum init, exit purgamentum. > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From dmison at redhat.com Fri Oct 15 00:55:07 2010 From: dmison at redhat.com (Darrin Mison) Date: Fri, 15 Oct 2010 10:55:07 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7A11D.3030907@redhat.com> References: <1300842016.548651287033684103.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB793B1.90108@redhat.com> <4CB7A11D.3030907@redhat.com> Message-ID: <1287104107.8630.0.camel@dhcp-1-137.bne.redhat.com> > Style - "Coloured Title bar, offset icon " > Brand - Common > +1 From anross at redhat.com Fri Oct 15 00:55:26 2010 From: anross at redhat.com (Andrew Ross) Date: Thu, 14 Oct 2010 20:55:26 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7A11D.3030907@redhat.com> Message-ID: <349742764.465011287104126146.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> ----- "Ryan Lerch" wrote: > On 10/15/2010 09:35 AM, Jeffrey Fearn wrote: > > I don't think we have any consensus at all on admonitions, or if any > > > of them are even out of the running. So I left them alone. > > > > How about people vote for their favorite style and the brand they > > think it should be applied for? > > > > Cheers, Jeff. > > > My Vote: > > Style - "Coloured Title bar, offset icon " > Brand - Common > ++ > cheers, > ryanlerch > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Andrew Ross Quality Engineer, Content Services RHCE Red Hat Asia Pacific Phone: 3514 8331 E-mail: anross at redhat.com "Commander Cody, the time has come. Execute Order 66." - Darth Sidious Ep.III From serogers at redhat.com Fri Oct 15 01:02:58 2010 From: serogers at redhat.com (Sean Rogers) Date: Thu, 14 Oct 2010 21:02:58 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <349742764.465011287104126146.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <1153300579.633471287104578303.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> 1st choice: coloured title bar... although I'd have to see it with the programlistings, since the background colours look very similar. Also the warning icon should be changed back to the hazard sign instead of the quasi-stop sign. I also think the green may be too strong for the note as it brings more attention to it than is perhaps warranted. 2nd choice: thick coloured borders. Common brand. - Sean ----- "Andrew Ross" wrote: | ----- "Ryan Lerch" wrote: | | > On 10/15/2010 09:35 AM, Jeffrey Fearn wrote: | > > I don't think we have any consensus at all on admonitions, or if | any | > | > > of them are even out of the running. So I left them alone. | > > | > > How about people vote for their favorite style and the brand they | | > > think it should be applied for? | > > | > > Cheers, Jeff. | > > | > My Vote: | > | > Style - "Coloured Title bar, offset icon " | > Brand - Common | > | | ++ | | > cheers, | > ryanlerch | > | > _______________________________________________ | > publican-list mailing list | > publican-list at redhat.com | > https://www.redhat.com/mailman/listinfo/publican-list | > Wiki: https://fedorahosted.org/publican | | -- | | Andrew Ross | Quality Engineer, Content Services | RHCE | Red Hat Asia Pacific | Phone: 3514 8331 | E-mail: anross at redhat.com | | | "Commander Cody, the time has come. Execute Order 66." - Darth Sidious | Ep.III | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jmorgan at redhat.com Fri Oct 15 01:04:59 2010 From: jmorgan at redhat.com (Jared Morgan) Date: Thu, 14 Oct 2010 21:04:59 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <8636967.42.1287104272128.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Message-ID: <15331082.45.1287104496409.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Admonitions Vote 1st - Thick Border, Colour. 2nd - Coloured Title Bar, Offset Icon Jared Morgan Content Author Red Hat Asia Pacific 1/193 North Quay BRISBANE QLD 4000 P: +61 7 3514 8242 M: +61 413 005 479 From: "Jeffrey Fearn" To: "Misty Stanley-Jones" , "Publican discussions" Sent: Friday, October 15, 2010 9:35:13 AM Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) Misty Stanley-Jones wrote: > ----- "Jeffrey Fearn" wrote: > >> From: "Jeffrey Fearn" >> To: "Publican discussions" >> Sent: Thursday, October 14, 2010 1:46:32 PM GMT +10:00 Brisbane >> Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) >> >> Can we get an update on which admonition styles are still in the >> running? >> >> Maybe update https://fedorahosted.org/publican/wiki/JBossBrandChanges >> by >> removing the ones no longer being considered from being embedded? May >> as >> well leave them attached for history. >> >> Are we all agreed upon 'Thick border left-hand side only' for >> Examples? >> If so we could un-embed ... is that a word ... the rest of them, maybe >> >> have "current" and "The Chosen One" embedded. >> >> Cheers, Jeff. >> > > Done. Thanks Misty. > I don't think we have any consensus at all on admonitions, or if any of them are even out of the running. So I left them alone. How about people vote for their favorite style and the brand they think it should be applied for? Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican -------------- next part -------------- An HTML attachment was scrubbed... URL: From leecarlon at redhat.com Fri Oct 15 01:10:48 2010 From: leecarlon at redhat.com (Lee Carlon) Date: Thu, 14 Oct 2010 21:10:48 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7A11D.3030907@redhat.com> Message-ID: <852929580.570711287105048789.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> ----- "Ryan Lerch" wrote: > Style - "Coloured Title bar, offset icon " > Brand - Common + 1 Lee From dmison at redhat.com Fri Oct 15 03:26:33 2010 From: dmison at redhat.com (Darrin Mison) Date: Fri, 15 Oct 2010 13:26:33 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1153300579.633471287104578303.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> References: <1153300579.633471287104578303.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1287113193.8630.2.camel@dhcp-1-137.bne.redhat.com> On Thu, 2010-10-14 at 21:02 -0400, Sean Rogers wrote: > I also think the green may be too strong for the note as it brings more attention to it than is perhaps warranted. > Agreed. Perhaps a lighter or desaturated green ? From rlerch at redhat.com Fri Oct 15 04:01:47 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Fri, 15 Oct 2010 14:01:47 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <852929580.570711287105048789.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> References: <852929580.570711287105048789.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> Message-ID: <4CB7D22B.1010508@redhat.com> I think the majority of previous contributors to this discussion have now voted. I have tallied up the votes where first choices get 2 points, and 1 point to secondary preference (if given) The Coloured Title bar, offset icon option with 18 points the coloured border option came in second with 7 points. The overwhelming winner is the Coloured Title Bar option. IMHO, we should try to get this basic functionality implemented in the common brand, while keeping the discussion going to address the issues some have expressed with regards to both the colour choice of the Note, and icon choice for Note, Important and Warning. cheers, ryanlerch From jfearn at redhat.com Fri Oct 15 04:44:37 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 15 Oct 2010 14:44:37 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7D22B.1010508@redhat.com> References: <852929580.570711287105048789.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> <4CB7D22B.1010508@redhat.com> Message-ID: <4CB7DC35.5040207@redhat.com> Ryan Lerch wrote: > I think the majority of previous contributors to this discussion have > now voted. I have tallied up the votes where first choices get 2 points, > and 1 point to secondary preference (if given) > > The Coloured Title bar, offset icon option with 18 points > the coloured border option came in second with 7 points. > > The overwhelming winner is the Coloured Title Bar option. > > IMHO, we should try to get this basic functionality implemented in the > common brand, while keeping the discussion going to address the issues > some have expressed with regards to both the colour choice of the Note, > and icon choice for Note, Important and Warning. +1 If you count first votes it's 8 to 2. Since most of the requested changes have been accepted in to the common brand, the customizations for a brand that wishes to use colored borders will be fairly small, which makes maintaining them much easier. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Fri Oct 15 04:59:47 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 15 Oct 2010 14:59:47 +1000 Subject: [publican-list] Installing from source on fedora Message-ID: <4CB7DFC3.8060007@redhat.com> Andrew Ross has kindly documented how to install and run trunk: https://fedorahosted.org/publican/wiki/Installing If you are feeling game and would like to risk your productivity the instructions there should help you! Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From rlerch at redhat.com Fri Oct 15 05:03:29 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Fri, 15 Oct 2010 15:03:29 +1000 Subject: [publican-list] Installing from source on fedora In-Reply-To: <4CB7DFC3.8060007@redhat.com> References: <4CB7DFC3.8060007@redhat.com> Message-ID: <4CB7E0A1.4030302@redhat.com> On 10/15/2010 02:59 PM, Jeffrey Fearn wrote: > Andrew Ross has kindly documented how to install and run trunk: > https://fedorahosted.org/publican/wiki/Installing > > If you are feeling game and would like to risk your productivity the > instructions there should help you! > > Cheers, Jeff. > Thanks so much for this Andrew! I was setting up a new test machine the other day, and these instructions (especially the deps list) would have been super useful! cheers, and thanks again. ryanlerch From r.landmann at redhat.com Fri Oct 15 05:39:56 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Fri, 15 Oct 2010 15:39:56 +1000 Subject: [publican-list] Installing from source on fedora In-Reply-To: <4CB7DFC3.8060007@redhat.com> References: <4CB7DFC3.8060007@redhat.com> Message-ID: <4CB7E92C.50701@redhat.com> On 10/15/2010 02:59 PM, Jeffrey Fearn wrote: > Andrew Ross has kindly documented how to install and run trunk: > https://fedorahosted.org/publican/wiki/Installing > > If you are feeling game and would like to risk your productivity the > instructions there should help you! > +1 Can I add that this is the number one way in which people can help out with Publican development? If you're running trunk, notice something weird, *and file a bug*, the issue can get corrected before the next version hits the streets. As Linus' Law states: "Given enough eyeballs, all bugs are shallow."[0] Nobody builds your books more often than you, and nobody knows your books as well as you do; therefore nobody else is anywhere near as likely to notice anything strange about them. Once you have the Build script set up on your system as described on Andrew's wiki page, upgrading to a new version of trunk takes no more than two commands and a couple of minutes. If there's ever something seriously broken in trunk, downgrading to the latest stable version is a single command and even less time than that. The key, of course, is reporting anything strange that you see, and not just working around it[1] or ignoring it.[2] Cheers Rudi [0] Eric S. Raymond, "The Cathedral and the Bazaar" -- http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html [1] http://2.bp.blogspot.com/_N82afJPvr7Q/Riy-oWpCtUI/AAAAAAAAB9k/cOO1gPQ0GH0/s320/not_my_job.jpg [2] http://humour.200ok.com.au/img/not-my-job-redux.jpg From misty at redhat.com Fri Oct 15 06:14:50 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Fri, 15 Oct 2010 02:14:50 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7D22B.1010508@redhat.com> Message-ID: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> It is live in trunk now, and looks fanTASTIC! Thanks Jeff and Ryan! ----- "Ryan Lerch" wrote: > From: "Ryan Lerch" > To: "Lee Carlon" , "Publican discussions" > Sent: Friday, October 15, 2010 2:01:47 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) > > I think the majority of previous contributors to this discussion have > > now voted. I have tallied up the votes where first choices get 2 > points, > and 1 point to secondary preference (if given) > > The Coloured Title bar, offset icon option with 18 points > the coloured border option came in second with 7 points. > > The overwhelming winner is the Coloured Title Bar option. > > IMHO, we should try to get this basic functionality implemented in the > > common brand, while keeping the discussion going to address the issues > > some have expressed with regards to both the colour choice of the > Note, > and icon choice for Note, Important and Warning. > > cheers, > ryanlerch > > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones Content Author, ECS Brisbane Ph: +61 7 3514 8105 RHCT #60501081553354 Purgamentum init, exit purgamentum. From serogers at redhat.com Fri Oct 15 06:21:30 2010 From: serogers at redhat.com (Sean Rogers) Date: Fri, 15 Oct 2010 02:21:30 -0400 (EDT) Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <737536310.649581287123690854.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Yeah, excellent work! It is a massive improvement. - Sean ----- "Misty Stanley-Jones" wrote: | It is live in trunk now, and looks fanTASTIC! Thanks Jeff and Ryan! | | ----- "Ryan Lerch" wrote: | | > From: "Ryan Lerch" | > To: "Lee Carlon" , "Publican discussions" | | > Sent: Friday, October 15, 2010 2:01:47 PM GMT +10:00 Brisbane | > Subject: Re: [publican-list] RFC: Modified JBoss brand (was Re: RFE | for Publican Brands) | > | > I think the majority of previous contributors to this discussion | have | > | > now voted. I have tallied up the votes where first choices get 2 | > points, | > and 1 point to secondary preference (if given) | > | > The Coloured Title bar, offset icon option with 18 points | > the coloured border option came in second with 7 points. | > | > The overwhelming winner is the Coloured Title Bar option. | > | > IMHO, we should try to get this basic functionality implemented in | the | > | > common brand, while keeping the discussion going to address the | issues | > | > some have expressed with regards to both the colour choice of the | > Note, | > and icon choice for Note, Important and Warning. | > | > cheers, | > ryanlerch | > | > | > | > _______________________________________________ | > publican-list mailing list | > publican-list at redhat.com | > https://www.redhat.com/mailman/listinfo/publican-list | > Wiki: https://fedorahosted.org/publican | | -- | Misty Stanley-Jones | Content Author, ECS Brisbane | Ph: +61 7 3514 8105 | RHCT #60501081553354 | Purgamentum init, exit purgamentum. | | _______________________________________________ | publican-list mailing list | publican-list at redhat.com | https://www.redhat.com/mailman/listinfo/publican-list | Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Fri Oct 15 06:26:02 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 15 Oct 2010 16:26:02 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CB7F3FA.7060409@redhat.com> Misty Stanley-Jones wrote: > It is live in trunk now, and looks fanTASTIC! Thanks Jeff and Ryan! Yeah it looks heaps better. I'd like to thank Misty for driving this change. Sometimes it's hard to get people involved and motivated, but you have done it well on this issue! Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From rlerch at redhat.com Fri Oct 15 06:41:18 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Fri, 15 Oct 2010 16:41:18 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7F3FA.7060409@redhat.com> References: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB7F3FA.7060409@redhat.com> Message-ID: <4CB7F78E.4020500@redhat.com> On 10/15/2010 04:26 PM, Jeffrey Fearn wrote: > Misty Stanley-Jones wrote: >> It is live in trunk now, and looks fanTASTIC! Thanks Jeff and Ryan! > > Yeah it looks heaps better. I'd like to thank Misty for driving this > change. +1 It has been something that has annoyed me for ages, and i am so glad with the outcome! cheers, ryanlerch > > Cheers, Jeff. > From smumford at redhat.com Fri Oct 15 07:41:11 2010 From: smumford at redhat.com (Scott Mumford) Date: Fri, 15 Oct 2010 17:41:11 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB7F78E.4020500@redhat.com> References: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB7F3FA.7060409@redhat.com> <4CB7F78E.4020500@redhat.com> Message-ID: <4CB80597.4020904@redhat.com> :-D Thanks to everyone who was involved with this. The result is awesome! Is anyone else considering republishing all their books to get this slickness out into the world asap? Scott Mumford Associate Content Author Engineering Content Services Random fun fact: Mexicans consumed more Coca-Cola products than Americans, on average, in 2005. The average Mexican consumed 533 beverages during 2005, while the average American consumed 431. On 10/15/10 16:41, Ryan Lerch wrote: > On 10/15/2010 04:26 PM, Jeffrey Fearn wrote: >> Misty Stanley-Jones wrote: >>> It is live in trunk now, and looks fanTASTIC! Thanks Jeff and Ryan! >> >> Yeah it looks heaps better. I'd like to thank Misty for driving this >> change. > +1 > It has been something that has annoyed me for ages, and i am so glad > with the outcome! > > cheers, > ryanlerch >> >> 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 r.landmann at redhat.com Sun Oct 17 22:59:14 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 18 Oct 2010 08:59:14 +1000 Subject: [publican-list] RFC: Modified JBoss brand (was Re: RFE for Publican Brands) In-Reply-To: <4CB80597.4020904@redhat.com> References: <1306860334.700861287123290967.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> <4CB7F3FA.7060409@redhat.com> <4CB7F78E.4020500@redhat.com> <4CB80597.4020904@redhat.com> Message-ID: <4CBB7FC2.2080006@redhat.com> On 10/15/2010 05:41 PM, Scott Mumford wrote: > :-D > Thanks to everyone who was involved with this. The result is awesome! > > Is anyone else considering republishing all their books to get this > slickness out into the world asap? > Note that these changes will not be available for books published through Brew until the next release of Publican, and that discussion about the precise shade of green for "Notes" and about the icons in all these admonitions is still ongoing :) Cheers Rudi From rlerch at redhat.com Mon Oct 18 00:33:27 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Mon, 18 Oct 2010 10:33:27 +1000 Subject: [publican-list] Code Samples highlighting colours Message-ID: <4CBB95D7.4050805@redhat.com> I was looking at the updated styles for s and noticed that some of the colours used to highlight the different elements of code in them can be a little hard to see (and sometimes a bit jarring) Does anyone have any thoughts on the current default colours used, and maybe some thoughts on a better palette to use for this highlighting? cheers, ryanlerch From jfearn at redhat.com Mon Oct 18 00:48:44 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Mon, 18 Oct 2010 10:48:44 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <4CBB95D7.4050805@redhat.com> References: <4CBB95D7.4050805@redhat.com> Message-ID: <4CBB996C.4000502@redhat.com> Ryan Lerch wrote: > I was looking at the updated styles for s and noticed > that some of the colours used to highlight the different elements of > code in them can be a little hard to see (and sometimes a bit jarring) > > Does anyone have any thoughts on the current default colours used, They are bad. Here is the existing pallet in cut down form: Alert: #0000ff BaseN: #007f00 BString: #5C3566 Char: #ff00ff Comment: #FF00FF DataType: #0000ff DecVal: #00007f Error: #ff0000 Float: #00007f Function: #007f00 IString: #5C3566 Keyword: #002F5D Operator: #ffa500 Others: #b03060 RegionMarker: #96b9ff Reserved: #9b30ff String: #5C3566 Variable: #0000ff Warning: #0000ff The exact mapping is language specific, you have to read the individual modules to know the exact mapping, but it's probably better to try and abstract from that. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From misty at redhat.com Mon Oct 18 00:50:21 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Sun, 17 Oct 2010 20:50:21 -0400 (EDT) Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <4CBB95D7.4050805@redhat.com> Message-ID: <828358671.1012351287363021916.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Ryan Lerch" wrote: > Does anyone have any thoughts on the current default colours used, and > > maybe some thoughts on a better palette to use for this highlighting? > I vote for using the same rules that Eclipse uses by default. Thoughts? > cheers, > ryanlerch > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones, RHCE Content Author, ECS Brisbane Projects: https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 From jmorgan at redhat.com Mon Oct 18 01:44:57 2010 From: jmorgan at redhat.com (Jared Morgan) Date: Sun, 17 Oct 2010 21:44:57 -0400 (EDT) Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <17476716.1.1287366035799.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Message-ID: <22385279.4.1287366095279.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Isn't this the same problem I raised in a recent publican ticket about syntax highlighter kate problems? https://bugzilla.redhat.com/show_bug.cgi?id=639751 Jared Morgan Content Author Red Hat Asia Pacific 1/193 North Quay BRISBANE QLD 4000 P: +61 7 3514 8242 M: +61 413 005 479 From: "Misty Stanley-Jones" To: "Publican discussions" Sent: Monday, October 18, 2010 10:50:21 AM Subject: Re: [publican-list] Code Samples highlighting colours ----- "Ryan Lerch" wrote: > Does anyone have any thoughts on the current default colours used, and > > maybe some thoughts on a better palette to use for this highlighting? > I vote for using the same rules that Eclipse uses by default. Thoughts? > cheers, > ryanlerch > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones, RHCE Content Author, ECS Brisbane Projects: https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican -------------- next part -------------- An HTML attachment was scrubbed... URL: From misty at redhat.com Mon Oct 18 01:48:49 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Sun, 17 Oct 2010 21:48:49 -0400 (EDT) Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <22385279.4.1287366095279.JavaMail.jmorgan@dhcp-1-169.bne.redhat.com> Message-ID: <1399933865.1021401287366529814.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> ----- "Jared Morgan" wrote: > > Isn't this the same problem I raised in a recent publican ticket about > syntax highlighter kate problems? > > https://bugzilla.redhat.com/show_bug.cgi?id=639751 Not quite, Jared. The colors themselves are controlled by CSS. Your bug has to do with the actual way the highlighting is done, not the colors used to render it. Ryan just wants to tweak the CSS, as far as I know. Misty > > Jared Morgan > Content Author > Red Hat Asia Pacific > 1/193 North Quay > BRISBANE QLD 4000 > > P: +61 7 3514 8242 > M: +61 413 005 479 > > > From: "Misty Stanley-Jones" > To: "Publican discussions" > Sent: Monday, October 18, 2010 10:50:21 AM > Subject: Re: [publican-list] Code Samples highlighting colours > > ----- "Ryan Lerch" wrote: > > > Does anyone have any thoughts on the current default colours used, > and > > > > maybe some thoughts on a better palette to use for this > highlighting? > > > > I vote for using the same rules that Eclipse uses by default. > Thoughts? > > > cheers, > > ryanlerch > > > > _______________________________________________ > > publican-list mailing list > > publican-list at redhat.com > > https://www.redhat.com/mailman/listinfo/publican-list > > Wiki: https://fedorahosted.org/publican > > -- > > > Misty Stanley-Jones, RHCE > Content Author, ECS Brisbane > Projects: > https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule > > IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 > > _______________________________________________ > 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 -- Misty Stanley-Jones, RHCE Content Author, ECS Brisbane Projects: https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 From rlerch at redhat.com Mon Oct 18 02:22:58 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Mon, 18 Oct 2010 12:22:58 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <1399933865.1021401287366529814.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1399933865.1021401287366529814.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CBBAF82.5010602@redhat.com> On 10/18/2010 11:48 AM, Misty Stanley-Jones wrote: > ----- "Jared Morgan" wrote: >> Isn't this the same problem I raised in a recent publican ticket about >> syntax highlighter kate problems? >> >> https://bugzilla.redhat.com/show_bug.cgi?id=639751 > Not quite, Jared. The colors themselves are controlled by CSS. Your bug has to do with the actual way the highlighting is done, not the colors used to render it. Ryan just wants to tweak the CSS, as far as I know. Yes. My query was purely about the colour choice in CSS. cheers, ryanlerch From rlerch at redhat.com Mon Oct 18 02:41:05 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Mon, 18 Oct 2010 12:41:05 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <4CBB996C.4000502@redhat.com> References: <4CBB95D7.4050805@redhat.com> <4CBB996C.4000502@redhat.com> Message-ID: <4CBBB3C1.7010401@redhat.com> On 10/18/2010 10:48 AM, Jeffrey Fearn wrote: > Ryan Lerch wrote: >> I was looking at the updated styles for s and >> noticed that some of the colours used to highlight the different >> elements of code in them can be a little hard to see (and sometimes a >> bit jarring) >> >> Does anyone have any thoughts on the current default colours used, > > They are bad. +1 Here the colours listed below (by Jeff) can be viewed in context in the image attached. cheers, ryanlerch > > Here is the existing pallet in cut down form: > > Alert: #0000ff > BaseN: #007f00 > BString: #5C3566 > Char: #ff00ff > Comment: #FF00FF > DataType: #0000ff > DecVal: #00007f > Error: #ff0000 > Float: #00007f > Function: #007f00 > IString: #5C3566 > Keyword: #002F5D > Operator: #ffa500 > Others: #b03060 > RegionMarker: #96b9ff > Reserved: #9b30ff > String: #5C3566 > Variable: #0000ff > Warning: #0000ff > > The exact mapping is language specific, you have to read the > individual modules to know the exact mapping, but it's probably better > to try and abstract from that. > > Cheers, Jeff. > -------------- next part -------------- A non-text attachment was scrubbed... Name: colours.png Type: image/png Size: 64702 bytes Desc: not available URL: From misty at redhat.com Mon Oct 18 03:04:25 2010 From: misty at redhat.com (misty at redhat.com) Date: Sun, 17 Oct 2010 23:04:25 -0400 (EDT) Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <664684803.1032011287370561327.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <1557717708.1033021287371065982.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> For accessibility, #ff00ff, #ffa500, #96b9ff need to go. #9b30ff is debatable. ----- "Ryan Lerch" wrote: > From: "Ryan Lerch" > To: "Publican discussions" > Sent: Monday, October 18, 2010 12:41:05 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] Code Samples highlighting colours > > On 10/18/2010 10:48 AM, Jeffrey Fearn wrote: > > Ryan Lerch wrote: > >> I was looking at the updated styles for s and > >> noticed that some of the colours used to highlight the different > >> elements of code in them can be a little hard to see (and sometimes > a > >> bit jarring) > >> > >> Does anyone have any thoughts on the current default colours used, > > > > They are bad. > +1 > > Here the colours listed below (by Jeff) can be viewed in context in > the > image attached. > > cheers, > ryanlerch > > > > Here is the existing pallet in cut down form: > > > > Alert: #0000ff > > BaseN: #007f00 > > BString: #5C3566 > > Char: #ff00ff > > Comment: #FF00FF > > DataType: #0000ff > > DecVal: #00007f > > Error: #ff0000 > > Float: #00007f > > Function: #007f00 > > IString: #5C3566 > > Keyword: #002F5D > > Operator: #ffa500 > > Others: #b03060 > > RegionMarker: #96b9ff > > Reserved: #9b30ff > > String: #5C3566 > > Variable: #0000ff > > Warning: #0000ff > > > > The exact mapping is language specific, you have to read the > > individual modules to know the exact mapping, but it's probably > better > > to try and abstract from that. > > > > Cheers, Jeff. > > > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones, RHCE Content Author, ECS Brisbane Projects: https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 From r.landmann at redhat.com Mon Oct 18 03:22:31 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 18 Oct 2010 13:22:31 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <1557717708.1033021287371065982.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <1557717708.1033021287371065982.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CBBBD77.9040302@redhat.com> On 10/18/2010 01:04 PM, misty at redhat.com wrote: > For accessibility, #ff00ff, #ffa500, #96b9ff need to go. #9b30ff is debatable. > Here's a tool that validates colours against the Web Content Accessibility Guidelines (WCAG) 2.0 http://www.snook.ca/technical/colour_contrast/colour.html according to it, #9b30ff text on a #f5f5f5 background also fails one of the four standards, so yeah, is probably not a good choice. Cheers Rudi From rlerch at redhat.com Mon Oct 18 04:06:49 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Mon, 18 Oct 2010 14:06:49 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <4CBBB3C1.7010401@redhat.com> References: <4CBB95D7.4050805@redhat.com> <4CBB996C.4000502@redhat.com> <4CBBB3C1.7010401@redhat.com> Message-ID: <4CBBC7D9.8010207@redhat.com> On 10/18/2010 12:41 PM, Ryan Lerch wrote: > On 10/18/2010 10:48 AM, Jeffrey Fearn wrote: >> Ryan Lerch wrote: >>> I was looking at the updated styles for s and >>> noticed that some of the colours used to highlight the different >>> elements of code in them can be a little hard to see (and sometimes >>> a bit jarring) >>> >>> Does anyone have any thoughts on the current default colours used, >> >> They are bad. > +1 > > Here the colours listed below (by Jeff) can be viewed in context in > the image attached. And, i got them wrong first time around. Misrepresented magenta as green. attached is a repaired image. cheers, ryanlerch >> > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -------------- next part -------------- A non-text attachment was scrubbed... Name: colours-fixed.png Type: image/png Size: 63969 bytes Desc: not available URL: From jwulf at redhat.com Mon Oct 18 04:30:34 2010 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 18 Oct 2010 14:30:34 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <828358671.1012351287363021916.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <828358671.1012351287363021916.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CBBCD6A.4090503@redhat.com> On 10/18/2010 10:50 AM, Misty Stanley-Jones wrote: > ----- "Ryan Lerch" wrote: > >> Does anyone have any thoughts on the current default colours used, and >> >> maybe some thoughts on a better palette to use for this highlighting? >> > > I vote for using the same rules that Eclipse uses by default. Thoughts? Saves us having to think. > >> cheers, >> ryanlerch >> >> _______________________________________________ >> publican-list mailing list >> publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list >> Wiki: https://fedorahosted.org/publican > From dmison at redhat.com Mon Oct 18 22:08:05 2010 From: dmison at redhat.com (dmison at redhat.com) Date: Mon, 18 Oct 2010 18:08:05 -0400 (EDT) Subject: [publican-list] Code Samples highlighting colours In-Reply-To: <828358671.1012351287363021916.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <828358671.1012351287363021916.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: On 18/10/2010, at 10:51 AM, Misty Stanley-Jones wrote: > ----- "Ryan Lerch" wrote: > >> Does anyone have any thoughts on the current default colours used, and >> >> maybe some thoughts on a better palette to use for this highlighting? >> > > I vote for using the same rules that Eclipse uses by default. Thoughts? Not a bad idea. Was the original colour scheme based on anything ? > >> cheers, >> ryanlerch >> >> _______________________________________________ >> publican-list mailing list >> publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list >> Wiki: https://fedorahosted.org/publican > > -- > > > Misty Stanley-Jones, RHCE > Content Author, ECS Brisbane > Projects: https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule > IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Mon Oct 18 22:58:28 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 19 Oct 2010 08:58:28 +1000 Subject: [publican-list] Code Samples highlighting colours In-Reply-To: References: <828358671.1012351287363021916.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CBCD114.1010300@redhat.com> dmison at redhat.com wrote: > > On 18/10/2010, at 10:51 AM, Misty Stanley-Jones wrote: > >> ----- "Ryan Lerch" wrote: >> >>> Does anyone have any thoughts on the current default colours used, and >>> >>> maybe some thoughts on a better palette to use for this highlighting? >>> >> I vote for using the same rules that Eclipse uses by default. Thoughts? > > Not a bad idea. Assuming someone knows what the actual colors are and which tags they map to. > Was the original colour scheme based on anything ? Nope. This is a tango color scheme someone pointed out to me http://a0u.xanga.com/718956889/tango-schema-for-kate/ sadly I forget who it was ... memory is pants :( Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From jfearn at redhat.com Mon Oct 18 23:28:06 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 19 Oct 2010 09:28:06 +1000 Subject: [publican-list] RFC: Accessibility Review Message-ID: <4CBCD806.6000406@redhat.com> Hi, it's been a long time since we have done a review of the accessibility of our output; the web site output has never had such a review. I don't have time to perform or chair such a review, would anyone be interested in chairing or participating in this effort? I believe the web site output has the basic structure required for a fully accessible site, however it's probable that the bits aren't linked to in all the correct places, or in all the correct ways. e.g. we have a page that doesn't use javascript or objects and links to all the content, but is it linked to where it's required, and is the page itself formated in a usable fashion? Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From misty at redhat.com Mon Oct 18 23:52:38 2010 From: misty at redhat.com (Misty Stanley-Jones) Date: Mon, 18 Oct 2010 19:52:38 -0400 (EDT) Subject: [publican-list] RFC: Accessibility Review In-Reply-To: <4CBCD806.6000406@redhat.com> Message-ID: <225049861.164921287445958962.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> I like this idea. I know a couple of people (external) who would probably be happy to do an accessibility review, at least from a vision perspective. I think this is one thing that can really set apart our documentation products from the competition. I do not have enough experience in this to chair a committee, but I am happy to participate on one and to give opinions (as always). Misty ----- "Jeffrey Fearn" wrote: > From: "Jeffrey Fearn" > To: "Publican List" > Sent: Tuesday, October 19, 2010 9:28:06 AM GMT +10:00 Brisbane > Subject: [publican-list] RFC: Accessibility Review > > Hi, it's been a long time since we have done a review of the > accessibility of our output; the web site output has never had such a > > review. > > I don't have time to perform or chair such a review, would anyone be > interested in chairing or participating in this effort? > > I believe the web site output has the basic structure required for a > fully accessible site, however it's probable that the bits aren't > linked > to in all the correct places, or in all the correct ways. > > e.g. we have a page that doesn't use javascript or objects and links > to > all the content, but is it linked to where it's required, and is the > page itself formated in a usable fashion? > > Cheers, Jeff. > > -- > Jeff Fearn > Software Engineer > Engineering Operations > Red Hat, Inc > Freedom ... courage ... Commitment ... ACCOUNTABILITY > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican -- Misty Stanley-Jones, RHCE Content Author, ECS Brisbane Projects: https://engineering.redhat.com/trac/ContentServices/wiki/MistySchedule IRC: misty_wrk (Freenode) / Ph: +61 7 3514 8105 From lbrindle at redhat.com Tue Oct 19 00:01:44 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Tue, 19 Oct 2010 11:01:44 +1100 Subject: [publican-list] RFC: Accessibility Review In-Reply-To: <4CBCD806.6000406@redhat.com> References: <4CBCD806.6000406@redhat.com> Message-ID: <4CBCDFE8.7040408@redhat.com> On 10/19/2010 10:28 AM, Jeffrey Fearn wrote: > Hi, it's been a long time since we have done a review of the > accessibility of our output; the web site output has never had such a > review. > > I don't have time to perform or chair such a review, would anyone be > interested in chairing or participating in this effort? > > I believe the web site output has the basic structure required for a > fully accessible site, however it's probable that the bits aren't linked > to in all the correct places, or in all the correct ways. > > e.g. we have a page that doesn't use javascript or objects and links to > all the content, but is it linked to where it's required, and is the > page itself formated in a usable fashion? > > Cheers, Jeff. > Hmm ... accessibility or usability? L -- Lana Brindley Content Author Engineering Content Services +61 7 3514 8178 - ext (85) 88178 RHEL5 RHCT: 605008757717273 "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use hammer." -- IBM maintenance manual, 1975 From jfearn at redhat.com Tue Oct 19 00:08:37 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 19 Oct 2010 10:08:37 +1000 Subject: [publican-list] RFC: Accessibility Review In-Reply-To: <4CBCDFE8.7040408@redhat.com> References: <4CBCD806.6000406@redhat.com> <4CBCDFE8.7040408@redhat.com> Message-ID: <4CBCE185.6030202@redhat.com> Lana Brindley wrote: > On 10/19/2010 10:28 AM, Jeffrey Fearn wrote: >> Hi, it's been a long time since we have done a review of the >> accessibility of our output; the web site output has never had such a >> review. >> >> I don't have time to perform or chair such a review, would anyone be >> interested in chairing or participating in this effort? >> >> I believe the web site output has the basic structure required for a >> fully accessible site, however it's probable that the bits aren't linked >> to in all the correct places, or in all the correct ways. >> >> e.g. we have a page that doesn't use javascript or objects and links to >> all the content, but is it linked to where it's required, and is the >> page itself formated in a usable fashion? >> >> Cheers, Jeff. >> > > Hmm ... accessibility or usability? Accessibility. e.g. US Section 508 compliance. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From lbrindle at redhat.com Tue Oct 19 00:42:55 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Tue, 19 Oct 2010 11:42:55 +1100 Subject: [publican-list] RFC: Accessibility Review In-Reply-To: <4CBCE185.6030202@redhat.com> References: <4CBCD806.6000406@redhat.com> <4CBCDFE8.7040408@redhat.com> <4CBCE185.6030202@redhat.com> Message-ID: <4CBCE98F.8010204@redhat.com> On 10/19/2010 11:08 AM, Jeffrey Fearn wrote: > Lana Brindley wrote: >> On 10/19/2010 10:28 AM, Jeffrey Fearn wrote: >>> Hi, it's been a long time since we have done a review of the >>> accessibility of our output; the web site output has never had such a >>> review. >>> >>> I don't have time to perform or chair such a review, would anyone be >>> interested in chairing or participating in this effort? >>> >>> I believe the web site output has the basic structure required for a >>> fully accessible site, however it's probable that the bits aren't linked >>> to in all the correct places, or in all the correct ways. >>> >>> e.g. we have a page that doesn't use javascript or objects and links to >>> all the content, but is it linked to where it's required, and is the >>> page itself formated in a usable fashion? >>> >>> Cheers, Jeff. >>> >> >> Hmm ... accessibility or usability? > > > Accessibility. e.g. US Section 508 compliance. > Well, I know nothing about accessibility, so I'll leave that to the experts. If ever we decide to do a usability review, though, I'd like to be involved. L -- Lana Brindley Content Author Engineering Content Services +61 7 3514 8178 - ext (85) 88178 RHEL5 RHCT: 605008757717273 "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use hammer." -- IBM maintenance manual, 1975 From rlerch at redhat.com Tue Oct 19 02:22:02 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Tue, 19 Oct 2010 12:22:02 +1000 Subject: [publican-list] RFC: Accessibility Review In-Reply-To: <225049861.164921287445958962.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> References: <225049861.164921287445958962.JavaMail.root@zmail03.collab.prod.int.phx2.redhat.com> Message-ID: <4CBD00CA.7070606@redhat.com> On 10/19/2010 09:52 AM, Misty Stanley-Jones wrote: > I like this idea. I know a couple of people (external) who would probably be happy to do an accessibility review, at least from a vision perspective. I think this is one thing that can really set apart our documentation products from the competition. I do not have enough experience in this to chair a committee, but I am happy to participate on one and to give opinions (as always). > > Misty From a theorectical point of view we could start by assessing publican's output (both documents and the website) against The W3C's Web Content Accessibility Guidelines [1]. But I defninitely agree that a real life review would be even more valuable. cheers, ryanlerch [1] - http://www.w3.org/TR/WAI-WEBCONTENT/ > ----- "Jeffrey Fearn" wrote: > >> From: "Jeffrey Fearn" >> To: "Publican List" >> Sent: Tuesday, October 19, 2010 9:28:06 AM GMT +10:00 Brisbane >> Subject: [publican-list] RFC: Accessibility Review >> >> Hi, it's been a long time since we have done a review of the >> accessibility of our output; the web site output has never had such a >> >> review. >> >> I don't have time to perform or chair such a review, would anyone be >> interested in chairing or participating in this effort? >> >> I believe the web site output has the basic structure required for a >> fully accessible site, however it's probable that the bits aren't >> linked >> to in all the correct places, or in all the correct ways. >> >> e.g. we have a page that doesn't use javascript or objects and links >> to >> all the content, but is it linked to where it's required, and is the >> page itself formated in a usable fashion? >> >> Cheers, Jeff. >> >> -- >> Jeff Fearn >> Software Engineer >> Engineering Operations >> Red Hat, Inc >> Freedom ... courage ... Commitment ... ACCOUNTABILITY >> >> _______________________________________________ >> publican-list mailing list >> publican-list at redhat.com >> https://www.redhat.com/mailman/listinfo/publican-list >> Wiki: https://fedorahosted.org/publican From sparks at fedoraproject.org Thu Oct 21 03:22:45 2010 From: sparks at fedoraproject.org (Eric "Sparks" Christensen) Date: Wed, 20 Oct 2010 23:22:45 -0400 Subject: [publican-list] Open Feedback Publishing System (OFPS) Message-ID: <4CBFB205.4030004@fedoraproject.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jared pointed out a neat "feature" O'Reilly is trying out called Open Feedback Publishing System (OFPS)[1]. This allows readers to leave comments on a particular paragraph of a document. Contrary to its name, OFPS is NOT open source. There are other projects that are open source that do the same thing. The one I saw listed was called Wooki[2]. I'm wondering if something similar could be implemented within Publican to be used, at a minimum, in our draft documentation. It might make it easier for people to let us know of problems without filing a bug. Because it would take less time to leave feedback we might find that we receive more than we currently do through BZ. [1] http://labs.oreilly.com/ofps.html [2] http://wookicentral.com - --Eric Fedora Docs Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMv7IEAAoJEDbiLlqcYamxHPMP/0BXgJ45r5fmvC8Dt9jbVcYz 9WDOr3y8ZQhWrKaA1yAPzpvBsfkX3Ou/yi9tzAOLfJC1+8LmsDMIDlFmFA9KTpFL yH6vtDx1rU+XK65GMo8xl9gJ7sjNkoDhXiZXn9FXC04TODht/V7Sz1eIbUeaUmz5 VJKsnHWMXXyKIEdjLw6YkjSc+grHe8snNa+PEiXqJdpm9uSo1MHcJbkf6ItLG40g dBhksOAyyLvbvCret6xkXyw+BuoT5rrJX+vCbh552D1CHh1OBjbgWVWTSWDfHXPy a+SP7o6fxmhNP/tPyCBhjCkf5OPId9NChd/YqRL33Rk7dP6NfeRGp5l+Ky3SjwA0 pFdmKplcY874VthpKzbsMjDBWB1uCairlQlWXQ8nDdPNwDoqAEfCEQ4YxEZNab4C bAq5QwmmKATXdn4ylChE1W091aI5PUQ9tWJ42LGp6qSO0LienU/cyxbXAep0Lexw kr68jfEXepp+oi8I0RwYIeiN9K7iKOswqREMmXpQhUztSlsc+ZEKMq8wYKtYuj10 klGJuOnfSBtMRi/0QP2No4SWOYwDxhVmsGsiFHOYh/9RotlIYdWS3REGJinxYUab bbC64zkpU51tkcTqGAiXP0qXKTf4w6vOcc1bsrSpTeRPjQHUaVqSXD5PPK+68Yi+ 0Nd5jTNcWbDxi9EWjmu+ =NGYl -----END PGP SIGNATURE----- From djorm at redhat.com Thu Oct 21 04:36:18 2010 From: djorm at redhat.com (David Jorm) Date: Thu, 21 Oct 2010 00:36:18 -0400 (EDT) Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <1071431863.1272861287635611716.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1455720001.1273001287635778080.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> We have prototyped some mechanisms for doing this as an extension to publican. It seems viable, but there are some questions around the best method to implement it. +1 from me, I want to see this as a feature of publican if possible. I am happy to help prototype mechanisms to drive this discussion. David ----- Original Message ----- From: "Eric \"Sparks\" Christensen" To: "Publican discussions" Sent: Thursday, October 21, 2010 1:22:45 PM GMT +10:00 Brisbane Subject: [publican-list] Open Feedback Publishing System (OFPS) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jared pointed out a neat "feature" O'Reilly is trying out called Open Feedback Publishing System (OFPS)[1]. This allows readers to leave comments on a particular paragraph of a document. Contrary to its name, OFPS is NOT open source. There are other projects that are open source that do the same thing. The one I saw listed was called Wooki[2]. I'm wondering if something similar could be implemented within Publican to be used, at a minimum, in our draft documentation. It might make it easier for people to let us know of problems without filing a bug. Because it would take less time to leave feedback we might find that we receive more than we currently do through BZ. [1] http://labs.oreilly.com/ofps.html [2] http://wookicentral.com - --Eric Fedora Docs Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMv7IEAAoJEDbiLlqcYamxHPMP/0BXgJ45r5fmvC8Dt9jbVcYz 9WDOr3y8ZQhWrKaA1yAPzpvBsfkX3Ou/yi9tzAOLfJC1+8LmsDMIDlFmFA9KTpFL yH6vtDx1rU+XK65GMo8xl9gJ7sjNkoDhXiZXn9FXC04TODht/V7Sz1eIbUeaUmz5 VJKsnHWMXXyKIEdjLw6YkjSc+grHe8snNa+PEiXqJdpm9uSo1MHcJbkf6ItLG40g dBhksOAyyLvbvCret6xkXyw+BuoT5rrJX+vCbh552D1CHh1OBjbgWVWTSWDfHXPy a+SP7o6fxmhNP/tPyCBhjCkf5OPId9NChd/YqRL33Rk7dP6NfeRGp5l+Ky3SjwA0 pFdmKplcY874VthpKzbsMjDBWB1uCairlQlWXQ8nDdPNwDoqAEfCEQ4YxEZNab4C bAq5QwmmKATXdn4ylChE1W091aI5PUQ9tWJ42LGp6qSO0LienU/cyxbXAep0Lexw kr68jfEXepp+oi8I0RwYIeiN9K7iKOswqREMmXpQhUztSlsc+ZEKMq8wYKtYuj10 klGJuOnfSBtMRi/0QP2No4SWOYwDxhVmsGsiFHOYh/9RotlIYdWS3REGJinxYUab bbC64zkpU51tkcTqGAiXP0qXKTf4w6vOcc1bsrSpTeRPjQHUaVqSXD5PPK+68Yi+ 0Nd5jTNcWbDxi9EWjmu+ =NGYl -----END PGP SIGNATURE----- _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Thu Oct 21 06:03:31 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Thu, 21 Oct 2010 16:03:31 +1000 Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <4CBFB205.4030004@fedoraproject.org> References: <4CBFB205.4030004@fedoraproject.org> Message-ID: <4CBFD7B3.7030202@redhat.com> Eric "Sparks" Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jared pointed out a neat "feature" O'Reilly is trying out called Open > Feedback Publishing System (OFPS)[1]. This allows readers to leave > comments on a particular paragraph of a document. > > Contrary to its name, OFPS is NOT open source. There are other projects > that are open source that do the same thing. The one I saw listed was > called Wooki[2]. > > I'm wondering if something similar could be implemented within Publican > to be used, at a minimum, in our draft documentation. It might make it > easier for people to let us know of problems without filing a bug. > Because it would take less time to leave feedback we might find that we > receive more than we currently do through BZ. > > [1] http://labs.oreilly.com/ofps.html > [2] http://wookicentral.com One of the founding constraints to Publican design is that there is no server side scripting. I don't see how you could do this without doing server side scripting and processing of some kind. It would require a major change in direction for Publican to become a web service instead of a static content provider. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From djorm at redhat.com Thu Oct 21 06:19:28 2010 From: djorm at redhat.com (David Jorm) Date: Thu, 21 Oct 2010 02:19:28 -0400 (EDT) Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <4CBFD7B3.7030202@redhat.com> Message-ID: <864476086.1276441287641968292.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I wouldn't change that design constraint to support this, but publican could provide the capability to link in to external feedback-capturing mechanisms. Off the top of my head, one approach would be to conditionally allow books to be configured as feedback=mechanism, where mechanism is a pluggable option. For Red Hat use, we could build a bugzilla feedback extension, which would inject code into the output (probably just for html) allowing you to leave feedback for a particular chapter/section. This would be static output, providing a deep link into bugzilla with the appropriate component, version etc. to match the book filled out. Plugins could be developed for any other feedback mechanism people want to use. David ----- Original Message ----- From: "Jeffrey Fearn" To: sparks at fedoraproject.org, "Publican discussions" Sent: Thursday, October 21, 2010 4:03:31 PM GMT +10:00 Brisbane Subject: Re: [publican-list] Open Feedback Publishing System (OFPS) Eric "Sparks" Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jared pointed out a neat "feature" O'Reilly is trying out called Open > Feedback Publishing System (OFPS)[1]. This allows readers to leave > comments on a particular paragraph of a document. > > Contrary to its name, OFPS is NOT open source. There are other projects > that are open source that do the same thing. The one I saw listed was > called Wooki[2]. > > I'm wondering if something similar could be implemented within Publican > to be used, at a minimum, in our draft documentation. It might make it > easier for people to let us know of problems without filing a bug. > Because it would take less time to leave feedback we might find that we > receive more than we currently do through BZ. > > [1] http://labs.oreilly.com/ofps.html > [2] http://wookicentral.com One of the founding constraints to Publican design is that there is no server side scripting. I don't see how you could do this without doing server side scripting and processing of some kind. It would require a major change in direction for Publican to become a web service instead of a static content provider. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Fri Oct 22 02:40:37 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Fri, 22 Oct 2010 12:40:37 +1000 Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <864476086.1276441287641968292.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> References: <864476086.1276441287641968292.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Message-ID: <1287715237.31441.40.camel@captcha> On Thu, 2010-10-21 at 02:19 -0400, David Jorm wrote: > I wouldn't change that design constraint to support this, but publican could provide the capability to link in to external feedback-capturing mechanisms. Off the top of my head, one approach would be to conditionally allow books to be configured as feedback=mechanism, where mechanism is a pluggable option. For Red Hat use, we could build a bugzilla feedback extension, which would inject code into the output (probably just for html) allowing you to leave feedback for a particular chapter/section. This would be static output, providing a deep link into bugzilla with the appropriate component, version etc. to match the book filled out. Plugins could be developed for any other feedback mechanism people want to use. > > David > > ----- Original Message ----- > From: "Jeffrey Fearn" > To: sparks at fedoraproject.org, "Publican discussions" > Sent: Thursday, October 21, 2010 4:03:31 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] Open Feedback Publishing System (OFPS) > > Eric "Sparks" Christensen wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Jared pointed out a neat "feature" O'Reilly is trying out called Open > > Feedback Publishing System (OFPS)[1]. This allows readers to leave > > comments on a particular paragraph of a document. > > > > Contrary to its name, OFPS is NOT open source. There are other projects > > that are open source that do the same thing. The one I saw listed was > > called Wooki[2]. > > > > I'm wondering if something similar could be implemented within Publican > > to be used, at a minimum, in our draft documentation. It might make it > > easier for people to let us know of problems without filing a bug. > > Because it would take less time to leave feedback we might find that we > > receive more than we currently do through BZ. > > > > [1] http://labs.oreilly.com/ofps.html > > [2] http://wookicentral.com > > One of the founding constraints to Publican design is that there is no > server side scripting. I don't see how you could do this without doing > server side scripting and processing of some kind. It would require a > major change in direction for Publican to become a web service instead > of a static content provider. I don't think this addresses what Eric was asking for. In the case of interactive systems like OFPS or Wooki, I think it would be better for those kind of tools to use publican at the back-end instead of trying to integrate publican in to their front end; or implementing such a system from scratch specifically for Publican use. Similar to how Transifex can handle Publican's directory structure, so we don't have to expend a lot of effort trying to make one. I haven't seen any discussions about a plugin architecture, how it would work, or what it would do, so I don't have any position on that. Overriding the output is easy to do at the brand level, if there was a brad implementing this then we could look at how it works and decide whether and how best to integrate it in to Publican, or even if it's more appropriate to try and get it in to the upstream DocBook XSL as XSL function calls, similar to how highlighting and call-outs work. 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 djorm at redhat.com Fri Oct 22 03:22:06 2010 From: djorm at redhat.com (David Jorm) Date: Thu, 21 Oct 2010 23:22:06 -0400 (EDT) Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <1287715237.31441.40.camel@captcha> Message-ID: <925426364.1408561287717726781.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> I eagerly await Rudi's publican brand creation tech talk so I can get the skills to proof of concept this :) ----- Original Message ----- From: "Jeff Fearn" To: "Publican discussions" Sent: Friday, October 22, 2010 12:40:37 PM GMT +10:00 Brisbane Subject: Re: [publican-list] Open Feedback Publishing System (OFPS) On Thu, 2010-10-21 at 02:19 -0400, David Jorm wrote: > I wouldn't change that design constraint to support this, but publican could provide the capability to link in to external feedback-capturing mechanisms. Off the top of my head, one approach would be to conditionally allow books to be configured as feedback=mechanism, where mechanism is a pluggable option. For Red Hat use, we could build a bugzilla feedback extension, which would inject code into the output (probably just for html) allowing you to leave feedback for a particular chapter/section. This would be static output, providing a deep link into bugzilla with the appropriate component, version etc. to match the book filled out. Plugins could be developed for any other feedback mechanism people want to use. > > David > > ----- Original Message ----- > From: "Jeffrey Fearn" > To: sparks at fedoraproject.org, "Publican discussions" > Sent: Thursday, October 21, 2010 4:03:31 PM GMT +10:00 Brisbane > Subject: Re: [publican-list] Open Feedback Publishing System (OFPS) > > Eric "Sparks" Christensen wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Jared pointed out a neat "feature" O'Reilly is trying out called Open > > Feedback Publishing System (OFPS)[1]. This allows readers to leave > > comments on a particular paragraph of a document. > > > > Contrary to its name, OFPS is NOT open source. There are other projects > > that are open source that do the same thing. The one I saw listed was > > called Wooki[2]. > > > > I'm wondering if something similar could be implemented within Publican > > to be used, at a minimum, in our draft documentation. It might make it > > easier for people to let us know of problems without filing a bug. > > Because it would take less time to leave feedback we might find that we > > receive more than we currently do through BZ. > > > > [1] http://labs.oreilly.com/ofps.html > > [2] http://wookicentral.com > > One of the founding constraints to Publican design is that there is no > server side scripting. I don't see how you could do this without doing > server side scripting and processing of some kind. It would require a > major change in direction for Publican to become a web service instead > of a static content provider. I don't think this addresses what Eric was asking for. In the case of interactive systems like OFPS or Wooki, I think it would be better for those kind of tools to use publican at the back-end instead of trying to integrate publican in to their front end; or implementing such a system from scratch specifically for Publican use. Similar to how Transifex can handle Publican's directory structure, so we don't have to expend a lot of effort trying to make one. I haven't seen any discussions about a plugin architecture, how it would work, or what it would do, so I don't have any position on that. Overriding the output is easy to do at the brand level, if there was a brad implementing this then we could look at how it works and decide whether and how best to integrate it in to Publican, or even if it's more appropriate to try and get it in to the upstream DocBook XSL as XSL function calls, similar to how highlighting and call-outs work. 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 _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From sparks at fedoraproject.org Fri Oct 22 11:28:00 2010 From: sparks at fedoraproject.org (Eric "Sparks" Christensen) Date: Fri, 22 Oct 2010 07:28:00 -0400 Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <4CBFD7B3.7030202@redhat.com> References: <4CBFB205.4030004@fedoraproject.org> <4CBFD7B3.7030202@redhat.com> Message-ID: <4CC17540.6070607@fedoraproject.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/21/2010 02:03 AM, Jeffrey Fearn wrote: > Eric "Sparks" Christensen wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Jared pointed out a neat "feature" O'Reilly is trying out called Open >> Feedback Publishing System (OFPS)[1]. This allows readers to leave >> comments on a particular paragraph of a document. >> >> Contrary to its name, OFPS is NOT open source. There are other projects >> that are open source that do the same thing. The one I saw listed was >> called Wooki[2]. >> >> I'm wondering if something similar could be implemented within Publican >> to be used, at a minimum, in our draft documentation. It might make it >> easier for people to let us know of problems without filing a bug. >> Because it would take less time to leave feedback we might find that we >> receive more than we currently do through BZ. >> >> [1] http://labs.oreilly.com/ofps.html >> [2] http://wookicentral.com > > One of the founding constraints to Publican design is that there is no > server side scripting. I don't see how you could do this without doing > server side scripting and processing of some kind. It would require a > major change in direction for Publican to become a web service instead > of a static content provider. > > Cheers, Jeff. > Jeff, Yeah if Publican could maybe not implement the solution but provide the hooks for such a solution I think this could work without having Publican become a larger monster. Having the hooks available would mean we wouldn't be locked into a particular solution, which is good. - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMwXU/AAoJEDbiLlqcYamxmF8QALuCUxsuNY2MSGHiNr+22fmQ pXC7PSqi5VkPUl9KQMU/SoEgEvkjKb7BCNBeknfqCa/pE5Wj91kKN0GhR52Bd75k XtDxtviyanc8dnKodR18D+u3yfBtMavu/oFegCNLGd0LoquWmr0+LINpZcbugr0j lODiOKaUkz28kd4Mhv0KanDDEFpo+sOL62w48rXB3JRSXL8HPmKvT1bLSAwg1B7Y 0VxCmbW5JavpO3I/o099E6mjOQj9b6Lgwv2Msd0KfOxSIgb046iIXw+ASttCYkIm ZrDHqkFtNxjtbdHYjqUCJFOUl9N4ja206YboVSpupid4yLls4lZuieKQbH0vaLrQ Yr5wYXBLdGayGvBzFjbxXSJrQ0qimWnvQCgW5CCqjmJwzvGF7LQZPiWS7eukAjAI CTzmauE2dd5kdFROsbiCT+8j0OHY9XYZ33vUD7fbWIlBvunWK53EiZTL7hgRrYls ZttvoMAj4cgJYDv5hLtRnHz31KeII4yyt52+JyGDfNPfJFt4AcXAHA7bgsRT0eIN u9bpvaegALT0v9gtfwLO/hbdZYo9C/CXQvh0AJI44DkK9SchndyidPzn7eNehd0n bF4GI5HDHQUstnfJ46Min/fbHnlTHtj0QaDavSlKTNUA4CD8X/xK6VjHtkg8tOCJ WtdVEyWWWU2sfrakrcO1 =yTq2 -----END PGP SIGNATURE----- From jfearn at redhat.com Mon Oct 25 02:38:41 2010 From: jfearn at redhat.com (Jeff Fearn) Date: Mon, 25 Oct 2010 12:38:41 +1000 Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <4CC17540.6070607@fedoraproject.org> References: <4CBFB205.4030004@fedoraproject.org> <4CBFD7B3.7030202@redhat.com> <4CC17540.6070607@fedoraproject.org> Message-ID: <1287974321.2452.11.camel@captcha> On Fri, 2010-10-22 at 07:28 -0400, Eric "Sparks" Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/21/2010 02:03 AM, Jeffrey Fearn wrote: > > Eric "Sparks" Christensen wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Jared pointed out a neat "feature" O'Reilly is trying out called Open > >> Feedback Publishing System (OFPS)[1]. This allows readers to leave > >> comments on a particular paragraph of a document. > >> > >> Contrary to its name, OFPS is NOT open source. There are other projects > >> that are open source that do the same thing. The one I saw listed was > >> called Wooki[2]. > >> > >> I'm wondering if something similar could be implemented within Publican > >> to be used, at a minimum, in our draft documentation. It might make it > >> easier for people to let us know of problems without filing a bug. > >> Because it would take less time to leave feedback we might find that we > >> receive more than we currently do through BZ. > >> > >> [1] http://labs.oreilly.com/ofps.html > >> [2] http://wookicentral.com > > > > One of the founding constraints to Publican design is that there is no > > server side scripting. I don't see how you could do this without doing > > server side scripting and processing of some kind. It would require a > > major change in direction for Publican to become a web service instead > > of a static content provider. > > > > Cheers, Jeff. > > > > Jeff, > > Yeah if Publican could maybe not implement the solution but provide the > hooks for such a solution I think this could work without having > Publican become a larger monster. Having the hooks available would mean > we wouldn't be locked into a particular solution, which is good. I guess we'd need someone to define what a hook is and list what hooks they'd need. It's a command line app, I'd expect people to just use the command line, not try and use it like a library; like we do with FOP. 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 djorm at redhat.com Mon Oct 25 03:52:54 2010 From: djorm at redhat.com (David Jorm) Date: Sun, 24 Oct 2010 23:52:54 -0400 (EDT) Subject: [publican-list] Open Feedback Publishing System (OFPS) In-Reply-To: <1287974321.2452.11.camel@captcha> Message-ID: <1056981073.13391287978774247.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> VDSM has hooks which are subscribed to by putting a script in a directory. For example, if you want something to run when the before_vm_start hook is triggered, you put something executable in /usr/libexec/vdsm/before_vm_start/. Everything in the directory gets run, in alphabetical order. This makes for a simple hooks mechanism at the command line, without developing library/APIesque capabilities. ----- Original Message ----- From: "Jeff Fearn" To: sparks at fedoraproject.org Cc: "Publican discussions" Sent: Monday, October 25, 2010 12:38:41 PM GMT +10:00 Brisbane Subject: Re: [publican-list] Open Feedback Publishing System (OFPS) On Fri, 2010-10-22 at 07:28 -0400, Eric "Sparks" Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/21/2010 02:03 AM, Jeffrey Fearn wrote: > > Eric "Sparks" Christensen wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Jared pointed out a neat "feature" O'Reilly is trying out called Open > >> Feedback Publishing System (OFPS)[1]. This allows readers to leave > >> comments on a particular paragraph of a document. > >> > >> Contrary to its name, OFPS is NOT open source. There are other projects > >> that are open source that do the same thing. The one I saw listed was > >> called Wooki[2]. > >> > >> I'm wondering if something similar could be implemented within Publican > >> to be used, at a minimum, in our draft documentation. It might make it > >> easier for people to let us know of problems without filing a bug. > >> Because it would take less time to leave feedback we might find that we > >> receive more than we currently do through BZ. > >> > >> [1] http://labs.oreilly.com/ofps.html > >> [2] http://wookicentral.com > > > > One of the founding constraints to Publican design is that there is no > > server side scripting. I don't see how you could do this without doing > > server side scripting and processing of some kind. It would require a > > major change in direction for Publican to become a web service instead > > of a static content provider. > > > > Cheers, Jeff. > > > > Jeff, > > Yeah if Publican could maybe not implement the solution but provide the > hooks for such a solution I think this could work without having > Publican become a larger monster. Having the hooks available would mean > we wouldn't be locked into a particular solution, which is good. I guess we'd need someone to define what a hook is and list what hooks they'd need. It's a command line app, I'd expect people to just use the command line, not try and use it like a library; like we do with FOP. 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 _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Tue Oct 26 02:26:28 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Tue, 26 Oct 2010 12:26:28 +1000 Subject: [publican-list] Publican 2.3 released Message-ID: <4CC63C54.4050509@redhat.com> Hi everybody! Publican 2.3 is out the door, building on various platforms has begun. This release has some release notes written up by Ryan Lerch and Darrin Minson, check them out if you'd like a verbose (legible) explanation of the changes http://jfearn.fedorapeople.org/en-US/Publican/2.3/html-single/Release_Notes/index.html The updated users' Guide is at http://jfearn.fedorapeople.org/en-US/Publican/2.3/html/Users_Guide/index.html Here is the short change log: - Prepend product name to product/version splash pages. - Fix bash completion for --brand and --type. - Use --nocolours in spec files. - Update tocs when home/product/version pages are updated. BZ #612027 - Scroll to current entry in navigation menu. - Highlight current book in navigation menu. - Fix single quote in abstract/subtitle breaking RPM install. BZ #642088 - Fix RPM website not installing cleanly. - Fix splash page icon wrap. BZ #642109 - Moved titles before: example, equation, table. BZ #638787 - Change html and PDF style for verbatim & example. BZ #638787 - Change html and PDF style for admonitions. BZ #638787 - Fix HTML footer style and layout. - Add bump action Tech Preview. - Fix indexterm merge missing nested nodes. BZ #643275 - Add phrase to translatable tag list. BZ #643287 - Fix POT files breaking when using HTML::Tree 4.0. - Fix translated label missing from manually installed book. BZ #643781 - Add icon.svg to Create Book. BZ #644105 - Add XML dump options for site config. - Fix histroy typo - Stop max_image_width overriding XML width settings. - Decrease white space at top and bottom of PDF. - Fix toc links to refentry in chunked HTML. BZ #645602 Thanks to all the people involved in getting this version out, with special props to Misty for her motivation of the style rework, and Rudi for his tireless help in advocating, testing, and community relations. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From lbrindle at redhat.com Tue Oct 26 21:35:22 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Wed, 27 Oct 2010 08:35:22 +1100 Subject: [publican-list] epub MRG documentation compatibility with Nook In-Reply-To: <4CC73BBC.7040802@redhat.com> References: <4CC73BBC.7040802@redhat.com> Message-ID: <4CC7499A.6060806@redhat.com> On 10/27/2010 07:36 AM, Neal Kim wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Out of curiosity I downloaded the new MRG 1.3 documentation in epub > format and copied it over to my Nook. Both the installation and user > guide do not work. When I attempt to read either document, my Nook takes > a couple minutes to load the document, at which point I cannot go beyond > the first page. > Which Installation and User Guides? Messaging or Grid? > I am wondering if there have been similar reports? My Nook has been > updated to the latest available firmware (1.4). I haven't personally (other than Will's Kindle issues), but I've cc'd the Publican list to get some more feedback. Lana -- Lana Brindley Content Author Engineering Content Services +61 7 3514 8178 - ext (85) 88178 RHEL5 RHCT: 605008757717273 "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use hammer." -- IBM maintenance manual, 1975 From lbrindle at redhat.com Tue Oct 26 22:04:47 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Wed, 27 Oct 2010 09:04:47 +1100 Subject: [publican-list] epub MRG documentation compatibility with Nook In-Reply-To: <4CC74D0C.50504@redhat.com> References: <4CC73BBC.7040802@redhat.com> <4CC7499A.6060806@redhat.com> <4CC74D0C.50504@redhat.com> Message-ID: <4CC7507F.1020304@redhat.com> On 10/27/2010 08:50 AM, Neal Kim wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have only tried the Grid documentation. OK, so for the benefit of the Publican list, it's these books: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/epub/Grid_User_Guide/Red_Hat_Enterprise_MRG-1.3-Grid_User_Guide-en-US.epub http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/epub/Grid_Installation_Guide/Red_Hat_Enterprise_MRG-1.3-Grid_Installation_Guide-en-US.epub > > I am just raising the issue just in case anyone else is using a Nook :D I wonder if it's Nook-related, or Publican-related, though ... ? > > Thanks Lana. You're welcome. L -- Lana Brindley Content Author Engineering Content Services +61 7 3514 8178 - ext (85) 88178 RHEL5 RHCT: 605008757717273 "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use hammer." -- IBM maintenance manual, 1975 From dmison at redhat.com Tue Oct 26 23:39:33 2010 From: dmison at redhat.com (dmison at redhat.com) Date: Tue, 26 Oct 2010 19:39:33 -0400 (EDT) Subject: [publican-list] epub MRG documentation compatibility with Nook Message-ID: <6B403013-D615-49DE-AF56-FDA6C2F14E39@redhat.com> They work ok in Stanza on iPad, not able to check in iBooks until I get home (shakes tiny angry fist at Steve Jobs) On 27/10/2010, at 8:05 AM, Lana Brindley wrote: > On 10/27/2010 08:50 AM, Neal Kim wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I have only tried the Grid documentation. > > OK, so for the benefit of the Publican list, it's these books: > http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/epub/Grid_User_Guide/Red_Hat_Enterprise_MRG-1.3-Grid_User_Guide-en-US.epub > http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/epub/Grid_Installation_Guide/Red_Hat_Enterprise_MRG-1.3-Grid_Installation_Guide-en-US.epub > >> >> I am just raising the issue just in case anyone else is using a Nook :D > > I wonder if it's Nook-related, or Publican-related, though ... ? > >> >> Thanks Lana. > > You're welcome. > > L > > -- > Lana Brindley > Content Author > Engineering Content Services > +61 7 3514 8178 - ext (85) 88178 > RHEL5 RHCT: 605008757717273 > > "All parts should go together without forcing. You must remember that > the parts you are reassembling were disassembled by you. Therefore, if > you can't get them together again, there must be a reason. By all > means, do not use hammer." -- IBM maintenance manual, 1975 > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From lbrindle at redhat.com Wed Oct 27 19:43:06 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Thu, 28 Oct 2010 06:43:06 +1100 Subject: [publican-list] broken splash page images on docs.redhat.com Message-ID: <4CC880CA.30805@redhat.com> Hi everyone, Sorry if this isn't new to anyone, but I'm seeing broken images on the sub-directory splash pages on docs.redhat.com. Two screenshots attached so you can see what I mean. Lana -- Lana Brindley Content Author Engineering Content Services +61 7 3514 8178 - ext (85) 88178 RHEL5 RHCT: 605008757717273 "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use hammer." -- IBM maintenance manual, 1975 -------------- next part -------------- A non-text attachment was scrubbed... Name: BrokenImages_Rhel.png Type: image/png Size: 165640 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BrokenImages_Sat.png Type: image/png Size: 161727 bytes Desc: not available URL: From jfearn at redhat.com Wed Oct 27 22:28:22 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Thu, 28 Oct 2010 08:28:22 +1000 Subject: [publican-list] broken splash page images on docs.redhat.com In-Reply-To: <4CC880CA.30805@redhat.com> References: <4CC880CA.30805@redhat.com> Message-ID: <4CC8A786.3050508@redhat.com> Lana Brindley wrote: > Hi everyone, > > Sorry if this isn't new to anyone, but I'm seeing broken images on the > sub-directory splash pages on docs.redhat.com. Yeah it's new, please open a bug. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From lbrindle at redhat.com Wed Oct 27 23:01:45 2010 From: lbrindle at redhat.com (Lana Brindley) Date: Thu, 28 Oct 2010 10:01:45 +1100 Subject: [publican-list] broken splash page images on docs.redhat.com In-Reply-To: <4CC8A786.3050508@redhat.com> References: <4CC880CA.30805@redhat.com> <4CC8A786.3050508@redhat.com> Message-ID: <4CC8AF59.4090407@redhat.com> On 10/28/2010 09:28 AM, Jeffrey Fearn wrote: > Lana Brindley wrote: >> Hi everyone, >> >> Sorry if this isn't new to anyone, but I'm seeing broken images on the >> sub-directory splash pages on docs.redhat.com. > > Yeah it's new, please open a bug. > > Cheers, Jeff. > https://bugzilla.redhat.com/show_bug.cgi?id=647338 L -- Lana Brindley Content Author Engineering Content Services +61 7 3514 8178 - ext (85) 88178 RHEL5 RHCT: 605008757717273 The Territorial Imperatives of The Trumpeter Swan Obviously, the title of this section is a bit bizarre. Its real title should be "LET'S GET STARTED," but that's such a disgustingly cute phrase that it has no business adorning any page. -- Franklin Ace 1000 manual, 1983 From rlerch at redhat.com Wed Oct 27 23:13:10 2010 From: rlerch at redhat.com (Ryan Lerch) Date: Thu, 28 Oct 2010 09:13:10 +1000 Subject: [publican-list] broken splash page images on docs.redhat.com In-Reply-To: <4CC880CA.30805@redhat.com> References: <4CC880CA.30805@redhat.com> Message-ID: <4CC8B206.9030706@redhat.com> Just FYI - Firefox hides the brokenness. It appears that the issue is only visible on webkit based browsers. regards, ryanlerch On 10/28/2010 05:43 AM, Lana Brindley wrote: > Hi everyone, > > Sorry if this isn't new to anyone, but I'm seeing broken images on the > sub-directory splash pages on docs.redhat.com. > > Two screenshots attached so you can see what I mean. > > Lana > > > _______________________________________________ > publican-list mailing list > publican-list at redhat.com > https://www.redhat.com/mailman/listinfo/publican-list > Wiki: https://fedorahosted.org/publican From jfearn at redhat.com Wed Oct 27 23:15:37 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Thu, 28 Oct 2010 09:15:37 +1000 Subject: [publican-list] broken splash page images on docs.redhat.com In-Reply-To: <4CC8B206.9030706@redhat.com> References: <4CC880CA.30805@redhat.com> <4CC8B206.9030706@redhat.com> Message-ID: <4CC8B299.1030402@redhat.com> Ryan Lerch wrote: > Just FYI - Firefox hides the brokenness. > > It appears that the issue is only visible on webkit based browsers. To clarify, Firefox doesn't display a broken image for missing backgrounds, however the fact that the background is not not visible and the link is not click-able, is still obvious. Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY From dmison at redhat.com Thu Oct 28 07:13:10 2010 From: dmison at redhat.com (Darrin Mison) Date: Thu, 28 Oct 2010 17:13:10 +1000 Subject: [publican-list] indexes for procedures/examples/figures etc Message-ID: <1288249990.3425.340.camel@dhcp-1-137.bne.redhat.com> Is it possible to include automatic indexes for certain types of elements, eg. an index of procedures, an index of figures etc. Is this something that would require brand changes or a new publican feature ? From jfearn at redhat.com Thu Oct 28 22:40:33 2010 From: jfearn at redhat.com (Jeffrey Fearn) Date: Fri, 29 Oct 2010 08:40:33 +1000 Subject: [publican-list] indexes for procedures/examples/figures etc In-Reply-To: <1288249990.3425.340.camel@dhcp-1-137.bne.redhat.com> References: <1288249990.3425.340.camel@dhcp-1-137.bne.redhat.com> Message-ID: <4CC9FBE1.9000104@redhat.com> Darrin Mison wrote: > Is it possible to include automatic indexes for certain types of > elements, eg. an index of procedures, an index of figures etc. > > Is this something that would require brand changes or a new publican > feature ? Probably best to do it at the brand level, by overriding generate.toc in a custom xsl file. Most brands already have basic custom xsl files, to overide the title colours and such. http://docbook.sourceforge.net/release/xsl/current/doc/html/generate.toc.html Cheers, Jeff. -- Jeff Fearn Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY