Mercurial > emacs
view lisp/gnus/mail-parse.el @ 83094:8e5779acd195
Merged in changes from CVS HEAD
Patches applied:
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-193
Update from CVS
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-194
Update from CVS
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-195
Update from CVS
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-196
Remove RCS keywords
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-197
Stupid CVS keyword changes
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-198
Update from CVS
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-199
Update from CVS
git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-134
author | Karoly Lorentey <lorentey@elte.hu> |
---|---|
date | Sat, 10 Apr 2004 23:06:09 +0000 |
parents | 695cf19ef79e |
children | 55fd4f77387a 375f2633d815 |
line wrap: on
line source
;;; mail-parse.el --- interface functions for parsing mail ;; Copyright (C) 1998, 1999, 2000 ;; Free Software Foundation, Inc. ;; Author: Lars Magne Ingebrigtsen <larsi@gnus.org> ;; This file is part of GNU Emacs. ;; GNU Emacs is free software; you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 2, or (at your option) ;; any later version. ;; GNU Emacs is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs; see the file COPYING. If not, write to the ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330, ;; Boston, MA 02111-1307, USA. ;;; Commentary: ;; This file contains wrapper functions for a wide range of mail ;; parsing functions. The idea is that there are low-level libraries ;; that impement according to various specs (RFC2231, DRUMS, USEFOR), ;; but that programmers that want to parse some header (say, ;; Content-Type) will want to use the latest spec. ;; ;; So while each low-level library (rfc2231.el, for instance) decodes ;; faithfully according to that (proposed) standard, this library is ;; the interface library. If some later RFC supersedes RFC2231, one ;; would just have to write a new low-level library, adjust the ;; aliases in this library, and the users and programmers won't notice ;; any changes. ;;; Code: (require 'mail-prsvr) (require 'ietf-drums) (require 'rfc2231) (require 'rfc2047) (require 'rfc2045) (defalias 'mail-header-parse-content-type 'rfc2231-parse-string) (defalias 'mail-header-parse-content-disposition 'rfc2231-parse-string) (defalias 'mail-content-type-get 'rfc2231-get-value) (defalias 'mail-header-encode-parameter 'rfc2045-encode-string) (defalias 'mail-header-remove-comments 'ietf-drums-remove-comments) (defalias 'mail-header-remove-whitespace 'ietf-drums-remove-whitespace) (defalias 'mail-header-strip 'ietf-drums-strip) (defalias 'mail-header-get-comment 'ietf-drums-get-comment) (defalias 'mail-header-parse-address 'ietf-drums-parse-address) (defalias 'mail-header-parse-addresses 'ietf-drums-parse-addresses) (defalias 'mail-header-parse-date 'ietf-drums-parse-date) (defalias 'mail-narrow-to-head 'ietf-drums-narrow-to-header) (defalias 'mail-quote-string 'ietf-drums-quote-string) (defalias 'mail-header-narrow-to-field 'rfc2047-narrow-to-field) (defalias 'mail-encode-encoded-word-region 'rfc2047-encode-region) (defalias 'mail-encode-encoded-word-buffer 'rfc2047-encode-message-header) (defalias 'mail-encode-encoded-word-string 'rfc2047-encode-string) (defalias 'mail-decode-encoded-word-region 'rfc2047-decode-region) (defalias 'mail-decode-encoded-word-string 'rfc2047-decode-string) (provide 'mail-parse) ;;; arch-tag: 3e63d75c-c962-4784-ab01-7ba07ca9d2d4 ;;; mail-parse.el ends here