🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: demon.ip.support.pc
Article #871

Re: odd (?) problem: snews' unbatch misses some #<number>s when...

#871
From: pete
Date: Wed, 14 May 2008 16:36
49 lines
3131 bytes
In article  <20080513.1225.80506028snz$@i-m-t.demon.co.uk>
           v$af$ppint@i-m-t.demon.co.uk "ppint. at IMT" writes:

>         - hi; quiet round here, isn't it? [a] must be the excessi^W
>         unaccustomed heat and all those strange sunbeams [b] causing
>         dipspcers to doze off...

Indirectly -- I believe the heat simply makes the beer evaporate 
faster.  ;-)

>         - so, 'specially with your mental health in mind, and to
>         exercise your little gray cells, a problem i've managed to
>         create and inflict upon myself:

[snip description of batch-butchery and the results]

Initially I thought this might be a LF vs CR/LF problem (as Snews 
uses the *nix-like linefeed EOL character), but no.  Batch.txt 
uses standard rfc-whatever CR/LF as line delimiters, which get 
converted to LF for storage in the newsbase.

However, taking a fleeting look at the unbatch source (at least, 
the version I have here which might be different from the JLW 
one) it looks like there is a mechanism which checks the number 
of bytes in an article -- that is, the length of the file between 
successive "#! rnews <length>" entries.  I think it allows some 
leeway, 10 bytes or so, as a check that the "#! rnews.." isn't 
part of an article body <boggle> and if it fails this check it 
assumes that this is _not_ the start of a new article but a 
continuation of the present one.  Which is what I understand you 
are seeing.

So, the lesson learned is to excise articles _very_ carefully.  
If the article you're cutting has for example lots of spurious 
white space or blank lines (or rather the one before) you have to 
maintain that garbag^H^H^H^H^H^Hwhite space.

Oh -- and one more thing: the <number> after the "#! rnews" 
refers I believe to the length of the succeeding article, so when 
excising an article, make sure that you don't accidentally leave 
that "#! rnews" line instead of that of the next actual article.

Hope that makes sense (and that it is not a red herring...)

Pete

-- 
   "We have not inherited the earth from our ancestors,
    we have borrowed it from our descendants."
Technical Details
Message-ID: <1210782979snz@nospam.demon.co.uk>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!204.71.34.3!newsfeed.cwix.com!newsfeed.gamma.ru!Gamma.RU!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Thread: fb525,cdd9002dc8169cc5
X-Google-Attributes: gidfb525,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!204.71.34.3!newsfeed.cwix.com!newsfeed.gamma.ru!Gamma.RU!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: pete@nospam.demon.co.uk
Newsgroups: demon.ip.support.pc
Subject: Re: odd (?) problem: snews' unbatch misses some #<number>s when...
Date: Wed, 14 May 2008 16:36:19 +0000 (UTC)
Organization: PDL
Lines: 49
Message-ID: <1210782979snz@nospam.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: individual.net rHUcpaNwYYyo4ieMVdOtaQdMBG+lUXtvnt6GHE0A1r0nYbCwXZ
X-Orig-Path: nospam.demon.co.uk!not-for-mail
Cancel-Lock: sha1:o2uXuKGX58149MBQS0fsF+eNTWo=
X-Newsreader: Snews v1.32.00 (GeK/PJD)