This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28868 - Fig 1 error?
Summary: Fig 1 error?
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P3 editorial
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/TR/html-polyglot/#r...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-30 12:38 UTC by Simon Grant
Modified: 2015-07-06 13:47 UTC (History)
5 users (show)

See Also:


Attachments

Description Simon Grant 2015-06-30 12:38:24 UTC
The table in Fig 1 has
]]>	end of CDATA declaration	uninterpreted	uninterpreted	interpreted (ends CDATA block)

Should it be that INSIDE a CDATA section it is interpreted as the end of the section, OUTSIDE a CDATA section it is uninterpreted?
Comment 1 Michael[tm] Smith 2015-07-06 12:56:12 UTC
I'll leave this bug open but be aware that this document is no longer being maintained and shouldn't actually be used any longer for anything.
Comment 2 Simon Grant 2015-07-06 13:38:30 UTC
I first saw this on the dev version -- sorry, that was no longer relevant. I have the same question here.

In Fig 1. I would have thought that the row
]]>	end of CDATA declaration	uninterpreted	uninterpreted	interpreted (ends CDATA block)
should rather be
]]>	end of CDATA declaration	uninterpreted	interpreted (ends CDATA block)	uninterpreted

I guess people will understand what is right, but it's confusing anyway and it would be great to get it straight.
Comment 3 Michael[tm] Smith 2015-07-06 13:47:56 UTC
(In reply to Simon Grant from comment #2)
> I guess people will understand what is right, but it's confusing anyway and
> it would be great to get it straight.

The message we rightly should be sending to readers about this document right now is just: Don't use. At all.

I will work on getting the /TR document and Editor's Draft both updated to say that.

Actually, the broader message we need to be sending is

* Don't try to make polyglot documents.
* That is, don't try to make documents that can be parsed by XML parsers and by HTML parsers (because there are too many things that can go wrong)

That's the message that many people over many years suggested we make a long time ago. Unfortunately we had other people who thought it was a good idea to encourage authors to try it, so this spec ended up getting made.

But now as you can see the people thought this spec was such a great idea have since abandoned it and we're now stuck with cleaning up the mess they left behind.