Re: pgawk and Chinese

[Dan Jacobson]

>>>>> "Eli" == Eli Zaretskii <address@hidden> writes:

Eli> On 19 Jun 2001, Dan Jacobson wrote:

>> You probably also want to make a pgawk.1 man page.

Eli> gawk.1 includes the docs for pgawk.  If anything, a simple symlink
Eli> will be enough.

Arnold also says [in a Bcc: email that went into my spamtrap because my
name wasn't in the header]:

A> pgawk is documented on the gawk man page, which ought to do the trick.

I'd say do a ln gawk_manpage pgawk_manpage during make install,
as that way we can have more "any */bin/* has a */man*/* page"
conformity.   I think many users often stumble into great commands
thru typos, then want to learn more about that command with a neat
name by using man <command>... Those commands without any man page
links being some hack the administrator installed not for normal use
etc.

A> Gawk has no knowledge that it's read Chinese characters.
A> It knows they're not in the range of ASCII characters and not
A> regular escapes, so it falls back to the least-common-denominator
A> representation of the source.

I'd say: if the programmer put non-ASCII characters in the source of a
program, he is probably able to deal with it in a pgawk listing of his
source.

Perhaps make least-common-denominator representation be an option:
--least-common-denominator ...

I mean how can one with Chinese character strings in print statements
tell which is which otherwise in the pgawk output?

P.S. $ pgawk --help should say "do man gawk, or better: info gawk" more
explicitly than now.
-- 
http://www.geocities.com/jidanni Tel886-4-25854780 e-mail:restore .com.