Notes - Revision history

194.171.144.181: Resolved issue.

2018-02-08T08:59:24Z

Resolved issue.

2018-01-23T11:44:27Z

Clarify issue

2018-01-23T10:42:09Z

Resolved issue.

2018-01-23T10:37:37Z

2018-01-23T10:27:28Z

Resolved issue.

2018-01-23T09:49:30Z

Correction

2018-01-23T09:41:56Z

Resolved issue.

2018-01-12T10:07:51Z

‎Discussion

2017-12-12T13:17:07Z

Add comment

2017-12-12T12:24:08Z

‎Discussion

@@ Line 31: / Line 31: @@
 ===Discussion===
 * Define when to use <ref>, <ptr>, <anchor>? The TEI Gyudelines say:
 ** <ptr> (pointer) defines a pointer to another location.

← Older revision		Revision as of 11:44, 23 January 2018
Line 36:		Line 36:
	** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)		** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

−	* Define when to use <ref>, <ptr>, <anchor>?	+	* 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.

@@ 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
 * ...
 ===Restjes===
@@ Line 32: / Line 37: @@
 * Define when to use <ref>, <ptr>, <anchor>?

← Older revision		Revision as of 10:37, 23 January 2018
Line 32:		Line 32:

	* Define when to use <ref>, <ptr>, <anchor>?		* Define when to use <ref>, <ptr>, <anchor>?
−
−	* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering

	* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.		* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

@@ Line 30: / Line 30: @@
 ** q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
 ** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)
 * Define when to use <ref>, <ptr>, <anchor>?

@@ Line 34: / Line 34: @@
 * Define when to use <ref>, <ptr>, <anchor>?
 * Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering
 * Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

← Older revision		Revision as of 10:07, 12 January 2018
Line 38:		Line 38:

	* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering		* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering
		+
		+	* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

← Older revision		Revision as of 13:17, 12 December 2017
Line 37:		Line 37:
	* Can <sic> and <corr> be rendered standalone?		* Can <sic> and <corr> be rendered standalone?

−	* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML	+	* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering

← Older revision		Revision as of 12:24, 12 December 2017
Line 36:		Line 36:

	* Can <sic> and <corr> be rendered standalone?		* Can <sic> and <corr> be rendered standalone?
		+
		+	* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML