"Object reference not set to an instance of an object" error when reopening GlobalSight-generated XLF files in Studio 2017

Hello,

I have come across the dreaded "Object reference not set..." error message when working in a project with two XLIFF files created with GlobalSight.

A project was created with said XLF files as source files. I started working with them (I opened both files for translation at the same time) and everything went just fine until I closed the files and shut the program. When I reopened Studio and tried to reopen the bilingual files to resume work, I got the aforementioned error message and was unable to open the files :(.

I looked up for similar errors on SDL Community and came across this similar question: https://community.sdl.com/solutions/language/translationproductivity/f/90/t/6227#pi6614filter=all&pi6614scroll=false that was related to Studio 2015.

In order to check if file comments had actually something to do with this error, I unzipped the bilingual files from original project package, opened them with Notepad++ and did the same thing with edited files in current project.

As a matter of fact, comments had been somehow altered in edited files.

This is how one of the SDLXLIFF files looked before editing it in Studio:

 

And this is how it looked after editing and saving it:

 

Thus, I tried manually copying and pasting the header from the older file into the edited file and apparently it worked. I opened both files, everything was just as I left it, did some edits, saved, and reopened them seamlessly. What I still don't know is if Studio will be making the same joke when I close and reopen these files tomorrow. Thus, I would like to know if anyone knows how to prevent this kind of error from ever happening again.

BTW, I was told that, from Studio 2014 onwards, in order to batch open several XLIFF files as I did in this project, I had to go to File > Settings > File types > XLIFF > Settings and check the second checkbox ("Do not store segmentation info in translated file" or something similar), and that is exactly what I did before doing anything with this files. Are there any other settings that must be adjusted in order to work with this kind of files?

Many thanks in advance for any help.

  • Hello Carmen,

    Can we see the original source file to test this?  You can email it to pfilkin@sdl.com if this is ok?

    Unknown said:
    BTW, I was told that, from Studio 2014 onwards, in order to batch open several XLIFF files as I did in this project, I had to go to File > Settings > File types > XLIFF > Settings and check the second checkbox ("Do not store segmentation info in translated file" or something similar), and that is exactly what I did before doing anything with this files. Are there any other settings that must be adjusted in order to work with this kind of files?

    This is not correct.  You don't need to check any boxes to be able to open all the files at once.  That checkbox is just to prevent segmentation information from being stored in the target file as some systems won't know what to do with this, not do they want it anyway.  Frankly I think this should be the default.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hello Paul,

    Thank you for your prompt answer. The original source file was an Excel file that was then processed through GlobalSight into an XLIFF file for translation. I assume you mean the latter, is that right?

    And sorry, I did not explain myself well. Of course there is no need to check/uncheck any boxes to open several files at once. What I meant is that I had been told that opening several SDLXLIFF coming from XLIFF-based without ticking this box on could lead to potential issues caused by that segment information storage in target file. And yes, if this can indeed generate compatibility problems, this option should definitely be the default? Any chance to forward this thought to the developer team so that this box is checked by default in future releases/updates of Studio?

    Thank you!

    Best regards,

    Mamen
  • Hi Mamen,

    Unknown said:
    And yes, if this can indeed generate compatibility problems, this option should definitely be the default? Any chance to forward this thought to the developer team so that this box is checked by default in future releases/updates of Studio?

    You should vote for this idea...

    community.sdl.com/.../storing-segmentation-information-in-the-translated-file

    Your post reminded me of this yesterday so I create the idea for it.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub