Re: LYNX-DEV new release?

[Klaus Weide]

On Fri, 15 Aug 1997, Yaping Chen wrote:

> Hi, Klaus,
> 
>       It would be very helpful for me to put lynx in SCO's product if you
> guys can make the decision to put out a new verion for lynx. I am having
> a dealine problem to wait any longer. Now I chose lynx2-7-1 plus
> fotemodes. But it is not a formal version. We need to translate the
> lynx.man to html format to put it in our product. In the man page it is
> hard to explain the version correctly, since the "fotemodes" changes
> everyday. I have to put the date of the fotemodes, but still... 

Well it seems you have found a solution, you just don't like it much :)

>       Another thing is we may be able to work out message catologue
> of internationalization for lynx in our prodcut. It would make more
> sense for us if it is a formal verion.

Well, calling something a formal version doesn't necessarily make it more
stable or usable, it's more of a psychological device...  But I agree
that it's time there should be a Lynx/(some number > 2.7.1) soon, even if
there is nobody here to give a "formal" stamp of approval.

I don't know what is involved in the "working out of message catalogue",
so pardon me if my understanding is too naive.  But I assume it means
making (a) lots of changes to the code itself, and (b) the catologue(s).
Is there a technical reason why you cannot start doing that now, under
the assumption that a coming release would be not-too-different from the
current devel code?  Also, are you planning to contribute all your
internationalization changes back, and are they appropriate for general
use? (In that case, maybe we should be waiting for you, not the other way
around :) )

>       By the way, how should I send back our changes, such as
> lynx.man.html to lynx-org? Do I need to put it in some specific
> place or should I just put in some public place in SCO's site
> and send mail to lynx-dev so that people know where it is?

There is no special address for submitting contributions, at
lynx.browser.org or elsewhere, other than address@hidden, as far as I
know.  Just send mail to the list.  You probably should make clear what
the intention of the changes is, especially whether you suggest that they
be included in the general distribution.


    Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;