Comprehensive CSS Stylesheet - Revision history

Brettz9: /* References used */ heading fix

2011-06-05T15:42:14Z

‎References used: heading fix

2011-06-05T15:41:41Z

reordering like items

2011-06-05T15:40:33Z

structuring page further

2011-06-05T15:35:35Z

+advantage

2011-06-05T15:34:02Z

more advantages of CSS

2010-07-14T08:27:41Z

2010-07-14T04:03:43Z

2010-07-12T09:24:05Z

‎a: +additions

2010-07-12T09:22:20Z

‎a: add, addName comment

2010-07-12T09:09:49Z

‎a: additional fixes

@@ Line 646: / Line 646: @@
 * zone
-===References used===
+==References used==
 * http://math.ut.ee/~kaarel/NLP/TEI/visualization/ (on rationales)
 [[Category:CSS]]

@@ Line 17: / Line 17: @@
 # 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==
@@ Line 28: / Line 32: @@
 ...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==

@@ Line 8: / Line 8: @@
 # 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:

@@ Line 3: / Line 3: @@
 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)
+# 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.

@@ Line 9: / Line 9: @@
 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)
+# 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)
+# 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.)
+# Unable to create form controls and some other HTML GUI components.
-# Assumes that the structure of the TEI essentially similar to the desired output. This precludes stand-off markup; switching between multiple overlapping hierarchical structures; and other document transformations.
+# 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

@@ Line 38: / Line 38: @@
 * 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
+ 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 */}

@@ Line 32: / Line 32: @@
   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
+ add[place="sup"] {vertical-align:super;} add[place="sub"] {vertical-align:sub;}
-* addName
+* 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;}