Re: lynx-dev Re: lynx should respect LANG

[Henry Nelson]

> or ~/.lynxrc but it is not true that there is no need to touch 
> userdefs.h at all just "for Japanese users."

What define(s) do Japanese users _have_ to set in userdefs.h?

> - Japanese input did not work correctly with Lynx2.8.2.
>   It is Lynx2.8.3 that one can input Japanese or delete
>   Japanese character correctly.

You mean the built-in editor?  Well, I admit it's not perfect, but
that is another topic.  Furthermore, it's not just Japanese.  No amount
of munging of lynx.cfg is going to solve those problems for you.

> - Japanese messages could not be displayed with Lynx2.8.1
>   It is Lynx2.8.2 that uses *.po files.  And, yes, I put

You're talking about NLS here.  If you really want to do _that_ right,
I still think the wrapper is the best way to go.  With a single binary
you could easily have support for any number of messages catalogues,
even offer them as choices in a menu.  With NLS you're mostly interested
in TEXTDOMAIN and TEXTDOMAINDIR, not LANG, as I am sure you are aware.

>   (And I used LYMessages_ja.h of Asada-san with Lynx2.8.1)

We all used them, from Lynx2.3, more than 5 years ago.  For you to tell
me that Lynx is/was not one of the forerunners of CJK support is a total
mind blower.

> So it is Lynx2.8.3 that one can say that Lynx works satisfactorily
> for Japanese.                                       ^^^^^^^^^^^^^^

Guess it's what one believes is satisfactory.  Ever used Netscape ver 2,
now _that_ is hard to stomach.

> > The lynx binary is exactly the same no matter what $LANG is.
> 
> I think it is a problem in which a user must set up by hand
> in any way.  And please think of novice users.

Who do you think I am thinking about?  It is the novices who are the
ones who have to learn.  It's the experienced users who can cut corners
and slack off, fool with userdefs.h and be done with it.

> Even recently there are mails asking "Lynx does not display
> Japanese correctly, please tell me how to do" in a mailing list
> of Debian JP.  (Of cource my answer is "Install lynx-ja")

That's not an answer.  The question was "tell me how to do."  Well,
why don't you tell them?  In your words: "please think of novice users."

> I hope you will understand what I want to say.  And it is true,

I'm sorry, but I do not.

> I think, that a wrapper is a good candidate but if it is possible
> it is not bad that lynx binary can handle these problems in some

If it can be done well, and I believe it can be done better, with
a wrapper, then coding is unnecessary and adds weight where it is
not wanted.

__Henry

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden