mirror of
https://sourceware.org/git/glibc.git
synced 2024-12-23 03:10:05 +00:00
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.
This commit is contained in:
parent
a917305749
commit
e8dd47916f
@ -1,3 +1,8 @@
|
||||
2013-05-07 Carlos O'Donell <carlos@redhat.com>
|
||||
|
||||
* manual/message.texi (Message Translation): Talk about users.
|
||||
Message to key mapping impacts design.
|
||||
|
||||
2013-05-06 Roland McGrath <roland@hack.frob.com>
|
||||
|
||||
* sysdeps/unix/sysv/linux/wordsize-64/glob64.c: New file.
|
||||
|
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user