Jirka Kosek wrote:
> Unfortunatelly not. XSLT operates on a tree constructed by XML parser -
> all text entities are lost at this stage of processing.
so the T in XSLT does not stand for transforming from one DTD to another
without modifying contents at all? :(
Hartmut Holzgraefe wrote:
> btw: is there a way to tell an xslt processor to copy entities
> verbatim? right now i do a "sed -e's/&/&'" before
> applying my conversion stylesheet :(
Unfortunatelly not. XSLT operates on a tree constructed by XML parser -
all text entities are lost at
> > Do you use XSLT style sheets to convert
> > them to DocBook 4? IMHO that would work for many cases.
>
> have it ready for sablotron, but tested only with apache.xml yet
>
> btw: is there a way to tell an xslt processor to copy entities
> verbatim? right now i do a "sed -e's/&/&'" befor
Hojtsy Gabor wrote:
> Do you use XSLT style sheets to convert
> them to DocBook 4? IMHO that would work for many cases.
have it ready for sablotron, but tested only with apache.xml yet
btw: is there a way to tell an xslt processor to copy entities
verbatim? right now i do a "sed -e's/&/&
Hartmut Holzgraefe wrote:
>
> Hojtsy Gabor wrote:
>
> > Encoding is needed, version is optional :)
>
> so it wouldn't harm if i added version all over the place?
No, it wouldn't.
--
-
Jirka Kosek
e-m
Egon Schmid wrote:
>
> From: "Hojtsy Gabor" <[EMAIL PROTECTED]>
>
> > > is there any reason that we have only
> > > instead of
> > > as first line in files included by manual.xml?
> >
> > Yes. Encoding is needed, version is optional :)
> > http://www.w3.org/TR/2000/REC-xml-20001006#sec-TextDec
> this is true for jade / OpenJade
> but some XSLT processors might be more picky about standard conformance
Jade has even not complained for entities written
as &entityname without any ; at the end...
> i want to convert the function reference files to docbook 4
>
> i want to use XSLT to do so
Egon Schmid wrote:
> From: "Hojtsy Gabor" <[EMAIL PROTECTED]>
>
>>>is there any reason that we have only
>>>instead of
>>>as first line in files included by manual.xml?
>>>
>>Yes. Encoding is needed, version is optional :)
>>http://www.w3.org/TR/2000/REC-xml-20001006#sec-TextDecl
>>
>
> We do
From: "Hojtsy Gabor" <[EMAIL PROTECTED]>
> > is there any reason that we have only
> > instead of
> > as first line in files included by manual.xml?
>
> Yes. Encoding is needed, version is optional :)
> http://www.w3.org/TR/2000/REC-xml-20001006#sec-TextDecl
We don´t need encodings in every fi
Hojtsy Gabor wrote:
> Encoding is needed, version is optional :)
so it wouldn't harm if i added version all over the place?
> is there any reason that we have only
> instead of
> as first line in files included by manual.xml?
Yes. Encoding is needed, version is optional :)
http://www.w3.org/TR/2000/REC-xml-20001006#sec-TextDecl
Goba
is there any reason that we have only
instead of
as first line in files included by manual.xml?
12 matches
Mail list logo
