Whenever I run mencoder I get the message "iconv: conversion from UTF-8 to UTF-8 unsupported". Not sure if it's affecting anything as I haven't done any real converting with mencoder yet. --- Terminal output: $ mencoder iconv: conversion from UTF-8 to UTF-8 unsupported Service unavailableMEncoder SVN-r37153-snapshot-3.3 (C) 2000-2014 MPlayer Team iconv: conversion from UTF-8 to UTF-8 unsupported No file given iconv: conversion from UTF-8 to UTF-8 unsupported Exiting... (error parsing command line) mencoder: _mcleanup: mencoder.gmon: Permission denied --- Possible packages related to issue: multimedia/mencoder multimedia/mplayer converters/libiconv
over to maintainer
Not a maintaner. Bouncing back. Anyway, I doubt that this is an issue with libiconv port itself. Just to prove that can you please run command below: $ echo foobar | iconv -f UTF-8 -t UTF-8 If you do not see any errors than I'd rather look into mencoder itself, or perhaps there is something special about your setup which you did not mention.
I don't observe the issue in either mencoder or mplayer.
(In reply to Alexander Nedotsukov from comment #2) > Not a maintaner. Bouncing back. > What? Go look at converters/iconv/Makefile MAINTAINER= bland@FreeBSD.org Where's the breakdown?
$ echo foobar | iconv -f UTF-8 -t UTF-8 foobar
(In reply to John Marino from comment #4) > (In reply to Alexander Nedotsukov from comment #2) > > Not a maintaner. Bouncing back. > > > > What? > > Go look at converters/iconv/Makefile > > MAINTAINER= bland@FreeBSD.org > > > Where's the breakdown? Quoting original mail for you: Possible packages related to issue: multimedia/mencoder multimedia/mplayer >>> converters/libiconv Can you see it now? I also suggest you to go and look at /usr/ports/Mk/Uses/iconv.mk to avoid confusion going forward.
The breakdown is the original title "[converters/iconv] Message: conversion from UTF-8 to UTF-8 unsupported" Using this title means the converters/iconv is the port is question. I see the port in the title, I assign to the maintainer of that port. I could have read the description closer but the damn title lead me astray, that's the source of the issue.
change very misleading title.
@Jordan: Does the issue still occur for you? @Alexander: Jordan provided the output in comment 5, which seems to indicate that iconv itself is not at fault, correct?
Yes, this issue still occurs on my system.
Jordan, thanks for the report. As it's been two years, I'm closing this. If this problem still appears, which I doubt, please file a new report or reopen this one.