Bug 18773

Summary:	Merge ports/japanese/less to src/contrib/less
Product:	Base System	Reporter:	Makoto Matsushita <matusita>
Component:	bin	Assignee:	Mark Linimon <linimon>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	5.0-CURRENT
Hardware:	Any
OS:	Any

Description Makoto Matsushita 2000-05-23 10:10:01 UTC

	Now we have /usr/bin/less, however, it's *pure* less; no
	japanese users are happy, they *should* install yet another
	less available via ports (ports/japanese/less).

Fix: 

Merge changes which is done in ports/japanese/less.
How-To-Repeat: 
	/usr/bin/less whatever-textfile-which-is-written-in-japanese

Comment 1 Makoto Matsushita 2000-09-27 05:47:11 UTC

Here is a summary of this PR.

* No one checked this PR, however,

* I've heard that there are efforts to do that, is it right?

-- -
Makoto `MAR' MATSUSHITA

Comment 2 Giorgos Keramidas freebsd_committer

2002-01-12 05:32:00 UTC

Responsible Changed
From-To: freebsd-bugs->matusita

Makoto can take care of his own PR now :)

Comment 3 matusita freebsd_committer

2002-01-26 04:41:15 UTC

State Changed
From-To: open->analyzed

It's easy to merge process itself, but it also requires that maintaining 
processes.  The jam less (less extensions to ISO-2022-JP or other charset) 
said in his webpage <URL:http://www.io.com/~kazushi/less/> that: 

Copyright and future of this patch 

I, sometimes, submitted my patches and asked Mark to merge mine to 
the original tree. However, these are not merged. He said he may 
merge in future. I also think this code is too compilcated to 
understand without ISO 2022 knowledge, so I think this will not be 
merged.  

On the other hand, there is a copyright issue. The copyright of an 
original less was BSD-style licnese. Then, it is changed to GPL 
once. Currently, it is using both, GPL and less license. I 
personally don't want to publish my libraries under the GPL. So, 
my patch is under only BSD-style less license.  

It seems that it's hard to intergrate both into the single one, but I 
*hope* that will happen in the future.  So keep this PR un-closed state.

Comment 4 matusita freebsd_committer

2002-01-31 17:39:04 UTC

State Changed
From-To: analyzed->suspended

'suspended' is more appropriate state for this PR.

Comment 5 Mark Linimon freebsd_committer

2008-11-12 15:07:04 UTC

State Changed
From-To: suspended->closed

matusita has had his src commit bit taken for safekeeping.  With bugmeister 
hat, close this PR, since nothing has happened on it in years.

Comment 6 Mark Linimon freebsd_committer

2008-11-12 15:07:04 UTC

Responsible Changed
From-To: matusita->linimon