[
https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541299
]
Martijn Dashorst commented on WICKET-1139:
------------------------------------------
I think this has some adverse side effects for the rest of the world that
*dont'* want your behavior. I think it triggers a different rendering engine in
browsers, so we really don't want to force that onto our users.
You can create your own servlet filter that prepends the response with this
declaration if it is missing. No biggy IMO. If you want a more permanent
solution, I suggest creating your own copy of Wicket with the markup files
modified to your liking.
> 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
>
> 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.
