> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: Proposal for implementation of lookup of localized
web-resources
> From: [EMAIL PROTECTED] (Kazuhiro Kazama)
> X-Dispatcher: imput version 20000228(IM140)
>
> Arieh,
>
> Basically lookup of localized resources is welcomed. As I have
> evaluated your localization codes to 3.2, I write comments:
>
> 1, Your file-based naming scheme isn't compatible with apache
> MultiView function that David Rees and Takashi Okamoto says.
>
> Now apache naming scheme becomes popular in Japan. But almost nobody
> uses your naming scheme. It is unhappy that we must change all
> filename that is written by apache naming scheme.
>
> At the least, compatible option is needed.
I don't think that my intent was to be compatible with Apache.
My first goal was to be compatible with Java localization.
The context in which I am using Jakarta is as an 'embedded' servlet
container inside of a Java application.
>
> 2, In your file-based approach & docbase-approach, we can't specify
> charset of HTML files. It is desiable that charset will be supported
> in consideration of Content-Type header.
That is certainly an improvement that can be done.
>
> 3, I think your file-based lookup don't work for JSP files by my
> experience (true?). But I hope you will support same localization for
> JSP files.
I believe it does.
Since you appear to be very experienced in areas of localization, it
would be very welcome if you proceeded to enhance the work that I
started.
Thanks for your comments.
Arieh
>
> Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories
--
Arieh Markel Sun Microsystems Inc.
Network Storage 500 Eldorado Blvd. MS UBRM11-194
e-mail: [EMAIL PROTECTED] Broomfield, CO 80021
Pray for snow !!!! Phone: (303) 272-8547 x78547
(e-mail me with subject SEND PUBLIC KEY to get public key)
