From: Karl Eichwalder <ke@gnu.franken.de>
Subject: Missing washing function
Date: Sat, 25 Oct 2003 19:43:51 +0200 [thread overview]
Message-ID: <shvfqdjjqg.fsf@tux.gnu.franken.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
It happens quite often that people send "flowed" messages, but failed to
declare them properly (I'll attach such a message - I hope Emacs will
not strip the SPCs at the end of the lines). Run `W w' on such a
message will fill it nicely, but it will not determine paragraphs ends
properly (after "Preface", after "worldwide access.", etc.). Lines to
be flowed together end with a SPC, paragraph ends end with a non-SPC
character.
I'd like to propose to make the washing function add an additional at
the end of an paragraph.
[-- Attachment #2: Type: message/rfc822, Size: 2370 bytes --]
From: "Karl Dietz" <karl.dietz@gmx.de>
To: inetbib@ub.uni-dortmund.de
Subject: Berlin Declaration on Open Access to Knowledge
Date: Sat, 25 Oct 2003 13:54:15 +0200
Message-ID: <3F9A8087.15189.59D7097@localhost>
Berlin Declaration on Open Access to Knowledge
in the Sciences and Humanities
Preface
The Internet has fundamentally changed the practical and
economic realities
of distributing scientific knowledge and cultural
heritage. For the first
time ever, the Internet now offers the chance to
constitute a global and
interactive representation of human knowledge, including
cultural heritage
and the guarantee of worldwide access.
We, the undersigned, feel obliged to address the
challenges of the Internet
as an emerging functional medium for distributing
knowledge. Obviously,
these developments will be able to significantly modify
the nature of
scientific publishing as well as the existing system of
quality assurance.
In accordance with the spirit of the Declaration of the
Budapest Open Acess
Initiative, the ECHO Charter and the Bethesda Statement
on Open Access
Publishing, we have drafted the Berlin Declaration to
promote the Internet
as a functional instrument for a global scientific
knowledge base and human
reflection and to specify measures which research policy
makers, research
institutions, funding agencies, libraries, archives and
museums need to
consider.
Goals
Our mission of disseminating knowledge is only half
complete if the
information is not made widely and readily available to
society. New
possibilities of knowledge dissemination not only
through the classical
form but also and increasingly through the open access
paradigm via the
Internet have to be supported. We define open access as
a comprehensive
source of human knowledge and cultural heritage that has
been approved by
the scientific community.
In order to realize the vision of a global and
accessible representation of
knowledge, the future Web has to be sustainable,
interactive, and
transparent. Content and software tools must be openly
accessible and
compatible.
[...]
aus:
------------
<{HYPERLINK "http://www.zim.mpg.de/openaccess-
berlin/berlindeclaration.html"}http://www.zim.mpg.de/openaccess-
berlin/berlindeclaration.html>
[-- Attachment #3: Type: text/plain, Size: 214 bytes --]
--
| ,__o
| _-\_<,
http://www.gnu.franken.de/ke/ | (*)/'(*)
next reply other threads:[~2003-10-25 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 17:43 Karl Eichwalder [this message]
2003-10-28 0:51 ` Karl Pflästerer
2003-10-28 19:30 ` Karl Eichwalder
2003-10-28 20:58 ` Karl Pflästerer
2003-10-28 22:01 ` Jesper Harder
2003-10-29 1:50 ` Karl Pflästerer
2003-10-30 19:52 ` Karl Eichwalder
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=shvfqdjjqg.fsf@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
/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).