Re: [groff] groff as the basis for comprehensive documentation?

ref="#description"], a[href="#authors"] { text-transform: uppercase; } Will typecast any link pointing to in majuscule "NAME". It's all CSS. =) On 21 April 2018 at 08:29, Steffen Nurpmeso wrote: > Ralph Corderoy wrote: > |Ingo wrote: > |

Re: [groff] groff as the basis for comprehensive documentation?

Nate Bargmann wrote: |* On 2018 19 Apr 18:47 -0500, James K. Lowden wrote: |> On Fri, 20 Apr 2018 01:44:06 +1000 |> John Gardner wrote: ... |I, for one, do not expect an HTML rendered version of *anything* to |be a faithful representation of a printed page. The output of |"groff -man -Th

Re: [groff] Brian Kernighan on the evoution of eqn, pic, grap, into troff

Mike Bianchi wrote: |True confession: Brian Kernighan is my hero. (stories upon request) | |In this talk, starting at about 41:45, he talks about the history of \ |creating |the eqn, pic, grap "little languages". |I offer it for those who might want a sense of how groff wound up where \ |

Re: [groff] hyphenation issues

Keith Marshall wrote: |On 05/05/18 10:48, G. Branden Robinson wrote: |> (Incidentally, I share your preference for putting type qualifiers |> [as opposed to storage classes] _after_ the type name itself. It |> makes complex declarations easier to understand.) | |Personally, I consider that

Re: [groff] Brian Kernighan on the evoution of eqn, pic, grap, into troff

Tadziu Hoffmann wrote: |> Computer Science - Brian Kernighan on successful language design |> https://www.youtube.com/watch?v=Sg4U4r_AgJU |> "How to succeed in language design without really trying." | |Very interesting. It's somewhat amusing to see that already |in 1961 (!) the proliferati

Re: [groff] Duff's Device lurking in refer.cpp

G. Branden Robinson wrote in <20180626153737.mf72sv3paetlc...@crack.dead\ beast.net>: |I enjoyed this Easter egg; maybe you will too. Why easter egg if i might ask? |src/preproc/refer/refer.cpp: ... |while (opt != 0 && *opt != '\0') { | switch (*opt) { ... | case '-': |

Re: [groff] Accented Cyrillic characters

Werner LEMBERG wrote in <20180802.162932.2121529583718521640...@gnu.org>: |> There appears to be specific code in groff to explicitly *BREAK* the |> return value of wcwidth(3). Actually, egregious mishandling of |> wcwidth(3) is a quite common error in application programs, so groff |> is cert

Re: [groff] mom manpage

Hello Ingo, Ingo Schwarze wrote in <20181201120713.ga89...@athene.usta.de>: |John Gardner wrote on Sat, Dec 01, 2018 at 05:36:25PM +1100: |> Ingo Schwarze wrote: |>> Even moderately large systems can be beautifully documented in a |>> single manual page - for example, a shell | |> It's amazi

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

Ingo Schwarze wrote in <20181209133200.gc7...@athene.usta.de>: .. |Ralph Corderoy wrote on Sun, Dec 09, 2018 at 10:36:25AM +: .. |> The time-honoured way to achieve this is using the built-in `set'. |> |> $ l='foo bar xyzzy' |> $ set -- $l; for f; do echo f=$f; done | fmt |>

Re: [groff] Regularize (sub)section cross references.

Tadziu Hoffmann wrote in <20181218231523.gm7...@usm.uni-muenchen.de>: |>> I'm against this whole locale thing. It needlessly |>> complicates groff and will probably fail when reading |>> foreign manual pages in a "C" locale. | |> That's _already_ a big fail, depending on the language. | |No

Re: [groff] a5 paper size?

John Gardner wrote in : |Hi Ricky, | |Try passing the paper-size option directly to Groff: | |groff -Tpdf *-P-l* … I have an A4 alias with -dpaper=a4 -P-pa4 --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach d

Re: [groff] no header in Japanese manpages

Hello. KUBO Koichi wrote in <51fe9714-c2f9-5351-e4d5-aacc92fa0...@obuk.org>: |I am using groff-1.22.4 on FreeBSD. |After updating groff, I realized that there is no header in Japanese |manpages using mdoc.tmac. So I added the following line to |mdoc.local: | |.if ((\n[.x]\n[.y] >= 122) & (\

Re: [groff] no header in Japanese manpages

KUBO Koichi wrote in <51db73de-bc1a-e930-1be6-b5b04e432...@obuk.org>: |On 4/21/19 2:22 AM, Steffen Nurpmeso wrote: |> KUBO Koichi wrote in <51fe9714-c2f9-5351-e4d5-aacc92fa0...@obuk.org>: |>|I am using groff-1.22.4 on FreeBSD. |>|After updating groff, I realized that

Re: [groff] 04/05: {g, n}roff.1.man: Give assistance to pager users.

James K. Lowden wrote in <20190703140438.a516b5af83532af9d7aa883b@schema\ mania.org>: |On Wed, 3 Jul 2019 07:08:44 +1000 |John Gardner wrote: | |> Really? That's interesting. What did do? On the terminal |> emulators I have on hand at the moment, none of them are responding |> or behaving d

Re: [groff] [PATCH] new requests to case-transform string register values

G. Branden Robinson wrote in <20190703154957.27lxnueucvu2cr5v@localhost.\ localdomain>: |A recurring theme in my man page clean-up work has been my violent |antipathy for shouting capitals in their texts. While I don't _like_ |being shouted at for reasons other than true emergency, the real pro

Re: [groff] 04/05: {g, n}roff.1.man: Give assistance to pager users.

Steffen Nurpmeso wrote in <20190704202830.ds7rz%stef...@sdaoden.eu>: |James K. Lowden wrote in <20190703140438.a516b5af83532af9d7aa883b@schema\ |mania.org>: ||On Wed, 3 Jul 2019 07:08:44 +1000 ||John Gardner wrote: || ||> Really? That's interesting. What did do? On the

Re: [groff] MacTeX (was: groff and pipes)

Douglas Johnson wrote in <20190807133230.ga25...@panix.com>: |On Aug 07, 2019, at 08:40, John Gardner wrote: | |>Installing TeX on macOS also requires a 3.9 GB download of the full |>MacTeX distribution, whereas Groff's source tree doesn't even consume |>that much space... | |Installing th

Re: [groff] Table of content for UTP in groff format

Andrea D'Amore wrote in : |On Thu, 24 Oct 2019 at 17:11, Andrea D'Amore wrote: |> link "groff and PostScript files--Beta" at [1] and built the default \ |> "utp_book.ps" target. |[…] |> [1]: https://www.oreilly.com/openbook/utp/ | |While [1] is active the mentioned link points to a differen

Re: [groff] Table of content for UTP in groff format

Andrea D'Amore wrote in : |Hello, |I got the "UNIX Text Processing" book in groff format, link "groff and |PostScript files--Beta" at [1] and built the default "utp_book.ps" |target. |The resulting PostScript file and its conversion to PDF via ps2pdf |have no outline. | |I see the Makefile

Re: pic anomalies

Doug McIlroy wrote in <201912271608.xbrg84jr128...@tahoe.cs.dartmouth.edu>: |The description of sprintf in the man page pic(1) does not |reveal that only a few format codes are permitted. | |Eric Raymond's "Making Pictures With GNU PIC" says only |%,%e,%f,%g are permitted. But what does a bar

Re: pic anomalies

Ingo Schwarze wrote in <20191227212705.gi66...@athene.usta.de>: |Hi Doug, | |Steffen Nurpmeso wrote on Fri, Dec 27, 2019 at 06:45:23PM +0100: | |> Should be handled by [...] | |I believe the first patch that got sent to the list is incorrect. | |The parser in src/pre-pic/pic.

Re: man Macro Package and pdfmark

Jeff Conrad wrote in : |A major drawback to manual pages formatted using the man macros is the |lack of bookmarks in a PDF file. A quick and dirty way to get bookmarks |appears to be adding | |.am SH |.pdfbookmark 1 "\&\\$*" |.. |.am SS |.pdfbookmark 2 "\&\\$*" |.. Why quick and dirty?

Re: man Macro Package and pdfmark

Ingo Schwarze wrote in <20200214184532.gj92...@athene.usta.de>: |Hi Jeff, | |Jeff Conrad wrote on Thu, Feb 13, 2020 at 03:45:10PM -0800: | |> A major drawback to manual pages formatted using the man macros is the |> lack of bookmarks in a PDF file. A quick and dirty way to get bookmarks |>

Re: Groff macro to make .UR and .UE links clickable in PDF?

B 9 wrote in <20200619061008.okwcr%hacke...@member.fsf.org>: |Since mdoc is a "semantic markup language", I presumed it would have |some way to specify a hyperlink in running text that won't (to the |best of mdoc's abilities) interfere with the flow of the text. The |exact implementation would

Fwd: Re: Groff macro to make .UR and .UE links clickable in PDF?

--- Forwarded from B 9 --- Date: Fri, 19 Jun 2020 13:55:30 -0700 From: B 9 To: Steffen Nurpmeso Subject: Re: Groff macro to make .UR and .UE links clickable in PDF? Message-ID: <20200619205530.n0y90%hacke...@member.fsf.org> Steffen Nurpmeso wrote: > Yes i am reading this list and

Re: .Xr mdoc(7) from groff_mdoc(7)?

I am off-topic. Ingo Schwarze wrote in <20200625214812.gf90...@athene.usta.de>: |given that two authoritative manual pages for the mdoc language |exist that describe exactly the same language, but in a somewhat ... | The manual page groff_mdoc(7): https://man.voidlinux.org/groff_mdoc | cont

Re: Groff macro to make .UR and .UE links clickable in PDF?

Michael Pirkola wrote in <20200717123254.3aff0148@walrus>: |On Sat, 11 Jul 2020 09:28:45 +0100 |Colin Watson wrote: | |> On Fri, Jul 10, 2020 at 11:26:46AM -0400, Steve Izma wrote: |>> I think it's an abomination that a man page extends it's line |>> length to fit the width of the terminal;

Re: Plan 9 man added a new macro for man page references

G. Branden Robinson wrote in <20200815112655.xow4f3d4dcdaiaui@localhost.localdomain>: |[CCing Russ Cox out of the blue; Russ, I work on GNU roff] | |Plan 9 went and did an interesting thing[1]. They implemented a macro |just for man page cross-references. ... |[1] https://github.com/9fans/

Re: manlint?

Sergiusz Pawlowicz wrote in : |Hi, |is there anything like "manlint"? |A tool which verifies the syntax of a man file and eventually points \ |to errors? Use "mandoc -Tlint". It has flaws but is the best i know. You can also use FreeBSD's igor, it is meant for mdoc macros but nonetheless can

Re: [groff] 01/08: mdoc: Accept mixed-case section headings.

Hallo Ingo. Ingo Schwarze wrote in <20200915133505.gi1...@athene.usta.de>: |Hi Steffen, | |Steffen Nurpmeso wrote on Tue, Sep 15, 2020 at 01:59:04PM +0200: | |> Just out of interest: why do you change an omnipresent idiom that |> is in use for standard section headers in Unix

Re: [groff] 01/08: mdoc: Accept mixed-case section headings.

G. Branden Robinson wrote in <20200915183356.3xt3ywitpzifixm2@localhost.localdomain>: |At 2020-09-15T13:59:04+0200, Steffen Nurpmeso wrote: |> Just out of interest: why do you change an omnipresent idiom that |> is in use for standard section headers in Unix manual pages since

Re: [groff] 01/08: mdoc: Accept mixed-case section headings.

G. Branden Robinson wrote in <20200927063701.vj6bg474km3ofpfh@localhost.localdomain>: |At 2020-09-16T01:21:14+0200, Steffen Nurpmeso wrote: |> C64 had no login. And DMR would not have used it. |> I am all with Tadziu Hoffmann in this thread. | |Did Tadziu comment on this thre

Re: [bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints

Dave wrote in <20201013-025509.sv93119.83...@savannah.gnu.org>: |Update of bug #42233 (project groff): | | Summary: wcwidth(3) used on UCS4/UTF-32 codepoints \ | => [PATCH] |wcwidth(3) used on UCS4/UTF-32 codepoints My patch is based on old groff and even more

Re: [bug #43541] [PATCH] FILE* encapsulation via class; compression support for input files

Dave wrote in <20201013-025522.sv93119.18...@savannah.gnu.org>: |Update of bug #43541 (project groff): | | Summary: FILE* encapsulation via class; compression \ | support |for input files => [PATCH] FILE* encapsulation via class; compression \ |support |for i

Re: [bug #45034] [PATCH] mdoc(7): add support for the mdocmx(7) reference extension

Dave wrote in <20201013-025534.sv93119.11...@savannah.gnu.org>: |Update of bug #45034 (project groff): | | Summary: mdoc(7): add support for the mdocmx(7) reference |extension => [PATCH] mdoc(7): add support for the mdocmx(7) reference |extension Likewise, i am not going to r

Re: Learning troff - where to start?

Greg 'groggy' Lehey wrote in <20201013232627.gb24...@eureka.lemis.com>: |On Tuesday, 13 October 2020 at 22:49:03 +0200, J.-J. wrote: |> Le mardi 13 octobre 2020 à 14:41 +0200, Johann Höchtl a écrit : |>> * What would be a good starting point (tutorial) into troff and its |>> core principles?

Re: Learning troff - where to start?

Morten Bo Johansen wrote in : |On 2020-10-14 Peter Schaffter wrote: | |> What difficulties do you have entering UTF8 directly into the |> source? I've produced groff documents in most of the Western |> European and Scandinavian languages | |I thought we Scandinavians were also considered p

Re: [bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints

|Steffen has withdrawn most/all of his other patches and even after reading I do not know what this has to do with this bug. |this report a few times I'm not clear on what exactly the problem is supposed |to be. | |The "solution", "drop gnulib", is not likely, especially not during an RC |c

Re: [groff] 01/08: mdoc: Accept mixed-case section headings.

Hello, and sorry for the late reply. G. Branden Robinson wrote in <20201101035740.2azpyoxgyrd6ozdl@localhost.localdomain>: |Hi, Steffen. Coming back to an old item of business. | |At 2020-09-29T19:12:00+1000, G. Branden Robinson wrote: |> At 2020-09-28T22:57:37+0200, Steffen Nurpm

Re: [bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints

G. Branden Robinson wrote in <20201101042024.gfw4dqth3qlfxxw2@localhost.localdomain>: |At 2020-10-21T15:18:29+0200, Steffen Nurpmeso wrote: |>> Steffen has withdrawn most/all of his other patches and even after |>> reading |> |> I do not know what this has to do

Re: Unable to get GROFF_ENCODING to seep through to sourced subfiles

Dorai Sitaram wrote in <1129728531.3387046.1604937518...@mail.yahoo.com>: |I have GROFF_ENCODING set to utf8, but this only works for the main \ |file processed by groff, not to any subfiles that are sourced via .so . |Giving the -s option to groff to force a soelim doesn't work either.   |Add

Re: [DRAFT] Revised groff ms manual for review

Tadziu Hoffmann wrote in <20201108120208.gd2...@usm.uni-muenchen.de>: | |> When you say points are '(about 1/72")', it probably |> doesn't hurt to go the extra mile (!) in precision and |> say '(1/72.27")'. It's shorter (no need for 'about') |> and more correct. | |Historically, the size of

Re: pdfmark not working

Timothy Groves wrote in : |Any attempt to use the pdfmark macro package causes exactly nothing to |happen - no error messages, but also no metadata being added to my PDF.  |I've followed the instructions that come with pdfmark slavishly, |including testing in the most minimal document human

Re: How to make groff use local timezone?

Colin Watson wrote in <20201214154336.ga32...@riva.ucam.org>: |On Mon, Dec 14, 2020 at 02:12:28PM +1100, G. Branden Robinson wrote: |> At 2020-12-12T21:19:38-0800, Jim Avera wrote: |>> I suspect groff is always in UTC (but haven't confirmed).   |> |> No, that is not true, at least not in gro

Re: Question about Unicode Greek

Hello. Robert Goulding wrote in : |I've been away from groff for a long time; I think the last time I used it, |there was no Unicode support at all. Now I'm interested in using it as a |filter from markdown, through pandoc to groff to pdf. | |This is working well for me, except for a handful

Re: man-intro

Ulrich Lauther wrote in <20210522214249.GA20730@starlite>: |On Sat, May 22, 2021 at 08:18:41PM +0200, Oliver Corff wrote: |> |> "man cd", on the other hand, opens the bash built-in command *man page*, |> which, at least on my system is a plethora of text to read (and digest). |> |on my syt

Re: getting more out of man pages with less(1)

Hello. |> Good idea. I've further changed the Subject: to reflect the flow of the |> discussion. ... |> I also wonder if the pager wars are basically over and less(1) won them. | |That's certainly what I thought... .. Ever since less(1) started supporting OSC 8 "Hyperlinks in Terminal Emu

Re: getting more out of man pages with less(1)

Steffen Nurpmeso wrote in <20210523212903.58vrh%stef...@sdaoden.eu>: |Good evening and Hello. And thanks to Mario Blättermann, replying to the mail unrevealed a bug that is present in the MUA i maintain since at least 2003 (nail 10.05)! A nice Monday i wish. (And happy 80th birthda

Re: getting more out of man pages with less(1)

Good evening and Hello. Steffen Nurpmeso wrote in <20210523004836.gta8l%stef...@sdaoden.eu>: ... ||> Good idea. I've further changed the Subject: to reflect the flow of the ||> discussion. | ... ||> I also wonder if the pager wars are basically over and less(1) won

Re: getting more out of man pages with less(1)

Hey. Steffen Nurpmeso wrote in <20210523212903.58vrh%stef...@sdaoden.eu>: |Steffen Nurpmeso wrote in | <20210523004836.gta8l%stef...@sdaoden.eu>: | ... |||> Good idea. I've further changed the Subject: to reflect the flow \ |||> of the |||> discussion. || ...

Re: WAYTO: indexed man pages

Ingo Schwarze wrote in <20210602223746.ga92...@athene.usta.de>: ... |Then again, i feel that's a problem of relatively little urgency. That is because you use that mutilated less. The original can. --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he c

Re: Find a char in string

Wim Stockman wrote in : |Is there a function in groff to find the position of a char in a string. |So I can split a string into more than one. |I found the substring function that can cut based on length. If I could my |marker in the string I could cut it there. Loop over the string and use s

Re: [Groff] cvs(1) cannot be accessed (with old clients?)

Werner LEMBERG wrote: |> i couldn't update my repo: |> |> AuthReply: cvs: unrecognized option '--allow-root-regexp=^/srv/cvs/sourc\ | es/.*$' |> |> What can be done about that? | |I suspect a temporary problem. Yes, it works again -- thank you! |Werner --steffen

[Groff] Tiny make patch: avoid Netpbm dependency

Hello, for me the dependency upon Netpbm is "annoying"; i always restart failed makes to get over all related problems: like that (single-threaded) compilation is just fine. Configuration checks for (some) Netpbm programs and avoids $make_html as necessary -- however, xpmtoppm(1), pnmdepth(1) and

Re: [Groff] Tiny make patch: avoid Netpbm dependency

Hello, Werner LEMBERG wrote: |> for me the dependency upon Netpbm is "annoying"; i always restart |> failed makes to get over all related problems: like that |> (single-threaded) compilation is just fine. | |With the distributed tarballs, there is *no* dependency on Netpbm! This may be so,

Re: [Groff] Tiny make patch: avoid Netpbm dependency

Werner LEMBERG wrote: |> ...and no chance to take advantage of git(1) compressing it's |> blobs, which is what i was indeed referring to? The bitmap seems |> to be unchanged from the first check-in until today (and i can't |> imagine that someone wants to change that one, too). | |It is a v

Re: [Groff] Tiny make patch: avoid Netpbm dependency

Werner LEMBERG wrote: |>|installed to build the info files, or `autoconf' to generate the |>|configure script. People who check out from the git *must* have |>|all |> |> Hah! I was really thankful that the generated `configure' became |> part of the git(1) repo -- *thank you* for this de

Re: [Groff] Tiny make patch: avoid Netpbm dependency

Peter Schaffter wrote: |On Wed, Mar 12, 2014, Werner Lemberg wrote: |>> Would it make sense to send a patch that does this if at the end of |>> all the conditions there is still no `gnu.eps'? |> |> No, thanks. Instead, you might contribute a patch to implement a |> `--without-doc' configur

Re: [Groff] Tiny make patch: avoid Netpbm dependency

Hello Ingo, Ingo Schwarze wrote: |Hi, | |Steffen Nurpmeso wrote on Wed, Mar 12, 2014 at 08:59:29PM +0100: |> Werner LEMBERG wrote: | |>> Instead, you might contribute a patch to implement a |>> `--without-doc' configure switch that completely disables the |>> g

Re: [Groff] Tiny make patch: avoid Netpbm dependency

Hello Ralph, Ralph Corderoy wrote: |Hi Steffen, | |>> It is a very good principle to put only real source files into a git |>> repository, and no generated files. I will continue so. My |>> successor might make a different decision, though. |> |> Sure, that is your decision. | |It's a

Re: [Groff] Tiny make patch: avoid Netpbm dependency

hey, Ralph Corderoy wrote: |Hi Steffen, | |> Then `configure' only needs to change when something changes, like |> adding perl(1) detection or similar. | |It can also change due to different versions of autoconf being used by |developers; the same functionality represented by differing ex

[Groff] Add --with-doc configuration option

Hello, well ok, i think i have something that i could post (after some more checking, i.e., tomorrow). What would you say about an additional --with-examples? We could solely skip PDF_PROGRAMS if neiter is desired, then. And how fully blown do you actually want it: should a `make dist' fail and co

Re: [Groff] Add --with-doc configuration option

Nice saturday, Peter Schaffter wrote: |On Fri, Mar 14, 2014, Steffen Nurpmeso wrote: |> well ok, i think i have something that i could post (after some |> more checking, i.e., tomorrow). |> What would you say about an additional --with-examples? | |What would be the point? P

Re: [Groff] Add --with-doc configuration option

Keith Marshall wrote: |On 14/03/14 20:04, Peter Schaffter wrote: |> Can't imagine a situation where 'make dist' would want to exclude |> documentation. Assume nothing. :) | |Since the intended purpose of "make dist" is to create distribution |tarballs, such as those published on FSF mirror

Re: [Groff] Mission statement

Pierre-Jean wrote: |And why not mentionning heirloom implementation ? Isn't it |an important reference for anyone wishing to work on these |features ? I think Werner Lemberg also mentioned a clean and nicely scalable object based implementation in that thread. That GNU Troff has. --steffen

Re: [Groff] Add --with-doc configuration option

.. i've taken keithmarshall@ off Cc:, my mail-provider cannot deliver to this address Werner LEMBERG wrote: |> IMO, "--without-doc" should not apply to the "make dist" goal. | |Yep. | |> I also think having a check here and there is not a bad thing. I'll |> add it for my patch. | |

Re: [Groff] Add --with-doc configuration option

I wrote.. |find below something that adds the mentioned options and also |tweaks the make system a bit -- 'make install' and 'make |uninstall' seem to work again after the patch series is applied. |There are still problems ('make install' with DESTDIR set results |in some errors along the way,

Re: [Groff] Add --with-doc configuration option

Heya, Ralph, Ralph Corderoy wrote: |Hi Steffen, | |> That is, tr(1) is buggy | |tr(1) seems to be behaving as I'd expect. The \n is a control character oh yes, compilation on CRUX-3 Linux succeeds without any problems, the font listing is worked from top to bottom. Now the only problem th

Re: [Groff] Add --with-doc configuration option

Peter Schaffter wrote: |On Wed, Mar 19, 2014, Werner Lemberg wrote: |>> I can't spot any problems with Steffen's 'touch gnu.eps' proposal to |>> prevent build failure in the absence of the netpbm tools. Werner? |> |> Well, this *only* happens if you do a build from the git repository; |> f

Re: [Groff] Add --with-doc configuration option

Hello Werner, Werner LEMBERG wrote: |> But the FSFology will not make me sign something that is not legal, |> which is admitted by even the FSFE itself [...] | |Well, it would probably have no influence to the jurisdiction in |Germany, but it would have a value for the FSF in the US... Yes

Re: [Groff] [groff] 04/09: Fixes for `uninstall' target.

Well then hello, Keith Marshall wrote: |On 30/03/14 21:13, Werner LEMBERG wrote: |> Fixes for `uninstall' target. |> |> * Makefile.in (uninstall_dirs): Use `DESTDIR'. | |A couple of minor concerns here: [.] |2) Does DESTDIR have any real value, for an uninstall target? Its v

Re: [Groff] Formatting algorithm

Peter Schaffter wrote: |BTW--does anyone know how KP/TeX handles paragraphs with "spread" |(.brp) lines? \def\@fillbr{\ifvmode\else\unskip\hfill\penalty-1\fi\relax}% \def\@nofillbr{\ifvmode\else\penalty-1\fi\relax}% % ('\\' is redefined in some envs) \let\\\@fillbr% \def\br{\\

[Groff] A followup on the Makefile cleanup

Hello, i would have a followup which removes the GNULib dependency off groff. I've sent it to Werner a month ago but i think that is not his direction, yet i want to at least mention it on the list. The problem: i think currently groff makes false use of wcwidth(3): if it finds the `unicode' pro

Re: [Groff] A followup on the Makefile cleanup

Werner LEMBERG wrote: |> i would have a followup which removes the GNULib dependency off |> groff. I've sent it to Werner a month ago but i think that is not |> his direction, yet i want to at least mention it on the list. [...] | |Ah, I forgot to respond, sorry. Please file a bug report a

Re: [Groff] Formatting algorithm, an experiment

Hello Ralph, Ralph Corderoy wrote: |Hi Peter, | |>> http://lists.gnu.org/archive/html/groff/2014-06/bin14bGZPiUPU.bin |>> which |> |> The .bin extension issue for attachments in archived email has come up |> before. Does anyone know why lists.gnu.org is doing this and whether |> there'd

Re: [Groff] Formatting algorithm, an experiment

Hello Ralph, Ralph Corderoy wrote: |Hi Steffen, | |>> The closest is |>> http://www.iana.org/assignments/media-types/application/gzip which |>> leaves the tar for the user to fathom out if left to MIME types |>> alone. |> |> [http://svn.apache.org/viewvc/tika/trunk/tika-core/src/ma\ |> i

Re: [Groff] Formatting algorithm, an experiment

Hello Ulrich, Ulrich Lauther wrote: |On Fri, Jun 27, 2014 at 03:43:24PM +0200, Steffen Nurpmeso wrote: |> Oh, after fiddling with unsupported linker options etc. to compile |> the showcase i got a SIGBUS. You know, as in "Bus stop, wet day, |> she's there" etc. On

[Groff] Invalid HTML on groff website

Stumbled over during finding the ultimative underline mail-archive entry, why did i look at the source?, but indeed [1] at least embeds a in a , has a useless and keeps a open over boundaries. Just in case noone noticed it yet. Still looks pretty pretty nonetheless and imho. [1]

Re: [Groff] Compression support for files?

~2002 i'd rather wonder if anyone can; waiting on multiple objects seems to be your daily bread)! --steffen --- Begin Message --- Not directly related to subject, but (in an attached diff) ... On 16/07/14 17:53, Steffen Nurpmeso wrote: > -# not all make programs have $(RM) predefined

Re: [Groff] Compression support for files?

dback for you, and if you do get feedback, |it is likely do be unrelated and the discussion is likely |to get derailed, as you see here... I'm sorry for the inconvience! It was thought like this (in S-nail(1)) ?0[ +track]? f >N 111 Steffen Nurpmeso 18:53 07-16 2181/ 65381 [Groff

Re: [Groff] Compression support for files?

Hello Werner, Werner LEMBERG wrote: |Hello Steffen! | |> It effectively adds compression support for (practically) *all* |> files that groff uses during a run. | |Similar to others on the list I'm not really enthused about this |feature. Your idea of wrapping all possible file access meth

Re: [Groff] Compression support for files?

Hello Ralph, Ralph Corderoy wrote: |Hi Steffen, | |> The original intent of Matthew Dillon i think was to be able to |> blindly use the `.so' request and make it work regardless of wether |> whatever file is compressed or not. | |You dislike .pso because your run in `safer' mode? yes and

Re: [Groff] Compression support for files?

Werner LEMBERG wrote: |May I suggest to discuss your future changes on this list in advance? |This helps everyone in understanding your plans, and probably saves |you from needless coding. I will cleanup my local commits and make the decompressor-search an optional flag to searchpath; it is no

Re: [Groff] Compression support for files?

Huhu Keith, Keith Marshall wrote: |On 17/07/14 12:13, Steffen Nurpmeso wrote: |> Keith Marshall wrote: |>|I consider this to be a regression. |> |> The last Windows i've seen anything of other than the browser |> window in an Internet Café was 95B (with Plus pac

Re: [Groff] Compression support for files?

Good morning, Clarke Echols wrote: |In 1985, disk space was very expensive. HP sold a 400 Mbyte hard |drive that consumed 600 watts of power to operate for US$ 38,000 |each. [.] |Today, you can buy a 1000 Gbyte hard drive in a local retail store |for under $100. That is 10 cents per gigab

Re: [Groff] Compression support for files?

Good morning, (Ted Harding) wrote: [.] |As far as Unix/Linux are concerned, their beauty, simplicitly |and reliability, and above all their flexibility, depend on |the fact that different aspects of a program's functionality |for a specific purpose are delegated to components of the |progra

Re: [Groff] Compression support for files?

Keith Marshall wrote: |On 17/07/14 21:05, Steffen Nurpmeso wrote: |> Not with GNU make. | |Huh? Now you've utterly destroyed any chance you may have had of |gaining my confidence ... Sorry, that was a Freudian error of mine. Of course i meant GNU troff (and even before the

Re: [Groff] Compression support for files?

Hallo Ingo, Ingo Schwarze wrote: [.] |Unfortunately, your example is broken in multiple ways and can |hardly be amended to make it work, so it doesn't demonstrate True. (But what i did for testing was ?0[]$ groff -mdoc -Tutf8 xwhat.1 2>/dev/null and it works -- in fact i've chosen what.

Re: [Groff] Compression support for files?

Clarke Echols wrote: |There is no possible justification for compressing font files or any |other files related to nroff/groff/troff in today's environment, unless |they are being delivered online over the Internet as compressed HTML |or some other equivalent. | |Groff is fast, efficient, an

Re: [Groff] Inputfile_caseencapsulation --with-unpack (and --with-zlib) support

First: someone messed up the subject when reencoding the message, the correct one would have been Input file_case encapsulation --with-unpack (and --with-zlib) support Sorry. (Don't use Python.) I wrote: [.] | ea111b9 Add GROFF_UNPACK_CHECK m4++ / --with-unpack=XY (Public Domain) | |New

Re: [Groff] Inputfile_caseencapsulation --with-unpack (and --with-zlib) support

So for some more annoyance i'll also post the review tweaks. Brings some consistency and avoids a uselessly large buffer. Everything in the Public Domain, of course. Ciao, --steffen commit b3f543a09f987abacbd13b590cb6b5d1a342c650 Author: Steffen Nurpmeso Date: 2014-07-28 17:46:27

Re: [Groff] Inputfile_caseencapsulation --with-unpack (and --with-zlib) support

Hallo Werner, Werner LEMBERG wrote: |I don't have time to review this. I suggest that you open an |bugtracker issue and post a cleaned-up mbox file for further |inspection. You don't need to review but could just commit it, it is ok by itself. I.e., i would commit it. |It's really time th

Re: [Groff] Invalid HTML on groff website

Peter Schaffter wrote: |On Tue, Jul 08, 2014, Steffen Nurpmeso wrote: |> Stumbled over during finding the ultimative underline mail-archive |> entry, why did i look at the source?, but indeed [1] at least |> embeds a in a , has a useless and keeps a |> open over boundaries.

Re: [Groff] [groff] 01/01: gpinyin: new preprocessor for adding pinyin parts, the European-style Chinese writing

Hello Bernd, Bernd Warken wrote: |bwarken pushed a commit to branch master |in repository groff. | |commit b46f950a45b084518020637287471fbd11516533 |Author: Bernd Warken |Date: Fri Aug 1 22:01:45 2014 +0200 | |gpinyin: new preprocessor for adding pinyin parts, the European-style \

Re: [Groff] [groff] 01/01: gpinyin: new preprocessor for adding pinyin parts, the European-style Chinese writing

"Bernd Warken" wrote: |>|Author: Bernd Warken |>|+can be used in order to let all fowllowing arguments mean file names, |> typo ^^ | |Thanx. This is just a preversion, it cannot really be used so far. I for one don't understand why i introduce so many

Re: [Groff] [OT] Patches for AT&T DWB and Heirloom troff

|Heirloom troff: | |The Sourceforge version compiles on usual UNIX systems (but \ |also with lots of shift/reduce errors) and also works as expected--except \ |on OpenBSD. There the binary crashes with 90% probability. \ | Posts can be found about this issue but no solution for it. \ | I ha

Re: [Groff] [OT] Patches for AT&T DWB and Heirloom troff

Carsten Kunze wrote: |> Indeed, it is not 64-bit safe (as in, returning pointer values in |> an `int' etc.). | |The Heirloom troff bug is not a 64-bit problem. An uninitialized \ I don't understand why you talk in singular. A dauntlessness comparable to that of the Pirates in the Carribean.

Re: [Groff] Automake migration proposal

well, hello nonetheless, Werner LEMBERG wrote: |> Do you need any additional help in testing this? |A major test would be the OS X platform, since it tends to have (a) |missing a lot of functionality, and (b) use LLVM, not gcc, as the |compiler. There should be a note that on Snow Leopard y

Re: [Groff] Inputfile_caseencapsulation --with-unpack (and --with-zlib) support

Vaibhaw Pandey wrote: |Steffen, | |I took a shot at reviewing this last week. Turned out I don't have enough |context of the groff code base to be able to do a useful review. I am |currently familiarizing myself with the parts of code to which this review |is pertinent. However, given my cur

Re: [Groff] UTF-8/Unicode Implementation, Paragraph-at-once Formatting and Right to Left Text

Hello Ali! Ali Gholami Rudi wrote: |Hello, | |Carsten Kunze wrote: |>> Just wanted to bring this to the attention of the list. |>> |>> Neatroff - a C implementation of Troff. |> Not really new news: http://lists.gnu.org/archive/html/gr\ |> off/2013-07/msg1.html | |I recently modif

<    1   2   3   4   >