[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev [PATCH 2.8.3.dev6] various fixes

From: Klaus Weide
Subject: Re: lynx-dev [PATCH 2.8.3.dev6] various fixes
Date: Tue, 17 Aug 1999 17:58:53 -0500 (CDT)

On Mon, 16 Aug 1999, Vlad Harchev wrote:
> On Tue, 17 Aug 1999, Klaus Weide wrote:
> > Other cases to watch out for: [snipped ]
> > with '|' denoting the point at which split_line gets called (in other words,
> > the point at which the line has reached maximum length).  Also with several
> > spaces instead of one.  Variations that have en-space, em-space, nbsp, soft
> > hyphen characters instead of, or in addition to, the normal spaces.
>  I won't try e[nm]-space,nbsp, soft hyphen - these chars are absent in psrc
> mode (since the entity's name is displayed, rather it's not rendered).

If the _raw bytes_ for theses characters occur in the input stream,
are they converted to character entities or NCRs?

> As for
> multiplie trailing whitespaces, I posted the patch yesterday (that prevented
> trimming trailing whites in split_line).
>  I'll try other variations, but seems they'll be ok - the problem my last
> patch fixed was calculations of the line_pos and hightex2offset for anchors.
>  Frankly speaking, I don't understand why you suggested such "testsuit" - 
> IMO it should contain only breaks inside hightexts, the things you've proposed
> don't contain them inside hrefs.

Those cases are "other cases" that could have problems.  I was assuming
that you had already taken care of the cases of spaces inside.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]