GuidelinesFormattingSuggestions - Revision history

Piotr Banski: + Category:Scratchpad

2007-10-31T17:13:27Z

+ Category:Scratchpad

Piotr Banski: + category

2007-09-25T12:08:31Z

+ category

James: /* Website Issues */

2007-09-10T08:07:45Z

‎Website Issues

James: /* Changes in Styles */

2007-09-10T08:06:59Z

‎Changes in Styles

James: /* Appendix B */

2007-09-10T08:06:35Z

‎Appendix B

James: /* Changes in Styles */

2007-09-08T09:37:12Z

‎Changes in Styles

James: /* Changes in Styles */

2007-09-08T09:35:57Z

‎Changes in Styles

James: /* Code Examples Styling */

2007-09-07T15:51:22Z

‎Code Examples Styling

James: /* Appendix B */

2007-09-07T10:01:59Z

‎Appendix B

James: /* Changes in Source */

2007-09-06T13:48:50Z

‎Changes in Source

← Older revision		Revision as of 17:13, 31 October 2007
Line 1:		Line 1:
	[[Category: TEI:P5]]		[[Category: TEI:P5]]
		+	[[Category:Scratchpad]]

	This is just a page to collect suggestions for changes to the formatting of the TEI Guidelines.		This is just a page to collect suggestions for changes to the formatting of the TEI Guidelines.

← Older revision		Revision as of 12:08, 25 September 2007
Line 1:		Line 1:
		+	[[Category: TEI:P5]]
		+
	This is just a page to collect suggestions for changes to the formatting of the TEI Guidelines.		This is just a page to collect suggestions for changes to the formatting of the TEI Guidelines.

@@ Line 62: / Line 62: @@
 ===Website Issues===
-# What is the purpose of  "Skip links" (at to of the menu to the left)?   (Website Issue?)
+# DONE <del>What is the purpose of  "Skip links" (at to of the menu to the left)?   (Website Issue?)</del>
 == Suggestions for PDF Version of TEI Guidelines ==
 # No suggestions specifically received so far, except some which carry over from HTML formatting (i.e. that element references should show possible children, etc.)

@@ Line 30: / Line 30: @@
 # DONE <del>The layout of the the entry for each element, macro or classes are different from the rest of the guidelines. Should it be more of the same? For instance is the menu to the left not available. On the other hand I think there should be a distinction between these two parts.</del>
 # DONE <del>Have a "print view" (In addition to the PDF, a most-formatting-stripped view without layout structure) (though only accessible through printing or print-preview)</del>
-# Show possible children of elements in the reference chapter
+# DONE <del>Show possible children of elements in the reference chapter</del>
 ===Changes in Source===

@@ Line 21: / Line 21: @@
 # DONE <del>The element description in the Element appendix is not part of the table showing the other information about the element. I think this might cause people to miss it. I'd recommend adding it as a first row: <nowiki><td>Description:</td><td><!-- actual description --></td></nowiki><br/>''I'm not sure what is the issue here''</del>
 # (JC:) Maybe a 'prev element'  'toc' 'next element' in the element reference pages?
-# Alphabetised grouping of elements in appB similar to: http://www.oucs.ox.ac.uk/atoz/ but show-all should have option of alphabetised grouping or by-module grouping.
+# DONE <del>Alphabetised grouping of elements in appB similar to: http://www.oucs.ox.ac.uk/atoz/ but show-all should have option of alphabetised grouping or by-module grouping.</del>
 ===Changes in Styles===

@@ Line 26: / Line 26: @@
 # Better styling of XML examples which are given as CDATA since they aren't TEI elements
-# DONE <del>It would be good if attributes could be not only indented as they are now, visualised better or rendered differently from the main text when inserted in the explanation e.g. <nowiki><specDesc key="head" atts="type"/></nowiki><br/>''If I understand this correctly then I agree. What about italicizing them? There doesn't seem to be rhyme or reason for when attributes appear in the explanation and when they do not.''</del
+# DONE <del>It would be good if attributes could be not only indented as they are now, visualised better or rendered differently from the main text when inserted in the explanation e.g. <nowiki><specDesc key="head" atts="type"/></nowiki><br/>''If I understand this correctly then I agree. What about italicizing them? There doesn't seem to be rhyme or reason for when attributes appear in the explanation and when they do not.''</del>
 # DONE <del>First line highlighted when moused over<br/>''I don't understand. Is this a comment or a request? "First line" of what?'' (In some of the rendering the first line of text used to be rendered with an underline appearing when moused-over.  I believe this was an accidental CSS error and has been solved, but I've left it here to double-check later.)</del>
 # DONE <del>The layout of the the entry for each element, macro or classes are different from the rest of the guidelines. Should it be more of the same? For instance is the menu to the left not available. On the other hand I think there should be a distinction between these two parts.</del>

@@ Line 16: / Line 16: @@
 ===Code Examples Styling===
 # DONE <del>Better styling of all Relax NG examples.<br/>''Is this being taken care of with the RNG/RNC switch?'' (only partly... Yes that give better styling, but we want (better) syntax highlighting of both of them.  Also links in the RNG for model.foo etc.) </del>
-# Tidy up the display of rng fragments and make the display (and print!) of these passages optional (i.e. When printing, they seem to run occasionally over the edge of the page. Thinking of it, the same also happens to the examples here and there.) (Answer: "both the schema fragments and examples are pretty-printing. and the algorithm obviously needs more tweaking.")   (Appears to be browser dependent, needs more thought).
+# DONE <del>Tidy up the display of rng fragments and make the display (and print!) of these passages optional (i.e. When printing, they seem to run occasionally over the edge of the page. Thinking of it, the same also happens to the examples here and there.) (Answer: "both the schema fragments and examples are pretty-printing. and the algorithm obviously needs more tweaking.")   (Appears to be browser dependent, needs more thought).</del>
 ===Appendix B===

@@ Line 39: / Line 39: @@
 # Space is output before <nowiki><gi>ptr</gi> e.g. <ptr target="#SG17"/></nowiki><br/>''That is an extra space in the code (between > and E), not a problem with the styles.''
 # The Appendix E Index: There are an extra line between each entry with an underline which looks odd. And the links does not work here. And I do not quite get by which criteria these index words are selected. And is a one column list the best way to present this? Should there be a paragraph at the top to say what this is?<br/>''I agree completely. The Index needs a good hard look. Those little lines are weird.''
-# Sometimes chapter names not output as in note on http://tei.oucs.ox.ac.uk/Query/tag.xq?name=att.declaring<br/>''I don't know if this is a problem with the styles or with the source''
+# DONE <del> Sometimes chapter names not output as in note on http://tei.oucs.ox.ac.uk/Query/tag.xq?name=att.declaring<br/>''I don't know if this is a problem with the styles or with the source''</del>
 ===DONE===