[DOCU-51] Encoding issues on documentation page. Created: 12/Jun/08 Updated: 03/Nov/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Philippe Marschall | Assignee: | Magnolia International |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Several documentation pages have encoding issues, they are ISO-8859-1 but reported as UTF-8 For example http://documentation.magnolia.info/modules/dms/managingdocs.html |
| Comments |
| Comment by Magnolia International [ 12/Jun/08 ] |
|
Thanks! I had noticed this before but didn't really know what was going on, especially since this is only happening on the public instance. Now I'm curious to see how/where you see they were ISO-8859-1 ? Http headers seem to confirm they (should) be utf-8 ? |
| Comment by Philippe Marschall [ 13/Jun/08 ] |
|
Seen too many encoding issues You can check this by forcing Firefox to use ISO-8859-1: View -> Character Encoding -> Western (ISO-8859-1) |
| Comment by Ralf Hirning [ 13/Jun/08 ] |
|
We see this effect in an other project too. If you disable caching everything is fine. So it seems that this is related to cache |
| Comment by Magnolia International [ 13/Jun/08 ] |
|
Ralf : yes, that's what I suspected, given that it only happens on the author instance. |
| Comment by Philippe Marschall [ 13/Jun/08 ] |
|
As far as I can see the cache is byte-oriented, which is good. The bug can either happen when writing to the cache or when reading from the cache. The first step is to check the encoding of the cache file on the disk. It should be utf-8 which means « should be encoded using two bytes. If that is the case then the bug happens when reading from the cache, else when writing to the cache. |
| Comment by Magnolia International [ 13/Jun/08 ] |
|
yeah i just debunked it - the character encoding at the response doesn't seem to be set properly, and that's used when getting a writer on the caching response wrapper... |
| Comment by Magnolia International [ 13/Jun/08 ] |
|
thanks for reporting |