Download the PHP package saeven/zf2-circlical-trans without Composer

zf3-twig-trans

Magic glue to create the expected experience when developing with ZfcTwig, the MvcTranslator (e.g., from within your controllers), and your twig templates using a custom {% trans %} that this module provides. Usage is very simple! With this package included, "trans" becomes available in your templates.

New! This module supports text domains!

Inspired by ZfcTwig and its extensions project at https://github.com/twigphp/Twig-extensions

Requirements

Installation

Configuration

Loading the module: application.config.php

In your module's application.config.php, make sure you've got these modules loaded:

'ZfcTwig',
'CirclicalTwigTrans'

By loading CirclicalTwigTrans, you will be setting an alias from 'translator' to 'MvcTranslator'. If you have an existing translator alias in your system, please remove it.

Managing Locale: Your Application's Module.php

It's assumed that you are managing locale in your app's bootstrap. For example, in your Application module's onBootstrap:

Proper Language File Setup

gettext imposes a certain file structure; language folders for a module would look like so:

The .mo files are truly the ones that matter. The .po files, are the source files that are used to compile the .mo files with msgfmt.

The nomenclature, default.mo, indicates that that file contains text strings for the 'default' text domain. In other words, the name of the files is vital to proper functionality.

You need to tweak your translator configuration to support this file structure, it's very simple. Per module:

Very important: there's a critical difference between Zend's translator implementations, and gettext's implementation. The Zend translator will allow you to use multiple .mo files for a same domain, but gettext does not support this behavior. To ensure that both the Twig translations, and your in-app translations (e.g., $translator->translate('foo')) work properly, your domain names must be unique. A good practice is to name your domain, after your module.

Usage

Included tests support all flavors of trans, adding direct support for domain overrides from within the template. These syntax structures all work:

Translate 'Sorry' from text-domain 'errors'

Translate 'Home' from the 'default' domain

Translate "A 404 error occurred" from the 'default' domain

Translate with pluralization from the 'default' domain

Translate with pluralization from the 'errors' domain

Translate with notes

Controllers

Usage in controllers doesn't change.

You can test it with the ZF3 Skeleton, by translating "Home" to "fr_CA" which becomes "Acceuil" (good test).

Enjoy!

Let me know if you find any issues. I use this module as well in production, so definitely want to hunt bugs down!