[
https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542620
]
Johan Compagner commented on WICKET-1139:
-----------------------------------------
yeah i see your point, we have to fix this and set some encoding in the file so
that the readers uses that.
because platform specific can be any thing and if we save it in 8859 then
another system can be on a completely different encoding and tries to load
those files with something else.
i just have to check if we change the page (ExceptionErrorPage) then we have to
strip that again from the real output because thats by default always utf-8.
But maybe we already do that
> 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.
