> >"nls" seems most appropriate to me.

Most people suggested nls, so that's what it'll be.

> Also, you might note that last time I tried it, the NetBSD nls stuff
> was broken for message files with multiple $set directives. (I think
> that only the first set was used; the rest were ignored).

Hmm.  I haven't noticed this, and the message catalog I've been using
at home has more that one $set.  The code currently in the tree hasn't
been significantly changed since it was extracted from the elm dist.

> So under nls, you're planning to have "C", "german", "finnish", etc.
> subdirectories?

I was planning that each program (or library) that supports message
catalogs would have a subdirectory "nls" that would contain the *.msg
files for that program.  These would be compiled into *.cat files, and
then installed in /usr/share/nls.

For example libc's C.msg would be compiled into C.cat, and installed
in /usr/share/nls/C/libc.cat.

I have not decided on a naming convention for $LANG, so if any of you
have suggestions so that NetBSD will be more interoperable with other
systems please speak up.

	--jtc