From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: "Michal Vlasák" <lahcim8@gmail.com>,
"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Multimedia, PDF and ConTeXt
Date: Tue, 27 Jul 2021 15:21:05 +0200 [thread overview]
Message-ID: <ca7b1a17-a7ce-89ff-8d1b-695a7a61a91a@xs4all.nl> (raw)
In-Reply-To: <CD3VSBQEQKT8.2VLW23KXZIC3Y@phobos>
On 7/27/2021 1:20 PM, Michal Vlasák wrote:
> I thought that recent Edge versions used Chrome's PDFium, as you say
> with some additions (like drawing). I would have to double check that.
yes but i think with their own additions (not sure about the pdf stuff)
i do notice differences in printing so maybe that part is also different
> My understanding is that U3D was the first thing they designed. It is
> standardised by ECMA, so freely available. Then they came up with PRC,
> which should be more space efficient IIRC. It is standardized by ISO, so
> it is open, but not free.
>
> Both formats seemed to worked fine in Acrobat and Foxit and I don't see
> that changing soon.
>
> Both have some writing support in open source tools - meshlab supports
> U3D export with https://github.com/ningfei/u3d, and Asymptote supports
> PRC export. Although I didn't get either to quite work and used export
> from Autodesk Inventor instead for my tests.
ok, so that might stay
> Not fully official, but it is only logical that they need a compatibility
> layer for old documents. But, Adobe employee mentionts the use of OS Player
> for these Flash using documents here:
>
> https://community.adobe.com/t5/acrobat-reader/playing-embedded-video-without-flash/td-p/11266205/page/2
ok
> Do you mean table summarizing what parts of the Acrobat JavaScript API
> is supported in individual viewers?
>
> There is a separate API for normal things:
>
> https://opensource.adobe.com/dc-acrobat-sdk-docs/acrobatsdk/pdfs/acrobatsdk_jsapiref.pdf
ok
> Do you mean existing PDFs that work in viewers or ConTeXt source files
> that use these features? I can provide both.
good
> I am not sure what you mean by "small set of files for media".
proper freely distributable test files
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-07-27 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 22:49 Michal Vlasák via ntg-context
2021-07-27 6:54 ` Hans Hagen via ntg-context
2021-07-27 11:20 ` Michal Vlasák via ntg-context
2021-07-27 13:21 ` Hans Hagen via ntg-context [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca7b1a17-a7ce-89ff-8d1b-695a7a61a91a@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=lahcim8@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).