From: SourceForge.net <no...@so...> - 2009-01-21 08:12:09
|
Feature Requests item #1295953, was opened at 2005-09-20 04:51 Message generated for change (Comment added) made by didierbr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520350&aid=1295953&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jean-Christophe Helary (brandelune) Assigned to: Nobody/Anonymous (nobody) Summary: Coloring the tags in tag validation window Initial Comment: the tag validation window could use some coloring. mistaken tags could be displayed in <red> for ex. so that the eye spots them right away. ---------------------------------------------------------------------- >Comment By: Didier Briel (didierbr) Date: 2009-01-21 09:11 Message: >From Jean-Christophe: ----- There are 3 types of valid tag modifications 1) order change 2) omission 3) addition to each type correspond errors that will make the (ODF) document invalid: 1) overlapping 2) omission of one part of a tag pair 3) addition of one part of a tag pair Using different colors for valid (blue ?) and for invalid (red ?) modifications would greatly speedup the tag validation process. ----- Didier ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2006-12-11 17:48 Message: Logged In: YES user_id=915082 Originator: YES currently, only the tags missing in a tag pair and overlapping tags (inversed) really have the potential to mess with the file. the two above categories should be indicated in contrasted colors (red for missing, orange for overlapping for ex) single tags/full pairs missing/ tag groups for which the order has been changed do not have such a destructive potential and could be colored in blue/green etc. ---------------------------------------------------------------------- Comment By: Didier Briel (didierbr) Date: 2006-11-08 15:26 Message: Logged In: YES user_id=1343245 <<No, tags appearing as text would be properly escaped, and the regex would not catch those.>> Thanks for the clarification. Didier ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-11-08 15:17 Message: Logged In: YES user_id=545103 No, tags appearing as text would be properly escaped, and the regex would not catch those. ---------------------------------------------------------------------- Comment By: Didier Briel (didierbr) Date: 2006-11-08 13:50 Message: Logged In: YES user_id=1343245 <<Well, the regex needs to be tested, but it should catch only OmegaT tags.>> Except when the text contains an OmegaT tag, but as text, or am I missing something? <<And I think I can even work out which tags are missing or extra and which aren't.>> This would be very nice. ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-11-08 13:25 Message: Logged In: YES user_id=545103 Well, the regex needs to be tested, but it should catch only OmegaT tags. And I think I can even work out which tags are missing or extra and which aren't. ---------------------------------------------------------------------- Comment By: Didier Briel (didierbr) Date: 2006-11-08 09:10 Message: Logged In: YES user_id=1343245 <<anything that matches </?[a-z]+\d+> is output as <font color=red></?[a-z]+\d+></font> or something.>> Aren't we going to display text as tags, then? What we want is really identify tags, not text looking like tags. Didier ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2006-11-08 04:35 Message: Logged In: YES user_id=915082 sorry, not knowing the code I did not figure out the dependancy that way. I was thinking more a simple regex thing when the validation table is created. anything that is a tag is colored. after all this is simple html that we are dealing with here no ? anything that matches </?[a-z]+\d+> is output as <font color=red></?[a-z]+\d+></font> or something. ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-11-08 04:15 Message: Logged In: YES user_id=545103 By dependent I meant that it's not possible to implement this RFE before 1363760 is implemented. However, thinking about it, there may be a way to do this without first implementing 1363760. We could simply use regex to identify tags in the source, and check whether they appear in the target, and vice versa, and simply colour everything that doesn't have a corresponding tag in either segment. ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2006-11-08 02:20 Message: Logged In: YES user_id=915082 maybe the first step would be to implement this one, and then to get more complex behaviors as in 1295953. ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-11-07 20:50 Message: Logged In: YES user_id=545103 Ok, RFE remains open. Depends on implementation of RFE 1295953 though. http://sourceforge.net/support/tracker.php?aid=1545637 ---------------------------------------------------------------------- Comment By: Didier Briel (didierbr) Date: 2006-11-06 08:30 Message: Logged In: YES user_id=1343245 Just tested. No, there is no colouring of the tags in the tag validation window. Didier ---------------------------------------------------------------------- Comment By: Henry Pijffers (henry_pijffers) Date: 2006-11-06 00:33 Message: Logged In: YES user_id=545103 Isn't this implemented by now? Please close if yes. ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2006-06-23 11:40 Message: Logged In: YES user_id=488500 a duplicate of this rfe was posted as https://sourceforge.net/support/tracker.php?aid=1509031 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520350&aid=1295953&group_id=68187 |