[OGo-Translation] Hebrew support

[Danny Lieberman]

Helga

Does OGo have PG functions and/or have meta-data inside the database that
would have to be converted?

An issue with Exchange conversion may be data, MS Office uses UCS-16
internally, whereas IE supports UTF-8 nicely. Most of our target
market here are MS Exchange users so we can safely assume that they will be
using IE.  This is a onetime issue for the Exchange to OGo migration
utility.

Maybe a kludge - but I think we could get a quick version off the ground if
we limited ourselves to Hebrew(Windows) encoding which is 8 bit.
and shouldnt require changing the codebase and at most will require a
pg_dump and pg_reload of the database

I'm also concerned about mapping functionality between Exchange and OGo - if
you have a table that'd be great - if not we'll start gathering the data in
our investigation and post what we have.

Is there an issue with using qmail? That is our MTA of choice.
wr
Danny Lieberman
OSI-Open Solutions Israel
+972-8-970-1485(voice)
+972-54-471114(Cell)
www.software.co.il



----- Original Message ----- 
From: "Helge Hess" <helge.hess@opengroupware.org>
To: <translation@opengroupware.org>
Sent: Thursday, March 11, 2004 1:46 PM
Subject: Re: [OGo-Translation] Hebrew support


On Mar 11, 2004, at 12:29 PM, Danny Lieberman wrote:
> We're thinking about doing hebrew support - if I'm not mistaken we'll
> have to consider the following:
>
> 1. Code changes for UTF-8 /Unicode support - I notice that the system
> is 8 bit today.

Most of the system is Unicode (NSString API). Its mostly libFoundation
which is, again mostly, 8-bit.
I guess instead of tweaking libFoundation, one should rather work on
the gstep-base port (gstep-base is already completely Unicode aware).
Apparently compilation with gstep-base is smooth now, though I'm not
sure whether it works.

> 2. UI translation

Yes. You could start that (in "blind" mode) before so that people
working on the Unicode system actually have something to try out.

> 3. Input methods - I'll assume that we're using a 100% browser
> interface so this should be pretty easy especially if clients are IE 6

Probably.

> 4. Postgres - conversion to a Unicode database

Yes, this would probably also require some changes in the OGo
PostgreSQL adaptor (in ThirdParty/gnustep-db/PostgreSQL72).

> 5. Help pages

The online help system isn't in place (yet ;-).

> 6. Microsoft Exchange migration utility

Yes, something like this would be awesome.

> anything I've forgotten?
>
> based on other language ports - how much time should we scope out?
> (I've got my own estimates but I'd love to hear other people on this
> topic)

Well, making the full codebase Unicode aware is going to take quite
some time (but is of course well worth the effort).

regards,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org

-- 
OpenGroupware.org Translation
translation@opengroupware.org
http://mail.opengroupware.org/mailman/listinfo/translation