Settings/Configure Segmentation... menu item disabled
Brought to you by:
laseray
Menu
▾
▴
This is not really a bug, unless something is wrong I have missed. Changes to segmentation stuff through the project configure dialog should result in reopening of the project. Thus, it is a deliberate action on the part of a user to make a change of the open project.
So it is more like just a design decision (for better or worse), since most users will not want to reopen the project, and have to decide upon the segmentation rules beforehand.
Thank Raymond...
If you say it's a design decision it must be so...
Then I should perhaps list this as a feature request, and perhaps you might re-consider this design decision ( like allowing me to touch my left ear with my right hand, but not with my left hand ;-)
Segmentation rules sometimes (or often, when you've just started using OmegaT+ and seen that default segmentation rules for English are not adequate, for example) need to be amended in the course of a translation project...
Users who don't want to re-open the project should not attempt to amend the segmentation rules after they've begun a project...
Okay, I understand what you are saying. I also have thought that the segmentation rules should be changeable in the process of a project. The problem is that even the smallest change in one rule will require a complete reopening of the project. This is overkill for say just adding one more character to segment on. A happy medium would be the best thing between having to have all rules up front and being able to apply them dynamically. The only workaround I can think of is just to new rules in small bunches so as to limit the number of times that reopening has to take place.
Go ahead and add it as a feature request, but I cannot say when I could get around to rethinking this. It would need a significant change to be useful without seriously disrupting the way it works currently.