xhtml teething troubles

[Ted]

This page
http://homepage.ntlworld.com/r.a.mcc..._local_dtd.xml
doesn't work properly in Firefox or IE6. The faults are different. In
Firefox the TestText entity is not recognised. In IE6, the <br /> tag
doesn't cause a line break. Can anyone tell me what I'm doing wrong?

[Jack]

Ted wrote:

This page
http://homepage.ntlworld.com/r.a.mcc..._local_dtd.xml
doesn't work properly in Firefox or IE6. The faults are different.
In Firefox the TestText entity is not recognised. In IE6, the <br />
tag doesn't cause a line break. Can anyone tell me what I'm doing
wrong?

As you say, the DTD is local; I can't inspect it. You may or may not
have defined those entities. Consider defining them in an inline DTD
subset; you can't count on the browser fetching your DTD.

--
Jack.

[Chaddy2222]

Ted wrote:

This page
http://homepage.ntlworld.com/r.a.mcc..._local_dtd.xml
doesn't work properly in Firefox or IE6. The faults are different. In
Firefox the TestText entity is not recognised. In IE6, the <br /> tag
doesn't cause a line break. Can anyone tell me what I'm doing wrong?

For a start, the XHTML support inIE6 is not very good. You also must
validate your XHTML, that should go a long way in getting the browsers
to display your code correctly.
Also, use a proper XHTML Strict Doc Type as that will be better
recognized by browsers.
--
Regards Chad. http://freewebdesign.cjb.cc

[VK]

Ted wrote:

http://homepage.ntlworld.com/r.a.mcc..._local_dtd.xml
doesn't work properly in Firefox or IE6. The faults are different. In
Firefox the TestText entity is not recognised.
Right - because Firefox currently is not able to fetch external DTD's
of any kind. See <https://bugzilla.mozill a.org/show_bug.cgi?id =35984>
and outsprings. A very nasty bug forcing to declare all extra entities
in internal DTD like
<!DOCTYPE template [
<!ENTITY nbsp " ">
... etc
]>

Note: there is no "local DTD" as a term. There is external DTD (your
case) and internal DTD (my sample).
In IE6, the <br /> tag doesn't cause a line break.

Because an XML document in default XML namespace has no special
treatment for <br /> - it's just a well-formed element w/o closing tag.
It meay mean something important to HTML parser (like "make line break
here"), but mute to XML.

Use your template in XSL template and link it to XML data file so the
resulting page would be HTML. Briefly: stop /hacking/ things and start
/using/ them ;-)

<comp.text.xm l> is another good source of help on the matter.

[VK]

VK wrote:

Use your template in XSL template and link it to XML data file so the
resulting page would be HTML. Briefly: stop /hacking/ things and start
/using/ them ;-)

Also it is not clear why did you call the post " xhtml teething
troubles" as the linked document has no relation neither to XHTML nor
to HTML. It's a well-formed (accounting extra entities in DTD) XML
document served as XML document.

IE handles is absolutely correctly, FF cannot retrieve DTD because of
bug I mentioned so it breaks its "well-formedness".
In both cases it is really out of the scope of (X)HTML authoring,
<comp.text.xm l> is more relevant.

[Andy Dingley]

Ted wrote:

http://homepage.ntlworld.com/r.a.mcc..._local_dtd.xml
doesn't work properly in Firefox or IE6.

Pragmatically, I think you're stuffed. It appears to be implemented
correctly as a piece of XML work, but this just isn't how the web
works, barely how XML is used (in practice) and is _certainly_ not a
technique that's usable on the web for the forseeable future.

There's a raft of valid techniques out there that just aren't commonly
used in practice, so support for them varies from poor to none.

[Michael Winter]

On 31/05/2006 07:48, VK wrote:

[...] Firefox currently is not able to fetch external DTD's
of any kind.
That statement, as-is, is entirely false. Firefox can process external
subsets, but only does so in certain circumstances and they do not
include DTDs found on the Web.
[...] A very nasty bug
How many times do I have to repeat this: it is /not/ a bug! It may not
be desirable, but it's entirely correct behaviour. As I've also stated
before, Firefox is not the only browser featuring an XML processor that
doesn't process external subsets.
forcing to declare all extra entities in internal DTD [...]
Or don't use entities; encode the document using UTF-8, for example, and
enter the characters directly.

[snip]
Note: there is no "local DTD" as a term.

The OP didn't use it as such. From his perspective the DTD is local as
it's on the same server. Of course, to the rest of us, it's just as remote.

[snip]

Mike

--
Michael Winter
Prefix subject with [News] before replying by e-mail.

[VK]

Michael Winter wrote:

[...] Firefox currently is not able to fetch external DTD's
of any kind.

That statement, as-is, is entirely false. Firefox can process external
subsets, but only does so in certain circumstances and they do not
include DTDs found on the Web.

Yeh, right... Firefox can process external subsets but it cannot
process external subsets. :-)

[...] A very nasty bug

How many times do I have to repeat this: it is /not/ a bug! I

You may repeat it as many times as you want: it doesn't change the
production mechanics.
<http://www.w3.org/TR/REC-xml/>
<q>The productions later in this specification for individual
nonterminals (elementdecl, AttlistDecl, and so on) describe the
declarations after all the parameter entities have been included.</q>

Plain and simple: either you include all declared entities and start
production, or you don't bother with the production at all. I already
explained the real issue with this bug: the impossibility to divide
standard-wise between bogus DTD in (X)HTML and real DTD

[Eric B. Bednarz]

"VK" <sc**********@y ahoo.com> writes:

Note: there is no "local DTD" as a term. There is external DTD (your
case) and internal DTD (my sample).

There ain't no 'external DTD' and 'internal DTD' as terms as well,
except perhaps in your parallel universe. There is an external and an
internal subset, and there is a DTD, which is the sum of both.
--
||| hexadecimal EBB
o-o decimal 3771
--oOo--( )--oOo-- octal 7273
205 goodbye binary 111010111011

[VK]

Eric B. Bednarz wrote:

"VK" <sc**********@y ahoo.com> writes:

Note: there is no "local DTD" as a term. There is external DTD (your
case) and internal DTD (my sample).

There ain't no 'external DTD' and 'internal DTD' as terms as well,
except perhaps in your parallel universe. There is an external and an
internal subset, and there is a DTD, which is the sum of both.

I'm affraid that the you are who's speaking from a parallel universe
;-) There are "external DTD subsets" and "internal DTD subsets"
commonly referred as "external DTD" and "internal DTD" ("commonly"
means by authoring software producers and in manuals, not by VK).
Before inventing more stuff, check the Web.