With UtfPropertiesFilePropertiesLoader you can use properties with UTF-8
encoding, no XML involved there.
Sven
On 12/11/2012 09:42 AM, Martin Grigorov wrote:
On Tue, Dec 11, 2012 at 8:38 AM, Sven Meier wrote:
Give your file the suffix ".utf8.properties".
In Wicket 6 you h
was just .xml (com.example.MyApp.xml)
>
>
> Sven
>
>
> On 12/11/2012 08:33 AM, oliver.stef wrote:
>
>> Hi all,
>>
>> When i'm saving my properties file in 'UTF-8' coding, i can't see the
>> correct chars (image 1).
>> but when i'm
Yep!
On Tue, Dec 11, 2012 at 9:37 AM, Sven Meier wrote:
> IIRC you have to run on Java 6 for that feature.
>
> Sven
>
>
> On 12/11/2012 09:36 AM, Ernesto Reinaldo Barreiro wrote:
>
>> Hi,
>>
>> I think to be able to use UTF-8 you have to encode the prop
IIRC you have to run on Java 6 for that feature.
Sven
On 12/11/2012 09:36 AM, Ernesto Reinaldo Barreiro wrote:
Hi,
I think to be able to use UTF-8 you have to encode the properties files as
XML properties files (otherwise you have to escape characters that cannot
be directly represented on
Hi,
I think to be able to use UTF-8 you have to encode the properties files as
XML properties files (otherwise you have to escape characters that cannot
be directly represented on ISO 8859-1).
On Tue, Dec 11, 2012 at 8:33 AM, oliver.stef wrote:
> Hi all,
>
> When i'm saving my p
Give your file the suffix ".utf8.properties".
Sven
On 12/11/2012 08:33 AM, oliver.stef wrote:
Hi all,
When i'm saving my properties file in 'UTF-8' coding, i can't see the
correct chars (image 1).
but when i'm saving it as displayed if i'm as 'IS
I guess you can use language files in xml format instead of properties
On Tue, Dec 11, 2012 at 2:33 PM, oliver.stef wrote:
> Hi all,
>
> When i'm saving my properties file in 'UTF-8' coding, i can't see the
> correct chars (image 1).
> but when i'
Nitpicking a bit: .properties files need to be in ISO 8859-1 encoding not
in default.
Attila
2011/11/2 Wilhelmsen Tor Iver
> > It's a known fact for me aswell now :)
>
> Note that even though properties files need to be in the "default"
> encoding, you can use non-iso-latin characters by way of
> It's a known fact for me aswell now :)
Note that even though properties files need to be in the "default" encoding,
you can use non-iso-latin characters by way of the \u syntax, though a bit
more cumbersome than "raw" Unicode characters.
- Tor Iver
---
n Wed, Nov 2, 2011 at 10:54 AM, nino martinez wael
> wrote:
> > Hi
> >
> > I've UTF-8 encoded all my files, setup tomcat to support utf-8 and
> > everything.. But something did'nt work because my chars where all
> garble..
> >
> > Then I tried a
On Wed, Nov 2, 2011 at 10:54 AM, nino martinez wael
wrote:
> Hi
>
> I've UTF-8 encoded all my files, setup tomcat to support utf-8 and
> everything.. But something did'nt work because my chars where all garble..
>
> Then I tried all sorts of stuff, only to discover th
Hi
I've UTF-8 encoded all my files, setup tomcat to support utf-8 and
everything.. But something did'nt work because my chars where all garble..
Then I tried all sorts of stuff, only to discover that nothing worked.
Finally I figured out that I was using .property files and not
.pr
pache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907047.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: us
t; --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907047.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail:
Oh, And I've also tried putting
org.springframework.web.filter.CharacterEncodingFilter as the first filter
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907047.html
Sent from the Users forum mailing list archive at Nabbl
ngFilter
encoding
UTF-8
forceEncoding
true
You have to configure a filter (write one or reuse existing ones like
http://static.springsource.org/spring/docs/3.1.0.RC1/javadoc-api/org/springframework/web/filter/CharacterEncodingFilter.html)
to call request.setCharacterEncoding("UTF-8") before wicket gets the
request. This is not n
Sorry. Forgot to say wicket version 1.4.18
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
set in init
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp
Hi,
i have the following situation.
In browser i type my url (localhost:8080/param/Küche).
In page-parameters param is Küche (fine).
On Page there are two links
public MyPage(final PageParameters parameters) {
super(parameters);
StatelessForm form = new StatelessForm("form");
looking at the code its using the Application class logger...strange,
i will fix in the branch.
private static final Logger log = LoggerFactory.getLogger(Application.class);
-igor
On Fri, Feb 5, 2010 at 12:02 AM, smallufo wrote:
> 2010/2/5 Igor Vaynberg
>
>> disable it in your logging configur
2010/2/5 Igor Vaynberg
> disable it in your logging configuration
>
> -igor
>
>
I tried a lot of configurations , but http.WicketURLDecoder's warning still
pops up...
log4j.rootLogger=INFO, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.
disable it in your logging configuration
-igor
On Thu, Feb 4, 2010 at 8:13 PM, smallufo wrote:
> After upgrading to 1.4.6 , it always pops up this warning :
>
> WARN http.WicketURLDecoder - No current Application found - defaulting
> encoding to UTF-8
>
> It is ok in 1.4.5
After upgrading to 1.4.6 , it always pops up this warning :
WARN http.WicketURLDecoder - No current Application found - defaulting
encoding to UTF-8
It is ok in 1.4.5 , but I don't know why it has such warning in 1.4.6 .
How to get rid of it ?
Thanks ...
e:
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
and both, static texts from .HTML, translated texts from .XML are show O.K.,
but data posted from a form are not.
---
Hmm.. can't you fix this with encoding settings?
getMarkupSettings().setDefaultMarkupEncoding(WebPageConstants.ISO_8859_1);
Or something?
I would assume a modified version wicket-ajax can be just accomplished
by creating a new one in same package. However, if there is no setup
for such thing
Hi all,
I'm probably facing the same problem as described here:
http://mail-archives.apache.org/mod_mbox/wicket-users/200804.mbox/%3cdf3d7452-0ac0-4cf7-8164-87e9371d8...@signicat.com%3e
I use Maven to build my applications, so I have a beginner's qustion:
how to reorganize a project to work with
Allright, I fed the daemon ;)
I created a new issue in
https://issues.apache.org/jira/browse/WICKET-2451 and I found that
WICKET-1443 is similar but already closed since 1 year.
2009/9/2 Eelco Hillenius :
>> The result is in the attachment file (sorry but I don't have a quick
>> way to do a patch
> The result is in the attachment file (sorry but I don't have a quick
> way to do a patch file against SVN trunk at the moment).
The mailing list daemon thinks attachments are delicious. The way to
submit patches is to attach it to a JIRA issue. Did anyone already
open a feature request for this?
I had a look at T5 and Spring code :
- Spring checks if the JDK supports UTF-8 files, and if it does not
support it acts like T4 and parses the properties file. The
implementation is much more compact than in T4.
- T5 does a native2ascii conversion of the properties files on the fly.
So I
On Tue, Sep 1, 2009 at 3:39 PM, Johan Compagner wrote:
> Everybody should stop using any other encoding then UTF-8
> Common people we should start this change from happening now :)
>
> Drop all charsets and all over the world. ban them everywhere, it should be
> illegal to use
>
> But I'm sure you can write a properties implementation that reads from
> UTF-8 in a few hours max, especially now that you have an example in
> Tapestry's code. Patch is welcome :-)
>
> Eelco
>
>
FYI, spring supports UTF-8 property files as well:
see org.springframework.context.support.ReloadableResourceBundleMessageSource
Maarten
On Wed, Sep 2, 2009 at 2:37 AM, Eelco Hillenius
wrote:
> >> But I'm sure you can write a properties implementation that reads from
>
>> But I'm sure you can write a properties implementation that reads from
>> UTF-8 in a few hours max, especially now that you have an example in
>> Tapestry's code. Patch is welcome :-)
>
> Why not just "borrow" the code from Tapestry? It's Apach
On Tue, Sep 1, 2009 at 12:00 PM, Eelco
Hillenius wrote:
> But I'm sure you can write a properties implementation that reads from
> UTF-8 in a few hours max, especially now that you have an example in
> Tapestry's code. Patch is welcome :-)
>
Why not just "borrow&quo
On Tue, Sep 1, 2009 at 1:19 AM, Olivier
Bourgeois wrote:
> That's exactly what I said : I had to use XML properties files to have
> UTF-8 localized properties.
>
> You can't use simple properties format because Java can't handle
> natively anything else than ISO. We u
Yeah, one charset to rule them all !
:-)
2009/9/1 Johan Compagner :
> Everybody should stop using any other encoding then UTF-8
> Common people we should start this change from happening now :)
>
> Drop all charsets and all over the world. ban them everywhere, it should be
> ille
Everybody should stop using any other encoding then UTF-8
Common people we should start this change from happening now :)
Drop all charsets and all over the world. ban them everywhere, it should be
illegal to use them, if you do still use them you should be thrown in to
prison for at least 5
We usually do multilanguage sites, so we always try to keep the web
application in a full UTF-8 cycle. With Wicket we were fine doing the
following:
as mentioned above:
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
getRequestCycleSettings().setResponseRequestEncoding(&quo
The people at my office handling translations are using a simple UTF-8
capable editor (that can be Eclipse for instance) and there is no need
to escape anything when you use UTF-8 in the properties files. That's
much more comfortable when working with arabic or chinese, because
people can
Man, use the native2ascii built-in JDK tool.
It's very simple, transforms your messages into ASCII escaped.
Regards,
Wojtek
Olivier Bourgeois pisze:
That's exactly what I said : I had to use XML properties files to have
UTF-8 localized properties.
You can't use simple pr
In case you use Eclipse, there is an utility called Properties Editor
http://propedit.sourceforge.jp/index_en.html
Vit
Olivier Bourgeois wrote:
That's exactly what I said : I had to use XML properties files to have
UTF-8 localized properties.
You can't use simple properties form
That's exactly what I said : I had to use XML properties files to have
UTF-8 localized properties.
You can't use simple properties format because Java can't handle
natively anything else than ISO. We use also Tapestry here, and you
can use UTF-8 properties files (thanks to the
> Erm
> http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/
Which says Wicket 2.0 (yes, it's that old), but it was also one of the
first things backported. Loading is automatic, and .xml takes
precedence over .properties.
Eelco
---
> Because Wicket uses Java Properties objects and it can't handle UTF-8.
> In Tapestry they made a wapper around Java Properties so that you can
> use the good old properties format (ie "key=value") with UTF8 encoding
> and IMO it's a nice feature m
I am using Wicket 1.4 with UTF-8 pages and properties, and I added in
my Application :
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
That's enough. For the localization properti
Excellent.
I saw a bunch of emails floating around saying that you'd have to also
1) Edit connectors in server.xml and add URIEncoding="UTF-8"
2) Call request.setCharacterEncoding("UTF-8") (at the very beginning of the
cycle)
Are those also necessary?
I'm assumi
Add this to init() method in your Application class:
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
This should be enough.
--
Regards,
Tomasz Dziurko
Is there a documented process for enabling UTF-8 in wicket?
D/
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
files within Wicket HTML files using VelocityPanels and no
> matter how I encode the vm file (UTF-8 encoded or unicode escaped), I am not
> getting the proper characters displayed when the page is served. I have set
> the default encoding on the MarkupSettings and I have also created a
>
Hello,
I cannot seem to get VelocityPanel to output my files properly. I am
embedding vm files within Wicket HTML files using VelocityPanels and no
matter how I encode the vm file (UTF-8 encoded or unicode escaped), I am not
getting the proper characters displayed when the page is served. I
Ok, sorry for the noise.
I just needed to add the [NE] rule to my RewriteRule in my apache
config and that did the trick.
Cheers,
=David
On Jun 9, 2009, at 2:06 PM, David Leangen wrote:
Ok, this seems to have something to do with proxying, not Wicket.
When I enter "日本語" into the form
Ok, this seems to have something to do with proxying, not Wicket.
When I enter "日本語" into the form, Wicket correctly sends back the
reply:
HTTP/1.1 302
Location: http://www.example.com/path?q=%E6%97%A5%E6%9C%AC%E8%AA%9E
To which my browser redirects with:
GET /path/?q=%25E6%2597%25A5%25E6
Hello!
I am having a problem with the double-encoding of Japanese characters
that are in the query string. For example:
http://www.example.com/path/q=日本語
If I write the raw value directly in the URL string in my browser,
there are no problems. If I write the URL encoded value directly i
We had similar problems and by changing
to
in the /conf/server.xml fixed the problem.
Tom
Johan Compagner wrote:
> Did you configure tomcat correctly for utf 8?
> Search this list for the right settings
>
> On 30/01/2009, Philipp Daumke wrote:
>> Hi all,
>>
Hi Jonas, hi Johann,
grrh, I forgot to set URIEncoding="UTF-8". Now it works, thank you for
your help.
All the best
Philipp
Hi Philipp,
yes, thats correct. We had similar problems and fixed it that way, but maybe
something else is still not set to UTF-8.
I assume you have confi
Hi Philipp,
yes, thats correct. We had similar problems and fixed it that way, but maybe
something else is still not set to UTF-8.
I assume you have configured your tomcat connector using
URIEncoding="UTF-8" (I think that is what Johan is referring to?).
Have you tried adding a meta t
n#init correctly, you meant to do it like this,
> right(?):
>
> public class MyApp extends WebApplication {
> public void init()
> {
> getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
> getMarkupSettings().setDefaultMar
tings().setResponseRequestEncoding("UTF-8");
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
}
public Class getHomePage() {
return Index.class;
}
}
Still, it seems to convert my code from latin1 to utf8, even though I
enter utf8-text.
Thanks for further he
Did you configure tomcat correctly for utf 8?
Search this list for the right settings
On 30/01/2009, Philipp Daumke wrote:
> Hi all,
>
> when I enter German umlauts (e.g. "äöü") in a wicket text field it's
> converted to "äöü". Everything seems to be in
Hi,
have you tried setting
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
in your Application#init
If you don't set the default markup encoding explicitly, the default
for it is the &#
is actually already converted to 'äöü' when I add a
breakpoint at the onSubmit method of my form (so right when I get the
input of the text field from my model).
My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page,
my firefox says UTF-8. What I think is that Wicket or
Hi Mathias,
'äöü' is actually already converted to 'äöü' when I add a breakpoint
at the onSubmit method of my form (so right when I get the input of the
text field from my model).
My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my
firefox says UT
Do you save it to a database and then display the text? How do you present
it?
--
View this message in context:
http://www.nabble.com/UTF-8-bug-in-wicket--Or-in-Tomcat--tp21738467p21738754.html
Sent from the Wicket - User mailing list archive at Nabble.com
Hi all,
when I enter German umlauts (e.g. "äöü") in a wicket text field it's
converted to "äöü". Everything seems to be in "UTF-8". I already
tried to apply a filter as described in
http://wiki.apache.org/tomcat/Tomcat/UTF-8 without success. Any id
Hello,
I'm trying to use UTF-8 as the default encoding in a web application using
Wicket and Spring. Although everything seems to be working properly, I'm
facing a problem when dealing with a page mounted using the
QueryStringUrlCodingStrategy.
The application configuration
* The
all a error 42
thx all.
--
View this message in context:
http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19308386.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
an327.blogspot.com/2006/05/utf-8-encoding-fix-tomcat-jsp-etc.html
>
> Just use the EncodingFilter and I bet my [EMAIL PROTECTED]@#$ it will work :-)
>
> Am 29.08.2008 um 11:04 schrieb Ray trace:
>
>>
>> i dont think u actually read my post but thx anyways.
>
It's a standard tomcat problem that everybody sooner or later
encounters...
This will work for you:
http://cagan327.blogspot.com/2006/05/utf-8-encoding-fix-tomcat-jsp-etc.html
Just use the EncodingFilter and I bet my [EMAIL PROTECTED]@#$ it will work :-)
Am 29.08.2008 um 11:04 schrie
i dont think u actually read my post but thx anyways.
as stated in the initial post i tried that allready.
Emanuele Gesuato-2 wrote:
>
> Ray trace wrote:
>> ino its wierd
>>
>> yes my browser says utf-8 .
>> the mysql database is in utf-8.
>> hiberna
Ray trace wrote:
ino its wierd
yes my browser says utf-8 .
the mysql database is in utf-8.
hibernate is utf-8.
basically all is utf-8 except the incoming post data.arg.
true
UTF-8
database schema is created with utf-8 ...so that hibernate tools generate
the correct tables.
all
ino its wierd
yes my browser says utf-8 .
the mysql database is in utf-8.
hibernate is utf-8.
basically all is utf-8 except the incoming post data.arg.
true
UTF-8
database schema is created with utf-8 ...so that hibernate tools generate
the correct tables.
all though i dont think
info/properties/encoding??
At our place it works fine, ofcourse we also configured all databases
and databse connections to use also utf8
Johan
On 8/29/08, Ray trace <[EMAIL PROTECTED]> wrote:
>
>
> i tried that ...however...then u cant use the ajax since it only uses xml
>
i tried that ...however...then u cant use the ajax since it only uses xml
utf-8 posting
so that is not an option heresince i need special chars ...and allready
have alot of ajax.
Stefan Lindner wrote:
>
> I had the same problem some week ago but got no answer on this list. Now I
4M3. Wicket seems to ignore the
XHTML header completely.
Stefan
-Ursprüngliche Nachricht-
Von: Ray trace [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 29. August 2008 09:57
An: users@wicket.apache.org
Betreff: Wicket,tomcat and UTF-8
Hi i have a problem with tomcat and wicket and UTF
Hi i have a problem with tomcat and wicket and UTF-8
im developing my first large wicket app.
no matter what i do wicket dont seem to use the utf-8 settings i specified.
the incoming request converts the incoming UTF-8 to iso-8859-1 (the
default).
only tried post since that what wicket uses
s I found.
I'm using Notepad++ (on Windows) which has the choices "UTF-8" and
"UTF-8 without BOM," which to a newbie like me makes it appear that
having the BOM is the default.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
if your editor prefixes your templates with a BOM(1), Wicket is not able
to recognize the encoding in your xml declaration, see
org.apache.wicket.util.io.XmlReader#xmlDecl .
You might want to create a JIRA request, that Wicket should skip a
leading BOM in the encoding detection.
Regard
Not sure what you mean by BOM (Bill Of Materials?)
However I have seen something odd with documents there were generated
on a Mac with little "?" in various places.
- Brill Pappin
On 25-Jun-08, at 2:22 PM, Miguel Paraz wrote:
On Wed, Jun 25, 2008 at 9:51 PM, Brill Pappin <[EMAIL PROTECTED]
On Wed, Jun 25, 2008 at 9:51 PM, Brill Pappin <[EMAIL PROTECTED]> wrote:
> I think it might be your browser that is not displaying the unicode chars.
> That you see the odd symbols at all means that the made it to the client
> side.
>
> Are you on a Mac?
Hi! Thanks for the reply.
No, I'm on Firef
I think it might be your browser that is not displaying the unicode
chars.
That you see the odd symbols at all means that the made it to the
client side.
Are you on a Mac?
- Brill Pappin
On 25-Jun-08, at 9:37 AM, Miguel Paraz wrote:
Hi,
I found out - through a lot of trial and error - tha
Hi,
I found out - through a lot of trial and error - that if your .html
file has a Byte Order Mark, the at the top
of the document is ignored.
The document is treated as something else - I'm not sure what.
The effect is that the special output characters become the
unknown characters.
Is this a
Hi
After upgrading from wicket 1.2.6 to 1.3 we got a problem with opening PDF
files inline in a browser window.
At least for some browser versions and/or PDF readers, it now opens the PDF
file in a separate window instead of inline.
The difference is that in Wicket 1.3 ";charset=UTF-
>
> I have a problem with XML page incodings. We use wicket for applications
> on our cisco ip phones. The firmware http client on these phones does not
> understand utf-8 xml. So we need to provide iso-8859-1 encoded xml
> responses so that the output is rendered correct
I have a problem with XML page incodings. We use wicket for applications on
our cisco ip phones. The firmware http client on these phones does not
understand utf-8 xml. So we need to provide iso-8859-1 encoded xml responses
so that the output is rendered correctly.
We tried setting the correct
hi tom,
Wicket reads this page, and re-encodes it as UTF-8. So the output is no
longer displayed correctly on our phones. Is there some possibility to have
the output rendered as ISO-8859-1 ?
on intializing your application try setting
getMarkupSettings().setDefaultMarkupEncoding( "ISO
Hi,
I have a problem with XML page incodings. We use wicket for applications on
our cisco ip phones. The firmware http client on these phones does not
understand utf-8 xml. So we need to provide iso-8859-1 encoded xml responses
so that the output is rendered correctly.
We tried setting the
Thank you in advance Matej, you're right - we had incorrect Page encoding.
After a few hours of debugging and testing I found, that the one page (which
used DatePicker) had incorrect
encoding - ISO-8859-2 and not UTF-8. All other pages were good.
I didn't found the reason yet ( why th
Well, I guess we kind of expect the page to be utf-8 encoded, as that
is most common case. Is there any special reason why you can't send
your page as utf-8? That way the javascript would be encoded correctly
(it would match the page).
-Matej
On 8/2/07, Stefan Simik <[EMAIL PROTECTED
Hi,
I search old discussion, but I cannot find answer.
We use a DatePicker component from wicket.extensions.
This component has many *.js files for localization (we use Slovak locale ->
calendar-sk-utf8.js )
Problem is, that these files are written using UTF-8 encoding.
Header contribut
89 matches
Mail list logo
