Hello again,
Reading bug #257 (<https://gna.org/bugs/?func=detailitem&item_id=257>)
I've read a comment (sent by you) speaking about table modifications.
I was thinking is the same line, and I think the best way would be
create an alternate column in sensible tables like task_field,
taks_field_value, bug_field, ... (all those tables with frontend
interaction. This column would be a replacement for "label" field an
could be named something like label.<locale> so the system could try to
use it in first instance and revert to default (english) values if
fields are emply in a similar way that /ets/site-specific-content files
are read but over the database instead filesystem. I think only
label/description fields needs to be translated so DB would not grow in
a considerable way (I supose)
Taking advantatge of this e-mail I would ask to you why still things
like the e-mail message that is sent at project registering is hardcoded
at ./frontend/php/register/confirmation.php, or the text like: "[BACKEND
SPECIFIC] If this group must ..." hardcoded at
./frontend/php/siteadmin/groupedit.php
This kind of messages don't not support consistent translation
mechanisms and I don't know if there is some programing reason I can't see.
Thanks in advance
Tobias Toedter wrote:
On Thursday 27 April 2006 13:32, Sergi Domènech wrote:
Hello everybody,
We are close to finish the catalan translation of savane.
Hello,
this is great news!
We have translated the po file using the template and files contained in
/etc/site-specific-content
Which is the process must we follow now? Do you want an URL to download
the files?
Yes, that's probably the easiest way to include your work.
And another question: we want to translate also the "obligatory" fileds
of task tracker like "status" for example.
Is there a procedure? Or must we change it in the database making the
system "catalan only"?
Unfortunately, Savane does not offer the possibility of translating database
fields. See bug #257 (<https://gna.org/bugs/?func=detailitem&item_id=257>)
for some small discussion about the problem. There are currently no plans
to fix this in a reasonable fashion. If you have an idea, it would be more
than welcome. So to get Catalan translations for those fields, you must
indeed convert the internal database directly to use your translations.
Cheers,
_______________________________________________
Savane-dev-i18n mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev-i18n
