RTE while importing XLIFF: No open start element, when trying to write end element

Follow

Volker Weinreich

June 19, 2019 09:56

Hello,

are there any known issues with these RTE while importing XLIFF-files?

java.lang.RuntimeException: javax.xml.stream.XMLStreamException: No open start element, when trying to write end element

At first I thought, the problems where caused by our TMS-Tools, which we are testing now, but then I tested to export XLF and import the zip directly without any changes. And the error still happens. So some exported files are already faulty. There are certain pages which seem to have not a proper structure. In some cases I could locate these pages, but found nothing. I searched for similarities between them. Maybe the error is always provoked by a certain macro, but found nothing.

Okay, we use ST 3.7.6 (with SV 3.7.6), so you will say, we can't do anything. So, we are ready to upgrade and purchase an new licence. But I have no hope that this will solve our problem. 

So, are there any known issues. Or could somenone give me a hint, where we should investigate?

Greetings,

Volker

0

• 

  Roman Serazhiev June 21, 2019 07:07

  Hi Volker, 

  we have had similar errors with certain Translation ZIP files, but there had to be examined on an individual basis to determine the incorrect structure. One of such errors was related to some anchor links producing extra XML tags such as "end-code" and the "end-link-body".

  If you would like us to have a look at the file, please create a support ticket.

  Cheers,
  Roman.

  0

  Comment actions Permalink
• 

  Volker Weinreich June 26, 2019 12:09

  Hi Roman,

  it seems to be the "end-link-body". But simply deleting it, hasn't solved the problem. Do you know, how to handle it?

  

  We are currently preparing for updating and renewing our licences. In that case, I'll open a ticket.

  Greetings,

  Volker

   

  -1

  Comment actions Permalink
• 

  Volker Weinreich June 26, 2019 12:40

  Okay, I have solved the problem. The XLIFF-export-import doesn' like "sup" in a link. It handles it like a link with an embedded image for the body (storage format "<ac:link-body>" and not "<ac:plain-text-link-body>" https://confluence.atlassian.com/doc/confluence-storage-format-790796544.html) That produces the tag "end-link-body" and some other tags like "end-sup". I replaced them by "plain-body" and could re-import the XLIFF. Of course you have to edit the text afterwards.

  

  1

  Comment actions Permalink
• 

  Roman Serazhiev June 27, 2019 06:19

  Hi Volker,

  glad to hear you have solved the issue!

  Roman.

  0

  Comment actions Permalink

Please sign in to leave a comment.