Katja Pagenhardt 

Which XML file type was your old ST4 file type based on? I think all the XML1.X file types were dropped in Studio 2024, and only XML 2 is left. Could that be a source of problems?

Hallo Daniel,

that's right, before we used XML 1 and chose XML 2 now since it was the only option.

Katja Pagenhardt 

It might be that by importing settings or basing your new XML 2 filetype on settings from an XML 1 filetype you are creating a problem that surfaces when you want to use the file type. I would try setting up an XML 2 file type from scratch and manually copy all settings. I know that's inconvenient, but I think that is the most promising approach here. Do you have the knowledge how to set this up or did you inherit the old filetype and the person who set it up left the organization?

I did inherit the old file type and I don't know how to setup from scratch. I tried already but apparently I'm doing something wrong. Any help for this process is very welcome.

 Katja Pagenhardt 

I sent you the filetype based on the old settings. Preview works fine for me. XML2 seems to handle namespaces differently than XML 1.

EDIT: I created a test project and the file type works fine for me. I compared with the old filetype on Studio 2021, and it looks identical.

Hope this works for you.

 Katja Pagenhardt 

I sent you the filetype based on the old settings. Preview works fine for me. XML2 seems to handle namespaces differently than XML 1.

EDIT: I created a test project and the file type works fine for me. I compared with the old filetype on Studio 2021, and it looks identical.

Hope this works for you.

Dear Daniel, 
I would desperately need that very filetype. Could you help me, too?
Thank you so much.

Hi,

I would need to reopen this discussion, as we upgraded from Studio 2022 to 2024, and stumbled accross this problem here.

So, do I get this right?

Studio is not supporting XML 1 anymore, but XML 1 is needed for the ST4 data type?

The here offered solution is to recreate the data type from scratch, right?

Is this really the only solution, RWS is offering?

I suppose there are many users who used to work with this data type, do they all now have to recreated their data type?

I already tried to do that, but encountered a number of problems, so this is something that does not work automatically, it needs readjustments.

But there is no solution from RWS to deal with this problem, right?

Besides that we have noticed, that Studio 2022 projects based on the ST4 data type do not work in Studio 2024, because the data types do not match. This means, when you upgrade to 2024 and you still have 2022 projects with that data type, you can re-start with your work.

Did I understand that correct or is there a solution in the meantime?

Thanks,

Johannes

Johannes Purer 

Johannes Purer said:

Studio is not supporting XML 1 anymore, but XML 1 is needed for the ST4 data type?

Incorrect.  XML2 also can obviously support ST4.

Johannes Purer said:

Is this really the only solution, RWS is offering?

RWS don't have to offer a solution at all.  Quanos, the company responsible for SCHEMA ST4 provide the filetype settings for all versions of Trados Studio, and they make this available to all companies using their solution.  We have offerred to do something but they didn't want us to, and with good reason.  Each Schema solution they provide for a customer can be different, so they provide each customer with the ST4 settings files to suit the implementation they have been given.

Johannes Purer said:

But there is no solution from RWS to deal with this problem, right?

There is of course, but it's not the right way to tackle it.

The solution is to speak to your customer and ask them to provide you with the appropriate settings file for 2024.

Hi Paul,

thanks a lot for your reply.

I have now asked the client to send me the ST4 settings from their system. When I import them, I get this error message:

ST4 cannot be imported - Component Builder not found.

Any idea, what the error might be?

Thanks,

Johannes

Johannes Purer 

Any chance you can share the settings file?

sure, here it is. As the file type is not allowed, I had to zip it.

2311.ST4.zip

Johannes Purer 

Thanks for that... although these are clearly settings for an older version of Studio and not 2024.  However, I imported them into 2022 and this worked fine without any messages.  So then I created a new XML2 version with the same settings file and this also worked without an error.  As I said earlier upgrading it isn't the right approach as your client should be able to provide you with a version for 2024 and this would be preferable in case there had been changes that the upgrade doesn't pick up... however, I recorded the processes so you can see I don't get any errors:

I think it might be worth making sure you have got the latest versions of whatever version of Studio you are using.

Hi Paul,

thanks a lot for your reply. I can reproduce these steps, this is very helpful.

Anyway, can you then open this file with the new ST4 settings?

I can open it, but no segments are displayed, althought the file is not empty.

And is it correct, that a Studio 2022 project based on the XML1 settings cannot be processed in Studio 2024? It's possible to open the project, but the files cannot be saved in their target format. Error message: Data type definition with ID ST4 not found.

Many thanks for your help.

Johannes

<?xml version="1.0" encoding="UTF-8"?>
<l:langdata xmlns:l="http://www.schema.de/XSL/ST4DocuManagerlang">
	<l:langblock xml:lang="en">
		<l:gentext key="caution" value="CAUTION" />
		<l:gentext key="commented.by" value="Comment by" />
		<l:gentext key="componentlink" value="Additional components" />
		<l:gentext key="danger" value="DANGER" />
		<l:gentext key="edition" value="Output" />
		<l:gentext key="embedded.caution" value="CAUTION!" />
		<l:gentext key="embedded.danger" value="DANGER!" />
		<l:gentext key="embedded.notice" value="NOTICE!" />
		<l:gentext key="embedded.warning" value="WARNING!" />
		<l:gentext key="footnotes" value="Footnotes" />
		<l:gentext key="furtherinformation" value="Additional information" />
		<l:gentext key="glossary" value="Glossary" />
		<l:gentext key="glossaryentry" value="Glossary entry" />
		<l:gentext key="graficgrouplink" value="Included graphic resources" />
		<l:gentext key="GrammaticalGender" value="Grammatical Gender" />
		<l:gentext key="images" value="Images" />
		<l:gentext key="index" value="Index" />
		<l:gentext key="indexsections" value="Icons[*];Numerical[0-9];A;B;C;D;E;F;G;H;I;J;K;L;M;N;O;P;Q;R;S;T;U;V;W;X;Y;Z" />
		<l:gentext key="label.fig" value="Fig." />
		<l:gentext key="label.part" value="PART" />
		<l:gentext key="label.table" value="Table" />
		<l:gentext key="Language" value="Language" />
		<l:gentext key="lexicon" value="Glossary" />
		<l:gentext key="maintenance.duration" value="Required time" />
		<l:gentext key="maintenance.facilities" value="Tools" />
		<l:gentext key="maintenance.interval" value="Maintenance interval" />
		<l:gentext key="maintenance.title" value="Maintenance notice" />
		<l:gentext key="maintenance.tools" value="Special Tools" />
		<l:gentext key="MaintenanceCycleLink" value="Maintenance cycle" />
		<l:gentext key="multilangtitle" value="Title Page" />
		<l:gentext key="multilangtoc" value="Contents" />
		<l:gentext key="nav.back-to" value="Back to…" />
		<l:gentext key="nav.components" value="Components" />
		<l:gentext key="nav.content" value="Sitemap" />
		<l:gentext key="nav.glossary" value="Glossary" />
		<l:gentext key="nav.glossry" value="Glossary" />
		<l:gentext key="nav.home" value="Home" />
		<l:gentext key="nav.index" value="Index" />
		<l:gentext key="nav.infotypes" value="Information types" />
		<l:gentext key="nav.search" value="Search" />
		<l:gentext key="nav.to-infotypes" value="Information types avaliable" />
		<l:gentext key="notice" value="NOTICE" />
		<l:gentext key="PersonnelLink" value="Personnel" />
		<l:gentext key="relatedDocuments" value="Documents about this" />
		<l:gentext key="search.submit" value="Execute Search" />
		<l:gentext key="seealsolink" value="See also" />
		<l:gentext key="seedocuments" value="Documents about this" />
		<l:gentext key="seq.images" value="Image" />
		<l:gentext key="seq.tables" value="Table" />
		<l:gentext key="SortKey" value="Sort Key" />
		<l:gentext key="SubjectField" value="Subject Field" />
		<l:gentext key="tables" value="Tables" />
		<l:gentext key="Term" value="Designation" />
		<l:gentext key="toc" value="Contents" />
		<l:gentext key="Validity" value="Status" />
		<l:gentext key="version" value="Version" />
		<l:gentext key="warning" value="WARNING" />
		<l:gentext key="WatermarkText" value="Preliminary - For internal use only" />
		<l:gentext key="xref" value="You can find the information on page " />
		<l:gentext key="xreftoc" value="(reuse)" />
		
		
				


	<l:gentext key="m06.misprint" value="Subject to technical changes and typographical errors!" />
	<l:gentext key="m06.validfrom" value="Valid from" />
	<l:gentext key="m06.originalversion" value="Original operating manual" />
	<l:gentext key="m06.BA" value="Operating manual" />
	<l:gentext key="m06.SA" value="Service manual" />
	<l:gentext key="m06.MA" value="Assembly manual" />
	<l:gentext key="m06.originalBA" value="Original operating manual" />
	<l:gentext key="m06.originalSA" value="Original service manual" />
	<l:gentext key="m06.originalMA" value="Original assembly manual" />
	<l:gentext key="information" value="INFORMATION" />
	<l:gentext key="embedded.information" value="INFORMATION" />
	</l:langblock>
</l:langdata>

Johannes Purer 

Exactly why I said you need to get the correct updated settings file from your client.  The problem, that we sometimes see, is that when namespaces are used the XML version 1 fails to correctly report the namespace declarations in the settings file.  So when you upgrade to version 2 the namespace is missing.  I added the missing namespace into the updated settings and now have this... yours will most likely be empty:

If it helps, and if you use Python, I created a script here that checks a version 1 settings file for missing declarations and reports them:

https://github.com/paulfilkin/Python-scripts/tree/main/namespace_corrections

Running this on the V1 settings file you provided returns this:

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

You can find the URI in the XML you tried to parse:

<l:langdata xmlns:l="">www.schema.de/.../ST4DocuManagerlang">

So add that in and then you should preview this:

Which has the same 71 segments extracted as Trados Studio 2022 using the V1 settings.

Hope that helps?

Johannes Purer 

Also... I forgot to answer your other question too... the fact the namespace fails to be correctly reporting in the settings file is not a bug.  It happens because the V1 settings, in your case, is set up like this:

Because the option to provide the prefix and namespace was not used Studio actually doesn't know what it is.  So this has to be taken from the files you are translating.  The option to "Use namespace when declared in the document" was removed in V2 because this didn't help when sharing settings between applications (the Trados ecosystem is bigger than just Trados Studio), so now you always need to be explicit if you wish to share settings, or use localname in the parser rules (if appropriate).

Johannes Purer said:

And is it correct, that a Studio 2022 project based on the XML1 settings cannot be processed in Studio 2024? It's possible to open the project, but the files cannot be saved in their target format. Error message: Data type definition with ID ST4 not found.

This is correct.  Same with any XML using custom settings.  The settings file needs to be on both machines if you want full flexibility.  Given this is no longer possible in 2024 you would need to either recreate the project in 2024 and Perfect Match or pre-translate from a TM to be where you were in 2022, or send the updated translation back to whoever created it so they can do it.