Menu
▾
▴
[ omegat-Bugs-1436563 ] OmegaT version number in the TMX
|
From: SourceForge.net <no...@so...> - 2006-02-27 16:45:12
|
Bugs item #1436563, was opened at 2006-02-22 11:37 Message generated for change (Comment added) made by mihmax You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520347&aid=1436563&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: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: OmegaT version number in the TMX Initial Comment: OmegaT should indicate precisely which version the TMX has been created with. Currently all the RCs are identified as 1.6 which could lead people into thinking that all RCs are equivalent. OmegaT should indicate the exact version (including RC number, build date eventually) and produce an error message when a project is opened with a non matching OmegaT version (like are you sure you want to open this project with this version: TMX creation OmegaT version=..., current OmegaT version=... there may be segmentation and TM problems of you proceed). I know it should be a RFE but with RC7 release and 1.6.0 close, it is very important that users are informed of the possible issues related to upgrading. JC ---------------------------------------------------------------------- >Comment By: Maxym Mykhalchuk (mihmax) Date: 2006-02-27 17:45 Message: Logged In: YES user_id=488500 Henry, probably you misunderstood me (or I misunderstood your last comment). Let me repeat myself. For a paragraph like "Word</f0><f1>more words</f2><f3>. Plus </f3>more words." OmegaT would create two segments: <seg>Word</f0><f1>more words</f2><f3>.</seg> <seg>Plus </f3>more words</seg> 1. Renumbering <f3> in the second segment based on how many segments there were in a previous one is more or less simple: (n+1)/2 should almost always work. 2. The difficult thing here is NOT to add <f3> to the beginning of the second segment, and not add </f3> to the end of the first one. 3. Also difficult are standalone segments (<f6/> in current notation) -- earlier OmegaT versions didn't add a slash, and it's totally unclear how to detect them given only TMX files... ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-02-27 17:17 Message: Logged In: YES user_id=545103 If you apply the same conversion when splitting paragraphs, then the problem is solved. ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2006-02-27 16:53 Message: Logged In: YES user_id=488500 Henry, you are right. The only issue I see is detecting and fixing this problem if the paragraph was split into several segments. No dark magic, but not simple anyway... ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-02-27 16:41 Message: Logged In: YES user_id=545103 If I encounter the following segment: <seg>Word</f0><f1>more words</f2>, plus <f3>more words</seg> I could very simply convert it to the following: <seg><f0>Word</f0><f1>more words</f1>, plus <f2>more words</f2></seg> You don't really need to know about the original tags, do you? ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2006-02-27 16:26 Message: Logged In: YES user_id=488500 Not really, because there's no longer any information there (only, say, "<f3>"), but OmegaT can more or less reliably guess that. Not easy, though... ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-02-27 16:18 Message: Logged In: YES user_id=545103 I didn't intend to overwrite the TM files, but to apply the conversion in-memory only. So, is it possible? Can you renumber the tags in a segment correctly, and simply stick missing ones in front and behind? ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2006-02-27 16:06 Message: Logged In: YES user_id=488500 Hi Henry, Well... That's some work to rewrite tag definitions on-the-fly, and in case of TMX files in /tm folder OmegaT cannot (by contract) modify these files. ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-02-26 16:01 Message: Logged In: YES user_id=545103 Instead of displaying warning messages, can't these tag errors be automatically corrected? Is it possible to automatically convert The TMX to the new format? ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-02-23 10:55 Message: Logged In: YES user_id=545103 I definitely agree that the user should be aware of the issue. It should be mentioned in the documentation, and I think the issue warrants an alert message too. However, it'll soon get obnoxious if you work with older TMs a lot, so I'd strongly advice adding the familiar "Do not bother me again" option to such a message dialog. Furthermore, this issue only appears when working with RC7 or later with TMs created by RC6 or earlier, so before displaying any messages, that should be checked, so messages aren't displayed unnecessarily. ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2006-02-23 01:24 Message: Logged In: YES user_id=915082 I have a project created with RC6, I use RC7 with it: all the tagged segments are wrong so there _will_ be problems. An alert (not error, sorry :) message should be there to remind me that I have created the project TM with such version and that using a different version can result in project TM matching problems. ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2006-02-22 18:03 Message: Logged In: YES user_id=488500 JC, It's OK to indicate the exact version number, but why should OmegaT produce an error message importing any TMX, and why on Earth on its own (!!!) TMX? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520347&aid=1436563&group_id=68187 |