Re: Arabic on Zaurus/Ipaq

[Abdulhaq Lynch <al-arabeyes at alinsyria dot fsnet dot co dot uk>]

I'm replying in the developer list.

On Monday 28 February 2005 13:29, Mohammed Yousif wrote:
> On Saturday 26 February 2005 16:34, Abdulhaq Lynch wrote:
> > I think initially the thing to do is to port QtQuran and keep the
> > bidi/shaping as a library call for now. When we've done that we can try
> > to incorporate the bidi/shaping into Qt/E itself. What do you think?
>
> I don't think it worth the trouble to add this code to Qt/E if anyway
> Qt4 will solve this problem altogether. It also will not benefit porting
> QtQuran since we would have to draw text ourselves anyway due
> to the various Unicode limitations w.r.t this topic.
>
> So, I go for keeping bidi/shaping as a library call temporarily until
> Qt/E can do it in its own.
>
> > How will you test the code? Do you have a zaurus? (I bought mine (SL5500)
> > second-hand recently for about 100 pounds and I'm very pleased with it.
> > The only down side is the short battery life). The OpenEmbedded
> > development environment needs at a bare minimum 512MB RAM and really it
> > needs over 800MB. It takes about 4G of hard disk space and a lot of Sabr
> > too.
> >
> > It is also possible to run everything on a PC in a virtual framebuffer
> > but you will need a fair amount of RAM as I say.
>
> I don't have a Zaurus and I don't plan to get one (can't afford it anyway
> and no real need for it, My Sony CMD-Z5 "although, not exactly your
> favorite handheld" is more than enough for me :-)
>
> When I decided to port QtQuran, I was planning to test it in my PC anyway.
>
> > Even if that is not a possibility for you, you could be a massive help in
> > changing (as you mention) the XML code etc. in the QtQuran app itself.
>
> So, expat is there, that is good. All we need now is to strip Audio code
> and such.