Ilkka Priha wrote:
>
> It's great that Michael has detected the problem and even solved it. We've
> been also testing some simple Chinese templates and didn't notice it.
>
> Just for motivation Geir, there's not any other even near as good tool for
> multilingual web application development as Velocity after the problems are
> solved. So it would be cool to have this one already in Velocity 1.1/Turbine
> 2.1. I don't mean to put any pressure, reliability comes always first.
>
> But it would be cool :-)
It would be, wouldn't it. :)
The risk that worries me is that some smart person went to some trouble
to mask the upper byte of the characters. I want to know why.
Michael's detective work is great in running this down - however, this
change is about as core as it gets, and affects every template run
through Velocity, for every user, in every encoding.
How's that for doom and gloom :)
I take this very seriously, and am quite bummed about it - I have to be
at a client this morning, but should get a block of time later today to
really focus and drill down. If I can convince myself thoroughly, in a
way that I can explain to this list so everyone is thorougly convinced,
then we should consider 1.1. Otherwise, I wouldn't be adverse to a
quick 1.2 right after, just so people who want a released 1.1 to take
advantage of the other features can sleep well.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
"still climbing up to the shoulders..."
