Re: [Groff] Re: Introduction

at I need 40 years more to start to master it." Well, something like that. I don't know where is my copy of the Analects these days. :-) -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Re: Introduction

n showed up in the texinfo distribution. I wonder what happened to that. Has anyone noticed that most man pages in a GNU/Linux system have been written by members of the Debian Documentation Team? Even those of official GNU software? I bow to them. -- Alejandro López-Valencia _

Re: [Groff] Foxit PDF Reader

rendering added in version 7). For a reader I take Evince first anyday even though it is quite unfinished, probably needs two Gnome releases more to reach maturity, Kpdf always finds ways to annoy me. XPdf is based on motif and feels soo 1987, oh well -- Alejandro López-Valencia _

Re: [Groff] XML and groff as frontend

a nail". A good dose of SGML hand-coding should sober up anyone any day. -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] XSL-FO to groff to PDF?

they just don't have the output drivers. -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Introduction

> > In the end, there can be only one. Christophe Lambert or Adrian Paul? -- Alejandro López-Valencia troff spoken here ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] SGR

ansform to use troff as the processing backend and thus have the groff manual eat its own dogfood (a long standing critique is that the groff manual must be typeset with TeX of all things). -- Alejandro López-Valencia troff spoken here ___ Groff mailin

Re: [Groff] SGR

tool, wouldn't be better to promote the use of troff (or some of the macro packages) as an output target for XML transform tools such as Open Jade and OpenSP... -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Introduction

Emacs (or Xemacs)"...! I still wonder why Even plain Sys7 vi has better support (as seen in http://ex-vi-sf.net/ ;-) -- Alejandro López-Valencia troff spoken here ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] SGR

* man). I knew making SGR the default would bite back with a vengeance sooner or later; it was later alright. My mind is at ease on this matter, I kicked and screamed when it was proper to do so and no one listened :-). Check the mailing list archives for the historical records. -

Re: [Groff] PS and "page background"

pages/books.html>: Thinking in Postscript (Glen Reid, 1990). It is available free from the author's website in PDF format. -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Would I dare to post here?

ow more than we do and help those who know less than we do so that they may one day surpass us; that is teach, in the true sense of the word . -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Converting groff input to LaTex input?

old, and pre-groff. > (Moreover, it crashes my Mac OS Tiger.) And it didn't work that nicely then, either. -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Re: What's missing for Unicode support of groff?

as an example for what you would need if using > > vim as your editor. > > You might also make this a package, providing documentation, etc., so > that I can put this to the `contrib' tree on http://groff.ffii.org. > > > Werner That's a deal. I'll look

Re: [Groff] Re: What's missing for Unicode support of groff?

oper character names (which follows Adobe's specification for the most part). -- Alejandro López-Valencia ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: Re: [Groff] Multilingual documents using groff

tup output wifh CJKV fonts. In short, I will repeat Werner's advice: Use CJK LaTeX, which Werner has written and maintains. I've used that package (for as little Japanese I know) and I can say he's done an outstanding job. -- Alejandro López-Valencia ___

Re: [Groff] groff and layout stability

On 4/26/05, Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > On comp.tex.latex there was some discussion w.r.t. document layout > stability and hyphenation patterns: > > Subject: Consistency of US hyphenation patterns across distributions > References: <[EMAIL PROTECTED]> > > Up to today, noone

Re: [Groff] refer question

Mats Broberg wrote: I've begun work on adding refer capabilities to mom. Using the ms refer module as a starting point, I'm setting mom up to use MLA bibliographic rules. MLA seems to be "Modern Language Association". What kind of status (official or unofficial) does this style have? I h

Re: [Groff] developers only?

Otavio Exel wrote: Jorgen Grahn wrote: Yes, the list is dominated by developers and/or power users, but that should not discourage anyone from talking about more basic things. in the hope that "more basic" includes "stupid".. here I go! :-)) This is not stupid! In fact this is not partic

Re: [Groff] developers only?

Otavio Exel wrote: Groff'ers, I see this list is mainly for groff developers; could you please recommend a list for groff users (actually groff newbies)? [ Hola Otavio, there is no beginner's list, but don't be afraid to ask; somebody, usually someone a lot more knowledgeable than I, will answer.

Re: [Groff] mom: Some follow-up questions

Larry McVoy wrote: [blah, blah] 1. Where is the open source client *source code* at the website? I can't find it. http://www.bitmover.com/bk-client.shar And no indication of it in your website whatsoever. 2. Where is the open source license? In the source files. It's basically a BSD

Re: [Groff] mom: Some follow-up questions

Larry McVoy wrote: On Tue, Mar 15, 2005 at 12:50:39PM -0500, Alejandro L?pez-Valencia wrote: I never said CVS or Subverson were better technical choices, you just imposed your fears and biases upon my words. I merely said *better choices*. Yes, you say that but you don't say why. As far

Re: [Groff] mom: Some follow-up questions

Larry McVoy wrote: On Tue, Mar 15, 2005 at 04:51:48AM -0500, Alejandro L?pez-Valencia wrote: IMO, CVS and Subversion are better choices. Have you read ? That's a religious argument, not a technical one. Show me one example of someone saying that CVS or Subve

Re: [Groff] mom: Some follow-up questions

Larry Kollar wrote: Larry K., have you found a new CVS host for the UTP meanwhile? Have you finally announced the UTP on the various lists? Maybe we can find volunteers more easily if more people know of its existence... No, and no. Larry McVoy has offered Bitkeeper, and I'm going to take him u

Re: [Groff] ubuntu, groff and utf-8

Werner LEMBERG wrote: > Michail Vidiassov wrote AFAIK, opentype fonts have tables of relative positions of accented characters and accents, AFM files can have a section describing the construction of composites. Can groff use that information? No. It shouldn't be too difficult to write a scr

Re: [Groff] groff CVS now needs texinfo 4.8

Keith MARSHALL wrote: I never had any success using the groff CVS, as it *should* be used, on MS-Windows, even using Cygwin -- I suspect a corporate firewall may be blocking the SSH data stream :-( But, back on the original topic, texinfo 4.8 builds OOTB with Cygwin. This provides a mechanism for M

Re: [Groff] groff CVS now needs texinfo 4.8

Kees Zeelenberg wrote: > Werner LEMBERG" writes: `progreloc.c' in the gnulib CVS (on Savannah)? I wonder whether it makes sense to use this `canonical' source code instead... request has been sent separately). BTW, have you ever had a look at Of course, it would be preferable to use gnulib for t