This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
[COMMITTED] manual/message.texi: Fix English and clarify.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 07 May 2013 12:38:26 -0400
- Subject: [COMMITTED] manual/message.texi: Fix English and clarify.
Team,
While doing work on some of the _nl_* functions I had a chance
to read through manual/message.texi and found some of the language
difficult to follow. I've cleaned it up and checked it in.
2013-05-07 Carlos O'Donell <carlos@redhat.com>
* manual/message.texi (Message Translation): Talk about users.
Clarify that the message to key mapping impacts design.
diff --git a/manual/message.texi b/manual/message.texi
index ea5e1a1..bb5b11b 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.
---
Cheers,
Carlos.