- Sep 6, 2016
- 130
- 400
- Thread starter Alexander Krisnov
- Start date
-
- Tags
- rpg
- May 26, 2017
- 1,334
- 312
It would be really neat if someone more code savy could have this plug into a good translation software like google or something so that it actually translates decently... the tool is good but having a dedicated translation software integrate into it would take this to the next level
- Sep 9, 2017
- 74
- 91
yeah, have been looking for them like a day. found only
You must be registered to see the links
. i think google in my region is shit because i rarely find what i want to find
- Sep 9, 2017
- 74
- 91
well Translation aggregator is really good and there is also VNR (visual novel reader) and chiitrans
- Sep 6, 2016
- 130
- 400
I don't know. Have you read the whole topic? Maybe you missed the part that the translatorserver isn't online anymore?
- Sep 6, 2017
- 207
- 603
Translations back again, but you need to do the following in order to fix it:
(Instructions taken from a comment by
(Instructions taken from a comment by
You must be registered to see the links
at
You must be registered to see the links
)- Download the program normally from the github
- go to
You must be registered to see the linksand press start scripting, copyYou must be registered to see the linksinto it
- click publish then deploy as web app, give the script whatever name and description you want, set "Execute the app as:" to me and "Who has access to the app:" to anyone, even anonymous then deploy
- authorize the script then copy the "Current web app URL"
- download my
You must be registered to see the linksfile
- replace the original "auto_translate.rb" with the new one
- open up the new "auto_translate.rb" file with notepad++ (
You must be registered to see the links)
- ctrl+F and search YOUR_WEB_APP_HERE
- replace "YOUR_WEB_APP_HERE" with the link you copied to the web app
- done
- Feb 21, 2018
- 286
- 218
According to information from that forum tho. that method is...kind of shady. since APIS usually cost money. i would wonder if you could face repercussions from it.
- Sep 6, 2017
- 207
- 603
- Feb 21, 2018
- 286
- 218
They are? and of course if they weren't the first thing would be terminating your account since you're connected with it.
IF you're sure it's safe to use then there's no problem :3
IF you're sure it's safe to use then there's no problem :3
- Sep 6, 2017
- 207
- 603
Yeah, they only stop the service for up to 24 hours if you abuse of it, but you need to really use it, for example i asked for 657.798 requests before i get locked for 24 hours.
You get to use it again after 24 hours again, and there is no "ban" until you abuse of it again, but it's only for 24 hours.
Can you help me, I get the Output directory not found. I think the problem is in the google script that I need to make. Can you give me the right route? like option 1 or 2?
- Sep 6, 2017
- 207
- 603
I totally forgot all about this lol, i use it once.
But are you sure you are selecting an output directory? The Google API has nothing to do with that error message.
Unfortunately I do think it is something to do with the Google API, as unlikely as that sounds, because before using the Google API I had not trouble setting up a working directory, only connecting to the non-working server. Now, even using the same directory as before, it comes up with the same error as if I hadn't set an output at all. Very strange.
Help, it keeps saying
Translation API failed for [うさぎのしっぽ] with message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Translation API failed for [薬の材料] with message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Translation API failed for [薬の材料] with message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
and the same "certificate verify failed" for everything.
Translation API failed for [うさぎのしっぽ] with message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Translation API failed for [薬の材料] with message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Translation API failed for [薬の材料] with message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
and the same "certificate verify failed" for everything.
Make sure the script is set to be accessible by 'Everyone, even anonymous'. If that doesn't change anything, on the Github page, Tranquwil also gave instructions to change the option of the script.
"I used option 2 for the script but I don't understand the differences between them well and both seem to work. If anybody wants to switch just uncomment line 23, comment out 27-32 and publish as a new project version. After that if you want to swap again you can just set it to whichever version while publishing without needing to change the script."
Try changing it to Option 1. Also, uncomment means to remove the // at the start of the line, comment means to add // at the start of the line.