On Thu, 04 Jan 2018 17:22:10 -0500
Sam Varshavchik wrote:
> The man page for iconv_open() gives you a clue.
So it does. Thanks!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Tom Horsley writes:
On Fri, 5 Jan 2018 02:31:16 +0800
Ed Greshko wrote:
> I do not see that behavior Unless I | the output to more, less, or
cat.
Yep. If I run it in a terminal I don't see it either.
I was running it as a shell command under emacs (which
would send output to a pipe),
On Fri, 5 Jan 2018 02:31:16 +0800
Ed Greshko wrote:
> I do not see that behavior Unless I | the output to more, less, or cat.
Yep. If I run it in a terminal I don't see it either.
I was running it as a shell command under emacs (which
would send output to a pipe), and that's where
I get the
On 01/04/18 23:27, Tom Horsley wrote:
> If I run "iconv --list" it sticks "//" on the end of every
> encoding name, but I don't need the "//" when specifying
> a to or from encoding name.
>
> Does anyone have the slightest clue why the slashes
> are there in the listing output?
I do not see that b
If I run "iconv --list" it sticks "//" on the end of every
encoding name, but I don't need the "//" when specifying
a to or from encoding name.
Does anyone have the slightest clue why the slashes
are there in the listing output?
___
users mailing list --
