Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-17 Thread Raphael Ritz
Laurence Rowe wrote: [..] I don't think we'll persuade libxml2 to implement it the as xhtml output until the standard is finalised, it's already been changed from in the last few months. More on this here. http://www.contentwithstyle.co.uk/content/xslt-and-html-5-problems I'm probably mi

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Laurence Rowe
On 16 March 2010 23:37, Alexander Limi wrote: > On Tue, Mar 16, 2010 at 4:27 PM, Laurence Rowe wrote: >> >> Unfortunately it's not possible to generate that from an xslt >> processor / libxml2 / lxml, and in order to trigger the xhtml output >> mode (so you get with the space) you need to specif

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Alexander Limi
On Tue, Mar 16, 2010 at 4:27 PM, Laurence Rowe wrote: > Unfortunately it's not possible to generate that from an xslt > processor / libxml2 / lxml, and in order to trigger the xhtml output > mode (so you get with the space) you need to specify an xhtml > 1.0 doctype to be output. It seems quite

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Laurence Rowe
Unfortunately it's not possible to generate that from an xslt processor / libxml2 / lxml, and in order to trigger the xhtml output mode (so you get with the space) you need to specify an xhtml 1.0 doctype to be output. It seems quite likely with deco / blocks / xdv that we will have an lxml based

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Alexander Limi
Right, I don't see a reason to do that, though — it doesn't buy us anything. The reason the HTML5 doctype is simply: …is that it's the shortest possible string that will trigger strict/standards parsing (ie. not quirks mode) in all browsers, including IE6. On Tue, Mar 16, 2010 at 3:34 PM, Lau

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Laurence Rowe
It is listed as an "obsolete permitted doctype string" http://dev.w3.org/html5/spec/Overview.html#obsolete-permitted-doctype-string - i.e. we can lie about the doctype. I'm not sure why xhtml 1.0 transitional is not allowed. Laurence On 16 March 2010 22:18, Alexander Limi wrote: > The way it wor

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Alexander Limi
The way it works is that you can use the XHTML "spelling" (ie. closing your tags), but you serve it up as normal HTML. http://wiki.whatwg.org/wiki/FAQ#Should_I_close_empty_elements_with_.2F.3E_or_.3E.3F There's no Strict or similar thing in HTML5, AFAIK. (There is also something informally refer

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Laurence Rowe
By my reading of the html 5 draft, it would seem conformant with the (html5) spec to serve a document with a text/html Content-Type but an XHTML Strict doctype. On 16 March 2010 20:14, Alexander Limi wrote: > What does transitional doctype have to do with geolocation? > > (and XHTML STRICT is a p

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Alexander Limi
What does transitional doctype have to do with geolocation? (and XHTML STRICT is a problem, since it implies serving with XML MIME type, which IE doesn't handle, so that's unlikely to happen) On Tue, Mar 16, 2010 at 12:48 PM, Veda Williams wrote: > This brings up the question of when we're mov

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Wichert Akkerman
On 3/16/10 18:40 , Alexander Limi wrote: On Tue, Mar 16, 2010 at 4:45 AM, Wichert Akkerman mailto:wich...@wiggy.net>> wrote: I'ld like to see a list of pros and cons of using HTML 5 as well. I am quite worried by the lack of proper support in existing browsers. None of them implement

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Alexander Limi
On Tue, Mar 16, 2010 at 4:45 AM, Wichert Akkerman wrote: > I'ld like to see a list of pros and cons of using HTML 5 as well. I am > quite worried by the lack of proper support in existing browsers. None of > them implement any of the existing HTML standards properly, and I fear that > switching t

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Alexander Limi
On Tue, Mar 16, 2010 at 4:45 AM, Wichert Akkerman wrote: > I'ld like to see a list of pros and cons of using HTML 5 as well. I am > quite worried by the lack of proper support in existing browsers. None of > them implement any of the existing HTML standards properly, and I fear that > switching t

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Hanno Schlichting
On Tue, Mar 16, 2010 at 12:45 PM, Wichert Akkerman wrote: > I'ld like to see a list of pros and cons of using HTML 5 as well. I am quite > worried by the lack of proper support in existing browsers. None of them > implement any of the existing HTML standards properly, and I fear that > switching t

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Wichert Akkerman
On 3/16/10 12:34 , Laurence Rowe wrote: On 15 March 2010 09:13, Alexander Limi wrote: 2010/3/12 Hanno Schlichting On Fri, Mar 12, 2010 at 5:39 PM, Laurence Rowe wrote: On 12 March 2010 15:07, Hanno Schlichting wrote: Currently listed for Plone 4.x are things like: ... - Well formed, val

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-16 Thread Laurence Rowe
On 15 March 2010 09:13, Alexander Limi wrote: > 2010/3/12 Hanno Schlichting >> >> On Fri, Mar 12, 2010 at 5:39 PM, Laurence Rowe wrote: >> > On 12 March 2010 15:07, Hanno Schlichting wrote: >> >> Currently listed for Plone 4.x are things like: >> > ... >> >> - Well formed, valid XHTML (as a fou

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-15 Thread Eric Steele
On Mar 15, 2010, at 4:58 PM, Nate Aune wrote: > What about Amberjack for self-guided tours/help? > http://dev.plone.org/plone/ticket/9324 > > Is that still on the roadmap for landing in Plone 4.1? It certainly is if someone resubmits it. I asked the implementers to continue developing it outsi

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-15 Thread Hanno Schlichting
On Mon, Mar 15, 2010 at 4:58 PM, Nate Aune wrote: > On Fri, Mar 12, 2010 at 11:07 AM, Hanno Schlichting > wrote: >> >> - ... tons of new or better features > > What about Amberjack for self-guided tours/help? > http://dev.plone.org/plone/ticket/9324 The entire list is at http://dev.plone.org/plo

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-15 Thread Nate Aune
On Fri, Mar 12, 2010 at 11:07 AM, Hanno Schlichting wrote: > Currently listed for Plone 4.x are things like: > > - Include plone.app.registry > - Include z3c.form > - Improved commenting infrastructure > - Improving the event type with recurrence, etc. > - New roles : Webmaster/site administrator

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-15 Thread Hanno Schlichting
On Mon, Mar 15, 2010 at 10:13 AM, Alexander Limi wrote: > We could also take a page from how Firefox is looking to change their > release management strategy, ie. landing stuff that has only infrastructural > impact in a 4.x release (out-of-process plugins in FF's example, which will > land in the

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-15 Thread Alexander Limi
2010/3/12 Hanno Schlichting > On Fri, Mar 12, 2010 at 5:39 PM, Laurence Rowe wrote: > > On 12 March 2010 15:07, Hanno Schlichting wrote: > >> Currently listed for Plone 4.x are things like: > > ... > >> - Well formed, valid XHTML (as a foundation for easier theming via xdv) > > That's really go

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-12 Thread Hanno Schlichting
On Fri, Mar 12, 2010 at 5:39 PM, Laurence Rowe wrote: > On 12 March 2010 15:07, Hanno Schlichting wrote: >> Currently listed for Plone 4.x are things like: > ... >> - Well formed, valid XHTML (as a foundation for easier theming via xdv) > > Just to note that xdv uses the HTMLParser which is reall

Re: [Framework-Team] Plone 5 - rough roadmap

2010-03-12 Thread Laurence Rowe
On 12 March 2010 15:07, Hanno Schlichting wrote: > Currently listed for Plone 4.x are things like: ... > - Well formed, valid XHTML (as a foundation for easier theming via xdv) Just to note that xdv uses the HTMLParser which is really very tolerant of badly formed markup (an earlier problem with