El Viernes, 13 de Marzo de 2009, H. Langos escribió:
In my case the problem is that the directory where the UTF8 locale is stored is:
/usr/share/locale/es_ES.utf8/
if I change to:
/usr/share/locale/es_ES.UTF8
All work ok.
Jose Alberto
Hi,
have you tried VDRAdmin-AM v3.6.6? UTF8 handling has been changed there.
Best regards, Andreas
2009/3/14 Jose Alberto Reguero jareguero@telefonica.net:
El Sábado, 13 de Marzo de 2010, Andreas Mair escribió:
There is still the problem with es_ES.utf8 and es_ES.UTF8. I think that the problem is that in the sources in the locale directory there are es_ES.utf8 instead of es_ES.UTF8.
Jose Alberto
Jose Alberto Reguero wrote:
With version 3.6.6 the *.utf8 locales shouldn't be required at all. The charset encoding is handled by gettext.
Please provide the following information:
- Output of the `locale` command - Output of the `locale charmap` command - cat vdradmind.conf | grep LANG - svdrpsend HELP | grep 220 - Which encoding is detected by the browser and which encoding do you see in the HTML source?
You might need to change the LANG setting in vdradmind.conf to es_ES if it is configured to es_ES.UTF8 or drop it altogether to automatically use the systems default locale.
Tobias
Hi,
2010/3/14 Tobi listaccount@e-tobi.net:
Unfortunately the old and obsolete utf8 locales have found their way into the VDRAdmin-AM archive and can (should?) be deleted.
Best regards, Andreas
El Domingo, 14 de Marzo de 2010, Tobi escribió:
I delete vdradmin.mo from /usr/share/locale/es_ES.UTF-8/LC_MESSAGES/ and the program still work well, in spanish. I thought that it was using vdradmin.mo because the installation program still copy it to the locale directory.
Jose Alberto
-
Andreas Mair -
Jose Alberto Reguero -
Tobi