Re: [tei-council] HTML rendering on TEI-C website (was Re: 2.9.0 in Vault)

I agree that it would be nice if everything was also valid XML. What we have now should pretty much be that way even though it uses self-closing tags that aren't actually valid HTML5. If I fix those, then the result isn't valid XML any more. Given the web is going in the HTML5 direction and not the XML direction, and given that I can't figure out what part of OpenCMS actually creates the bad code, I'm going to leave it as it is. :) On 11/7/15 7:55 PM, Martin Holmes wrote:

I don't really see any downside to having pages which are both valid HTML5 and are XML. That's what I tend to do myself. I find it cleaner to be able to specify an XHTML namespace for output in a context where I'm dealing with lots of namespaces (TEI, TEIX, XSL, XInclude) rather than producing HTML without a namespace. That's what we do in the Guidelines pages too.

But your call -- as long as it's valid, I guess it doesn't matter.

Cheers, Martin

On 15-11-07 04:03 PM, Kevin Hawkins wrote:

...

If I follow the link at the top of that editor's draft to "latest published version", I get a working group note with a giant prominent note in the "status of the document" section saying:

"Beware. This specification is no longer in active maintenance and the HTML Working Group does not intend to maintain it further."

I haven't been keeping up with things in the HTML5 world, but I wonder if polyglot markup is a dead end? I mean, so is the TEI-C website, but I think I'm more inclined to stick with something that is at least actively maintained. More to the point, I can't imagine us processing the HTML output of the TEI-C website with an XML tool, or trying to embed something in another namespace that isn't part of HTML5. What do you think?

On 11/7/15 5:23 PM, Martin Holmes wrote:

...

HI Kevin,

I think the ideal is not plain HTML5 but polyglot markup, as defined here:

http://dev.w3.org/html5/html-polyglot/html-polyglot.html

That allows explicit namespaces and processing by XML tools, while still being HTML5-compatible.

Cheers, Martin

On 15-11-07 02:55 PM, Kevin Hawkins wrote:

...

I've updated the JSP code that drives the formation of the top of the HTML documents to follow HTML5 practices. Unfortunately, there are still some self-closing tags being created in the HTML output which trip up the W3C HTML5 validation, and I can't determine where these are coming from. Still, I think this situation is now improved.

On 11/2/15 9:03 AM, Martin Holmes wrote:

...

Hi Kevin,

I think replacing the doctype with the HTML5 one, and fixing any of the HTML inconsistencies (I think they're trivial) would really help.

Cheers, Martin

On 15-11-02 06:37 AM, Kevin Hawkins wrote:

...

Yeah, when that XSLT was developed, it may have produced XHTML output, but we've tweaked it since then, such as by adding the Twitter chicklet in the footer.

Till we get a new TEI website, would it help if I removed the DOCTYPE and html@xmlns? I would check a few pages to make sure that this introduce any significant change in how browsers render pages.

K.

On 11/2/15 6:43 AM, Martin Holmes wrote: > That page on the site: > > http://www.tei-c.org/Guidelines/P5/ > > is a horrible mess; it claims to be XHTML transitional but > because of > the likes of Twitter stuff embedded in it, it has HTML5 content. I > don't > see how it could ever validate without being rewritten as HTML5 (as > the > Guidelines pages have been). > > I think the reason nobody has gone near this stuff recently is that > we've been hoping for the replacement for OpenCMS to come along; if > that's not in prospect during the next year or so, we should > probably > make an effort to refactor the XSLT on the website. > > Cheers, > Martin > > On 15-11-02 04:01 AM, Kevin Hawkins wrote: >> Thanks to whoever added 2.9.1 to >> http://www.tei-c.org/Guidelines/P5/#previous . Is the next release >> expected in 2015, or should that be listed as 2016? >> >> The extra space character that Fabio mentions is a bug in the XSLT >> that >> produces the HTML pages ( http://www.tei-c.org/xsl/tei2.xsl ). If >> anyone can tell me how to fix it, please let me know. >> >> Kevin >> >> On 10/9/15 1:30 PM, Fabio Ciotti wrote: >>> It looks ok to me as well. For whoever is going to edit the page >>> ther >>> seem >>> to bne an extraspace after the point in the first line of the page >>> f >>> >>> 2015-10-09 20:14 GMT+02:00 Martin Holmes : >>> >>>> Looks good to me, with a quick click-around. It's not linked on >>>> the >>>> Vault >>>> page yet: >>>> >>>> http://www.tei-c.org/Guidelines/P5/#previous >>>> >>>> Cheers, >>>> Martin >>>> >>>> >>>> On 15-10-09 11:11 AM, Hugh Cayless wrote: >>>> >>>>> Can everyone who’s able take a look at >>>>> http://www.tei-c.org/Vault/P5/2.9.0/doc/tei-p5-doc/en/html/ < >>>>> http://www.tei-c.org/Vault/P5/2.9.0/doc/tei-p5-doc/en/html/> It >>>>> looks ok >>>>> to me… >>>>> >>>>> Need to step away while I go pick the kids up, but should be >>>>> able to >>>>> resume in an hour if I don’t hear screams from anyone. >>>>> >>>>> -- >>>> tei-council mailing list >>>> tei-council@lists.tei-c.org >>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council >>>> >>>> PLEASE NOTE: postings to this list are publicly archived >>>> >>> >>> >>>