Re: [NTG-context] Size of fences, factor key

On Sat, Apr 21, 2018 at 7:30 PM, Mikael P. Sundqvist wrote: > Dear Hans and others, > > I'm usually use the \big, \Big, \bigg etc to get the size of parentheses, > brackets and braces to be the size I want. I realize that the fences > machinery is probably a cleaner way of

Re: [NTG-context] Loading units fails

On 4/24/2018 7:58 PM, Michael Guravage wrote: Dear list members, I do not know when this problem first appeared, I have not used the units package for a while, but merely invoking the package with the latest beta provokes an error. MWE: \usemodule[units]   \starttext     help  

[NTG-context] Loading units fails

Dear list members, I do not know when this problem first appeared, I have not used the units package for a while, but merely invoking the package with the latest beta provokes an error. MWE: \usemodule[units] \starttext help \stoptext The attached log says there is a problem on line 42

Re: [NTG-context] Installing a specific version of context

At 2018-04-24T08:44:24-04:00, Mohammad Hossein Bateni wrote: > I don't think it's possible to do off-the-shelf. The Wiki http://wiki.contextgarden.net/ConTeXt_Standalone#Reverting_to_an_older_installation says that it is possible with sh ./first-setup.sh --context=date Also, mtx-update.lua,

Re: [NTG-context] Installing a specific version of context

I don't think it's possible to do off-the-shelf. The following is what I used to do to run some tests: 1) Install the latest beta. 2) Clone to the mirror on Github [ https://github.com/contextgarden/context-mirror] 3) Sync the cloned repository to an older date 4) Replace the tex folder in

Re: [NTG-context] xmlpos not enough for me

On 4/24/2018 11:00 AM, Hans van der Meer wrote: The macro \xmlpos{#1} returns the position number of the current node in its parent. However, I would like to know the position number in its parent for the node with the same tag. An example of what I mean: inside it \xmlpos{#1} will return 2

Re: [NTG-context] luatex hangs with \placebookmarks

Just in case it helps if , openaction=FitWidth, focus=width] is commented out in first line, the hanging problem disappears. De : Joseph Canedo Envoyé le :lundi 23 avril 2018 18:56 À : mailing list for ConTeXt users Objet :luatex hangs with \placebookmarks Dear list, I use $ context

[NTG-context] Installing a specific version of context

I would like to install the version of context dated 2017.11.14. How can one do this? I tried sh first-setup.sh --context=2017.11.14 but it produces errors like rsync: change_dir "/current/context/2017.11.14" (in minimals) failed: No such file or directory (2) I'd appreciate suggestions

[NTG-context] xmlpos not enough for me

The macro \xmlpos{#1} returns the position number of the current node in its parent. However, I would like to know the position number in its parent for the node with the same tag. An example of what I mean: inside it \xmlpos{#1} will return 2 but I would like 1>

Re: [NTG-context] Reproducible PDF output not working

At 2018-04-24T10:03:16+02:00, Arthur Reutenauer wrote: >> PS: Incidentally, what is the "-19:00" in date in the first identifier? >> In my time zone, IST, I would have expected 2018-04-24T01:49:47+05:30. > > I remember noticing something strange in the date format when files > were compiled after

Re: [NTG-context] Reproducible PDF output not working

At 2018-04-24T09:44:09+02:00, Hans Hagen wrote: > fixed in beta but no beta soon ... in lpdf-ini.lua you can try to fix > this Thank you for the solution. Raghu. -- N. Raghavendra , http://www.retrotexts.net/ Harish-Chandra Research Institute, http://www.hri.res.in/

Re: [NTG-context] Reproducible PDF output not working

> On the other hand, with the 2017.11.14 version, the identifier in the > output of `context --nodates' is just > > foo The longer identifier is definitely better, but it should be possible to make it predictable over successive runs. > PS: Incidentally, what is the "-19:00" in date in the

Re: [NTG-context] Reproducible PDF output not working

On 4/24/2018 6:28 AM, N. Raghavendra wrote: At 2018-04-23T23:49:19+02:00, Arthur Reutenauer wrote: it seems the identifier uses the time of compilation, when it should probably use the time of last modification of the source file. Yes, with the 2018.04.19 version, the identifier in the