Re: [NTG-context] names of cached images

[Jano Kula]

Hi Aditya!

On Fri, Jul 2, 2021, 17:43 Aditya Mahajan  wrote:

>
> On Fri, 2 Jul 2021, Jano Kula wrote:
>
> > Hello again,
> >
> > likely a bug and one question. Using this code with lmtx:
> >
> > \starttext
> > \externalfigure[mill][width=40mm,cache=./first,conversion=gray.pdf] %
> > mill...
> > \externalfigure[mill][width=40mm,cache=.,conversion=gray.pdf]   %
> > m_k_i_v_mill...
> > \externalfigure[mill][width=40mm,cache=./second]% no
> > visible caching
> > \stoptext
> >
> > *First two figures*
> > Chached image in the ./cache subdirectory has a lmtx name without prefix,
> > the cached image in the current directory has mkiv syntax with  m_k_i_v_
> > prefix.
> >
> > *Third figure*
> > The images are cached to a specified directory, only when some conversion
> > is used. I'd like to cache images without any transformation. Is there
> any
> > conversion which doesn't alter the figure, just caches it? Is new
> > conversion type needed? Or is there other way to force caching without
> > conversion?
>
> Conversion is costly and that is why caching makes sense there. What is
> the benefit of caching (i.e., simply copying the file to a different
> directory) when there is no conversion?
>

Images are on the remote sever and I don't want to download them with every
run. Images don't change, changed ones have different ID. Encapsualating
jpgs into pdfs might be the right conversion, because pdf inclusion is
fast, right? So I probably answered myself: write a conversion jpg -> pdf
without any changes to the image.

J.



> Aditya
>
> ___
> 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] names of cached images

[Aditya Mahajan]

On Fri, 2 Jul 2021, Jano Kula wrote:

> Hello again,
> 
> likely a bug and one question. Using this code with lmtx:
> 
> \starttext
> \externalfigure[mill][width=40mm,cache=./first,conversion=gray.pdf] %
> mill...
> \externalfigure[mill][width=40mm,cache=.,conversion=gray.pdf]   %
> m_k_i_v_mill...
> \externalfigure[mill][width=40mm,cache=./second]% no
> visible caching
> \stoptext
> 
> *First two figures*
> Chached image in the ./cache subdirectory has a lmtx name without prefix,
> the cached image in the current directory has mkiv syntax with  m_k_i_v_
> prefix.
> 
> *Third figure*
> The images are cached to a specified directory, only when some conversion
> is used. I'd like to cache images without any transformation. Is there any
> conversion which doesn't alter the figure, just caches it? Is new
> conversion type needed? Or is there other way to force caching without
> conversion?

Conversion is costly and that is why caching makes sense there. What is the 
benefit of caching (i.e., simply copying the file to a different directory) 
when there is no conversion?

Aditya
___
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] Rolling out a pandoc-context publication workflow in an organization

[Aditya Mahajan]

On Fri, 2 Jul 2021, Jan U. Hasecke wrote:

> 
> Dear Hans,
> 
> thanks for the hint to the repo. I remember that it was mentiooned before.
> 
> Am 02.07.21 um 10:42 schrieb Hans Hagen:
> > official    : https://bitbucket.org/phg/context-mirror/src/beta/

There is also

github: https://github.com/contextgarden/context-mirror

which simply mirrors the bitbucket repo.

> Is there a how-to-bootstrap-from-repository? How can I get a running 
> context with the repo?

These repos contain just the contents on texmf-context, but not the binaries 
(or sources of binaries). You need the binaries (and fonts!) to get a working 
installation. 

Aditya___
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] names of cached images

[Jano Kula]

Hello again,

likely a bug and one question. Using this code with lmtx:

\starttext
\externalfigure[mill][width=40mm,cache=./first,conversion=gray.pdf] %
mill...
\externalfigure[mill][width=40mm,cache=.,conversion=gray.pdf]   %
m_k_i_v_mill...
\externalfigure[mill][width=40mm,cache=./second]% no
visible caching
\stoptext

*First two figures*
Chached image in the ./cache subdirectory has a lmtx name without prefix,
the cached image in the current directory has mkiv syntax with  m_k_i_v_
prefix.

*Third figure*
The images are cached to a specified directory, only when some conversion
is used. I'd like to cache images without any transformation. Is there any
conversion which doesn't alter the figure, just caches it? Is new
conversion type needed? Or is there other way to force caching without
conversion?

Thank you,
Jano


On Wed, Jun 9, 2021 at 3:23 PM Jano Kula  wrote:

> Hello Hans,
>
> On Sun, Jun 6, 2021 at 4:56 PM Hans Hagen  wrote:
>
>> On 6/6/2021 1:16 PM, Jano Kula wrote:
>> > Hello list,
>> >
>> > usingconversion=gray.pdf in lmtx the cached images' names have some
>> > string in their name. I thought it's a name of random sequence of
>> luatex
>> > cache, but the string is the same on other machines and I don't know,
>> > where it comes from. mkiv used to have m_k_i_v_ string there.
>> >
>> > hacker.pdf = source image
>> > hacker_jpg_c60ccda70ef92e32d7a6334f31c23259.gray.pdf = cached linux
>> > hacker_jpg_c60ccda70ef92e32d7a6334f31c23259.gray.pdf = cached win
>> >
>> > MWE
>> > \starttext
>> > \externalfigure[hacker]
>> >  [cache=./,
>> >  conversion=gray.pdf]
>> > \stoptext
>> >
>> > Is it intended behavior?
>> sure, something like that is always intended; it's an md5 of a hash of
>> all relevant parameters so that when you change one (say the resolution)
>> we now that we need to update
>>
>
> Thank you, wiki updated.
> J.
>
___
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] Rolling out a pandoc-context publication workflow in an organization

[Jan U. Hasecke]

Dear Hans,

thanks for the hint to the repo. I remember that it was mentiooned before.

Am 02.07.21 um 10:42 schrieb Hans Hagen:

official    : https://bitbucket.org/phg/context-mirror/src/beta/


Is there a how-to-bootstrap-from-repository? How can I get a running 
context with the repo?


TIA
juh
___
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] Fwd: columnsets messed up

[Henning Hraban Ramm]

> Am 02.07.2021 um 11:03 schrieb Henning Hraban Ramm  >:
> 
>> 
>> Am 02.07.2021 um 08:51 schrieb Hans Hagen > >:
>> 
>> On 7/1/2021 8:04 PM, Henning Hraban Ramm wrote:
>>> Hi,
>>> I’m working at the current CG journal whose layout uses columnsets. They 
>>> aren’t usable any more. Same in current LMTX and MkIV.
>>> - the first line can start one or more lines lower
>>> - then the same number of lines is printed over each other at the bottom
>>> - it gets worse with footnotes (looks like their space isn’t considered at 
>>> all)
>>> - if the column set doesn’t start at the top of the page, the second column 
>>> does
>>> Hraban
>>> \definecolumnset[cgjcolset][n=2]
>>> \starttext
>>> \chapter{This is a chapter about column sets}
>>> \startcolumnset[cgjcolset]
>>> \dorecurse{20}{
>>> \samplefile{sapolsky}\par
>>> }
>>> \stopcolumnset
>>> \stoptext
>> Personally I'd never use columnsets for anything else than very controlled 
>> situations because that's what they were made for. Not to be mixed with the 
>> normal pagebuilder. So, first of all you need to operate on the grid (i can 
>> probably get rid of some side effects and maigt even force that but not 
>> now). Then, \chapter itself flushes pages so that should be disabled.
> 
> Thank you, I got it mostly working now.

In several articles I get a problem, and I can’t (yet) reproduce it in a MWE:

The text in a two-column columnset suddenly breaks at the end of a left column, 
the end is missing.

Here’s an example PDF:
https://sedna.fiee.net/f/24d54a952b0243a98775/?dl=1

What could case that?

Hraban

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

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

Re: [NTG-context] Rolling out a pandoc-context publication workflow in an organization

[Hans Hagen]

On 7/2/2021 11:56 AM, Jan U. Hasecke wrote:


Dear Hans,

thanks for the hint to the repo. I remember that it was mentiooned before.

Am 02.07.21 um 10:42 schrieb Hans Hagen:

official    : https://bitbucket.org/phg/context-mirror/src/beta/


Is there a how-to-bootstrap-from-repository? How can I get a running 
context with the repo?

no, not yet ... we want to do it 'right' from the start


-
  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] columnsets messed up

[Hans Hagen]

On 7/2/2021 11:03 AM, Henning Hraban Ramm wrote:



Am 02.07.2021 um 08:51 schrieb Hans Hagen :

On 7/1/2021 8:04 PM, Henning Hraban Ramm wrote:

Hi,
I’m working at the current CG journal whose layout uses columnsets. They aren’t 
usable any more. Same in current LMTX and MkIV.
- the first line can start one or more lines lower
- then the same number of lines is printed over each other at the bottom
- it gets worse with footnotes (looks like their space isn’t considered at all)
- if the column set doesn’t start at the top of the page, the second column does
Hraban
\definecolumnset[cgjcolset][n=2]
\starttext
\chapter{This is a chapter about column sets}
\startcolumnset[cgjcolset]
\dorecurse{20}{
\samplefile{sapolsky}\par
}
\stopcolumnset
\stoptext

Personally I'd never use columnsets for anything else than very controlled 
situations because that's what they were made for. Not to be mixed with the 
normal pagebuilder. So, first of all you need to operate on the grid (i can 
probably get rid of some side effects and maigt even force that but not now). 
Then, \chapter itself flushes pages so that should be disabled.


Thank you, I got it mostly working now.

The CGJ layout doesn’t actually use \chapter but its own convoluted 
\startArticle. Until last issue it tried to be flexible and setup three 
different column modes. Now I eliminated the last leftovers of that. I still 
struggle to understand some pecularities...

What I did wrong:
* \setuplayout[grid=yes] is important
* you can’t start a columnsetspan before the columnset
leter this year i will into the several column mechanisms (maybe also 
some mechanism to warn for mixed usage or use of features that interfere 
.. doing columns is hairy in tex)


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] Hyphens broken with lucidaot

[Hans Hagen]

On 7/1/2021 7:12 AM, Lutz Haseloff wrote:

Hi all,

the same here with
current version: 2021.06.29 23:13

Greetings Lutz

Am 1. Juli 2021 03:02:53 MESZ schrieb Otared Kavian :

Hi Hans,

I noticed that with the recent LMTX version 2021.06.27 16:59 the hyphens do 
not show up correctly with lucidaot.
Here is a minimal example and the resulting PDF

\setupbodyfont[lucidaot,10pt]
\startTEXpage
c'est-à-dire

sous-ensemble

sous-préfet
\stopTEXpage

Best regards: Otared
lucidaot has inconsistent hyphens (one can argue that it's a bug but 
changing the font is not good for stability so bugs become features in 
the end) ... i catch that in the next upload


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] columnsets messed up

[Henning Hraban Ramm]

> Am 02.07.2021 um 08:51 schrieb Hans Hagen :
> 
> On 7/1/2021 8:04 PM, Henning Hraban Ramm wrote:
>> Hi,
>> I’m working at the current CG journal whose layout uses columnsets. They 
>> aren’t usable any more. Same in current LMTX and MkIV.
>> - the first line can start one or more lines lower
>> - then the same number of lines is printed over each other at the bottom
>> - it gets worse with footnotes (looks like their space isn’t considered at 
>> all)
>> - if the column set doesn’t start at the top of the page, the second column 
>> does
>> Hraban
>> \definecolumnset[cgjcolset][n=2]
>> \starttext
>> \chapter{This is a chapter about column sets}
>> \startcolumnset[cgjcolset]
>> \dorecurse{20}{
>> \samplefile{sapolsky}\par
>> }
>> \stopcolumnset
>> \stoptext
> Personally I'd never use columnsets for anything else than very controlled 
> situations because that's what they were made for. Not to be mixed with the 
> normal pagebuilder. So, first of all you need to operate on the grid (i can 
> probably get rid of some side effects and maigt even force that but not now). 
> Then, \chapter itself flushes pages so that should be disabled.

Thank you, I got it mostly working now.

The CGJ layout doesn’t actually use \chapter but its own convoluted 
\startArticle. Until last issue it tried to be flexible and setup three 
different column modes. Now I eliminated the last leftovers of that. I still 
struggle to understand some pecularities...

What I did wrong:
* \setuplayout[grid=yes] is important
* you can’t start a columnsetspan before the columnset

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

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

Re: [NTG-context] Rolling out a pandoc-context publication workflow in an organization

[Hans Hagen]

On 7/2/2021 9:38 AM, Jan U. Hasecke wrote:


Am 02.07.21 um 01:07 schrieb Bruce Horrocks:
One option you might try, if your cooperative has a web-server 
available to editors, is to store your own ConTeXt repository. That 
way you can update the LMTX version when you are ready to.


This works because "install.sh" can have a "--server" parameter 
supplied. By default it goes to lmtx.pragma-ade.com/install-lmtx but 
if you were to copy the install-lmtx directory and host the copy on 
your own server at the same path, then you could 'freeze' your LMTX 
version until you were ready to change.



Thanks for this hint.

This might solve one more problem. We would like to pin the installation 
to a version that is known too work.


BTW: Are there plans to use a GitHub repository or an alternative to it? 
As that would ease pinning a bit.

All uploads end up here too alsk kind of an archive:

official: https://bitbucket.org/phg/context-mirror/src/beta/
experimental : https://github.com/mojca/context2

The official oen can be checked out, the experimental one is a 
playground because for quite a while Mojca and I have some ideas for a 
more extensive install on github which would then involve:


-- core context code (with luametatex in source tree too: 
tex/texmf-context in the distribution


-- the minimal set of resources: tex/texmf in the distribution

-- binaries (which is the more complex part)

-- modules: texmf/modules

So, basically several repositories alongside (totaling to the amoutn we 
now have in the zips). We then have doif-it-yourself-zips, the garden 
installer, the lmtx self updater and install-from-github as 
alternatives. I have a sort of proof of concept for it. We looked into 
the binary bit and things have changed a bit over the years so maybe 
it's more doable now.


One of the complications is always that it depends on helper programs:

- zips are easy as all systems have it (ok, some linux distributions 
don't install unzip but one can easily add it)


- the garden install needs a matching rsync (we need to ship on for 
windows and sometimes a mismatch will require an update on other 
platforms); it reminds me that we have to swap the cygwin bins by mingw 
bins; anyway. one problem is that organizations block the port


- the lmtx installer needs a (luametatex) binary which is no big deal; 
it uses http and there might be organizations that demand https and ssl 
keeps evolving so in the long run it can fail to update older 
installations (it anyway means that we need to also ship e.g. curl or 
libcurl (the later works ok for us); no big deal but more work)


- a github install demands that git is installed; that itself is a big 
piece of software (a small git binary for windows is already 200 MB due 
to all the dependencies while actually we only need a stupid fetch); the 
gh binary is still 25M but might be a solution, apart from the fact that 
we then expect users to have a recent bin ... will a 5 year old 
installation update?); of course users can also decide to completely do 
it themselves (check out etc) but for a local project-specific run one 
doesn't want all those gigs


So, each approach has pros and cons, and we need to prevent lock into 
some specific technology.


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] Different authorconversion for citation alternatives and bibliographic entries

[denis.maier]

Oh, and needless to say, I'd be happy to help with this.

> -Ursprüngliche Nachricht-
> Von: Maier, Denis Christian (UB)
> Gesendet: Freitag, 2. Juli 2021 10:01
> An: 'Alan Braslau' 
> Cc: ntg-context@ntg.nl
> Betreff: AW: [NTG-context] Different authorconversion for citation 
> alternatives
> and bibliographic entries
> 
> > -Ursprüngliche Nachricht-
> > Von: Alan Braslau 
> > Gesendet: Mittwoch, 30. Juni 2021 23:50
> > An: Maier, Denis Christian (UB) 
> > Cc: ntg-context@ntg.nl
> > Betreff: Re: [NTG-context] Different authorconversion for citation
> > alternatives and bibliographic entries
> >
> [...]
> > >
> > > So what would be needed to make add real support for it?
> >
> > First of all, come to a consensus on a clear style guide to base this
> > on, so as not to run after ambiguous and perhaps contradictory
> > specifications. This would be distinct from the APA (author-year)
> > model as well as from the minimalist APS
> > (numbered) style. Could this perhaps be the Chicago style? (does that
> > have a footnote specification?)
> 
> Chicago is certainly not a bad choice for this. It's probably one of the most
> complete footnote specifications out there. (I knows multiple variants though,
> so you need to settle for one or support both.) One thing to be aware of is 
> that
> Chicago is utterly complex. Other styles like MHRA are a bit simpler. This
> complexity might be an advantage and a disadvantage at the same time. It may
> be hard to get this completely right. The already mentioned biblatex-chicago
> package shows how much is involved. OTOH, if you get this right that should
> cover almost everything that might come up in note based styles.
> 
> Denis

___
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] Different authorconversion for citation alternatives and bibliographic entries

[denis.maier]

> -Ursprüngliche Nachricht-
> Von: Alan Braslau 
> Gesendet: Mittwoch, 30. Juni 2021 23:50
> An: Maier, Denis Christian (UB) 
> Cc: ntg-context@ntg.nl
> Betreff: Re: [NTG-context] Different authorconversion for citation 
> alternatives
> and bibliographic entries
> 
[...]
> >
> > So what would be needed to make add real support for it?
> 
> First of all, come to a consensus on a clear style guide to base this on, so 
> as not
> to run after ambiguous and perhaps contradictory specifications. This would be
> distinct from the APA (author-year) model as well as from the minimalist APS
> (numbered) style. Could this perhaps be the Chicago style? (does that have a
> footnote specification?)

Chicago is certainly not a bad choice for this. It's probably one of the most 
complete footnote specifications out there. (I knows multiple variants though, 
so you need to settle for one or support both.)
One thing to be aware of is that Chicago is utterly complex. Other styles like 
MHRA are a bit simpler. This complexity might be an advantage and a 
disadvantage at the same time. It may be hard to get this completely right. The 
already mentioned biblatex-chicago package shows how much is involved. OTOH, if 
you get this right that should cover almost everything that might come up in 
note based styles.

Denis

___
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] Heading for endnotes / grouped by chapter endnotes

[denis.maier]

Thanks for this. I'll look into it.

> -Ursprüngliche Nachricht-
> Von: ntg-context  Im Auftrag von Rik Kabel
> Gesendet: Mittwoch, 30. Juni 2021 21:40
> An: ntg-context@ntg.nl
> Betreff: Re: [NTG-context] Heading for endnotes / grouped by chapter endnotes
> 
> For what its worth, I offer my endnote apparatus with updates for parts.
> It uses the standard note/notation mechanism, not a list, for endnotes.
> Perhaps it can be further adapted to the needs of this thread.
> 
> There is at least one small issue with it: I have to use \stopendnote even 
> though
> I define \startEndnote. This causes issues with the linter (mtxrun --script 
> check
> ) but seems otherwise harmless.
> 
> I am sure that others more versed in ConTeXt can find some ways to fix this 
> and
> improve the overall approach. I welcome suggestions.
> 
> %--%
> % Endnote apparatus adapted for parts
> %
> \mainlanguage  [en]
> \language  [en]
> \setupinteraction  [state=start]
> \setuppagenumbering[alternative=doublesided]
> 
> \setupheadertexts [{\it\getmarking[part]}][{\it\getmarking[section]}]
> [{\it\getmarking[chapter]}][{\it\getmarking[part]}]
> \setupheads    [number=no]
> \setuphead [part]
>     [placehead=yes,
>      header=empty]
> 
> %- footnote setup -% % 
> footnotes uses
> asterisk, dagger, ddagger... so that endnotes %   and pagenotes have separate
> sequences. Change way= to suit %   your footnote frequency
> 
> \setupnotation [footnote]
>     [numberconversion=set 2,
>      way=chapter]
> 
> %- endnote setup --% % 
> endnotes use
> numeric indices, reset by part
> 
> \setupnote [endnote][
>      textseparator={,},
>      textstyle=\high{\small\hairspace},
>      location=none,
>      bodyfont=]
> 
> \setupnotation [endnote]
>     [headstyle=\small,
>      way=bypart,
>      numbercommand=,
>      after={\blank[halfline]}]
> 
> %- endnote pages setup %
> 
> \definemarking [notePage]
> 
> \startsetups   [noteHeadingsText]
>    {\em Notes for page
> \doifelse{\fetchmark[notePage][top]}{\fetchmark[notePage][bottom]}
>      { \getmarking[notePage][top]}
>      {s \getmarking[notePage][top]–\getmarking[notePage][bottom]}}
> \stopsetups
> 
> \starttexdefinition unexpanded startEndnote
>    \dosingleempty\doStartEndnote
> \stoptexdefinition
> 
> \starttexdefinition doStartEndnote [#1]
>    \expanded{\dodoStartEndnote[#1][{\rawcountervalue[userpage]}]}
> \stoptexdefinition
> 
> \starttexdefinition dodoStartEndnote [#1][#2]
>    \startendnote[#1]
>      \marking[notePage]{#2}\removeunwantedspaces
> \stoptexdefinition
> 
> \starttexdefinition endnoteChapter
>    \startchapter    [title=Notes]
> \setupheadertexts[{\it\getmarking[part]}][\setups{noteHeadingsText}]
> [\setups{noteHeadingsText}][{\it\getmarking[part]}]
>    \placenotes  [endnote]
>    \page
> \setupheadertexts[{\it\getmarking[part]}][{\it\getmarking[section]}]
>     [{\it\getmarking[chapter]}][part]
>    \stopchapter
> \stoptexdefinition
> 
> %--%
> 
> \starttext
> 
> \completecontent
> 
> \startpart[title=Part 1]
> \dorecurse{3}{
>    \startchapter[title=Chapter #1]
>      If a man wants to read good books, he must make a point of
>      avoiding bad ones; for life is short, and time and energy
>      limited.
>      \startfootnote
>    T.\,Baily Saunders’ translation, in his 1891 {\em
>    The Art of Literature}, of part of one of Arthur
>    Schopenhauer’s essays.
>      \stopfootnote
>      \startEndnote
>    {\language[deo]%
>    Um das Gute zu lesen, ist eine Bedingung, dass man das
>    Schlechte nicht lese: denn das Leben ist kurz, Zeit und
>    Kräfte beschränkt.}
>      \stopendnote
> 
>      \dorecurse{6}{
>    \startsection[title=Section ##1]
>      This followed by:
> 
>      {\it Repetitio est mater studiorum}. Any book that is at
>      all important ought to be at once read through twice;
>      partly because, on a second reading, the connection of the
>      different portions of the book will be better understood,
>      and the beginning comprehended only when the end is known;
>      and partly because we are not in the same temper and
>      disposition on both readings. On the second perusal we get a
>      new view of every passage and a different impression of the
>      whole book, which then appears in another light.
>    \startEndnote
>      {\language[deo]%
>      Repetitio est mater studiorum. Jedes irgend wichtige

Re: [NTG-context] Rolling out a pandoc-context publication workflow in an organization

[denis.maier]

Hi,
in case you don't know it already, for your use-case you might also be 
interested in this workflow:
https://oa-pub.hos.tuhh.de/de/

It's a publishing workflow for OA-Journals. IIUC, the interesting part (in this 
context here) is that they use Gitlab, author in markdown, and whenever you 
push a commit, Gitlab actions are used to produce the final output. I think 
they use Pandoc and LaTeX with Docker Images, but maybe it could be possible to 
set something similar up with ConTeXt... 

Denis


> -Ursprüngliche Nachricht-
> Von: ntg-context  Im Auftrag von Jan U. Hasecke
> Gesendet: Donnerstag, 1. Juli 2021 08:03
> An: mailing list for ConTeXt users 
> Betreff: [NTG-context] Rolling out a pandoc-context publication workflow in an
> organization
> 
> 
> Dear all,
> 
> in the last weeks I asked more questions than I normally do. The reason is 
> that
> my organization is discussing to roll out a markdown-pandoc-context
> publication workflow.
> 
> Some time ago we started to use context to produce flyers and some other
> documents. In fact I was the only one to use it. The results are so good that 
> we
> discussed how to use it more often.
> 
> Currently we use LaTeX to produce our legal documents, terms of services etc.
> With ConTeXt we are able to meet our corporate design guidelines and to
> produce good looking and individually designed documents.
> 
> But our authors and editors were not willing to use ConTeXt directly so that 
> we
> decided to look into Pandoc and use Markdown as authors input markup.
> Markdown is much better supported by text editors than ConTeXt.
> 
> The main problem for me is to come up with a good organization of the
> ConTeXt workflow so that it is easy usable and meets our requirements for
> quality management.
> 
> These are quite strict. We are a Debian based cooperative and the majority of
> our editors also use this distribution on their private computers. Some use a
> MacBook, only one uses of Windows.
> 
> For this reason we would like to stay with the Debian ConTeXt, which I never
> used as it is quite old. The same is true for Pandoc which made some
> improvements in the last years and also is very old in the current Debian
> distribution. As we did not decide this issue I can't say how much I have to
> refactor our styles to meet the older versions of ConTeXt.
> 
> Apart from this I have to organize our style files and ressources, anyway.
> 
> In another thread Hans said how to use these folders. Thanks a lot.
> 
> texmf-local   : maybe configurations
> texmf-project : stuff you're working on (styles)
> texmf-fonts   : fonts you downloaded or bought
> 
> All our styles and our shared image folder are versioned by git so I think 
> that I
> either put links into texmf-project pointing to our style repository and to 
> our
> image repository to have easy access to these ressources no matter how we
> call context or to put them into texmf-project directly. (We did not decide 
> yet
> whether we call context from pandoc using a tmp directory for building or
> directly from our build script.
> 
> If we use the current lmtx distribution, all editors would have to install 
> ConTeXt
> with the install.sh script on their private computers, then we would either 
> call a
> post installation script to clone the repositories in texmf-project or to 
> clone
> them in another folder and set links to texmf-project. Linking seems better 
> as I
> am not sure what "context generate" would do with the .git folder inside the
> repositories.
> 
> All document projects are in their own repository. Currently we use a build
> script to call pandoc with an individual set of arguments including a custom
> context template which is stored in the document repository, also. Inside of 
> this
> template we include all the environments we need for this particular
> document. We have a lot of small environments to reuse them in different
> document types.
> 
> This is our plan so far.
> 
> But to role out this successfully I would like to ease the way to a working
> pandoc-context installation for our editors. Do you have an idea how to do 
> this?
> 
> I come up with the idea of an "organizational context distribution" that has 
> all
> requirements preinstalled. That could look like this:
> 
> We have a repository:
> 
> hs.lmtx
> 
> which contains the install script and all our ressources (images and styles).
> 
> Our editors would clone the repository and just call the installation script 
> to
> download the lmtx distribution. Afterwards they are ready to start as we would
> point to the right context executable in our build scripts.
> 
> Problem: What will happen if our editors do a git pull in hs.lmtx and a 
> "context
> generate"? There are also concerns if something breaks after updating context
> with the install.sh. Is there a way to reset the installation to a given point
> release? How do you solve this in a production environment? On my private
> computer I sometimes ins

Re: [NTG-context] Rolling out a pandoc-context publication workflow in an organization

[Jan U. Hasecke]

Am 02.07.21 um 01:07 schrieb Bruce Horrocks:

One option you might try, if your cooperative has a web-server available to 
editors, is to store your own ConTeXt repository. That way you can update the 
LMTX version when you are ready to.

This works because "install.sh" can have a "--server" parameter supplied. By 
default it goes to lmtx.pragma-ade.com/install-lmtx but if you were to copy the install-lmtx 
directory and host the copy on your own server at the same path, then you could 'freeze' your LMTX 
version until you were ready to change.



Thanks for this hint.

This might solve one more problem. We would like to pin the installation 
to a version that is known too work.


BTW: Are there plans to use a GitHub repository or an alternative to it? 
As that would ease pinning a bit.


juh
___
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
___