Peter Törnstrand » localization http://www.tornstrand.com Drupal, PHP and web developing Fri, 16 Apr 2010 07:04:56 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Zend_Form custom/localized error messages http://www.tornstrand.com/2008/06/27/zend_form-customlocalized-error-messages/ http://www.tornstrand.com/2008/06/27/zend_form-customlocalized-error-messages/#comments Fri, 27 Jun 2008 19:45:25 +0000 peter http://www.tornstrand.com/2008/06/27/zend_form-customlocalized-error-messages/ I’ve been playing around with Zend_Form and Zend Framework 1.5 these last couple of days. Like most people I hade some trouble getting used to the decorator part of the form API. Decorators are used to style form elements for rendering in the browser, adding tags before, after and wrapping the form element itself. After much swearing I finally found this article in the Zend Developer forums that did a pretty good job explaining it.

The next problem I ran into was customizing the form error messages, not just customizing the messages but also localizing them. The framework has default error messages defined for all validators you can use with your form elements but they are kind of stiff and I doubt anyone really want’s to use them. It turns out the solution is really simple.

To attach a validator to a form element you normally write something like this:

$textField = new Zend_Form_Element_Text("myField");
$textField->addValidator(new Zend_Validate_NotEmpty());

If you want to customize the message and maybe even localize it you simply init a validator and manuelly set the message via the setMessage method, like this:

$notEmpty = new Zend_Validate_NotEmpty();
$notEmpty->setMessage("You have to enter a value");
$textField = new Zend_Form_Element_Text("myField");
$textField->addValidator($notEmpty);

If you like to localize the error message, replace the setMessage call with:

$notEmpty->setMessage($this->getView()->translate("You have to enter a value"));

It’s just that simple ;-)

]]> http://www.tornstrand.com/2008/06/27/zend_form-customlocalized-error-messages/feed/ 2 String localization with gettext and Zend Framework http://www.tornstrand.com/2008/03/29/string-localization-with-gettext-and-zend-framework/ http://www.tornstrand.com/2008/03/29/string-localization-with-gettext-and-zend-framework/#comments Sat, 29 Mar 2008 12:57:48 +0000 peter http://www.tornstrand.com/2008/03/29/string-localization-with-gettext-and-zend-framework/ There’s a lot more to localizing a web site then just replacing strings with diffrent languages (for an exelent introduction read the ZF documentation on Zend_Locale). But in this post I will talk about string localization, and especially string localization using gettext and .mo-files with Zend Framework.

The Zend Framework offers many ways for you to store your translated strings. It could be an array, a CSV or XML file or you could use gettext which we will be using in the examples below.

First you need an example application, it doesn’t need to be more complicated than a clean installation of ZF with a IndexController and a matching view, and of course the bootstrap.

Ok, so the first thing we will do is to load the Zend_Translate class in our bootstrap, load the language files, and save the object in the registry using Zend_Registry.

Zend_Loader::loadClass('Zend_Translate');
Zend_Loader::loadClass('Zend_Registry');
$translate = new Zend_Translate('gettext', './languages');
$registry = Zend_Registry::getInstance();
$registry->set('Zend_Translate', $translate);

Ok, so what we did here was to first load the classes that we need, the Zend_Translate and Zend_Registry classes. Next we create the Zend_Translate object and pass in the directory containing all of our different languages we will support in our application, in this case we will be supporting swedish and english language. Don’t worry about the language files, I will explain how you create those later on. Finally we save our Zend_Translate object to the registry so we don’t need to create our object over and over again in our application.

The next step is to dive into our applications views to identify the strings we want translated. In our example we only have one view, the index view of our IndexController. So let’s open that up and have a look at it.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Zend_Translate example</title>
</head>
<body>
<h1>Hello World!</h1>
<p>This is a Zend_Translate demonstration</p>
</body>
</html>

Here we have two strings that needs to be localized, so we wrap these strings in a call to the translate object.

<h1><?php echo $this->translate("Hello World!"); ?></h1>
<p><?php echo $this->translate("This is a Zend_Translate demonstration"); ?></p>

Zend Framwork 1.5 ships with the Zend_View_Helper_Translate which makes translating strings easy, before you were forced to translate the strings in the controller or write your own translation view helper.

Now we have made all the modifications to our application that needs to be done to support string localization. Now it’s time to create our translation files, the .mo-files. First thing you want to do is to download Poedit. Poedit is an application that helps you gather all the strings that should be translated from your application and presents them in a interface for you to translate. The program is open source and exists in versions for all major operating systems.

Lets fire up Poedit and try to import the strings. Click File -> New catalogue and a settings windows should appear.

Poedit - Settings form

Fill in the settings so it looks something like the above image. Then click the Paths tab.

Poedit - Paths

Here you first enter the base path to your application and then you add the directories in your application that contains the files with the strings to be translated (your views). When your done click the Keywords tab.

Poedit - Keywords

Here you enter the name of the function you are calling to translate a string, in Zend Framework the function name is translate ($this->translate(“String”)).

When you’re done click OK. If your setup is anything like mine you will now encounter a error saying the catalogue update failed.

Poedit - Error

This was expected and happens because Poedit don’t know to look for strings in .phtml files that are used by Zend Framework. Click File -> Preferences and click the tab Code readers. Select the PHP item and click Edit.

Poedit - PHP settings

Edit the settings so they reflect the settings in the picture above.

Now when you click update the strings that we wrapped in the translate function call should appear in Poedit in a list with the original strings to the left and the translations to the right. Get to work translating your strings and then save the catalogue. I’m keeping all my language files in a directory called languages in the web application root next to the library and application directories.

The application will automatically detects locale based on the HTTP_ACCEPT_LANGUAGE header sent by browsers. It will try to match the available languages to the users preffered language and if no match is made it will use the default language (the strings in your view files). You can customize this to use other methods but that’s out of the scope for this post.

]]> http://www.tornstrand.com/2008/03/29/string-localization-with-gettext-and-zend-framework/feed/ 10