Re: [NTG-context] new upload/issue with t-vim?

[Aditya Mahajan via ntg-context]

On Mon, 9 Aug 2021, Hans Hagen wrote:

> On 8/8/2021 11:53 PM, Aditya Mahajan via ntg-context wrote:
> > On Sun, 8 Aug 2021, Hans Hagen via ntg-context wrote:
> > 
> > > On 8/8/2021 1:13 PM, Benjamin Buchmuller via ntg-context wrote:
> > > > I'm not sure if it's related to this latest:
> > > > 
> > > > ConTeXt  ver: 2021.08.07 22:53 LMTX  fmt: 2021.8.8  int: english/english
> > > > 
> > > > or a previous one, but with this one:
> > > > 
> > > > ConTeXt  ver: 2021.07.30 00:57 LMTX  fmt: 2021.8.8  int: english/english
> > > > 
> > > > My document compiled fine.
> > > > 
> > > > When I use the t-vim module (freshly installed again from the garden;
> > > > but I
> > > also tried to replace some files from the GitHub, but not sure if I did it
> > > right …), I now get an error when I do something like
> > > > 
> > > > \usemodule[vim]
> > > > 
> > > > \definevimtyping[vimR]
> > > > 
> > > > \typevimRfile{path_to_file.R} % specifically: {../sourcecodes/myfile.R}
> > > > 
> > > > --
> > > > 
> > > > lua error > lua error on line 2 in file virtual://block.sourcecode.7:
> > > > 
> > > > token call, execute:
> > > ...ConTeXt/tex/texmf-context/tex/context/base/mkiv/l-io.lua:70: bad
> > > argument
> > > #1 to '?' (string expected, got nil)
> > > i'll check it, i cleaned up some code but didn't realize that it was
> > > used in a module
> > 
> > This was also reported on t-vim's github page:
> > https://github.com/adityam/filter/pull/48.
> > 
> > I basically use jobs.file.run to cache the results and I can easily write a
> > module specific version of that, if needed. I'll look at it in a day or two
> > (away from a stable internet connection until then).
> blame me for this one
> 
> just wait for the update (i added the name,action interface again as i assumes
> the { filename =, action= } usage)

For the record, the vim module is working again with version 2021.08.10. Thanks 
Hans!

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] Both pdfinfo & exiftool have trouble with 1.0.4 but works with 1.0.3

[Ramkumar KB via ntg-context]

Hans,

To close this thread, both poppler and exiftool worked properly after I
upgraded to the latest version (details below). I will add a section in the
wiki about these tools, as they are mighty useful when working with PDFs.

mtx-context | ConTeXt Process Management 1.04 mtx-context |
mtx-context | main context file:
/home/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context
 | current version: 2021.08.10 12:42 mtx-context | main context file:
/home/tex/texmf-context/tex/context/base/mkxl/context.mkxl mtx-context
 | current version: 2021.08.10 12:42

Thanks again!

best regards,
Ramkumar

On Tue, Aug 10, 2021 at 7:01 PM Ramkumar KB  wrote:

> Hans,
>
> Thanks for the feedback. I will update to the latest version and run some
> tests again.
>
> mtxrun does not list the custom attributes unlike the others. From our
> (limited) experience, mutool / poppler / exiftool all excel in different
> areas. Dealing with different tools and keeping them upto date is
> something we have internalized.
>
> We did observe that mutool did not give errors with version 1.0.4 but
> others did. In the ConTeXt development workflow, are there any tests with
> such external tools (to possibly catch regression issues)?
>
> We have experienced (reasonable) success with tools like diff-pdf
>  to catch regression in our workflow.
>
> Thank you as always!
>
> best regards,
> Ramkumar
>
>
> On Tue, Aug 10, 2021 at 3:19 PM Hans Hagen  wrote:
>
>> On 8/10/2021 6:33 AM, Ramkumar KB via ntg-context wrote:
>> > Hi,
>> >
>> > We use PDF tools like mutool, pdfinfo (from poppler) and exiftool in
>> our
>> > workflow (once the PDFs are created by ConTeXt).
>> >
>> > But looks like we have hit upon some regression issue between 1.0.3 and
>> > 1.0.4 versions. Both pdfinfo (from poppler) and exiftool are able to
>> > read PDFs created from 1.0.3 but have trouble reading PDFs created with
>> > 1.0.4. Please see below logs for details.
>> hard to say without files but indeed updating might help
>>
>> btw, there is (kind of old but still ok):
>>
>> mtxrun --script pdf --info filename.pdf
>>
>> 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] 15th International ConTeXt Meeting (registration closes Aug 22)

[Taco Hoekwater via ntg-context]

Hi all,

There is still room for some extra participants for the ConTeXt meeting in 
Bassenge, 
Belgium from Sept 20 to Sept 25. Despite the still somewhat lingering situation 
wrt
COVID-19, we are now certain that the meeting can and will in fact take place in
person. Hurrah!

Even if we still have room by then, registration will close on Aug 22, because 
by 
that time we need to make final arrangements for T-shirt printing and catering. 
So if you are still on the fence about attending, do not wait too long!


Also remember that it is possible for ConTeXt Group members to attend 
online-only
for free. That is less than ideal because you cannot join us for a drink and a 
chat,
but it gives you bragging rights for attending, and you will get a T-shirt as 
well !
(if you register before Aug 22)

You can easily become a member of CG by filling in the form at

  https://group.contextgarden.net/register.shtml

Besides being able to register for the online portion of the upcoming meeting,
you will also receive the nicely printed ConTeXt journal, and additionally you
will help the ConTeXt Group to do more for the community in the future. 

Even if you are not going to attend the online meeting, we think becoming a 
CG member is a great idea! More that fifty people have joined already!

To see more details about the upcoming meeting, see the website at

  https://meeting.contextgarden.net/


In other news, there is now a provisional programme page:

  https://meeting.contextgarden.net/2021/programme.shtml


I can't wait to see (some of) you in person in Bassenge!

Best wishes,
Taco

— 
Taco Hoekwater  E: t...@bittext.nl
genderfluid (all pronouns)



___
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] Create an enumeration style

[Wolfgang Schuster via ntg-context]

Fabrice Couvreur via ntg-context schrieb am 11.08.2021 um 12:57:

I forgot this : how to reduce the font size for the exponents "er", "e" ?


The exponents are placed with \high and you can change the style with

    \setuphigh[style=...]

but this affects all texts which use \high.

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] Footnotes in columns

[Hans Hagen via ntg-context]

On 8/13/2021 8:54 AM, Henning Hraban Ramm via ntg-context wrote:




Am 13.08.2021 um 08:43 schrieb Hans Hagen :

On 8/13/2021 12:32 AM, Henning Hraban Ramm via ntg-context wrote:

Am 13.08.2021 um 00:03 schrieb Hans Hagen via ntg-context :

On 8/12/2021 10:01 PM, Jano Kula via ntg-context wrote:

Hello Hraban!
On Thu, Aug 12, 2021, 15:24 Henning Hraban Ramm via ntg-context mailto:ntg-context@ntg.nl>> wrote:
Footnotes still don’t work in columnsets (latest LMTX):
- they stay in one column (I’d prefer them over the whole width of
the text area)
- they often get overwritten by main text
Is there a workaround?
I had to switch back to mkiv. It's on Hans' agenda, but with lots of 
interferencies there will be no quick fix.



good old mkiv ... so it serves a purpose! i would be more worried when you went 
back to mkii

;D
Unfortunately I can’t go back to MkIV with the CG journal since some articles 
use LMTX features.
I’ll probably find some ugly hack to work around the issues...

A lot has to do with defaults. We have several multicolumn mechanisms an cnotes 
themselves can also come in columns and it's nto easy to have a setup that 
suits them all, so each mechanism has additional settings. I'm still not sure 
how to deal with this because there are conflicting demands. So, one ends up in 
'fix this setup' 'break that setup' situations (basically it means that we need 
to setup things on an extra axis: the kind of otr used). It's a bit the price 
we pay for configurability.


Would it be viable to use columnset areas for footnotes? Then the user could 
configure themselves where they should go, how many columns they should span 
etc.
the problem with notes is that the pagebreak depends on them so it is 
impossible to predict sizes .. it works with ratios and such in 
basically a one column operation mode (because that is what tex has)


text text text
text text text
text text text
text text text

note
note
note

tex has to split page and notes if needed and take optional distance 
into account


the lua(meta)tex engine already privides a bit more control but 
solutions always have to operate with margins


now, if users would accept limitations much is possible but in the end 
there always a 'i want this note to end up here' demand


the same with figures: if they may float we can do a good job, but 
designers / publishers (unaware of reliable floating) nearly always 
demand 'it should end up here' which then conflicts with automated 
typesetting because 'here' means that one also manually messes with the 
rest


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] Footnotes in columns

[Henning Hraban Ramm via ntg-context]

> Am 13.08.2021 um 08:43 schrieb Hans Hagen :
> 
> On 8/13/2021 12:32 AM, Henning Hraban Ramm via ntg-context wrote:
>>> Am 13.08.2021 um 00:03 schrieb Hans Hagen via ntg-context 
>>> :
>>> 
>>> On 8/12/2021 10:01 PM, Jano Kula via ntg-context wrote:
 Hello Hraban!
 On Thu, Aug 12, 2021, 15:24 Henning Hraban Ramm via ntg-context 
 mailto:ntg-context@ntg.nl>> wrote:
Footnotes still don’t work in columnsets (latest LMTX):
- they stay in one column (I’d prefer them over the whole width of
the text area)
- they often get overwritten by main text
Is there a workaround?
 I had to switch back to mkiv. It's on Hans' agenda, but with lots of 
 interferencies there will be no quick fix.
 
>>> 
>>> good old mkiv ... so it serves a purpose! i would be more worried when you 
>>> went back to mkii
>> ;D
>> Unfortunately I can’t go back to MkIV with the CG journal since some 
>> articles use LMTX features.
>> I’ll probably find some ugly hack to work around the issues...
> A lot has to do with defaults. We have several multicolumn mechanisms an 
> cnotes themselves can also come in columns and it's nto easy to have a setup 
> that suits them all, so each mechanism has additional settings. I'm still not 
> sure how to deal with this because there are conflicting demands. So, one 
> ends up in 'fix this setup' 'break that setup' situations (basically it means 
> that we need to setup things on an extra axis: the kind of otr used). It's a 
> bit the price we pay for configurability.

Would it be viable to use columnset areas for footnotes? Then the user could 
configure themselves where they should go, how many columns they should span 
etc.

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] Footnotes in columns

[Hans Hagen via ntg-context]

On 8/13/2021 12:32 AM, Henning Hraban Ramm via ntg-context wrote:



Am 13.08.2021 um 00:03 schrieb Hans Hagen via ntg-context :

On 8/12/2021 10:01 PM, Jano Kula via ntg-context wrote:

Hello Hraban!
On Thu, Aug 12, 2021, 15:24 Henning Hraban Ramm via ntg-context mailto:ntg-context@ntg.nl>> wrote:
Footnotes still don’t work in columnsets (latest LMTX):
- they stay in one column (I’d prefer them over the whole width of
the text area)
- they often get overwritten by main text
Is there a workaround?
I had to switch back to mkiv. It's on Hans' agenda, but with lots of 
interferencies there will be no quick fix.



good old mkiv ... so it serves a purpose! i would be more worried when you went 
back to mkii


;D
Unfortunately I can’t go back to MkIV with the CG journal since some articles 
use LMTX features.

I’ll probably find some ugly hack to work around the issues...
A lot has to do with defaults. We have several multicolumn mechanisms an 
cnotes themselves can also come in columns and it's nto easy to have a 
setup that suits them all, so each mechanism has additional settings. 
I'm still not sure how to deal with this because there are conflicting 
demands. So, one ends up in 'fix this setup' 'break that setup' 
situations (basically it means that we need to setup things on an extra 
axis: the kind of otr used). It's a bit the price we pay for 
configurability.


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
___