Ronald Florence said:
OK, I found the Gentium font that Matt recommended. Easy to istall,
comes up fine in Word 2004, and (Yes!) it handles the unicode characters
I need to use. It is not especially attractive (better than Times
Roman, but no prize), but it is versatile and it comes up with the
correct characters not only on the screen, but in PDF and presumably in
printed output. Many thanks, Matt!
For what it is worth, trade publishers (Random House, Viking, St.
Martins, etc.) and university presses want manuscripts submitted in what
I call "lowest common denominator" format -- Times Roman, no different
fonts or font sizes for headings, etc. I've done enough books that I
can get away with some variations from that requirement, but if my ms.
requires the editor and production department to fetch a font off the
Internet, I can pretty much predict the reaction ... and it may not be
pretty.
Gentium was a pleasant surprise to me too. (Thanks again Matt)
I think the Gentium authors permit you sending the font to the
publisher. IANAL but they seemed to say so on.
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=Gentium
"Gentium is freely available and may be used by anyone at no cost. It
is not public domain, and cannot be altered, but can be given to anyone
who might need it."
I guess you have a pretty good case for getting Random House to accept
it. I'm pretty sure that if you fronted up with an Ms full of my EQ
kluge and one with it set in Gentium, they would take the latter.
On the other hand a university publisher would prefer LaTeX surely?
If I were a publisher, I'd be running LaTeX courses for all my writers
and supporting a TeXniXal ;-) department for creating special TeX
macros for guys like you who need runes more than you need fonts ;-)
As an aside, I spent a little time this morning looking for LaTeX tools
that support unicode. I am still a bit confused about what might work.
I have not yet sprung for Word 2004, so I don't yet have first hand
experience with Word's unicode, but I'm fearing the worst and teaching
myself LaTeX and emacs. Something I should have done years ago.
Warning! Long boring aside follows:-
...not to mention a rambling introduction..
When programming, my preferred editor is teco. I use it in a command
mode where the bottom three lines of the screen show my commands and
the rest shows what a mess I have made of the text. People who see me
at work walk away shaking their heads and mumbling what seems to sound
like "dinosaur".
Keeping emacs and teco apart is strangely difficult. My fingers know
teco. Emacs is similar but different and equally full of arcanity. You
should be able to keep your thinking about layout *almost* separate
from your thinking about content. Thinking about driving the text
editor should be halfway down your spinal column if not right in your
fingertips.
Word /almost/ gets this right, except that you know two things
1. What you see is as good as you get
2. Your reader/publisher won't see it that good
(Gosh, that sounds like the first and second laws of thermodynamics!)
....so you get the visual clues, supported by outline view when you need
it for keeping your subject thoughts in a row. This is good. What is
not so good is that when the numbering goes wrong, or the styles go
doolally, you have to swap to typographer mindset before you can
continue.
LaTeX on the other hand, keeps those tasks apart. Too far apart. It
forces another mindset on you, that of skillfully driving your text
editor to navigate the logical structure of your writing.
I have been playing with LaTeX because I am getting increasingly
irritated with Word's capriciousness. So many of the things it thinks
it is helping me with are an annoyance. Sometimes it makes something
that should be easy far too hard. To be even-handed, there are lots of
little 'helps' that really do help ;-)
What Word needs is an author/publisher view. Perhaps all that we don't
have is a set of templates and page set-ups. Ronald, you could probably
help me here. What do the publishers give you in the way of templates
and styles and procedures to make your dealing with them efficient?
It would do Word's developers no harm to look carefully at TeX and
LaTeX (I know, they are way ahead of me here - EQ fields are a nod
toward TeX) and work out a way to get some of the good bits into Word.
Right, that's enough Monday quarterbacking, and its only Saturday.