- From: Yves Savourel <ysavourel@translate.com>
- Date: Mon, 28 Jan 2008 10:47:25 -0700
- To: "'Richard Ishida'" <ishida@w3.org>, <public-i18n-its@w3.org>
Sound OK to me. -ys -----Original Message----- From: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] On Behalf Of Richard Ishida Sent: Monday, January 28, 2008 9:56 AM To: public-i18n-its@w3.org Subject: RE: AI-46: Make an explanation of the BP 24 issue Here is the thread where we discussed BP 24 just before Christmas. If I can make the change suggested by Yves to the BP title and blue text (with a small tweak to the latter) then I think we are ok for BP 24, ie. Title: Best Practice 24: Storing markup from another format Blue text: Avoid escaping markup to enable storage of markup from another format. Is this ok? Cheers, RI ============ Richard Ishida Internationalization Lead W3C (World Wide Web Consortium) http://www.w3.org/International/ http://rishida.net/blog/ http://rishida.net/ > -----Original Message----- > From: public-i18n-its-request@w3.org [mailto:public-i18n-its- > request@w3.org] On Behalf Of Yves Savourel > Sent: 26 December 2007 05:09 > To: public-i18n-its@w3.org > Subject: RE: AI-46: Make an explanation of the BP 24 issue > > > > I think this is a lot clearer now, in the Why do this section. > > I'm still worried about the title and blue text, though. > > It also seems to me that the issue only really arises when you are > > including markup in *a different* format (ie. > > namespace) into your (container) format. Otherwise you wouldn't > > have to escape anything, right? (Although, i suppose that > > theoretically this could relate to fragments of markup in the same > > namespace if they weren't normally allowed in that particular > > location.) > > > > So I'm wondering whether we can use the following: > > > > Best Practice 24: Storing included markup from another format Avoid > > escaping markup to enable inclusion of markup. > > I like the new viewpoint, but I'm not sure about 'included/inclusion' > Maybe something like: > > Best Practice 24: Storing markup from another format > > Avoid escaping markup to enable inclusion of markup. > > ??? > > > > I think, btw, that I came across another example of this while > > reading the Atom spec this week. In Atom, HTML has to be stored in > > escaped form, eg. > > > > <?xml version="1.0" encoding="utf-8"?> > > <feed xmlns="http://www.w3.org/2005/Atom"> > > <title type="text">dive into mark</title> > > <subtitle type="html"> > > A <em>lot</em> of effort > > went into making this effortless > > </subtitle> > > <updated>2005-07-31T12:29:29Z</updated> > > ... > > </feed> > > Yes. Well, at least they do the next good thing: they indicate the > content needs some kind of special process (type="html"). > > -ys
Received on Monday, 28 January 2008 17:48:16 UTC