|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
windows xp, tomcat 5.5 (started with -Dfile.encoding=UTF-8 option, this way myfaces doesn't convert all non-ascii characters to html entities), myfaces 1.1.3
|
|
|
Clay reads html files assuming ascii encoding. This way it's impossible to have characters other than ascii in templates. They do not display correctly. As indicated on the user mailing list a Reader object should be used for reading templates instead of InputStream. I wrote more about this on shale user mailing list.
We probably need:
1. app wide config option for setting encoding clay should use for reading templates in. Clay would default to this setting unless maybe
2. some per file encoding config option was set (something similar to @page pageEncoding directive for jsps)
I marked it as major as this should be corrected if one wants to develop localized applications with non-ascii characters in html templates.
As noted by Craig this probably also applies to xml templates, which I haven't tried myself.
|
|
Description
|
Clay reads html files assuming ascii encoding. This way it's impossible to have characters other than ascii in templates. They do not display correctly. As indicated on the user mailing list a Reader object should be used for reading templates instead of InputStream. I wrote more about this on shale user mailing list.
We probably need:
1. app wide config option for setting encoding clay should use for reading templates in. Clay would default to this setting unless maybe
2. some per file encoding config option was set (something similar to @page pageEncoding directive for jsps)
I marked it as major as this should be corrected if one wants to develop localized applications with non-ascii characters in html templates.
As noted by Craig this probably also applies to xml templates, which I haven't tried myself. |
Show » |
|
Bug
Resolved
Major
Clay doesn't consider file's encoding when loading/parsing html templates from hdd
