On Thu, Jan 14, 2021 at 06:01:33AM +, Dorai Sitaram via wrote:
> I'm used to single-spacing by now, given its ubiquity, but surely the
> Germans carry their disdain for typographic breathing space a little too far?
> As in the posted article, paragraphs are difficult to visually separate,
>
On 1/13/21, G. Branden Robinson wrote:
> I have no argument against your reasoning. The main reason this isn't
> being done is because no one is working on it (to my knowledge).
I get the scarcity of groff developers, but I had sort of assumed this
wasn't being done because no one had floated th
(Repeating as public confirmation.) I have updated
https://gitlab.com/ds26gte/groff1345 with a COPYRIGHT file. Thanks for
suggesting the prose.
--d
Sent from Yahoo Mail on Android
On Thu, Jan 14, 2021 at 1:45 AM, G. Branden
Robinson wrote: Hi Dorai,
I'm replying to both you and the lis
On 1/14/21, G. Branden Robinson wrote:
> If Commonwealthers are sufficiently annoyed by Umerican hyphenation
> patterns being applied to the Queen's English, they should contribute
> en_GB hyphenation and exception files.
A very good point. Groff is making available all the hyphenation data
On 2021-01-14, Ulrich Lauther wrote:
> On Thu, Jan 14, 2021 at 06:01:33AM +, Dorai Sitaram via wrote:
>> I'm used to single-spacing by now, given its ubiquity, but surely the
>> Germans carry their disdain for typographic breathing space a little too
>> far? As in the posted article, paragra
Hi,
where can I find all commands that can be run? How do I make implication
arrows and such?
Best regards
Filip
Hi Filip,
the man pages are your friend. While eqn(1) is admittedly not especially
talkative to this effect, your answers can be found in groff_char(7).
There is a whole section entitled "Arrows". Since I am not a
mathematician I cannot answer whether implication arrows are included or
not, but i
Hi Everybody,
Filip's question prompted me to have a look at the eqn(1) manpage, and
unfortunately, the "See also" section near the end does not point to
groff_char(7) where all the symbols groff knows are listed.
What about appending this short paragraph and change it from
SEE ALSO: groff(1),
