Currently, when you add a view for a service in the skin, you add a xslt file and a xml file.
In the xml file when you use an i18n key, you have to specify the catalogue "skin.MYSKIN:", because the default catalogue is the one of the plugin creating the view.

This is not a problem when parsing the xslt file because you have a variable $skin, but in this xml file...

This become critical for generated skins: in the 3.4 blog skin , you will find a "skin.demo:XXXXX" for example.

A way to correct this could be in the ServiceXSLTEnumerator to change the _parseI18nizableText method by giving it the defaultCatalogue that can be computed above BUT this imply an API change