Nino Saturnino Martinez Vazquez Wael wrote:
I think he could just take a look at the Strings class(1.3), and make a
workaround .. That should'nt be that critical...
into commons-lang, there is StringEscapeUtils.escapeHtml(String str)
from javadoc :
Escapes the characters in a String usin
Sorry if I am too blund, for what do you need the character entities? Is
serving the characters in UTF-8 encoding not sufficient?
Regards,
Erik.
Manuel Barzi wrote:
I have a lot of literal files (properties) with some special
characters
(spanish accents) that I would desire to convert to H
thanks for the notice, frank.
applied the change.
gerolf
On 10/4/07, Frank Bille <[EMAIL PROTECTED]> wrote:
>
> FYI, we also have our own replaceAll, which doesn't fire up the regex
> engine.
>
> Strings.replaceAll[1]
>
> Frank
>
> [1]:
>
> http://people.apache.org/~tobrien/wicket/apidocs/org/apa
I think he could just take a look at the Strings class(1.3), and make a
workaround .. That should'nt be that critical...
Another option are to upgrade to 1.3 ... But it's still beta and may
take a day or two depending on complicity of the application(that how
long it took us upgrading a medium
> It's a nice idea, Eelco. So, should we conclude this thread confirming that
> this conversion is not already implemented for Wicket 1.2.6? I mean, do we
> need a patch (correction) or do we need an implementation (new
> implementation)?
Depends on what you want. Those XML files don't convert to
It's a nice idea, Eelco. So, should we conclude this thread confirming that
this conversion is not already implemented for Wicket 1.2.6? I mean, do we
need a patch (correction) or do we need an implementation (new
implementation)?
Eelco Hillenius wrote:
>
>> I think it may be e nice proposal t
> I think it may be e nice proposal to Wicket to allow somekind of set-able
> Character2HTMLEntity converter on rendering in the application side, some
> like:
>
> customWicketApp.setCharacter2HTMLEntityConversionForLiteralResourceOnRender(true);
>
> What do you think?
>
> I am working on Wicket 1.
Any devs having a comment on this?
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
It should be working no matter what...
This fragment
add(new Label("mailingListTitle","àáèéíòóú"));
Yields this fragment when rendered:
wicket:id="mailingListTitle">àáèéíòóú
However this is on wi
No, I havent created my own components. When I mentioned
customStringResourceModel I meant a whatever instance of
StringResourceModel, but not a custom implementation of it.
So, from your last message I understand that Wicket 1.2.6 is not confirmed
to be working with this character2HTMLEntity con
It should be working no matter what...
This fragment
add(new Label("mailingListTitle","àáèéíòóú"));
Yields this fragment when rendered:
àáèéíòóú
However this is on wicket 1.3 beta 3.. I dont have a running 1.26 at my hands
right now... I think every component that writes strings to the outpu
Anyway, Nino, there are some fragments of code in which we require to use the
literal (in a list, or map, or whatever), recover it, and then add it to
some rendering point (like a table, list, etc.) where there might no be so
simple as label.
On those code fragments, of course, we need to use the
Hmmm... Nino, I found this suspicious code @ labels creation, for example:
linkTab1.add(new Label("ConsultaDadesTramesaPanel-tab-1", new
StringResourceModel("ConsultaDadesTramesaPanel-lit-45", this,
null).getString()));
I guess that "getString()" may be misleading the FW to apply the
conversion.
Hmmm, strange.. Should be working then.
How do you create your labels? You dont by any chance call
setEscapeModelStrings(false) on your labels, some where?
could you provide an example?
regards Nino
Manuel Barzi wrote:
Sorry, I tried to mean "It doesN'T seem to be working in my case."
Man
Sorry, I tried to mean "It doesN'T seem to be working in my case."
Manuel Barzi wrote:
>
> It does seem to be working in my case.
>
> I use Labels with literals that in some cases have some of the following
> accents: àáèéíòóú. But when I do a "View source..." (HTML already
> rendered), I can
It does seem to be working in my case.
I use Labels with literals that in some cases have some of the following
accents: àáèéíòóú. But when I do a "View source..." (HTML already rendered),
I can see the same literals without character2HTMLEntity conversion.
So, my question is: should I specify
Yes it automatically interprets a string and replaces special characters
with html equallents.
But how did you pickup that it does not do that? How are you displaying
your strings ? Are you using labels or?
-Nino
Manuel Barzi wrote:
So, what's the conclusion? Does Wicket 1.2.6 support this
So, what's the conclusion? Does Wicket 1.2.6 support this automatic
character2HTMLEntity conversion or not?
Nino.Martinez wrote:
>
> Sorry if im totally wrong on this but, you guys talking about xml and
> stuff... Arent wicket doing just that automatically... I mean in denmark
> our Ø Å Æ are
FYI, we also have our own replaceAll, which doesn't fire up the regex
engine.
Strings.replaceAll[1]
Frank
[1]:
http://people.apache.org/~tobrien/wicket/apidocs/org/apache/wicket/util/string/Strings.html#replaceAll(java.lang.CharSequence,%20java.lang.CharSequence,%20java.lang.CharSequence)
On 1
18 matches
Mail list logo
