System out of memory exception for a mere 10MB file?

Cannot save my file. It's a chemistry patent, yes, loads of images, yes, I've been a user since 6 months or so, I run on 4GB of RAM, but you cannot seriously tell me the program is so flawed that it is unable to export a 10 MB word file. This is absolutely shocking and ridiculous. 

Is there anyway around this, anyone? I did not purchase the program so I can copy from it and paste it in a new word file. 

Any help would be appreciated.  Thank you :(

 

  • Hi

    The 'out of memory' message doesn't mean the file is too big to store. System out of memory refers to RAM. So, have you tried closing the project and Studio and rebooting your system?

    Unknown said:

    Cannot save my file ... unable to export a 10 MB word file 

    I presume you mean you cannot 'save Target as' to Word, rather than being unable to save your SDLXLIFF file.

    Sometimes this can be due to tag content not being transferred properly from Source to Target - so, did you perform a verification with Tag Verifier?

    Also, without opening the project, you could select the file under the Files view, right-click on it, select 'Batch Tasks' then 'Generate Target Translation' in the second popdown menu, as here:

    If that doesn't work...

    Frequently when a Word-based translation fails to save Target it is due to something in the Word file itself. Particularly if it is a large/complex file.

    It is always best to try to save Target as from SDLXLIFF straight away before translation. That way if there is an error or incompatibility, you can go back to the Word file BEFORE translation, to try to solve it. 

    You can still test this - if you set up a new project with the same file and then save Target as, and it fails, this will show it's the Word file that is the problem.

    So, if it is the Word file itself, first of all, if the Word file was in .doc format, save it as .docx 

    You could also save the file with a new filename. This is also a way to remove some unnecessary background content.

    Then repeat the test with a new project. If that works, create a new memory and clean the first translation to it. Then you can pretranslate with that memory and it shouldn't take too long before you have a file that works.

    If, however, that does not work, there are further descriptions of how Word files can be made to work more smoothly, written by , here:

    Word formatting issues

    I hope some of the above is useful to you...

    If not, I'm sure someone more knowledgeable than I will come up with a solution

    All the best,

    Alison

  • Hi ,

    If the suggestion from Ali didn't help try turning off the wysiwyg effect in the Editor. This may also be a problem related to certain fonts, non unicode compliant fonts. So go to File -> Options -> Editor -> "Formatting display style" and set this to "Show all tags but do not show formatting".

    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

  • Hi Paul,

    Interesting suggestion. I wouldn't have thought of that though that is how I always work. I'd much rather see the tags without the formatting because then I can be sure that the correct tags are used in the target. In a recent .idml or maybe xml-based job I was reviewing, the translator had obviously had only the WYSIWYG effect set up and therefore somehow generated new tags that had the same visible effect but triggered error messages. Easy to sort but time-consuming.

    Thanks!
    Ali