Re: [NTG-context] new lua/stack error

In my larger document (approx 600 pages, over 1000 references) problematic entries like \cite[{{A, B, and C}}] did not display at all, though the document did process without claims of stack errors etc. Curiously, \goto{A, B, and C}[{{A, B, and C}}] does work as expected. Alan On Thu, Feb 23,

Re: [NTG-context] new lua/stack error

Thanks, Hans! That does work nicely. On Thu, Feb 23, 2017 at 3:42 PM, Hans Hagen wrote: > On 2/22/2017 6:21 PM, Alan Bowen wrote: > >> Here is the file that I have been working with: >> >> \installlanguage[packed][en] >> \setuplanguage[packed][spacing=packed] >>

[NTG-context] floats on pages without headers

I have some large floats that look best on empty pages, i.e., pages that do not have headers? The wiki suggests that location=page will put the float on an empty page but this does not seem to be the case: \starttext \dorecurse{3}{\input knuth} \startplacefigure[title=Cow, location={page}]

Re: [NTG-context] new lua/stack error

On 2/22/2017 6:21 PM, Alan Bowen wrote: Here is the file that I have been working with: \installlanguage[packed][en] \setuplanguage[packed][spacing=packed] \startsetups[tightspace] \spaceskip 0.5\interwordspace plus .5\interwordstretch minus \interwordshrink \stopsetups

Re: [NTG-context] decomposed and precomposde glyphs

On Thu, Feb 23, 2017 at 6:50 PM, Ulrike Fischer wrote: > Am Thu, 23 Feb 2017 18:45:04 +0100 schrieb luigi scarso: > >> no crash here with luatex 1.0.4 on my local box > > I just tried the lualatex examples with my luatex 1.0.4 too (I got > it from w32tex.org) and the error

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 6:26 PM, Ulrike Fischer wrote: Am Thu, 23 Feb 2017 16:55:08 +0100 schrieb Hans Hagen: it's not a ligature but a multiple fonts.handlers.otf.addfeature { name= "decompose", type= "multiple", nocheck = true, -- new trick I updated my context version and

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 18:45:04 +0100 schrieb luigi scarso: > no crash here with luatex 1.0.4 on my local box I just tried the lualatex examples with my luatex 1.0.4 too (I got it from w32tex.org) and the error seems to be gone. -- Ulrike Fischer http://www.troubleshooting-tex.de/

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 6:26 PM, Ulrike Fischer wrote: With the standard fontloader of luaotfload there is no error but the output is not correct. btw, plain tests can be done with mtxrun --script plain --make mtxrun --script plain yourfile (at least that is how Luigi and I test generic when plain

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 18:41:28 +0100 schrieb Hans Hagen: > I think that you cannot drop the new context code in an old otfload, > because (1) afaik otfload patches code, Well not every fontloader version works, and it is always possible that a too new (or too old) context fontloader breaks, but

Re: [NTG-context] decomposed and precomposde glyphs

On Thu, Feb 23, 2017 at 6:26 PM, Ulrike Fischer wrote: > Am Thu, 23 Feb 2017 16:55:08 +0100 schrieb Hans Hagen: > >> it's not a ligature but a multiple >> >> fonts.handlers.otf.addfeature >>{ >> name= "decompose", >> type= "multiple", >> nocheck =

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 16:55:08 +0100 schrieb Hans Hagen: > it's not a ligature but a multiple > > fonts.handlers.otf.addfeature >{ > name= "decompose", > type= "multiple", > nocheck = true, -- new trick I updated my context version and changed my luaotfload.conf so

Re: [NTG-context] decomposed and precomposde glyphs

> I looked at the code and it actually uses an idea that I had already > tried. The problem I couldn't solve was do decompose a glyph. > Looking at an context example it seems that context can do it. The B > with dot below (U+1E04) ends as BU+0323 in the pdf. But how does > context does it? It

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 4:12 PM, Ulrike Fischer wrote: Am Thu, 23 Feb 2017 14:08:54 +0100 schrieb Hans Hagen: Did you sent the second mail only for me for a reason or did you only forget to add the list? Imho this is interesting for others too. well, it had an attachment that you can test which is not

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 14:08:54 +0100 schrieb Hans Hagen: >> Did you sent the second mail only for me for a reason or did you >> only forget to add the list? Imho this is interesting for others >> too. > > well, it had an attachment that you can test which is not meant for > context (to which i'll

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 3:05 PM, Ulrike Fischer wrote: Am Thu, 23 Feb 2017 14:08:54 +0100 schrieb Hans Hagen: btw, i suppose most context enter composed glyphs anyway instead of separate thingies But as my example (for the B with dot below) shows that this fails if the font hasn't the precomposed

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 14:08:54 +0100 schrieb Hans Hagen: > btw, i suppose most context enter composed glyphs anyway instead of > separate thingies But as my example (for the B with dot below) shows that this fails if the font hasn't the precomposed glyph. Also the problem is not so much to

[NTG-context] controlling title head distances when grid is enabled

Dear context users: I would like to typeset my documents to gridlines. If grid is enabled, the distances between titles (section, subsection,subsubsection heads) and text are too big. Here's an example: \setuplayout[grid=yes] \showgrid \starttext \section{Section One} \input tufte

Re: [NTG-context] XML export of a lua table

Am 23.02.2017 um 14:10 schrieb Hans Hagen: > On 2/23/2017 1:50 PM, Peter Rolf wrote: >> Hi, >> >> what is the easiest way to export a lua table (mostly key-value pairs) >> into a XML file? I found 'lxml.save', but no luck with a converter >> function. Any help welcome. > > kind of obvious: > >

Re: [NTG-context] XML export of a lua table

On 2/23/2017 1:50 PM, Peter Rolf wrote: Hi, what is the easiest way to export a lua table (mostly key-value pairs) into a XML file? I found 'lxml.save', but no luck with a converter function. Any help welcome. kind of obvious: local t = { a = { b = 1 } } inspect(table.toxml(t))

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 1:35 PM, Ulrike Fischer wrote: Did you sent the second mail only for me for a reason or did you only forget to add the list? Imho this is interesting for others too. well, it had an attachment that you can test which is not meant for context (to which i'll add a similar collapse

[NTG-context] XML export of a lua table

Hi, what is the easiest way to export a lua table (mostly key-value pairs) into a XML file? I found 'lxml.save', but no luck with a converter function. Any help welcome. Peter ___ If your question is of interest to

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 13:19:12 +0100 schrieb Hans Hagen: > On 2/23/2017 11:58 AM, Ulrike Fischer wrote: >> When using input like the following with xetex then harfbuzz kicks >> in and one would always get the good looking precomposed U+1EA0 for >> the A and the decomposed B+U+0323 for the B. >> >>

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 11:58 AM, Ulrike Fischer wrote: When using input like the following with xetex then harfbuzz kicks in and one would always get the good looking precomposed U+1EA0 for the A and the decomposed B+U+0323 for the B. With context (and lualatex) one get a rather bad looking -- as the dot

[NTG-context] decomposed and precomposde glyphs

When using input like the following with xetex then harfbuzz kicks in and one would always get the good looking precomposed U+1EA0 for the A and the decomposed B+U+0323 for the B. With context (and lualatex) one get a rather bad looking -- as the dot is misplaced -- output for the A0323 input

[NTG-context] Purpose/use of loadsetup interface *.xml files

Hello, Problem: I am having trouble getting a simple module's documentation to load setup information. Question: - Where can I find up-to-date documentation on the load setup interface file use and required format? Background: -- I have a current standalone ConTeXt