TEIWiki - User contributions [en]

HTML5 Microdata TEI Serialization

2011-06-10T05:27:34Z

Brettz9: /* Advantages of editing original texts in TEI XML (or use cases for sometimes converting such TEI-enriched HTML5 to TEI XML) */ +XBL

[http://www.w3.org/TR/microdata/ HTML5 Microdata specification] offers the ability to add semantics to HTML, including the ability to specify a particular namespace (in HTML5, called an "item type"), offering the potential for TEI to be encoded in HTML5 without loss of any semantic information.

A collaboration between Google, Microsoft, and Yahoo, [http://schema.org Schema.org], is pushing for adoption over other offered alternatives such as RDFa or Microformats, citing the complexity of the former and the lack of open extensibility (namespacing) of the latter, and with their ability to offer search tools (as [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 Google's]) to take advantage of this information, it seems increasingly likely that this may be the ultimate means of encoding enhanced semantics in regular HTML, thereby offering a compelling argument for allowing TEI texts to be offered in such a serialization.

The question then becomes, when and where to use TEI XML and when and where (and how) to use such a serialization (especially once a particular approach for serializing may be formalized).

Note that in discussing the advantages of one format over the other, using one in one environment does not preclude the possibility of converting between the two formats. For example, one might create texts in TEI XML (including inside web-based editors), share them as HTML5 Microdata to take advantage of search engine discoverability, collaborative HTML editing tools which only are built to recognize HTML (e.g., wikis), and/or convert HTML5 TEI-based Microdata texts found on the web or in such HTML tools back into TEI for convenience of markup editing or manipulation. It would be possible to ensure lossless conversions in either direction (assuming the HTML is not enriched with features not used in TEI such as form controls), so there is little disadvantage in providing such a serialization.

Still, the entries below highlight environments and conditions under which preferring one over the other would be advantageous.

==Advantages of editing original texts in TEI XML (or use cases for sometimes converting such TEI-enriched HTML5 to TEI XML)==
* Existing tools for TEI such as Roma and the default XSL stylesheets assume TEI XML (though stylesheets could also be designed to convert back into TEI XML to allow taking advantage of tools built for TEI XML)
* It is more succinct in syntax than would be an HTML5 Microdata serialization, making the text itself more succinct and human-readable as with queries (such as XQueries), XSL transformations, CSS selectors, JavaScript or other programmatic manipulation against such data, and making the text more rapidly deliverable over networks, assuming that the likely necessary but bulky stylesheets could be cached for reuse. (It is conceivable that browsers might support a language called XBL which would allow transformations which occur opaquely to preserve the original DOM structure, thus allowing queries, etc. to work against the original syntax, but XBL is currently phrased as not supporting transformations of semantics, as converting to XHTML5 Microdata would be seeking to do.)
* It is slightly easier to produce such texts, not only due to brevity, but also because an HTML5 serialization would require editors to be familiar with more HTML markup--the degree depending on the serialization implementation chosen (with some implementations allowing for very little new HTML to be required (primarily using anonymous HTML5 div, span, meta, or link elements joined with the handful of Microdata attributes to add TEI element and attributes), and others seeking to take more advantage of HTML's native markup (e.g., converting quote to blockquote, as the TEI XSL stylesheets do) by converting into it where there is an adequate correspondence with TEI semantics). A Microdata serialization might also wish to translate parts of TEI, where equivalent, into specific [http://schema.org Schema.org] schemas to take advantage of recognition by search engines, requiring those wishing to directly work with such HTML to be familiar with those schemas' semantic markup which could differ in naming from TEI.

==Advantages of using an HTML5 (Microdata) Serialization==
* Allows for taking advantage of '''HTML-only tools such as online WYSIWYG editors''' (e.g., [http://ckeditor.com/demo CKEditor] or [http://en.wikipedia.org/wiki/WYSIWYM WYSIWYM] editors (probably none created to date which are TEI-aware), tools which may not be aware of XML or XSL and thus otherwise unable and unlikely to support TEI.
* Allows for storage on '''sites which only allow HTML (or conversion into HTML) such as the popular Mediawiki wikis''', driving such sites as [http://wikisource.org Wikisource] (a logical place where TEI texts might be offered and made universally discoverable). In the case of Mediawiki, you might add your support to https://bugzilla.wikimedia.org/show_bug.cgi?id=28776 in order for Mediawiki to make the relatively easy but productive fix of allowing Microdata on such wikis (allowing TEI XML would be a much harder sell, given its less familiar and non-historically-web-oriented non-HTML nature). Such wikis also allow a succinct and user-friendly syntax for creating HTML without need for all of the mark-up (e.g., line breaks might auto-create paragraph tags), though admittedly this could introduce some initial ambiguity for editors in becoming clear about the exact HTML which will be produced. While their open collaborative potential is large as evidenced by the success of Wikipedia, wikis can also be used in closed projects to offer revision control and history.
* Allowed encoding in the '''format already most familiar to the web community, HTML''', albeit enhanced, in a standardly outlined manner, by
TEI-based semantic markup. While it could add the additional burden that mark-up creators must learn both HTML and TEI, applications
could be designed to utilize TEI XML as the primary format, converting back to HTML when sending text to the wikis (and converting from HTML to TEI XML when the editor obtains the latest copy on the server, thereby avoiding the need for editors to know anything about HTML at all--using it exclusively as a delivery or storage format. People not familiar with TEI would thus also be able to build the initial syntax in HTML which could be progressively enhanced by TEI semantics.
* '''Search engines''' such as Google (see http://www.google.com/support/webmasters/bin/answer.py?answer=99170 ) are already being made available which can discover such markup in a semantically-aware manner. For example, if your TEI text encoded mention of a particular date or person, your document could show up in such searches. Google's search testing tool offers examples such as [http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Feventful.com%2Fsanfrancisco%2Fevents this one] demonstrating that, for example, that it is aware (and can expose to searchers) semantic information encoded in the document, such as calendar events, person names, etc.---unlike traditional unstructured search indexing which does not know for certain or is not intelligent enough to know that a certain snippet of text represents a date, for example.

==Questions to determine in deciding on a specific serialization algorithm==

Although search engines could discover TEI-encoded Microdata HTML no matter the algorithm, it would probably be of benefit to standardize on a particular approach, specifying exactly how TEI should be converted into such HTML, and exactly how HTML could then be converted back into TEI.

Some issues to consider:

* Degree to which HTML markup will be used in place of (or in addition to) TEI semantics. The more native HTML markup, the more one can take advantage of HTML features (such as preview in an HTML editor or HTML-aware search tools looking for say a "blockquote" but which wouldn't understand the HTML5 TEI semantic equivalent (e.g., <div itemprop="quote">), but the more HTML a TEI editor would need to learn. The default TEI stylesheets tend to already take advantage of such markup where available, so these could be leveraged in preparing such an enriched conversion into HTML5. (A review of the stylesheets might also help express build up a [[Formatting TEI documents#Consideration_of_default_transformation_behavior|human-readable description of the default formatting typically assumed when using TEI markup]] as well as enhance the [[Comprehensive CSS Stylesheet]] effort.)
* Degree to which [http://schema.org Schema.org] schemas would be used in place of (or in addition to) TEI semantics, but the more other semantic vocabularies a TEI editor would need to learn.

[[Category:Customization]]

HTML5 Microdata TEI Serialization

2011-06-10T05:24:21Z

Brettz9: /* Advantages of editing original texts in TEI XML (or use cases for sometimes converting such TEI-enriched HTML5 to TEI XML) */ elaboration

[http://www.w3.org/TR/microdata/ HTML5 Microdata specification] offers the ability to add semantics to HTML, including the ability to specify a particular namespace (in HTML5, called an "item type"), offering the potential for TEI to be encoded in HTML5 without loss of any semantic information.

A collaboration between Google, Microsoft, and Yahoo, [http://schema.org Schema.org], is pushing for adoption over other offered alternatives such as RDFa or Microformats, citing the complexity of the former and the lack of open extensibility (namespacing) of the latter, and with their ability to offer search tools (as [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 Google's]) to take advantage of this information, it seems increasingly likely that this may be the ultimate means of encoding enhanced semantics in regular HTML, thereby offering a compelling argument for allowing TEI texts to be offered in such a serialization.

The question then becomes, when and where to use TEI XML and when and where (and how) to use such a serialization (especially once a particular approach for serializing may be formalized).

Note that in discussing the advantages of one format over the other, using one in one environment does not preclude the possibility of converting between the two formats. For example, one might create texts in TEI XML (including inside web-based editors), share them as HTML5 Microdata to take advantage of search engine discoverability, collaborative HTML editing tools which only are built to recognize HTML (e.g., wikis), and/or convert HTML5 TEI-based Microdata texts found on the web or in such HTML tools back into TEI for convenience of markup editing or manipulation. It would be possible to ensure lossless conversions in either direction (assuming the HTML is not enriched with features not used in TEI such as form controls), so there is little disadvantage in providing such a serialization.

Still, the entries below highlight environments and conditions under which preferring one over the other would be advantageous.

==Advantages of editing original texts in TEI XML (or use cases for sometimes converting such TEI-enriched HTML5 to TEI XML)==
* Existing tools for TEI such as Roma and the default XSL stylesheets assume TEI XML (though stylesheets could also be designed to convert back into TEI XML to allow taking advantage of tools built for TEI XML)
* It is more succinct in syntax than would be an HTML5 Microdata serialization, making the text itself more succinct and human-readable as with queries (such as XQueries), XSL transformations, CSS selectors, JavaScript or other programmatic manipulation against such data, and making the text more rapidly deliverable over networks, assuming that the likely necessary but bulky stylesheets could be cached for reuse.
* It is slightly easier to produce such texts, not only due to brevity, but also because an HTML5 serialization would require editors to be familiar with more HTML markup--the degree depending on the serialization implementation chosen (with some implementations allowing for very little new HTML to be required (primarily using anonymous HTML5 div, span, meta, or link elements joined with the handful of Microdata attributes to add TEI element and attributes), and others seeking to take more advantage of HTML's native markup (e.g., converting quote to blockquote, as the TEI XSL stylesheets do) by converting into it where there is an adequate correspondence with TEI semantics). A Microdata serialization might also wish to translate parts of TEI, where equivalent, into specific [http://schema.org Schema.org] schemas to take advantage of recognition by search engines, requiring those wishing to directly work with such HTML to be familiar with those schemas' semantic markup which could differ in naming from TEI.

==Advantages of using an HTML5 (Microdata) Serialization==
* Allows for taking advantage of '''HTML-only tools such as online WYSIWYG editors''' (e.g., [http://ckeditor.com/demo CKEditor] or [http://en.wikipedia.org/wiki/WYSIWYM WYSIWYM] editors (probably none created to date which are TEI-aware), tools which may not be aware of XML or XSL and thus otherwise unable and unlikely to support TEI.
* Allows for storage on '''sites which only allow HTML (or conversion into HTML) such as the popular Mediawiki wikis''', driving such sites as [http://wikisource.org Wikisource] (a logical place where TEI texts might be offered and made universally discoverable). In the case of Mediawiki, you might add your support to https://bugzilla.wikimedia.org/show_bug.cgi?id=28776 in order for Mediawiki to make the relatively easy but productive fix of allowing Microdata on such wikis (allowing TEI XML would be a much harder sell, given its less familiar and non-historically-web-oriented non-HTML nature). Such wikis also allow a succinct and user-friendly syntax for creating HTML without need for all of the mark-up (e.g., line breaks might auto-create paragraph tags), though admittedly this could introduce some initial ambiguity for editors in becoming clear about the exact HTML which will be produced. While their open collaborative potential is large as evidenced by the success of Wikipedia, wikis can also be used in closed projects to offer revision control and history.
* Allowed encoding in the '''format already most familiar to the web community, HTML''', albeit enhanced, in a standardly outlined manner, by
TEI-based semantic markup. While it could add the additional burden that mark-up creators must learn both HTML and TEI, applications
could be designed to utilize TEI XML as the primary format, converting back to HTML when sending text to the wikis (and converting from HTML to TEI XML when the editor obtains the latest copy on the server, thereby avoiding the need for editors to know anything about HTML at all--using it exclusively as a delivery or storage format. People not familiar with TEI would thus also be able to build the initial syntax in HTML which could be progressively enhanced by TEI semantics.
* '''Search engines''' such as Google (see http://www.google.com/support/webmasters/bin/answer.py?answer=99170 ) are already being made available which can discover such markup in a semantically-aware manner. For example, if your TEI text encoded mention of a particular date or person, your document could show up in such searches. Google's search testing tool offers examples such as [http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Feventful.com%2Fsanfrancisco%2Fevents this one] demonstrating that, for example, that it is aware (and can expose to searchers) semantic information encoded in the document, such as calendar events, person names, etc.---unlike traditional unstructured search indexing which does not know for certain or is not intelligent enough to know that a certain snippet of text represents a date, for example.

==Questions to determine in deciding on a specific serialization algorithm==

Although search engines could discover TEI-encoded Microdata HTML no matter the algorithm, it would probably be of benefit to standardize on a particular approach, specifying exactly how TEI should be converted into such HTML, and exactly how HTML could then be converted back into TEI.

Some issues to consider:

* Degree to which HTML markup will be used in place of (or in addition to) TEI semantics. The more native HTML markup, the more one can take advantage of HTML features (such as preview in an HTML editor or HTML-aware search tools looking for say a "blockquote" but which wouldn't understand the HTML5 TEI semantic equivalent (e.g., <div itemprop="quote">), but the more HTML a TEI editor would need to learn. The default TEI stylesheets tend to already take advantage of such markup where available, so these could be leveraged in preparing such an enriched conversion into HTML5. (A review of the stylesheets might also help express build up a [[Formatting TEI documents#Consideration_of_default_transformation_behavior|human-readable description of the default formatting typically assumed when using TEI markup]] as well as enhance the [[Comprehensive CSS Stylesheet]] effort.)
* Degree to which [http://schema.org Schema.org] schemas would be used in place of (or in addition to) TEI semantics, but the more other semantic vocabularies a TEI editor would need to learn.

[[Category:Customization]]

HTML5 Microdata TEI Serialization

2011-06-09T06:09:14Z

Brettz9: link

[http://www.w3.org/TR/microdata/ HTML5 Microdata specification] offers the ability to add semantics to HTML, including the ability to specify a particular namespace (in HTML5, called an "item type"), offering the potential for TEI to be encoded in HTML5 without loss of any semantic information.

A collaboration between Google, Microsoft, and Yahoo, [http://schema.org Schema.org], is pushing for adoption over other offered alternatives such as RDFa or Microformats, citing the complexity of the former and the lack of open extensibility (namespacing) of the latter, and with their ability to offer search tools (as [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 Google's]) to take advantage of this information, it seems increasingly likely that this may be the ultimate means of encoding enhanced semantics in regular HTML, thereby offering a compelling argument for allowing TEI texts to be offered in such a serialization.

The question then becomes, when and where to use TEI XML and when and where (and how) to use such a serialization (especially once a particular approach for serializing may be formalized).

Note that in discussing the advantages of one format over the other, using one in one environment does not preclude the possibility of converting between the two formats. For example, one might create texts in TEI XML (including inside web-based editors), share them as HTML5 Microdata to take advantage of search engine discoverability, collaborative HTML editing tools which only are built to recognize HTML (e.g., wikis), and/or convert HTML5 TEI-based Microdata texts found on the web or in such HTML tools back into TEI for convenience of markup editing or manipulation. It would be possible to ensure lossless conversions in either direction (assuming the HTML is not enriched with features not used in TEI such as form controls), so there is little disadvantage in providing such a serialization.

Still, the entries below highlight environments and conditions under which preferring one over the other would be advantageous.

==Advantages of editing original texts in TEI XML (or use cases for sometimes converting such TEI-enriched HTML5 to TEI XML)==
* Existing tools for TEI such as Roma and the default XSL stylesheets assume TEI XML
* It is more succinct in syntax than would be an HTML5 Microdata serialization, making the text itself more succinct and human-readable as with queries (such as XQueries), XSL transformations, CSS selectors, JavaScript or other programmatic manipulation against such data, and making the text more rapidly deliverable over networks, assuming that the likely necessary but bulky stylesheets could be cached for reuse.
* It is slightly easier to produce such texts, not only due to brevity, but also because an HTML5 serialization would require editors to be familiar with more HTML markup--the degree depending on the serialization implementation chosen (with some implementations allowing for very little new HTML to be required (primarily using anonymous HTML5 div, span, meta, or link elements joined with the handful of Microdata attributes to add TEI element and attributes), and others seeking to take more advantage of HTML's native markup (e.g., converting quote to blockquote, as the TEI XSL stylesheets do) by converting into it where there is an adequate correspondence with TEI semantics). A Microdata serialization might also wish to translate parts of TEI, where equivalent, into specific [http://schema.org Schema.org] schemas to take advantage of recognition by search engines, requiring those wishing to directly work with such HTML to be familiar with those schemas' semantic markup which could differ in naming from TEI.

==Advantages of using an HTML5 (Microdata) Serialization==
* Allows for taking advantage of '''HTML-only tools such as online WYSIWYG editors''' (e.g., [http://ckeditor.com/demo CKEditor] or [http://en.wikipedia.org/wiki/WYSIWYM WYSIWYM] editors (probably none created to date which are TEI-aware), tools which may not be aware of XML or XSL and thus otherwise unable and unlikely to support TEI.
* Allows for storage on '''sites which only allow HTML (or conversion into HTML) such as the popular Mediawiki wikis''', driving such sites as [http://wikisource.org Wikisource] (a logical place where TEI texts might be offered and made universally discoverable). In the case of Mediawiki, you might add your support to https://bugzilla.wikimedia.org/show_bug.cgi?id=28776 in order for Mediawiki to make the relatively easy but productive fix of allowing Microdata on such wikis (allowing TEI XML would be a much harder sell, given its less familiar and non-historically-web-oriented non-HTML nature). Such wikis also allow a succinct and user-friendly syntax for creating HTML without need for all of the mark-up (e.g., line breaks might auto-create paragraph tags), though admittedly this could introduce some initial ambiguity for editors in becoming clear about the exact HTML which will be produced. While their open collaborative potential is large as evidenced by the success of Wikipedia, wikis can also be used in closed projects to offer revision control and history.
* Allowed encoding in the '''format already most familiar to the web community, HTML''', albeit enhanced, in a standardly outlined manner, by
TEI-based semantic markup. While it could add the additional burden that mark-up creators must learn both HTML and TEI, applications
could be designed to utilize TEI XML as the primary format, converting back to HTML when sending text to the wikis (and converting from HTML to TEI XML when the editor obtains the latest copy on the server, thereby avoiding the need for editors to know anything about HTML at all--using it exclusively as a delivery or storage format. People not familiar with TEI would thus also be able to build the initial syntax in HTML which could be progressively enhanced by TEI semantics.
* '''Search engines''' such as Google (see http://www.google.com/support/webmasters/bin/answer.py?answer=99170 ) are already being made available which can discover such markup in a semantically-aware manner. For example, if your TEI text encoded mention of a particular date or person, your document could show up in such searches. Google's search testing tool offers examples such as [http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Feventful.com%2Fsanfrancisco%2Fevents this one] demonstrating that, for example, that it is aware (and can expose to searchers) semantic information encoded in the document, such as calendar events, person names, etc.---unlike traditional unstructured search indexing which does not know for certain or is not intelligent enough to know that a certain snippet of text represents a date, for example.

==Questions to determine in deciding on a specific serialization algorithm==

Although search engines could discover TEI-encoded Microdata HTML no matter the algorithm, it would probably be of benefit to standardize on a particular approach, specifying exactly how TEI should be converted into such HTML, and exactly how HTML could then be converted back into TEI.

Some issues to consider:

* Degree to which HTML markup will be used in place of (or in addition to) TEI semantics. The more native HTML markup, the more one can take advantage of HTML features (such as preview in an HTML editor or HTML-aware search tools looking for say a "blockquote" but which wouldn't understand the HTML5 TEI semantic equivalent (e.g., <div itemprop="quote">), but the more HTML a TEI editor would need to learn. The default TEI stylesheets tend to already take advantage of such markup where available, so these could be leveraged in preparing such an enriched conversion into HTML5. (A review of the stylesheets might also help express build up a [[Formatting TEI documents#Consideration_of_default_transformation_behavior|human-readable description of the default formatting typically assumed when using TEI markup]] as well as enhance the [[Comprehensive CSS Stylesheet]] effort.)
* Degree to which [http://schema.org Schema.org] schemas would be used in place of (or in addition to) TEI semantics, but the more other semantic vocabularies a TEI editor would need to learn.

[[Category:Customization]]

HTML5 Microdata TEI Serialization

2011-06-09T05:58:36Z

Brettz9: starting page

[http://www.w3.org/TR/microdata/ HTML5 Microdata specification] offers the ability to add semantics to HTML, including the ability to specify a particular namespace (in HTML5, called an "item type"), offering the potential for TEI to be encoded in HTML5 without loss of any semantic information.

A collaboration between Google, Microsoft, and Yahoo, [http://schema.org Schema.org], is pushing for adoption over other offered alternatives such as RDFa or Microformats, citing the complexity of the former and the lack of open extensibility (namespacing) of the latter, and with their ability to offer search tools (as [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 Google's]) to take advantage of this information, it seems increasingly likely that this may be the ultimate means of encoding enhanced semantics in regular HTML, thereby offering a compelling argument for allowing TEI texts to be offered in such a serialization.

The question then becomes, when and where to use TEI XML and when and where (and how) to use such a serialization (especially once a particular approach for serializing may be formalized).

Note that in discussing the advantages of one format over the other, using one in one environment does not preclude the possibility of converting between the two formats. For example, one might create texts in TEI XML (including inside web-based editors), share them as HTML5 Microdata to take advantage of search engine discoverability, collaborative HTML editing tools which only are built to recognize HTML (e.g., wikis), and/or convert HTML5 TEI-based Microdata texts found on the web or in such HTML tools back into TEI for convenience of markup editing or manipulation. It would be possible to ensure lossless conversions in either direction (assuming the HTML is not enriched with features not used in TEI such as form controls), so there is little disadvantage in providing such a serialization.

Still, the entries below highlight environments and conditions under which preferring one over the other would be advantageous.

==Advantages of editing original texts in TEI XML (or use cases for sometimes converting such TEI-enriched HTML5 to TEI XML)==
* Existing tools for TEI such as Roma and the default XSL stylesheets assume TEI XML
* It is more succinct in syntax than would be an HTML5 Microdata serialization, making the text itself more succinct and human-readable as with queries (such as XQueries), XSL transformations, CSS selectors, JavaScript or other programmatic manipulation against such data, and making the text more rapidly deliverable over networks, assuming that the likely necessary but bulky stylesheets could be cached for reuse.
* It is slightly easier to produce such texts, not only due to brevity, but also because an HTML5 serialization would require editors to be familiar with more HTML markup--the degree depending on the serialization implementation chosen (with some implementations allowing for very little new HTML to be required (primarily using anonymous HTML5 div, span, meta, or link elements joined with the handful of Microdata attributes to add TEI element and attributes), and others seeking to take more advantage of HTML's native markup (e.g., converting quote to blockquote, as the TEI XSL stylesheets do) by converting into it where there is an adequate correspondence with TEI semantics). A Microdata serialization might also wish to translate parts of TEI, where equivalent, into specific [http://schema.org Schema.org] schemas to take advantage of recognition by search engines, requiring those wishing to directly work with such HTML to be familiar with those schemas' semantic markup which could differ in naming from TEI.

==Advantages of using an HTML5 (Microdata) Serialization==
* Allows for taking advantage of '''HTML-only tools such as online WYSIWYG editors''' (e.g., [http://ckeditor.com/demo CKEditor] or [http://en.wikipedia.org/wiki/WYSIWYM WYSIWYM] editors (probably none created to date which are TEI-aware), tools which may not be aware of XML or XSL and thus otherwise unable and unlikely to support TEI.
* Allows for storage on '''sites which only allow HTML (or conversion into HTML) such as the popular Mediawiki wikis''', driving such sites as [http://wikisource.org Wikisource] (a logical place where TEI texts might be offered and made universally discoverable). In the case of Mediawiki, you might add your support to https://bugzilla.wikimedia.org/show_bug.cgi?id=28776 in order for Mediawiki to make the relatively easy but productive fix of allowing Microdata on such wikis (allowing TEI XML would be a much harder sell, given its less familiar and non-historically-web-oriented non-HTML nature). Such wikis also allow a succinct and user-friendly syntax for creating HTML without need for all of the mark-up (e.g., line breaks might auto-create paragraph tags), though admittedly this could introduce some initial ambiguity for editors in becoming clear about the exact HTML which will be produced. While their open collaborative potential is large as evidenced by the success of Wikipedia, wikis can also be used in closed projects to offer revision control and history.
* Allowed encoding in the '''format already most familiar to the web community, HTML''', albeit enhanced, in a standardly outlined manner, by
TEI-based semantic markup. While it could add the additional burden that mark-up creators must learn both HTML and TEI, applications
could be designed to utilize TEI XML as the primary format, converting back to HTML when sending text to the wikis (and converting from HTML to TEI XML when the editor obtains the latest copy on the server, thereby avoiding the need for editors to know anything about HTML at all--using it exclusively as a delivery or storage format. People not familiar with TEI would thus also be able to build the initial syntax in HTML which could be progressively enhanced by TEI semantics.
* '''Search engines''' such as Google (see http://www.google.com/support/webmasters/bin/answer.py?answer=99170 ) are already being made available which can discover such markup in a semantically-aware manner. For example, if your TEI text encoded mention of a particular date or person, your document could show up in such searches. Google's search testing tool offers examples such as [http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Feventful.com%2Fsanfrancisco%2Fevents this one] demonstrating that, for example, that it is aware (and can expose to searchers) semantic information encoded in the document, such as calendar events, person names, etc.---unlike traditional unstructured search indexing which does not know for certain or is not intelligent enough to know that a certain snippet of text represents a date, for example.

==Questions to determine in deciding on a specific serialization algorithm==

Although search engines could discover TEI-encoded Microdata HTML no matter the algorithm, it would probably be of benefit to standardize on a particular approach, specifying exactly how TEI should be converted into such HTML, and exactly how HTML could then be converted back into TEI.

Some issues to consider:

* Degree to which HTML markup will be used in place of (or in addition to) TEI semantics. The more native HTML markup, the more one can take advantage of HTML features (such as preview in an HTML editor or HTML-aware search tools looking for say a "blockquote" but which wouldn't understand the HTML5 TEI semantic equivalent (e.g., <div itemprop="quote">), but the more HTML a TEI editor would need to learn. The default TEI stylesheets tend to already take advantage of such markup where available, so these could be leveraged in preparing such an enriched conversion into HTML5. (A review of the stylesheets might also help express build up a human-readable description of the default formatting typically assumed when using TEI markup as well as enhance the [[Comprehensive CSS Stylesheet]] effort.)
* Degree to which [http://schema.org Schema.org] schemas would be used in place of (or in addition to) TEI semantics, but the more other semantic vocabularies a TEI editor would need to learn.

[[Category:Customization]]

Comprehensive CSS Stylesheet

2011-06-05T15:42:14Z

Brettz9: /* References used */ heading fix

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

==Advantages of CSS (compared to XSL)==

# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Simpler for communicating the underlying behavior and inviting discussion on assumptions
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier and XBL, were it to be implemented in browsers (as planned in Firefox) and forgo discouraging semantic alterations, could preserve the DOM (unlike typical stylesheets) while rendering according to a kind of transformation)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.
# If the selectors were changed, the style rules could be applied to an HTML5 serialization of TEI, being in a language already familiar to web developers

==Disadvantages of CSS (compared to XSL)==

# Does not allow transformations such as re-ordering and duplication (thus no automatically generated indexes, tables of contents, etc).
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value).
# Unable to create form controls and some other HTML GUI components.
# Assumes that the structure of the TEI essentially similar to the desired output (thus no stand-off markup; switching between multiple overlapping hierarchical structures; etc).

==Features of XSL which are impossible to leverage in a CSS stylesheet for TEI==

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

==Namespaces==

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

==(Level of completion)==

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==Alphabetical==

===a===
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
additions {display: block;} additions:before {content: "Additions: ";font-weight: bold;}
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

===b===

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

===c===

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

===d===

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

===e===

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

===f===

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

===g===

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

===h===

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

===i===

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

===j===

* join
* joinGrp

===k===

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

===l===

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

===m===

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

===n===

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

===o===

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

===p===

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

===q===

* q
* quotation
* quote

===r===

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

===s===

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

===t===

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

===u===

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

===v===

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

===w===

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

===x===

* xr

===y===

(none)

===z===
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2011-06-05T15:41:41Z

Brettz9: reordering like items

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

==Advantages of CSS (compared to XSL)==

# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Simpler for communicating the underlying behavior and inviting discussion on assumptions
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier and XBL, were it to be implemented in browsers (as planned in Firefox) and forgo discouraging semantic alterations, could preserve the DOM (unlike typical stylesheets) while rendering according to a kind of transformation)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.
# If the selectors were changed, the style rules could be applied to an HTML5 serialization of TEI, being in a language already familiar to web developers

==Disadvantages of CSS (compared to XSL)==

# Does not allow transformations such as re-ordering and duplication (thus no automatically generated indexes, tables of contents, etc).
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value).
# Unable to create form controls and some other HTML GUI components.
# Assumes that the structure of the TEI essentially similar to the desired output (thus no stand-off markup; switching between multiple overlapping hierarchical structures; etc).

==Features of XSL which are impossible to leverage in a CSS stylesheet for TEI==

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

==Namespaces==

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

==(Level of completion)==

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==Alphabetical==

===a===
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
additions {display: block;} additions:before {content: "Additions: ";font-weight: bold;}
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

===b===

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

===c===

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

===d===

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

===e===

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

===f===

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

===g===

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

===h===

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

===i===

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

===j===

* join
* joinGrp

===k===

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

===l===

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

===m===

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

===n===

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

===o===

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

===p===

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

===q===

* q
* quotation
* quote

===r===

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

===s===

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

===t===

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

===u===

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

===v===

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

===w===

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

===x===

* xr

===y===

(none)

===z===
z

* zone

===References used===
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2011-06-05T15:40:33Z

Brettz9: structuring page further

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

==Advantages of CSS (compared to XSL)==

# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Simpler for communicating the underlying behavior and inviting discussion on assumptions
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier and XBL, were it to be implemented in browsers (as planned in Firefox) and forgo discouraging semantic alterations, could preserve the DOM (unlike typical stylesheets) while rendering according to a kind of transformation)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.
# If the selectors were changed, the style rules could be applied to an HTML5 serialization of TEI, being in a language already familiar to web developers

==Disadvantages of CSS (compared to XSL)==

# Does not allow transformations such as re-ordering and duplication (thus no automatically generated indexes, tables of contents, etc).
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value).
# Unable to create form controls and some other HTML GUI components.
# Assumes that the structure of the TEI essentially similar to the desired output (thus no stand-off markup; switching between multiple overlapping hierarchical structures; etc).

==Namespaces==

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

==Features of XSL which are impossible to leverage in a CSS stylesheet for TEI==

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

==(Level of completion)==

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==Alphabetical==

===a===
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
additions {display: block;} additions:before {content: "Additions: ";font-weight: bold;}
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

===b===

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

===c===

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

===d===

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

===e===

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

===f===

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

===g===

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

===h===

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

===i===

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

===j===

* join
* joinGrp

===k===

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

===l===

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

===m===

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

===n===

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

===o===

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

===p===

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

===q===

* q
* quotation
* quote

===r===

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

===s===

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

===t===

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

===u===

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

===v===

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

===w===

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

===x===

* xr

===y===

(none)

===z===
z

* zone

===References used===
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2011-06-05T15:35:35Z

Brettz9: +advantage

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Simpler for communicating the underlying behavior and inviting discussion on assumptions
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier and XBL, were it to be implemented in browsers (as planned in Firefox) and forgo discouraging semantic alterations, could preserve the DOM (unlike typical stylesheets) while rendering according to a kind of transformation)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.
# If the selectors were changed, the style rules could be applied to an HTML5 serialization of TEI, being in a language already familiar to web developers

Disadvantages:
# Does not allow transformations such as re-ordering and duplication (thus no automatically generated indexes, tables of contents, etc).
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value).
# Unable to create form controls and some other HTML GUI components.
# Assumes that the structure of the TEI essentially similar to the desired output (thus no stand-off markup; switching between multiple overlapping hierarchical structures; etc).

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
additions {display: block;} additions:before {content: "Additions: ";font-weight: bold;}
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2011-06-05T15:34:02Z

Brettz9: more advantages of CSS

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Simpler for communicating the underlying behavior and inviting discussion on assumptions
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier and XBL, were it to be implemented in browsers (as planned in Firefox) and forgo discouraging semantic alterations, could preserve the DOM (unlike typical stylesheets) while rendering according to a kind of transformation)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow transformations such as re-ordering and duplication (thus no automatically generated indexes, tables of contents, etc).
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value).
# Unable to create form controls and some other HTML GUI components.
# Assumes that the structure of the TEI essentially similar to the desired output (thus no stand-off markup; switching between multiple overlapping hierarchical structures; etc).

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
additions {display: block;} additions:before {content: "Additions: ";font-weight: bold;}
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Formatting TEI documents

2010-09-15T03:03:11Z

Brettz9: /* Respecting the original formatting */

This page aims to spell out some considerations when formatting TEI documents or considering how mark-up issues inter-relate with (or should not inter-relate with) output formatting. It is based on a proposed chapter draft at http://www.tei-c.org/Activities/Council/Working/tcw10.xml

Per http://www.tei-c.org/Activities/Council/Meetings/tcm38.xml?style=raw , the TEI "Council reached a consensus that the draft document is not suitable as a formal chapter of the Guidelines, largely because the technologies and procedures used for output rendering change frequently and are not under the control of the TEI Consortium (e.g., XSLT processors, CSS standards, etc.)", but I wanted to offer it here in case others wish to revise or expand on it.

----
While TEI makes no claims about how a document is to be rendered--except to the extent that it allows description of the original formatting and to the extent that publishers wish to reflect that formatting--it is a general expectation that the TEI documents a project is creating can be rendered at some point in a more human-readable manner. While the desired formatting should not prompt one to violate the TEI Abstract model by altering the semantics of a document in order to adjust output formatting, the process of creating formatting output (or even well before doing so), may lead a project to reconsider some aspects of its semantic markup, as well as the more conventional means of adjusting a stylesheet, so the issues raised here go beyond the work of a designer. This chapter will discuss various issues related to formatting a TEI document.

==Respecting the original formatting==

In order to fully respect the original formatting of a document, it is necessary to consider (and thoroughly use) the global @rendition attribute and/or the @render attribute on <tagUsage> elements to point to <rendition> elements and/or the global @rend attribute to provide its own definition without referring elsewhere.

While semantic hooks and reliance on the typical formatting of specific tags for cases where @rend and @rendition are not needed to override typical behaviors might be sufficient to create an output document reflecting the formatting of the original document, if the original rendering is important information to preserve, this can be done more explicitly by ensuring that all elements are given a <tagUsage> element which uses its @render attribute to point to a <rendition> element which contains the styling details that can be applied to all instances of the tag. In this way, there is no ambiguity about how a tag is to be rendered. This is also recommended practice when <tagUsage> elements are provided. (see http://tei.oucs.ox.ac.uk/P5/Guidelines-web/en/html/HD.html#HD57 ).

However, note that <tagUsage> elements do not allow for the specification of a default rendering behavior for element-attribute combinations--only for specific elements regardless of any attributes or attribute values. They also do not allow the specification of a default behavior for an element based on its position (e.g., <quote> within <cit> ), so as this point, it may be inevitable to heavily rely on @rend and @rendition if one must thoroughly indicate this original formatting, independent of a stylesheet.

For maximum specificity in encoding formatting details, the content supplied within <rendition> and @rend ought to use a formal formatting language. However, besides not specifying a particular formatting language that ought to be used, at present TEI does not offer a fail-safe means of translating @rend and <rendition> content into a stylesheet (even though this information could potentially be used to create @style attribute content, or, by using XSLT 2.0, simultaneously create a CSS stylesheet alongside the X/HTML output.

One may use the @scope attribute on <rendition/> to express that a particular style rule should target CSS pseudo-elements (like :before, :after, :first), such as one might wish to do in specifying the addition of distinct content at the beginning or end of a tag (e.g., adding left and right curly quotes to a <q> element.

Even where the output does faithfully reflect the original, it should be fairly common to need to optimize the resulting CSS stylesheet, since it would likely be fairly large with there being no means besides <tagUsage> to indicate a behavior to apply to element-attribute combinations or elements in particular positions.

==Original vs. output rendering==

One might find oneself tempted to force the rendition mechansims in TEI (@rend or @rendition or <tagUsage's> @render with <rendition> ) to go beyond their intended use for describing the original rendering of a document. However, it is important to keep in mind that if one wishes to control how the formatting will be output, independently of the original formatting (adding details of formatting not expressed about the original with the TEI render mechanisms or overriding these details), one must not subvert the semantics of a TEI document (at the risk of introducing TEI non-conformance and interoperability issues) for the sake of controlling formatting--that should instead be handled by a stylesheet.

This might necessitate a different stylesheet or, as is probable for most cases, modifications to the default stylesheets provided by TEI, if the parameter options (assuming XSL stylesheets are used) are insufficient to express a project's output requirements. It is, for example, possible to allow the stylesheets to recognize multiple attributes, even at the same time.

==Returning changes to the default stylesheets==

The stylesheets from TEI are evolving with the TEI project, however, so it may be possible that the TEI project might be open to certain changes (whether optional or required) to its default stylesheets, if the changes offered may be of interest to a wider audience and TEI has the resources to implement the changes. Given that the code of these stylesheets is open source, it may benefit both TEI and its users as well as an individual project for stylesheet improvements (or other TEI resources for that matter) to be returned back to the community, as it precludes the individual project from needing to make modifications each time an update occurs.

With more standard (but not standardized) styling expectations (and stylesheet), the more likely that TEI processing applications might be used to render TEI in a familiar format (such as when obtained directly off the web, etc.), even while allowing publishers' full freedom to deviate from such common conventions if they wish.

==Influence of formatting (or accessibility) concerns on markup==

While one should not subvert the semantics of a TEI document in order to control formatting, besides customizing a stylesheet alone, the viewing of a formatted document might prompt a project to consider changes to the original TEI documents, such as:

# giving a more detailed encoding of the original rendering (as that information can be used to produce output rendering, assuming again that the original document being represented indeed possesses this rendering), using <rendition> , <tagUsage> render, @rendition, and @rend
# adding more semantic "hooks" whether this is the use of hitherto unused elements or attributes such as @n or @type (potentially with the adding of generic elements like <seg> ) which can provide more semantic detail about certain text that can in turn be targeted by a stylesheet to provide more granular control in output formatting. This may also have the benefit of providing more semantic richness to the document (ideally using the more specific elements already recommended for this purpose). Such semantic 'hooks' can also be of the variety that ensures that the output formatting includes sufficient accessibility features such as to make available alternative text along with any graphics or images that could not otherwise be interpreted by a speech browser.

==Semantic information and output formatting==

Besides formatting concerns leading one to add additional semantic distinctions into a TEI document, one may also wish to encode a certain degree of semantic information (to the extent allowed in the output formatting language) into one's formatting output and consider the extent to which output formatting markup is separated from any more generic output structural markup (e.g., creating CSS to hold styles with XHTML used to present the structure or encoding structural and formatting markup together). These are both discussed below.

===Encoding semantic information within formatted output===

While it may often be the case that TEI will be converted to a formatted output in which semantic information is lost, certain output formats allow some if not all semantic information to be retained in some manner. For example, XHTML can use the approach of microformats (http://microformats.org) to use the global and generic XHTML @class attribute to contain information such as the original TEI tag name. While it would likely be too cumbersome to originate documents in such a format (assuming all TEI semantics could be encoded with such an approach), it offers the advantage that one might, for example, use a web browser to obtain a document already pre-rendered, yet use a microformat processor within the browser (possibly available as a browser extension) to search for semantic information.

===Encoding formatting within structural and semantic output===

It has become a generally recommended practice for even XHTML documents on the web to separate their formatting content (as with CSS) into a separate file from the structural content (of paragraphs, generic divisions, etc.). This offers various advantages such as speed in downloading (by browser caching for repeatedly used stylesheet files or by those using speech browsers being able to avoid downloading visually-oriented stylesheets), or flexibility in subsequent style changes. While one might define an XSL stylesheet to create specific XHTML @class attribute values which are associated with those classes targeted in a predefined CSS stylesheet, XSLT 2.0 might be employed to utilize information such as contained within @rend or <rendition> elements to specify the creation of a CSS document while also simultaneously creating the XHTML output document. See the sections on preserving original formatting.

Despite the generally recommended practice of separating styles from structure and semantic information, given the present absence of a means of making queries which utilize style information contained in separate files, it may be conceivable for some to wish to have their formatting output mixed in with structural output (the @style attribute might be harder to parse in a query than if specific XHTML formatting structures were used--even though these may be deprecated in later versions)--just as one might prefer to encode say italic emphasis using <emph n="italic" rend="font-style:italic"> rather than use a more formal but correct syntax of <emph rend="font-style: italic;"> since the former is easier to parse -- so that queries can take advantage of both styling information and/or semantic information. For example, if one views a document and sees that italic text is used for emphasis, one might wish to search for a certain phrase contained within italic text, for example, because one recalled the text occurring there, or because one identified a pattern represented by italic text but where one did not know what the exact name of the pattern was, and thus not knowing what specific tag one must search for to find the desired text.

==General categories of elements to consider in formatting (or not formatting at all)==

Before considering the usual rendering and default rendering options for specific elements (along with any specific attributes), it is worth considering some general issues pertaining to certain types of elements.

===Likelihood of printing out specific elements===

Elements differ in the likelihood a project will wish to render them in a formatted output document. They range from editorial information which might never be printed out for common viewing, to elements which will sometimes be printed out (such as a <choice> listing the original text and a regularized or corrected form) to elements such as paragraphs which almost certainly will be printed out.

For the case of those which will always be printed out, one can make their styling explicit by using <tagUsage> elements with a @render attribute pointing to a <rendition> element with the styling details (and optionally the code). One might optionally even indicate specific elements which should not be displayed (though depending on the stylesheet language, this might not strictly be necessary).

Moreover, a stylesheet might wish to depend on element-specific or global attributes (whether semantic or rendition-related) to target elements with or without these attributes or with specific values to display or not display them selectively.

Elements which occur in the header, will generally not be printed out, though for some project's purposes, display of this information (e.g., bibliographic data) may be useful to include in the formatting output.

While other elements that occur within the running text will generally be printed out, it is important to understand that with TEI--which, as cannot be emphasized enough, is not a formatting language--this will not always be the case. If one has editorial information that should not be printed out within the running text (or at least should not appear alongside the running text), as a project might not wish the encoder-added information to disrupt the flow of the text (e.g., of a narrative) and for which it might even be considered irreverent by some viewers (such as for scriptural works), it will be important to be aware of all such tags that a project might not want printed out so that the stylesheet (possibly in conjunction with special semantic TEI markup if not markup indicating original rendering) does not display those tags' content.
Elements which are defined by the following macros are generally not to be displayed:

# macro.limitedContent (http://www.tei-c.org/release/doc/tei-p5-doc/html/ref-macro.limitedContent.html ): desc, fDescr, figDesc, fsDescr, meeting, rendition, tagUsage, witness
# macro.phraseSeq.limited (http://www.tei-c.org/release/doc/tei-p5-doc/html/ref-macro.phraseSeq.limited.html ): activity, age, authority, channel, classCode, constitution, creation. derivation, domain, factuality, funder, interaction, interp, langKnown, language, locale, metSym, preparedness, principal, purpose, resp, span, sponsor, valDesc

Moreover, there are some elements such as those in model.noteLike ( <note> and <witDetail> ) which while they might occur in the outputted document, might also in other cases or within some projects not always be rendered if at all. model.global.meta with members such as alt, altGrp, certainty, fLib, fs, fvLib, index, interp, interpGrp, join, joinGrp, link, linkGrp, respons, span, spanGrp, and timeline as well as elements containing the global @exclude attribute may or may not be output when included within a document.

Still others include items such as may be contained within <choice> : abbr, am, corr, ex, expan, orig, reg, seg, sic, unclear .. A project may need to consider whether to output these elements with both choices being shown in some manner (even as a mere tooltip that is exposed when certain text is hovered over) or whether to only show one of the choices (such as that reflecting the original or some regularization, correction, expansion, or abbreviation).

Likewise with elements belonging to model.pPart.transcriptional: add, app, corr, damage, del, orig, reg, restore, sic, supplied, unclear . One may or may not wish to indicate <supplied> text for example, or choose how to format damaged sections in some particular manner.

(any others????)

Since there is no way of knowing whether some of the elements mentioned above such as <note> refer to text that should be printed out or not, one must rely on other mechanisms to specify or glean this information. One way would be to use attributes, such as @resp to detect whether the note was the responsibility of a markup editor of the document, or whether it was provided by an original annotator of the document. However, as the detection of this might not always be clear (especially if the markup annotator also served as the original annotator), the user of other attributes such as @type, or where @type is not available, possibly @n or even xml:id might be used.

Note that despite its being listed above, an element such as <figDesc> , while it might not normally be displayed immediately to a visual browser, might still nevertheless be important (or even required in some formatting languages or in use with projects needing by law to adhere to accessibility regulations) for the sake of being accessible to those with visual disabilities who might depend on speech browsers or tooltips to be able to get a sense of what a particular graphic, photograph, etc. was displaying. It is certainly good practice to follow such an encoding, both within TEI documents and in the formatted output, where available.

===Behaviour within <corr> and similar elements===

One exception to @rend, @rendition (or their absence) indicating original formatting is that within a <corr> tag.

The addition of a @rend within <corr> (or <reg> ) would apply to an intended output formatting, rather than to the original formatting as it normally does.
<choice><sic><title level="j" rend="noitalic">The Times</title></sic><corr><title level="j" rend="italic">The Times</corr></choice>
Likewise, especially if the default rendering of <title> were specified by a <tagUsage> and <rendition> element (here to indicate a title as being by default in italic), the absence of @rend or @rendition would still imply a change of formatting:
<choice><sic><title level="j" rend="noitalic">The Times</title></sic><corr><title level="j">The Times</corr></choice>

===Items needing replication===

Some elements or elements with certain attributes may need special consideration for output such as @copyOf or <join> , as these might indicate that certain formatting output might need to be created such as might (as with other cases described earlier) not be evident by simply stripping the markup out of the document.

===Text attributes===

Most attributes are used with coded values, as they are not mean to represent human language or to be displayed. Text attributes represent the exception to this, though it is commonly preferred for an XML language to represent these attributes as elements so that further nested subelements representing markup at the phrasal level, etc. can be added within as needed.

Text attributes have generally been removed from TEI, and some of the ones that remain one might not wish to output in a formatted version anyways, but if one wishes to include, for example, @reason in one's output, one will be unable to add styling which depends on child elements for more specific formatting since the information is expressed within an attribute (but one can style differently depending on the element's @xml:lang, as that does apply for text attributes, as well as any other attributes on the element). Likewise for the dictionary attributes, @expand, @norm, @split, @value, and @orig which represent the remaining text attributes????.

((((Syd prepared a list of potential text attributes to review to see if they were still text attributes--it'd be nice to be able to give such an exhaustive list here.))))

I think the element-specific details might be logically incorporated as documentation elements within XSL that could be extracted for automatic inclusion within the TEI reference pages, making clear that the formatting discussed is only that of the default behavior used in TEI-provided stylesheets (though also discussing the range of options that the stylesheet makes available through parameters). I really think giving awareness of these formatting issues in the context of considering these elements would be more helpful than waiting for people to discover them separately in the stylesheets.

==Consideration of default transformation behavior==

While, as mentioned earlier, there is no required mapping of TEI elements and attributes to specific output document structures (e.g., XHTML/CSS, LaTeX, etc.), the fact that TEI provides a default set of stylesheets to work with (albeit a parameterized one) and that these are presumably well-used [by the number of downloads????] indicates that there are a general set of expectations about how most TEI structures will appear when output. The effort required to create one's own stylesheets from scratch for such a large vocabulary as TEI provides, or even to significantly modify existing stylesheets (no less each time as improvements and adjustments are made to the default files), also makes the understanding of how documents will be transformed an imperative for many projects. Thus, it becomes necessary to understand how TEI might commonly be transformed (or understood to be transformed), even beyond the extent to which the stylesheets themselves are documented and express (mostly in technical language) the templates used to transform TEI into a formatting language.

The default stylesheets provided by TEI serve as a good basis for discussion on how formatting can be performed and are documented here for the sake of those who wish to know how each structure they might use in a TEI document might be rendered by default. The stylesheets nor this discussion should be taken as any kind of requirement to use these stylesheets as a base, or even at all.

===Specific formatting for specific elements (and any attributes)===

(to be displayed on reference pages?)

See [[Comprehensive CSS Stylesheet]] for a beginning at describing default styling (attempting to mimic the XSL stylesheets) as expressed in the simple, precise, and usually intuitive, but still technical, language CSS.

===Specific formatting for specific categories of formatting (images, etc.)===

(to be compiled after reference pages have their information fleshed out)

Comprehensive CSS Stylesheet

2010-07-12T09:24:05Z

Brettz9: /* a */ +additions

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
additions {display: block;} additions:before {content: "Additions: ";font-weight: bold;}
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T09:22:20Z

Brettz9: /* a */ add, addName comment

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
* addName (XSL has not yet covered (from namesdates module))
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T09:09:49Z

Brettz9: /* a */ additional fixes

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";} additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;} additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;} additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;} additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T09:09:08Z

Brettz9: /* a */ +additional

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity (XSL has not yet covered (from language module))
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
additional {padding-top: 3pt; padding-bottom: 2pt; display: block;} additional>listBibl>bibl:after {content: ".";}
additional:before {content: "Additional:";display: block;font-weight: 600; font-variant: small-caps;font-size: 120%;}
additional>listBibl {display: block;list-style-type: none;margin-top: 10pt;}
additional>listBibl:before {content: "Bibliography:";display: block;font-weight: 600;font-variant: small-caps;font-size: 120%;}
additional>listBibl>bibl {text-align: left;display: list-item;margin-left: 30pt;}
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T09:02:02Z

Brettz9: /* a */ acquisition

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
history acquisition:before {content: "Acquisition: ";font-weight: bold;} history acquisition {display: block;}
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T08:58:44Z

Brettz9: /* a */ accMat

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
accMat {display: block;} accMat:before {content: "Accompanying material: "; font-weight: bold;}
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T08:54:32Z

Brettz9: expan/abbr comments

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("} /* Assumes inside choice and expan before abbr */
choice > expan + abbr:after {content:")"} /* Assumes inside choice and expan before abbr */
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-07-12T08:52:39Z

Brettz9: abbr+expan

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
choice > expan + abbr:before {content:"("}
choice > expan + abbr:after {content:")"}
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
choice > expan + abbr:before {content:"("}
choice > expan + abbr:after {content:")"}
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-17T16:43:51Z

Brettz9:

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content? (Firefox allows content: '123'attr(class)'456' at least); See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Tips on using CSS with XML/TEI

2010-06-16T06:31:57Z

Brettz9: /* HTML to CSS Equivalents */

For those who are fairly familiar with using CSS with HTML or XHTML, one might be familiar enough with how to define colors, etc., but still remain unaware of how to make a simple stylesheet.

Since one cannot use .class-name as in X/HTML (though some processors might be able to use xml:id to be the target of the # id selector), one first ought to be familiar with the generic [http://www.w3.org/TR/CSS21/selector.html#attribute-selectors attribute selectors].

For example,

<code><pre><div type="chapter">...</pre></code>

Could be styled with:
<code><pre>div[type="chapter"] {}</pre></code>

Another important adjustment to make is that while X/HTML defines a default display behavior (e.g., <p> in HTML is block while <span> in HTML is inline), other XML is more generic and forces you to define which elements out to be defined as block (they will otherwise be rendered inline).

For example, for TEI, you might define the following:

<code><pre>p, div, div1, div2, div3 {display:block}</pre></code>

You can also specify inline elements by using <code>display:inline</code>

==HTML to CSS Equivalents==

(Display is inline by default unless indicated.)
(Note that in order to bypass the spam filter, some bogus spaces were added in the display: none; (and height: 2px) lines.)

// the following was obtained from resource://gre-resources/html.css , with the license terms under MPL 1.1/GPL 2.0/LGPL 2.1.

<pre>
@namespace url(http://www.w3.org/1999/xhtml); /* set default namespace to HTML */
@namespace xul url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

/* bidi */

[dir="rtl"] {
direction: rtl;
unicode-bidi: embed;
}
[dir="ltr"] {
direction: ltr;
unicode-bidi: embed;
}
bdo[dir] {
unicode-bidi: bidi-override;
}

/* To ensure http://www.w3.org/TR/REC-html40/struct/dirlang.html#style-bidi:
*
* "When a block element that does not have a dir attribute is transformed to
* the style of an inline element by a style sheet, the resulting presentation
* should be equivalent, in terms of bidirectional formatting, to the
* formatting obtained by explicitly adding a dir attribute (assigned the
* inherited value) to the transformed element." */

address, blockquote, body, caption, center, col, colgroup, dd, dir, div, dl, dt,
fieldset, form, h1, h2, h3, h4, h5, h6, hr, html, isindex, li, listing, map,
marquee, menu, noframes, ol, p, plaintext, pre, table, tbody, td, tfoot, th,
thead, tr, ul, xmp {
unicode-bidi: embed;
}

/* blocks */

html, div, map, dt, isindex, form {
display: block;
}

body {
display: block;
margin: 8px;
}

p, dl, multicol {
display: block;
margin: 1em 0;
}

dd {
display: block;
-moz-margin-start: 40px;
}

blockquote {
display: block;
margin: 1em 40px;
}

address {
display: block;
font-style: italic;
}

center {
display: block;
text-align: -moz-center;
}

blockquote[type=cite] {
display: block;
margin: 1em 0px;
-moz-padding-start: 1em;
-moz-border-start: solid;
border-color: blue;
border-width: thin;
}

span[_moz_quote=true] {
color: blue;
}

pre[_moz_quote=true] {
color: blue;
}

h1 {
display: block;
font-size: 2em;
font-weight: bold;
margin: .67em 0;
}

h2 {
display: block;
font-size: 1.5em;
font-weight: bold;
margin: .83em 0;
}

h3 {
display: block;
font-size: 1.17em;
font-weight: bold;
margin: 1em 0;
}

h4 {
display: block;
font-weight: bold;
margin: 1.33em 0;
}

h5 {
display: block;
font-size: 0.83em;
font-weight: bold;
margin: 1.67em 0;
}

h6 {
display: block;
font-size: 0.67em;
font-weight: bold;
margin: 2.33em 0;
}

listing {
display: block;
font-family: -moz-fixed;
font-size: medium;
white-space: pre;
margin: 1em 0;
}

xmp, pre, plaintext {
display: block;
font-family: -moz-fixed;
white-space: pre;
margin: 1em 0;
}

/* tables */

table {
display: table;
border-spacing: 2px;
border-collapse: separate;
margin-top: 0;
margin-bottom: 0;
/* XXXldb do we want this if we're border-collapse:collapse ? */
-moz-box-sizing: border-box;
text-indent: 0;
}

table[align="left"] {
float: left;
}

table[align="right"] {
float: right;
text-align: start;
}

table[rules]:not([rules="none"]) {
border-collapse: collapse;
}

/* caption inherits from table not table-outer */
caption {
display: table-caption;
text-align: center;
-moz-box-sizing: border-box;
}

table[align="center"] > caption {
margin-left: auto;
margin-right: auto;
}

table[align="center"] > caption[align="left"] {
margin-right: 0;
}

table[align="center"] > caption[align="right"] {
margin-left: 0;
}

tr {
display: table-row;
vertical-align: inherit;
}

col {
display: table-column;
}

colgroup {
display: table-column-group;
}

tbody {
display: table-row-group;
vertical-align: middle;
}

thead {
display: table-header-group;
vertical-align: middle;
}

tfoot {
display: table-footer-group;
vertical-align: middle;
}

/* for XHTML tables without tbody */
table > tr {
vertical-align: middle;
}

td {
display: table-cell;
vertical-align: inherit;
text-align: inherit;
padding: 1px;
}

th {
display: table-cell;
vertical-align: inherit;
font-weight: bold;
padding: 1px;
}

tr > form:-moz-is-html, tbody > form:-moz-is-html,
thead > form:-moz-is-html, tfoot > form:-moz-is-html,
table > form:-moz-is-html {
/* Important: don't show these forms in HTML */
display: none !important;
}

/* inlines */

q:before {
content: open-quote;
}

q:after {
content: close-quote;
}

b, strong {
font-weight: bolder;
}

i, cite, em, var, dfn {
font-style: italic;
}

tt, code, kbd, samp {
font-family: -moz-fixed;
}

u, ins {
text-decoration: underline;
}

s, strike, del {
text-decoration: line-through;
}

blink {
text-decoration: blink;
}

big {
font-size: larger;
}

small {
font-size: smaller;
}

sub {
vertical-align: sub;
font-size: smaller;
line-height: normal;
}

sup {
vertical-align: super;
font-size: smaller;
line-height: normal;
}

nobr {
white-space: nowrap;
}

/* titles */
abbr[title], acronym[title] {
border-bottom: dotted 1px;
}

/* lists */

ul, menu, dir {
display: block;
list-style-type: disc;
margin: 1em 0;
-moz-padding-start: 40px;
}

ol {
display: block;
list-style-type: decimal;
margin: 1em 0;
-moz-padding-start: 40px;
}

li {
display: list-item;
}

/* nested lists have no top/bottom margins */
ul ul, ul ol, ul dir, ul menu, ul dl,
ol ul, ol ol, ol dir, ol menu, ol dl,
dir ul, dir ol, dir dir, dir menu, dir dl,
menu ul, menu ol, menu dir, menu menu, menu dl,
dl ul, dl ol, dl dir, dl menu, dl dl {
margin-top: 0;
margin-bottom: 0;
}

/* 2 deep unordered lists use a circle */
ol ul, ul ul, menu ul, dir ul,
ol menu, ul menu, menu menu, dir menu,
ol dir, ul dir, menu dir, dir dir {
list-style-type: circle;
}

/* 3 deep (or more) unordered lists use a square */
ol ol ul, ol ul ul, ol menu ul, ol dir ul,
ol ol menu, ol ul menu, ol menu menu, ol dir menu,
ol ol dir, ol ul dir, ol menu dir, ol dir dir,
ul ol ul, ul ul ul, ul menu ul, ul dir ul,
ul ol menu, ul ul menu, ul menu menu, ul dir menu,
ul ol dir, ul ul dir, ul menu dir, ul dir dir,
menu ol ul, menu ul ul, menu menu ul, menu dir ul,
menu ol menu, menu ul menu, menu menu menu, menu dir menu,
menu ol dir, menu ul dir, menu menu dir, menu dir dir,
dir ol ul, dir ul ul, dir menu ul, dir dir ul,
dir ol menu, dir ul menu, dir menu menu, dir dir menu,
dir ol dir, dir ul dir, dir menu dir, dir dir dir {
list-style-type: square;
}

/* leafs */

/* <hr> noshade and color attributes are handled completely by
* the nsHTMLHRElement attribute mapping code
*/
hr {
display: block;
height: 2px;
border: 1px inset;
margin: 0.5em auto 0.5em auto;
color: gray;
-moz-float-edge: margin-box;
-moz-box-sizing: border-box;
}

hr[size="1"] {
border-style: solid none none none;
}

*|*:-moz-any-link img, img[usemap], object[usemap] {
border: 2px solid;
}

img:-moz-broken::before, input:-moz-broken::before,
img:-moz-user-disabled::before, input:-moz-user-disabled::before,
img:-moz-loading::before, input:-moz-loading::before,
applet:-moz-empty-except-children-with-localname(param):-moz-broken::before,
applet:-moz-empty-except-children-with-localname(param):-moz-user-disabled::before {
content: -moz-alt-content !important;
unicode-bidi: embed;
}

object:-moz-broken > *|*, applet:-moz-broken > *|*
object:-moz-user-disabled > *|*, applet:-moz-user-disabled > *|* {
/*
Inherit in the object's alignment so that if we aren't aligned explicitly
we'll end up in the right place vertically. See bug 36997. Note that this
is not !important because we _might_ be aligned explicitly.
*/
vertical-align: inherit;
}

img:-moz-suppressed, input:-moz-suppressed, object:-moz-suppressed,
embed:-moz-suppressed, applet:-moz-suppressed {
/*
Set visibility too in case the page changes display. Note that we _may_
want to just set visibility and not display, in general, if we find that
display: none breaks too many layouts. And if we decide we really do want
people to be able to right-click blocked images, etc, we need to set
neither one, and hack the painting code.... :(
*/
display: none !important;
visibility: hidden !important;
}

img[usemap], object[usemap] {
color: blue;
}

frameset {
display: block ! important;
overflow: -moz-hidden-unscrollable;
position: static ! important;
float: none ! important;
border: none ! important;
}

frame {
border: none ! important;
}

iframe {
border: 2px inset;
}

noframes {
display: none;
}

spacer {
position: static ! important;
float: none ! important;
}

canvas {
-moz-user-select: none;
}

/* focusable content: anything w/ tabindex >=0 is focusable */
abbr:focus, acronym:focus, address:focus, b:focus,
base:focus, big:focus, blockquote:focus, br:focus, canvas:focus, caption:focus,
center:focus, cite:focus, code:focus, col:focus, colgroup:focus, dd:focus,
del:focus, dfn:focus, dir:focus, div:focus, dl:focus, dt:focus, em:focus,
fieldset:focus, font:focus, form:focus, h1:focus, h2:focus, h3:focus, h4:focus,
h5:focus, h6:focus, hr:focus, i:focus, img:focus, ins:focus,
kbd:focus, label:focus, legend:focus, li:focus, link:focus, menu:focus,
ol:focus, p:focus, pre:focus, q:focus, s:focus, samp:focus,
small:focus, span:focus, strike:focus, strong:focus, sub:focus, sup:focus,
table:focus, tbody:focus, td:focus, tfoot:focus, th:focus, thead:focus,
tr:focus, tt:focus, u:focus, ul:focus, var:focus {
/* Don't specify the outline-color, we should always use initial value. */
outline: 1px dotted;
}

/* hidden elements */
area, base, basefont, head, meta, script, style, title,
noembed, param {
display: none;
}

/* media elements */
video > xul|videocontrols, audio > xul|videocontrols {
display: -moz-box;
-moz-box-orient: vertical;
-moz-binding: url("chrome://global/content/bindings/videocontrols.xml#videoControls");
}

video:not([controls]) > xul|videocontrols,
audio:not([controls]) > xul|videocontrols {
visibility: hidden;
}

audio:not([controls]) {
display: none;
}

/* emulation of non-standard HTML <marquee> tag */
marquee {
width: -moz-available;
display: inline-block;
vertical-align: text-bottom;
text-align: start;
-moz-binding: url('chrome://xbl-marquee/content/xbl-marquee.xml#marquee-horizontal');
}

marquee[direction="up"], marquee[direction="down"] {
-moz-binding: url('chrome://xbl-marquee/content/xbl-marquee.xml#marquee-vertical');
height: 200px;
}

/* PRINT ONLY rules follow */
@media print {

marquee { -moz-binding: none; }

}
</pre>

[[Category:CSS]]

Tips on using CSS with XML/TEI

2010-06-16T06:31:37Z

Brettz9: /* HTML to CSS Equivalents */ using Firefox's own

For those who are fairly familiar with using CSS with HTML or XHTML, one might be familiar enough with how to define colors, etc., but still remain unaware of how to make a simple stylesheet.

Since one cannot use .class-name as in X/HTML (though some processors might be able to use xml:id to be the target of the # id selector), one first ought to be familiar with the generic [http://www.w3.org/TR/CSS21/selector.html#attribute-selectors attribute selectors].

For example,

<code><pre><div type="chapter">...</pre></code>

Could be styled with:
<code><pre>div[type="chapter"] {}</pre></code>

Another important adjustment to make is that while X/HTML defines a default display behavior (e.g., <p> in HTML is block while <span> in HTML is inline), other XML is more generic and forces you to define which elements out to be defined as block (they will otherwise be rendered inline).

For example, for TEI, you might define the following:

<code><pre>p, div, div1, div2, div3 {display:block}</pre></code>

You can also specify inline elements by using <code>display:inline</code>

==HTML to CSS Equivalents==

(Display is inline by default unless indicated.)
(Note that in order to bypass the spam filter, some bogus spaces were added in the display: none; lines.)

// the following was obtained from resource://gre-resources/html.css , with the license terms under MPL 1.1/GPL 2.0/LGPL 2.1.

<pre>
@namespace url(http://www.w3.org/1999/xhtml); /* set default namespace to HTML */
@namespace xul url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

/* bidi */

[dir="rtl"] {
direction: rtl;
unicode-bidi: embed;
}
[dir="ltr"] {
direction: ltr;
unicode-bidi: embed;
}
bdo[dir] {
unicode-bidi: bidi-override;
}

/* To ensure http://www.w3.org/TR/REC-html40/struct/dirlang.html#style-bidi:
*
* "When a block element that does not have a dir attribute is transformed to
* the style of an inline element by a style sheet, the resulting presentation
* should be equivalent, in terms of bidirectional formatting, to the
* formatting obtained by explicitly adding a dir attribute (assigned the
* inherited value) to the transformed element." */

address, blockquote, body, caption, center, col, colgroup, dd, dir, div, dl, dt,
fieldset, form, h1, h2, h3, h4, h5, h6, hr, html, isindex, li, listing, map,
marquee, menu, noframes, ol, p, plaintext, pre, table, tbody, td, tfoot, th,
thead, tr, ul, xmp {
unicode-bidi: embed;
}

/* blocks */

html, div, map, dt, isindex, form {
display: block;
}

body {
display: block;
margin: 8px;
}

p, dl, multicol {
display: block;
margin: 1em 0;
}

dd {
display: block;
-moz-margin-start: 40px;
}

blockquote {
display: block;
margin: 1em 40px;
}

address {
display: block;
font-style: italic;
}

center {
display: block;
text-align: -moz-center;
}

blockquote[type=cite] {
display: block;
margin: 1em 0px;
-moz-padding-start: 1em;
-moz-border-start: solid;
border-color: blue;
border-width: thin;
}

span[_moz_quote=true] {
color: blue;
}

pre[_moz_quote=true] {
color: blue;
}

h1 {
display: block;
font-size: 2em;
font-weight: bold;
margin: .67em 0;
}

h2 {
display: block;
font-size: 1.5em;
font-weight: bold;
margin: .83em 0;
}

h3 {
display: block;
font-size: 1.17em;
font-weight: bold;
margin: 1em 0;
}

h4 {
display: block;
font-weight: bold;
margin: 1.33em 0;
}

h5 {
display: block;
font-size: 0.83em;
font-weight: bold;
margin: 1.67em 0;
}

h6 {
display: block;
font-size: 0.67em;
font-weight: bold;
margin: 2.33em 0;
}

listing {
display: block;
font-family: -moz-fixed;
font-size: medium;
white-space: pre;
margin: 1em 0;
}

xmp, pre, plaintext {
display: block;
font-family: -moz-fixed;
white-space: pre;
margin: 1em 0;
}

/* tables */

table {
display: table;
border-spacing: 2px;
border-collapse: separate;
margin-top: 0;
margin-bottom: 0;
/* XXXldb do we want this if we're border-collapse:collapse ? */
-moz-box-sizing: border-box;
text-indent: 0;
}

table[align="left"] {
float: left;
}

table[align="right"] {
float: right;
text-align: start;
}

table[rules]:not([rules="none"]) {
border-collapse: collapse;
}

/* caption inherits from table not table-outer */
caption {
display: table-caption;
text-align: center;
-moz-box-sizing: border-box;
}

table[align="center"] > caption {
margin-left: auto;
margin-right: auto;
}

table[align="center"] > caption[align="left"] {
margin-right: 0;
}

table[align="center"] > caption[align="right"] {
margin-left: 0;
}

tr {
display: table-row;
vertical-align: inherit;
}

col {
display: table-column;
}

colgroup {
display: table-column-group;
}

tbody {
display: table-row-group;
vertical-align: middle;
}

thead {
display: table-header-group;
vertical-align: middle;
}

tfoot {
display: table-footer-group;
vertical-align: middle;
}

/* for XHTML tables without tbody */
table > tr {
vertical-align: middle;
}

td {
display: table-cell;
vertical-align: inherit;
text-align: inherit;
padding: 1px;
}

th {
display: table-cell;
vertical-align: inherit;
font-weight: bold;
padding: 1px;
}

tr > form:-moz-is-html, tbody > form:-moz-is-html,
thead > form:-moz-is-html, tfoot > form:-moz-is-html,
table > form:-moz-is-html {
/* Important: don't show these forms in HTML */
display: none !important;
}

/* inlines */

q:before {
content: open-quote;
}

q:after {
content: close-quote;
}

b, strong {
font-weight: bolder;
}

i, cite, em, var, dfn {
font-style: italic;
}

tt, code, kbd, samp {
font-family: -moz-fixed;
}

u, ins {
text-decoration: underline;
}

s, strike, del {
text-decoration: line-through;
}

blink {
text-decoration: blink;
}

big {
font-size: larger;
}

small {
font-size: smaller;
}

sub {
vertical-align: sub;
font-size: smaller;
line-height: normal;
}

sup {
vertical-align: super;
font-size: smaller;
line-height: normal;
}

nobr {
white-space: nowrap;
}

/* titles */
abbr[title], acronym[title] {
border-bottom: dotted 1px;
}

/* lists */

ul, menu, dir {
display: block;
list-style-type: disc;
margin: 1em 0;
-moz-padding-start: 40px;
}

ol {
display: block;
list-style-type: decimal;
margin: 1em 0;
-moz-padding-start: 40px;
}

li {
display: list-item;
}

/* nested lists have no top/bottom margins */
ul ul, ul ol, ul dir, ul menu, ul dl,
ol ul, ol ol, ol dir, ol menu, ol dl,
dir ul, dir ol, dir dir, dir menu, dir dl,
menu ul, menu ol, menu dir, menu menu, menu dl,
dl ul, dl ol, dl dir, dl menu, dl dl {
margin-top: 0;
margin-bottom: 0;
}

/* 2 deep unordered lists use a circle */
ol ul, ul ul, menu ul, dir ul,
ol menu, ul menu, menu menu, dir menu,
ol dir, ul dir, menu dir, dir dir {
list-style-type: circle;
}

/* 3 deep (or more) unordered lists use a square */
ol ol ul, ol ul ul, ol menu ul, ol dir ul,
ol ol menu, ol ul menu, ol menu menu, ol dir menu,
ol ol dir, ol ul dir, ol menu dir, ol dir dir,
ul ol ul, ul ul ul, ul menu ul, ul dir ul,
ul ol menu, ul ul menu, ul menu menu, ul dir menu,
ul ol dir, ul ul dir, ul menu dir, ul dir dir,
menu ol ul, menu ul ul, menu menu ul, menu dir ul,
menu ol menu, menu ul menu, menu menu menu, menu dir menu,
menu ol dir, menu ul dir, menu menu dir, menu dir dir,
dir ol ul, dir ul ul, dir menu ul, dir dir ul,
dir ol menu, dir ul menu, dir menu menu, dir dir menu,
dir ol dir, dir ul dir, dir menu dir, dir dir dir {
list-style-type: square;
}

/* leafs */

/* <hr> noshade and color attributes are handled completely by
* the nsHTMLHRElement attribute mapping code
*/
hr {
display: block;
height: 2px;
border: 1px inset;
margin: 0.5em auto 0.5em auto;
color: gray;
-moz-float-edge: margin-box;
-moz-box-sizing: border-box;
}

hr[size="1"] {
border-style: solid none none none;
}

*|*:-moz-any-link img, img[usemap], object[usemap] {
border: 2px solid;
}

img:-moz-broken::before, input:-moz-broken::before,
img:-moz-user-disabled::before, input:-moz-user-disabled::before,
img:-moz-loading::before, input:-moz-loading::before,
applet:-moz-empty-except-children-with-localname(param):-moz-broken::before,
applet:-moz-empty-except-children-with-localname(param):-moz-user-disabled::before {
content: -moz-alt-content !important;
unicode-bidi: embed;
}

object:-moz-broken > *|*, applet:-moz-broken > *|*
object:-moz-user-disabled > *|*, applet:-moz-user-disabled > *|* {
/*
Inherit in the object's alignment so that if we aren't aligned explicitly
we'll end up in the right place vertically. See bug 36997. Note that this
is not !important because we _might_ be aligned explicitly.
*/
vertical-align: inherit;
}

img:-moz-suppressed, input:-moz-suppressed, object:-moz-suppressed,
embed:-moz-suppressed, applet:-moz-suppressed {
/*
Set visibility too in case the page changes display. Note that we _may_
want to just set visibility and not display, in general, if we find that
display: none breaks too many layouts. And if we decide we really do want
people to be able to right-click blocked images, etc, we need to set
neither one, and hack the painting code.... :(
*/
display: none !important;
visibility: hidden !important;
}

img[usemap], object[usemap] {
color: blue;
}

frameset {
display: block ! important;
overflow: -moz-hidden-unscrollable;
position: static ! important;
float: none ! important;
border: none ! important;
}

frame {
border: none ! important;
}

iframe {
border: 2px inset;
}

noframes {
display: none;
}

spacer {
position: static ! important;
float: none ! important;
}

canvas {
-moz-user-select: none;
}

/* focusable content: anything w/ tabindex >=0 is focusable */
abbr:focus, acronym:focus, address:focus, b:focus,
base:focus, big:focus, blockquote:focus, br:focus, canvas:focus, caption:focus,
center:focus, cite:focus, code:focus, col:focus, colgroup:focus, dd:focus,
del:focus, dfn:focus, dir:focus, div:focus, dl:focus, dt:focus, em:focus,
fieldset:focus, font:focus, form:focus, h1:focus, h2:focus, h3:focus, h4:focus,
h5:focus, h6:focus, hr:focus, i:focus, img:focus, ins:focus,
kbd:focus, label:focus, legend:focus, li:focus, link:focus, menu:focus,
ol:focus, p:focus, pre:focus, q:focus, s:focus, samp:focus,
small:focus, span:focus, strike:focus, strong:focus, sub:focus, sup:focus,
table:focus, tbody:focus, td:focus, tfoot:focus, th:focus, thead:focus,
tr:focus, tt:focus, u:focus, ul:focus, var:focus {
/* Don't specify the outline-color, we should always use initial value. */
outline: 1px dotted;
}

/* hidden elements */
area, base, basefont, head, meta, script, style, title,
noembed, param {
display: none;
}

/* media elements */
video > xul|videocontrols, audio > xul|videocontrols {
display: -moz-box;
-moz-box-orient: vertical;
-moz-binding: url("chrome://global/content/bindings/videocontrols.xml#videoControls");
}

video:not([controls]) > xul|videocontrols,
audio:not([controls]) > xul|videocontrols {
visibility: hidden;
}

audio:not([controls]) {
display: none;
}

/* emulation of non-standard HTML <marquee> tag */
marquee {
width: -moz-available;
display: inline-block;
vertical-align: text-bottom;
text-align: start;
-moz-binding: url('chrome://xbl-marquee/content/xbl-marquee.xml#marquee-horizontal');
}

marquee[direction="up"], marquee[direction="down"] {
-moz-binding: url('chrome://xbl-marquee/content/xbl-marquee.xml#marquee-vertical');
height: 200px;
}

/* PRINT ONLY rules follow */
@media print {

marquee { -moz-binding: none; }

}
</pre>

[[Category:CSS]]

Tips on using CSS with XML/TEI

2010-06-16T06:19:32Z

Brettz9: /* HTML to CSS Equivalents */ adding parenthesizing around non-showing elements

Tips on using CSS with XML/TEI

2010-06-16T06:18:42Z

Brettz9: /* HTML to CSS Equivalents */

Tips on using CSS with XML/TEI

2010-06-16T06:17:31Z

Brettz9: /* HTML to CSS Equivalents */ spacing

Tips on using CSS with XML/TEI

2010-06-16T06:16:30Z

Brettz9: /* HTML to CSS Equivalents */ +div, span, etc.

Tips on using CSS with XML/TEI

2010-06-16T06:05:41Z

Brettz9: /* HTML to CSS Equivalents */ +blockquote

Tips on using CSS with XML/TEI

2010-06-16T05:58:55Z

Brettz9: /* HTML to CSS Equivalents */ +etc

Tips on using CSS with XML/TEI

2010-06-16T05:58:36Z

Brettz9: html->CSS equivs

Comprehensive CSS Stylesheet

2010-06-16T04:39:14Z

Brettz9: /* s */ make indented

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T04:38:46Z

Brettz9: /* s */ +soCalled (applyRend not yet applied for this or others)

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled:before {content:'‘'} soCalled {display:inline;} soCalled:after {content:'’'} /* Quote style is parameterized in XSL; note: content can also accept 'open-quote' and 'close-quote', but the default is as already included in the rule */
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T04:24:27Z

Brettz9: /* c */ +castList comment fix

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements as a direct child castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T04:22:00Z

Brettz9: /* s */ +se x

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements inside castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (XSL has not yet covered (namesdates module)) /* space-separated for spam filter! */
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T04:13:08Z

Brettz9: /* r */ semicolon

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements inside castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" ";}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T04:12:30Z

Brettz9: +placeName, persName, name, genName, geogName, roleName

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements inside castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
genName {display:inline;}
* geo
* geoDecl
* geogFeat
geogName {display:inline;}
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

name {display:inline;}
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
persName {display:inline;}
* person
* personGrp
* phr
* physDesc
* place
placeName {display:inline;}
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
roleName {display:inline;}
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T04:03:31Z

Brettz9: /* c */ +castList

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
castList {} /* Note: has additional rules: */
castList {display:block;} /* applies whether children are head or not */
/* Note: for this to mirror the XSL exactly, head would always need to be preceding other elements inside castList */
castList > head {display:inline; font-style:italic;}
castList > *:not(head) {margin-left: 40px;} /* If children of castList needed their own indents, then it should be relative to this (if possible) */

* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T03:40:10Z

Brettz9: /* c */ +catDesc

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc (Only defined in XSL conditionally if using catRef)
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T03:38:51Z

Brettz9: /* c */ +note on additional rules

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
catRef {} /* Note: has additional rules: */
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T03:36:00Z

Brettz9: +catRef

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
catRef {}
catRef + catRef:before {'\A'} /* Add line break if preceded by another catRef */
catRef:after {content:attr(scheme); display:inline; font-style:italic;} /* Add scheme in italics */
/*
Commenting out as XPath not currently supported in CSS as needed by third 'after'
catRef:after(2) {content:':'}*//* Requires CSS3 to add such additional 'after' content; See http://www.w3.org/TR/css3-content/#nesting or http://www.w3.org/TR/css3-content/#inserting0 */
/*
catRef:after(3) {content: <not possible to reference target's catDesc unless XPath gets added to CSS>} */
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-16T03:00:10Z

Brettz9: +2 not covered

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode (XSL has not yet covered (from header module))
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords (XSL has not yet covered (from header module))
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Category:CSS

2010-06-08T12:13:04Z

Brettz9: +see also

This page collects together any pages relating to CSS (Cascading Style Sheets) for TEI resources. The main TEI website has [http://www.tei-c.org/Stylesheets/ a page about stylesheets] as well. 

All of the stylesheets posted here are freely available for public use. They are offered as is, and we make no guarantees about their usefulness or effectiveness. Please feel free to experiment with them. If you make any useful revisions, please post the modified version here.
The [[call for stylesheets]] includes more details about what we are seeking and how you can help.

----
'''To contribute a stylesheet, please create a new page within this category and paste it there, between <nowiki><pre><nowiki>...</nowiki></pre></nowiki> tags. Documenting it will be appreciated.'''

==See also==
* [[tips on using CSS with XML/TEI]]
* http://tei.svn.sourceforge.net/viewvc/tei/trunk/TEICSS/tei.css?view=markup
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/

[[Category:Code]]

Comprehensive CSS Stylesheet

2010-06-08T08:40:06Z

Brettz9: attribute issue

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer but not including the integer (e.g., space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-08T05:38:23Z

Brettz9: link

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate (see [[Formatting TEI documents]] on how there is a need for this despite TEI being agnostic as to output formatting), at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer (e.g., item.n => li.value or space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Formatting TEI documents

2010-06-08T05:37:06Z

Brettz9: /* Specific formatting for specific elements (and any attributes) */

This page aims to spell out some considerations when formatting TEI documents or considering how mark-up issues inter-relate with (or should not inter-relate with) output formatting. It is based on a proposed chapter draft at http://www.tei-c.org/Activities/Council/Working/tcw10.xml

Per http://www.tei-c.org/Activities/Council/Meetings/tcm38.xml?style=raw , the TEI "Council reached a consensus that the draft document is not suitable as a formal chapter of the Guidelines, largely because the technologies and procedures used for output rendering change frequently and are not under the control of the TEI Consortium (e.g., XSLT processors, CSS standards, etc.)", but I wanted to offer it here in case others wish to revise or expand on it.

----
While TEI makes no claims about how a document is to be rendered--except to the extent that it allows description of the original formatting and to the extent that publishers wish to reflect that formatting--it is a general expectation that the TEI documents a project is creating can be rendered at some point in a more human-readable manner. While the desired formatting should not prompt one to violate the TEI Abstract model by altering the semantics of a document in order to adjust output formatting, the process of creating formatting output (or even well before doing so), may lead a project to reconsider some aspects of its semantic markup, as well as the more conventional means of adjusting a stylesheet, so the issues raised here go beyond the work of a designer. This chapter will discuss various issues related to formatting a TEI document.

==Respecting the original formatting==

In order to fully respect the original formatting of a document, it is necessary to consider (and thoroughly use) the global @rendition attribute and/or the @render attribute on <tagUsage> elements to point to <rendition> elements and/or the global @rend attribute to provide its own definition without referring elsewhere.

While semantic hooks and reliance on the typical formatting of specific tags for cases where @rend and @rendition are not needed to override typical behaviors might be sufficient to create an output document reflecting the formatting of the original document, if the original rendering is important information to preserve, this can be done more explicitly by ensuring that all elements are given a <tagUsage> element which uses its @render attribute to point to a <rendition> element which contains the styling details that can be applied to all instances of the tag. In this way, there is no ambiguity about how a tag is to be rendered. This is also recommended practice when <tagUsage> elements are provided. (see http://tei.oucs.ox.ac.uk/P5/Guidelines-web/en/html/HD.html#HD57 ).

However, note that <tagUsage> elements do not allow for the specification of a default rendering behavior for element-attribute combinations--only for specific elements regardless of any attributes or attribute values. They also do not allow the specification of a default behavior for an element based on its position (e.g., <quote> within <cit> ), so as this point, it may be inevitable to heavily rely on @rend and @rendition if one must thoroughly indicate this original formatting, independent of a stylesheet.

For maximum specificity in encoding formatting details, the content supplied within <rendition> and @rend ought to use a formal formatting language. However, besides not specifying a particular formatting language that ought to be used, at present TEI does not offer a fail-safe means of translating @rend and <rendition> content into a stylesheet (even though this information could potentially be used to create @style attribute content, or, by using XSLT 2.0, simultaneously create a CSS stylesheet alongside the X/HTML output.

While it might be sufficient in most cases, there is no formal means at present to express that a particular style rule should target CSS pseudo-elements (like :before, :after, :first), such as one might wish to do in specifying the addition of distinct content at the beginning or end of a tag (e.g., adding left and right curly quotes to a <q> element; this is nothing to speak of needing to target a specific attribute, say xml:lang to determine which type of quotation marks to add). And even where the output does faithfully reflect the original, it should be fairly common to need to optimize the resulting CSS stylesheet, since it would likely be fairly large with there being no means besides <tagUsage> to indicate a behavior to apply to element-attribute combinations or elements in particular positions.

==Original vs. output rendering==

One might find oneself tempted to force the rendition mechansims in TEI (@rend or @rendition or <tagUsage's> @render with <rendition> ) to go beyond their intended use for describing the original rendering of a document. However, it is important to keep in mind that if one wishes to control how the formatting will be output, independently of the original formatting (adding details of formatting not expressed about the original with the TEI render mechanisms or overriding these details), one must not subvert the semantics of a TEI document (at the risk of introducing TEI non-conformance and interoperability issues) for the sake of controlling formatting--that should instead be handled by a stylesheet.

This might necessitate a different stylesheet or, as is probable for most cases, modifications to the default stylesheets provided by TEI, if the parameter options (assuming XSL stylesheets are used) are insufficient to express a project's output requirements. It is, for example, possible to allow the stylesheets to recognize multiple attributes, even at the same time.

==Returning changes to the default stylesheets==

The stylesheets from TEI are evolving with the TEI project, however, so it may be possible that the TEI project might be open to certain changes (whether optional or required) to its default stylesheets, if the changes offered may be of interest to a wider audience and TEI has the resources to implement the changes. Given that the code of these stylesheets is open source, it may benefit both TEI and its users as well as an individual project for stylesheet improvements (or other TEI resources for that matter) to be returned back to the community, as it precludes the individual project from needing to make modifications each time an update occurs.

With more standard (but not standardized) styling expectations (and stylesheet), the more likely that TEI processing applications might be used to render TEI in a familiar format (such as when obtained directly off the web, etc.), even while allowing publishers' full freedom to deviate from such common conventions if they wish.

==Influence of formatting (or accessibility) concerns on markup==

While one should not subvert the semantics of a TEI document in order to control formatting, besides customizing a stylesheet alone, the viewing of a formatted document might prompt a project to consider changes to the original TEI documents, such as:

# giving a more detailed encoding of the original rendering (as that information can be used to produce output rendering, assuming again that the original document being represented indeed possesses this rendering), using <rendition> , <tagUsage> render, @rendition, and @rend
# adding more semantic "hooks" whether this is the use of hitherto unused elements or attributes such as @n or @type (potentially with the adding of generic elements like <seg> ) which can provide more semantic detail about certain text that can in turn be targeted by a stylesheet to provide more granular control in output formatting. This may also have the benefit of providing more semantic richness to the document (ideally using the more specific elements already recommended for this purpose). Such semantic 'hooks' can also be of the variety that ensures that the output formatting includes sufficient accessibility features such as to make available alternative text along with any graphics or images that could not otherwise be interpreted by a speech browser.

==Semantic information and output formatting==

Besides formatting concerns leading one to add additional semantic distinctions into a TEI document, one may also wish to encode a certain degree of semantic information (to the extent allowed in the output formatting language) into one's formatting output and consider the extent to which output formatting markup is separated from any more generic output structural markup (e.g., creating CSS to hold styles with XHTML used to present the structure or encoding structural and formatting markup together). These are both discussed below.

===Encoding semantic information within formatted output===

While it may often be the case that TEI will be converted to a formatted output in which semantic information is lost, certain output formats allow some if not all semantic information to be retained in some manner. For example, XHTML can use the approach of microformats (http://microformats.org) to use the global and generic XHTML @class attribute to contain information such as the original TEI tag name. While it would likely be too cumbersome to originate documents in such a format (assuming all TEI semantics could be encoded with such an approach), it offers the advantage that one might, for example, use a web browser to obtain a document already pre-rendered, yet use a microformat processor within the browser (possibly available as a browser extension) to search for semantic information.

===Encoding formatting within structural and semantic output===

It has become a generally recommended practice for even XHTML documents on the web to separate their formatting content (as with CSS) into a separate file from the structural content (of paragraphs, generic divisions, etc.). This offers various advantages such as speed in downloading (by browser caching for repeatedly used stylesheet files or by those using speech browsers being able to avoid downloading visually-oriented stylesheets), or flexibility in subsequent style changes. While one might define an XSL stylesheet to create specific XHTML @class attribute values which are associated with those classes targeted in a predefined CSS stylesheet, XSLT 2.0 might be employed to utilize information such as contained within @rend or <rendition> elements to specify the creation of a CSS document while also simultaneously creating the XHTML output document. See the sections on preserving original formatting.

Despite the generally recommended practice of separating styles from structure and semantic information, given the present absence of a means of making queries which utilize style information contained in separate files, it may be conceivable for some to wish to have their formatting output mixed in with structural output (the @style attribute might be harder to parse in a query than if specific XHTML formatting structures were used--even though these may be deprecated in later versions)--just as one might prefer to encode say italic emphasis using <emph n="italic" rend="font-style:italic"> rather than use a more formal but correct syntax of <emph rend="font-style: italic;"> since the former is easier to parse -- so that queries can take advantage of both styling information and/or semantic information. For example, if one views a document and sees that italic text is used for emphasis, one might wish to search for a certain phrase contained within italic text, for example, because one recalled the text occurring there, or because one identified a pattern represented by italic text but where one did not know what the exact name of the pattern was, and thus not knowing what specific tag one must search for to find the desired text.

==General categories of elements to consider in formatting (or not formatting at all)==

Before considering the usual rendering and default rendering options for specific elements (along with any specific attributes), it is worth considering some general issues pertaining to certain types of elements.

===Likelihood of printing out specific elements===

Elements differ in the likelihood a project will wish to render them in a formatted output document. They range from editorial information which might never be printed out for common viewing, to elements which will sometimes be printed out (such as a <choice> listing the original text and a regularized or corrected form) to elements such as paragraphs which almost certainly will be printed out.

For the case of those which will always be printed out, one can make their styling explicit by using <tagUsage> elements with a @render attribute pointing to a <rendition> element with the styling details (and optionally the code). One might optionally even indicate specific elements which should not be displayed (though depending on the stylesheet language, this might not strictly be necessary).

Moreover, a stylesheet might wish to depend on element-specific or global attributes (whether semantic or rendition-related) to target elements with or without these attributes or with specific values to display or not display them selectively.

Elements which occur in the header, will generally not be printed out, though for some project's purposes, display of this information (e.g., bibliographic data) may be useful to include in the formatting output.

While other elements that occur within the running text will generally be printed out, it is important to understand that with TEI--which, as cannot be emphasized enough, is not a formatting language--this will not always be the case. If one has editorial information that should not be printed out within the running text (or at least should not appear alongside the running text), as a project might not wish the encoder-added information to disrupt the flow of the text (e.g., of a narrative) and for which it might even be considered irreverent by some viewers (such as for scriptural works), it will be important to be aware of all such tags that a project might not want printed out so that the stylesheet (possibly in conjunction with special semantic TEI markup if not markup indicating original rendering) does not display those tags' content.
Elements which are defined by the following macros are generally not to be displayed:

# macro.limitedContent (http://www.tei-c.org/release/doc/tei-p5-doc/html/ref-macro.limitedContent.html ): desc, fDescr, figDesc, fsDescr, meeting, rendition, tagUsage, witness
# macro.phraseSeq.limited (http://www.tei-c.org/release/doc/tei-p5-doc/html/ref-macro.phraseSeq.limited.html ): activity, age, authority, channel, classCode, constitution, creation. derivation, domain, factuality, funder, interaction, interp, langKnown, language, locale, metSym, preparedness, principal, purpose, resp, span, sponsor, valDesc

Moreover, there are some elements such as those in model.noteLike ( <note> and <witDetail> ) which while they might occur in the outputted document, might also in other cases or within some projects not always be rendered if at all. model.global.meta with members such as alt, altGrp, certainty, fLib, fs, fvLib, index, interp, interpGrp, join, joinGrp, link, linkGrp, respons, span, spanGrp, and timeline as well as elements containing the global @exclude attribute may or may not be output when included within a document.

Still others include items such as may be contained within <choice> : abbr, am, corr, ex, expan, orig, reg, seg, sic, unclear .. A project may need to consider whether to output these elements with both choices being shown in some manner (even as a mere tooltip that is exposed when certain text is hovered over) or whether to only show one of the choices (such as that reflecting the original or some regularization, correction, expansion, or abbreviation).

Likewise with elements belonging to model.pPart.transcriptional: add, app, corr, damage, del, orig, reg, restore, sic, supplied, unclear . One may or may not wish to indicate <supplied> text for example, or choose how to format damaged sections in some particular manner.

(any others????)

Since there is no way of knowing whether some of the elements mentioned above such as <note> refer to text that should be printed out or not, one must rely on other mechanisms to specify or glean this information. One way would be to use attributes, such as @resp to detect whether the note was the responsibility of a markup editor of the document, or whether it was provided by an original annotator of the document. However, as the detection of this might not always be clear (especially if the markup annotator also served as the original annotator), the user of other attributes such as @type, or where @type is not available, possibly @n or even xml:id might be used.

Note that despite its being listed above, an element such as <figDesc> , while it might not normally be displayed immediately to a visual browser, might still nevertheless be important (or even required in some formatting languages or in use with projects needing by law to adhere to accessibility regulations) for the sake of being accessible to those with visual disabilities who might depend on speech browsers or tooltips to be able to get a sense of what a particular graphic, photograph, etc. was displaying. It is certainly good practice to follow such an encoding, both within TEI documents and in the formatted output, where available.

===Behaviour within <corr> and similar elements===

One exception to @rend, @rendition (or their absence) indicating original formatting is that within a <corr> tag.

The addition of a @rend within <corr> (or <reg> ) would apply to an intended output formatting, rather than to the original formatting as it normally does.
<choice><sic><title level="j" rend="noitalic">The Times</title></sic><corr><title level="j" rend="italic">The Times</corr></choice>
Likewise, especially if the default rendering of <title> were specified by a <tagUsage> and <rendition> element (here to indicate a title as being by default in italic), the absence of @rend or @rendition would still imply a change of formatting:
<choice><sic><title level="j" rend="noitalic">The Times</title></sic><corr><title level="j">The Times</corr></choice>

===Items needing replication===

Some elements or elements with certain attributes may need special consideration for output such as @copyOf or <join> , as these might indicate that certain formatting output might need to be created such as might (as with other cases described earlier) not be evident by simply stripping the markup out of the document.

===Text attributes===

Most attributes are used with coded values, as they are not mean to represent human language or to be displayed. Text attributes represent the exception to this, though it is commonly preferred for an XML language to represent these attributes as elements so that further nested subelements representing markup at the phrasal level, etc. can be added within as needed.

Text attributes have generally been removed from TEI, and some of the ones that remain one might not wish to output in a formatted version anyways, but if one wishes to include, for example, @reason in one's output, one will be unable to add styling which depends on child elements for more specific formatting since the information is expressed within an attribute (but one can style differently depending on the element's @xml:lang, as that does apply for text attributes, as well as any other attributes on the element). Likewise for the dictionary attributes, @expand, @norm, @split, @value, and @orig which represent the remaining text attributes????.

((((Syd prepared a list of potential text attributes to review to see if they were still text attributes--it'd be nice to be able to give such an exhaustive list here.))))

I think the element-specific details might be logically incorporated as documentation elements within XSL that could be extracted for automatic inclusion within the TEI reference pages, making clear that the formatting discussed is only that of the default behavior used in TEI-provided stylesheets (though also discussing the range of options that the stylesheet makes available through parameters). I really think giving awareness of these formatting issues in the context of considering these elements would be more helpful than waiting for people to discover them separately in the stylesheets.

==Consideration of default transformation behavior==

While, as mentioned earlier, there is no required mapping of TEI elements and attributes to specific output document structures (e.g., XHTML/CSS, LaTeX, etc.), the fact that TEI provides a default set of stylesheets to work with (albeit a parameterized one) and that these are presumably well-used [by the number of downloads????] indicates that there are a general set of expectations about how most TEI structures will appear when output. The effort required to create one's own stylesheets from scratch for such a large vocabulary as TEI provides, or even to significantly modify existing stylesheets (no less each time as improvements and adjustments are made to the default files), also makes the understanding of how documents will be transformed an imperative for many projects. Thus, it becomes necessary to understand how TEI might commonly be transformed (or understood to be transformed), even beyond the extent to which the stylesheets themselves are documented and express (mostly in technical language) the templates used to transform TEI into a formatting language.

The default stylesheets provided by TEI serve as a good basis for discussion on how formatting can be performed and are documented here for the sake of those who wish to know how each structure they might use in a TEI document might be rendered by default. The stylesheets nor this discussion should be taken as any kind of requirement to use these stylesheets as a base, or even at all.

===Specific formatting for specific elements (and any attributes)===

(to be displayed on reference pages?)

See [[Comprehensive CSS Stylesheet]] for a beginning at describing default styling (attempting to mimic the XSL stylesheets) as expressed in the simple, precise, and usually intuitive, but still technical, language CSS.

===Specific formatting for specific categories of formatting (images, etc.)===

(to be compiled after reference pages have their information fleshed out)

Comprehensive CSS Stylesheet

2010-06-08T05:30:27Z

Brettz9: noting elements in speech module (not yet supported in XSL either)

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer (e.g., item.n => li.value or space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident (speech module: XSL has not yet covered)
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic (speech module: XSL has not yet covered)

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause (speech module: XSL has not yet covered)
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift (speech module: XSL has not yet covered)
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u (speech module: XSL has not yet covered)
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal (speech module: XSL has not yet covered)

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing (speech module: XSL has not yet covered)

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-07T03:15:02Z

Brettz9: +disadvanage

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer (e.g., item.n => li.value or space.extent => number of spaces) a separate rule must be created for each possible attribute value)
# (Another disadvantage of CSS in general is being unable to create certain kinds of output such as form controls, but in the case of TEI, we hardly need this.)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-07T03:13:48Z

Brettz9:

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.).

Advantages of CSS over XSL might include:
# Simpler for maintenance/alteration (though CSS can still be combined with simpler XSL as needed)
# Downloading (and parsing?) is faster
# Wider browser support (and for browser caching?)
# Allows DOM and other manipulation directly on semantically-named TEI elements (though admittedly, use of frameworks like jQuery may make traversal of X/HTML as easy or easier)
# TEI could potentially be used as is in HTML (though empty self-closing elements will not be treated properly unless changed to <elem></elem> form and namespaces will not be present) in addition to true XHTML.

Disadvantages:
# Does not allow for certain kinds of transformations (though again, CSS can be combined with a simple XSL stylesheet which preserves TEI except in cases where needed)
# Is cumbersome for certain variable structures (e.g., for values varying by integer (e.g., item.n => li.value or space.extent => number of spaces) a separate rule must be created for each possible attribute value)

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to make equivalents for XSLT templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible (besides rend/rendition which may later be done globally for all elements, as these are indeed globals).

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing

==x==

* xr

==y==

(none)

==z==
z

* zone

==References used==
* http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-07T02:53:06Z

Brettz9: /* c */ correction re: Firefox support

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.):

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to use templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible.

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing

==x==

* xr

==y==

(none)

==z==
z

* zone

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-06T13:34:14Z

Brettz9: /* r */ +roleDesc

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.):

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to use templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible.

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too (though Firefox seems to have a bug with it), but the important thing is that this is an empty element */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
roleDesc { margin-left: 40px; margin-right: 40px; } roleDesc > *:not(p) {display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing

==x==

* xr

==y==

(none)

==z==
z

* zone

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-06T12:52:07Z

Brettz9: +most drama elements

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.):

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to use templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible.

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
actor {display:inline; font-style: italic;}
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too (though Firefox seems to have a bug with it), but the important thing is that this is an empty element */}
camera {display:inline; font-style: italic;}
caption {display:inline; font-style: italic;}
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
role {display:inline; font-style: italic;}
* roleDesc
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
set {display:inline; font-style: italic;}
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
sound {display:inline; font-style: italic;}
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
stage {font-style: italic; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
tech {display:inline; font-style: italic;}
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
view {display:inline; font-style: italic;}
* vocal

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing

==x==

* xr

==y==

(none)

==z==
z

* zone

[[Category:CSS]]

Comprehensive CSS Stylesheet

2010-06-06T12:37:31Z

Brettz9: /* t */ +term

The following is an attempt to gradually build CSS for each TEI element, paralleling the default TEI stylesheets (while also potentially serving as a kind of discussion center for how the stylesheets ought to operate, at least for issues pertaining solely to formatting as opposed to semantics), by indicating here necessary deviations from the XHTML stylesheets (due to CSS constraints) or potentially desirable alternatives, etc.):

Per CSS Namespaces, one can use either
@namespace "http://www.tei-c.org/ns/1.0"

or

@namespace tei "http://www.tei-c.org/ns/1.0"

...but we will use the former since we will presume the stylesheet will be primarily (if not exclusively) for TEI.

We will not be able to use templates like rendToClass (e.g., ab) or applyRend (emph), applyRendition (emph) since we cannot (nor do we need to) add an id or class (though @rend or @rendition would be useful to utilize, there is no "eval()"-like code in CSS; however, we could test against predefined values like "bold" (maybe as a global * or at least the elements using these in the stylesheets (emph, hi, ...))).

All fields below should be complete for an element, or otherwise noted that it is incomplete, so that it can otherwise be assumed that the CSS has been completely applied as far as possible.

==a==
ab {display:block;}
* abbr
* accMat
* acquisition
* activity
* actor
* add
* addName
* addSpan
* additional
* additions
addrLine {display:block;}
address {display:block; /* font-style:italic; If wish to appear as HTML addresses are rendered by default, at least in Firefox */}
* adminInfo
* affiliation
* age
* alt
* altGrp
* altIdent
* altIdentifier
* am
* analytic
* anchor
* app
* appInfo
* application
* arc
* argument
att {display:inline; font-weight:bold;} att:before {content:"@"}
* attDef
* attList
* attRef
* author
* authority
* availability

==b==

* back
* bibl
* biblFull
* biblScope
* biblStruct
* bicond
* binary
* binaryObject
* binding
* bindingDesc
* birth
* bloc
* body
* broadcast
byline {display:block;}

==c==

* c
* cRefPattern
caesura:before {display:inline; content:"\a0\a0\a0\a0"; /* could be :after too (though Firefox seems to have a bug with it), but the important thing is that this is an empty element */}
* camera
* caption
* case
* castGroup
* castItem
* castList
* catDesc
* catRef
* catchwords
* category
* cb
* cell
* certainty
* change
* channel
* char
* charDecl
* charName
* charProp
* choice
* cit
* cl
* classCode
* classDecl
* classSpec
* classes
* climate
* closer
code {display:inline; font-family:monospace;}
* collation
* collection
* colloc
* colophon
* cond
* condition
* constitution
* constraint
* constraintSpec
* content
* corr
* correction
* country
* creation
* custEvent
* custodialHist

==d==

* damage
* damageSpan
* datatype
* date
* dateline
* death
* decoDesc
* decoNote
* def
* default
* defaultVal
del {display:inline; text-decoration: line-through;}
* delSpan
* depth
* derivation
* desc
* dictScrap
* dim
* dimensions
* distinct
* distributor
* district
* div
* div1
* div2
* div3
* div4
* div5
* div6
* div7
* divGen
* docAuthor
* docDate
* docEdition
* docImprint
* docTitle
* domain

==e==

* eLeaf
* eTree
* edition
* editionStmt
* editor
* editorialDecl
* education
* eg
* egXML
* elementSpec
* email
emph {display:inline; font-style:italic;}
* encodingDesc
* entry
* entryFree
epigraph {display:block;}
* epilogue
* equipment
* equiv
* etym
* event
* ex
* exemplum
* expan
* explicit
* extent

==f==

* f
* fDecl
* fDescr
* fLib
* facsimile
* factuality
* faith
* figDesc
* figure
* fileDesc
* filiation
* finalRubric
* floatingText
* floruit
* foliation
foreign {display:inline;}
* forename
* forest
* forestGrp
* form
* formula
* front
* fs
* fsConstraints
* fsDecl
* fsDescr
* fsdDecl
* fsdLink
* funder
* fvLib
* fw

==g==

* g
* gap
* gen
* genName
* geo
* geoDecl
* geogFeat
* geogName
gi:before {display:inline;content:"<"} gi:after {display:inline;content:">"}
gloss {display:inline;}
* glyph
* glyphName
* gram
* gramGrp
* graph
* graphic
* group

==h==

* handDesc
* handNote
* handNotes
* handShift
* head
* headItem
* headLabel
* height
* heraldry
hi {display:inline; font-weight:bold;}
* history
* hom
* hyph
* hyphenation

==i==

* iNode
* iType
ident[type] {display:inline; font-weight:bold;} ident:not([type]) {display:inline; } /* Just as the stylesheet allows for different types; a specific type could be styled by ident[type="XXX"] */
* idno
* if
* iff
* imprimatur
* imprint
* incident
* incipit
* index
* institution
* interaction
* interp
* interpGrp
* interpretation
* item

==j==

* join
* joinGrp

==k==

* keywords
* kinesic

==l==

l {display:block;}
label {display:inline;}
* lacunaEnd
* lacunaStart
* lang
* langKnowledge
* langKnown
* langUsage
* language
* layout
* layoutDesc
lb {display:block;}
* lbl
* leaf
* lem
lg {display:block;}
* link
* linkGrp
* list
* listBibl
* listEvent
* listNym
* listOrg
* listPerson
* listPlace
* listRef
* listWit
* localName
* locale
* location
* locus
* locusGrp

==m==

* m
* macroSpec
* mapping
* material
* measure
* measureGrp
* meeting
* memberOf
mentioned {display:inline;}
* metDecl
* metSym
* milestone
* moduleRef
* moduleSpec
* monogr
* mood
* move
* msContents
* msDesc
* msIdentifier
* msItem
* msItemStruct
* msName
* msPart
* musicNotation

==n==

* name
* nameLink
* namespace
* nationality
* node
* normalization
* note
* notesStmt
* num
* number
* numeric
* nym

==o==

* oRef
* oVar
* objectDesc
* occupation
* offset
* opener
* org
* orgName
* orig
* origDate
* origPlace
* origin
* orth

==p==

* p
* pRef
* pVar
* particDesc
* pause
* pb
* pc
* per
* performance
* persName
* person
* personGrp
* phr
* physDesc
* place
* placeName
* population
* pos
* postBox
* postCode
* postscript
* precision
* preparedness
* principal
* profileDesc
* projectDesc
* prologue
* pron
* provenance
* ptr
* pubPlace
* publicationStmt
* publisher
* purpose

==q==

* q
* quotation
* quote

==r==

* rdg
* rdgGrp
* re
* recordHist
* recording
* recordingStmt
* ref
* refState
* refsDecl
* reg
* region
* relatedItem
* relation
* relationGrp
* remarks
* rendition
* repository
* residence
resp:after {content:" "}
respStmt {display:inline;}
* respons
* restore
* revisionDesc
* rhyme
* role
* roleDesc
* roleName
* root
* row
* rs
* rubric

==s==

* s
* said
salute {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* samplingDecl
* schemaSpec
* scriptStmt
* seal
* sealDesc
* secFol
seg {display:inline;}
* segmentation
* sense
* series
* seriesStmt
* set
* setting
* settingDesc
* settlement
* se x (separated for spam filter)
* shift
sic {display:inline;} sic:after {content: " (sic)"}
* signatures
signed {text-align:left; display:block; margin-bottom:1em; /* Latter is to act like a paragraph*/}
* soCalled
* socecStatus
* sound
* source
* sourceDesc
* sp
* space
* span
* spanGrp
* speaker
* specDesc
* specGrp
* specGrpRef
* specList
* sponsor
* stage
* stamp
* state
* stdVals
* street
* stress
* string
* stringVal
* subc
* subst
* summary
* superEntry
* supplied
* support
* supportDesc
* surface
* surname
* surplus
* surrogates
* syll
* symbol

==t==

* TEI
* table
* tag
* tagUsage
* tagsDecl
* taxonomy
* tech
* teiCorpus
* teiHeader
term {display:inline;}
* terrain
* text
* textClass
* textDesc
* textLang
* then
* time
* timeline
* title
* titlePage
* titlePart
* titleStmt
* tns
* trailer
* trait
* tree
* triangle
* typeDesc
* typeNote

==u==

* u
unclear {display:inline;}
* unicodeName
* usg

==v==

* vAlt
* vColl
* vDefault
* vLabel
* vMerge
* vNot
* vRange
* val
* valDesc
* valItem
* valList
* value
* variantEncoding
* view
* vocal

==w==

* w
* watermark
* when
* width
* wit
* witDetail
* witEnd
* witStart
* witness
* writing

==x==

* xr

==y==

(none)

==z==
z

* zone

[[Category:CSS]]