This tutorial demonstrates how to add multi-language support to a PHP application using Twig and Gettext. It's significantly faster than userland solutions like Symfony's translation component. We'll modify a pre-existing English-only application (nofw) to illustrate this.
Key Advantages:
- Efficiency: Gettext's native implementation offers superior performance compared to userland alternatives.
- Simplicity: The process of adding internationalization to an existing application is surprisingly straightforward.
-
Comprehensive Guide: This tutorial covers environment setup, string extraction (using
xgettext
),.po
and.mo
file generation, Twig integration via thei18n
extension, and helpful utility scripts.
Setup and Fundamentals:
We'll use Homestead Improved (assuming Gettext is already installed; instructions for manual installation are provided later). Because nofw uses Twig, the i18n
extension is required:
git clone https://github.com/swader/nofw cd nofw git checkout tags/2.93 -b 2.93 composer require twig/extensions
(Note: This clones an older nofw version without built-in internationalization for tutorial purposes.)
Follow the nofw README to configure the database. The application should now be running.
Gettext uses gettext("string")
or its alias _("string")
to mark translatable strings. If a translation isn't found, the original string (the placeholder) is returned.
Let's test this with a simple PHP file (outside of Twig) to verify Gettext functionality. Create i18n.php
:
<?php $language = "en_US.UTF-8"; putenv("LANGUAGE=" . $language); setlocale(LC_ALL, $language); $domain = "messages"; bindtextdomain($domain, "Locale"); bind_textdomain_codeset($domain, 'UTF-8'); textdomain($domain); echo _("HELLO_WORLD");
Create the directory structure:
The code sets the language, locale, and domain for Gettext. Running this will echo "HELLO_WORLD" because the language file is missing.
String Extraction:
Use xgettext
to extract strings from your files:
xgettext --from-code=UTF-8 -o Locale/messages.pot public/i18n.php
This creates messages.pot
(Portable Object Template). Generate an English .po
file:
msginit --locale=en_US --output-file=Locale/en_US/LC_MESSAGES/messages.po --input=Locale/messages.pot
Edit messages.po
, translating "HELLO_WORLD" (e.g., to "Howdy"). Compile to .mo
:
msgfmt -c -o Locale/en_US/LC_MESSAGES/messages.mo Locale/en_US/LC_MESSAGES/messages.po
Adding a New Language (e.g., Croatian):
- Install the locale:
sudo locale-gen hr_HR hr_HR.UTF-8; sudo update-locale; sudo dpkg-reconfigure locales
- Generate the
.po
file:mkdir -p Locale/hr_HR/LC_MESSAGES; msginit --locale=hr_HR --output-file=Locale/hr_HR/LC_MESSAGES/messages.po --input=Locale/messages.pot
- Translate "HELLO_WORLD" to "Zdravo" in
messages.po
. - Compile to
.mo
:msgfmt -c -o Locale/hr_HR/LC_MESSAGES/messages.mo Locale/hr_HR/LC_MESSAGES/messages.po
- Change
i18n.php
's locale tohr_HR.UTF-8
and test. A server restart might be needed.
Twig Integration:
Add this to app/config/config_web.php
:
git clone https://github.com/swader/nofw cd nofw git checkout tags/2.93 -b 2.93 composer require twig/extensions
In your Twig templates, use the trans
block:
<?php $language = "en_US.UTF-8"; putenv("LANGUAGE=" . $language); setlocale(LC_ALL, $language); $domain = "messages"; bindtextdomain($domain, "Locale"); bind_textdomain_codeset($domain, 'UTF-8'); textdomain($domain); echo _("HELLO_WORLD");
xgettext
doesn't handle Twig directly, so we'll use a caching mechanism. Create app/bin/twigcache.php
:
xgettext --from-code=UTF-8 -o Locale/messages.pot public/i18n.php
Then extract strings from the cached files:
msginit --locale=en_US --output-file=Locale/en_US/LC_MESSAGES/messages.po --input=Locale/messages.pot
Update .po
files using msgmerge
and recompile .mo
files.
Bonus: Utility Scripts (app/bin/i18n):
The tutorial provides bash scripts (addlang.sh
, update-pot.sh
, update-mo.sh
, config.sh
) to automate the process of adding languages, updating .pot
and .mo
files. These scripts are detailed in the original text.
Deployment:
Ensure Gettext is installed and locales are generated on your server. On Ubuntu:
msgfmt -c -o Locale/en_US/LC_MESSAGES/messages.mo Locale/en_US/LC_MESSAGES/messages.po
The .pot
, .po
, and .mo
files should be part of your version control. Adapt the installation command and scripts for non-Ubuntu systems. The FAQs section provides further details and troubleshooting information.
The above is the detailed content of Easy Multi-Language Twig Apps with Gettext. For more information, please follow other related articles on the PHP Chinese website!

Thedifferencebetweenunset()andsession_destroy()isthatunset()clearsspecificsessionvariableswhilekeepingthesessionactive,whereassession_destroy()terminatestheentiresession.1)Useunset()toremovespecificsessionvariableswithoutaffectingthesession'soveralls

Stickysessionsensureuserrequestsareroutedtothesameserverforsessiondataconsistency.1)SessionIdentificationassignsuserstoserversusingcookiesorURLmodifications.2)ConsistentRoutingdirectssubsequentrequeststothesameserver.3)LoadBalancingdistributesnewuser

PHPoffersvarioussessionsavehandlers:1)Files:Default,simplebutmaybottleneckonhigh-trafficsites.2)Memcached:High-performance,idealforspeed-criticalapplications.3)Redis:SimilartoMemcached,withaddedpersistence.4)Databases:Offerscontrol,usefulforintegrati

Session in PHP is a mechanism for saving user data on the server side to maintain state between multiple requests. Specifically, 1) the session is started by the session_start() function, and data is stored and read through the $_SESSION super global array; 2) the session data is stored in the server's temporary files by default, but can be optimized through database or memory storage; 3) the session can be used to realize user login status tracking and shopping cart management functions; 4) Pay attention to the secure transmission and performance optimization of the session to ensure the security and efficiency of the application.

PHPsessionsstartwithsession_start(),whichgeneratesauniqueIDandcreatesaserverfile;theypersistacrossrequestsandcanbemanuallyendedwithsession_destroy().1)Sessionsbeginwhensession_start()iscalled,creatingauniqueIDandserverfile.2)Theycontinueasdataisloade

Absolute session timeout starts at the time of session creation, while an idle session timeout starts at the time of user's no operation. Absolute session timeout is suitable for scenarios where strict control of the session life cycle is required, such as financial applications; idle session timeout is suitable for applications that want users to keep their session active for a long time, such as social media.

The server session failure can be solved through the following steps: 1. Check the server configuration to ensure that the session is set correctly. 2. Verify client cookies, confirm that the browser supports it and send it correctly. 3. Check session storage services, such as Redis, to ensure that they are running normally. 4. Review the application code to ensure the correct session logic. Through these steps, conversation problems can be effectively diagnosed and repaired and user experience can be improved.

session_start()iscrucialinPHPformanagingusersessions.1)Itinitiatesanewsessionifnoneexists,2)resumesanexistingsession,and3)setsasessioncookieforcontinuityacrossrequests,enablingapplicationslikeuserauthenticationandpersonalizedcontent.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 English version
Recommended: Win version, supports code prompts!

Notepad++7.3.1
Easy-to-use and free code editor
