roynielsen2000@gmail.com

Hi, I would like to solve the problem when a developer do not update the xlat file from a newly built .exe file, we had an example yesterday actually. Sometimes when a developer forgets to sync, the translations on various components can be wrong, one example from yesterday was headers on a database grid with wrong titles and the forms caption bar title text was also wrong. After an update og the xlat file and a new build, problem was solved, but some customers already had the wrong version.

Question: Does the commandline tool update the project when generating language files ? If not, is it possible to include that functionality ?

Our old Sisulizer tool added the language resource files to our exe files after the build and we extract the resource files and reloads a users chosen language at runtime (we also switch the language "on-the-fly" by re-initializing the forms and call System.SysUtils.ResStringCleanupCache I have been experimenting with adding the language files as a resource, but as Anders writes, it's the chicken-egg problem with that solution How can I add the resources to a .exe files after it is build ? Does someone know how this is done ?

Hi, We have a challenge in distributing our exe files and language files to our customers and keeping the respective file versions (exe and language files) in sync, due to files in use, locked etc. Does anyone know a solution to, for example, include the language files into the .exe file and then extract the language files when the starting the exe file ? Best regards Roy Nielsen

Hi, Probably a dumb question: If I have a TcxGridDBTableView, how do I translate the column headers in the grid ? Looking in my project(s) on the relevant forms containing the component

Hi, A question: We have several applications that share the same modules/TForm's, Is there any way to import from a module in one application to the application we are translating ?

Ok, thanks, that solved it 🙂

Still the same issue: c:\Program Files (x86)\Melander\Better Translation Manager>amResourceModuleBuilder.exe c:\PicassoSVN\local\Localization\Reception\Reception.xlat -b -v -o:c:\PicassoSVN\local\ExeFiles\emb\ -n 1 amTranslationManager resource module builder version 1.3.8198.28909 Loading project: Reception... Project information: Source file : c:\PicassoSVN\local\ExeFiles\Reception.exe Source Language: Locale=0409, Name=English (United States) Symbol file : .\Reception.drc Target language: Translated=19.339, Locale=0406, Name=Danish (Denmark) Target language: Translated= 0, Locale=0814, Name=Norwegian Nynorsk (Norway) Target language: Translated= 0, Locale=042D, Name=Basque (Basque) Target language: Translated= 0, Locale=041D, Name=Swedish (Sweden) Target language: Translated= 0, Locale=041F, Name=Turkish (Turkey) Modules : 500 Items : 26.785 Properties : 33.886 Output folder: c:\PicassoSVN\local\ExeFiles\emb\ Building resource module for Danish (Denmark): Reception.DAN... Building resource module for Norwegian Nynorsk (Norway): Reception.NON... Building resource module for Basque (Basque): Reception.EUQ... Building resource module for Swedish (Sweden): Reception.SVE... Building resource module for Turkish (Turkey): Reception.TRK... Done

Hi Anders, It seems as if this bug is back again with the newest build ?

Thank you, I will continue with the TMX files

Hi Anders, Do you still need the tmx file ? I can see you seem to have found the problem

Hi, I think I found a bug: I have export a Sisulizer file to tmx format with Danish, Swedish, Norwegian (Nynorsk) + 2 other languages Now when adding Norwegian Nynorsk to BTM and try to "Translate from TM" nothing is translated, but if I add Norwegian (Bokmål) as a language and translate, then I get translation as expected I think it is a BTM problem because in the tmx file it is the countrycode "nn" which from what I found i Norwegian Nynorsk (and nb is Norwegian Bokmål)

Hi, We would like to switch from Sisulizer to BTM, so we where thinking if there is someone who has already done that and if there are anything we need to have attention on ? We think about doing it this way: 1. For each if our applications, export the Sisulizer translation to TMX format (is that the way to do it or is there a better way?) 2. Translate each application using BTM with the TMX file Is there a better/easier way than this (we would like to reuse our translation as much as possible) ? Sisulizer integrates the language files into the .exe files (SlMake.exe does this as far as I can tell), and the language files is then extracted when the .exe file is launched, so we will modify our build tool to create the language files and distribution tool to update the language files, so that shouldn't be a issue

Please uplolad a new build 🙂 And I will say hi to Arne from you 🙂

Hi, I'm testing the translation tool and may have encountered a problem with the commandline tool, it ignores the -n filename scheme paramterer ? It doesn't matter if I use -n:1 or -n 1 (or 0 or 2 as the value), I always get the 3 letter extension for the translation files c:\Program Files (x86)\Melander\Better Translation Manager>amResourceModuleBuilder.exe c:\PicassoSVN\local\Localization\Reception\Reception.xlat -b -v -o:c:\PicassoSVN\local\ExeFiles\emb\ -n 1 amTranslationManager resource module builder version 1.3.8055.21506 Loading project: Reception... Project information: Source file : c:\PicassoSVN\local\ExeFiles\Reception.exe Source Language: Locale=0409, Name=English (United States) Symbol file : .\Reception.drc Target language: Translated=22.585, Locale=0406, Name=Danish (Denmark) Target language: Translated=11.844, Locale=041D, Name=Swedish (Sweden) Target language: Translated=11.266, Locale=0414, Name=Norwegian Bokmål (Norway) Modules : 501 Items : 26.765 Properties : 33.866 Output folder: c:\PicassoSVN\local\ExeFiles\emb\ Building resource module for Danish (Denmark): Reception.DAN... Building resource module for Swedish (Sweden): Reception.SVE... Building resource module for Norwegian Bokmål (Norway): Reception.NOR... Done