Re: [PGCanada] James McIntyre
Ah.... the cheese-poet. He's been the subject of a PGDP discussion thread. One of his books was cleared in August 2003 and is listed in-progress. ----- Original Message ----- From: Andrew Sly <sly@victoria.tc.ca> Date: Wednesday, April 6, 2005 11:18 pm Subject: [PGCanada] James McIntyre
I've run into someone whose poetry I would love to include in the PG Canada collection. James McIntyre, who is apparantly "widely regarded as the worst poet in all of Canadian literature." And his topic of choice was cheese.
Ok, good. The prospects for Canadian dairy-related poetry are hopeful then. :) (That sounds a conversation topic for some CBC radio program.) Andrew On Wed, 6 Apr 2005, Wallace J.McLean wrote:
Ah.... the cheese-poet.
He's been the subject of a PGDP discussion thread. One of his books was cleared in August 2003 and is listed in-progress.
----- Original Message ----- From: Andrew Sly <sly@victoria.tc.ca> Date: Wednesday, April 6, 2005 11:18 pm Subject: [PGCanada] James McIntyre
I've run into someone whose poetry I would love to include in the PG Canada collection. James McIntyre, who is apparantly "widely regarded as the worst poet in all of Canadian literature." And his topic of choice was cheese.
_______________________________________________ Project Gutenberg of Canada Website: http://www.projectgutenberg.ca/ List: pgcanada@lists.pglaf.org Archives: http://lists.pglaf.org/private.cgi/pgcanada/
On Apr 6, 2005 11:19 PM, Andrew Sly <sly@victoria.tc.ca> wrote:
Ok, good. The prospects for Canadian dairy-related poetry are hopeful then. :)
In my dreamier dreams of how the web site is going to work, there will be a prominent place for highlighting the works of Canada's illustrious cheese poets. :) As an update, my work on the site is coming along. I've got some simple wire-frames posted on the wiki: http://www.jenzed.com/pgcawiki/pmwiki.php?n=Main.Wireframes. I'd appreciate people's comments and ideas about how they'd like the site to look / work / etc. Please feel free to post thoughts either here or on the wiki. Currently, I'm experimenting with Drupal (http://www.drupal.org) as our front-end and content-management system, but I've yet to arrive at the stage where I can validate that it will meet our needs. I expect that I'll have a prototype up within two or three weeks. jen.
I must admit that I am partial to the idea of a simple interface that anyone can come to and get the text he wants. I'm not particularly attached to the idea of presenting a text (like the German Projekt Gutenberg-DE) in one part of the screen and surrounding it with other information. While we are dreaming, a dream of mine is to have a simple, basic, stable interface to the collection which can be translated into multiple languages. (Anything that changes too often would likely pose a problem in requiring updates to different language versions.) Andrew On Thu, 7 Apr 2005, Jen Zed wrote:
As an update, my work on the site is coming along. I've got some simple wire-frames posted on the wiki: http://www.jenzed.com/pgcawiki/pmwiki.php?n=Main.Wireframes. I'd appreciate people's comments and ideas about how they'd like the site to look / work / etc. Please feel free to post thoughts either here or on the wiki.
Currently, I'm experimenting with Drupal (http://www.drupal.org) as our front-end and content-management system, but I've yet to arrive at the stage where I can validate that it will meet our needs. I expect that I'll have a prototype up within two or three weeks.
hmmmm...yeah, I should probably think of the site architecture as "core" (book search / book display) and "extended" (accounts, favourites, tagging, etc). The "extended" interface could be enabled or disabled by the webmaster or the user (or based on the language selected on the portal page) ... more on the wiki: http://www.jenzed.com/pgcawiki/pmwiki.php?n=Main.PortalPlan Good feedback, Andrew - thanks for preventing me from riding madly off in all directions. :) jen. On Apr 7, 2005 9:37 AM, Andrew Sly <sly@victoria.tc.ca> wrote:
I must admit that I am partial to the idea of a simple interface that anyone can come to and get the text he wants. I'm not particularly attached to the idea of presenting a text (like the German Projekt Gutenberg-DE) in one part of the screen and surrounding it with other information.
While we are dreaming, a dream of mine is to have a simple, basic, stable interface to the collection which can be translated into multiple languages. (Anything that changes too often would likely pose a problem in requiring updates to different language versions.)
Andrew
On Thu, 7 Apr 2005, Jen Zed wrote:
As an update, my work on the site is coming along. I've got some simple wire-frames posted on the wiki: http://www.jenzed.com/pgcawiki/pmwiki.php?n=Main.Wireframes. I'd appreciate people's comments and ideas about how they'd like the site to look / work / etc. Please feel free to post thoughts either here or on the wiki.
Currently, I'm experimenting with Drupal (http://www.drupal.org) as our front-end and content-management system, but I've yet to arrive at the stage where I can validate that it will meet our needs. I expect that I'll have a prototype up within two or three weeks.
I've thought about this a little more. And yes, favourites, tagging, and "community" features are good _if people want them_. But on the other hand, I have many times taken a look at a potentially interesting web site, only to see that I have to register or create an account to access any content, and then I leave without looking any further. So i would suggest that free un-encumbered access to the texts in the collection is needed. Andrew On Fri, 8 Apr 2005, Jen Zed wrote:
hmmmm...yeah, I should probably think of the site architecture as "core" (book search / book display) and "extended" (accounts, favourites, tagging, etc). The "extended" interface could be enabled or disabled by the webmaster or the user (or based on the language selected on the portal page) ... more on the wiki: http://www.jenzed.com/pgcawiki/pmwiki.php?n=Main.PortalPlan
Good feedback, Andrew - thanks for preventing me from riding madly off in all directions. :)
Oh, it was *never* my intention to make registration mandatory. Absolutely not. No way. Registration will only be required if people want to use user-based features, like favourites, bookmarks, tagging, discussions, etc. jen. On Apr 8, 2005 12:12 PM, Andrew Sly <sly@victoria.tc.ca> wrote:
I've thought about this a little more. And yes, favourites, tagging, and "community" features are good _if people want them_.
But on the other hand, I have many times taken a look at a potentially interesting web site, only to see that I have to register or create an account to access any content, and then I leave without looking any further.
So i would suggest that free un-encumbered access to the texts in the collection is needed.
Andrew
On Fri, 8 Apr 2005, Jen Zed wrote:
hmmmm...yeah, I should probably think of the site architecture as "core" (book search / book display) and "extended" (accounts, favourites, tagging, etc). The "extended" interface could be enabled or disabled by the webmaster or the user (or based on the language selected on the portal page) ... more on the wiki: http://www.jenzed.com/pgcawiki/pmwiki.php?n=Main.PortalPlan
Good feedback, Andrew - thanks for preventing me from riding madly off in all directions. :)
_______________________________________________ Project Gutenberg of Canada Website: http://www.projectgutenberg.ca/ List: pgcanada@lists.pglaf.org Archives: http://lists.pglaf.org/private.cgi/pgcanada/
Comments regarding this (from the wiki): * By fostering a community, the division between content production and content acquisition could be reduced: "Report a typo" on the book display page would encourage a user, perhaps, to think about contributing on a larger scale (for example, by proofing a page). Jim Tinsely, who has dealt with making corrections to PG texts for years, and at the present deals with most of the emails sent to the PG "errata" list, has reported that "about half" of the submitted "corrections" are actually right in the etext. That is, the e-text itself correctly represents the original, and the suggested correction is in error. There are apparently some spots in Mark Twain's writing which were intentionally misspelled by the author for the effect in the story, and which are regularly reported as "errors". Also, sometimes people will try to "fix" older spellings of words such as Tokio--Tokyo; shew--show; fyle--file; etc. It takes a very patient volunteer to work through these suggested corrections, go about fixing those that are obvious, send messages back saying "thanks for your help, but..." for those mentioned above, and do further investigation/guessing for those in a grey area. Andrew
Can I suggest in your new site, and possibly in the pdg site, that you consider a prominent discussion of this with examples. However, that does not excuse some obvious typos that I have found in the books downloaded from blackmask and manybooks.
-----Original Message----- From: pgcanada-bounces@lists.pglaf.org [mailto:pgcanada-bounces@lists.pglaf.org] On Behalf Of Andrew Sly Sent: April 9, 2005 4:55 AM To: Project Gutenberg of Canada Subject: [PGCanada] Fixing typos
Comments regarding this (from the wiki):
* By fostering a community, the division between content production and content acquisition could be reduced: "Report a typo" on the book display page would encourage a user, perhaps, to think about contributing on a larger scale (for example, by proofing a page).
Jim Tinsely, who has dealt with making corrections to PG texts for years, and at the present deals with most of the emails sent to the PG "errata" list, has reported that "about half" of the submitted "corrections" are actually right in the etext. That is, the e-text itself correctly represents the original, and the suggested correction is in error.
There are apparently some spots in Mark Twain's writing which were intentionally misspelled by the author for the effect in the story, and which are regularly reported as "errors".
Also, sometimes people will try to "fix" older spellings of words such as Tokio--Tokyo; shew--show; fyle--file; etc.
It takes a very patient volunteer to work through these suggested corrections, go about fixing those that are obvious, send messages back saying "thanks for your help, but..." for those mentioned above, and do further investigation/guessing for those in a grey area.
Andrew
_______________________________________________ Project Gutenberg of Canada Website: http://www.projectgutenberg.ca/ List: pgcanada@lists.pglaf.org Archives: http://lists.pglaf.org/private.cgi/pgcanada/
Sure, auditing corrections is a big, thankless grunt-work job (sounds a little like DP). :) I don't think that should make us wary of taking typo submissions, though; the submissions can go into a queue and get dealt with as we have time. Also, I bet we could reduce the number of typo submissions if we could give users easy access to the the original scans. For example, maybe the "Report a typo" button could bring up the OCR of the original page. (This might be possible with hooks into James' UniBook - not sure. We'll see.) Also, on the same page, we should include an explanation of the (PG) proofing standards regarding typos - fix those that are obvious printing errors but preserve original spellings. I'll add this discussion to the plans for this function (after I write a plan for this function). :) jen. On Apr 9, 2005 1:55 AM, Andrew Sly <sly@victoria.tc.ca> wrote:
Comments regarding this (from the wiki):
* By fostering a community, the division between content production and content acquisition could be reduced: "Report a typo" on the book display page would encourage a user, perhaps, to think about contributing on a larger scale (for example, by proofing a page).
Jim Tinsely, who has dealt with making corrections to PG texts for years, and at the present deals with most of the emails sent to the PG "errata" list, has reported that "about half" of the submitted "corrections" are actually right in the etext. That is, the e-text itself correctly represents the original, and the suggested correction is in error.
There are apparently some spots in Mark Twain's writing which were intentionally misspelled by the author for the effect in the story, and which are regularly reported as "errors".
Also, sometimes people will try to "fix" older spellings of words such as Tokio--Tokyo; shew--show; fyle--file; etc.
It takes a very patient volunteer to work through these suggested corrections, go about fixing those that are obvious, send messages back saying "thanks for your help, but..." for those mentioned above, and do further investigation/guessing for those in a grey area.
Andrew
_______________________________________________ Project Gutenberg of Canada Website: http://www.projectgutenberg.ca/ List: pgcanada@lists.pglaf.org Archives: http://lists.pglaf.org/private.cgi/pgcanada/
Comments regarding this (from the wiki):
* By fostering a community, the division between content production and content acquisition could be reduced: "Report a typo" on the book display page would encourage a user, perhaps, to think about contributing on a larger scale (for example, by proofing a page).
Jim Tinsely, who has dealt with making corrections to PG texts for years, and at the present deals with most of the emails sent to the PG "errata" list, has reported that "about half" of the submitted "corrections" are actually right in the etext. That is, the e-text itself correctly represents the original, and the suggested correction is in error.
There are apparently some spots in Mark Twain's writing which were intentionally misspelled by the author for the effect in the story, and which are regularly reported as "errors".
Also, sometimes people will try to "fix" older spellings of words such as Tokio--Tokyo; shew--show; fyle--file; etc.
It takes a very patient volunteer to work through these suggested corrections, go about fixing those that are obvious, send messages back saying "thanks for your help, but..." for those mentioned above, and do further investigation/guessing for those in a grey area.
This shows the need and the benefit of having the original page scans available to readers so those who submit errata can first check with the original. Jon
participants (5)
-
Andrew Sly -
Jen Zed -
Jon Noring -
Paul M. Jacobson -
Wallace J.McLean