4 May
2001
4 May
'01
1:10 p.m.
Another little think: if you add a new string,
please add it to *every* lang files (just keep the
english translation),
Oh YEESSSS, it's so annoying to update the
translation else (I've just done it with the portuguese
that was posted to the forum).
Regards,
Loïc
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
4 May
4 May
3:04 p.m.
I suggest this:
in select_lang.inc.php3, just before the require, add this:
require($lang_path . 'english.inc.php3');
So, if the translation is not available, english will show (hopefully the english file
should be
complete).
This way, we won't have to modify twice every lang file.
Loïc a écrit :
--
Marc Delisle
Another little think: if you add a new string,
please add it to *every* lang files (just keep the
english translation),
Oh YEESSSS, it's so annoying to update the
translation else (I've just done it with the portuguese
that was posted to the forum).
Regards,
Loïc
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel(a)lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel 
11:19 p.m.
On Fri, May 04, 2001 at 08:04:40AM -0400, Marc Delisle wrote:
I suggest this:
in select_lang.inc.php3, just before the require, add this:
require($lang_path . 'english.inc.php3');
So, if the translation is not available, english will show (hopefully the english file
should be
complete).
It would be a good hack, but that's not clean IMHO. This way, the
translators (not always technical people) would always have to compare
their file to the englich version on every check, which takes time.
It think it's much easier to add an "// last" tag at the end
of every lang file, and then with a
perl -i -p -e 's/\/\/\ last/newstringdef\n\/\/\ last/g' lang/*.php3
add the new string everywhere. That's the way I use for example
with omail-webmail.
-> consistency
-> easier for translators
-> clean :)
Regards,
Olivier
--
_________________________________________________________________
Olivier Mueller - om(a)8304.ch - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
5 May
5 May
3:33 a.m.
New subject: [Phpmyadmin-devel] Re: /lang
"Olivier M." a écrit :
On Fri, May 04, 2001 at 08:04:40AM -0400, Marc Delisle
wrote:
Olivier,
The // last tag is ok for me. BTW do we have "official" translators for every
language?
I was under the impression that the phmyadmin-translators mailing list would give
us quick answers, and each developper would himself add the translated strings
to appropriate files, but I realize that we won't have immediately translations for
all supported
language files. So a lag will develop, and it will be clean to see the new strings at the
end of
file.
Marc
I suggest this:
in select_lang.inc.php3, just before the require, add this:
require($lang_path . 'english.inc.php3');
So, if the translation is not available, english will show (hopefully the english file
should be
complete).
It would be a good hack, but that's not clean IMHO. This way, the
translators (not always technical people) would always have to compare
their file to the englich version on every check, which takes time.
It think it's much easier to add an "// last" tag at the end
of every lang file, and then with a
perl -i -p -e 's/\/\/\ last/newstringdef\n\/\/\ last/g' lang/*.php3
add the new string everywhere. That's the way I use for example
with omail-webmail.
-> consistency
-> easier for translators
-> clean :)
Regards,
Olivier
8538
days inactive
8539
days old
3 comments
4 participants
participants (4)
-
Loïc -
Marc Delisle -
Marc Delisle -
Olivier M.