Your comment is a bit off-topic because I was talking about a technical problem and you suggested a regulatory solution but I will still answer.
Hebrew open source localization is a very small swamp, most of the external projects which are included by default in Ubuntu are handled by me to make sure they are aligned with the rest of the system and that the translation is upstream.
I can try contacting myself although I’m pretty sure I won’t answer.
If I understand correctly you’re suggesting keeping them untranslated or copy the original string to the translation, it could work in some cases but I’d rather have a simpler solution such as marking a string or a whole template as irrelevant for Hebrew so the new translators won’t invest time in a CLI app that the users won’t benefit from.
I’ll explain briefly about the Hebrew in CLI:
Hebrew is written from Right-To-Left (Hence RTL) and most terminal emulators does not support that either because of encoding (Unicode) or incorrect implementation of BiDi (Bi-Directional) algorithms including the Linux kernel most basic TTY/PTY/whatever.
So there are cases where the messages appear correctly on screen when using CLI in the following cases:
- The terminal fully supports Unicode (MLTerm)
- The CLI app is translated in reverse (dlroW olleH)
- FriBiDi is implemented correctly and the app is translated correctly.
Mixing those methods usually leads to a big mess and unreadable messages on screen.
The only place where Hebrew is supported correctly on CLI is either the Hebrew version of Ubuntu CLI installer (and the name of the language in grub before that) or the Debian installer.
Besides these two, although there has been some nice attempts to fix this issue it was never standardized and it simply frustrates many Hebrew users daily.