I have gone through the react-intl docs but my question is
How to get the converted/desired language in react-intl similar to google translator feature rather than convert manually.
Related
I am doing my dissertation on sentiment analysis on transcriptions of oral testimonies and have a few questions/clarifications regarding the programming behind Google Cloud's Natural Language API v1beta2.
I assume that it is a combination of lexicon-based methods and machine learning based methods of sentiment analysis but would appreciate confirmation of this.
What language model does Google NLP use? (I am guessing something involving deep learning and Tensorflow but am not sure)
What source material was the language model trained on? And was
anything like SentiWordNet or WordNet used?
If the API can detect both implicit and explicit sentiment?
Is the tool only capable of working in English or can it translate/trace sentiment in, for example, German or Polish?
I am open to any and all answers. Also, if anyone knows of any official Google document which lists this information that would also be appreciated. Thank you.
We're currently using a large CNN implemented in TF. The model in the Cloud NL API does not use a LM. The API can detect both implicit and explicit sentiment, but it does not differentiate between them. The Sentiment API supports English, Spanish, French, German, Portuguese, Korean, Japanese, and Chinese
Source: I'm the Product Manager for NLU Research # Google/Alphabet.
This applies to popular languages used for web development e.g. Python, Java, Rails etc.
I want to be able to programatically generate TeX documents. For example a user submits a form and a field contains the LaTeX code to be typeset and the web service returns the typeset PDF.
Are there libraries available for such a task? I can't find any.
The only other solution I can think of is to use external shell command functionality that's usually available. But this is a bit messy.
Some time ago I created an Etherpad lite plugin that allows you to compile the LaTeX serverside. FlyLaTeX does it similarly, but didn't really work for me and the code looked pretty messy and almost impossible to fix and debug when I was having a look at it about 4 months ago.
Basically you need to generate a temporary file that you can then compile with LaTeX.
I don't know of any generation libraries, but LaTeX is quite easy to generate. However, pandoc can convert different formats into LaTeX.
There is also https://github.com/manuels/texlive.js/ which is an emscripten-based clientside port of LaTeX (that unfortunately has very limited capabilities and is quite large).
i currently use Microsoft input method and Google method for my native language called Amharic but they are not giving me what am looking for. Microsoft has weird typing mechanism and Google is so much good but i needed something more.
i have good c++ knowledge , but not much on C programming , i hate structural , and i hate MFC is there an resource that can help me make an input method for windows OS specially windows 7,8.
MSDN documents the Text Services Framework.
TSF provides a simple and scalable framework for the delivery of advanced text input and natural language technologies. TSF can be enabled in applications, or as a TSF text service. A TSF text service provides multilingual support and delivers text services such as keyboard processors, handwriting recognition, and speech recognition.
Microsoft has published a set of guidelines for implementing IMEs and has notes about third-party IMEs. They have also published a sample IME.
Google Input Methods can be customized. You can create your own scheme which means you can define which keystroke or a set of keystrokes map to what unicode character. Follow the guide in the following url: http://www.google.com/inputtools/windows/canonical.html
File name: visual-geez.scm
version: 1.0
name: visual-geez
ha ሀ
hu ሁ
hi ሂ
Put the above file in the schemes directory under the installation directory of the input method (for example: C:\Program Files\Google\AmharicInputMethod\schemes and then restart the input method (change to another language and change back to amharic). Enable the newly created scheme by clicking the settings (cog) button -> schemes -> visual-geez
Now when you start typing you will see the transliteration rules have changed to your newly created scheme.
So, I've got an app that needs to deal with files created by Adobe InDesign (.INDD), and while the XMP Metadata is useful, there are additional things that I want to know about the files that do not appear to be in the metadata.
Specifically, I would want to know the number of actual pages (not just number of page previews created), and what the dimensions of those pages are.
Has anyone run across any toolkit, sdk, etc. that can get me this information?
This will be for a non-open source commercial app, so licenses are a potential roadblock. Also, this app will not be a plug-in for any Adobe product, so the InDesign Plugin SDK is not an option either.
C++ is the preferred language.
.indd is a proprietary format owned by Adobe. You are not allowed to interact with this format outside of InDesign. If the documents are saved in the .idml format, it's quite possible and not very difficult, but if all you have to work with is a bunch of .indd files that someone else created, you're gonna have to use a plugin or scripts together with InDesign.
We're in the middle of deploying a new software system to lot's of users in lot's of places (200+ users over 8 countries). In the past we've written a manual for the users, then update it every so often. This works ok, in that all the users ahve the same manual and it covers the main things but it has it's problems, like it doesn't get updated that often, we sometimes miss updates, and some users will have old copies.
We've been talking about using a wiki during the testing and deployment phases to build a knowledge base about the system. Ideally we'd then like some way to convert that into some form fo electronic document that we can then 'pretty-fie' and send out as the official manual, as well as letting users use and update the wiki.
Has anyone else done anything similar ? Any suggestions for wiki systems, workflows, document formats etc?
Most wikis support export via PDF e.g.:
MediaWiki PDF Export
DokuWiki PDF Export
TWiki PDF Export
You can write something that generates LaTeX from the wiki and renders a manual to PDF. With packages like hyperref you can retain cross-references as hyperlinks.
Additionally, you can integrate content from multiple sources such as a data dictionary into the LaTeX document, which can be mixed and matched with the wiki content. You could also set the architecture up so it can support cross-referencing that goes either way.
Framemaker could also support this using generated MIF files, and you could also use Lout in a similar way or convert your wiki content to docbook, which would allow you to use any of the many rendering options available to that format.
As an aside, the following Stackoverflow postings discuss various systems for maintaining documentation.
Application (Not a Markup Language) for Producing a User Manual
Can LaTeX be used for producing any documentation that accompanies software?
What tools are used to write documentation?
What tools does your team use for writing user manuals?
How best to write documentation (ideally in latex) targeting both the web (html) and paper (pdf)?
Best tool(s) for working with DocBook XML documents?
What is the recommended toolchain for formatting XML DocBook?
Is a successor for TeX/LaTeX in sight?
Madcap Flare is a help-and-manual authoring tool that uses HTML for the source of each topic. You could pretty easily do a mass import of the Wiki pages. Would then require some cleaning but after that you have a nice single-source system that can output CHM, web-browsable help, PDF, DOC/DOCX, etc.
How are you storing the help source at the moment? Is it MS Word files, MS help, LaTeX?
If you put your help source files under version control then you will get all the benefits of a wiki without having to migrate to a new system - people can make edits to the help files easily - those changes can be tracked, reverted etc. and you get the prettified manuals as before.
I followed Node's links and came across some mediawiki pages that I thought were noteworthy.
Extension:OpenDocument Export
Extension:PDF Writer
Category:Data extraction extensions
I gave a previous answer which may be useful for the "wiki to PDF" part -- look at using the open source PediaPress code or functionality. You can get ODFs from it too, although their PDFs are already quite pretty (but you might want to rebrand it and restyle it for your company I suppose).