[dvipdfmx] bug of dvipdfm-x

݆ޒ 16144565 at qq.com
Mon Jan 24 17:28:01 CET 2022


for the pdfparse.c file in dvipdfm-x, the `static const char *valid_chars` in the function `parse_ident` missing `/`.


char *
parse_ident (const char **start, const char *end)
{
  static const char *valid_chars =
    "!\"#$&'*+,-.0123456789:;=?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\^_`abcdefghijklmnopqrstuvwxyz|~";


  return parse_gen_ident(start, end, valid_chars);
}


should change to:


char *
parse_ident (const char **start, const char *end)
{
  static const char *valid_chars =
    "!\"#$&'*+,-./0123456789:;=?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\^_`abcdefghijklmnopqrstuvwxyz|~";


  return parse_gen_ident(start, end, valid_chars);
}


because when I set StemV for TureType font (such simhei.ttf), the fontmap is:
C:/Windows/Fonts/simhei.ttf/0/H/65536/0/0
but because valid_chars don't include `/`, so dvipdfmx can't recognize:
C:/Windows/Fonts/simhei.ttf/0/H/65536/0/0 Identity-H simhei.ttf -v 50
in cid-x.map to change SimHei's StemV.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/dvipdfmx/attachments/20220125/701150a8/attachment.html>


More information about the dvipdfmx mailing list.