Re: [NTG-context] \setvariables and database module

2018-01-31 Thread Otared Kavian 


> On 31 Jan 2018, at 18:11, Wolfgang Schuster  
> wrote:
> 
>> […]
>> Thanks again, but I wonder where did you find this trick?… in i-context.pdf 
>> there is no entry for \defineseparatedlist…
> 
> setup-en.pdf (and i-context.pdf) contains only commands from the core. There 
> are lists for many modules (e.g. i-database.xml contains the options for the 
> database module) but no PDF which shows them.

Indeed looking for the file i-database.xml I discovered that in
context-minimal/tex/texmf-context/tex/context/interface/mkiv/
there are lots of file such as i-ABC.xml, which can be typeset in order to 
obtain a pdf. 
A great piece of information… thanks!

Best regards: OK

___
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] \setvariables and database module

2018-01-31 Thread Wolfgang Schuster 



Otared Kavian 
31. Januar 2018 um 17:58

Yes it does the job!
Thanks again, but I wonder where did you find this trick?… in 
i-context.pdf there is no entry for \defineseparatedlist…


setup-en.pdf (and i-context.pdf) contains only commands from the core. 
There are lists for many modules (e.g. i-database.xml contains the 
options for the database module) but no PDF which shows them.


Wolfgang
___
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] \setvariables and database module

2018-01-31 Thread Otared Kavian 


> On 31 Jan 2018, at 17:40, Wolfgang Schuster  
> wrote:
> 
>> […]
>> 
> Add “strip=yes” to remove spaces around the cells.
> 
> \defineseparatedlist
>   [seplisttalk]
>   [separator={;},
>command=\maketalk,
>strip=yes]
> 

Yes it does the job! 
Thanks again, but I wonder where did you find this trick?… in i-context.pdf 
there is no entry for \defineseparatedlist…

Best regards: OK___
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] \setvariables and database module

2018-01-31 Thread Wolfgang Schuster 



Otared Kavian 
30. Januar 2018 um 16:53
Hi again Wolfgang,

I think I understood what is going wrong with my example after your 
hint: I have to remove all spaces around the separator and remove also 
the braces around each entry.

That is the following works fine:

\startseplisttalk
Hacker;Up to date hacking;hacker.jpg
Hacker;Up to date hacking;hacker.jpg
\stopseplisttalk

while the following does not (as far as the filename is concerned):

\startseplisttalk
{Hacker};{Up to date hacking};{hacker.jpg}
Hacker ; Up to date hacking ; hacker.jpg
\stopseplisttalk


Add “strip=yes” to remove spaces around the cells.

\defineseparatedlist
  [seplisttalk]
  [separator={;},
   command=\maketalk,
   strip=yes]

Wolfgang
___
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] Expansion help needed, getvariable and TABLE

2018-01-31 Thread Hans Hagen 

On 1/31/2018 4:40 PM, Rik Kabel wrote:

On 2018-01-31 09:54, Wolfgang Schuster wrote:

Rik Kabel schrieb:

\starttexdefinition doTableRowExpB #SET
    \define\A{\getvariable{#SET}{a}}
    \define\B{\getvariable{#SET}{b}}
    \define\C{\getvariable{#SET}{c}}
    \bTR
  \expanded{\bTC\A\eTC}
  \expanded{\bTC\B\eTC}
  \expanded{\bTC\C\eTC}
    \eTR
\stoptexdefinition


You can’t use \define but it creates non expandable commands
(which can be solved when you use \defineexpandable instead)
and there is no need for this extra step.

\starttexdefinition doTableRowExpB #SET
    \bTR
  \expanded{\bTC\getvariable{#SET}{a}\eTC}
  \expanded{\bTC\getvariable{#SET}{b}\eTC}
  \expanded{\bTC\getvariable{#SET}{c}\eTC}
    \eTR
\stoptexdefinition

Wolfgang
___ 

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
___


Great. This does the job, and allows assigning more 
semantically-meaningful names to the elements.


\starttexdefinition doTableRowExpB #SET
     \defineexpandable\A{\getvariable{#SET}{a}}
     \defineexpandable\B{\getvariable{#SET}{b}}
     \defineexpandable\C{\getvariable{#SET}{c}}
     \bTR
   \expanded{\bTC\A\eTC}
   \expanded{\bTC\B\eTC}
   \expanded{\bTC\C\eTC}
     \eTR
\stoptexdefinition

I see no performance difference on a much larger test, and I think that 
the readability is improved (and thus the opportunity for simple 
mistakes) when the hundreds of \getvariable macros are refactored into a 
few macro definitions.


maybe the next can convince you then

\starttexdefinition doTableRowExpB #SET
\expanded {\bTR
  \bTC\getvariable{#SET}{a}\eTC
  \bTC\getvariable{#SET}{b}\eTC
  \bTC\getvariable{#SET}{c}\eTC
\eTR}
\stoptexdefinition

with

\starttexdefinition doTableRowExpB #SET
\normalexpanded {\bTR
  \bTC\getvariable{#SET}{a}\eTC
  \bTC\getvariable{#SET}{b}\eTC
  \bTC\getvariable{#SET}{c}\eTC
\eTR}
\stoptexdefinition

being a bit faster

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] Expansion help needed, getvariable and TABLE

2018-01-31 Thread Rik Kabel 

On 2018-01-31 09:54, Wolfgang Schuster wrote:

Rik Kabel schrieb:

\starttexdefinition doTableRowExpB #SET
    \define\A{\getvariable{#SET}{a}}
    \define\B{\getvariable{#SET}{b}}
    \define\C{\getvariable{#SET}{c}}
    \bTR
  \expanded{\bTC\A\eTC}
  \expanded{\bTC\B\eTC}
  \expanded{\bTC\C\eTC}
    \eTR
\stoptexdefinition


You can’t use \define but it creates non expandable commands
(which can be solved when you use \defineexpandable instead)
and there is no need for this extra step.

\starttexdefinition doTableRowExpB #SET
    \bTR
  \expanded{\bTC\getvariable{#SET}{a}\eTC}
  \expanded{\bTC\getvariable{#SET}{b}\eTC}
  \expanded{\bTC\getvariable{#SET}{c}\eTC}
    \eTR
\stoptexdefinition

Wolfgang
___ 

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
___


Great. This does the job, and allows assigning more 
semantically-meaningful names to the elements.


   \starttexdefinition doTableRowExpB #SET
    \defineexpandable\A{\getvariable{#SET}{a}}
    \defineexpandable\B{\getvariable{#SET}{b}}
    \defineexpandable\C{\getvariable{#SET}{c}}
    \bTR
  \expanded{\bTC\A\eTC}
  \expanded{\bTC\B\eTC}
  \expanded{\bTC\C\eTC}
    \eTR
   \stoptexdefinition

I see no performance difference on a much larger test, and I think that 
the readability is improved (and thus the opportunity for simple 
mistakes) when the hundreds of \getvariable macros are refactored into a 
few macro definitions.


Thank you once again.

--
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] Expansion help needed, getvariable and TABLE

2018-01-31 Thread Wolfgang Schuster 

Rik Kabel schrieb:

\starttexdefinition doTableRowExpB #SET
\define\A{\getvariable{#SET}{a}}
\define\B{\getvariable{#SET}{b}}
\define\C{\getvariable{#SET}{c}}
\bTR
  \expanded{\bTC\A\eTC}
  \expanded{\bTC\B\eTC}
  \expanded{\bTC\C\eTC}
\eTR
\stoptexdefinition


You can’t use \define but it creates non expandable commands
(which can be solved when you use \defineexpandable instead)
and there is no need for this extra step.

\starttexdefinition doTableRowExpB #SET
\bTR
  \expanded{\bTC\getvariable{#SET}{a}\eTC}
  \expanded{\bTC\getvariable{#SET}{b}\eTC}
  \expanded{\bTC\getvariable{#SET}{c}\eTC}
\eTR
\stoptexdefinition

Wolfgang
___
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] Expansion help needed, getvariable and TABLE

2018-01-31 Thread Rik Kabel 

On 2018-01-31 01:04, Wolfgang Schuster wrote:



Rik Kabel 
31. Januar 2018 um 03:10

Listers,

I have a problem, and a question on ConTeXt programming efficiency.

In the example below, I have a set of variables. When these are 
reference directly via \getvariable, everything works as expected in 
simple text and in TABLEs. When I \define a macro to the 
\getvariable, that works in simple text, but only the value of the 
last iteration appears in the TABLE. The macro definition is saved 
and when it is used, that is the value that it has.


So, how can I \define (or \def, ...) a macro to the expanded value to 
avoid this? That is the problem.


The question is, Is there is any advantage to be had in doing this? 
Assume that the value is referenced many (tens of) times. There seems 
to be an aesthetic value of factoring out the multiple identical 
instances of the \getvariable syntax and assigning a more 
semantically informative name, but beyond that, is there any other value?



Natural tables collect the content of all cells to perform the width 
and height calculations
and you have to expand the content of the cells to get the current 
value of \getvariable.


\starttexdefinition unexpanded doTableRow #SET
    \bTR
  \expanded{\bTC\getvariable{#SET}{a}\eTC}
  \expanded{\bTC\getvariable{#SET}{b}\eTC}
    \eTR
\stoptexdefinition


BTW: You can use the \processcommacommand command when you save your 
lists in a macro (no need for \expandafter).


\defineexpandable\Sets{one,two}

\processcommacommand[\Sets]\doInlineTextExp


Wolfgang


Thank you for the help and the processcommacommand bit. However, the 
problem is still there (and I was just wrong in my own follow-up).


Below is an updated example with and without the \expanded{\bTC...

It does not seem to make a difference here, but perhaps it is needed in 
some situations.


My question is about factoring the \getvariable out of the \bTC rows (in 
this example) and \defining a simpler macro to hold the value. Should it 
be done, and if so, how?


   % macros=mkvi engine=luajittex

   \setvariables  [one]
   [a=1,b=1b,c=1c]
   \setvariables  [two]
   [a=2a,b=2,c=2c]

   \defineexpandable  \Sets
   {one,two}

   \starttexdefinition unexpanded doInlineText #SET
    Direct: \getvariable{#SET}{a} \getvariable{#SET}{b}\
    \getvariable{#SET}{c}\par
   \stoptexdefinition

   \starttexdefinition unexpanded doTableRow #SET
    \bTR
  \bTC\getvariable{#SET}{a}\eTC
  \bTC\getvariable{#SET}{b}\eTC
  \bTC\getvariable{#SET}{c}\eTC
    \eTR
   \stoptexdefinition

   \starttexdefinition doInlineTextExpA #SET
    \define\A{\getvariable{#SET}{a}}
    \define\B{\getvariable{#SET}{b}}
    \define\C{\getvariable{#SET}{c}}
    Factored A: \A\ \B\ \C\par
   \stoptexdefinition

   \starttexdefinition doTableRowExpA #SET
    \define\A{\getvariable{#SET}{a}}
    \define\B{\getvariable{#SET}{b}}
    \define\C{\getvariable{#SET}{c}}
    \bTR
  \bTC\A\eTC
  \bTC\B\eTC
  \bTC\C\eTC
    \eTR
   \stoptexdefinition

   \starttexdefinition doInlineTextExpB #SET
    \define\A{\getvariable{#SET}{a}}
    \define\B{\getvariable{#SET}{b}}
    \define\C{\getvariable{#SET}{c}}
    Factored B: \A\ \B\ \C\par
   \stoptexdefinition

   \starttexdefinition doTableRowExpB #SET
    \define\A{\getvariable{#SET}{a}}
    \define\B{\getvariable{#SET}{b}}
    \define\C{\getvariable{#SET}{c}}
    \bTR
  \expanded{\bTC\A\eTC}
  \expanded{\bTC\B\eTC}
  \expanded{\bTC\C\eTC}
    \eTR
   \stoptexdefinition

   \starttext

    \processcommacommand[\Sets]\doInlineText

    \bTABLE[frame=off]
  \bTABLEhead
    \bTR[nc=2]
  \bTH Direct\eTH
    \eTR
  \eTABLEhead
  \bTABLEbody
  \processcommacommand[\Sets]\doTableRow
  \eTABLEbody
    \eTABLE

    \processcommacommand[\Sets]\doInlineTextExpA

    \bTABLE[frame=off]
  \bTABLEhead
    \bTR[nc=2]
  \bTH Factored A\eTH
    \eTR
  \eTABLEhead
  \bTABLEbody
    \processcommacommand[\Sets]\doTableRowExpA
  \eTABLEbody
    \eTABLE

    \processcommacommand[\Sets]\doInlineTextExpB

    \bTABLE[frame=off]
  \bTABLEhead
    \bTR[nc=2]
  \bTH Factored B\eTH
    \eTR
  \eTABLEhead
  \bTABLEbody
    \processcommacommand[\Sets]\doTableRowExpB
  \eTABLEbody
    \eTABLE

   \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

Re: [NTG-context] Spurious space in \definestartstop

2018-01-31 Thread Wolfgang Schuster 



Henri Menke 
30. Januar 2018 um 21:46
On Tue, 2018-01-30 at 21:24 +0100, Wolfgang Schuster wrote:

Henri Menke 30. Januar 2018 um 21:12
On Tue, 2018-01-30 at 11:58 +0100, Hans Hagen wrote:

On 1/30/2018 11:34 AM, Henri Menke wrote:

On 01/30/2018 09:17 PM, Hans Hagen wrote:

On 1/30/2018 2:54 AM, Henri Menke wrote:

Dear list,

the title says it all.  Please add \ignorespaces in a place you deem
appropriate.  MWE is below.

sometimes you will also add \removeuwantedspaces in the stop

I'm confused.  Does that mean there is going to be a fix?
no, why should there be? spaces are never ignored after the last [...] 
that is checked for unless a command has an explicit \ignorespaces

I'm not convinced.  Both "before" and "commands" see a \relax and therefore
\ignorespaces is dropped.  I can put \removeunwantedspaces there but that
deletes the space before \start.  The \framed command correctly drops the
space
after the options.

---

\definestartstop
   [spurious space a]
   [before=\ignorespaces,
after=\removeunwantedspaces]

\definestartstop
   [spurious space b]
   [before=\removeunwantedspaces,
after=\removeunwantedspaces]

\starttext

Hello Foo Bar World

Hello \start[spurious space a] Foo Bar \stop\ World
%   ^^^ neither space^^^ is skipped

Hello \start[spurious space b] Foo Bar \stop\ World
%   ^^^ skips this space ^^^ instead of this

Hello \startframed[offset=overlay] Foo Bar \stopframed\ World
% That's the behaviour I'm looking for.

\stoptext


  You assume \start[<...>] ... \stop is linked to \definestartstop but this
isn’t the case,
what the environment does is to generate a start-command with the argument
but this works for every environment, e.g. \start[itemize] ... \stop does the
same
as \startitemize ... \stopitemize.


I'm not asking to add \ignorespaces to the definition of \start.  I'm rather
asking, where I have to but \ignorespaces in the setup to eat the space after
the options I pass to \start.

Why do use insinst on the use of \start, when you create a new 
command/environment
with \definestartstop you get additional commands for the instance where 
the space

at the begin of the environment are gobbled.

\definestartstop[Highlight][style=italic,color=red]

\starttext

Text \Highlight{Text} Text

\blank

\input ward\par

\startHighlight
\input ward
\stopHighlight

\input ward

\stoptext

To answer your question where you can add \ignorespace, there is no way 
to add it.


Wolfgang
___
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] Question about an environment

2018-01-31 Thread Fabrice Couvreur 
Hello,
Maybe I have not been clear enough about what I would like to do ?
In the first exercise, I get this:

*Ex1* BlablaBlablaBlablaBlablaBlablaBlablaBlablaBlabla
BlablaBlablaBlablaBlablaBlablaBlablaBlablaBlabla

In the second exercise, this:

*Ex2*

1.

2.

3.

I would like to do this:

*Ex2* 1.
2.
3.

Thank you.
Fabrice

2018-01-28 22:54 GMT+01:00 Fabrice Couvreur :

> Hello,
> How to make the first item on the baseline of the numbering as in the
> first exercise ?
> Thanks.
> Fabrice
>
> \defineframed
>   [ACFRAME]
>   [frame=off,
>boffset=0pt,
>width=fit,
>align=flushleft,
>location=low,
>background=color,
>backgroundcolor=MyColorA]
>
> \defineframed
>   [EXFRAME]
>   [frame=off,
>offset=0pt,
>location=low,
>width=\struttotal,
>background=color,
>backgroundcolor=black,
>foregroundcolor=white,
>forgroundstyle=bold]
>
> \defineprocessor[ACPROCESSOR][command=\EXFRAME]
> \defineconversionset[ACCONVERSION][][ACPROCESSOR->n]
>
> \defineenumeration
>   [ex]
>   [text=,
>width=fit,
>numberconversionset=ACCONVERSION,
>alternative=serried,
>number=yes]
>
> \starttext
> \startex
> \input ward
> \stopex
> \startex
>   \startitemize[n]
>   \item One
>   \item Two
>   \item Three
>   \stopitemize
> \stopex
> \stoptext
>
___
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] Support for musl

2018-01-31 Thread Hans Hagen 

On 1/31/2018 10:26 AM, Mojca Miklavec wrote:

On 30 January 2018 at 00:23, Henri wrote:

It looks like we are going to get upstream support for musl from TeX live.

There is this extremely long thread on the tlbuild mailing list.
https://tug.org/pipermail/tlbuild/2018q1/003972.html


Thanks a lot. This *enormously* simplifies things. (After your initial
reply to the tlbuild I nearly lost hope, please don't repeat such
attempts ... :)


An automated build on Alpine Linux has been included in the TeX live continuous
integration on GitHub.
https://github.com/TeX-Live/texlive-source/blob/master/.travis.yml

What would I have to do in order to get an automated build for ConTeXt
standalone for musl?


- We need "the latest" luatex. (It's not yet clear to me what "the
latest" means at this moment as it's still totally confusing to me and
we didn't configure the other builders yet either. Luigi sent me a
relatively confusing message about which branch should be used.)


We have release (1.07), trunk (also 1.07 but more modern and hipper as 
it does lua 53) and experimental (our playground). The garden can use 
trunk while texlive uses release.



- It would help to have a simple patch for
   http://distribution.contextgarden.net/setup/first-setup.sh
   to correctly detect the platform


someone has to provide that then as i have no clue (i use opensuse on 
servers which works out of the box and linux subsystem on windows which 
also works ok)



- I would copy the TL binaries from you for now and later take them
from the subversion repository (I assume that would happen once the
updates are frozen).


Hans might be interested in detecting musl libc automatically, which I have
recently merged into GNU autotools:
https://git.savannah.gnu.org/cgit/config.git/commit/?id=3d00f60242f1726fc6eaa38e09435a969ee7ebe5
It uses ldd to detect whether musl is used because ldd prints "musl libc" to
stderr.
https://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1538


Does that really matter then? Aren't those system libs loaded by luatex 
itself?



That's something which I still believe should be somehow "hardcoded"
into LuaTeX itself, so that LuaTeX itself would be aware of which
platform it was compiled for. At the moment part of detection happens
in mtxrun, but that's somewhat strange.


There is some code in luatex but the more one hard-codes the worse it 
gets when it's wrong. Only the shell knows ... (we had these many many 
hardcodes paths in some texmf vars long ago ... failures). In the end, 
all that is needed to know the binary path. In fact, if texlive wasn't 
multi-platform-at-the-same-time we could let all binaries fly to


tex/texmf-binaries

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] Support for musl

2018-01-31 Thread luigi scarso 
On Wed, Jan 31, 2018 at 10:26 AM, Mojca Miklavec
 wrote:
> - We need "the latest" luatex. (It's not yet clear to me what "the
> latest" means at this moment as it's still totally confusing to me and
> we didn't configure the other builders yet either. Luigi sent me a
> relatively confusing message about which branch should be used.)
I wonder, the things are the same from at least one year (perhaps two):
texlive <-> tags
garden  <-> trunk
only hans. <-> experimental

-- 
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] Support for musl

2018-01-31 Thread Mojca Miklavec 
On 30 January 2018 at 00:23, Henri wrote:
> It looks like we are going to get upstream support for musl from TeX live.
>
> There is this extremely long thread on the tlbuild mailing list.
> https://tug.org/pipermail/tlbuild/2018q1/003972.html

Thanks a lot. This *enormously* simplifies things. (After your initial
reply to the tlbuild I nearly lost hope, please don't repeat such
attempts ... :)

> An automated build on Alpine Linux has been included in the TeX live 
> continuous
> integration on GitHub.
> https://github.com/TeX-Live/texlive-source/blob/master/.travis.yml
>
> What would I have to do in order to get an automated build for ConTeXt
> standalone for musl?

- We need "the latest" luatex. (It's not yet clear to me what "the
latest" means at this moment as it's still totally confusing to me and
we didn't configure the other builders yet either. Luigi sent me a
relatively confusing message about which branch should be used.)
- It would help to have a simple patch for
  http://distribution.contextgarden.net/setup/first-setup.sh
  to correctly detect the platform
- I would copy the TL binaries from you for now and later take them
from the subversion repository (I assume that would happen once the
updates are frozen).

> Hans might be interested in detecting musl libc automatically, which I have
> recently merged into GNU autotools:
> https://git.savannah.gnu.org/cgit/config.git/commit/?id=3d00f60242f1726fc6eaa38e09435a969ee7ebe5
> It uses ldd to detect whether musl is used because ldd prints "musl libc" to
> stderr.
> https://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1538

That's something which I still believe should be somehow "hardcoded"
into LuaTeX itself, so that LuaTeX itself would be aware of which
platform it was compiled for. At the moment part of detection happens
in mtxrun, but that's somewhat strange.

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
___