On Wed, Feb 07, 2024, Deri wrote:
> It is with a heavy heart that I announce I shall be leaving the groff mailing
> list, I'm finding it too much work.
Deri --
This news just unmade my day. The value of gropdf and your
contributions to mom have been immeasurable. I will miss your voice
on the
Deri,
I'm very sad to see your departure. This list and the groff project
will sorely miss your knowledge, expertise, and coding skills. I hope
you find a way to return soon.
Hi Branden,
It is with a heavy heart that I announce I shall be leaving the groff mailing
list, I'm finding it too much work. Yesterday, you managed over 2900 words in
approx 80 minutes whilst also doing a code review, and probably 3 other things
as well! I am so jealous my paltry sub 10 words
[self-follow-up]
Hi Deri,
One more thing occurred to me, because your last paragraph was sticking
in my mind and I think I figured out why.
At 2024-02-06T19:30:58-0600, G. Branden Robinson wrote:
> > I am quite sure there will be "bugs" in my code, it is fairly
> > complex, but subjecting it to
On Wednesday, 7 February 2024 01:07:37 GMT Robin Haberkorn wrote:
> Still, when using UTF-8 input, there are problems (missing letters) with
> link texts autogenerated by .pdfhref L.
[...]
>
> Best regards,
> Robin
>
> PS: And to comment on some of the heated discussions on this list:
> It's gr
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
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:
>
Regarding cyrillic characters in PDF outlines, I think I got a few
insights today.
It turns out that the pdfmarks in the postscript code are "text strings"
according to the PDF specs, that is either a PDFDocEncoding or
UTF-16BE with a leading byte-order marker (cf. PDF Reference 1.7).
A PDFDocEnco
On Saturday, 12 August 2023 07:35:20 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-06-23T22:40:42+0100, Deri wrote:
> > On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote:
> > > So it seems that the main problem really lies in grops and/or gropdf
> > > which should ideally work wit
Hi Deri,
At 2023-06-23T22:40:42+0100, Deri wrote:
> On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote:
> > So it seems that the main problem really lies in grops and/or gropdf
> > which should ideally work with the Unicode escapes produced by
> > preconv. I am not sure if we would still
On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote:
> Hello Peter,
>
> I am also now stumbling across Cyrillc-related issues with pdfmark. I am
> using ms for the time being. The bug also affects autogenerating link texts
> given via `.pdfhref L`.
> In the most simple case, preconv will tu
Hello Peter,
I am also now stumbling across Cyrillc-related issues with pdfmark. I am using
ms for the time being. The bug also affects autogenerating link texts given via
`.pdfhref L`.
In the most simple case, preconv will turn your Cyrillic characters into escapes
which are apparently not furthe
[self-reply]
At 2022-09-18T09:37:32-0500, G. Branden Robinson wrote:
> GNU troff doesn't, as far as I can tell, ever write anything but the
> 94 graphical code points in ASCII, spaces, and newlines to its output.
I left out a sentence here; it should be clear from the rest of the
message but it mi
Hi Branden,
> A shorter pole might be to establish a protocol for communication of
> Unicode code points within device control commands. Portability isn't
> much of an issue here: as far as I know there has been no effort to
> achieve interoperation of device control escape sequences among
> trof
Dear Peter, Dear All,
this problem is presumably not limited to groff. I remember the same
issue when I was building LaTeX texts with foreign language elements (in
my case, among others: Chinese) with the package to create internal
links from (hyperref, iirc) table of contents to chapters,etc. As
Hi Peter,
At 2022-09-17T17:35:02-0400, Peter Schaffter wrote:
> Source documents written in Cyrillic and processed with mom/pdfmom
> break the PDF outline:
>
> 1. The text of titles and headings is not displayed in the outline.
[...]
> At a guess, it looks as if gropdf or pdfmark isn't recognizin
Greetings, all.
Source documents written in Cyrillic and processed with mom/pdfmom
break the PDF outline:
1. The text of titles and headings is not displayed in the outline.
2. If there are items where English is automatically part of the
outline label (cover, title page), the label prints (m
19 matches
Mail list logo
