Hi, the new release got delayed until I can figure out how to add the new terminology support without having to train new base models for each language (I have some solutions for that, but it's still not optimal). I have recently got funding for publishing a new version of the engine (with Mac and Linux support), so I should be able to also include the terminology support in that release (and hopefully other outstanding things).

[Khalid-kamal]

          Hi, the new release got delayed until I can figure out how to add the new terminology support without having to train new base models for each language (I have some solutions for that, but it's still not optimal). I have recently got funding for publishing a new version of the engine (with Mac and Linux support), so I should be able to also include the terminology support in that release (and hopefully other outstanding things).

Originally posted by @TommiNieminen in #90 (comment)

[Khalid-kamal]

Hi Tommi,
I am only reminding of your reply to the issue of (rtl) is not supported in OpusCatMTEngine_v1.2.4.0 and of course in the new edition and you promised to add new feature relating to formatting

[TommiNieminen]

The problem is I don't remember what the RTL issue was about, so I need to know what parts of the user interface should be changed to fix that? Was it that the Translate functionality did not display RTL text correctly?

[Khalid-kamal]

Yes, when I translate from English into Arabic the translation is displayed from left to right which is difficult to read. If you remember, we talked about richtext also if it is supported, it will be nice. Khalid Kamal Translation Manager Alukah English Website Mobile: + 02 01124776419 E-mail: ***@***.*** ***@***.*** On Tuesday, April 30, 2024 at 12:58:58 PM GMT+3, TommiNieminen ***@***.***> wrote: The problem is I don't remember what the RTL issue was about, so I need to know what parts of the user interface should be changed to fix that? Was it that the Translate functionality did not display RTL text correctly? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>