• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1996 views
  • Users 0 members are here
Options
Related

Allow source editing & saving edited source

Naoko Jones

Hi Community,


We have an interesting situation where a client requested that we reflect any translation changes made by In-Country-Reviewer/SME into Source. This request came in after we delivered the translation.

So now, we wanted to re-prep, with "Allow source editing" option on during project creation. Applying perfect matches and TM was a terrible solution here. So we just replaced the target SDLXLIFF with the target SDLXLIFF from the original translation project (after project creation), hoping that still works for what we are trying to achieve, but no it didn't work. We then run a quick test- edit source, save SDLXLIFF, go to File > Advanced Save > Save Source as, but this option is grayed out.

We can edit the source but cannot save the edited source. Does anyone know how to save the edited source?

Thanks,

Naoko
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi

    I'm not completely clear on your process. But would this work?

    - Create a new project with the amended target file as source
    - add the same TM using AnyTM
    - make the necessary changes and save target (to get the updated source)

    If you have not retrofitted the translation changes then when you translate to fuzzy you should find all the emended segments and be able to correct them easily.

    Sorry if I missed the obvious here!

    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

  • 0 in reply to Paul

    Hi Paul,

    Thanks for responding. I did try responding to you on Friday, but I think it timed out.

    What we are working with:
    Source: xlsm
    Parser used : Excel 2007 v 2.0.0.0 file type in TMS
    A ton of soft returns in cells, but they were treated as segment break in the original prep by TMS


    Our goals:
    Update TM with ICR edits in both source and target
    Since updating TM is our goal, we do not want to change the original segmentation too much
    Deliver XLSM with ICR edits in both source and target (regardless of merged as bilingual or not)

    Where we are right now:
    Recreate a studio project with Allow source editing option on
    Modified segmentation to include soft returns, to remove colon as segment break in TM
    Apply PM and apply TM to non-PMed segments, leaving about 10 egments new and fuzzy

    Two options we are considering:
    Take the newly created project and linguists fix new and fuzzy before implementing ICR changes
    We want to save both edited source and target in XLSM format at the end of ICR edits
    Advanced Save for source is grayed out, i.e. TM can be updated but can't generate the udpated XLSM in source English

    OR:
    Replace the target SDLXLIFf with the ones from the original translation
    We don't need to rely on TM application, but we can only save the target with ICR edits in XLSM
    Advanced Save for source is grayed out, i.e. TM can be updated but can't generate the udpated XLSM in source English


    Some combination of things are making saving source disabled.
    I think I could save source in XLSM when Spreadsheet ML v. 1 file type is used, with the default Studio segmentation
    Can't save source when soft returns are segment break?
    Can't save when target SDLXLIFF are replaced (more understandable)

     

    That's all I have for now. Thanks for your help.

    Thanks,

    Naoko
Reply
  • 0 in reply to Paul

    Hi Paul,

    Thanks for responding. I did try responding to you on Friday, but I think it timed out.

    What we are working with:
    Source: xlsm
    Parser used : Excel 2007 v 2.0.0.0 file type in TMS
    A ton of soft returns in cells, but they were treated as segment break in the original prep by TMS


    Our goals:
    Update TM with ICR edits in both source and target
    Since updating TM is our goal, we do not want to change the original segmentation too much
    Deliver XLSM with ICR edits in both source and target (regardless of merged as bilingual or not)

    Where we are right now:
    Recreate a studio project with Allow source editing option on
    Modified segmentation to include soft returns, to remove colon as segment break in TM
    Apply PM and apply TM to non-PMed segments, leaving about 10 egments new and fuzzy

    Two options we are considering:
    Take the newly created project and linguists fix new and fuzzy before implementing ICR changes
    We want to save both edited source and target in XLSM format at the end of ICR edits
    Advanced Save for source is grayed out, i.e. TM can be updated but can't generate the udpated XLSM in source English

    OR:
    Replace the target SDLXLIFf with the ones from the original translation
    We don't need to rely on TM application, but we can only save the target with ICR edits in XLSM
    Advanced Save for source is grayed out, i.e. TM can be updated but can't generate the udpated XLSM in source English


    Some combination of things are making saving source disabled.
    I think I could save source in XLSM when Spreadsheet ML v. 1 file type is used, with the default Studio segmentation
    Can't save source when soft returns are segment break?
    Can't save when target SDLXLIFF are replaced (more understandable)

     

    That's all I have for now. Thanks for your help.

    Thanks,

    Naoko
Children