Spanish Laguage in Active Report

Posted by: usuariosp on 4 August 2017, 2:32 pm EST

  • Posted 4 August 2017, 2:32 pm EST

    Hello

    We´ve followed this link (http://www.datadynamics.com/ShowPost.aspx?PostID=397) to translate AR to Spanish. Everything is ok, but some words,like GroupHeader, ReportFooter, Fields..., are missing and they´re in English. We´re sure that this words have been translated to Spanish in the resources File.

    Dll files are in the correct directory (c:\aplication\3082). That´s rigth because most of words are in spanish.

    do you know what´s wrong?

    Thanks.
  • Replied 4 August 2017, 2:32 pm EST

    Ok, here you have a sample. You can see a control translated at the left of he picture.

    But, in the other hand, if we open one of your sample projects (diamond reports) we can see all the words translated. With the same references in VB...

    thanks.

  • Replied 4 August 2017, 2:32 pm EST

    That should be right. Is it displaying any of the other localized header/footer changes made from the localized resource file? Can you take a screenshot of the missing localization so I know where to look for it? Thanks!
  • Replied 4 August 2017, 2:32 pm EST

    "IDS_SECTIONPROGNAME_GROUPHEADER" and "IDS_SECTIONPROGNAME_GROUPFOOTER" are already translated. What else could be wrong?

    Thanks.
  • Replied 4 August 2017, 2:32 pm EST

    The GroupHeader and GroupFooter are localized in the ARIntl.rc under "IDS_SECTIONPROGNAME_GROUPHEADER" and "IDS_SECTIONPROGNAME_GROUPFOOTER", respectively.
  • Replied 4 August 2017, 2:32 pm EST

    Hello again.

    Brandon, here you have dll´s translated and the localization files... Can you tell us what´s wrong?

    Thanks.

    2005/03/Localization.zip
  • Replied 4 August 2017, 2:32 pm EST

    We´ve found out that changing the order of the references of AR in the .VBP project, affects the rendering of localization strings

    Is there any correct way to do the same in .exe file?

    Thanks.

  • Replied 4 August 2017, 2:32 pm EST

     UsuarioSP wrote:
    Ok, here you have a sample. You can see a control translated at the left of he picture.

    But, in the other hand, if we open one of your sample projects (diamond reports) we can see all the words translated. With the same references in VB...

    thanks.


    The "GroupHeader3" is the name of the section. You can change the GroupHeader's Name property if you want it to be localized. There's no way to change the default GroupHeader when ActiveReports inserts a new header.
  • Replied 4 August 2017, 2:32 pm EST

    Hello Brandon, here you have another sample. We´re sure that we´ve translated all words in dll´s... but, you can see, some words are translated (As buttons, New and Delete) and others aren´t. why?

    We still have the problem.

    Thanks.


  • Replied 4 August 2017, 2:32 pm EST

    The GroupHeader3 that you are seeing is the name property of the section. This is jsut like naming a textbox "TextBox1". You can change the name property of the section and it will reflect the updated name. You will still see GroupHeader1, GroupHeader2, GroupHeader3 until you change their names in code. The controls and sections on the report cannot be localized with the localization dlls; they must be renamed.
  • Replied 4 August 2017, 2:32 pm EST

    Thanks for your support, but the problem continue... we think that the problem is the way of dll´s register... Is any correct way?

    thanks again
  • Replied 4 August 2017, 2:32 pm EST

    The GroupHeader3 that you are seeing is the name property of the section. You can change the name property of the section and it will reflect the updated name. You will still see GroupHeader1, GroupHeader2, GroupHeader3 until you change their names in code. The controls and sections on the report cannot be localized with the localization dlls; they must be renamed. Here's a sample demonstrating how to rename the Group sections once they have been added. You can use the same code to rename the sections when the report is loaded.
    2005/03/Designer.zip
  • Replied 4 August 2017, 2:32 pm EST

    Any English you see after using the localization DLL is a unique property or name and cannot be localized with the DLL. The point of the sample was to show you how to change those names using code. You can change any property of the section and the designer will then show the new name. The controls, their properties and sections on the report cannot be localized with the localization dlls; they must be renamed. The sample gave you a way to change the English to Spanish using code. If you want to see your entire report in Spanish, you must use the similar code to rename the sections, the properties and the controls when the report is loaded or newly created.
  • Replied 4 August 2017, 2:32 pm EST

    Hello again.

    Brandon, this is the result of your sample. As you can see the names are in english. But, if we create a new report we can see that the names are translated.

    On the other hand, if we open a stored report, having a break point in ARD_LayoutChanged Sub, we can see that the sample try to change the name... but the final result it´s what you can see.

    Another thing, the properties window isn´t translated on interface...

    Thanks for your support.


  • Replied 4 August 2017, 2:32 pm EST

    ok, and what about name of properties?
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels