The described issue is something that usually can’t be solved just here in the forum. I would highly recommend to log a support case and forward the files for further analysis.

Seeing the warning message in the first screen shots gives you a first hint what might go wrong. You are trying to generate a target file, but the corresponding translation list doesn’t have all the entries that were found in the source file that now becomes your target. This is usually an indicator, that your source file has changed, in your case new entries were added which are shown in the warning message. That will result into the fact that some untranslated (German) strings appear in your Arabic target files.

This is not a bug, this is a simple user error. You can easily solve it. When you are not sure if your source files have been changed, please open up the base project first and update the complete project. Close the base project, open the cascaded project and again update it completely. Then create the target files. I assume that the warning will not be shown and that everything work properly.

Dear Achim,

thank you for your looking into this.

I've been using Passolo for almost two decades, I know the behavior you describe, and I assure you, that's not it.

Still, I followed your advice, but the problem is still there.

The generated file does not contain untranslated properties. It contains the Arabic translation with some additional German text (and tagging) appended to it.

I would like to submit the files, but I do not have a support contract. Where can I report the case?

Kind regards

Susanne

This is a very tricky issue. It is a bug that seem to be here nearly forever. It is related to cascaded projects and segmentation rules. Explaining it in details will take some time, so I decided to skip this here.

I will log it as a case for the developers, but I’m not sure if it can be solved and when. Therefore I will propose some easy work-arounds.

#1: If you switch off the segmentation

Your project has 8 Java source files, but just for the file  Multi_reporting_charts_resources_de the segmentation is activated and just here you see the error when generating the Arabic. Switch off the segmentation for this file and the error will not occur anymore.

#2: Change some source sentences in Multi_reporting_charts_resources_de

The problematic key/value pairs that cause the issues are the IDs listed in the warning messages. All these sentences will have some German abbreviations (z.B., i.d.R.) that will cause the issue. If you exchange these abbreviations with the long words, it will also work properly.

This is a very tricky issue. It is a bug that seem to be here nearly forever. It is related to cascaded projects and segmentation rules. Explaining it in details will take some time, so I decided to skip this here.

I will log it as a case for the developers, but I’m not sure if it can be solved and when. Therefore I will propose some easy work-arounds.

#1: If you switch off the segmentation

Your project has 8 Java source files, but just for the file  Multi_reporting_charts_resources_de the segmentation is activated and just here you see the error when generating the Arabic. Switch off the segmentation for this file and the error will not occur anymore.

#2: Change some source sentences in Multi_reporting_charts_resources_de

The problematic key/value pairs that cause the issues are the IDs listed in the warning messages. All these sentences will have some German abbreviations (z.B., i.d.R.) that will cause the issue. If you exchange these abbreviations with the long words, it will also work properly.

Excellent, thank you so much.

I used workaround #2 to keep the segmentation for these lengthy texts, and it worked nicely.