Activity for Martin Engelke
-
Martin Engelke modified a comment on ticket #1285
Edit: I would expect the Autocomplete window to be on top and focused as long as I am not performing an escape event, so the inline commands should not work anymore, which is obvisiously not the case. Another approach would be to give the Shortcuts in the EditorShortcuts.properties the highest priority so that certain inline movements/actions will be disabled if I choose to use them for another task.
-
Another approach would be to give the Shortcuts in the EditorShortcuts.properties the highest priority so that certain inline movements/actions will be disabled if I choose to use them for another task.
-
autocomplete/character table/...-pane is not focused properly [macOS]
-
Alt+Up/Down already triggers alternative fuzzy matches.
-
Any news regard this issue? I do not want to downgrade since my Omegat 6.1.0 is just running fine on macOS. The fast scrolling is bothering me since beginning but I tried turn a blind eye regarding that issue, since I love your Tool. I would now like to get rid of the last small bugs.
-
Multiple filters (refined search)
-
The request relates to this one.
-
Negative search
-
Search/Replace within a Filter
-
For sure.
-
That sounds fantastic. OmegaT made my job as a translator a lot easier. Am 31.07.2024 um 05:41 schrieb Jean-Christophe Helary brandelune@users.sourceforge.net: It seems to me that in the current state of affaire, a search/replace within a filter and a negative search are 2 functions that would help a lot and stay in line with the current OmegaT search/filter paradigm. [feature-requests:#1755] https://sourceforge.net/p/omegat/feature-requests/1755/ More Powerful Search and Replace Filters Status:...
-
Hi, Thank you for your reply. I did so, but especially for new words/wordcreations (patents) it happens regularly, that I am not 100 % sure about which proper word I am going to use in that case. In the very end of the document I often have to do a replacement loop, since one of the last paragraphs may reminds me of better rethinking about my decision ^^ Am 31.07.2024 um 05:13 schrieb Jean-Christophe Helary brandelune@users.sourceforge.net: You could check the issues for your document and include...
-
Edit: I tried out a few RegEx: This one was the closest I found to be practical: (?i)\b(?:srcword).*\b(?:trgtword)[^\s]+ which is just showing me the the preferred translated segments, if I search for source and target simultaneously. If I could just do a negotiation of this Regex, to find all segments, which does not include the right target in case of a certain source, I would be happy for now. Maybe you could reach this by a script and RegEx lookarounds (which I will proof next), but that leads...
-
Editor Pane does not focus after Search / Replace
-
More Powerful Search and Replace Filters
-
I like that idea, imagine you would put that together with my demand for a Hit Counter. Amazing – people could just dynamically see how many hits they score for getting more indepth/concrete with their search pattern.
-
Hit Counter (Search Statistics)
1
