How do I prepare MadCap snipped files (.flsnp) for translation?

Question

I am using Studio 2015 and can see an FLSNP file type under Project Settings > File Types, but when I select a .flsnp file under Files (source file list) in the Home menu and then click on Batch Tasks I only get "(No tasks available)" greyed out.

Wieder Gerhard · Accepted Answer

Hi Paul, 
 
Your first question gets straight to the point and made me regret having posted mine. As soon as I saw your reply I remembered that the file type 'definition' in my project is very likely the result of my (unsuccessful) attempt to create it under a previous version of Studio, which would explain why it doesn't work. 
 
It would still be handy to have a working filter, but that will have to wait until another day... My workaround, if anyone is interested, is to translate the snippet files as .xml files as follows: 
 
Open command prompt window as administrator 
 
Before edit in Trados Studio: 
copy *.flsnp *.xml 
 
After edit in Trados Studio: 
copy /-y *.xml *.flsnp

Wieder Gerhard · Answer

Thanks Paul. Great tip to add the file extension to the wildcard list. It certainly beats fuffing around in DOS. I appreciate the proviso about parsing but, in my case, the text I want for translation is extracted nicely.

Paul · Answer

Hi Wieder, 
 
Where did you get the *.flnsp filetype from? The default MadCap does not support this (only *.html;*.htm) so you would have had to make the necessary changes to the default filetype first. You may have done this but I'd like to be clear on the process you followed first. 
 
The next thing would be that is batch tasks are greyed it's usually for these two reasons. First, you didn't select a file, and second you have not saved the project. 
 
Perhaps we can understand better your situation forst and then suggest something more helpful? 
 
Thanks

Paul · Answer

Hi Wieder, 
 
Pretty unusual workaround. You could have just added *.flnsp to the file wildcard dialogue and achieved the same thing. But I think the better approach is to make sure that the AnyXML, or the MadCap filetype is really parsing what you need. I'm not sure that this file is normally translated, but you're not the first person to raise this and I have adapted the rules for a couple of people in the past. Interestingly it was different each time, so I think there must be an element of how MadCap is being used here which a default filetype may not always pick up. 
 
Regards

Trados Studio > 1. Trados Studio

How do I prepare MadCap snipped files (.flsnp) for translation?