Scribus, properties of type settings

Question

Scribus is and open source DTP program, and kind of XML file. 
 However (in Studio 2014 SP2) I tried to create a new file type, importing a scribus file. I tried various settings, however, after using this setting, the resulting bilingual file was always empty. 
 I tried some workaround exporting scribus to pdf. The result was catastrophic: either the word file (generated by Studio), had additional spaces within the words, and there were spaces missing between two words, or (generated with Adobe Acrobat) the file in terms of layout and formatting was unusable 
 Does somebody have an idea?

Paul · Accepted Answer

Hi Beate, 
 I thought it would be helpful if I just recorded what I did so you could follow the process and see how I go about this. There are many ways to tackle this but I find this works for me... I hope it helps! I also attached my settings file here so you can also use this if you like: 
 https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/scribus-v1.sdlftsettings 
 
 Regards 
 Paul

Paul · Answer

Hi Beate, 
 
I guess the best thing is if you can share a sample of one of these files? If it is xml then it's got to be down to the parser rules required to get at the text... maybe it's all in the attributes or something like that. If you can share a sample, or even share your file, then we can help. 
 
Regards 
 
Paul 
pfilkin@sdl.com

Paul · Answer

Hi Beate, 
 When you reply use the rich formatting option: 
 
 Then you can insert an image, or a file. You can also email it to me if you like, I put my email in the last post. 
 Regards 
 Paul

Paul · Answer

Hi Beate,

Why do you need to exclude the fonts? They were not parsed in the first place in my example. Excluding the TITRE_2 is probably simple enough too... maybe I didn't need to extract the PARENT attribute at all. As I scroll through the file it looks as though they are all metadata so perhaps you just remove that rule?

Regards

Paul

Paul · Answer

Hi Beate, Sometimes you can resolve bad segmentation with the TM segmentation rules, but in this case I think you're stuck, Where you have things like this: Which should really come out like this: Some text in here... ("... then a bit more...") finally some more more text…). It will inevitably come out like this: Some text in here... (" ... then a bit more... ") finally some more more text…). Not much you can do about this with Studio 2015. In Studio 2017 you can enable merging over paragraph segments and this will support the three segments being merged into one. But I'm not sure about the effect of this on the resultant file. Regards Paul

Trados Studio > 1. Trados Studio

Scribus, properties of type settings