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 conversion automatically. Then,
if you are not on the same situation, we cannot compare behaviors...

I guess I should create my own Character2HTMLEntityConverter and then
inserted it when retrieving literals? Something like:

linkTab1.add(new Label("tab-1",
Character2HTMLEntityConverter.toHTMLEntity(new
StringResourceModel("literal-1", this, null).getString()))); ?


Nino.Martinez wrote:
> 
> It should be working no matter what...
> 
> This fragment
> 
>  add(new Label("mailingListTitle","àáèéíòóú"));
> 
> Yields this fragment when rendered:
> 
> <div
> wicket:id="mailingListTitle">&#224;&#225;&#232;&#233;&#237;&#242;&#243;&#250;</div>
> 
> 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
> output goes thru encoding, im not sure..
> 
> Might be if you created youre own components from webmarkupcontainer that
> it does not support the automaticly encoding..
> 
> 
> 
> 
> 
> 
> Manuel Barzi wrote:
>> 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
>> customStringResourceModel.getString().
>>
>> Is there any mechanisme to make the "getString()" to return the resource
>> literal string, but converted to HTML entity?
>>
>>
>> Manuel Barzi wrote:
>>   
>>> 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... It shouldnt be used, I will have to correct this attitude
>>> in
>>> the developer who was implementing this :)
>>>
>>> I will try removing those suspicious "getString()"... then I will let
>>> you
>>> know. 
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>> Nino.Martinez wrote:
>>>     
>>>> 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."
>>>>>
>>>>>
>>>>> 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 see the same literals without character2HTMLEntity
>>>>>> conversion.
>>>>>>
>>>>>> So, my question is: should I specify the activation of this
>>>>>> conversion
>>>>>> to
>>>>>> be effective, by means of any set-able API in WicketApplication or
>>>>>> any
>>>>>> other point?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Nino.Martinez wrote:
>>>>>>     
>>>>>>           
>>>>>>> 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 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 converted into html equallents, when passing thru 
>>>>>>>>> labels...? It's done thru the 
>>>>>>>>> org.apache.wicket.util.string.Strings.escapeMarkup , if using it 
>>>>>>>>> manually just remember to use the method taking the use convert to
>>>>>>>>> html 
>>>>>>>>> unicode param..
>>>>>>>>>
>>>>>>>>> regards Nino
>>>>>>>>>
>>>>>>>>> Manuel Barzi wrote:
>>>>>>>>>     
>>>>>>>>>           
>>>>>>>>>                 
>>>>>>>>>> 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.2.6, so I cannot take advantage of your
>>>>>>>>>> xml
>>>>>>>>>> based
>>>>>>>>>> support if it starts from 1.3.
>>>>>>>>>>
>>>>>>>>>> Cheers
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Martijn Dashorst wrote:
>>>>>>>>>>   
>>>>>>>>>>       
>>>>>>>>>>             
>>>>>>>>>>                   
>>>>>>>>>>> I think Wicket supports xml based resource bundles since 1.3? So
>>>>>>>>>>> you
>>>>>>>>>>> can use properly encoded resource bundles directly if you create
>>>>>>>>>>> them
>>>>>>>>>>> in xml format.
>>>>>>>>>>>
>>>>>>>>>>> but this is based on limited memory.
>>>>>>>>>>>
>>>>>>>>>>> Martijn
>>>>>>>>>>>
>>>>>>>>>>> On 10/3/07, ManuelBarzi <[EMAIL PROTECTED]> wrote:
>>>>>>>>>>>     
>>>>>>>>>>>         
>>>>>>>>>>>               
>>>>>>>>>>>                     
>>>>>>>>>>>> Dear Sirs,
>>>>>>>>>>>>
>>>>>>>>>>>> I have a lot of literal files (properties) with some special
>>>>>>>>>>>> characters
>>>>>>>>>>>> (spanish accents) that I would desire to convert to HTML
>>>>>>>>>>>> entities
>>>>>>>>>>>> during
>>>>>>>>>>>> rendering. Is this conversion set-able in Wicket, so to
>>>>>>>>>>>> automatically
>>>>>>>>>>>> let
>>>>>>>>>>>> the framework transform special characters to its HTML entity
>>>>>>>>>>>> representation?
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you ;)
>>>>>>>>>>>>
>>>>>>>>>>>> Manu
>>>>>>>>>>>> --
>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>> http://www.nabble.com/Automatic-character2HTMLEntity-conversion--tf4561020.html#a13016399
>>>>>>>>>>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>       
>>>>>>>>>>>>           
>>>>>>>>>>>>                 
>>>>>>>>>>>>                       
>>>>>>>>>>> -- 
>>>>>>>>>>> Buy Wicket in Action: http://manning.com/dashorst
>>>>>>>>>>> Apache Wicket 1.3.0-beta3 is released
>>>>>>>>>>> Get it now:
>>>>>>>>>>> http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>     
>>>>>>>>>>>         
>>>>>>>>>>>               
>>>>>>>>>>>                     
>>>>>>>>>>   
>>>>>>>>>>       
>>>>>>>>>>             
>>>>>>>>>>                   
>>>>>>>>>     
>>>>>>>>>           
>>>>>>>>>                 
>>>>>>>>   
>>>>>>>>         
>>>>>>>>               
>>>>>>>       
>>>>>>>             
>>>>>>     
>>>>>>           
>>>>>   
>>>>>         
>>>>       
>>>     
>>
>>   
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Automatic-character2HTMLEntity-conversion--tf4561020.html#a13038245
Sent from the Wicket - Dev mailing list archive at Nabble.com.

Reply via email to