Dmytro Duk
Nov 6, 2009
visibility 6880
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
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |