G Translate Plugin
Jeannine Lander
Highlight or right-click on a section of text and click on Translate icon next to it to translate it to your language.Learn more about Google Translate at installing this extension, you agree to the Google Terms of Service and Privacy Policy at (v.2.0): Now you can highlight or right-click a text and translate it vs. translate the entire page. You can also change extension options to automatically show translation every time you highlight text.UPDATE (v.2.14+): Page translation is now supported natively in Chrome browsers and is no longer supported in the Google Translate extension. See to learn how to use it.
The Language Translator plugin was recently released. It allows you to translate selected text into the desired language. This is based on a free instance of Azure Translator. (Please do not abuse it)
A visitor can select their chosen language using the native SitePicker component that is included in the October CMS core. This component will display a simple dropdown that changes the page language depending on the selection.
You may also define the translations in a separate file, where the path is relative to the theme. The following definition will source the default messages from the file config/lang.yaml inside the theme.
You may also define the translations in a separate file per locale, where the path is relative to the theme. The following definition will source the default messages from the file config/lang-en.yaml inside the theme for the english locale and from the file config/lang-fr.yaml for the french locale.
In order to make these default values reflected to your frontend site, go to Settings -> Translate messages in the backend and hit Scan for messages. They will also be loaded automatically when the theme is activated.
Translatable model attributes can also be declared as an index by passing the $transatable attribute value as an array. The first value is the attribute name, the other values represent options, in this case setting the option index to true.
The word "Contact" in French is the same so a translated URL is not given, or needed. If the page has no URL override specified, then the default URL will be used. Pages will not be duplicated for a given language.
It is possible to conditionally extend a plugin's models to support translation by placing an @ symbol before the behavior definition. This is a soft implement will only use TranslatableModel if the Translate plugin is installed, otherwise it will not cause any errors.
In my opinion the use of this plugin (we used it in the V1 and 2 of October CMS) is a big mess now. How can we translate the SEO atributes..the Menu names and so on? In the previous version there were some drop downs right to every Input typte text and Rich text editor..now we have to chage the language from (Manage sites) top right..and recreate the pages over and over again for each language.
i want to limit my posts with current language or choose two thumbnail pic for my posts in newsletter plugin or portfoliofor example i want to show different posts with different language HELP ME PLZ...
I use this plugin and plugin news , but I do not want the slug in the post as multi-language. I want the slug to be fixed. How do I do ?I have a suggestion that, when changing the language at a certain position, all languages in the other position will change.For example: I clicked change language from English to English in the title textbox, the other positions (such as content, summary, ...) are automatically selected in English.And... This is great plugin ! Thanks
I find this plugin really useful!!! Some Bug... Hebrew not work! I Changed he to heb but steel Translate Messages not works! You may Look at the my site www.ghiml.co.il. Content in hebrew header and footer in english.
Love this plugin!@Hessel, it will be perfect real soon! It already works in our testing website with the option for "Bleeding edge updates" turned on. I think it all wil be part of the upcoming version 1
For example if I navigate to the Pirate's language URL then switch back to English I still view the Pirate language messages. I tried clearing the cache thousand times in my console, in the plugin interface, using a cache cleaner plugin /disabling cache and settings English as default language!
Updated Hungarian translation. Added Arabic translation. Fixed issue where default texts are overwritten by import. Fixed issue where the language switcher for repeater fields would overlap with the first repeater row.
Beginning from October CMS v3.1, a multisite feature was introduced that supercedes many functions provided by the RainLab.Translate plugin. The existing data structures are preserved so all translations are carried across and no "retranslation" or modifying existing plugins should be needed.
The translate.localePicker.translateQuery event has been replaced by the cms.sitePicker.overrideQuery. The arguments are the same except the site definition is passed instead of the locale code, use the hard_locale attribute of the site definition to obtain the locale.
The translate.localePicker.translateParams event has been replaced by the cms.sitePicker.overrideParams event. The arguments are the same except the site definition is passed instead of the locale code, use the hard_locale attribute of the site definition to obtain the locale.
For English-speaking people, problems of this kind are not very clear. However, try, for example, to go to a German forum and understand something there without speaking German. Or on the Russian-language forum. To quickly translate from an unfamiliar language, Google Translate is used. And it is completely broken on this forum and many other forums using Discourse.
Considering that Chrome / Chromium is the most popular browser, and Google Translate is the most popular machine translator, most of the audience that does not understand the language of the forum is cut off from the forum using Discourse.
No, this is definitely not a language confusion problem. Google translate has long been able to properly separate and translate this.
In my case, I checked it without even logging into the forum. In this case, only 1 language is used in the interface and content. And my interface language here is English.
Surprisingly, when I created this thread, I checked all the translation methods here and on forum.ghost.org. The translation did not work either there or here. Now I have checked forum.ghost.org again and the translation was possible with the help of the official plugin and with the help of the translator built into Chrome. Translation via google.translate.com also does not work. I try this site and the translation works unpredictably (the official plugin translates some pages and some not).
An interesting fact, if I am not logged into the forum, then the interface is shown to me in my system language and I cannot change it until I enter the forum under my account. If the problem of mixing languages really exists, then this behavior is also erroneous.
There are still problems with the google translate site (I already found questions about this problem here) and problems with the official google translate extension for browsers that do not have a built-in translator. This is less of a problem, but still a problem for me because I am not using Chrome, but using the Brave browser due to security issues.
At the moment, I can say that the official google translate plugin cannot translate this forum, but forum.ghost.org does translate without problems. Perhaps the matter is in what forum settings or styles.
I have not checked the entire list, but it is obvious that only a small part of these forums can be easily translated if the visitor has a Chromium browser installed (for example Brave) with the official google translate plugin. I have no doubt that some of the blame lies with this plugin, but it is absolutely useless to point google about this. A critical issue with the plugin only occurs with the Discourse engine (most Discourse forums, but not all) and discussions.apple.com forums.
I cannot yet draw such a conclusion based on all the data collected. After all, this plugin has no problems with any other forum and site engines (even those with a lot of JavaScript, for example NodeBB). I can only 100% say that Google will not solve this problem, even if it is on their side.
You won't be able to translate the text in the file itself, as Reader is technically not capable of doing that. And I don't see anyone bothering to do it in a window, as you can just copy the text and paste it in Google Translate or something like that. In other words, I still very much doubt it's going to happen.
I also struggeld a lot with not having an instant translation in Adobe Reader and in Windows generally - I really think adobe should Implement an instant translation into adobe reader or Micrsoft into Windows.
The best workaround I have found for this issue, is the Translation-Tool Qtranslate, it's not perfect but the best workaround for the moment and it works more or less globally, meaning it can translate out of every program similar to the MacOS build-in dictionary.
Adobe Reader wouldn't be the proper tool to translate a file anyway since, to put it simply, it lacks all the editing features that you normally need to translate a document from one language to another.
If you're working with InDesign files, you might want to check out Redokun (disclaimer: I'm a co-founder), otherwise, there are plenty of translation tools that work with pretty much every file format.
You can not translate within the Adobe Reader but you can open the PDF file in the browser and add some translate extension in it and you can instantly translate within the browser to any language. Thanks
c80f0f1006