option for printing range

option for printing range

[Pablo Rodriguez]

Hans,

would it be possible to add an key to \setupinteractionscreen that
implements the /PrintPageRange key in the /ViewerPreferences dictionary
(https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=373)?

For example, "\setupinteractionscreen[range={2, 4-7, 10}]" should add
the "/PrintPageRange [1 1 3 6 9 9]" in /ViewerPreferences. (BTW, the key
name is the first one that came to my mind.)

This is extremely useful to help the user to print only the required
pages and not the whole document (which may be required only for viewing
purposes).

Many thanks for your help,

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: option for printing range

[Hans Hagen]

On 2/24/2018 11:31 AM, Pablo Rodriguez wrote:
> Hans,
> 
> would it be possible to add an key to \setupinteractionscreen that
> implements the /PrintPageRange key in the /ViewerPreferences dictionary
> (https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=373)?
> 
> For example, "\setupinteractionscreen[range={2, 4-7, 10}]" should add
> the "/PrintPageRange [1 1 3 6 9 9]" in /ViewerPreferences. (BTW, the key
> name is the first one that came to my mind.)
> 
> This is extremely useful to help the user to print only the required
> pages and not the whole document (which may be required only for viewing
> purposes).
well, 'extremely' is a bit of a exaggeration i guess as most of these 
fancy acrobat only features are hardly used or requested (i still have 
to meet a publisher who wants anything fancy pdf anyway) so we're 
talking of yet another feature creep that probably only one person will use

anyway, that said, as we use abstraction and as we don't know pages in 
advance the only way i'm willing to support it is by using the (probably 
unknown) marked pages feature

\setupinteractionscreen
   [print={foo,oof}]

\starttext

% \markpage[foo][1,4,5]
% \markpage[foo][+2]

\markpage[foo] foo \page
\markpage[foo] foo \page
\markpage[oof] oof \page
\markpage[bar] bar \page
\markpage[foo] foo \page
\markpage[foo] foo \page
\markpage[bar] bar \page
\markpage[foo] foo \page
\markpage[oof] oof \page
\markpage[bar] bar \page

\stoptext

and guess who is going to document it on the wiki ...

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
___________________________________________________________________________________

page-ini.lua, was Re: option for printing range

[Rik Kabel]

On 2018-02-24 13:50, Hans Hagen wrote:
> On 2/24/2018 11:31 AM, Pablo Rodriguez wrote:
>> Hans,
>>
>> would it be possible to add an key to \setupinteractionscreen that
>> implements the /PrintPageRange key in the /ViewerPreferences dictionary
>> (https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=373)? 
>>
>>
>> For example, "\setupinteractionscreen[range={2, 4-7, 10}]" should add
>> the "/PrintPageRange [1 1 3 6 9 9]" in /ViewerPreferences. (BTW, the key
>> name is the first one that came to my mind.)
>>
>> This is extremely useful to help the user to print only the required
>> pages and not the whole document (which may be required only for viewing
>> purposes).
> well, 'extremely' is a bit of a exaggeration i guess as most of these 
> fancy acrobat only features are hardly used or requested (i still have 
> to meet a publisher who wants anything fancy pdf anyway) so we're 
> talking of yet another feature creep that probably only one person 
> will use
>
> anyway, that said, as we use abstraction and as we don't know pages in 
> advance the only way i'm willing to support it is by using the 
> (probably unknown) marked pages feature
>
> \setupinteractionscreen
>   [print={foo,oof}]
>
> \starttext
>
> % \markpage[foo][1,4,5]
> % \markpage[foo][+2]
>
> \markpage[foo] foo \page
> \markpage[foo] foo \page
> \markpage[oof] oof \page
> \markpage[bar] bar \page
> \markpage[foo] foo \page
> \markpage[foo] foo \page
> \markpage[bar] bar \page
> \markpage[foo] foo \page
> \markpage[oof] oof \page
> \markpage[bar] bar \page
>
> \stoptext
Hans,

A question on the code in page-ini.lua.

Should there be a test for a '-' with subtraction from realpage if 
present, as there is for '+' and addition to realpage, around line 
number 28-30, or is it the case that it does not make sense to mark a 
prior page? (If it does not make sense, why parse the '-'?)

-- 
Rik
___________________________________________________________________________________
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: page-ini.lua, was Re: option for printing range

[Hans Hagen]

On 2/24/2018 9:29 PM, Rik Kabel wrote:
> On 2018-02-24 13:50, Hans Hagen wrote:
>> On 2/24/2018 11:31 AM, Pablo Rodriguez wrote:
>>> Hans,
>>>
>>> would it be possible to add an key to \setupinteractionscreen that
>>> implements the /PrintPageRange key in the /ViewerPreferences dictionary
>>> (https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=373)? 
>>>
>>>
>>> For example, "\setupinteractionscreen[range={2, 4-7, 10}]" should add
>>> the "/PrintPageRange [1 1 3 6 9 9]" in /ViewerPreferences. (BTW, the key
>>> name is the first one that came to my mind.)
>>>
>>> This is extremely useful to help the user to print only the required
>>> pages and not the whole document (which may be required only for viewing
>>> purposes).
>> well, 'extremely' is a bit of a exaggeration i guess as most of these 
>> fancy acrobat only features are hardly used or requested (i still have 
>> to meet a publisher who wants anything fancy pdf anyway) so we're 
>> talking of yet another feature creep that probably only one person 
>> will use
>>
>> anyway, that said, as we use abstraction and as we don't know pages in 
>> advance the only way i'm willing to support it is by using the 
>> (probably unknown) marked pages feature
>>
>> \setupinteractionscreen
>>   [print={foo,oof}]
>>
>> \starttext
>>
>> % \markpage[foo][1,4,5]
>> % \markpage[foo][+2]
>>
>> \markpage[foo] foo \page
>> \markpage[foo] foo \page
>> \markpage[oof] oof \page
>> \markpage[bar] bar \page
>> \markpage[foo] foo \page
>> \markpage[foo] foo \page
>> \markpage[bar] bar \page
>> \markpage[foo] foo \page
>> \markpage[oof] oof \page
>> \markpage[bar] bar \page
>>
>> \stoptext
> Hans,
> 
> A question on the code in page-ini.lua.
> 
> Should there be a test for a '-' with subtraction from realpage if 
> present, as there is for '+' and addition to realpage, around line 
> number 28-30, or is it the case that it does not make sense to mark a 
> prior page? (If it does not make sense, why parse the '-'?)
i can't figure a reasonable meaning for minus (after all, we're past 
that page then and this mechanism is for testing pages)

just to make sure that we have a number (but we ignore a -)

btw, a few decases ago we had a similar feature which we used to inject 
pages from a different bin in the printer

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: option for printing range

[Pablo Rodriguez]

On 02/24/2018 07:50 PM, Hans Hagen wrote:
> On 2/24/2018 11:31 AM, Pablo Rodriguez wrote:
>> [...]
>> This is extremely useful to help the user to print only the required
>> pages and not the whole document (which may be required only for viewing
>> purposes).
> 
> well, 'extremely' is a bit of a exaggeration i guess as most of these 
> fancy acrobat only features are hardly used or requested (i still have 
> to meet a publisher who wants anything fancy pdf anyway) so we're 
> talking of yet another feature creep that probably only one person will use

Many thanks for your implementation, Hans.

I agree it is not a general-purpose feature, but it is very useful when
needed.

The printing features (duplex and others) that I request are extremely
useful for my workmates and in copyshops. With them, I don’t have to
explain them how the PDF documents should be printed.

I would love to have them in the webapps I have at work, but
unfortunately they don’t contain them.

> anyway, that said, as we use abstraction and as we don't know pages in 
> advance the only way i'm willing to support it is by using the (probably 
> unknown) marked pages feature

Just to understand, why is it required that pages are known in advance?
Is it only a question of convenience for the user or does ConTeXt

As for the marked pages feature, it should read for me "(totally
unknown)" instead of "(probably unknown)".

> % \markpage[foo][1,4,5]

From what I read in i-context.pdf, I wonder whether it would be possible
to add page ranges with [10:90].

I don’t have a way of testing it, since I don’t know how to use
\markpage for other purposes.

> and guess who is going to document it on the wiki ...

Already documented:
http://wiki.contextgarden.net/PDF_Print_Options#Print_Page_Range.

I agree it might need some editing, but after testing the feature ;-).

Many thanks for the implementation again,

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: option for printing range

[Hans Hagen]

On 2/25/2018 10:11 AM, Pablo Rodriguez wrote:
> On 02/24/2018 07:50 PM, Hans Hagen wrote:
>> On 2/24/2018 11:31 AM, Pablo Rodriguez wrote:
>>> [...]
>>> This is extremely useful to help the user to print only the required
>>> pages and not the whole document (which may be required only for viewing
>>> purposes).
>>
>> well, 'extremely' is a bit of a exaggeration i guess as most of these
>> fancy acrobat only features are hardly used or requested (i still have
>> to meet a publisher who wants anything fancy pdf anyway) so we're
>> talking of yet another feature creep that probably only one person will use
> 
> Many thanks for your implementation, Hans.
> 
> I agree it is not a general-purpose feature, but it is very useful when
> needed.
> 
> The printing features (duplex and others) that I request are extremely
> useful for my workmates and in copyshops. With them, I don’t have to
> explain them how the PDF documents should be printed.
> 
> I would love to have them in the webapps I have at work, but
> unfortunately they don’t contain them.

as is much (like layers)

>> anyway, that said, as we use abstraction and as we don't know pages in
>> advance the only way i'm willing to support it is by using the (probably
>> unknown) marked pages feature
> 
> Just to understand, why is it required that pages are known in advance?
> Is it only a question of convenience for the user or does ConTeXt
> 
> As for the marked pages feature, it should read for me "(totally
> unknown)" instead of "(probably unknown)".
> 
>> % \markpage[foo][1,4,5]
> 
>  From what I read in i-context.pdf, I wonder whether it would be possible
> to add page ranges with [10:90].
> 
> I don’t have a way of testing it, since I don’t know how to use
> \markpage for other purposes.

the only way to test is dummy documents ... and as one never know pages 
in advance marking a specific page actually makes not much sense .. i'll 
add an automatism but as usual with such page break related features you 
need to be explicit in the sense of adding \page (a bit like headers and 
footers)

\page
\startmarkpages [extra]
     \dorecurse {10} {
         \samplefile{greenfield} \par
     }
     \page
\stopmarkpages

(it's no big deal to add a real marking feature that would be more 
automatic but it's overkill)

>> and guess who is going to document it on the wiki ...
> 
> Already documented:
> http://wiki.contextgarden.net/PDF_Print_Options#Print_Page_Range.
> 
> I agree it might need some editing, but after testing the feature ;-).
> 
> Many thanks for the implementation again,
> 
> Pablo
> 


-- 

-----------------------------------------------------------------
                                           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: option for printing range

[Pablo Rodriguez]

On 02/25/2018 01:21 PM, Hans Hagen wrote:
> On 2/25/2018 10:11 AM, Pablo Rodriguez wrote:
>> As for the marked pages feature, it should read for me "(totally
>> unknown)" instead of "(probably unknown)".
>>
>>> % \markpage[foo][1,4,5]
>>
>>  From what I read in i-context.pdf, I wonder whether it would be possible
>> to add page ranges with [10:90].
>>
>> I don’t have a way of testing it, since I don’t know how to use
>> \markpage for other purposes.
> 
> the only way to test is dummy documents ... and as one never know pages 
> in advance marking a specific page actually makes not much sense .. i'll 
> add an automatism but as usual with such page break related features you 
> need to be explicit in the sense of adding \page (a bit like headers and 
> footers)

Many thanks for the implementation in the latest beta, Hans.

I’m afraid I found a bug. Page numbers in /PrintPageRange are actual
page numbers minus one. Here you have a sample:

    \setupinteractionscreen
       [print={foo}]

    \starttext

    first \page
    \markpage[foo] foo \page
    foo \page
    oof \page
    \markpage[foo] foo \page
    foo \page
    oof \page
    \markpage[foo] foo \page
    \startmarkpages[foo]
    foo \page
    oof \page
    \stopmarkpages
    \stoptext

The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
(the document only contains 10 pages).

BTW, "\markpage[foo][+1]" works fine (with the issue I described), but
"\markpage[foo][3,4]" doesn’t work at all.

Many thanks for your help again,

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: option for printing range

[Hans Hagen]

On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
> On 02/25/2018 01:21 PM, Hans Hagen wrote:
>> On 2/25/2018 10:11 AM, Pablo Rodriguez wrote:
>>> As for the marked pages feature, it should read for me "(totally
>>> unknown)" instead of "(probably unknown)".
>>>
>>>> % \markpage[foo][1,4,5]
>>>
>>>   From what I read in i-context.pdf, I wonder whether it would be possible
>>> to add page ranges with [10:90].
>>>
>>> I don’t have a way of testing it, since I don’t know how to use
>>> \markpage for other purposes.
>>
>> the only way to test is dummy documents ... and as one never know pages
>> in advance marking a specific page actually makes not much sense .. i'll
>> add an automatism but as usual with such page break related features you
>> need to be explicit in the sense of adding \page (a bit like headers and
>> footers)
> 
> Many thanks for the implementation in the latest beta, Hans.
> 
> I’m afraid I found a bug. Page numbers in /PrintPageRange are actual
> page numbers minus one. Here you have a sample:
> 
>      \setupinteractionscreen
>         [print={foo}]
> 
>      \starttext
> 
>      first \page
>      \markpage[foo] foo \page
>      foo \page
>      oof \page
>      \markpage[foo] foo \page
>      foo \page
>      oof \page
>      \markpage[foo] foo \page
>      \startmarkpages[foo]
>      foo \page
>      oof \page
>      \stopmarkpages
>      \stoptext
> 
> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
> (the document only contains 10 pages).

is ok here (looking in the pdf file)

> BTW, "\markpage[foo][+1]" works fine (with the issue I described), but
> "\markpage[foo][3,4]" doesn’t work at all.

i'll look at it (next week)

> Many thanks for your help again,
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: option for printing range

[Pablo Rodriguez]

On 02/25/2018 10:51 PM, Hans Hagen wrote:
> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>> [...]
>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
>> (the document only contains 10 pages).
> 
> is ok here (looking in the pdf file)

You’re right. The /PrinPagetRange is right, but Acrobat 9 for Linux adds
a number to each number in that array.

The specification is clear in this point (on its page 365):

  The first page of the PDF file shall be denoted by 1.

I’ll test the file on a newer version of Acrobat.

Sorry for the noise,

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: option for printing range

[Pablo Rodriguez]

On 02/25/2018 10:51 PM, Hans Hagen wrote:
> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>> [...]
>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
>> (the document only contains 10 pages).
> 
> is ok here (looking in the pdf file)

I have tested the file in Acrobat XI and since I got the same wrong page
ranges, I asked to an Adobe engineer.

He confirmed that the spec is wrong. Page counting for /PrintPageRange
should be zero-based and it shouldn’t start from one.

Sorry for this. Could you correct the implementation?

Many thanks for your help,

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: option for printing range

[Hans Hagen]

On 2/26/2018 8:02 PM, Pablo Rodriguez wrote:
> On 02/25/2018 10:51 PM, Hans Hagen wrote:
>> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>>> [...]
>>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
>>> (the document only contains 10 pages).
>>
>> is ok here (looking in the pdf file)
> 
> I have tested the file in Acrobat XI and since I got the same wrong page
> ranges, I asked to an Adobe engineer.
> 
> He confirmed that the spec is wrong. Page counting for /PrintPageRange
> should be zero-based and it shouldn’t start from one.
> 
> Sorry for this. Could you correct the implementation?
the usual pdf spec rubish ... no one uses it (although tex is often 
first), they it gets a bugged implementation and then the specs change 
... one of the reasons why i don't bother too much in implementing the 
latest pdf gadgets ... i wasted too much time adapting to changed 
(interpretation of the) specs

Hans

(I don't officially have the latest spec as i refuse to pay for a pdf 
specification that could be distributed in pdf format.)

-----------------------------------------------------------------
                                           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: option for printing range

[Henning Hraban Ramm]

Am 2018-02-26 um 20:02 schrieb Pablo Rodriguez <oinos@gmx.es>:

> On 02/25/2018 10:51 PM, Hans Hagen wrote:
>> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>>> [...]
>>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
>>> (the document only contains 10 pages).
>> 
>> is ok here (looking in the pdf file)
> 
> I have tested the file in Acrobat XI and since I got the same wrong page
> ranges, I asked to an Adobe engineer.
> 
> He confirmed that the spec is wrong. Page counting for /PrintPageRange
> should be zero-based and it shouldn’t start from one.

That’s so typical Adobe!
Write faulty/unusable specs, let everyone in the dark and declare their implementation right.
:(
Too bad I can’t live (make a living) without Photoshop, InDesign etc...

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
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: option for printing range

[Floris van Manen]

[-- Attachment #1.1: Type: text/plain, Size: 271 bytes --]


> On 27 Feb 2018, at 13:50, Henning Hraban Ramm <texml@fiee.net> wrote:
> 
> Too bad I can’t live (make a living) without Photoshop, InDesign etc...

well, that depends as how you organise the workflow…
i switched away from adobe using context instead.

.F

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

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

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

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

Re: option for printing range

[Henning Hraban Ramm]

Am 2018-02-27 um 14:43 schrieb Floris van Manen <vm@klankschap.nl>:

>> On 27 Feb 2018, at 13:50, Henning Hraban Ramm <texml@fiee.net> wrote:
>> Too bad I can’t live (make a living) without Photoshop, InDesign etc...
> 
> well, that depends as how you organise the workflow…
> i switched away from adobe using context instead.

I’m using ConTeXt for most of my serious products (books, magazines) nowadays, but it’s only efficient if you need TeX’s strengths (and can avoid its weaknesses) and make several issues with the same layout.

I’m struggling a lot with ConTeXt’s quirks (e.g. the recently fixed spacing bug, but also just the lack of documentation on all the commands and their options) and too often I get no answers to my questions on this list or I can’t even ask something because I can’t come up with a minimal example, e.g. I recognized just today, float placement "right" or "left" failed to work because I compiled with --mode=something ...

For one-off products (flyers, advertising etc.) ConTeXt is just not an option. And while I’m very fast in image processing with Photoshop I probably didn’t try enough achieving the same results with Gimp... Oh, and Scribus doesn’t help either - the GUI feels clumsy (like the old versions of Corel Draw I tried), and it’s still not possible to properly use layers in templates.

At the moment I’m trying to typeset a book with a lot of poems and similar artsy stuff where every second needs a different formatting - not really a suitable ConTeXt project, but it also has a lot of footnotes that I wouldn’t like to typeset in InDesign..

Sorry, that went OT...

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
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: option for printing range

[Henning Hraban Ramm]

Am 2018-02-27 um 09:15 schrieb Hans Hagen <pragma@wxs.nl>:

> (I don't officially have the latest spec as i refuse to pay for a pdf specification that could be distributed in pdf format.)

Since DANTE is now a member of the PDF Association, don’t "we" get it for free?


Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
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: option for printing range

[Pablo Rodriguez]

On 02/25/2018 10:51 PM, Hans Hagen wrote:
> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>> [...]
>> BTW, "\markpage[foo][+1]" works fine (with the issue I described), but
>> "\markpage[foo][3,4]" doesn’t work at all.
> 
> i'll look at it (next week)

Hans,

many thanks for having fixed all issues in the beta released today.

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: option for printing range

[Christoph Reller]

On Tue, Feb 27, 2018 at 10:05 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 2/27/2018 7:47 PM, Christoph Reller wrote:
>
> anyway, i normally test pdf with an old acrobat X pro (i don't want to lock
> into some subscription and i don't really need a more modern version) and i
> preview / print pdf using sumatra pdf
>
> (printing houses often use pretty old versions anyway)
>

You may actually be better off with Acrobat X then with Acrobat DC
when it comes to testing, because Acrobat DC has an even stronger
tendency to ignore errors silently. :-)

Cheers,
Christoph
___________________________________________________________________________________
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: option for printing range

[Hans Hagen]

On 2/27/2018 7:47 PM, Christoph Reller wrote:
> On Tue, 27 Feb 2018 09:15:37 +0100 Hans Hagen <pragma@wxs.nl> wrote:
>> On 2/26/2018 8:02 PM, Pablo Rodriguez wrote:
>>> On 02/25/2018 10:51 PM, Hans Hagen wrote:
>>>> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>>>>> [...]
>>>>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
>>>>> (the document only contains 10 pages).
>>>>
>>>> is ok here (looking in the pdf file)
>>>
>>> I have tested the file in Acrobat XI and since I got the same wrong page
>>> ranges, I asked to an Adobe engineer.
>>>
>>> He confirmed that the spec is wrong. Page counting for /PrintPageRange
>>> should be zero-based and it shouldn’t start from one.
> 
> This is only one of many cases for which ISO-32000 is the spec and the
> Adobe Reader is the de-facto spec. Others affect annotations and
> rendering.

the pdf spec sometimes looks like a mixture between wishful thinking and 
reverese engineered spec (as there are some real weird constructs in there)

anyway, i normally test pdf with an old acrobat X pro (i don't want to 
lock into some subscription and i don't really need a more modern 
version) and i preview / print pdf using sumatra pdf

(printing houses often use pretty old versions anyway)

>>> Sorry for this. Could you correct the implementation?
>> the usual pdf spec rubish ... no one uses it (although tex is often
>> first), they it gets a bugged implementation and then the specs change
>> ... one of the reasons why i don't bother too much in implementing the
>> latest pdf gadgets ... i wasted too much time adapting to changed
>> (interpretation of the) specs
>>
>> Hans
>>
>> (I don't officially have the latest spec as i refuse to pay for a pdf
>> specification that could be distributed in pdf format.)
> 
> A small detail: The ISO specification for PDF 2.0 also defines the
> first page in /PrintPageRange to be page number 1 (not 0). :(

makes me wonder if there was a 0/1 bug in some adobe pdf generator that 
then defined the standard to have a bug instead -)

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: option for printing range

[Christoph Reller]

On Tue, 27 Feb 2018 09:15:37 +0100 Hans Hagen <pragma@wxs.nl> wrote:
> On 2/26/2018 8:02 PM, Pablo Rodriguez wrote:
>> On 02/25/2018 10:51 PM, Hans Hagen wrote:
>>> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
>>>> [...]
>>>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
>>>> (the document only contains 10 pages).
>>>
>>> is ok here (looking in the pdf file)
>>
>> I have tested the file in Acrobat XI and since I got the same wrong page
>> ranges, I asked to an Adobe engineer.
>>
>> He confirmed that the spec is wrong. Page counting for /PrintPageRange
>> should be zero-based and it shouldn’t start from one.

This is only one of many cases for which ISO-32000 is the spec and the
Adobe Reader is the de-facto spec. Others affect annotations and
rendering.

>> Sorry for this. Could you correct the implementation?
> the usual pdf spec rubish ... no one uses it (although tex is often
> first), they it gets a bugged implementation and then the specs change
> ... one of the reasons why i don't bother too much in implementing the
> latest pdf gadgets ... i wasted too much time adapting to changed
> (interpretation of the) specs
>
> Hans
>
> (I don't officially have the latest spec as i refuse to pay for a pdf
> specification that could be distributed in pdf format.)

A small detail: The ISO specification for PDF 2.0 also defines the
first page in /PrintPageRange to be page number 1 (not 0). :(

Cheers,
Christoph
___________________________________________________________________________________
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
___________________________________________________________________________________