I am just starting to learn how Trados works as a new Project Coordinator.
Presently, the organization I am at is using Acquia to create their webpages. The issue with some of the files is that, I believe it is the
code in the xlf file, how they design the file is creating giant segments instead of manageable segments.
This is just one such segment:
I am trying to find a way to assist my translators in getting a more manageable file. I was wondering if within the Segmentation Rules something could be created to break this down into segments of the areas that do not need to be translated and the actual text that does need translation. If not within Rules would there be another way.
I am trying to determine how to do this for both our in-house translators and for any freelance we might use.
Any suggestions/workaround would be greatly appreciated.
Hi David McDermit
Could you tell what file type this is? Are you exporting bilingual XLIFFs from the CMS (Acquia)?
David McDermit said:I am trying to find a way to assist my translators in getting a more manageable file.
Hopefully it's XLIFF 1.2 and not 2.0. This would allow you to use the embedded content processor and create parser rules for the content ensuring it segments in the appropriate places. You would not use segmentation rules for this.
It looks like Acquia creates 1.2.
"<?xml version="1.0" encoding="UTF-8"?><xliff version="1.2" "
Where can I find information on Parser Rules so I can learn how to use efficiently?
Yes, these *.xlf files are coming to us from another department for each language needed.
I do believe I found the Parsing Rules option and tried it out.
It looks like the tag
is at every spot would need a segment break. Tried getting rule setup for it and no changes.
Chatted with someone here, now back from vacation, and they do not believe that the Acquia XLF files can be parsed into new segments. He suggested seeing if instead of Acquia exporting to us the XLF files but HTML files to translate.
Can you provide a small sample file with a couple of segments in it?
I would like to but when I try to upload the file I keep getting "Error" during the file upload process.
zip it first.
Here is a sample file. It should open up as Simple Chinese.
Yeah, Drupal Translation Management Tools... another ignorance-driven source of completely BAD wannabe-XLIFFs, just like WPML :(
You need to copy the entire content of "source" element into "target" element first and then process the file as XML with embedded HTML.
Unfortunately, that might not be a possibility. There are actually 10 other language files with this one job. I know I would not have time to do all that editing, and the originator would not even trust to go near the file like that.
Well, this is the only sensible way to process it.Blame the Drupal authors, it's their fault - they produce files which have nothing to do with real XLIFF.
You are not the only one having issues with these pretending-to-be-XLIFF crappy files.Search this forum for "WPML" and you will find many desperate posts like yours.
I wouldn't give up so quickly... based on your sample it seems doable. I used three rules:
And can see this:
I'm sure this could be improved with a little effort, but at least it means no need for preprocessing, although the idea from Evzen is a good one and not hard given Studio can do this for you so you won't have to mess with the actual file itself in an Editor.
Paul--thank you. I will look at the coding a bit more.
The source/target change you said can be done in Studio. Really?
Now have to figure out which would be the better way to go so the translators I work with can get right to work on the file.
Interesting. I will have to look at those other posts.