Hi, At Mon, 21 May 2001 17:55:54 +0100, Colin Watson wrote:
> I'm about to adopt the groff package - I already maintain man-db - and > I'm having problems with the jgroff patch applied by Fabrizio. groff has > a new upstream version (1.17), which I want to package; however, the > Japanese patch doesn't apply cleanly to it (there are a large number of > places where code was simply duplicated in a #ifdef NIPPON section, and > the code that was duplicated has since changed), and I don't yet know > the internals of groff well enough to fix it, nor can I read Japanese to > test the results if I do manage to hack something up. So I think I'm > going to need some help. > > Having cleaned up most of the patch conflicts, the result doesn't > compile. For example: > > env.cc: In method `void environment::add_char(charinfo *)': > env.cc:305: no matching function for call to > `word_space_node::word_space_node (units)' > node.h:201: candidates are: word_space_node::word_space_node(hunits, > int, width_list *, int, node * = 0) > node.h:203: word_space_node::word_space_node(hunits, > width_list *, node * = 0) > node.h:214: word_space_node::word_space_node(const > word_space_node &) > > I guess there are people here who know the jgroff patch a lot better > than I do. Is there any chance that some of the people who worked on it > originally could prepare a patch against the 1.17 source code > (ftp://ftp.ffii.org/pub/groff/groff-1.17.tar.gz) and send it to me or to > the BTS? I apologize for this being somewhat short notice. If it's > already been done and is available elsewhere, a pointer would be greatly > appreciated. I'm trying to fix jgroff patch into groff-1.17. Just now, I've succssfully built groff 1.17 deb with jgroff patch. I put it http://people.debian.org/~ukai/groff/ It seems to work well at least to browse Japanese manaul pages, but I'm not tested well and patch is not cleaned up, so please wait a few days. > If the patch could be made clean enough that upstream would be willing > to accept it rather than leave it in my inexpert hands, that would be > even better. :) Sure :-) Regards, Fumitoshi UKAI
