ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Christoph Reller <christoph.reller@gmail.com>
Subject: Re: follow up
Date: Wed, 3 Apr 2019 09:06:30 +0200	[thread overview]
Message-ID: <9db0f0aa-4700-c55c-1380-be9bc4f8cfd5@xs4all.nl> (raw)
In-Reply-To: <CAO8LnPEgVJXD_DLTp2PTK-2hO4mS9_6DnZbCnL1SwH5bc+ZQpQ@mail.gmail.com>

On 4/3/2019 7:58 AM, Christoph Reller wrote:
> My two cents:
> 
> I don't believe that it is the CIDSet. Both fun.pdf and fun1.pdf have no 
> CIDSet (which is good).
> The (relevant) differences between the two PDFs are:
> - Different ToUnicode
> - Different embedded font stream
> - Minor differences in the font descriptor
> It could be the ToUnicode: If preview is not able to parse the last 
> entry in the ToUnicode table then it may also drop this glyph in its 
> display, although ToUnicode is only relevant for text extraction.

indeed and only very few viewers do that right

> It could be the font stream: In the CFF font file there is a CharSet 
> table that maps character-IDs to glyph-IDs. If preview cannot read the 
> last entry in this table (or the last glyph, glyph nr. 10) then it might 
> drop it.

coul dbe but acrobat is very picky on that as is ghostscript and they work

> By bet is on the ToUnicode, because, usually, if viewers fail to read a 
> font file then they drop the entire font file and not single glyphs.

hm, but i don't think it's different from non lmtx .. i need to check it

> Anyway, both PDFs seem to be valid. But I wonder if the differences in 
> the font descriptor are legitimate (especially StemV):
> Object 9 <-> 7: Different entry Ascent integer value: 1127 <-> 806 in 
> font descriptor dictionary.
> Object 9 <-> 7: Different entry Descent integer value: -280 <-> -194 in 
> font descriptor dictionary.
> Object 9 <-> 7: Different entry StemV integer value: 91 <-> 0 in font 
> descriptor dictionary.

yes, but most of these are bogus and heuristically derived (could be the 
subset or whole font) and quite certainly not used in rendering 
(positioning happens at the pdf level)

we'll see what magic taco has embrained ... he knows apple pdf handling 
in detail so ...

> Cheers,
> Christoph
> 
> On Tue, Apr 2, 2019 at 10:16 PM Hans Hagen <j.hagen@xs4all.nl 
> <mailto:j.hagen@xs4all.nl>> wrote:
> 
>     On 4/2/2019 8:38 PM, Taco Hoekwater wrote:
>      >
>      >
>      >> On 2 Apr 2019, at 17:11, Hans Hagen <j.hagen@xs4all.nl
>     <mailto:j.hagen@xs4all.nl>> wrote:
>      >>
>      >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
>      >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
>      >>>>> indeed on preview no x shows up but it does in other viewers
>      >>>>>
>      >>>>
>      >>>> Not just the x.
>      >>>> In the second example the s will disappear, be shows up if you
>     add some extra digits, and then dropping the 2
>      >>> I don't have a mac and can't reproduce the problem. But the missing
>      >>> char seems to be always the last one in the beginbfchar/endbfchar
>      >>> list.
>      >>>> The OSX preview is flaky but i’d assume the output of both
>     context version would be similar (enough)
>      >>> The new context adds new lines inside the beginbfchar/endbfchar
>      >>> block. Perhaps this confuses preview and it drops the last entry.
>      >> it is indeed the last one that is the issue but changing spacing
>     or adding dummies doesn't help
>      >
>      > More likely the problem it has is due to the omitted /CIDSet in
>     the font descriptor.
>      >
>      > The error is in the display engine, not the text extractor (since
>     cut&paste work ok).
>      > And that means the problem is almost certainly not the cmap. The
>     only other non-trivial
>      > difference I saw in the old vs. new pdf was that no longer
>     present /CIDSet.
>      >
>      > Unf., generating one in the text editor is bit beyond
>     me-on-the-could mode, so I can
>      > not be certain of that although it seems likely (I checked with
>     FF that the two glyphs
>      > are indeed in the embedded font subset and in the exact slots the
>     pdf says they have, so
>      > that is also unlikely to be the problem.)
>     ok, i'll check that tomorrow ... (cidsets are actually obsolete)
> 
>     Hans
> 
>     -----------------------------------------------------------------
>                                                 Hans Hagen | PRAGMA ADE
>                     Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>              tel: 038 477 53 69 | www.pragma-ade.nl
>     <http://www.pragma-ade.nl> | www.pragma-pod.nl
>     <http://www.pragma-pod.nl>
>     -----------------------------------------------------------------
>     ___________________________________________________________________________________
>     If your question is of interest to others as well, please add an
>     entry to the Wiki!
> 
>     maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> /
>     http://www.ntg.nl/mailman/listinfo/ntg-context
>     webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
>     archive  : https://bitbucket.org/phg/context-mirror/commits/
>     wiki     : http://contextgarden.net
>     ___________________________________________________________________________________
> 
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-04-03  7:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.557.1554137032.1194.ntg-context@ntg.nl>
2019-04-02 11:49 ` Jeong Dal
2019-04-02 12:25   ` Hans Hagen
2019-04-02 12:40     ` Floris van Manen
2019-04-02 12:50       ` Hans Hagen
2019-04-02 13:12         ` Floris van Manen
2019-04-02 13:23           ` Hans Hagen
2019-04-02 13:58             ` Floris van Manen
2019-04-02 14:18               ` Ulrike Fischer
2019-04-02 14:50                 ` Hans Hagen
2019-04-02 15:11                 ` Hans Hagen
2019-04-02 18:38                   ` Taco Hoekwater
2019-04-02 19:29                     ` Floris van Manen
2019-04-02 20:16                     ` Hans Hagen
2019-04-03  5:58                       ` Christoph Reller
2019-04-03  7:06                         ` Hans Hagen [this message]
2019-04-02 14:42               ` Hans Hagen
2019-04-04 22:17 ` Jeong Dal
2019-04-04 22:28   ` Hans Hagen
2019-04-05  6:49   ` Otared Kavian
     [not found] <mailman.769.1554712325.1194.ntg-context@ntg.nl>
2019-04-08 13:32 ` Jeong Dal
     [not found] <mailman.1.1554458401.26589.ntg-context@ntg.nl>
2019-04-05 14:30 ` Jeong Dal
2019-04-08  8:32   ` Otared Kavian
2019-04-01 12:56 Hans Hagen
2019-04-01 13:18 ` Floris van Manen
2019-04-01 13:31   ` Mojca Miklavec
2019-04-01 19:41 ` Henning Hraban Ramm
2019-04-02 15:56 ` Aditya Mahajan
2019-04-02 16:24   ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9db0f0aa-4700-c55c-1380-be9bc4f8cfd5@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=christoph.reller@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).