[
https://issues.apache.org/jira/browse/WICKET-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635251#action_12635251
]
Timo Rantalaiho commented on WICKET-1795:
-----------------------------------------
Martijn, surely you can have non-ASCII characters in the markup file as long as
you ensure that the markup file will be read with the correct encoding (for
example, by setting the "file.encoding" system property to "utf-8"). In many
minor languages, such as Finnish, this makes a lot of sense -- for example,
"instructions of use" in Finnish would be "Käyttöohje" written with a common
encoding that has more than just ASCII (such as UTF-8 or ISO-Latin-1 or
ISO-Latin-9 or cp1252), but "Käyttöohje" in the escaped form. It's
very handy to have the readable form everywhere, these character entity
encodings are a thing of the past century to me :)
Nino, can this issue be closed?
> Make it possible for to encode unicode strings in component
> -----------------------------------------------------------
>
> Key: WICKET-1795
> URL: https://issues.apache.org/jira/browse/WICKET-1795
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.4
> Reporter: Nino Martinez
> Priority: Minor
> Fix For: 1.3.5
>
> Attachments: wicketComponentEncoding.patch
>
> Original Estimate: 0.33h
> Remaining Estimate: 0.33h
>
> It would be very nice to be able to tell a component for example label that
> it had to encode unicode chars into equalent html encoding, I've supplied a
> patch aswell.
> Additionally im not sure what goes for the wicket:message tag? It would be
> very nice to have a switch in markupsettings to decide all encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
