In Eelco's first mail he mentioned that he'd expected
<img wicket:id="resetButtonImage" value="buttonFactory:reset:\u53D6\u6D88"/>
to work. And because it didn't he tried several others like new
DefaultButtonImageResource("\u4E4B\u5916")); etc.. Under the hood the
first implicitly calls DefaultButtonImageResource as well. Both don't
work (and still don't) because our parser doesn't detect \uXXXX and
thus doesn't translate it into the appropriate char. \uXXXX is Unicode
specific and thus should depends on <?xml encoding="..."?> the
encoding used (If the file is not utf encoded we should not convert
\uXXXX). Only if the encoding is "utf-8" we should (if at all, but imo
we should not) convert \uXXXX into a char. The 2nd (html specific)
option is &#ddddd;. Every browser knows how to handle it. However the
image created by the button-factory is created by wicket (and not the
browser) and wicket didn't know know about &#ddddd; (and it still
doesn't know about &acct; etc.). new
DefaultButtonImageResource("值之")); now should do.
Juergen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
