Bhagavata Purana ready to submit?
With all your help I managed to get my submission, *A Study Of The Bhagavata Purana Or Esoteric Hinduism* into pretty good shape. This is the latest: http://epubmaker.pglaf.org/cache/20120406103034/ The book is such a big and complex project that rather than just inflict the whole thing on some unfortunate white washer I'd like to get some comments from anyone willing to give it a quick look first. I expect that the way I handled family trees (and this book has many) will be controversial. If I get a consensus that the book doesn't suck (or if I don't get any feedback at all) I'll submit it. I would be especially interested in Bowerbird's opinion on this. No, really. Bowerbird gave me some good advice early on with this book, and while I did not take all of it it did lead me to try RST, which I am convinced saved me a ton of work. I like RST better than the ZML that he had originally suggested. My reason is that while ZML documents look like they aren't marked up at all, that is not necessarily an advantage. For instance, to make a heading in ZML it sounds like you have to insert some number of blank lines before the text. Counting blank lines is something I'd rather not deal with. RST lets you underline the heading with something and not worry about blank lines before or after. The RST converter deals with that. I also learned that you don't re-wrap your text before proofing. You let the converter deal with re-wrapping. Next time I'll know better. Thanks, James Simmons
A couple of suggestions: - move your transcriber's note to the very top of the file, rather than after the Preface. This will make it obvious that it's not part of the actual book, and give the reader an immediate heads-up. Perhaps add to the TN mention that the assorted ASCII tables/charts are accompanied by their graphic equivalent. - run Gutcheck/Jeebies/Gutspell on the generated ASCII or Latin1 file, to pick up on any unintentional mismatched/wrongspaced quotes, spellos, spaced punctuation, etc, etc. - when you upload, give the rst file a shorter name, e.g. purana.rst (short, all lower-case, and easy to type), rather than "AStudyOfTheBhagavataPurana.rst" (not, not, and not). Name the upload file purana.zip--the upload check may think "bp.zip" is a "misleading filename". Al -----Original Message----- From: gutvol-d-bounces@lists.pglaf.org [mailto:gutvol-d-bounces@lists.pglaf.org] On Behalf Of James Simmons Sent: Friday, April 06, 2012 11:16 AM To: Gutenberg Volunteers; bowerbird@aol.com Subject: [gutvol-d] Bhagavata Purana ready to submit? With all your help I managed to get my submission, A Study Of The Bhagavata Purana Or Esoteric Hinduism into pretty good shape. This is the latest: http://epubmaker.pglaf.org/cache/20120406103034/ The book is such a big and complex project that rather than just inflict the whole thing on some unfortunate white washer I'd like to get some comments from anyone willing to give it a quick look first. I expect that the way I handled family trees (and this book has many) will be controversial. If I get a consensus that the book doesn't suck (or if I don't get any feedback at all) I'll submit it. I would be especially interested in Bowerbird's opinion on this. No, really. Bowerbird gave me some good advice early on with this book, and while I did not take all of it it did lead me to try RST, which I am convinced saved me a ton of work. I like RST better than the ZML that he had originally suggested. My reason is that while ZML documents look like they aren't marked up at all, that is not necessarily an advantage. For instance, to make a heading in ZML it sounds like you have to insert some number of blank lines before the text. Counting blank lines is something I'd rather not deal with. RST lets you underline the heading with something and not worry about blank lines before or after. The RST converter deals with that. I also learned that you don't re-wrap your text before proofing. You let the converter deal with re-wrapping. Next time I'll know better. Thanks, James Simmons
On 04/06/2012 08:15 PM, James Simmons wrote:
With all your help I managed to get my submission, *A Study Of The Bhagavata Purana Or Esoteric Hinduism* into pretty good shape. This is the latest:
From a summary glance, two problems: 1. it lacks a ..footnotes:: section. This can easily be corrected by adding one. 2. it has ordered lists that do not begin with 1. This is a known limitation of RST and produces an invalid HTML file. The only current workaround is to rewrite the list as simple paragraphs with numbering. -- Marcello Perathoner webmaster@gutenberg.org
In your ascii-art family trees, it is disappointing to see the PG-hack underline "convention" being used to represent italic in those files formats which actually *do* support real italic. I would hope to see the PG-hack underline "convention" - if anywhere - only in the .txt file versions. If it is not possible to actually represent these in italic, then I would think it would be better to remove the PG-hack underline "convention" entirely in those files except the .txt file versions. In any case I think readers will find the PG-hack underline needlessly confusing and obscuring when trying to read the ascii-art family trees.
James, I agree with you entirely, but RST does not give me a way to do it. If you specify :: you get a set of <pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do. James Simmons On Sat, Apr 7, 2012 at 1:41 PM, James Adcock <jimad@msn.com> wrote:
** **
In your ascii-art family trees, it is disappointing to see the PG-hack underline “convention” being used to represent italic in those files formats which actually **do** support real italic. I would hope to see the PG-hack underline “convention” – if anywhere – only in the .txt file versions. If it is not possible to actually represent these in italic, then I would think it would be better to remove the PG-hack underline “convention” entirely in those files except the .txt file versions. In any case I think readers will find the PG-hack underline needlessly confusing and obscuring when trying to read the ascii-art family trees.****
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
On 04/07/2012 09:39 PM, James Simmons wrote:
James,
I agree with you entirely, but RST does not give me a way to do it. If you specify
::
you get a set of<pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do.
You could use the parsed-literal directive: http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-literal-... -- Marcello Perathoner webmaster@gutenberg.org
Marcello, That works all right, but the asterisks are not replaced with spaces when the <i> tags are put in so it throws the alignment of the ASCII art off. If I fix it it will no doubt screw up the plain text version. I'm going to keep fooling with it until I get something usable. Thanks, James Simmons On Sat, Apr 7, 2012 at 4:34 PM, Marcello Perathoner <marcello@perathoner.de>wrote:
On 04/07/2012 09:39 PM, James Simmons wrote:
James,
I agree with you entirely, but RST does not give me a way to do it. If you specify
::
you get a set of<pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do.
You could use the parsed-literal directive:
http://docutils.sourceforge.**net/docs/ref/rst/directives.** html#parsed-literal-block<http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-literal-block>
-- Marcello Perathoner webmaster@gutenberg.org
______________________________**_________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/**mailman/listinfo/gutvol-d<http://lists.pglaf.org/mailman/listinfo/gutvol-d>
OK, I think I have something just about ready to submit. I'm going to read through the MOBI on my Kindle before turning it over to the whitewashwers, but I'm still interested in any comment from you all. The latest stuff is here: http://epubmaker.pglaf.org/cache/20120408081709/ Thanks, James Simmons On Sat, Apr 7, 2012 at 8:51 PM, James Simmons <nicestep@gmail.com> wrote:
Marcello,
That works all right, but the asterisks are not replaced with spaces when the <i> tags are put in so it throws the alignment of the ASCII art off. If I fix it it will no doubt screw up the plain text version. I'm going to keep fooling with it until I get something usable.
Thanks,
James Simmons
On Sat, Apr 7, 2012 at 4:34 PM, Marcello Perathoner < marcello@perathoner.de> wrote:
On 04/07/2012 09:39 PM, James Simmons wrote:
James,
I agree with you entirely, but RST does not give me a way to do it. If you specify
::
you get a set of<pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do.
You could use the parsed-literal directive:
http://docutils.sourceforge.**net/docs/ref/rst/directives.** html#parsed-literal-block<http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-literal-block>
-- Marcello Perathoner webmaster@gutenberg.org
______________________________**_________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/**mailman/listinfo/gutvol-d<http://lists.pglaf.org/mailman/listinfo/gutvol-d>
but I'm still interested in any comment from you all.
Don't understand why you didn't do a UTF-8 txt version so that you can get the char set that you want? Not sure your intent, but the family trees certainly don't render "correctly" in ADE. ADE page numbers overlap text. Nit: some paragraphs are indented after a title heading, others are (correctly) flush left. Images fail to display in the non-image version when viewed in Kindle Previewer, with an apparent indication that Kindle Previewer considers the image files to be corrupt, whereas in the non-image version I would expect the image files to be silently redacted, rather implementing in some kind of "fail mode." Images fail to display correctly in the image version when viewed in Kindle Previewer in Kindle Fire mode, with aspect ratio not being maintained. Family trees don't display correctly in Kindle Previewer. Many tables are way too wide to be successfully viewed on ebook readers, which realistically can only support about three columns. MOBI version contain the error message: file:///htdocs/epubmaker/cache/21....bpurana.rst, line 5111); backlink 1O thousand sons, presumably meant to say: 10 thousand sons PDF version gives indication that the image files are corrupt rather than displaying the images.
James, My RST file is UTF-8 and has a first line showing it as such. I do have the char set I want, so I'm not sure what you're getting at. I haven't tried using Adobe Digital Editions, which I assume is what you mean by ADE. I know the ASCII family trees will look like crap in pretty much any e-book reader other than the plain text reader I wrote for the One Laptop Per Child project: http://activities.sugarlabs.org/en-US/sugar/addon/4035 The larger image files would look a lot better on a e-book reader if they were rotated but the PG guidelines don't allow that. Any problems with the non-image versions of the e-books must be caused by the epub generator. I'm just submitting an RST file with images in a subdirectory. I may replace the big table in the e-book version I will eventually make for Amazon and Nook with a page image. I'll check out that backlink message and the 1O thousand sons. For the PDF it looks like the images are present in the document when you click on the link to the PDF but when you download the PDF and open the downloaded file you don't get the images. Looks like a problem with the PDF generating code. It would be nice to have some kind of RST markup that says "put the following in the text version only". That would be a big help with the family trees. James Simmons On Sun, Apr 8, 2012 at 11:09 PM, James Adcock <jimad@msn.com> wrote:
*>*but I'm still interested in any comment from you all.****
** **
Don’t understand why you didn’t do a UTF-8 txt version so that you can get the char set that you want?****
** **
Not sure your intent, but the family trees certainly don’t render “correctly” in ADE.****
** **
ADE page numbers overlap text.****
** **
Nit: some paragraphs are indented after a title heading, others are (correctly) flush left.****
** **
Images fail to display in the non-image version when viewed in Kindle Previewer, with an apparent indication that Kindle Previewer considers the image files to be corrupt, whereas in the non-image version I would expect the image files to be silently redacted, rather implementing in some kind of “fail mode.”****
** **
Images fail to display correctly in the image version when viewed in Kindle Previewer in Kindle Fire mode, with aspect ratio not being maintained.****
** **
Family trees don’t display correctly in Kindle Previewer.****
** **
Many tables are way too wide to be successfully viewed on ebook readers, which realistically can only support about three columns.****
** **
MOBI version contain the error message:****
** **
file:///htdocs/epubmaker/cache/21....bpurana.rst, line 5111); backlink****
** **
1O thousand sons, presumably meant to say: 10 thousand sons****
** **
PDF version gives indication that the image files are corrupt rather than displaying the images.****
** **
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
James, I figured out the backlink problem. I use backslashes in my ASCII art family trees. I'm going to have to stop doing that. James Simmons On Mon, Apr 9, 2012 at 11:32 AM, James Simmons <nicestep@gmail.com> wrote:
James,
My RST file is UTF-8 and has a first line showing it as such. I do have the char set I want, so I'm not sure what you're getting at.
I haven't tried using Adobe Digital Editions, which I assume is what you mean by ADE. I know the ASCII family trees will look like crap in pretty much any e-book reader other than the plain text reader I wrote for the One Laptop Per Child project:
http://activities.sugarlabs.org/en-US/sugar/addon/4035
The larger image files would look a lot better on a e-book reader if they were rotated but the PG guidelines don't allow that.
Any problems with the non-image versions of the e-books must be caused by the epub generator. I'm just submitting an RST file with images in a subdirectory.
I may replace the big table in the e-book version I will eventually make for Amazon and Nook with a page image.
I'll check out that backlink message and the 1O thousand sons.
For the PDF it looks like the images are present in the document when you click on the link to the PDF but when you download the PDF and open the downloaded file you don't get the images. Looks like a problem with the PDF generating code.
It would be nice to have some kind of RST markup that says "put the following in the text version only". That would be a big help with the family trees.
James Simmons
On Sun, Apr 8, 2012 at 11:09 PM, James Adcock <jimad@msn.com> wrote:
*>*but I'm still interested in any comment from you all.****
** **
Don’t understand why you didn’t do a UTF-8 txt version so that you can get the char set that you want?****
** **
Not sure your intent, but the family trees certainly don’t render “correctly” in ADE.****
** **
ADE page numbers overlap text.****
** **
Nit: some paragraphs are indented after a title heading, others are (correctly) flush left.****
** **
Images fail to display in the non-image version when viewed in Kindle Previewer, with an apparent indication that Kindle Previewer considers the image files to be corrupt, whereas in the non-image version I would expect the image files to be silently redacted, rather implementing in some kind of “fail mode.”****
** **
Images fail to display correctly in the image version when viewed in Kindle Previewer in Kindle Fire mode, with aspect ratio not being maintained.****
** **
Family trees don’t display correctly in Kindle Previewer.****
** **
Many tables are way too wide to be successfully viewed on ebook readers, which realistically can only support about three columns.****
** **
MOBI version contain the error message:****
** **
file:///htdocs/epubmaker/cache/21....bpurana.rst, line 5111); backlink*** *
** **
1O thousand sons, presumably meant to say: 10 thousand sons****
** **
PDF version gives indication that the image files are corrupt rather than displaying the images.****
** **
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
You can use backslashes, but you have to escape them: '\\' -----Original Message----- From: gutvol-d-bounces@lists.pglaf.org [mailto:gutvol-d-bounces@lists.pglaf.org] On Behalf Of James Simmons Sent: Monday, April 09, 2012 9:36 AM To: Project Gutenberg Volunteer Discussion Subject: Re: [gutvol-d] Bhagavata Purana ready to submit? James, I figured out the backlink problem. I use backslashes in my ASCII art family trees. I'm going to have to stop doing that. James Simmons On Mon, Apr 9, 2012 at 11:32 AM, James Simmons <nicestep@gmail.com> wrote: James, My RST file is UTF-8 and has a first line showing it as such. I do have the char set I want, so I'm not sure what you're getting at. I haven't tried using Adobe Digital Editions, which I assume is what you mean by ADE. I know the ASCII family trees will look like crap in pretty much any e-book reader other than the plain text reader I wrote for the One Laptop Per Child project: http://activities.sugarlabs.org/en-US/sugar/addon/4035 The larger image files would look a lot better on a e-book reader if they were rotated but the PG guidelines don't allow that. Any problems with the non-image versions of the e-books must be caused by the epub generator. I'm just submitting an RST file with images in a subdirectory. I may replace the big table in the e-book version I will eventually make for Amazon and Nook with a page image. I'll check out that backlink message and the 1O thousand sons. For the PDF it looks like the images are present in the document when you click on the link to the PDF but when you download the PDF and open the downloaded file you don't get the images. Looks like a problem with the PDF generating code. It would be nice to have some kind of RST markup that says "put the following in the text version only". That would be a big help with the family trees. James Simmons On Sun, Apr 8, 2012 at 11:09 PM, James Adcock <jimad@msn.com> wrote:
but I'm still interested in any comment from you all.
Don't understand why you didn't do a UTF-8 txt version so that you can get the char set that you want? Not sure your intent, but the family trees certainly don't render "correctly" in ADE. ADE page numbers overlap text. Nit: some paragraphs are indented after a title heading, others are (correctly) flush left. Images fail to display in the non-image version when viewed in Kindle Previewer, with an apparent indication that Kindle Previewer considers the image files to be corrupt, whereas in the non-image version I would expect the image files to be silently redacted, rather implementing in some kind of "fail mode." Images fail to display correctly in the image version when viewed in Kindle Previewer in Kindle Fire mode, with aspect ratio not being maintained. Family trees don't display correctly in Kindle Previewer. Many tables are way too wide to be successfully viewed on ebook readers, which realistically can only support about three columns. MOBI version contain the error message: file:///htdocs/epubmaker/cache/21....bpurana.rst, line 5111); backlink 1O thousand sons, presumably meant to say: 10 thousand sons PDF version gives indication that the image files are corrupt rather than displaying the images. _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
My RST file is UTF-8 and has a first line showing it as such. I do have the char set I want, so I'm not sure what you're getting at.
Never mind, I see it now - 1.0.txt is your UTF-8 encoding.
I haven't tried using Adobe Digital Editions, which I assume is what you mean by ADE. I know the ASCII family trees will look like crap in pretty much any e-book reader other than the plain text reader I wrote for the One Laptop Per Child project
Any problems with the non-image versions of the e-books must be caused by
Okay, but why submit something that people can't actually read? the epub generator. I'm just submitting an RST file with images in a subdirectory. Okay, but there are certainly ways of doing what you want to do successfully. Why choose a method which is not successful, and then blame the tool?
For the PDF it looks like the images are present in the document when you click on the link to the PDF but when you download the PDF and open the downloaded file you don't get the images. Looks like a problem with the PDF generating code.
Again, you chose the tools you used to make your e-book.
James, This book has LOTS of family tree tables and unfortunately the text of the book refers to them. They are really needed in the Plain Text version of the book. They are unnecessary in every other format, but RST does not give me a way to eliminate them in the other formats. I believe in the value of the Plain Text format, so I want to do my best with it. I chose RST because in my earlier donations I found that I would have a lot of corrections to make after I generated the HTML version, no matter how careful I was. I also like that the RST generated books have a consistent look, automatically give you a table of contents and simplify putting in footnotes. RST also does a much better job of creating EPUBs than just submitting a web page would. It breaks up the EPUB files by chapter, for one thing. The PDF problem with the images is a bug. If I didn't use RST I would not get a PDF at all, so I can live with the PDF being imperfect. I don't consider PDF to be an e-book format. On the other hand, if you could get it sized to work for submission to CreateSpace (6" x 9" trade paperback with the required margins, TOC with real page numbers) then you'd have something! If RST had a few new features it would be perfect for the Bhagavata Purana: 1). A feature that says "only put this block in the Plain Text versions". That way you could use ASCII art as a substitute for diagrams that would be images in all other formats. 2). A way to rotate images for EPUBs. The long side of the image would be vertical, for better reading on e-book readers. As an alternative, allow images already rotated that way in HTML. 3). A way to represent a table as an image but use the HTML table for the web page version would be helpful too. I share your frustration that we can only submit Plain Text and HTML and have to live with automatically generated EPUBs from HTML. I see RST as a way to improve the situation, eventually. James Simmons On Mon, Apr 9, 2012 at 3:21 PM, James Adcock <jimad@msn.com> wrote:
*>*My RST file is UTF-8 and has a first line showing it as such. I do have the char set I want, so I'm not sure what you're getting at.
****
Never mind, I see it now – 1.0.txt is your UTF-8 encoding.****
I haven't tried using Adobe Digital Editions, which I assume is what you mean by ADE. I know the ASCII family trees will look like crap in pretty much any e-book reader other than the plain text reader I wrote for the One Laptop Per Child project****
Okay, but why submit something that people can’t actually read?****
Any problems with the non-image versions of the e-books must be caused by the epub generator. I'm just submitting an RST file with images in a subdirectory.
****
Okay, but there are certainly ways of doing what you want to do successfully. Why choose a method which is not successful, and then blame the tool?****
For the PDF it looks like the images are present in the document when you click on the link to the PDF but when you download the PDF and open the downloaded file you don't get the images. Looks like a problem with the PDF generating code.
****
Again, you chose the tools you used to make your e-book.****
** **
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
When I ran Gutcheck on 1-8.txt, it flagged 10 items that I think need attention--spaced quotes, wrongspaced quotes, extra periods, spaced punctuation, etc., etc. Jeebies flagged 8 he/be errors. Al -----Original Message----- From: gutvol-d-bounces@lists.pglaf.org [mailto:gutvol-d-bounces@lists.pglaf.org] On Behalf Of James Simmons Sent: Sunday, April 08, 2012 5:17 PM To: Project Gutenberg Volunteer Discussion Subject: Re: [gutvol-d] Bhagavata Purana ready to submit? OK, I think I have something just about ready to submit. I'm going to read through the MOBI on my Kindle before turning it over to the whitewashwers, but I'm still interested in any comment from you all. The latest stuff is here: http://epubmaker.pglaf.org/cache/20120408081709/ Thanks, James Simmons On Sat, Apr 7, 2012 at 8:51 PM, James Simmons <nicestep@gmail.com> wrote: Marcello, That works all right, but the asterisks are not replaced with spaces when the <i> tags are put in so it throws the alignment of the ASCII art off. If I fix it it will no doubt screw up the plain text version. I'm going to keep fooling with it until I get something usable. Thanks, James Simmons On Sat, Apr 7, 2012 at 4:34 PM, Marcello Perathoner <marcello@perathoner.de> wrote: On 04/07/2012 09:39 PM, James Simmons wrote: James, I agree with you entirely, but RST does not give me a way to do it. If you specify :: you get a set of<pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do. You could use the parsed-literal directive: http://docutils.sourceforge. <http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-l iteral-block> net/docs/ref/rst/directives.html#parsed-literal-block -- Marcello Perathoner webmaster@gutenberg.org _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/ <http://lists.pglaf.org/mailman/listinfo/gutvol-d> mailman/listinfo/gutvol-d
Al, I should probably run gutcheck and jeebies on the generated text file rather than the RST file. Some of the spaced punctuation is legitimate. My problem with this book is that there are so many odd names that finding genuine errors in the middle of the reported errors is a challenge. James Simmons On Sun, Apr 8, 2012 at 11:54 PM, Al Haines <ajhaines@shaw.ca> wrote:
** When I ran Gutcheck on 1-8.txt, it flagged 10 items that I think need attention--spaced quotes, wrongspaced quotes, extra periods, spaced punctuation, etc., etc. Jeebies flagged 8 he/be errors.
Al
-----Original Message----- *From:* gutvol-d-bounces@lists.pglaf.org [mailto: gutvol-d-bounces@lists.pglaf.org] *On Behalf Of *James Simmons *Sent:* Sunday, April 08, 2012 5:17 PM *To:* Project Gutenberg Volunteer Discussion *Subject:* Re: [gutvol-d] Bhagavata Purana ready to submit?
OK, I think I have something just about ready to submit. I'm going to read through the MOBI on my Kindle before turning it over to the whitewashwers, but I'm still interested in any comment from you all.
The latest stuff is here:
http://epubmaker.pglaf.org/cache/20120408081709/
Thanks,
James Simmons
On Sat, Apr 7, 2012 at 8:51 PM, James Simmons <nicestep@gmail.com> wrote:
Marcello,
That works all right, but the asterisks are not replaced with spaces when the <i> tags are put in so it throws the alignment of the ASCII art off. If I fix it it will no doubt screw up the plain text version. I'm going to keep fooling with it until I get something usable.
Thanks,
James Simmons
On Sat, Apr 7, 2012 at 4:34 PM, Marcello Perathoner < marcello@perathoner.de> wrote:
On 04/07/2012 09:39 PM, James Simmons wrote:
James,
I agree with you entirely, but RST does not give me a way to do it. If you specify
::
you get a set of<pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do.
You could use the parsed-literal directive:
http://docutils.sourceforge.**net/docs/ref/rst/directives.** html#parsed-literal-block<http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-literal-block>
-- Marcello Perathoner webmaster@gutenberg.org
______________________________**_________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/**mailman/listinfo/gutvol-d<http://lists.pglaf.org/mailman/listinfo/gutvol-d>
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
Gutcheck/Jeebies/Gutspell don't work well on UTF8 files. I ran the reports on the generated 1-8.txt Latin1 file. Agreed, the bulk of the reported items are legitimate, but 18 actual problems are more than sufficient to make it worthwhile. I also ran Gutspell on 1-8.txt, but didn't feel like browsing its 3000+-line report. As mentioned on the upload page (http://upload.pglaf.org/), Gutcheck is a required pre-upload check, and by extension, so are Jeebies and Gutspell. A word to the wise... -----Original Message----- From: gutvol-d-bounces@lists.pglaf.org [mailto:gutvol-d-bounces@lists.pglaf.org] On Behalf Of James Simmons Sent: Monday, April 09, 2012 9:11 AM To: Project Gutenberg Volunteer Discussion Subject: Re: [gutvol-d] Bhagavata Purana ready to submit? Al, I should probably run gutcheck and jeebies on the generated text file rather than the RST file. Some of the spaced punctuation is legitimate. My problem with this book is that there are so many odd names that finding genuine errors in the middle of the reported errors is a challenge. James Simmons On Sun, Apr 8, 2012 at 11:54 PM, Al Haines <ajhaines@shaw.ca> wrote: When I ran Gutcheck on 1-8.txt, it flagged 10 items that I think need attention--spaced quotes, wrongspaced quotes, extra periods, spaced punctuation, etc., etc. Jeebies flagged 8 he/be errors. Al -----Original Message----- From: gutvol-d-bounces@lists.pglaf.org [mailto:gutvol-d-bounces@lists.pglaf.org] On Behalf Of James Simmons Sent: Sunday, April 08, 2012 5:17 PM To: Project Gutenberg Volunteer Discussion Subject: Re: [gutvol-d] Bhagavata Purana ready to submit? OK, I think I have something just about ready to submit. I'm going to read through the MOBI on my Kindle before turning it over to the whitewashwers, but I'm still interested in any comment from you all. The latest stuff is here: http://epubmaker.pglaf.org/cache/20120408081709/ Thanks, James Simmons On Sat, Apr 7, 2012 at 8:51 PM, James Simmons <nicestep@gmail.com> wrote: Marcello, That works all right, but the asterisks are not replaced with spaces when the <i> tags are put in so it throws the alignment of the ASCII art off. If I fix it it will no doubt screw up the plain text version. I'm going to keep fooling with it until I get something usable. Thanks, James Simmons On Sat, Apr 7, 2012 at 4:34 PM, Marcello Perathoner <marcello@perathoner.de> wrote: On 04/07/2012 09:39 PM, James Simmons wrote: James, I agree with you entirely, but RST does not give me a way to do it. If you specify :: you get a set of<pre> tags and absolutely everything within them is passed through as is. I had to change '*' to '_' to get the underscores in there. The text actually says that wives names are in asterisks, so if I simply left the underscores out I'd remove information from the file. I did the best that RST allows me to do. You could use the parsed-literal directive: http://docutils.sourceforge. <http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-l iteral-block> net/docs/ref/rst/directives.html#parsed-literal-block -- Marcello Perathoner webmaster@gutenberg.org _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/ <http://lists.pglaf.org/mailman/listinfo/gutvol-d> mailman/listinfo/gutvol-d _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
participants (4)
-
Al Haines -
James Adcock -
James Simmons -
Marcello Perathoner