This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
VIA AILooking for an interpreter?
Remoto by ProZ.com connects you with an identity-verified interpreter by video or phone in about 60 seconds — 300+ languages, on demand or booked ahead.
Try Remoto »
I've a problem when converting my XLIFF file to original file.
The following message appears:
"(Fatal error) 2:86231 the element type "text:span" must be terminated by the matching end-tag "
I've checked (twice) each segment and I've also made a tag analysis and nothing appears.
Yet, this error message still appears when I want to convert my document back to the original .odt.
I've a problem when converting my XLIFF file to original file.
The following message appears:
"(Fatal error) 2:86231 the element type "text:span" must be terminated by the matching end-tag "
I've checked (twice) each segment and I've also made a tag analysis and nothing appears.
Yet, this error message still appears when I want to convert my document back to the original .odt.
Does anyone know what can I do?
I have to hand back this document to a client as soon as tuesday. Thank you for your help.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Piotr Bienkowski Poland Local time: 17:55 English to Polish + ...
Try Maxprograms technical support
May 2, 2011
CaroleTrad wrote:
Hello,
I've a problem when converting my XLIFF file to original file.
The following message appears:
"(Fatal error) 2:86231 the element type "text:span" must be terminated by the matching end-tag "
I've checked (twice) each segment and I've also made a tag analysis and nothing appears.
Yet, this error message still appears when I want to convert my document back to the original .odt.
Does anyone know what can I do?
I have to hand back this document to a client as soon as tuesday. Thank you for your help.
Carole
Send the original, plus the XLIFF file, and the skeleton file if it is not embedded in the xlf file to [email protected] . They should be able to help.
Hope this helps,
Piotr
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
That kind of error usually happens when you merge or split segments with tags despite the warning.
Convert the source file to XLIFF again and re-translate using your TM database. Translate the segments that don't have matches and finally convert back to original format.
If you still have problems, send the source file & translated XLIFF to [email protected]
Regards,
Rodolfo
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.