Fomatting in omegat3/30/2023 The class SRX predates any support for the actual SRX XML serialization format, so I think the best way to understand it is as a synonym for "segmentation". My proposal would be the following: add a checkbox in the GUI, but when the user unchecks it, display a dialog "do you want to uncascade current rules?", with 3 possibilities: 1) YES (apply the algorithm and refreshes the editor), 2) NO (uncheck the box but do not touch the rules), 3) CANCEL (leave all as is, keep the box checked) In my project, for which I just sent you the link in previous message, I also implemented the possibility to "uncascade" an SRX file: not only it sets cascade="no", but it copies all the rules which would have applied to a given language in the correct location, ensuring that the resulting file is equivalent to the previously cascaded file. The simplest, of course, is to simply set the boolean value.īut if you know what cascade means, you certainly understand that all language rules are affected when you uncheck the box : all rules coming from next language maps are not used anymore.ī. What to do when the user checks/unchecks the box?Ī. Now that cascade is really supported by OmegaT, shouldn't we add a checkbox in the already existing GUI panel?.do you plan at any time to implement a window or a panel to edit these fields? if not, shouldn't we delete SRXOptionsModel?.This is the only class which uses getters and setters for segment subflows (but actually it does not support cascade) However, you have a class .datamodels.SRXOptionsModel which seems written for that but actually unused (I checked that it is called nowhere) In the meantime I found a location where these accessors may/should be used.Īctually, your segmentation customizer (GUI) does not allow to modify these parameters. I would be OK with you not adding this new getter, but I don't feel that strongly about it. Now that I understand your reason, we can think about whether or not coherency is a good thing in this instance, given that the current code has some obvious problems.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |