Re: [NTG-context] Typescript/fallbacks problem

[Mohammad Hossein Bateni]

The following email had large attachments (more than 100K).  I uploaded
everything here:
http://mhbateni.com/context/bug-04/

On Thu, May 25, 2017 at 11:40 PM, Mohammad Hossein Bateni 
wrote:

> Hello Hans,
>
> I'm going to explain a strange problem which came about, as far as I can
> tell, in beta 2017.04.27 01:00.  The same beta had introduced some other
> issues with fallbacks, which you fixed already.  Thanks a lot for that!
>
> I am now using the latest beta, version 2017.05.25 12:50.  Unfortunately I
> don't know what is going on precisely.  Here is a sort-of-minimal
> non-working example.
>
>
> %
>
> \definefontfeature[slanted][slant=.4]
>
>
> \starttypescript [serif][sahel][name]
>
>   \resetfontfallback [dejavudefault]
>
>   \definefontfallback[dejavudefault][dejavusans]
> [range=generalpunctuation,check=yes,force=no]
>
> %
>
>   \definefontsynonym [SahelReg][Sahel][features={arabic,
> tlig},fallbacks=dejavudef]
>
> %% NOTE 1
>
> %  \definefontsynonym [SahelReg] [Sahel][features={arabic,tlig}]
>
>   \definefontsynonym [SahelBd]   [SahelBold][features={arabic,
> tlig},fallbacks=dejavudef]
>
>   \definefontsynonym [SahelIt] [Sahel][features={arabic,tlig,
> slanted},fallbacks=dejavudef]
>
>   \definefontsynonym [SahelBdIt] [SahelBold][features={arabic,
> tlig,slanted},fallbacks=dejavudef]
>
> %
>
>   \definefontsynonym [Serif] [SahelReg]
>
>   \definefontsynonym [SerifBold] [SahelBd]
>
>   \definefontsynonym [SerifItalic] [SahelIt]
>
>   \definefontsynonym [SerifBoldItalic] [SahelBdIt]
>
> \stoptypescript
>
>
> \starttypescript [math] [modern] [name]
>
> \definefontsynonym [MathRoman] [name:modern] [features=math\mathsizesuffix]
>
> \stoptypescript
>
>
> \starttypescript [myfont]
>
> \definetypeface [myfont][rm] [serif][sahel] [default]
>
> %% NOTE 2
>
> \definetypeface [myfont][mm] [math] [modern][default]
>
> \stoptypescript
>
>
> \setupbodyfont[myfont,rm]
>
> %% NOTE 3
>
> %\definedfont[Serif]
>
>
> \def\Sample{{\lefttoright Salam} {\righttoleft سلام} }
>
>
> \starttext
>
> rm:\Sample
>
> {\bf bf:\Sample}
>
> {\it it:\Sample}
>
> {\bi bi:\Sample}
>
>
> %% NOTE 4
>
> \definedfont[SahelReg]\Sample
>
> \definedfont[Serif]\Sample
>
>
> \stoptext
> %
>
>
> *Background*:
>
> Commenting/uncommenting some of the lines produces three outputs, only one
> of which seems correct to me.  I have attached the three.  Betas before
> 4/27 always produced the correct solution.
>
> I am using a free open-source Farsi font, whose English glyphs come from
> Open Sans font.  I am attaching the specific versions of the Farsi font to
> reproduce the same results.
> [https://github.com/rastikerdar/sahel-font]
> [https://github.com/google/fonts/tree/master/apache/opensans]
>
>
> *Explanation*:
>
> Compiling the MWE above produces wrong-1.pdf in recent betas.  The serif
> font has not been set up properly on the first line of output.  Instead the
> default Latin Modern has been used, which looks different and misses the
> Farsi glyphs.
>
> Strangely there is nothing wrong with the second line of text, which shows
> Serif and SahelReg fonts are both set up just fine.  See "NOTE 4" in the
> MWE.
>
> Replacing the line above "NOTE 1" with the line below it—i.e., if I remove
> the fallbacks for definition of SahelReg—generates correct.pdf as output.
> I get the same correct output if uncomment the line below "NOTE 3," which
> should be a no-op in my opinion.  Notice that setting the fallback for
> bold, italic and bold italic has not caused any issues.  It's only the
> serif itself that's acting up weirdly.
>
> Finally when I comment the math definition below "NOTE 2," I get
> wrong-2.pdf as output.  Here everything seems okay except that the serif on
> the first line—but strangely not on the second line—misses the Arabic
> features: the letters are not joined.
>
>
> I spent quite some time investigating the changes to the GitHub
> repository on 4/27, to pinpoint what might have caused this issue, but my
> efforts didn't go anywhere.  I hope you can spot the issue.
>
>
> Thanks a lot for your attention!
> —MHB
>
>
>
___
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] Formula numbers in RTL mode

[Mohammad Hossein Bateni]

For the record, here is my solution until the issue is fixed for RTL.

\setupformula[distance=0pt]

This causes the formula numbers to be at the proper place for left/right as
well as LTR/RTL.  It prevents some custom placement of the formula number,
which I do not care about.

—MHB

On Mon, May 15, 2017 at 11:09 PM, Mohammad Hossein Bateni 
wrote:

> Hi Hans,
>
> I recall something like this was reported a few months back, and you said
> you were reworking math alignment mechanisms at the time.  Now that you're
> getting ready for the Tex Live version, I want to bring attention to this
> issue once again, in the hope of getting it resolved.
>
> Formula numbers are not placed at the far end when in RTL.  Here is a MWE:
>
>
> \starttext
>
> \input knuth
>
> \placeformula
> \startformula
> E = mc^2.
> \stopformula
>
> \righttoleft
>
> \placeformula
> \startformula
> E = mc^2.
> \stopformula
>
> \stoptext
>
>
> Attached is the result from context version 2017.05.14 19:09.   Using
> \setupformula[location=left] gives similar results with directions swapped:
> output is as desired in LTR but slightly off the edge in RTL.
>
> Thanks,
> MHB
>
___
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] \start pagefigure not working as expected

[cryo shock]

Hi Andrés,

The problem with \insertpages is that it inserts pages as layers, which
means that header, footer and page numbers will be printed on it as well.
That's what I don't want, and also your suggested link points to me to
\insertpage in my case:

"Please note that the inserted pages will be placed on your ConTeXt pages
like a new "layer", or floating object. This means that your existing
headers, footers, crop marks will still be printed on top of or behind the
inserted pages.
*If you want to insert pages as completely independent pages between your
existing ConTeXt pages, use\startpagefigure
.*"

But the command \startpagefigure doesn't work as described on the wiki...

2017-05-25 20:48 GMT+02:00 Andres Conrado :

>  I think you need to use \insertpages instead. Check this out:
> http://wiki.contextgarden.net/Command/insertpages
>
> Andrés Conrado Montoya
> http://chiquitico.org
>
> 
> ___
> 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
___

[NTG-context] Placing of integral limits

[Mathias Schickel]

Dear list,

I think that the placement of the indices of integrals has some issues, at 
least in some fonts. If you try

\setupbodyfont[cambria]
%
\starttext
%
\startformula
%
\int\nolimits_a^b f
%
\stopformula
%
\stoptext

or if you replace Cambria by Stix Two using \setupbodyfont[stixtwo], you will 
notice that the index a is placed a little too far away form the integral sign. 
The reference is the „exponent“ b and the Word output. I think the Word output 
should be the reference here because the font design of Cambria is done by 
Microsoft and Word supports the font as intended. Apart form that you see the 
very same effect using Latin Modern and this font should look similar to 
Computer Modern in LaTeX.

Best regards
Mathias
___
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] \start pagefigure not working as expected

[Andres Conrado]

 I think you need to use \insertpages instead. Check this out:
http://wiki.contextgarden.net/Command/insertpages

Andrés Conrado Montoya
http://chiquitico.org
___
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] Position of prime for derivatives

[Mathias Schickel]

> Am 25.05.2017 um 18:59 schrieb Mikael P. Sundqvist :
> 
> On Tue, May 23, 2017 at 5:02 PM, Mikael P. Sundqvist  wrote:
>> On Tue, May 23, 2017 at 11:58 AM, Mathias Schickel
>>  wrote:
>>> Hi Mikael and Otared,
>>> 
>>> I can confirm issues regarding primes, too. If you are using the STIX 2
>>> fonts (http://www.stixfonts.org) and my example below you get a somewhat
>>> strange behaviour of primes that is pretty obvious. I think the issues
>>> should be fixed.
>>> 
>>> By the way the issue seems to depend to some extend on the fonts. Using
>>> Lucida by \setupbodyfont[lucidaot] it is not that obvious but still present.
>>> Using Latin Modern it seems that the spacing between the primes changes
>>> between f'' and f^{''}. Cambria seems to show that behaviour (like Latin
>>> Modern), too, but less obvious.
>>> 
>>> Best regards
>>> Mathias
>>> 
>>> %% example
>>> \unprotect
>>> 
>>> \definefontfeature
>>> [stixtwo-math-feature]
>>> [kern=yes,
>>> ss01=no,% calligraphic letters
>>> ss02=yes, % lowercase italic variants (e.g. open g)
>>> ss03=no, % hbar und lambdabar variants
>>> ss04=yes, % larger and lower primes, minute etc.
>>> ss05=no, % shorter arrows
>>> ss06=no, % narrower and shorter element and similar symbols
>>> ss07=no, % some smaller operators and emptyset variant
>>> ss08=yes, % upright integrals etc.
>>> ss09=no, % variant negated symbols
>>> ss10=yes, % variants of greater and lesser and similar symbols
>>> ss11=yes, % variant of negated set (inclusion etc.) symbols
>>> ss14=yes, %
>>> ss16=yes] % variants of circled operators
>>> 
>>> \starttypescriptcollection[Stix2]
>>> \starttypescript [\s!serif] [Stix2] [\s!all]
>>> \definefontsynonym
>>>[Stix2Regular]
>>>[file:STIX2Text-Regular.otf]
>>>\definefontsynonym
>>>[Stix2Bold]
>>>[file:STIX2Text-Bold.otf]
>>>\definefontsynonym
>>>[Stix2Italic]
>>>[file:STIX2Text-Italic.otf]
>>>\definefontsynonym
>>>[Stix2BoldItalic]
>>>[file:STIX2Text-BoldItalic.otf]
>>>\definefontsynonym[\s!Serif] [Stix2Regular] [\s!features=\s!default]
>>>\definefontsynonym[\s!SerifBold] [Stix2Bold]
>>> [\s!features=\s!default]
>>>\definefontsynonym[\s!SerifItalic] [Stix2Italic]
>>> [\s!features=\s!default]
>>>\definefontsynonym[\s!SerifBoldItalic] [Stix2BoldItalic]
>>> [\s!features=\s!default]
>>>\stoptypescript
>>> 
>>>\starttypescript [\s!math] [Stix2]
>>>\definefontsynonym
>>>[Stix2Math]
>>>[file:STIX2Math.otf]
>>>[features=math\mathsizesuffix]
>>>\definefontsynonym [\s!MathRoman] [Stix2Math]
>>> [\s!features={\s!math\mathsizesuffix,mathextra,stixtwo-math-feature},\s!designsize=\s!auto]
>>>\stoptypescript
>>> 
>>>\starttypescript [Stix2]
>>>\definetypeface [\typescriptone] [\s!rm] [\s!serif] [Stix2]
>>> [\s!default]
>>>\definetypeface [\typescriptone] [\s!mm] [\s!math] [Stix2]
>>> [\s!default]
>>>\stoptypescript
>>> 
>>> \stoptypescriptcollection
>>> 
>>> \protect
>>> 
>>> \setupbodyfont[Stix2]
>>> 
>>> \starttext
>>> %
>>> Compare $f'$ to $(f')$ and to $f''$, $(f'')$, $f^{''}$ and $(f^{''})$.
>>> %
>>> \stoptext
>>> %% end of example
>>> 
>>> 
>>> 
>>> Am 22.05.2017 um 09:50 schrieb Otared Kavian :
>>> 
>>> Hi Mikael,
>>> 
>>> You are correct, the position of \prime depends on whether there is a next
>>> character or not after it, and it seems that this has an effect on its
>>> position for characters having a subscript as in
>>> $f_{1}''(x) \neq f''_{1}(x)$
>>> $f'f''f'’'$
>>> Best regards: OK
>>> 
>>> On 22 May 2017, at 08:51, Mikael P. Sundqvist  wrote:
>>> 
>>> On Sun, May 21, 2017 at 10:29 PM, Otared Kavian  wrote:
>>> 
>>> Hi Mikael,
>>> 
>>> I agree with what you are reporting: the current behavior of the \prime
>>> operator is not completely satisfying when using ConTeXt mkiv, while in mkii
>>> it is the most satisfying (in my opinion…).
>>> 
>>> The turn around consisting in using $f^{‘’}$ or  $f^{\prime\prime}$, or even
>>> $f^{{}^{\prime\prime}}$, is not really satisfying either.
>>> 
>>> But I think (or I hope that) at some point Hans will fix it in mkiv.
>>> 
>>> Best regards: OK
>>> 
>>> On 21 May 2017, at 08:14, Mikael P. Sundqvist  wrote:
>>> […]
>>> 
>>> And just for reference, the document below gives the attached pdf,
>>> compiled with lualatex. I think the location of the primes there look
>>> better. Sorry for spamming about this issue, but I think it is
>>> important for all people writing math with ConTeXt.
>>> 
>>> /Mikael
>>> 
>>> \RequirePackage{luatex85}
>>> \documentclass[border=2pt]{standalone}
>>> 
>>> \usepackage{unicode-math}
>>> \setmainfont{LucidaBrightOT}
>>> \setmathfont{LucidaBrightMathOT}
>>> 
>>> \begin{document}
>>> $f'f''$
>>> \end{document}
>>> 

Re: [NTG-context] Position of prime for derivatives

[Mikael P. Sundqvist]

On Tue, May 23, 2017 at 5:02 PM, Mikael P. Sundqvist  wrote:
> On Tue, May 23, 2017 at 11:58 AM, Mathias Schickel
>  wrote:
>> Hi Mikael and Otared,
>>
>> I can confirm issues regarding primes, too. If you are using the STIX 2
>> fonts (http://www.stixfonts.org) and my example below you get a somewhat
>> strange behaviour of primes that is pretty obvious. I think the issues
>> should be fixed.
>>
>> By the way the issue seems to depend to some extend on the fonts. Using
>> Lucida by \setupbodyfont[lucidaot] it is not that obvious but still present.
>> Using Latin Modern it seems that the spacing between the primes changes
>> between f'' and f^{''}. Cambria seems to show that behaviour (like Latin
>> Modern), too, but less obvious.
>>
>> Best regards
>> Mathias
>>
>> %% example
>> \unprotect
>>
>> \definefontfeature
>> [stixtwo-math-feature]
>> [kern=yes,
>> ss01=no,% calligraphic letters
>> ss02=yes, % lowercase italic variants (e.g. open g)
>> ss03=no, % hbar und lambdabar variants
>> ss04=yes, % larger and lower primes, minute etc.
>> ss05=no, % shorter arrows
>> ss06=no, % narrower and shorter element and similar symbols
>> ss07=no, % some smaller operators and emptyset variant
>> ss08=yes, % upright integrals etc.
>> ss09=no, % variant negated symbols
>> ss10=yes, % variants of greater and lesser and similar symbols
>> ss11=yes, % variant of negated set (inclusion etc.) symbols
>> ss14=yes, %
>> ss16=yes] % variants of circled operators
>>
>> \starttypescriptcollection[Stix2]
>> \starttypescript [\s!serif] [Stix2] [\s!all]
>> \definefontsynonym
>> [Stix2Regular]
>> [file:STIX2Text-Regular.otf]
>> \definefontsynonym
>> [Stix2Bold]
>> [file:STIX2Text-Bold.otf]
>> \definefontsynonym
>> [Stix2Italic]
>> [file:STIX2Text-Italic.otf]
>> \definefontsynonym
>> [Stix2BoldItalic]
>> [file:STIX2Text-BoldItalic.otf]
>> \definefontsynonym[\s!Serif] [Stix2Regular] [\s!features=\s!default]
>> \definefontsynonym[\s!SerifBold] [Stix2Bold]
>> [\s!features=\s!default]
>> \definefontsynonym[\s!SerifItalic] [Stix2Italic]
>> [\s!features=\s!default]
>> \definefontsynonym[\s!SerifBoldItalic] [Stix2BoldItalic]
>> [\s!features=\s!default]
>> \stoptypescript
>>
>> \starttypescript [\s!math] [Stix2]
>> \definefontsynonym
>> [Stix2Math]
>> [file:STIX2Math.otf]
>> [features=math\mathsizesuffix]
>> \definefontsynonym [\s!MathRoman] [Stix2Math]
>> [\s!features={\s!math\mathsizesuffix,mathextra,stixtwo-math-feature},\s!designsize=\s!auto]
>> \stoptypescript
>>
>> \starttypescript [Stix2]
>> \definetypeface [\typescriptone] [\s!rm] [\s!serif] [Stix2]
>> [\s!default]
>> \definetypeface [\typescriptone] [\s!mm] [\s!math] [Stix2]
>> [\s!default]
>> \stoptypescript
>>
>> \stoptypescriptcollection
>>
>> \protect
>>
>> \setupbodyfont[Stix2]
>>
>> \starttext
>> %
>> Compare $f'$ to $(f')$ and to $f''$, $(f'')$, $f^{''}$ and $(f^{''})$.
>> %
>> \stoptext
>> %% end of example
>>
>>
>>
>> Am 22.05.2017 um 09:50 schrieb Otared Kavian :
>>
>> Hi Mikael,
>>
>> You are correct, the position of \prime depends on whether there is a next
>> character or not after it, and it seems that this has an effect on its
>> position for characters having a subscript as in
>> $f_{1}''(x) \neq f''_{1}(x)$
>> $f'f''f'’'$
>> Best regards: OK
>>
>> On 22 May 2017, at 08:51, Mikael P. Sundqvist  wrote:
>>
>> On Sun, May 21, 2017 at 10:29 PM, Otared Kavian  wrote:
>>
>> Hi Mikael,
>>
>> I agree with what you are reporting: the current behavior of the \prime
>> operator is not completely satisfying when using ConTeXt mkiv, while in mkii
>> it is the most satisfying (in my opinion…).
>>
>> The turn around consisting in using $f^{‘’}$ or  $f^{\prime\prime}$, or even
>> $f^{{}^{\prime\prime}}$, is not really satisfying either.
>>
>> But I think (or I hope that) at some point Hans will fix it in mkiv.
>>
>> Best regards: OK
>>
>> On 21 May 2017, at 08:14, Mikael P. Sundqvist  wrote:
>> […]
>>
>> And just for reference, the document below gives the attached pdf,
>> compiled with lualatex. I think the location of the primes there look
>> better. Sorry for spamming about this issue, but I think it is
>> important for all people writing math with ConTeXt.
>>
>> /Mikael
>>
>> \RequirePackage{luatex85}
>> \documentclass[border=2pt]{standalone}
>>
>> \usepackage{unicode-math}
>> \setmainfont{LucidaBrightOT}
>> \setmathfont{LucidaBrightMathOT}
>>
>> \begin{document}
>> $f'f''$
>> \end{document}
>> ___
>> If your question is of interest to others as well, please add an entry to
>> the Wiki!
>>
>> maillist : ntg-context@ntg.nl /
>> 

[NTG-context] issue with annotation flags

[Pablo Rodriguez]

Dear list,

I have the following code:

\setupinteraction[state=start, color=]
\enabledirectives[references.border]
\starttext
\startTEXpage[offset=1em]
\useURL[url1][http://some-url.com]\from[url1]
\stopTEXpage
\stoptext

The annotation code in the PDF file reads:

<< /Subtype /Link
   /A 7 0 R /Rect [12.354 10.896 131.607 25.324]
   /C [0.6 0.6 0.6]
   /F 4
   /Border [0 0 0.5]>>

I need to report a bug in a PDF viewer with printing the annotation (in
this case, it is only border).

The code that generates the annotation is (with some removals):

local plus = { -- /F
Invisible = 2^0, --   1
Hidden= 2^1, --   2
Print = 2^2, --   3
NoZoom= 2^3, --   4
NoRotate  = 2^4, --   5
NoView= 2^5, --   6
ReadOnly  = 2^6, --   7
Locked= 2^7, --   8
ToggleNoView  = 2^8, --   9
LockedContents= 2^9, --  10,
}

I assume that /F is set to NoZoom in the sample above (bit position 4).
Acrobat displays the annotation flag set to NoZom.

The developers assume that 4 is actually the decimal conversion for a
binary number (100, actually bit position 3). So it prints the
annotation border in the sample above.

It took me a while to understand this (math is all Greek to me).

Is there a way that I can set the annotation flag in the sample above to
Print (/F 3)? (This would be unambiguous, since only a bit can be set
[11 would be an invalid flag value].)

Or am I missing something and Acrobat is misbehaving?

Sorry for such a weird request, but bug reporting has become extremely
complex these days ;-).

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: [NTG-context] \start pagefigure not working as expected

[cryo shock]

Your suggestion works fine for me. I tried \filterpages too, as it is
mentioned on the wiki as well, but the pages then got scaled to the
\setuplayout definitions. I didn't think about using it within the
\startpagemakeup environment though.

So thanks Pablo.

P.S.: I'd still love to know why the simple \startpagefigure doesn't work
as expected as I thought that's what it's there for.


2017-05-25 17:44 GMT+02:00 Pablo Rodriguez :

> On 05/25/2017 05:22 PM, cryo shock wrote:
> > Hi guys,
> >
> > I created a CTX document and now I am trying to merge it with two other
> > pages from another (already compiled) pdf document. Usually I did this
> > job with PDF Split And Merge software, but if CTX (mkiv, LuaTeX) is
> > capable of doing the job, I'd be glad to use CTX instead.
> >
> > On the wiki I found a code snippet that sounds promising, as I don't
> > want headers, page numbers etc. on the two merged pages:
>
> Hi Sebastian,
>
> how about the following code (I don’t remember when, how or where I
> found it)?
>
> \starttext
> \startpagemakeup\filterpages[file.pdf][1]\stoppagemakeup
> \startpagemakeup\filterpages[file.pdf][2]\stoppagemakeup
> \startpagemakeup\filterpages[file.pdf][3]\stoppagemakeup
> \stoptext
>
> > Like I mentioned: even although there is no 5th page in file.pdf, LuaTeX
> > pastes the first page three times...
>
> If you add a non-existing page, you will get a blank page (with the code
> above).
>
> > Am I overlooking something or was there some undocumented change to the
> > code?
>
> Sorry, but I don’t know. Probably I used pagefigure before discovering
> pagemakeup.
>
> Just in case it might 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
> 
> ___
___
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] issue with signature field

[Pablo Rodriguez]

On 05/24/2017 11:57 AM, luigi scarso wrote:
> On Sun, May 21, 2017 at 9:17 PM, Pablo Rodriguez  wrote:
>> Dear list,
>>
>> some time ago, Hans implemented signature fields:
>>
>> \setupinteraction[state=start]
>> \starttext
>> \definefield[x][signature]
>> \field[x]
>> \stoptext
>>
>> I’m afraid I’m not able to sign it using Acrobat 9.5.5, which is the
>> latest version released for Linux.
>
> Alternatives are a reader for android (quite ok, of course you need> decent 
> android device)

Many thanks for your reply, Luigi.

I’m afraid I might be an indecent user, because I only have real
computers (no mobile devices).

> or under linux Wine +  latest Reader for  windows (crossing the fingers)

In that case, I’d rather use Windows at work.

But many thanks for your suggestions,


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] \start pagefigure not working as expected

[Pablo Rodriguez]

On 05/25/2017 05:22 PM, cryo shock wrote:
> Hi guys,
> 
> I created a CTX document and now I am trying to merge it with two other
> pages from another (already compiled) pdf document. Usually I did this
> job with PDF Split And Merge software, but if CTX (mkiv, LuaTeX) is
> capable of doing the job, I'd be glad to use CTX instead.
> 
> On the wiki I found a code snippet that sounds promising, as I don't
> want headers, page numbers etc. on the two merged pages:

Hi Sebastian,

how about the following code (I don’t remember when, how or where I
found it)?

\starttext
\startpagemakeup\filterpages[file.pdf][1]\stoppagemakeup
\startpagemakeup\filterpages[file.pdf][2]\stoppagemakeup
\startpagemakeup\filterpages[file.pdf][3]\stoppagemakeup
\stoptext

> Like I mentioned: even although there is no 5th page in file.pdf, LuaTeX
> pastes the first page three times...

If you add a non-existing page, you will get a blank page (with the code
above).

> Am I overlooking something or was there some undocumented change to the
> code?

Sorry, but I don’t know. Probably I used pagefigure before discovering
pagemakeup.

Just in case it might 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: [NTG-context] issue with signature field

[Pablo Rodriguez]

On 05/24/2017 11:00 AM, Hans Hagen wrote:
> On 5/21/2017 9:17 PM, Pablo Rodriguez wrote:
>>  \setupinteraction[state=start]
>>  \starttext
>>  \definefield[x][signature]
>>  \field[x]
>>  \stoptext
>>
>> I’m afraid I’m not able to sign it using Acrobat 9.5.5, which is the
>> latest version released for Linux.
>>
>> Acrobat Reader 9.5.5 is able to sign this document:
>> https://bugs.ghostscript.com/attachment.cgi?id=11678 (and
>> https://bugs.ghostscript.com/attachment.cgi?id=11707).
>>
>> I guess it may not be the cause, but which is the way to force the
>> document to be written in PDF version 1.6?
>> I only have an old acrobat x pro and reader dc and both open the
> document. I never used signature fields so I have no clue what to expect 
> anyway.

Many thanks for your reply, Hans.

If you click inside the signature field, a dialog will pop up.

You may use a signature (such as http://acrobat.ousia.tk/JohnDoe.pfx).
The password is "123456".

After sending my original message, I analyzed the contents of the file
that Acrobat for Linux is able to sign. The issue seems to be (or I
think it is) different default settings.

But I need to investigate this further.

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
___

[NTG-context] \start pagefigure not working as expected

[cryo shock]

Hi guys,

I created a CTX document and now I am trying to merge it with two other
pages from another (already compiled) pdf document. Usually I did this job
with PDF Split And Merge software, but if CTX (mkiv, LuaTeX) is capable of
doing the job, I'd be glad to use CTX instead.

On the wiki I found a code snippet that sounds promising, as I don't want
headers, page numbers etc. on the two merged pages:

\startpagefigure[file.pdf][page=1]\stoppagefigure

So I added another line with page=2 as content, yet the output generates a
PDF with the *first page twice* only. In fact, my precompiled doc has 3
pages, of which I want the first two only in my new PDF, even when I use
the following code, LuaTeX generates the first page of the precompiled
PDF *three
times*:

\startpagefigure[file.pdf][page=3]\stoppagefigure
\startpagefigure[file.pdf][page=1]\stoppagefigure
\startpagefigure[file.pdf][page=5]\stoppagefigure

Like I mentioned: even although there is no 5th page in file.pdf, LuaTeX
pastes the first page three times...

Am I overlooking something or was there some undocumented change to the
code?


Thanks in advance, Sebastian
___
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
___