Re: lynx-dev lynx2.8.2dev.19 patch #6 (em dash = --)

[Klaus Weide]

On Fri, 19 Mar 1999, Leonid Pauzner wrote:

> 18-Mar-99 08:48 Klaus Weide wrote:
> > On Thu, 18 Mar 1999, Leonid Pauzner wrote:
> >> 16-Mar-99 20:28 Klaus Weide wrote:
> >> > Think
> >>
> >> >    HTTP/1.0 200 OK
> >> >    .....
> >> >    Content-type: text/plain;charset=utf-8
> >> >    .....
> >>
> >> Probably. (I have no idea how utf-8 console work about such spaces
> >> with a fixed-width screen font).


> Was interested in (1) and (2) below,
> so seems we will end up with a single space for emsp.

> But how about "  " - should it result with two spaces or not?

Do you mean (a) for the special case Display character set = UTF-8
or (b) in general?

For (a), either outputting UTF-8 encoding for U+2003 (that's what the
user wants after all, what the display system does with that code can
be regarded as out of scope for lynx - in general it doesn't know what
the display system can display) or outputting Lynx's replacement i.e.
normal space(s) would be ok IMO.

For (b), my preference is to make it one space (also in def7_uni.tbl).

Well this is all very theoretical; nobody has shown a page that uses
this (execept for example/test pages) and that would benefit from
this.

And if authors really want to control harizontal spacing, they will
probably use   anyway.

   Klaus


> > About how utf-8 for linux console (the only situation I know where
> > Display character set == UTF-8 makes sense) would work for a U+2003 -
> 
> >  (1) either it gets translated to "normal" space(s) by lynx,
> >      so no special consideration necessary, or
> 
> >  (2) it depends on the currently loaded (linux kernel) console