Page 1 of 1

Translators failing

Posted: Sun Feb 19, 2017 6:19 pm
by Mike Lorrey
Please note that language translator devices/huds seem to be very intermittent or failing entirely this week. Possibly the webservice providing the translations has clamped down on the number of free translations (I believe its google doing this), but we need to look at other options. This may require a scripted process that allows the user of the hud to register with the website providing their translations.

Re: Translators failing

Posted: Mon Feb 20, 2017 12:59 pm
by Constance Peregrine
This should be the scripted translator that Magnuz Binder fixed up for us when the old one pointing to a microsoft place added limiters which essentially made them unusable.

This new one includes a backend choice option and it is default set to LP (lost paradise grid) as they had agreed to add an additional choice for Magnuz.

So goto the backend choice and click on (I am unsure what he named that atm...but the non LP one) the other one and all is well.

He did post recently that people could go back to his previous one with only his own backend.

He can be reached in g+ or in the Metropolis grid HG hypergrid.org:8002:media (and quite a few other regions but this one is cool also)

Re: Translators failing

Posted: Sat Feb 25, 2017 2:51 am
by Mike Lorrey
Constance Peregrine wrote:This should be the scripted translator that Magnuz Binder fixed up for us when the old one pointing to a microsoft place added limiters which essentially made them unusable.

This new one includes a backend choice option and it is default set to LP (lost paradise grid) as they had agreed to add an additional choice for Magnuz.

So goto the backend choice and click on (I am unsure what he named that atm...but the non LP one) the other one and all is well.

He did post recently that people could go back to his previous one with only his own backend.

He can be reached in g+ or in the Metropolis grid HG hypergrid.org:8002:media (and quite a few other regions but this one is cool also)
Here's the URL in one of the translators in my inventory that was buggy (yes its a Magnuz Binder script): http://5.9.108.75/cgi-bin/xl.sh

The one by Minethere Always that was using the microsoft service is permanently nonfunctional.

There is also a translator that appears to have been created in Craftworld that is used in All City and other Brazilian grids (they call it a tradudor). The URL used in their script is: https://translate.yandex.net/api/v1.5/t ... 1f644ecbe2

This is also exhibiting buggy or nonfunctional behavior.

Re: Translators failing

Posted: Sat Feb 25, 2017 1:46 pm
by Constance Peregrine
Here is Magnuz direct info which should help fix things up.

The one with minethere always is the one to throw away. It is the one that was passed around quite a bit but started throwing errors something like reached limit or so, the microsoft one.

You should be able to fix it all up with the opensource script Magnuz points to if you wish.

Or maybe Kitely can also add a back end option?