tag:old.nabble.com,2006:forum-15826Nabble - DocBook2009-11-23T07:39:32Z<a href="http://docbook.org/help" target="_top" rel="nofollow">DocBook</a> is a schema (available in several languages including RELAX NG, SGML and XML DTDs, and W3C XML Schema) maintained by the DocBook Technical Committee of OASIS. It is particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).tag:old.nabble.com,2006:post-26480476Re: RFE 2791288: add quote to corpauthor and gui elements2009-11-23T07:39:32Z2009-11-23T07:39:32ZNorman WalshNorman Walsh <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26480476&i=0" target="_top" rel="nofollow">ndw@...</a>> writes:
<br>> My current thinking is that we should treat the inlines in groups. If
<br>> you're going to allow some elements of a group, you might just as well
<br>> allow all the elements.
<br>[...]
<br>> I think the natural proposal at this point is to say that we should
<br>> allow the publishing inlines (and trademark) into the ubiquituos
<br>> inlnes.
<br><br>At the November 2009 telcon, I took an action to produce a
<br>customization layer that implements this proposal. Please find it
<br>attached, along with an example document that outlines the scope of
<br>the changes imposed by this proposal.
<br><br><br /> <br /> <br /><?xml version="1.0" encoding="utf-8"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>More ubiquitous inlines</title>
<link rel="stylesheet" type="text/css" href="/sourceforge/docbook/xsl2/html/default.css" />
</head>
<body>
<div class="article" id="R.1">
<div class="article-titlepage">
<h2>More ubiquitous inlines</h2>
</div>
<p>Under this proposal, all of the “publishing inlines” and
<tt class="tag-element">trademark</tt> are added to the set of “ubiquitous inlines”.
This will extend the content models of all of the following
elements:
</p>
<table class="simplelist" border="0" summary="Simple list">
<tr>
<td><span class="member"><tt class="tag-element">abbrev</tt></span></td>
<td><span class="member"><tt class="tag-element">database</tt></span></td>
<td><span class="member"><tt class="tag-element">keycap</tt></span></td>
<td><span class="member"><tt class="tag-element">postcode</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">accel</tt></span></td>
<td><span class="member"><tt class="tag-element">edition</tt></span></td>
<td><span class="member"><tt class="tag-element">keycode</tt></span></td>
<td><span class="member"><tt class="tag-element">productname</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">acronym</tt></span></td>
<td><span class="member"><tt class="tag-element">email</tt></span></td>
<td><span class="member"><tt class="tag-element">keysym</tt></span></td>
<td><span class="member"><tt class="tag-element">productnumber</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">address</tt></span></td>
<td><span class="member"><tt class="tag-element">emphasis</tt></span></td>
<td><span class="member"><tt class="tag-element">label</tt></span></td>
<td><span class="member"><tt class="tag-element">property</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">application</tt></span></td>
<td><span class="member"><tt class="tag-element">envar</tt></span></td>
<td><span class="member"><tt class="tag-element">lineage</tt></span></td>
<td><span class="member"><tt class="tag-element">publishername</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">arg</tt></span></td>
<td><span class="member"><tt class="tag-element">errorcode</tt></span></td>
<td><span class="member"><tt class="tag-element">lineannotation</tt></span></td>
<td><span class="member"><tt class="tag-element">refmiscinfo</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">artpagenums</tt></span></td>
<td><span class="member"><tt class="tag-element">errorname</tt></span></td>
<td><span class="member"><tt class="tag-element">literal</tt></span></td>
<td><span class="member"><tt class="tag-element">releaseinfo</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">attribution</tt></span></td>
<td><span class="member"><tt class="tag-element">errortext</tt></span></td>
<td><span class="member"><tt class="tag-element">manvolnum</tt></span></td>
<td><span class="member"><tt class="tag-element">remark</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">authorinitials</tt></span></td>
<td><span class="member"><tt class="tag-element">errortype</tt></span></td>
<td><span class="member"><tt class="tag-element">markup</tt></span></td>
<td><span class="member"><tt class="tag-element">returnvalue</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">bibliocoverage</tt></span></td>
<td><span class="member"><tt class="tag-element">exceptionname</tt></span></td>
<td><span class="member"><tt class="tag-element">mathphrase</tt></span></td>
<td><span class="member"><tt class="tag-element">revnumber</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">biblioid</tt></span></td>
<td><span class="member"><tt class="tag-element">fax</tt></span></td>
<td><span class="member"><tt class="tag-element">methodname</tt></span></td>
<td><span class="member"><tt class="tag-element">revremark</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">bibliomisc</tt></span></td>
<td><span class="member"><tt class="tag-element">filename</tt></span></td>
<td><span class="member"><tt class="tag-element">modifier</tt></span></td>
<td><span class="member"><tt class="tag-element">seriesvolnums</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">bibliomset</tt></span></td>
<td><span class="member"><tt class="tag-element">firstname</tt></span></td>
<td><span class="member"><tt class="tag-element">mousebutton</tt></span></td>
<td><span class="member"><tt class="tag-element">shortaffil</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">bibliorelation</tt></span></td>
<td><span class="member"><tt class="tag-element">funcdef</tt></span></td>
<td><span class="member"><tt class="tag-element">msgaud</tt></span></td>
<td><span class="member"><tt class="tag-element">state</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">bibliosource</tt></span></td>
<td><span class="member"><tt class="tag-element">funcparams</tt></span></td>
<td><span class="member"><tt class="tag-element">msglevel</tt></span></td>
<td><span class="member"><tt class="tag-element">street</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">citebiblioid</tt></span></td>
<td><span class="member"><tt class="tag-element">function</tt></span></td>
<td><span class="member"><tt class="tag-element">msgorig</tt></span></td>
<td><span class="member"><tt class="tag-element">subscript</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">city</tt></span></td>
<td><span class="member"><tt class="tag-element">givenname</tt></span></td>
<td><span class="member"><tt class="tag-element">option</tt></span></td>
<td><span class="member"><tt class="tag-element">superscript</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">classname</tt></span></td>
<td><span class="member"><tt class="tag-element">guibutton</tt></span></td>
<td><span class="member"><tt class="tag-element">optional</tt></span></td>
<td><span class="member"><tt class="tag-element">surname</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">code</tt></span></td>
<td><span class="member"><tt class="tag-element">guiicon</tt></span></td>
<td><span class="member"><tt class="tag-element">orgname</tt></span></td>
<td><span class="member"><tt class="tag-element">symbol</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">command</tt></span></td>
<td><span class="member"><tt class="tag-element">guilabel</tt></span></td>
<td><span class="member"><tt class="tag-element">otheraddr</tt></span></td>
<td><span class="member"><tt class="tag-element">tag</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">confdates</tt></span></td>
<td><span class="member"><tt class="tag-element">guimenu</tt></span></td>
<td><span class="member"><tt class="tag-element">othername</tt></span></td>
<td><span class="member"><tt class="tag-element">token</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">confnum</tt></span></td>
<td><span class="member"><tt class="tag-element">guimenuitem</tt></span></td>
<td><span class="member"><tt class="tag-element">package</tt></span></td>
<td><span class="member"><tt class="tag-element">trademark</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">confsponsor</tt></span></td>
<td><span class="member"><tt class="tag-element">guisubmenu</tt></span></td>
<td><span class="member"><tt class="tag-element">pagenums</tt></span></td>
<td><span class="member"><tt class="tag-element">type</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">conftitle</tt></span></td>
<td><span class="member"><tt class="tag-element">hardware</tt></span></td>
<td><span class="member"><tt class="tag-element">paramdef</tt></span></td>
<td><span class="member"><tt class="tag-element">uri</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">constant</tt></span></td>
<td><span class="member"><tt class="tag-element">holder</tt></span></td>
<td><span class="member"><tt class="tag-element">parameter</tt></span></td>
<td><span class="member"><tt class="tag-element">varname</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">contractnum</tt></span></td>
<td><span class="member"><tt class="tag-element">honorific</tt></span></td>
<td><span class="member"><tt class="tag-element">personname</tt></span></td>
<td><span class="member"><tt class="tag-element">volumenum</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">contractsponsor</tt></span></td>
<td><span class="member"><tt class="tag-element">interfacename</tt></span></td>
<td><span class="member"><tt class="tag-element">phone</tt></span></td>
<td><span class="member"><tt class="tag-element">wordasword</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">contrib</tt></span></td>
<td><span class="member"><tt class="tag-element">issuenum</tt></span></td>
<td><span class="member"><tt class="tag-element">phrase</tt></span></td>
<td><span class="member"><tt class="tag-element">year</tt></span></td>
</tr>
<tr>
<td><span class="member"><tt class="tag-element">country</tt></span></td>
<td><span class="member"><tt class="tag-element">jobtitle</tt></span></td>
<td><span class="member"><tt class="tag-element">pob</tt></span></td>
<td> </td>
</tr>
</table>
<p>In addition to <tt class="tag-element">inlinemediaobject</tt>, <tt class="tag-element">remark</tt>,
<tt class="tag-element">subscript</tt>, <tt class="tag-element">superscript</tt>, the linking inlines,
and <tt class="tag-element">alt</tt>, these elements would now also allow
<tt class="tag-element">abbrev</tt>, <tt class="tag-element">acronym</tt>, <tt class="tag-element">trademark</tt>,
<tt class="tag-element">date</tt>, <tt class="tag-element">emphasis</tt>, <tt class="tag-element">footnote</tt> and
<tt class="tag-element">footnoteref</tt>, <tt class="tag-element">foreignphrase</tt>, <tt class="tag-element">phrase</tt>,
<tt class="tag-element">quote</tt>, <tt class="tag-element">wordasword</tt>, <tt class="tag-element">firstterm</tt>,
<tt class="tag-element">glossterm</tt>, and <tt class="tag-element">coref</tt>.
</p>
<p>In the particular case of <tt class="tag-element">emphasis</tt>,
<tt class="tag-element">foreignphrase</tt>, <tt class="tag-element">phrase</tt>, <tt class="tag-element">quote</tt>,
<tt class="tag-element">firstterm</tt>, and <tt class="tag-element">glossterm</tt> only
a limited form of each element would be allowed. A <tt class="tag-element">quote</tt>, for example,
in this context would also have a content model limited to the new
definition of “ubiquitious inlines”.
</p>
<p>The new schema will allow things like:
<span class="application">An <em>application</em></span>
and <tt class="filename">filename.<span class="abbrev">xml</span></tt>.
</p>
</div>
</body>
</html><br /><br> Be seeing you,
<br> norm
<br><br>--
<br>Norman Walsh <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26480476&i=1" target="_top" rel="nofollow">ndw@...</a>> | A compromise is the art of
<br><a href="http://www.oasis-open.org/docbook/" target="_top" rel="nofollow">http://www.oasis-open.org/docbook/</a> | dividing a cake in such a way that
<br>Chair, DocBook Technical Committee | everyone believes he has the
<br> | biggest piece.--Ludwig Erhard
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>moreubiq.rnc</strong> (1K) <a href="http://old.nabble.com/attachment/26480476/0/moreubiq.rnc" target="_top">Download Attachment</a><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>moreubiq-test.xml</strong> (7K) <a href="http://old.nabble.com/attachment/26480476/1/moreubiq-test.xml" target="_top">Download Attachment</a><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>attachment2</strong> (191 bytes) <a href="http://old.nabble.com/attachment/26480476/2/attachment2" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26467301Re: Can I make XSL template for i18n2009-11-22T09:24:42Z2009-11-22T09:24:42ZJirka KosekAkihiro Moriguchi wrote:
<br><br><br>> I think it means I need a template for the "its" namespace, but I'm
<br>> quite not for sure because of my lack of DocBook XML and XSL knowledge.
<br>>
<br>> I'm now reading "DocBook XSL: The Complete Guide".
<br>> Is it possible to write the template for the feature or need further
<br>> reference?
<br><br>Yes, you must add custom templates for handling your Ruby markup into
<br>your customization layer, something like:
<br><br><xsl:template match="its:ruby" xmlns:its="<a href="http://www.w3.org/2005/11/its" target="_top" rel="nofollow">http://www.w3.org/2005/11/its</a>">
<br> ... code for handling ruby markup ...
<br></xsl:template>
<br><br>Probably you will have to map Ruby markup to layout tables as support
<br>for Ruby in web browsers and FO engines is very poor.
<br><br> Jirka
<br><br>--
<br>------------------------------------------------------------------
<br> Jirka Kosek e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26467301&i=0" target="_top" rel="nofollow">jirka@...</a> <a href="http://xmlguru.cz" target="_top" rel="nofollow">http://xmlguru.cz</a><br>------------------------------------------------------------------
<br> Professional XML consulting and training services
<br> DocBook customization, custom XSLT/XSL-FO document processing
<br>------------------------------------------------------------------
<br> OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
<br>------------------------------------------------------------------
<br><br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (267 bytes) <a href="http://old.nabble.com/attachment/26467301/0/signature.asc" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26466867minimal set of packages for docbook5 processing on fedora 12?2009-11-22T08:41:04Z2009-11-22T08:41:04ZRobert P. J. Day-2<br> i posted this on the fedora list earlier today, but i figure this is
<br>just as appropriate a venue.
<br><br> what's the starter set of packages that one needs to start
<br>processing docbook5 on fedora 12, if one wants to work strictly with
<br>XML (not SGML), and leave DSSSL out of it, and so on? in short, how
<br>little must i install depending on what output i want to generate?
<br><br> minimally, i realize i'm going to need (and what follows is out of
<br>pure ignorance since i have yet to attempt db5 processing on fedora):
<br><br> * libxml2 (for xmllint and xmlcatalog)
<br> * libxslt (for xsltproc)
<br> * docbook5-schemas
<br> * docbook5-style-xsl
<br> * fop (for PDF output)
<br><br>you get the idea. i want to put together a single-page wiki entry
<br>that shows fedora 12 people how to get started with writing and
<br>processing db5, but i don't want to drag along all the historical
<br>baggage.
<br><br> thoughts? i'm just about to peruse bob stayton's docbook XSL book,
<br>and i can already see the caution that xmllint can't fully handle
<br>docbook5.
<br><br>rday
<br>--
<br><br>========================================================================
<br>Robert P. J. Day Waterloo, Ontario, CANADA
<br><br> Linux Consulting, Training and Kernel Pedantry.
<br><br>Web page: <a href="http://crashcourse.ca" target="_top" rel="nofollow">http://crashcourse.ca</a><br>Twitter: <a href="http://twitter.com/rpjday" target="_top" rel="nofollow">http://twitter.com/rpjday</a><br>========================================================================
<br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466867&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466867&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26450237Can I make XSL template for i18n2009-11-20T13:02:57Z2009-11-20T13:02:57ZAkihiro Moriguchi-2Hi all,
<br><br>Please let me know if it is possible to make template for XSL,
<br>because I'm quite new to DocBook XML and XSL.
<br><br>I'm Japanese and interested in DocBook i17n customization.
<br>As I can read Mr. Kosek's post from archive following,
<br><a href="http://markmail.org/search/?q=ruby&q=list%3Aorg.oasis-open.lists.docbook#query:ruby%20list%3Aorg.oasis-open.lists.docbook+page:2+mid:spm6csstu5x6axzk+state:results" target="_top" rel="nofollow">http://markmail.org/search/?q=ruby&q=list%3Aorg.oasis-open.lists.docbook#query:ruby%20list%3Aorg.oasis-open.lists.docbook+page:2+mid:spm6csstu5x6axzk+state:results</a><br>I got to know I can implement ruby annotation feature,
<br><a href="http://www.w3.org/TR/xml-i18n-bp/#DevRuby" target="_top" rel="nofollow">http://www.w3.org/TR/xml-i18n-bp/#DevRuby</a>, with adding
<br><a href="http://www.w3.org/TR/its/" target="_top" rel="nofollow">http://www.w3.org/TR/its/</a> schema.
<br><br>But the result of processing with xsltproc, I got following output.
<br><br>----------------
<br>Element ruby in namespace '<a href="http://www.w3.org/2005/11/its'" target="_top" rel="nofollow">http://www.w3.org/2005/11/its'</a> encountered in
<br>para, but no template matches.
<br>Element rb in namespace '<a href="http://www.w3.org/2005/11/its'" target="_top" rel="nofollow">http://www.w3.org/2005/11/its'</a> encountered in
<br>its:ruby, but no template matches.
<br> .
<br> .
<br>----------------
<br><br>I think it means I need a template for the "its" namespace, but I'm
<br>quite not for sure because of my lack of DocBook XML and XSL knowledge.
<br><br>I'm now reading "DocBook XSL: The Complete Guide".
<br>Is it possible to write the template for the feature or need further
<br>reference?
<br><br>Best regards,
<br>Akihiro Moriguchi
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26450237&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26450237&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26439875Re: Footnotes in Lists don't work2009-11-20T00:25:23Z2009-11-20T00:25:23ZJohannes Katelaan-2Cool!
<br>The current trunk version works perfectly!
<br><br>Thanks a lot!
<br><br>Johannes
<br><br>Am 19.11.2009 um 17:17 schrieb Vincent Hennebert:
<br><div class='shrinkable-quote'><br>> Hi,
<br>>
<br>> If that's an acceptable option for you, you can use the Trunk version of
<br>> FOP in which that bug has been fixed. You can download a snapshot of the
<br>> source code here:
<br>> <a href="http://svn-master.apache.org/snapshots/fop/" target="_top" rel="nofollow">http://svn-master.apache.org/snapshots/fop/</a><br>> And see here for help about building FOP:
<br>> <a href="http://xmlgraphics.apache.org/fop/trunk/compiling.html" target="_top" rel="nofollow">http://xmlgraphics.apache.org/fop/trunk/compiling.html</a><br>>
<br>> HTH,
<br>> Vincent
<br>>
<br>>
<br>> Johannes Katelaan wrote:
<br>>> So it's a bug in FOP. Too bad!
<br>>> I will have a closer look at the workarounds described in the blog entry and see if it helps in the docbook context.
<br>>>
<br>>> Thanks!
<br>>>
<br>>> Johannes
<br>>>
<br>>> Am 17.11.2009 um 12:23 schrieb Damon Mannion:
<br>>>
<br>>>> I *think* this is a known limitation to footnotes and FOP?
<br>>>>
<br>>>> I *think* this is explained here:
<br>>>> <a href="http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/" target="_top" rel="nofollow">http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/</a><br>>>>
<br>>>> but am in China at the moment, and access to wordpress seems to be
<br>>>> blocked...
<br>>>>
<br>>>> Damon
<br>>>>
<br>>>> On Tue, 17 Nov 2009 12:01 +0100, "Johannes Katelaan"
<br>>>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=0" target="_top" rel="nofollow">jk@...</a>> wrote:
<br>>>>> Hi,
<br>>>>>
<br>>>>> if I put a footnote into a list (I tried itemizedlist and variablelist),
<br>>>>> then the footnote number will be calculated correctly and will appear in
<br>>>>> the text, but the footnote body does not appear at the bottom of the
<br>>>>> page. Is this a bug or a feature? Is there a workaround for this?
<br>>>>>
<br>>>>> Johannes
<br>>>>>
<br>>>>>
<br>>>>> ---------------------------------------------------------------------
<br>>>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=1" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>>>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=2" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>>>
<br>>>> ---------------------------------------------------------------------
<br>>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=3" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=4" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>>
<br>>>
<br>>>
<br>>> ---------------------------------------------------------------------
<br>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=5" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=6" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=7" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=8" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>
</div><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=9" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26439875&i=10" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26435106RE: Customizing Generated Text with No Context2009-11-19T14:17:00Z2009-11-19T14:17:00ZMauritz Jeanson| -----Original Message-----
<br>| From: John Green
<br>|
<br>| However, the text I want to customize doesn't seem to have a
<br>| context. I want to customize the "Table of Contents" string
<br>| to "Contents". I found the gentext entry for
<br>| "TableofContents" in en.xml, and it seems to be outside of
<br>| any <l:context> element.
<br>|
<br>| How do I make the code work without specifying a context? I
<br>| tried removing the l:context lines, and I tried setting the
<br>| l:template name attribute to "", "/", and ".", but nothing
<br>| works. How do I do this?
<br><br><br>Just use <l:gentext>:
<br><br> <l:i18n xmlns:l="<a href="http://docbook.sourceforge.net/xmlns/l10n/1.0" target="_top" rel="nofollow">http://docbook.sourceforge.net/xmlns/l10n/1.0</a>">
<br> <l:l10n language="en">
<br> <l:gentext key="TableofContents" text="Contents"/>
<br> </l:l10n>
<br> </l:i18n>
<br><br>Mauritz
<br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26435106&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26435106&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26433705Customizing Generated Text with No Context2009-11-19T12:34:19Z2009-11-19T12:34:19ZJohn Green-3Hello,
<br><br>I want to customize text that is generated by the docbook xslt (all output formats). I found the sections on customizing generated text in the documentation. It includes the following code sample that creates a local.l10n.xml parameter and specifies a language and context as well as the text to be customized.
<br><br><xsl:param name="local.l10n.xml" select="document('')"/>
<br><l:i18n xmlns:l="<a href="http://docbook.sourceforge.net/xmlns/l10n/1.0" target="_top" rel="nofollow">http://docbook.sourceforge.net/xmlns/l10n/1.0</a>">
<br> <l:l10n language="en">
<br> <l:context name="xref-number-and-title">
<br> <l:template name="chapter" text="Chapter %n: “%t”"/>
<br> </l:context>
<br> </l:l10n>
<br></l:i18n>
<br><br>However, the text I want to customize doesn't seem to have a context. I want to customize the "Table of Contents" string to "Contents". I found the gentext entry for "TableofContents" in en.xml, and it seems to be outside of any <l:context> element.
<br><br>How do I make the code work without specifying a context? I tried removing the l:context lines, and I tried setting the l:template name attribute to "", "/", and ".", but nothing works. How do I do this?
<br><br>Thanks
<br>John
<br><br>--
<br>John Green
<br><br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26433705&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26433705&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26433175RE: Tag formatting in PDF output2009-11-19T12:04:35Z2009-11-19T12:04:35ZDavid Cramer (Tech Pubs)<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18852"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN class=626305819-19112009>Hi Andrew,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN class=626305819-19112009>To do that you'll need to create a "customization
layer" with templates to control the formatting for the elements you want to
change. </SPAN></FONT><FONT color=#0000ff size=2 face=Arial><SPAN class=626305819-19112009>You'll find that Bob Stayton's book is a
great resource for this kind of thing. </SPAN></FONT><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=626305819-19112009>Look </SPAN><SPAN class=626305819-19112009>here: </SPAN></FONT></FONT></FONT><A href="http://www.sagehill.net/docbookxsl/CustomInlines.html" target="_top" rel="nofollow"><FONT size=2 face=Arial>http://www.sagehill.net/docbookxsl/CustomInlines.html</FONT></A><FONT face=Arial><FONT color=#0000ff><FONT size=2> <SPAN class=626305819-19112009>and for information about creating the
customization layer: <A href="http://www.sagehill.net/docbookxsl/CustomMethods.html" target="_top" rel="nofollow"><FONT face=Arial><FONT size=2>http://www.sagehill.net/docbookxsl/CustomMethods.html</FONT></FONT></A><SPAN class=626305819-19112009><FONT color=#0000ff size=2 face=Arial>
</FONT></SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN class=626305819-19112009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><SPAN class=626305819-19112009><FONT color=#0000ff size=2 face=Arial>David</FONT></SPAN></DIV><BR>
<BLOCKQUOTE style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=ltr>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Andrew Light
[mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26433175&i=0" target="_top" rel="nofollow">light.andrew@...</a>] <BR><B>Sent:</B> Thursday, November 19, 2009
1:43 PM<BR><B>To:</B> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26433175&i=1" target="_top" rel="nofollow">docbook-apps@...</a><BR><B>Subject:</B>
[docbook-apps] Tag formatting in PDF output<BR></FONT><BR></DIV>
<DIV></DIV>Hi all,
<DIV><BR></DIV>
<DIV>I have DocBook files that I am converting to PDF (using FOP). I would
like my xml tags (like guilabel, guibutton, etc) to be formatted in a special
way in the PDF (comparable to the way they are when I convert to HTML
using CSS).</DIV>
<DIV><BR></DIV>
<DIV>How can I control the formatting of my XML tags through to the PDF
output?</DIV>
<DIV><BR></DIV>
<DIV>Thanks in advance!</DIV>
<DIV><BR></DIV>
<DIV>Andrew</DIV></BLOCKQUOTE></BODY></HTML>
<p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26432827Tag formatting in PDF output2009-11-19T11:43:29Z2009-11-19T11:43:29ZAndrew LightHi all,<div><br></div><div>I have DocBook files that I am converting to PDF (using FOP). I would like my xml tags (like guilabel, guibutton, etc) to be formatted in a special way in the PDF (comparable to the way they are when I convert to HTML using CSS).</div>
<div><br></div><div>How can I control the formatting of my XML tags through to the PDF output?</div><div><br></div><div>Thanks in advance!</div><div><br></div><div>Andrew</div>
<p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26431030DocBook Technical Committee Meeting Minutes: 18 November 20092009-11-19T09:59:42Z2009-11-19T09:59:42ZBob StaytonDocBook Technical Committee Meeting Minutes: 18 November 2009
<br>=============================================================
<br><br>The DocBook Technical Committee met on Wednesday, 18 November 2009 at
<br>01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
<br>022:30p India+) for 60 minutes.
<br><br>1. Roll call
<br><br>Present: Patricia Gee, Paul Grosso, Dick Hamilton,
<br>Scott Hudson, Gershon Joseph, Jirka Kosek, Larry Rowland,
<br>Bob Stayton, Norm Walsh. We have a quorum.
<br><br>Absent: Chris Chung, Jim Earley, Keith Falhgren, Nancy Harrison,
<br>Corey Leong, Dave Pawson, John Pederson, Pine Zhang
<br><br>2. Accepted the minutes [1] of the previous meeting.
<br><br>3. Next meeting: 16 December 2009
<br><br>4. Review of the agenda.
<br><br>Add item 11a regarding DocBook website maintenance.
<br><br>5. Review of open action items
<br><br> a. Norm to put the new backwards compatibility policy in the spec.
<br> COMPLETED.
<br><br> b. Norm to put the new backwards compatibility policy in the
<br> reference documentation.
<br> COMPLETED.
<br><br> c. Norm to take a look at the inlines and make a proposal
<br> regarding RFE 2791288.
<br> COMPLETED.
<br><br> d. Norm to reply to RFE 2820947 (transclusion) with the
<br> committee's concerns (see the minutes).
<br> COMPLETED.
<br><br> e. Gershon to develop a reltable example.
<br> CONTINUED.
<br><br><br>6. DocBook 5.0 standards celebration.
<br><br>DocBook 5.0 was approved as an OASIS Standard. Congratulations
<br>to all involved. [Pop goes the virtual champagne cork]
<br><br>7. New edition of DocBook: The Definitive Guide
<br><br>Dick reports that they are close to doing a technical review,
<br>and he will solicit technical reviewers.
<br><br>8. Publishing Subcommittee report.
<br><br>Scott reports that they are still having problems deriving a
<br>DTD from the RelaxNG for the publishing schema.
<br>This technical glitch is holding up the process, and he
<br>may have to resort to creating it by hand.
<br><br>9. eLearning Subcommittee report.
<br><br>Scott is organizing an initial meeting for 8 December at
<br>10am EST. They will meet the 2nd Tuesday of each month.
<br><br>10. DocBook assembly schema.
<br><br>No further changes have been suggested. Members said they
<br>would try out the prototype stylesheets that Bob provided
<br>that convert between a DocBook document and an assembly
<br>with topics.
<br><br>ACTION: Larry will publish an updated schema with last month's
<br>changes.
<br><br>Norm suggested that we make available both full and simplified
<br>versions. He is concerned that the details of the full
<br>version will overwhelm those getting started who need
<br>just basic assembly. It may be separate schemas, or
<br>just documentation and examples.
<br><br>ACTION: Norm to prepare a proposal for full and simplified
<br>assembly versions.
<br><br>Bob proposed adding a relatedlink element to DocBook 5. [2]
<br>This could complement related links managed at the
<br>assembly level. Members were generally favorable, but
<br>no action was taken yet.
<br><br>Bob suggested organizing a separate discussion of
<br>linking in modular DocBook, and several members
<br>expressed interest.
<br><br>ACTION: Bob to organize a meeting to discuss linking
<br>in modular DocBook.
<br><br>11. topic element (RFE #2820190).
<br><br>No further discussion at this time.
<br><br>11a. DocBook websites.
<br>We have received feedback on the docbook mailing lists
<br>that the number and organization of DocBook websites is
<br>a bit confusing.
<br><br>ACTION: Norm to develop a proposal for maintaining
<br>the DocBook websites.
<br><br>12. Review of Requests for Enhancement
<br><br> To browse a specific RFE, enter the URL (on one line):
<br><br> <a href="http://sourceforge.net/tracker/index.php?func=detail&;" target="_top" rel="nofollow">http://sourceforge.net/tracker/index.php?func=detail&;</a><br> group_id=21935&atid=384107&aid=XXXX
<br><br> RFEs to revisit for 6.0
<br> 1907003 biblioid content model too broad
<br><br> RFEs to be considered
<br> 1679665 Add better support for modular documentation
<br><br>This is covered under agenda item 10.
<br><br> 2770858 Add limited emphasis to ubiquitous inlines
<br> 2791288 add quote to corpauthor and gui elements
<br><br>Norm looked at these two items together. He agrees that since
<br>quote characters are permitted everywhere, the quote element
<br>should also since it can generate quote characters suitable
<br>to each locale. Norm suggested allowing the elements defined
<br>in this DocBook RelaxNG pattern to appear almost everywhere:
<br><br>db.publishing.inlines =
<br> (db.abbrev
<br> | db.acronym
<br> | db.date
<br> | db.emphasis
<br> | db.footnote
<br> | db.footnoteref
<br> | db.foreignphrase
<br> | db.phrase
<br> | db.quote
<br> | db.subscript
<br> | db.superscript
<br> | db.wordasword)
<br> | db.glossary.inlines
<br> | db.coref
<br><br>He suggests using other alternate patterns as needed to prevent
<br>nested use of inappropriate elements. There were no
<br>objections.
<br><br>ACTION: Norm to develop schema changes for discussion at
<br>the next meeting.
<br><br> 2820190 add a topic element
<br><br>Pending.
<br><br> 2820947 Ability to transclude text
<br><br>At the August 2009 meeting [3], the committee suggested that
<br>this feature be developed as an XML standard rather than a DocBook
<br>feature. Members now don't feel this is likely to solve the
<br>problems users have expressed. Members have suggested that
<br>XInclude is not sufficient, conref is too complicated, but the
<br>needs persist.
<br><br>ACTION: Norm to develop a list of use cases and requirements
<br>for transclusion.
<br><br>ACTION: Bob to add agenda item for this RFE to next meeting.
<br><br> 2821653 indexterms in footnotes
<br><br>Bob had reported that indexterms in footnotes work in XSLT.
<br>We thought we approved allowing indexterms in footnotes at
<br>the last meeting, but it was not recorded in the minutes,
<br>so it is considered not approved yet. We will reconsider
<br>at the next meeting. Paul suggested that this needs
<br>better documentation.
<br><br>ACTION: Norm to better document indexterm placement.
<br><br>-----
<br><br>[1] <a href="http://lists.oasis-open.org/archives/docbook-tc/200910/msg00022.html" target="_top" rel="nofollow">http://lists.oasis-open.org/archives/docbook-tc/200910/msg00022.html</a><br>[2] <a href="http://lists.oasis-open.org/archives/docbook-tc/200911/msg00003.html" target="_top" rel="nofollow">http://lists.oasis-open.org/archives/docbook-tc/200911/msg00003.html</a><br>[3] <a href="http://lists.oasis-open.org/archives/docbook-tc/200908/msg00004.html" target="_top" rel="nofollow">http://lists.oasis-open.org/archives/docbook-tc/200908/msg00004.html</a><br><br>Bob Stayton
<br>Sagehill Enterprises
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26431030&i=0" target="_top" rel="nofollow">bobs@...</a>
<br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26431030&i=1" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26431030&i=2" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26429195Re: Footnotes in Lists don't work2009-11-19T08:17:04Z2009-11-19T08:17:04ZVincent Hennebert-2Hi,
<br><br>If that's an acceptable option for you, you can use the Trunk version of
<br>FOP in which that bug has been fixed. You can download a snapshot of the
<br>source code here:
<br><a href="http://svn-master.apache.org/snapshots/fop/" target="_top" rel="nofollow">http://svn-master.apache.org/snapshots/fop/</a><br>And see here for help about building FOP:
<br><a href="http://xmlgraphics.apache.org/fop/trunk/compiling.html" target="_top" rel="nofollow">http://xmlgraphics.apache.org/fop/trunk/compiling.html</a><br><br>HTH,
<br>Vincent
<br><br><br>Johannes Katelaan wrote:
<div class='shrinkable-quote'><br>> So it's a bug in FOP. Too bad!
<br>> I will have a closer look at the workarounds described in the blog entry and see if it helps in the docbook context.
<br>>
<br>> Thanks!
<br>>
<br>> Johannes
<br>>
<br>> Am 17.11.2009 um 12:23 schrieb Damon Mannion:
<br>>
<br>>> I *think* this is a known limitation to footnotes and FOP?
<br>>>
<br>>> I *think* this is explained here:
<br>>> <a href="http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/" target="_top" rel="nofollow">http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/</a><br>>>
<br>>> but am in China at the moment, and access to wordpress seems to be
<br>>> blocked...
<br>>>
<br>>> Damon
<br>>>
<br>>> On Tue, 17 Nov 2009 12:01 +0100, "Johannes Katelaan"
<br>>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=0" target="_top" rel="nofollow">jk@...</a>> wrote:
<br>>>> Hi,
<br>>>>
<br>>>> if I put a footnote into a list (I tried itemizedlist and variablelist),
<br>>>> then the footnote number will be calculated correctly and will appear in
<br>>>> the text, but the footnote body does not appear at the bottom of the
<br>>>> page. Is this a bug or a feature? Is there a workaround for this?
<br>>>>
<br>>>> Johannes
<br>>>>
<br>>>>
<br>>>> ---------------------------------------------------------------------
<br>>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=1" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=2" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>>
<br>>> ---------------------------------------------------------------------
<br>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=3" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=4" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>
<br>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=5" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=6" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>
</div><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=7" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429195&i=8" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26429161indexterms in footnotes [was: DocBook Technical Committee Meeting Agenda: 18 November 2009]2009-11-19T08:12:47Z2009-11-19T08:12:47ZGrosso, PaulAs I said, I'm okay with allowing indexterm as a child of footnote
<br>if we feel it is worthwhile making that change (that has not been
<br>the case throughout DB 4.x, so I question the need).
<br><br>But you're inventing some kind of semantic that doesn't exist.
<br><br>Unless you have indexterm-start and indexterm-end elements that
<br>apply the index semantic to all the intervening content or some
<br>other way to indicate to what content an indexterm applies, indexterms
<br>don't apply to anything. They are point-wise things. The point
<br>on the composed page corresponding to where the indexterm element
<br>occurred is the point that determines the page number in the index,
<br>and the contents of the indexterm gives the index entry content.
<br><br>To take an example having nothing to do with footnotes, suppose
<br>you have a indexterm immediately following a para start tag. If
<br>you claim that such an indexterm applies to the para, then what
<br>happens when that para flows over a page break? Do you expect
<br>both pages to be reflected in the index? If the indexterm applied
<br>to the para, you should get both page numbers in the index, but
<br>I claim you should only get the first page number because the
<br>indexterm applies just to the point at which it occurred.
<br><br>Going back to the footnote, if you claim the indexterm applies
<br>to the footnote, would you expect the footnote callout (e.g.,
<br>the superscripted number) to be a target of the index entry
<br>as well as the footnote body?
<br><br>paul
<br><br>> -----Original Message-----
<br>> From: Rowland, Larry [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=0" target="_top" rel="nofollow">larry.rowland@...</a>]
<br>> Sent: Thursday, 2009 November 19 9:49
<br>> To: Grosso, Paul; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=1" target="_top" rel="nofollow">docbook-tc@...</a>;
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=2" target="_top" rel="nofollow">docbook@...</a>-
<br>> open.org
<br>> Subject: RE: [docbook] RE: [docbook-tc] DocBook Technical Committee
<br>> Meeting Agenda: 18 November 2009
<br>>
<br>> To me, an index term is at least as likely to apply to an entire
<br>> footnote as it is to an element contained within the footnote. I
<br>would
<div class='shrinkable-quote'><br>> favor allowing it as a child of footnote.
<br>>
<br>> Larry Rowland
<br>>
<br>> -----Original Message-----
<br>> From: Grosso, Paul [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=3" target="_top" rel="nofollow">pgrosso@...</a>]
<br>> Sent: Thursday, November 19, 2009 8:34 AM
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=4" target="_top" rel="nofollow">docbook-tc@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=5" target="_top" rel="nofollow">docbook@...</a>
<br>> Subject: RE: [docbook] RE: [docbook-tc] DocBook Technical Committee
<br>> Meeting Agenda: 18 November 2009
<br>>
<br>> [I'm not sure Mike's email made it to the lists, so I'm forwarding
<br>> it along with a response of mine.]
<br>>
<br>> > -----Original Message-----
<br>> > From: maxwell [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=6" target="_top" rel="nofollow">maxwell@...</a>]
<br>> > Sent: Wednesday, 2009 November 18 21:32
<br>> > To: Grosso, Paul
<br>> > Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=7" target="_top" rel="nofollow">docbook-tc@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=8" target="_top" rel="nofollow">docbook@...</a>
<br>> > Subject: Re: [docbook] RE: [docbook-tc] DocBook Technical Committee
<br>> > Meeting Agenda: 18 November 2009
<br>> >
<br>> > On Wed, 18 Nov 2009 15:09:39 -0500, "Grosso, Paul" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=9" target="_top" rel="nofollow">pgrosso@...</a>>
<br>> > wrote:
<br>> > > ...
<br>> > >> 2821653 indexterms in footnotes
<br>> > > ...
<br>> > > First, I note that indexterm is already allowed within paras
<br>> > > within footnotes (at least in DocBook 4.x) which is where I'd
<br>> > > usually expect an indexterm to be. The discussion during the
<br>> > > TC call seemed not to realize this, so I wonder if I'm confused
<br>> > > or the discussion was confused. (Perhaps this is different in
<br>> > > DocBook 5.0--I didn't check.)
<br>> > > ...
<br>> > > Given that footnotes are allowed as descendants of footnote
<br>> > > but just not as immediate children, and given that I don't
<br>> > > see also allowing indexterm as an immediate child of footnote
<br>> > > as useful, I suggest there is no reason to accept this RFE.
<br>> >
<br>> > From the DB 5 documentation for <footnote>
<br>> > (<a href="http://www.docbook.org/tdg5/en/html/footnote.html):" target="_top" rel="nofollow">http://www.docbook.org/tdg5/en/html/footnote.html):</a><br>> > indexterm must not occur in the descendants of footnote
<br>> > So this is exactly the opposite of what you're describing above
<br>> > for DB4: according to the DB5 documentation, <indexterm>s are
<br>> > allowed as immediate children of <footnote>, but *not* as
<br>> > children of descendents of <footnote>. Hence the RFE.
<br>> >
<br>> > Mike Maxwell
<br>>
<br>> Just to be clear, I did not review--and was not talking
<br>> about--any documentation (for DB4 or DB5) nor the DB5
<br>> schemas. I merely checked (and tested within Arbortext)
<br>> the XML DTD-based DocBook 4.x doctype in which
<br>> (1) %footnote.mix; (the content model for footnote)
<br>> does not allow indexterm, but
<br>> (2) does allow para and other elements whose content models
<br>> do allow indexterm.
<br>> In fact, I note that, in the SGML version, there are some
<br>> exclusions on footnote, but indexterm is not excluded.
<br>>
<br>> I leave it to the rest of the DocBook TC to decide exactly
<br>> what to do, but my suggestion would be:
<br>>
<br>> a. ensure the DB5 schema matches the DB4 DTD in this case
<br>> so that indexterm is not excluded from children of
<br>> footnote that would ordinarily allow indexterm if
<br>> they were not within a footnote;
<br>>
<br>> b. ensure the content model for footnote does not allow
<br>> indexterm as an immediate child of footnote (though
<br>> I could go either way, but I see no reason to change
<br>> the status quo here);
<br>>
<br>> c. ensure the documentation reflects the schema and puts
<br>> no further constraints on how indexterm can be used
<br>> within footnote.
<br>>
<br>> As an aside, if the DB5 schema does not exclude footnote
<br>> within footnote (the DB4 XML DTD does not [because it
<br>> could not given what one can do in an XML DTD]), then
<br>> that semantic exclusion should be indicated in the
<br>> documentation. (I did not look at the DB5 schema, so
<br>> this exclusion may already be covered.)
<br>>
<br>> paul
</div><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=10" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429161&i=11" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26428624RE: RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 18 November 20092009-11-19T07:49:10Z2009-11-19T07:49:10ZRowland, LarryTo me, an index term is at least as likely to apply to an entire footnote as it is to an element contained within the footnote. I would favor allowing it as a child of footnote.
<br><br>Larry Rowland
<br><br>-----Original Message-----
<br>From: Grosso, Paul [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=0" target="_top" rel="nofollow">pgrosso@...</a>]
<br>Sent: Thursday, November 19, 2009 8:34 AM
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=1" target="_top" rel="nofollow">docbook-tc@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=2" target="_top" rel="nofollow">docbook@...</a>
<br>Subject: RE: [docbook] RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 18 November 2009
<br><br>[I'm not sure Mike's email made it to the lists, so I'm forwarding
<br>it along with a response of mine.]
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: maxwell [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=3" target="_top" rel="nofollow">maxwell@...</a>]
<br>> Sent: Wednesday, 2009 November 18 21:32
<br>> To: Grosso, Paul
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=4" target="_top" rel="nofollow">docbook-tc@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=5" target="_top" rel="nofollow">docbook@...</a>
<br>> Subject: Re: [docbook] RE: [docbook-tc] DocBook Technical Committee
<br>> Meeting Agenda: 18 November 2009
<br>>
<br>> On Wed, 18 Nov 2009 15:09:39 -0500, "Grosso, Paul" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=6" target="_top" rel="nofollow">pgrosso@...</a>>
<br>> wrote:
<br>> > ...
<br>> >> 2821653 indexterms in footnotes
<br>> > ...
<br>> > First, I note that indexterm is already allowed within paras
<br>> > within footnotes (at least in DocBook 4.x) which is where I'd
<br>> > usually expect an indexterm to be. The discussion during the
<br>> > TC call seemed not to realize this, so I wonder if I'm confused
<br>> > or the discussion was confused. (Perhaps this is different in
<br>> > DocBook 5.0--I didn't check.)
<br>> > ...
<br>> > Given that footnotes are allowed as descendants of footnote
<br>> > but just not as immediate children, and given that I don't
<br>> > see also allowing indexterm as an immediate child of footnote
<br>> > as useful, I suggest there is no reason to accept this RFE.
<br>>
<br>> From the DB 5 documentation for <footnote>
<br>> (<a href="http://www.docbook.org/tdg5/en/html/footnote.html):" target="_top" rel="nofollow">http://www.docbook.org/tdg5/en/html/footnote.html):</a><br>> indexterm must not occur in the descendants of footnote
<br>> So this is exactly the opposite of what you're describing above
<br>> for DB4: according to the DB5 documentation, <indexterm>s are
<br>> allowed as immediate children of <footnote>, but *not* as
<br>> children of descendents of <footnote>. Hence the RFE.
<br>>
<br>> Mike Maxwell
</div><br>Just to be clear, I did not review--and was not talking
<br>about--any documentation (for DB4 or DB5) nor the DB5
<br>schemas. I merely checked (and tested within Arbortext)
<br>the XML DTD-based DocBook 4.x doctype in which
<br>(1) %footnote.mix; (the content model for footnote)
<br> does not allow indexterm, but
<br>(2) does allow para and other elements whose content models
<br> do allow indexterm.
<br>In fact, I note that, in the SGML version, there are some
<br>exclusions on footnote, but indexterm is not excluded.
<br><br>I leave it to the rest of the DocBook TC to decide exactly
<br>what to do, but my suggestion would be:
<br><br>a. ensure the DB5 schema matches the DB4 DTD in this case
<br> so that indexterm is not excluded from children of
<br> footnote that would ordinarily allow indexterm if
<br> they were not within a footnote;
<br><br>b. ensure the content model for footnote does not allow
<br> indexterm as an immediate child of footnote (though
<br> I could go either way, but I see no reason to change
<br> the status quo here);
<br><br>c. ensure the documentation reflects the schema and puts
<br> no further constraints on how indexterm can be used
<br> within footnote.
<br><br>As an aside, if the DB5 schema does not exclude footnote
<br>within footnote (the DB4 XML DTD does not [because it
<br>could not given what one can do in an XML DTD]), then
<br>that semantic exclusion should be indicated in the
<br>documentation. (I did not look at the DB5 schema, so
<br>this exclusion may already be covered.)
<br><br>paul
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=7" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428624&i=8" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26428333RE: RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 18 November 20092009-11-19T07:34:01Z2009-11-19T07:34:01ZGrosso, Paul[I'm not sure Mike's email made it to the lists, so I'm forwarding
<br>it along with a response of mine.]
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: maxwell [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428333&i=0" target="_top" rel="nofollow">maxwell@...</a>]
<br>> Sent: Wednesday, 2009 November 18 21:32
<br>> To: Grosso, Paul
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428333&i=1" target="_top" rel="nofollow">docbook-tc@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428333&i=2" target="_top" rel="nofollow">docbook@...</a>
<br>> Subject: Re: [docbook] RE: [docbook-tc] DocBook Technical Committee
<br>> Meeting Agenda: 18 November 2009
<br>>
<br>> On Wed, 18 Nov 2009 15:09:39 -0500, "Grosso, Paul" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26428333&i=3" target="_top" rel="nofollow">pgrosso@...</a>>
<br>> wrote:
<br>> > ...
<br>> >> 2821653 indexterms in footnotes
<br>> > ...
<br>> > First, I note that indexterm is already allowed within paras
<br>> > within footnotes (at least in DocBook 4.x) which is where I'd
<br>> > usually expect an indexterm to be. The discussion during the
<br>> > TC call seemed not to realize this, so I wonder if I'm confused
<br>> > or the discussion was confused. (Perhaps this is different in
<br>> > DocBook 5.0--I didn't check.)
<br>> > ...
<br>> > Given that footnotes are allowed as descendants of footnote
<br>> > but just not as immediate children, and given that I don't
<br>> > see also allowing indexterm as an immediate child of footnote
<br>> > as useful, I suggest there is no reason to accept this RFE.
<br>>
<br>> From the DB 5 documentation for <footnote>
<br>> (<a href="http://www.docbook.org/tdg5/en/html/footnote.html):" target="_top" rel="nofollow">http://www.docbook.org/tdg5/en/html/footnote.html):</a><br>> indexterm must not occur in the descendants of footnote
<br>> So this is exactly the opposite of what you're describing above
<br>> for DB4: according to the DB5 documentation, <indexterm>s are
<br>> allowed as immediate children of <footnote>, but *not* as
<br>> children of descendents of <footnote>. Hence the RFE.
<br>>
<br>> Mike Maxwell
</div><br>Just to be clear, I did not review--and was not talking
<br>about--any documentation (for DB4 or DB5) nor the DB5
<br>schemas. I merely checked (and tested within Arbortext)
<br>the XML DTD-based DocBook 4.x doctype in which
<br>(1) %footnote.mix; (the content model for footnote)
<br> does not allow indexterm, but
<br>(2) does allow para and other elements whose content models
<br> do allow indexterm.
<br>In fact, I note that, in the SGML version, there are some
<br>exclusions on footnote, but indexterm is not excluded.
<br><br>I leave it to the rest of the DocBook TC to decide exactly
<br>what to do, but my suggestion would be:
<br><br>a. ensure the DB5 schema matches the DB4 DTD in this case
<br> so that indexterm is not excluded from children of
<br> footnote that would ordinarily allow indexterm if
<br> they were not within a footnote;
<br><br>b. ensure the content model for footnote does not allow
<br> indexterm as an immediate child of footnote (though
<br> I could go either way, but I see no reason to change
<br> the status quo here);
<br><br>c. ensure the documentation reflects the schema and puts
<br> no further constraints on how indexterm can be used
<br> within footnote.
<br><br>As an aside, if the DB5 schema does not exclude footnote
<br>within footnote (the DB4 XML DTD does not [because it
<br>could not given what one can do in an XML DTD]), then
<br>that semantic exclusion should be indicated in the
<br>documentation. (I did not look at the DB5 schema, so
<br>this exclusion may already be covered.)
<br><br>paul
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26419880Re: RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 18 November 20092009-11-18T19:32:21Z2009-11-18T19:32:21ZMike Maxwell-2On Wed, 18 Nov 2009 15:09:39 -0500, "Grosso, Paul" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26419880&i=0" target="_top" rel="nofollow">pgrosso@...</a>>
<br>wrote:
<div class='shrinkable-quote'><br>> ...
<br>>> 2821653 indexterms in footnotes
<br>> ...
<br>> First, I note that indexterm is already allowed within paras
<br>> within footnotes (at least in DocBook 4.x) which is where I'd
<br>> usually expect an indexterm to be. The discussion during the
<br>> TC call seemed not to realize this, so I wonder if I'm confused
<br>> or the discussion was confused. (Perhaps this is different in
<br>> DocBook 5.0--I didn't check.)
<br>> ...
<br>> Given that footnotes are allowed as descendants of footnote
<br>> but just not as immediate children, and given that I don't
<br>> see also allowing indexterm as an immediate child of footnote
<br>> as useful, I suggest there is no reason to accept this RFE.
</div><br>From the DB 5 documentation for <footnote>
<br>(<a href="http://www.docbook.org/tdg5/en/html/footnote.html):" target="_top" rel="nofollow">http://www.docbook.org/tdg5/en/html/footnote.html):</a><br> indexterm must not occur in the descendants of footnote
<br>So this is exactly the opposite of what you're describing above for DB4:
<br>according to the DB5 documentation, <indexterm>s are allowed as immediate
<br>children of <footnote>, but *not* as children of descendents of <footnote>.
<br>Hence the RFE.
<br><br> Mike Maxwell
<br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26419880&i=1" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26419880&i=2" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26415788DocBook Publishers Schema2009-11-18T13:08:24Z2009-11-18T13:08:24ZNic Gibson-2Hi folks
<br><br>I've just come back to DocBook after about a year away and I'm doing some work that's going to involve using the Publishers Schema. I've come across an inconsistency that I'm unsure about.
<br><br>The spec for the schema lists <toc> as an included element. However, publishers.rnc does not include toc.rnc either directly or indirectly as far as I can tell. Have I missed something or not?
<br><br>cheers
<br><br>nic
<br>--
<br>Nic Gibson
<br>Director, Corbas Consulting Ltd
<br>Editorial and Technical Consultancy and Training
<br><a href="http://www.corbas.co.uk" target="_top" rel="nofollow">http://www.corbas.co.uk</a>, +44 (0)7718 906817
<br><br><br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26415788&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26415788&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26415279make bold all the xref labels? (Customizing xref style)2009-11-18T12:34:50Z2009-11-18T12:34:50ZRobert NagleI'm trying to figure out how to make bold all the xref labels in my printed PDF.
<br><br>IN Chapter 15 of the XSL book p264 4th edition, there is a section on
<br>Customizing Cross Reference Typography.
<br><a href="http://www.sagehill.net/docbookxsl/CustomXrefs.html#CustomXrefStyle" target="_top" rel="nofollow">http://www.sagehill.net/docbookxsl/CustomXrefs.html#CustomXrefStyle</a><br><br> But I'm not sure what it means or how to actually implement it.
<br><br><br>Two methods are suggested. The first is using the insert.title.markup
<br>mode (whatever that is). The second method (which is more global) lets
<br>you use the xref.properties set. Both methods, of course, are over my
<br>head.
<br><br>Let's try the second method, which seems easier.
<br><br>What is xref.properties? The example given lists name="color" and a
<br>test for it. I don't recognize the name="color" attribute here. What
<br>other attributes could you use here? Is there some kind of reference
<br>for what can go inside xref.properties?
<br><br>The earlier example in the same section shows a stylesheet
<br>customization that looks inside sect1 or section and whenever it sees
<br>an xref, it inserts an FO statement when the $purpose="xref":
<br><br><xsl:template match="sect1|sect2|sect3|sect4|sect5|section"
<br> mode="insert.title.markup">
<br> <xsl:param name="purpose"/>
<br> <xsl:param name="xrefstyle"/>
<br> <xsl:param name="title"/>
<br><br> <xsl:choose>
<br> <xsl:when test="$purpose = 'xref'">
<br> <fo:inline font-style="italic">
<br> <xsl:copy-of select="$title"/>
<br> </fo:inline>
<br> </xsl:when>
<br> <xsl:otherwise>
<br> <xsl:copy-of select="$title"/>
<br> </xsl:otherwise>
<br> </xsl:choose>
<br></xsl:template>
<br><br><br>But I don't understand purpose='xref' here. What is purpose and how
<br>would a writer specify this? Did this template just create
<br>name="purpose" out of thin air or is this something already described
<br>in a stylesheet? In fact, the first part of this doesn't make sense at
<br>all to me; can anyone explain what is going on with purpose and
<br>mode="insert.title.markup" (I recognize xrefstyle and title but not
<br>the rest).
<br><br>Thanks for your help.
<br><br>Robert
<br><br><br>--
<br>Robert Nagle
<br>htpt://www.robertnagle.info
<br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26415279&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26415279&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26414849RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 18 November 20092009-11-18T12:09:39Z2009-11-18T12:09:39ZGrosso, Paul<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: Bob Stayton [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26414849&i=0" target="_top" rel="nofollow">bobs@...</a>]
<br>> Sent: Monday, 2009 November 16 11:44
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26414849&i=1" target="_top" rel="nofollow">docbook-tc@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26414849&i=2" target="_top" rel="nofollow">docbook@...</a>
<br>> Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 18
<br>> November 2009
<br>>
<br>> DocBook Technical Committee Meeting Agenda: 18 November 2009
<br>> =============================================================
</div><br><br>> 2821653 indexterms in footnotes
<br><br><br>First, I note that indexterm is already allowed within paras
<br>within footnotes (at least in DocBook 4.x) which is where I'd
<br>usually expect an indexterm to be. The discussion during the
<br>TC call seemed not to realize this, so I wonder if I'm confused
<br>or the discussion was confused. (Perhaps this is different in
<br>DocBook 5.0--I didn't check.)
<br><br>I'm not sure how an indexterm as a child of footnote would be
<br>usefully different from putting the indexterm within the para
<br>(or other child of footnote, since footnote requires some child)
<br>that is within the footnote.
<br><br>Given that footnotes are allowed as descendants of footnote
<br>but just not as immediate children, and given that I don't
<br>see also allowing indexterm as an immediate child of footnote
<br>as useful, I suggest there is no reason to accept this RFE.
<br><br>On the other hand, the Arbortext composition products have no
<br>problem handling either indexterms as a children of footnote
<br>or as children of para within footnotes.
<br><br>paul
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26414849&i=3" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26414849&i=4" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26407967RFE 2791288: add quote to corpauthor and gui elements2009-11-18T05:41:25Z2009-11-18T05:41:25ZNorman WalshHello world,
<br><br>This RFE[1] makes the (quite reasonable, I think) suggestion that
<br><quote> should be allowed in <holder>. (I'm not sure I see the
<br>relevance of <quote> in the <gui...> elements, but let's set that
<br>aside for a moment.)
<br><br>Nowhere are the quote characters forbidden, so I think it's reasonable
<br>to assume that the quote element should be ubiquitous. (This is
<br>especially true when you consider that quote characters vary by
<br>language and locale, so being able to generate the appropriate
<br>quotation character has real value.)
<br><br>Reviewing the content model of holder, we find that it boils down to
<br>the ubiquitous inlines, a limited form of phrase that can only contain
<br>the ubiquitous inlines, replaceable, and text.
<br><br>Recall that the ubiquitous inlines are:
<br><br> inlinemediaobject (for non-unicode characters)
<br> remark (for comments)
<br> superscript and subscript (for ... super and subscripts)
<br> link, olink, xref, anchor (for linking)
<br> alt (for accessibility)
<br><br>How much markup to allow in ubiquitious inlines (i.e. *everywhere*) is
<br>a judgement call. The more stuff you allow, the more stuff processors
<br>have to be prepared to support *everywhere*. (As a concrete example,
<br>consider that xsl:value-of on an element that can contain inline
<br>markup is *never* safe.)
<br><br>That said, we've already let that particular cat out of the bag, so
<br>there's proportionally less harm in going a little farther. (To mix my
<br>metaphors.)
<br><br>My current thinking is that we should treat the inlines in groups. If
<br>you're going to allow some elements of a group, you might just as well
<br>allow all the elements.
<br><br>In fact, if we'd applied that rule when we first added superscript and
<br>subscript to the ubiquitous inlines, we would never have received this
<br>RFE because the quote element is in the same group: publishing inlines.
<br><br>The publishing inlines are:
<br><br> abbrev
<br> acronym
<br> date
<br> emphasis
<br> footnote and footnoteref
<br> foreignphrase
<br> phrase
<br> quote
<br> subscript
<br> superscript
<br> wordasword
<br> firstterm
<br> glossterm
<br> coref
<br><br>The abbrev and acronym elements can also include trademark, but like
<br><quote> that should probably be allowed anywhere (because the ™
<br>character is allowed anywhere).
<br><br>I think the natural proposal at this point is to say that we should
<br>allow the publishing inlines (and trademark) into the ubiquituos
<br>inlnes.
<br><br>The only reservations I have are:
<br><br>1. Allowing footnote (and to a lesser extent footnoteref) is a pretty
<br> substantial change. It means you could wind up with just about
<br> anything as a descendant of any element that allows ubiquitous
<br> inlines:
<br><br> <phone>+1-413-555-1212<footnote><para>In the United States, all
<br> phone numbers in the <quote>555</quote> exchange are reserved for
<br> use in examples. They will never be assigned to residential or
<br> business customers.</para></footnote></phone>
<br><br> But maybe that's ok. As I said, we've already let the cat out of
<br> the bag, and are there really any places where footnotes shouldn't
<br> be allowed?
<br><br>2. Some of these elements allow *all* inlines. In order to keep them
<br> from being a complete escape hatch, we'll have to build limited
<br> forms of, for example, firstterm just like we have the limited
<br> form of phrase.
<br><br> But maybe that's ok, too. It's definitely work for the schema
<br> authors, but does it really matter to users? Well, only to the
<br> extent that it might be confusing that sometimes phrase can contain
<br> "envar" and sometimes it can't. But we've already let that cat out
<br> of the bag too with phrase.
<br><br> Be seeing you,
<br> norm
<br><br>P.S. I'm not sure that coref belongs in publishing inlines, but if I
<br>was going to move it, I'd move it to the linking inlines which are
<br>already part of the ubiquitious inlines, so it makes no difference to
<br>the issue at hand.
<br><br>[1] <a href="https://sourceforge.net/tracker/?func=detail&aid=2791288&group_id=21935&atid=384107" target="_top" rel="nofollow">https://sourceforge.net/tracker/?func=detail&aid=2791288&group_id=21935&atid=384107</a><br><br>--
<br>Norman Walsh <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26407967&i=0" target="_top" rel="nofollow">ndw@...</a>> | The perfect man has no method; or
<br><a href="http://www.oasis-open.org/docbook/" target="_top" rel="nofollow">http://www.oasis-open.org/docbook/</a> | rather the best of methods, which
<br>Chair, DocBook Technical Committee | is the method of no-method.--
<br> | Shih-T'ao
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>attachment0</strong> (191 bytes) <a href="http://old.nabble.com/attachment/26407967/0/attachment0" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26390679Re: DocBook web infrastructure needs work2009-11-17T06:14:35Z2009-11-17T06:14:35ZKlorthoJust a quick response to Dave (the first)'s comment -- I'm talking about the initial cost of entry into the DocBook club, you know, not the difficulty of staying abreast of the happenings, once you've already gotten in.<br>
<br>The current situation, with many sites duplicating information, seems to similar to the problem of URI aliases, described here: <a href="http://www.w3.org/TR/webarch/#uri-aliases" target="_top" rel="nofollow">http://www.w3.org/TR/webarch/#uri-aliases</a> , where each alias divides the "web of related resources".<br>
<br>Also, just by the principle of DRY, having many sites with duplicate information creates a maintenance problem, which is apparent here, as there are so many bits of outdated information in so many places.<br><br><br><div class="gmail_quote">
On Tue, Nov 17, 2009 at 12:09 AM, David Cramer <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=0" target="_top" rel="nofollow">dcramer@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And to make things even more confusing, it appears that there are two David Cramers on the DocBook mailing lists :-) ...well, a Dave and a David anyway.<br>
<br>
For a while there was a second David Cramer here at Motive. To disambiguate us in Exchange, they made me "David Cramer (Tech Pubs)" and him "David C. Cramer (Marketing)". I got a lot of his email.<br>
<br>
But I guess I shouldn't complain. I can only imagine what it's like to be named "Mike Smith"!<br>
<font color="#888888"><br>
David<br>
</font><div><div></div><div class="h5"><br>
> -----Original Message-----<br>
> From: Dave Cramer [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=1" target="_top" rel="nofollow">d.cramer@...</a>]<br>
> Sent: Monday, November 16, 2009 9:49 PM<br>
> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=2" target="_top" rel="nofollow">docbook@...</a><br>
> Subject: Re: [docbook] DocBook web infrastructure needs work<br>
><br>
> I'll admit to having trouble finding the schemas sometimes (I<br>
> should just bookmark them!). I think most of the confusion<br>
> comes from Docbook itself vs. the Docbook stylesheets...<br>
><br>
> Dave Cramer<br>
><br>
><br>
> On Mon, Nov 16, 2009 at 6:33 PM, Chris Maloney<br>
> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=3" target="_top" rel="nofollow">voldrani@...</a>> wrote:<br>
> > Hi, I'm new to DocBook. I'm trying to jump into it, but am<br>
> having a<br>
> > really hard time. I've spent an inordinate amount of time<br>
> just trying<br>
> > to figure out what the latest-and-greatest of everything<br>
> is, where on<br>
> > the web are the resources, etc., etc.<br>
><br>
> ---------------------------------------------------------------------<br>
> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=4" target="_top" rel="nofollow">docbook-unsubscribe@...</a><br>
> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=5" target="_top" rel="nofollow">docbook-help@...</a><br>
><br>
><br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=6" target="_top" rel="nofollow">docbook-unsubscribe@...</a><br>
For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26390679&i=7" target="_top" rel="nofollow">docbook-help@...</a><br>
<br>
</div></div></blockquote></div><br>
<p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26388501Re: Footnotes in Lists don't work2009-11-17T03:38:58Z2009-11-17T03:38:58ZJohannes Katelaan-2So it's a bug in FOP. Too bad!
<br>I will have a closer look at the workarounds described in the blog entry and see if it helps in the docbook context.
<br><br>Thanks!
<br><br>Johannes
<br><br>Am 17.11.2009 um 12:23 schrieb Damon Mannion:
<br><div class='shrinkable-quote'><br>> I *think* this is a known limitation to footnotes and FOP?
<br>>
<br>> I *think* this is explained here:
<br>> <a href="http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/" target="_top" rel="nofollow">http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/</a><br>>
<br>> but am in China at the moment, and access to wordpress seems to be
<br>> blocked...
<br>>
<br>> Damon
<br>>
<br>> On Tue, 17 Nov 2009 12:01 +0100, "Johannes Katelaan"
<br>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=0" target="_top" rel="nofollow">jk@...</a>> wrote:
<br>>> Hi,
<br>>>
<br>>> if I put a footnote into a list (I tried itemizedlist and variablelist),
<br>>> then the footnote number will be calculated correctly and will appear in
<br>>> the text, but the footnote body does not appear at the bottom of the
<br>>> page. Is this a bug or a feature? Is there a workaround for this?
<br>>>
<br>>> Johannes
<br>>>
<br>>>
<br>>> ---------------------------------------------------------------------
<br>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=1" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=2" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=3" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=4" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>
</div><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=5" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388501&i=6" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26388288Re: Footnotes in Lists don't work2009-11-17T03:23:03Z2009-11-17T03:23:03ZDamon MannionI *think* this is a known limitation to footnotes and FOP?
<br><br>I *think* this is explained here:
<br><a href="http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/" target="_top" rel="nofollow">http://rvdb.wordpress.com/2008/03/07/rendering-footnotes-in-tables-and-lists-with-fop/</a><br><br>but am in China at the moment, and access to wordpress seems to be
<br>blocked...
<br><br>Damon
<br><br>On Tue, 17 Nov 2009 12:01 +0100, "Johannes Katelaan"
<br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388288&i=0" target="_top" rel="nofollow">jk@...</a>> wrote:
<div class='shrinkable-quote'><br>> Hi,
<br>>
<br>> if I put a footnote into a list (I tried itemizedlist and variablelist),
<br>> then the footnote number will be calculated correctly and will appear in
<br>> the text, but the footnote body does not appear at the bottom of the
<br>> page. Is this a bug or a feature? Is there a workaround for this?
<br>>
<br>> Johannes
<br>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388288&i=1" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388288&i=2" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>
</div><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388288&i=3" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26388288&i=4" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26387984Footnotes in Lists don't work2009-11-17T03:01:17Z2009-11-17T03:01:17ZJohannes Katelaan-2Hi,
<br><br>if I put a footnote into a list (I tried itemizedlist and variablelist), then the footnote number will be calculated correctly and will appear in the text, but the footnote body does not appear at the bottom of the page. Is this a bug or a feature? Is there a workaround for this?
<br><br>Johannes
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26387984&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26387984&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26386639Re: A bibliographical mark-up question2009-11-17T01:19:34Z2009-11-17T01:19:34ZNic Gibson-2<br>On 13 Nov 2009, at 17:50, Bob Stayton wrote:
<br><div class='shrinkable-quote'><br>> Hi Nic,
<br>> DocBook (since version 4.2) supports Dublin Core metadata with elements like biblioid, bibliocoverage, bibliorelation, and bibliosource. I would think bibliorelation would suit your information. See:
<br>>
<br>> <a href="http://docbook.org/tdg/en/html/bibliorelation.html" target="_top" rel="nofollow">http://docbook.org/tdg/en/html/bibliorelation.html</a><br>>
<br>> In the biblioentry for the article, include something like this:
<br>>
<br>> <bibliorelation type="ispartof" class="other" otherclass="title">BookName</bibliorelation>
<br>>
<br>> This establishes the relationship connecting the article to the book. The stylesheets simply output this element, though, so you might want to customize its template to better express the relationship in the output.
<br>>
<br>> Bob Stayton
<br>> Sagehill Enterprises
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386639&i=0" target="_top" rel="nofollow">bobs@...</a>
<br>>
</div><br><br>Thanks Bob. That does the job nicely.
<br><br>cheers
<br><br>nic
<br>--
<br>Nic Gibson
<br>Director, Corbas Consulting Ltd
<br>Editorial and Technical Consultancy and Training
<br><a href="http://www.corbas.co.uk" target="_top" rel="nofollow">http://www.corbas.co.uk</a>, +44 (0)7718 906817
<br><br><br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386639&i=1" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386639&i=2" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26385897RE: simplified docbook to PDF | ePub ?2009-11-17T00:10:04Z2009-11-17T00:10:04ZCompagnon ChristopherHi,
<br><br>To publish from docbook to PDF you must first generate your book into FO format. FO generation is in docbook-xsl-1.xx.x\fo directory, but you can use a customized layer.
<br><br>Example :
<br>msxsl.exe .\src\my-book.xml .\xslt\docbook-xsl-1.75.1\fo\docbook.xsl -o .\output\fo\my-book.fo
<br>Or (with customized layer)
<br>msxsl.exe .\src\my-book.xml .\xslt\my-fo.xsl -o .\output\fo\my-book.fo
<br><br>With your fo file, you generate PDF with FOP (apache)
<br><br>.\xslt\fop-0.95\fop.bat .\output\fo\my-book.fo -pdf \output\pdf\my-book.pdf
<br><br>To ePub, I don't know.
<br><br>Anybody has some examples ?
<br><br>Cordialement,
<br><br>____________________________________________
<br>Christopher COMPAGNON
<br>AXA GROUP SOLUTIONS - Procurement, BI Supply
<br>Département Solutions Business Intelligence
<br>Domaine BI France - Reporting Opérationnel
<br>( 01 44 45 04 16 (55 04 16)
<br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=0" target="_top" rel="nofollow">christopher.compagnon.alti@...</a>
<br>____________________________________________
<br>Pensez à l'environnement avant d'imprimer ce message
<br>
<br><br>-----Message d'origine-----
<br>De : Anthony Ettinger [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=1" target="_top" rel="nofollow">ettinger@...</a>]
<br>Envoyé : mardi 17 novembre 2009 04:55
<br>À : <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=2" target="_top" rel="nofollow">docbook@...</a>
<br>Objet : [docbook] simplified docbook to PDF | ePub ?
<br><br>Is there such a thing?
<br><br>I want to publish my book online in both PDF and ePub format.
<br><br><br>--
<br>Anthony Ettinger
<br>408-656-2473
<br><a href="http://anthony.ettinger.name" target="_top" rel="nofollow">http://anthony.ettinger.name</a><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=3" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=4" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=5" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26385897&i=6" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26384542RE: DocBook web infrastructure needs work2009-11-16T21:09:23Z2009-11-16T21:09:23ZDavid Cramer (Tech Pubs)And to make things even more confusing, it appears that there are two David Cramers on the DocBook mailing lists :-) ...well, a Dave and a David anyway.
<br><br>For a while there was a second David Cramer here at Motive. To disambiguate us in Exchange, they made me "David Cramer (Tech Pubs)" and him "David C. Cramer (Marketing)". I got a lot of his email.
<br><br>But I guess I shouldn't complain. I can only imagine what it's like to be named "Mike Smith"!
<br><br>David
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: Dave Cramer [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=0" target="_top" rel="nofollow">d.cramer@...</a>]
<br>> Sent: Monday, November 16, 2009 9:49 PM
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=1" target="_top" rel="nofollow">docbook@...</a>
<br>> Subject: Re: [docbook] DocBook web infrastructure needs work
<br>>
<br>> I'll admit to having trouble finding the schemas sometimes (I
<br>> should just bookmark them!). I think most of the confusion
<br>> comes from Docbook itself vs. the Docbook stylesheets...
<br>>
<br>> Dave Cramer
<br>>
<br>>
<br>> On Mon, Nov 16, 2009 at 6:33 PM, Chris Maloney
<br>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=2" target="_top" rel="nofollow">voldrani@...</a>> wrote:
<br>> > Hi, I'm new to DocBook. I'm trying to jump into it, but am
<br>> having a
<br>> > really hard time. I've spent an inordinate amount of time
<br>> just trying
<br>> > to figure out what the latest-and-greatest of everything
<br>> is, where on
<br>> > the web are the resources, etc., etc.
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=3" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>> For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=4" target="_top" rel="nofollow">docbook-help@...</a>
<br>>
<br>>
</div><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=5" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384542&i=6" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26384049simplified docbook to PDF | ePub ?2009-11-16T19:55:11Z2009-11-16T19:55:11ZAnthony Ettinger-4Is there such a thing?
<br><br>I want to publish my book online in both PDF and ePub format.
<br><br><br>--
<br>Anthony Ettinger
<br>408-656-2473
<br><a href="http://anthony.ettinger.name" target="_top" rel="nofollow">http://anthony.ettinger.name</a><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384049&i=0" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384049&i=1" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26384000Re: DocBook web infrastructure needs work2009-11-16T19:48:55Z2009-11-16T19:48:55ZDave Cramer-9I'll admit to having trouble finding the schemas sometimes (I should
<br>just bookmark them!). I think most of the confusion comes from Docbook
<br>itself vs. the Docbook stylesheets...
<br><br>Dave Cramer
<br><br><br>On Mon, Nov 16, 2009 at 6:33 PM, Chris Maloney <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384000&i=0" target="_top" rel="nofollow">voldrani@...</a>> wrote:
<br>> Hi, I'm new to DocBook. I'm trying to jump into it, but am having a really
<br>> hard time. I've spent an inordinate amount of time just trying to figure
<br>> out what the latest-and-greatest of everything is, where on the web are the
<br>> resources, etc., etc.
<br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384000&i=1" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26384000&i=2" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26381867DocBook web infrastructure needs work2009-11-16T15:33:16Z2009-11-16T15:33:16ZKlorthoHi, I'm new to DocBook. I'm trying to jump into it, but am having a really hard time. I've spent an inordinate amount of time just trying to figure out what the latest-and-greatest of everything is, where on the web are the resources, etc., etc.<br>
Here I've jotted a few notes from my newbie perspective, for your consideration:<br><br>Here's just a small subset of the sites I've come across:<br>(1) Docbook project page: <a href="http://docbook.sourceforge.net/" target="_top" rel="nofollow">http://docbook.sourceforge.net/</a><br>
(2) DocBook.org, Norman Walsh' DocBook site<br>(3) <a href="http://nwalsh.com/docbook/" target="_top" rel="nofollow">http://nwalsh.com/docbook/</a>, Norman Walsh' *other* DocBook site<br>(4) DocBook repository: <a href="http://sourceforge.net/projects/docbook/" target="_top" rel="nofollow">http://sourceforge.net/projects/docbook/</a><br>
(A) DocBook Wiki - <a href="http://wiki.docbook.org/" target="_top" rel="nofollow">http://wiki.docbook.org/</a><br>(B) DocBook FAQ - <a href="http://www.dpawson.co.uk/docbook/" target="_top" rel="nofollow">http://www.dpawson.co.uk/docbook/</a><br><br>- I'd propose to make the DocBook project page (1) the primary resource for<br>
people wanting to get involved with DocBook.<br> - Right now, in a Google search on "docbook", this site comes up ninth.<br> (behind the wiki, the faq, etc.)<br> - Norm's site (2) should have a prominent link to it. Right now, I don't<br>
know if there's any link at all (but I didn't search exhaustively).<br> - Norm's other site (3) has a link to the repository, but not the DocBook<br> project page. Norm, I'd suggest making a link to the DocBook project <br>
page #1 in your list of "principle sources".<br><br>- TDG is very good, and is a good entry-point, but it is a little bit hard to find<br> (and hard to know that you're looking at the latest version.)<br>
- But what's really missing is a dead-simple "Getting Started with DocBook<br> in one hour" lesson.<br>- Examples! I want more examples/templates of complete documents. These should<br> be kept up-to-date, and should showcase as many of the tags as possible, by<br>
category.<br>- It seems that the wiki (A) is dead -- so links to it should either be removed,<br> or else some other caveat should be given before the user clicks through.<br> (At the very least, remove "up-to-date".)<br>
- The FAQ (B) is also badly out of date. So, ditto with the links to it, unless<br> it can be beaten into shape.<br><br>Who maintains the DocBook project page? If anyone's with me here, maybe I<br>could follow this up with some specific suggestions for improvements to that<br>
page.<br><br> <br>
<p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26380034Publishing extremely long tables2009-11-16T13:40:38Z2009-11-16T13:40:38ZjrhookerHi all,
<br><br>I'm publishing docbook files that have been generated off of RDL (register description language) files. Some of the tables in the documents are sufficiently huge that they overwhelm the dbxsl publishing scripts due to, I believe, the degree of recursion necessary to handle rowspan elements.
<br><br>The thing is, none of the huge tables *use* rowspan elements, so checking for them is a waste of resources. I'm going to alter the table processing so that it checks at each tbody element to see if any of the containing rows contain rowspan elements, and if not then have it use a simplified processing model. Just thought I'd check to see if anyone had already done this and what the best approach turned out to be.
<br><br>Thanks,
<br>Jeff.
<br><br>Jeff Hooker, XDocs Admin, Technical Communications
<br>PMC-Sierra, Inc., 100-2700 Production Way, Burnaby BC V5A 4X1
<br>(Tel) 604.415.6000 x 2625
<br>(Cell) 778-855-7406
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26380034&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26380034&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26378088Re: Building UTF-8 pdfs.2009-11-16T11:37:38Z2009-11-16T11:37:38ZChris Jones-44On Mon, Nov 16, 2009 at 01:51:53PM EST, Jirka Kosek wrote:
<br><br>> Chris Jones wrote:
<br>> > I created a bare-bones DocBook xml file that contains:
<br>>
<br>> This problem is too TeX spefic -- probably you can expect more help on
<br>> specialized XeTeX and TeX lists.
<br><br>That's the problem with tool chains - you're never sure where to ask.
<br><br>This is initially an asciidoc problem :-)
<br><br>Thanks,
<br><br>CJ
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26378088&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26378088&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26377843Re: Image overflows2009-11-16T11:21:24Z2009-11-16T11:21:24ZTobias Anstett [k15t.com]I don't know if I was too fast stating that XEP supports it, but I
<br>will evaluate it. My assumption was based on
<br><a href="http://www.renderx.com/reference.html" target="_top" rel="nofollow">http://www.renderx.com/reference.html</a> -> Core Options ->
<br>SUPPORT_XSL11 which turns on/off XSL-FO 1.1 support. I will try
<br>tomorrow and tell you if it works or not. For me this would be a
<br>really useful feature too.
<br><br>Cheers,
<br>Tobias
<br><br><br>On Sun, Nov 15, 2009 at 8:13 PM, David Cramer <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=0" target="_top" rel="nofollow">dcramer@...</a>> wrote:
<div class='shrinkable-quote'><br>> I don't see any reference to it being supported in the XEP docs. This is surprising given how usefult a feature it is.
<br>>
<br>> <a href="http://www.google.com/search?q=%22scale-down-to-fit%22+site%3Arenderx.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a" target="_top" rel="nofollow">http://www.google.com/search?q=%22scale-down-to-fit%22+site%3Arenderx.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a</a><br>>
<br>> David
<br>>
<br>>> -----Original Message-----
<br>>> From: Tobias Anstett [k15t.com] [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=1" target="_top" rel="nofollow">tobias@...</a>]
<br>>> Sent: Sunday, November 15, 2009 7:24 AM
<br>>> To: Vincent Hennebert
<br>>> Cc: DocBook Apps
<br>>> Subject: Re: [docbook-apps] Image overflows
<br>>>
<br>>> Thanks Vincent, thanks Bob,
<br>>>
<br>>> We are using FOP as well as XEP so it should work for me. Are
<br>>> there any plans to update the graphics template to support
<br>>> this FO 1.1 feature out of the box?
<br>>>
<br>>> Best,
<br>>> Tobias
<br>>>
<br>>>
<br>>> On Fri, Nov 13, 2009 at 9:19 PM, Vincent Hennebert
<br>>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=2" target="_top" rel="nofollow">vhennebert@...</a>> wrote:
<br>>> > Hi Bob,
<br>>> >
<br>>> > Bob Stayton wrote:
<br>>> >> Hi Vincent,
<br>>> >> If you don't mind my asking, how did you learn that FOP
<br>>> 0.95 supports
<br>>> >> it?
<br>>> >
<br>>> > I ran it on a simple FO file and noticed it was producing
<br>>> the expected
<br>>> > output, so I assumed it had support for it :-)
<br>>> >
<br>>> >
<br>>> >> The FOP compliance page does not mention it:
<br>>> >>
<br>>> >> <a href="http://xmlgraphics.apache.org/fop/compliance.html" target="_top" rel="nofollow">http://xmlgraphics.apache.org/fop/compliance.html</a><br>>> >>
<br>>> >> The only 1.1 property it mentions is for bookmarks. I suspect the
<br>>> >> compliance page needs to be updated.
<br>>> >
<br>>> > Indeed, what's confusing is that the compliance page mentions the
<br>>> > XSL-FO 1.0 Recommendation, and not 1.1. In fact, FOP has already
<br>>> > started to implement some 1.1 features.
<br>>> > (Actually, there already is a reported bug about that:
<br>>> > <a href="https://issues.apache.org/bugzilla/show_bug.cgi?id=46565" target="_top" rel="nofollow">https://issues.apache.org/bugzilla/show_bug.cgi?id=46565</a>)
<br>>> >
<br>>> >
<br>>> > Vincent
<br>>> >
<br>>> >
<br>>> >> Bob Stayton
<br>>> >> Sagehill Enterprises
<br>>> >> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=3" target="_top" rel="nofollow">bobs@...</a>
<br>>> >>
<br>>> >>
<br>>> >> ----- Original Message ----- From: "Vincent Hennebert"
<br>>> >> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=4" target="_top" rel="nofollow">vhennebert@...</a>>
<br>>> >> To: "docbook-apps" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=5" target="_top" rel="nofollow">docbook-apps@...</a>>
<br>>> >> Sent: Friday, November 13, 2009 9:16 AM
<br>>> >> Subject: Re: [docbook-apps] Image overflows
<br>>> >>
<br>>> >>
<br>>> >>> Hi Bob,
<br>>> >>>
<br>>> >>> Bob Stayton wrote:
<br>>> >>>> Hi,
<br>>> >>>>
<br>>> >>>> content-width="scale-down-to-fit"
<br>>> >>>>
<br>>> >>>> is a new feature in XSL-FO version 1.1. Do you know of
<br>>> any XSL-FO
<br>>> >>>> processors that support it? I can't seem to find it
<br>>> mentioned in
<br>>> >>>> any documentation of the processors.
<br>>> >>>
<br>>> >>> Apache FOP supports it since version 0.95. I don't know
<br>>> about other
<br>>> >>> XSL-FO processors.
<br>>> >>>
<br>>> >>>
<br>>> >>> Vincent
<br>>> >>>
<br>>> >>>
<br>>> >>>> Bob Stayton
<br>>> >>>> Sagehill Enterprises
<br>>> >>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=6" target="_top" rel="nofollow">bobs@...</a>
<br>>> >>>>
<br>>> >>>>
<br>>> >>>> ----- Original Message ----- From: "Vincent Hennebert"
<br>>> >>>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=7" target="_top" rel="nofollow">vhennebert@...</a>>
<br>>> >>>> To: "docbook-apps" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=8" target="_top" rel="nofollow">docbook-apps@...</a>>
<br>>> >>>> Sent: Friday, November 13, 2009 2:53 AM
<br>>> >>>> Subject: Re: [docbook-apps] Image overflows
<br>>> >>>>
<br>>> >>>>
<br>>> >>>>> Hi Tobias,
<br>>> >>>>>
<br>>> >>>>> Tobias Anstett [k15t.com] wrote:
<br>>> >>>>>> Hi,
<br>>> >>>>>>
<br>>> >>>>>> Recently I had a problem with image overflows using Apache as
<br>>> >>>>>> well as XEP.
<br>>> >>>>>>
<br>>> >>>>>> I use both very wide and very high images in my documentation.
<br>>> >>>>>> When applying my customization layers they are always
<br>>> scaled to
<br>>> >>>>>> match the width of the page but I have problems if the
<br>>> image is
<br>>> >>>>>> still to high to match the available page space/size.
<br>>> >>>>>>
<br>>> >>>>>> Using Apache images are just rendered on top of the
<br>>> page ignoring
<br>>> >>>>>> the page master setup (so above header, body, footer, starter
<br>>> >>>>>> ...) not fitting into the available area in the body.
<br>>> >>>>>> Using XEP there is just some information in the logs
<br>>> stating that
<br>>> >>>>>> XEP was not able to satisfy the constraints and (!!!) does not
<br>>> >>>>>> print the image at all.
<br>>> >>>>>>
<br>>> >>>>>> I use <d:imagedata width="100%" contentdepth="100%"
<br>> .../> in docbook.
<br>>> >>>>>> Is there a way to enable some kind of auto-fit
<br>>> functionality? In
<br>>> >>>>>> a customization layer producing some kind of powerpoint slide
<br>>> >>>>>> layout I overwrote the graphic template to set the (maximum)
<br>>> >>>>>> height. Now,
<br>>> >>>>>> i) very wide but not that high images are scaled to fit the
<br>>> >>>>>> available width (OK)
<br>>> >>>>>> ii) very high but not very wide images are scaled to fit the
<br>>> >>>>>> available height (OK)
<br>>> >>>>>> iii) small images are upscaled to match height or respectively
<br>>> >>>>>> the width (NOT REALLY OK)
<br>>> >>>>>>
<br>>> >>>>>>
<br>>> >>>>>> Do somebody have a solution for point iii ?
<br>>> >>>>>
<br>>> >>>>> Not sure of what needs to be done at the DocBook level,
<br>>> but at the
<br>>> >>>>> XSL-FO level you should generate something like this:
<br>>> >>>>> <fo:external-graphic src="url('path/to/the/image')"
<br>>> >>>>> inline-progression-dimension.maximum="100%"
<br>>> >>>>> content-width="scale-down-to-fit"
<br>>> >>>>> block-progression-dimension.maximum="<height of
<br>>> region-body>"
<br>>> >>>>> content-height="scale-down-to-fit"/>
<br>>> >>>>>
<br>>> >>>>> That should keep small images to their natural widths and scale
<br>>> >>>>> down bigger images.
<br>>> >>>>>
<br>>> >>>>>
<br>>> >>>>> HTH,
<br>>> >>>>> Vincent
<br>>> >
<br>>> >
<br>>> ---------------------------------------------------------------------
<br>>> > To unsubscribe, e-mail:
<br>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=9" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>> > For additional commands, e-mail:
<br>>> > <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=10" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>> >
<br>>> >
<br>>>
<br>>> ---------------------------------------------------------------------
<br>>> To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=11" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>>> For additional commands, e-mail:
<br>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=12" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br>>>
<br>>>
<br>>
</div><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=13" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377843&i=14" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26377401Re: Building UTF-8 pdfs.2009-11-16T10:51:53Z2009-11-16T10:51:53ZJirka KosekChris Jones wrote:
<br>> I created a bare-bones DocBook xml file that contains:
<br><br>This problem is too TeX spefic -- probably you can expect more help on
<br>specialized XeTeX and TeX lists.
<br><br> Jirka
<br><br>--
<br>------------------------------------------------------------------
<br> Jirka Kosek e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26377401&i=0" target="_top" rel="nofollow">jirka@...</a> <a href="http://xmlguru.cz" target="_top" rel="nofollow">http://xmlguru.cz</a><br>------------------------------------------------------------------
<br> Professional XML consulting and training services
<br> DocBook customization, custom XSLT/XSL-FO document processing
<br>------------------------------------------------------------------
<br> OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
<br>------------------------------------------------------------------
<br><br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (267 bytes) <a href="http://old.nabble.com/attachment/26377401/0/signature.asc" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>tag:old.nabble.com,2006:post-26376279DocBook Technical Committee Meeting Agenda: 18 November 20092009-11-16T09:43:39Z2009-11-16T09:43:39ZBob StaytonDocBook Technical Committee Meeting Agenda: 18 November 2009
<br>=============================================================
<br><br>The DocBook Technical Committee will meet on Wednesday, 18 November 2009 at
<br>01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
<br>022:30p India+) for 90 minutes.
<br><br>Attendance at teleconferences is restricted to members
<br>(and prospective members) of the committee.
<br><br>This is the phone number for Wednesday's DocBook TC call:
<br><br>Phone: +1-719-387-5556
<br> Code: 902213
<br><br>The DocBook TC uses the #docbook IRC channel on
<br>irc.freenode.org. The IRC channel is used for exchanging
<br>URIs, providing out-of-band comments, and other aspects
<br>of the teleconference, so please join us there if at
<br>all possible.
<br><br>Agenda
<br><br>1. Roll call
<br>2. Accepting the minutes [1] of the previous meeting.
<br>3. Next meeting: 16 December 2009
<br>4. Review of the agenda.
<br>5. Review of open action items
<br><br> a. Norm to put the new backwards compatibility policy in the spec.
<br><br> b. Norm to put the new backwards compatibility policy in the
<br> reference documentation.
<br><br> c. Norm to take a look at the inlines and make a proposal
<br> regarding RFE 2791288.
<br><br> d. Norm to reply to RFE 2820947 (transclusion) with the
<br> committee's concerns (see the minutes).
<br><br> e. Gershon to develop a reltable example.
<br><br>6. DocBook 5.0 standards celebration.
<br><br>7. New edition of DocBook: The Definitive Guide
<br><br>8. Publishing Subcommittee report.
<br><br>9. eLearning Subcommittee report.
<br><br>10. DocBook assembly schema.
<br><br>11. topic element (RFE #2820190).
<br><br>12. Review of Requests for Enhancement
<br><br> To browse a specific RFE, enter the URL (on one line):
<br><br> <a href="http://sourceforge.net/tracker/index.php?func=detail&;" target="_top" rel="nofollow">http://sourceforge.net/tracker/index.php?func=detail&;</a><br> group_id=21935&atid=384107&aid=XXXX
<br><br> RFEs to revisit for 6.0
<br> 1907003 biblioid content model too broad
<br><br> RFEs to be considered
<br> 1679665 Add better support for modular documentation
<br> 2770858 Add limited emphasis to ubiquitous inlines
<br> 2791288 add quote to corpauthor and gui elements
<br> 2820190 add a topic element
<br> 2820947 Ability to transclude text
<br> 2821653 indexterms in footnotes
<br><br><br>-----
<br><br>[1] <a href="http://lists.oasis-open.org/archives/docbook-tc/200910/msg00022.html" target="_top" rel="nofollow">http://lists.oasis-open.org/archives/docbook-tc/200910/msg00022.html</a><br><br>Bob Stayton
<br>Sagehill Enterprises
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26376279&i=0" target="_top" rel="nofollow">bobs@...</a>
<br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26376279&i=1" target="_top" rel="nofollow">docbook-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26376279&i=2" target="_top" rel="nofollow">docbook-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-General-f15827.html" embed="fixTarget[15827]" target="_top" >docbook General</a></p>tag:old.nabble.com,2006:post-26367891Building UTF-8 pdfs.2009-11-15T23:41:08Z2009-11-15T23:41:08ZChris Jones-44I created a bare-bones DocBook xml file that contains:
<br><br><?xml version="1.0" encoding="UTF-8"?>
<br><!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "<a href="http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" target="_top" rel="nofollow">http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd</a>">
<br><br><article>
<br><articleinfo>
<br> <title>Unicode blocks</title>
<br></articleinfo>
<br><section id="_cjk">
<br><title>CJK</title>
<br><para>Some CJK:</para>
<br><para>
<br>㺀 㺁 㺂 㺃 㺄 㺅 㺆 㺇 㺈 㺉 㺊 㺋 㺌 㺍 㺎
<br>㺏 㺐 㺑 㺒 㺓 㺔 㺕 㺖 㺗 㺘 㺙 㺚 㺛 㺜 㺝
<br>㺞 㺟 㺠 㺡 㺢 㺣 㺤 㺥 㺦 㺧 㺨 㺩 㺪 㺫 㺬
<br>㺭 㺮 㺯 㺰 㺱 㺲 㺳 㺴 㺵 㺶 㺷 㺸 㺹 㺺 㺻
<br>㺼 㺽 㺾 㺿 㻀 㻁 㻂 㻃 㻄 㻅 㻆 㻇 㻈 㻉 㻊
<br>㻋 㻌 㻍 㻎 㻏 㻐 㻑 㻒 㻓 㻔 㻕 㻖 㻗 㻘 㻙
<br></para>
<br></section>
<br></article>
<br><br>I have tried building a pdf with this command:
<br><br>-------------------------------------------------------------
<br>$ dblatex -v -b xetex cjk0.xml
<br>-------------------------------------------------------------
<br>dblatex version 0.2.9-3
<br>Build the listings...
<br>XSLT stylesheets DocBook - LaTeX 2e (0.2.9-3)
<br>===================================================
<br>Build cjk0.pdf
<br>This is XeTeXk, Version 3.141592-2.2-0.996-patch2 (Web2C 7.5.6)
<br> %&-line parsing enabled.
<br>entering extended mode
<br><br>** WARNING ** This .map file looks like a dvips format fontmap file.
<br>** WARNING ** -- Current input buffer is: bchb8r CharterBT-Bold "TeXBase1Encoding ReEncodeFont" <8r.enc <bchb8a.pfb
<br>** WARNING ** -- Reading fontmap file stopped at: file="pdftex.map", line=6.
<br>This is XeTeXk, Version 3.141592-2.2-0.996-patch2 (Web2C 7.5.6)
<br> %&-line parsing enabled.
<br>entering extended mode
<br><br>** WARNING ** This .map file looks like a dvips format fontmap file.
<br>** WARNING ** -- Current input buffer is: bchb8r CharterBT-Bold "TeXBase1Encoding ReEncodeFont" <8r.enc <bchb8a.pfb
<br>** WARNING ** -- Reading fontmap file stopped at: file="pdftex.map", line=6.
<br>'cjk0.pdf' successfully built
<br>-------------------------------------------------------------
<br><br>There are no catastrophic errors and the cjk0.pdf is built, but when I
<br>use evince or xpdf to visualize, all I see is the dreaded empty
<br>rectangles.
<br><br>I was under the impression that xetex used fontconfig and I do have at
<br>least one font installed that has the corresponding glyphs but it looks
<br>like I need to tell dblatex/xetex where to look for it.
<br><br>I haven't seen anything in the doc that appears to deal with fonts, so
<br>maybe there is a configuration file that I need to modify, but I have no
<br>idea what it might be.
<br><br>I did find a file at /usr/share/texmf-live/fonts/map/pdftex/ called
<br>pdftex.map that lists what looks like a very large number of fonts, but
<br>none looked familiar.
<br><br>I also tried xmlto/xsltproc with identical results.
<br><br>Also, this happens on a debian/lenny system and there is always a
<br>chance that the packages that are installed are not current.
<br><br>Thanks,
<br><br>CJ
<br><br><br><br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26367891&i=0" target="_top" rel="nofollow">docbook-apps-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26367891&i=1" target="_top" rel="nofollow">docbook-apps-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/docbook-apps-f15828.html" embed="fixTarget[15828]" target="_top" >docbook apps</a></p>