I have almost no notes on the page, but I do have a link to the current test.xml I'm using and the resulting html and text from the online conversion. If you're at all interested in on-going progress, you can see if here. http://home.alltel.net/hutch2000/test.html Josh
As I promised already some time ago, I've prepared a draft TEI Lite conventions document, and a zip file with a TEI encoded file, following that. The end result of the TEI to HTML transform can already be seen in PG: http://www.gutenberg.net/etext/10772 To get the guidelines in PDF format: http://www.bohol.ph/PG/TEI-PG-Guidelines-0.1.pdf in open office format: http://www.bohol.ph/PG/TEI-PG-Guidelines-0.1.sxw To get the sample file: http://www.bohol.ph/PG/IncaLand.zip I hope to be adding more examples soon, and update the guidelines, among others with what things are optional, and what will be required. I hope to keep the instructions within 30 pages. Jeroen Hellingman.
Jeroen Hellingman wrote:
As I promised already some time ago, I've prepared a draft TEI Lite conventions document,
1. The main point of incompatibility with my proposal is the lack of support for plain <div>. I support both, <div> and <divN>. I think you should also. 2. The rend attributes are ill-chosen and need reworking. rend is a global attribute and can be used on all TEI elements. It is counter-intuitive to make the effect dependent on the element. <figure rend="left"> floats the picture to the left <p rend="left"> makes a ragged-right paragraph better use <figure rend="float(left)"> <p rend="text-align(left)"> 3. The urls have to be changed. www.gutenberg.org/css/ is already taken for the site css and I don't want to mix those with the book css. www.gutenberg.org/xslt/ and www.gutenberg.org/dtd/ are off the main directory. I try to keep the number of subdirectories in the main directory to a minimum. Proposal: one directory off the main with a hierarchy to accomodate all xslt stuff by different people. www.gutenberg.org/tei/ www.gutenberg.org/tei/jeroen/ www.gutenberg.org/tei/jeroen/css/ www.gutenberg.org/tei/jeroen/dtd/ www.gutenberg.org/tei/jeroen/xslt/ www.gutenberg.org/tei/marcello/ www.gutenberg.org/tei/marcello/css www.gutenberg.org/tei/marcello/dtd www.gutenberg.org/tei/marcello/xslt etc. The prefix www.gutenberg.org/tei/jeroen/ should also be used for all your namespaces. Is this ok? -- Marcello Perathoner webmaster@gutenberg.org
Marcello Perathoner wrote:
1. The main point of incompatibility with my proposal is the lack of support for plain <div>. I support both, <div> and <divN>. I think you should also.
It means some extra programming from my side. I would like to see the various people working on this issue converge to a single standard.
2. The rend attributes are ill-chosen and need reworking.
rend is a global attribute and can be used on all TEI elements. It is counter-intuitive to make the effect dependent on the element.
<figure rend="left"> floats the picture to the left <p rend="left"> makes a ragged-right paragraph
better use
<figure rend="float(left)"> <p rend="text-align(left)">
I agree the rendition ladder approach is much better. The "simple" rend attributes are actually quick hacks. I've looked in your code, and the generic code for rend attributes you use is a much better way to deal with it. Quite some work needs to be done though before rendition ladders are fully supported.
3. The urls have to be changed.
www.gutenberg.org/css/ is already taken for the site css and I don't want to mix those with the book css.
www.gutenberg.org/xslt/ and www.gutenberg.org/dtd/ are off the main directory. I try to keep the number of subdirectories in the main directory to a minimum.
Proposal: one directory off the main with a hierarchy to accomodate all xslt stuff by different people.
www.gutenberg.org/tei/ www.gutenberg.org/tei/jeroen/ www.gutenberg.org/tei/jeroen/css/ www.gutenberg.org/tei/jeroen/dtd/ www.gutenberg.org/tei/jeroen/xslt/ www.gutenberg.org/tei/marcello/ www.gutenberg.org/tei/marcello/css www.gutenberg.org/tei/marcello/dtd www.gutenberg.org/tei/marcello/xslt etc.
The prefix www.gutenberg.org/tei/jeroen/ should also be used for all your namespaces.
That sounds like a good proposal, how do others think about it, especially if books in the books hierarchy start referencing to these things? Currently, they are rather self-contained things, with all required stuff in one place. Doing this will basically require us to keep things in the generic directories downwards compatible with texts posted before. Jeroen
Marcello Perathoner <marcello@perathoner.de> writes:
Jeroen Hellingman wrote:
2. The rend attributes are ill-chosen and need reworking.
rend is a global attribute and can be used on all TEI elements. It is counter-intuitive to make the effect dependent on the element.
<figure rend="left"> floats the picture to the left <p rend="left"> makes a ragged-right paragraph
better use
<figure rend="float(left)"> <p rend="text-align(left)">
Should `rend' then be a means of passing CSS to a processor? I see a lot of people using the `rend' attribute as a means of dumping in presentational instructions, when it should be used as a means of describing the original: ,----[ TEI Manual: Global Attributes ] | rend (rendition or presentation) indicates how the element in question | was rendered or presented in the source text. | Datatype: CDATA | Values: any string of characters; if the typographic rendition | of a text is to be systematically recorded, a | systematic set of values for the rend attribute should | be defined. | Default: #IMPLIED `---- I would suggest that PG define a set of enumerated values for `rend' which then can be mapped to CSS. That is more restrictive and requires changing the datatype. Any thoughts? b/ -- Brad Collins <brad@chenla.org>, Bangkok, Thailand
Brad Collins wrote:
<figure rend="float(left)"> <p rend="text-align(left)">
Should `rend' then be a means of passing CSS to a processor?
Not necessarily CSS. I used those values as example.
I see a lot of people using the `rend' attribute as a means of dumping in presentational instructions, when it should be used as a means of describing the original:
Of course, you should use rend judiciously, and only to preserve the rendition of the original when you feel it needs recording. If we are going to define a set of values we will most probably end up with something resembling CSS very much. -- Marcello Perathoner webmaster@gutenberg.org
participants (4)
-
Brad Collins -
Jeroen Hellingman -
Joshua Hutchinson -
Marcello Perathoner