• State Verified Answer
  • Replies 11 replies
  • Subscribers 370 subscribers
  • Views 7799 views
  • Users 0 members are here
Options
Related

Application to extract an analysis from a standalone SDLXLIFF

Paul

The scenario is this.  You are sent an sdlxliff to translate without a TM and it has already been pretranslated and payments terms stated on the basis of what's in the file.  How do you determine what this is in summary so you have the basis for questionning the payment if necessary?  I ask this because I had such a query this morning and couldn't solve it easily.

I could create a new TM from the sdlxliff and rerun the analysis from this, but the results are of course not correct because we don't have the basis for a proper comparison.

So I created a small spreadsheet on the basis of the report that comes from the SDLXLIFF Converter and then added a couple of columns to count the words and group the matches.  Clearly the wordcount will also be off and the analysis still doesn't match exactly, but it gave me an idea for another application.  So I'm adding this one too for comments.  A proper application that could use the proper analysis mechanisms would be quite cool I think.

I attached the spreadsheet too so you can see what I mean... it was actually useful for the user even with it's obvious flaws.

Regards

Paul

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear? 
Tell us what you need in our Community Solutions Hub

Analysis Spreadsheet.xlsx
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi Paul,

    I guess "pretranslated" means, that the SDL-XLIFF file you got has all 100% and CM pretranslated? Or are ther also Fuzzy matches pretranslated?

    First of all: If we get a pretranslated SDLXLIFF-File and analyse it against an empty TM, we get "wrong" results. Technically the results are correct (0 Matches as the TM is empty), but it does not take the pretranslated TUs into account. That means, the analysis does not reflect the "real world effort".

    My first idea was to create an empty TM, import the SDL-XLIFF file and re-analyse it. That works fine.

    Beside this, you can also go into the "Projects" or "Files" view in Studio, select the projct or a specific file. Check the "Confirmation Statistics". This gives you a detailed view of the situation: How many segments are untranslated / draft / translated / Rejecteed / Approved. You can switch between Percentage, Counts or both together in the view.

    Is this not enough / what you're client wanted?

    Cheers,

    *Stefan.
Reply
  • 0

    Hi Paul,

    I guess "pretranslated" means, that the SDL-XLIFF file you got has all 100% and CM pretranslated? Or are ther also Fuzzy matches pretranslated?

    First of all: If we get a pretranslated SDLXLIFF-File and analyse it against an empty TM, we get "wrong" results. Technically the results are correct (0 Matches as the TM is empty), but it does not take the pretranslated TUs into account. That means, the analysis does not reflect the "real world effort".

    My first idea was to create an empty TM, import the SDL-XLIFF file and re-analyse it. That works fine.

    Beside this, you can also go into the "Projects" or "Files" view in Studio, select the projct or a specific file. Check the "Confirmation Statistics". This gives you a detailed view of the situation: How many segments are untranslated / draft / translated / Rejecteed / Approved. You can switch between Percentage, Counts or both together in the view.

    Is this not enough / what you're client wanted?

    Cheers,

    *Stefan.
Children
  • 0 in reply to Stefan Gentz

    Unknown said:

    I guess "pretranslated" means, that the SDL-XLIFF file you got has all 100% and CM pretranslated? Or are ther also Fuzzy matches pretranslated?

    First of all: If we get a pretranslated SDLXLIFF-File and analyse it against an empty TM, we get "wrong" results. Technically the results are correct (0 Matches as the TM is empty), but it does not take the pretranslated TUs into account. That means, the analysis does not reflect the "real world effort".

    My first idea was to create an empty TM, import the SDL-XLIFF file and re-analyse it. That works fine.

    Hi Stefan,

    Yep... all kinds of matches similar to the matches in the spreadsheet... actually I just changed the text.  Using the TM approach doesn't work at all because you only get CM, 100% and New.  You don't get the fuzzies, and of course the CM and 100% may not have been this in the sdlxliff.

    Unknown said:

    Beside this, you can also go into the "Projects" or "Files" view in Studio, select the projct or a specific file. Check the "Confirmation Statistics". This gives you a detailed view of the situation: How many segments are untranslated / draft / translated / Rejecteed / Approved. You can switch between Percentage, Counts or both together in the view.

    Is this not enough / what you're client wanted?

    This is also not helpful.  Remember, I only have the sdlxliff so there has been no analysis carried out on this for Studio to generate this information.  The user has been given a pretranslated sdlxliff file and been asked to finish it off.  There is also no analysis included, only a report that contains a count for payment.  I know the user should really have a discussion with the client because this is hardly fair, but I thought that if there was a quick way to extract this informaiton from the sdlxliff then you have the basis for a discussion if it's really needed.

    This isn't the first time I have come across this scenario which is why I put together the spreadsheet, but it would be better to be able to set the bands properly and summarise the content neatly in the same way we do in the analyse reports... albeit not by running a analysis, rather reading in an already pretranslated sdlxliff.

    Cheers

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub