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 myFileName!
!!! Unsupported param of type variable at line 54

I tried including the mixin as include : [qx.locale.MTranslation], but 
still the same error.

I even tried myLabel.set({content: qx.locale.Manager.tr(str)}); but same 
error.

regards
-- 

Amit Rana
SpagoBI Developer
www.eng.it                    
www.spagoworld.org


thron7 wrote:
> 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 JSON file. And if the load application is diff., then you do :
>>
>> ...
>>  "jobs" :
>>   {
>>       "common" :
>>     {
>>       "include" :
>>       [
>>         "new application name",
>>         "${QXTHEME}",
>>         "qx.legacy.theme.ClassicRoyale"
>>       ],
>>       "settings" :
>>       {
>>         "qx.legacy.theme" : "qx.legacy.theme.ClassicRoyale",
>>         "qx.application"  : "new application name"
>>       }
>>     },
>> ...
>> "translation" :
>>     {
>>       "extend" : ["common", "appconf::translation"]
>>     }
>>   
>>     
>
> Yes, that was a bug in the 0.8. 'migration' and 'with-contrib' skeleton 
> templates, but has been fixed in trunk. The local 'translate' job was 
> referencing the appconf job incorrectly ("appconf::translate" rather 
> than "appconf::translation", as you already found out). It would have 
> sufficed to change the existing job to using appconf::translation, and 
> then call 'generate.py translate'. But your solution works just as well.
>
> It was also a good idea to create a local "common" job and reference 
> that in the 'extend' section of "translation", especially since you do 
> not use the default for the main application class (which is 
> "<namespace>.Application").
>
> The DeprecationWarning in newer Python versions has also been taken care of.
>
> Sorry for the trouble.
> Thomas

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to