[
https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Compagner updated WICKET-1139:
------------------------------------
Fix Version/s: 1.3.0-rc2
can we just add the UTF-8 encoding to all our files?
Are they then saved as UTF-8 as well?
Also if it is panel then we can do it. Because that part is just for loading.
But if it are pages then it is not that easy because then we also have that in
the resulting page as far as i know.
> Wicket html files do not have xml prolog
> ----------------------------------------
>
> Key: WICKET-1139
> URL: https://issues.apache.org/jira/browse/WICKET-1139
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta4
> Environment: n/a
> Reporter: Marat Radchenko
> Fix For: 1.3.0-rc2
>
>
> We want to enforce all our pages to explicitly specify xml prolog in order to
> avoid troubles with encodings (unfortunately we are not ASCII-speaking). We
> want to do that by specifying invalid defaultMarkupEncoding. This way we will
> get exceptions for all htmls that didn't declare encoding. However it is not
> possible at the moment because many wicket built-in html files do not have
> xml prolog.
> Fix is very simple: just add <?xml version="1.0" encoding="UTF-8" ?> to your
> html files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
