I'm trying to use personality insight API by IBM to get personality and value scores from social media posts in simplified Chinese language.
I find that they do support the Chinese language in the API document, but I get the error when I try to hit API.
Error info is:
{
"code": 400,
"sub_code": "C00001",
"error": "The language you requested, zh-cn, is not supported. Languages
supported: en,es,ja,ar,ko."
}
Can anyone figure this out, what's wrong? Am I using API in wrong way?
The entry for supported languages in the service documentation shows
Table 2. Specifying request and response languages
Language Argument Supported by Content-Language Supported by Accept-Language
Simplified Chinese zh-cn No Yes
ie. Chinese isn't supported for input text, but it is supported as the output report. So you can specify Spanish as the language of the text that you want to analyse, and request the analysis report back in Chinese.
Related
I have found a spell checker in english:
spellchecker english
Is there also one in german?
Try JavaScript SpellCheck.
It supports a wide variety of languages including German.
Most of the application i developed, I used the key-value paired JS file for all required languages. Those translations i am received from business or i translated English to XXX language using google translator & verified those from the business. Once you have it then it is very easy to apply it into application using angular translation service.
We recently implemented the Document Conversion API from IBM Watson.
We always get the error, even though we specify the document type:
415 Unsupported Media Type - The media type of the input file is not supported. Specify the MIME type of the document if auto-detection was not correct.
We are trying to convert PDF's to plain text. Even the sample PDF from IBM didn't work for us.
is there a skeleton java backend (json rpc) for qooxdoo js framework?
Could any json RPC backend work for qooxdoo or we need the date hack to have it work?
Regards,
TL;DR: If you set the "protocol" property to "2.0", you should be able to interoperate with any standards-based JSON-RPC 2.0 server.
Detailed answer:
The qooxdoo JSON RPC client supports both its original protocol, a variation of JSON-RPC 1.0 called "qx1" (the default, for age-old backward compatibility), and the standardized JSON-RPC 2.0. You'll want to switch it to 2.0 by setting the "protocol" property to "2.0". If I recall correctly, our JSON-RPC client is then fully 2.0 standards-compliant except that we don't support batch requests.
Additionally, as you've noted, qooxdoo used to try to fix the "bug" in JSON/JavaScript, that there is no literal form for a Date object as there is for all other types in JavaScript. The qooxdoo JSON-RPC implementation has provisions for automatically converting Date objects into a string format that is easily parsed.
As of many years ago, we realized that it was poor form to muck with JSON-RPC since mucking with it allowed us to communicate only with qooxdoo-enhanced JSON-RPC servers. At that time, we changed the default to not do any date conversions. This is controlled by the static variable, qx.io.remote.Rpc.CONVERT_DATES, which can be set to true to "fix the bug" as we did originally, or left at its now default null (or false) value, which says "do not muck with dates."
That's all a long-winded answer to say that qooxdoo's JSON-RPC client, if you switch it to use the 2.0 protocol, should interoperate fine with any standards-based JSON-RPC 2.0 server.
Derrell
I want to try and use Elasticsearch as a full text search engine for a website in Hebrew.
I wanted to know if this Elasticsearch can produce good results for Hebrew and if there are any big websites in Israel that use it as their search engine.
If not ElasticSearch - maybe Apache Solr?
By the way - I'm using Ruby, but can work with Java as well.
Thanks!
Have a look at the ICU plugin for Elasticsearch.
David.
Solr seems to support Hebrew, see links to Language Analysers below:
Solr language analysis in Hebrew
http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.ICUTokenizerFactory
Although I am not certain what the options for ElasticSearch are.
Look at hebmorph - http://www.code972.com/blog/hebmorph/
It's a lucene plugin and we've been working with it in http://alpha.gov.il and http://www.guidestar.org.il/
Take a look at Algolia
By design the Algolia engine is language agnostic. Out of the box, it supports all languages / alphabets, including symbol based languages such as Chinese, Japanese and Korean.
Additionally, Algolia handles multi-languages on the same website/app, meaning some users could search in French, and some in English, using the same Algolia account on the background.
The purpose of this guide is to explain how to organize your indices to enable multi-language search.
Taken from here
I am rewriting our company's search functionality to use Solr instead of Compass. Our old code is using CompassQueryBuilder.CompassQueryStringBuilder to build a query out of a list of keywords. The keywords may have spaces in them: for example: "john smith", "tom jones".
Is there an existing facility I can use in Solr to replicate this functionality?
The closest thing I know for SolrJ is the solrj-criteria project. It seems to be currently unmaintained though.
Solr offers a wide variety of querying and indexing options. So fields that contain keywords with spaces in it, can be made possible by defining a custom type in the configuration file (see here). Queries with spaced keywords in it can be made possible by specifying a custom QueryParser. (see here)
Solr itself doesn't offer a QueryStringBuilder in an API. Actually, Solr itself doesn't offer any API classes at all, since all interaction is done by posting messages over Http. There are client libraries for Java, .NET and PHP etc. In the SolrNet api there exists a SolrMultipleCriteriaQuery, which is quite similar to the CompassQueryStringBuilder.