From jwulf at redhat.com  Fri Nov  4 07:05:44 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Fri, 04 Nov 2011 17:05:44 +1000
Subject: [publican-list] Help with xsl customization
Message-ID: <4EB38EC8.6040308@redhat.com>

I'm trying to create a custom brand that renders
<mediaobject><videoobject> in html as <iframe>, rather than <embed>.

I've found what I think is the xsl that applies this tag, in
graphics.xsl [1]:

<xsl:template match="videodata">
  <xsl:call-template name="process.image">
    <xsl:with-param name="tag" select="'iframe'"/>
    <xsl:with-param name="alt">
      <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
    </xsl:with-param>
  </xsl:call-template>
</xsl:template>

[1] http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl

I'm not sure where this is imported in publican. It's not in
publican/datadir/xsl.

I've created a publican brand [2] with a graphics.xsl file in it, with
the following contents:

<?xml version='1.0'?>
<xsl:stylesheet
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

    <xsl:import
href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"/>
    <xsl:import
href="http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl"/>

<xsl:template match="videodata">
  <xsl:call-template name="process.image">
    <xsl:with-param name="tag" select="'iframe'"/>
    <xsl:with-param name="alt">
      <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
    </xsl:with-param>
  </xsl:call-template>
</xsl:template>

</xsl:stylesheet>

[2] https://svn.devel.redhat.com/repos/ecs/toolkit/publican-redhat-video

This doesn't work, though.

Anyone know how to do this?

- Josh



From jwulf at redhat.com  Fri Nov  4 07:07:44 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Fri, 04 Nov 2011 17:07:44 +1000
Subject: [publican-list] Help with xsl customization
In-Reply-To: <4EB38EC8.6040308@redhat.com>
References: <4EB38EC8.6040308@redhat.com>
Message-ID: <4EB38F40.3020907@redhat.com>

On 11/04/2011 05:05 PM, Joshua Wulf wrote:
> I'm trying to create a custom brand that renders
> <mediaobject><videoobject> in html as <iframe>, rather than <embed>.
> 
> I've found what I think is the xsl that applies this tag, in
> graphics.xsl [1]:
> 
> <xsl:template match="videodata">
>   <xsl:call-template name="process.image">
>     <xsl:with-param name="tag" select="'iframe'"/>
>     <xsl:with-param name="alt">
>       <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
>     </xsl:with-param>
>   </xsl:call-template>
> </xsl:template>
> 
Sorry, that should be "embed" above, rather than "iframe":

<xsl:template match="videodata">
  <xsl:call-template name="process.image">
    <xsl:with-param name="tag" select="'embed'"/>
    <xsl:with-param name="alt">
      <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
    </xsl:with-param>
  </xsl:call-template>
</xsl:template>



> [1] http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl
> 
> I'm not sure where this is imported in publican. It's not in
> publican/datadir/xsl.
> 
> I've created a publican brand [2] with a graphics.xsl file in it, with
> the following contents:
> 
> <?xml version='1.0'?>
> <xsl:stylesheet
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
> 
>     <xsl:import
> href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"/>
>     <xsl:import
> href="http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl"/>
> 
> <xsl:template match="videodata">
>   <xsl:call-template name="process.image">
>     <xsl:with-param name="tag" select="'iframe'"/>
>     <xsl:with-param name="alt">
>       <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
>     </xsl:with-param>
>   </xsl:call-template>
> </xsl:template>
> 
> </xsl:stylesheet>
> 
> [2] https://svn.devel.redhat.com/repos/ecs/toolkit/publican-redhat-video
> 
> This doesn't work, though.
> 
> Anyone know how to do this?
> 
> - Josh
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican


-- 
Give us your feedback on JBoss Enterprise Documentation, take the key
survey:
http://www.keysurvey.com/survey/361436/1065/



From misty at redhat.com  Mon Nov  7 06:35:07 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Mon, 07 Nov 2011 01:35:07 -0500 (EST)
Subject: [publican-list] Compiling Publican in Mac OSX Lion
In-Reply-To: <4fdc7ed4-c721-4bfe-9f27-5e10068477df@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <6fe05e6c-f49f-4f07-ae09-ae8b24ede2f4@zmail13.collab.prod.int.phx2.redhat.com>

I have succeeded in compiling Publican in Mac OSX Lion. First I'll describe what I did. Then I'll ask some questions about some problems.

1. Download the source for Publican from SVN.
2. Install the XCode developer tools from the Mac App Store.
3. Install Mac Ports (http://www.macports.org/)
   a. This was needed in order to get the module Image::Magick installed properly. With the native Perl, it was failing to build.
4. Install ImageMagick with PerlMagick via Mac Ports:
   a. port install ImageMagick +no_x11 +perl
5. Change to the branch/publican-2.x/ directory in the Publican source.
6. Execute perl ./Build.PL
7. Note the first dependency missing, open cpan, and do "install <module_name>".
8. Repeat #6 and #7 a bunch of times.
   a. Note: I had to do "force install Makefile:Parser" because otherwise it was failing
9. When I got a clean run of "perl ./Build.PL" I ran "./Build" and then "sudo ./Build install"
   a. It installed Publican into /opt/local/bin
   b. It installed the Common config into /usr/share/publican
10. Run "publican create --name=testbook" and note that the book is created.
11. Change to "testbook" and run "publican build --format=html --langs=en-US"
   a. It takes a long time.
   b. Then it fails because it can't find the common brand files.
12. Specify the directory for the brand and common config:
   publican build --format=html --langs=en-US --common_config=/usr/share/publican --common_content=/usr/share/publican/Common_Content
   a. It takes a looooooong time.
   b. It works.

So my questions are:

1. How can I troubleshoot the "It takes a long time"? It is during the " Using XML::LibXSLT on /usr/share/publican/Common_Content/JBoss_EAP6/xsl/html.xsl" phase, and I think it might be because it's trying to find the file in several different locations before it finds the proper one. I actually used dtruss, which is the equivalent of strace in linux. It almost looked like it was having trouble finding the DTD file, even though the URL is accessible.

2. Is there a way for me to run the "./Build install" in such a way that it installs everything into /opt? That might help a bit.

Thanks,
Misty



From jfearn at redhat.com  Mon Nov  7 07:07:55 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Mon, 07 Nov 2011 17:07:55 +1000
Subject: [publican-list] Compiling Publican in Mac OSX Lion
In-Reply-To: <6fe05e6c-f49f-4f07-ae09-ae8b24ede2f4@zmail13.collab.prod.int.phx2.redhat.com>
References: <6fe05e6c-f49f-4f07-ae09-ae8b24ede2f4@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <4EB783CB.1050509@redhat.com>

On 11/07/2011 04:35 PM, Misty Stanley-Jones wrote:
> I have succeeded in compiling Publican in Mac OSX Lion. First I'll describe what I did. Then I'll ask some questions about some problems.
>
> 1. Download the source for Publican from SVN.
> 2. Install the XCode developer tools from the Mac App Store.
> 3. Install Mac Ports (http://www.macports.org/)
>     a. This was needed in order to get the module Image::Magick installed properly. With the native Perl, it was failing to build.
> 4. Install ImageMagick with PerlMagick via Mac Ports:
>     a. port install ImageMagick +no_x11 +perl
> 5. Change to the branch/publican-2.x/ directory in the Publican source.
> 6. Execute perl ./Build.PL
> 7. Note the first dependency missing, open cpan, and do "install<module_name>".
> 8. Repeat #6 and #7 a bunch of times.
>     a. Note: I had to do "force install Makefile:Parser" because otherwise it was failing
> 9. When I got a clean run of "perl ./Build.PL" I ran "./Build" and then "sudo ./Build install"
>     a. It installed Publican into /opt/local/bin
>     b. It installed the Common config into /usr/share/publican
> 10. Run "publican create --name=testbook" and note that the book is created.
> 11. Change to "testbook" and run "publican build --format=html --langs=en-US"
>     a. It takes a long time.
>     b. Then it fails because it can't find the common brand files.
> 12. Specify the directory for the brand and common config:
>     publican build --format=html --langs=en-US --common_config=/usr/share/publican --common_content=/usr/share/publican/Common_Content
>     a. It takes a looooooong time.
>     b. It works.
>
> So my questions are:
>
> 1. How can I troubleshoot the "It takes a long time"? It is during the " Using XML::LibXSLT on /usr/share/publican/Common_Content/JBoss_EAP6/xsl/html.xsl" phase, and I think it might be because it's trying to find the file in several different locations before it finds the proper one. I actually used dtruss, which is the equivalent of strace in linux. It almost looked like it was having trouble finding the DTD file, even though the URL is accessible.

It's probably looking for the DocBook XSL files, can't find them 
locally, so it goes off and downloads them. It doesn't cache things 
though, so it does this every time. You'd need to install them locally 
then workout how to set up an XML catalogue on OSX.

> 2. Is there a way for me to run the "./Build install" in such a way that it installs everything into /opt? That might help a bit.

You can try setting the base path, it might work ... or it might be 
creative O_O

./Build install --install_base /opt

Failing that you can override the paths individually, gives greater control:

./Build install --install_path datadir=/opt/???/publican --install_path 
generated=/opt/???/publican/sitetemplate  --install_path 
web=/opt/???/publican/sitetemplate --install_path 
templates=/opt/???/publican/templates --install_path etc=/opt/??? 
--install_path completion=???

Basically in Build.PL there is an entry 'install_path' and for each of 
the fields in there you can add an --install_path argument and override 
it to wherever you want.

Cheers, Jeff.

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From domingobecker at gmail.com  Mon Nov  7 14:18:56 2011
From: domingobecker at gmail.com (Domingo Becker)
Date: Mon, 7 Nov 2011 11:18:56 -0300
Subject: [publican-list] conditionally exclude a paragraph
Message-ID: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>

I would like to exclude a paragraph or section depending on the
language being built.

The paragraph must exist in all languages except the source one.

According to [1] I should use lang attribute, the section would look
like the following:

<section lang="en-US">
    <title>The title</title>
    ...
</section>

But what I really need is to exclude the paragraph when the language is en-US.

Is there an operator or something like lang!="en-US", to indicate for
all languages except en-US?

kind regards

Domingo Becker



From domingobecker at gmail.com  Mon Nov  7 16:10:20 2011
From: domingobecker at gmail.com (Domingo Becker)
Date: Mon, 7 Nov 2011 13:10:20 -0300
Subject: [publican-list] conditionally exclude a paragraph
In-Reply-To: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>
References: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>
Message-ID: <CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>

2011/11/7 Domingo Becker <domingobecker at gmail.com>:
> I would like to exclude a paragraph or section depending on the
> language being built.
>
> The paragraph must exist in all languages except the source one.
>
> According to [1] I should use lang attribute, the section would look
> like the following:
>
> <section lang="en-US">
> ? ?<title>The title</title>
> ? ?...
> </section>
>
> But what I really need is to exclude the paragraph when the language is en-US.
>
> Is there an operator or something like lang!="en-US", to indicate for
> all languages except en-US?
>

Sorry, I forgot the link.

[1] http://www.sagehill.net/docbookxsl/Profiling.html#MarkProfileText

kind regards

Domingo Becker



From jwulf at redhat.com  Mon Nov  7 23:40:57 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Tue, 08 Nov 2011 09:40:57 +1000
Subject: [publican-list] conditionally exclude a paragraph
In-Reply-To: <CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>
References: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>
	<CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>
Message-ID: <4EB86C89.4030502@redhat.com>

== The brute force method ==


<section lang="de-DE" lang="es-ES" lang="pt-BR" ...>
    <title>The title</title>
    ...
</section>


== Using Condition ==

You could also use "condition" [1], although it requires to be manually
switched when changing between en-US and non-en-US.

[1]
http://rlandmann.fedorapeople.org/pug/sect-Users_Guide-Conditional_tagging.html

So:

<section condition="non-EN">
    <title>The title</title>
    ...
</section>


and then in publican.cfg you set

condition: non-EN

When building non-en-US languages.

== Scripting Condition ==

You could automate the switching by calling a shellscript that sets this
depending on the lang that you are building. So:

mypublicanbuild.sh

if 'en-US' in langs[] then write 'condition: EN' to publican.cfg
else
  write 'condition: non-EN' to publican.cfg

== Publican RFE? Langs as Conditions ==

Maybe it would be useful if publican exposed the langs argument as an
array of 'condition's? Then it would be automatic.






On 11/08/2011 02:10 AM, Domingo Becker wrote:
> 2011/11/7 Domingo Becker <domingobecker at gmail.com>:
>> I would like to exclude a paragraph or section depending on the
>> language being built.
>>
>> The paragraph must exist in all languages except the source one.
>>
>> According to [1] I should use lang attribute, the section would look
>> like the following:
>>
>> <section lang="en-US">
>>    <title>The title</title>
>>    ...
>> </section>
>>
>> But what I really need is to exclude the paragraph when the language is en-US.
>>
>> Is there an operator or something like lang!="en-US", to indicate for
>> all languages except en-US?
>>
> 
> Sorry, I forgot the link.
> 
> [1] http://www.sagehill.net/docbookxsl/Profiling.html#MarkProfileText
> 
> kind regards
> 
> Domingo Becker
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican


-- 
Give us your feedback on JBoss Enterprise Documentation, take the key
survey:
http://www.keysurvey.com/survey/361436/1065/



From jfearn at redhat.com  Mon Nov  7 23:47:08 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Tue, 08 Nov 2011 09:47:08 +1000
Subject: [publican-list] conditionally exclude a paragraph
In-Reply-To: <4EB86C89.4030502@redhat.com>
References: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>	<CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>
	<4EB86C89.4030502@redhat.com>
Message-ID: <4EB86DFC.7090909@redhat.com>

On 11/08/2011 09:40 AM, Joshua Wulf wrote:
> == The brute force method ==
>
>
> <section lang="de-DE" lang="es-ES" lang="pt-BR" ...>

<section lang="de-DE,es-ES,pt-BR" ...>

Cheers, Jeff.

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From jfearn at redhat.com  Mon Nov  7 23:50:23 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Tue, 08 Nov 2011 09:50:23 +1000
Subject: [publican-list] Help with xsl customization
In-Reply-To: <4EB38EC8.6040308@redhat.com>
References: <4EB38EC8.6040308@redhat.com>
Message-ID: <4EB86EBF.2080907@redhat.com>

On 11/04/2011 05:05 PM, Joshua Wulf wrote:
> I'm trying to create a custom brand that renders
> <mediaobject><videoobject>  in html as<iframe>, rather than<embed>.
>
> I've found what I think is the xsl that applies this tag, in
> graphics.xsl [1]:
>
> <xsl:template match="videodata">
>    <xsl:call-template name="process.image">
>      <xsl:with-param name="tag" select="'iframe'"/>
>      <xsl:with-param name="alt">
>        <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
>      </xsl:with-param>
>    </xsl:call-template>
> </xsl:template>
>
> [1] http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl
>
> I'm not sure where this is imported in publican. It's not in
> publican/datadir/xsl.
>
> I've created a publican brand [2] with a graphics.xsl file in it, with
> the following contents:
>
> <?xml version='1.0'?>
> <xsl:stylesheet
>      xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
>
>      <xsl:import
> href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"/>
>      <xsl:import
> href="http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl"/>
>
> <xsl:template match="videodata">
>    <xsl:call-template name="process.image">
>      <xsl:with-param name="tag" select="'iframe'"/>
>      <xsl:with-param name="alt">
>        <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
>      </xsl:with-param>
>    </xsl:call-template>
> </xsl:template>
>
> </xsl:stylesheet>
>
> [2] https://svn.devel.redhat.com/repos/ecs/toolkit/publican-redhat-video
>
> This doesn't work, though.
>
> Anyone know how to do this?

In your html.xsl file add:

<xsl:import 
href="http://docbook.sourceforge.net/release/xsl/current/xhtml/graphics.xsl"/>

to the list of other imports.

Copy your videodata template in to html.xsl.

Delete your graphics.xsl file.

Rebuild brand.

Cheers, Jeff.

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From domingobecker at gmail.com  Tue Nov  8 04:01:06 2011
From: domingobecker at gmail.com (Domingo Becker)
Date: Tue, 8 Nov 2011 01:01:06 -0300
Subject: [publican-list] conditionally exclude a paragraph
In-Reply-To: <4EB86DFC.7090909@redhat.com>
References: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>
	<CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>
	<4EB86C89.4030502@redhat.com> <4EB86DFC.7090909@redhat.com>
Message-ID: <CABJ5b7pe5bUqM8yDRn+m-ga_1gBOxfcLq1gOiJ5zrrVA1VshFA@mail.gmail.com>

2011/11/7 Jeff Fearn <jfearn at redhat.com>:
> On 11/08/2011 09:40 AM, Joshua Wulf wrote:
>>
>> == The brute force method ==
>>
>>
>> <section lang="de-DE" lang="es-ES" lang="pt-BR" ...>
>
> <section lang="de-DE,es-ES,pt-BR" ...>
>

This seems to be the best way by now.

But perhaps, a Publican RFE: if Publican interprpets the ',' (comma)
operator in a string, then it would be possible to add a negation
operator like '!' in C++ inside the string.

The problem I want to solve is the one being discussed in [1].

Then Petr Kovar asked me if the paragraph including
"translator-credits" string would appear in the source language of the
manual [2]. And it's reasonable to exclude it when building the book
for the source language.

The <section lang="de-DE,es-ES,pt-BR" ...> approach will make book
writers work a little more. I don't know if they will like it.

Thank you guys.

[1] http://lists.fedoraproject.org/pipermail/trans/2011-November/009453.html

[2] http://lists.fedoraproject.org/pipermail/trans/2011-November/009455.html

kind regards

Domingo Becker



From jfearn at redhat.com  Tue Nov  8 04:47:48 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Tue, 08 Nov 2011 14:47:48 +1000
Subject: [publican-list] conditionally exclude a paragraph
In-Reply-To: <CABJ5b7pe5bUqM8yDRn+m-ga_1gBOxfcLq1gOiJ5zrrVA1VshFA@mail.gmail.com>
References: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>	<CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>	<4EB86C89.4030502@redhat.com>
	<4EB86DFC.7090909@redhat.com>
	<CABJ5b7pe5bUqM8yDRn+m-ga_1gBOxfcLq1gOiJ5zrrVA1VshFA@mail.gmail.com>
Message-ID: <4EB8B474.6020603@redhat.com>

On 11/08/2011 02:01 PM, Domingo Becker wrote:
> 2011/11/7 Jeff Fearn<jfearn at redhat.com>:
>> On 11/08/2011 09:40 AM, Joshua Wulf wrote:
>>>
>>> == The brute force method ==
>>>
>>>
>>> <section lang="de-DE" lang="es-ES" lang="pt-BR" ...>
>>
>> <section lang="de-DE,es-ES,pt-BR" ...>
>>
>
> This seems to be the best way by now.
>
> But perhaps, a Publican RFE: if Publican interprpets the ',' (comma)
> operator in a string, then it would be possible to add a negation
> operator like '!' in C++ inside the string.

The current functionality is built in to DocBook, specialising it for 
Publican would mean books could no longer be built properly with other 
DocBook tool chains.

> The problem I want to solve is the one being discussed in [1].
>
> Then Petr Kovar asked me if the paragraph including
> "translator-credits" string would appear in the source language of the
> manual [2]. And it's reasonable to exclude it when building the book
> for the source language.

Why not have an XML file for each language and put the condition on the 
xi:include?

e.g.

en-US/es-ES_translators.xml would contain a list of Spanish translators, 
you could probably automate generating it.

Then at the end of en-US/Author_Group.xml

    <xi:include lang="es-ES" href="es-ES_translators.xml" 
xmlns:xi="http://www.w3.org/2001/XInclude" />
    <xi:include lang="fr-FR "href="fr-FR_translators.xml" 
xmlns:xi="http://www.w3.org/2001/XInclude" />
  ... etc
</authorgroup>

That list of xi:includes only needs to be updated when a new translation 
is added, so the overhead for writers is small.

FYI Publican 3 will have the ability to have a per language Author_Group 
file [1], it could take a while to get released though.

Cheers, Jeff.

1: https://bugzilla.redhat.com/show_bug.cgi?id=697371

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From jwulf at redhat.com  Tue Nov  8 11:08:20 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Tue, 08 Nov 2011 21:08:20 +1000
Subject: [publican-list] Help with xsl customization
In-Reply-To: <4EB86EBF.2080907@redhat.com>
References: <4EB38EC8.6040308@redhat.com> <4EB86EBF.2080907@redhat.com>
Message-ID: <4EB90DA4.7060206@redhat.com>

On 11/08/2011 09:50 AM, Jeff Fearn wrote:
> On 11/04/2011 05:05 PM, Joshua Wulf wrote:
>> I'm trying to create a custom brand that renders
>> <mediaobject><videoobject>  in html as<iframe>, rather than<embed>.
>>
>> I've found what I think is the xsl that applies this tag, in
>> graphics.xsl [1]:
>>
>> <xsl:template match="videodata">
>>    <xsl:call-template name="process.image">
>>      <xsl:with-param name="tag" select="'iframe'"/>
>>      <xsl:with-param name="alt">
>>        <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
>>      </xsl:with-param>
>>    </xsl:call-template>
>> </xsl:template>
>>
>> [1] http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl
>>
>> I'm not sure where this is imported in publican. It's not in
>> publican/datadir/xsl.
>>
>> I've created a publican brand [2] with a graphics.xsl file in it, with
>> the following contents:
>>
>> <?xml version='1.0'?>
>> <xsl:stylesheet
>>      xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
>>
>>      <xsl:import
>> href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"/>
>>      <xsl:import
>> href="http://docbook.sourceforge.net/release/xsl/1.76.1/xhtml/graphics.xsl"/>
>>
>> <xsl:template match="videodata">
>>    <xsl:call-template name="process.image">
>>      <xsl:with-param name="tag" select="'iframe'"/>
>>      <xsl:with-param name="alt">
>>        <xsl:apply-templates select="(../../textobject/phrase)[1]"/>
>>      </xsl:with-param>
>>    </xsl:call-template>
>> </xsl:template>
>>
>> </xsl:stylesheet>
>>
>> [2] https://svn.devel.redhat.com/repos/ecs/toolkit/publican-redhat-video
>>
>> This doesn't work, though.
>>
>> Anyone know how to do this?
> 
> In your html.xsl file add:
> 
> <xsl:import 
> href="http://docbook.sourceforge.net/release/xsl/current/xhtml/graphics.xsl"/>
> 
> to the list of other imports.
> 
> Copy your videodata template in to html.xsl.
> 
> Delete your graphics.xsl file.
> 
> Rebuild brand.
> 
> Cheers, Jeff.
> 

Rocked it. Thanks Jeff.



From jwulf at redhat.com  Tue Nov  8 11:17:48 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Tue, 08 Nov 2011 21:17:48 +1000
Subject: [publican-list] Adding a publican epub catalog feed to FBReader
Message-ID: <4EB90FDC.1070108@redhat.com>

FBReader is an ebook reader for linux that is packaged in Fedora 15. You
can use it to remotely browse a website that exposes an opds epub
catalog (such as a publican generated docs website).

Here are the steps to add a publican website epub catalog to FBReader,
using docs.redhat.com as the example:

To add docs.redhat.com to FBReader:

1. yum install fbreader

2. create the file: /usr/share/FBReader/network/docs.redhat.com.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE catalog SYSTEM "catalog.dtd">
<catalog type="opds">
<site>docs.redhat.com</site>
<title>Red Hat Docs OPDS Catalog</title>
<summary>Red Hat Documentation</summary>
<link rel="main"
type="application/atom+xml">http://docs.redhat.com/docs/en-US/opds.xml</link>
<feeds>
<condition
show="always">http://docs.redhat.com/docs/en-US/opds.xml<</condition>
</feeds>
<authentication type="basic"/>

</catalog>

3. Run FBReader.



From domingobecker at gmail.com  Tue Nov  8 11:48:17 2011
From: domingobecker at gmail.com (Domingo Becker)
Date: Tue, 8 Nov 2011 08:48:17 -0300
Subject: [publican-list] conditionally exclude a paragraph
In-Reply-To: <4EB8B474.6020603@redhat.com>
References: <CABJ5b7oJhGxf9QQyG5ki7Bipkkg06-Wjck7M2KsMVrACdmjwfA@mail.gmail.com>
	<CABJ5b7rZPBk-6yPxWiYoqZOY-zWA+xyqognGUjziHEgNR7yY5g@mail.gmail.com>
	<4EB86C89.4030502@redhat.com> <4EB86DFC.7090909@redhat.com>
	<CABJ5b7pe5bUqM8yDRn+m-ga_1gBOxfcLq1gOiJ5zrrVA1VshFA@mail.gmail.com>
	<4EB8B474.6020603@redhat.com>
Message-ID: <CABJ5b7rfWKw1RDZEMG+dFXiUSNsOjinDANke3RrBK5vf0D3JKA@mail.gmail.com>

2011/11/8 Jeff Fearn <jfearn at redhat.com>:
> On 11/08/2011 02:01 PM, Domingo Becker wrote:
>>
>> 2011/11/7 Jeff Fearn<jfearn at redhat.com>:
>>>
>>> On 11/08/2011 09:40 AM, Joshua Wulf wrote:
>>>>
>>>> == The brute force method ==
>>>>
>>>>
>>>> <section lang="de-DE" lang="es-ES" lang="pt-BR" ...>
>>>
>>> <section lang="de-DE,es-ES,pt-BR" ...>
>>>
>>
>> This seems to be the best way by now.
>>
>> But perhaps, a Publican RFE: if Publican interprpets the ',' (comma)
>> operator in a string, then it would be possible to add a negation
>> operator like '!' in C++ inside the string.
>
> The current functionality is built in to DocBook, specialising it for
> Publican would mean books could no longer be built properly with other
> DocBook tool chains.
>

Understood.

>> The problem I want to solve is the one being discussed in [1].
>>
>> Then Petr Kovar asked me if the paragraph including
>> "translator-credits" string would appear in the source language of the
>> manual [2]. And it's reasonable to exclude it when building the book
>> for the source language.
>
> Why not have an XML file for each language and put the condition on the
> xi:include?
>

It would mean to give translator write access to the books' git
repositories, and more XML files to maintain. The idea is to not
overload the doc writer.

Thank you.

kind regards

Domingo Becker



From misty at redhat.com  Thu Nov 10 00:30:17 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Wed, 09 Nov 2011 19:30:17 -0500 (EST)
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <ab97f668-2f88-411a-86a3-c75adb7232ff@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>

I'd appreciate it if someone could test this procedure for me. It has worked several times now for me on OS X Lion.

Notes:
1. I have not dealt with installing extra brands at all yet.
2. Steps 1-6 are preparatory work and hopefully some of it will be streamlined in the future.
3. Everything is stored in /opt/local along with the rest of the Macports stuff. This segregates it from your OS install. 
4. It is easy to uninstall Macports, and doing so would also take Publican with it. See the Macports documentation.
5. At the moment, you have to override some path settings for every Publican command you run. The way around this is to create a symbolic link from /opt/local/share/publican to /usr/share/publican. This impacts #3 above, but is a minimal risk. A longer-term solution to this is underway.
6. The commands below are meant to be pasted into the command line as a single line each.


Procedure:

1. Install Xcode from Mac App Store

2. Install Macports from
http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.

3. Open a terminal.

4. Install dependencies for Publican which are available as ports.
sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion ImageMagick +perl +no_x11

5. Install Perl modules available as Macports. They will pull in more dependencies and install them all under /opt/local.
sudo port install p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit 

6. Install CPAN modules for dependencies which can't be satisfied with ports. The first line forces Makefile::Parser to install even though its tests fail.
sudo cpan -f -i Makefile::Parser
sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder

7. Check out Publican 2.x branch:
svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
cd publican-2x/

8. In the publican-2x directory, run: 
perl ./Build.PL

9. In the publican-2x directory, run:
./Build

10. Run the following command to install Publican and put all of its bits into /opt/local:
sudo ./Build install --install_path datadir=/opt/local/share/publican --install_path generated=/opt/local/share/publican/sitetemplate  --install_path web=/opt/local/share/publican/sitetemplate --install_path templates=/opt/local/share/publican/templates --install_path etc=/opt/local/etc --install_path completion=/opt/local/etc/bash_completion.d

11. Create a book. 
publican create --name=testbook --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content

12. Change to the book's main directory: cd testbook

13. Build the book, pointing to the proper places for things Publican expects to find in /usr:
publican build --formats=html --langs=en-US --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content

14. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.



From a3linux at gmail.com  Thu Nov 10 01:56:24 2011
From: a3linux at gmail.com (Allen Chen)
Date: Thu, 10 Nov 2011 09:56:24 +0800
Subject: [publican-list] A quick question with build document without draft
	watermark?
Message-ID: <CAPadsuG30Mk_q-CiZ-_Z3ne7qQMZYWwV7TPJi=g8Fvw+PW4kLw@mail.gmail.com>

Hi All,

I have a simple question, I found my publican ONLY creating PDF/HTML with
draft watermark as default even I didn't add status="draft" in the <book>
or <article> tag.
I wonder if this is ok, if so, how can I build a document without the Draft
watermark?

Thanks.

 Best
      Regards!

Allen Chen

Mail:  a3linux AT gmail . com
MSN: a3linux AT hotmail . com
MP: +86 186 2159 1967
Skype: a3linux
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/publican-list/attachments/20111110/70c21ac8/attachment.htm>

From a3linux at gmail.com  Thu Nov 10 02:01:38 2011
From: a3linux at gmail.com (Allen Chen)
Date: Thu, 10 Nov 2011 10:01:38 +0800
Subject: [publican-list] A quick question with build document without
	draft watermark?
In-Reply-To: <CAPadsuG30Mk_q-CiZ-_Z3ne7qQMZYWwV7TPJi=g8Fvw+PW4kLw@mail.gmail.com>
References: <CAPadsuG30Mk_q-CiZ-_Z3ne7qQMZYWwV7TPJi=g8Fvw+PW4kLw@mail.gmail.com>
Message-ID: <CAPadsuHhW1xNAJoocxc2++BzHHTUZprn=91QsBj6fmmYemTRcg@mail.gmail.com>

Hi All,

I found this in bugzilla,
https://bugzilla.redhat.com/show_bug.cgi?id=740123

It is said it fixed in 2.8. I just used the latest F16 with Publican 2.7.
ok. I can confirm this is ONLY for PDF format output.

That's ok.
When the 2.8 version available to update?

Thanks.

 Best
      Regards!

Allen Chen

Mail:  a3linux AT gmail . com
MSN: a3linux AT hotmail . com
MP: +86 186 2159 1967
Skype: a3linux



On Thu, Nov 10, 2011 at 9:56 AM, Allen Chen <a3linux at gmail.com> wrote:

> Hi All,
>
> I have a simple question, I found my publican ONLY creating PDF/HTML with
> draft watermark as default even I didn't add status="draft" in the <book>
> or <article> tag.
> I wonder if this is ok, if so, how can I build a document without the
> Draft watermark?
>
> Thanks.
>
>  Best
>       Regards!
>
> Allen Chen
>
> Mail:  a3linux AT gmail . com
> MSN: a3linux AT hotmail . com
> MP: +86 186 2159 1967
> Skype: a3linux
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/publican-list/attachments/20111110/7f53f164/attachment.htm>

From jfearn at redhat.com  Thu Nov 10 02:45:50 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Thu, 10 Nov 2011 12:45:50 +1000
Subject: [publican-list] A quick question with build document without
 draft watermark?
In-Reply-To: <CAPadsuHhW1xNAJoocxc2++BzHHTUZprn=91QsBj6fmmYemTRcg@mail.gmail.com>
References: <CAPadsuG30Mk_q-CiZ-_Z3ne7qQMZYWwV7TPJi=g8Fvw+PW4kLw@mail.gmail.com>
	<CAPadsuHhW1xNAJoocxc2++BzHHTUZprn=91QsBj6fmmYemTRcg@mail.gmail.com>
Message-ID: <4EBB3ADE.6000802@redhat.com>

On 11/10/2011 12:01 PM, Allen Chen wrote:
> Hi All,
>
> I found this in bugzilla,
> https://bugzilla.redhat.com/show_bug.cgi?id=740123
>
> It is said it fixed in 2.8. I just used the latest F16 with Publican 2.7.
> ok. I can confirm this is ONLY for PDF format output.
>
> That's ok.
> When the 2.8 version available to update?
>

Appears to be stuck in the testing repo.

https://admin.fedoraproject.org/updates/FEDORA-2011-13162?_csrf_token=b32e3eaa441d1faeb06231556896285a79a6bad6

You should be able to install it by running:

$ sudo yum upgrade --enablerepo=updates-testing publican\*

Cheers, Jeff.

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From jwulf at redhat.com  Thu Nov 10 04:08:23 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Thu, 10 Nov 2011 14:08:23 +1000
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
References: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <4EBB4E37.6090102@redhat.com>

Kickass! I'll try it tonight.

On 11/10/2011 10:30 AM, Misty Stanley-Jones wrote:
> I'd appreciate it if someone could test this procedure for me. It has worked several times now for me on OS X Lion.
> 
> Notes:
> 1. I have not dealt with installing extra brands at all yet.
> 2. Steps 1-6 are preparatory work and hopefully some of it will be streamlined in the future.
> 3. Everything is stored in /opt/local along with the rest of the Macports stuff. This segregates it from your OS install. 
> 4. It is easy to uninstall Macports, and doing so would also take Publican with it. See the Macports documentation.
> 5. At the moment, you have to override some path settings for every Publican command you run. The way around this is to create a symbolic link from /opt/local/share/publican to /usr/share/publican. This impacts #3 above, but is a minimal risk. A longer-term solution to this is underway.
> 6. The commands below are meant to be pasted into the command line as a single line each.
> 
> 
> Procedure:
> 
> 1. Install Xcode from Mac App Store
> 
> 2. Install Macports from
> http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.
> 
> 3. Open a terminal.
> 
> 4. Install dependencies for Publican which are available as ports.
> sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion ImageMagick +perl +no_x11
> 
> 5. Install Perl modules available as Macports. They will pull in more dependencies and install them all under /opt/local.
> sudo port install p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit 
> 
> 6. Install CPAN modules for dependencies which can't be satisfied with ports. The first line forces Makefile::Parser to install even though its tests fail.
> sudo cpan -f -i Makefile::Parser
> sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder
> 
> 7. Check out Publican 2.x branch:
> svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
> cd publican-2x/
> 
> 8. In the publican-2x directory, run: 
> perl ./Build.PL
> 
> 9. In the publican-2x directory, run:
> ./Build
> 
> 10. Run the following command to install Publican and put all of its bits into /opt/local:
> sudo ./Build install --install_path datadir=/opt/local/share/publican --install_path generated=/opt/local/share/publican/sitetemplate  --install_path web=/opt/local/share/publican/sitetemplate --install_path templates=/opt/local/share/publican/templates --install_path etc=/opt/local/etc --install_path completion=/opt/local/etc/bash_completion.d
> 
> 11. Create a book. 
> publican create --name=testbook --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
> 
> 12. Change to the book's main directory: cd testbook
> 
> 13. Build the book, pointing to the proper places for things Publican expects to find in /usr:
> publican build --formats=html --langs=en-US --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
> 
> 14. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican


-- 
Give us your feedback on JBoss Enterprise Documentation, take the key
survey:
http://www.keysurvey.com/survey/361436/1065/



From dmison at redhat.com  Thu Nov 10 04:12:03 2011
From: dmison at redhat.com (Darrin Mison)
Date: Wed, 09 Nov 2011 23:12:03 -0500 (EST)
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
References: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <9B10C6CE-2DD2-4193-AD15-D06784DF839A@redhat.com>

What's required from XCode ?

It's a 4 gig download and then even more than that to install it.



On 10/11/2011, at 10:30 AM, Misty Stanley-Jones <misty at redhat.com> wrote:

> I'd appreciate it if someone could test this procedure for me. It has worked several times now for me on OS X Lion.
> 
> Notes:
> 1. I have not dealt with installing extra brands at all yet.
> 2. Steps 1-6 are preparatory work and hopefully some of it will be streamlined in the future.
> 3. Everything is stored in /opt/local along with the rest of the Macports stuff. This segregates it from your OS install. 
> 4. It is easy to uninstall Macports, and doing so would also take Publican with it. See the Macports documentation.
> 5. At the moment, you have to override some path settings for every Publican command you run. The way around this is to create a symbolic link from /opt/local/share/publican to /usr/share/publican. This impacts #3 above, but is a minimal risk. A longer-term solution to this is underway.
> 6. The commands below are meant to be pasted into the command line as a single line each.
> 
> 
> Procedure:
> 
> 1. Install Xcode from Mac App Store
> 
> 2. Install Macports from
> http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.
> 
> 3. Open a terminal.
> 
> 4. Install dependencies for Publican which are available as ports.
> sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion ImageMagick +perl +no_x11
> 
> 5. Install Perl modules available as Macports. They will pull in more dependencies and install them all under /opt/local.
> sudo port install p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit 
> 
> 6. Install CPAN modules for dependencies which can't be satisfied with ports. The first line forces Makefile::Parser to install even though its tests fail.
> sudo cpan -f -i Makefile::Parser
> sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder
> 
> 7. Check out Publican 2.x branch:
> svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
> cd publican-2x/
> 
> 8. In the publican-2x directory, run: 
> perl ./Build.PL
> 
> 9. In the publican-2x directory, run:
> ./Build
> 
> 10. Run the following command to install Publican and put all of its bits into /opt/local:
> sudo ./Build install --install_path datadir=/opt/local/share/publican --install_path generated=/opt/local/share/publican/sitetemplate  --install_path web=/opt/local/share/publican/sitetemplate --install_path templates=/opt/local/share/publican/templates --install_path etc=/opt/local/etc --install_path completion=/opt/local/etc/bash_completion.d
> 
> 11. Create a book. 
> publican create --name=testbook --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
> 
> 12. Change to the book's main directory: cd testbook
> 
> 13. Build the book, pointing to the proper places for things Publican expects to find in /usr:
> publican build --formats=html --langs=en-US --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
> 
> 14. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.
> 



From dmison at redhat.com  Thu Nov 10 04:14:09 2011
From: dmison at redhat.com (Darrin Mison)
Date: Wed, 09 Nov 2011 23:14:09 -0500 (EST)
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <9B10C6CE-2DD2-4193-AD15-D06784DF839A@redhat.com>
References: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
	<9B10C6CE-2DD2-4193-AD15-D06784DF839A@redhat.com>
Message-ID: <E1EE7A52-320C-4782-9D1E-4A22FB5B8C6D@redhat.com>

Ah, it's a MacPorts requirement. 



On 10/11/2011, at 2:12 PM, Darrin Mison <dmison at redhat.com> wrote:

> What's required from XCode ?
> 
> It's a 4 gig download and then even more than that to install it.
> 
> 
> 
> On 10/11/2011, at 10:30 AM, Misty Stanley-Jones <misty at redhat.com> wrote:
> 
>> I'd appreciate it if someone could test this procedure for me. It has worked several times now for me on OS X Lion.
>> 
>> Notes:
>> 1. I have not dealt with installing extra brands at all yet.
>> 2. Steps 1-6 are preparatory work and hopefully some of it will be streamlined in the future.
>> 3. Everything is stored in /opt/local along with the rest of the Macports stuff. This segregates it from your OS install. 
>> 4. It is easy to uninstall Macports, and doing so would also take Publican with it. See the Macports documentation.
>> 5. At the moment, you have to override some path settings for every Publican command you run. The way around this is to create a symbolic link from /opt/local/share/publican to /usr/share/publican. This impacts #3 above, but is a minimal risk. A longer-term solution to this is underway.
>> 6. The commands below are meant to be pasted into the command line as a single line each.
>> 
>> 
>> Procedure:
>> 
>> 1. Install Xcode from Mac App Store
>> 
>> 2. Install Macports from
>> http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.
>> 
>> 3. Open a terminal.
>> 
>> 4. Install dependencies for Publican which are available as ports.
>> sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion ImageMagick +perl +no_x11
>> 
>> 5. Install Perl modules available as Macports. They will pull in more dependencies and install them all under /opt/local.
>> sudo port install p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit 
>> 
>> 6. Install CPAN modules for dependencies which can't be satisfied with ports. The first line forces Makefile::Parser to install even though its tests fail.
>> sudo cpan -f -i Makefile::Parser
>> sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder
>> 
>> 7. Check out Publican 2.x branch:
>> svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
>> cd publican-2x/
>> 
>> 8. In the publican-2x directory, run: 
>> perl ./Build.PL
>> 
>> 9. In the publican-2x directory, run:
>> ./Build
>> 
>> 10. Run the following command to install Publican and put all of its bits into /opt/local:
>> sudo ./Build install --install_path datadir=/opt/local/share/publican --install_path generated=/opt/local/share/publican/sitetemplate  --install_path web=/opt/local/share/publican/sitetemplate --install_path templates=/opt/local/share/publican/templates --install_path etc=/opt/local/etc --install_path completion=/opt/local/etc/bash_completion.d
>> 
>> 11. Create a book. 
>> publican create --name=testbook --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
>> 
>> 12. Change to the book's main directory: cd testbook
>> 
>> 13. Build the book, pointing to the proper places for things Publican expects to find in /usr:
>> publican build --formats=html --langs=en-US --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
>> 
>> 14. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.
>> 
> 
> _______________________________________________
> 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 Nov 10 04:36:08 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Wed, 09 Nov 2011 23:36:08 -0500 (EST)
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <9B10C6CE-2DD2-4193-AD15-D06784DF839A@redhat.com>
Message-ID: <262cf7fa-0a5c-4ec5-9f2f-83af3a999acc@zmail13.collab.prod.int.phx2.redhat.com>

I think it gets you Perl and GNU Make. It is possible you could just rely on Macports entirely. It is a bit more difficult for me to remove Xcode than to remove Macports, so I have not tested without it. This procedure relies on the Perl provided by Macports.

----- Original Message -----
> From: "Darrin Mison" <dmison at redhat.com>
> To: "Misty Stanley-Jones" <misty at redhat.com>
> Cc: "Publican discussions" <publican-list at redhat.com>, "Engineering Content Services Writing projects."
> <content-services-list at redhat.com>
> Sent: Thursday, November 10, 2011 2:12:03 PM
> Subject: Re: Install Publican on OS X Lion - Working
> 
> What's required from XCode ?
> 
> It's a 4 gig download and then even more than that to install it.
> 
> 
> 
> On 10/11/2011, at 10:30 AM, Misty Stanley-Jones <misty at redhat.com>
> wrote:
> 
> > I'd appreciate it if someone could test this procedure for me. It
> > has worked several times now for me on OS X Lion.
> > 
> > Notes:
> > 1. I have not dealt with installing extra brands at all yet.
> > 2. Steps 1-6 are preparatory work and hopefully some of it will be
> > streamlined in the future.
> > 3. Everything is stored in /opt/local along with the rest of the
> > Macports stuff. This segregates it from your OS install.
> > 4. It is easy to uninstall Macports, and doing so would also take
> > Publican with it. See the Macports documentation.
> > 5. At the moment, you have to override some path settings for every
> > Publican command you run. The way around this is to create a
> > symbolic link from /opt/local/share/publican to
> > /usr/share/publican. This impacts #3 above, but is a minimal risk.
> > A longer-term solution to this is underway.
> > 6. The commands below are meant to be pasted into the command line
> > as a single line each.
> > 
> > 
> > Procedure:
> > 
> > 1. Install Xcode from Mac App Store
> > 
> > 2. Install Macports from
> > http://guide.macports.org/chunked/installing.macports.html.
> > Everything you install with it goes into /opt/local, away from
> > your normal OS files.
> > 
> > 3. Open a terminal.
> > 
> > 4. Install dependencies for Publican which are available as ports.
> > sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5
> > bash-completion ImageMagick +perl +no_x11
> > 
> > 5. Install Perl modules available as Macports. They will pull in
> > more dependencies and install them all under /opt/local.
> > sudo port install p5-file-pushd p5-config-simple p5-file-find-rule
> > p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils
> > p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt
> > p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime
> > p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite
> > p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage
> > p5-template-toolkit
> > 
> > 6. Install CPAN modules for dependencies which can't be satisfied
> > with ports. The first line forces Makefile::Parser to install even
> > though its tests fail.
> > sudo cpan -f -i Makefile::Parser
> > sudo cpan Locale::Maketext::Gettext Locale::PO
> > DateTime::Format::DateParse Syntax::Highlight::Engine::Kate
> > XML::TreeBuilder
> > 
> > 7. Check out Publican 2.x branch:
> > svn co
> > http://svn.fedorahosted.org/svn/publican/branches/publican-2x
> > cd publican-2x/
> > 
> > 8. In the publican-2x directory, run:
> > perl ./Build.PL
> > 
> > 9. In the publican-2x directory, run:
> > ./Build
> > 
> > 10. Run the following command to install Publican and put all of
> > its bits into /opt/local:
> > sudo ./Build install --install_path
> > datadir=/opt/local/share/publican --install_path
> > generated=/opt/local/share/publican/sitetemplate  --install_path
> > web=/opt/local/share/publican/sitetemplate --install_path
> > templates=/opt/local/share/publican/templates --install_path
> > etc=/opt/local/etc --install_path
> > completion=/opt/local/etc/bash_completion.d
> > 
> > 11. Create a book.
> > publican create --name=testbook
> > --common_config=/opt/local/share/publican
> > --common_content=/opt/local/share/publican/Common_Content
> > 
> > 12. Change to the book's main directory: cd testbook
> > 
> > 13. Build the book, pointing to the proper places for things
> > Publican expects to find in /usr:
> > publican build --formats=html --langs=en-US
> > --common_config=/opt/local/share/publican
> > --common_content=/opt/local/share/publican/Common_Content
> > 
> > 14. Open the tmp/en-US/html/index.html in a browser to prove that
> > it built properly.
> > 
> 

-- 
Misty Stanley-Jones, RHCE 
Content Author, ECS Brisbane 
?: misty (Freenode IRC) ?: misty at redhat.com ?: + 61 7 3514 8105 ?: 88105 



From misty at redhat.com  Thu Nov 10 04:36:25 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Wed, 09 Nov 2011 23:36:25 -0500 (EST)
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <E1EE7A52-320C-4782-9D1E-4A22FB5B8C6D@redhat.com>
Message-ID: <4b28d0ed-4563-4bf5-b1a9-f89cfca5668b@zmail13.collab.prod.int.phx2.redhat.com>

Yep, there ya go then.

----- Original Message -----
> From: "Darrin Mison" <dmison at redhat.com>
> To: "Publican discussions" <publican-list at redhat.com>
> Cc: "Misty Stanley-Jones" <misty at redhat.com>, "Engineering Content Services Writing projects."
> <content-services-list at redhat.com>, "Publican discussions" <publican-list at redhat.com>
> Sent: Thursday, November 10, 2011 2:14:09 PM
> Subject: Re: [publican-list] Install Publican on OS X Lion - Working
> 
> Ah, it's a MacPorts requirement.
> 
> 
> 
> On 10/11/2011, at 2:12 PM, Darrin Mison <dmison at redhat.com> wrote:
> 
> > What's required from XCode ?
> > 
> > It's a 4 gig download and then even more than that to install it.
> > 
> > 
> > 
> > On 10/11/2011, at 10:30 AM, Misty Stanley-Jones <misty at redhat.com>
> > wrote:
> > 
> >> I'd appreciate it if someone could test this procedure for me. It
> >> has worked several times now for me on OS X Lion.
> >> 
> >> Notes:
> >> 1. I have not dealt with installing extra brands at all yet.
> >> 2. Steps 1-6 are preparatory work and hopefully some of it will be
> >> streamlined in the future.
> >> 3. Everything is stored in /opt/local along with the rest of the
> >> Macports stuff. This segregates it from your OS install.
> >> 4. It is easy to uninstall Macports, and doing so would also take
> >> Publican with it. See the Macports documentation.
> >> 5. At the moment, you have to override some path settings for
> >> every Publican command you run. The way around this is to create
> >> a symbolic link from /opt/local/share/publican to
> >> /usr/share/publican. This impacts #3 above, but is a minimal
> >> risk. A longer-term solution to this is underway.
> >> 6. The commands below are meant to be pasted into the command line
> >> as a single line each.
> >> 
> >> 
> >> Procedure:
> >> 
> >> 1. Install Xcode from Mac App Store
> >> 
> >> 2. Install Macports from
> >> http://guide.macports.org/chunked/installing.macports.html.
> >> Everything you install with it goes into /opt/local, away from
> >> your normal OS files.
> >> 
> >> 3. Open a terminal.
> >> 
> >> 4. Install dependencies for Publican which are available as ports.
> >> sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5
> >> bash-completion ImageMagick +perl +no_x11
> >> 
> >> 5. Install Perl modules available as Macports. They will pull in
> >> more dependencies and install them all under /opt/local.
> >> sudo port install p5-file-pushd p5-config-simple p5-file-find-rule
> >> p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils
> >> p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt
> >> p5-locale-gettext p5-image-size p5-file-copy-recursive
> >> p5-datetime p5-archive-zip p5-timedate p5-html-format
> >> p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod
> >> p5-test-pod-coverage p5-template-toolkit
> >> 
> >> 6. Install CPAN modules for dependencies which can't be satisfied
> >> with ports. The first line forces Makefile::Parser to install
> >> even though its tests fail.
> >> sudo cpan -f -i Makefile::Parser
> >> sudo cpan Locale::Maketext::Gettext Locale::PO
> >> DateTime::Format::DateParse Syntax::Highlight::Engine::Kate
> >> XML::TreeBuilder
> >> 
> >> 7. Check out Publican 2.x branch:
> >> svn co
> >> http://svn.fedorahosted.org/svn/publican/branches/publican-2x
> >> cd publican-2x/
> >> 
> >> 8. In the publican-2x directory, run:
> >> perl ./Build.PL
> >> 
> >> 9. In the publican-2x directory, run:
> >> ./Build
> >> 
> >> 10. Run the following command to install Publican and put all of
> >> its bits into /opt/local:
> >> sudo ./Build install --install_path
> >> datadir=/opt/local/share/publican --install_path
> >> generated=/opt/local/share/publican/sitetemplate  --install_path
> >> web=/opt/local/share/publican/sitetemplate --install_path
> >> templates=/opt/local/share/publican/templates --install_path
> >> etc=/opt/local/etc --install_path
> >> completion=/opt/local/etc/bash_completion.d
> >> 
> >> 11. Create a book.
> >> publican create --name=testbook
> >> --common_config=/opt/local/share/publican
> >> --common_content=/opt/local/share/publican/Common_Content
> >> 
> >> 12. Change to the book's main directory: cd testbook
> >> 
> >> 13. Build the book, pointing to the proper places for things
> >> Publican expects to find in /usr:
> >> publican build --formats=html --langs=en-US
> >> --common_config=/opt/local/share/publican
> >> --common_content=/opt/local/share/publican/Common_Content
> >> 
> >> 14. Open the tmp/en-US/html/index.html in a browser to prove that
> >> it built properly.
> >> 
> > 
> > _______________________________________________
> > 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 
?: misty (Freenode IRC) ?: misty at redhat.com ?: + 61 7 3514 8105 ?: 88105 



From jfearn at redhat.com  Thu Nov 10 05:37:27 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Thu, 10 Nov 2011 15:37:27 +1000
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
References: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <4EBB6317.9080407@redhat.com>

On 11/10/2011 10:30 AM, Misty Stanley-Jones wrote:
> I'd appreciate it if someone could test this procedure for me. It has worked several times now for me on OS X Lion.
>
> Notes:
> 1. I have not dealt with installing extra brands at all yet.
> 2. Steps 1-6 are preparatory work and hopefully some of it will be streamlined in the future.
> 3. Everything is stored in /opt/local along with the rest of the Macports stuff. This segregates it from your OS install.
> 4. It is easy to uninstall Macports, and doing so would also take Publican with it. See the Macports documentation.
> 5. At the moment, you have to override some path settings for every Publican command you run. The way around this is to create a symbolic link from /opt/local/share/publican to /usr/share/publican. This impacts #3 above, but is a minimal risk. A longer-term solution to this is underway.
> 6. The commands below are meant to be pasted into the command line as a single line each.
>
>
> Procedure:
>
> 1. Install Xcode from Mac App Store
>
> 2. Install Macports from
> http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.
>
> 3. Open a terminal.
>
> 4. Install dependencies for Publican which are available as ports.
> sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion ImageMagick +perl +no_x11
>
> 5. Install Perl modules available as Macports. They will pull in more dependencies and install them all under /opt/local.
> sudo port install p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit
>
> 6. Install CPAN modules for dependencies which can't be satisfied with ports. The first line forces Makefile::Parser to install even though its tests fail.
> sudo cpan -f -i Makefile::Parser
> sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder
>
> 7. Check out Publican 2.x branch:
> svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
> cd publican-2x/
>
> 8. In the publican-2x directory, run:
> perl ./Build.PL
>
> 9. In the publican-2x directory, run:
> ./Build
>
> 10. Run the following command to install Publican and put all of its bits into /opt/local:
> sudo ./Build install --install_path datadir=/opt/local/share/publican --install_path generated=/opt/local/share/publican/sitetemplate  --install_path web=/opt/local/share/publican/sitetemplate --install_path templates=/opt/local/share/publican/templates --install_path etc=/opt/local/etc --install_path completion=/opt/local/etc/bash_completion.d
>
> 11. Create a book.
> publican create --name=testbook --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
>
> 12. Change to the book's main directory: cd testbook
>
> 13. Build the book, pointing to the proper places for things Publican expects to find in /usr:
> publican build --formats=html --langs=en-US --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content
>
> 14. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.

FYI 3 bugs were raised about making this easier:

https://bugzilla.redhat.com/show_bug.cgi?id=752637
https://bugzilla.redhat.com/show_bug.cgi?id=752620
https://bugzilla.redhat.com/show_bug.cgi?id=752640

All have been addressed and are waiting for QA.

If you are testing this and want to avoid FOP, and who wouldn't, you can 
test wkhtmltopdf. There is a OSX binary on the website [1] make sure you 
get at least 0.10.0_rc2!

Cheers, Jeff.

1: http://code.google.com/p/wkhtmltopdf/downloads/list

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From sburgess at redhat.com  Thu Nov 10 05:53:43 2011
From: sburgess at redhat.com (Susan Burgess)
Date: Thu, 10 Nov 2011 00:53:43 -0500 (EST)
Subject: [publican-list] Install Publican on OS X Lion - Working
In-Reply-To: <451ac3e3-0186-475b-b5b1-e86073d8d68f@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <060ddedd-53e1-418a-99ba-296a5b604658@zmail16.collab.prod.int.phx2.redhat.com>

Ok I'll try it when I get home..
though I have a fedora vm which I run publican on on my home iMac..er I mean my kids iMac..

Susan

----- Original Message -----
From: "Misty Stanley-Jones" <misty at redhat.com>
To: "Publican discussions" <publican-list at redhat.com>
Cc: "Engineering Content Services Writing projects." <content-services-list at redhat.com>
Sent: Thursday, November 10, 2011 10:30:17 AM
Subject: [publican-list] Install Publican on OS X Lion - Working

I'd appreciate it if someone could test this procedure for me. It has worked several times now for me on OS X Lion.

Notes:
1. I have not dealt with installing extra brands at all yet.
2. Steps 1-6 are preparatory work and hopefully some of it will be streamlined in the future.
3. Everything is stored in /opt/local along with the rest of the Macports stuff. This segregates it from your OS install. 
4. It is easy to uninstall Macports, and doing so would also take Publican with it. See the Macports documentation.
5. At the moment, you have to override some path settings for every Publican command you run. The way around this is to create a symbolic link from /opt/local/share/publican to /usr/share/publican. This impacts #3 above, but is a minimal risk. A longer-term solution to this is underway.
6. The commands below are meant to be pasted into the command line as a single line each.


Procedure:

1. Install Xcode from Mac App Store

2. Install Macports from
http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.

3. Open a terminal.

4. Install dependencies for Publican which are available as ports.
sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion ImageMagick +perl +no_x11

5. Install Perl modules available as Macports. They will pull in more dependencies and install them all under /opt/local.
sudo port install p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit 

6. Install CPAN modules for dependencies which can't be satisfied with ports. The first line forces Makefile::Parser to install even though its tests fail.
sudo cpan -f -i Makefile::Parser
sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder

7. Check out Publican 2.x branch:
svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
cd publican-2x/

8. In the publican-2x directory, run: 
perl ./Build.PL

9. In the publican-2x directory, run:
./Build

10. Run the following command to install Publican and put all of its bits into /opt/local:
sudo ./Build install --install_path datadir=/opt/local/share/publican --install_path generated=/opt/local/share/publican/sitetemplate  --install_path web=/opt/local/share/publican/sitetemplate --install_path templates=/opt/local/share/publican/templates --install_path etc=/opt/local/etc --install_path completion=/opt/local/etc/bash_completion.d

11. Create a book. 
publican create --name=testbook --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content

12. Change to the book's main directory: cd testbook

13. Build the book, pointing to the proper places for things Publican expects to find in /usr:
publican build --formats=html --langs=en-US --common_config=/opt/local/share/publican --common_content=/opt/local/share/publican/Common_Content

14. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.

_______________________________________________
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 Nov 10 07:14:16 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Thu, 10 Nov 2011 02:14:16 -0500 (EST)
Subject: [publican-list] Install Publican on OSX Lion (now with fewer steps)
In-Reply-To: <6e83595b-fbe1-4b50-8739-3e4e0495c63b@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <a4da0a5c-87ae-4359-bcfa-3668ec48de22@zmail13.collab.prod.int.phx2.redhat.com>

Changes:
* Fewer steps
* All paths are taken care of automatically
* Not having to install ImageMagick or Makefile::Parser

If you tried the first revision of these instructions and you want to clean things up and start fresh, follow these instructions to uninstall Macports, and then begin at step 2 below (Macports should still be in your Downloads):

sudo port -fp uninstall --follow-dependents installed
sudo rm -rf /opt/local
sudo rm -rf /Library/Tcl/macports1.0


Install Publican on OSX
---------------------------------------------------------
1. Install Xcode from Mac App Store

2. Install Macports from
http://guide.macports.org/chunked/installing.macports.html. Everything you install with it goes into /opt/local, away from your normal OS files.

3. Open a terminal.

4. Install dependencies for Publican which are available as ports.
sudo port install docbook-xml docbook-xsl docbook-sgml-4.2 perl5 bash-completion p5-file-pushd p5-config-simple p5-file-find-rule p5-file-slurp p5-class-trigger p5-time-hires p5-list-moreutils p5-ipc-run3 p5-class-accessor p5-test-perl-critic p5-xml-libxslt p5-locale-gettext p5-image-size p5-file-copy-recursive p5-datetime p5-archive-zip p5-timedate p5-html-format p5-dbd-sqlite p5-xml-simple p5-devel-cover p5-test-pod p5-test-pod-coverage p5-template-toolkit 

5. Install CPAN modules for dependencies which can't be satisfied with ports.
sudo cpan Locale::Maketext::Gettext Locale::PO DateTime::Format::DateParse Syntax::Highlight::Engine::Kate XML::TreeBuilder

6. Install FOP if you want PDFs to work: 
	a. sudo port install fop
	b. echo "FOP_OPTS='-Xms50m -Xmx700m'" > ~/.foprc  (to fix a quirk with Fop)

7. Check out Publican 2.x branch:
	a. svn co http://svn.fedorahosted.org/svn/publican/branches/publican-2x
	b. cd publican-2x/

8. In the publican-2x directory, run "perl ./Build.PL". If all goes well, run "./Build".

9. Run the following command to install Publican and put all of its bits into /opt/local
	sudo ./Build install 

10. Create and build a book: 
	a. publican create --name=testbook
	b. cd testbook
	c. publican build --formats=html --langs=en-US
	d. Open the tmp/en-US/html/index.html in a browser to prove that it built properly.
	



From misty at redhat.com  Fri Nov 11 06:06:43 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Fri, 11 Nov 2011 01:06:43 -0500 (EST)
Subject: [publican-list] Install Publican brands on OSX
In-Reply-To: <de11ec4c-7c4d-4386-aa21-77f965eae7a6@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <482c2999-0ef2-403a-bcea-27dd15872712@zmail13.collab.prod.int.phx2.redhat.com>

To install Publican brands on OS X, do the following:

1. Only once, fix the permissions on the common brand:
find /opt/local/share/publican -type f |xargs sudo chmod 644
(we will eventually figure out how to fix this properly)

2. Check out the brand from svn or obtain a pre-built brand from a friend. The SVN location for all of the standard brands is: http://svn.fedorahosted.org/svn/publican

3. Check to the brand directory of your choice: 
cd publican/publican-jboss 
(or where you put your pre-built brand)

4. Build the brand (skip this if you have a pre-built brand)
publican build --formats=xml --langs=all --publish

5. Install the brand:
udo publican install_brand --path=/opt/local/share/publican/Common_Content


Now you can build books with your brand, for fun and profit.



From misty at redhat.com  Fri Nov 11 06:39:56 2011
From: misty at redhat.com (Misty Stanley-Jones)
Date: Fri, 11 Nov 2011 01:39:56 -0500 (EST)
Subject: [publican-list] OS X information added to the Publican Wiki
In-Reply-To: <2f32463f-1f27-43ea-a55e-1d6731c19f23@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <e13ef29e-e8eb-4dd8-b681-ff925c5ab75e@zmail13.collab.prod.int.phx2.redhat.com>

See https://fedorahosted.org/publican/wiki/Installing_OSX for a centralized location for Publican on OS X.

-- 
Misty Stanley-Jones, RHCE 
Content Author, ECS Brisbane 
?: misty (Freenode IRC) ?: misty at redhat.com ?: + 61 7 3514 8105 ?: 88105 



From sgordon at redhat.com  Fri Nov 11 15:02:33 2011
From: sgordon at redhat.com (Steve Gordon)
Date: Fri, 11 Nov 2011 10:02:33 -0500 (EST)
Subject: [publican-list] OS X information added to the Publican Wiki
In-Reply-To: <e13ef29e-e8eb-4dd8-b681-ff925c5ab75e@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <1fe1212c-70c6-4741-b265-36fb436eaaa9@zmail15.collab.prod.int.phx2.redhat.com>

This is great Misty, it would awesome if this ended up in the PUG :).

-Steve

----- Original Message -----
> From: "Misty Stanley-Jones" <misty at redhat.com>
> To: "Publican discussions" <publican-list at redhat.com>
> Sent: Friday, November 11, 2011 1:39:56 AM
> Subject: [publican-list] OS X information added to the Publican Wiki
> 
> See https://fedorahosted.org/publican/wiki/Installing_OSX for a
> centralized location for Publican on OS X.
> 
> --
> Misty Stanley-Jones, RHCE
> Content Author, ECS Brisbane
> ?: misty (Freenode IRC) ?: misty at redhat.com ?: + 61 7 3514 8105 ?:
> 88105
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican



From bugzilla at redhat.com  Mon Nov 14 03:08:16 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Sun, 13 Nov 2011 22:08:16 -0500
Subject: [publican-list] [Bug 642127] %changelog doesn't follow packaging
 Version Release format with publican 'package' action
In-Reply-To: <bug-642127-264938@bugzilla.redhat.com>
References: <bug-642127-264938@bugzilla.redhat.com>
Message-ID: <201111140308.pAE38Gx2028616@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=642127

--- Comment #15 from sandeep shedmake <sshedmak at redhat.com> 2011-11-13 22:08:12 EST ---
Is the fix available in publican-2.8-1 release ?

-- 
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  Mon Nov 14 03:12:01 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Sun, 13 Nov 2011 22:12:01 -0500
Subject: [publican-list] [Bug 642127] %changelog doesn't follow packaging
 Version Release format with publican 'package' action
In-Reply-To: <bug-642127-264938@bugzilla.redhat.com>
References: <bug-642127-264938@bugzilla.redhat.com>
Message-ID: <201111140312.pAE3C1Jw008432@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=642127

--- Comment #16 from sandeep shedmake <sshedmak at redhat.com> 2011-11-13 22:12:01 EST ---
(In reply to comment #15)
> Is the fix available in publican-2.8-1 release ?

Please, disregard Comment 15;  Target Milestone is 3.0.

-- 
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 anjana at gluster.com  Mon Nov 14 08:52:39 2011
From: anjana at gluster.com (Anjana Suparna)
Date: Mon, 14 Nov 2011 08:52:39 +0000
Subject: [publican-list] Newbie Questions
Message-ID: <E6E376533AECB643A02A4E62DC263C60A4B401@mbx024-e1-nj-8.exch024.domain.local>

Hi,

Newbie questions:

1) how would I go about updating my Publican 2.3 installation to version 2.8 on my Ubuntu 11.4 client?

2) *WARNING: Questionable tag found: glossdef - What's the alternative to this tag.

3)[warning] /usr/bin/fop: Unable to locate servlet-api in /usr/share/java - How do we resolve this issue?

4) SEVERE: Couldn't find hyphenation pattern en - How do we resolve this issue?

Regards,
Divya and Anjana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/publican-list/attachments/20111114/4f85f0f5/attachment.htm>

From djorm at redhat.com  Tue Nov 15 00:30:42 2011
From: djorm at redhat.com (David Jorm)
Date: Mon, 14 Nov 2011 19:30:42 -0500 (EST)
Subject: [publican-list] Newbie Questions
In-Reply-To: <E6E376533AECB643A02A4E62DC263C60A4B401@mbx024-e1-nj-8.exch024.domain.local>
Message-ID: <efb7cd04-417b-41e0-9132-751d1f6f07a5@zmail15.collab.prod.int.phx2.redhat.com>

Hi Anjana

> 1) how would I go about updating my Publican 2.3 installation to
> version 2.8 on my Ubuntu 11.4 client?
> 

It appears that the most recent Ubuntu 11 Publican package is version 2.5:

http://packages.ubuntu.com/oneiric/publican

You could adapt these instructions to build from the Publican 2.8 source:

https://fedorahosted.org/publican/wiki/Installing

Or you could use Fedora. I think the majority of Publican users are running Fedora, and it is by far the best-supported distribution for running Publican.

Thanks
David



From hertzog at debian.org  Tue Nov 15 07:23:40 2011
From: hertzog at debian.org (Raphael Hertzog)
Date: Tue, 15 Nov 2011 08:23:40 +0100
Subject: [publican-list] Newbie Questions
In-Reply-To: <efb7cd04-417b-41e0-9132-751d1f6f07a5@zmail15.collab.prod.int.phx2.redhat.com>
References: <E6E376533AECB643A02A4E62DC263C60A4B401@mbx024-e1-nj-8.exch024.domain.local>
	<efb7cd04-417b-41e0-9132-751d1f6f07a5@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <20111115072340.GE14362@rivendell.home.ouaza.com>

Hi,

On Mon, 14 Nov 2011, David Jorm wrote:
> Or you could use Fedora. I think the majority of Publican users are
> running Fedora, and it is by far the best-supported distribution for
> running Publican.

Please... publican runs very well on Debian/Ubuntu too. The reason why 2.8
is not yet in Debian/Ubuntu is because docbook-xsl is lagging behind
and the required version is not yet there. I have to prod the
maintainer...

If you want to build the latest version of the Debian package, you can do
so with git-buildpackage using this git repository:
git://git.debian.org/collab-maint/publican.git
http://git.debian.org/?p=collab-maint/publican.git

epub support will be broken due to the too old docbook-xsl but the other
output formats will work fine.

Cheers,
-- 
Rapha?l Hertzog ? Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/



From hertzog at debian.org  Tue Nov 15 07:38:09 2011
From: hertzog at debian.org (Raphael Hertzog)
Date: Tue, 15 Nov 2011 08:38:09 +0100
Subject: [publican-list] Inline tags within verbatim environment
Message-ID: <20111115073809.GF14362@rivendell.home.ouaza.com>

Hello,

I don't have the habit to discuss decisions of maintainers but in this
particular case I would like the feedback of the wider community
on this specific bug report that got closed as NOTABUG despite
feedback from the upstream community proving that publican
was doing the weird thing here.

https://bugzilla.redhat.com/show_bug.cgi?id=752851

The upstream docbook-xsl stylesheets do preserve whitespaces and
linebreaks in inlines elements within verbatim environment.

Do any of you have any document where you need the current Publican
behaviour of converting any sequence of whitespace/newlines to a single
space in inline tags within verbatim environments?

To me this behaviour just ensures that I'll never be able to use
any inline element within a verbatim tag because I'll lose
the formatting of my <screens> <programlisting> and so on.
It's really counter-productive IMO and I can't really see who
would like to lose his formatting...

Cheers,
-- 
Rapha?l Hertzog ? Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/



From jwulf at redhat.com  Wed Nov 16 00:20:26 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Wed, 16 Nov 2011 10:20:26 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <20111115073809.GF14362@rivendell.home.ouaza.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
Message-ID: <4EC301CA.1020704@redhat.com>

On 11/15/2011 05:38 PM, Raphael Hertzog wrote:
> Hello,
> 
> I don't have the habit to discuss decisions of maintainers but in this
> particular case I would like the feedback of the wider community
> on this specific bug report that got closed as NOTABUG despite
> feedback from the upstream community proving that publican
> was doing the weird thing here.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=752851
> 
> The upstream docbook-xsl stylesheets do preserve whitespaces and
> linebreaks in inlines elements within verbatim environment.
> 
> Do any of you have any document where you need the current Publican
> behaviour of converting any sequence of whitespace/newlines to a single
> space in inline tags within verbatim environments?
> 
> To me this behaviour just ensures that I'll never be able to use
> any inline element within a verbatim tag because I'll lose
> the formatting of my <screens> <programlisting> and so on.
> It's really counter-productive IMO and I can't really see who
> would like to lose his formatting...
> 
> Cheers,

Interesting problem.

You can achieve the result you want, it just means that if you use an
non-verbatim inline element within a verbatim tag you have to close it
when you want to force a line break.

Which makes sense.

Inheriting also makes a kind of sense. Are there any other examples of
elements inheriting behaviour from the block level element that encloses
them? Or is this the only potential case for this kind of behaviour in
Docbook?

- Josh



From hertzog at debian.org  Wed Nov 16 07:16:52 2011
From: hertzog at debian.org (Raphael Hertzog)
Date: Wed, 16 Nov 2011 08:16:52 +0100
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4EC301CA.1020704@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4EC301CA.1020704@redhat.com>
Message-ID: <20111116071652.GC24582@rivendell.home.ouaza.com>

Hi,

On Wed, 16 Nov 2011, Joshua Wulf wrote:
> You can achieve the result you want, it just means that if you use an
> non-verbatim inline element within a verbatim tag you have to close it
> when you want to force a line break.

And also before each sequence of multiple spaces, and it's quite common in
output of programs which align text in various columns (think df, free).

> Inheriting also makes a kind of sense. Are there any other examples of
> elements inheriting behaviour from the block level element that encloses
> them? Or is this the only potential case for this kind of behaviour in
> Docbook?

This "XML standardization" is really specific to Publican AFAIK so it's
difficult to compare with anything else.

We do have elements that are treated as block when they are outside of
blocks, but not when they are embedded in other blocks (this is the case
of <indexterm> for instance). This is meaningful just to define the
strings needed for a translation. It's the thing that comes closest to
your "inheriting behaviour" request.

In the XSL stylesheets, it's also quite common to look up the parent
hierarchy to adapt the output. Just look how often "ancestor::" appears
in the files.

Cheers,
-- 
Rapha?l Hertzog ? Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/



From jwulf at redhat.com  Wed Nov 16 22:31:39 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Thu, 17 Nov 2011 08:31:39 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <20111116071652.GC24582@rivendell.home.ouaza.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4EC301CA.1020704@redhat.com>
	<20111116071652.GC24582@rivendell.home.ouaza.com>
Message-ID: <4EC439CB.1000106@redhat.com>

On 11/16/2011 05:16 PM, Raphael Hertzog wrote:
> Hi,
> 
> On Wed, 16 Nov 2011, Joshua Wulf wrote:
>> You can achieve the result you want, it just means that if you use an
>> non-verbatim inline element within a verbatim tag you have to close it
>> when you want to force a line break.
> 
> And also before each sequence of multiple spaces, and it's quite common in
> output of programs which align text in various columns (think df, free).

So you mean:

<screen>
...
<computeroutput>Something</computeroutput>     <computeroutput>Column
Two</computeroutput>      <computeroutput>column Three</computeroutput>
</screen>

Yeah, that would suck.

> 
>> Inheriting also makes a kind of sense. Are there any other examples of
>> elements inheriting behaviour from the block level element that encloses
>> them? Or is this the only potential case for this kind of behaviour in
>> Docbook?
> 
> This "XML standardization" is really specific to Publican AFAIK so it's
> difficult to compare with anything else.
> 
> We do have elements that are treated as block when they are outside of
> blocks, but not when they are embedded in other blocks (this is the case
> of <indexterm> for instance). This is meaningful just to define the
> strings needed for a translation. It's the thing that comes closest to
> your "inheriting behaviour" request.
> 
> In the XSL stylesheets, it's also quite common to look up the parent
> hierarchy to adapt the output. Just look how often "ancestor::" appears
> in the files.
> 
> Cheers,


-- 
Give us your feedback on JBoss Enterprise Documentation, take the key
survey:
http://www.keysurvey.com/survey/361436/1065/



From jfearn at redhat.com  Wed Nov 16 22:46:41 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Thu, 17 Nov 2011 08:46:41 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4EC439CB.1000106@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>	<4EC301CA.1020704@redhat.com>	<20111116071652.GC24582@rivendell.home.ouaza.com>
	<4EC439CB.1000106@redhat.com>
Message-ID: <4EC43D51.5060409@redhat.com>

On 11/17/2011 08:31 AM, Joshua Wulf wrote:
> On 11/16/2011 05:16 PM, Raphael Hertzog wrote:
>> Hi,
>>
>> On Wed, 16 Nov 2011, Joshua Wulf wrote:
>>> You can achieve the result you want, it just means that if you use an
>>> non-verbatim inline element within a verbatim tag you have to close it
>>> when you want to force a line break.
>>
>> And also before each sequence of multiple spaces, and it's quite common in
>> output of programs which align text in various columns (think df, free).
>
> So you mean:
>
> <screen>
> ...
> <computeroutput>Something</computeroutput>      <computeroutput>Column
> Two</computeroutput>       <computeroutput>column Three</computeroutput>
> </screen>
>
> Yeah, that would suck.

I'd love an example of a screen that doesn't contain "Text that a user 
sees or might see on a computer screen" AND does contain computer output.

screen is the verbatim brother of computeroutput, I've never seen an 
example of where nesting them isn't pointless, but I would love to see 
such an example! So bring one on and I will reconsider my position.

Cheers, Jeff.

-- 
"Reply All" why you shouldn't use it: 
http://www.emailreplies.com/#12replytoall



From bugzilla at redhat.com  Thu Nov 17 03:45:48 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Wed, 16 Nov 2011 22:45:48 -0500
Subject: [publican-list] [Bug 705953] Formatting issues in PDF version of
 HTTP Connectors Load Balancing Guide
In-Reply-To: <bug-705953-264938@bugzilla.redhat.com>
References: <bug-705953-264938@bugzilla.redhat.com>
Message-ID: <201111170345.pAH3jmHL022372@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=705953

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |needinfo?(jmorgan at redhat.co
                   |                            |m)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Thu Nov 17 03:47:15 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Wed, 16 Nov 2011 22:47:15 -0500
Subject: [publican-list] [Bug 710304] <xref>ing to Appendix does not create
 a link in html-single
In-Reply-To: <bug-710304-264938@bugzilla.redhat.com>
References: <bug-710304-264938@bugzilla.redhat.com>
Message-ID: <201111170347.pAH3lFgH013325@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=710304

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|                            |NOTABUG
        Last Closed|                            |2011-11-16 22:47:14

--- Comment #3 from Jeff Fearn <jfearn at redhat.com> 2011-11-16 22:47:14 EST ---
Assuming this still works, please reopen if you can duplicate this issue.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Thu Nov 17 04:28:08 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Wed, 16 Nov 2011 23:28:08 -0500
Subject: [publican-list] [Bug 705953] Formatting issues in PDF version of
 HTTP Connectors Load Balancing Guide
In-Reply-To: <bug-705953-264938@bugzilla.redhat.com>
References: <bug-705953-264938@bugzilla.redhat.com>
Message-ID: <201111170428.pAH4S8VN021912@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=705953

Jared Morgan <jmorgan at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |MODIFIED
               Flag|needinfo?(jmorgan at redhat.co |needinfo?(jfearn at redhat.com
                   |m)                          |)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Thu Nov 17 05:08:46 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 17 Nov 2011 00:08:46 -0500
Subject: [publican-list] [Bug 705953] Formatting issues in PDF version of
 HTTP Connectors Load Balancing Guide
In-Reply-To: <bug-705953-264938@bugzilla.redhat.com>
References: <bug-705953-264938@bugzilla.redhat.com>
Message-ID: <201111170508.pAH58kA1006465@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=705953

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?(jfearn at redhat.com |
                   |)                           |

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Thu Nov 17 05:14:17 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 17 Nov 2011 00:14:17 -0500
Subject: [publican-list] [Bug 726548] <superscript> tags display an
	"Unvalidated Tag Warning"
In-Reply-To: <bug-726548-264938@bugzilla.redhat.com>
References: <bug-726548-264938@bugzilla.redhat.com>
Message-ID: <201111170514.pAH5EHXJ007604@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=726548

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |MODIFIED
   Target Milestone|---                         |2.9

--- Comment #1 from Jeff Fearn <jfearn at redhat.com> 2011-11-17 00:14:16 EST ---
Added support for superscript, fixed color.

Applied to branches/publican-2x and trunk.

Committed revision 1952.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Thu Nov 17 06:17:01 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 17 Nov 2011 01:17:01 -0500
Subject: [publican-list] [Bug 708259] RFE: Support per-book additions to the
	legal notice
In-Reply-To: <bug-708259-264938@bugzilla.redhat.com>
References: <bug-708259-264938@bugzilla.redhat.com>
Message-ID: <201111170617.pAH6H10S013052@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=708259

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |jfearn at redhat.com
         Resolution|                            |NOTABUG
        Last Closed|                            |2011-11-17 01:17:00

--- Comment #4 from Jeff Fearn <jfearn at redhat.com> 2011-11-17 01:17:00 EST ---
This can be done using fallbacks, an empty entry!

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Thu Nov 17 06:18:02 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 17 Nov 2011 01:18:02 -0500
Subject: [publican-list] [Bug 715382] Add switch to enable TOC in appendix
In-Reply-To: <bug-715382-264938@bugzilla.redhat.com>
References: <bug-715382-264938@bugzilla.redhat.com>
Message-ID: <201111170618.pAH6I2Lq013218@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=715382

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |jfearn at redhat.com
         Resolution|                            |NOTABUG
        Last Closed|                            |2011-11-17 01:18:01

--- Comment #2 from Jeff Fearn <jfearn at redhat.com> 2011-11-17 01:18:01 EST ---
Assuming this was done in a brand, let me know directly if you need any
assistance getting brands working.

-- 
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 hertzog at debian.org  Thu Nov 17 08:04:26 2011
From: hertzog at debian.org (Raphael Hertzog)
Date: Thu, 17 Nov 2011 09:04:26 +0100
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4EC43D51.5060409@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4EC301CA.1020704@redhat.com>
	<20111116071652.GC24582@rivendell.home.ouaza.com>
	<4EC439CB.1000106@redhat.com> <4EC43D51.5060409@redhat.com>
Message-ID: <20111117080426.GE26718@rivendell.home.ouaza.com>

Hi,

On Thu, 17 Nov 2011, Jeff Fearn wrote:
> I'd love an example of a screen that doesn't contain "Text that a
> user sees or might see on a computer screen" AND does contain
> computer output.
> 
> screen is the verbatim brother of computeroutput, I've never seen an
> example of where nesting them isn't pointless, but I would love to
> see such an example! So bring one on and I will reconsider my
> position.

Ok, you can argue that <computeroutput> is useless in <screen> and I could
agree with that (but then why is it allowed by the standard in the first
place?).

But the story is the same with <userinput> and this one is really useful
to highlight the part of the screen that the user is supposed to type
(it's rendered in bold while computeroutput is usually not, except that
Publican overrides this...)! Here's one example where you might want to
keep the linebreaks and the multiple spaces.

<screen>
$ <userinput>cat &gt;crontab &lt;&lt;END
# min hours day month dow command
  0   19    *   *     *   fetchmail
END</userinput>
$ <userinput>crontab crontab</userinput>
</screen>

Cheers,
-- 
Rapha?l Hertzog ? Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/



From jwulf at redhat.com  Thu Nov 17 11:13:44 2011
From: jwulf at redhat.com (Joshua Wulf)
Date: Thu, 17 Nov 2011 06:13:44 -0500 (EST)
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <20111117080426.GE26718@rivendell.home.ouaza.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4EC301CA.1020704@redhat.com>
	<20111116071652.GC24582@rivendell.home.ouaza.com>
	<4EC439CB.1000106@redhat.com> <4EC43D51.5060409@redhat.com>
	<20111117080426.GE26718@rivendell.home.ouaza.com>
Message-ID: <348C1846-3197-423F-93BE-11D5CAA5786A@redhat.com>

In other words, it's really only an issue if you want to distinguish among the contents of a <screen> tag by marking them up differently. 

Marking up what the user enters and what the computer displays seems like a logical use-case, but yeah it relies on <userinput> and <computeroutput> being presented differently on output to make any sense. 

- Josh

~ Kirtan is Life! ~
Sent from my iPhone.

On 17/11/2011, at 7:04 PM, Raphael Hertzog <hertzog at debian.org> wrote:

> Hi,
> 
> On Thu, 17 Nov 2011, Jeff Fearn wrote:
>> I'd love an example of a screen that doesn't contain "Text that a
>> user sees or might see on a computer screen" AND does contain
>> computer output.
>> 
>> screen is the verbatim brother of computeroutput, I've never seen an
>> example of where nesting them isn't pointless, but I would love to
>> see such an example! So bring one on and I will reconsider my
>> position.
> 
> Ok, you can argue that <computeroutput> is useless in <screen> and I could
> agree with that (but then why is it allowed by the standard in the first
> place?).
> 
> But the story is the same with <userinput> and this one is really useful
> to highlight the part of the screen that the user is supposed to type
> (it's rendered in bold while computeroutput is usually not, except that
> Publican overrides this...)! Here's one example where you might want to
> keep the linebreaks and the multiple spaces.
> 
> <screen>
> $ <userinput>cat &gt;crontab &lt;&lt;END
> # min hours day month dow command
>  0   19    *   *     *   fetchmail
> END</userinput>
> $ <userinput>crontab crontab</userinput>
> </screen>
> 
> Cheers,
> -- 
> Rapha?l Hertzog ? Debian Developer
> 
> Pre-order a copy of the Debian Administrator's Handbook and help
> liberate it: http://debian-handbook.info/go/ulule-rh/
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican



From bugzilla at redhat.com  Thu Nov 17 21:58:56 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 17 Nov 2011 16:58:56 -0500
Subject: [publican-list] [Bug 705953] Formatting issues in PDF version of
 HTTP Connectors Load Balancing Guide
In-Reply-To: <bug-705953-264938@bugzilla.redhat.com>
References: <bug-705953-264938@bugzilla.redhat.com>
Message-ID: <201111172158.pAHLwuvL024719@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=705953

Jared Morgan <jmorgan at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |needinfo?(jfearn at redhat.com
                   |                            |)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Fri Nov 18 05:01:15 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Fri, 18 Nov 2011 00:01:15 -0500
Subject: [publican-list] [Bug 705953] Formatting issues in PDF version of
 HTTP Connectors Load Balancing Guide
In-Reply-To: <bug-705953-264938@bugzilla.redhat.com>
References: <bug-705953-264938@bugzilla.redhat.com>
Message-ID: <201111180501.pAI51FCU023796@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=705953

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?(jfearn at redhat.com |
                   |)                           |

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Tue Nov 22 17:10:41 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Tue, 22 Nov 2011 12:10:41 -0500
Subject: [publican-list] [Bug 691301] No SELinux context for
 /var/www/html/docs/index.html file in publican generated web RPMs?
In-Reply-To: <bug-691301-264938@bugzilla.redhat.com>
References: <bug-691301-264938@bugzilla.redhat.com>
Message-ID: <201111221710.pAMHAfZM018401@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=691301

Stephen Gordon <sgordon at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|                            |WORKSFORME
        Last Closed|                            |2011-11-22 12:10:40

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From jfearn at redhat.com  Wed Nov 23 06:00:49 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Wed, 23 Nov 2011 16:00:49 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <20111115073809.GF14362@rivendell.home.ouaza.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
Message-ID: <4ECC8C11.9030308@redhat.com>

On 11/15/2011 05:38 PM, Raphael Hertzog wrote:
> Hello,
>
> I don't have the habit to discuss decisions of maintainers but in this
> particular case I would like the feedback of the wider community
> on this specific bug report that got closed as NOTABUG despite
> feedback from the upstream community proving that publican
> was doing the weird thing here.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=752851
>
> The upstream docbook-xsl stylesheets do preserve whitespaces and
> linebreaks in inlines elements within verbatim environment.
>
> Do any of you have any document where you need the current Publican
> behaviour of converting any sequence of whitespace/newlines to a single
> space in inline tags within verbatim environments?
>
> To me this behaviour just ensures that I'll never be able to use
> any inline element within a verbatim tag because I'll lose
> the formatting of my<screens>  <programlisting>  and so on.
> It's really counter-productive IMO and I can't really see who
> would like to lose his formatting...
>
> Cheers,

For me this raises a larger issue, should Publican be interfering with 
the source XML at all?

XmlClean exists for two historical reasons, neither of which still 
exist. Migrating old html/sgml content to XML, enforcing certain 
standards are met.

The old content was migrated years ago and that process required a bunch 
of scripts that never made it in to Publican ... they were horrific 
people, horrific!

We backed away from enforcing standards sometime ago, see the death of 
STRICT mode.

Given that neither of the reasons the code exists are of any relevance 
any more, maybe we should just remove XmlClean completely. This would 
see the death of clead_ids as well, but that was specifically for 
migrating content and has never been supported for general use.

Comments?

Cheers, Jeff.



From hertzog at debian.org  Wed Nov 23 07:32:45 2011
From: hertzog at debian.org (Raphael Hertzog)
Date: Wed, 23 Nov 2011 08:32:45 +0100
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4ECC8C11.9030308@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4ECC8C11.9030308@redhat.com>
Message-ID: <20111123073245.GJ26080@rivendell.home.ouaza.com>

On Wed, 23 Nov 2011, Jeff Fearn wrote:
> For me this raises a larger issue, should Publican be interfering
> with the source XML at all?
> 
> XmlClean exists for two historical reasons, neither of which still
> exist. Migrating old html/sgml content to XML, enforcing certain
> standards are met.

Oh, interesting, I thought it was partly also related to the
"standardization" required to generate strings for PO files. But if it's
something different, then I support its removal. It's best to not
interfer with the source XML when it's not required.

Cheers,
-- 
Rapha?l Hertzog ? Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/



From jaredsmith at jaredsmith.net  Wed Nov 23 13:59:52 2011
From: jaredsmith at jaredsmith.net (Jared Smith)
Date: Wed, 23 Nov 2011 08:59:52 -0500
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4ECC8C11.9030308@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4ECC8C11.9030308@redhat.com>
Message-ID: <CAJKpme-_UP+B3rRrS95njC8jyFeQ089Kg0sK869RrhHPdrGaDw@mail.gmail.com>

On Wed, Nov 23, 2011 at 1:00 AM, Jeff Fearn <jfearn at redhat.com> wrote:
> Given that neither of the reasons the code exists are of any relevance any
> more, maybe we should just remove XmlClean completely.

That proposal has my full support.

--
Jared Smith



From davido at redhat.com  Thu Nov 24 00:56:21 2011
From: davido at redhat.com (David O'Brien)
Date: Thu, 24 Nov 2011 10:56:21 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4ECC8C11.9030308@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4ECC8C11.9030308@redhat.com>
Message-ID: <4ECD9635.3000407@redhat.com>

On 11/23/2011 04:00 PM, Jeff Fearn wrote:
> On 11/15/2011 05:38 PM, Raphael Hertzog wrote:
>> Hello,
>>
>> I don't have the habit to discuss decisions of maintainers but in this
>> particular case I would like the feedback of the wider community
>> on this specific bug report that got closed as NOTABUG despite
>> feedback from the upstream community proving that publican
>> was doing the weird thing here.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=752851
>>
>> The upstream docbook-xsl stylesheets do preserve whitespaces and
>> linebreaks in inlines elements within verbatim environment.
>>
>> Do any of you have any document where you need the current Publican
>> behaviour of converting any sequence of whitespace/newlines to a single
>> space in inline tags within verbatim environments?
>>
>> To me this behaviour just ensures that I'll never be able to use
>> any inline element within a verbatim tag because I'll lose
>> the formatting of my<screens>  <programlisting>  and so on.
>> It's really counter-productive IMO and I can't really see who
>> would like to lose his formatting...
>>
>> Cheers,
> 
> For me this raises a larger issue, should Publican be interfering with
> the source XML at all?
> 
> XmlClean exists for two historical reasons, neither of which still
> exist. Migrating old html/sgml content to XML, enforcing certain
> standards are met.
> 
> The old content was migrated years ago and that process required a bunch
> of scripts that never made it in to Publican ... they were horrific
> people, horrific!
> 
> We backed away from enforcing standards sometime ago, see the death of
> STRICT mode.
> 
> Given that neither of the reasons the code exists are of any relevance
> any more, maybe we should just remove XmlClean completely. This would
> see the death of clead_ids as well, but that was specifically for
> migrating content and has never been supported for general use.
> 
> Comments?
> 
> Cheers, Jeff.
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican

I would mourn the loss of clean_ids.

Perhaps it was created for a particular purpose that may no longer (or
rarely) exist, but clean_ids has proven to be very useful for other
purposes. I know I'm not the only one who uses it; I also know several
people who are against using it. Those sorts of debates will always
exist, and are probably healthy.

Is it not possible to remove only those aspects of xmlClean that are not
used, and retain clean_ids? If I were a coder I would happily get
involved in this exercise, but I'm an end user who sees the potential
loss of a very useful tool.

-- 

David O'Brien
Senior Content Author
Engineering Content Services (ECS)
Red Hat Asia Pacific Pty Ltd
+61 7 3514 8189


"We couldn't care less about comfort. We make you feel good."
 ~ Federico Minoli CEO Ducati Motor S.p.A.



From lbrindle at redhat.com  Thu Nov 24 02:44:09 2011
From: lbrindle at redhat.com (Lana Brindley)
Date: Thu, 24 Nov 2011 13:44:09 +1100
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4ECD9635.3000407@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4ECC8C11.9030308@redhat.com> <4ECD9635.3000407@redhat.com>
Message-ID: <4ECDAF79.50908@redhat.com>

On 11/24/2011 11:56 AM, David O'Brien wrote:
> On 11/23/2011 04:00 PM, Jeff Fearn wrote:
>> On 11/15/2011 05:38 PM, Raphael Hertzog wrote:
>>> Hello,
>>>
>>> I don't have the habit to discuss decisions of maintainers but in this
>>> particular case I would like the feedback of the wider community
>>> on this specific bug report that got closed as NOTABUG despite
>>> feedback from the upstream community proving that publican
>>> was doing the weird thing here.
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=752851
>>>
>>> The upstream docbook-xsl stylesheets do preserve whitespaces and
>>> linebreaks in inlines elements within verbatim environment.
>>>
>>> Do any of you have any document where you need the current Publican
>>> behaviour of converting any sequence of whitespace/newlines to a single
>>> space in inline tags within verbatim environments?
>>>
>>> To me this behaviour just ensures that I'll never be able to use
>>> any inline element within a verbatim tag because I'll lose
>>> the formatting of my<screens>   <programlisting>   and so on.
>>> It's really counter-productive IMO and I can't really see who
>>> would like to lose his formatting...
>>>
>>> Cheers,
>>
>> For me this raises a larger issue, should Publican be interfering with
>> the source XML at all?
>>
>> XmlClean exists for two historical reasons, neither of which still
>> exist. Migrating old html/sgml content to XML, enforcing certain
>> standards are met.
>>
>> The old content was migrated years ago and that process required a bunch
>> of scripts that never made it in to Publican ... they were horrific
>> people, horrific!
>>
>> We backed away from enforcing standards sometime ago, see the death of
>> STRICT mode.
>>
>> Given that neither of the reasons the code exists are of any relevance
>> any more, maybe we should just remove XmlClean completely. This would
>> see the death of clead_ids as well, but that was specifically for
>> migrating content and has never been supported for general use.
>>
>> Comments?
>>
>> Cheers, Jeff.
>>
>> _______________________________________________
>> publican-list mailing list
>> publican-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/publican-list
>> Wiki: https://fedorahosted.org/publican
>
> I would mourn the loss of clean_ids.
>
> Perhaps it was created for a particular purpose that may no longer (or
> rarely) exist, but clean_ids has proven to be very useful for other
> purposes. I know I'm not the only one who uses it; I also know several
> people who are against using it. Those sorts of debates will always
> exist, and are probably healthy.
>
> Is it not possible to remove only those aspects of xmlClean that are not
> used, and retain clean_ids? If I were a coder I would happily get
> involved in this exercise, but I'm an end user who sees the potential
> loss of a very useful tool.

+1

Used deliberately and with caution, clean_ids is a great tool.

L

-- 
Lana Brindley
Senior Content Author
Engineering Content Services
+61 7 3514 8178 - ext (85) 88178
RHEL5 RHCT: 605008757717273
RHEL5 RHCSA: 100-043-694

No passion in the world is equal to the passion to alter someone else's 
draft.
H. G. Wells (1866 - 1946)



From dmison at redhat.com  Mon Nov 28 22:42:50 2011
From: dmison at redhat.com (Darrin Mison)
Date: Tue, 29 Nov 2011 08:42:50 +1000
Subject: [publican-list] Release tags/branches
Message-ID: <C1A5514B-A304-4631-8272-503DD7760AB5@redhat.com>

To follow up on Misty's awesome OSX install instructions I was looking at what would be involved in getting Publican into MacPorts - or at least contribute a port file to do a local install.

However I can't see any tags or final release branches for any of the Publican 2 point releases in svn.fedorahosted.org/svn/publican.  I can see directories for the release notes for each.  

Am I looking in the wrong place?

--
Darrin Mison
"I'm not a JBoss Developer, I just play one on TV"
Content Author - Engineering Content Services, Red Hat, Inc.
RHCSA #111-092-417



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/publican-list/attachments/20111129/6811710f/attachment.htm>

From jfearn at redhat.com  Mon Nov 28 23:02:30 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Tue, 29 Nov 2011 09:02:30 +1000
Subject: [publican-list] Release tags/branches
In-Reply-To: <C1A5514B-A304-4631-8272-503DD7760AB5@redhat.com>
References: <C1A5514B-A304-4631-8272-503DD7760AB5@redhat.com>
Message-ID: <4ED41306.5010201@redhat.com>

On 11/29/2011 08:42 AM, Darrin Mison wrote:
> To follow up on Misty's awesome OSX install instructions I was looking
> at what would be involved in getting Publican into MacPorts - or at
> least contribute a port file to do a local install.
>
> However I can't see any tags or final release branches for any of the
> Publican 2 point releases in svn.fedorahosted.org/svn/publican
> <http://svn.fedorahosted.org/svn/publican>. I can see directories for
> the release notes for each.
>
> Am I looking in the wrong place?

We don't track minor releases in SVN. We branch when we start a new 
major release and track all minor releases for the previous major 
release in a single branch.

The branch for 2.x is:

svn.fedorahosted.org/svn/publican/branches/publican-2x

You can get tar balls for every release at:

https://fedorahosted.org/releases/p/u/publican/

Cheers, Jeff.



From dmison at redhat.com  Mon Nov 28 23:17:49 2011
From: dmison at redhat.com (Darrin Mison)
Date: Tue, 29 Nov 2011 09:17:49 +1000
Subject: [publican-list] Release tags/branches
In-Reply-To: <4ED41306.5010201@redhat.com>
References: <C1A5514B-A304-4631-8272-503DD7760AB5@redhat.com>
	<4ED41306.5010201@redhat.com>
Message-ID: <0FD56271-E172-4829-BB3F-B7F3D2C996E0@redhat.com>


On 29/11/2011, at 9:02 AM, Jeff Fearn wrote:

> On 11/29/2011 08:42 AM, Darrin Mison wrote:
>> To follow up on Misty's awesome OSX install instructions I was looking
>> at what would be involved in getting Publican into MacPorts - or at
>> least contribute a port file to do a local install.
>> 
>> However I can't see any tags or final release branches for any of the
>> Publican 2 point releases in svn.fedorahosted.org/svn/publican
>> <http://svn.fedorahosted.org/svn/publican>. I can see directories for
>> the release notes for each.
>> 
>> Am I looking in the wrong place?
> 
> We don't track minor releases in SVN. We branch when we start a new major release and track all minor releases for the previous major release in a single branch.
> 
> The branch for 2.x is:
> 
> svn.fedorahosted.org/svn/publican/branches/publican-2x
> 
> You can get tar balls for every release at:
> 
> https://fedorahosted.org/releases/p/u/publican/

Ah ha!  I think this is relevant to my interests ;-)

Thanks.


> Cheers, Jeff.
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican

Darrin Mison
"I'm not a JBoss Developer, I just play one on TV"
Content Author - Engineering Content Services, Red Hat, Inc.
RHCSA #111-092-417



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/publican-list/attachments/20111129/cd703dd7/attachment.htm>

From jfearn at redhat.com  Mon Nov 28 23:48:08 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Tue, 29 Nov 2011 09:48:08 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <4ECDAF79.50908@redhat.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4ECC8C11.9030308@redhat.com> <4ECD9635.3000407@redhat.com>
	<4ECDAF79.50908@redhat.com>
Message-ID: <4ED41DB8.70606@redhat.com>

On 11/24/2011 12:44 PM, Lana Brindley wrote:
> On 11/24/2011 11:56 AM, David O'Brien wrote:
>> On 11/23/2011 04:00 PM, Jeff Fearn wrote:
>>> On 11/15/2011 05:38 PM, Raphael Hertzog wrote:
>>>> Hello,
>>>>
>>>> I don't have the habit to discuss decisions of maintainers but in this
>>>> particular case I would like the feedback of the wider community
>>>> on this specific bug report that got closed as NOTABUG despite
>>>> feedback from the upstream community proving that publican
>>>> was doing the weird thing here.
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=752851
>>>>
>>>> The upstream docbook-xsl stylesheets do preserve whitespaces and
>>>> linebreaks in inlines elements within verbatim environment.
>>>>
>>>> Do any of you have any document where you need the current Publican
>>>> behaviour of converting any sequence of whitespace/newlines to a single
>>>> space in inline tags within verbatim environments?
>>>>
>>>> To me this behaviour just ensures that I'll never be able to use
>>>> any inline element within a verbatim tag because I'll lose
>>>> the formatting of my<screens> <programlisting> and so on.
>>>> It's really counter-productive IMO and I can't really see who
>>>> would like to lose his formatting...
>>>>
>>>> Cheers,
>>>
>>> For me this raises a larger issue, should Publican be interfering with
>>> the source XML at all?
>>>
>>> XmlClean exists for two historical reasons, neither of which still
>>> exist. Migrating old html/sgml content to XML, enforcing certain
>>> standards are met.
>>>
>>> The old content was migrated years ago and that process required a bunch
>>> of scripts that never made it in to Publican ... they were horrific
>>> people, horrific!
>>>
>>> We backed away from enforcing standards sometime ago, see the death of
>>> STRICT mode.
>>>
>>> Given that neither of the reasons the code exists are of any relevance
>>> any more, maybe we should just remove XmlClean completely. This would
>>> see the death of clead_ids as well, but that was specifically for
>>> migrating content and has never been supported for general use.
>>>
>>> Comments?
>>>
>>> Cheers, Jeff.
>>>
>>> _______________________________________________
>>> publican-list mailing list
>>> publican-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/publican-list
>>> Wiki: https://fedorahosted.org/publican
>>
>> I would mourn the loss of clean_ids.
>>
>> Perhaps it was created for a particular purpose that may no longer (or
>> rarely) exist, but clean_ids has proven to be very useful for other
>> purposes. I know I'm not the only one who uses it; I also know several
>> people who are against using it. Those sorts of debates will always
>> exist, and are probably healthy.
>>
>> Is it not possible to remove only those aspects of xmlClean that are not
>> used, and retain clean_ids? If I were a coder I would happily get
>> involved in this exercise, but I'm an end user who sees the potential
>> loss of a very useful tool.
>
> +1
>
> Used deliberately and with caution, clean_ids is a great tool.
>
> L
>

Since the white space munging code in XmlClean is causing yet another 
issue [1], for 2.9 I'm killing off the white space munging, so clean_ids 
won't reformat your XML in 2.9. It will still change all your ID's when 
and how it sees fit and it might even update the PO files to some extent 
... maybe even correctly ... you roll the dice and take your changes 
with it :)

Cheers, Jeff.

1: https://bugzilla.redhat.com/show_bug.cgi?id=756756



From bugzilla at redhat.com  Tue Nov 29 01:38:14 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 28 Nov 2011 20:38:14 -0500
Subject: [publican-list] [Bug 711348] Linking to a bridgehead does not work
	in html formats
In-Reply-To: <bug-711348-264938@bugzilla.redhat.com>
References: <bug-711348-264938@bugzilla.redhat.com>
Message-ID: <201111290138.pAT1cECq027246@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=711348

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|MODIFIED                    |CLOSED
   Fixed In Version|                            |2.3
         Resolution|                            |NEXTRELEASE
        Last Closed|                            |2011-11-28 20:38:13

--- Comment #2 from Jeff Fearn <jfearn at redhat.com> 2011-11-28 20:38:13 EST ---
wow this fix shipped ages ago!

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Tue Nov 29 01:39:19 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 28 Nov 2011 20:39:19 -0500
Subject: [publican-list] [Bug 545334] Invalid XML can cause hard to decipher
	entity errors
In-Reply-To: <bug-545334-264938@bugzilla.redhat.com>
References: <bug-545334-264938@bugzilla.redhat.com>
Message-ID: <201111290139.pAT1dJts027381@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=545334

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|MODIFIED                    |CLOSED
         Resolution|                            |NEXTRELEASE
               Flag|needinfo?(dmison at redhat.com |
                   |)                           |
        Last Closed|                            |2011-11-28 20:39:16

--- Comment #9 from Jeff Fearn <jfearn at redhat.com> 2011-11-28 20:39:16 EST ---
Required modules were updated some time ago.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Tue Nov 29 01:40:34 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 28 Nov 2011 20:40:34 -0500
Subject: [publican-list] [Bug 676472] Koji doesn't like Publican-produced
	SRPMs
In-Reply-To: <bug-676472-264938@bugzilla.redhat.com>
References: <bug-676472-264938@bugzilla.redhat.com>
Message-ID: <201111290140.pAT1eYn6027860@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=676472

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|MODIFIED                    |CLOSED
         Resolution|                            |UPSTREAM
        Last Closed|                            |2011-11-28 20:40:33

--- Comment #4 from Jeff Fearn <jfearn at redhat.com> 2011-11-28 20:40:33 EST ---
Fix shipped some time ago.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From bugzilla at redhat.com  Tue Nov 29 01:45:13 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 28 Nov 2011 20:45:13 -0500
Subject: [publican-list] [Bug 705953] Formatting issues in PDF version of
 HTTP Connectors Load Balancing Guide
In-Reply-To: <bug-705953-264938@bugzilla.redhat.com>
References: <bug-705953-264938@bugzilla.redhat.com>
Message-ID: <201111290145.pAT1jDB7028618@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=705953

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |2.9

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



From jfearn at redhat.com  Tue Nov 29 01:54:38 2011
From: jfearn at redhat.com (Jeff Fearn)
Date: Tue, 29 Nov 2011 11:54:38 +1000
Subject: [publican-list] Inline tags within verbatim environment
In-Reply-To: <20111123073245.GJ26080@rivendell.home.ouaza.com>
References: <20111115073809.GF14362@rivendell.home.ouaza.com>
	<4ECC8C11.9030308@redhat.com>
	<20111123073245.GJ26080@rivendell.home.ouaza.com>
Message-ID: <4ED43B5E.3010801@redhat.com>

On 11/23/2011 05:32 PM, Raphael Hertzog wrote:
> On Wed, 23 Nov 2011, Jeff Fearn wrote:
>> For me this raises a larger issue, should Publican be interfering
>> with the source XML at all?
>>
>> XmlClean exists for two historical reasons, neither of which still
>> exist. Migrating old html/sgml content to XML, enforcing certain
>> standards are met.
>
> Oh, interesting, I thought it was partly also related to the
> "standardization" required to generate strings for PO files. But if it's
> something different, then I support its removal. It's best to not
> interfer with the source XML when it's not required.

FYI the white space munging has been removed for 2.9, which is scheduled 
sometime between now and Christmas ... assuming you have all been good 
boys and girls of course!

Cheers, Jeff.



From bugzilla at redhat.com  Tue Nov 29 01:50:54 2011
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 28 Nov 2011 20:50:54 -0500
Subject: [publican-list] [Bug 735687] fop error when authorgroup contains
	only corpauthor
In-Reply-To: <bug-735687-264938@bugzilla.redhat.com>
References: <bug-735687-264938@bugzilla.redhat.com>
Message-ID: <201111290150.pAT1osOP010028@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=735687

Jeff Fearn <jfearn at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|                            |DUPLICATE
        Last Closed|                            |2011-11-28 20:50:53

--- Comment #2 from Jeff Fearn <jfearn at redhat.com> 2011-11-28 20:50:53 EST ---


*** This bug has been marked as a duplicate of bug 756864 ***

-- 
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.