summaryrefslogtreecommitdiff
path: root/manual/message.texi
diff options
context:
space:
mode:
authorCarlos O'Donell <carlos@redhat.com>2013-05-07 12:33:44 -0400
committerCarlos O'Donell <carlos@redhat.com>2013-05-07 12:33:44 -0400
commite8dd47916fdb437ae44163719e6e876f9073e5d4 (patch)
tree5baafc9dcd5a90f0743a33d42f8b8bca5545c3e2 /manual/message.texi
parenta9173057496fb751210f857dbd2310e9ed8431c3 (diff)
manual/message.texi: Fix english and clarify.
Rewrite the first paragraph to talk about users not humans, and to use correct English. Clarify that it is the mapping of messages to IDs that impacts the design of the message translation API. --- 2013-05-07 Carlos O'Donell <carlos@redhat.com> * manual/message.texi (Message Translation): Talk about users. Message to key mapping impacts design.
Diffstat (limited to 'manual/message.texi')
-rw-r--r--manual/message.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/manual/message.texi b/manual/message.texi
index ea5e1a1326..bb5b11bc6f 100644
--- a/manual/message.texi
+++ b/manual/message.texi
@@ -2,9 +2,9 @@
@c %MENU% How to make the program speak the user's language
@chapter Message Translation
-The program's interface with the human should be designed in a way to
-ease the human the task. One of the possibilities is to use messages in
-whatever language the user prefers.
+The program's interface with the user should be designed to ease the user's
+task. One way to ease the user's task is to use messages in whatever
+language the user prefers.
Printing messages in different languages can be implemented in different
ways. One could add all the different languages in the source code and
@@ -40,7 +40,7 @@ map a given key to the translated message
@end itemize
The two approaches mainly differ in the implementation of this last
-step. The design decisions made for this influences the whole rest.
+step. Decisions made in the last step influence the rest of the design.
@menu
* Message catalogs a la X/Open:: The @code{catgets} family of functions.