Mercurial > emacs
view etc/CENSORSHIP @ 51743:f63c242330b2
2003-06-30 Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
* textmodes/bibtex.el (bibtex-sort-entry-class): new entry
catch-all.
(bibtex-sort-ignore-string-entries): default value t.
(bibtex-entry-kill-ring-max): Reintroduced as it was removed
erroneously in previous version.
(bibtex-string-files): Docstring reflects new parsing scheme.
(bibtex-autokey-transcriptions): Merge some rewrite entries, fix
docstring, add # as one of the chars to crush
(bibtex-autokey-prefix-string, bibtex-autokey-names)
(bibtex-autokey-names-stretch, bibtex-autokey-additional-names)
(bibtex-autokey-name-change-strings)
(bibtex-autokey-name-case-convert, bibtex-autokey-name-length)
(bibtex-autokey-name-separator, bibtex-autokey-year-length)
(bibtex-autokey-use-crossref, bibtex-autokey-titlewords)
(bibtex-autokey-title-terminators)
(bibtex-autokey-titlewords-stretch)
(bibtex-autokey-titleword-ignore)
(bibtex-autokey-titleword-case-convert)
(bibtex-autokey-titleword-abbrevs)
(bibtex-autokey-titleword-abbrevs)
(bibtex-autokey-titleword-change-strings)
(bibtex-autokey-titleword-length)
(bibtex-autokey-titleword-separator)
(bibtex-autokey-name-year-separator)
(bibtex-autokey-year-title-separator)
(bibtex-autokey-before-presentation-function)
(bibtex-entry-type-history, bibtex-entry-maybe-empty-head): Fix
docstring.
(bibtex-strings, bibtex-reference-keys): Use
lazy-completion-table and make-variable-buffer-local.
(bibtex-sort-entry-class-alist): Use downcase, account for
catch-all.
(bibtex-braced-string-syntax-table)
(bibtex-quoted-string-syntax-table): New variables.
(bibtex-parse-nested-braces): Remove.
(bibtex-parse-field-string): Use syntax table and forward-sexp.
(bibtex-parse-association): Simplify.
(bibtex-parse-field-name): Obey bibtex-autoadd-commas.
(bibtex-parse-field-text): Simplify.
(bibtex-search-forward-field, bibtex-search-backward-field):
argument BOUND can take value t.
(bibtex-start-of-field, bibtex-start-of-name-in-field)
(bibtex-end-of-name-in-field, bibtex-end-of-field)
(bibtex-start-of-text-in-field, bibtex-end-of-text-in-field)
(bibtex-start-of-text-in-string, bibtex-end-of-text-in-string)
(bibtex-end-of-string, bibtex-type-in-head): Use defsubst.
(bibtex-skip-to-valid-entry): Return buffer position of beginning
and ending of entry. Update for changes of bibtex-search-entry.
Simplify.
(bibtex-map-entries): FUN is called with three arguments.
(bibtex-search-entry): Return a cons pair with buffer positions of
beginning and end of entry.
(bibtex-enclosing-field): Simplify.
(bibtex-format-entry): Use booktitle to set a missing title.
(bibtex-autokey-get-names): Fiddle with regexps.
(bibtex-generate-autokey): Use identity.
(bibtex-parse-keys): Use simplified parsing algorithm if
bibtex-parse-keys-fast is non-nil. Simplify. Change order of
arguments. Return alist of keys.
(bibtex-parse-strings): Simplify. Return alist of strings.
(bibtex-complete-string-cleanup): Fix docstring.
(bibtex-read-key): New function.
(bibtex-mode): Fix docstring. Do not parse for keys and
strings when the mode is entered. Set fill-paragraph-function to
bibtex-fill-field. Setup font-lock-mark-block-function the way
font-lock intended.
(bibtex-entry): Use bibtex-read-key. Obey bibtex-autofill-types.
(bibtex-parse-entry, bibtex-autofill-entry): New functions.
(bibtex-print-help-message, bibtex-remove-OPT-or-ALT)
(bibtex-Preamble): Avoid hard coded constants.
(bibtex-make-field): Fix docstring. Simplify.
(bibtex-beginning-of-entry): Always return new position of point.
(bibtex-end-of-entry): Rearrange cond clauses.
(bibtex-count-entries, bibtex-validate, bibtex-reformat): Update
for changes of bibtex-map-entries.
(bibtex-ispell-abstract): Do not move point.
(bibtex-entry-index): Use downcase. Simplify.
(bibtex-lessp): Handle catch-all.
(bibtex-find-crossref): Turned into a command.
(bibtex-find-entry): Simplify. Use bibtex-read-key. Fix regexp.
(bibtex-clean-entry): Use bibtex-read-key. Handle string and
preamble entries.
(bibtex-fill-field-bounds): New function.
(bibtex-fill-field): New command. Bound to
fill-paragraph-function.
(bibtex-fill-entry): Use bibtex-fill-field-bounds
(bibtex-String): Use bibtex-strings. Always obey
bibtex-sort-ignore-string-entries.
author | Kai Großjohann <kgrossjo@eu.uu.net> |
---|---|
date | Sat, 05 Jul 2003 12:41:24 +0000 |
parents | e96ffe544684 |
children | 01772baf50a3 |
line wrap: on
line source
Censoring my Software Richard Stallman [From Datamation, 1 March 1996] Last summer, a few clever legislators proposed a bill to "prohibit pornography" on the Internet. Last fall, right-wing Christians made this cause their own. Last week, President Clinton signed the bill, and we lost the freedom of the press for the public library of the future. This week, I'm censoring GNU Emacs. No, GNU Emacs does not contain pornography. It is a software package, an award-winning extensible and programmable text editor. But the law that was passed applies to far more than pornography. It prohibits "indecent" speech, which can include anything from famous poems, to masterpieces hanging in the Louvre, to advice about safe sex...to software. Naturally, there was a lot of opposition to this bill. Not only from people who use the Internet, and people who appreciate erotica, but from everyone who cares about freedom of the press. But every time we tried to tell the public what was at stake, the forces of censorship responded with a lie: they told the public that the issue was simply pornography. By embedding this lie as a presupposition in their statements about the issue, they succeeded in misinforming the public. So here I am, censoring my software. You see, Emacs contains a version of the famous "doctor program", a.k.a. Eliza, originally developed by Professor Weizenbaum at MIT. This is the program that imitates a Rogerian psychotherapist. The user talks to the program, and the program responds--by playing back the user's own statements, and by recognizing a long list of particular words. The Emacs doctor program was set up to recognize many common curse words, and respond with an appropriately cute message such as, "Would you please watch your tongue?" or "Let's not be vulgar." In order to do this, it had to have a list of curse words. That means the source code for the program was indecent. Because of the censorship law, I had to remove this feature. (I replaced it with a message announcing that the program has been censored for your protection.) The new version of the doctor doesn't recognize the indecent words. If you curse at it, it curses right back to you--for lack of knowing better. Now that people are facing the threat of two years in prison for indecent network postings, it would be helpful if they could access precise rules via the Internet for how to avoid imprisonment. However, this is impossible. The rules would have to mention the forbidden words, so posting them on the Internet would be against the rules. Of course, I'm making an assumption about just what "indecent" means. I have to do this, because nobody knows for sure. The most obvious possibile meaning is the meaning it has for television, so I'm using that as a tentative assumption. However, there is a good chance that our courts will reject that interpretation of the law as unconstitutional. We can hope that the courts will recognize the Internet as a medium of publication like books and magazines. If they do, they will entirely reject any law prohibiting "indecent" publications on the Internet. What really worries me is that the courts might take a muddled in-between escape route--by choosing another interpretation of "indecent", one that permits the doctor program or a statement of the decency rules, but prohibits some of the books that children can browse through in the public library and the bookstore. Over the years, as the Internet replaces the public library and the bookstore, some of our freedom of the press will be lost. Just a few weeks ago, another country imposed censorship on the Internet. That was China. We don't think well of China in this country--its government doesn't respect basic freedoms. But how well does our government respect them? And do you care enough to preserve them here? If you care, stay in touch with the Voters Telecommunications Watch. Look in their Web site http://www.vtw.org/ for background information and political action recommendations. Censorship won in February, but we can beat it in November. Copyright 1996 Richard Stallman Verbatim copying and distribution is permitted in any medium provided this notice is preserved.