[
https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542488
]
Marat Radchenko commented on WICKET-1139:
-----------------------------------------
Your files are ASCII-only and so they do not care a lot about exact encoding.
You can specify UTF-8 or ISO 8859-1 (or some other because all encodings (as
far as I know) have same byte numbers for ASCII symbols).
Affected files (list may be incomplete):
org/apache/wicket/markup/html/panel/FeedbackPanel.html
org/apache/wicket/markup/html/panel/EmptyPanel.html
org/apache/wicket/markup/html/pages/RedirectPage.html
org/apache/wicket/markup/html/pages/PageExpiredErrorPage.html
org/apache/wicket/markup/html/pages/InternalErrorPage.html
org/apache/wicket/markup/html/pages/ExceptionErrorPage.html
org/apache/wicket/markup/html/pages/AccessDeniedPage.html
> 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.
