[Savannah-dev] [bug #4247] include/i18n.php is not aware of the locale installation dir

[nobody]

=================== BUG #4247: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4247&group_id=11

Changes by: Anonymous user        Date: Thu 09/11/03 at 09:25

            What     | Removed                   | Added
---------------------------------------------------------------------------
                  CC |                           | address@hidden


------------------ Additional Follow-up Comments ----------------------------
At the date I reported the bug, "configure" script asked

about where I would like to install the .po files:

============================================================

Where should we install i18n files?

ex: /usr/share/locale

ex: /usr/local/share/locale

[/usr/share/locale]:

============================================================



Now, tell me, whats the point of asking that if include/i18n.php will only work 
if I answer  /usr/share/locale?



I answered the second of the _suggestions_ (/usr/local/share/locale), but 
include/i18n.php wasnt 

aware of that (using bindtexdomain as I suggested

would solve the problem).



This bug shouldn't be closed before deciding whether

removing that question from configure or include/i18n.php

is fixed.





=================== BUG #4247: FULL BUG SNAPSHOT ===================


Submitted by: aacosta                 Project: Savannah                     
Submitted on: Wed 07/09/03 at 08:38
Category:  Web Interface              Severity:  1 - Enhancement            
Priority:  None                       Resolution:  Wont Fix                 
Assigned to:  yeupou                  Status:  Closed                       
Fixed Release:                        

Summary:  include/i18n.php is not aware of the locale installation dir

Original Submission:  The locale install directory should be stored during 
installation, for instance in a config file variable named sys_localeroot.



Something like  bindtextdomain ("savannah", $sys_localeroot); should then be 
added to include/i18n.php.



Otherwise internationalization wont work if the locale installation dir  isn't 
/usr/share/locale (/usr/local/share/localein my case)

Follow-up Comments
*******************

-------------------------------------------------------
Date: Thu 09/11/03 at 09:25         By: None
At the date I reported the bug, "configure" script asked

about where I would like to install the .po files:

============================================================

Where should we install i18n files?

ex: /usr/share/locale

ex: /usr/local/share/locale

[/usr/share/locale]:

============================================================



Now, tell me, whats the point of asking that if include/i18n.php will only work 
if I answer  /usr/share/locale?



I answered the second of the _suggestions_ (/usr/local/share/locale), but 
include/i18n.php wasnt 

aware of that (using bindtexdomain as I suggested

would solve the problem).



This bug shouldn't be closed before deciding whether

removing that question from configure or include/i18n.php

is fixed.



-------------------------------------------------------
Date: Wed 09/10/03 at 06:03         By: yeupou
Hum, maybe you should set up your system to consider /usr/local/share/locale as 
a path of i18n, it would be easier than adding a bindtextdomain which may at a 
later time something that broke an installation.

Basically, a system set up to install things in /usr/local should have path 
according to that (for instance, if you shell $PATH environment value is not 
set for /usr/local/bin, it's pretty problematic to get binaries in 
/usr/local/bin).

So I'm not whether it's something we have to change in Savannah. In doubt, I 
close the report. But a report can be reopened if there are good reasons to see 
things differently.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
address@hidden                | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4247&group_id=11

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/