Menu

#728 lamenting the passing of SGML SDATA

AMBER
open
None
5(default)
2015-05-28
2015-02-18
No

CH-LanguagesCharacterSets.xml
/div/div[2]/div[6]/div[2]/head[1]

Non-Unicode Characters in XML Documents

I think everything in this section is correct, but it will not help much, only mystify. Much of the section is given to a lamentation of the passing of SGML SDATA type ("a transparent use of a CER" at the end echoes this), but this will mean nothing to most TEI users (indeed, it meant nothing to me until I looked it up). That parsed entity references disappear as references when resolved (and that the result of this may be both pure character data and markup/PIs) needs to be said, but not in a section dealing with the problem of non-Unicode characters.

Discussion

  • Hugh A. Cayless

    Hugh A. Cayless - 2015-03-12

    Assigning to Stefanie for review.

     
  • Hugh A. Cayless

    Hugh A. Cayless - 2015-03-12
    • assigned_to: Stefanie Gehrke
     
  • Stefanie Gehrke

    Stefanie Gehrke - 2015-05-28

    as the labeling states, this "bug" is not about the content itself, it is about the way the content is presented. The guideline's paragraph about Non-Unicode Characters in XML Documents (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CH.html#D4-45-2) was understood as "a look behind". This seems to be an important feedback.

    => first step : add what the acronyms used in the text stand for ?

     
  • Jens Østergaard Petersen

    I did not mean this as a comment on the presentation; rather, I doubt the relevance of the contents. The Guidelines are about guiding users, not about explaining things that might have been relevant a decade or more ago.