> Oh, I was assuming it would just be a matter of adding keys to the .po
> file using some poEditor.
The way its done currently is to use the set of keys from the source as a
filter. This makes sure you're not drawing in unused keys from a .po file
where they're might still hang around. But if you
Hi All,
I'm just coming to realize something.
I think I have a broader feature request.
Can the localisation support, offer the ability to use our own classes
that provide the translation?
Perhaps in a way where we can set the translation manager per class?
I think most people that are hitting i
2010/7/18 thron7 :
> Ralf,
> This has been fixed (http://bugzilla.qooxdoo.org/show_bug.cgi?id=3669).
> It's a good idea to put yourself on CC on the bugs that interest you so
> you get notifications.
Agreed. I just didn't realize there was already a bug. I usually just
search the qooxdoo mailing l
Ralf,
> Hi,
>
> I'm replying to this old thread again, because I really wonder if this
> is possible.
> I understand it's great the toolchain can extract the strings for
> translations. But why does it have to be that way mandatory?
This has been fixed (http://bugzilla.qooxdoo.org/show_bug.cgi?i
Hi,
I'm replying to this old thread again, because I really wonder if this
is possible.
I understand it's great the toolchain can extract the strings for
translations. But why does it have to be that way mandatory?
I at least need to 'patch' it at this side, so I'm hoping somebody can
guide me a
Le 01/06/2010 11:16, thron7 a écrit :
>
>
> On 06/01/2010 10:54 AM, geoffre wrote:
>> Le 01/06/2010 09:52, geoffre a écrit :
>>> Le 01/06/2010 09:50, geoffre a écrit :
Hi,
I have the following problem; the method this.tr() use for
internationnalization return me a "qx.locale.Loc
On 06/01/2010 10:54 AM, geoffre wrote:
> Le 01/06/2010 09:52, geoffre a écrit :
>> Le 01/06/2010 09:50, geoffre a écrit :
>>> Hi,
>>>
>>> I have the following problem; the method this.tr() use for
>>> internationnalization return me a "qx.locale.LocalizedString" instead of
>>> a "qx.locale.String
Le 01/06/2010 09:52, geoffre a écrit :
> Le 01/06/2010 09:50, geoffre a écrit :
>> Hi,
>>
>> I have the following problem; the method this.tr() use for
>> internationnalization return me a "qx.locale.LocalizedString" instead of
>> a "qx.locale.String".
>>
>> Am I obliged to add a toString() after e
Le 01/06/2010 09:50, geoffre a écrit :
> Hi,
>
> I have the following problem; the method this.tr() use for
> internationnalization return me a "qx.locale.LocalizedString" instead of
> a "qx.locale.String".
>
> Am I obliged to add a toString() after each this.tr() ?
>
> Thanks.
>
>
> --
Hi,
I have the following problem; the method this.tr() use for
internationnalization return me a "qx.locale.LocalizedString" instead of
a "qx.locale.String".
Am I obliged to add a toString() after each this.tr() ?
Thanks.
--
Andy Fuchs wrote:
> If I create a localizable application, wouldn't it be nice to create a mixin
> containing all localizable strings, instead of distributing the strings all
> over the code...
>
> Or are there any disadvantages with this approach (or other ideas)?
>
No, it's a fairly common
If I create a localizable application, wouldn't it be nice to create a mixin
containing all localizable strings, instead of distributing the strings all
over the code...
Or are there any disadvantages with this approach (or other ideas)?
tia
andy
2008/12/29 Ralf Nieuwenhuijsen :
> 2008/12/16 thron7 :
>>
>>
>> Amit Rana wrote:
>>> yes, we can edit the files but have to repeat the same code of calling
>>> function call tr() in all my files. Anyways, i got the point.
>>>
>>
>> Well, you might want to open a bug that these tr() errors might be
2008/12/16 thron7 :
>
>
> Amit Rana wrote:
>> yes, we can edit the files but have to repeat the same code of calling
>> function call tr() in all my files. Anyways, i got the point.
>>
>
> Well, you might want to open a bug that these tr() errors might be
> turned into warnings, so the generation p
Hi to all
thron7-2 saying the right
but you can edit your .po translation files manually
with ant text editor and add new entries you want
--
View this message in context:
http://n2.nabble.com/Internationalization-not-working-tp1657776p1662909.html
Sent from the qooxdoo mailing list archive a
Amit Rana wrote:
> yes, we can edit the files but have to repeat the same code of calling
> function call tr() in all my files. Anyways, i got the point.
>
Well, you might want to open a bug that these tr() errors might be
turned into warnings, so the generation process continues.
Then, you
yes, we can edit the files but have to repeat the same code of calling
function call tr() in all my files. Anyways, i got the point.
Now, that my internationalization feature has been added, I get an error
when I try to change the language. This error appears only the 1st time.
After I have chang
Amit Rana wrote:
> hi,
>
> I get the point.
>
> The reason I asked this is because I have a function to create a label
> and set its contents based on the parameter passed to it. Now, I have to
> call tr() everytime I pass the parameter. Instead, if I know that
> whatever is passed is a string
hi,
I get the point.
The reason I asked this is because I have a function to create a label
and set its contents based on the parameter passed to it. Now, I have to
call tr() everytime I pass the parameter. Instead, if I know that
whatever is passed is a string, so I just need to call tr() ins
Amit Rana wrote:
> hi,
>
> yes .. I got that. Thanks for the help.
> But, I am not able to translate the content present in a variable.
>
> For example,
> var str = "Hello World";
> var myLabel = new qx.ui.basic.Label();
> myLabel.set({content: this.tr(str)});//line 54
>
> gives me error as:
>
hi,
yes .. I got that. Thanks for the help.
But, I am not able to translate the content present in a variable.
For example,
var str = "Hello World";
var myLabel = new qx.ui.basic.Label();
myLabel.set({content: this.tr(str)});//line 54
gives me error as:
!!! Could not extract translation from
Amit Rana wrote:
> hi,
>
> I figured out the way but just want to communicate that the step
> mentioned that config.json does not include the translation job by
> default. So, we need to add the line :
>
> "translation" :
> {
> "extend" : ["appconf::translation"]
> }
>
> in the JS
hi,
I figured out the way but just want to communicate that the step
mentioned that config.json does not include the translation job by
default. So, we need to add the line :
"translation" :
{
"extend" : ["appconf::translation"]
}
in the JSON file. And if the load application is
Hi,
I am using v0.8 SDK and I want to use the internationalization feature.
I was following the instructions as given on :
http://qooxdoo.org/documentation/0.8/internationalization
But, I am getting errors. How do I setup my config.json for this ? I use
a path diff. from Application.js (like c
>
> Finally, it seems that your post is being seen as a reply to a previous,
> unrelated post (at least nabble understood it so - maybe it got
> confused?).
> If you have further doubts regarding translation support, I'd suggest
> creating a new thread.
It's nabble, because it looks fine in my g
Bryan Coutch wrote:
>
> (...) it doesn't seem to mention the following files:
> /frontend/framework/source/class/qx/locale/data/*.js
> /frontend/framework/source/locale/*.xml
> What are these files used for? I assume I will want to create a
> translation for the languages I need?
>
AFAIK,
I have read through
http://qooxdoo.org/documentation/0.7/internationalization?s=translation
which describes how to translate strings in your application into other
languages, but it doesn't seem to mention the following files:
/frontend/framework/source/class/qx/locale/data/*.js
Hi Sergei,
On Monday 30 April 2007 Sergei Kolomiets wrote:
> Hi!
> Can I use internationalization of properties default values with usage
> this.tr()?
You have to use the static method of "tr()" (located in
the "qx.locale.Manager" class) because "this" is not available/accessable at
the time you
Hi!
Can I use internationalization of properties default values with usage
this.tr()?
--
View this message in context:
http://www.nabble.com/Internationalization-of-properties-tf3672021.html#a10260736
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
29 matches
Mail list logo
