[ omegat-Bugs-1587606 ] first segment validation persistence issue

[SourceForge.net <no...@so...>]

Bugs item #1587606, was opened at 2006-10-31 09:34
Message generated for change (Comment added) made by brandelune
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520347&aid=1587606&group_id=68187

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
Summary: first segment validation persistence issue

Initial Comment:
I have a completed translation with reference TMs including exact 
matches on the first segment.

I have "insert the best fuzzy match" on.

When I load the project and after dismissing the project files window, 
OmegaT automatically updates the first segment _although it has been 
already validated as translated and should not be modified by OmegaT_

I suppose that is a side effect of a previous bug fix where the first 
segment was automatically validated by OmegaT even though the 
translator had not validated it.

So, it looks the previous bug fix is actually forcing OmegaT to ignore the 
contents of the first segment and handle it as if it were empty... ?

----------------------------------------------------------------------

>Comment By: Jean-Christophe Helary (brandelune)
Date: 2006-10-31 14:02

Message:
Logged In: YES 
user_id=915082

Well, it may not be related to that bug fix, but I don't remember ever having that before the bug fix. So it may be related to code added 
later on.

Ok, in fact the problem may not be at loading time. But at the moment OmegaT is doing a first save of the project, just after loading ?

There, it would be on the first segment since nothing has happened yet and the conditions you have put in the bug fix would trigger 
the first segment to not be saved (?) and eventually to be replaced by the fuzzy since it is not in the project memory.

Whatever the cause is, after some tests, it seems to happens only when target=source, even though target=source is allowed in the 
settings.

When target and source are different, whatever match pops up on the first segment, nothing is replaced.

----------------------------------------------------------------------

Comment By: Henry Pijffers (henry_pijffers)
Date: 2006-10-31 12:44

Message:
Logged In: YES 
user_id=545103

I've checked the code and it's completely impossible that
this is a side effect of fixing bug 1409309. All I do in
that fix is check upon saving, and then forget about saving
the first segment under certain conditions. I definitely
don't do anything upon loading.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520347&aid=1587606&group_id=68187