[
https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542544
]
Juergen Donnerstag commented on WICKET-1139:
--------------------------------------------
the encoding given in the markup file is always only used for loading the data
and will never be forwarded to the client browser. We use Settings (and
configureResponse) to determine what goes into the response and that setting is
applied to all responses (except you define different in configureResponse).
In my opinion this is not a valid request. Our internal markup files do not
contain any none-ascii characters. If a user wants to supersede with an
extended subclass and add <?xml ..> to the his own markup than that is
perfectly fine. As mentioned above we are using it for loading only and it is
perfectly fine to mix and match different encoding. No <?xml ..> means that the
JVM / OS default will be used.
> 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.
