- gutvol-d - lists.pglaf.org

Re: unluckily for us (gutvol-d Digest, Vol 13, Issue 24)
by Lee Passey 25 Aug '05

25 Aug '05

Bowerbird(a)aol.com wrote: > lee said: > > Unluckily for us, Bowerbird has not yet > > released his algorithm for determining whether > > a block of unstructured text is a paragraph. > > oh gee, i'm sorry. i thought i had. > > in z.m.l., anything surrounded by two or more blank lines > is a paragraph. In z.m.l., anything surrounded by two or more blank lines is structured text. When you can recognize a paragraph, and distinquish it from a title or a block quotation inside of a paragraph, no matter how many blank lines surround them, then I'll be impressed.

1 0

1950 periodicals renewals
by Greg Weeks 25 Aug '05

25 Aug '05

When looking for the periodicals renewals for 1950 last night I didn't find any. 1947 had about 900 renewals and 1951 had about 1000, but 1948, 1949 and 1950 didn't even have a renewals section in the book. This is "The Catalog of Copyright Entries" in the Carnegie Library. Does anyone know what's going on with these? I've got some journal entries I'm trying to put a rule 6 clearance together for and I neede information on 1950 through 1955. -- Greg Weeks http://durendal.org:8080/greg/

2 3

Re: User style sheets in Firefox (gutvol-d Digest, Vol 13, Issue 27)
by Lee Passey 25 Aug '05

25 Aug '05

Robert Cicconetti <grythumn(a)gmail.com> wrote: >On 8/24/05, Lee Passey <lee(a)novomail.net> wrote: > > >>Unfortunately, I haven't been able to figure out how to tell Firefox how >>to use a user specified css file (I've got version 1.0.4). If anyone can >>enlighten me on this score, I would be most grateful. Mr. Noring tells >>me that I can do it with Opera, but I've yet to try it. >> >> > >Put it in userContent.css? > >http://www.mozilla.org/support/firefox/edit#content > >R C > > I _thought_ that was what I had done, but at your urging I did some more experimentation. I finally discovered that on this particular box (Windows XP, which I ordinarily wouldn't use, but sometimes you have to compromise) the userContent.css file had to be in C:\Documents and Settings\lpassey\Application Data\Mozilla\Firefox\Profiles\0wlij0cb.default\chrome -- not the most intuitive location. Once I had found the right location it still didn't work until I had restarted Firefox, so apparently the .css file is loaded on startup, and not consulted thereafter -- great if you want to override HTML defaults, but not so good if you want to switch style sheets when looking at a particular document. And I haven't tested it yet but my guess is that this means it will _not_ override some of the screwy choices that some document authors choose to use. That is, if an HTML file links to "screwy.css" those style will be applied _after_ my preferences, not before. And the userContent.css styles are only applied to HTML documents, not to XML documents. Ah well, I guess our reach should always exceed our grasp, that's how progress is made. Thanks for your help.

1 0

Re: gutvol-d Digest, Vol 13, Issue 27
by Wallace J.McLean 25 Aug '05

25 Aug '05

> The other three collections are editions of works > that were public domain at the time of the edition (eg `Best Known > Works: Defoe'). Other than any new material, arguably editorial changes, arguably (or certainly, in some jurisdictions) typographical arrangement, copyright would subsist in the compilation alone of a "Best Known Works" type dealie. Today's Topics: 1. Re: ANNOUNCEMENT: XML has hit the PG archives! (gutvol-d Digest, Vol 13, Issue 25) (Andrew Sly) 2. re: ANNOUNCEMENT: XML has hit the PG archives! (gutvol-d Digest, Vol 13, Issue 25) (Bowerbird(a)aol.com) 3. Re: on viewing the .pgtei file directly (gutvol-d Digest, Vol 13, Issue 23) (Robert Cicconetti) 4. TEI markup question (Andrew Sly) 5. newbie question: copyright editions of public domain works (Greg Smith) 6. Re: newbie question: copyright editions of public domain works (Andrew Sly) 7. Re: TEI markup question (Marcello Perathoner) 8. Re: TEI markup question (Joshua Hutchinson) 9. Re: ANNOUNCEMENT: XML has hit the PG archives! (gutvol-d Digest, Vol 13, Issue 19) (Brad Collins) 10. Re: TEI markup question (Jon Noring) _______________________________________________ gutvol-d mailing list gutvol-d(a)lists.pglaf.org http://lists.pglaf.org/listinfo.cgi/gutvol-d

1 0

TEI markup question
by Andrew Sly 25 Aug '05

25 Aug '05

Here is a question for those interested in TEI markup. (non-constuctive answers will be ignored) Has anyone here had experience in marking up a passage which contains a couple of quoted lines of verse that clearly occur within a paragraph? Here is a particular example (from anne11.txt): == Begin Excerpt == The cows swung placidly down the lane, and Anne followed them dreamily, repeating aloud the battle canto from MARMION--which had also been part of their English course the preceding winter and which Miss Stacy had made them learn off by heart--and exulting in its rushing lines and the clash of spears in its imagery. When she came to the lines The stubborn spearsmen still made good Their dark impenetrable wood, she stopped in ecstasy to shut her eyes that she might the better fancy herself one of that heroic ring. When she opened them again it was to behold Diana coming through the gate that led into the Barry field and looking so important that Anne instantly divined there was news to be told. But betray too eager curiosity she would not. == End Excerpt == The first reaction, which I have seen done before, is to use a then a <lg> then a . This is not an ideal solution, (as I am sure Lee would not hesitate to point out). >From a semantic point of view the section beginning "she stopped in ecstasy to shut her eyes" is not structually a complete paragraph. From a presentational point of view, you are likely to get an undesirable styling on that last element if someone decides to have initial indentation on all paragraphs in the document. According to the PGTEI dtd, is it valid to have a <lg> within a ? If not, I don't suppose we can lable a as Initial, Medial or Final as with the <l> element... Andrew

3 2

Re: [gutvol-d] TEI markup question
by Joshua Hutchinson 25 Aug '05

25 Aug '05

I don't remember if you can place a <lg> within a block, but ... You can put a rend="noindent" on the second paragraph to insure that it won't ever have an indention. As to what is the "right way to do it" ... I don't know. Josh ----- Original Message ----- From: "Andrew Sly" <sly(a)victoria.tc.ca> > > Here is a question for those interested in TEI markup. > (non-constuctive answers will be ignored) > > Has anyone here had experience in marking up a passage > which contains a couple of quoted lines of verse that > clearly occur within a paragraph? > > Here is a particular example (from anne11.txt): > > == Begin Excerpt == > The cows swung placidly down the lane, and Anne followed them > dreamily, repeating aloud the battle canto from MARMION--which > had also been part of their English course the preceding winter > and which Miss Stacy had made them learn off by heart--and > exulting in its rushing lines and the clash of spears in its > imagery. When she came to the lines > > The stubborn spearsmen still made good > Their dark impenetrable wood, > > she stopped in ecstasy to shut her eyes that she might the better > fancy herself one of that heroic ring. When she opened them > again it was to behold Diana coming through the gate that led > into the Barry field and looking so important that Anne instantly > divined there was news to be told. But betray too eager > curiosity she would not. > > == End Excerpt == > > The first reaction, which I have seen done before, is > to use a then a <lg> then a . This is not an ideal > solution, (as I am sure Lee would not hesitate to point out). > > From a semantic point of view the section beginning "she > stopped in ecstasy to shut her eyes" is not structually > a complete paragraph. From a presentational point of > view, you are likely to get an undesirable styling on > that last element if someone decides to have initial > indentation on all paragraphs in the document. > > > According to the PGTEI dtd, is it valid to have a <lg> > within a ? > > If not, I don't suppose we can lable a as Initial, Medial > or Final as with the <l> element... > > Andrew > _______________________________________________ > gutvol-d mailing list > gutvol-d(a)lists.pglaf.org > http://lists.pglaf.org/listinfo.cgi/gutvol-d

1 0

newbie question: copyright editions of public domain works
by Greg Smith 25 Aug '05

25 Aug '05

I inherited from my grandfather 25 years ago 4 collections from his library. He was a Baptist minister (read poor). The first collection is the 11th edition of the Encyclopedia Brittanica published 1910-1911. The other three collections are editions of works that were public domain at the time of the edition (eg `Best Known Works: Defoe'). The copyright dates range from the mid teens to the early forties. But what are these copyrights copyrighting? I can understand editor comments, translations, pictures, etc. But what if spelling/grammar was modernized? Or, portions cut or moved? Would these books (~120 volumes) be of any use? Apologies for my ignorance, Greg Smith

2 1

Re: [gutvol-d] on viewing the .pgtei file directly (gutvol-d Digest, Vol 13, Issue 23)
by Lee Passey 25 Aug '05

25 Aug '05

Bowerbird(a)aol.com wrote: > p.s. when i try to view 16523-x.xml directly in firefox, it says: > "this xml file does not appear to have any style information > associated with it. the document tree is shown below." and > then it shows me the document tree. how can i fix this problem? Download the file 16523-x.zip, and extract the files. Hopefully, the file "persistent.css" is still part of the package. Edit the .xml file with a simple text editor (beware Microsoft tools!) to add the line: <?xml-stylesheet href="persistent.css" type="text/css"?> immediately after the line: <?xml version="1.0" encoding="utf-8" ?> Save the file, and hopefully your editor won't have screwed up the utf-8 encoding. Now view the file from your local file system with Firefox. You should see just a bunch of run-on text, because the styles in 'persistent.css' are designed to be used with the XSL transformation to XHTML, and so none of them apply. But the document structure will disappear. You can experiment by adding new styles to 'persistent.css' (don't forget to save the file and reload your browser after adding rules). For example, add "p { display:block; text-indent: 3em }" and all of a sudden you will get distinct, indented paragraphs (and some non-paragraphs will also become distinct and indented). Add "teiHeader { display: none }" and all the Gutenberg legal cruft, together with the metadata which is typically only of interest to archivers, will disappear (it's still there, it's just not "in your face" anymore). Add "head { display:block; font-size: x-large; text-align: center }" and the headers will pop out. Add "hi { font-style: italic }" and highlighted text will become italicized. Use "hi { background: yellow }" instead and the highlighted text will look like you have run over it with a yellow highlighter. Or combine them both: "hi { font-style: italic; background: yellow }". The TEI markup used in this file is fairly simple, so you could probably get a pretty good looking file by using no more than a dozen or so CSS rules. Mr. Perathoner's TEI version of Alice in Wonderland (http://www.gutenberg.org/tei/marcello/0.3/examples/alice/) looks like it is much more complex, and would be funner to play with. I really like _Alice_ as an experimental text because it has quite a few typographical oddities which make it a good test case. Unfortunately, I haven't been able to figure out how to tell Firefox how to use a user specified css file (I've got version 1.0.4). If anyone can enlighten me on this score, I would be most grateful. Mr. Noring tells me that I can do it with Opera, but I've yet to try it.

2 1

re: [gutvol-d] ANNOUNCEMENT: XML has hit the PG archives! (gutvol-d Digest, Vol 13, Issue 25)
by Bowerbird＠aol.com 25 Aug '05

25 Aug '05

andrew said: > A brief explanation here of > the historical edition numbering of PG texts. > Every text was released initially in a version "10" > (Think of that as 1.0) And then subsequent "editions" > would be numbered 11, 12, etc. If you look hard enough > in the pre-10,000 files, you can find a couple of exceptions, > but that will cover most cases. Also note that the consensus > that emerged was that a small number of minor corrections > could be made without increasing the edition number. it is this last "consensus that emerged" that is most troublesome. as long as the filename stays unique for each different version, at least people can depend on the name to identify the version. when you substitute in a different file without changing its name, you've introduced unnecessary ambiguity into the situation, and thus made it extremely difficult for people to keep track of things. and when you fail to provide changelogs on the entire process, the difficulty-factor starts to climb into the "impossible" range... apologies for spoiling your fun... -bowerbird

1 0

Re: [gutvol-d] ANNOUNCEMENT: XML has hit the PG archives! (gutvol-d Digest, Vol 13, Issue 25)
by Lee Passey 25 Aug '05

25 Aug '05

Jeroen Hellingman wrote: [snip] > Some have argued (with valid reasons) that the entire idea of TEI > markup is broken, and have proposed systems > in which the mark-up is separated from the text (stream of > characters), in such a way that multiple, parallel systems of > mark-up can exist. Think of a separate (part of a) file, saying > characters 21 to 34 are italics, and so on. This may sound > odd, but it is the way the old Macintosh wordprocessor MacWrite worked. > > Jeroen. This is also the way HTML Tidy works, internally. As an HTML file is parsed (and fixed, if necessary) a DOM tree is built. But when a text node is encountered rather than malloc'ing a potentially small amount of memory and storing a pointer, the text is copied into a pre-allocated text buffer, and the start and end points of the fragment are saved in the node structure (the start and end points are actually saved in every node, so you can grab any node in the tree and know that it encompasses "this much" of the actual text.) When 'pretty-printing' the tree, text is grabbed from the buffer as needed. Having created this structure in memory, there is no reason at all it couldn't be saved out separately, with text nodes simply referring to an offset and length in a separate file which receives the entire text buffer, or a separate segment in the same file that contains the text. Likewise, if someone wanted, hypothetically mind you, to write a set of annotations and footnotes to classic literature found at Gutenberg, the same sort of strategy could be used; the annotations would be in a separate file and refer to text at a certain offset in the base file. You'd have to write a small application to merge the two files for presentations, but that sort of thing is trivial, perfectly suited for perl, awk or python. This type of division between markup and content is also perfectly suited to writing an application to display e-books in a low memory/low power device. The DOM tree could quickly be loaded into memory and remain resident, permitting fast navigation and styling, but the actual text could remain in static storage, only being accessed when needed. One of the downsides to this sort of system is that the base content _must_ remain 1. accessible and 2. inviolate. The Gutenberg edition of _The Adventures of Sherlock Holmes_ was first released in 1999 and has gone through 12 revisions, the most recent being in 2002. Version 10 is still available at gutenberg.org, but I can't find any earlier versions (this is not a criticism; PG is not an archive, after all). So if I were to write an annotation designed to be overlayed over the PG text I would want to have some assurances that the base text were always available, or I would want to be sure that the base text was always physically attached to the annotation file (to the extent that anything digital can be said to be physical). If I were to write a separate HTML markup file for TAOSH, I would want some assurance that the base text would not be altered in any way which would change the position of any character in the file, otherwise my markup would break. So there are definitely problems with this sort of application, but there are real benefits too, in some circumstances.

2 1