Menu
▾
▴
[ omegat-Feature Requests-1202411 ] Display list of errors at the end of project loading
|
From: SourceForge.net <no...@so...> - 2009-04-22 14:24:54
|
Feature Requests item #1202411, was opened at 2005-05-15 20:10 Message generated for change (Settings changed) made by didierbr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520350&aid=1202411&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 Private: No Submitted By: Jean-Christophe Helary (brandelune) Assigned to: Nobody/Anonymous (nobody) >Summary: Display list of errors at the end of project loading Initial Comment: Ok, with all the testing I've done today I found that we need OmegaT to be smarter when it comes to loading projects. I'd propose something like this: Option 1) "Testing before loading" Use the OmegaT parser to check all the /source files without actually loading them. Output all the error messages to a log file. If there are no errors resume loading If there are errors, send a message like "some files in /source could not be parsed, verify them by checking the log and reload". The user gets the log, checks files one by one, and when everything is fixed reloads. Option 2) "Safe loading" OmegaT parses the files and loads them one by one. When a bad files comes in, OmegaT renames it to .bad, output the problem to the log, does not load the file and proceeds to the next file. Once the project is loaded, OmegaT sends a message like "some of the files in /source could not be loaded, I renamed them .bad. You can proceed with the current project and reload the totality after you verify the bad files by checking the log". Option 3) "Selective loading" When handling big projects, it is not necessary to get everything loaded at once. "Selective loading" would propose a check boxes pane for the totality of the /source contents (from directory to single files, in a similar way to when one wants a "custom" install of an app). That way, one can select only a directory, or a few files, considering that one gets the full benefit of the existing project TM. ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2005-12-23 14:00 Message: Logged In: YES user_id=488500 still targeted at post-1.6 ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2005-12-22 15:43 Message: Logged In: YES user_id=915082 have you advanced on this one ? (I am looking at all the RFEs with a developer's name assigned :) ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2005-09-19 21:43 Message: Logged In: YES user_id=488500 the next OmegaT release will be called 2.0 (not 1.5) ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2005-05-23 10:14 Message: Logged In: YES user_id=488500 OK, targeting for 1.5 then... ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2005-05-19 13:51 Message: Logged In: YES user_id=915082 About 2) I think your proposal is fine. ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2005-05-19 12:43 Message: Logged In: YES user_id=488500 No, not separately... OK, 1. Will increase the time needed for project load twice... 3. Is really unrealistic to do for 1.4.5, and also I don't see any benefit for the long run. Loading it's done pretty fast... What is implementable and sound fine for me is #2. What fo you think of the following approach: #2 revised "Safe loading" OmegaT parses the files and loads them one by one. - When a bad files comes in, OmegaT does not load the file and proceeds to the next file. - Once the project is loaded, OmegaT sends a BIG table message like === Some of the Source files could not be loaded: File Name | Reason filename.html | bag tag start on line 28 somefile.sxw | not an OpenOffice file Bundle.properties | illegal \\u sequence on line 324 ... === ---------------------------------------------------------------------- Comment By: Jean-Christophe Helary (brandelune) Date: 2005-05-18 02:13 Message: Logged In: YES user_id=915082 I proposed three options that would have the same result: ease project opening with big and potentially not "clean" projects. I think it should be up to you to see which one is the easiest to implement. 1) and 2) seem to me implementable within the existing code (without changing too much of it) while 3) requires a whole new paradigm for project loading (better in the long term eventually). 3) could be combined with 1) or 2) in the future. Do you want me to file them all separately ? ---------------------------------------------------------------------- Comment By: Maxym Mykhalchuk (mihmax) Date: 2005-05-18 00:03 Message: Logged In: YES user_id=488500 JC, I don't understand what EXACTLY you propose... Which one of the three should be implemented? They are pretty controversal... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520350&aid=1202411&group_id=68187 |