Dmytro Duk
Optimizely
Nov 6, 2009
visibility 7023
star star star star star
(5 votes)

Quick Translate gadget

Hi! Here is my little contribution to Gadget Contest 2009 – Quick Translate gadget.

QuickTranslate1

I believe that user doesn’t want to click on many dropdowns, radio buttons, checkboxes, etc to define complex translation settings.

The main idea is to provide convenient tool for quick translation of short texts and pages.

As an alternative you can use staggering Ruwen’s gadget and find something for translation in 170000 third party gadgets :)

Key features:

Type and go! Just type or paste text and submit by Enter, that’s it. Quick translate gadget is not intended for long texts translation. You won’t see any text area controls and don’t have to click on a submit button.

Detect my language! Source language is detected automatically and indicated below the translated text. We avoid extra control and don’t make user to specify source language. It is quick and simple. Moreover user might not know what source language is.

QuickTranslate2

The more words you input the more correctly source language is determined.

Translate my page! You can submit any URL and get translated page in a new window.

Remember me! Since we have minimal control set, there is only one setting: translation result language. Gadget will remember your last choice and this language will be selected when you back tomorrow. Or next year. Until you clear cookies.

Technical details

Yes, it uses Google AJAX Language API.

One strange thing is that Google returns not localized list of supported languages, even when you specify required culture. My solution: I load the list of native names of .NET neutral cultures using AJAX and then build dropdown of supported languages.

Download and installation

Module can be installed on existing EPiServer CMS 6 site using Deployment Center.

Unpack sources to Modules folder of your site.

Nov 06, 2009

Comments

Sep 21, 2010 10:32 AM

Nice one!
/ Allan Thraen

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026