Umakers.Babel 1.1.1

Babel is a language support for labels and descriptions in Umbraco back-office.

Benefits of the package:

Fast editing of language files with favorite text editor for all doctypes Everything in repo Extemely easy to copy files to next solution

Babel stores each language in a JSON file.

Babel aims to replace Umbraco Dictionary items for the back-office only.

To get Babel going you only need to install the package, add the Babel datatype to doctypes that need translation and start editing your language files.

It's still an early version of the package and we've only tested on latest Umraco (7.7.x). So please report back if you find any issues (see below).

Pre-requisites

Umbraco 7 installed Setup your Umbraco User to whatever language you need

Get started

Installation:

Install the latest version of Babel package Add the pre-installed Babel datatype to doctypes that need translation Setup translation files (see below)

Workflow

During installation of the package, a couple of example files will be added to the /config/Babel folder

Copy one of the example files and rename simply by removing the example prefix or using the following file naming syntax to support your language:

/config/babel/en.json /config/babel/da.json

The JSON files are build with a default section, where you can create property aliases that are being reused across the whole installation.

Add doctype aliases needed to the translation files (as sections - level 1)

Add property aliases to the translation files (level 2)

Translate labels and descriptions (level 3)

As default the pre-installed Babel datatype looks in the translation file for the current doctype alias with "fallback" to the default section. If the property and/or doctype alias is not found in the JSON file, no automated translation will be executed.

It's possible to configure the datatype to look for property aliases in a specific doctype alias "section" in the translation file. This is helpful if you have multiple doctypes with identical properties setup, for example, if they are all based on the "Textpage" doctype. Add a new Babel datatype with the specific doctype alias written in the configuration "Section" field - and use this datatype on the doctypes in question.

Plans for future

Better support for compositions Supporting Tabs Google Translate support Autogenerate language files from doctype

If you have any questions or want to contribute please contact UMAKERS ([email protected])