ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: Alan BRASLAU <alan.braslau@cea.fr>, NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: command reference not searchable
Date: Thu, 19 May 2016 18:32:17 +0000	[thread overview]
Message-ID: <32A591A1-ECFB-45B1-AE52-48CA39820498@uva.nl> (raw)
In-Reply-To: <20160519110817.0e1d9097@cea.fr>

Very weird. I haven't the faintest idea why this pdf is not searchable and similar ones in the same folder do. 
Checked the permissions but they are the same.
However, I have another document that cannot be searched, the context reference manual from 2013 and there seems to be a difference between these two and the others.
Those I cannot search have in their properties as PDF producer "Mac OSX (version) Quartz PDFContext" (older pdf versions 1.3 and 1.4), the others have Luatex as producer (pdf version 1.7).
Therefore, I strongly suspect that the Quartz producer is the culprit, weird as it may be.
Is it possible to produce the command reference with Luatex as producer excluding the Mac Quartz producer?
It is the only difference I am aware of that matches the behaviour.

> On 19 May 2016, at 19:08, Alan BRASLAU <alan.braslau@cea.fr> wrote:
> 
> I can search this document using any and all pdf tools to which I have
> access on my system.
> 
> Alan
> 
> On Thu, 19 May 2016 16:49:31 +0000
> "Meer, Hans van der" <H.vanderMeer@uva.nl> wrote:
> 
>> Checked again also on a MacBook, definitely not searchable here.
>> I am running El Capitan, and the command reference version is the one
>> from May 17, 2016, found in one of the latest contextbeta
>> distributions.
>> 
>>> On 19 May 2016, at 18:02, Hans Åberg <haberg-1@telia.com> wrote:
>>> 
>>> 
>>>> On 19 May 2016, at 17:00, Meer, Hans van der <H.vanderMeer@uva.nl>
>>>> wrote:
>>>> 
>>>> The command reference in file i-context.pdf is highly useful, but
>>>> that document is not searchable, neither with Preview nor Adobe
>>>> Reader.   
>>> 
>>> Searches work for me in Preview.
> 

Hans van der Meer




___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-05-19 18:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 15:00 Meer, Hans van der
2016-05-19 16:02 ` Hans Åberg
2016-05-19 16:49   ` Meer, Hans van der
2016-05-19 16:59     ` Thomas A. Schmitz
2016-05-19 17:08     ` Alan BRASLAU
2016-05-19 18:32       ` Meer, Hans van der [this message]
2016-05-19 18:23     ` Hans Åberg
2016-05-19 18:24     ` Hans Åberg
2016-05-19 19:59 ` Jean-Pierre Delange
2016-05-19 21:03   ` Mohammad Hossein Bateni
2016-05-19 21:09   ` Wolfgang Schuster
2016-05-20  7:10     ` Meer, Hans van der
2016-05-20  8:34       ` Jean-Pierre Delange
2016-05-20  8:36     ` Jean-Pierre Delange
2016-05-20  3:14 Akira Kakuto
2016-05-20  8:27 ` Hans Hagen
2016-05-20 10:13 Akira Kakuto

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=32A591A1-ECFB-45B1-AE52-48CA39820498@uva.nl \
    --to=h.vandermeer@uva.nl \
    --cc=alan.braslau@cea.fr \
    --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).