Re: optik...what about subcommands, then? :) (fwd)

On Tue, May 06, 2003 at 08:05:16PM -0400, Greg Ward wrote:
> Good point.  Feel free to file a bug with the Optik project
> (optik.sf.net).  It's much more likely to get fixed if you supply a
> patch, though.  (Patches should be relative to the Optik CVS, in unified
> diff ("diff -u") format.)
i've filed a bug with a supplied patch to 1.4.1. if you really want a patch
against CVS HEAD, i can provide that too. do you think the way this patch
does it is ok?

i've only bothered to wrap strings that will be displayed to users for
correctly configured Optik parsers...i think you'll want error messages
indicating problems with Optik state/configuration to still be in English for
you as author to be able to debug user problems in any fashion.

i also purposely didn't wrap the strings inside self.error() and the like
for the obvious reason that users will want the flexibility of having
formattable strings in their .po files.

i've tested these changes with the following code in my application:

import gettext
_ = gettext.gettext

gettext.bindtextdomain('nvp', localedir)
gettext.textdomain('nvp')

and having a compiled .po file with all the _() strings in optik.

leon.


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com