Péter Orosz

I can't find the examples you show here... the link only show the different ways connections can be made.  However, I don't really understand your point.  If this is a screenshot of some tutorial somewhere then I imagine this is not a tutorial about the language itself, but rather a tutorial about the way connections work.  In terms of an example what do you need?  If you use the same text to illustrate the way connections work then one of them is highly likely to make les sense than the other.

Or am I missing something about your point?

Dear Paul

My examples are fake ones.

At 

https://docs.rws.com/813470/673915/trados-studio-2021-sr2/alignment-connection-types

I found "2:2" does exist but there is no example

I DO understand how one SOURCE segment can be attached to TWO TARGET segments at the same time (1:2)

BUT

I DO NOT understand how

- one SOURCE segment can be attached to TWO TARGET segments at the same time 

AND

- those TWO TARGET segments are attached to THIS SOURCE segment AND ANOTHER ONE at the same time

I just can’t imagine a situation when

- „3 large garlic cloves, minced” means „3 spicchi d'aglio grandi, tritati” AND ALSO „peperoncino macinato”

AND AT THE SAME TIME

- „ground chili peppers” means „peperoncino macinato” AND ALSO „3 spicchi d'aglio grandi, tritati”

Péter Orosz

Both of your difficulties are answered in the same way.  When you use the alignment module you have to add a source file and a target file.  The way each file is segmented can depend on how the file was segmented in the base of bilingual files, or the filetype itself in case of monolingual files.

Image  a situation where your client had the original source as a DOCX, and its corresponding translation as a PDF only.  When you align it you could quite easily end up with a 1:2, or 1:3 or even a 1:4 alignment problem.  And the other way around you could find you have a 2:1, 3:1 or even a 4:1 alignment problem.

Same thing could happen with many different configurations of files.  I don't really see the need to show examples, although it would be fairly trivial to provide some as it's not uncommon and easy to reproduce.  If you still want an example after this let me know and I'll make one up!

I think, if you have "perfect" source and target files you'll never need this. But the reason the functionality is there is because sometimes you do.

Péter Orosz

Both of your difficulties are answered in the same way.  When you use the alignment module you have to add a source file and a target file.  The way each file is segmented can depend on how the file was segmented in the base of bilingual files, or the filetype itself in case of monolingual files.

Image  a situation where your client had the original source as a DOCX, and its corresponding translation as a PDF only.  When you align it you could quite easily end up with a 1:2, or 1:3 or even a 1:4 alignment problem.  And the other way around you could find you have a 2:1, 3:1 or even a 4:1 alignment problem.

Same thing could happen with many different configurations of files.  I don't really see the need to show examples, although it would be fairly trivial to provide some as it's not uncommon and easy to reproduce.  If you still want an example after this let me know and I'll make one up!

I think, if you have "perfect" source and target files you'll never need this. But the reason the functionality is there is because sometimes you do.

Dear Paul

1:2, 1:3, 1:4, 1:5

2:1, 3:1, 4:1, 5:1

...all clear to me.

The girl has some unwanted shifts here that resulted in some 1:2 connections, which she adjusted manually:

https://www.youtube.com/watch?v=I9DGXVHkeYk

Also, I can even imagine this situation easily:

What we have here is two, nice, understandable, separate 1:1 connections.

However, it is technically possible to create 2:2:

WHY?

Why should anyone connect any segments this way?

A realistic example would help me understand.

If there is no example, the instructions at the docs.rws page above just confuse me.

Péter Orosz

it’s really just another example of the same. Imagine you are aligning subtitle files for example (and other Filetypes can behave in similar ways), and you want to add the TUs to your TM so the content is available for translation work where the sentences are not broken up in the same way. Here it is very likely you would have an alignment task that is full of these sort of scenarios.