Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #3730

Printing UTF8 (Unicode) - opinions please

Show all headers | View raw

Hi All,

I'm soliciting opinions...

On 21/1/22 9:56 pm, David Newall wrote:
> I've written some PostScript to allow me to print UTF8-encoded strings
> ...
> I also use a table which Adobe published ("UNICODE translation table for 
> non-ASCII characters"), which they say is for going from a glyph name to 
> a Unicode codepoint.  I (ab)use it in the reverse direction.  I turned 
> it into a dictionary keyed on the codepoint.

Many (most?) fonts have glyphs which aren't in Adobe's table, or which
are named differently.  Fontforge can write a table of glyphs in a font
and their corresponding codepoints.  Using that table, unicodeshow looks
more like this:

   % lookup a unicode codepoint (int) in a list of known glyphs (dict)
   % and display the glyph found.
   % dict int unicodeshow -
   /unicodeshow {
     2 copy known { get } { pop pop /.notdef } ifelse glyphshow
   } bind def

While this looks much neater, it requires pre-generating a dictionary
for each font used.

I can't decide which approach is better.

I'm not delighted by needing to add a dictionary that's specific to the
current font to utfshow and unicodeshow because it feels wrong.

I suppose whatever fonts are used to print unicode will be embedded in
the PS, so I could add the table to each font's dictionary.  I wonder if
that would cause confusion to anybody reading the code:

   /unicodeshow { % int unicodeshow -
     currentfont /unicode 2 copy known not {
       pop pop /unicodeshow cvx /invalidfont
       /.error where {pop .error} {signalerror} ifelse
     } if
     get exch 2 copy known { get } { pop pop /.notdef } ifelse glyphshow
   } bind def

Maybe that's not so awful.

Opinions?  Would adding to a font dictionary going to break things?
(I'm looking at you, Acrobat and Distiller.)

Regards,

David

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-21 21:56 +1100
  Re: Printing UTF8 (Unicode) Carlos <carlos@cvkm.cz> - 2022-01-21 14:23 +0100
    Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-22 12:27 +1100
  Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-23 13:31 +1100
    Re: Printing UTF8 (Unicode) Carlos <carlos@cvkm.cz> - 2022-01-23 13:35 +0100
      Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-26 14:59 +1100
        Re: Printing UTF8 (Unicode) Carlos <carlos@cvkm.cz> - 2022-02-10 15:05 +0100
          Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-02-16 13:55 +1100
  Printing UTF8 (Unicode) - opinions please David Newall <davidn@davidnewall.com> - 2022-01-23 14:10 +1100
    Re: Printing UTF8 (Unicode) - opinions please Carlos <carlos@cvkm.cz> - 2022-01-23 13:56 +0100
      Re: Printing UTF8 (Unicode) - opinions please luser droog <luser.droog@gmail.com> - 2022-01-24 08:37 -0800
    Re: Printing UTF8 (Unicode) - opinions please luser droog <luser.droog@gmail.com> - 2022-01-24 08:33 -0800
      Re: Printing UTF8 (Unicode) - opinions please David Newall <davidn@davidnewall.com> - 2022-01-26 15:06 +1100

csiph-web