Re: [NTG-context] PDF viewer

[Pablo Rodriguez via ntg-context]

On 9/26/22 16:44, Willi Egger via ntg-context wrote:
> Hi Pablo,
>
> Hraban refers to Paulo Ney de Souza from US. He recently joined the
> ConTeXt meeting and indeed he mentioned that TUG had a fund raising
> campaign which was successful.
Many thanks for your replies, Hraban and Willi.

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Willi Egger via ntg-context]

Hi Pablo,

Hraban refers to Paulo Ney de Souza from US. He recently joined the ConTeXt 
meeting and indeed he mentioned that TUG had a fund raising campaign which was 
successful.

Kind regards
Willi

> On 23 Sep 2022, at 17:23, Pablo Rodriguez via ntg-context 
>  wrote:
> 
> On 9/22/22 20:07, Henning Hraban Ramm via ntg-context wrote:
>> […]
>> I suggest we’ll discuss funding in the context group board, but there
>> was also a discussion about fundraising at the 2022 meeting that I
>> didn’t follow – I think Paulo said he had experience in fundraising?
> 
> Hi Hraban,
> 
> sorry if I’m misreading, but I’m afraid I wasn’t able to find any Paulo
> in the messages I have from this list.
> 
> Now I wonder who he might be.
> 
> Many thanks for your help,
> 
> Pablo
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Pablo Rodriguez via ntg-context]

On 9/25/22 17:24, juh via ntg-context wrote:
> Am Thu, Sep 22, 2022 at 06:47:50PM -0600 schrieb Max Chernoff via ntg-context:
>> I think that pdf.js (the Firefox PDF viewer) meets most of these
>> requirements. There are a few requirements that it doesn't meet, but
>> it's open source and written in JavaScript, so we should be able to add
>> anything that's missing.
>
> I found a nasty bug in firefox.
>
> https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1781022

As Jonathan Kew explained, TeX Gyre Heros is also poorly displayed with
Acrobat. The issue may be trickier than we thought (since fixing Firefox
with Heros+LMTX is only part of the issue).

Just as a personal note, I tend to avoid using Heros with LMTX, since
resulting PDF documents may be displayed (poorly on screen) with Acrobat.

I wonder whether this is related to common code for both Acrobat and
Firefox (originally comming from
https://lists.nongnu.org/archive/html/freetype-devel/2013-05/msg0.html).

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[juh via ntg-context]

Am Thu, Sep 22, 2022 at 06:47:50PM -0600 schrieb Max Chernoff via ntg-context:
> I think that pdf.js (the Firefox PDF viewer) meets most of these
> requirements. There are a few requirements that it doesn't meet, but
> it's open source and written in JavaScript, so we should be able to add
> anything that's missing.
> 

I found a nasty bug in firefox.

https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html

https://bugzilla.mozilla.org/show_bug.cgi?id=1781022

juh



signature.asc
Description: PGP signature
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Pablo Rodriguez via ntg-context]

On 9/23/22 12:18, Max Chernoff via ntg-context wrote:
>> Unfortunately, Firefox doesn’t register itself as a PDF viewer (at
>> least on MacOS), that means I can’t use it easily to open a PDF
>> from the command line (e.g. in scripts).
>
> That's odd. You can set it as the default PDF viewer on Windows and
> Linux at least.

Hi Hraban,

I know you wrote scripts, but here you have two links on how to set
another PDF default viewer:

  https://discussions.apple.com/thread/7883441
  https://www.igeeksblog.com/how-to-change-default-pdf-viewer-on-mac/

And to open PDF documents from scripts, once the default viewer is set,
it seems that "open" is the right way to go (similar to "xdge-open" in
Linux).


>>> […]
 - JS for calculations

I would love that JS worked fine in PDF.js.

I was surprised that not even this worked fine
(https://github.com/mozilla/pdf.js/issues/13918):

  this.pageNum = this.numPages ;

I would love that the kind of presentation contained in
https://free-culture.tk could be displayed as
https://www.vector-video.tk/bga-presvoz.pdf (only Acrobat seems to be
able to deal with it).

If PDF.js could deal with multimedia and JS in PDF, other audio formats
than MP3 (such as Opus) could be used.

 for annotations […]
>>> Reading annotations works, but you can't modify anything.
>> […]
> Microsoft Edge has decent PDF annotation support. I've never tested
> it on Linux, but a Linux version does exist. Okular also lets you add
> some annotations.

Annotations may be part of a PDF viewer, but the problem is that in some
projects they understand that the feature to add them is part of a PDF
editor (so annotations won’t be added).

I think this is what happened to annotations in Evince (but I may be
wrong here). And I wonder whether PDF.js might take this approach.

Just in case it might help,

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Bruce Horrocks via ntg-context]

On 23 Sep 2022, at 08:59, Henning Hraban Ramm via ntg-context 
 wrote:
> 
> Unfortunately, Firefox doesn’t register itself as a PDF viewer (at least on 
> MacOS), that means I can’t use it easily to open a PDF from the command line 
> (e.g. in scripts).

The following works for me in Monterey on an Intel Mac:

$ /Applications/Firefox.app/Contents/MacOS/firefox test.pdf  

—
Bruce Horrocks
Hampshire, UK

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Pablo Rodriguez via ntg-context]

On 9/22/22 20:07, Henning Hraban Ramm via ntg-context wrote:
> […]
> I suggest we’ll discuss funding in the context group board, but there
> was also a discussion about fundraising at the 2022 meeting that I
> didn’t follow – I think Paulo said he had experience in fundraising?

Hi Hraban,

sorry if I’m misreading, but I’m afraid I wasn’t able to find any Paulo
in the messages I have from this list.

Now I wonder who he might be.

Many thanks for your help,

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Max Chernoff via ntg-context]

Hi Hraban,

> Unfortunately, Firefox doesn’t register itself as a PDF viewer (at least 
> on MacOS), that means I can’t use it easily to open a PDF from the 
> command line (e.g. in scripts).

That's odd. You can set it as the default PDF viewer on Windows and
Linux at least.

> >> for forms:
> >>   - fill in
> > Yes.
> 
> Just checked again with current Firefox: It doesn’t work with all of my 
> test files.

I tested it with the eforms manual:

   http://mirrors.ctan.org/macros/latex/contrib/acrotex/doc/eformman.pdf
   
and it seems to work fine for me. I've also used it to fill out a few
government forms in the past and it's worked too. Unfortunately, I think
that there are like 12 incompatible ways of making a form in PDF, so
support probably heavily depends on how the document was made.

> >>   - print documents with/without form contents
> > Yes.
> 
> I couldn’t find an option to print without form contents. (But usually
> you would want filled forms, so “with” is ok.)

Well if you refresh the page, you can delete everything that you've
filled in :)

> >>   - custom checkmarks/radiobuttons should work & display correctly
> > 
> > Usually it works, sometimes it doesn't.
> > 
> >>   - JS for calculations
> > 
> > Usually it works, sometimes it doesn't.
> 
> Need to check further...

I checked with the eforms manual linked above. Check marks and radio
buttons seem to work, but calculations don't.

> >> for annotations (correction workflow; generally just nice to have):
> >>   - similar to Adobe/Foxit Reader
> > 
> > Reading annotations works, but you can't modify anything.
> 
> Ok. There’s still no PDF viewer on Linux that can handle annotations 
> well. (But even Acrobat Reader on MacOS frequently crashes on them; I’m 
> using Foxit Reader for annotations, but the one for Linux is too old.)

Microsoft Edge has decent PDF annotation support. I've never tested it
on Linux, but a Linux version does exist. Okular also lets you add some
annotations.


> > I've been using pdf.js almost exclusively for the past few years either
> > via Firefox or VS Code, and I've never really had any problems. The only
> > real issue that I've had is that it gets fairly slow with documents over
> > a few thousand pages long. Otherwise, it seems pretty fast and stable,
> > and it supports nearly every feature that I tend to need.
> 
> Well, documents with thousands of pages are probably unreliable/slow in 
> most viewers.

I've got a 1.1GB document with 16000 pages, and Okular handles it just
as fast as a 10 page document. Firefox at least manages to not crash
when opening the document, which is better than most viewers.

Okular is actually a pretty nice viewer in general. It's really fast,
and it also seems to support most of these features. The tricky thing
with it though is that I think that it would be much harder to modify
compared to pdf.js.

-- Max

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[luigi scarso via ntg-context]

On Thu, Sep 22, 2022 at 8:08 PM Henning Hraban Ramm via ntg-context <
ntg-context@ntg.nl> wrote:

> Hi all,
> I compiled a kind of wishlist what we need or look for in a new or
> enhanced open source PDF viewer, as discussed e.g. at the 2021 meeting.
>
> https://wiki.contextgarden.net/PDF_viewer
>
>
slightly off-topic
1)   gs has a new pdf viewer
 https://www.ghostscript.com/blog/pdfi.html
but of course I think that they push on mupdf

2) EBookDroid - PDF & DJVU Reader is a very nice pdf viewer for android,
especially on 10" tablets. It's based on mupdf.

It seems that mupdf is more suited to be embedded into / used for
embedding   other programs:
latest mupdf (1.20, iirc)  has a js console and  I think you can interact
with the viewer -- sort of the js console of the browser;
I haven't seen how yet, perhaps you can add objects on the fly to the
documents, in this case one can think of embedding a
small luatex (no harms,  after all mupdf it's already a big binary) and add
(pdf)objects by scripting.


-- 
luigi
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Henning Hraban Ramm via ntg-context]

Am 23.09.22 um 02:47 schrieb Max Chernoff:


I compiled a kind of wishlist what we need or look for in a new or
enhanced open source PDF viewer, as discussed e.g. at the 2021 meeting.

https://wiki.contextgarden.net/PDF_viewer

Feel free to enhance the wiki page or discuss here.


I think that pdf.js (the Firefox PDF viewer) meets most of these
requirements. There are a few requirements that it doesn't meet, but
it's open source and written in JavaScript, so we should be able to add
anything that's missing.


You’re right, pdf.js is quite good, and it’s already used by a lot of 
projects (browsers, editor plugins etc.) – the latter also means that 
you often encounter old/buggy/limited versions.


Unfortunately, Firefox doesn’t register itself as a PDF viewer (at least 
on MacOS), that means I can’t use it easily to open a PDF from the 
command line (e.g. in scripts).


But anyway, that could shift our focus to add/enable features for pdf.js 
in TeX editors.




  - PDF 2.0 compatible


It can open PDF 2.0 files, but I doubt that it supports every single
feature.


I won’t expect every feature, there are too many. Actually I don’t know 
which features of PDF 2.0 Hans was missing in viewers.



  - proper color and transparency display (respect color profiles)


It supports all of the PDF colour models/profiles for vectors, although
it ignores embedded colour profiles in images.

https://github.com/mozilla/pdf.js/issues/2856

Regular RGB and CMYK stuff works fine though.


That’s a problem if you prepare PDFs for printing. Apple’s PDF library 
(used e.g. in Preview.app, Skim, TeXshop) also does a bad job at it, as 
well as Sumatra and Chrome (according to the comments to that ticket).



  - limited JavaScript support (no modification, no file operations)


Yes, although it is quite limited:


https://blog.mozilla.org/attack-and-defense/2021/10/14/implementing-form-filling-and-accessibility-in-the-firefox-pdf-viewer/


Thank you for the link!

What they write about the scope of JS in pdf.js sounds good; but 
presentation stuff like buttons (e.g. for OCG) is probably missing.


I need to check the limits of forms in pdf.js; but Mozilla even 
implemented XFA (e.g. Qoppa didn’t).



  - update on file change (configurable)


Not by default in Firefox. It works fine in this extension though:

https://github.com/tomoki1207/vscode-pdfviewer


There it’s probably the editor framework that enables refresh. (Same 
experience with pdf.js in Atom.)



  - SyncTeX support


Not in Firefox, although there are patches to enable it:


https://github.com/James-Yu/LaTeX-Workshop/blob/cff1a372/viewer/components/synctex.ts

https://github.com/tomoki1207/vscode-pdfviewer/blob/92fecdb8/src/pdfPreview.ts


One of the Atom plugins was supposed to have it, but it didn’t work... 
(SyncTeX with ConTeXt is special anyway, we need to look into that again.)



  - accessibility (e.g. alternative text must work)


I've never used it, but it looks like there's good support:


https://blog.mozilla.org/attack-and-defense/2021/10/14/implementing-form-filling-and-accessibility-in-the-firefox-pdf-viewer/


Sounds good.


  - JS for controlling optional content groups (OCGs, Viewer Layers)


You can toggle all the layers in the side panel. I don't think that you
can toggle via buttons or JS though.


Same as in Okular. OCG control via JS would enable stepwise 
presentations and simple animations.



  - inner- and inter-document links must work


Yes; however, inter-document links are sometimes limited depending for
security reasons. I'm sure that this can be configured though.


Of course; I just meant it would be handy to be able to jump between 
PDFs in the same directory.



  - multimedia support at least via links (suggestion: use “plain Rich
Media” approach with OS’ default player)


I don't think so, although I guess you could include a video file as an
attachment.


A question for Michal...


  - transition effects not necessary (but if the developer has fun
including them, go on)


No transition effects.


for forms:
  - fill in

Yes.


Just checked again with current Firefox: It doesn’t work with all of my 
test files.



  - print documents with/without form contents

Yes.


I couldn’t find an option to print without form contents. (But usually 
you would want filled forms, so “with” is ok.)



  - same-ID fields on different pages must be synchronized


No idea.


If the form generally works, this does also.
I listed it because it’s a problem in some viewers.


  - custom checkmarks/radiobuttons should work & display correctly


Usually it works, sometimes it doesn't.


  - JS for calculations


Usually it works, sometimes it doesn't.


Need to check further...


for annotations (correction workflow; generally just nice to have):
  - similar to Adobe/Foxit Reader


Reading annotations works, but you can't modify anything.


Ok. There’s still no PDF viewer on Linux that can handle annotations 

Re: [NTG-context] PDF viewer

[Alan Braslau via ntg-context]

On Thu, 22 Sep 2022 18:47:50 -0600
Max Chernoff via ntg-context  wrote:

> I've been using pdf.js almost exclusively for the past few years
> either via Firefox or VS Code, and I've never really had any
> problems. The only real issue that I've had is that it gets fairly
> slow with documents over a few thousand pages long. Otherwise, it
> seems pretty fast and stable, and it supports nearly every feature
> that I tend to need.

I have never used firefox to display pdf files. I just tried it and
find that it has an interesting feature of caching rendered pages.

Pages with complicated graphics (think MetaPost with hundreds of
thousands of objects) get rendered pretty quickly, although one can see
the very many objects being drawn the first time the page is displayed.
Subsequently displays of these pages have no lag whatsoever.

Alan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] PDF viewer

[Max Chernoff via ntg-context]

Hi Hraban,

> I compiled a kind of wishlist what we need or look for in a new or 
> enhanced open source PDF viewer, as discussed e.g. at the 2021 meeting.
> 
> https://wiki.contextgarden.net/PDF_viewer
> 
> Feel free to enhance the wiki page or discuss here.

I think that pdf.js (the Firefox PDF viewer) meets most of these
requirements. There are a few requirements that it doesn't meet, but
it's open source and written in JavaScript, so we should be able to add
anything that's missing.

Going down the list on the Wiki:

> in general:
>  - PDF 2.0 compatible

It can open PDF 2.0 files, but I doubt that it supports every single
feature.

>  - proper color and transparency display (respect color profiles)

It supports all of the PDF colour models/profiles for vectors, although
it ignores embedded colour profiles in images.

   https://github.com/mozilla/pdf.js/issues/2856

Regular RGB and CMYK stuff works fine though.

>  - limited JavaScript support (no modification, no file operations)

Yes, although it is quite limited:

   
https://blog.mozilla.org/attack-and-defense/2021/10/14/implementing-form-filling-and-accessibility-in-the-firefox-pdf-viewer/

>  - search

Yes.

>  - update on file change (configurable)

Not by default in Firefox. It works fine in this extension though:

   https://github.com/tomoki1207/vscode-pdfviewer

>  - keyboard control for as much as possible (but also menus/menubars)

Yes

>  - sidebar for bookmarks/ToC

Yes

>  - SyncTeX support

Not in Firefox, although there are patches to enable it:

   
https://github.com/James-Yu/LaTeX-Workshop/blob/cff1a372/viewer/components/synctex.ts
   
https://github.com/tomoki1207/vscode-pdfviewer/blob/92fecdb8/src/pdfPreview.ts

>  - accessibility (e.g. alternative text must work)

I've never used it, but it looks like there's good support:

   
https://blog.mozilla.org/attack-and-defense/2021/10/14/implementing-form-filling-and-accessibility-in-the-firefox-pdf-viewer/

>  - access to file attachments (lower priority)

Surprisingly, yes.

> for presentations:
>  - presentation mode (full screen, no visible controls, on one 
>monitor/beamer of choice)

Yes.

>  - JS for controlling optional content groups (OCGs, Viewer Layers)

You can toggle all the layers in the side panel. I don't think that you
can toggle via buttons or JS though.

>  - inner- and inter-document links must work

Yes; however, inter-document links are sometimes limited depending for
security reasons. I'm sure that this can be configured though.

>  - multimedia support at least via links (suggestion: use “plain Rich
>Media” approach with OS’ default player)

I don't think so, although I guess you could include a video file as an
attachment.

>  - transition effects not necessary (but if the developer has fun
>including them, go on)

No transition effects.

> for forms:
>  - fill in

Yes.

>  - print documents with/without form contents

Yes.

>  - same-ID fields on different pages must be synchronized

No idea.

>  - custom checkmarks/radiobuttons should work & display correctly

Usually it works, sometimes it doesn't. 

>  - JS for calculations

Usually it works, sometimes it doesn't. 

> for annotations (correction workflow; generally just nice to have):
>  - similar to Adobe/Foxit Reader

Reading annotations works, but you can't modify anything.

> for development/debugging:
>  - show metadata (incl. XMP), e.g. in a sidebar or dialog

You can see all the "regular" metadata, but XMP doesn't work.

>  - show fonts metadata (inclusion etc.)

No.

>  - show PDF Boxes (MediaBox, CropBox, TrimBox, BleedBox, ArtBox) as
>colored frames, switchable via preferences and menu (bar) item

No.

>  - check for PDF/A and PDF/X compliance would be nice (integrate
>VeraPDF?)

>  - FOSS license

Yes. (Apache 2.0)

>  - should at least work on Windows, MacOS (preferably 10.14+), Linux
>and *BSD; iOS & Android versions would be nice

It's built in to Firefox, so it works on Windows, macOS, Linux, and the
BSDs. It should also work on mobile, although support is a little
spottier there.

>  - how about (long term) support?

It should be supported as long as Firefox exists.

>  - Funding

Overleaf uses pdf.js as its default PDF viewer, so they may perhaps be
willing to help.

~~

I've been using pdf.js almost exclusively for the past few years either
via Firefox or VS Code, and I've never really had any problems. The only
real issue that I've had is that it gets fairly slow with documents over
a few thousand pages long. Otherwise, it seems pretty fast and stable,
and it supports nearly every feature that I tend to need.

Since it's written in JavaScript, it should be fairly easy to modify,
and it should run on nearly everything.

-- Max


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 

Re: [NTG-context] PDF viewer poll

[Hans Hagen]

On 10/20/2019 10:15 PM, Marcin Borkowski wrote:


Maybe Lua is, but every scriptable program is a risk.
LuaTeX and write18 _are_ dangerous.
It would be very easy to spread malicious TeX code, since everyone uses CTAN 
(LaTeX) packages without checking them first.
But it wouldn’t come far, I guess, for it needs a while for a package to become 
known and in wide use, and that still means only in a subset of the (La)TeX 
community, where there are enough expert hackers who would find this malicious 
code.


Assuming that they would search for it.  I'm less of an optimist here.

no problem getting a hit on a search

https://www.usenix.org/system/files/login/articles/73506-checkoway.pdf

-
  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
___

Re: [NTG-context] PDF viewer poll

[Marcin Borkowski]

On 2019-10-19, at 12:21, Henning Hraban Ramm  wrote:

>> Am 2019-10-15 um 08:17 schrieb Marcin Borkowski :
 Basically javascript can be limited to (1) setting annotation properties, 
 like toggling layers or button renditions, and (2) some simple 
 calculations (for forms). Constructing pdf runtime using javascript is 
 pretty braindead (use html instead then).
>>>
>>> D’accord.
>>
>> Of course you are aware that limiting a powerful language is not an easy
>> task?
>
> I am. But JS in PDF is completely different from PDF in browsers anyway (no 
> DOM!), so they don’t need a complete interpreter and could have limited PDF 
> scripting to a few commands, in JS syntax or anything else.

Fair enough, although I don't have an association JS <-> browser
ingrained so much - for me, JS is a general purpose language which
happens to be embedded in browsers, but also many other places.  Most of
my JS code runs either on a server (backend code) or in a development
environment (various, let's call it, DevOps-ish scripts).  Only now and
then I write JS for browsers, and then it is often crippled JS, full of
things like "var" (because old browsers etc.)

 It is one of the puzzling areas to me: no problem in browsers and 
 elsewhere but not in open source pdf viewers. It's not the most complex 
 stuff so it probably indicates that no one cares much about these features.
>>>
>>> I wouldn’t say "no problem", because JS causes security problems everywhere.
>>
>> It's not JS that causes problems.  Any other (powerful enough) language
>> not specifically designed with browser environment in mind could be
>> problematic here.  I guess that having Perl, Python or Ruby instead of
>> JS would create a similar set of problems.  (Lua might be an exception
>> due to its design and a possibility to whitelist functions for eval,
>> AFAIR.)
>
> Of course any programming language is a security risk. More so if it runs in 
> an ubiquitous program like a browser. And since they created JavaScript for 
> that, JS causes problems.
>
> When I read "Java runs on millions of devices" I don’t feel that’s good 
> advertising, but it remembers me that each of those devices is at risk.

I like this approach:-).  There is also that old joke than "every time
you install Java it gets moved from another device to yours", since the
installer has been saying that "3 billion devices run Java" for almost
two decades now.

>> Just 2 cents from a JS programmer who actually thinks that JS is not the
>> worst Lisp dialect out there.
>
> I didn’t say JS is bad. For me it’s a necessary evil.
> I don’t think my beloved Python would be a better choice for client scripts.

Python is a worse Lisp dialect than JS, but still nice.  (Disclaimer:
i have only written less than 1000 lines of Python in my life.)

> Maybe Lua is, but every scriptable program is a risk.
> LuaTeX and write18 _are_ dangerous.
> It would be very easy to spread malicious TeX code, since everyone uses CTAN 
> (LaTeX) packages without checking them first.
> But it wouldn’t come far, I guess, for it needs a while for a package to 
> become known and in wide use, and that still means only in a subset of the 
> (La)TeX community, where there are enough expert hackers who would find this 
> malicious code.

Assuming that they would search for it.  I'm less of an optimist here.

> And you can count the people on one hand who would be able to publish a 
> malicious ConTeXt module… Malicious code snippets in our wiki or ML also 
> wouldn’t come far.

That's interesting.  It would be enough to have a "plain TeX virus",
probably.  I guess the main reason malicious ConTeXt code does not exist
(assuming this is the case!) is that it is not economically viable - the
ConTeXt community is too small.

>
> There was PDF malware (using JS or media stuff). There also was PostScript 
> malware in its time. The latter didn’t make a lot of sense, except it could 
> destroy RIP hardware. The RIP technician at the newspaper where I worked told 
> me stories, e.g. there was an evil EPS (some faulty customer logo, no 
> deliberate malware) that caused the deletion of important parts of the RIP 
> software. At my time there was a PS ghost: somehow a page got installed on 
> one of the printers and got printed at odd times. Reboot didn’t help, we 
> never found the cause.

That's absolutely fascinating!

Best,

--
Marcin Borkowski
http://mbork.pl
___
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
___

Re: [NTG-context] PDF viewer poll

[Henning Hraban Ramm]

Hi, nice to read you again!

(BTW what’s the state of Husayni fonts?)


> Am 2019-10-15 um 06:58 schrieb Hamid,Idris :
> 
> As a commercial replacement to Adobe Acroboat, nothing beats NitroPDF.  
> Clean interface. Avoids most if not all of the problems mentioned by Hans.

I can’t check it out since i don’t use Windows, and their website is a lot of 
marketing fluff.
So I hope you can tell me:
Can/has Nitro…
- check PDF/X, /A, /UA? (AFAIK only /A)*
- convert colors (e.g. RGB->CMYK or any->grayscale)?*
- update changed files (automatically or on key press)?
- support SyncTeX? (probably not)
- handle forms (print, save)? (probably yes)
- support JavaScript? (probably not)
- a localized interface? (probably yes)

*) or general preflighting like Acrobat has


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
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
___

Re: [NTG-context] PDF viewer poll

[Henning Hraban Ramm]

> Am 2019-10-19 um 12:51 schrieb Hans Hagen :
> 
> On 10/19/2019 12:21 PM, Henning Hraban Ramm wrote:
> 
>> When I read "Java runs on millions of devices" I don’t feel that’s good 
>> advertising, but it remembers me that each of those devices is at risk.
> 
> The java updates keept telling that it runs on 3 billion devices but that 
> message doesn't change over years. I always wonder about numbers. One can 
> find similar huge numbers for tex usage but what defines usage (forced? 
> ontime? for fun? lifelong? advanced or like any word processor usage?).

Jep. And it doesn’t help if my washing machine runs Java if I can’t change the 
program. (Or play Tetris on it while waiting, or whatever.)

>> It would be very easy to spread malicious TeX code, since everyone uses CTAN 
>> (LaTeX) packages without checking them first.
>> But it wouldn’t come far, I guess, for it needs a while for a package to 
>> become known and in wide use, and that still means only in a subset of the 
>> (La)TeX community, where there are enough expert hackers who would find this 
>> malicious code.
>> And you can count the people on one hand who would be able to publish a 
>> malicious ConTeXt module… Malicious code snippets in our wiki or ML also 
>> wouldn’t come far.
> 
> Also, I tend to stay optimistic. If there were way more strict rules for 
> software abuse (with hard penalties) it would be less of a problem, but for 
> now we just have to trust. So, far we could trust texies.

Exactly. I guess it makes sense to be aware that there is a risk, but on the 
other hand the risk is quite neglectable, depending on your own programming 
skills… (I managed to mess up a git repository last week, trying to rename a 
file in all of the branches. Big pro of SCM repositories: you can restore them.)

>> There was PDF malware (using JS or media stuff). There also was PostScript 
>> malware in its time. The latter didn’t make a lot of sense, except it could 
>> destroy RIP hardware. The RIP technician at the newspaper where I worked 
>> told me stories, e.g. there was an evil EPS (some faulty customer logo, no 
>> deliberate malware) that caused the deletion of important parts of the RIP 
>> software. At my time there was a PS ghost: somehow a page got installed on 
>> one of the printers and got printed at odd times. Reboot didn’t help, we 
>> never found the cause.
> Writing could be restricted I guess, so wiping rip source is also bit of a 
> bug in the rip i guess. Anyway, I do remember sending postscript to our 
> printer just to find out that you ended up with an empty paperbin and a few 
> lines per page with garbage ascii. In that respect pdf is a bit better: 
> something or nothing gets printed.
> 
> This ghost: makes for nice debugging. Kind of a challenge.

We weren’t up to it, and it was just a minor annoyance. Maybe the problem was 
not really in the printer but in the print spooler of one workstation, so that 
the job was printed every time it was switched on or some user logged in.

> (btw, this makes for a nice topic next meeting: security and documents and 
> such)

No, that’s boring ;)

Best, Hraban
___
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
___

Re: [NTG-context] PDF viewer poll

[Hans Hagen]

On 10/19/2019 12:21 PM, Henning Hraban Ramm wrote:


When I read "Java runs on millions of devices" I don’t feel that’s good 
advertising, but it remembers me that each of those devices is at risk.


The java updates keept telling that it runs on 3 billion devices but 
that message doesn't change over years. I always wonder about numbers. 
One can find similar huge numbers for tex usage but what defines usage 
(forced? ontime? for fun? lifelong? advanced or like any word processor 
usage?).



Just 2 cents from a JS programmer who actually thinks that JS is not the
worst Lisp dialect out there.


I didn’t say JS is bad. For me it’s a necessary evil.
I don’t think my beloved Python would be a better choice for client scripts.
Maybe Lua is, but every scriptable program is a risk.


The fact that it's simple kind of helps. One can disable by overloading.


LuaTeX and write18 _are_ dangerous.


Sure, so can be crossing a street. Anyway, for quite a while there 
actually is a sandbox model in context which can limit its scope pretty 
much but it (being done a while ago) hasn't been tested that much (afer 
all I dont' need it).



It would be very easy to spread malicious TeX code, since everyone uses CTAN 
(LaTeX) packages without checking them first.
But it wouldn’t come far, I guess, for it needs a while for a package to become 
known and in wide use, and that still means only in a subset of the (La)TeX 
community, where there are enough expert hackers who would find this malicious 
code.
And you can count the people on one hand who would be able to publish a 
malicious ConTeXt module… Malicious code snippets in our wiki or ML also 
wouldn’t come far.


Also, I tend to stay optimistic. If there were way more strict rules for 
software abuse (with hard penalties) it would be less of a problem, but 
for now we just have to trust. So, far we could trust texies.



There was PDF malware (using JS or media stuff). There also was PostScript 
malware in its time. The latter didn’t make a lot of sense, except it could 
destroy RIP hardware. The RIP technician at the newspaper where I worked told 
me stories, e.g. there was an evil EPS (some faulty customer logo, no 
deliberate malware) that caused the deletion of important parts of the RIP 
software. At my time there was a PS ghost: somehow a page got installed on one 
of the printers and got printed at odd times. Reboot didn’t help, we never 
found the cause.
Writing could be restricted I guess, so wiping rip source is also bit of 
a bug in the rip i guess. Anyway, I do remember sending postscript to 
our printer just to find out that you ended up with an empty paperbin 
and a few lines per page with garbage ascii. In that respect pdf is a 
bit better: something or nothing gets printed.


This ghost: makes for nice debugging. Kind of a challenge.

(btw, this makes for a nice topic next meeting: security and documents 
and such)


Hans

-
  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
___

Re: [NTG-context] PDF viewer poll

[Henning Hraban Ramm]

> Am 2019-10-15 um 08:17 schrieb Marcin Borkowski :
>>> Basically javascript can be limited to (1) setting annotation properties, 
>>> like toggling layers or button renditions, and (2) some simple calculations 
>>> (for forms). Constructing pdf runtime using javascript is pretty braindead 
>>> (use html instead then).
>> 
>> D’accord.
> 
> Of course you are aware that limiting a powerful language is not an easy
> task?

I am. But JS in PDF is completely different from PDF in browsers anyway (no 
DOM!), so they don’t need a complete interpreter and could have limited PDF 
scripting to a few commands, in JS syntax or anything else.

>>> It is one of the puzzling areas to me: no problem in browsers and elsewhere 
>>> but not in open source pdf viewers. It's not the most complex stuff so it 
>>> probably indicates that no one cares much about these features.
>> 
>> I wouldn’t say "no problem", because JS causes security problems everywhere.
> 
> It's not JS that causes problems.  Any other (powerful enough) language
> not specifically designed with browser environment in mind could be
> problematic here.  I guess that having Perl, Python or Ruby instead of
> JS would create a similar set of problems.  (Lua might be an exception
> due to its design and a possibility to whitelist functions for eval,
> AFAIR.)

Of course any programming language is a security risk. More so if it runs in an 
ubiquitous program like a browser. And since they created JavaScript for that, 
JS causes problems.

When I read "Java runs on millions of devices" I don’t feel that’s good 
advertising, but it remembers me that each of those devices is at risk.

> Just 2 cents from a JS programmer who actually thinks that JS is not the
> worst Lisp dialect out there.

I didn’t say JS is bad. For me it’s a necessary evil.
I don’t think my beloved Python would be a better choice for client scripts. 
Maybe Lua is, but every scriptable program is a risk.
LuaTeX and write18 _are_ dangerous.
It would be very easy to spread malicious TeX code, since everyone uses CTAN 
(LaTeX) packages without checking them first.
But it wouldn’t come far, I guess, for it needs a while for a package to become 
known and in wide use, and that still means only in a subset of the (La)TeX 
community, where there are enough expert hackers who would find this malicious 
code.
And you can count the people on one hand who would be able to publish a 
malicious ConTeXt module… Malicious code snippets in our wiki or ML also 
wouldn’t come far.

There was PDF malware (using JS or media stuff). There also was PostScript 
malware in its time. The latter didn’t make a lot of sense, except it could 
destroy RIP hardware. The RIP technician at the newspaper where I worked told 
me stories, e.g. there was an evil EPS (some faulty customer logo, no 
deliberate malware) that caused the deletion of important parts of the RIP 
software. At my time there was a PS ghost: somehow a page got installed on one 
of the printers and got printed at odd times. Reboot didn’t help, we never 
found the cause.

Best, Hraban


___
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
___

Re: [NTG-context] PDF viewer poll

[context]

Hello,

On 2019-10-13 12:43, Henning Hraban Ramm wrote:

Hi, I’d like to update my list of (usable!) PDF viewers.
Which one do you use? (Current version?)


PDF XChange Viewer 
(https://www.tracker-software.com/product/pdf-xchange-viewer)



What are its pros and cons?


+ Free; not annoying as AR is; many functions included, restore last 
view, tabbed env, page thumbs navigator/bookmarks navigator, attachment 
list, comment list; OCR included; handy designed; (many command line 
options, e.g.) /open and /close options to be used by 3rd party 
programs; /printto for batch printing; printing also: tile large pages / 
print many pages on one sheet of paper; some "extras" require pro 
(non-free) version.



Is it free (open source, freeware)?


Free, not open source.


Does it work on Win/Lin/Mac?


Windows


Does it have a localized interface? (I don’t care, but I work with
people who don’t understand a lot of English.)


Yes.


Can it handle comments, attachments?


Yes.


Can it handle forms with or without JavaScript?


Not using - don't know


Does it support SyncTeX? (Who uses that anyway?)


No.

Does it update changed PDFs on its own (or does it even block 
overwriting)?


No. With working with ConTeXt, I'm using a batch file which normally 
opens a copy of a PDF being compiled, and once it's (successfully) 
compiled, the batch reopens the PDF in the viewer.



Which other features are essential for your choice?


Handy work - after some time of using the prog, you see how much "handy" 
the program is, but hard to say which feature is essetial or most 
important; "total handyness" is the goal.


I would probably change this PDF viewer just if synctex worked WELL with 
the source (and in my case - I'm using Lua in ConTeXt widely to generate 
the PDF, so in most cases synctech navigates me badly to the source).


Best regards,

Lukas



E.g. I’m working with:
- Preview.app (Mac)
  Default on MacOS, fast & easy. No JS, bad forms support, updates
"sometimes". Usable as a previewer, not as a PDF toolbox.
- Adobe Reader DC (Mac)
  I use it only to check forms or as reference. Unusable GUI.
- Acrobat Pro 9 (Mac)
  Was my workhorse, but works on MacOS Mojave only partly; slow &
crash-prone; no updates. Can check PDF/X<4 and convert colors.
- PDF Studio Pro (on Mac & Linux)
  Bought to replace AcroPro9; JS support broken; slow startup; no
updates. Can check PDF/X, A, UA and convert colors.
  Ok with forms, but doesn’t support LiveCycle forms (deprecated, but
used by German boards).
- Qpdfview (Linux)
  Fast and easy; reliably updates.
- PDF.js (Browser or Atom)
  Is said to do SyncTeX (never tried). Easy, but slow. Updates.


Curious: Hraban
___
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
___

___
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
___

Re: [NTG-context] PDF viewer poll

[luigi scarso]

>
> mupdf started simple but I think it also grew in a weird
> direction (large codebase, some reflow I think, a strange epub
> substandard support, etc .. all pretty useless to me and I'm not sure
> how optional it it ... so no longer as lightweight as it could be ...)
>

mupdf-1.16.1-source/build/release$ du -sh platform resources source
thirdparty
524K platform
42M resources
7.2M source
6.6M thirdparty

where resources is a directory with 155 fonts compressed and embedded into
the exe.
Following (the quite old) pdf this  should be configurable
https://ghostscript.com/~robin/mupdf_explored.pdf
(ch. 18)

I guess that mupdf's targets are windows/mac/Linux/Android but as a  base
tool (eg ebook reader make senses on Android).

License is AGPL
https://mupdf.com/license.html
like GPL plus
"""
Network Use – However, AGPL also has some conditions even if you are not
distributing the software. For example, if you are using the software on
your own company's equipment, but you are making the functionality of the
software available to users interacting with it remotely through a computer
network, and you make any change to the software, you must make the source
code for your changed version available to users of the software. Take care
to ensure that during network deployment that there is no code change that
could invoke the source code availability obligation. This special
requirement of AGPL is in Section 13; see the GNU web site for more details.

Bottom line, if you distribute our software, or make the functionality of
the software available to users interacting with it remotely through a
computer network, you must share your source code.
"""

and also the "Corresponding Source " subsection.


-- 
luigi
___
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
___

Re: [NTG-context] PDF viewer poll

[Benct Philip Jonsson]

On 2019-10-14 18:55, Marcin Borkowski wrote:

Hi,

I don't use ConTeXt anymore, but I still get the emails from the list,
and I quickly skimmed throught this thread to see if someone writes
about my pdf-viewer of choice - pdf-tools
(https://github.com/politza/pdf-tools).



I too don't use context anymore[^1] but I thought I should mention 
Zathura which is a good alternative if you like vi(m) and/or 
dislike/have trouble using a GUI.[^2].  The WP page (and `man zathura`) 
describes its capabilities well without me needing to type them. :-) 
They include synctex but I don't use it.




[^1]: I never really took off with context because I already know how to 
do 9 out of 10 tasks in LaTeX, and when I don't the info is much easier 
to find online. Sorry!


[^2]: I have a motor disability which makes pointing with a mouse 
difficult and point-dragging almost impossible.  That's the main reason 
I got into text-only/plaintext/non-gui workflows, but I keep on because 
I find them better.  Unfortunately when computer accessibility is 
discussed it is almost synonymous with vision disability accessibility, 
but there are other reasons for having trouble with GUIs.




On 2019-10-13, at 12:43, Henning Hraban Ramm  wrote:


Hi, I’d like to update my list of (usable!) PDF viewers.
Which one do you use? (Current version?)


pdf-tools (version 20190701.202)


What are its pros and cons?


cons:
- no "continuous display"/"double page" modes

pros:
- searchable (also with regexen), also grep-like (i.e., display all
lines containing some regex and jump to them easily)
- annotations/comments are viewable (and jumpable to) w/o using the
mouse
- fast
- runs within Emacs (not sure if this is a "pro" for everyone...)


Is it free (open source, freeware)?


yes (GPL3)


Does it work on Win/Lin/Mac?


GNU/Linux, maybe Mac


Does it have a localized interface? (I don’t care, but I work with
people who don’t understand a lot of English.)


No.


Can it handle comments, attachments?


Yes.


Can it handle forms with or without JavaScript?


AFAIK, no.


Does it support SyncTeX? (Who uses that anyway?)


Yes, and I do all the time!


Does it update changed PDFs on its own (or does it even block
overwriting)?


I guess it can be configured to do so (like Emacs in general)


Which other features are essential for your choice?


As I said - I don't have to leave Emacs.  Also, incremental or grep-like
searching with literal text or regexen are killer features.

Best,

--
Marcin Borkowski
http://mbork.pl
___
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
___



___
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
___

Re: [NTG-context] PDF viewer poll

[luigi scarso]

On Sun, Oct 13, 2019 at 12:43 PM Henning Hraban Ramm  wrote:

> Hi, I’d like to update my list of (usable!) PDF viewers.
>

A recent android tablet 10" with HD display is quite ok with Adobe Reader
and  several others apps ( eg foxit pdf reader)
EBookDroid is another app  pdf +djvu reader ,  also quite ok to read a pdf
on screen.

-- 
luigi
___
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
___

Re: [NTG-context] PDF viewer poll

[luigi scarso]

On Tue, Oct 15, 2019 at 10:21 AM Hans Hagen  wrote:

> > Most of my PDF debugging is done using 'mutool clean’ (especially with
> the -d switch) and textmate / diff.
> qpdf also has something like that (with comments of where the objects
> come from)


it's the qdf export : pdf -> qdf -> (edit qdf)  -> pdf


-- 
luigi
___
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
___

Re: [NTG-context] PDF viewer poll

[Hans Hagen]

On 10/15/2019 10:12 AM, Taco Hoekwater wrote:




On 15 Oct 2019, at 06:42, Henning Hraban Ramm  wrote:

Thank you all for you valuable insights so far!
I’ll compile them to a wiki page and also complete the list in my upcoming book.


Am 2019-10-14 um 11:17 schrieb Hans Hagen :

When developing pdf specific code (like last months) I do use acrobat reader 
and an older acrobat x (which keeps telling me that it wants to be updated but 
the update fails) ... both have their different issues. Acrobat X has some 
validation on board and one can introspect the file (and fonts) to some extend 
but in the end it's often still trial and error.


Do you know any other tools for PDF debugging? Those few I know of cost four to 
five figures or were plugins to very old versions of Acrobat


Most of my PDF debugging is done using 'mutool clean’ (especially with the -d 
switch) and textmate / diff.
qpdf also has something like that (with comments of where the objects 
come from) and using both tools in parallel can normally reveal issues


there are catches: for instance some tools don't really use the xref 
table but just run through the objects so finding issues in the xref 
(and compressed object tables) is a bitch but luckily it seldom needed


Hans

-
  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
___

Re: [NTG-context] PDF viewer poll

[Marcin Borkowski]

On 2019-10-15, at 06:42, Henning Hraban Ramm  wrote:

>> Basically javascript can be limited to (1) setting annotation properties, 
>> like toggling layers or button renditions, and (2) some simple calculations 
>> (for forms). Constructing pdf runtime using javascript is pretty braindead 
>> (use html instead then).
>
> D’accord.

Of course you are aware that limiting a powerful language is not an easy
task?

>> It is one of the puzzling areas to me: no problem in browsers and elsewhere 
>> but not in open source pdf viewers. It's not the most complex stuff so it 
>> probably indicates that no one cares much about these features.
>
> I wouldn’t say "no problem", because JS causes security problems everywhere.

It's not JS that causes problems.  Any other (powerful enough) language
not specifically designed with browser environment in mind could be
problematic here.  I guess that having Perl, Python or Ruby instead of
JS would create a similar set of problems.  (Lua might be an exception
due to its design and a possibility to whitelist functions for eval,
AFAIR.)

Just 2 cents from a JS programmer who actually thinks that JS is not the
worst Lisp dialect out there.

Best,

--
Marcin Borkowski
http://mbork.pl
___
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
___

Re: [NTG-context] PDF viewer poll

[Marcin Borkowski]

Hi,

I don't use ConTeXt anymore, but I still get the emails from the list,
and I quickly skimmed throught this thread to see if someone writes
about my pdf-viewer of choice - pdf-tools
(https://github.com/politza/pdf-tools).

On 2019-10-13, at 12:43, Henning Hraban Ramm  wrote:

> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)

pdf-tools (version 20190701.202)

> What are its pros and cons?

cons:
- no "continuous display"/"double page" modes

pros:
- searchable (also with regexen), also grep-like (i.e., display all
lines containing some regex and jump to them easily)
- annotations/comments are viewable (and jumpable to) w/o using the
mouse
- fast
- runs within Emacs (not sure if this is a "pro" for everyone...)

> Is it free (open source, freeware)?

yes (GPL3)

> Does it work on Win/Lin/Mac?

GNU/Linux, maybe Mac

> Does it have a localized interface? (I don’t care, but I work with
> people who don’t understand a lot of English.)

No.

> Can it handle comments, attachments?

Yes.

> Can it handle forms with or without JavaScript?

AFAIK, no.

> Does it support SyncTeX? (Who uses that anyway?)

Yes, and I do all the time!

> Does it update changed PDFs on its own (or does it even block
> overwriting)?

I guess it can be configured to do so (like Emacs in general)

> Which other features are essential for your choice?

As I said - I don't have to leave Emacs.  Also, incremental or grep-like
searching with literal text or regexen are killer features.

Best,

--
Marcin Borkowski
http://mbork.pl
___
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
___

Re: [NTG-context] PDF viewer poll

[Taco Hoekwater]

> On 15 Oct 2019, at 06:42, Henning Hraban Ramm  wrote:
> 
> Thank you all for you valuable insights so far!
> I’ll compile them to a wiki page and also complete the list in my upcoming 
> book.
> 
>> Am 2019-10-14 um 11:17 schrieb Hans Hagen :
>> 
>> When developing pdf specific code (like last months) I do use acrobat reader 
>> and an older acrobat x (which keeps telling me that it wants to be updated 
>> but the update fails) ... both have their different issues. Acrobat X has 
>> some validation on board and one can introspect the file (and fonts) to some 
>> extend but in the end it's often still trial and error.
> 
> Do you know any other tools for PDF debugging? Those few I know of cost four 
> to five figures or were plugins to very old versions of Acrobat

Most of my PDF debugging is done using 'mutool clean’ (especially with the -d 
switch) and textmate / diff.

Best wishes,
Taco


___
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
___

Re: [NTG-context] PDF viewer poll

[Hans Hagen]

On 10/15/2019 6:42 AM, Henning Hraban Ramm wrote:


Do you know any other tools for PDF debugging? Those few I know of cost four to 
five figures or were plugins to very old versions of Acrobat.


normally i trust my eyes and mind and 'standard' ... if it really get 
hairy there are a few folks one can ask for a second opinion



Acrobat used to be ok upto version 6 (I even remember the msdos version to be 
ok) but each version the user interface changed fo rthe worse  (very bad imo 
and an indication that it's not meant for power usage as there one wants at 
least an upward compatible interface) and it's slower compared to other viewers 
(probably due to color management).


I agree. Adobe needlessly changed the interface with every release, and it 
didn’t get better.
There were different translation errors (at least in the German interface) in 
every version, and they never got fixed with the updates.
Updates were announced by the Updater, but never installed.
Don’t know about the speed – some functions like certificate lookup were always 
dead slow, and the display speed was mostly ok. (I should benchmark different 
viewers with my OpenStreetMap vector maps…)


speed is ok, but when using acrobat one has to close/open which takes 
time (and then go to the right spot again)



I found Qoppa’s PDF Studio Pro a viable alternative to Acrobat Pro with a 
usable interface (default has ribbons, but you can switch it).
Their customer support is friendly, I hope they will also fix the problems I 
reported.


i must admit that i never used these alternatives (and i'm not going to 
spend money on programs just for testing)



=== javascript ===
Only acrobat offers that.


Not completely true. But there aren’t a lot of apps that support JS in PDF - for a reason: if you 
allow scripting, you create a lot of vulnerabilities that you can easily avoid leaving out this 
feature that "nobody" needs. It would have made sense to define a small and safe JS (or 
whatever scripting language) _subset_ from the start, but the early versions of Acrobat were 
completely "hackable", and they only much later thought about security (like in lots of 
other programs). PDF viruses existed.


i always wondered why they added all those 'editing features' ... the 
hold plugging was also kind of random



Basically javascript can be limited to (1) setting annotation properties, like 
toggling layers or button renditions, and (2) some simple calculations (for 
forms). Constructing pdf runtime using javascript is pretty braindead (use html 
instead then).


D’accord.


It is one of the puzzling areas to me: no problem in browsers and elsewhere but 
not in open source pdf viewers. It's not the most complex stuff so it probably 
indicates that no one cares much about these features.


I wouldn’t say "no problem", because JS causes security problems everywhere.


Depends: enabling a layer? checking a value in a field? turning a button 
appearance on / off? Only lousy programing can make that buggy. A 
reasonable subsset can be made pretty robust. Launching a video is also 
quite harmless.



=== annotations ===

Some useful stuff was dropped: like native sound and movies (was very simple: 
show a movie, play a sound, simple annotations). What seems to be natural to 
html became complex and unuseable in pdf ... the media subsystem is (obsolete) 
flash based, imo mostly driven by third party commercial pressure / demand / 
whatever. Not future safe, if working at all: from simple to complex to useless.


If I remember correctly, Adobe first based the media subsystem on Apple’s 
Quicktime until Apple discontinued that on Windows and Adobe bought Macromedia, 
including Flash. 3D media was a short hype, nobody used it. Anyway, doesn’t 
matter. Nowadays PDF doesn’t have any working media subsystem.


indeed. but just supporting mp3, flac and mp4 and maybe a few video 
formats would be enough ... i guess that there are plenty of libs out 
they that they vould use (but instead they went for flash and flash 
driven controls and pretty complex 3d stuff)



In a similar fashion forms (for some widgets bugs because features esp default 
rendering, inheritance, etc and also some strange relation with viewer 
settings, that change per version). It made me loose interest it those things 
that once were promising.


I can understand that, but at least ConTeXt’s radiobuttons *have* bugs; the few 
viewers that support forms stumble over some parsing/nesting error. Adobe 
catches it apparently.


they don't catch all (differs per version which is why the code changed 
over time) ... much has to do with appearances (mostly dingbat driven in 
acrobat itself, but we want different things, possible per standard, but 
these all have timing and initialization issues and some even have 
pseudo documented issues with what happens when a page opens ... i 
presume it works with their own tools but then these can impose 
limitations that texies never would like



(Some 

Re: [NTG-context] PDF viewer poll

[Otared Kavian]

> On 13 Oct 2019, at 12:43, Henning Hraban Ramm  wrote:
> 
> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)

Hi Hraban,

I am on MacOS and use the PDF viewer included in TeXShop (which is based on 
Preview.app of MacOS). For my presentations I use Adobe Acrobat Reader DC, but 
for readings on the screen the Preview.app of MacOS is just fine (one can also 
annotate a PDF file, but strangely when such files are used in ConTeXt the 
annotations disappear: so one has to transform them into a JPG then again into 
a PDF).

I use extensively synctex within TeXShop, and although there has been a split 
in the way synctex is implemented in ConTeXt and other TeX flavors, it works 
fine. When writing lecture notes and math exercises, having synctex is 
fundamental for me.

Best regards: OK
___
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
___

Re: [NTG-context] PDF viewer poll

[Hamid,Idris]

Hi Henning, all,

On Sun, 13 Oct 2019 04:43:14 -0600, Henning Hraban Ramm   
wrote:

> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)
> What are its pros and cons?
> Is it free (open source, freeware)?
> Does it work on Win/Lin/Mac?
> Does it have a localized interface? (I don’t care, but I work with  
> people who don’t understand a lot of English.)
> Can it handle comments, attachments?
> Can it handle forms with or without JavaScript?
> Does it support SyncTeX? (Who uses that anyway?)
> Does it update changed PDFs on its own (or does it even block  
> overwriting)?
> Which other features are essential for your choice?
>
> E.g. I’m working with:
> - Preview.app (Mac)
>   Default on MacOS, fast & easy. No JS, bad forms support, updates  
> "sometimes". Usable as a previewer, not as a PDF toolbox.
> - Adobe Reader DC (Mac)
>   I use it only to check forms or as reference. Unusable GUI.
> - Acrobat Pro 9 (Mac)
>   Was my workhorse, but works on MacOS Mojave only partly; slow &  
> crash-prone; no updates. Can check PDF/X<4 and convert colors.
> - PDF Studio Pro (on Mac & Linux)
>   Bought to replace AcroPro9; JS support broken; slow startup; no  
> updates. Can check PDF/X, A, UA and convert colors.
>   Ok with forms, but doesn’t support LiveCycle forms (deprecated, but  
> used by German boards).
> - Qpdfview (Linux)
>   Fast and easy; reliably updates.
> - PDF.js (Browser or Atom)
>   Is said to do SyncTeX (never tried). Easy, but slow. Updates.

On Windows:

For a ConTeXt workflow, sumatrapdf, for all the reasons mentioned by Hans  
and others. Works well with SyncTeX and Notepad++.

As a commercial replacement to Adobe Acroboat, nothing beats NitroPDF.  
Clean interface. Avoids most if not all of the problems mentioned by Hans.

University machine has Acrobat, so for pdf manipulation beyond the  
capabilities of sumatrapdf: mostly Acrobat at school and NitroPDF at home.

Best wishes
Idris
-- 
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512
___
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
___

Re: [NTG-context] PDF viewer poll

[Henning Hraban Ramm]

Thank you all for you valuable insights so far!
I’ll compile them to a wiki page and also complete the list in my upcoming book.

> Am 2019-10-14 um 11:17 schrieb Hans Hagen :
> 
> When developing pdf specific code (like last months) I do use acrobat reader 
> and an older acrobat x (which keeps telling me that it wants to be updated 
> but the update fails) ... both have their different issues. Acrobat X has 
> some validation on board and one can introspect the file (and fonts) to some 
> extend but in the end it's often still trial and error.

Do you know any other tools for PDF debugging? Those few I know of cost four to 
five figures or were plugins to very old versions of Acrobat.


> On the commandline, when I need to check a pdf I sometimes use qpf (quite ok 
> but I always need to stepwise build the commandline using help as it's 
> somewhat complex). The other command line tool I use is mutool (mudraw) which 
> is different but also ok.

Need to look into those.


> Acrobat used to be ok upto version 6 (I even remember the msdos version to be 
> ok) but each version the user interface changed fo rthe worse  (very bad imo 
> and an indication that it's not meant for power usage as there one wants at 
> least an upward compatible interface) and it's slower compared to other 
> viewers (probably due to color management).

I agree. Adobe needlessly changed the interface with every release, and it 
didn’t get better.
There were different translation errors (at least in the German interface) in 
every version, and they never got fixed with the updates.
Updates were announced by the Updater, but never installed.
Don’t know about the speed – some functions like certificate lookup were always 
dead slow, and the display speed was mostly ok. (I should benchmark different 
viewers with my OpenStreetMap vector maps…)

I found Qoppa’s PDF Studio Pro a viable alternative to Acrobat Pro with a 
usable interface (default has ribbons, but you can switch it).
Their customer support is friendly, I hope they will also fix the problems I 
reported.

> === javascript ===
> Only acrobat offers that.

Not completely true. But there aren’t a lot of apps that support JS in PDF - 
for a reason: if you allow scripting, you create a lot of vulnerabilities that 
you can easily avoid leaving out this feature that "nobody" needs. It would 
have made sense to define a small and safe JS (or whatever scripting language) 
_subset_ from the start, but the early versions of Acrobat were completely 
"hackable", and they only much later thought about security (like in lots of 
other programs). PDF viruses existed.

> Basically javascript can be limited to (1) setting annotation properties, 
> like toggling layers or button renditions, and (2) some simple calculations 
> (for forms). Constructing pdf runtime using javascript is pretty braindead 
> (use html instead then).

D’accord.

> It is one of the puzzling areas to me: no problem in browsers and elsewhere 
> but not in open source pdf viewers. It's not the most complex stuff so it 
> probably indicates that no one cares much about these features.

I wouldn’t say "no problem", because JS causes security problems everywhere.

> === annotations ===
> 
> Some useful stuff was dropped: like native sound and movies (was very simple: 
> show a movie, play a sound, simple annotations). What seems to be natural to 
> html became complex and unuseable in pdf ... the media subsystem is 
> (obsolete) flash based, imo mostly driven by third party commercial pressure 
> / demand / whatever. Not future safe, if working at all: from simple to 
> complex to useless. 

If I remember correctly, Adobe first based the media subsystem on Apple’s 
Quicktime until Apple discontinued that on Windows and Adobe bought Macromedia, 
including Flash. 3D media was a short hype, nobody used it. Anyway, doesn’t 
matter. Nowadays PDF doesn’t have any working media subsystem.

> In a similar fashion forms (for some widgets bugs because features esp 
> default rendering, inheritance, etc and also some strange relation with 
> viewer settings, that change per version). It made me loose interest it those 
> things that once were promising.

I can understand that, but at least ConTeXt’s radiobuttons *have* bugs; the few 
viewers that support forms stumble over some parsing/nesting error. Adobe 
catches it apparently.

> (Some of the bad in pdf is a result from it being a container format for a 
> lot of things: documents, editing tools, printing, application stuff turned 
> annotation, etc.).

D’accord.


Herzliche Grüße,
Hraban


___
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 : 

Re: [NTG-context] PDF viewer poll

[Alan Braslau]

On Sun, 13 Oct 2019 12:43:14 +0200
Henning Hraban Ramm  wrote:

> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)

On Mac OS, there is skim, which has better features than preview but uses the 
same Apple rendering engine (with all of its bugs).

zathura (many systems) can use either the mupdf or the poppler engine. Your 
choice.

mupdf-gl on MacOS doesn't need X11, but it has some annoying bugs that might 
get fixed ... someday.

But, as Hans says, it should not be too hard to build a mupdf-engine based 
lightweight viewer with lua integrated. Or why not add this to lua-bloat-tex as 
an output option? That way, one can interpret (xml) source files with on the 
fly rendering.

Alan
___
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
___

Re: [NTG-context] PDF viewer poll

[Greedwolf DSS]

Henning Hraban Ramm  writes:

pdf-tools in Emacs is well.
___
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
___

Re: [NTG-context] PDF viewer poll

[Hans Hagen]

On 10/13/2019 12:43 PM, Henning Hraban Ramm wrote:

Hi, I’d like to update my list of (usable!) PDF viewers.
Which one do you use? (Current version?)
What are its pros and cons?
Is it free (open source, freeware)?
Does it work on Win/Lin/Mac?
Does it have a localized interface? (I don’t care, but I work with people who 
don’t understand a lot of English.)
Can it handle comments, attachments?
Can it handle forms with or without JavaScript?
Does it support SyncTeX? (Who uses that anyway?)
Does it update changed PDFs on its own (or does it even block overwriting)?
Which other features are essential for your choice?

E.g. I’m working with:
- Preview.app (Mac)
   Default on MacOS, fast & easy. No JS, bad forms support, updates 
"sometimes". Usable as a previewer, not as a PDF toolbox.
- Adobe Reader DC (Mac)
   I use it only to check forms or as reference. Unusable GUI.
- Acrobat Pro 9 (Mac)
   Was my workhorse, but works on MacOS Mojave only partly; slow & crash-prone; no 
updates. Can check PDF/X<4 and convert colors.
- PDF Studio Pro (on Mac & Linux)
   Bought to replace AcroPro9; JS support broken; slow startup; no updates. Can 
check PDF/X, A, UA and convert colors.
   Ok with forms, but doesn’t support LiveCycle forms (deprecated, but used by 
German boards).
- Qpdfview (Linux)
   Fast and easy; reliably updates.
- PDF.js (Browser or Atom)
   Is said to do SyncTeX (never tried). Easy, but slow. Updates.

=== viewing ===

99% of the time i use the mupdf based sumatrappdf (which has not been 
updated for a while, not that it seems to matter much)


I also occasionally use the gui that comes with mupdf but it is limited 
(no bookview for instance; if that was there + printing I'd use it more 
often) ... mupdf started simple but I think it also grew in a weird 
direction (large codebase, some reflow I think, a strange epub 
substandard support, etc .. all pretty useless to me and I'm not sure 
how optional it it ... so no longer as lightweight as it could be ...)


When developing pdf specific code (like last months) I do use acrobat 
reader and an older acrobat x (which keeps telling me that it wants to 
be updated but the update fails) ... both have their different issues. 
Acrobat X has some validation on board and one can introspect the file 
(and fonts) to some extend but in the end it's often still trial and error.


It's no problem keeping sumatrapdf open when processing a file, it even 
goes to the same spot (if possible). Acrobat is cumbersome (I can 
understand why it was the case when mem was low as some caching happens.)


(When browsing and opening a pdf chrome uses the built-in, firefox the 
reader and edge the build in. Last time I checked edge was the best in 
that.)


I have okular installed but I think what i installed is too old by now. 
When it comes to for instance cut and paste (testing) I think open 
source viewers never catched on (and there has been plenty of time to do 
it). I sometimes suspect build-in fixes (heuristics) for situations but 
i might be wrong in that. Ok, it's volunteers work, so no complaints; 
and I can use mupdf quite well.


=== checking ===

On the commandline, when I need to check a pdf I sometimes use qpf 
(quite ok but I always need to stepwise build the commandline using help 
as it's somewhat complex). The other command line tool I use is mutool 
(mudraw) which is different but also ok.


=== verdict ===

In general I think that mupdf has the best viewer code, and qpdf the 
best commandline stuff (no viewing code). Acrobat used to be ok upto 
version 6 (I even remember the msdos version to be ok) but each version 
the user interface changed fo rthe worse  (very bad imo and an 
indication that it's not meant for power usage as there one wants at 
least an upward compatible interface) and it's slower compared to other 
viewers (probably due to color management). With acrobat moving to the 
cloud and with all these sharing and validation and security stuff built 
it became kind of unuseable for every day use. It demonstrates that one 
cannot easilly mix a commercial product with a general 'standadized' 
format vor document distribution (I'm not even sure if there has been a 
long term agenda involved). I'm not going to lock into some subscription 
model for something that i hardly use (Do they really expect people to 
subscribe when their employer is not paying for it? If one retires then 
...). I have no problem paying for something but it has to be in 
proportion (and on the average everything pdf has cost us more than in 
brought in).


=== synctex ===

I don't use it myself. I think that it being a library that has to be 
linked in is a bad design decision: it could have been a call to an 
external program that gets the filename + page and position and then 
returns the source file and line. That way it would a future proof 
system with no dependencies. There could a way better feedback then too. 
(Context already ships a script that does that.) Not all 

Re: [NTG-context] PDF viewer poll

[Taco Hoekwater]

Hi,

> On 13 Oct 2019, at 12:43, Henning Hraban Ramm  wrote:
> 
> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)

Preview.App (Mac) — since it is fast and the MacOS default. But it does
  not handle anything well except the actual page display. 

  Auto-refreshes, but only if the pdf update is finished when you switch 
  back to the preview window. If the pdf is still being updated then, it 
  produces an error and refuses to update any more after that. That is 
  really annoying, which is why I am trying to switch to:

mupdf-gl — trying to get used to that, but it is not an actual application
  according to MacOS, so it only works from the command-line in Terminal.
  Not sure about features, but it is fast. I should create a wrapper app
  script so I can use it more often.

  Refreshes with Cmd-R (and SIGHUP, since 1.15), but not automatically. 
  mostly keyboard-driven, which works fine for me but may be a negative 
  for other users.

Acrobat Reader DC — but only if I really have to because of 
forms/js/attachments/etc.
  I do not object to commercial software, but I think the newer Adobe Apps are 
  horrible in use. The last one with a ‘sane’ interface was version 9.0 or so.

I only really care about (speed of) page display; I normally don’t need the 
interactive stuff. I never use synctex since most of my docs are quite short. 
No idea what pdf view supports it (and does it not need editor support as well?
no idea what editors support it, either).

Best wishes,
Taco
___
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
___

Re: [NTG-context] PDF viewer poll

[denis.maier]

SumtraPDF on Windows
Easy, fast, quite basic. (I take this as an advantage)
Interface is localized.
Forms: don't know
Free
Synctex: Don't need it at the moment, but the documentation says it should be 
supported
Updates automatically

Hope this helps,
Denis



-Ursprüngliche Nachricht-
Von: ntg-context  Im Auftrag von Henning Hraban Ramm
Gesendet: Sonntag, 13. Oktober 2019 12:43
An: mailing list for ConTeXt users 
Betreff: [NTG-context] PDF viewer poll

Hi, I’d like to update my list of (usable!) PDF viewers.
Which one do you use? (Current version?) What are its pros and cons?
Is it free (open source, freeware)?
Does it work on Win/Lin/Mac?
Does it have a localized interface? (I don’t care, but I work with people who 
don’t understand a lot of English.) Can it handle comments, attachments?
Can it handle forms with or without JavaScript?
Does it support SyncTeX? (Who uses that anyway?) Does it update changed PDFs on 
its own (or does it even block overwriting)?
Which other features are essential for your choice?

E.g. I’m working with:
- Preview.app (Mac)
  Default on MacOS, fast & easy. No JS, bad forms support, updates "sometimes". 
Usable as a previewer, not as a PDF toolbox.
- Adobe Reader DC (Mac)
  I use it only to check forms or as reference. Unusable GUI.
- Acrobat Pro 9 (Mac)
  Was my workhorse, but works on MacOS Mojave only partly; slow & crash-prone; 
no updates. Can check PDF/X<4 and convert colors.
- PDF Studio Pro (on Mac & Linux)
  Bought to replace AcroPro9; JS support broken; slow startup; no updates. Can 
check PDF/X, A, UA and convert colors.
  Ok with forms, but doesn’t support LiveCycle forms (deprecated, but used by 
German boards).
- Qpdfview (Linux)
  Fast and easy; reliably updates.
- PDF.js (Browser or Atom)
  Is said to do SyncTeX (never tried). Easy, but slow. Updates.


Curious: Hraban
___
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
___

___
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
___

Re: [NTG-context] PDF viewer poll

[Hans Åberg]

> On 13 Oct 2019, at 12:43, Henning Hraban Ramm  wrote:
> 
> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)

There is TeXShop that comes with the Mac TeX Live distribution. It can be set 
up to compile ConTeXt.

> What are its pros and cons?

You might let us know, if you so will. :-)


___
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
___

Re: [NTG-context] PDF viewer poll

[Damien Thiriet]

Hello,


I am using SumatraPDF at school (Windows). Lightweight, opens where it
was closed last time (very convenient when you've got presentations up
to 100 slides or more that takes several weeks to be discussed). Self
actualizes when the ConTeXt source is compiled.

At home (OpenBSD), mupdf and zathura. Rather for ratpoisons or Vim fans
(keyboard-driven).

Regards,


Damien Thiriet
___
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
___

Re: [NTG-context] PDF viewer poll

[kaddour kardio]

- Okular v1.8.1 on my linux machines.
- SumatraPDF on windows at work (that never use for my ConTeXT related work)

Le dim. 13 oct. 2019 à 17:49, Pablo Rodriguez  a écrit :

> On 10/13/19 12:43 PM, Henning Hraban Ramm wrote:
> > Hi, I’d like to update my list of (usable!) PDF viewers.
>
> 1. Evince-3.28.5, MuPDF-1.16.1 and (sometimes) acroread-9.5.5 on Linux.
> 2. SumatraPDF, MuPDF and Acrobat Reader DC on Windows.
>
> From MuPDF, I use mupdf-gl (just in case it might be relevant).
>
> They are zero cost programs. Except Acrobat, all of them are FLOSS.
>
> SumatraPDF is Windows only.
> mupdf runs on Linux, Windows, Android and iOS.
>
> mupdf has an English-only help. All the other programs have localized
> interfaces.
>
> Evince can handle comments and attachments.
> mupdf can handle comments, but not attachments.
> Sumatra cannot handle comments, but it does handle embedded files.
>
> Evince can handle forms without JS (support is on the way).
> mupdf can handle forms with JS (but I would say that JS support in MuPDF
> is incomplete).
> SumatraPDF cannot handle forms.
>
> I don’t use SyncTeX myself, so I don’t know whether it is supported or not.
>
> Evince and SumatraPDF reload modified documents automatically.
> mupdf-gl allows document reloading with the 'r' key.
>
> My basic features are bookmarks, links and attachments. Evince and
> SumatraPDF can handle all of them. mupdf-gl cannot handle attachments
> and partial implementation for bookmarks.
>
> Just in case it helps,
>
> Pablo
> --
> http://www.ousia.tk
>
> ___
> 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
>
> ___
>


-- 
Dr YAHYAOUI Mohamed Kaddour, cardiologue  .
___
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
___

Re: [NTG-context] PDF viewer poll

[Pablo Rodriguez]

On 10/13/19 12:43 PM, Henning Hraban Ramm wrote:
> Hi, I’d like to update my list of (usable!) PDF viewers.

1. Evince-3.28.5, MuPDF-1.16.1 and (sometimes) acroread-9.5.5 on Linux.
2. SumatraPDF, MuPDF and Acrobat Reader DC on Windows.

From MuPDF, I use mupdf-gl (just in case it might be relevant).

They are zero cost programs. Except Acrobat, all of them are FLOSS.

SumatraPDF is Windows only.
mupdf runs on Linux, Windows, Android and iOS.

mupdf has an English-only help. All the other programs have localized
interfaces.

Evince can handle comments and attachments.
mupdf can handle comments, but not attachments.
Sumatra cannot handle comments, but it does handle embedded files.

Evince can handle forms without JS (support is on the way).
mupdf can handle forms with JS (but I would say that JS support in MuPDF
is incomplete).
SumatraPDF cannot handle forms.

I don’t use SyncTeX myself, so I don’t know whether it is supported or not.

Evince and SumatraPDF reload modified documents automatically.
mupdf-gl allows document reloading with the 'r' key.

My basic features are bookmarks, links and attachments. Evince and
SumatraPDF can handle all of them. mupdf-gl cannot handle attachments
and partial implementation for bookmarks.

Just in case it helps,

Pablo
--
http://www.ousia.tk
___
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
___

Re: [NTG-context] PDF viewer poll

[Pablo Rodriguez]

On 10/13/19 5:26 PM, Henning Hraban Ramm wrote:
> [...]
> xpdf I found a bit too basic for my taste. And it’s also based on
> poppler nowadays, like Qpdfview and several others.
Hi Hraban,

just for the record, poppler is a fork of xpdf-3 (from
https://poppler.freedesktop.org/).

Pablo
--
http://www.ousia.tk
___
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
___

Re: [NTG-context] PDF viewer poll

[Henning Hraban Ramm]

> Am 2019-10-13 um 16:50 schrieb Rudolf Bahr :
> 
> Hello Hraban,
> 
> I'm working with only 2 pdf-viewers, "okular" and "xpdf". My main-viewer is 
> "okular", but
> at the moment it doesn't work with my context-pdfs, I don't know why, but I 
> don't care.
> Then it's good to have "xpdf" which is simpler than "okular" but works 
> especially in
> this case. And before sending pdf-data to a printing-house I use "qpdf" not 
> to view,
> but to transform my pdf files as rotate them to get them binded at a book 
> side not
> offered by printers.
> 
> All 3 programs are open source on Linux and because I'm updating regularly my 
> OS, those
> programs are regularly updated too.
> JS? Form support? PDF/X/A/UA? Convert colors? SyncTex? Handle comments? I'm 
> not using
> any of these. To some of them I can't say anything, because I dont't even 
> know, what they
> are good for. So, I'm sorry not to be able to say more to those possible 
> properties
> of my used programs:

Thank you!

xpdf I found a bit too basic for my taste. And it’s also based on poppler 
nowadays, like Qpdfview and several others.

Of course there are a lot of features that one could compare, e.g. presentation 
control or printing options.

Since I regularly need to send pdfs to the printers, I need to check if they 
will print correctly. That’s what PDF/X is for. Often it’s easier to convert 
colors in the PDF instead of finding and converting the elements separately. (I 
don’t convert RGB to CMYK, printshop workflows can handle this, but e.g. 
ensuring everything’s grayscale can save costs in digital printing. And 
sometimes I get logos in spot colors...)

I never used SyncTeX myself, but I guess it would make my correction workflows 
easier. And I usually get corrections as comments in PDFs.

Forms support I usually need only to fill in some official forms, but I got one 
customer with a ConTeXt-set form of >30 pages…
And that’s one area where ConTeXt is a bit buggy (e.g. radiobuttons don’t 
work), and I’d like to debug that.

I was only asking for "current version", because some folks still use acroread 
on Linux, and that was last updated in 2005 (I think), and some other readers 
aren’t updated any more, e.g. Nitro.


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
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
___

Re: [NTG-context] PDF viewer poll

[Rudolf Bahr]

On Sun, Oct 13, 2019 at 12:43:14PM +0200, Henning Hraban Ramm wrote:

> Hi, I’d like to update my list of (usable!) PDF viewers.
> Which one do you use? (Current version?)
> What are its pros and cons?
> Is it free (open source, freeware)?
> Does it work on Win/Lin/Mac?
> Does it have a localized interface? (I don’t care, but I work with people who 
> don’t understand a lot of English.)
> Can it handle comments, attachments?
> Can it handle forms with or without JavaScript?
> Does it support SyncTeX? (Who uses that anyway?)
> Does it update changed PDFs on its own (or does it even block overwriting)?
> Which other features are essential for your choice?
> 
> E.g. I’m working with:
> - Preview.app (Mac)
>   Default on MacOS, fast & easy. No JS, bad forms support, updates 
> "sometimes". Usable as a previewer, not as a PDF toolbox.
> - Adobe Reader DC (Mac)
>   I use it only to check forms or as reference. Unusable GUI.
> - Acrobat Pro 9 (Mac)
>   Was my workhorse, but works on MacOS Mojave only partly; slow & 
> crash-prone; no updates. Can check PDF/X<4 and convert colors.
> - PDF Studio Pro (on Mac & Linux)
>   Bought to replace AcroPro9; JS support broken; slow startup; no updates. 
> Can check PDF/X, A, UA and convert colors.
>   Ok with forms, but doesn’t support LiveCycle forms (deprecated, but used by 
> German boards).
> - Qpdfview (Linux)
>   Fast and easy; reliably updates.
> - PDF.js (Browser or Atom)
>   Is said to do SyncTeX (never tried). Easy, but slow. Updates.
> 
> 
> Curious: Hraban


Hello Hraban,

I'm working with only 2 pdf-viewers, "okular" and "xpdf". My main-viewer is 
"okular", but
at the moment it doesn't work with my context-pdfs, I don't know why, but I 
don't care.
Then it's good to have "xpdf" which is simpler than "okular" but works 
especially in
this case. And before sending pdf-data to a printing-house I use "qpdf" not to 
view,
but to transform my pdf files as rotate them to get them binded at a book side 
not
offered by printers.

All 3 programs are open source on Linux and because I'm updating regularly my 
OS, those
programs are regularly updated too.
JS? Form support? PDF/X/A/UA? Convert colors? SyncTex? Handle comments? I'm not 
using
any of these. To some of them I can't say anything, because I dont't even know, 
what they
are good for. So, I'm sorry not to be able to say more to those possible 
properties
of my used programs:

"okular": 
version: 1.6.3
Manual in German

"xpdf":
version: 3.04
Manual in English

"qpdf":
version: 8.4.0
Manual in English

Best wishes,

Rudolf
___
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
___

Re: [NTG-context] PDF Viewer Navigation Tree

[Kip Warner]

On Sat, 2011-06-18 at 06:18 +0200, Wolfgang Schuster wrote:
 When you use a environment file put all setups in it. When you have only
 one product you dont need a project file because you can load the environment
 file from the product and component files.
 
 Wolfgang

Thanks Wolfgang. For some reason, and I have absolutely no idea why, the
index is showing today and I can't recall what I had changed. Oh well,
as Scotty said, if it ain't broke, don't fix it.

I'll also merge the project / product files together into one as you
suggested.

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com


signature.asc
Description: This is a digitally signed message part
___
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
___

Re: [NTG-context] PDF Viewer Navigation Tree

[Kip Warner]

luigi scarso luigi.scarso at gmail.com writes:
 pdfbookmarks ?
 http://wiki.contextgarden.net/PDF_Bookmarks_and_Headers


Hey Luigi. The sample code in the link you gave me works fine if I compile it.
If I put it in my own book, should the adjusted code be in the environment,
project, or product file? I have only one project / product.

Kip

___
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
___

Re: [NTG-context] PDF Viewer Navigation Tree

[Wolfgang Schuster]

Am 18.06.2011 um 03:43 schrieb Kip Warner:

 luigi scarso luigi.scarso at gmail.com writes:
 pdfbookmarks ?
 http://wiki.contextgarden.net/PDF_Bookmarks_and_Headers
 
 Hey Luigi. The sample code in the link you gave me works fine if I compile it.
 If I put it in my own book, should the adjusted code be in the environment,
 project, or product file? I have only one project / product.

When you use a environment file put all setups in it. When you have only
one product you don’t need a project file because you can load the environment
file from the product and component files.

Wolfgang

___
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
___

Re: [NTG-context] PDF Viewer Navigation Tree

[Yury G. Kudryashov]

Kip Warner wrote:

 Hey folks,
 
 I'm not sure where to be looking, as this may well be a feature already
 implemented in ConTeXt or its lower level dependencies. I couldn't find
 anything in the mailing archives, nor in the reference manual or wiki.
 
 In my PDF viewer Evince, I have a navigation tree in the side bar that
 allows me quick access to various parts of some PDF documents. When I
 was using Texinfo, this was generated automatically for each @chapter /
 @section / @subsection / etc when the PDF was being written out. I
 noticed this doesn't appear to happen automatically with ConTeXt.
 
 How does one go about doing the same in ConTeXt?
 
Try \setupinteraction[state=start].

___
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
___

Re: [NTG-context] PDF Viewer Navigation Tree

[luigi scarso]

On Thu, Jun 16, 2011 at 1:51 AM, Kip Warner k...@thevertigo.com wrote:
 Hey folks,

 I'm not sure where to be looking, as this may well be a feature already
 implemented in ConTeXt or its lower level dependencies. I couldn't find
 anything in the mailing archives, nor in the reference manual or wiki.

 In my PDF viewer Evince, I have a navigation tree in the side bar that
 allows me quick access to various parts of some PDF documents. When I
 was using Texinfo, this was generated automatically for each @chapter /
 @section / @subsection / etc when the PDF was being written out. I
 noticed this doesn't appear to happen automatically with ConTeXt.

 How does one go about doing the same in ConTeXt?
pdfbookmarks ?
http://wiki.contextgarden.net/PDF_Bookmarks_and_Headers
-- 
luigi
___
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
___