I'm using the (unofficial) Google translate TTS api to retrieve mp3s to support disabled learners to read web pages. It all works fine, however we have an American accent (we're in the UK!). When I use Google translate however, it fetches the mp3 with a British accent - how do I invoke this behavior?
I've used the same GET request URL so I can assume it's not that:
http://translate.google.com/translate_tts?q=testing+1+2+3&tl=en
(I've played with other language codes (en-gb) with no luck - fr works for french however.)
Many thanks
You can specify a regional variation in the tl parameter after an _ character, e.g.
http://translate.google.com/translate_tts?q=testing+1+2+3&tl=en_us
http://translate.google.com/translate_tts?q=testing+1+2+3&tl=en_gb
http://translate.google.com/translate_tts?q=testing+1+2+3&tl=en_au
By using google's ".co.uk" translate site's GET request, you can generate British English.
So for example: translate.google.co.uk/translate_tts?q=Your+soundcard+works+perfectly&tl=en
Related
I've got a multilingual WordPress installation with buddypress using wpml.
The problem is for example my Spanish users fill in location in Spanish so then for example my English users can't find Spanish users by location because it's in Spanish and viceversa.
Any solution?
Your query is too broad to give a precise coding solution, but here are two ideas:
(1) Geotag the users instead of using free text searches.
Convert a user's location to geocoordinates when they enter it into their profile. Then do the same when someone does a text search, giving results in order of proximity.
You'll need an API for this. Have a look at Google's Geocoding API.
(2) Much easier, but much more limiting:
Limit locations to a dropdown list of nearest major location. Store these as generic identifiers for searching, but display them on screen in the user's required language.
I need to set up A/B testing for my homepage using Google Experiments. Thing is, my page serves 2 languages - English and German.
The path to homepage itself is simply / for EN, and /de for DE.
Then, I have the following variations of the homepage prepared:
/experiment-A and /de/experiment-A
/experiment-B and /de/experiment-B
The goal for the experiment is user's registration. I don't care which language the user has set. The question is: Do I need to set up 2 separate experiments for the two language versions?
Yeah, I'd set up two experiments. The plus side is you'll also be able to get some insights from it. I find Germans behave quite differently than our North American visitors.
I am using direction services and I get response like the following:
"Head north on Piazza del Duomo toward Piazza S. Giovanni/圣若望广场/聖若望廣場"
I saw this several times for sites in Florence.
For example, between Florence Cathedral and Battistero but there are more.
Is there anything I can do to fix this?
Thanks,
Amir
It must be a bug(data-defect?).
These chinese characters seem to be a real translation of Piazza S. Giovanni(of course the translation should not be there).
When I e.g. set the language to german I even get more translations(russian, hebrew,hungarian,greek)
I'm afraid the only thing you can do so far is to send a bug-report: https://code.google.com/p/gmaps-api-issues/issues/entry?template=Directions%20API%20-%20Bug
I am not a professional with websites - just an amateur DIY dabbler, so apologies in advance if this is rather simplistic.
I have three Wordpress sites. For simplicity, let's say they are widgets.com, blue-widgets.com and red-widgets.com.
With Google AdWords, this works well as I send all searches for 'red widgets' to red-widgets.com, searches for 'blue widgets' to blue-widgets.com and everything else to the generic widgets.com.
I am now targeting the Chinese market using the AdWords equivalent from the main search engine in China, which is Baidu.com.
Whereas with AdWords, it's pay-as-you-go and it doesn't matter which site you send the traffic to, Baidu is hard work. For companies outside China they need around $3600 pre-payment. For that, you are only able to promote one website. If I wanted to promote all three, I would have to set up three accounts and send them $10,800 (which is more credit than I am likely to spend with them in several years!)
So I have set up an account just for widgets.com Javascript redirects are specifically disallowed.
What I would like to do is to set up third level domains for red.widgets.com and blue.widgets.com and have them display the home pages for red-widgets.com and blue-widgets.com respectively.
Is there a simple way that I could achieve this and how?
I wonder if you can use many URLs, such as the following:
widgets.com
widgets.com?red_widget=1
widgets.com?blue_widget=1
If you can use such URL, you should be able to redirect the URL through a specific PHP code. Here is an example of a code that will redirection the initial URL to a new one:
if (isset($_GET['red_widget']) && $_GET['red_widget']=='1') {
header('Location: http://red-widget.example.com/');
exit;
}
Hope this helps.
I am developing a flight search engine for a customer, and currently the URLs look as follows (ad = destination airport, ao = origin airport, dates and number of passengers are not specified here):
http://example.com/#ad=S%C3%A3o+Paulo+-+Todos+os+aeroportos+(SAO),+Brasil&ao=Recife+-+Guararapes+Intl+(REC),+Brasil
My customer wants to make search pages more search engine friendly (SEO). The idea is that Brazilians who are looking for flights from, say, SAO to REC by e.g. Google should have a higher chance of finding that particular flight search engine.
The first step is probably replacing the fragment identifier (#) by a query string (?). The server then dynamically generates nice text content that can be viewed without JavaScript (search results would still be loaded via XHR). In my opinion, that makes a lot of sense.
Now, to make the URLs more search engine friendly:
(A) My customer proposes adding additional keywords into the URL, something like:
http://example.com?flights+to+Porto+Alegre&S%C3%A3o+Paulo+-+Todos+os+aeroportos+(SAO),+Brasil&ao=Recife+-+Guararapes+Intl+(REC),+Brasil
(B) I propose adding a slug instead, which can easily be internationalized, and which is good to read also for humans. Example:
http://example.com/pt_BR?ad=REC&ao=SAO/voos_de_Sao_Paulo_para_Recife
(C) Or, perhaps without a slug (but - due to parsability - only for a limited parameter set, which has the disadvantage of limiting sharing of URLs by users):
http://example.com/pt_BR/voos_de_Sao_Paulo_(SAO)_para_Recife_(REC)
What do you suggest? Any examples of good URLs for similar use cases?
That all being said: I understand that links from highly ranked pages are still the most important ranking measure. In the end, I wonder if all that complexity really is worth the effort. When I look at Google's own search pages, then they are rather simple. For example, there is no summary of the search query in a H1 tag, just as my customer wants. Of course, Google doesn't search itself...
don't use _ (underscore) to delimit words. Google interprets hello_world as one word but hello-world as two words.
don't put your human readable keywords in the query string (after the ?). Instead make it a normal URL http://example.com/pt_BR/search/voos-de-Sao-Paulo-(SAO)-para-Recife-(REC)
I would go for a something like: http://example.com/pt_BR/2012-10-28/voos-de-Sao-Paulo-(SAO)-para-Recife-(REC)