Re: CUPS in Action (need help :)

[Ahmad Khalifa <ahmad at khalifa dot ws>]

Nadim Shaikli wrote:
> Could you then regenerate the .PS using a monospaced Arabic font for us
> to see ?  If all is well (and I think there were other issues with regards
> to Harakat and composing characters taking too many spaces) then we should
> proceed with getting this patch adopted - as it stands now it does a hell
> of alot more with it than without it :-)

yeah sure, just need the monospaced font :?
If you have a monospaced pfa font, try putting it inplace of
Kacst-Qr.pfa and see what happens :)

regarding harakat, AFAIR it was fixed.

> NO, no, no - ___never___ give up, please don't.  This and others are very
> important topics and we are very eager to complete 'em and again sorry for
> my delay (why no one else stepped forward is a different story :-)

well, there is a certain limit to what 1 person can do.
you dont need to apologize as you have been the most helpful.
Thanks again :)

BTW, if you do get a font (and for future reference), the Kacst-Qr.pfa
     font file has 256 entries (or glyphs or characters or whatever
     they're called) the lower 128 are from the 0x600 range, and the
     uper 128 are the 0xFE70 range (Pres. Form-B), the Unicode values
     are tied to the names of the glyphs in file
     /usr/share/cups/data/psglyphs . so if you do get a font you need
     to edit most of the font using pfaedit (from sf.net) and make sure
     it complies with the names in psglyphs (or change the names in
     psglyphs, but CUPS would like to stick to adobe's standard names)

     In short, the Kacst-Qr.pfa font is 128 values from 0600 range and
     128 values from FE70 range, because CUPS would like to keep them in
     1 font.


ak.