Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Anupam Sengupta <anupamsg@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: What exactly is a NOV header
Date: Wed, 04 Jul 2007 13:17:51 -0700	[thread overview]
Message-ID: <m2myyb9b4g.fsf@gmail.com> (raw)
In-Reply-To: <m2r6no7xbn.fsf@gmail.com>

>>>>> "Anupam" == Anupam Sengupta <anupamsg@gmail.com> writes:

>>>>> "Madhu" == Madhu  <enometh@meer.net> writes:
    Slackrat> Slackrat <87ps38lx7i.fsf@azurservers.com> wrote:
    Slackrat> Could someone please refer me to a definition of exactly what a
    Slackrat> NOV header is in simple language?

    Anupam> NOV stands for _News Overview_ and is a header/database format for
    Anupam> newsreaders to process data in the NNTP articles. This format was
    Anupam> developed by Geoff Collyer and is now a defacto standard for NNTP
    Anupam> newsreaders - including Gnus.

    Anupam> You can read more about the NOV format and headers at:

    Anupam> http://www.faqs.org/faqs/usenet/software/inn-faq/part1/section-15.html

    Madhu> Its described in the info file for gnus.  Did you already read this:
    Madhu> M-x eval-expression RET (info "(gnus)Headers") RET

    Anupam>     No. NOV is NOT described in the info node you mentioned (at
    Anupam> least on my install, which is gnus v5.11). Please check before
    Anupam> posting. A *reference* is made to NOV headers - but as the OP
    Anupam> pointed out, no definition of *what* NOV headers are is not
    Anupam> provided.

Another good definition is at:

http://quimby.gnus.org/notes/nov-faq.txt

>From the FAQ:

,----
| _What is the Overview/NOV database?_
| 
| The Overview or News OverView (NOV) database was designed by Geoff
| Collyer.  Its a more generalized database, it it contains *no*
| threading information, just the information needed to thread.  The
| overview database is just a database of files, one for each group,
| containing a reference to each article, with seven or eight of the
| most popular headers.  Thus, the newsreader client can get most of the
| information it needs to thread, but it does the threading the way it
| wants to.  Yes, the downside is that now the threading occurs on the
| client's CPU, but that's not as expensive as it may seem, if done
| properly. 
`----

-- 
Anupam

  reply	other threads:[~2007-07-04 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  2:27 Slackrat
     [not found] ` <m3ved0zaqr.fsf@robolove.meer.net>
2007-07-04 20:01   ` Anupam Sengupta
2007-07-04 20:17     ` Anupam Sengupta [this message]
2007-07-04 23:26       ` Slackrat
     [not found]     ` <m3sl831w7y.fsf@robolove.meer.net>
2007-07-05  5:36       ` Anupam Sengupta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2myyb9b4g.fsf@gmail.com \
    --to=anupamsg@gmail.com \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).