2.9.0 in Vault

Hugh Cayless

9 Oct 2015 9 Oct '15

8:11 p.m.

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.

Show replies by date

Martin Holmes

9 Oct 9 Oct

8:14 p.m.

New subject: [tei-council] 2.9.0 in Vault

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.

Hugh Cayless

8:17 p.m.

New subject: [tei-council] 2.9.0 in Vault

Don’t believe I have CMS editing privs. So you or James will have to do that when it’s over. Anyway, shouldn’t link it until we’re done.

...

On Oct 9, 2015, at 14:14 , Martin Holmes wrote:

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

Fabio Ciotti

8:30 p.m.

New subject: [tei-council] 2.9.0 in Vault

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

-- Fabio Ciotti Dipartimento di Studi letterari, Filosofici e Storia dell’arte Università di Roma Tor Vergata President "Associazione Informatica Umanistica Cultura Digitale" (AIUCD)

Kevin Hawkins

2 Nov 2 Nov

1:01 p.m.

New subject: [tei-council] 2.9.0 in Vault

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

Martin Holmes

1:43 p.m.

New subject: [tei-council] 2.9.0 in Vault

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

Kevin Hawkins

3:37 p.m.

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

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

Martin Holmes

4:03 p.m.

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

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

Kevin Hawkins

7 Nov 7 Nov

11:55 p.m.

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

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

Martin Holmes

8 Nov 8 Nov

12:23 a.m.

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

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 >

Kevin Hawkins

1:03 a.m.

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

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 >> > > >

Martin Holmes

2:55 a.m.

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

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 >>> >> >> >>

Kevin Hawkins

9 Nov 9 Nov

7:13 p.m.

New subject: [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 >>>> >>> >>> >>>

Lou Burnard

9 Oct 9 Oct

8:33 p.m.

New subject: [tei-council] 2.9.0 in Vault

Yup, the HTML looks fine to me too. (I note by the way that the drop down next to the search box at top left still allows you to search the P4 Guidelines. Doesn't work though.) I can probably hack the CMS site if needed, but no doubt Kevin will leap into action in due course. On 09/10/15 19:14, Martin Holmes wrote:

...

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.

Martin Holmes

8:38 p.m.

New subject: [tei-council] 2.9.0 in Vault

This is not something Kevin can solve; that P4 search is not part of the main site (the equivalent search box, which is on the right on other pages, doesn't have it). This is in the Stylesheets that build the Guidelines, and is exactly the sort of thing we don't want to notice on release day. :-) Cheers, Martin On 15-10-09 11:33 AM, Lou Burnard wrote:

...

Yup, the HTML looks fine to me too.

(I note by the way that the drop down next to the search box at top left still allows you to search the P4 Guidelines. Doesn't work though.)

I can probably hack the CMS site if needed, but no doubt Kevin will leap into action in due course.

On 09/10/15 19:14, Martin Holmes wrote:

...
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.

Stefan Majewski

8:47 p.m.

New subject: [tei-council] 2.9.0 in Vault

I clicked through it rather extensively, looks good to me. One thing I noticed, again actually is that the language switch links aren't particularly useful, but I think that has never been much different, right? Well done, thanks for preparing this. Kind regards, Stefan Am 09.10.2015 8:33 nachm. schrieb "Lou Burnard" < lou.burnard@retired.ox.ac.uk>:

...

Yup, the HTML looks fine to me too.

(I note by the way that the drop down next to the search box at top left still allows you to search the P4 Guidelines. Doesn't work though.)

I can probably hack the CMS site if needed, but no doubt Kevin will leap into action in due course.

On 09/10/15 19:14, Martin Holmes wrote:

...
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

Raffaele Viglianti

9:41 p.m.

New subject: [tei-council] 2.9.0 in Vault

Looks good, couldn't catch anything unusual Raff On Fri, Oct 9, 2015 at 2:47 PM, Stefan Majewski wrote:

...

I clicked through it rather extensively, looks good to me. One thing I noticed, again actually is that the language switch links aren't particularly useful, but I think that has never been much different, right?

Well done, thanks for preparing this.

Kind regards, Stefan Am 09.10.2015 8:33 nachm. schrieb "Lou Burnard" < lou.burnard@retired.ox.ac.uk>:

...
Yup, the HTML looks fine to me too.

(I note by the way that the drop down next to the search box at top left still allows you to search the P4 Guidelines. Doesn't work though.)

I can probably hack the CMS site if needed, but no doubt Kevin will leap into action in due course.

On 09/10/15 19:14, Martin Holmes wrote:

...
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 -- 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

Syd Bauman

10:04 p.m.

New subject: [tei-council] 2.9.0 in Vault

Looks overall good to me. Although Lou's right about the P4 search, it's been there all along, right? So 2.9.0 is no worse than 2.8.1 in this respect. I presume there is nothing we can do about the version number, in this case "e6e2f86". The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.) P.S. Hugh -- not that I'm likely to be much help with an eXist problem, if you don't give us more details, none of us can help you out, here. :-|

Hugh Cayless

10:11 p.m.

New subject: [tei-council] 2.9.0 in Vault

I can’t be very specific, I’m afraid. Here’s the output: curl: (22) The requested URL returned error: 401 curl: (22) The requested URL returned error: 401 The eXist config seems to have changed without the script being updated. Someone with OpenCMS credentials will need to fix the menus. Sorry, I was under the impression that was already either done or underway. There’s nothing to be done about the revision number, because that’s the revision number (or the first few digits anyway).

...

On Oct 9, 2015, at 16:04 , Syd Bauman wrote:

Looks overall good to me. Although Lou's right about the P4 search, it's been there all along, right? So 2.9.0 is no worse than 2.8.1 in this respect.

I presume there is nothing we can do about the version number, in this case "e6e2f86".

The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

P.S. Hugh -- not that I'm likely to be much help with an eXist problem, if you don't give us more details, none of us can help you out, here. :-| -- 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

Hugh Cayless

10:14 p.m.

New subject: [tei-council] 2.9.0 in Vault

I think the port # for eXist is wrong in the script, but when I change it, it still fails. Is there a username/password on the db now?

...

On Oct 9, 2015, at 16:11 , Hugh Cayless wrote:

I can’t be very specific, I’m afraid. Here’s the output:

curl: (22) The requested URL returned error: 401 curl: (22) The requested URL returned error: 401

The eXist config seems to have changed without the script being updated.

Someone with OpenCMS credentials will need to fix the menus. Sorry, I was under the impression that was already either done or underway. There’s nothing to be done about the revision number, because that’s the revision number (or the first few digits anyway).

...
On Oct 9, 2015, at 16:04 , Syd Bauman wrote:

Looks overall good to me. Although Lou's right about the P4 search, it's been there all along, right? So 2.9.0 is no worse than 2.8.1 in this respect.

I presume there is nothing we can do about the version number, in this case "e6e2f86".

The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

P.S. Hugh -- not that I'm likely to be much help with an eXist problem, if you don't give us more details, none of us can help you out, here. :-| -- 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

Martin Holmes

10:43 p.m.

New subject: [tei-council] 2.9.0 in Vault

There is a username and password, which Peter put in place. It is stored in a config file: "This will update the eXist-db used by Roma. The script takes no parameters but expects a configuration file in the user’s home directory at ~/etc/tei-exist.conf with the appropriate paths and credentials. For the main server at tei-c.org this should already be set and no adjustments should be needed." Presumably you were following TCW 22 and running this on tei-c.org? If so, then we have a bug. Cheers, Martin On 15-10-09 01:14 PM, Hugh Cayless wrote:

...

I think the port # for eXist is wrong in the script, but when I change it, it still fails. Is there a username/password on the db now?

...
On Oct 9, 2015, at 16:11 , Hugh Cayless wrote:

I can’t be very specific, I’m afraid. Here’s the output:

curl: (22) The requested URL returned error: 401 curl: (22) The requested URL returned error: 401

The eXist config seems to have changed without the script being updated.

Someone with OpenCMS credentials will need to fix the menus. Sorry, I was under the impression that was already either done or underway. There’s nothing to be done about the revision number, because that’s the revision number (or the first few digits anyway).

...
On Oct 9, 2015, at 16:04 , Syd Bauman wrote:

Looks overall good to me. Although Lou's right about the P4 search, it's been there all along, right? So 2.9.0 is no worse than 2.8.1 in this respect.

I presume there is nothing we can do about the version number, in this case "e6e2f86".

The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

P.S. Hugh -- not that I'm likely to be much help with an eXist problem, if you don't give us more details, none of us can help you out, here. :-| -- 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

Martin Holmes

10:45 p.m.

New subject: [tei-council] 2.9.0 in Vault

The conf file is there and it has the credentials in it, as well as the port. Cheers, Martin On 15-10-09 01:14 PM, Hugh Cayless wrote:

...

I think the port # for eXist is wrong in the script, but when I change it, it still fails. Is there a username/password on the db now?

...
On Oct 9, 2015, at 16:11 , Hugh Cayless wrote:

I can’t be very specific, I’m afraid. Here’s the output:

curl: (22) The requested URL returned error: 401 curl: (22) The requested URL returned error: 401

The eXist config seems to have changed without the script being updated.

Someone with OpenCMS credentials will need to fix the menus. Sorry, I was under the impression that was already either done or underway. There’s nothing to be done about the revision number, because that’s the revision number (or the first few digits anyway).

...
On Oct 9, 2015, at 16:04 , Syd Bauman wrote:

Looks overall good to me. Although Lou's right about the P4 search, it's been there all along, right? So 2.9.0 is no worse than 2.8.1 in this respect.

I presume there is nothing we can do about the version number, in this case "e6e2f86".

The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

P.S. Hugh -- not that I'm likely to be much help with an eXist problem, if you don't give us more details, none of us can help you out, here. :-| -- 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

Martin Holmes

10:40 p.m.

New subject: [tei-council] 2.9.0 in Vault

The links to SF are created as part of the build process too. They could be fixed manually in Open CMS, but it's not the best thing to do. We should fix this (and the P4 search thing) before going live with a new version. Cheers, Martin On 15-10-09 01:11 PM, Hugh Cayless wrote:

...

I can’t be very specific, I’m afraid. Here’s the output:

curl: (22) The requested URL returned error: 401 curl: (22) The requested URL returned error: 401

The eXist config seems to have changed without the script being updated.

Someone with OpenCMS credentials will need to fix the menus. Sorry, I was under the impression that was already either done or underway. There’s nothing to be done about the revision number, because that’s the revision number (or the first few digits anyway).

...
On Oct 9, 2015, at 16:04 , Syd Bauman wrote:

Looks overall good to me. Although Lou's right about the P4 search, it's been there all along, right? So 2.9.0 is no worse than 2.8.1 in this respect.

I presume there is nothing we can do about the version number, in this case "e6e2f86".

The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

P.S. Hugh -- not that I'm likely to be much help with an eXist problem, if you don't give us more details, none of us can help you out, here. :-| -- 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

Kevin Hawkins

10:11 p.m.

New subject: [tei-council] 2.9.0 in Vault

On 10/9/15 3:04 PM, Syd Bauman wrote:

...

The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

Ah drats, both Martin and I missed that when updating the TEI website. The file that drives the menus is stored in a strange place that I can never remember but is stored in the webmaster documentation, which is in Google Docs, which is currently unavailable. Once it's back, I'll update those links so that all pages loaded by OpenCMS will be fixed. I believe the P5 build process grabs a snapshot of the OpenCMS-created menu to use when creating the static files for the release, so I fear that we're too late to fix this in the 2.9.0 release without doing a global search-and-replace in what Hugh has generated. Kevin

Kevin Hawkins

10:59 p.m.

New subject: [tei-council] 2.9.0 in Vault

I've now updated the dynamically generated navigation menu so that all pages generated by OpenCMS have the right menu. However, as I explained below, pages under http://www.tei-c.org/release/ are not affected by this change. That includes the in-progress 2.9.0 release. On 10/9/15 3:11 PM, Kevin Hawkins wrote:

...

On 10/9/15 3:04 PM, Syd Bauman wrote:

...
The links to "Bug Reports" and "Feature Requests" under the "Support" menu item still link to Sourceforge. Is that what we want? (The link to "Bug Reports, Feature Requests, etc." on the index page links to GitHub.)

Ah drats, both Martin and I missed that when updating the TEI website. The file that drives the menus is stored in a strange place that I can never remember but is stored in the webmaster documentation, which is in Google Docs, which is currently unavailable. Once it's back, I'll update those links so that all pages loaded by OpenCMS will be fixed.

I believe the P5 build process grabs a snapshot of the OpenCMS-created menu to use when creating the static files for the release, so I fear that we're too late to fix this in the 2.9.0 release without doing a global search-and-replace in what Hugh has generated.

Kevin

3293

Age (days ago)

3324

Last active (days ago)

List overview

Download

24 comments

8 participants

participants (8)

Fabio Ciotti
Hugh Cayless
Kevin Hawkins
Lou Burnard
Martin Holmes
Raffaele Viglianti
Stefan Majewski
Syd Bauman