Hi Bram,
2016/8/18 Thu 6:17:48 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > I wrote a patch for the following todo item:
> >
> > > Win32: When running ":make" and 'encoding' differs from the system
> > > locale, the
> > > output should be converted. Esp. when 'encoding' is "utf-8". (Yongwei Wu)
> > > Should we use 'termencoding' for this?
> >
> > I think using 'termencoding' for this is not so good. Normally the encoding
> > of a command output is the same as the encoding of the terminal, but not
> > always the same. I hear that some commands on Windows use utf-8 instead of
> > the current codepage. So I added a new option 'cmdencoding' ('cenc').
> > What do you think of this?
>
> Seems reasonable. It's not nice that it's yet another option. But in
> case you know the compiler output is in a certain encoding it's the only
> way to make it work.
>
> Why they "char" value? It's using the system locale, wouldn't "system"
> be better? Hmm, I don't see where "char" is recognized.
At least, GNU libiconv supports "char".
See: https://www.gnu.org/software/libiconv/
| Locale dependent, in terms of `char' or `wchar_t' (with machine dependent
| endianness and alignment, and with OS and locale dependent semantics)
| char, wchar_t
| The empty encoding name "" is equivalent to "char": it denotes the locale
| dependent character encoding.
I don't know about other iconv implementations.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
