Foro teknikoak » MemoQ support »
'unexpected token ' error during *.sdlppx import
Haria hasi duena: Peter Zauner
Peter Zauner
Peter Zauner  Identity Verified
Australia
Local time: 09:25
Bazkidea (2010)
Alemanatik Ingelesara
+ ...

Foro honetako moderatzailea
Jan 27, 2019

All,

I am using memoQ 7.8.4.
On a recent job, a customer sent me a *.sdlppx file, which I imported using the "Import Package" function. The customer had packaged two *.docx files and a TM.
However, while one of the two *.docx files imported correctly, the other one failed to import. The error message read: '10' is an unexpected token, The expected token is "" or "". Line 1, position 10.
At the time, I didn’t understand what this meant and my customer's project m... See more
All,

I am using memoQ 7.8.4.
On a recent job, a customer sent me a *.sdlppx file, which I imported using the "Import Package" function. The customer had packaged two *.docx files and a TM.
However, while one of the two *.docx files imported correctly, the other one failed to import. The error message read: '10' is an unexpected token, The expected token is "" or "". Line 1, position 10.
At the time, I didn’t understand what this meant and my customer's project manager didn't know what to do either. As a result, after translating the one *.docx file that imported correctly, I was not able to export a *.sdlrpx package. Instead, the 'Export (stored path)' and 'Export Dialog' options both created a *.docx file.

I have since found this thread (https://bel.proz.com/forum/sdl_trados_support/191768-unexpected_token.html) and have concluded that the 'unexpected token ' error comes from SDL and should have been resolved in the source *.docx file before creating the *.sdlppx. Is this correct?

I probably should have never accepted the job until the PM had fixed this error.

A related question is:
When I used the 'Export Bilingual - option memoQ XLIFF [Plain XLIFF for other tools]' option, MemoQ created a *. mqxliff file, that the PM could not open.
Why is a supposedly 'plain XLIFF for other tools', named *. mqxliff? Could it be converted to a truly 'plain' XLIFF that the PM can open in SDL?

Any comments are highly welcome.

Thank you,

Peter

[Edited at 2019-01-28 12:18 GMT] ▲ Collapse
 
Andriy Yasharov
Andriy Yasharov  Identity Verified
Ukraina
Local time: 02:25
Bazkidea (2008)
Ingelesatik Errusierara
+ ...
extension .xlf is needed Jan 27, 2019

Peter Zauner wrote:

Could to be converted to a truly 'plain' XLIFF that the PM can open in SDL?



When using 'Export Bilingual - option memoQ XLIFF' save your file with extension .xlf instead of *. mqxliff or change the file extension after the export. Then Studio will be able to open that file.

[Edited at 2019-01-27 13:57 GMT]
 


To report site rules violations or get help, contact a site moderator:

Foro honetako moderatzailea
Maya Gorgoshidze[Call to this topic]
Peter Zauner[Call to this topic]
Prachya Mruetusatorn[Call to this topic]

You can also contact site staff by submitting a support request »

'unexpected token ' error during *.sdlppx import






TM-Town
Manage your TMs and Terms ... and boost your translation business

Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.

More info »
Pastey
Your smart companion app

Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.

Find out more »