Hi Philip!
At 2020-10-14T02:43:36+, Philip Bushee wrote:
> I'm using Heirloom doctools on OpenBSD. I'm using the version on the
> ports system[1]. I'm trying to use the .CW macro to mark a text in
> typwriter font (courier). But it does not work.
> Using \f(CW works, however.
>
> Does .CW
Hi,
Damian McGuckin wrote on Wed, Oct 14, 2020 at 11:41:59AM +1100:
> On Wed, 14 Oct 2020, Greg 'groggy' Lehey wrote:
>> But that brings us back to where we came in: where is there
>> well-structured documentation for the current groff?
> Agreed. It is not there.
I wonder where this myth is co
Hi Federico,
Federico Lucifredi via wrote on Tue, Oct 13, 2020 at 08:04:10PM -0400:
> For man page writing, I collected the available resources in this
> blog post a while ago - happy to hear about new resources.
If you are curious about new resources, you could mention the
concept of semantic m
Dear Peter,
while I first thought a follow-up question would warrant a separate thread,
now as you mention mom, I feel comfortable not to wander astray.
Of course I discovered mom and wow it looks feature-rich and very polished.
I wonder how big of an effort it would be to make it "portable".
Gr
Hi Branden,
given that we are working towards release, i started testing on
non-Linux platforms, first on OpenBSD. After that, i'm planning
to test on Oracle Solaris 11 and on SUN Solaris 10.
This is the first (but not the only) fatal issue i found.
I'm looking for an OK to push the fix.
No Cha
Hello Raf,
>
> Also, when it comes to history of *roff from the UNIX manpages
> angle, this[0] is a good place to visit.
>
> [0] https://manpages.bsd.lv/history.html
>
That is awesome, it is one of the best stories of man yet (there was a good
conference talk a few years back as well, I will
Hello Ingo,
> On Oct 14, 2020, at 7:10 AM, Ingo Schwarze wrote:
>
> Finally, there is an obvious, rather serious error. I do not think
> misattribution should be taken lightly:
>
> the man macro package, originally written by James Clark
>
> The correct statement is:
>
> The man language f
Hi Federico,
Federico Lucifredi wrote on Wed, Oct 14, 2020 at 08:21:49AM -0400:
> On Oct 14, 2020, at 7:10 AM, Ingo Schwarze wrote:
>> Finally, there is an obvious, rather serious error. I do not think
>> misattribution should be taken lightly:
>>
>> the man macro package, originally written
On Wednesday, 14 October 2020 03:20:17 BST Damian McGuckin wrote:
> The UTP Revival Project recreated the source code because Tim and
Sale
> were unable to locate a copy of the original source. It is located at:
>
> http://home.windstream.net/kollar/utp/
There is a version with clickabl
> Admittedly, it would be better to also credit the original authors,
> not only the authors of the GNU reimplementation, as it is done
> here, for example:
>
> https://mandoc.bsd.lv/man/man.7.html
Mhmm, my name is missing...
Anyway, there are some serious typos on that page, for example
M
Hi,
this is the second portability issue that killed the build for me.
Again, i'm looking for an OK to push the fix.
Since i have little experience with C++, please check that the fix
is correct and matches your intent.
I don't think a Changelog entry is needed here, either. This mini-issue
nev
> Isn't it sad that nothing more modern is available?
Since it is open source,
it might make sense to have a team produce a groff version?
Mike
Sent from my Adesso PCK-308UW.
On Wed, Oct 14, 2020 at 10:26:27AM +1100, Greg 'g
Hi Werner,
Werner LEMBERG wrote on Wed, Oct 14, 2020 at 03:27:24PM +0200:
> Ingo Schwarze wrote:
>> Admittedly, it would be better to also credit the original authors,
>> not only the authors of the GNU reimplementation, as it is done
>> here, for example:
>>
>> https://mandoc.bsd.lv/man/man.7.
Hello Ingo,
> On Oct 14, 2020, at 9:06 AM, Ingo Schwarze wrote:
> [..]
>
>> Interesting. As far as I can tell, the origin of that statement
>> is in man 7 groff_man:
>> http://manpages.ubuntu.com/manpages/trusty/man7/groff_man.7.html
>
> That document says:
>
> DESCRIPTION
> The man macros u
On Wed, 14 Oct 2020 11:13:39 -0400
Federico Lucifredi wrote:
> > For man pages, what you need is knowledge of the man macro package,
> > originally written by James Clark [...]
>
> I removed the ?originally? bit, which I believe corrects the flaw (if
> I am reading you correctly).
If I may,
On Wed, Oct 14, 2020, Johann Höchtl wrote:
> Groff is certainly feature-rich, stable and polished with
> great documentation. But I also value l8n, being able to
> input utf8-characters directly into the source or easily
> switch fonts. Not to mention PAO (paragraph-at-once) from
> Knuth-Plass.
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 part of Western
Europe, including our language
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
On 14.10.20 18:41, Peter Schaffter wrote:
Also not sure what
you mean by "easily switch fonts." Since '.ft " is as easy as
it gets, I assume you mean something else.
I have been imprecise. By switching fonts I actually meant making fonts
available to groff, which requires fontforge to ge
Peter Schaffter did make this shell script for font installation available on
his website :
http://schaffter.ca/mom/mom-05.html#install-font
Regards, Thomas
‐‐‐ Original Message ‐‐‐
Le mercredi, octobre 14, 2020 8:16 PM, Johann Höchtl
a écrit :
>
>
> On 14.10.20 18:41, Peter Schafft
On Wed, 14 Oct 2020, Mike Bianchi wrote:
Isn't it sad that nothing more modern is available?
Since it is open source,
it might make sense to have a team produce a groff version?
I did follow up with that site. In case you missed it:
http://home.windstream.net/kollar/utp/
And Deri
Hi Ingo,
On Mon, Oct 12 2020 at 06:08:27 PM, Ingo Schwarze wrote:
> A major problem with gnulib emerged just now that we should perhaps
> treat as a blocker.
[...]
> The code in
>
> gnulib/lib/vasnprintf.c
>
> line 4879 puts a format string containing a %n directive into
> writeable memory and
22 matches
Mail list logo
