Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#42 origDate without attributes tei.datable

closed
Syd Bauman
5
2006-02-07
2004-09-30
Torsten Schassan
No

In 1.2 it says, that <origDate> has no other attributes
than those globally available. In the formal
description there's tei.datable listed.

Besides this: when msHeading was removed, where there
any suggestions where to put the information of
origDate instead? As phrase-level element it can be
used everywhere but where do I find (and put) the
information about "the whole manuscript", the way many
catalogues provide the information? (And German
catalogues HAVE TO!)

Discussion

  • Logged In: YES
    user_id=1125795

    PS: The same question as for origDate arises for origPlace.
    origDate and origPlace might be put in <origin>, but how to
    deal with multiple origDates in a document, e.g. in
    history/origin and in bindingDesc and in msPart?

    And where goes <textLang>?

     
  • Logged In: NO

    looks like a bug to me -- Chris

     
  • Lou Burnard
    Lou Burnard
    2005-08-30

    • assigned_to: nobody --> sbauman
     
  • Lou Burnard
    Lou Burnard
    2005-08-30

    Logged In: YES
    user_id=1021146

    I think the first point has been resolved in the most recent
    stylesheet but please check.

    Matthew's working paper comments on the second point. I am
    not closing this ticket, because I am not confident that we
    have a proper answer as yet.

     
  • Lou Burnard
    Lou Burnard
    2006-02-07

    • status: open --> closed
     
  • Lou Burnard
    Lou Burnard
    2006-02-07

    Logged In: YES
    user_id=1021146

    Fixed in release 0.3