You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Marat Radchenko (JIRA)" <ji...@apache.org> on 2007/11/09 13:25:51 UTC

[jira] Issue Comment Edited: (WICKET-1139) Wicket html files do not have xml prolog

    [ https://issues.apache.org/jira/browse/WICKET-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541300 ] 

slonopotamus edited comment on WICKET-1139 at 11/9/07 4:24 AM:
------------------------------------------------------------------

Well, I'm not speaking about outputting xml prolog to users. I'm speaking about using it when loading markup files.

Outputting xml prolog to users is handled by stripXmlDeclarationFromOutput in IMarkupSettings.

      was (Author: slonopotamus):
    Well, I'm not speaking about outputting xml prolog to users. I'm speaking about using it when loading markup files.
  
> 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.