[
https://issues.apache.org/jira/browse/TRINIDAD-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735079#action_12735079
]
Cedric Durmont commented on TRINIDAD-1505:
------------------------------------------
Sorry to bring bad news, but I still happen to have the problem.
I ran the patch proposed on issue 1430 against the 1.2.11 source tree and
compiled my libs.
My setup is still the same as above, the only difference is that I can't get
the thing working with 1.2.10 anymore (so it's probably just me forgetting an
obvious thing, but who knows)
Using a http proxy I could see what's happening :
value entered in the tr:inputNumber field :
250,00 €
(the value is a Double(250) the formatting is correctly done by tr:formatNumber)
value returned by the browser when submitting :
250%2C00+%E2%82%AC
%2C is the comma, the "+" is for the space, and € in UTF-8 is 0x20AC, which
becomes %E2%82%AC. Everything is as expected
And in Tomcat's response :
250,00 €
As you can see the %E2%82%AC (1 utf-8 char) is interpreted as 3 single-byte
chars. The second one (%82) is replaced by a 2-bytes value :"‚" (notice the
comma).
Do anyone has any idea of what the problem could be ? (Yes I'm starting to be
desperate with this issue). Is this another encoding issue in Trinidad or is it
just me ?
(note that I have run a text search on my entire tomcat folder with my app
deployed, and I am sure there is not a single iso8859-1 reference in it)
> Encoding on IE
> --------------
>
> Key: TRINIDAD-1505
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1505
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.2.11-core
> Environment: Apache Tomcat 6.0.18
> Sun Win32 JDK 1.6.14u
> Reporter: João Rui Barradas Peixoto
> Assignee: Matthias Weßendorf
>
> On IE (my application uses PPR) when you try to insert some characters
> (using simple and multiple lines <tr:inputtext> ) different from English
> encoding you will get those characters incorrectly shown .
> I have returned to version 1.2.10 from version 1.2.11 and it have solved my
> problem.
> This problem doesn't occurs on Firefox.
> Any additional information help you need let me know please.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
