On Wed, Nov 08, 2017, Gour wrote:
> Let me say that the reason to loook (again) at groff was the fact that Pandoc
> got support for creating groff output as stated in its release notes:
>
> "New output format ms (groff ms). Complete support, including tables, math,
> syntax highlighting, and PDF b
Hi,
Gour wrote on Wed, Nov 08, 2017 at 05:57:00PM +0100:
> Here I'd like to ask what has happened in the meantime in regard to
> the groff's features and plans stated in the mission statement like
> Knuth-Plass algorithmy for paragraph-based linebreaks, native support
> for TrueType, Open Type, a
On Sat, 2 Sep 2017 13:33:45 -0500
Blake McBride wrote:
> First, I love troff. In my 35+ years in the software industry, I've
> never seen a better balance between simplicity, effectiveness, and
> power with respect to producing fine documents.
Today when browsing archives of this list I fou
On Sat, 2 Sep 2017 18:02:39 -0400
Peter Schaffter wrote:
> When we were drafting a mission statement for groff in 2014, we all
> agreed that backward compatibility would remain a top priority.
> Troff's very long history stands as a functioning proof-of-concept
> that continued backward compatibi
Hi Branden,
> Yes, I admit I had to look in
> /usr/share/X11/locale/en_US.UTF-8/Compose for how to do it
Programs like vim(1) and screen(1) support digraphs from
https://tools.ietf.org/html/rfc1345, e.g. in vim's Insert mode I can
type these nine,
Ctrl-K ' 6 f o o Ctrl-K ' 9
and get
‘f
>> Note that using only straight quotes like '...' is not a good
>> replacement for input IMHO; I much prefer paired quotes.
>
> For input, absolutely. Non-identical paired delimiters are one
> reason why $() is better than `` for process substitution in the
> shell.
Well, $(...) is not as porta
At 2017-09-04T22:35:40+0200, Werner LEMBERG wrote:
>
> > Stuff like `this' should be burned with fire and extreme prejudice.
> > It's been ugly for over 20 years and is indefensible.
>
> I disagree. While it shouldn't be displayed after processing with
> groff, it is very convenient for input ev
> Stuff like `this' should be burned with fire and extreme prejudice.
> It's been ugly for over 20 years and is indefensible.
I disagree. While it shouldn't be displayed after processing with
groff, it is very convenient for input even today. On my US keyboard
it is still non-trivial to enter ‘
At 2017-08-31T20:54:10+, Bjarni Ingi Gislason wrote:
> Introduction:
>
> A) There are about 1400 lines in the code in the "groff" repository that
> contains the backquote, grave (`) as a directional quote, but it is output
> exactly as itself, as it is not processed as an input to "groff" to b
On Sat, Sep 02, 2017, Blake McBride wrote:
> Second, I don't think troff is gaining in popularity. The contrary is,
> Lastly, as stated by others, troff has a substantial history. Significant
> changes in troff could invalidate most of the old documents leaving troff
> with no usage base, and a p
On Thu, Aug 31, 2017 at 3:54 PM, Bjarni Ingi Gislason
wrote:
>
> it is time to modernize "groff" and
> get rid of Americanism, old, obsolete, deprecated, bad, and worse
> decisions.
>
> .
First, I love troff. In my 35+ years in the software industry, I've never
seen a better ba
Modernizing is all well and good, but many people use groff to typeset legacy
documents. Indeed, one could argue that groff has done an excellent job of
walking that line between modernizing and backward compatibility. We have long
names, HTML output (however crude), and a lot of people on this
Hi Bjarni,
You present too long a list, and that may be putting off people from
attempting to reply, but I think the general answer is "no".
> an-old.tmac:.tm `R' is a string (producing the registered sign), not a
> macro.
> devices/grodvi/dvi.cpp:error("unrecognised drawing command `%1'
On 31/08/17 21:54, Bjarni Ingi Gislason wrote:
Introduction:
A) There are about 1400 lines in the code in the "groff" repository that
contains the backquote, grave (`) as a directional quote, but it is output
exactly as itself, as it is not processed as an input to "groff" to be
formatted and ty
14 matches
Mail list logo
