Hello there,

I think I am struggling with the same problem. I would be very happy someone could help me with some basic explanation as I am new to translation management. 

My ultimate goal is to send a package of Flare files to a translation agency, get it back translated and then import it to a second Flare project for the second language.

My current problem is that the Flare variables are not shown after import into SDL Studio and the respective sentences get split into two units where the variables were before.

I disabled all file types except SDL XLIFF and XML MadCap Compliant and moved the latter up to the top of the list. I also looked into the settings of XML MadCap Compliant and found the parsing rules but really have no clue what to change in order to make the variables appear.

Do you have any advice for me which settings to change and how?

Thank you very much,

Ines

Ines Wendler

I suggest you try the filetype Evzen already prepared first as this may solve your problem... I'd be interested to know if it does:

https://community.sdl.com/product-groups/translationproductivity/f/studio/15217/customized-madcap-flare-file-type-disappears-from-project-settings-after-closing-and-reopening-studio

If it doesn't then you're going to have a learn a little about how to customise an XML filetype.  This article may be a good starting place:

multifarious.filkin.com/.../

Thanks, Paul. I imported Evzen's filetype and changed "IsStandardCustomization" to "false". Unfortunately, it does not change how the variables are shown. I will look at the article you linked.

There is just something else that strikes me: The htm-files of the flare project got an extra ending ".sdlxliff" upon importing them into SDL Studio (I did New project, Add folder and chose a folder with several subfolders with htm-files in it). Same thing happens if I do Welcome - Drag files - SK.flprj (although this was just a useless test as no translatable files get imported).

Should the file ending really change to .sdlxliff? Doesn't that contradict using a custom filetype?

Thanks, Paul. I imported Evzen's filetype and changed "IsStandardCustomization" to "false". Unfortunately, it does not change how the variables are shown. I will look at the article you linked.

There is just something else that strikes me: The htm-files of the flare project got an extra ending ".sdlxliff" upon importing them into SDL Studio (I did New project, Add folder and chose a folder with several subfolders with htm-files in it). Same thing happens if I do Welcome - Drag files - SK.flprj (although this was just a useless test as no translatable files get imported).

Should the file ending really change to .sdlxliff? Doesn't that contradict using a custom filetype?

HI Ines Wendler

concerning the "extra ending" sdlxliff - this is so for all files you work on with Studio. The original file is converted to XLIFF. When you finalize the files or "Generate target files", the XLIFF files are converted back to their original format (exception pdf, which is returned as a docx).

(Hello.xml would become Hello.xml.sdlxliff while in process and then be converted back to Hello.xml.)

So the "extra ending" is normal and no problem, part of how Studio works. The rest of your question I can not help you with.

Daniel

Update: 

I did read your article, Paul. That clarified a lot.

I tried changing the parsing rules in the filetype but not see that my changes in the rules affected what SDL Studio would import from the xml-files. Turned out that filetype settings should be changed before importing a document to take effect. So I changed my project template settings, created a new project, imported the files again and now I get the variables as tags and the surrounding sentences do not get split anymore. I'll just have to dig a little deeper if this is something we can actually work with.

Ines Wendler

Ines Wendler said:

Turned out that filetype settings should be changed before importing a document to take effect.

Of course... you have already converted your file to an SDLXLIFF by this time so you either change the settings before, OR you could update the file in your project and this would also prepare the file again with your updated settings.