Re: [docbook] Callout, footnotes, annotations.
cga2000 wrote: can imagine creating alternative output of callouts using SVG to draw connecting arrows instead bulleted numbers. That's (vaguely) what I had in mind .. clean arrows, rather than these ugly hyphens .. etc. But I didn't find any sample or doc that would show you how to do that so I figured it wasn't possible. Rather than having n callouts on one line, why not make 5 references to the same one? lt;define name=section co xml:id=triggers.ex3.3/ lt;element name=section lt;element name=titlelt;text/lt;/element lt;oneOrMorelt;element name=paralt;text/lt;/elementlt;/oneOrMore lt;/element lt;/define lt;define name=sect co xml:id=triggers.ex3.4/ lt;element name=sect lt;element name=headlt;text/lt;/element lt;oneOrMorelt;element name=paralt;text/lt;/elementlt;/oneOrMore lt;/element lt;/define lt;/grammar /programlisting calloutlist callout arearefs=triggers.ex3.1 paraAny of the 3 elements may be used as the start element/para /callout callout arearefs=triggers.ex3.2 paraThe root element is defined as being empty/para /callout callout arearefs=triggers.ex3.3 paraThe tag class=elementsection/tag element contains a tag class=elementtitle/tag child/para /callout callout arearefs=triggers.ex3.4 paraThe tag class=elementsect/tag element contains a tag class=elementhead /tag child/para /callout /calloutlist /example No reason I can't have 5 callouts, each specifying the same co element? Does that helpl? btw, I hope you have the appropriate customisation in place, to use the Unicode glyphs instead of just numbers? regards regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [docbook] Callout, footnotes, annotations.
cga2000 wrote: I can imagine creating alternative output of callouts using SVG to draw connecting arrows instead bulleted numbers. That's (vaguely) what I had in mind .. clean arrows, rather than these ugly hyphens .. etc. But I didn't find any sample or doc that would show you how to do that so I figured it wasn't possible. The stylesheets doesn't support it, but it is doable. Though it would be very hard customization. -- -- Jirka Kosek e-mail: [EMAIL PROTECTED] http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO/JTC1/SC34 member -- Want to speak at XML Prague 2007 = http://xmlprague.cz/cfp.html signature.asc Description: OpenPGP digital signature
[docbook] problem with docbook-xsl-1.72.0
Hi, I'm trying to switch from 1.69.1 to 1.72.0. When using 1.72.0 with xalan-1.2.7.0 we get the error: (It's a german WindowsXP...) xalan.bat -PARAM base.dir html/ -PARAM chunk.first.sections 1 -PARAM chunk.section.depth 2 -PARAM use.id.as.filename 1 -ENTITYRESOLVER org.apache.xml.resolver.tools.CatalogResolver -URIRESOLVER org.apache.xml.resolver.tools.CatalogResolver -in user_manual.xml -xsl %DOCBOOK_XSL_HOME%/xhtml/chunk.xsl file:/C:/Programme/docbook-xsl-1.72.0/xhtml/glossary.xsl; Zeilennummer53; Spaltennummer4468; XSLT-Fehler (javax.xml.tran sform.TransformerConfigurationException): javax.xml.transform.TransformerException: javax.xml.transform.TransformerExcep tion: UnzulΣssiger Wert $language fⁿr NMTOKEN-Attribut verwendet: lang. Exception in thread main java.lang.RuntimeException: javax.xml.transform.TransformerException: javax.xml.transform.Tra nsformerException: UnzulΣssiger Wert $language fⁿr NMTOKEN-Attribut verwendet: lang. at org.apache.xalan.xslt.Process.doExit(Process.java:1153) at org.apache.xalan.xslt.Process.main(Process.java:1126) What is the problem with the $language value? I tried to set various language param values but couldn't solve the problem. Any help? -- View this message in context: http://www.nabble.com/problem-with-docbook-xsl-1.72.0-tf3427274.html#a9552718 Sent from the docbook General mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [docbook] problem with docbook-xsl-1.72.0
That problem was fixed shortly after 1.72.0 was released. Try the
docbook-xsl-snapshot release or wait until 1.72.1. It replaces:
xsl:sort lang=$language
with
xsl:sort lang={$language}
which Xalan likes better.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: ThomasK [EMAIL PROTECTED]
To: docbook@lists.oasis-open.org
Sent: Monday, March 19, 2007 6:07 AM
Subject: [docbook] problem with docbook-xsl-1.72.0
Hi,
I'm trying to switch from 1.69.1 to 1.72.0.
When using 1.72.0 with xalan-1.2.7.0 we get the error: (It's a german
WindowsXP...)
xalan.bat -PARAM base.dir html/ -PARAM chunk.first.sections 1 -PARAM
chunk.section.depth 2 -PARAM use.id.as.filename 1 -ENTITYRESOLVER
org.apache.xml.resolver.tools.CatalogResolver -URIRESOLVER
org.apache.xml.resolver.tools.CatalogResolver -in user_manual.xml -xsl
%DOCBOOK_XSL_HOME%/xhtml/chunk.xsl
file:/C:/Programme/docbook-xsl-1.72.0/xhtml/glossary.xsl; Zeilennummer53;
Spaltennummer4468; XSLT-Fehler (javax.xml.tran
sform.TransformerConfigurationException):
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerExcep
tion: UnzulΣssiger Wert $language fⁿr NMTOKEN-Attribut verwendet: lang.
Exception in thread main java.lang.RuntimeException:
javax.xml.transform.TransformerException: javax.xml.transform.Tra
nsformerException: UnzulΣssiger Wert $language fⁿr NMTOKEN-Attribut
verwendet: lang.
at org.apache.xalan.xslt.Process.doExit(Process.java:1153)
at org.apache.xalan.xslt.Process.main(Process.java:1126)
What is the problem with the $language value?
I tried to set various language param values but couldn't solve the
problem.
Any help?
--
View this message in context:
http://www.nabble.com/problem-with-docbook-xsl-1.72.0-tf3427274.html#a9552718
Sent from the docbook General mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[docbook] Functional programming, help to avoid using saxon:assign
Hello everyone, I am attempting to customize the match for phrase roles from docbook (the phrase match calls inline.charseq which is also called by emphasis, and abbrev). My trouble is getting past programming without assignment statements. Using; xml version=1.0, DocBook 4.5, SAXON 6.5.5(current)/8.8J(transition), and Antenna House formatter 4.0 The method I tried to use is to set parameters or variables and change them based on the role and wether or not a processing instruction exists within the phrase. However, saxon:assign is likely being/has been deprecated and what I've read makes me believe there's a better way that I'm not aware of. The idea is: - be able to add one-of fo:inline attributes at any point by checking for processing instructions (working) - based on the role or self pre-format the text. (emphasis italic, uppercase-normal uppercase no margin, some branding formats - which are the most likely to need overrides, make abbrev periods different than non-abbrev periods, and handle things like having both an underline and overscore with UnderOver). The example text below is what I'm using to test the overrides are working. dedication titlephrase role=THEKEYthe key/phrase ndash; My book!--this won't work for other people bookname;--/title titleabbrev!--this won't work for other people bookname;--My Book/titleabbrev paraphrase role=uppercase-normal?dbfo text-transform=lowercase??dbfo font-style=italic color=#c0c0c0 text-decoration=underline border-before=solid?This is a test of border-before style with underline, italics, and some color. Override is to make uppercase lowercase./phrase This text is outside the phrase and should format itself normally. phrase role=uppercase-normalTest to make sure uppercase normal was not damaged./phrase/para /dedication I am able to figure out how to do the tests within the processing.attributes template by having each variable test for a result from call-templates and if there is no result check the parent for the role. However, that idea is not very maintainable. Is there a better way to make the customized roles easily maintainable while still keeping the advantage of inline.charseq? What I was hoping for for the customizationed roles was a fairly simple template with example text like: xsl:when test=@role='uppercase-normal' xsl:variable name=text-transformuppercase/xsl:variable xsl:variable name=margin0pt/xsl:variable /xsl:when ==A PORTION OF THE STYLESHEET ATTEMPT= ?xml version=1.0 encoding=UTF-8? xsl:stylesheet exclude-result-prefixes=xlink stext xtext lxslt simg ximg extension-element-prefixes=stext xtext version=1.0 xmlns=http://www.w3.org/TR/xhtml1/transitional; xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:lxslt=http://xml.apache.org/xslt; xmlns:simg=http://nwalsh.com/xslt/ext/com.nwalsh.saxon.ImageIntrinsics; xmlns:stext=http://nwalsh.com/xslt/ext/com.nwalsh.saxon.TextFactory; xmlns:ximg=xalan://com.nwalsh.xalan.ImageIntrinsics xmlns:xlink=http://www.w3.org/1999/xlink; xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:xtext=xalan://com.nwalsh.xalan.Text xmlns:saxon=http://saxon.sf.net/; xsl:import href=../fo/docbook.xsl/ !-- not included for request for assitance xsl:import href=CastleRock_Master.xsl/-- lxslt:component elements=insertfile prefix=xtext/ lxslt:component functions=new getWidth getDepth prefix=simg/ !--begin inline.charseq-- xsl:template name=inline.charseq !--these are from fo/inline.xsl-- xsl:param name=content xsl:call-template name=simple.xlink xsl:with-param name=content xsl:apply-templates/ /xsl:with-param /xsl:call-template /xsl:param !--modified, this had the fo:inline in a spot that made it not as re-usable.-- fo:inline xsl:if test=@dir xsl:attribute name=directionxsl:choosexsl:when test=@dir = 'ltr' or @dir = 'lro'ltr/xsl:whenxsl:otherwisertl/xsl:otherwise/xsl:choose/xsl:at tribute /xsl:if xsl:call-template name=processing.attributes/ xsl:choose xsl:when test=@role='UnderOver' !--this is not so elegant but required-- fo:inline text-decoration=overline xsl:copy-of select=$content/ /fo:inline /xsl:when xsl:when test=self::abbrev
Re: [docbook] Callout, footnotes, annotations.
On Mon, Mar 19, 2007 at 07:45:07AM EST, Dave Pawson wrote: cga2000 wrote: can imagine creating alternative output of callouts using SVG to draw connecting arrows instead bulleted numbers. That's (vaguely) what I had in mind .. clean arrows, rather than these ugly hyphens .. etc. But I didn't find any sample or doc that would show you how to do that so I figured it wasn't possible. Rather than having n callouts on one line, why not make 5 references to the same one? lt;define name=section co xml:id=triggers.ex3.3/ lt;element name=section lt;element name=titlelt;text/lt;/element lt;oneOrMorelt;element name=paralt;text/lt;/elementlt;/oneOrMore lt;/element lt;/define lt;define name=sect co xml:id=triggers.ex3.4/ lt;element name=sect lt;element name=headlt;text/lt;/element lt;oneOrMorelt;element name=paralt;text/lt;/elementlt;/oneOrMore lt;/element lt;/define lt;/grammar /programlisting calloutlist callout arearefs=triggers.ex3.1 paraAny of the 3 elements may be used as the start element/para /callout callout arearefs=triggers.ex3.2 paraThe root element is defined as being empty/para /callout callout arearefs=triggers.ex3.3 paraThe tag class=elementsection/tag element contains a tag class=elementtitle/tag child/para /callout callout arearefs=triggers.ex3.4 paraThe tag class=elementsect/tag element contains a tag class=elementhead /tag child/para /callout /calloutlist /example No reason I can't have 5 callouts, each specifying the same co element? Can't test it tonight, but I think I understand what you're saying and it looks like it might lead to a clean solution. Have a feeling part of your example got messed up by my mailer (mutt) -- ie. some closing ''s wrap to the next line and become mixed with the '' that mutt uses for quoting. Does that helpl? Pretty sure it will. The reason I posted was that I began to realize that I was too focused on the way I am used to doing it in text files and was finding it hard to reformulate to something suitable for more sophisticated environments. btw, I hope you have the appropriate customisation in place, to use the Unicode glyphs instead of just numbers? That's another issue I have begun to look at from a more general perspective. Noticed I was getting the odd black diamond with an embedded question mark when I set mozilla's Character Encoding to unicode so I specified encoding=UTF-8 at the top of my .xml files and that took care of this problem. But I'm not sure what I need to do where DocBook is concerned. My understanding is that regarding callouts, I need to specifiy UTF-8 if I want little black circles with embedded numbers in my pdf's, right? What makes it a little tricky in my context, is that some applications I depend on do not play well with unicode .. so I can't just set my locale to UTF-8. I'll research further next weekend because I don't think this is the kind of stuff you can figure out in a couple of hours. Thanks, cga - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[docbook] DocBook Technical Committee Meeting Agenda: 21 March 2007
DocBook Technical Committee Meeting Agenda: 21 March 2007 = The DocBook Technical Committee will meet on Wednesday, 28 June 2006 at 05:00p EDT (02:00p PDT, 21:00GMT, 22:00BST, 23:00CEST, 06:00JST+, 02:30a India+) for 90 minutes. The teleconference phone number is +1.865.524.6352. The participant code is 7386368. Attendance at teleconferences is restricted to members (and prospective members) of the committee. The DocBook TC uses the #docbook IRC channel on irc.freenode.org. The IRC channel is used for exchanging URIs, providing out-of-band comments, and other aspects of the teleconference, so please join us there if at all possible. Agenda 1. Roll call 2. Accepting the minutes[1] of the previous meeting. 3. Next meeting: 18 April 2007 4. Review of the agenda. 5. Review of open action items a. Norm to create a new DB5 candidate release with caption on cals table and informaltable, title and titleabbrev in qandaentry, expand HTML table caption content model to match titles, and allow empty glossary. b. Norm to write an RFC for registering a DocBook MIME type. c. Scott to create a test file of info in CALS table and try it with various XML editors. d. Scott to work on creating a subcommittee charter to submit to the TC. 6. Registered MIME type for DocBook XML See Norm's proposal [2] 7. info in html tables (continued from last meeting) 8. Extend charter to include commercial publishing (continued from last meeting). See Scott's proposed charter [3] 9. DocBook 5 feature freeze 10. Review of Requests for Enhancement To browse a specific RFE, enter the URL (on one line): http://sourceforge.net/tracker/index.php?func=detail;; group_id=21935atid=384107aid= 1097183 Allow Task as a sibling of sections 1588693 Allow ackno in book 1626321 Add a frame attribute to entrytbl element 1641607 Add values for (table|informaltable)/@frame 1644553 Add a label attribute to all elements with caption 1664541 allow termdef in acronym 1666938 Add a description element to subject 1673820 define an xlink:role for olinking 1679665 Add better support for modular documentation 1679712 Fix header comment in dbpoolx.mod (SGML) 1679775 Fix termdef so that glossterm isn't ambiguous 1682917 add pgwide to example - [1] http://lists.oasis-open.org/archives/docbook-tc/200703/msg4.html [2] http://lists.oasis-open.org/archives/docbook-tc/200703/msg5.html [3] http://lists.oasis-open.org/archives/docbook-tc/200703/msg2.html Bob Stayton Sagehill Enterprises DocBook Consulting [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [docbook-apps] xsl:text and \fB results in \efB in manpage output
Am Montag, den 19.03.2007, 18:41 -0500 schrieb Paul DuBois: Daniel Leidert wrote: Hi, If I use e.g. xsl:template match=literal xsl:text\fB/xsl:text xsl:apply-templates/ xsl:text\fR/xsl:text /xsl:template in the customization layer for a manpage XSLT stylesheet, I get an output of: \efB...\efR I'm wondering, what is so different to using xsl:template match=literal xsl:apply-templates mode=bold select=./ /xsl:template which results in \fB...\fR? I can reproduce this issue with the latest release, but not with the latest snapshot. I'm wondering, what's causing this (different) behaviour? Can someone point me into the right direction? Which difference are you referring to? The difference between releases? No. Between the output of both examples. Releases may differ in behaviour of course :) Or the difference between the output from your two examples? (The output for both looks reasonable to me.) They do not look reasonable to me. But I found it. In the 1.72.0 release, the mode=bold template used #x2593;fB to avoid the substitution (by the substitution map). This explains the different behaviour. It would have been nice to announce it in the Release Notes. But I cannot find a special note there. Regards, Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[docbook-apps] specify ID of index.html for JavaHelp's homeID
Hello list, I'm integrating a JavaHelp helpset, created with db5-xsl javahelp.xsl, into a Java application. In JavaHelp, you can specify the ID of the initial page that loads in the JavaHelp viewer. I'd like the index.html page to load, but it doesn't at present. The ID is specified in the helpset file (.hs) under mapshomeID; the ID-URL mapping is specified in the the javahelp map (.jhm), in a mapID element. How do I specify an ID for index.html? The javahelp.xsl transformation yields a mapID and homeID that are not useful. (from jhelpmap.jhm): mapID target=id4679642 url=index.html/ (from jhelpset.hs): maps homeIDtop/homeID I'm fine with homeIDtop/homeID, but how do I change the target ID above? Do I just need an xml:id on my root element (book) before transforming? Thanks! Brett Leber - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[docbook-apps] formatting level 2 headings as a custom side float
I'm working with a DocBook customization that currently formats level 2 headings side-by-side with body text by placing the content in a two-column table. The code worked fine when using FOP 0.20.5 to output to PDF, but it's not working so well with FOP 0.93. I wondered if there's a better, simpler approach I can take to fix. For example, can I format level 2 headings as a custom side float? Keep in mind that I want the heading to be outdented from the body text and right-aligned within the left margin. How would I do that? Regards, Jeff Powanda Vocera Communications Senior Technical Writer 408-790-4256
[docbook-apps] informalfigure/ floats?
I've been trying to accomplish something that would appear to be relatively easy. But it's stumping me. (Using XEP 4.9 and DocBook XML 4.4, and DocBook Stylesheets 1.70) I'd like to have a captioned informal figure around which the text flows. eg. para informalfigure floatstyle=outside mediaobject caption/ /mediaobject /informalfigure /para Given something similar to the above, shouldn't I expect the text to flow around as many as three sides of the figure? -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
