From: SourceForge.net <no...@so...> - 2009-09-10 12:52:59
|
Feature Requests item #2020048, was opened at 2008-07-17 00:20 Message generated for change (Comment added) made by didierbr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2020048&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: OmegaT Application Group: future Status: Open Resolution: None Priority: 5 Private: No Submitted By: hajma (tropikhajma2) Assigned to: Nobody/Anonymous (nobody) Summary: Give weight to memories Initial Comment: I have one TMX (a) which I know is the best. Then I have a couple of other TMX (b,c,d) which I know are in worse shape and could introduce inconsistencies to the project. So I'd like a way to setup TMs so that 100% matches from TMX b,c, and d would automatically become 80%. And if match from TMX a has the same value as match from TMX b, then the "a" should be given first. ---------------------------------------------------------------------- >Comment By: Didier Briel (didierbr) Date: 2009-09-10 14:52 Message: Thank you for your suggestion. For the second point ('And if match from TMX a has the same value as match from TMX b, then the "a" should be given first.'), there is an easy workaround. You can rename TMX (a) to something lower alphabetically than the others (e.g., 'a_'). This will ensure that, in case of equality, 'a' will be given first. For the first point, it's more complicated. As a crude workaround, you could replace all <tuv lang="xx"> (xx being your source language) <seg> with <tuv lang="xx"> (xx being your source language) <seg>[PENALTY] or something similar. Didier Briel ---------------------------------------------------------------------- Comment By: Gabix (gabix) Date: 2009-09-10 14:16 Message: Just an idea, a comment to Samuel’s comment: >Then you can specify match penalties for specific folders. Maybe, we could do it as follows: have, say, subdirectories /1, and /2, and /3 in /tm. The TM files in /1 have high priority, in /2 — normal, in /3 — low. So, OmegaT first reads /1 and adds a fixed percentage to matches similarity, then reads /2 and calculates similarity as they are, then reads /3 and subtracts a fixed percentage from similarity. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-17 00:02 Message: Logged In: NO Yep. Wordfast calls this "match penalties". In fact, in Wordfast the user can penalise a lot of other things too. So, you can decide to penalise a.tmx with 5% and b.tmx with 10% (well, not in Wordfast because WF supports only one reference TM). Another (better) implementation of this may be possible once it becomes possible to have nested folders in the /tm/ folder. Then you can specify match penalties for specific folders. -- leuce / Samuel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2020048&group_id=68187 |