Problem with AR19 localization

Problem with AR19 localization

Posted by: vbie on 27 June 2025, 11:47 am EST

• 

  vbie

  • Post Options:
  • Link
    Copy

  Posted 27 June 2025, 11:47 am EST

  Dear community,

  Our product has encountered the following localization problem. We have localized into three languages ​​fr-CA, pt-BR, he-IL, but the compiled libraries do not want to be loaded when the application is launched.

  I have supplemented the standard EndUserDesigner program with logs that display the process of loading libraries and, in particular, resource libraries. Some resource libraries are written in the logs, but I do not see the result of using these libraries, some resource libraries (HtmlExport and ect) are not even called. The appearance of the export types remains in English.

  You can find the program + an example of a translated, but not yet compiled library for html exprot in the appendix. Also, the resource libraries were assembled according to the guide https://developer.mescius.com/activereportsnet/docs/latest/online/net-localize.html

  You can also find a set of scripts and keys used for assembly in the appendix.

  Please help solve this problem. Maybe someone has already encountered this and there is some solution. Maybe there is an error in the guide or assembly scripts.AR19fr_CALocalization.zip

• 

  anand.sinha

  

  • Post Options:
  • Link
    Copy

  Posted 1 July 2025, 1:40 am EST - Updated 1 July 2025, 5:00 am EST

  Hi Vadym,

  Due to the name change from GrapeCity to MESCIUS our packages names have also changed to ‘MESCIUS’ however, the namespace within the packages have remained ‘GrapeCity’, so please make sure when editing the batch (.bat) files with your culture name you also update the DLL name with ‘MESCIUS’.

  For example, the batch file for ‘fr-CA’ localization for WinViewer should look like:

  set Culture=**fr-CA**
  
  set ProjectName=WinViewer
  set DllName=**MESCIUS**.ActiveReports.Viewer.Win.resources.dll
  set BaseNamespace=GrapeCity.ActiveReports.Viewer.Win
  
  call Localize.bat
  
  

  ** are the manual changes that are required in batch files.

  We have created a WinViewer sample using the localized DLL (We have only changed the content for the toggle sidebar button) for you to reference.

  However, please note, this issue is fixed in ActiveReports 19.1, with the batch files containing the correct DllName, so you only need to change the Culture value of them.

  You can update to v19.1 by downloading the same from here: https://developer.mescius.com/activereports/download-version-history.

  Regards,
  
  Anand

  Localization.zip
  
  

  

  765×398 13.1 KB

• 

  vbie

  • Post Options:
  • Link
    Copy

  Posted 1 July 2025, 1:05 pm EST

  Hi Anand,

  I rebuilt the resource libraries as you said. Then I replaced the MESCIUS.ActiveReports.Viewer.Win.resources.dll file in your program with my own MESCIUS.ActiveReports.Viewer.Win.resources.dll from the compiled package for fr-CA and saw that it was fully applied in your example.

  But I still can’t achieve this effect for the standard EndUserDesigner example. I even added the AssemvlyResolver event handler there and loaded the necessary resource libraries, but they still are not applied in this example.

  Could you please tell me why my resource libraries are applied to your example and I see that they work, but they are not applied for EndUserDesigner?

  You can find the program with logging and resource libraries for fr-CA in the attachmentfr-CA.zipExampleForSupport.zip

• 

  vbie

  • Post Options:
  • Link
    Copy

  Posted 1 July 2025, 1:09 pm EST

  ExampleForSupport.zip

• 

  vbie

  • Post Options:
  • Link
    Copy

  Posted 1 July 2025, 1:10 pm EST

  fr-CA.zip

• 

  anand.sinha

  

  • Post Options:
  • Link
    Copy

  Posted 3 July 2025, 4:42 am EST

  Hi Vadym,

  Thanks for reporting this issue to us, we were able to notice that generating a Localized DLL for ARDesigner does not seem to be working with the EndUserDesigner sample.

  We have therefore reported this to our development team [Internal Tracking ID: AR-35954] and will get back to you as soon as we have any update regarding the same.

  Thanks,
  
  Anand