NetTalk Central

Author Topic: PR36 Translate bits  (Read 3283 times)

Alberto

  • Hero Member
  • *****
  • Posts: 1873
    • MSN Messenger - alberto-michelis@hotmail.com
    • View Profile
    • ARMi software solutions
    • Email
PR36 Translate bits
« on: April 30, 2009, 04:42:34 AM »
Hi,

>>> The buttons are already not been translated
You are still using Translator.TranslateString :
  s_web._SitesQueue.Defaults.UploadButton.TextValue = Translator.TranslateString('Upload')
  s_web._SitesQueue.Defaults.UploadButton.ToolTip = 'Click here to Upload the file'
Idea: You are not using Translator.TranslateString for the Tooltip and the tooltip _translates ok_, may be you translate it when you create the button, why dont translate the TextValue the same way?

>>> The Text of a Button field in a WebForm is not translated

>>> Please, please, please!!! I do need, and I think anybody will do, a way to avoid the translation of the options loaded from a file. I realized you are translating it in the CreateOption Method and then I cant even omit it by hand coding.
Please, read my explanation in my last Translate Problems post.

>>> It would be greate if you can add a parameter to the Translate Method to know the type of string, that is for a Prompt, Option, Check, etc.
That is because when you are extracting the strings you need to be translated, it is very helpfull to know the procedure from where it belongs to ( I'm doing it with GlobalErrors.GetProcedureName() ) and the type of field.

Thanks
Alberto




-----------
Regards
Alberto

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: PR36 Translate bits
« Reply #1 on: April 30, 2009, 05:13:23 AM »
Hi Alberto,

sorry - there's a mistake in the PR36 build. The NetTalk TPL file (which generates the WebServer procedure) did not get updated. So the translation stuff in the WebServer procedure was not updated.

>> I'm doing it with GlobalErrors.GetProcedureName() ) and the type of field.

that's the correct way to do it.

Cheers
Bruce


Alberto

  • Hero Member
  • *****
  • Posts: 1873
    • MSN Messenger - alberto-michelis@hotmail.com
    • View Profile
    • ARMi software solutions
    • Email
Re: PR36 Translate bits
« Reply #2 on: May 01, 2009, 04:58:38 AM »
Hi Bruce, thanks, I know you are busy but I insist with which I thinks is the most important part...

>>> Please, please, please!!! I do need, and I think anybody will do, a way to avoid the translation of the options "loaded from a file". I realized you are translating it in the CreateOption Method and then I cant even omit it by hand coding.
Please, read my explanation in my last Translate Problems post.

If you cant do it then is preferable not to translate, I can omit the template code and translate where I need.

Thanks
Alberto
-----------
Regards
Alberto

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: PR36 Translate bits
« Reply #3 on: May 01, 2009, 06:26:38 AM »
Ok, I haven't addressed this in PR37 but I'll see what we can do in PR38.