On 20 Jun 2006 17:23:16 -0000, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
------- Additional comments from [EMAIL PROTECTED] Tue Jun 20 10:23:10 -0700 2006 -------
The *only* way to have truly correct placement of nikud/vowel points/diacritics
is to use an OpenType font, which is what OOo currently does.

The old OOo used to use a heuristic method of positioning nikud/vowel
points/diacritics by guesswork, which is prone to breakage. I think it does not
work with multiple marks on a single consonant, for instance. The problem is
that non-OpenType fonts only have glyphs for nikud, but no positioning
information--this is why non-OpenType fonts are inadequate for proper Hebrew
nikud support. The best that can be done with these fonts is to guess, which is
at best completely inadequate for serious Hebrew word processing and publishing,
and at worst completely broken for more complex rendering such as multiple marks
on a consonant.

this all sounds very good and interesting, but it does nothing to eleviate the fact that other software (specifically any using pango, I guess) does correct (or close enought to correct) diactrics without that much trouble - including multiple marks on the same letter.

While I understand that there is one "Right Way (tm)", I also know that TrueType fonts are here to stay and at least with other implementations they are quite usable.

I wish that OpenOffice would support both font types, but if that is a problem then I personally would prefer that more effort would be put into making TrueType fonts usable as TrueType fonts are much more likely to be available then OpenType fonts - specifically almost all (all?) Operating Systems for which OpenOffice is bundled today offer Hebrew TrueType fonts (if at all) installed by default and AFAIK none offer OpenType fonts (which always have to be installed from a 3rd party).

--
Oded

Reply via email to