Hello Paul,

I wonder whether the update fixing this issue has been released yet. We have Studio 2017 and 2 versions of it on different computers, before and after the latest update to 14.0.5889.5.
If we process files in the version before the update, we get the described issue where source content is missing.
In the updated version, however, we can only convert the same file and copy to target languages. The file can't be opened, I only get the full progress bar and nothing happens, no error message either. Also any attempt for batch task stops at around 95%, which means that after the latest update we can't really process the files at all.

Thank you for any news.

Regards
Michaela

Update from 26.7.2017: SR1 has been released just yesterday. I have already installed it and processed the problematic files. Though it seems that less source content was affected, the issue persists.

Hi Stefan,

I do too, and that it will work. It's hard to pin down sometimes why content doesn't flow into the translation file as it should. It can be because it's generated by 3rd party software that takes it down or up a level so that the software doesn't see it as text, for example. This happens in Word and also in DTP software such as InDesign.

BTW have you played with the filetype settings, for example here?:

You'd have to do it before conversion to .sdlxliff of course.

If the document were saved as a .doc, you would have even more settings to play with, for example here's where you can define which footnotes should be excluded:

You probably know that already but, in case not, I thought it was worth mentioning.

All the best,

Ali

Hi Stefan,

Re the .docx settings, Microsoft Word 2007-2016, the one I'd try first is 'Extract hidden text for translation', not because I know that would work; it just seems the most likely to me.

Re the .doc settings, Microsoft Word 2000-2003, I was thinking you might be able to un-exclude the footnotes by removing whichever footnote marker/s in the list apply, if any.

Also, you don't risk anything in changing the settings because you can try out your changes via the Preview function without committing to your change. If the preview SDLXLIFF isn't what you wish, you can just close the preview and click 'Cancel'.

I've never needed to use the above, haven't even played with it but wouldn't hesitate if I needed to. One doesn't always have the chance to know exactly what one is doing when trying to fathom out how to make a file work because one can't always know for example what 3rd party content is in a document and the effect it will have. It's a good idea when one is experimenting with settings, to only change one thing or one definable combination of things at a time and see the effect that has, before trying something else.

Trial and error is also a very good way to learn how things work. Lots of the things I know came from learning by my mistakes ;-))) As I often say, my knowledge is like a lace tablecloth, covers the whole table but is full of holes!

One thing to always remember... Project settings always overrule the profile settings created via File>Options so if you are using an existing project template to set up new projects with this sort of file, you would have to make the filetype settings changes in that before adding the files for translation.

In fact you could use the New project wizard specifically for experimenting with the filetype settings which you would access here...

...before adding the file/s and when successful you could save the project settings as a template at the last stage of the project wizard. Then you could use that project template every time you needed to cope with a file that has these normally excluded footnotes.

All the best,

Ali