On 25/04/2009, ольга крыжановская <[email protected]> wrote: > On 4/25/09, Wendy Lin <[email protected]> wrote: > > I need help with $"string" strings to localise a script until Tuesday. > > I created a test script with $"string" messages, ran ksh -D to extract > > the strings but gencat refuses to process this output with a Syntax > > error message. > > > > Can anyone provide a complete example with NLSPATH for Solaris how I > > can localise a script from the beginning to the end, please? > > > I tried to apply the description in > http://wooledge.org:8000/BashFAQ/098 to ksh93 but failed: > $ cat myscript > #!/usr/bin/ksh93 > echo $"hello world" > $ mkdir jjj > $ cd jjj > $ cat myscript.in > msgid "hello world" > msgstr "hello world l10n" > $ /usr/bin/msgfmt -s -o myscript.cat myscript.in > $ cd .. > $ NLSPATH="$HOME/jjj/%N.cat" gettext -d myscript "hello world" > hello world l10n > $ TEXTDOMAIN="myscript" NLSPATH="$HOME/jjj/%N.cat" bash ./myscript > hello world l10n > $ TEXTDOMAIN="myscript" NLSPATH="$HOME/jjj/%N.cat" ksh93 ./myscript > hello world > > It looks the built in gettext support in ksh93 is broken.
I agree this is broken or not sufficiently documented. My manager wishes to ask if a AST support contract is required to obtain information how to use $"string" or a bug fix? Wendy _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
