Peter Eisentraut writes:
> I have a question whether markup inside title elements is recommended
> practice.
It’s definitely one of those edge cases that probably depends a lot on
your specific processing expectations. I don’t think there’s anything
wrong with markup in titles, in principle, but
> The 51st table raises warnings in oxygen 20.1 and I donot know why:
>
>
> Erstbeobachtung
The empty element can’t be followed by a title. You could remove
it, or move the title inside it.
The caption element is, I think, only available in the HTML table model,
so you either
> I get the error:
> non SGML character number
You need to use a different SGML Declaration that includes the
characters you want to use. It shouldn’t be too hard to find the “SGML
Declaration for XML” which will probably work for you.
> To work around the problem I tried to use the HTML
> I have also wondered whether anyone has built DocBook XSLT that directly
> converts the XML to markdown.
No. If you can use CommonMark, which codifies that anything not
represented in CommonMark can always be inserted as HTML, you might get
better mileage from DocBook->HTML5->CommonMark than
Kevin Dunn writes:
> Thanks, Dave. You were helpful to me 10 years ago. The XEP PDF output
> looks pretty nice with the default xsl stylesheet. There are some
> fancy things I achieved with dsssl and jadetex, and I'm not sure how
There’s a blast from the past!
I’ve been chatting, off and on,
Dave Pawson writes:
> from your [1] https://docbook.org/docs/transclusion/transclusion.html
> https://docbook.org/docs/transclusion-requirements/ is 404 Norm?
>
> Should it be the 2010 version?
> https://docbook.org/docs/transclusion-requirements/transclusion-requirements.html
I think so.
Good morning (well, in this locale anyway),
I set out to implement DocBook Transclusion in the DocBook xslTNG
Stylesheets the other day and discovered that a previous attempt to
implement it was already in place.
It appears to have been an attempt to implement the previous draft of
DocBook
Dave Pawson writes:
> And (for some), in either requirement or defn, add a defn of
> transclusion please.
Yup.
Be seeing you,
norm
--
Norman Tovey-Walsh
https://nwalsh.com/
> Space isn't remote at all. It's
Sorry, this got lost in my inbox.
Michael Urban writes:
> I tried out the xslTNG stylesheets recently. I found that my understanding
> of the appearance of inlines like does not match what appears to
> happen in my browsers: in particular, the element generated
> by the xslTNG inline module
Kevin Dunn writes:
> Are there reasons to prefer one of these xslt processors to the
> others? Is it worth looking at the commercial processors?
That’s going to depend on how complicated your output is. The commercial
processors like AntennaHouse offer both better and more complete support
for
Kevin Dunn writes:
> Thanks, Norm. Yes, I evaluated fop, xep, and ahf, and bought the
> Antenna House Formatter. My question now is between xsltproc, Saxon
> 6.5, and Saxon 10.
Sorry I misunderstood your question.
> All three are working for me, and I don't have a reason to prefer one
> to the
Oh, and coming back to the question in your subject line:
Do different xslt processors and parsers really make a difference for
pdf output?
If there are no extensions in use, the answer to that question should be
“no.” Any XSLT processor should produce the same transformed output,
whether
Frank Steimke writes:
> Thank you very much for your comments and suggestions, Norm. Please allow a
> few remarks.
>
> "After a while, this starts to feel less like a canonical DocBook and
> more like a structural interchange format".
>
> Yes, based on DocBook. After all, the result of standard
> Norm, how would an (Relax NG | XSD 1.1) Schema for the outcome of Step
> 7 differ from the DocBook 5.2 Schema? It is a subset, isn't it?
I think so. It’s intended to be, but since it’s never been validated,
it’s possible I messed up :-)
The big changes, on a quick skim, are that an info
> Our own stylesheets are therefore divided into at least phases. First,
[…]
> As far as I can see, the XSL 3 stylesheets for XslTNG are also similar
> in structure.
Yep. The xslTNG stylesheets go through several standard stages:
1. Normalize the logical structure (get rid of entity refs,
s whom I could contact.
>
> Bob Stayton
> Chair, OASIS DocBook Technical Committee
> b...@sagehill.net
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> We are thinking beings, and we cannot exclude the intellect from
> participating in any of our functions.--William James
signature.asc
Description: PGP signature
Hi folks,
I’ve been trying to get a new version of the DocBook xslTNG Stylesheets
finished for a few weeks now. The big (and sometimes backwards
incompatible changes) are:
* The system for dealing with generated text has been completely
rewritten. We’re back to using templates as described in
Hello world,
I discovered last week that I was no longer subscribed to docbook-apps.
I didn’t do that on purpose (I don’t think I did it at all!).
I see that Eric Streit wrote about a regression in xslTNG back in
December. I’ll investigate that. In the meantime:
1. If you find a bug in the
> I see that Eric Streit wrote about a regression in xslTNG back in
> December. I’ll investigate that. In the meantime:
Fixed in 1.11.2 published today.
Be seeing you,
norm
--
Norman Tovey-Walsh
> This gave me some errors which I'm not able to interpret. For easier reading,
> I've uploaded the messages and the XML source code here:
Thank you! I love a test case :-)
Will report back after I’ve had a chance to investigate.
Be seeing you,
> I'd prefer to control it via xsl if that's possible as it provides max
> flexibility.
> Not sure if it's possible 樂
It’s always possible. but sometimes it’s more work. Find the template
for, let’s say “db:book”, that’s putting the ToC in the “wrong” place.
Override that template in your
Hi folks,
A few weeks ago, I posted a note about the DocBook xslTNG Stylesheets
then current 2.0.2 prerelease. This morning I posted 2.0.7. The big
change is in handling of media:
https://xsltng.docbook.org/guide/2.0.7/ch-customizing.html#media
Feedback eagerly solicited.
> No localization exists for "" or "". Using default "en".
> Error at xsl:text on line 169 column 19 of functions.xsl:
> XTMM9000 Processing terminated by xsl:message at line 169 in
> functions.xsl
Fixed in 2.0.8 just released. The termination was a bug, probably left
over from when I was
Tony Graham writes:
> I've just read that part of the XInclude spec [1], and I'm not sure that
> I know what it says, either, but it's clear that the 'language fixup' is
> able to create 'xml:lang=""' in some circumstances.
Yes. I think my XInclude implementation should ad xml:lang="" when the
Hi folks,
This is (I hope) the last pre-release. I just bumped the dependencies
for XML Resolver and the XInclude extension function to the latest
versions.
Feedback welcome.
Be seeing you,
norm
--
Norman
> As I understand the XML specification, the meaning of an empty
> "xml:lang" attribute is defined as overriding any language inherited
> from the parent element and reverting to the processor default. So it
> might make sense that if no language is indicated in an included file,
> it is taken as
> The 'terminate="yes"' on line 168 does rather contradict the message
> that processing will continue with the default language.
Yeah. That seems like a bug. Perhaps I did that when I was trying to
debug and forgot to take it out.
Be seeing you,
Tony Graham writes:
> On 06/02/2023 18:58, Dave Pawson wrote:
>> On Mon, 6 Feb 2023 at 18:48, Tony Graham wrote:
> ...
>> Which begs the question, where to set the default language, and should
>> it be reported as a bug if not set?
>> [Guess, $gentext-language will default to 'default language'
Jirka Kosek writes:
> Empty @xml:lang can be result of XInclude when included files do not
> explicitly specify @xml:lang.
*Blink*. Really? I would not have expected language fixup to do that,
but maybe it does. So xml:lang="" is equivalent to $default-language,
I suppose.
code point 0x41 in Symbol and Zapf Dingbats,
respectively.
Be seeing you,
norm
[1] https://en.wikipedia.org/wiki/Symbol_%28typeface%29
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> Life always comes to a
https://xsltng.docbook.org/guide/2.1.3/m_toc.html
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> The bitterness of poor quality remains long after the sweetness of
> meeting the schedule has be
the error *and* describe how to fix it (!) most appreciated.
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> It is said that power corrupts, but actually it's more true that power
> at
org/guide/2.1.6/ch-using.html#java-main
If you have any trouble, I’m happy to try to help.
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> In matters of style, swim with the c
hese days.
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> Any sufficiently advanced technology is indistinguishable from a rigged
> demo.
signature.asc
Description: PGP signature
ss I’m not as
clever as I think I am ;-)
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> Thanks to words, we have been able to rise above the brutes; and thanks
> to words, we hav
35 matches
Mail list logo
