Hi onf,
At 2024-11-12T16:43:56+0100, onf wrote:
> On Tue Nov 5, 2024 at 8:15 PM CET, onf wrote:
> > as the title says. If I use UTF-8 via preconv and request
> > .hy 2
> > .hpf hyphen.cs
> > will that work, given that the file is using the Latin-2 encoding
> > for characters with diacritics? I
Hi Branden,
On Wed Nov 13, 2024 at 4:36 PM CET, G. Branden Robinson wrote:
> [...]
> > Latin1 characters continue working even when loading Latin2 as long as
> > they are specified as the respective UTF-8 codes.
>
> And they _should_ continue to hyphenate at appropriate locations because
> s set o
Hi onf,
At 2024-11-13T18:22:43+0100, onf wrote:
> On Wed Nov 13, 2024 at 4:36 PM CET, G. Branden Robinson wrote:
> > [...]
> > > Latin1 characters continue working even when loading Latin2 as
> > > long as they are specified as the respective UTF-8 codes.
> >
> > And they _should_ continue to hyph
Dear All,
Recently I started using groff for writing business letters. In my
particular case, I experimented with the macro package me following the
example letter I found in the documentationm, but my question is not
linked to the choice of any particular macro package.
In me, adding a footer w
Hi onf,
At 2024-11-13T20:42:57+0100, onf wrote:
> On Wed Nov 13, 2024 at 7:25 PM CET, G. Branden Robinson wrote:
> > [...]
> > > i.e. translation should happen on output, not on input,
> >
> > I'm not sure I agree with that, given the above. When I see `tr` used,
> > it is typically to make input
Hi Branden,
On Wed Nov 13, 2024 at 7:25 PM CET, G. Branden Robinson wrote:
> [...]
> > i.e. translation should happen on output, not on input,
>
> I'm not sure I agree with that, given the above. When I see `tr` used,
> it is typically to make input more convenient.
I never said it's not used li
At 2024-11-13T16:25:58-0600, G. Branden Robinson wrote:
> Here's a solution using mm(7). Seems okay, can't say that it's "best".
No, it's bad. Where's the writer's address, date, inside address, and
salutation?
Another day, another mm bug.
"Branden, you've made too many changes to mm and broke
On Wed Nov 13, 2024 at 11:11 PM CET, onf wrote:
> A complete example might look like this:
> .ev FOOTER \" configure new environment FOOTER:
> . evc 0 \" copy default environment's properties
> .ev
> .de FOOTER \" define footer
> . ev FOOTER \" switch to environment FOOTER
> . sp
Hi Branden,
On Wed Nov 13, 2024 at 9:48 PM CET, G. Branden Robinson wrote:
> At 2024-11-13T20:42:57+0100, onf wrote:
> > [...]
> > I never said it's not used like that. I just meant to say that groff(7)
> > suggests the translation happens at the moment the character is
> > formatted for output ra
[self-follow-up]
Corrections:
At 2024-11-13T14:48:58-0600, G. Branden Robinson wrote:
> I agree. Alas, the CSRG seems to have thought of hyphenation as a
s/CSRG/CSRC/
> one-time, set-and-forget configuration parameter. There wasn't even a
> way in the AT&T troff language for a document to inq
Hi Oliver,
On Wed Nov 13, 2024 at 8:44 PM CET, Oliver Corff wrote:
> [...]
> In me, adding a footer with .fo 'arg left'arg center'arg right' works as
> expected, with the blatantly obvious limitation that the elements of the
> footer should not contain line breaks.
>
> However, I'd like to have in
Hi onf,
At 2024-11-13T23:45:59+0100, onf wrote:
> On Wed Nov 13, 2024 at 9:48 PM CET, G. Branden Robinson wrote:
> > I guess I interpret those words more generally than you do. To me,
> > "prior to output" can mean _any time_ prior to output (once the
> > formatter has started running), and you s
At 2024-11-13T20:44:23+0100, Oliver Corff via GNU roff typesetting system
discussion wrote:
> Recently I started using groff for writing business letters. In my
> particular case, I experimented with the macro package me following
> the example letter I found in the documentationm, but my question
13 matches
Mail list logo
