omegat-google-translate-without-api-key Activity
Status: Abandoned
Brought to you by:
bvfalcon
Activity for omegat-google-translate-without-api-key
-
Dimitry Prihodko posted a comment on ticket #4
Cool, it works now but provides two variants of translation))) Two is better than none, so thank you! )))
-
Will download tomorrow, check and advise result Thanks a lot -- Отправлено из Mail.ru для Android четверг, 01 июня 2023г., 23:54 +04:00 от Vladimir Bychkov bvfalcon@users.sourceforge.net : Solved in version 1.1.2 [tickets:#4] Does not work with OmegaT 6 Status: open Milestone: 1.0 Created: Thu Jun 01, 2023 01:54 PM UTC by Dimitry Prihodko Last Updated: Thu Jun 01, 2023 01:54 PM UTC Owner: nobody the script seemd to be not working with OmegaT 6, though with 5.7 it works (although not always flawlessly)....
-
Vladimir Bychkov modified ticket #4
Does not work with OmegaT 6
-
Solved in version 1.1.2
-
omegat-google-translate-without-api-key released /google-translate-without-api-key-1.1.2.jar
-
Vladimir V. Bychkov committed [4a7233] on Code
feat: adapt to new google-translate format
-
Does not work with OmegaT 6
-
Hello Mr. Jiayuan. But I found out if switch the entries back and forth, the result can be displayed May be. From what language do you translate? And what is the target language? If it is possible, attach hier an example (OmegaT project), with this problem can place. Unfortunately I cannot reproduce it myself.
-
How to use the tool.
-
Jiayuan Yu posted a comment on ticket #3
I thought it was not showing the results because it too to long to response. But I found out if switch the entries back and forth, the result can be displayed. Forgot to change the topic. The proper topic should be: Result not Showing unless Switch Entries Back and Forth
-
Sometimes Takes Too Long to Display Result
-
As any other translation: in Menu "Options -> Translate -> Google Translation (without API key)"
-
Yusuke Ozaki created ticket #2
How to use the tool.
-
MT result after "." (period) and ";" (semicolon)
-
Kos Ivantsov posted a comment on ticket #1
The problem is indeed solved, thank you. This ticket can be closed.
-
Is problem yet actual? I think, it was solved in version 1.1.0. Please attach screenshots, because in my cases problem not appear.
-
-
Added slf4j support
-
Multiple rows in segment translation
-
small optimization
-
MT result after "." (period) and ";" (semicolon)
-
Home
-
Home
-
-
Initial revision
1
