Zeta resource editor is not accepeting the ID code genereated by Google

Question

1.00/5 (1 vote)

See more:

Zeta Resource Editor is not accepting the ID code generated by Google, returns 404 error for ID.

I know this is old code, but was wondering if you have an updated version available for new Google Translate API logic.

Thanks.

What I have tried:

no other resource tried since the Api call is embedded in the source code.

Would like a resolution as needed for a project.

Posted 17-Jun-17 5:27am

Member 3773125

Updated 17-Jun-17 6:24am

Add a Solution

Comments

Richard MacCutchan 17-Jun-17 12:05pm

You probably need to be asking this question at Zeta or Google.

Patrice T 17-Jun-17 12:07pm

Ask Zeta and Google !

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RickZeeland · Answer 1 · 2017-06-17T06:24:00

Solution 1

If you are brave you can get the source code from GitHub and modify that: GitHub - UweKeim/ZetaResourceEditor: Free multilingual, parallel .NET resource file editing[^]
You can also make an "issue" on GitHub about the problem.

Posted 17-Jun-17 6:24am

RickZeeland