From: Paul Eggert Date: Sun, 23 Dec 2012 12:52:28 +0000 (+0000) Subject: Hyphen and dash fixes in texinfo files X-Git-Url: http://cgit.sxemacs.org/?p=gnus;a=commitdiff_plain;h=1676d047efa755d58963b87b71c227dd7e1790db Hyphen and dash fixes in texinfo files --- diff --git a/lisp/ChangeLog b/lisp/ChangeLog index 24aa9e9af..173400627 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -5,7 +5,7 @@ (gnus-open-server): Use it to add more tracing. (gnus-finish-retrieve-group-infos): Add backend tracing. -2012-12-22 Philipp Haselwarter +2012-12-22 Philipp Haselwarter * gnus-sync.el (gnus-sync-file-encrypt-to, gnus-sync-save): Set epa-file-encrypt-to from variable to avoid querying. diff --git a/texi/auth.texi b/texi/auth.texi index 00ef2b1f5..f56a60423 100644 --- a/texi/auth.texi +++ b/texi/auth.texi @@ -10,7 +10,7 @@ @copying This file describes the Emacs auth-source library. -Copyright @copyright{} 2008-2012 Free Software Foundation, Inc. +Copyright @copyright{} 2008--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document diff --git a/texi/emacs-mime.texi b/texi/emacs-mime.texi index e936baf62..df083fd0e 100644 --- a/texi/emacs-mime.texi +++ b/texi/emacs-mime.texi @@ -11,7 +11,7 @@ @copying This file documents the Emacs MIME interface functionality. -Copyright @copyright{} 1998-2012 Free Software Foundation, Inc. +Copyright @copyright{} 1998--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -1855,7 +1855,7 @@ Conformance Criteria and Examples Languages, and Continuations @item RFC1843 -HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and +HZ---A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and @acronym{ASCII} characters @item draft-ietf-drums-msg-fmt-05.txt diff --git a/texi/epa.texi b/texi/epa.texi index 74c966f87..e376e3fb9 100644 --- a/texi/epa.texi +++ b/texi/epa.texi @@ -9,7 +9,7 @@ @copying This file describes EasyPG Assistant @value{VERSION}. -Copyright @copyright{} 2007-2012 Free Software Foundation, Inc. +Copyright @copyright{} 2007--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document diff --git a/texi/gnus-coding.texi b/texi/gnus-coding.texi index 35ec21209..a06fb45bb 100644 --- a/texi/gnus-coding.texi +++ b/texi/gnus-coding.texi @@ -7,7 +7,7 @@ @syncodeindex pg cp @copying -Copyright @copyright{} 2004-2005, 2007-2012 Free Software +Copyright @copyright{} 2004--2005, 2007--2012 Free Software Foundation, Inc. @quotation @@ -300,7 +300,7 @@ reason. @c (typically so far the only exception has been that the changes @c already exist in the trunk in modified form). Because of this, when the next major version of Gnus will be included in -Emacs, it should be very easy -- just plonk in the files from the Gnus +Emacs, it should be very easy---just plonk in the files from the Gnus trunk without worrying about lost changes from the Emacs tree. The effect of this is that as hacker, you should generally only have to @@ -314,7 +314,7 @@ tree, and it will show up in the Gnus tree a few days later. If you don't have Emacs bzr access (or it's inconvenient), you can change such a file in the v5-10 branch, and it should propagate to Emacs -bzr -- however, it will get some extra scrutiny (by Miles) to see if the +bzr---however, it will get some extra scrutiny (by Miles) to see if the changes are possibly controversial and need discussion on the mailing list. Many changes are obvious bug-fixes however, so often there won't be any problem. @@ -329,7 +329,7 @@ including improvements on the documentation. If you know that there will be conflicts (perhaps because the affected source code is different in v5-10 and the Gnus git trunk), then you can install your change in both places, and when I try to sync them, there -will be a conflict -- however, since in most such cases there would be a +will be a conflict---however, since in most such cases there would be a conflict @emph{anyway}, it's often easier for me to resolve it simply if I see two @samp{identical} changes, and can just choose the proper one, rather than having to actually fix the code. diff --git a/texi/gnus-faq.texi b/texi/gnus-faq.texi index 038b78cce..adc84f8e7 100644 --- a/texi/gnus-faq.texi +++ b/texi/gnus-faq.texi @@ -80,7 +80,7 @@ want. This FAQ was maintained by Justin Sheehy until March 2002. He would like to thank Steve Baur and Per Abrahamsen for doing a wonderful -job with this FAQ before him. We would like to do the same - thanks, +job with this FAQ before him. We would like to do the same: thanks, Justin! This version is much nicer than the unofficial hypertext @@ -1038,7 +1038,7 @@ mail groups. Is this a bug? No, that's a matter of design of Gnus, fixing this would mean reimplementation of major parts of Gnus' -back ends. Gnus thinks "highest-article-number - +back ends. Gnus thinks "highest-article-number @minus{} lowest-article-number = total-number-of-articles". This works OK for Usenet groups, but if you delete and move many messages in mail groups, this fails. To cure the diff --git a/texi/gnus.texi b/texi/gnus.texi index e3411ca90..d954a270c 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -11,7 +11,7 @@ @documentencoding UTF-8 @copying -Copyright @copyright{} 1995-2012 Free Software Foundation, Inc. +Copyright @copyright{} 1995--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -1296,7 +1296,7 @@ subscribing these groups. variable defaults to @code{gnus-subscribe-alphabetically}. The ``options -n'' format is very simplistic. The syntax above is all -that is supports -- you can force-subscribe hierarchies, or you can +that is supports: you can force-subscribe hierarchies, or you can deny hierarchies, and that's it. @vindex gnus-options-not-subscribe @@ -2143,14 +2143,14 @@ In groups in some news servers, there might be a big gap between a few very old articles that will never be expired and the recent ones. In such a case, the server will return the data like @code{(1 . 30000000)} for the @code{LIST ACTIVE group} command, for example. Even if there -are actually only the articles 1-10 and 29999900-30000000, Gnus doesn't +are actually only the articles 1--10 and 29999900--30000000, Gnus doesn't know it at first and prepares for getting 30000000 articles. However, it will consume hundreds megabytes of memories and might make Emacs get stuck as the case may be. If you use such news servers, set the variable @code{gnus-newsgroup-maximum-articles} to a positive number. The value means that Gnus ignores articles other than this number of the latest ones in every group. For instance, the value 10000 makes Gnus -get only the articles 29990001-30000000 (if the latest article number is +get only the articles 29990001--30000000 (if the latest article number is 30000000 in a group). Note that setting this variable to a number might prevent you from reading very old articles. The default value of the variable @code{gnus-newsgroup-maximum-articles} is @code{nil}, which @@ -3823,7 +3823,7 @@ So, to move a topic to the beginning of the list of topics, just hit @kbd{C-k} on it. This is like the ``cut'' part of cut and paste. Then, move the cursor to the beginning of the buffer (just below the ``Gnus'' topic) and hit @kbd{C-y}. This is like the ``paste'' part of cut and -paste. Like I said -- E-Z. +paste. Like I said---E-Z. You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So you can move topics around as well as groups. @@ -13665,7 +13665,7 @@ server. The default value of this variable is @code{("XOVER" @vindex nntp-nov-gap @code{nntp} normally sends just one big request for @acronym{NOV} lines to the server. The server responds with one huge list of lines. However, -if you have read articles 2-5000 in the group, and only want to read +if you have read articles 2--5000 in the group, and only want to read article 1 and 5001, that means that @code{nntp} will fetch 4999 @acronym{NOV} lines that you will not need. This variable says how big a gap between two consecutive articles is allowed to be before the @@ -15962,7 +15962,7 @@ Decode Quoted Readable encoding. If you are a member of a couple of mailing lists, you will sometimes receive two copies of the same mail. This can be quite annoying, so @code{nnmail} checks for and treats any duplicates it might find. To do -this, it keeps a cache of old @code{Message-ID}s--- +this, it keeps a cache of old @code{Message-ID}s: @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by default. The approximate maximum number of @code{Message-ID}s stored there is controlled by the @code{nnmail-message-id-cache-length} @@ -16626,8 +16626,8 @@ future. Here are some high and low points on each: @table @code @item nnmbox -UNIX systems have historically had a single, very common, and well- -defined format. All messages arrive in a single @dfn{spool file}, and +UNIX systems have historically had a single, very common, and well-defined +format. All messages arrive in a single @dfn{spool file}, and they are delineated by a line whose regular expression matches @samp{^From_}. (My notational use of @samp{_} is to indicate a space, to make it clear in this instance that this is not the RFC-specified @@ -21174,7 +21174,7 @@ features (inspired by the Google search input language): AND, OR, and NOT are supported, and parentheses can be used to control operator precedence, e.g., (emacs OR xemacs) AND linux. Note that operators must be written with all capital letters to be -recognized. Also preceding a term with a - sign is equivalent to NOT +recognized. Also preceding a term with a @minus{} sign is equivalent to NOT term. @item Automatic AND queries @@ -21222,7 +21222,8 @@ Note that operators must be written with all capital letters to be recognized. @item Required and excluded terms -+ and - can be used to require or exclude terms, e.g., football -american ++ and @minus{} can be used to require or exclude terms, e.g., football +@minus{}american @item Unicode handling The search engine converts all text to utf-8, so searching should work @@ -21359,7 +21360,7 @@ This engine is obsolete. @table @code @item nnir-method-default-engines -Alist of server backend - search engine pairs. The default associations +Alist of pairs of server backends and search engines. The default associations are @example (nnimap . imap) @@ -22574,7 +22575,7 @@ configuration function will use @code{group} as the key. A full list of possible names is listed below. The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer -should occupy. To take the @code{article} split as an example - +should occupy. To take the @code{article} split as an example: @lisp (article (vertical 1.0 (summary 0.25 point) @@ -26351,9 +26352,9 @@ with the information when possible). On the January 31th 2012, Ma Gnus was begun. -If you happen upon a version of Gnus that has a prefixed name -- -``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'', -``Pterodactyl Gnus'', ``Oort Gnus'', ``No Gnus'', ``Ma Gnus'' -- don't +If you happen upon a version of Gnus that has a prefixed name---``(ding) +Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'', +``Pterodactyl Gnus'', ``Oort Gnus'', ``No Gnus'', ``Ma Gnus''---don't panic. Don't let it know that you're frightened. Back away. Slowly. Whatever you do, don't run. Walk away, calmly, until you're out of its reach. Find a proper released version of Gnus and snuggle up to @@ -26500,14 +26501,14 @@ on Son-of-RFC 1036. They have produced a number of drafts proposing various changes to the format of news articles. The Gnus towers will look into implementing the changes when the draft is accepted as an RFC. -@item MIME - RFC 2045-2049 etc +@item MIME---RFC 2045--2049 etc @cindex @acronym{MIME} All the various @acronym{MIME} RFCs are supported. -@item Disposition Notifications - RFC 2298 +@item Disposition Notifications---RFC 2298 Message Mode is able to request notifications from the receiver. -@item PGP - RFC 1991 and RFC 2440 +@item PGP---RFC 1991 and RFC 2440 @cindex RFC 1991 @cindex RFC 2440 RFC 1991 is the original @acronym{PGP} message specification, @@ -26517,15 +26518,15 @@ non-@acronym{MIME} aware @acronym{PGP} format. Gnus supports both encoding (signing and encryption) and decoding (verification and decryption). -@item PGP/MIME - RFC 2015/3156 +@item PGP/MIME---RFC 2015/3156 RFC 2015 (superseded by 3156 which references RFC 2440 instead of RFC 1991) describes the @acronym{MIME}-wrapping around the RFC 1991/2440 format. Gnus supports both encoding and decoding. -@item S/MIME - RFC 2633 +@item S/MIME---RFC 2633 RFC 2633 describes the @acronym{S/MIME} format. -@item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731 +@item IMAP---RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731 RFC 1730 is @acronym{IMAP} version 4, updated somewhat by RFC 2060 (@acronym{IMAP} 4 revision 1). RFC 2195 describes CRAM-MD5 authentication for @acronym{IMAP}. RFC 2086 describes access control @@ -26580,7 +26581,7 @@ circles) @dfn{snapshots}. During this phase, Gnus is assumed to be unstable and should not be used by casual users. Gnus alpha releases have names like ``Oort Gnus'' and ``No Gnus''. @xref{Gnus Versions}. -After futzing around for 10-100 alpha releases, Gnus is declared +After futzing around for 10--100 alpha releases, Gnus is declared @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix, and is called things like ``Gnus 5.10.1'' instead. Normal people are supposed to be able to use these, and these are mostly discussed on the @@ -28167,7 +28168,7 @@ The behavior can be changed by customizing @code{message-insert-canlock}. @item Gnus supports @acronym{PGP} (RFC 1991/2440), @acronym{PGP/MIME} (RFC -2015/3156) and @acronym{S/MIME} (RFC 2630-2633). +2015/3156) and @acronym{S/MIME} (RFC 2630--2633). It needs an external @acronym{S/MIME} and OpenPGP implementation, but no additional Lisp libraries. This add several menu items to the @@ -28586,10 +28587,10 @@ know that the server makes wrong @acronym{NOV} data. @item level @cindex levels -Each group is subscribed at some @dfn{level} or other (1-9). The ones +Each group is subscribed at some @dfn{level} or other (1--9). The ones that have a lower level are ``more'' subscribed than the groups with a -higher level. In fact, groups on levels 1-5 are considered -@dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9 +higher level. In fact, groups on levels 1--5 are considered +@dfn{subscribed}; 6--7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9 are @dfn{killed}. Commands for listing groups and scanning for new articles will all use the numeric prefix as @dfn{working level}. @@ -29165,8 +29166,8 @@ return value. Some back ends could be said to be @dfn{server-forming} back ends, and some might be said not to be. The latter are back ends that generally -only operate on one group at a time, and have no concept of ``server'' ----they have a group, and they deliver info on that group and nothing +only operate on one group at a time, and have no concept of ``server''; +they have a group, and they deliver info on that group and nothing more. Gnus identifies each message by way of group name and article number. A diff --git a/texi/message.texi b/texi/message.texi index e686f39b7..07628ce45 100644 --- a/texi/message.texi +++ b/texi/message.texi @@ -10,7 +10,7 @@ @copying This file documents Message, the Emacs message composition mode. -Copyright @copyright{} 1996-2012 Free Software Foundation, Inc. +Copyright @copyright{} 1996--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -476,7 +476,7 @@ You can use one or more of the above variables. All their values are Now you are all set. Just start composing a message as you normally do. And just send it; as always. Just before the message is sent out, Gnus' MFT generation thingy kicks in and checks if the message already has a -MFT field. If there is one, it is left alone. (Except if it's empty - +MFT field. If there is one, it is left alone. (Except if it's empty; in that case, the field is removed and is not replaced with an automatically generated one. This lets you disable MFT generation on a per-message basis.) If there is none, then the list of recipient @@ -2206,12 +2206,12 @@ This function won't add the header if the header is already present. @item message-send-mail-hook @vindex message-send-mail-hook -Hook run before sending mail messages. This hook is run very late -- +Hook run before sending mail messages. This hook is run very late: just before the message is actually sent as mail. @item message-send-news-hook @vindex message-send-news-hook -Hook run before sending news messages. This hook is run very late -- +Hook run before sending news messages. This hook is run very late: just before the message is actually sent as news. @item message-sent-hook diff --git a/texi/sasl.texi b/texi/sasl.texi index e4b89de19..8209074c5 100644 --- a/texi/sasl.texi +++ b/texi/sasl.texi @@ -10,7 +10,7 @@ @copying This file describes the Emacs SASL library, version @value{VERSION}. -Copyright @copyright{} 2000, 2004-2012 Free Software Foundation, Inc. +Copyright @copyright{} 2000, 2004--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -54,18 +54,18 @@ SASL is a common interface to share several authentication mechanisms between applications using different protocols. @ifnottex -@insertcopying +@insertcopying @end ifnottex @menu * Overview:: What Emacs SASL library is. * How to use:: Adding authentication support to your applications. -* Data types:: +* Data types:: * Back end drivers:: Writing your own drivers. * GNU Free Documentation License:: The license for this documentation. -* Index:: -* Function Index:: -* Variable Index:: +* Index:: +* Function Index:: +* Variable Index:: @end menu @node Overview @@ -106,9 +106,9 @@ security layer---a mechanism, a client parameter and an authentication step. @menu -* Mechanisms:: -* Clients:: -* Steps:: +* Mechanisms:: +* Clients:: +* Steps:: @end menu @node Mechanisms diff --git a/texi/sieve.texi b/texi/sieve.texi index 63c8df3ea..ed55bd6e6 100644 --- a/texi/sieve.texi +++ b/texi/sieve.texi @@ -11,7 +11,7 @@ @copying This file documents the Emacs Sieve package, for server-side mail filtering. -Copyright @copyright{} 2001-2012 Free Software Foundation, Inc. +Copyright @copyright{} 2001--2012 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -212,7 +212,7 @@ Bury the Manage Sieve buffer without closing the connection. @kindex ? @kindex h @findex sieve-help -Displays help in the minibuffer. +Displays help in the minibuffer. @end table