#231 how to handle forme work

AMBER
closed-wont-fix
Tite (10)
5(default)
2014-06-30
2010-09-16
No

Tite does not include <fw> but also does not give guidance on how to handle running headers and footers. Should these be included in the markup or discarded? If they are included, how should they be encoded? (AccessTEI is currently including these, creating texts using <divN type="page"><head><!-- running header info here -->, with a <divN> at the beginning of each page!)

Discussion

  • Lou Burnard

    Lou Burnard - 2010-09-17

    Use <fw>, obviously, if it's going to be captured at all. Using <div> is complete madness, as it will screw up the structuring of the text entirely. Unless you want to structure the text as a sequence of <page> elements, of course!

     
  • Kevin Hawkins

    Kevin Hawkins - 2010-09-20

    AccessTEI is changing their practice to no longer include <divN type="page">.

     
  • Kevin Hawkins

    Kevin Hawkins - 2011-02-27

    Will return to this once tickets 3136934, 3136935 3136936, and 3164403 are resolved, bringing canonical and Apex versions of Tite into alignment.

     
  • Kevin Hawkins

    Kevin Hawkins - 2011-02-27
    • status: open --> open-postponed
     
  • James Cummings

    James Cummings - 2013-11-10
    • Group: --> AMBER
    • Priority: 5 --> 5(default)
     
  • James Cummings

    James Cummings - 2013-11-10

    Setting as AMBER

     
  • Lou Burnard

    Lou Burnard - 2014-06-30

    Council reviewed this at June 2014 meeting. Agreed that if you dont have an <fw> element you cannot encode forme-work like material. If you want to encode such material, you should add <fw> to tite.

     
  • Lou Burnard

    Lou Burnard - 2014-06-30
    • status: open-postponed --> closed-wont-fix
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks