Recent changes to feature-requests

#1451 [fuzzy] option in "Check issues"

2026-04-08T03:23:40.649000Z

For those still using 6.0 or older versions, this is the regex that works as Flagged text:

[[fuzzy]+]|[fuzzy]+]|[[fuzzy]+

Zero Width Space as special character

2026-02-25T07:39:17.459000Z

It would be useful to have the zero width space (https://unicode-explorer.com/c/200B) in the character sheet accessible via Ctrl+Space

Add Basque machine translation engines

2026-02-21T10:26:50.302000Z

It would be great to have some machine translation engine running from inside OmegaT. I have no idea of how to add them, but these are the three available:

https://www.euskadi.eus/itzuli/
https://elia.eus/itzultzailea (info@elia.eus)
https://www.batua.eus/ (https://itzuli.vicomtech.org/en/api/)

#1616 Non-unique IDs when segmenting text blocks extracted by Okapi OpenXML filter

2026-02-13T16:48:57.401000Z

#1777 Installer to place selected manual in best folder for platform

2026-02-05T22:55:55.778000Z

status: open-fixed --> open

#1781 Externalize the script folder so that macOS users can access it

2026-01-12T05:22:24.284000Z

I reflect your comment in the another PR#1859
https://github.com/omegat-org/omegat/pull/1859/changes

#1781 Externalize the script folder so that macOS users can access it

2026-01-12T03:45:48.379000Z

@miurahr9 did you consider this comment of mine in the current implementation?

#1781 Externalize the script folder so that macOS users can access it

2025-12-30T08:42:02.974000Z

Sorry, it should have been scripts.

The folder you mention is an old artifact that was used as a very primitive API to access segment contents.

It has no relation whatsoever with what we call "scripts" here.

The scripts folder is what we discuss here and it is by default in the application folder.

Maybe it is time to rename that old script folder to something more explicit, and keep scripts for the OmegaT distributed scripts.

#1781 Externalize the script folder so that macOS users can access it

2025-12-30T08:36:20.812000Z

There is no script folder in the application folder in my OmegaT installation. There is script folder in the configuration folder which is created when OmegaT open the project.

Addtional comment;

I think there is incosistency in folder usage.

SegmentExportImport class uses the OmegaT Configuration script Directory to exchange data with external scripts. It writes source.txt, target.txt, and selection.txt to this directory and monitors it for import.txt. However, users typically store their scripts in the User-defined Scripts Directory. If a script wants to interact with SegmentExportImport feature, it must know to look in the configuration directory.

#1781 Externalize the script folder so that macOS users can access it

2025-12-30T05:08:45.192000Z

Ok, so, the script folder is in the application folder for any version of OmegaT. Some users know that it can be in the configuration folder and put either all or a part of the scripts in the configuration folder.

So the easiest and safest way to solve the issue is to check whether there is a script folder in the configuration folder. If there is none, install the scripts, if there is one, consider that it is user action and do not install anything.

What do you think?