Glenn Fowler wrote: > > getopts --man lists getopts details > > note that you can get the usage string for any ast command/script by (ksh > here) > ksh '--??usage' 2>&1 | fmt -o > where fmt is the ast fmt and -o formats usage strings > without fmt -o the usage string will most likely contain little or no newlines > > use $'...' for the usage string > this will properly handle the \b...\b etc. modifiers
How can I get the manual page then localised ? The idea behind using $"..." was to get the manual page put into the output of "ksh -D" and therefore get a translation of the localisation team for free... :-) [snip] > [--catalog?foo] in the usage string provides an alternate catalog name > (besides the script base name provided by ksh at runtime) Will that only affect the manual page or the whole script ? What about the idea to implement something like ".sh.msgcat.name" to make this "dymamic" ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
