> On Mon, Jul 31, 2017 at 10:55 AM, Christian Brabandt <[email protected]>
> wrote:
> >
> > On Mo, 31 Jul 2017, Tony Mechelynck wrote:
> >
> >> (Yes, I am pleading devil's advocate in this discussion. I use UTF-8
> >> myself — mostly. But I also keep an up-to-date Tiny build of Vim under
> >> executable name "vi" and I build it with as few optional features as I
> >> can. Executable sizes: Huge, 2934944 bytes; Tiny, 766992 bytes. Size
> >> ratio: 3.826564 to 1.)
> >
> > And why would you refrain from using UTF-8? In my experience, using a
> > non multi-byte aware Vim will do more harm than good and users will risk
> > data damage.
> >
>
> UTF-8 is designed so that no damage will occur. UTF-16 encodings might
> be damaged, but typically only if the file is edited. Saving binary
> data without editing typically doesn't cause harm with Unix tools.
That is only true when being careful. I have corrupted files, or
unintentionally changed their encoding, at times. Setting 'encoding' to
"latin1" avoids those problems, no conversion will take place. Of
course you deal with bytes instead of characters then.
--
Apologies for taking up the bandwidth with the apology. Anything else I
can apologise for ...... er no can't think of anything, sorry about that.
Andy Hunt (Member of British Olympic Apology Squad)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
