Right now, the Settings search in Directory Opus only matches what’s shown in the current UI language.In practice, this works fine for casual use, but once you start using documentation, forum posts, or scripting references, things start to feel a bit disconnected.
If your UI is in a non-English language, you can only search using that language’s terms. Most official docs, forum answers, and scripting examples use English terminology.
So users often end up doing this small but annoying loop:
read English guide → find term → guess translation → search in UI → hope it matches.
Some UI translations are slightly different from the original concept, and sometimes multiple English terms map to similar localized labels.
I think the Settings search could feel a lot more natural if it didn’t care so much about the current UI language.Allow searching with English terms even when the UI is not in English.Settings search should be decoupled from localization layer and bound to canonical feature identifiers.
A toggle that prioritizes canonical feature names and internal identifiers would be very useful for power users.It would make it much easier to move between documentation, forum advice, and actual settings without constantly translating terms in your head (or in your GPT).
Thanks for considering this suggestion. I really appreciate the continued improvements to Directory Opus.
