DefaultJetspeedParameterParser (Jetspeed-japan-dev) - Japanese Support for Jetspeed

こんにちは．

DefaultJetspeedParameterParser と JetspeedTemplatePage のパッチについて，
以下のようなメールを jetspeed-dev に出しておきました．だいたい間違っていることは
言っていないとは思っていますが，何かコメントなどありましたら，お願いします．

これを機に国際化の問題などを意識してもらえれば良いかと思っています．
まずは，すべてのメッセージを翻訳できる状態にしてほしいですね．

shinsuke

-------- Original Message --------
Subject: Re: cvs commit: jakarta-jetspeed/src/java/org/apache/jetspeed/util/parser DefaultJetspeedParameterParser.java
Date: Sat, 15 Feb 2003 13:57:10 +0900
From: Shinsuke SUGAYA <shins****@yahoo*****>
Reply-To: Jetspeed Developers List <jetsp****@jakar*****>
To: Jetspeed Developers List <jetsp****@jakar*****>
References: <20030****@icaru*****>

Hi all,

I have Japanese(L10n) Jetspeed proje****@sourc***** in Japan.
The target of this project is to add a feature/fix for Japanese environment.
DefaultJetspeedParameterParser and JetspeedTemplatePage patch were created
as I18n fix in the project. I describe it below.

Jetspeed 1.4b3 has 2 issue:

 1) The page encoding is specified by content.defaultencoding in JetspeedResources.properties.
    Applying the JetspeedTemplatePage patch, Jetspeed uses the encoding by the following
    priorities.

     1. character-set parameter in media.xreg
     2. content.defaultencoding in JetspeedResources.properties
     3. UTF-8

    Using this encoding order, Jetspeed uses UTF-8 when media-type is text/html.
    Therefore Jetspeed can display a multibyte character(ex. Japanese) correctly in the
    default environment. (For Jetspeed 1.4b3, user must change content.defaultencoding
    in order to display the multibyte character correctly.)

 2) The form data is not parsed correctly.
    For example, in the HelloVelocity portlet, a multibyte character is displayed as
    "?" or garbage if user submits it. So the portlet developer needs to add a code
    for handling the correct encoding into the portlet. The cause is to parse the form
    data by 8859_1. Therefore, using DefaultJetspeedParameterParser, the form data
    is parsed by correct encoding.(The portlet developer does not need to add the special
    code) DefaultJetspeedParameterParser applies the following priorities when determining
    a encoding information.

     1. the character encoding used in the body of the request.
     2. character-set parameter in media.xreg
     3. content.defaultencoding in JetspeedResources.properties
     4. US-ASCII

    In many cases, it will use the character-set parameter in media.xreg.

 Please let me know if you have any comment about DefaultJetspeedParameterParser and
 JetspeedTemplatePage patch.

I think that Jetspeed has the I18n issues, such as #14464, #13286(Please fix this bugzilla bugs.
I attached info for fixing it.) and the L10n properties file(since all messages are not picked up
to the properties file, I cannot localize Jetspeed...).

Japanese Jetspeed project would like to contribute to Jetspeed from the point of view of I18n and L10n.

Best regards,
 shinsuke
--
Jetspeed for Japanese (sorry, Japanese only...)
 http://sourceforge.jp/projects/jetspeed-japan/

__________________________________________________
Do You Yahoo!?
Yahoo! BB is Broadband by Yahoo!  http://bb.yahoo.co.jp/

Japanese Support for Jetspeed

[Jetspeed-japan-dev] DefaultJetspeedParameterParser