Hi, Samuel !
On 9/12/07, Samuel Murray <leuce@...> wrote:
So, this feedback much better ;)
> 1. Run OmegaT2 by clicking run.cmd
> 2. I created a new project using Project -> New
> 3. I did not select sentence segmentation (it wasn't selected by default)
> 4. After clicking OK, nothing happened, so I added a source text file to
> the /source/ folder.
> 5. Then I used Project -> Reload sources to load the source text from
> the /source/ folder. Here, I double-clicked the source text file in the
> list, and OmegaT2 opened the file.
So, It's very good. Loading of new sources works perfect.
> 6. I realised that the segments are too large, so I went back to Project
> -> Properties and enabled sentence segmentation.
Application should inform you about reparsing files. Did you see
message box about it ?
BTW, when you change segmentation rules from project properties
dialog, this can be make some misunderstanding. When user change
anything in project properties dialog box, then he should think what
he make changes in the project. But old OmegaT implementation change
segmentation settings for OmegaT, not for one project. It means what
user changes global settings from project properties dialog box. I
think it's wrong way.
I can implement project-level segmentation rules, but are we really
need it ? I think we can just remove "Segmentation..." button from the
project properties dialog. In this case user will be able to change
segmentation rules from the main menu. What do you think about it ?
> 7. OmegaT2 didn't change the way the current file was displayed -- it
> was still segmented by paragraph -- so I used Project -> Reload sources
> again. The I got an error message "java.lang.NullPointerException".
Yes, it will displays paragraphs in the same way as it stored in
source document. But when you will click on the paragraph, editor will
show only one segment for translation, not a full paragraph. I don't
know how to display it better. If anybody know better solutino, lets
About NullPointerException. Coud you send me log of application with
stack trace ? You can see log in the OmegaT2.log file in the current
directory, or on the console.
> 8. I clicked OK on the error message, and OmegaT2 reloaded the source
> file, but it is still segmented by paragraph.
> 9. Then I closed OmegaT2, and rerun it using run.cmd. I tried to open
> the project I created previously, but I was unable to select it in the
> opening dialog, and it doesn't have an OmegaT icon.
This is happen because you didn't "save" project. But I agree, you
should be able to open project when directories was created, even you
didn't click "save". Will fix it soon.
> So here's my suggestion:
> 1. Fix the bug that the user is unable to reopen an existing project.
> 2. Decide how a user is supposed to add source files, implement it, and
> create buttons or menu items for it.
It will be able by "Load/Reload sources" menu item. Is it okay ?
I think old-style implementation, when "import sources" copyed files
into source directory is not so good. User can select source not on
the file system, but in SVN, for example. And event user make sources
on the file system, but not in the default place in the project
subdirectory, then sometimes is not so good to copy imported files in
So, I think user should be able to import files only by copy files in
the source directory, then click "Reload sources" menu item.
> Do these two things first before adding any new features. It's no good
> you're adding many, many useful features, but the features can't be used
> because of two very critical, essential bugs.
I absolutelly agree. I will fix these bugs asap.
My projects works correctly yet. Of course, my current testing is
not enought to say "application is stable now". It is very important
to give feedback from users, because different users use application
by different scenarios, and some errors can be found only by some