Re: UTF8 and (La)TeX backend?

2005-01-04 Thread Werner LEMBERG
As perverse as it probably sounds in the very first moment, what do you think of always create an EPS file, even for the TeX backend, but without the text strings? Hmmm; that's an interesting idea. I agree it sounds perverse at the beginning, but on 2nd thought it actually makes sense,

Re: UTF8 and (La)TeX backend?

2005-01-04 Thread Werner LEMBERG
Ideally, those OpenType TeX fonts should behave similar to any other OpenType font; this means the loss of italic correction (which isn't available in OpenType fonts), for example, but it assures that the font interface doesn't have to cope with special cases.

Boxed rehersal marks

2005-01-04 Thread Erlend Aasland
Hello I find myself using boxed rehersal marks all the time. Instead of using long \markup stuff, I've created a patch for scm/translation-functions.scm. This patch makes it easy to write \mark \default and get nice boxed rehersal marks: \set Score.markFormatter = #format-mark-box-letters, or

Re: [Fontforge-devel] Re: UTF8 and (La)TeX backend?

2005-01-04 Thread Rogier van Dalen
On Tue, 04 Jan 2005 09:09:16 +0100 (CET), Werner LEMBERG [EMAIL PROTECTED] wrote: Ideally, those OpenType TeX fonts should behave similar to any other OpenType font; this means the loss of italic correction (which isn't available in OpenType fonts), for example, but it

Re: [Fontforge-devel] Re: UTF8 and (La)TeX backend?

2005-01-04 Thread George Williams
On Tue, 2005-01-04 at 00:09, Werner LEMBERG wrote: Ideally, those OpenType TeX fonts should behave similar to any other OpenType font; this means the loss of italic correction (which isn't available in OpenType fonts), for example, but it assures that the font interface