Re: [NTG-context] No menu bar option for Adobe Reader

2019-05-01 Thread Paul Schalck
I have just tested the latest beta (2019-04-29). The new option works as 
expected in both Acrobat Reader 11 and DC. Thanks again.

Paul
___
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] No menu bar option for Adobe Reader

2019-05-01 Thread Henning Hraban Ramm
Am 2019-04-28 um 12:27 schrieb Hans Hagen :

> On 4/27/2019 6:07 PM, Paul Schalck wrote:
>> Hi,
>> I use the "Hide menu bar" option extensively in Adobe Acrobat Reader to get 
>> a cleaner interface. To this end, I usually hack lpdf-mis.lua after a 
>> ConTeXt upgrade to create a \setupinteractionscreen[option=nomenubar] switch.
>> I wonder if it would be possible to add this little feature to the source 
>> code. Perhaps it can be useful to others as well.
>> Greetings!
>> Paul
>> Attachment: patch + modified lpdf-mis.lua (from ConTeXt MkVI 2019.04.25)
> ok, but i didn't test it, so you need to check next beta

Thanks, I added it in the wiki.

Greetlings, 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] No menu bar option for Adobe Reader

2019-05-01 Thread luigi scarso
On Sun, Apr 28, 2019 at 10:38 PM Paul Schalck  wrote:

> @luigi: Version 11. I know, it isn't supported anymore since October 2017.
>



https://linuxconfig.org/how-to-install-latest-adobe-acrobat-reader-dc-on-ubuntu-18-04-bionic-beaver-linux-with-wine
seems to work,
I have installed
AcroRdrDC1901020099_en_US.exe
and opened a couple of files.

-- 
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] No menu bar option for Adobe Reader

2019-04-28 Thread Paul Schalck
@luigi: Version 11. I know, it isn't supported anymore since October 2017.
___
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] No menu bar option for Adobe Reader

2019-04-28 Thread luigi scarso
On Sun, Apr 28, 2019 at 9:42 PM Paul Schalck  wrote:

>
>  I use Acrord because I'm used to it and because I think it still has the
> best subpixel rendering, at least in the Linux world (with Wine). Mozilla's
> PDF.js comes close though.
>

 which version of adobe reader are you using?

-- 
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] No menu bar option for Adobe Reader

2019-04-28 Thread Paul Schalck
@Hans: Thanks a lot, I'm looking forward to testing it.

@Alan: Like Hans said. It's a new option, and I have it activated in my local 
environment file. It's the only and clumsy way to control the interface setting 
since Adobe Reader cannot save the state of the menu bar permanently (which is 
complete nonsense). I use Acrord because I'm used to it and because I think it 
still has the best subpixel rendering, at least in the Linux world (with Wine). 
Mozilla's PDF.js comes close though.

Paul
___
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] No menu bar option for Adobe Reader

2019-04-28 Thread Hans Hagen

On 4/28/2019 5:25 PM, Alan Braslau wrote:



On 28Apr19, at 04:27, Hans Hagen  wrote:


\setupinteractionscreen[option=nomenubar] switch.
I wonder if it would be possible to add this little feature to the source code.


Why don’t you simply put this setup in your local environment (texmf-local) as 
I do not believe that it should in anyway become a default.
they are options (nomenubar is a new one), no defaults (also, only afaik 
only acrobat listens to such options)


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] No menu bar option for Adobe Reader

2019-04-28 Thread Alan Braslau

> On 28Apr19, at 04:27, Hans Hagen  wrote:
> 
>> \setupinteractionscreen[option=nomenubar] switch.
>> I wonder if it would be possible to add this little feature to the source 
>> code. 

Why don’t you simply put this setup in your local environment (texmf-local) as 
I do not believe that it should in anyway become a default.

Alan


--
Alan Braslau



___
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] No menu bar option for Adobe Reader

2019-04-28 Thread Hans Hagen

On 4/27/2019 6:07 PM, Paul Schalck wrote:

Hi,

I use the "Hide menu bar" option extensively in Adobe Acrobat Reader to get a 
cleaner interface. To this end, I usually hack lpdf-mis.lua after a ConTeXt upgrade to 
create a \setupinteractionscreen[option=nomenubar] switch.

I wonder if it would be possible to add this little feature to the source code. 
Perhaps it can be useful to others as well.

Greetings!

Paul

Attachment: patch + modified lpdf-mis.lua (from ConTeXt MkVI 2019.04.25)

ok, but i didn't test it, so you need to check next beta

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
___


[NTG-context] No menu bar option for Adobe Reader

2019-04-27 Thread Paul Schalck
Hi,

I use the "Hide menu bar" option extensively in Adobe Acrobat Reader to get a 
cleaner interface. To this end, I usually hack lpdf-mis.lua after a ConTeXt 
upgrade to create a \setupinteractionscreen[option=nomenubar] switch.

I wonder if it would be possible to add this little feature to the source code. 
Perhaps it can be useful to others as well.

Greetings!

Paul

Attachment: patch + modified lpdf-mis.lua (from ConTeXt MkVI 2019.04.25)if not modules then modules = { } end modules ['lpdf-mis'] = {
version   = 1.001,
comment   = "companion to lpdf-ini.mkiv",
author= "Hans Hagen, PRAGMA-ADE, Hasselt NL",
copyright = "PRAGMA ADE / ConTeXt Development Team",
license   = "see context related readme files"
}

-- Although we moved most pdf handling to the lua end, we didn't change
-- the overall approach. For instance we share all resources i.e. we
-- don't make subsets for each xform or page. The current approach is
-- quite efficient. A big difference between MkII and MkIV is that we
-- now use forward references. In this respect the MkII code shows that
-- it evolved over a long period, when backends didn't provide forward
-- referencing and references had to be tracked in multiple passes. Of
-- course there are a couple of more changes.

local next, tostring, type = next, tostring, type
local format, gsub, formatters = string.format, string.gsub, string.formatters
local flattened = table.flattened

local backends, lpdf, nodes = backends, lpdf, nodes

local nodeinjections   = backends.pdf.nodeinjections
local codeinjections   = backends.pdf.codeinjections
local registrations= backends.pdf.registrations

local nuts = nodes.nuts
local copy_node= nuts.copy

local nodepool = nuts.pool
local pageliteral  = nodepool.pageliteral
local register = nodepool.register

local pdfdictionary= lpdf.dictionary
local pdfarray = lpdf.array
local pdfconstant  = lpdf.constant
local pdfreference = lpdf.reference
local pdfunicode   = lpdf.unicode
local pdfverbose   = lpdf.verbose
local pdfstring= lpdf.string
local pdfflushobject   = lpdf.flushobject
local pdfflushstreamobject = lpdf.flushstreamobject
local pdfaction= lpdf.action
local pdfminorversion  = lpdf.minorversion

local formattedtimestamp   = lpdf.pdftimestamp
local adddocumentextgstate = lpdf.adddocumentextgstate
local addtocatalog = lpdf.addtocatalog
local addtoinfo= lpdf.addtoinfo
local addtopageattributes  = lpdf.addtopageattributes
local addtonames   = lpdf.addtonames

local pdfgetmetadata   = lpdf.getmetadata

local texset   = tex.set

local variables= interfaces.variables

local v_stop   = variables.stop
local v_none   = variables.none
local v_max= variables.max
local v_bookmark   = variables.bookmark
local v_fit= variables.fit
local v_doublesided= variables.doublesided
local v_singlesided= variables.singlesided
local v_default= variables.default
local v_auto   = variables.auto
local v_fixed  = variables.fixed
local v_landscape  = variables.landscape
local v_portrait   = variables.portrait
local v_page   = variables.page
local v_paper  = variables.paper
local v_attachment = variables.attachment
local v_layer  = variables.layer
local v_lefttoright= variables.lefttoright
local v_righttoleft= variables.righttoleft
local v_title  = variables.title
local v_nomenubar  = variables.nomenubar

local positive = register(pageliteral("/GSpositive gs"))
local negative = register(pageliteral("/GSnegative gs"))
local overprint= register(pageliteral("/GSoverprint gs"))
local knockout = register(pageliteral("/GSknockout gs"))

local omitextraboxes   = false

directives.register("backend.omitextraboxes", function(v) omitextraboxes = v end)

local function initializenegative()
local a = pdfarray { 0, 1 }
local g = pdfconstant("ExtGState")
local d = pdfdictionary {
FunctionType = 4,
Range= a,
Domain   = a,
}
local negative = pdfdictionary { Type = g, TR = pdfreference(pdfflushstreamobject("{ 1 exch sub }",d)) } -- can be shared
local positive = pdfdictionary { Type = g, TR = pdfconstant("Identity") }
adddocumentextgstate("GSnegative", pdfreference(pdfflushobject(negative)))
adddocumentextgstate("GSpositive", pdfreference(pdfflushobject(positive)))
initializenegative = nil
end

local function initializeoverprint()
local g = pdfconstant("ExtGState")
local knockout  = pdfdictionary { Type = g, OP = false, OPM  = 0 }
local overprint = pdfdictionary { Type = g, OP = true,  OPM  = 1 }