>>>>>>>>>>>> Rick Hillegas wrote (2007-06-16 11:05:40): > Myrna van Lunteren wrote: > >On 6/16/07, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: > >>This highlights a problem with the release notes process. The input is > >>HTML but they are then processed with an XML tool. Since HTML is not XML > >>we will hit this problem with many release notes. Any change folks make > >>to a release note has the potential to break the generation, even if > >>they are using valid HTML as expected. > [...] > We should talk more about whether xml or html is the right markup for > the release notes. People will want to sanity check their notes in a > browser. I don't know if most of the popular browsers will display the > xml properly. I'm afraid that if a browser displays the file as html > (even though the file says it's xml), then the browser will switch into > the forgiving mode which allows unbalanced tags and is not > case-sensitive, etc.. In any event, I think that the lint tool described > in (1) will be useful.
Well, if we want release notes to be in XML and we also want release notes to be HTML for sanity checking in a browser, that's no problem. It's called XHTML (http://www.w3.org/TR/xhtml1/) and is supported by most browsers. Bernt -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway
signature.asc
Description: Digital signature
