On 9/17/01 12:25 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> On 9/17/01 12:16 PM, "Gareth Coltman" <[EMAIL PROTECTED]>
> wrote:
>
> The encoding specified in the org.apache.turbine.util.parser.BaseValueParser
> is "US-ASCII". We could probably pick better default encoding which might be
> a little more forgiving.
In 2.x there is no decent way for a character encoding to flow through the
system so that each tool use it. In 3.x we can pick off the locale and than
use the MimeTypeService to map the locale to the most appropriate character
encoding than make sure that this character encoding is used in all the
appropriate places.
I'm taking a quick peek at the RunData service and I believe that we can
control the parameters used in the construction of an object. The
BaseValueParser constructor class takes a parameter for the character
encoding so maybe we could quickly make the RunDataService construct a
ParameterParser with an encoding. This won't flow through the rest of the
system but will work for anything that the RunDataService constructs. I'll
give it a try and let you know.
If you want to just change the hardcoded "US-ASCII" value in BaseValueParser
and try your app I'd be interested in the results. Would be a work around
for people having problems like yourself.
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
