Re: XSLT and DTD

[email protected] wrote:
> On Apr 11, 10:39 am, Martin Honnen <[email protected]> wrote:
>> [email protected] wrote:
>>> For standard mode which does not
>>> http://arsmc.org/documents/test_w_dtd.html
>>> 2) Both render on Opera
>> The example above also works in a recent Firefox trunk build
>> (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a4pre)
>> Gecko/20070407 Minefield/3.0a4pre), displaying "XSL Output" so I am
>> afraid there is a bug in Firefox 2.0 that it does not render anything.
>> As the bug has been fixed on the trunk there is not much we can do now
>> besides looking for workarounds. Your original aim was to start with an
>> XML document (e.g. <http://arsmc.org/documents/canobie_series.xml>) and
>> that way you should get standards compliant mode even if you don't
>> include a DOCTYPE node as XML is always rendered in standards compliant
>> mode.
>>
>> --
>>
>>         Martin Honnen
>>        http://JavaScript.FAQTs.com/
> 
> Martin
> 
> Thanks very much.
> 
> I appreciate the information.
> 
> I am merely attempting to get something as compliance as possible than
> works on IE, Firefox, Opera, and Safari.
> 
> So far I have something that works in IE6 and IE7, Firefox 2, and
> Opera 9, and Apollo Scout which uses Webkit so hopefully it will work
> on Safari 3 when it is released.
> 
> Hopefully in a few more years all the major browsers will support XSLT
> 2.0 and XHTML 2.0 so something this easy can be done without any need
> for javascript and DOM.
> 
> However I am very glad that Opera and Safari are finally coming on
> board the XSLT band wagon.
> 
> To my way of thinking declarative is much more straight forward that
> imperative.
> 
> Thanks again
> John Perkins

Are you sure that your script is loaded and run when it fails to transform?

Michael