Create your AI Cum Slut -70% for Mother's Day
x

Tool Translator++ 4.9.28 Standard Version / Developer Version

5.00 star(s) 2 Votes
Discussion Reviews (2)
W

wsg123

Newbie
Mar 4, 2022
16
1
TheExorcist- said:
Translator++ 7.5.2 -------->
You must be registered to see the links


Thanks for sharing, my friend. Dev_past

I've added the plugins I currently have.
Click to expand...
Thank you for sharing.
I found this version of Google Translate (not Google Page) works correctly.
0xf00 error no longer occurs.
It seems the T++ developer has already fixed this issue.
 
L

lyk5t

Member
Sep 25, 2021
149
50
I think you'll probably be very happy to hear this news, I've installed the deepl extension I have and verified that it works, I'll post it here after I test it some more
 
  • Like
Reactions: Hein Daddel
L

lyk5t

Member
Sep 25, 2021
149
50
There are problems like these in the tests I made, it does not work perfectly, the biggest problem is the problem of spreading the word in a box to other boxes, if I need to explain in a little more detail
"before translation"
box 1: "how are you? nice to see you" - "no translation"
"after translation"
box 1: "how are you? nice to see you" - "how are you? "
box 2: "no translation" - "nice to see you"
box 3: "no translation" - "nice"
the image is the same in this way, there was no problem when I tried it in the other translation, but there is such a problem in the deepl extension, if this problem is solved, it can be used very well. I did not want to touch it because it works, if anyone wants to touch it, the file is below
 
  • Like
Reactions: Hein Daddel and Dark Pixel
Hein Daddel

Hein Daddel

Active Member
Modder
Nov 22, 2019
707
1,335
lyk5t said:
There are problems like these in the tests I made, it does not work perfectly, the biggest problem is the problem of spreading the word in a box to other boxes, if I need to explain in a little more detail
"before translation"
box 1: "how are you? nice to see you" - "no translation"
"after translation"
box 1: "how are you? nice to see you" - "how are you? "
box 2: "no translation" - "nice to see you"
box 3: "no translation" - "nice"
the image is the same in this way, there was no problem when I tried it in the other translation, but there is such a problem in the deepl extension, if this problem is solved, it can be used very well. I did not want to touch it because it works, if anyone wants to touch it, the file is below
Click to expand...
Many thanks for the file. Deepl under Translator++ runs very well if you stick to the following procedures:

1. the files to be translated per translation run must not exceed the number of 440 “batches”. This corresponds to approx. 740kByte of data. So do not mark all files if there are more.
2. to translate larger files, the files must be split. (scrypt.rpy in script1.rpy, script2.rpy, etc.) (always 740kbyte large) Then merge them again later after the translation.
3. wait approx. 3 hours after a translation run with Translator++, otherwise Deepl will not run.

Deepl has this lock under Translator++.

Vielen Dank für die Datei. Deepl unter Translator++ läuft sehr gut, wenn man sich an folgende Abläufe hält:

1. Die zu übersetzenden Dateien pro Übersetzungsdurchgang dürfen die Zahl von 440 "Batch's" nicht überschreiten. Das in spricht ca. 740kByte Datenmenge. Also nicht alle Dateien markieren, wenn es mehr werden.
2. Um größere Dateien zu übersetzen muss man die Dateien aufteilen. (scrypt.rpy in script1.rpy, script2.rpy, usw.) (immer 740kbyte groß) Diese dann nach der Übersetzung später wieder vereinen.
3. Nach einen Übersetzungsdurchgang mit Translator++ ca. 3 Std. warten, sonst läuft Deepl nicht.

Deepl hat unter dem Translator++ diese Sperre.
 
Last edited:
  • Like
Reactions: Garter2269 and lyk5t
TheExorcist-

TheExorcist-

Member
Dec 8, 2019
173
165
Hein Daddel said:
Many thanks for the file. Deepl under Translator++ runs very well if you stick to the following procedures:

1. the files to be translated per translation run must not exceed the number of 440 “batches”. This corresponds to approx. 740kByte of data.
2. to translate larger files, the files must be split. (scrypt.rpy in script1.rpy, script2.rpy, etc.) Then merge them again later after the translation.
3. wait approx. 3 hours after a translation run with Translator++, otherwise Deepl will not run.

Deepl has this lock under Translator++.

Vielen Dank für die Datei. Deepl unter Translator++ läuft sehr gut, wenn man sich an folgende Abläufe hält:

1. Die zu übersetzenden Dateien pro Übersetzungsdurchgang dürfen die Zahl von 440 "Batch's" nicht überschreiten. Das inspricht ca. 740kByte Datenmenge.
2. Um größere Dateien zu übersetzen muss man die Dateien aufteilen. (scrypt.rpy in script1.rpy, script2.rpy, usw.) Diese dann nach der Übersetzung später wieder vereinen.
3. Nach einen Übersetzungsdurchgang mit Translator++ ca. 3 Std. warten, sonst läuft Deepl nicht.

Deepl hat unter dem Translator++ diese Sperre.
Click to expand...
Are you doing anything extra during the setup? Because it's not working for me!

"Translation failed. Please check your DeepL addon or network connection."
 
L

lyk5t

Member
Sep 25, 2021
149
50
Hein Daddel said:
Many thanks for the file. Deepl under Translator++ runs very well if you stick to the following procedures:

1. the files to be translated per translation run must not exceed the number of 440 “batches”. This corresponds to approx. 740kByte of data. So do not mark all files if there are more.
2. to translate larger files, the files must be split. (scrypt.rpy in script1.rpy, script2.rpy, etc.) (always 740kbyte large) Then merge them again later after the translation.
3. wait approx. 3 hours after a translation run with Translator++, otherwise Deepl will not run.

Deepl has this lock under Translator++.

Vielen Dank für die Datei. Deepl unter Translator++ läuft sehr gut, wenn man sich an folgende Abläufe hält:

1. Die zu übersetzenden Dateien pro Übersetzungsdurchgang dürfen die Zahl von 440 "Batch's" nicht überschreiten. Das inspricht ca. 740kByte Datenmenge. Also nicht alle Dateien makieren, wenn es mehr werden.
2. Um größere Dateien zu übersetzen muss man die Dateien aufteilen. (scrypt.rpy in script1.rpy, script2.rpy, usw.) (immer 740kbyte groß) Diese dann nach der Übersetzung später wieder vereinen.
3. Nach einen Übersetzungsdurchgang mit Translator++ ca. 3 Std. warten, sonst läuft Deepl nicht.

Deepl hat unter dem Translator++ diese Sperre.
Click to expand...
Thanks for the information, there is probably no way to remove that lock, but there is no settings menu in the extension, there used to automatically translate up to 440 letters or words and so on, so we didn't have to split the file, it automatically split itself, it would be great if we could set this, I guess there are no such settings in trans++, I need to look at the source code.
 
  • Like
Reactions: Hein Daddel
L

lyk5t

Member
Sep 25, 2021
149
50
Hein Daddel said:
Many thanks for the file. Deepl under Translator++ runs very well if you stick to the following procedures:

1. the files to be translated per translation run must not exceed the number of 440 “batches”. This corresponds to approx. 740kByte of data. So do not mark all files if there are more.
2. to translate larger files, the files must be split. (scrypt.rpy in script1.rpy, script2.rpy, etc.) (always 740kbyte large) Then merge them again later after the translation.
3. wait approx. 3 hours after a translation run with Translator++, otherwise Deepl will not run.

Deepl has this lock under Translator++.

Vielen Dank für die Datei. Deepl unter Translator++ läuft sehr gut, wenn man sich an folgende Abläufe hält:

1. Die zu übersetzenden Dateien pro Übersetzungsdurchgang dürfen die Zahl von 440 "Batch's" nicht überschreiten. Das in spricht ca. 740kByte Datenmenge. Also nicht alle Dateien markieren, wenn es mehr werden.
2. Um größere Dateien zu übersetzen muss man die Dateien aufteilen. (scrypt.rpy in script1.rpy, script2.rpy, usw.) (immer 740kbyte groß) Diese dann nach der Übersetzung später wieder vereinen.
3. Nach einen Übersetzungsdurchgang mit Translator++ ca. 3 Std. warten, sonst läuft Deepl nicht.

Deepl hat unter dem Translator++ diese Sperre.
Click to expand...
Code: 
"maxRequestLength": {
                "type": "number",
                "title": "Max Request Length",
                "description": "The maximum length of characters for each translation batch.\nEach translator has a different specs.\nI recommend less than 2000 for WEB front-end translator that uses GET parameter.",
                "default":400,
                "attr": {
                    "max":2000,
                    "min":20
It seems like there is not much need to split the file, it is set to 400 at a time, but the following "attr": {
"max":2000,
"min":20
this section can be tweaked
 
You must log in or register to reply here.
Top Bottom
5.00 star(s) 2 Votes