David McDermit

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.

I do believe I found the Parsing Rules option and tried it out.  

It looks like the tag &#13 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.

David McDermit

zip it first.

JobID1711_en_zh-hans.zip

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.

David McDermit

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.

Evzen

Interesting.  I will have to look at those other posts.

David McDermit said:

The source/target change you said can be done in Studio.  Really?

I believe, Paul meant the processing of HTML embedded inside XML, not the source -> target copy.
At least I'm not aware of a way how Studio would do that for you.

David McDermit

David McDermit said:

The source/target change you said can be done in Studio.  Really? 

Well, to get the source to target is trivial, and easily accomplished across all files in your project in one go if you install something like the SDL Trados Toolkit from the AppStore. Then all you do is save the target files and you'll have XLF files with the source copied to target which you can use for the approach Evzen suggested.  A bit of extra work but perhaps easier because you can use the HTML filetype as a means to handle the embedded content without having to create all the rules.

But if your files don't get much more complicated than the example you provided then the embedded content filter in the XLIFF filetype may be the simplest approach as it won't require any workarounds.

David McDermit

David McDermit said:

The source/target change you said can be done in Studio.  Really? 

Well, to get the source to target is trivial, and easily accomplished across all files in your project in one go if you install something like the SDL Trados Toolkit from the AppStore. Then all you do is save the target files and you'll have XLF files with the source copied to target which you can use for the approach Evzen suggested.  A bit of extra work but perhaps easier because you can use the HTML filetype as a means to handle the embedded content without having to create all the rules.

But if your files don't get much more complicated than the example you provided then the embedded content filter in the XLIFF filetype may be the simplest approach as it won't require any workarounds.