Re: XHTML

>> Is there any objection to specify XHTML Transitional in doctype of 
>> app-personality jsp pages? Or even XHTML Strict?
>
>
> I don't know enough to object or not object  :-).  I assume this will 
> affect browser compatibility....can you please detail the pros and cons?
>
Main point: to insure future compatibility.

XHTML 1.0 is only a reformulation of HTML 4 in XML 1.0. The difference 
between the XHTML 1.0 flavors or XHTML 1.1 is their support for older 
depreciated HTML tags.

About XHTML 1.0 Transitional: a priori no issue, only strict writting of 
tags.

About XHTML 1.0 Strict: some more changes, but not so more. Mainly 
remove deprecated things and use only CSS styles.

About XHTML 1.1 :  see 
http://www.w3.org/TR/xhtml11/changes.html#a_changes. Doesn't seem to be 
a big issue.

About backward browser compatibility:
- XHTML 1.0 is backward compatible with HTML when served as text/html.
- Some precautions must be taken for old browsers. Mainly with empty 
elements, put a white space before the slash like in <br /> (bad 
exemple: br shouldn't be used at all...almost not at all!)
- The initial default values for some of the supplied tags: body, |p|, 
|ol, ul, dl| and |h1 to h6| come with pre-defined margin and padding 
values that differ between browsers.
- CSS won't be fully rendered.

But the last two points are not specific to XHTML.

On general issues about compatibility, see 
http://vasa.communitypoint.org/compatibility.html  and  
http://en.wikipedia.org/wiki/XHTML

I started to check HTML validation (http://validator.w3.org/)for 
app-personality/app-register/app-crud.While I'm doing it, I prefer to do 
it with XHTML 1.0, at least Transitional.

May be it should be possible to offer the choice, with some parameter in 
app-personality or clnt-struts?

> On a related note, I saw you checked in some configuration (in web.xml 
> snippets) to configure Jasper to trim spaces in the generated HTML. 
> Even though I personally like that, since I use Tomcat as well, this 
> configuration will mess up everybody that is using containers other 
> than Tomcat.  I'd recommend commenting the config, but keeping it as 
> an example.  You can simply put the configuration in your own project, 
> and the maven build system would pick it up just as well.

OK. I'll commited it.

Pierre


http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com