Merci Paul pour ta réponse.

Oui, les fichiers sont au format XLIFF. Selon ton conseil, j'ai ouvert un fichier avec le bloc-notes. Le texte est en français.

Que puis-je faire pour que cela fonctionne ? Je dois absolument commencer le travail de traduction.

Merci pour ton retour.

Sarah Rochat 

ok - the important part here is what languages... plural.  For example, in an XLIFF you'll see something like this:

<?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file original="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" source-language="en-GB" target-language="de-DE" datatype="html" tool-id="SharePoint Server 2013">
<header>

It may not be exactly like this, but it should contain the languages in the file. Can yo copy the languages part and tell s what they are?

More importantly do you have both languages installed in your version of Trados Studio?

Sarah Rochat 

ok - the important part here is what languages... plural.  For example, in an XLIFF you'll see something like this:

<?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file original="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" source-language="en-GB" target-language="de-DE" datatype="html" tool-id="SharePoint Server 2013">
<header>

It may not be exactly like this, but it should contain the languages in the file. Can yo copy the languages part and tell s what they are?

More importantly do you have both languages installed in your version of Trados Studio?

Voici l'indication dans mon fichier XLIFF : source-language="fr" target-language="de"

Voici ce que j'ai indiqué lors de la création de mon projet dans Trados Studio : langue source FRch > langues cibles DEch et DE

J'ai déjà un autre projet existant avec les mêmes langues, mais inversement (source : DEch ; cible : FRch). Je n'ai jamais eu de soucis.

Voici le type de fichiers que je dois traduire.

Sarah Rochat 

I'm guessing a bit, but it may be a problem because you have these languages in your project:

fr-CH
de-CH
de-DE

But your XLIFF is undefined and the software doesn't know what to do with this.

Why do you need two target languages in your project?  Is that deliberate, or is it because you have them in your project template and you are doing this unwittingly?

I would try two things to try and solve this problem:

1. try editing the XLFF and change the codes from this:
   source-language="fr" target-language="de"
   to this:
   source-language="fr-CH" target-language="de-CH"
   
   or
   
   
2. Recreate your project with only one language pair so you don't have this choice.

Ok. J'ai créé un nouveau projet. Voici mes langues :

Maintenant, j'arrive à ouvrir le fichier dans Trados Studio. Mais, il m'affiche le même texte dans les 2 colonnes.

Question : lorsque j'ai créé le projet, j'ai non seulement créé une mémoire de traduction, mais aussi une base terminologique (modèle bilingue). Est-ce bien correct ?

Sarah Rochat 

Sarah Rochat said:

Maintenant, j'arrive à ouvrir le fichier dans Trados Studio. Mais, il m'affiche le même texte dans les 2 colonnes.

This is most likely because the XLIFF file contains this information.  Did you look?  If you scroll down a bit when you open the XLIFF in a text editor and you'll find Translation Units (TU) that contain the source TU and also the target TU.  It's fairly common for these files to have same source/target content before they are translated.

Sarah Rochat said:

Question : lorsque j'ai créé le projet, j'ai non seulement créé une mémoire de traduction, mais aussi une base terminologique (modèle bilingue). Est-ce bien correct ?

Entirely up to you and how you wish to work.  None of this will be sent to your client when you return the file, unless they asked you for this and you are happy to provide it.

Most users probably already have a Translation Memory and a Termbase already created and they would just add these to the project so they don't keep creating new ones and can benefit from the work they did before.

J'ai contacté le fournisseur des fichiers. Le problème venait effectivement de son codage. Maintenant, ça fonctionne. MERCI BEAUCOUP POUR TON AIDE :-)

En écoutant un tutoriel pour la création d'un projet, il est conseillé de créer une mémoire de traduction par projet resp. "client" puisque les termes ne sont pas identiques d'un client à un autre. C'est la raison pour laquelle j'ai créé une nouvelle mémoire. Et dans la foulée, une nouvelle base terminologique.

Sarah Rochat 

Sarah Rochat said:

En écoutant un tutoriel pour la création d'un projet, il est conseillé de créer une mémoire de traduction par projet resp. "client" puisque les termes ne sont pas identiques d'un client à un autre.

You know what they say about teachers ;-)

Si je comprends bien, tu me conseilles de ne pas créer de nouvelles mémoires de traduction, ni de bases terminologiques ?

Si c'est le cas, je dois donc recréer un nouveau projet ?

Mais les langues sont inversées...

Sarah Rochat 

Sarah Rochat said:

Si je comprends bien, tu me conseilles de ne pas créer de nouvelles mémoires de traduction, ni de bases terminologiques ?

No that's not what I'm advising you.  I'm saying that anyone who told you that you that it is advisable to create a translation memory for each project or "customer", as the terms are not identical from one customer to another may not have given you the best advice.  Certainly this is not a definitive requirement.  You may well have clients who have customer specific terminology and then you can either use attributes in the termbase so you can filter on the results when working with this customer, or create a new termbase that you work on with just that client.  But you may also have several clients all working in the same domain which could allow you to have one termbase for them all and then you benefit from the re-use when you work.

Ultimately what you do is something you need to decide, it's not something that you do because you heard someone said you should.

Sarah Rochat said:

Si c'est le cas, je dois donc recréer un nouveau projet ?

No you would not.  You would just remove the resources you created and add the ones you wanted to use instead.

Sarah Rochat said:

Mais les langues sont inversées...

For termbases it makes no difference, and for Translation Memories you can use AnyTM.

Bonjour Paul,

Tu l'auras compris, je suis débutante. Comment puis-je supprimer la base terminologique bilingue que j'ai attribuée au projet ? Est-ce je laisse néanmoins la nouvelle mémoire de traduction puisque le domaine est différent ?

Sarah Rochat 

Sarah Rochat said:

Comment puis-je supprimer la base terminologique bilingue que j'ai attribuée au projet ?

Why do you want to delete it?  Do you have one you would prefer to use in its place?

But if you do want to delete it just remove it from your project settings (pay attention to it's location before you remove it) and then go and delete it in File Explorer by selecting the associated files and deleting them.

Sarah Rochat said:

Est-ce je laisse néanmoins la nouvelle mémoire de traduction puisque le domaine est différent ?

As I have tried to explain.  If you want to have different TMs for each domain then you should remove the one you have there now and use one that you intend to use for this domain.

Alternatively you could even create a field for domain in your TM and then use one TM for everything you do.  This article may help:

https://multifarious.filkin.com/2013/07/12/fields_attributes/

It's 10-years old but the concept may be helpful for you.

I feel a little as though I am only confusing you because I don't know enough about how you would prefer to work, and you don't know enough about how you want to work either.  Perhaps you should start a separate thread to simply discuss with others how to manage these types of resources, domains, customers etc.  I think that once you are clear in your mind about how you would like to work then we can talk about how to set up the resources you would use in a more helpful and effective way.