[
https://issues.apache.org/jira/browse/WAVE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219275#comment-13219275
]
Ali Lown commented on WAVE-331:
-------------------------------
Browser: Chrome 17/18 (Set to use UTF-8 if unspecified)
Server. I hacked it to always use socket.io (XHR-Multipart) because I found the
frequency of server crashes was significantly less than with Websockets.
The pound signs render correctly for the person who enters it only whilst the
wave isn't loaded from snapshots. For everybody else (and after a page reload)
it simply renders with the unicode 'unsupported' symbol.
Server restarts never help with this encoding issue.
I do agree though that server restarts solve more problems than you would
expect (I set mine to restart with a cron job at 0300 every day to reduce this).
> Non-ascii character encodings are often incorrectly rendered
> ------------------------------------------------------------
>
> Key: WAVE-331
> URL: https://issues.apache.org/jira/browse/WAVE-331
> Project: Wave
> Issue Type: Bug
> Components: Web Client
> Environment: All browsers + operating systems (a nice mix of these
> makes the problem especially obvious)
> Reporter: Ali Lown
> Priority: Minor
> Labels: encoding, utf-8
>
> Characters such as the £ (uk pound sign) or euro sign or reports with (eg.
> german umlaut) etc. are incorrectly rendered in the wave panel (most of the
> time).
> Notably though: often when the wave panel incorrectly loads them they load
> correctly in the search inbox wave snippet text...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
