Re: UTF-8 line feeds versus LS/PS

[Bram Moolenaar <Bram@moolenaar.net>]

Kai Henningsen wrote:

> > One disadvantage is that the width of the wrapped lines depends on the
> > width of the terminal. If you view the file on a different terminal it may
> > look different.  It might be different again when you print it.  That
> > might not always be what you want.
> 
> Why not?

WYSIWYG.  You want to get on paper what you see on the screen.  You sometimes
don't want your paragraph reformatted when you resize your window.
Sometimes you do want that though.

> >Wordstar (do you remember that?)
> 
> Of course. I still use compatible editors.
> 
> >had a soft
> > linebreak character for this (CR with the 8th bit set).  But only Wordstar
> > supported it, thus it wasn't very useful.  You always had to print the file
> > from Wordstar.
> 
> OTOH, "long lines" is a concept that already has pretty wide support. In  
> fact, you might say it has too much, when people use it with text/plain  
> where it doesn't belong.

True.  Some e-mail messages contain one-line paragraphs.  That's not what good
old mail applications expect.

> > Just using NL should work fine.  As far as I know LF is just another name
> > for NL, it's the same character (hex 0x0A).  A paragraph could be ended by
> > an empty line (in the file that's a double NL).  We could even recommend
> > this. Perhaps we should add a note about this in appropriate places?
> 
> news.announce.newusers? :-)

I was thinking of the Vim documentation.  Everybody reads that.  Not? :-)

--
hundred-and-one symptoms of being an internet addict:
113. You are asked about a bus schedule, you wonder if it is 16 or 32 bits.

--/-/---- Bram Moolenaar ---- Bram@moolenaar.net ---- Bram@vim.org ---\-\--
  \ \    www.vim.org/iccf      www.moolenaar.net       www.vim.org    / /
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/