|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #53986 Weird behavior upon reading .mo files
Submitted: 2011-02-10 17:32 UTC Modified: 2011-02-14 14:56 UTC
From: cristian dot datculescu at gmail dot com Assigned:
Status: Open Package: I18N and L10N related
PHP Version: Irrelevant OS: CentOS 5.2
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
14 - 14 = ?
Subscribe to this entry?

 [2011-02-10 17:32 UTC] cristian dot datculescu at gmail dot com
When changing the .mo files, the changes are not taken into consideration until reloading/restarting the webserver. The solution we are using at the moment is to make symlinks for the modified .mo files and version them (so basicly php ends up reading a file). But we have run into a bug that it is for us very hard to track: sometimes while changing the .mo files and updating the version, about 50% of the translation attempts fail, reverting to printing the original text. It continues to do so until the webserver is reloaded/restarted. I have managed to replicate the bug by doing this: create the sylink, restart server, delete the symlink. In some of the cases the weird behaviour will start to manifest. What is even weirder is that putting back the symlinks does not help, the translation requests continuing to be 50% failed.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2011-02-12 08:40 UTC]
-Status: Open +Status: Feedback
 [2011-02-12 08:40 UTC]
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.

 [2011-02-14 14:56 UTC] cristian dot datculescu at gmail dot com
-Status: Feedback +Status: Open
 [2011-02-14 14:56 UTC] cristian dot datculescu at gmail dot com
// set the locale
setlocale(LC_ALL, "fr_FR");
$domain_new = "messages_1";
// bind the text domain
bindtextdomain($domain_new, dirname(__FILE__) . DIRECTORY_SEPARATOR . "locale");
// set the new domain
$strlen = array();
// the sample text
echo gettext("Niste informatie de test!");

The .mo file contains only the "Niste informatie de test!" phrase translated into "version1". This script runned for the first time will translate ok. Changing the name of the file to messages_2 and the translation to "version_2" [and updating the php as necessary], will lead to keeping the old translation [although a new domain has been set] or translating the text only about 50% [with a small deviation].
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Fri Nov 27 00:01:24 2020 UTC