[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] 254/352: Rephrase some parts of README
From: |
Stefan Monnier |
Subject: |
[elpa] 254/352: Rephrase some parts of README |
Date: |
Mon, 07 Jul 2014 14:04:42 +0000 |
monnier pushed a commit to branch master
in repository elpa.
commit 2e81f6677b6a87b389438a754730974161107ed3
Author: Teemu Likonen <address@hidden>
Date: Sun Jun 26 15:03:12 2011 +0300
Rephrase some parts of README
---
README | 28 ++++++++++++++--------------
1 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/README b/README
index 0b1178f..a0e9345 100644
--- a/README
+++ b/README
@@ -43,10 +43,10 @@ output, decides if some parts of text should be marked in
the buffer.
Features
--------
-User can have several different configuration units which are called
+In Wcheck mode's configuration different configuration units are called
"languages". In terms of spelling checker it is natural to think of them
-as different human languages. That's not the only point of view, though.
-In Wcheck mode language is just a configuration unit for certain kind of
+as different human languages. That's only one point of view, though. In
+Wcheck mode language is just a configuration unit for certain kind of
text checking purpose.
Each language can use its own checker engine (external program or a
@@ -58,10 +58,10 @@ used to mark text elements in buffer.
User can create language-specific and major mode specific settings
defining which "faces" to read or skip in buffers. A typical use for
this feature is to spell-check only those areas in buffer which are
-written in human language. For example, in email messages usually the
-message body and Subject header are important enough to spell-check. In
-programming modes user could spell-check only documentation strings and
-comments (or the opposite if you want to use Wcheck mode to check
+written in the target language. For example, in email messages usually
+the message body and Subject header are important enough to spell-check.
+In programming modes user could spell-check only documentation strings
+and comments (or the opposite if you want to use Wcheck mode to check
keywords and syntax of the programming language itself).
Wcheck mode can also be configured to offer any kind of actions for
@@ -73,17 +73,17 @@ or (2) executing interactive command `wcheck-actions' while
the cursor
If you use `wcheck-mode' as a spelling checker then it's natural to
configure an action menu that offers spelling suggestions for the
misspelled word. The action menu could also have an option to add the
-word to spell-checker's dictionary, so that the word is recognized next
-time. That's only one application for Wcheck mode, though. Wcheck mode
-can be configured to find almost any kind of text elements from buffer,
-highlight them, and offer any kind of actions for them.
+word to spell-checker's dictionary, so that the word is recognized in
+the future. That's only one application for Wcheck mode, though. Wcheck
+mode can be configured to find almost any kind of text elements from
+buffer, mark them, and offer any kind of actions for marked text.
How does it compare to other spell-checkers?
--------------------------------------------
The open design makes Wcheck mode (internally) quite different from
-spell-checkers like flyspell-mode and speck-mode. They are specific
+spell-checkers like Flyspell mode and Speck mode. They are specific
tools for spell-checking through Ispell or compatible program and are
therefore very much tied to Ispell's features and command-line
interface. This can be useful if you want to use Ispell or fully
@@ -93,7 +93,7 @@ be other kind of text-checking needs.
The motivation behind Wcheck mode is to offer more general-purpose and
configurable interface for text checking. It can be configured to work
-with almost anything: user's custom shell, awk or perl scripts, Lisp
+with almost anything: user's custom shell, Awk or Perl scripts, Lisp
functions or other checkers and text filters. Even if you only need a
spelling checker for human languages Wcheck mode can be a good choice.
It has more configuration possibilities than other spell-checkers and
@@ -112,7 +112,7 @@ and add the following lines to Emacs's initialization file
(~/.emacs):
(autoload 'wcheck-change-language "wcheck-mode"
"Switch wcheck-mode languages." t)
(autoload 'wcheck-actions "wcheck-mode"
- "Open the action menu." t)
+ "Open actions menu." t)
(autoload 'wcheck-jump-forward "wcheck-mode"
"Move point forward to next marked text area." t)
(autoload 'wcheck-jump-backward "wcheck-mode"
- [elpa] 239/352: Tyylillistä hienosäätöä funktioon wcheck-make-overlay, (continued)
- [elpa] 239/352: Tyylillistä hienosäätöä funktioon wcheck-make-overlay, Stefan Monnier, 2014/07/07
- [elpa] 243/352: Add README file, Stefan Monnier, 2014/07/07
- [elpa] 250/352: Improve wcheck-language-data doc, Stefan Monnier, 2014/07/07
- [elpa] 244/352: Copy Emacs wiki page's content to new README file, Stefan Monnier, 2014/07/07
- [elpa] 249/352: Fix a typo in wcheck-language-data doc string, Stefan Monnier, 2014/07/07
- [elpa] 253/352: Add \< and \> to regexps in "email" language example, Stefan Monnier, 2014/07/07
- [elpa] 252/352: Rephrase grouping construct \(\) description in doc string, Stefan Monnier, 2014/07/07
- [elpa] 247/352: Escape \\< with \\=\\< in wcheck-language-data doc string, Stefan Monnier, 2014/07/07
- [elpa] 248/352: Clearer reference to the license text, Stefan Monnier, 2014/07/07
- [elpa] 255/352: Copy examples from wcheck-language-data doc to README, Stefan Monnier, 2014/07/07
- [elpa] 254/352: Rephrase some parts of README,
Stefan Monnier <=
- [elpa] 261/352: Merge branch 'action', Stefan Monnier, 2014/07/07
- [elpa] 258/352: README: Move copyright and license text to the end, Stefan Monnier, 2014/07/07
- [elpa] 256/352: Add link to the GPL3 license text in www.gnu.org, Stefan Monnier, 2014/07/07
- [elpa] 260/352: The "args" option can no longer be a string, Stefan Monnier, 2014/07/07
- [elpa] 263/352: README: Add a section about source code repository, Stefan Monnier, 2014/07/07
- [elpa] 264/352: Ensure case-fold-search=t in the example email detect function, Stefan Monnier, 2014/07/07
- [elpa] 277/352: Accept any value for case-fold option in customize system, Stefan Monnier, 2014/07/07
- [elpa] 268/352: Add a note for programmers about wcheck-marked-text-at, Stefan Monnier, 2014/07/07
- [elpa] 279/352: Remove examples from wcheck-language-data doc and replace it with URL, Stefan Monnier, 2014/07/07
- [elpa] 272/352: Revert "Emphasize wcheck-language-data-defaults in read-or-skip-faces doc", Stefan Monnier, 2014/07/07