Maria Pettersson

Thank you.  So I think this means that if the files come with this part already populated

source="fr" target="it" source-culture="fr-FR" target-culture="it-IT"

and if this is essential information for the CMS using it then you do one of these two things:

1. create a single Studio project for all files with the same source language and add as many target languages as you need.  Then after saving the target files do a batch search & replace to address the target language codes with a descent editor, or script.  So you would only use one of the target language source files in Studio.  OR
2. create multiple projects, one for each of the target language source files.

If it was me I think I'd use 1.  Once you have the process defined to manage the renaming with a script it'll be a trivial task, whilst the management of the multiple Studio projects would be a lot more time intensive.

Unfortunately these files don't use the xml:lang attribute at all so Studio cannot change these automatically for you.

Maybe someone else with more experience of dealing with these formats in practice has a better idea?  Someone like Arnold from Kaleidoscope might also have a good solution for this.  A while ago they supported COTI which might be relevant here and provide a better process for industry "standards" like Schema:

https://multifarious.filkin.com/2016/12/19/coti-chuckling-on-the-inside/

Thanks a lot Paul. I still wonder why "New Fragment" is visible in Studio. I will see with an xml expert at our office. 

Maria 

Maria Pettersson

Maria Pettersson said:

I still wonder why "New Fragment" is visible in Studio.

Perhaps you just need to make sure you have a parser rule that excludes the title element.  The ST4 settings file, if this is what you are using, may just need tweaking for the particular content you have.