Re: DOCBOOK: Re: marking up keycaps according to their semantics

2003-03-07 Thread Tobias Reif
Steinar Bang wrote: I think it would be clearer if the new element has key in its name But then I'd tend to stay with keycap, allow it to be empty, and add an attribute. Since both sides have merit, I guess you will just have to pick one for your proposed DTD changes for the RFE...:-) I

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Camille =?unknown?q?B=E9gnis?=
Hi Ben, I think the situation is the following: SGML is the legacy system most people get on using because it allows acceptable print output. For HTML output this is not true as XSL allows for efficient rendering. Now if most discussions are around XML and not SGML it is because XML evolves

DOCBOOK: Re: marking up keycaps according to their semantics

2003-03-07 Thread Steinar Bang
Tobias Reif [EMAIL PROTECTED]: But then I'd tend to stay with keycap, allow it to be empty, and add an attribute. Empty keycap elements is already allowed by today's DTD. Remember, keycap/ is just the same as keycap/keycap. The reason I might wish for a different element with an EMPTY

Re: DOCBOOK: Re: marking up keycaps according to their semantics

2003-03-07 Thread Tobias Reif
Steinar Bang wrote: Empty keycap elements is already allowed by today's DTD. I see. Then all that's left is to add an attribute :) (the name might be function, control, action, or etc) Remember, keycap/ is just the same as keycap/keycap. sure The reason I might wish for a different

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Jirka Kosek
Camille Bgnis wrote: I think the situation is the following: SGML is the legacy system most people get on using because it allows acceptable print output. This is not quite truth. With SGML you are mostly using DSSSL stylesheets and toolchain which has quite good print output. But this

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Joachim Ziegler
Bob Stayton wrote: In the meanwhile, you can extend the list in notation.class using local.notation.class to allow PDF by adding this to your DOCTYPE in each file: !DOCTYPE book PUBLIC ... ... [ !ENTITY % local.notation.class | PDF ] That should enable validation. It seems that xmllint can't

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Daniel Veillard
On Fri, Mar 07, 2003 at 01:05:15PM +0100, Joachim Ziegler wrote: Bob Stayton wrote: In the meanwhile, you can extend the list in notation.class using local.notation.class to allow PDF by adding this to your DOCTYPE in each file: !DOCTYPE book PUBLIC ... ... [ !ENTITY %

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Joachim Ziegler
Daniel Veillard wrote: Strange ... I don't know DocBook DTD, before saying it's a libxml2 bug I would like a full example. But please check first with a recent version 2.4.12 is really old (current is 2.5.4). http://xmlsoft.org/bugs.html Sorry, but this is hard to do for me. I would have to

DOCBOOK: any reason why a procedure is not a child of para?

2003-03-07 Thread Robert P. J. Day
i just noticed that the procedure element cannot be a child of a para, as can other lists. any reason for this? it seems like this would be useful if a procedure should be considered part of its enclosing paragraph. just curious. rday

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Tobias Reif
Joachim Ziegler wrote: The only thing I did was inserting Bob's proposed extension line as the first line in the local part of the DTD: xmllint --version using libxml version 20430 xmllint --valid --noout --catalogs skeleton.xml skeleton.xml:25: validity error: NOTATION attribute application

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Daniel Veillard
On Fri, Mar 07, 2003 at 02:06:32PM +0100, Tobias Reif wrote: Joachim Ziegler wrote: The only thing I did was inserting Bob's proposed extension line as the first line in the local part of the DTD: xmllint --version using libxml version 20430 xmllint --valid --noout --catalogs

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Tobias Reif
Daniel Veillard wrote: I bet on also need to define PDF as a NOTATION, obviously the | PDF allows to extend the attribute list but doesn't define it as a notation. Try to add !NOTATION PIC SYSTEM PIC in the internal subset of the document, and see if this validates, I bet it's

Re: DOCBOOK: No attribute value 'PDF' in imagedata

2003-03-07 Thread Joachim Ziegler
Daniel Veillard wrote: it as a notation. Try to add !NOTATION PIC SYSTEM PIC in the internal subset of the document, and see if this validates, I bet it's the problem :-) OK, I got now !ENTITY % local.notation.class | PDF !NOTATION PDF SYSTEM PDF and it works! Thank

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Stephane Bortzmeyer
On Thu, Mar 06, 2003 at 05:28:58PM -0800, Ben Hratshorne [EMAIL PROTECTED] wrote a message of 43 lines which said: I was wondering a while ago whether to start my docbook project stuff using dsssl or xml. They are not incompatible. Unless this is a typo, you compare apples and oranges.

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Yann Dirson
On Fri, Mar 07, 2003 at 10:53:10AM +0100, Jirka Kosek wrote: Camille Bégnis wrote: I think the situation is the following: SGML is the legacy system most people get on using because it allows acceptable print output. This is not quite truth. With SGML you are mostly using DSSSL

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Jirka Kosek
Yann Dirson wrote: This is not true as well. Although it has been dormant for a long time, Openjade 1.3.1 and then 1.3.2 were released several months ago. Work is ongoing to incorporate the developments that were done in the 1.4 branch. And people are working at implementing the most

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Ben Hratshorne
On Fri, Mar 07, 2003 at 04:32:30PM +0100, Stephane Bortzmeyer wrote: On Thu, Mar 06, 2003 at 05:28:58PM -0800, Ben Hratshorne [EMAIL PROTECTED] wrote a message of 43 lines which said: I was wondering a while ago whether to start my docbook project stuff using dsssl or xml. They are

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Jirka Kosek
Ben Hratshorne wrote: I was confused by this. Though I understood the difference between SGML/XML and DSSSL/XSL (you're right it was a typo), I thought that if you use SGML, you must use DSSSL, and if you use XML, you must use XSL. I was unaware you could use DSSSL with XML. Is the converse

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Ben Hratshorne
On Fri, Mar 07, 2003 at 09:57:24PM +0100, Jirka Kosek wrote: Ben Hratshorne wrote: I was confused by this. Though I understood the difference between SGML/XML and DSSSL/XSL (you're right it was a typo), I thought that if you use SGML, you must use DSSSL, and if you use XML, you must use

Re: DOCBOOK: sgml vs xml

2003-03-07 Thread Jirka Kosek
Ben Hratshorne wrote: What about non-closing tags such as imagedata? mediaobject imageobject imagedata fileref=images/stack.pdf /imageobject imageobject imagedata fileref=images/stack.png /imageobject /mediaobject

Re: DOCBOOK-APPS: Posts not being delivered...

2003-03-07 Thread Patrick Eisenacher
Ok, this explains things. Then those citing your missing mails got them personally and not via the mailing list. Since I was on the recipients list of this mail, I can't assure you whether things work again as expected or not. I propose you answer another time to this mail, but only to the

DOCBOOK-APPS: Re: srcdir/objdir issues and including variableusability issues with xsltproc

2003-03-07 Thread Alex Lancaster
[Reposting because my first post didn't appear to go through. Apologies if you get this twice]. JL == John Levon [EMAIL PROTECTED] writes: JL I've found this stuff to be entirely impenetrable. Is there some JL good reason why a sensible, simple include and variable JL substitution system isn't

Re: DOCBOOK-APPS: Re: srcdir/objdir issues and including variableusability issues with xsltproc

2003-03-07 Thread John Levon
On Fri, Mar 07, 2003 at 09:25:37PM -0800, Alex Lancaster wrote: http://www.sagehill.net/xml/docbookxsl/Catalogs.html and more specifically to locate XSL stylesheets: http://www.sagehill.net/xml/docbookxsl/Catalogs.html#d0e1733 I'm aware of catalogs. They aren't a solution because users