The developers want to know if it is possible to export the content of the translated German string lists of a Passolo Professionla 2022 lpu project to an rc file.
They want to know if it is possible in principle for them to integrate the existing German localization into the source files in Developer Studio so the English and German version of the strings is in one file.
I'm not quite sure what the background to this question is. If the source file is a monolingual RC file, Passolo will then generate a translated monolingual RC file. Please note that the source file is only monolingual and the translated RC file can only be monolingual. Multilingual RC files are not supported. Too many #ifdefs and other conditional dependencies.
On the other hand, the binary localization of EXE, DLL etc. is also supported for C++ programs, and it is possible to create multilingual target files.
I'm not quite sure what the background to this question is. If the source file is a monolingual RC file, Passolo will then generate a translated monolingual RC file. Please note that the source file is only monolingual and the translated RC file can only be monolingual. Multilingual RC files are not supported. Too many #ifdefs and other conditional dependencies.
On the other hand, the binary localization of EXE, DLL etc. is also supported for C++ programs, and it is possible to create multilingual target files.
Hi Armin, thanks for your answer. Talked to the programmer again, he wants to run some experiments, what for I don't know.
We have a monolingual source file in English and want to generate a German monolingual target file.
How do I go about that? Where can I select rc file as the target file format after addiing German as the target language?
(Is the built-in RC File Parser the Add-In for Windows Resource Script (.rc) Files or is the Add-In a different tool?)
The RC Parser add-in is not an optional one, it is always available. When your source file is an RC file, the target file will automatically be the translated RC file. For RC files, Microsoft never documented a naming convention for the translated files. This is always user defined, and you need to ask your developers, then implement the naming convention. This can be done by manually changing the translated file name or by creating and applying a target path rule, which is recommended for a project with many files and many target languages.
Hi Achim, thank you much for answer, this is exactly what the programmer hoped for!
Echt toller Support he said.
Translate
