Hi Guido Vermeer , the issue is caused by the "fct:ExternalLink" parser rule, as it references a namespace that was not added under Namespace mapping in the filter settings. As this should not prevent you from migrating the filter, I logged the issue for our Development (as CRQ-40344), so it can be fixed in the future. 

Hi Guido Vermeer , the issue is caused by the "fct:ExternalLink" parser rule, as it references a namespace that was not added under Namespace mapping in the filter settings. As this should not prevent you from migrating the filter, I logged the issue for our Development (as CRQ-40344), so it can be fixed in the future. 

Guido Vermeer 

I sent you an email to explain this in a little more detail but for the benefit of others who might stumble across this thread the main points are these.

First of all when you get to this page pay attention to the messages:

In my case there are two warnings that should be considered: 

• Parser Rules
• Namespace Settings

Everything else is ok for the migration.  So what this means in practice is that when you get to here you need to check and see whether the XML files you are handling use namespaces:

The old XMLv1 filetype was a bit trickier, and also more forgiving, to set up for namespaces so you may not have done this in the old filetype.  So in the original settings file you had a rule like this:

You can see the rule used a namespace in the XPath, but in the namespaces section this was not declared at all:

So, when you migrate the settings the XML v2 filetype requires this namespace information.  It is easy enough to solve once you know which namespace is missing as you just add it when you get to step 5 in the migration workflow I showed above.  So in this case you would add fct to the Prefix.  The Uri won't be in the settings file as you didn't add it in the old settings so you need to get that from the XML files you are translating.  In this case something like this:

xmlns:fct="">www.fct.com/somename" 

So the entry would be this:

Once you do that all is well.

Now, given this is pretty straightforward to identify where a namespace was used in the old parser rules this is going to be easy if you still have access to the old version of Trados Studio.  But if you don't then here's a simple Python script that will report the missing info when you run it and select the old settings file. 

namespace_corrections.zip

Run the script in a Python processsor (Visual Studio Code, PyCharm or Jupitor Notebook for example), select the old settings file when prompted and you'll get a result like this:

Missing namespace declarations found:
Prefix: fct
Uri: [MISSING URI]

So you only need to get the Uri from one of your translatable XML files.