This mail is an automated notification from the bugs tracker
of the project: Savane.
/**************************************************************************/
[bugs #257] Latest Modifications:
Changes by:
Mathieu Roy <[EMAIL PROTECTED]>
'Date:
mer 08.09.2004 à 18:23 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Fixed
Assigned to | None | yeupou
Status | Open | Closed
------------------ Additional Follow-up Comments ----------------------------
close in bug #493
/**************************************************************************/
[bugs #257] Full Item Snapshot:
URL: <http://gna.org/bugs/?func=detailitem&item_id=257>
Project: Savane
Submitted by: Tobias Toedter
On: mer 11.02.2004 à 18:28
Category: Web Frontend
Severity: 2 - Ordinary
Priority: A - Later
Resolution: Fixed
Privacy: Public
Assigned to: yeupou
Status: Closed
Release:
Planned Release:
Summary: HTML select boxes are not prepared for I18N
Original Submission: The HTML select boxes on the site are generated through
an SQL query. The returned result contains the id and the text of an item.
This way, only texts from the database are inserted into the select boxes,
bypassing gettext.
I think that the severity of this bug is ordinary (or even trivial), but the
solution seems to be a major pain in the ass.
Commentaires
------------------
-------------------------------------------------------
Date: mer 08.09.2004 à 18:23 By: Mathieu Roy <yeupou>
close in bug #493
-------------------------------------------------------
Date: mar 22.06.2004 à 17:18 By: Tobias Toedter <toddy>
Yes, sort of. For examples, just see this page: On top of the page, there are
some select boxes, which indicate certain states of this bug report (e.g.
Severity, Priority, Resolution, Status).
All these select boxes make perfectly sense to be translated, but the content
comes from the SQL-Database and is therefore not recognizable by gettext.
Another option of resolving this bug (instead of duplicating all tables for
every language/locale) would be to add another column to the existing tables,
named locale (or something along these lines). It would then be possible to
select the matching entry (e.g. by adding "locale='de_DE'" to the
WHERE-clause). If no such translation exists, the function should revert to the
default language and return the entry for e.g. locale='en_US' or maybe even
locale='C'.
-------------------------------------------------------
Date: mar 22.06.2004 à 12:59 By: Mathieu Roy <yeupou>
Can you give an example?
There is indeed the problem of i18n database data -- I'm afraid to think about
duplicating for each language possible the tables. Is that what you thinking of?
For detailed info, follow this link:
<http://gna.org/bugs/?func=detailitem&item_id=257>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
