• State Suggested Answer
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 46 subscribers
  • Views 2397 views
  • Users 0 members are here
Options
Related

Are there any Apps/SDL Studio features that would enable multiple SDLXliff files to be glued into a single file in SDL Trados Studio 2015? I need to reduce the number of source files I am feeding actually loading into groupshare....

kevin spence

Are there any Apps/SDL Studio features that would enable multiple SDLXliff files to be glued into a single file in SDL Trados Studio 2015? I need to reduce the number of source files I am actually loading into groupshare and the inbuilt merge feature during source loading doesn't help. I can see tools that can split and merge SDLXliff files but I would  need to do the opposite (merge then split again after translation) on the files once I have locally created some SDLXliff files to use as the source for translation. Any ideas much appreciated, this would help as a work around to avoid issues publishing large numbers of files to groupshare which is being dealt with separately via SDL technical support. Another option could be to batch the source Dita xml files before loading into studio if a reliable tool exists that can do this. Any suggestions very much appreciated, many thanks.
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Hi Kevin,

    Why doesn't merging when you create the project work for you?

    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

  • 0 in reply to Paul

    Hi Paul, merging at project creation does what it is supposed to do I think but it doesn't seem to help address the performance issues we are having with groupshare which relates to numbers of files that can be published at anyone time. As mentioned this is something we are working with the SDL support team so my question is essentially in the context of a short/medium term workaround.

    Anyway as an example if we try to publish 200 xml files into 20 languages the groupshare publish fails and the processing takes much longer, if I use the merging option at project creation the same issue remains but if I combine all the xml files together into a couple of larger xmls before loading the project the processing happens much more quickly and it loads on to groupshare with out any problems.

    The issue I have is when I combine the xmls the reverse separation process isn't 100% reliable hence I wondered if there were any tools/apps that could combine a set of source sdlxliffs or something along those lines and then I might load these? Hence perhaps the reason the inbuilt merge option doesn't seem to help is potentially because it might be more of a virtual merge and perhaps the source files are not actually combined when the project is loaded? When I actually combine the xmls prior to creating the project they process fine and I can publish much larger projects to groupshare.

    Any ideas much appreciated, processing files in small source/language sets has been proposed but is not a great solution for us hence I was looking at some alternatives.

    Many thanks
  • 0 in reply to kevin spence
    Hi Kevin,

    I guess you could do two operations.

    1. Create the projects in Studio and merge the files
    2. Take the merged sdlxliff files and create a new project with just these

    That would allow you to work with merged sdlxliff files but it feels like an odd workaround. Is this what you were trying to achieve?

    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

  • 0 in reply to Paul
    Hi Paul, yes it does sound odd but if the end result is that I can load 2 source files into Studio instead of 200 that should provide a work around for us I think and mean we can publish to groupshare more easily in the short term. I will test and let you know if it works ok. Thanks
Reply Children
  • 0 in reply to kevin spence

    Hi Kevin,

    I spoke to the product team in the meantime and this is a known issue that is highly dependent on server performance and the type of files.  So we have examples where 5000 files works fine, and then we have seen some where only a few hundred could cause a problem.  There is a KB article on this problem.

    So the current resolution may be one or more of the following:

    1. the one I gave you by merging the files and recreating the project with the merged files.
    2. reducing the number of files added at a time, so multiple projects
    3. increase the SQL Server performance

    Hope something helps here until we have a more permanent solution for this (no timelines yet...)

    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