Hello Victoria Zolotareva ,

I don't think I have seen this before. A couple of the segments display correctly it seems- but others not.

What happens when you create a single file translation? Do you still have a display issue?

Are you able to share some of the files so i can test? (swhale@sdl.com)

Also- please let me know which version of Studio you are using and which OS version.

Hello ,

Thank you for the quick response!

>>A couple of the segments display correctly it seems- but others not.

Yes, segments with English text inside are OK, question marks appear instead of Russian text in the segments.

>>What happens when you create a single file translation? Do you still have a display issue?

No problem with single file translation. Also, if I create a project for 5, 10, 15 files taken from this batch, everything is ok but 400 files are not processed correctly.

>>Also- please let me know which version of Studio you are using and which OS version.

I am using Studio 2019, my OS is Windows 10 Enterprise, version 1607, 64-bit operating system

Hello Victoria Zolotareva ,

Unless someone else has seen such behaviour and can suggest a different solution-

-my guess is a number of the files are malformed- hence why you can make small projects but not take the whole batch.

If it were just a couple of files, I would suggest opening these in NotePad++ to try and identify where the issue lies.

However, in this case, I think the only option is to split the files eg.200/200 and run them through Studio as separate projects- open each one in turn and check- then keep splitting the files into small batches, repeating until you find the files that are causing the issue.

Hi,

is there a known solution to this problem in the meantime. The same problem shows up for us with a Hungarian file in Studio 2021. When opening the file on another computer with Studio 2022, the text is displayed correctly. So the issue seems to be with some settings in Studio, the computer itself or the version of Studio, not the file itself.

We had a solution for this problem in the past (quite a few years ago), but I do not remember. Sorry.

Thanks,

Johannes

Johannes Purer 

The issue is almost certainly due to a couple of things:

1. general encoding issues for the source documents
2. in 2021 and earlier we allowed more freedom over supported fonts (non-UTF compliant for example)
3. Microsoft started to enforce the fonts used despite what you think you select because of this sort of issue with some fonts

So in 2022, and later, we enforce things similarly to Microsoft to try and reduce these sorts of issues since most users will not be aware of the problems that can be caused by non-UTF compliant fonts; and we have completely replaced the Studio Editor to help with this and many other things related to font support.  So this could be why you don't have this problem in 2022.

There is no solution for you in 2021 unless you can fix this yourself by ensuring that the document is encoded correctly and the fonts being used are UTF compliant.

Johannes Purer 

The issue is almost certainly due to a couple of things:

1. general encoding issues for the source documents
2. in 2021 and earlier we allowed more freedom over supported fonts (non-UTF compliant for example)
3. Microsoft started to enforce the fonts used despite what you think you select because of this sort of issue with some fonts

So in 2022, and later, we enforce things similarly to Microsoft to try and reduce these sorts of issues since most users will not be aware of the problems that can be caused by non-UTF compliant fonts; and we have completely replaced the Studio Editor to help with this and many other things related to font support.  So this could be why you don't have this problem in 2022.

There is no solution for you in 2021 unless you can fix this yourself by ensuring that the document is encoded correctly and the fonts being used are UTF compliant.

Hi Paul, okay, thanks a lot for the reply. It seems our solution back then was to move to Studio 2022.

Regards, Johannes