Re: CUPS in Action (need help :)

[Nadim Shaikli <shaikli at yahoo dot com>]

--- Ahmad Khalifa <ahmad at khalifa dot ws> wrote:
> 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 :)

Ahmad, I'm not going to pretend like I know what the heck you are
talking about (I don't :-), but if you are in need of a monospaced
.pfa font file then can't we simply convert a monospaced TTF to a
.pfa using 'ttf2pfa',

  http://ttf2pt1.sourceforge.net/ttf2pfa.html
  (In passing, http://mheath.customer.netspace.net.au/ttf2pt1)

So if this is a possiblitiy, we now simply need a monospaced TTF
to start with (Uniball noted that KACST shipped one).

> regarding harakat, AFAIR it was fixed.

Ah, we'll need to verify that then ;-)
 
> 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
>      upper 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

pfaedit is now called fontforge (http://fontforge.sf.net :-)

>      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.

OK, this all sounds simple enough (ie. sounds like you've gone through
this pain once or twice :-).  So let's find a monospaced TTF convert it
to .pfa and verify the CUPS patch.

BTW: I get the feeling this is really secondary to what you've done to
     CUPS, so beyond all the .PS file mangling would it be possible for
     me to print things or can I bypass this hurdle to verify things a 
     different way (doubt it, but thought I'd ask).

Wait a second.  So CUPS requires you to use monospaced fonts to print
even in latin/english characters ?  This seems like a rather hefty
limitation, no ?  Meaning, if/when we get this going - we'll have
one font we can use to print things and from the sound of it we won't
be able to print both latin and Arabic due to the 256 entries
limitation (maybe), right ?  Sorry for all this confusion, just trying
to understand what the heck is going on.

Salam.

 - Nadim


		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com