Subject:
|
Re: summaries on main page
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Fri, 24 Mar 2000 04:52:05 GMT
|
Viewed:
|
572 times
|
| |
|
|
In lugnet.admin.general, Dan Boger writes:
> Hmmm... can someone help me figure out what's going on here?
>
> Here's the summary:
>
> Re: I just died and went to lego heaven... Sheree Rosenkrantz
> Shiri Dori <shirid@hotmail.com> wrote in message
> news:FrwnoL.Fyu@lugnet.com... [...] am... [...] word to [...] here. [...] when
> [...] that [...] and [...] it's [...] because [...] say [...] english [...]
> Shiri, you just moved this Sept.? You are [...] (4 minutes ago, 24-Mar-00, to
> lugnet.general, lugnet.loc.us.ma.bos)
>
> And here's the message:
>
> http://www.lugnet.com/general/?n=16716
>
> Is the brief algorithem broken?
Good question.
No, it's not broken. It's just not as "smart" about repairing bad line breaks
as the "All" view-mode is. Note that the actual article itself is what's
broken. Details:
Here is the raw, actual message, as received, with its line-break problems:
http://www.lugnet.com/news/raw.cgi?lugnet.general:16716
And here's how the "All" view-mode shows it after it cleans up the line
breaks:
http://www.lugnet.com/general/?n=16716&v=a
Any line it "repairs" or "joins back to how it should have been written" is
marked with a bullet character at the join-point.
Here's how the "Brief" view-mode shows the message:
http://www.lugnet.com/general/?n=16716&v=b
The reason the "Brief" mode looks like that is because it doesn't "clean up"
line break problems before compressing the message with [...]'s. So the line
break problems (which actually _are_there_ in the real message) show up in
the "Brief" mode.
The reason the "Brief" mode doesn't clean up the line breaks is for speed-of-
display reasons, because it's used on the homepage and lots of other pages.
Although -- I'm hard-pressed at this point to say that the speed of display is
actually an issue yet. Probably I should "fix" the Brief mode so that it
doesn't look like it has a bug (even though it doesn't) and have it call the
line-repair function before compressing the message. I'll have to come up with
some heuristic or something to pre-chop the message at some guess-point before
fixing the line breaks so that it doesn't waste time doing that over the whole
article just to display the first 250 characters of it. :) Or maybe rework
it to stop after it's accumulated "yay so many" characters of output, via a
collector-callback or something.
--Todd
|
|
Message has 1 Reply:
 | | Re: summaries on main page
|
| (...) Typical programmer answer. :-) Clearly it's not giving good results. But it's working as designed, so it's not a bug. It's a feature. Or a mis-feature. (1) :-) (puts on PM/Architect hat) Whatever you call it, it's not meeting requirements from (...) (25 years ago, 24-Mar-00, to lugnet.admin.general)
|
Message is in Reply To:
| | summaries on main page
|
| Hmmm... can someone help me figure out what's going on here? Here's the summary: Re: I just died and went to lego heaven... Sheree Rosenkrantz Shiri Dori <shirid@hotmail.com> wrote in message news:FrwnoL.Fyu@lugnet.com... [...] am... [...] word to (...) (25 years ago, 24-Mar-00, to lugnet.admin.general)
|
19 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
