Download the PHP package xelax90/zf-doctrine-orm-translation-loader without Composer
On this page you can find all versions of the php package xelax90/zf-doctrine-orm-translation-loader. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download xelax90/zf-doctrine-orm-translation-loader
More information about xelax90/zf-doctrine-orm-translation-loader
Files in xelax90/zf-doctrine-orm-translation-loader
Package zf-doctrine-orm-translation-loader
Short Description Provides a translation loader that uses doctrine ORM
License GPLv2
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package zf-doctrine-orm-translation-loader
Doctrine database translation loader for Zend Framework 3
This module adds an additional translation loader that uses Doctrine ORM to store translations.
Installation
Installation of LanguageRoute uses composer. For composer documentation, please refer to getcomposer.org.
Then add DoctrineORMTranslationLoader to your config/application.config.php
and run the doctrine schema update to create the database table:
Usage
This module uses the DoctrineORMTranslationLoader\Entity\Translation entity
to store translations. To add new translations, simply add new entities using
Doctrine or directly add them into the translation database table. The
default translator will automatically use the provided loader and the
translate() function/view helper will search the database for translations.
Translation Keys should not start with __META__ since this prefix is used for
storing metadata. Using __META__plural_forms in particular will lead to
unwanted side-effects.
Plural translations
You can store plural translations by using the translationPluralNumber property
of the DoctrineORMTranslationLoader\Entity\Translation entity. Provide a
translation for each plural form in your plural rule and use the translator's
translatePlural function to choose the correct form.
Meta data
You can also store meta data (such as the plural forms) for each locale and domain.
Each meta entry must have a translation key starting with __META__ followed by
the meta identifier. Meta rules are not deleted from the translator which makes
it possible to use them as translation keys, although it is not recommended. As
of now, only the plural_forms identifier is interpreted.
The DoctrineORMTranslationLoader\I18n\Translator\Loader\DoctrineEntity class
provides constants for the meta prefix and the plural_forms identifier which
you might find useful when adding or reading metadata in a PHP script.
To store the plural rules for a local and domain, use __META__plural_forms as
the translation key. For details about the plural rule syntax, please refer to
the Zend_i18n documentation.
All versions of zf-doctrine-orm-translation-loader with dependencies
doctrine/doctrine-orm-module Version ^1.1
zendframework/zend-servicemanager Version ^3.1
zendframework/zend-modulemanager Version ^2.7.2
zendframework/zend-i18n Version ^2.7.3