RE: BP 24: what's all that about?

Hi Richard,

> Your reply doesn't give me more than I can currently read in the document.
> My problem is, I think, understanding what you mean by 'markup as text'.
> By 'as text' do you mean, eg., examples like we have in the BP document?
> What's wrong with <p>This is a paragraph</p> ?

Yes, by 'markup as text' I mean things like "<p>This is a paragraph</p>"

What is wrong with it? --> "<p>" and "</p>"

How do you make the distinction between text and markup for translation, for spell-checking, etc.

I do realize that, at some level, it is the same as storing a chunk of JavaScript in XML: you could somehow detect the type of
content (then we need some kind of identifier for that) and parse it accordingly. But in the case of XML: why no use namespaces and
make it 'normal' XML content directly if you can? In some cases they just cannot, but in many cases it's just laziness that make
them use escaped markup (I know I do it too)

So the idea of the BP is to say roughly:
- avoid 'markup as text' if you can
- if you cannot, at least: a) make sure you indicate the content is not just plain text, and b) avoid CDATA


Cheers,
-yves

Received on Tuesday, 4 December 2007 15:11:24 UTC