ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Floris van Manen <vm@klankschap.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: follow up
Date: Tue, 2 Apr 2019 21:29:23 +0200	[thread overview]
Message-ID: <00EFBC2C-57A3-4039-A9DA-77262A2D8440@klankschap.nl> (raw)
In-Reply-To: <1BC1BA6B-67AB-488B-94BC-967ED5A69B87@elvenkind.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 839 bytes --]

> 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.)
> 

I’m not familiar with the internals of pdf files.

When i use firefox as pdf viewer, the font information seems to go void in the new version (fun1.pdf).



[-- Attachment #1.1.2: Screen Shot 2019-04-02 at 21.26.52.PNG --]
[-- Type: image/png, Size: 17234 bytes --]

[-- Attachment #1.1.3: Type: text/plain, Size: 2 bytes --]




[-- Attachment #1.1.4: Screen Shot 2019-04-02 at 21.27.03.PNG --]
[-- Type: image/png, Size: 17884 bytes --]

[-- Attachment #1.1.5: Type: text/plain, Size: 2 bytes --]




[-- Attachment #1.1.6: fun.pdf --]
[-- Type: application/pdf, Size: 6173 bytes --]

[-- Attachment #1.1.7: fun1.pdf --]
[-- Type: application/pdf, Size: 4942 bytes --]

[-- Attachment #1.1.8: Type: text/plain, Size: 2 bytes --]




[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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-02 19:29 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 [this message]
2019-04-02 20:16                     ` Hans Hagen
2019-04-03  5:58                       ` Christoph Reller
2019-04-03  7:06                         ` Hans Hagen
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=00EFBC2C-57A3-4039-A9DA-77262A2D8440@klankschap.nl \
    --to=vm@klankschap.nl \
    --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).