Follow-up Comment #11, bugs #1986 (project savane):

"all the low-level binary reading of the .mo file is done in this ngettext()
function I've written. So I need to determine the location of binary .mo
files." 



I am afraid this approach could creates more trouble than it fixes in first
place. 



Anyway, your function should obtain this information the way gettext() does.
Otherwise, we're just opening the door to complication (we would then need to
pay attention where the files are, stuff would end up broken if someone moves
the files to another legimitate location).



Upstream ngettext() is PHP 4.2.0. Too soon to use it everywhere - several
distro stable version ships anterior versions. But it would be unwise to
create something way complicated, that requires changes in the code, apart
from the addition of a function, just for, say, one year.





"During configuration, the user is asked where to install the binary .mo
files. The default is /usr/share/locale/, but it's possible to specify any
other directory. However, the setting of the textdomain in the i18n.php script
is done without specifying the path to the .mo files, so in effect the PHP
frontend of savane is *always* using the default location of
/usr/share/locale/, regardless of what the user specified during
configuration."



This is not a bug. Savane is designed to work on unix-like system like
GNU/Linux. There's no legitimate reason to have savane mo files in a directory
which is not in the system path for the mo files; Savane cannot be installed
on a user account anyway.



It would be pointless to add one more configuration option while were not
forced to.



The question at the configure step is here for the sole purpose of catching
the real system path for mo files. Not to encourage people to make a mess of
their system files hierarchy.



    _______________________________________________________

Reply to this item at:

  <http://gna.org/bugs/?func=detailitem&item_id=1986>

_______________________________________________
  Message post� via/par Gna!
  http://gna.org/


_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev

Reply via email to