Dear Paul,

Did you manage to handle the ST4.sdlftsettings files ? 

Many thanks in advance,

Maria 

Maria Pettersson

Apologies for the delayed response.  Handling the ST4 settings file is simple.  Just go your filetypes and import the settings file:

Say yes to create the new filetype.  Now you have a new filetype called "Scheme ST4".

The DST file is a "Document Settings Template" used by Across for the same purpose.  It creates a "SCHEMA_ST4_2018_TaggedXML" filetype in Across so you can handle ST4 XML files.

Thanks a lot Paul. Yes, very simple. But the files provided by the client to be translated are like already with the language combination. DOes it means that I have to create one project for each file ? 

Ex. files TCF_fr-FR_to_de-DE.xml and TCF_fr-FR_to_it-IT.xml  

Maria Pettersson

I guess that all depends on the files themselves and without seeing them I can't answer that.  Maybe you can edit one so we have a small sample with the language attributes in the file so we can see?

You have various options supporting language attributes in an xml file so these may help... just depends on what your file looks like:

<?xml version="1.0" encoding="utf-8"?><!DOCTYPE tms PUBLIC "-//Schema//DTD DocuMan TMS V5//EN" "Tms.dtd"><tms name="TCF" source="fr" target="it" source-culture="fr-FR" target-culture="it-IT" user="elbfra07" date="12/08/2020 15:22:38" version="ST4.ClientBase.TMS, Version=8.0.0.0, Culture=neutral, PublicKeyToken=201f642519e2a688" export-version="2" test="true" guid="ec15a0a9-7975-4af7-93b8-eea1ecde8598">
<!--TMS Settings
Test Export: true

Advanced Mode:
Type: XML
Target File: C:\Users\ELBFRA07\Desktop\TCF\it–IT\TCF_fr–FR_to_it–IT.xml
Filter: Urgent
Source Aspect: fr [fr-FR] (129798)
Target Aspect: it [it-IT] (130310)
Context Node(s): 7361564683
Variant Filter:
Skip Forbidden Nodes: true
Resource Treatment: textOnly
Graphic Selection: both
Export Original Graphic: true
Resource Folder Across: false
Export Context: true
Context in Target Language if Available: true
Export Fragment Titles: true
Export Resource Titles: true
Export DocumentStructure Titles: true
Export Group Titles: false
Recursive: true

Maria Pettersson

Can you also add a couple of lines with the elements containing the actual translatable content?  Obviously replace the text with something not important.  I just want to see what else is in this file as the header doesn't use the language attributes at all.  I would expect something like this:

xml:lang="fr-fr" and xml:lang="it-it"

If the file doesn't do this then you may still be able to create a single multilingual project but you, or your client, will have to manually edit the way the languages are annotated in each set of files once the translation is complete.

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/

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.