PandaTwo / php-language-api

Automatically exported from code.google.com/p/php-language-api
0 stars 0 forks source link

Example Does Not Work #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Simply running the script as is using the included example does not work

What is the expected output? What do you see instead?
Should be a Italian translation of "Welcome to my website.". Does not print.

What version of the product are you using? On what operating system?
Window XP Pro. Firefox & IE7.

Please provide any additional information below.
Any suggestions, please let me know...

Original issue reported on code.google.com by eliabrah...@gmail.com on 17 Feb 2009 at 1:06

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Do you get any errors? 

Try setting error reporting to max. 

{{{
<?php

error_reporting(E_ALL);
ini_set('display_errors', 1);

// code

?>
}}}

It may be that you do not have allow_url_fopen set to true in your PHP.ini. This
setting determines whether PHP can make HTTP requests. 
Many hosts disable this and offer the PHP CURL extention for making HTTP 
Requests. 

The library does not check for allow_url_fopen as it is. It just tries it 
anyway.
This can be changed to use CURL if available. 

Original comment by buca...@gmail.com on 10 Apr 2009 at 10:43

GoogleCodeExporter commented 8 years ago
Converting from english to japanese gives a very wrong translation no where 
close to the real thing. This is very frustrating.

Original comment by flexy...@gmail.com on 27 Oct 2010 at 8:38

GoogleCodeExporter commented 8 years ago
Its not Supported for Urdu langauge. Can any please help me how to use this API 
for Urdu langauge.

Best

Mevora

Original comment by supp...@mevora.com on 25 Jul 2011 at 8:07

GoogleCodeExporter commented 8 years ago
it gives us {"responseData": null, "responseDetails": "Suspected Terms of 
Service Abuse. Please see http://code.google.com/apis/errors", 
"responseStatus": 403} error

Original comment by cgtechno...@gmail.com on 1 May 2012 at 5:59