Hello Christian Blouin 

Perhaps you are just looking at this the wrong way.  You have two sentences, something like this:

FR
À cette fin, un peu plus de texte ici, avec les autres intervenants du milieu » (LSSSS, art. 100).

EN
To that end, some more text here, with other key players." (LSSSS, sec. 100).

The problem you have is that the FR source doesn't have a period before the closing quote so this is why it does not segment.  The EN target however does.  So if you add an exception to the fullstop rules in the EN language resources of your TM then you can prevent it from segmenting.  Something like this perhaps:

Then the alignment looks like this:

Which is what you were trying to achieve... I believe.

Hello Paul,

Thanks once again for your reply... but it doesn't work for me.
I scratched my head a couple of times, because I'm just so sure that when you give an answer

it just is the right answer.

So, I just started poking around and I found the problem... which I can't solve.

Here it is:

I created the exception to the segmentation rule in L2, exactly as you instructed,, opened the two files for alignment and Studio

still kept breaking the segment like before.

I went back to the "Edit rule Exception" dialog box in BASIC view and it looked fine.

I then clicked on the ADVANCED view button, and this is where there is a problem:

For some reason, Studio created a different regex on its own.

I corrected it and entered the right expression and clicked OK a couple of times to return to the alignment view.

I then proceeded to to the alignment again and sure enough, it was still incorrect.

I went back to the "Edit rule Exception" dialog box in BASIC view and it looked fine again. I toggled again to the ADVANCED view

and there was again the same erroneous regular expression that Studio created on its own:  " \w+\.\.+ "

I did this four or five times, and it was the same problem again and again.

I tried different scenarios where I would have the incorrectly aligned files open/active, then unopened.

The same for the TM concerned, I tried having it opened, then unopened during the procedure.

My last troubleshooting idea was to go back to the "Edit rule Exception" dialog box in BASIC view and enter XXXXX

in the "Before break" and check the "regular expression" box and the same for the "After break".

I then toggled to the advanced view and here's what Studio did:

So, this is as far as I can go on my own. I just can't solve it.

As usual, Paul, any help would be much appreciated,

Christian

Hello Paul,

Thanks once again for your reply... but it doesn't work for me.
I scratched my head a couple of times, because I'm just so sure that when you give an answer

it just is the right answer.

So, I just started poking around and I found the problem... which I can't solve.

Here it is:

I created the exception to the segmentation rule in L2, exactly as you instructed,, opened the two files for alignment and Studio

still kept breaking the segment like before.

I went back to the "Edit rule Exception" dialog box in BASIC view and it looked fine.

I then clicked on the ADVANCED view button, and this is where there is a problem:

For some reason, Studio created a different regex on its own.

I corrected it and entered the right expression and clicked OK a couple of times to return to the alignment view.

I then proceeded to to the alignment again and sure enough, it was still incorrect.

I went back to the "Edit rule Exception" dialog box in BASIC view and it looked fine again. I toggled again to the ADVANCED view

and there was again the same erroneous regular expression that Studio created on its own:  " \w+\.\.+ "

I did this four or five times, and it was the same problem again and again.

I tried different scenarios where I would have the incorrectly aligned files open/active, then unopened.

The same for the TM concerned, I tried having it opened, then unopened during the procedure.

My last troubleshooting idea was to go back to the "Edit rule Exception" dialog box in BASIC view and enter XXXXX

in the "Before break" and check the "regular expression" box and the same for the "After break".

I then toggled to the advanced view and here's what Studio did:

So, this is as far as I can go on my own. I just can't solve it.

As usual, Paul, any help would be much appreciated,

Christian

Christian Blouin

Two things to try I guess:

1. Don't waste time on the basic view. Always better to use the advanced view and just use the rules I showed

2. Make sure you are applying this to the right language.

3. Perhaps your text isn't the same as the one I made up.  It helps to have the real text and not just a screenshot as I may be missing something.

Studio has two languages in the TM and each language has it's own segmentation rules.  Normally we only play with source language since this is the file that gets opened.  Alignment is different since we open a source and a target language.

Maybe test the attached TM as an example:

fr-en.zip

Hello Paul,

Sorry for the delay. Had to take Maple, our Irish Setter, for his first morning walk.

OK, back to business:

I tried what you suggested, but it doesn't work. The same problem persists.

Here's a screen capture to show that I have followed your instructions and entered the regex you provided:

Then I went to Advanced view:

Again, Studio modified the regex on its own.

I also tried a second time and , out of curiosity, I toggled back to the Basic view without having clicked OK,

and Studio also modified the regex in the Basic view:

I have also attached the L1 (French) and the L2 (English) files for you to experiment with,

if you want to.

L1-L2 used for alignment_Christian Blouin.zip

Thanks for your help.

Christian

Christian Blouin

ok - I just played with your file and I see a reason why this isn't working for you.  Your file uses a curly quote and not a straight one.  So you need to make sure that the segmentation rule uses a curly quote too.  I'd suggest you copy/paste it from your file.  I just did a quick test with an extract from your file and now get this so it definitely works: