You know, maybe I could give you commit access to a subdirectory of the libprs500 SVN server and you could switch development of pielrf to that. That way you'd get Windows and OSX installers for free as part of the libprs500 umbrella of utilities.

- Is it possible to add some extra vertical space before each paragraph; I like some air between paragraphs?
- I can't get the bold functionality to work, and neither avoiding creating a TOC. pielrf logs that font weight 800 is used and that no TOC will be created, but neither of those are true...
- I've created an OSX application which wraps pielrf functionality in a GUI, for my personal use. It includes the pielrf stuff, but you have to install python >= 2.5 in /usr/local/bin yourself. Would it be OK for me to put it up for downloading?

You know, maybe I could give you commit access to a subdirectory of the libprs500 SVN server and you could switch development of pielrf to that. That way you'd get Windows and OSX installers for free as part of the libprs500 umbrella of utilities.

Thanks for the very kind offer Kovid! At this point, though, I'm going to keep it as a separate download. If I move toward needing additional features of libprs500 (like your extended image support), I'll consider this further.

- I've created an OSX application which wraps pielrf functionality in a GUI, for my personal use. It includes the pielrf stuff, but you have to install python >= 2.5 in /usr/local/bin yourself. Would it be OK for me to put it up for downloading?

Great! Go ahead and throw it up and see what people think. It'd be wonderful to make this easier for Mac users, since there's no BookDesigner on "our side" of the fence.

Quote:

I really like the look of the output for pielrf. A few questions:

- Is it possible to add some extra vertical space before each paragraph; I like some air between paragraphs?

Not at this point. I'm pretty sure it's offered as an option, but I never implemented it. I'll double-check and add it after I get the next revision out.

Quote:

- I can't get the bold functionality to work, and neither avoiding creating a TOC. pielrf logs that font weight 800 is used and that no TOC will be created, but neither of those are true...

Unfortunately, bold is not very bold. I loaded a set of mixed text onto the Reader, and there was very little discernable difference. If you do bold and increase the font size, that makes it more noticable.

On the "--without-toc" option, it's a little misleading as named. This suppresses the generation of the TOC Menu, which is item #5 in the Reader's Navigation menu. However, it STILL generates a TOC page. I do not (yet) offer an option to suppress the TOC page.

Originally, I mishandled TextBlocks, and this would cause the Reader to slow to a crawl when loading some books that had a TOC Menu. So I added "--without-toc" for these slow-loading books. I've since fixed the TextBlock issue, but I left the "--without-toc" in.

Note: New version attached using pielrf 2.1.2, and also adds pielrf installation procedure from within GUI (had forgot that before). Also, you have to run this installation procedure again since a new pielrf lib is used.

Lots and lots of changes, both new features, bug fixes, and under-the-hood cleanup.

NEW FEATURES

- UNIX style "preferences" file, ".pielrfrc" and a "--write-rc" function.
- <justified></justified> tags simply remove the indent on the first line of a paragraph in any paragraphs between these tags.
- <verse></verse> tags for proper indentation of poetry.
- "--verseparindent" a NEGATIVE number which pulls the first line of the verse further to toward the left margin. The Margin of subsequent lines in the same verse are shared with "--quoteoffset"
- Added "--html-quotes" and "--trust-html" as aliases to the "--use-rdquotes" switch. They make more sense.

BUG FIXES

- Fixed "<<" (double less-than). Pielrf now outputs the same number less-than signs it encounters! (I even tested it this time, so it's really fixed!)
- Formatting tags "<center>" and "<h1>,<h2>,etc." no longer create vertical whitespace when encountered... unless they are on paragraph -- this allows for more "fine grained" control of formatting.
- Bold, Italic, Subscript and Superscript can all be combined (well, not Subscript/Superscript).
- Multiple <blockquote> levels are now supported, to a maximum of 3 levels. Pielrf will not indent further than 3 <blockquote> levels -- if it encounters fruther <blockquotes>, those remain indented at level 3.
- Both "--html-quotes" (aka "--use-rdquotes") and "--preserve-spaces" now apply correctly.

Preferences (.pielrfrc) File

My original intent for providing full control over command line options came because I realized that people have a wide variety of tastes in the "look and feel" of their e-books. The problem is, if you don't like the default settings, that can add up to a lot of typing for every book you convert. The ".pielrfrc" file stores all formatting options so you don't have to re-type them every time, and command line options will still override the ".pielrfrc" options when you need to!

Note that non-formatting related command line options like "--title", "--author", "--headerstyle", etc. are not stored in the .pielrfrc file, since they change for every book.

The .pielrfrc is NOT created automatically. You can create one yourself, or you can have pielrf write out the current options with the "--writerc" command line switch.

This creates (or overwrites) the ".pielrfrc" file in your home directory. Either "/Users/<username>/.pielrfrc" on Mac OS X / Linux / UNIX or "c:\Documents and Settings\<username>\.pielrfrc" on Windows.

Thanks to Lee Bigelow for providing the code for this feature

FORMATTING ADDITIONS

The new tags "<justified></justified>" and "<verse></verse>" allow you to mix paragraph styles within the text.

Standard text has every paragraph's first line indented by the amount indicated in "parindent" to delimit a tab (you know, every paragraph in a book).

<justified></justified> tag makes the whole paragraph left justify, meaning it does not have the first-line indentation.

<verse></verse> makes each paragraph reverse-indent. The first line is justified (on the left margin), and subsequent lines are indented. This allows you to include poetry in your book.

The defaults for "--verseparindent" matches exactly with the default margins and indent used by pielrf. If you use the <verse></verse> tags AND change your margins, you probably need to adjust the "--verseparindent" and "--quoteoffset" options. Beside the default, using "--quoteoffset=50" and "--verseparindent=-225" are good alternatives.

FORMATTING CHANGES

(1) The main change is that the formatting tags "<center>" and "<h1>,<h2>,etc." used to generate a new paragaraph when the open/close tags were encountered. This is no longer the case -- unless the tags form their own paragraph (see below). For example, you can now have standard paragraphs followed by centered text with no interveneing vertical whitespace (crs).

Here's two examples to illustrate behaviour of the center tag.

<tabchar>And this time he'd make sure they didn't fail. He had a plan.
<center>
* * *
</center>
<tabchar>The repaired alarm clock rang at six o'clock the next morning.

Generates

And this time he'd make sure they didn't fail. He had a plan.
* * *
The repaired alarm clock rang at six o'clock the next morning.

And this...

<tabchar>And this time he'd make sure they didn't fail. He had a plan.
<tabchar><center>
<tabchar>* * *
<tabchar></center>
<tabchar>The repaired alarm clock rang at six o'clock the next morning.

Generates

And this time he'd make sure they didn't fail. He had a plan.

* * *

The repaired alarm clock rang at six o'clock the next morning.

In these examples, <tabchar> is the actual tab character, and is the paragraph telimiter (-b tab).

(2) The "<blockquote>", however, still generates a single vertical whitespace. Though if you have mulitple <blockquotes> in a row, you get only 1 vertical whitespace.

When you tested it in Windows, did you test the install and see that it actually works without having to call Python? If you have to call Python in Windows, then you might as well give it up for lost for most novices as that will lose then totally.

if they're using the command line anyway, it's not hard to add ONE WORD to the command you're typing. Please quit whining about trivial things, and let Pie focus on adding features that are useful.

Thx.

For people not used to a command line, they'd have to find the path to where Python lives and put in the full path in the command line as well as the command. This will cause a lot of frustration. If the Python programs had the .py extensions on them it would be a lot easier to just type pielrf.py and then whatever option you wanted. The tools need to be made easy to use or they won't get used. This is the way it is. It's not whining. People who grew up in a GUI world and did not learn the command line need to have the command line programs made as easy to use as possible.

When you tested it in Windows, did you test the install and see that it actually works without having to call Python? If you have to call Python in Windows, then you might as well give it up for lost for most novices as that will lose then totally.

Indeed, I don't have python in my Windows path, so I certainly have seen the benefit of this feature.

As I mentioned in a previous post, I couldn't get this to work in time for the 2.1 release, but will do it in an upcoming version. I'll either have to rename the pielrf library, or use py2exe as kovidgoyal suggested... both of which would have held pielrf 2.1 up, and it was already overdue.

I have a request for a feature. Is there any way to implement a <h0> tag, to force text that pielrf normally makes a header (like the first bit of a section, up to the first paragraph) to display as normal paragraphs? I'm trying to do a bit that looks like this:

and only have the two lines in the middle show up bigger.
Any suggestions?
P.S. Thanks for fixing the << issue, I LOL'd at your comment in the readme (especially since I knew it was directed ar me ^_^)

I have a request for a feature. Is there any way to implement a <h0> tag, to force text that pielrf normally makes a header (like the first bit of a section, up to the first paragraph) to display as normal paragraphs? I'm trying to do a bit that looks like this:

and only have the two lines in the middle show up bigger.
Any suggestions?
P.S. Thanks for fixing the << issue, I LOL'd at your comment in the readme (especially since I knew it was directed ar me ^_^)

If I interpret what you're asking correctly, there's a workaround. Specify "--chapterfontsize=95" and "--chapterfontweight=400" to have it match normal text. THEN you can add an <h1> tag to enlarge the font. Sort of a backwards way of doing what you're asking!

Quote:

Originally Posted by JSWolf

It would be a nice idea to be able to specify text in the font and font size we want. I would love to be able to have embedded fonts.

I'll have to look into the embedded fonts, along with the <h0> idea. Right now, I only have limited support of font sizes -- basically two sizes, normal and header. I don't currently have plans to move beyond this, but... we'll see.

If I interpret what you're asking correctly, there's a workaround. Specify "--chapterfontsize=95" and "--chapterfontweight=400" to have it match normal text. THEN you can add an <h1> tag to enlarge the font. Sort of a backwards way of doing what you're asking!

Sweet! I'll play around with this when I get home from work tonight!

EDIT: I tried compiling the file as you said, but the H1 and H2 tags are not affecting the text at all. I also tried it with a tab at the beginning of each line in the header, and no dice. Everything is all small (which _does_ look better than everything being frickin' huge)