Hi,
unfortunately Display Tag doesn't take care of the encoding of the request/response for encoding of paging and ordering links.
Although the response/request are set to UTF-8, we discover that Display Tag doesn't use the UTF-8 encoding for the links, but CP-1252. This leads to errors when we used as dynamically filled parameter for the original calling URI which consists of non ASCII characters.
For example the originial URI holds the parameter:
...City=M%C3%BCnchen
but the Display Tag generated link only holds:
...City=M%FCnchen
Which results in an error when we try to use UTF-8 encoding during the next request processing.
Have i missed something, or is it a real Bug?
regards, Norbert
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ displaytag-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-user
