Re: [GROFF] Install pdfmark.ms

2006-01-10 Thread Keith MARSHALL
Robert Goulding wrote: > Just an idea for the next release: pdfmark.ms (the source of the > pdfmark manual) should be installed in the examples directory of > the documentation tree. This annotated file is all but essential > for understanding how to create a pdf with the ms and pdfref macros. I

[Groff] Re: preconv autoconfigury

2006-01-10 Thread Werner LEMBERG
> Here is the patch. Now applied to the CVS, thanks. Please test. Werner ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Automated Reference Numbering with Refer & MM

2006-01-10 Thread Joerg van den Hoff
Damian McGuckin wrote: I have never used refer to its fullest capabilities. Luckily I have only ever had only tens of references in my papers, I have just numbered them manually and used a '.RL' to print them. I need to do this properly now because I have to worry about 100+ references in th

Re: [Groff] handling of composing and combined Unicode characters

2006-01-10 Thread Werner LEMBERG
> > Either you register `u0045_0302_0301' with .char directly in your > > document (or in a proper macro file, say, `vi.tmac'), or you add > > this to the devutf8 font description files. > > I want to get rid of the description files for everything that is > related to Unicode characters and can

Re: [Groff] Automated Reference Numbering with Refer & MM

2006-01-10 Thread Damian McGuckin
On Tue, 10 Jan 2006, Joerg van den Hoff wrote: > this is probably not helpful, but could'nt you just switch to MS (where the > necessary macros exit and auto-numbering is not a problem)? As far as I can tell, even the MS macros only autonumber in footnote style. They do not do automatic numberin

[Groff] Re: preconv autoconfigury

2006-01-10 Thread Werner LEMBERG
> > > The different include file name (relocatable.h versus > > > relocate.h) forced me to make a groff-local modification to the > > > localcharset.c file coming from gnulib. > > > > Hmm, any suggestions how to improve that? > > If you were to rename relocate.h to relocatable.h, the rest could be

Re: [Groff] handling of composing and combined Unicode characters

2006-01-10 Thread Bruno Haible
Werner, Thanks for the explanations. > Either you register `u0045_0302_0301' with .char directly in your > document (or in a proper macro file, say, `vi.tmac'), or you add this > to the devutf8 font description files. I want to get rid of the description files for everything that is related to U

[Groff] Re: preconv autoconfigury

2006-01-10 Thread Bruno Haible
Werner LEMBERG wrote: > > The different include file name (relocatable.h versus relocate.h) > > forced me to make a groff-local modification to the localcharset.c > > file coming from gnulib. > > Hmm, any suggestions how to improve that? If you were to rename relocate.h to relocatable.h, the rest

[Groff] Re: preconv autoconfigury

2006-01-10 Thread Werner LEMBERG
> Werner LEMBERG wrote: > > What do you think of providing a dummy relocatable.h file > > in the groff tree which simply includes relocate.h and which sets > > those preprocessor macros? > > If you prefer that, ok. Will have a look in the next few days. > (I tried to minimize the number of files

[Groff] Re: preconv autoconfigury

2006-01-10 Thread Bruno Haible
Werner LEMBERG wrote: > What do you think of providing a dummy relocatable.h file > in the groff tree which simply includes relocate.h and which sets > those preprocessor macros? If you prefer that, ok. (I tried to minimize the number of files.) > BTW, it seems to me that localcharset.c in gnulib

Re: [Groff] handling of composing and combined Unicode characters

2006-01-10 Thread Bruno Haible
Werner, > Please always bear in mind that groff is actually a typesetting > program, not a `man' filter! TTY output is handled similarly to other > decives like PS. This has advantages, but also some disadvantages. > What you want to do probably needs a lot of `Extrawürschte' just for > TTY outp