Hello! I kinda agree with you about OmegaT. I'm probably a bit too used to MemoQ to love OmegaT as much as it deserves haha. Lokalize and Poedit are great options for Linux too!
Regarding your question, this method only allows OmegaT to handle the file, it does not extract the to-be-translated strings from the rest of the text. Our team has been struggling with that part since day one. Currently, the best option that Niccolò (above) found with OmegaT is to tweak the segmentation rule.
To do so, go to your project Properties and click on Local segmentation rules. From there, click Add to add a rule. Choose a name for it (for instance "js ` strings" in the example below), and set the "language pattern" option to " .* ".
In the second box of the window, type a ` symbol as "Pattern before", and add another line so that you can also type it as "Pattern after". Tick both lines as "break/exception". This will add line breaks before and after each ` sign. It does not exactly extract the text, but isolate it from the rest so that it is slightly easier to read and translate in the editor. This is far from ideal but it is the only way that we've found for now. Please do let me know if you or anyone else finds a better method!
Don't forget to save your new settings and to reload the files in the project.
One other process we found is to convert and extract the strings from the .js file into an xliff with Rainbow from the Okapi Framework. This way, only the translatable strings are imported into the xliff and appear in the editor. Once the translation is done, you can convert your xliff back to a translated .js file. In my opinion, it is the most efficient way to go, but it requires more tinkering than simply dealing with CAT tools filters. I'll be glad to write a tutorial about that too if needed, though.
Hope this answers your question! Please don't hesitate to contact me should you need anything else.