On Sat, 23 Nov 2002, C Bobroff wrote: > > One point to raise is that the Nazanin we use is not *hinted*. Their > > Nazanin should be hinted. So our Nazanin is not based on theirs. > I wish I knew what hinting is. No, never mind. I don't want to know.
It should be interesting for you. It is lack of hinting (or improper hinting) that makes some fonts very ugly or unreadable in small sizes. It's good hinting that makes Tahoma the popular font it is. > However, our Nazanin has a whole list of defects: could use a few more of > the rarer glyphs (like dagger alif), You mean Unicode's SUPERSCRIPT ALEF? > But why did Microsoft even pay money for a ready-made font with so many > defects? And why Nazanin? Monotype/Linotype Nazanin is supposed to be free of these defects. I suggested Nazanin to Microsoft, after they were trying to license Mitra from Monotype/Linotype. I also suggested Traffic. I don't know what may have happened after that. > And why did this guy tell me that the font has nothing to do with the > diacritics break-up problem and that it was a browser problem? Can it > really be possible he doesn't know that it DOES have to do with the font? That was a bug in the our copy of the font. I don't know about the guy. > But what if they on-purpose don't fix the diacritics problem so that the > font won't work in non-IE browsers? Who are you talking about here? Sinasoft? Borna? Microsoft? *type? > What if I want to add dagger alif but can't because the new Nazanin MS > is no longer freeware?? No, you won't be able to modify Microsoft's distributed Nazanin legally. But I guess it will hopefully include the dagger Alef. roozbeh _______________________________________________ PersianComputing mailing list [EMAIL PROTECTED] http://lists.sharif.edu/mailman/listinfo/persiancomputing
