Hi Jim,
On Sat, Aug 12, 2023 at 03:48:21PM -0500, Jim Hall wrote:
> Hi everyone!
>
> I was thinking about writing a few articles for Technically We Write
> about fonts in groff. But I thought "This would be a great article for
> someone else to write" so I wanted to suggest it here.
>
> Here are
Hi everyone,
Recently I found some groff manual written in Spanish (standalone, not a
translation of the groff manual in English) the author had the idea of
generating a list of words with the .hw request with a script. I tried
this method and I got a better hyphenation than reading the patterns
On Wed, Aug 16, 2023 at 06:13:03PM +0200, Walter Alejandro Iglesias wrote:
> About your second point, I recently wrote this:
>
> http://en.roquesor.com/groff.html
If anyone tried the script I share in the web page of the link, perhaps
noticed that the "Usage" (it'
Dear groff users and developers,
I normally use OpenBSD in my desktop, which still comes with groff
1.22.4. Today I booted an old laptop with Debian testing (Devuan to be
more precise) and, after updating it, I could finally test groff 1.23.
Lately, as I mentioned in this same list months ago, i
On Mon, Sep 11, 2023 at 07:18:59PM +0200, Walter Alejandro Iglesias wrote:
> Dear groff users and developers,
>
> I normally use OpenBSD in my desktop, which still comes with groff
> 1.22.4. Today I booted an old laptop with Debian testing (Devuan to be
> more precise) and, after
Hi Branden,
On Mon, Sep 11, 2023 at 03:33:03PM -0500, G. Branden Robinson wrote:
> This suggests to me that preconv(1) _must_ be run before you try to
> process your documents with this technique.
> [...]
> Please share input file(s) that reproduce the problem, and a command
> line that produces
On Wed, Oct 04, 2023 at 01:49:49AM -0500, Dave Kemper wrote:
> On 9/12/23, Walter Alejandro Iglesias wrote:
> > This last command throws no error, that's because soelim(1) allows
> > preconv(1) to process the list.tr file.
>
> Walter,
>
> There's a proposal
On Wed, Oct 04, 2023 at 10:20:57PM +, Bjarni Ingi Gislason wrote:
> Latin1 iacute has the utf8 code 'Ã'
> and the hexadecimal code is C3AD which is "LATIN CAPITAL LETTER A WITH
> TILDE" and "SOFT HYPHEN"
>
> "groff" turns "soft hyphen" into "HYPHEN-MINUS" (0x2D)
>
> More is in the attachme
On Thu, Oct 05, 2023 at 10:08:50AM +0200, Walter Alejandro Iglesias wrote:
> On Wed, Oct 04, 2023 at 10:20:57PM +, Bjarni Ingi Gislason wrote:
> > Latin1 iacute has the utf8 code 'Ã'
> > and the hexadecimal code is C3AD which is "LATIN CAPITAL LETTER A WI
On Wed, Oct 25, 2023 at 05:03:36AM -0500, G. Branden Robinson wrote:
> Hi Walter & Dave,
>
> At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote:
> > If instead of sourcing hyphen.tr from my macros with .mso I source it
> > directly from the roff document with
On Wed, Oct 25, 2023 at 07:58:37AM -0500, G. Branden Robinson wrote:
> Hi Walter,
>
> At 2023-10-25T14:25:42+0200, Walter Alejandro Iglesias wrote:
> > > This transcript isn't as useful as it could be, because it didn't
> > > disclose to me what character
On Thu, Oct 26, 2023 at 09:35:07AM -0500, G. Branden Robinson wrote:
> At 2023-10-25T16:20:27+0200, Walter Alejandro Iglesias wrote:
> > What you did above is not the step by step way I posted to reproduce
> > the bug. Of course it won't be helpful if you overlook it.
>
an))
> id 1AlnuQ-0007hv-00
> for ; Wed, 02 Dec 2009 22:30:08 +0100
> X-Injected-Via-Gmane: http://gmane.org/
> To: help-gr...@gnu.org
> From: Walter Alejandro Iglesias
> Subject: widow lines and footnotes
> Date: Wed, 02 Dec 2009 22:18:51 +0100
> Lines: 15
On Thu, Dec 03, 2009 at 06:13:00AM +0100, Werner LEMBERG wrote:
>
> > What's wrong? Are groff@gnu.org and help-gr...@gnu.org in different
> > servers?
>
> help-gr...@gnu.org simply doesn't exist -- I can't remember that it
> has ever existed. Using google I've found three links, however, the
>
On Thu, Dec 03, 2009 at 10:38:08AM +0100, Patrik Schindler wrote:
>
> Am 03.12.2009 um 10:19 schrieb Walter Alejandro Iglesias:
>
> >2) Is it too difficult to write my own macros for footnotes?
>
>
> Don't know but I won't bother reinventing the wheel. Ther
On Thu, Dec 03, 2009 at 10:34:30AM -0500, Peter Schaffter wrote:
> On December 3, 2009 04:19:47 am Walter Alejandro Iglesias wrote:
> > 2) Is it too difficult to write my own macros for footnotes?
>
> If you're new to groff, I'd suggest getting comfortable with
>
Hello
Some of you seems to be Unix veterans. I bought my first computer in
2005. Before this date I did not know how to power on it :).
But I am forty two years old and I know something about other things
and I am able to draw an analogy.
In several occasions, I've attempted to show my point o
Hello all,
Searching for how implement crop marks with groff I've found this:
http://article.gmane.org/gmane.comp.printing.groff.general/7804
That do the job but I am a bit lost with the code. I couldn't find
documentation on internet to understand it and be able to modify it to fit the
A4 pape
On Thu, Nov 28, 2013 at 02:46:52PM +0100, Steffen Daode Nurpmeso wrote:
> The foldmark painter itself.
> All it effectively does is to move absolutely and paint two
> horizontal lines at precalculated positions; using different
> absolute .sp in combination with several \D''s should do what you
> d
On Fri, Jan 31, 2014 at 08:06:11PM -0500, Peter Schaffter wrote:
> On Wed, Jan 29, 2014, Werner Lemberg wrote:
>> Given today's memory abundance and the high velocity of CPUs, the
>> ideal route would be to implement a document-wide algorithm for
>> typesetting a document (in contrast to TeX's page
On Tue, Feb 04, 2014 at 11:32:00AM -0500, Peter Schaffter wrote:
> On Tue, Feb 04, 2014, Dave Kemper wrote:
>> I understand the need for backwards compatibility, but I more and more
>> find myself wishing groff had a global option to choose between "follow
>> historical usage" and "be sane." For s
On Tue, Feb 04, 2014 at 09:42:05PM -0500, James K. Lowden wrote:
> On Tue, 4 Feb 2014 15:43:11 -0500
> "Eric S. Raymond" wrote:
>
>> I have to say, unfortunately, that I think the entire
>> presentation-centric model within which groff lives just about run
>> its course. The future belongs to str
ain as useful and valuable as ever. The only
> thing that might be lost is the time it would take to write a Perl
> script to parse and update said documents to reflect probably very
> minor changes to groff's behaviour.
>
> Furthermore, let's not forget that under Werner&#
I have more to say.
I'm an immigrant. After burying my family and my country I came alone to
Europe 13 years ago with my skin and money enough to survive two weeks. After
twenty years like a professional cellist I leave the music. Do you still think
that I could be afraid of changes?
Groff alr
On Tue, Feb 25, 2014 at 11:06:09AM -0500, Eric S. Raymond wrote:
> Now let us imaging adding two primitives to groff:
>
> 1. Declare hygienic. Takes a request or macro name, sets a 'hygienic'
> bit on it.
>
> 2. Enable hygienic node. After this point, all explicit requests without
> their hygieni
On Tue, Feb 25, 2014 at 01:24:15PM -0500, Eric S. Raymond wrote:
> Walter Alejandro Iglesias :
>> Assuming you have not enough time to do it yourself, what I would do
>> in your place is to pay someone to write the html of your site and
>> replace DocBook with PHP scripting
On Wed, Feb 26, 2014 at 12:00:53PM +, Deri James wrote:
> On Wed 26 Feb 2014 11:46:32 Ralph Corderoy wrote:
>> Hi jkl,
>>
man pages don't really need expressive typography.
>>>
>>> Man pages are constrained by xterm. A better display system would
>>> invite tables, graphs, equations, and
On Wed, Feb 26, 2014 at 01:19:14PM +, Ralph Corderoy wrote:
> Hi Walter,
>
>> Man pages are not tutorials or complete manuals
>
> Yes they are, or should be. They used to be. I learnt Perl 4 from
> perl(1). Back then it was a single long man page, well-written by an
> experienced Unix hand,
On Wed, Feb 26, 2014 at 10:55:31PM -0500, James K. Lowden wrote:
> On Wed, 26 Feb 2014 11:46:32 +
> Ralph Corderoy wrote:
>
man pages don't really need expressive typography.
>>>
>>> Man pages are constrained by xterm. A better display system would
>>> invite tables, graphs, equations, a
> 1. In the sixties and seventies, computing was largely
> experimental. There were no penalties for trying
> something different.
It's the natural evolution of everything. In the beginning trying
different approaches is sane and has sense.
But to make a graphical version of what is al
On Fri, Feb 28, 2014 at 12:15:35PM -0500, Eric S. Raymond wrote:
> You will be pleased to hear, then, that RMS and I have been
> discussing specifics of how and when to shoot this bad idea
> through the head.
>
> Where we're probably going is that (a) info will die, to be replaced
> by HTML browsed
Some months ago this list was quiet as usual. Suddenly Mr Eric
Raymond appeared kindly offering himself to migrate Groff to git. At
the same time two guys started to make strange proposals and Eric to
flatter one of them and calling him the new project leader. Now
surprise, surprise that strange
I respect the idea of a tribal society and I'm aware that FOSS needs
it. Being myself a standalone savage creature, I'm aware I am not
able to participate in this structure more than giving some opinion.
Do you really want a modern approach?
Man Pages
OSs should include just plain ASCII Englis
Hello everyone,
I've been using groff to format my novels since years. Lately I wrote
my own version of fmt with some feature added to format troff files (in
the head comment of the code I explain its features in more detail.) I
decided to share it here, perhaps some of you find it useful:
ht
Hi John,
On Feb 17 2023, John Gardner wrote:
> >
> > https://en.roquesor.com/Downloads/fmtroff.c
> >
>
> Missed opportunity to call it "roffmt". ;-)
I didn't realize! My code is even less elegant than the name I chose. :-)
You can still do this:
$ cc fmtroff.c -o $HOME/bin/roffmt
>
> Anyway
On Feb 17 2023, Walter Alejandro Iglesias wrote:
> Hi John,
>
> On Feb 17 2023, John Gardner wrote:
> > >
> > > https://en.roquesor.com/Downloads/fmtroff.c
> > >
> >
> > Missed opportunity to call it "roffmt". ;-)
>
> I did
On Sat, Jul 27, 2024 at 08:51:32AM +0200, Gáspár Gergő wrote:
> Hi,
>
> I'm trying to make justified text look nicer, so I turned to hyphenation.
> Hungarian is not supported out of the box by groff, but I found a tex patterns
> file which seems quite good, that is what I tried to use, to not muc
On Thu, Sep 26, 2024 at 06:48:13PM +0200, Walter Alejandro Iglesias wrote:
> Some may find it strange that I have associated the 'ñ' with the 'p' and
> not with the 'n'. Well, in Spanish there are cases in which the 'ñ' is
> not treated as an &#x
On Fri, Feb 07, 2025 at 08:33:20PM +0100, onf wrote:
> Hi Walter,
>
> On Fri Feb 7, 2025 at 7:46 PM CET, Walter Alejandro Iglesias wrote:
> > [...]
> > Titles and subtitles (I'm referring to those in the body of the
> > document, not those in the header and fo
Hello guys,
There is something I can't figure out how to do it.
Titles and subtitles (I'm referring to those in the body of the
document, not those in the header and footer) look better when they have
more space above than below. I've recently been studying how to achieve
this without altering t
Happy New Year to everyone.
I have a question. Surely it's something silly that I'm missing. I
don't understand the logic in how centering (with .ad c or .ce) affects
horizontal movements (\h). Let's take this example:
.ad c
v
.br
\Z'\h'1i'v'
.br
\Z'\h'1i'Hello, World!'
.br
\h'1i'v
.br
\h'1i'H
On Sat, Jan 18, 2025 at 03:10:28PM +0100, onf wrote:
[...]
> TL;DR: When centering, horizontal motions become part of the line and
>centered with it.
This is what I didn't understand. Thank you for your detailed
explanation! (Don't get me wrong, I cut off the rest of your
explanation so
Hello list,
I've been using groff for years, but mostly solving problems as they
came up. Lately I decided to study the documentation more deeply, the
last thing I did was learn how to use diversions. After a week of
struggling, I got the code below, it's to automatically get rid of the
last lin
On Sat, Jan 18, 2025 at 08:17:11PM +0100, onf wrote:
> On Sat Jan 18, 2025 at 8:09 PM CET, onf wrote:
> > [...]
> > > \Z'123456789'
> > > .rj
> > > 123456789
> >
> > $ groff -Tutf8 | sed "s/ /'/g"
> > 123456789
> > '''123456789
> >
> > Huh. I ge
On Sat, Jan 18, 2025 at 08:09:56PM +0100, onf wrote:
> By the way, the way gpic does it is by emitting PostScript instructions
> to the grops postprocessor. See gropdf(1):
> gropdf understands some of the device control commands supported by
> grops(1).
>
> \X'ps: exec gsave currentpoint 2 c
On Tue, Jan 28, 2025 at 10:40:36PM +0100, onf wrote:
> Hi Walter,
>
> On Tue Jan 28, 2025 at 9:02 PM CET, Walter Alejandro Iglesias wrote:
> > [...] After a week of
> > struggling, I got the code below, it's to automatically get rid of the
> > last line of the last
On Sat, Feb 08, 2025 at 08:37:58PM +0100, onf wrote:
> I understand your use case, but it still seems simpler to me to use
> sp over strings. You could define registers which specify the ratio
> between the top and bottom space, so that instead of 1v:1v it becomes
> e.g. 0.4v:0.6v. Obviously the ra
47 matches
Mail list logo
