[OGo-Translation] Hebrew support

[Helge Hess]

On Mar 11, 2004, at 1:13 PM, Danny Lieberman wrote:
> Helga

Please, thats Helge ;-)

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

No.

> An issue with Exchange conversion may be data, MS Office uses UCS-16
> internally, whereas IE supports UTF-8 nicely.

OGo uses UTF-16 internally from an API point of view. Conversion 
from/to client encodings is automatic if the Foundation library 
supports that. libFoundation has some support for conversions, but only 
supports 8-bit mutable strings (more exactly: only 8-bit ISO-Latin-1 
strings).

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

I don't think that we have a major issue here.

> 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

This is not really relevant for OGo. Most code in OGo which relies on 
8-bit also relies on ISO-Latin-1 (eg for transparent UTF-16<->Latin-1 
conversion).

So I don't think that limiting yourself to Hebrew 8-bit will make 
things easier.


The following should be discussed/follow-uped on users@ogo:

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

We have no mapping for that. It really depends on how the users store 
their data in Exchange.

> Is there an issue with using qmail? That is our MTA of choice.

Qmail works, but AFAIK you need to set some defaults.

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