• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 431 subscribers
  • Views 2857 views
  • Users 0 members are here
Options
Related

SDL Studio 2015 target language processing - Loading 20 target language specific sets of source xml files with almost identical content for each langauge into SDL Studio 2015 , processing efficiency tips and suggestions please...

kevin spence

In Studio 2015 if a customer sends through separate sets of xml files for each of the 20 target languages in a project what is the most efficient way to load in each set of target language XML files for translation processing please? Are there any apps or methods you can recommend to reduce the need to load each set of files in one by one? The language specific xml files do contain a target language reference in their titles. Any suggestions very much appreciated, many thanks.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi Kevin,

    If the xml files are all the same aprt from the language then I think the best way to do this is create one project with one source file and all the target languages.  Then see whether you can use this setting to manage the target language attribute:

    That would save you loads of time.

    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

  • Former Member
    0 Former Member
    Hello Kevin,
    We have this issue frequently.
    One of the ways that we handle this is to load ALL source files in during project creation, but keep them within separate folders (1 folder for DE, 1 folder for FR, et al).
    Then, batch task 'Convert to translatable format | Copy to Target languages'. Once that is completed, go thru the Studio project and delete the folders that do not apply for the given language (When you have DE language files visible, delete all BUT DE; when you have FR language files visible, delete all BUT FR, et al).

    This allows you to go back to the project level and run your analysis, create packages, without having to do this 20 separate times.

    We have clients that have different source files for different languages, and sometimes the content can change, so it's difficult to use one source file for all the languages.

    I hope this helps!
    Best, Mindy
  • 0 in reply to Former Member
    Great Mindy thanks for the suggestion, I think we may eventually develop something to help with this or possibly use a single source approach as suggested in the previous post but your solution is probably the best option for now. Just too clarify I assume the best and only way to delete the folders that are not required is one by one via the 'Files' area using the individual language view which may still involve deleting 400 odd folders one by one? There is no way I can delete the folders as a group or by deleting them from the network locations where I might be able to select more than one at a time? Once again thanks for your help on this.
  • Former Member
    0 Former Member in reply to kevin spence
    Hi Kevin, you are correct. The only way I have figured out how to delete, if you use folders, is you have to delete each folder one at a time.

    OR, you can leave all the folders as they are, and only WORK in the folder that you need (i.e. When in the French files list, leave all other language folders in there, but only do batch tasks on the files you want to work in). Although, then you will have to do 'Analyze' and 'Create Studio package' 20 times, so it's a matter of which one you think will save you the most time - create 20 Studio projects or add them all at once and then risk working in the wrong language folder during processing.

    I wonder if Studio would recognize it if you went into the actual Studio document folder (not deleting the files IN Studio, but going into the project folder), and deleted the files you didn't want, if that makes any sense? I'm not sure if that would cause issues or not. Might be worth a test?
  • 0
    Hello Kevin and Mindy,
    As we translate a lot of such "bilingual XML", mainly from CMS, we developed a plugin for our internal needs to prepare the files for the corresponding languages, exactly as you describe. The plugin adds a new file type, which exactly looks like the custom XML one + a specific setting page for language mapping.
    Studio recognizes the language in the file name through a regular expression and the files are then copied in the corresponding folder through the common "copy to target languages" batch task. You have nothing to erase yourself.
    The plugin is not in the SDL AppStore yet but you can send me an email at sebastien.desautel@rws-group.de and we could check if it corresponds to your expectation.

    Kind regards
    Sébastien Desautel