i18n and gettext

The release related discussions, plans and questions.
Locked
eagleas
TestLink user
Posts: 6
Joined: Mon Mar 12, 2007 1:58 pm

i18n and gettext

Post by eagleas »

Hello.

May be in a version 1.7 use gettext interface to language resource?
Advantages:
1. Easy maintenance
2. Untranslated strings be output as English text. Now, as example: 'LOCALIZE: title_test_execution'
3. De facto _standard_ localization way.

Switch to gettext - easy. I can write perl script which be doing this.

Smarty and Gettext

--
eagleas
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

two years ago the proposal for using gettext, was discussed and final opinion was negative.
Right now after having doing a lot of work on this translation system (the same used by Mantis) my vote to swith is NO.
And IMHO thie is not an issue.

I appreciate your offer but my vote is not to switch.
We need to focus our efforts on other test related features.

May be in the future (one year ?) we can consider the switch.

Do you want to help us in another area ?
eagleas
TestLink user
Posts: 6
Joined: Mon Mar 12, 2007 1:58 pm

Post by eagleas »

fman wrote:Do you want to help us in another area ?
In short time we shall send patches for fix UTF-8 bugs and Russian translation.
Please, see topic "FOR DEVELOPERS: Russian translation" in "Localization and terminology".

--
eagleas
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

I've read the post.

Please create an issue on mantis, to updload your work

have a nice weekend
Locked