incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Holeczek (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (JSPWIKI-7) buggy handling of UTF-8 characters in page name
Date Sun, 11 Sep 2011 00:03:08 GMT

     [ https://issues.apache.org/jira/browse/JSPWIKI-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Florian Holeczek closed JSPWIKI-7.
----------------------------------


> buggy handling of UTF-8 characters in page name
> -----------------------------------------------
>
>                 Key: JSPWIKI-7
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-7
>             Project: JSPWiki
>          Issue Type: Bug
>    Affects Versions: 2.4.104
>         Environment: Solaris 10, Tomcat 5.5
>            Reporter: Thorsten Hirsch
>            Priority: Minor
>
> After upgrading from jspwiki 2.2.x to 2.4.104 pages with german umlaut characters cannot
be found. In jspwiki.properties the encoding is set to UTF-8, my browser also uses UTF-8 encoding
when displaying the jspwiki, and the filename of the page in the filesystem is UTF-8, also.
Here it is:
> pages/Einf%C3%A4rben.txt
> However, the following url does not work:
> http://myserver/wiki/Wiki.jsp?page=Einf%C3%A4rben
> This is what jspwiki displays in the headline: EinfÃRben
> So it seems to get corrupted. Before upgrading to version 2.4.104, there was no such
problem and I was also using UTF-8. Maybe it's also interesting, that when using a different
encoding for the url, the page is found correctly:
> http://myserver/wiki/Wiki.jsp?page=Einf%E4rben
> That's iso8859-1 / Latin1. And in this case, the headline is "resolved" correctly:
> Einfärben
> The encoding in firefox still is UTF-8. So firefox gives a latin1 url to jspwiki.org,
which is transforming it to UTF-8 in order to access the file and display the page in UTF-8
encoding. That's okay, but I really need the utf-8 url to be handled correctly (without transformation).
Is there some way to solve this issue?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message