Angela Brueckner 

I don't know if the AI answered your question as you left it as a verified response... I'm going to guess it didn't..  Anyway the answer is to review the parser rules because clearly the tags are not set correctly, hence the reason they are now external and causing your sentences to segment.

To get better help you need to:

1. explain how you migrated the filetype and what messages were there... if any?
2. show us the xml structure relevant to that part of the file?
3. show us a screenshot of your parser rules relevant to that part of the file

When you do that you might find the answer yourself, but if not we will be in a better position to help.

Hello Paul,

thank you for your quick response. Sorry, I'm not yet quite familiar with this forum and how it works, thus I've accidentally put the text body of my issue into the heading. Let me try to explain the Problem again, along with the measures we've already taken in attempts to solve it and then provide you with the requested information thereafter.

My main issue is the following:

The files I'm getting sent by my customer look like this:

'''

<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE chapter

  PUBLIC "-//docufy//Docufy Standard DTD 20080125//EN" "../dtd/manual.dtd">

<chapter y.linktarget="true" y.validity.allowed="true" y.id="ID_4447ac45a5e94de50a05001f056230f4" y.io.id="9757be0dcca6575f0a05001t14e64fca" y.io.version="1" y.io.language="fr" y.io.variant="FR" y.io.format="MEmodule" y.io.type="me-chapter" y.validity.mode="positive" y.io.validity.mode="positive" y.io.owner="Frank Freitag" y.io.status="Approved"><title y.commentable="true" y.linktarget="true" y.validity.allowed="true" y.id="ID_6a75a3d9a5e9fde50a05001f0f718979" y.validity.mode="positive" y.io.validity.mode="positive">Befüllschnecke vorbereiten bei 9&nbsp;<v-ref y.io.id="058b610b35f74b9e0a0500eb0c3e151f" y.io.version="1" y.io.language="de" y.io.variant="DE" y.io.type="swtext" y.reftype="textvar" y.id="ID_d5e0aba1a5e9fde50a05001f34b22e68" y.ref.io.types="swtext" translate="no" y.target.language="fr" y.target.variant="FR" y.target.content="m">m</v-ref> Arbeitsbreite</title>

</chapter>

'''

These files are still not only in XML V1.X but also do not contain any namespaces as a XML V 2.X parser would expect.

I have tried using this methodology here:

Migration von XML 1 Dateitypeinstellungen zu XML 2 in Trados Studio

However that has not proven successful but only yielded the results as you've seen above.

The parser setting as requested and imported using the guide above can be seen in this screenshot here:

We tried declaring various things in the namespace section to get this to work, however unsuccessful up until this point.

Thank you for your support in this matter and we'll be looking forward to your reply.

Kind Regards

Hello Paul,

thank you for your quick response. Sorry, I'm not yet quite familiar with this forum and how it works, thus I've accidentally put the text body of my issue into the heading. Let me try to explain the Problem again, along with the measures we've already taken in attempts to solve it and then provide you with the requested information thereafter.

My main issue is the following:

The files I'm getting sent by my customer look like this:

'''

<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE chapter

  PUBLIC "-//docufy//Docufy Standard DTD 20080125//EN" "../dtd/manual.dtd">

<chapter y.linktarget="true" y.validity.allowed="true" y.id="ID_4447ac45a5e94de50a05001f056230f4" y.io.id="9757be0dcca6575f0a05001t14e64fca" y.io.version="1" y.io.language="fr" y.io.variant="FR" y.io.format="MEmodule" y.io.type="me-chapter" y.validity.mode="positive" y.io.validity.mode="positive" y.io.owner="Frank Freitag" y.io.status="Approved"><title y.commentable="true" y.linktarget="true" y.validity.allowed="true" y.id="ID_6a75a3d9a5e9fde50a05001f0f718979" y.validity.mode="positive" y.io.validity.mode="positive">Befüllschnecke vorbereiten bei 9&nbsp;<v-ref y.io.id="058b610b35f74b9e0a0500eb0c3e151f" y.io.version="1" y.io.language="de" y.io.variant="DE" y.io.type="swtext" y.reftype="textvar" y.id="ID_d5e0aba1a5e9fde50a05001f34b22e68" y.ref.io.types="swtext" translate="no" y.target.language="fr" y.target.variant="FR" y.target.content="m">m</v-ref> Arbeitsbreite</title>

</chapter>

'''

These files are still not only in XML V1.X but also do not contain any namespaces as a XML V 2.X parser would expect.

I have tried using this methodology here:

Migration von XML 1 Dateitypeinstellungen zu XML 2 in Trados Studio

However that has not proven successful but only yielded the results as you've seen above.

The parser setting as requested and imported using the guide above can be seen in this screenshot here:

We tried declaring various things in the namespace section to get this to work, however unsuccessful up until this point.

Thank you for your support in this matter and we'll be looking forward to your reply.

Kind Regards

Angela Brueckner 

ok - so looking at your screenshot we see this:

So you essentially want the tags represented by 4 to be inline (3 is probably your non-breakiing space) and not structural which is what's happening here:

Looking at the snippet you just provided we are talking about this part:

<title y.commentable="true" y.linktarget="true" y.validity.allowed="true" y.id="ID_6a75a3d9a5e9fde50a05001f0f718979" y.validity.mode="positive" y.io.validity.mode="positive">

Befüllschnecke vorbereiten bei 9

&nbsp;

<v-ref y.io.id="058b610b35f74b9e0a0500eb0c3e151f" y.io.version="1" y.io.language="de" y.io.variant="DE" y.io.type="swtext" y.reftype="textvar" y.id="ID_d5e0aba1a5e9fde50a05001f34b22e68" y.ref.io.types="swtext" translate="no" y.target.language="fr" y.target.variant="FR" y.target.content="m">

m

</v-ref>

Arbeitsbreite

</title>

So the tag pair you want non-translatable and inline, represented by the tagID "4" is v-ref.

When I look at your screenshot there is no sign of the parser rule for v-ref as you only showed the top 30%... or so. So I suggest you scroll through the parser rules, find the v-ref rule and make sure it's set as non-translatable and inline.