Copyediting Feedback: Difference between revisions

From TEIWiki
Jump to navigation Jump to search
← Older editNewer edit →

Lorand (talk | contribs)

241 edits
Lorand (talk | contribs)
241 edits
mNo edit summary
Lorand (talk | contribs)
241 edits
Recorded copyediting decisions and outstanding issues
Line 1: Line 1:
[http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices Back to GBP]
[http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices Back to GBP]


* "TEI Header" in headings; "teiHeader" as element tag; "TEI header" in text. --[[User:Lorand|Susie]]


* Copyedit the text so that we use terms like "item", "work", "tag", "element", "project", and "collection". consistently. Also check that we speak with a consistent voice: "the encoder should" vs. "the encoder must" vs. "the encoder will".
* Referencing elements and attributes: pointy brackets around element names when the word "element" is not present; monospace for both attributes and elements. I recommend against @ signs for attributes even though the main TEI Guidelines use them, because they are confusing to the uninitiated. Quotation marks are used around attribute ''values'' (not attribute names). --[[User:Lorand|Susie]]


* Copyedit throughout: "TEI Header", "teiHeader", "header", "Header".
* "OCR" (not spelled out) and "optical character recognition" (lowercase) --[[User:Lorand|Susie]]


* Standardize how we reference elements and attributes -- sometimes with pointy brackets, sometimes monospace, sometimes both, sometimes in quotes, sometimes with no differentiating characters or font style.
* throughout: <teiHeader> <tt>&lt;!-- header goes here --&gt;</tt> </teiHeader> --[[User:Lorand|Susie]]
** elements should be referenced one way (monospace?)
** attributes another (in quotes, with the @ as the preface?)


* expand abbreviations and acronyms the first time mentioned
* Try to find a more generic heading for the Alger Hiss document examples? --[[User:Lorand|Susie]]


* do we need parentheses here? "that holds chapter 3 (rather than near the bottom of the <div> that holds chapter 2)."[[User:Natasha|Natasha]]
* When review of guidelines in the wiki is finished, remove redundancies from section headings ("Level 3" and "Level 4" in subheadings under "Level 3 Examples" and "General Level 4 Recommendations and Examples"
* Copyedit through the whole text: "OCR" (not spelled out) and "Optical Character Recognition" [[User:Natasha|Natasha]] Actually, "optical character recognition" (lowercase) is OK --[[User:Lorand|Susie]]
* throughout:
**  <teiHeader> [stuff] </teiHeader>
** <teiHeader> [info] </teiHeader>
**<teiHeader>  [Source and processing information goes here] </teiHeader>
 
What do we choose? [[User:Natasha|Natasha]]
 
* <tt>&lt;!-- header goes here --&gt;</tt> --[[User:Lorand|Susie]]


[[Category:SIG:Libraries]]
[[Category:SIG:Libraries]]

Revision as of 21:53, 21 April 2009

Back to GBP

  • "TEI Header" in headings; "teiHeader" as element tag; "TEI header" in text. --Susie
  • Referencing elements and attributes: pointy brackets around element names when the word "element" is not present; monospace for both attributes and elements. I recommend against @ signs for attributes even though the main TEI Guidelines use them, because they are confusing to the uninitiated. Quotation marks are used around attribute values (not attribute names). --Susie
  • "OCR" (not spelled out) and "optical character recognition" (lowercase) --Susie
  • throughout: <teiHeader> <!-- header goes here --> </teiHeader> --Susie
  • Try to find a more generic heading for the Alger Hiss document examples? --Susie
  • When review of guidelines in the wiki is finished, remove redundancies from section headings ("Level 3" and "Level 4" in subheadings under "Level 3 Examples" and "General Level 4 Recommendations and Examples"
Retrieved from "https://wiki.tei-c.org/index.php?title=Copyediting_Feedback&oldid=6277"