1
1

Ran across this comment about i18n support, so I figured I'd update

it.  :-)

This commit was SVN r24631.
Этот коммит содержится в:
Jeff Squyres 2011-04-22 12:14:20 +00:00
родитель ddc44cfbce
Коммит 16d8e9216b

Просмотреть файл

@ -9,7 +9,7 @@
* University of Stuttgart. All rights reserved. * University of Stuttgart. All rights reserved.
* Copyright (c) 2004-2005 The Regents of the University of California. * Copyright (c) 2004-2005 The Regents of the University of California.
* All rights reserved. * All rights reserved.
* Copyright (c) 2008 Cisco Systems, Inc. All rights reserved. * Copyright (c) 2008-2011 Cisco Systems, Inc. All rights reserved.
* $COPYRIGHT$ * $COPYRIGHT$
* *
* Additional copyrights may follow * Additional copyrights may follow
@ -34,13 +34,13 @@
* and printf()-style varargs parameters used to substitute into the * and printf()-style varargs parameters used to substitute into the
* message. * message.
* *
* There's work pending about i18n-like support (nothing near as * It was originally intended that this system would support a very
* complex as GNU gettext -- just a simple mechanism that may be * simple version of i18n-like support, but we got (strong) feedback
* used). But I won't describe it here until/if it's actually used. * that i18n support was not desired. So it never happened.
* So right now, the file lookup is quite straightforward -- the *
* caller passes in the filename to find the help message, and the SHS * As such, the file lookup is quite straightforward -- the caller
* looks for that file in $pkgdatadir (typically * passes in the filename to find the help message, and the SHS looks
* $prefix/share/openmpi). * for that file in $pkgdatadir (typically $prefix/share/openmpi).
* *
* Once the file is successfully opened, the SHS looks for the * Once the file is successfully opened, the SHS looks for the
* appropriate help message to display. It looks for the message name * appropriate help message to display. It looks for the message name