staticnav.xml can be replaced by a pull from tei-c.org

[TEITechnicalCouncil]

Currently, when the Guidelines are built for deployment on tei-c.org, they're built with an additional menu block which is stored in trunk/P5/Utilities/staticnav.xml. This file needs to be updated every time the menu on tei-c.org changes. To avoid its getting out of sync, for the XSLT to pull in this page:

http://www.tei-c.org/index.xml

and use //ul[@id='udm'] directly from it.

Assigned to Sebastian because it's already on his todo list. I created the bug just so we don't lose track of it. If this can be done before the next release, we won't have to add another step to the release manager document (tcw22).

Original comment by: @martindholmes

[TEITechnicalCouncil]

This issue was originally assigned to SF user: rahtz Current user is: sebastianrahtz

[TEITechnicalCouncil]

Note: any pull of the current code would contain undefined entities ( ). Those would need to be replaced with   in the source on tei-c.org's CMS before a pull could be used in XSLT.

Original comment by: @martindholmes

[TEITechnicalCouncil]

I have added a line to the Makefile for P5 to grab the top-level index page from www.tei-c.org and turn it into XML for the XSLT to read. This should obviate the need for the staticnav.xml file.

Original comment by: @sebastianrahtz

[TEITechnicalCouncil]

I am closing this ticket now, as I think the problem is solved. The Guidelines generation for the TEI web site (distinct from the normal one for distribution) grabs the top-level page from www.tei-c.org and gathers in the <ul> with an ID of "udm". If that ever changes, this will break too, of course.

Original comment by: @sebastianrahtz

[TEITechnicalCouncil]

• status: open --> closed-fixed

Original comment by: @sebastianrahtz