Mark, I see your point related to file encoding
changes working on select OS/JVM combinations, why is
probably why setting LANG=en_US.UTF-8 in catalina.sh
does the trick on Unix. There's got to be some
workaround for Windows.
My aim is to force Tomcat to use UTF-8. We have a EAR
that is deployed on Tomcat, and setting the file
encoding to UTF-8 would help satisfy i18n requirements
for the product. Otherwise for e.g. japanese usernames
would be seen as ???.  

Thanks,
Sriram

--- Mark Thomas <[EMAIL PROTECTED]> wrote:

> Sriram Subramanian wrote:
> > Hi, 
> > 
> > I am installing Tomcat 5.5.9 as a windows service
> > using the service.bat script. I need to set the
> jvm
> > file encoding to UTF-8, which I did using the
> > following syntax -
> > =======
> > "%EXECUTABLE%" //IS//%SERVICE_NAME% --JavaHome
> > %JAVA_HOME% --StartPath %CATALINA_HOME% --Startup
> auto
> > --JvmOptions -Dfile.encoding=UTF-8 <more stuff>
> 
> file.encoding is intended to be read only. That it
> is read/write on
> some JVM/OS combinations is a "feature" that cannot
> be relied upon to
> work in all cases.
> 
> What are you trying to do? Depending on your aims
> you might have
> better luck with some/all of the following:
> URIEncoding of the connector
> fileEncoding of the default servlet
> 
> Mark
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to