Hi,
if we would use a function for locale strings we could automatically add <span xml:lang="en" dir="ltr"></span> to not translated strings, avoiding display problems in RTL languages, and problems with screen readers
Sebastian Mendel a écrit :
Hi,
if we would use a function for locale strings we could automatically add <span xml:lang="en" dir="ltr"></span> to not translated strings, avoiding display problems in RTL languages, and problems with screen readers
Hi Sebastian, I reread the September 2007 thread about localization. I was wondering about the speed of calling a function for each message.
Also, with the current langage files, how to we detect an untranslated string?
Marc
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Hi,
if we would use a function for locale strings we could automatically add <span xml:lang="en" dir="ltr"></span> to not translated strings, avoiding display problems in RTL languages, and problems with screen readers
Hi Sebastian, I reread the September 2007 thread about localization. I was wondering about the speed of calling a function for each message.
Also, with the current langage files, how to we detect an untranslated string?
compare with the original english string, or do not include untranslated stings at all
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Hi,
if we would use a function for locale strings we could automatically add <span xml:lang="en" dir="ltr"></span> to not translated strings, avoiding display problems in RTL languages, and problems with screen readers
Hi Sebastian, I reread the September 2007 thread about localization. I was wondering about the speed of calling a function for each message.
Also, with the current langage files, how to we detect an untranslated string?
compare with the original english string, or do not include untranslated stings at all
If we don't have untranslated strings in the file, it will be more difficult (less motivating) for translators. Or maybe the full line could be commented in the file? //translate $strProfiling = 'Profiling';
If we compare, it means 2 global arrays, one for the active translation, one for english?