| Pages in topic: < [1 2 3] > | Trados Studio - invalid character - generate target file Thread poster: Tom Fennell
|
|---|
| Many thanks!!! | Nov 20, 2013 |
I got the same error message and I used Patrick's solution which worked at first attempt. What a relief!
Regards,
Judith
| | | | Pavel Janoušek 
Czech Republic
Local time: 07:45
Member (2007)
German to Czech
+ ...
| Used Notepad ++ to remove the invalid character | Mar 4, 2014 |
In my case, it was a non-breaking hyphen that caused the error. I replaced in the SDLXLIFF file with a standard hyphen and voila - the error disappeared.
Thank you very much!
| | | | | Thank you, CAT-wizzards! | Apr 15, 2014 |
In my case there was a non-breaking hyphen. Found it in the original, replaced it with „-”, uploaded the updated document in Studio. Worked like a charm.
Thank you!
| | | | Elina R-K
Finland
Local time: 08:45
English to Finnish
+ ...
| Use an XML validator to find the problem | May 12, 2014 |
This may be old news by now, but as this thread was the first Google hit when I searched for a solution to this problem earlier today, I might as well share my experience - dealing with this problem is really not that complicated even if, as in my case, Trados refuses to give any indication as to where the problematic segment might be:
1. Create a backup copy of the SDLXLIFF file and save it as an XML file.
2. Use an XML valida... See more This may be old news by now, but as this thread was the first Google hit when I searched for a solution to this problem earlier today, I might as well share my experience - dealing with this problem is really not that complicated even if, as in my case, Trados refuses to give any indication as to where the problematic segment might be:
1. Create a backup copy of the SDLXLIFF file and save it as an XML file.
2. Use an XML validator. Validome's free validator (http://www.validome.org/xml/validate/) worked for me. (Just use the Browse button to locate the file on your computer, then hit Validate.)
3. The validator tells you where the problem is.
4. Fix the error in the source document and retranslate it.
All this took less than 10 minutes once I knew what to do. ▲ Collapse
| | |
|
|
|
| Studio 2011 won't even start | Jun 13, 2014 |
Hi all,
Thanks for the very useful and detailed discussion. But unfortunately I am unable to make heads or tails of it
I am working on a large file and when I tried to generate a target translation file, it returned an error saying there was an invalid character at position X1E 53(
The worst part is I am unable to figure out ... See more
| | | | Dan Lucas
United Kingdom
Local time: 06:45
Member (2014)
Japanese to English
| Failed to save target content | Feb 21, 2015 |
I have just been hit by this problem, 20% of the way through a large J-E project. The specific error is:
"Failed to save target content: Name cannot begin with the < character, hexadecimal value 0x3C. Line 2, position 4127."
The error did not manifest itself immediately I started translating, it only appeared recently. Unfortunately I don't know which edit to which segment sparked the problem, so I cannot easily roll this back.
Here is what I ha... See more I have just been hit by this problem, 20% of the way through a large J-E project. The specific error is:
"Failed to save target content: Name cannot begin with the < character, hexadecimal value 0x3C. Line 2, position 4127."
The error did not manifest itself immediately I started translating, it only appeared recently. Unfortunately I don't know which edit to which segment sparked the problem, so I cannot easily roll this back.
Here is what I have tried so far.
1) In this SDL knowledgebase article it says:
Deleting invalid characters directly in SDLXLIFF document:
Create a backup copy of the existing .sdlxliff document.
Open the .sdlxliff document in an XML Editor that includes XML validation.
Run the XML validation to find the invalid characters.
Delete these characters and save your changes.
2) I downloaded and installed XML Copy Editor, which has a validation function. When I run this on the sdlxliff file, XML Copy Editor says:
"Error at line 1, column 174: no declaration found for element 'xliff'"
These are the first 180 or so characters of line 1:
<?xml version="1.0" encoding="utf-8"?><xliff xmlns:sdl="http://sdl.com/FileTypes/SdlXliff/1.0" xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2" sdl:version="1.0"><doc-info xmlns="http://sdl.com/FileTypes/SdlXliff/1.0">
Character 174 is the 'd' of the doc-info tag above.
So it almost looks as if the XML Copy Editor can't find a schema or DTD against which to validate the document. I'm guessing it should be looking at that sdl.com URL in the first line, but that throws a 404 error.
At this point I can't even work out how to validate the file, let alone fix it. Has anybody got any pointers / advice?
TIA
Dan
[Edited at 2015-02-21 15:27 GMT] ▲ Collapse
| | | | | Maybe try this solution... | Feb 21, 2015 |
... that I have seen to be of help in the past. Remove any Studio comments in the SDLXLIFF file and try again.
If it still fails can you first check that you can open the source file using the single file project approach and immediately save the target without using a TM or translating anything? If that fails then the problem is in the source file and you will need to isolate that first.
If it doesn't fail then try pretranslating the file from your TM and see if it w... See more ... that I have seen to be of help in the past. Remove any Studio comments in the SDLXLIFF file and try again.
If it still fails can you first check that you can open the source file using the single file project approach and immediately save the target without using a TM or translating anything? If that fails then the problem is in the source file and you will need to isolate that first.
If it doesn't fail then try pretranslating the file from your TM and see if it works this time?
Regards
Paul ▲ Collapse
| | | | Dan Lucas
United Kingdom
Local time: 06:45
Member (2014)
Japanese to English
SDL Support wrote:
Remove any Studio comments in the SDLXLIFF file and try again.
Paul, thanks for the suggestion. Do you mean open Studio, delete any comments and save the file, or manually edit the SDLXLIFF file in some way?
Dan
| | |
|
|
|
| I meant open Studio... | Feb 21, 2015 |
... not edit the SDLXLIFF itself.
Regards
Paul
| | | | Dan Lucas
United Kingdom
Local time: 06:45
Member (2014)
Japanese to English
| Deleting comments seems to have resolved target document failure | Feb 22, 2015 |
Paul, I had two comments in the SDLXLIFF file. I deleted these comments and now I can successfully generate a target file, which is great news. Thank you very much. I can resume translating the source with some confidence that I will be able to deliver a document at the end of the process.
That's the positive outcome. On the other hand, I spent most a day trying to resolve this "feature" in SDL Trados Studio and in future I do want to be able to use comments in my SDLXLIFF fi... See more Paul, I had two comments in the SDLXLIFF file. I deleted these comments and now I can successfully generate a target file, which is great news. Thank you very much. I can resume translating the source with some confidence that I will be able to deliver a document at the end of the process.
That's the positive outcome. On the other hand, I spent most a day trying to resolve this "feature" in SDL Trados Studio and in future I do want to be able to use comments in my SDLXLIFF files. I have two questions.
1) Does SDL have any idea how and why comments affect target output in these cases? That you were able to diagnose the problem and specify a fix so precisely suggests that I'm not the only one to have been affected.
2) With regard to my (failed) attempt to validate the SDLXLIFF file and find the invalid character/s as per the SDL KB article referenced earlier, would you care to briefly guess why that didn't work? Do I need to attach/associate schemas with the SDLXLIFF file to allow the XML reader to parse the file properly?
Thank you again
Dan ▲ Collapse
| | | | | No solid resolution to this one yet. | Feb 22, 2015 |
Dan Lucas wrote:
1) Does SDL have any idea how and why comments affect target output in these cases? That you were able to diagnose the problem and specify a fix so precisely suggests that I'm not the only one to have been affected.
I have seen this once or twice and in these cases the users figured this out before sending me the file. So I have not been able to see what's causing this yet. If you can send me a file that is affected like this please do. It's not a reproducible problem with all files so I think there has to be something file specific.
Dan Lucas wrote:
2) With regard to my (failed) attempt to validate the SDLXLIFF file and find the invalid character/s as per the SDL KB article referenced earlier, would you care to briefly guess why that didn't work? Do I need to attach/associate schemas with the SDLXLIFF file to allow the XML reader to parse the file properly?
I have no idea... probably nothing to do with the schemas at all. But if you can share the file I'll be very glad to take a look?
Regards
Paul
SDL Community Support
| | | | Eva Buol
Spain
Local time: 07:45
Member (2015)
French to Spanish
+ ...
| problem when converting the TXT to "translatable" in trados 2014 | Apr 5, 2015 |
Hi,
I hope someone can help me.
My problem is: I have a TTX file that I want to translate in Traods 2014, but when I click "Convert this file in translatable" an error occurs and I cannot open the file. The error is : invalid caracter lin 25 position 356".
I don't know how to fix it.
If you could help me It would save my life!!
Thank you in advance
Eva
| | |
|
|
|
| Thanks so much! | Apr 6, 2015 |
I got the same error and I tried Patrick's solution which worked fine.
| | | | | Simple solution worked for me | Apr 17, 2015 |
Patrick Stenson wrote:
Hi
First of all, thanks Tom for your fantastic explanation and help!
I had this error this morning, and after battling for a while I luckily stumbled upon a simple solution which I thought I'd share. As you say, when clicking on the error in Studio, nothing appears to be 'wrong' with the segment it takes you to. What I did (and don't ask me why I did it) was to delete the segment immediately above that. I then tried to Save As Target again, at which point I got the same error but that took me to a different segment. Again, I deleted the segment directly above it.
(When I say 'deleted the segment', I mean I removed the translated text from the target side).
Then, when I did Save As Target, it worked!
I then simply went back to the segments I'd deleted, found them in the TM and copied and pasted them manually into the target file.
Worked for me! Thanks a lot, it saved me quite a bit of trouble when fixing this problem!
| | | | | Solved it by removing comments | Jun 26, 2015 |
As earlier suggested on this thread, I also solved it by removing the comments I added in the sdlxliff file. Thank you!!
| | | | | Pages in topic: < [1 2 3] > | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Trados Studio - invalid character - generate target file | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
| | Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
