Re: next step.

["alsayed" <alsayed at mum dot mans dot edu dot eg>]

> Yes. We need to solve the following problems:
>
> - Memory representation of the characters that come over the wire. As
> I mentioned before I like the mlterm way and am thinking to borrow
> from there.
>
> - Understand the Windows Text and Font APIs. To be more specific,
> given a character code, UTF-8 or unicode, and a font, we need to
> locate the corresponding glyph from the font, and ask windows to draw
> that glyph. Microsoft's MSDN is your best friend here.
>
> - Implement shaping and BIDI, again borrowing from current
> implementations.
>
>
> I suggest that you take the second one, and I will take the
> first. What do you think ?
>

i see three problems , two requires programming( work , searching , ...
etc ) and one required researching .
the two requires programming is 1 and 3 and the one requires research is 2
so what do you mean about second  problem ?
2  - Understand the Windows Text and Font APIs. To be more specific ... etc

or  - Implement shaping and BIDI, again borrowing from current ?

or the first .  :-)


that is first thing ?

the second , i will do exactly what you will ask from me , so i will take
any job you specified to accomplish .

i need to learn and help .

the third , how to start exploring the code , any guidelines , any comments
, any urls .

the fourth , i need to download the code which url i will use ?.

i see that from th discussion that our tareget is win32 systems , is this
true ? will we trnsfer it to linux environments in the future ?.

> I don't see any need to change the "back-end" that is the low level
> communication and encryption logic. We are lucky that encryption
> algorithms used in ssh are not language depdnedent ;)
>
okay , until now i didnot see any code , but i will , iam happy that we are
lucky ;-) but iam still i need to explore the code and start contributing .

the glosssary will be available at staurday , and i will send it to u to
make any reviews and comments .


sayed








----- Original Message -----
From: "Kamal Dalal" <kamal+arabeyes at banoora dot net>
To: <developer at arabeyes dot org>
Sent: Monday, October 28, 2002 7:48 PM
Subject: Re: next step.


>
> On Mon, Oct 28, 2002 at 07:06:11PM +0200, alsayed wrote:
> > the first step i had already satisfied with working with PuTTY .
>
> Good!
>
> >
> > the problem still exist as iam here behind firwall and IRC is restricted
the
> > only way i have to chat is MSN (my id is alsayedtaham at hotmail dot com) i
dont
> > reply on this mail  :-).
>
> Then let's forget about char, and communicate via email. Shouldn't be
> a problem there.
>
> >
> > >I am looking into patching PuTTY, and make it shape arabic letters
> > >correctly.
> >
> > from the arab eyes site i had seen the first post of mr kamal dalal and
i
> > can now understand the problem , that he is trying to diplay arabic
> > characters correctly along with other characters in the shell .
> >
> > so my next step now is to explore the program architecture  ?
>
> Yes. We need to solve the following problems:
>
> - Memory representation of the characters that come over the wire. As
> I mentioned before I like the mlterm way and am thinking to borrow
> from there.
>
> - Understand the Windows Text and Font APIs. To be more specific,
> given a character code, UTF-8 or unicode, and a font, we need to
> locate the corresponding glyph from the font, and ask windows to draw
> that glyph. Microsoft's MSDN is your best friend here.
>
> - Implement shaping and BIDI, again borrowing from current
> implementations.
>
>
> I suggest that you take the second one, and I will take the
> first. What do you think ?
>
> I don't see any need to change the "back-end" that is the low level
> communication and encryption logic. We are lucky that encryption
> algorithms used in ssh are not language depdnedent ;)
>
> >
> > also iam now making glossary file (text file ) from the link you had
post
> > about all terms found in it to be small reference .
> > and if i can i will translate it also .
> >
>
> Great!
>
> _______________________________________________
> Developer mailing list
> Developer at arabeyes dot org
> http://arabeyes.org/mailman/listinfo/developer