Hi,
Please do not follow the idea to set encoding in freevo.conf. That
makes *no* sense.
It is possible, but not a good idea. I start to understand some locale
stuff and Freevo should handle by using the system locale. Like
writing the recordserver.fxd.
I do not know how this should be possible. In my understanding
freevo.conf incorporates only a list of programs.
Set your language to something different than UTF-8.
It should also work for UTF-8. Maybe it doesn't right now, but it
should. Problem is: I can't test everything. I use latin-1 and make
sure this will work.
It does not work because the python module 'locale' returns with its
method 'getdefaultlocale' only
the value 'utf' instead of 'utf-8'. This value is saved by the
recordserver into the file 'recordserver.fxd'.
Now on startup of the recordserver tries to parse this file by the
qp_xml.py module and this module
only understands 'utf-8'. That was the reason why I got the error
message I posted two days ago.
For my distro SuSE it's in the /etc/sysconfig/language. I commented
out the UTF-8 stuff and used the ISO-8859-1 instead.
# RC_LANG="de_DE.UTF-8"
RC_LANG="de_DE.ISO-8859-1"
WTF is RC_LANG? Some SuSE specific stuff?
I use LANG=de_DE and LC_MESSAGES=en_US to avoid stupid German
translations.
You're right its SuSE specific. During startup the RC_LANG variable is
used to generate and export the *real* variables LANG and LC_MESSAGES.
Best regards,
Markus
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
