RE: [Openinteract-dev] Small i18n issue

[Kutter M. <mar...@si...>]

Hi Teemu,

Your step 6. is not an issue with perl >= 5.8.0
Perl >= 5.8 supports IO-Layers that can be used to filter/recode content 
almost transparently (almost means: exactly like your example).

I don't think that all backends need to support utf-8 - if they don't 
that's no harm as long as we can recode it in the backend (currently we're 
recoding iso-8859-1 to utf8 for utf8-aware backends).

As for 7., using perl's locale() should override the broad scope of utf8's
\w meaning. 
And backends that support utf8, normally support searches etc on them, too.

I agree with you that full utf8-support will probably require perl >= 5.8.

But as we're probably talking about years until everything's up & working, 
this should not be an issue (hey, there's perl 5.10 out by nor - and perl6
will raise, too. Sure it will.).

Regards,

Martin Kutter

-----Original Message-----
From: ope...@li...
[mailto:ope...@li...]On Behalf Of Teemu
Arina
Sent: Mittwoch, 8. September 2004 17:02
To: Kutter Martin
Cc: 'ope...@li...'
Subject: Re: [Openinteract-dev] Small i18n issue

> Step 4 would probably be an issue for the Controller -
OI2::Controller::Raw
> should never re-code anything, and alternative controllers like, let's say
> for outputting PDFs - probably shouldn't recode their stuff, too.

I do agree. Although content_type should not include charset=iso-8859-1 as
it 
does now.

> This would allow OI2 to use UTF-8 only in it's internal processing, but
> serve frontends with potentially different character encodings.

Utf8 atleast for internal data presentation is the way to go. I would also
pay 
attention that utf8 from backend to frontend is also possible without losing

any bits or forcing to certain character set in the middle. i.e. russian 
interface with chinese content should be possible. This of course requires 
that all the backends speak utf8.

> 1. get the charset from the request
> 2. encode all parameters as UTF-8 when fetching them in the request object
> (all but uploads)
> 3. set the Content-type: charset="foo" for the response (if needed).
> 4. encode all output in the Response object to the appropriate charset
just
> before sending it (if needed).

For full UTF-8 support, also:

5. translation files (I18N/maketext framework) should be in standard GNU 
gettext (PO) format which is binary safe, instead of the current system
which 
is poorly utf-8 compatible
6. Reading/writing OI2 configuration files should also be utf-8 compatible, 
with something like:
open( INI, ">:utf8", "action.conf" );
7. Searching and text parsing should be utf8 compatible. This means use
utf8; 
and support for utf8 on the database backends. At the moment =~ /\w/ doesn't

work very well with utf8 content ;)

Full support most likely requires perl 5.8.x =(... 5.6.x utf8 support just 
sucks (Encode module for example does not work with 5.6.x).

-- 
--------------

Teemu Arina
www.dicole.org



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
openinteract-dev mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/openinteract-dev