[
https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542555
]
Marat Radchenko commented on WICKET-1139:
-----------------------------------------
Hi, Juergen. I do not ask to specify any encoding to be sent to client. And I
do not ask to specify default encoding for parsing of all markup files or for
client output. I just ask to explicitly specify any encoding that you consider
appropriate for Wicket built-in html files. It doesn't have to be UTF-8. It can
have absolutely any value that will allow correct file reading.
I know that this encoding is used for loading only. The point is that we want
to force all html files in our application to explicitly specify encoding
(because platform default may [an will] be inacceptable). And in current
situation we have to duplicate all Wicket htmls with addition of xml prolog.
As additional argument, you cannot be sure that all current and future
encodings that can possibly be set as platform default will correctly load your
html files. So explicit specifying will protect you against possible
environment-specific errors.
> 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.
