When setting USE="unicode" && !USE="iconv" or vice versa, there is no effect on the configure options. Not setting both flags results in broken code on unicode systems (at least for the playback of asf-files). The ebuild contains: if use iconv then use unicode && myconf="${myconf} --charset=UTF-8" else myconf="${myconf} --charset=noconv" fi In my opinion, it should print at least a warning like: if use iconv && use unicode then myconf="${myconf} --charset=UTF-8" else myconf="${myconf} --charset=noconv" && einfo "Setting unicode or iconv alone has no Effect." fi [P.S. Why was the split of unicode in unicode & iconv even introduced?]
*** Bug 142885 has been marked as a duplicate of this bug. ***
iconv should be always on beside on system that don't have glibc I'll think about it again.
(In reply to comment #2) > iconv should be always on beside on system that don't have glibc > > I'll think about it again. > iconv must be on for >=mplayer-1.0_rc1, if it's disabled mplayer can freeze on some osd fonts.
There's similar problem with truetype flag (observed on 1.0_rc1). Looks like it doesn't work standalone, you need to enable truetype AND iconv to actually get freetype -> fontconfig -> SSA/ASS support that everyone needs :) Checking for freetype >= 2.0.9 ... no (iconv support needed) Checking for fontconfig ... no (freetype support needed) Checking for SSA/ASS support ... no (FreeType support needed)
(In reply to comment #4) > There's similar problem with truetype flag (observed on 1.0_rc1). Looks like it > doesn't work standalone, you need to enable truetype AND iconv to actually get > freetype -> fontconfig -> SSA/ASS support that everyone needs :) > > Checking for freetype >= 2.0.9 ... no (iconv support needed) > Checking for fontconfig ... no (freetype support needed) > Checking for SSA/ASS support ... no (FreeType support needed) > I've added some notes to the rc1 build to point that out.
should be fixed in 1.0_rc2_pre20070321, let me know if otherwise.
