Difference between revisions of "Notes"
(Created page with "===Principles=== (To be realized step by step) * All XML documentation on this wiki * Describe general decisions only once, project-specific changes on project-level pages * E...") |
(Resolved issue.) |
||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 5: | Line 5: | ||
* Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace | * Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace | ||
* ... | * ... | ||
| + | |||
| + | ===Whitespace=== | ||
| + | |||
| + | When processing all whitespace (like \n\t\t) may be collapsed to a single space character without loss of meaning. If a document is to be re-edited by the author, (s)he will appreciate retrieval with whitespace as it was stored. | ||
| + | |||
| + | |||
| + | ===Restjes=== | ||
| + | |||
| + | For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced. | ||
| + | |||
| + | |||
| + | ---------------- | ||
| + | |||
| + | |||
| + | For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level. | ||
| + | |||
| + | These references may look like: | ||
| + | |||
| + | At paragraph level (in this example there are two source paragraphs): | ||
| + | <pre><p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3"></pre> | ||
| + | |||
| + | At term level: | ||
| + | <pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre> | ||
| + | |||
| + | |||
| + | ===Discussion=== | ||
| + | * Define when to use <ref>, <ptr>, <anchor>? The TEI Gyudelines say: | ||
| + | ** <ptr> (pointer) defines a pointer to another location. | ||
| + | ** <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. | ||
| + | ** <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. | ||
| + | In the ePistolarium <ptr> is not used, <ref> is sparingly used for annotation of Bible texts, and <anchor> is used for specifying the target of notes. | ||
Latest revision as of 09:59, 8 February 2018
Contents
Principles
(To be realized step by step)
- All XML documentation on this wiki
- Describe general decisions only once, project-specific changes on project-level pages
- Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
- ...
Whitespace
When processing all whitespace (like \n\t\t) may be collapsed to a single space character without loss of meaning. If a document is to be re-edited by the author, (s)he will appreciate retrieval with whitespace as it was stored.
Restjes
For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.
For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.
These references may look like:
At paragraph level (in this example there are two source paragraphs):
<p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3">
At term level:
which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.
Discussion
- Define when to use <ref>, <ptr>, <anchor>? The TEI Gyudelines say:
- <ptr> (pointer) defines a pointer to another location.
- <ref> (reference) defines a reference to another location, possibly modified by additional text or comment.
- <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
In the ePistolarium <ptr> is not used, <ref> is sparingly used for annotation of Bible texts, and <anchor> is used for specifying the target of notes.
