Sdl Trados Studio 2014 Activation Code 151
Sdl Trados Studio 2014 Activation Code 151
here we have four children of the root element and they are all formatted using xml entities. all the translatable text is also formatted using xml entities. studio has the facility to ignore entities and thats fine because at the end of the day we are just mixing xhtml with xml. but having them here makes the xml file very easy to understand because they provide a much more familiar structure to the xml file. if you take a look at the target file which has the same root element and the same children but formatted using the any xml filetype, you can see why we can never hope to get a nice translatable result. so if there are no specific features like this for you to use in your particular project, and i imagine there would be far less xml files that actually fell into the any xml filetype category, then the use of entities, like and here, are not so critical. but in other projects they can be really useful! to me the root element of our second xml example is a little confusing.
so after a long search through the documentation i think its time to let you know that there is no built-in method for actually dealing with the root element itself as translatable text. but this doesnt mean there is no easy way to fix it, and it is this:
ok in that case we cant use the root element as we normally would because the root element is actually the first and last element in the file. so we can take the element and make it the first element but we cant do anything for the last element because it is actually the end of the file. so what we can do is to select the element i showed you previously; the grandparent element and we can then select the children of the element, which is the children element and the translatable text element and copy everything to the target. you then have to go back to the source and find the last element and copy everything from the root element to the translatable text element. now we have created a dummy element and we have blanked out all the translatable text we cannot use. however we also need to look at the other attributes that the filetype automatically copies the translatable attributes for you. so for instance my name is george. would normally be copied as this:
ciao daniel, thanks for your feedback. as for your filetype i think the best way to export is by using xml with shortcodes (line breaks will be ignored by studio) so the cdata and html tags will not be exposed in the xml. if you use the xml parser you can add some simple lines to the rules section that should work. i was also thinking of creating a mime type based on the xml file type so the cat tool would be aware of the file type although i am sure you already have something in place for this. this may seem like adding a lot of complexity for no reason, but if you are creating a xml filetype you will be exposed to issues such as cdata since thats what they are there for in xml. for me, this seems to be the easiest way to avoid them. i hope you have a great weekend, paul.
hi paul, thanks for your feedback. as for your filetype i think the best way to export is by using xml with shortcodes (line breaks will be ignored by studio) so the cdata and html tags will not be exposed in the xml. if you use the xml parser you can add some simple lines to the rules section that should work. i was also thinking of creating a mime type based on the xml file type so the cat tool would be aware of the file type although i am sure you already have something in place for this. this may seem like adding a lot of complexity for no reason, but if you are creating a xml filetype you will be exposed to issues such as cdata since thats what they are there for in xml. for me, this seems to be the easiest way to avoid them. i hope you have a great weekend, paul.
thanks for the reply, the filetype were pretty happy with it, its been set to allow linebreaks. the project we are currently working on is going to use a lot of inline images as it is a blog site for job developers who are at different companies. with this much content, we would have been stuck using something like wordpress multisite for translation as for a developer, xml is like an afterthought as they will never have to deal with it. for this reason, its better to have a filetype for xml for them to deal with.. xml is the best for us but wasnt a support option on studio until the preview release of studio (and we only found out about it today). its worked well for us so far, and we are pleased with the results.