Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-09 Thread Mark Williamson
Hi Stefan, You are correct. However, I stand by my statement that it covers Kharoh because it does, in the same way that James Kass' Code2000 covers Burmese: it includes the basic glyphs, but not the OpenType tables nessecary for proper rendering of the script. When I made the font, I had no

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-09 Thread Andrew Glass
Dear Mark, I was interested to see that you had taken the trouble to make a Kharosthi font. It is exciting to see that people have noticed that Kharosthi is now part of Unicode, and a complement to our efforts to have it included in the first place, Thank you! As for the font, as Stefan has

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-09 Thread Paul Wise
On Sun, 2005-05-08 at 19:06 -0700, Stefan Baums wrote: Please do not package this font as is. It has already been packaged, no-one has sponsored the upload yet [1]. BTW, thanks go to the three of you for the interesting discussion on fonts :) I'm not very familiar with OpenType/fonts, or

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-09 Thread Stefan Baums
Dear Paul and Mark, I'm not very familiar with OpenType/fonts, or editing them, so I'd have to defer any changes to Mark. let me explain the problem a bit more. In any program where you dont explicitly configure a separate font for every script under the sun, which means pretty much anything

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-09 Thread Mark Williamson
On 09/05/05, Stefan Baums [EMAIL PROTECTED] wrote: Dear Paul and Mark, I'm not very familiar with OpenType/fonts, or editing them, so I'd have to defer any changes to Mark. let me explain the problem a bit more. In any program where you don't explicitly configure a separate font for

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-09 Thread Stefan Baums
From what I know about Limbu, complex shaping requirements are minimal and text can be read almost as easily without them. I am glad to hear that. As regards Kharosthi [...] although it definitely doesn't look good and is probably very difficult and irritating to read. Yes. I think it's

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-08 Thread Stefan Baums
Please do not package this font as is. It purports to cover the Kharoh block, but all the author did is copy the illustrative glyphs from Unicode 4.1 into the corresponding encoding slots. However, in common with the modern Indian scripts, a Kharoh font also needs contextual replacement

Bug#306290: ITP: ttf-mph-2b-damase -- font with ranges from the latest version of unicode

2005-05-08 Thread Stefan Baums
PS. On closer inspection, it seems that the Kharoh glyphs in the Damase font are in fact not just copies from the Unicode charts, but original designs. Which is great! Id be interested to hear (outside this bug report) what they were inspired by. (The real problem of the font no contextual