Follow-up Comment #6, bug #55155 (project groff):
True. For the cited example, the behavior seems clearly wrong. In the
general case, it may be less obvious what should happen.
.tr zx
.char \(zz zeezee
\(zz top
Is this expected to output "zeezee top" or "xeexee top"?
The manual explicitly
Follow-up Comment #2, bug #62814 (project groff):
[comment #1 comment #1:]
> So i think most users would be better served by loading it by default.
That's my gut feeling, though as someone who doesn't use most of this file's
character palette, I defer to the judgment of more experienced users.
Follow-up Comment #7, bug #62816 (project groff):
Had I bothered to RTFM before posting comment #5, I'd have added one more:
* mapping a character to nothing with the .tr request
___
Reply to this item at:
At 2022-07-31T17:57:22+0100, Deri wrote:
> I tested it by replacing the existing pdfpic.tmac.
>
> I notice that Branden has just checked in the two line changes in the
> pdfpic.tmac file I sent to you, so I think they were Ok, saves me some
> typing too. :-)
Yeah, I tried chasing down Joerg's
thanks for the explanations re PDFPIC and status of 1.22.4.
regarding the current issue I unintentionally replied only to deri directly in
last mail.
here is the essential part again:
I had located that sed "creature" and it indeed does not work for me. I suspect this has to do with
those
At 2022-07-31T20:59:44+0200, joerg van den hoff wrote:
> On 31.07.22 18:57, Deri wrote:
> > On Sunday, 31 July 2022 17:34:19 BST joerg van den hoff wrote:
> > > hi deri,
> > >
> > > thank you for looking into this!
> > >
> > > question: the pdfpic.tmac you've send is supposed to work if I
> > >
On Sunday, 31 July 2022 19:59:44 BST joerg van den hoff wrote:
> On 31.07.22 18:57, Deri wrote:
> > On Sunday, 31 July 2022 17:34:19 BST joerg van den hoff wrote:
> >> hi deri,
> >>
> >> thank you for looking into this!
> >>
> >> question: the pdfpic.tmac you've send is supposed to work if I
On 31.07.22 18:57, Deri wrote:
On Sunday, 31 July 2022 17:34:19 BST joerg van den hoff wrote:
hi deri,
thank you for looking into this!
question: the pdfpic.tmac you've send is supposed to work if I include it at
top of my document (e.g. the fragment tt.trf) so that it overrules the
pdfpic
Follow-up Comment #1, bug #62814 (project groff):
Arguably, the definitions in tty.tmac are of such a high quality that any user
of terminal output wants to use term unconditionally, and warnings about
characters in the input document that need any of these fallbacks would make
little sense.
On Sunday, 31 July 2022 17:34:19 BST joerg van den hoff wrote:
> hi deri,
>
> thank you for looking into this!
>
> question: the pdfpic.tmac you've send is supposed to work if I include it at
> top of my document (e.g. the fragment tt.trf) so that it overrules the
> pdfpic that is probably
hi deri,
thank you for looking into this!
question: the pdfpic.tmac you've send is supposed to work if I include it at top of my document
(e.g. the fragment tt.trf) so that it overrules the pdfpic that is probably loaded previously?
well, I have done that (include at top), but then it does
On Sunday, 31 July 2022 10:28:50 BST joerg van den hoff wrote:
> currently considering to slowly migrate to gropdf as my default output
> device (from grops + ps2pdf) and gave PDFPIC a first try. bad luck so far
> ... consider this `ms' document in a file named `tt.trf':
>
> .LP
> foo
> .PDFPIC
currently considering to slowly migrate to gropdf as my default output device
(from grops + ps2pdf)
and gave PDFPIC a first try. bad luck so far ... consider this `ms' document in
a file named `tt.trf':
.LP
foo
.PDFPIC aitail.pdf
.LP
bar
.PDFPIC fig2.pdf
(both pdf files are PDF 1.4)
I see
13 matches
Mail list logo
