Judit Barabas

I wonder why they don't use IDML and insist upon XLIFF?  Did this go through another translation tool first?

Might be related to using this setting when you prepare your XLIFF file project in Studio:

This used to be the default, although it was changed recently so it no longer is.  But perhaps you have an older version of Studio 2019 or you have used an old project template?

Hi Paul, 

thanks for getting back to me. The client says working with loads of idml files into 20 languages would be too much bother, so they use xlf because it's less work for them, and so far we had no problems. 

I checked, though, and the box you mention is not ticked, so this is not the problem. 

I'm at a loss and so is the client. 

Judit Barabas

Judit Barabas said:

please find attached the Polish files. At least I hope I managed to upload them. 

Unfortunately you didn't.

Zip them into a single zip file and then add the zip:

2002-052-HU04.zip

Let me try again... 

Thanks Judit Barabas

This looks like a bug to me.  I have logged this with the support team for investigation.  If it is a bug I'll let you have the bug number so you can chase progress on it more easily.  If it's not a bug I'll hopefully be able to explain what you need to do.

Thank you so much!

Judit Barabas

So... it's not actually a bug.  The support team have explained that this is occurring because you have a couple of segments in the file that are source only and have no target content.  But as the source only contains a tag Studio moves this externally so you don't see it.  But once the file is fully segmented and the status changes you see these segments in Studio too... this happens when you save the target file.

So for example, look at the end of your file and you'll see this in the source:

You can see that the target is empty.  The source only contains a tag and this is not seen when Studio opens the file for translation.  However, the target file is like this:

Note that this time the target is also populated and Studio won't hide this when you open the file again, and the status is "signed-off".  This happens in two segments (40 and 56), and this accounts for the additional two lines in the file.  They have always been there and once you populate the target as well it becomes more obvious.

If you change the target file so that the two affected segments are empty and given a "needs-translation" status then you'll have 54 segments again... as attached:

fixed_10_11_LOOK 01_20_iÜ_Hügli_Eisberg_hu.zip

It might be worth seeing if this makes the difference in importing back.  If it doesn't then the problem probably relates to something else and I think would need investigation in InDesign.

Hi Paul, 

thank you for the explanation. 

I only have one question: how do I empty the segments and change the status of I can't see them? If i open the files in Studio, I see 54 segments. 

Judit Barabas

You need to do this manually in a text editor to the target files as I attached.  It was just a suggestion because there is actually nothing wrong with the files you have that contain 56 segments.  But seeing as your customer is having problems importing and you thought it might be linked to this issue I thought you could test it by editing your target files so the segments that only contain tags are reset to the way they were prior to translation.

Thank you. We've fixed the files and sent them to the client but never heard of them since, so I suppose we can consider the case closed. 

Thank you for the help. 

Thanks Judit...

They've just got back to us saying the files are ok. 

They've just got back to us saying the files are ok.