CMap issue in PDF file generated with recent TeX Live + Ghostscript

[Vincent Lefevre]

On 2021-10-19 19:22:04 +0200, Ulrike Fischer wrote:
> LaTeX doesn't only activate \pdfgentounicode=1, it also load
> glyphtounicode which adds more entries. E.g. if you add to your list
> 
> \pdfglyphtounicode{Aogonek}{0104}
> 
> then after ps2pdf the cmap for fi is wrong again. 

Is there a way to avoid the load of glyphtounicode (while still
allowing \pdfgentounicode=1 for users who need to add their own
\pdfglyphtounicode entries) so that the obtained PDF conforms to
the original definition of ToUnicode CMaps?

In https://bugs.ghostscript.com/show_bug.cgi?id=704674#c3
Ken Sharp says:

  The pdfwrite device and PDF interpreter combination cannot currently
  pass ToUnicode CMap information which requires more than 2 bytes to
  represent. This is because it was written against the original
  definition of ToUnicode CMaps, which differed significantly from the
  current definition.

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)