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.
Error by analizing and pretranslating .xml in Studio
Thread poster: Francisco Mar Rubio (X)
Francisco Mar Rubio (X) Switzerland Local time: 23:52 English to Spanish + ...
Jul 4, 2011
Hi everybody,
I am new in Studio 2009. So far so good, but today I tried to create a project with a .xml file and when I clicked on "Analyse and Pretranslate", after the whole process, it appear an error mark in both Analysing and Pretranslating. Of course nothing has been translated (although I have a TM and Google Translator enabled).
Previously I had created a new .xml file type with the .xsd the client sent me, but I do not know what else to do...
I am new in Studio 2009. So far so good, but today I tried to create a project with a .xml file and when I clicked on "Analyse and Pretranslate", after the whole process, it appear an error mark in both Analysing and Pretranslating. Of course nothing has been translated (although I have a TM and Google Translator enabled).
Previously I had created a new .xml file type with the .xsd the client sent me, but I do not know what else to do...
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
sandymess Cameroon Local time: 22:52 Member (2010) English to French + ...
Need help for same reasons
Jul 5, 2011
Please, can somebody provide us help! What to do when tags revealed some errors and the target document cannot be convert back
[Modifié le 2011-07-05 02:47 GMT]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
RWS Community United Kingdom Local time: 23:52 English
Can you provide more details of the error?
Jul 5, 2011
Hi,
I'm not sure whether you are referring to QA error messages, or problem error messages? If you press F8 to check the document after translation what messages do you get?
Regards
Paul
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Francisco Mar Rubio (X) Switzerland Local time: 23:52 English to Spanish + ...
TOPIC STARTER
Problem solved
Jul 5, 2011
The problem was that I created the project with all the "file types" active, but I needed just one personal type of .xml (the one generated by .xsd). Now that I have created the project deactivating the rest of file types, it works perfectly!!!
THanks!!
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
RWS Community United Kingdom Local time: 23:52 English
You should not have to do this.
Jul 5, 2011
I think you are missing the correct file detection settings in your custom xml filetype and this is probably why the incorrect xml filetype was used in the first place.
But your solution also works
Regards
Paul
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
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.
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.