Having done a lot of complex localization with lift I can assure you  
that it works perfectly :-)

What specifically so you see as the problem? Do you have a stack trace  
or such that is leading you to these conclusions?

Cheers, Tim

Sent from my iPhone

On 27 May 2009, at 20:33, feelgood <[email protected]> wrote:

>
> But it's still doesn't work with plain properties. I think the problem
> is in the ResourceBundle class and getBundle method. "?" method of "S"
> object comes to using ResourceBundle.
>
> On 27 май, 22:02, feelgood <[email protected]> wrote:
>> Thanx a lot.
>>
>> On 27 май, 21:17, David Pollak <[email protected]> wro 
>> te:
>>
>>> On Wed, May 27, 2009 at 7:55 AM, feelgood <[email protected]>  
>>> wrote:
>>>> First, I tried to use UTF-8 encoded property files to localize my  
>>>> app.
>>>> I saw Неверно указан  
>>>> идентификатор. AIUI
>>>> this is ISO 8859-1 encoded representation of my UTF-8 string. I  
>>>> also
>>>> tried to use native2ascii tool to decode UTF-8 strings in ASCII  
>>>> string
>>>> like \u0420\u045c\u0420\u00b5\u0420... . But it's not help. Any  
>>>> idea?
>>
>>> I just enhanced the Props stuff to first try to use the properties  
>>> XML
>>> format (seehttp://java.sun.com/javase/6/docs/api/java/util/ 
>>> Properties.html#loadF...))
>>> and I also forced the input stream into UTF-8 format so there's no
>>> platform character set issues.  The changes should be available in  
>>> Hudson
>>> within the hour.
>>
>>> --
>>> Lift, the simply functional web frameworkhttp://liftweb.net
>>> Beginning Scalahttp://www.apress.com/book/view/1430219890
>>> Follow me:http://twitter.com/dpp
>>> Git some:http://github.com/dpp
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to