It is because that is only a intermediate presentation of the page's
content:
- it is read from filesystem by whatever encoding is configured
- it is pre-processed and written internally as UTF-8 (hard-coded) into
a byte array or such
- it is read again internally as System encoding (not hardcoded -> bug)
again.
It still would be great if this could be fixed :-)
Agreed, but I'm not convinced that hard coding UTF8 is the answer :)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
