hummm, ok thanx for the help that worked.
i guess i have to recap all the parameters for the HTML
stylesheets ;-)
regards
daniel s. haischt
--
> -Ursprungliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Gesendet: Samstag, 5. Oktober 2002 22:22
> An: Daniel S. Hais
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ "Daniel S. Haischt" <[EMAIL PROTECTED]> was heard to say:
| but if i am using ...
|
| translate('This is a foobar sentence.', ' ', ' ')
|
| ... with saxon i am getting the following result ...
|
| ThisA isA aA foobarA sentence.
That's the right a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ "Daniel S. Haischt" <[EMAIL PROTECTED]> was heard to say:
| but saxon should support the unicode representation
| of extended characters, shouldn't it?
I'm sure it does. And I think the
parameter would let you pick the default you want. For HTML
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ Peter Ring <[EMAIL PROTECTED]> was heard to say:
| maintenance a no-brainer. BTW, the catalog.dtd that you get from
| http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd is
| version 1.7, while the one in the spec is version 1.9. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ Bob Stayton <[EMAIL PROTECTED]> was heard to say:
| Try modelling these examples in a chapter element
| declaration:
|
|
|
|
Ah, yes, if you want xi:include to replace required elements, you're
not going to get the DTD to do that without a lot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ Bob Stayton <[EMAIL PROTECTED]> was heard to say:
| I started to extend the DocBook DTD to permit xi:include,
| but I think it is kind of impossible (except for maybe
| Norm 8^). The xi:include element can replace *any*
| element or group of elemen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ [EMAIL PROTECTED] was heard to say:
| My Parser tends to chuck out loads of noise - My aim is to get just a nice
What sort of errors is your parser producing? Usually that means
you've got errors in your document, and that's going to cause problem
On Sat, Oct 05, 2002 at 03:42:02PM +0200, Daniel S. Haischt wrote:
> hello,
>
> note: this mail belongs to the website DTD.
>
> i tried to use the element
> within one of my website XML source files. the
> website XML source file includes the website-full
> DTD.
>
> to test the element with t
Daniel Veillard <[EMAIL PROTECTED]> writes:
> You should really start accepting that URL can be used as identifiers
> like any other string, sigh ...
It can, but a SYSTEM identifiers is not canonical (= it is not fixed).
Let's hope somebody will finish the LSB some time soon regarding XML.
Sc
hello,
note: this mail belongs to the website DTD.
i tried to use the element
within one of my website XML source files. the
website XML source file includes the website-full
DTD.
to test the element with the
website DTD i tried to use the example that comes
with TDG on page 'programlistingco
that did the trick, thanx!
i had the output encoding set to text, because
i was generating a java script file.
regards
daniel s. haischt
--
> -Ursprungliche Nachricht-
> Von: Dave Pawson [mailto:[EMAIL PROTECTED]]
> Gesendet: Samstag, 5. Oktober 2002 09:15
> An: Daniel S. Haischt; [EMA
On Wed, 2002-10-02 at 11:41, Jeff Beal wrote:
> No one seems to have mentioned this yet, and it may just be a typo in your
> e-mail, but the element has to be
> http://www.w3.org/2001/XInclude"; href="Called.xml"/>,
> not just http://www.w3.org/2001/XInclude"; href="Called.xml"/>
>
It turns out
12 matches
Mail list logo