Hello. I would like to report problem I solved for myself, but I'm sure it's necessary to make some changes in mplayer ebuild. The problem is with localised mplayer messages. I'll describe the problem I had with russian language, but I think such problem exist in any language different from english. Mplayer uses macros definitions to define localised messages(/help/help_mp-ru.h files). This messages are encoded for russian with koi8-r encoding. Now I changed my locale on utf8 and messages mplayer writes to me become unreadable. So. How I solved my problem. Just this two lines into ebuild: iconv -f koi8-r ${S}/help/help_mp-ru.h > ${S}/help/help_mp-ru_utf8.h mv ${S}/help/help_mp-ru_utf8.h ${S}/help/help_mp-ru.h So just recoded file with that macros into utf8. This sollution is not universal, so it's bad. May be a good sollution will be adding "unicode" USE flag and then, if flag enabled converting user choosed help_mp-<language> into utf8? Reproducible: Always Steps to Reproduce:
And another question about mplayer ebuild. What does this mean: if [[ -n $LINGUAS ]] then [snip] else # sending blank LINGUAS, make it default to en einfo "No LINGUAS given, defaulting to English" export LINGUAS="en ${LINGUAS}" # ^^^^^^^^^^ fi Are there any reasons for ${LINGUAS} to exist there? Yes it's empty but for readability it's better to remove it.
It's upstream's decision to do the utf8-ing really. Also, the linguas stuff is to be as verbose as possible as to what linguas are being setup with mplayer, as the use nonstandard linguas format. Then en part, yes, is default without LINGUAS specified, but I'd like to be verbose at let users know that, so in case they wish to have mplayer work with nls messages.
