Re: [NTG-context] luatex binary is too old

2018-01-15 Thread luigi scarso
On Mon, Jan 15, 2018 at 9:12 PM, Mojca Miklavec
 wrote:
> On 15 January 2018 at 20:54, luigi scarso  wrote:
>> Il 15 gen 2018 20:52, "Mojca Miklavec" ha scritto:
>> On 15 January 2018 at 15:26, Mojca Miklavec wrote:
>>> On 15 January 2018 at 14:56, Hans Hagen wrote:
 On 1/15/2018 2:47 PM, Roger Mason wrote:
>
> : Your luatex binary is too old, you need at least version 1.05!
>
> Where do I get the updated luatex binary?
>
> I'm running on FreeBSD 10.3, 32 bit.

 Does that binary come from the garden too?
>>>
>>> I can take a look.
>>>
>>> It's quite possible that FreeBSD didn't get updated after the problems
>>> with firewalls and networks being shifted around at both ends.
>>
>> I tried to compile it, but it fails with
>>
>> In file included from
>> ../../../source/libs/poppler/poppler-src/poppler/Annot.cc:62:
>> In file included from
>> ../../../source/libs/poppler/poppler-src/poppler/PDFDoc.h:53:
>> ../../../source/libs/poppler/poppler-src/poppler/Form.h:271:79: error:
>> unknown type name 'time_t'
>>   SignatureInfo *validateSignature(bool doVerifyCert, bool
>> forceRevalidation, time_t validationTime);
>>
>> ^
>> ../../../source/libs/poppler/poppler-src/poppler/Form.h:534:79: error:
>> unknown type name 'time_t'
>>   SignatureInfo *validateSignature(bool doVerifyCert, bool
>> forceRevalidation, time_t validationTime);
>>
>> ^
>> 2 errors generated.
>>
>> Hm, trunk ?
>
> Are you suggesting to distribute LuaTeX trunk for everyone?
I mean if it's  trunk or tags/1.06.3

trunk is aligned with texlive
and last time I have compiled TeX Live revision 46275 built
2018-01-10T10:00:19+00:00 UTC
was ok for Linux .




-- 
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] Labels and Enumerations

2018-01-15 Thread Rik Kabel

Hans,

Even with the local scope, I cannot get multiple enumerations in a 
paragraph at the same time as I get inright labels in footnotes. The 
footnote enumerations appear only with display=yes, but that causes 
paragraph breaks after each enumeration. The default alignment works, 
but I need marginal indices.


Labels seem to me a bit more flexible here since they do not require 
paragraph semantics for termination. I am not looking for a taggable 
mark, simply a visible reference index to which reference can be applied.


So, with enumerations providing no benefit and introducing additional 
problems, is it unreasonable to request that labels be officially 
supported in MKIV and not marked as MKII relicts?


Here is my latest test harness.

   \defineconstructionalternative
  [mylabel]
  [renderingsetup=constructionrenderings:mylabel,
   width=]

   \startsetups[constructionrenderings:mylabel]
  \dontleavehmode
  \inright[scope=local]{\flushconstructionheadbox}
   \stopsetups
   %% constructionrenderings testing alternatives
   % \inright[scope=local]{\flushconstructionheadbox}
   % \flushconstructionheadbox
   % \inright{\flushconstructionheadbox}

   \defineenumeration
  [Enu]
  [alternative=mylabel,
   display=no,
   before=,
   after=]

   \definelabel
  [Lab]
  [alternative=mylabel,
   before=,
   after=]

   \definenote
  [endnote]
   \setupnotation
  [endnote]
  [way=bytext,
   location=none,
   conversion=numbers]

   \definenote
  [footnote]
   \setupnotation
  [footnote]
  [way=bypage,
   numberconversion=set 2]

   \define\testTextOne{\quotation{\startEnu\input ward \stopEnu}
    And the rest of the paragraph.}

   \define\testTextTwo{\startEnu\input jojomayer \stopEnu
    \quotation{\startEnu\input ward \stopEnu}
    And the rest of the paragraph.}

   \define\testTextThree{\Lab\input jojomayer
  \quotation{\Lab\input ward }
  And the rest of the paragraph.}

   \setupwhitespace[small]

   \starttext

    \startchapter[title=bar]

    Paragraph with one enumeration: \testTextOne\ A footnote with
    one enumeration\footnote{\testTextOne} and an endnote with one
    enumeration.\endnote{\testTextOne}

    Paragraph with two enumerations: \testTextTwo\ A footnote with
    two enumerations\footnote{\testTextTwo} and an endnote with two
    enumeration.\endnote{\testTextTwo}

    Paragraph with two labels: \testTextThree\ A footnote with
    two labels\footnote{\testTextThree} and an endnote with two
    labels.\endnote{\testTextThree}

    \stopchapter

    \startchapter[title=notes]

    \placenotes[endnote]

    \stopchapter

   \stoptext

--
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: [NTG-context] luatex binary is too old

2018-01-15 Thread Mojca Miklavec
On 15 January 2018 at 20:54, luigi scarso  wrote:
> Il 15 gen 2018 20:52, "Mojca Miklavec" ha scritto:
> On 15 January 2018 at 15:26, Mojca Miklavec wrote:
>> On 15 January 2018 at 14:56, Hans Hagen wrote:
>>> On 1/15/2018 2:47 PM, Roger Mason wrote:

 : Your luatex binary is too old, you need at least version 1.05!

 Where do I get the updated luatex binary?

 I'm running on FreeBSD 10.3, 32 bit.
>>>
>>> Does that binary come from the garden too?
>>
>> I can take a look.
>>
>> It's quite possible that FreeBSD didn't get updated after the problems
>> with firewalls and networks being shifted around at both ends.
>
> I tried to compile it, but it fails with
>
> In file included from
> ../../../source/libs/poppler/poppler-src/poppler/Annot.cc:62:
> In file included from
> ../../../source/libs/poppler/poppler-src/poppler/PDFDoc.h:53:
> ../../../source/libs/poppler/poppler-src/poppler/Form.h:271:79: error:
> unknown type name 'time_t'
>   SignatureInfo *validateSignature(bool doVerifyCert, bool
> forceRevalidation, time_t validationTime);
>
> ^
> ../../../source/libs/poppler/poppler-src/poppler/Form.h:534:79: error:
> unknown type name 'time_t'
>   SignatureInfo *validateSignature(bool doVerifyCert, bool
> forceRevalidation, time_t validationTime);
>
> ^
> 2 errors generated.
>
> Hm, trunk ?

Are you suggesting to distribute LuaTeX trunk for everyone?

Anyway, the same problem happens with the latest TeX Live sources as well.

I added
   #include 
to poppler-src/poppler/Form.h after which the build proceeds, but
later fails again building ICU.

../../../libs/icu/icu-src/source/i18n/coll.cpp:157:28: error: pasting
formed 'u"Collator"', an invalid preprocessing token
: ICULocaleService(UNICODE_STRING_SIMPLE("Collator"))
   ^

Mojca
___
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] luatex binary is too old

2018-01-15 Thread luigi scarso
Il 15 gen 2018 20:52, "Mojca Miklavec"  ha
scritto:

On 15 January 2018 at 15:26, Mojca Miklavec wrote:
> On 15 January 2018 at 14:56, Hans Hagen wrote:
>> On 1/15/2018 2:47 PM, Roger Mason wrote:
>>>
>>> : Your luatex binary is too old, you need at least version 1.05!
>>>
>>> Where do I get the updated luatex binary?
>>>
>>> I'm running on FreeBSD 10.3, 32 bit.
>>
>> Does that binary come from the garden too?
>
> I can take a look.
>
> It's quite possible that FreeBSD didn't get updated after the problems
> with firewalls and networks being shifted around at both ends.

I tried to compile it, but it fails with

In file included from
../../../source/libs/poppler/poppler-src/poppler/Annot.cc:62:
In file included from
../../../source/libs/poppler/poppler-src/poppler/PDFDoc.h:53:
../../../source/libs/poppler/poppler-src/poppler/Form.h:271:79: error:
unknown type name 'time_t'
  SignatureInfo *validateSignature(bool doVerifyCert, bool
forceRevalidation, time_t validationTime);

  ^
../../../source/libs/poppler/poppler-src/poppler/Form.h:534:79: error:
unknown type name 'time_t'
  SignatureInfo *validateSignature(bool doVerifyCert, bool
forceRevalidation, time_t validationTime);

  ^
2 errors generated.

Mojca

___
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

___

Hm ,trunk ?
___
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] luatex binary is too old

2018-01-15 Thread Mojca Miklavec
On 15 January 2018 at 15:26, Mojca Miklavec wrote:
> On 15 January 2018 at 14:56, Hans Hagen wrote:
>> On 1/15/2018 2:47 PM, Roger Mason wrote:
>>>
>>> : Your luatex binary is too old, you need at least version 1.05!
>>>
>>> Where do I get the updated luatex binary?
>>>
>>> I'm running on FreeBSD 10.3, 32 bit.
>>
>> Does that binary come from the garden too?
>
> I can take a look.
>
> It's quite possible that FreeBSD didn't get updated after the problems
> with firewalls and networks being shifted around at both ends.

I tried to compile it, but it fails with

In file included from
../../../source/libs/poppler/poppler-src/poppler/Annot.cc:62:
In file included from
../../../source/libs/poppler/poppler-src/poppler/PDFDoc.h:53:
../../../source/libs/poppler/poppler-src/poppler/Form.h:271:79: error:
unknown type name 'time_t'
  SignatureInfo *validateSignature(bool doVerifyCert, bool
forceRevalidation, time_t validationTime);
  ^
../../../source/libs/poppler/poppler-src/poppler/Form.h:534:79: error:
unknown type name 'time_t'
  SignatureInfo *validateSignature(bool doVerifyCert, bool
forceRevalidation, time_t validationTime);
  ^
2 errors generated.

Mojca
___
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] context tarball distribution?

2018-01-15 Thread Hans Hagen

On 1/15/2018 3:59 PM, Martin Fechner wrote:

Dear list,

Our slightly paranoid system administrator refuses to pull context via
rsync on our development and production hosts. He says there's no
protection against someone who may tamper with the data on its transfer
like e.g. TLS-protected traffic via https.

So I got the following question from him:

Can ConTeXt be obtained as a tarball or zipfile? Preferably with version
identifiers in the name so he can ensure the parity of the installations
across severeal host.
why not download it on your own computer and then zip it; that way you 
can satisfy all needs


there's a zip file on our website but it doesn't have the binaries (we 
had that once but the garden rsync solution replaced that; it doesn't 
pay off to offer all kind of variants)


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] luatex binary is too old

2018-01-15 Thread Roger Mason
Hans Hagen  writes:


>> : Your luatex binary is too old, you need at least version 1.05!
>>
>> Where do I get the updated luatex binary?
>>
>> I'm running on FreeBSD 10.3, 32 bit.
> Does that binary come from the garden too?
>
> Hans

Yes, I did not compile it myself, if that is what you are asking.

Cheers,
Roger
___
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] context tarball distribution?

2018-01-15 Thread Martin Fechner

Dear list,

Our slightly paranoid system administrator refuses to pull context via
rsync on our development and production hosts. He says there's no
protection against someone who may tamper with the data on its transfer
like e.g. TLS-protected traffic via https.

So I got the following question from him:

Can ConTeXt be obtained as a tarball or zipfile? Preferably with version
identifiers in the name so he can ensure the parity of the installations
across severeal host.

Greetings, Martin

___
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] luatex binary is too old

2018-01-15 Thread Mojca Miklavec
On 15 January 2018 at 14:56, Hans Hagen wrote:
> On 1/15/2018 2:47 PM, Roger Mason wrote:
>>
>> : Your luatex binary is too old, you need at least version 1.05!
>>
>> Where do I get the updated luatex binary?
>>
>> I'm running on FreeBSD 10.3, 32 bit.
>
> Does that binary come from the garden too?

I can take a look.

It's quite possible that FreeBSD didn't get updated after the problems
with firewalls and networks being shifted around at both ends.

Mojca
___
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] luatex binary is too old

2018-01-15 Thread Hans Hagen

On 1/15/2018 2:47 PM, Roger Mason wrote:

Hello,

I just updated ConTeXt:

context --version

resolvers   | trees | analyzing 'home:texmf'
resolvers   | globbing | confusing filename, name: 'README.txt', lower: 
'readme.txt', already: 'ReadMe.txt'
mtx-context | ConTeXt Process Management 1.02
mtx-context |
mtx-context | main context file: 
/opt/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2018.01.14 15:55

When I try to compile a file:

context --mode=manuscript --result=MineralsGemsMS.pdf --purgeall
MineralsGems.tex

I get this error:

: Your luatex binary is too old, you need at least version 1.05!

Where do I get the updated luatex binary?

I'm running on FreeBSD 10.3, 32 bit.

Does that binary come from the garden too?

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] luatex binary is too old

2018-01-15 Thread Roger Mason
Hello,

I just updated ConTeXt:

context --version   
   

resolvers   | trees | analyzing 'home:texmf'
resolvers   | globbing | confusing filename, name: 'README.txt', lower: 
'readme.txt', already: 'ReadMe.txt'
mtx-context | ConTeXt Process Management 1.02
mtx-context |
mtx-context | main context file: 
/opt/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2018.01.14 15:55

When I try to compile a file:

context --mode=manuscript --result=MineralsGemsMS.pdf --purgeall
MineralsGems.tex

I get this error:

: Your luatex binary is too old, you need at least version 1.05!

Where do I get the updated luatex binary?

I'm running on FreeBSD 10.3, 32 bit.

Thanks for any help,
Roger
___
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] Labels and Enumerations

2018-01-15 Thread Hans Hagen

On 1/14/2018 9:37 PM, Rik Kabel wrote:

On 2018-01-14 09:46, Hans Hagen wrote:

On 1/13/2018 10:17 PM, Rik Kabel wrote:
I would like to request the restoration of labels (\definelabel) to 
full citizenship in MKIV. While enumerations are more flexible in 
many ways, they cannot replace one particular use of labels if find 
necessary. Enumerations are paragraph entities, while labels are not 
so restricted.


I use labels displayed as numbers in the margin to serially identify 
quotations in a book about the development of quotation and 
misquotation, at the same time generating reference information for 
cross-referencing. While most quotations are blocks and can be 
handled by enumerations, many are in-line quotations, and enumeration 
cannot be used for these.


The wiki describes enumerations as the MKIV replacement for labels, 
and the documentation as far as I can see omits \definelabel. Unless 
there is something else supported in MKIV that can assume this 
function of labels, can we please have full support for labels? I 
would not want to see labels deprecated before the functionality is 
reproduced.


(Of course, if you can suggest how enumeration can be adapted to this 
requirement, or suggest an alternative mechanism, this request can be 
rejected.)


two options:

\defineconstructionalternative
  [mylabel]
  [renderingsetup=constructionrenderings:mylabel,
   width=]

\startsetups[constructionrenderings:mylabel]
    \dontleavehmode
    \flushconstructionheadbox
\stopsetups

\defineenumeration[two][alternative=mylabel,display=no,before=,after=]

\definelabel[foo][way=bychapter,prefix=chapter]

\starttext

    \startchapter[title=bar]

    here \starttwo\stoptwo \input tufte

    here \foo[xx] \input tufte

    whatever \in{foo}[xx]

    \stopchapter

\stoptext


I played a bit more with enumerations and resolved one issue, I think. 
The forced paragraph break is a feature of the default before/after keys 
(both of which I need to null). Once this is done, enumerations can be 
used for in-line text as well, and when an explicit \par is added to 
\footnotes, the enumeration index appears there, unlike labels, where it 
does not appear.


use

\startsetups[constructionrenderings:mylabel]
\dontleavehmode
\inright[scope=local]{\flushconstructionheadbox}
\stopsetups

also, an enumeration wants a paragraph as it needs to handle the 
following text an danythign between \whatever and the next \par (or 
emptyline) becomes that text so for the footnote it sees the end outside 
a group / argument


Can you explain why the enumeration defined with constructionalternative 
rendering fails in footnotes, as shown in the following example? I 
suspect it has to do with my not understanding the use of 
\flushconstructionheadbox.


\defineconstructionalternative
   [mylabel]
   [renderingsetup=constructionrenderings:mylabel,
    width=]

\startsetups[constructionrenderings:mylabel]
     \inright{\dontleavehmode\flushconstructionheadbox}
\stopsetups

\defineenumeration[two][alternative=mylabel, % use mylabel rendering
     headcolor=darkgreen,
     text=,   % no name preceding
label number
     display=no,  % suppresses line
break with constructs
     before=, % no added text before
label number
     after=]  % no added text after
label number

\defineenumeration[why][alternative=inright, % use inright rendering
     headcolor=blue,
     display=yes, % seems to be the default
     text=,   % no name preceding
label number
     before=, % no added text before
label number
     after=]  % no added text after
label number

\definelabel[foo][text=,headcolor=red,alternative=inright]

\starttext

         \startchapter[title=bar]

     here \starttwo[reference=aa]\stoptwo \input ward
\starttwo[reference=bb]\stoptwo \input ward

     here as well?\footnote{\starttwo[reference=cc]\stoptwo This
fails.\par}

     whatever \in{two}[aa] and \in{two}[bb] and \in{two}[cc]

     \blank

     here \two[dd]\input ward \two[ee]\input ward

     here as well?\footnote{\two[ff]This fails.\par}

     whatever \in{two}[dd] and \in{two}[ee] and \in{two}[ff] and why
     is this section not three paragraph?

     \blank

     here \why[gg]\input ward \why[hh] \input ward

     here as well?\footnote{\why[ii]This works!\par}

     whatever \in{why}[gg] and \in{why}[hh] and \in{why}[ii]

     \blank

     here \foo[xx] \input ward \foo[yy] \input ward

     here as well?\footnote{\foo[zz]This