- Further updated the manual (still work-in-progress!)
- Few minor bugfixes
Thanks, León. The ‘curly quotes’ in the table on page 39 of the PDF manual are still not curly, but you probably knew that already!
Yeah, we want to change the font from Arial to Verdana, but I ran into some issues yesterday. Will try again later.
Further updated manuals:
- Font changed to Verdana
- Bullet items fixed
- Smart quotes fixed
- Several other typo’s and items fixed
Looking good. I will take a closer look later.
There are still many remnants of Arial in the title and copyright pages, in the Table of Contents and Index, on the Chapter Title pages, in the Headings, in the page numbers, headers and footers, and in the numbered list on page 33 about Recommended Glyphs. Changing that should be easy, and would make for more consistent typography.
I am not one of those who just hate Arial because it’s a poor quality rip-off clone of Helvetica, but one font for all text is best, unless the body text is a Serif font, and headings are Sans Serif.
I attach a PNG screen shot for the Pali WOFF font test. It may be your PDF compression that is making such a mess of it, but it might be worth trying again.
I have uploaded a copy with some Comments to Wikisend
FontCreatorManual.pdf (Password = FontCreator81049)
What do you mean by “Missing smart quotes” ? you want us to change all quoted text to use those? or do you want a reference to them in the text?
For example: This can be useful to create an “override”
should be: This can be useful to create an “override”
There are some places where straight quotes are intended to be used, e.g.
quotedbl quotation mark " $0022
and
Smart quotes (also known as curly quotes) are fancy characters which make text look better compared to the straight apostrophe (') and straight quote or inches character ("). Microsoft Word also automatically changes 3 periods to an ellipsis.
and
!"#$%&'()*+,-./:;<=>?@©€
but in nearly all places they should be smart quotes.
In some places, you could drop the smart quotes entirely, using Bold for emphasis instead, e.g.
Selected glyphs in the overview window can be displayed in the Preview toolbar by pressing the > P > shortcut key. You can also use > Shift P > to add the selected glyphs to the current text.
The usual UK style is to put the punctuation before the close quotes, e.g. “black is on the right.”
Instead of “black is on the right”. This may be different to US style — I am not too sure.
You could argue that this is a purely stylistic choice, and that it therefore doesn’t really matter which way you go (as long as you’re consistent, of course). One instance where it clearly does matter is the ‘Sample’ column of the table on page 40 of the PDF file (numbered as page 34) but this has been corrected in the current build.
In my experience, it’s exactly the other way around!
Further updated the manuals. Everything mentioned in Bhikkhu Pesala’s last PDF has been put in except for the “smart” quoting. We’ll decide later on whether or not to change that in the entire manual.
>> DOWNLOAD PDF<<
>> DOWNLOAD Windows Help<<
There’s a mixture of Arial and Verdana on page 30 of the PDF file (numbered as page 24); also page 35 (numbered as 29) . I don’t know whether there are any other occurrences outstanding, but those ones are particularly noticeable.
Yes, there’s still lots of occurrences of Arial — open the PDF in PagePlus to check the Resource Manager.
- The Table of Contents contains several instances.
- Top of page 10 of the manual — From the font overview …
- Bottom of page 7 — The contours should stay within the visible area (the line-spacing is set to exactly 11.25pt for 11.25pt text, so it is too tight)
- Top of page 8 — Edit a glyph (same line-spacing issue)
- Bottom of page 8 — contours that need to be filled black
- Bottom of page 9 — Now we have finished
- Page 10 — To make your font available (and line-spacing)
- Page 11 — When you are satisfied
- Page 17 — Warning: if you want to open (and line-spacing exactly 9.75 pt instead of single)
- Page 18 — In Windows (line-spacing)
- and many other places
- Page 70 — Bounding box values
The one from the table of contents is mandatory, the dots after each item have to be Arial for the layout to stay ok. The other Arial related ones should be fixed for the next beta. I’ve tried the free version of Page Plus, but unfortunately does not support opening of PDF files (or am I missing something here?)
I don’t see an issue with the line spacing here and at the other places, maybe I accidentally already fixed it, could you check again with the next (released later today) beta?
Here’s is a PagePlus version that you should be able to open. Search all stories for Format, Font, Arial.
FontCreatorManual.7z (Password = Fridsma
Thanks for the attempt, but the resource manager is also not part of the free version 
You don’t need to use the resource manager — you can use the Find dialogue, though I guess you could equally do that in the source document in Word or whatever you’re using.