Re: [Groff] \o and \z do not work for -Tutf8

I was wrong. Dieresis is used in PinYin. The "Chinese for Beginners" (ISBN 7-5619-1117-3) I refer, also uses twice the size periods below the vowel to tag the accentuated syllable of a word. sorry Holger wrote (Thu, 7 Aug 2014 15:35:28 +0200): > > > [forward due to wrongly replied privatly

Re: [Groff] Git branching workflow (was: License for files with »ideal« parts)

Hello Bertrand, Bertrand Garrigues wrote: |On Tue, Sep 16 2014 at 11:19:41 AM, Steffen Nurpmeso \ |wrote: |> [1] |> |> Why does groff not take advantage of git(1) and introduce a second |> regular work branch? I think t

Re: [Groff] License for files with ?ideal? parts

> >Date: Tue, 16 Sep 2014 16:05:24 -0400 > >From: "James K. Lowden" >To: groff@gnu.org > >Subject: Re: [Groff] License for files with ?ideal? parts > >Message-ID: <20140916160524.8e7a9aa5.jklow...@schemamania.org> > >Content-Type: text/plain; charset=US-ASCII > > > >On Tue, 16 Sep 2014 18:42:23

[Groff] broken interaction between line numbering and diversions

.nm +1 Text before diversion. Text before diversion. Text before diversion. Text before diversion. Text before diversion. Text before diversion. Text before diversion. Text before diversion. .br .di my_diversion Diverted text. Diverted text. Diverted text. Diverted text. Diverted text. Diverted tex

Re: [Groff] broken interaction between line numbering and diversions

> The problem with the above input can be seen in either text or > PostScript output in groff 1.22.2. Using nroff, the output is I think you're using the diversion wrong. Diversions are meant for storing *formatted* text. If you're not replaying the diversion in no-fill mode (and you're not), y

Re: [Groff] broken interaction between line numbering and diversions

Dave Kemper wrote: > .nm +1 > Text before diversion. > Text before diversion. > Text before diversion. > Text before diversion. > Text before diversion. > Text before diversion. > Text before diversion. > Text before diversion. > .br > .di my_diversion > Diverted text. > Diverted text. > Diverted

Re: [Groff] broken interaction between line numbering and diversions

On 9/17/14, Tadziu Hoffmann wrote: > I think you're using the diversion wrong. This is, admittedly, an artificial example cooked up to illustrate the behavior. This is clearly a situation where a diversion, or even a macro, would be unnecessary at all. The question I'm posing is whether a user

Re: [Groff] broken interaction between line numbering and diversions

Dave Kemper wrote: > The question I'm posing is whether a user who uses a diversion in this > "wrong" (or, let's say, less than optimal) Wrong is the correct word here. > manner should see output > that is so clearly not what was intended, or whether the software > should do something intellige

Re: [Groff] Overview, Sept. 2014

On 9/9/14, Werner LEMBERG wrote: >> Out of that discussion came Doug's excellent suggestion for a new >> primitive, '.decor' or similarly named, that's extensible so various >> kinds of decoration can be applied to text, not just underlining >> (which, IMO, groff seriously needs). [...] > > Such

Re: [Groff] broken interaction between line numbering and diversions

> The question I'm posing is whether a user who uses a > diversion in this "wrong" (or, let's say, less than optimal) > manner should see output that is so clearly not what was > intended, or whether the software should do something > intelligent with the user's suboptimal input, producing > outpu

Re: [Groff] broken interaction between line numbering and diversions

Dave -- On Wed, Sep 17, 2014, Dave Kemper wrote: > On 9/17/14, Tadziu Hoffmann wrote: > > I think you're using the diversion wrong. > > This is, admittedly, an artificial example cooked up to illustrate the > behavior. This is clearly a situation where a diversion, or even a > macro, would be u

[Groff] PDFPIC macro

Attached is a proposal for a general use PDFPIC macro. It's modelled after and takes exactly the same arguments as PSPIC. Since there's no groff pdf equivalent to .psbb, an external program is used to get the image dimensions (pdfinfo(1) from the poppler-utils package). The alternative is to req

Re: [Groff] PDFPIC macro

> Von: "Peter Schaffter" > Attached is a proposal for a general use PDFPIC macro. It's > modelled after and takes exactly the same arguments as PSPIC. > > Since there's no groff pdf equivalent to .psbb, an external > program is used to get the image dimensions (pdfinfo(1) from the > poppler-uti

[Groff] nroff default hyphenation question

Hello, I have noticed that hyphenation in AT&T nroff (DWB, P9, P9P) and Solaris nroff seems to off by default, but it's on in groff and Heirloom. What is historically correct? CSTR54 says it is on by default (.hy 1). Does anyone know why the implementation differs? Carsten

Re: [Groff] PDFPIC macro

Hello, Peter Schaffter wrote: |Attached is a proposal for a general use PDFPIC macro. It's |modelled after and takes exactly the same arguments as PSPIC. |Comments and suggestions, please. I'm not in the position to say something to PDFPIC today (direct support would be pretty cool!), but t

Re: [Groff] PDFPIC macro

On Wed, Sep 17, 2014, Steffen Nurpmeso wrote: > I'm not in the position to say something to PDFPIC today (direct > support would be pretty cool!), but there should be general tools > for sh(1) (perl(1)...) that can be included in a defined way and > used. I.e., roff "libraries". > > And the very

Re: [Groff] PDFPIC macro

On 17/09/14 22:22, Peter Schaffter wrote: > On Wed, Sep 17, 2014, Steffen Nurpmeso wrote: >> I'm not in the position to say something to PDFPIC today (direct >> support would be pretty cool!), but there should be general tools >> for sh(1) (perl(1)...) that can be included in a defined way and >> u

Re: [Groff] PDFPIC macro

On 17/09/14 21:47, Steffen Nurpmeso wrote: > In general it is a pity that it is impossible to generate a complete > document with TOC, index etc. in "safe" mode. But this is way > off-topic. It may be off-topic, but FWIW, it is perfectly feasible to do all of the above entirely in safe mode, by

[Groff] mission statement source

Hi, Is it an oversight that the Mission Statement section of the project page (http://www.gnu.org/software/groff/#mission-statement) contains only two of the three groff source files needed to produce the formatted mission statement? Or was mission-statement-strings.mom intentionally omitted for

[Groff] Suggested patch to post-html.cpp

Hi, Attached for your review is a suggested patch to post-html.cpp. The motivation is that grohtml occasionally bungles the formatting of indented lists. Bug 30043 seems related, although that one is focused mainly on interactions with -mdoc. -ms is what I use for my day-to-day formatting.

Re: [Groff] broken interaction between line numbering and diversions

> When I opened a report in the bug tracker on this, Werner responded > that this is working as designed. I still think so. > While I understand the design of how diversions are implemented, and > why that implementation might produce these results, I contend that > this design is so poor as to