Hi Deri,
At 2024-02-06T21:35:05+, Deri wrote:
> Many thanks for your thoughts on my code. I shall reply in general
> terms since your grasp of some of the issues is rather hazy, as you
> admit.
I generally don't feel I grasp code of nontrivial complexity until I've
documented it and written t
On Tue, Feb 06, 2024 at 01:39:51PM +, Deri wrote:
> Hi Robin,
>
> The current gropdf (in the master branch) does support UTF-16BE for pdf
> outlines (see attached pdf), but Branden has not released the other parts to
> make it work! If you can compile and install the current git the applying
On Tuesday, 6 February 2024 14:45:59 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> Now _does_ seem to be a good time to catch up on gropdf-ng merge status.
> There were two things I knew were still unmerged: the slanted symbol
> (SS) font support and the stringhex business, which has larger
> cons
At 2024-02-05T13:11:04-0600, Dave Kemper wrote:
> On 2/5/24, G. Branden Robinson wrote:
> > As far as I know, groff has never extended AT&T troff syntax in _this_
> > respect.
> >
> > The argument count to requests (unlike macros) is seemingly sacrosanct.
>
> Groff extended the .ss request by add
At 2024-02-05T23:57:08+, Lennart Jablonka wrote:
> Quoth G. Branden Robinson:
> > Fortunately, ncurses is attentively maintained. So instead of
> > sucking up a whole bunch of oxygen there as I did with groff, I
> > found that it behooves me to actually read the X/Open Issue 7
> > standard for
Hi Deri,
Now _does_ seem to be a good time to catch up on gropdf-ng merge status.
There were two things I knew were still unmerged: the slanted symbol
(SS) font support and the stringhex business, which has larger
consequences than I understood at first.
At 2024-02-06T13:39:51+, Deri wrote:
>
