[NTG-context] LMTX: Command handling, Interface between TeX and Lua

[Gerion Entrup]

Hi,

I'd like to understand more of the inner workings of LMTX.
When I understand it right, most of the code is now processed in Lua but
I was not able to find it.

For example, I tried to find out how setupitemgroup is handled (just as
an example of a more complex command). The wiki has a (kind of)
autogenerated description:
https://wiki.contextgarden.net/Command/setupitemgroup
I found the data for this (at least this is my guess) here:
tex/texmf-context/tex/context/interface/mkiv/i-itemgroup.xml

Are these xml files created by hand or somehow generated? Now, when I
use `\setupitemgroup[itemize:1][symbol=3,itemalign=middle]`: How are the
arguments handled and is this a generic process or specific to each
command?

Is there a simple way to define a new command/environment and handle
the keyword arguments in Lua? For example defining a frontend command
like this:

\startsomething[firstword={Some},secondword={Text}]
Body
\stopsomething


which I can handle in some lua code like this:

function something(firstword, secondword, body)
tex.print(firstword)
tex.print(secondword)
tex.print(body)
end

Are there any resources beside the context code itself where I can learn
that?

Gerion


signature.asc
Description: This is a digitally signed message part.
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] lmtx update

[Hans Hagen via ntg-context]

Hi,

We were considering to drop the virtual math fonts mechanism (which has 
served its purpose in the transition in the very early days of luatex 
but became obsolete as math fonts evolved) but in the end we were forced 
keep this feature and even upgrade it because we liked iwona, kurier and 
anwykwa math too much. A typical case where one needs a week for 
reviewing, supporting, discussing, testing a few fonts, so let's hope it 
wi;l be used. Iwona and Kurier are nice sansish fonts and antykwa has a 
rather distinctive look and feel.


The current variant works okay for most of math (in most weights of the 
fonts)  but then, these fonts are not used for complex math or math 
using obscure symbols anyway.


It can also serve as a test case for somewhat ancient fonts but it is 
configured in the modern way we like more (as we might completely drop 
old code paths some day anyway).


And so, this update is dedicated to Janusz Nowacki, a Polish font 
friend, who passed away some time ago.


% \setupbodyfont[iwona]
% \setupbodyfont[kurier]
% \setupbodyfont[antykwa]

Hans & Mikael


-
  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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] lmtx upload

[Hans Hagen via ntg-context]

Hi,

I uploaded the first 2023 lmtx. There are not that many changes, most 
relate to updating manuals. Currently we're looking at the metafun / 
luametafun and lowlevel manuals - adding some accumulated todo's.


Keep in mind that when we update manuals that is is not automatically 
reflected in new pdf's (processing happens outside the tree on temporary 
paths) and only occasionally I push back a pdf (when it looks ok). So, 
manual sources can be more up to date than manual pdfs. If you feel 
something (fundamental and stable) is missing you can let us know here.


We gained some performance over the last month, mostly due to using 
different low level mechanisms (there are some more not yet widely used 
ones). The gain depends on (extreme) usage so quite likely most goes 
unnoticed unless one has many runs. After all, there are no fundamental 
changes in context, which is already reasonable optimized for ages (it's 
kind of a game to make it faster without obscuring the code, which is a 
criterium for rejection).


As usual, (new and old) bugs will be fixed,

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX: request for \tracinglostchars=3

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

>> LMTX only seems to support =0 (ignore) and =1 (report).  Making these
>> a fatal error (with exit status != 0) would be useful for automated
>> typesetting, as missing characters easily can get lost in the logs,
>> and then symbols are missing unnoticed in the output.
>
> Will never be default, you can play with:
>
> % \checkmissingcharacters
> % \removemissingcharacters
> % \replacemissingcharacters
> % \handlemissingcharacters
>
>> (However, \tracinglostchars=3 also doesn't seem to work with
>> LuaTeX+MKIV, probably because there is code to fallback to other fonts?)
> and if you want to quit:
>
> \enabledirectives[logs.errors=missing characters]

Ok, this is useful.

I looked around, but I couldn't find a similar feature for when a font
is not found?

cu,
-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX: request for \tracinglostchars=3

[Hans Hagen via ntg-context]

On 12/22/2022 4:23 PM, Leah Neukirchen via ntg-context wrote:

Hi,

since TeX Live 2021 (TeX 3.141592653), there is


- if \tracinglostchars >= 3, make missing characters an error (not just
   a log message), and always report the character code in hex.


LaTeX also enables this by default these days.


Not really our reference -)


LMTX only seems to support =0 (ignore) and =1 (report).  Making these
a fatal error (with exit status != 0) would be useful for automated
typesetting, as missing characters easily can get lost in the logs,
and then symbols are missing unnoticed in the output.


Will never be default, you can play with:

% \checkmissingcharacters
% \removemissingcharacters
% \replacemissingcharacters
% \handlemissingcharacters


(However, \tracinglostchars=3 also doesn't seem to work with
LuaTeX+MKIV, probably because there is code to fallback to other fonts?)

and if you want to quit:

\enabledirectives[logs.errors=missing characters]

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] LMTX: request for \tracinglostchars=3

[Leah Neukirchen via ntg-context]

Hi,

since TeX Live 2021 (TeX 3.141592653), there is

> - if \tracinglostchars >= 3, make missing characters an error (not just
>   a log message), and always report the character code in hex.

LaTeX also enables this by default these days.

LMTX only seems to support =0 (ignore) and =1 (report).  Making these
a fatal error (with exit status != 0) would be useful for automated
typesetting, as missing characters easily can get lost in the logs,
and then symbols are missing unnoticed in the output.

(However, \tracinglostchars=3 also doesn't seem to work with
LuaTeX+MKIV, probably because there is code to fallback to other fonts?)

cu,
-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

[NTG-context] lmtx upload

[Hans Hagen via ntg-context]

Hi,

I uploaded lmtx. Most significate:

- A slightly different implementaqtion of font modes 'base' and 'none' 
(hopefully no side effects).


- A few math updates (like primes done a bit differently, we made some 
choices here).


- Limited support for colr format 1 as needed for the rather nice:

https://gitlab.com/smc/fonts/Nupuram/-/blob/master/docs/README.md

which is used like:

\startTEXpage[offset=1dk,align={normal,tolerant,stretch}]
\definefontfeature[colored][default][colr=9]
\definefontfeature[slanted][default][slant=.2]
\definedfont[name:nupuramregular*default]  \input tufte 
\par \blank
\definedfont[name:nupuramregular*slanted]  \input tufte 
\par \blank
  % \definedfont[Nupuram-Color.colrv0.otf*colored] \input tufte 
\par \blank
\definedfont[Nupuram-Color.colrv1.otf*colored] \input tufte 
\par \blank
\definedfont[Nupuram-Dots.otf*default] \input tufte 
\par \blank

\definedfont[Nupuram-Arrows-Color.colrv0*,colored] \input tufte \par
\stopTEXpage

(don't install variable fonts and instances alongside)

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX: reimplementing texquotes as OTF feature

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> can you show what is wrong and what it should be with
>
> fonts.handlers.otf.addfeature {
> name = "germantexlig",
> type = "ligature",
> data = {
> ['“'] = { "`", "`" },
> ['”'] = { "'", "'" },
> ['„'] = { '"', "`" },
> ['“'] = { '"', "'" },
> ['‘'] = { "`" },
> ['’'] = { "'" }
> }
> }

Since `` and "' map to the same character, only "' works.
The table has only 5 entries, not 6!  (This took me a while to realize. ;))

> best not use an existign feature because we accumulate ... features
> come in order (you can force order if needed as you probably saw in
> one of the test files)
>
> \definefontfeature[ltest][germantexlig=yes,trep=no] \addff{ltest}

I think "texlig" and "texsub" aren't existing features.  But even
renaming doesn't help.

I've attached the working Schola screenshot and the broken LModern
behavior.


-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX: reimplementing texquotes as OTF feature

[Hans Hagen via ntg-context]

On 11/11/2022 10:19 PM, Leah Neukirchen via ntg-context wrote:

Hi,

as Hans recommended in the last video meeting, I tried to implement
the texquotes feature using OTF features, and hit two problems:

1) To support German quotes as well, I have two ligatures that end
up as the same glyph:
   `` -> “
   "' -> “
This can't be in the same ligature feature, as it will overwrite
the table entry with a duplicate key.

After some fiddling, I decided to map "' to a Unicode PUA symbol
and then add a second feature that maps this symbol to “ using
the substitute feature.  This works for TeX Gyre Schola.
But perhaps someone knows a nicer way.

2) This approach doesn't work for lmodern or palatino, I still
get "' as inch-sign/quote there... anything else I need to tweak
for these fonts?


\startluacode
 fonts.handlers.otf.addfeature {
 name = "texlig",
 type = "ligature",
 data = {
 ['“'] = { "`", "`" },
 ['”'] = { "'", "'" },
 ['„'] = { '"', "`" },
 [''] = { '"', "'" },
 ['‘'] = { "`" },
 ['’'] = { "'" }
 }
 }
 fonts.handlers.otf.addfeature {
 name = "texsub",
 type = "substitute",
 data = {
 [''] = '“',
 }
 }
\stopluacode

% with lmodern or palatino it breaks
\setupbodyfont[schola]

\definefontfeature[ltest][texlig=yes,texsub=yes,trep=no]
\addff{ltest}

\starttext

``foo'' `foo' "`foo"' 19" rack

\stoptext

can you show what is wrong and what it should be with

fonts.handlers.otf.addfeature {
name = "germantexlig",
type = "ligature",
data = {
['“'] = { "`", "`" },
['”'] = { "'", "'" },
['„'] = { '"', "`" },
['“'] = { '"', "'" },
['‘'] = { "`" },
['’'] = { "'" }
}
}

best not use an existign feature because we accumulate ... features come 
in order (you can force order if needed as you probably saw in one of 
the test files)


\definefontfeature[ltest][germantexlig=yes,trep=no] \addff{ltest}


-
  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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] LMTX: reimplementing texquotes as OTF feature

[Leah Neukirchen via ntg-context]

Hi,

as Hans recommended in the last video meeting, I tried to implement
the texquotes feature using OTF features, and hit two problems:

1) To support German quotes as well, I have two ligatures that end
   up as the same glyph:
  `` -> “
  "' -> “
   This can't be in the same ligature feature, as it will overwrite
   the table entry with a duplicate key.

   After some fiddling, I decided to map "' to a Unicode PUA symbol
   and then add a second feature that maps this symbol to “ using
   the substitute feature.  This works for TeX Gyre Schola.
   But perhaps someone knows a nicer way.

2) This approach doesn't work for lmodern or palatino, I still
   get "' as inch-sign/quote there... anything else I need to tweak
   for these fonts?


\startluacode
fonts.handlers.otf.addfeature {
name = "texlig",
type = "ligature",
data = {
['“'] = { "`", "`" },
['”'] = { "'", "'" },
['„'] = { '"', "`" },
[''] = { '"', "'" },
['‘'] = { "`" },
['’'] = { "'" }
}
}
fonts.handlers.otf.addfeature {
name = "texsub",
type = "substitute",
data = {
[''] = '“',
}
}
\stopluacode

% with lmodern or palatino it breaks
\setupbodyfont[schola]

\definefontfeature[ltest][texlig=yes,texsub=yes,trep=no]
\addff{ltest}

\starttext

``foo'' `foo' "`foo"' 19" rack

\stoptext


Thanks,
-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/13/2022 8:36 PM, Henning Hraban Ramm via ntg-context wrote:

Am 13.10.22 um 19:41 schrieb Pablo Rodriguez via ntg-context:

On 10/13/22 00:50, Max Chernoff via ntg-context wrote:

On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:

[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
We fixed that on the side. ;)


Yay!


Many thanks for your work fixing this, Leah and Hans.

The only remaining question is then when the new version will be be
released.


They who attended the latest online meeting know that there’s a secret 
project going on that needs to be completed first.
let's keep it a secret till at least the next meetup .. after all it 
relates to a more that 30 year old sort of secret


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/13/2022 7:41 PM, Pablo Rodriguez via ntg-context wrote:

On 10/13/22 00:50, Max Chernoff via ntg-context wrote:

On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:

[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
We fixed that on the side. ;)


Yay!


Many thanks for your work fixing this, Leah and Hans.

The only remaining question is then when the new version will be be
released.
some day soon ... the apple m1 has to come online first (afaik apple 
didn't release a robust vm yet so the machine has to be kicked into 
action every now and then) and we only release when we can do all 
platforms ... apart from ms and me wanting to finish something first


it's not that no-one can print, right?

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Willi Egger via ntg-context]

Now! I am astonished about this blog! Super that you, Leah and Hans, insisted 
to find out what the culprit was! Thank you both so much for your effort!

Kind regards
Willi

> On 11 Oct 2022, at 21:07, Leah Neukirchen via ntg-context 
>  wrote:
> 
> Hans Hagen via ntg-context  writes:
> 
>> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>>> Hi all,
>>> 
 I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
 
 Here's a tiny test document, I disabled PDF compression but it also
 doesn't work with the default settings.
 
 \setupbackend[level=0,compresslevel=0]
 \starttext
 Just a line of text.
 \stoptext
 
 When I print this "directly" (i.e. sending the raw PDF to the printer)
 on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>>> Just to add some more data points, I tested the attached MkXL file
>>> on
>>> two printers, and the file printed perfectly on both.
>>> Printer 1:
>>>Brother HL-3170CDW
>>>Printed via running "cat test.mkxl.pdf | nc Colour-Printer.local 9100"
>>>Printer 2:
>>>HP M227f LaserJet
>>>Printed from the PDF file on a USB stick
>>>Neither printer is anything fancy; they're both fairly
>>> inexpensive home
>>> laser printers. I've got a much older Brother laser printer that I may be
>>> able to test with next week.
>>> Sorry I can't be of more help.
>> Leah and I are zooming in on the issue. It might relate to wrong font
>> matrix default behavior in the pdf printer driver, and GS got a fix
>> for that long ago, so maybe old printers with not-updated drivers can
>> be affected.
>> 
>> Once we're confident that we can catch it Leah (who does the low level
>> introspective testing with viewers, printers and tools) likely will
>> report on it and there will be a test file for users to test if what
>> we do is okay before we apply the safeguard.
> 
> There's a write up now on the issue:
> https://leahneukirchen.org/blog/archive/2022/10/50-blank-pages-or-black-box-debugging-of-pdf-rendering-in-printers.html
> 
> -- 
> Leah Neukirchenhttps://leahneukirchen.org/
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Henning Hraban Ramm via ntg-context]

Am 13.10.22 um 19:41 schrieb Pablo Rodriguez via ntg-context:

On 10/13/22 00:50, Max Chernoff via ntg-context wrote:

On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:

[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
We fixed that on the side. ;)


Yay!


Many thanks for your work fixing this, Leah and Hans.

The only remaining question is then when the new version will be be
released.


They who attended the latest online meeting know that there’s a secret 
project going on that needs to be completed first.


Hraban

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Pablo Rodriguez via ntg-context]

On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
> On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
>> [...]
>> The last version of font-cff.lua should also copy the hinting-related
>> values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
>> We fixed that on the side. ;)
>
> Yay!

Many thanks for your work fixing this, Leah and Hans.

The only remaining question is then when the new version will be be
released.

Many thanks again for your work,

Pablo

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Max Chernoff via ntg-context]

On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
> > Seeing that you're modifying the font encoding, could you perhaps
> > reconsider supporting hinting in LMTX? 
> > 
> >https://mailman.ntg.nl/pipermail/ntg-context/2022/106311.html
> > 
> > Even with a high resolution screen, I can still see a difference, and
> > the issue can show up in print too:
> > 
> >
> >https://graphicdesign.stackexchange.com/q/5874
> >
> > I'm fairly confident that these issues are all hinting-related:
> > 
> >https://mailman.ntg.nl/pipermail/ntg-context/2022/106874.html
> >https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html
> >
> > Considering that all of the fonts included with ConTeXt are hinted, it
> > seems like a shame to not include any of that data in the generated
> > PDFs.
> 
> The last version of font-cff.lua should also copy the hinting-related
> values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
> We fixed that on the side. ;)

Yay!

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Max Chernoff via ntg-context  writes:

> Hi Leah,
>
>
>> > Leah and I are zooming in on the issue. It might relate to wrong font
>> > matrix default behavior in the pdf printer driver, and GS got a fix
>> > for that long ago, so maybe old printers with not-updated drivers can
>> > be affected.
>> >
>> > Once we're confident that we can catch it Leah (who does the low level
>> > introspective testing with viewers, printers and tools) likely will
>> > report on it and there will be a test file for users to test if what
>> > we do is okay before we apply the safeguard.
>> 
>> There's a write up now on the issue:
>> https://leahneukirchen.org/blog/archive/2022/10/50-blank-pages-or-black-box-debugging-of-pdf-rendering-in-printers.html
>
> Great write up! I was expecting the issue to be something quite simple,
> but it's actually fairly complicated. Especially considering that the
> issue only happens with a few printer models, I'm pretty impressed that
> you managed to find the problem. At least the fix appears quite easy.
>
> Seeing that you're modifying the font encoding, could you perhaps
> reconsider supporting hinting in LMTX? 
>
>https://mailman.ntg.nl/pipermail/ntg-context/2022/106311.html
>
> Even with a high resolution screen, I can still see a difference, and
> the issue can show up in print too:
>
>
>https://graphicdesign.stackexchange.com/q/5874
>
> I'm fairly confident that these issues are all hinting-related:
>
>https://mailman.ntg.nl/pipermail/ntg-context/2022/106874.html
>https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html
>
> Considering that all of the fonts included with ConTeXt are hinted, it
> seems like a shame to not include any of that data in the generated
> PDFs.

The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
We fixed that on the side. ;)

-- 
Leah Neukirchenhttps://leahneukirchen.org
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Max Chernoff via ntg-context]

Hi Leah,


> > Leah and I are zooming in on the issue. It might relate to wrong font
> > matrix default behavior in the pdf printer driver, and GS got a fix
> > for that long ago, so maybe old printers with not-updated drivers can
> > be affected.
> >
> > Once we're confident that we can catch it Leah (who does the low level
> > introspective testing with viewers, printers and tools) likely will
> > report on it and there will be a test file for users to test if what
> > we do is okay before we apply the safeguard.
> 
> There's a write up now on the issue:
> https://leahneukirchen.org/blog/archive/2022/10/50-blank-pages-or-black-box-debugging-of-pdf-rendering-in-printers.html

Great write up! I was expecting the issue to be something quite simple,
but it's actually fairly complicated. Especially considering that the
issue only happens with a few printer models, I'm pretty impressed that
you managed to find the problem. At least the fix appears quite easy.

Seeing that you're modifying the font encoding, could you perhaps
reconsider supporting hinting in LMTX? 

   https://mailman.ntg.nl/pipermail/ntg-context/2022/106311.html

Even with a high resolution screen, I can still see a difference, and
the issue can show up in print too:

   
   https://graphicdesign.stackexchange.com/q/5874
   
I'm fairly confident that these issues are all hinting-related:

   https://mailman.ntg.nl/pipermail/ntg-context/2022/106874.html
   https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html
   
Considering that all of the fonts included with ConTeXt are hinted, it
seems like a shame to not include any of that data in the generated
PDFs.

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Aditya Mahajan via ntg-context]

On Tue, 11 Oct 2022, Leah Neukirchen via ntg-context wrote:

> Hans Hagen via ntg-context  writes:

> > Once we're confident that we can catch it Leah (who does the low level
> > introspective testing with viewers, printers and tools) likely will
> > report on it and there will be a test file for users to test if what
> > we do is okay before we apply the safeguard.
> 
> There's a write up now on the issue:
> https://leahneukirchen.org/blog/archive/2022/10/50-blank-pages-or-black-box-debugging-of-pdf-rendering-in-printers.html

Wow, that was quite a ride. Kudos on getting to the bottom of this!

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>> Hi all,
>> 
>>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>>>
>>> Here's a tiny test document, I disabled PDF compression but it also
>>> doesn't work with the default settings.
>>>
>>> \setupbackend[level=0,compresslevel=0]
>>> \starttext
>>> Just a line of text.
>>> \stoptext
>>>
>>> When I print this "directly" (i.e. sending the raw PDF to the printer)
>>> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>> Just to add some more data points, I tested the attached MkXL file
>> on
>> two printers, and the file printed perfectly on both.
>> Printer 1:
>> Brother HL-3170CDW
>> Printed via running "cat test.mkxl.pdf | nc Colour-Printer.local 9100"
>> Printer 2:
>> HP M227f LaserJet
>> Printed from the PDF file on a USB stick
>> Neither printer is anything fancy; they're both fairly
>> inexpensive home
>> laser printers. I've got a much older Brother laser printer that I may be
>> able to test with next week.
>> Sorry I can't be of more help.
> Leah and I are zooming in on the issue. It might relate to wrong font
> matrix default behavior in the pdf printer driver, and GS got a fix
> for that long ago, so maybe old printers with not-updated drivers can
> be affected.
>
> Once we're confident that we can catch it Leah (who does the low level
> introspective testing with viewers, printers and tools) likely will
> report on it and there will be a test file for users to test if what
> we do is okay before we apply the safeguard.

There's a write up now on the issue:
https://leahneukirchen.org/blog/archive/2022/10/50-blank-pages-or-black-box-debugging-of-pdf-rendering-in-printers.html

-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:


Hi all,


I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.

Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.

\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext

When I print this "directly" (i.e. sending the raw PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.


Just to add some more data points, I tested the attached MkXL file on
two printers, and the file printed perfectly on both.

Printer 1:
Brother HL-3170CDW
Printed via running "cat test.mkxl.pdf | nc Colour-Printer.local 9100"

Printer 2:

HP M227f LaserJet
Printed from the PDF file on a USB stick

Neither printer is anything fancy; they're both fairly inexpensive home

laser printers. I've got a much older Brother laser printer that I may be
able to test with next week.

Sorry I can't be of more help.
Leah and I are zooming in on the issue. It might relate to wrong font 
matrix default behavior in the pdf printer driver, and GS got a fix for 
that long ago, so maybe old printers with not-updated drivers can be 
affected.


Once we're confident that we can catch it Leah (who does the low level 
introspective testing with viewers, printers and tools) likely will 
report on it and there will be a test file for users to test if what we 
do is okay before we apply the safeguard.


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Max Chernoff via ntg-context]

Hi all,

> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
> 
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
> 
> \setupbackend[level=0,compresslevel=0]
> \starttext
> Just a line of text.
> \stoptext
> 
> When I print this "directly" (i.e. sending the raw PDF to the printer)
> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.

Just to add some more data points, I tested the attached MkXL file on
two printers, and the file printed perfectly on both.

Printer 1:
   Brother HL-3170CDW
   Printed via running "cat test.mkxl.pdf | nc Colour-Printer.local 9100"
   
Printer 2:
   HP M227f LaserJet
   Printed from the PDF file on a USB stick
   
Neither printer is anything fancy; they're both fairly inexpensive home
laser printers. I've got a much older Brother laser printer that I may be
able to test with next week.

Sorry I can't be of more help.
-- Max
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> On 10/6/2022 2:42 PM, Leah Neukirchen wrote:
>
>> But I also found yet another printer model that doesn't print:
>> the HP Color LaserJet 4700 (Model Q7492A, Firmware 20060821 46.031.1).
>> Since you seem to own the only printer that works ;) would
>> you be so kind and share which model you have?
>
> We have a HP ColorFlowMFP X585 full-width highspeed duplex inkjet
> printer (a couple of years old, always prints ok). So far we never
> heard of printing failures elsewhere.
>
>> I also wondered whether bisecting the snapshot-repo would work.
>> But I only have one LMTX binary; this font handling should be all in
>> lua code tho?
>
> It makes no sense to compare luametatex and luatex .. it's different
> machinery.
>
> Btw, some in the thread mention issues (like bad looking heros shapes)
> but in your case there is no print at all, so that is different. Isn't
> there some error log in these printer?

The error log didn't contain anything useful.

I made two experiments now.

First, I modified the MKIV PDF file to use the MKXL font stream, and
changed the text primitives to use low chars.  This renders fine on
all PDF viewers I found (text is garbled, of course), but it still
doesn't print.  So now I'm fairly sure now the bug is in the font stream.



foo.doctored.pdf
Description: Adobe PDF document

I finally found a tool to analyze CID fonts at
https://github.com/janpe2/CFFDump
I noticed two things:
1) the MKIX Top DICT INDEX doesn't contain /version, but the string is
   in the SID.  Unfortunately merely adding it to topdict in
   tablewriters.cff doesn't fix the printing bug.  But I'd still
   recommend doing so.

2) The Private DICT doesn't contain /StdHW /StdVW /StemSnapH /StemSnapV.
   Also BlueScale is 0.
   This should not matter for printing(?) but it explains why
   Adobe displays it differently! The hinting information is missing.

   Note that the code would copy this data but it's missing in the
   cffinfo already.

I'll attach both CFF dumps here, perhaps someone finds other issues.



font-0008.mkiv.dump
Description: Binary data


font-0008.mkxl.dump
Description: Binary data

cu,
-- 
Leah Neukirchenhttps://leahneukirchen.org
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/6/2022 2:42 PM, Leah Neukirchen wrote:


But I also found yet another printer model that doesn't print:
the HP Color LaserJet 4700 (Model Q7492A, Firmware 20060821 46.031.1).

Since you seem to own the only printer that works ;) would
you be so kind and share which model you have?


We have a HP ColorFlowMFP X585 full-width highspeed duplex inkjet 
printer (a couple of years old, always prints ok). So far we never heard 
of printing failures elsewhere.



I also wondered whether bisecting the snapshot-repo would work.
But I only have one LMTX binary; this font handling should be all in
lua code tho?


It makes no sense to compare luametatex and luatex .. it's different 
machinery.


Btw, some in the thread mention issues (like bad looking heros shapes) 
but in your case there is no print at all, so that is different. Isn't 
there some error log in these printer?


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> On 10/6/2022 12:31 PM, Ulrike Fischer via ntg-context wrote:
>> Am Tue, 4 Oct 2022 18:09:28 +0200 schrieb Hans Hagen via
>> ntg-context:
>> 
 Hans, is it possible that LMTX uses some technique that is “too modern”
 for some built-in PDF interpreter?
>> 
>>> we basically use the old pre 1.6 embedding, same as luatex
>> I saw that the new code renumbers the glyphs, so it uses 0001, 0002
>> etc instead of the mix of various slot numbers in luatex. Perhaps
>> the printers don't like that.
> indeed, soem control code confusion; a few days ago i suggested a test
> for that and got no response yet

Sorry, I didn't have access to a printer until last night.

As I expected, starting the numbering from 31 doesn't help
either---still blank pages.  (Note that with DejaVu Sans the numbering
from 1 works fine.)

But I also found yet another printer model that doesn't print:
the HP Color LaserJet 4700 (Model Q7492A, Firmware 20060821 46.031.1).

Since you seem to own the only printer that works ;) would
you be so kind and share which model you have?

I also wondered whether bisecting the snapshot-repo would work.
But I only have one LMTX binary; this font handling should be all in
lua code tho?
-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/6/2022 12:31 PM, Ulrike Fischer via ntg-context wrote:

Am Tue, 4 Oct 2022 18:09:28 +0200 schrieb Hans Hagen via
ntg-context:


Hans, is it possible that LMTX uses some technique that is “too modern”
for some built-in PDF interpreter?



we basically use the old pre 1.6 embedding, same as luatex


I saw that the new code renumbers the glyphs, so it uses 0001, 0002
etc instead of the mix of various slot numbers in luatex. Perhaps
the printers don't like that.
indeed, soem control code confusion; a few days ago i suggested a test 
for that and got no response yet


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Ulrike Fischer via ntg-context]

Am Tue, 4 Oct 2022 18:09:28 +0200 schrieb Hans Hagen via
ntg-context:

>> Hans, is it possible that LMTX uses some technique that is “too modern” 
>> for some built-in PDF interpreter?

> we basically use the old pre 1.6 embedding, same as luatex

I saw that the new code renumbers the glyphs, so it uses 0001, 0002
etc instead of the mix of various slot numbers in luatex. Perhaps
the printers don't like that. 


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/5/2022 6:02 PM, Pablo Rodriguez via ntg-context wrote:


It happens both with LuaMetaTeX and LuaTeX. When playing with certain
levels of zooming, some blank spots are displayed inside the characters
(printing is fine).


Such artifacts can result from operating in the extremes and one has to 
keep in mind that maybe not all variables fonts have all characters 
tested for these extremes. Actually even regular fonts can have such 
effects like small bumps (we saw some in math fonts) and these also show 
up in font editors. But normally we don't see these at small sizes. Some 
has to do with 'sloppy or difficult or challenging' designs, some with 
(eo)fill side effects not much different from what mp graphics can do 
with envelopes (we've written about that). I'd not loose sleep over this.

 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Pablo Rodriguez via ntg-context]

On 10/3/22 20:57, Leah Neukirchen via ntg-context wrote:
>> [...]
>> \setupbackend[level=0,compresslevel=0]
>> \starttext
>> Just a line of text.
>> \stoptext
>> [...]
>
> On Acrobat DC on macOS, there is a visible difference between the two files:

Hi Leah,

this issue also happens with PDF.js included in Firefox. TeX Gyre Heros
is even clearer with dubious hinting.

It has been already reported
(https://bugzilla.mozilla.org/show_bug.cgi?id=1781022).

But even with variable fonts from Adobe
(https://github.com/adobe-fonts/source-code-pro/releases/latest),
Acrobat has issues with the following code:

\definefontfeature
[book]
[axis={weight=600}]

  \definefontfamily
[mainface]
[rm]
[SourceCodeVariable]
[features={book,none}]

  \setupbodyfont[mainface, 100pt]

  \starttext
  \startTEXpage[offset=1em]
  AefKkQrt4
  \stopTEXpage
  \stoptext

It happens both with LuaMetaTeX and LuaTeX. When playing with certain
levels of zooming, some blank spots are displayed inside the characters
(printing is fine).

BTW, as Hans explained
(https://mailman.ntg.nl/pipermail/ntg-context/2022/106840.html), the
following top line avoids your printing issue (by setting LuaTeX as the
engine, instead of LuaMetaTeX):

  % engine=luatex

Just in case it might help,

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Henning Hraban Ramm via ntg-context]

Am 04.10.22 um 18:11 schrieb Hans Hagen via ntg-context:
it is hidden in preflight, some tiny entry in a menu "browse internal 
.." or so but as adobe loves to change user interfaces with each version 
i have no clue where you can find it


Oops, I completely forgot that was part of Callas pdfInspektor (the 
plugin that Adobe bought as “Preflight” and didn’t even care to change 
the user interface).


Ok, so we (I) can analyze which characters of which font are embedded.

Here are the preflight reports (only about fonts and metadata) for 
Leah’s test files:

https://sedna.fiee.net/d/055c7150d6f24136b513/
Small, but still too big as attachments.
I don’t see anything suspicious.
Sorry, I can generate them only in German.

Hraban

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 5:52 PM, Leah Neukirchen via ntg-context wrote:


I looked into /StemV 0 (which was different in MKIV) but that works
with the TTF files, too.  Also should be ignored for Type 3 anyway.

Does your test have type 3 fonts? Should be no problem.

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 5:44 PM, Henning Hraban Ramm via ntg-context wrote:

Am 04.10.22 um 14:59 schrieb Hans Hagen via ntg-context:

On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:


Are there any tools to analyze this CID font stream?

You can browse the glyphs with full acrobat


You can? Not with Acrobat Pro v9 or before.
it is hidden in preflight, some tiny entry in a menu "browse internal 
.." or so but as adobe loves to change user interfaces with each version 
i have no clue where you can find it


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 6:03 PM, Henning Hraban Ramm via ntg-context wrote:

Am 04.10.22 um 15:21 schrieb Angel M Alganza via ntg-context:
On Tue, Oct 04, 2022 at 01:59:45PM +0200, Henning Hraban Ramm via 
ntg-context wrote:



How do you send the files “directly” to the printer? Copy to lpt queue?


In my case, as I explained in my original email, I plug in a USB drive
into the printer USB port, and I pick up the file to print from the
printer software on a touch screen.  I guess this qualifies as sendig te
file directly to the printer queue?


Yes, of course. Sorry, I didn’t read your mails thoroughly since I 
assumed I couldn’t help anyway.


Hans, is it possible that LMTX uses some technique that is “too modern” 
for some built-in PDF interpreter?
we basically use the old pre 1.6 embedding, same as luatex ... mayeb 
some other object is too modern (maybe some indirect reference is not 
seen or so but then one expects an error) .. I have no clue what is in 
those printers (it works here)


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Henning Hraban Ramm via ntg-context]

Am 04.10.22 um 15:21 schrieb Angel M Alganza via ntg-context:
On Tue, Oct 04, 2022 at 01:59:45PM +0200, Henning Hraban Ramm via 
ntg-context wrote:



How do you send the files “directly” to the printer? Copy to lpt queue?


In my case, as I explained in my original email, I plug in a USB drive
into the printer USB port, and I pick up the file to print from the
printer software on a touch screen.  I guess this qualifies as sendig te
file directly to the printer queue?


Yes, of course. Sorry, I didn’t read your mails thoroughly since I 
assumed I couldn’t help anyway.


Hans, is it possible that LMTX uses some technique that is “too modern” 
for some built-in PDF interpreter?


Hraban

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> Hi,
>
> does (the obsolete)
>
> \enabledirectives[backend.pdf.forcecidset]
>
> help

No; same blank page. :(

(Also MKIV works without CIDSet...)

I looked into /StemV 0 (which was different in MKIV) but that works
with the TTF files, too.  Also should be ignored for Type 3 anyway.

Really out of ideas now...

-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Henning Hraban Ramm via ntg-context]

Am 04.10.22 um 14:59 schrieb Hans Hagen via ntg-context:

On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:


Are there any tools to analyze this CID font stream?

You can browse the glyphs with full acrobat


You can? Not with Acrobat Pro v9 or before.

Hraban

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Angel M Alganza via ntg-context]

On Tue, Oct 04, 2022 at 01:59:45PM +0200, Henning Hraban Ramm via ntg-context 
wrote:


How do you send the files “directly” to the printer? Copy to lpt queue?


In my case, as I explained in my original email, I plug in a USB drive
into the printer USB port, and I pick up the file to print from the
printer software on a touch screen.  I guess this qualifies as sendig te
file directly to the printer queue?

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:


Are there any tools to analyze this CID font stream?
You can browse the glyphs with full acrobat (but I haven't a full 
acrobat installed ... I lost it when I upgraded my laptop and have no 
plans to buy a new version as I don't need it).


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

Hi,

does (the obsolete)

\enabledirectives[backend.pdf.forcecidset]

help

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:

Hans Hagen  writes:


what is sent to the printer .. maybe not pdf but something the printer
driver produces


For the Ricoh and Samsung printers, we printed the raw PDF directly
over JetDirect (port 9100).  For the Brother, the "upload PDF"
function was used.  So no outside printer drivers involved.

If I run it through Ghostscript, that somehow fixes it:
gs -dPDF -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=print.pdf foo.pdf

normally gs complains when there is an issue

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen  writes:

> what is sent to the printer .. maybe not pdf but something the printer
> driver produces

For the Ricoh and Samsung printers, we printed the raw PDF directly
over JetDirect (port 9100).  For the Brother, the "upload PDF"
function was used.  So no outside printer drivers involved.

If I run it through Ghostscript, that somehow fixes it:
gs -dPDF -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=print.pdf foo.pdf

But Ghostscript also seems to rewrite the font, at least in FontForge
it shows a different scale.

Are there any tools to analyze this CID font stream?

-- 
Leah Neukirchenhttps://leahneukirchen.org
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Henning Hraban Ramm via ntg-context]

Am 04.10.22 um 12:53 schrieb Leah Neukirchen via ntg-context:

Another data point: Brother B205 doesn't print it either.
But would all of these use the same licensed PDF renderer...


Print the test page of all these printers. Does it say something about 
the PDF/PostScript engine (RIP) and its version?
Printers that have an Adobe RIP usually have an Adobe sticker. But I’d 
guess that none of the mentioned printers has one of these. That doesn’t 
mean their RIP is worse.


How do you send the files “directly” to the printer? Copy to lpt queue?
In ye olden times you often used a PS downloader for such, but if it 
goes via the OS, there’s some driver involved.


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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 12:53 PM, Leah Neukirchen wrote:

Hans Hagen via ntg-context  writes:


On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote:

On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via
ntg-context wrote:


When I print this "directly" (i.e. sending the raw PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.

I believe that is the exact same problem I have and that I described
a
few days ago in my email with subject "Missing letters and numbers in
printout".  I have some grids on my document, which gets printed out,
but nothing else does.


Another data point: Brother B205 doesn't print it either.
But would all of these use the same licensed PDF renderer...


The PDFs render fine on every PDF reader I could find.

Same here.


PDFs generated directly from Context MKIV from TeXLive 2022 using
LuaTeX 1.5 render fine on these printers.
I've also printed PDFs from pdfTeX in the past fine.

Same here.


Any ideas what I should try to help debug this?

I was told that this is the default now, that isn't going to change,
and
that I could always use LuaTeX instead.  I could also use LaTeX, I
guess, but I'd rather keep using ConTeXt at least while my old 32 bits
OpenBSD installation works.

what happens if you include the lmtx pdf in a mkiv document as image


On above Brother B205, this document:

\starttext
\externalfigure[foo.mkxl.pdf]
\stoptext

only prints the page number of the outer document, which is kept in a
seperate font:

NREXLC+LMRoman12-Regular CID Type 0C   Identity-H   yes yes 
yes  5  0
CLLXEY+LMRoman12-Regular CID Type 0C   Identity-H   yes yes 
yes  8  0

I tried converting the pdf with pdfjam (which uses pdfTeX internally)
before, which probably uses similar mechanisms, and it didn't work
either.
what is sent to the printer .. maybe not pdf but something the printer 
driver produces


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote:
>> On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via
>> ntg-context wrote:
>> 
>>> When I print this "directly" (i.e. sending the raw PDF to the printer)
>>> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>> I believe that is the exact same problem I have and that I described
>> a
>> few days ago in my email with subject "Missing letters and numbers in
>> printout".  I have some grids on my document, which gets printed out,
>> but nothing else does.

Another data point: Brother B205 doesn't print it either.
But would all of these use the same licensed PDF renderer...

>>> The PDFs render fine on every PDF reader I could find.
>> Same here.
>> 
>>> PDFs generated directly from Context MKIV from TeXLive 2022 using
>>> LuaTeX 1.5 render fine on these printers.
>>> I've also printed PDFs from pdfTeX in the past fine.
>> Same here.
>> 
>>> Any ideas what I should try to help debug this?
>> I was told that this is the default now, that isn't going to change,
>> and
>> that I could always use LuaTeX instead.  I could also use LaTeX, I
>> guess, but I'd rather keep using ConTeXt at least while my old 32 bits
>> OpenBSD installation works.
> what happens if you include the lmtx pdf in a mkiv document as image

On above Brother B205, this document:

\starttext
\externalfigure[foo.mkxl.pdf]
\stoptext

only prints the page number of the outer document, which is kept in a
seperate font:

NREXLC+LMRoman12-Regular CID Type 0C   Identity-H   yes yes 
yes  5  0
CLLXEY+LMRoman12-Regular CID Type 0C   Identity-H   yes yes 
yes  8  0

I tried converting the pdf with pdfjam (which uses pdfTeX internally)
before, which probably uses similar mechanisms, and it didn't work
either.

-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote:
On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via 
ntg-context wrote:



When I print this "directly" (i.e. sending the raw PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.


I believe that is the exact same problem I have and that I described a
few days ago in my email with subject "Missing letters and numbers in
printout".  I have some grids on my document, which gets printed out,
but nothing else does.


The PDFs render fine on every PDF reader I could find.


Same here.


PDFs generated directly from Context MKIV from TeXLive 2022 using
LuaTeX 1.5 render fine on these printers.
I've also printed PDFs from pdfTeX in the past fine.


Same here.


Any ideas what I should try to help debug this?


I was told that this is the default now, that isn't going to change, and
that I could always use LuaTeX instead.  I could also use LaTeX, I
guess, but I'd rather keep using ConTeXt at least while my old 32 bits
OpenBSD installation works.

what happens if you include the lmtx pdf in a mkiv document as image

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Angel M Alganza via ntg-context]

On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via ntg-context wrote:


When I print this "directly" (i.e. sending the raw PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.


I believe that is the exact same problem I have and that I described a
few days ago in my email with subject "Missing letters and numbers in
printout".  I have some grids on my document, which gets printed out,
but nothing else does.


The PDFs render fine on every PDF reader I could find.


Same here.


PDFs generated directly from Context MKIV from TeXLive 2022 using
LuaTeX 1.5 render fine on these printers.
I've also printed PDFs from pdfTeX in the past fine.


Same here.


Any ideas what I should try to help debug this?


I was told that this is the default now, that isn't going to change, and
that I could always use LuaTeX instead.  I could also use LaTeX, I
guess, but I'd rather keep using ConTeXt at least while my old 32 bits
OpenBSD installation works.

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

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

> On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
>> Hi,
>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>> Here's a tiny test document, I disabled PDF compression but it also
>> doesn't work with the default settings.
>> \setupbackend[level=0,compresslevel=0]
>> \starttext
>> Just a line of text.
>> \stoptext
>> When I print this "directly" (i.e. sending the raw PDF to the
>> printer)
>> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>> The PDFs render fine on every PDF reader I could find.
>> Conversion to PostScript with pstopdf (poppler-22.07.0) and then
>> sending the PS renders the document correctly on the printer.
>> PDFs generated directly from Context MKIV from TeXLive 2022 using
>> LuaTeX 1.5 render fine on these printers.
>> I've also printed PDFs from pdfTeX in the past fine.
>> I attached the non-working 'foo.pdf.mkix'
>> and the working 'foo.pdf.mkiv' file.
>> I tried to disable font subsetting to debug this further, but I
>> couldn't figure out how to do it.
>
> subsetting should not be a problem and both files are subsetted  (lmxt
> a bit different but not fundamentally)

Well the idea was to have the same font stream in both files, so we
exclude that from the reasons it breaks.

Curiously, when I use Deja Vu:
\setupbodyfont[dejavu]

Then I get a
VHOYGZ+DejaVuSansMonoCID TrueType  Identity-H
   yes yes yes  8  0

and the PDF prints fine!  So it must be related to how Type 0C fonts
are written out, I think.

-- 
Leah Neukirchenhttps://leahneukirchen.org
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Hans Hagen via ntg-context]

On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:

Hi,

I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.

Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.

\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext

When I print this "directly" (i.e. sending the raw PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.

The PDFs render fine on every PDF reader I could find.

Conversion to PostScript with pstopdf (poppler-22.07.0) and then
sending the PS renders the document correctly on the printer.

PDFs generated directly from Context MKIV from TeXLive 2022 using
LuaTeX 1.5 render fine on these printers.
I've also printed PDFs from pdfTeX in the past fine.

I attached the non-working 'foo.pdf.mkix'
and the working 'foo.pdf.mkiv' file.

I tried to disable font subsetting to debug this further, but I
couldn't figure out how to do it.


subsetting should not be a problem and both files are subsetted  (lmxt a 
bit different but not fundamentally)



Any ideas what I should try to help debug this?

i'm clueless ...

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Leah Neukirchen via ntg-context  writes:

> Hi,
>
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compresslevel=0]
> \starttext
> Just a line of text.
> \stoptext
>
> When I print this "directly" (i.e. sending the raw PDF to the printer)
> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>
> The PDFs render fine on every PDF reader I could find.

On Acrobat DC on macOS, there is a visible difference between the two files:


Note that the 'a' and 'l' look quite different.

But I couldn't reproduce it with MuPDF for example.

-- 
Leah Neukirchenhttps://leahneukirchen.org
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

[NTG-context] LMTX generates PDFs with non-working fonts on real printers

[Leah Neukirchen via ntg-context]

Hi,

I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.

Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.

\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext

When I print this "directly" (i.e. sending the raw PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.

The PDFs render fine on every PDF reader I could find.

Conversion to PostScript with pstopdf (poppler-22.07.0) and then
sending the PS renders the document correctly on the printer.

PDFs generated directly from Context MKIV from TeXLive 2022 using
LuaTeX 1.5 render fine on these printers.
I've also printed PDFs from pdfTeX in the past fine.

I attached the non-working 'foo.pdf.mkix'
and the working 'foo.pdf.mkiv' file.

I tried to disable font subsetting to debug this further, but I
couldn't figure out how to do it.

Any ideas what I should try to help debug this?



foo.pdf.mkxl
Description: Binary data


foo.pdf.mkiv
Description: Binary data

cu,
-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] LMTX incompatibility in \meaning breaks TikZ, other minor issues

[Leah Neukirchen via ntg-context]

Hans Hagen via ntg-context  writes:

>> After a bunch of debugging, it turns out that LMTX breaks the TikZ
>> 'quotes'
>> library, which works using code ala:
>> \def\tikz@enable@node@quotes{%
>>\pgfkeyssetvalue{/handlers/first char syntax/the character
>> "}{\tikz@quote@parser}%
>>\let\tikz@quotes@as\tikz@node@quotes@as%
>> }
>> The last part of the /-key is derived from \meaning, but in LMTX,
>> \meaning" is "the character U+0022 'quotation mark'"
>> and thus the key cannot be found.
>> I have patched TikZ for now to match for this alternate string too.
>
> a bit weird way to test a key .. maybe you can compare to
>
> \edef\ThatQuote{\meaning/}
>
> using \ifx
>
>> But perhaps it would be better for compatibility to agree with the
>> original TeX \meaning strings for the 7-bit ASCII subset at least. 
>
> too messy when want to parse

To follow up on this: I have upstreamed patches to tikz and tikz-cd to
use the dynamic output of \meaning instead of hardcoding.

I'm not sure who maintains the t-tikz module, but if it gets updated
at some point the fix should be in.

-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

[NTG-context] lmtx status

[Hans Hagen via ntg-context]

Hi,

At the ctx meeting we released luametatex, that is, the source code is 
now in the context zip (so it grew a few MB). At the same time Mojca set 
up some contextgarden repositories on github. We're working on a setup 
for users to generate older snapshots, if needed (for instance because 
there are platform changes). She's also working on cmake based 
installation helpers.


One of the things we did was pruning the fonts that are part of the 
installation. With a few exceptions the type one fonts were dropped, 
which is most noticeable for math. There is no need for px and tx fonts, 
they served their puspose in the transition from old style t1 fonts to 
opentype math (when we started with mkiv; we could have dropped them 
already).


We're looking into antykwa math as well as in alternative script and 
calligraphic math alphabets so eventually virtual math from t1 
construction can be dropped completely (in principle if can be 
integrated in the tweak mechanisms) because it is not wirth the effort 
to make them better. That means that we will ship some additional 
companion fonts.


There are math times fonts but they are currently not free and there is 
some effort going on to turn them opentype so we can ditch their setups 
too (we can't test anyway; to some extend that is also true for minion 
math).


High on the agenda is euler (in combination with pagella). This also 
relates to upgraded mixed script and calligraphic support in math. It 
actually means that enabling alternative alphabets will happen a bit 
differently (more naturally integrated as we introduced dedicated ranges 
of slots). Again a side effect is that we have more granular math glyph 
properties (opentype math is too limited but basically frozen so we have 
to get over that and move on). We (Mikael and me) also try to compensate 
for the ommissions and weird things in unicode math but it will take 
some time before we have that all documented.


One of the next uploads will have the pruned / upgraded texmf tree (one 
can always install more in the local tree of course). At some point 
installing from the garden (or from a git clone) will also be supported 
(basically anyone can host a lmtx install).


For the next texlive we hope to switch to lmtx as default and that also 
means that luametatex is the runner then. One can (as currently in lmtx) 
always run luatex with "--luatex".


Als-in-all it's a lot of work but we're getting there.

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] LMTX incompatibility in \meaning breaks TikZ, other minor issues

[Hans Hagen via ntg-context]

On 9/22/2022 2:23 PM, Leah Neukirchen via ntg-context wrote:

Hi,

I'm trying to get tikz-cd to run on LMTX and some examples already
work fine, but I had a problem with text on arrows.

To reproduce:

\usemodule[tikz]
\usetikzlibrary[cd]

\starttext
\starttikzcd
A \arrow{r}{A} \NC B \NR
\stoptikzcd
\stoptext

This builds fine on MkIV from TeXLive 2022 with LuaTeX, but on LMTX I get:

system  > ConTeXt  ver: 2022.09.11 20:44 LMTX  fmt: 2022.9.20  int: 
english/english
...
close source> level 2, order 63, name 'tikzlibrarycd.code.tex'
fonts   > preloading latin modern fonts (second stage)
fonts   > 'fallback modern-designsize rm 12pt' is loaded
tex error   > tex error on line 8 in file ./tik.tex: Package pgfkeys Error: I do not 
know the key '/tikz/"{A}"{}' and I am going to ignore it. Perhaps you misspelled 
it.^^J...^^Jl.7 I think the culprit is a tikzcd arrow in cell 1-1

After a bunch of debugging, it turns out that LMTX breaks the TikZ 'quotes'
library, which works using code ala:

\def\tikz@enable@node@quotes{%
   \pgfkeyssetvalue{/handlers/first char syntax/the character 
"}{\tikz@quote@parser}%
   \let\tikz@quotes@as\tikz@node@quotes@as%
}

The last part of the /-key is derived from \meaning, but in LMTX,
\meaning" is "the character U+0022 'quotation mark'"
and thus the key cannot be found.

I have patched TikZ for now to match for this alternate string too.


a bit weird way to test a key .. maybe you can compare to

\edef\ThatQuote{\meaning/}

using \ifx


But perhaps it would be better for compatibility to agree with the
original TeX \meaning strings for the 7-bit ASCII subset at least. 


too messy when want to parse


I found another minor nit that's not really triggering a bug but still a
difference to LuaTeX: \eTeXrevision should expand to .2, but it
expands to 2 in MkIX.  There is some code out there which uses
constructions like
\number\eTeXversion\eTeXrevision
or even
\ifdim 0\XeTeXrevision pt > 0.9996pt

As LMTX doesn't care about this macro, this should be easy to adjust.
i'll add the period; btw afaikt testing for an etex version is useless 
because all used engines have it and there is basically only one version 
and there will be no follow ups


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] LMTX incompatibility in \meaning breaks TikZ, other minor issues

[Leah Neukirchen via ntg-context]

Hi,

I'm trying to get tikz-cd to run on LMTX and some examples already
work fine, but I had a problem with text on arrows.

To reproduce:

\usemodule[tikz]
\usetikzlibrary[cd]

\starttext
\starttikzcd
A \arrow{r}{A} \NC B \NR
\stoptikzcd
\stoptext

This builds fine on MkIV from TeXLive 2022 with LuaTeX, but on LMTX I get:

system  > ConTeXt  ver: 2022.09.11 20:44 LMTX  fmt: 2022.9.20  int: 
english/english
...
close source> level 2, order 63, name 'tikzlibrarycd.code.tex'
fonts   > preloading latin modern fonts (second stage)
fonts   > 'fallback modern-designsize rm 12pt' is loaded
tex error   > tex error on line 8 in file ./tik.tex: Package pgfkeys Error: 
I do not know the key '/tikz/"{A}"{}' and I am going to ignore it. Perhaps you 
misspelled it.^^J...^^Jl.7 I think the culprit is a tikzcd arrow in cell 1-1

After a bunch of debugging, it turns out that LMTX breaks the TikZ 'quotes'
library, which works using code ala:

\def\tikz@enable@node@quotes{%
  \pgfkeyssetvalue{/handlers/first char syntax/the character 
"}{\tikz@quote@parser}%
  \let\tikz@quotes@as\tikz@node@quotes@as%
}

The last part of the /-key is derived from \meaning, but in LMTX,
\meaning" is "the character U+0022 'quotation mark'"
and thus the key cannot be found.

I have patched TikZ for now to match for this alternate string too.

But perhaps it would be better for compatibility to agree with the
original TeX \meaning strings for the 7-bit ASCII subset at least.


I found another minor nit that's not really triggering a bug but still a
difference to LuaTeX: \eTeXrevision should expand to .2, but it
expands to 2 in MkIX.  There is some code out there which uses
constructions like
\number\eTeXversion\eTeXrevision
or even
\ifdim 0\XeTeXrevision pt > 0.9996pt

As LMTX doesn't care about this macro, this should be easy to adjust.


Thanks,
-- 
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] lmtx and \prime ?

[Hans Hagen via ntg-context]

On 8/4/2022 8:52 PM, Michael Urban via ntg-context wrote:

I get a different result for mkiv and lmtx for the following input:

\starttext
  Even now, a six footer is two
standard deviations from the mean. Remember, 5\prime{}7\prime\prime{} is 50th 
percentile today
for a 15 year old.
\stoptext


With mkiv, the prime marks for inches and feet are where I expect them; in 
lmtx, they are placed almost to the baseline.

Wrong lmtx, or user error?


% you can add this to cont-new.mkxl

\immutable\Umathchardef\minute\zerocount\zerocount\privatecharactercode{prime 
0x2032 1}
\immutable\Umathchardef\second\zerocount\zerocount\privatecharactercode{prime 
0x2033 1}


\starttext

Even now, a six footer is two standard deviations from the mean. Remember,
5\minute7\second\ is 50\high{th} percentile today for a 15 year old.

\stoptext

I need to discuss this with Mikael as it assumes that all math fonts are 
set up that way). In lmtx (luametatex) primes are native features and 
assume dimensions that we can work with (primes and minutes are a 
typical example of messed up math unicode).


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] lmtx and \prime ?

[Michael Urban via ntg-context]

I get a different result for mkiv and lmtx for the following input:

\starttext
 Even now, a six footer is two
standard deviations from the mean. Remember, 5\prime{}7\prime\prime{} is 50th 
percentile today
for a 15 year old. 
\stoptext


With mkiv, the prime marks for inches and feet are where I expect them; in 
lmtx, they are placed almost to the baseline.

Wrong lmtx, or user error?

Mike

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

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

[NTG-context] LMTX and modules

[Axel Kielhorn via ntg-context]

Hello,

Some years ago I wrote an introduction to ConTeXt in German:

https://github.com/AKielhorn/Context-Intro

But that was long ago.

Today LMTX is state of the art and I tried to build it with a recent LMTX.

This lead to problems because LMTX does not include modules.

Therefore my question is:
Is the a plan to include modules into the regular LMTX installation?

If not, is there a way to test for a certain module?

\doiffileexists{m-module}
\usemodule{module}

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

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

Re: [NTG-context] lmtx \placeinitial with nonzero par indent?

[Michael Urban via ntg-context]

Never mind.  Apparently lmtx changed the default for \setupindenting from 
'next' to 'first'?
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

[NTG-context] lmtx \placeinitial with nonzero par indent?

[Michael Urban via ntg-context]

The following produces different results in mkiv and lmtx (to which I am brand 
new):



\setupinitial[distance=1pt,font=Serif at 36pt,n=2]
\setupindenting[medium,yes]

\starttext

\placeinitial
\input knuth

\stoptext





The mkiv output is the desired effect.  It works fine in lmtx if I do not 
change to medium indentation.   Is this a bug or a feature (i.e., should I 
change something to work properly in both environments)?

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

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

Re: [NTG-context] lmtx installation paths not working

[Jano Kula via ntg-context]

Hello list,

thank you all for your advices.

Aditya was right. There was some mess in PATH variable.
Lesson learned: start with explicit paths to executables.
Still where mtxrun (Windows) was pointing to the right one, which was
fooling me.

I've noticed the problem with antivirus SW during the first installation of
lmtx.
It wasn't the case this time, but one should be aware antivirus programs
don't trust mtxrun.exe.

Thank you once again,
Jano



On Wed, Jun 15, 2022 at 11:23 PM Bruce Horrocks  wrote:

>
>
> > On 14 Jun 2022, at 12:20, Jano Kula via ntg-context 
> wrote:
> >
> > Do you have an idea how to fix problem?
> > I will be thankful for an advice, it is quite urgent (everything was
> working yesterday).
>
> Do you have an anti-virus product installed?
>
> In the past I've noticed that Symantec sometimes gives a false positive on
> some of the ConTeXt files as they are installed and silently deletes them
> thinking they contain malware.
>
> The result is a broken ConTeXt because files are missing but you have no
> idea which files are missing. :-(
>
> Try temporarily disabling AV and then do a complete re-install into an
> empty C:/data/context directory.
>
> —
> Bruce Horrocks
> Hampshire, UK
>
>
___
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] lmtx installation paths not working

[Bruce Horrocks via ntg-context]

> On 14 Jun 2022, at 12:20, Jano Kula via ntg-context  
> wrote:
> 
> Do you have an idea how to fix problem?
> I will be thankful for an advice, it is quite urgent (everything was working 
> yesterday).

Do you have an anti-virus product installed?

In the past I've noticed that Symantec sometimes gives a false positive on some 
of the ConTeXt files as they are installed and silently deletes them thinking 
they contain malware.

The result is a broken ConTeXt because files are missing but you have no idea 
which files are missing. :-(

Try temporarily disabling AV and then do a complete re-install into an empty 
C:/data/context directory.

—
Bruce Horrocks
Hampshire, UK

___
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] lmtx installation paths not working

[Alain Delmotte via ntg-context]

  
  
Hello,
I do not understand what you did!
I went to "http://www.pragma-ade.com/install.htm"
downlaoded the 64 bit Microsoft Windows file
"context-win64.zip".
I did create a folder c:\data\context
wher I did put the .zip file and unzipped it.
I got 
  
c:\data\context\bin
  c:\data\context\context-win64.zip
  c:\data\context\install.bat
  c:\data\context\installation.pdf
  c:\data\context\setpath.bat
Double-cliquing the install.bat it did
install all the structure; it took some time to fetch and unzip
texmf.zip and texmf-context.zip. After this doubleclic
setpath.bat ad everything was ok!
Hope this help.
Alain

Le 14/06/2022 à 13:20, Jano Kula via
  ntg-context a écrit :


  
  Hello list,


I cannot make fresh install of lmtx to work. The structure
  after unzipping:

  C:\data\context\bin\beta
  
  C:\data\context\bin\beta\bin
  
  C:\data\context\bin\beta\tex
  
  C:\data\context\bin\beta\tex\texmf
  
  C:\data\context\bin\beta\tex\texmf-cache
  
  C:\data\context\bin\beta\tex\texmf-context

etc.


First compilation of texfile is not working, so mtxrun --generate is the friend.



  C:\data>mtxrun --generate
  
  
  These paths contain probably
  correct path (watch /beta):
  
resolvers       | resolving | variable 'SELFAUTOLOC' set to
'C:/data/context/bin/beta/bin'
resolvers       | resolving | variable 'SELFAUTODIR' set to
'C:/data/context/bin/beta'
resolvers       | resolving | variable 'SELFAUTOPARENT' set
to 'C:/data/context/bin'
resolvers       | resolving | variable 'TEXMFCNF' set to ''
resolvers       | resolving | variable 'TEXMF' set to ''
resolvers       | resolving | variable 'TEXOS' set to 'beta'
resolvers       | resolving |
  
  
  and the paths bellow have no /beta from
  above, they are derived from selfautoparent C:/data/context/bin
(without /beta), so no surprise
  they cannot be found.
  
resolvers       | resolving | using configuration
specification
'home:texmf/web2c;selfautoparent:/texmf-local/web2c;selfautoparent:/texmf-context/web2c;selfautoparent:/texmf-dist/web2c;selfautoparent:/texmf/web2c'
resolvers       | resolving |
resolvers       | resolving | looking for regular
'texmfcnf.lua' on given path 'C:/Users/jano/texmf/web2c'
from specification 'home:texmf/web2c'
resolvers       | resolving | looking for regular
'texmfcnf.lua' on given path 'C:/data/context/bin/texmf-local/web2c'
from specification 'selfautoparent:/texmf-local/web2c'
resolvers       | resolving | looking for regular
'texmfcnf.lua' on given path 'C:/data/context/bin/texmf-context/web2c' from
specification 'selfautoparent:/texmf-context/web2c'
resolvers       | resolving | looking for regular
'texmfcnf.lua' on given path 'C:/data/context/bin/texmf-dist/web2c'
from specification 'selfautoparent:/texmf-dist/web2c'
  [... skip ...]
resolvers       | resolving | looking for regular
'texmfcnf.lua' on given path 
resolvers       | resolving |
resolvers       | resolving | warning: no lua configuration
files found
resolvers       | resolving | no texmf paths are defined
(using TEXMF)
resolvers       | resolving |
mtxrun          |
mtxrun          | elapsed lua time: 0.026 seconds

 
Do you have an idea how to fix problem?
I will be thankful for an advice, it is quite urgent
  (everything was working yesterday).


Thank you,
Jano


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

Re: [NTG-context] lmtx installation paths not working

[Aditya Mahajan via ntg-context]

On Tue, 14 Jun 2022, Jano Kula via ntg-context wrote:

> Hello list,
> 
> I cannot make fresh install of lmtx to work. The structure after unzipping:
> C:\data\context\bin\beta
> C:\data\context\bin\beta\bin
> C:\data\context\bin\beta\tex
> C:\data\context\bin\beta\tex\texmf
> C:\data\context\bin\beta\tex\texmf-cache
> C:\data\context\bin\beta\tex\texmf-context
> etc.
> 
> First compilation of texfile is not working, so mtxrun --generate is the
> friend.
> 
> C:\data>mtxrun --generate

It appears that you are running the wrong mtxrun. There should be mtxrun in 
C:\data\context\beta\texmf-win64\bin (the texmf-win64 directory might be named 
slightly differently, I haven't used windows in a while). If you add that to 
your path, then mtxrun --generate should work.

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] lmtx installation paths not working

[Jano Kula via ntg-context]

Hello,

I didn't mention the platform: context-setup-win64.

Thank you,
Jano

On Tue, Jun 14, 2022 at 1:20 PM Jano Kula  wrote:

> Hello list,
>
> I cannot make fresh install of lmtx to work. The structure after unzipping:
> C:\data\context\bin\beta
> C:\data\context\bin\beta\bin
> C:\data\context\bin\beta\tex
> C:\data\context\bin\beta\tex\texmf
> C:\data\context\bin\beta\tex\texmf-cache
> C:\data\context\bin\beta\tex\texmf-context
> etc.
>
> First compilation of texfile is not working, so mtxrun --generate is the
> friend.
>
> C:\data>mtxrun --generate
>
> These paths contain probably correct path (watch /beta):
>
> resolvers   | resolving | variable 'SELFAUTOLOC' set to '
> *C:/data/context/bin/beta/bin*'
> resolvers   | resolving | variable 'SELFAUTODIR' set to '
> *C:/data/context/bin/beta*'
> resolvers   | resolving | variable 'SELFAUTOPARENT' set to '
> *C:/data/context/bin*'
> resolvers   | resolving | variable 'TEXMFCNF' set to ''
> resolvers   | resolving | variable 'TEXMF' set to ''
> resolvers   | resolving | variable 'TEXOS' set to 'beta'
> resolvers   | resolving |
>
> and the paths bellow have no */beta* from above, they are derived from
> selfautoparent *C:/data/context/bin *(without /beta), so no surprise they
> cannot be found.
>
> resolvers   | resolving | using configuration specification
> 'home:texmf/web2c;selfautoparent:/texmf-local/web2c;selfautoparent:/texmf-context/web2c;selfautoparent:/texmf-dist/web2c;selfautoparent:/texmf/web2c'
> resolvers   | resolving |
> resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
> path 'C:/Users/jano/texmf/web2c' from specification 'home:texmf/web2c'
> resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
> path *'C:/data/context/bin/texmf-local/web2c*' from specification
> 'selfautoparent:/texmf-local/web2c'
> resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
> path '*C:/data/context/bin/texmf-context/web2c'* from specification
> 'selfautoparent:/texmf-context/web2c'
> resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
> path '*C:/data/context/bin/texmf-dist/web2c*' from specification
> 'selfautoparent:/texmf-dist/web2c'
> [... skip ...]
> resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
> path
> resolvers   | resolving |
> resolvers   | resolving | warning: no lua configuration files found
> resolvers   | resolving | no texmf paths are defined (using TEXMF)
> resolvers   | resolving |
> mtxrun  |
> mtxrun  | elapsed lua time: 0.026 seconds
>
> Do you have an idea how to fix problem?
> I will be thankful for an advice, it is quite urgent (everything was
> working yesterday).
>
> Thank you,
> Jano
>
>
___
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] lmtx installation paths not working

[Jano Kula via ntg-context]

Hello list,

I cannot make fresh install of lmtx to work. The structure after unzipping:
C:\data\context\bin\beta
C:\data\context\bin\beta\bin
C:\data\context\bin\beta\tex
C:\data\context\bin\beta\tex\texmf
C:\data\context\bin\beta\tex\texmf-cache
C:\data\context\bin\beta\tex\texmf-context
etc.

First compilation of texfile is not working, so mtxrun --generate is the
friend.

C:\data>mtxrun --generate

These paths contain probably correct path (watch /beta):

resolvers   | resolving | variable 'SELFAUTOLOC' set to '
*C:/data/context/bin/beta/bin*'
resolvers   | resolving | variable 'SELFAUTODIR' set to '
*C:/data/context/bin/beta*'
resolvers   | resolving | variable 'SELFAUTOPARENT' set to '
*C:/data/context/bin*'
resolvers   | resolving | variable 'TEXMFCNF' set to ''
resolvers   | resolving | variable 'TEXMF' set to ''
resolvers   | resolving | variable 'TEXOS' set to 'beta'
resolvers   | resolving |

and the paths bellow have no */beta* from above, they are derived from
selfautoparent *C:/data/context/bin *(without /beta), so no surprise they
cannot be found.

resolvers   | resolving | using configuration specification
'home:texmf/web2c;selfautoparent:/texmf-local/web2c;selfautoparent:/texmf-context/web2c;selfautoparent:/texmf-dist/web2c;selfautoparent:/texmf/web2c'
resolvers   | resolving |
resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
path 'C:/Users/jano/texmf/web2c' from specification 'home:texmf/web2c'
resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
path *'C:/data/context/bin/texmf-local/web2c*' from specification
'selfautoparent:/texmf-local/web2c'
resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
path '*C:/data/context/bin/texmf-context/web2c'* from specification
'selfautoparent:/texmf-context/web2c'
resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
path '*C:/data/context/bin/texmf-dist/web2c*' from specification
'selfautoparent:/texmf-dist/web2c'
[... skip ...]
resolvers   | resolving | looking for regular 'texmfcnf.lua' on given
path
resolvers   | resolving |
resolvers   | resolving | warning: no lua configuration files found
resolvers   | resolving | no texmf paths are defined (using TEXMF)
resolvers   | resolving |
mtxrun  |
mtxrun  | elapsed lua time: 0.026 seconds

Do you have an idea how to fix problem?
I will be thankful for an advice, it is quite urgent (everything was
working yesterday).

Thank you,
Jano
___
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] LMTX | (.\) at end of line causes fatal error

[Hans Hagen via ntg-context]

On 3/5/2022 9:39 PM, Richard Mahoney via ntg-context wrote:

Something I've noticed for a little while now, although it may be
long standing, I'm not sure. If one ends some of the lines in
the input files with a full stop (.) and a back slash (\) then LMTX
will fail to compile with a fatal error. The only way to recover is
to go through each of the files and ensure that no line ends with
(.\).

Is this a bug?

can there be somee invisible character after the \ ?

otherwise, we need a mwe

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] LMTX | (.\) at end of line causes fatal error

[Richard Mahoney via ntg-context]

Something I've noticed for a little while now, although it may be
long standing, I'm not sure. If one ends some of the lines in
the input files with a full stop (.) and a back slash (\) then LMTX
will fail to compile with a fatal error. The only way to recover is
to go through each of the files and ensure that no line ends with
(.\).

Is this a bug?


Best, Richard



-- 
T +6433121699  M +64210640216
rmaho...@indica-et-buddhica.org
https://indica-et-buddhica.org/

Indica et Buddhica
Littledene  Bay Road  Oxford  NZ
NZBN: 9429041761809



___
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] LMTX-latest | SciTE 5.1.6 --- 5.2.1 | Not working with tex/texmf-context/context/data/scite

[Richard Mahoney via ntg-context]

Thank you for this Hans.


Best, Richard


-- 
T +6433121699  M +64210640216
rmaho...@indica-et-buddhica.org
https://indica-et-buddhica.org/

Indica et Buddhica
Littledene  Bay Road  Oxford  NZ
NZBN: 9429041761809



-Original Message-
From: Hans Hagen via ntg-context 
Reply-To: mailing list for ConTeXt users 
To: Richard Mahoney via ntg-context 
Cc: Hans Hagen 
Subject: Re: [NTG-context] LMTX-latest | SciTE 5.1.6 --- 5.2.1 | Not
working with tex/texmf-context/context/data/scite
Date: Thu, 3 Mar 2022 08:53:06 +0100
Mailer: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0)
Gecko/20100101 Thunderbird/91.6.1
X-Spam-Score: 0.0

On 3/3/2022 12:08 AM, Richard Mahoney via ntg-context wrote:
> [Gentoo]
> 
> I've found that the config included with LMTX in:
> 
> tex/texmf-context/context/data/scite
> 
> does not work with SciTE 5.1.6+
> 
> The latest version that seems to be working is SciTE 5.1.5.
> 
> Version 5.1.5 Scintilla: 5.1.4 Lexilla: 5.1.3
> compiled for GTK:3.24.29
> Nov 14 2021 12:15:50
> 
> Is anyone else having any issues?
for long i time tried to keep up with the changes in the lpef plugin
but 
it kept changing to i quit using it; in the zip below is a version of 
scite with a built in lpeg ... i have adapted teh lexers but need to 
have a look at them again (i now go via some scite interfaces but
these 
sometimes have side effects i need to nail down more).

http://www.pragma-ade.com/context/latest/cont-sci.zip

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
__
_

___
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] LMTX-latest | SciTE 5.1.6 --- 5.2.1 | Not working with tex/texmf-context/context/data/scite

[Hans Hagen via ntg-context]

On 3/3/2022 12:08 AM, Richard Mahoney via ntg-context wrote:

[Gentoo]

I've found that the config included with LMTX in:

tex/texmf-context/context/data/scite

does not work with SciTE 5.1.6+

The latest version that seems to be working is SciTE 5.1.5.

Version 5.1.5 Scintilla: 5.1.4 Lexilla: 5.1.3
compiled for GTK:3.24.29
Nov 14 2021 12:15:50

Is anyone else having any issues?
for long i time tried to keep up with the changes in the lpef plugin but 
it kept changing to i quit using it; in the zip below is a version of 
scite with a built in lpeg ... i have adapted teh lexers but need to 
have a look at them again (i now go via some scite interfaces but these 
sometimes have side effects i need to nail down more).


http://www.pragma-ade.com/context/latest/cont-sci.zip

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] LMTX-latest | SciTE 5.1.6 --- 5.2.1 | Not working with tex/texmf-context/context/data/scite

[Richard Mahoney via ntg-context]

[Gentoo]

I've found that the config included with LMTX in:

tex/texmf-context/context/data/scite

does not work with SciTE 5.1.6+

The latest version that seems to be working is SciTE 5.1.5.

Version 5.1.5 Scintilla: 5.1.4 Lexilla: 5.1.3
compiled for GTK:3.24.29
Nov 14 2021 12:15:50

Is anyone else having any issues? 


Best, Richard



-- 
T +6433121699  M +64210640216 
rmaho...@indica-et-buddhica.com
https://indica-et-buddhica.org/

Indica et Buddhica Publishers
Littledene  Bay Road  Oxford  NZ
NZBN: 9429041761809



___
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] lmtx

[Hans Hagen via ntg-context]

Hi,

There haven't been updates and the reason is that we're in the middle of 
math and/or wrapping up on transliteration / indic (for which there is 
also a nice wiki page being made).


Concerning math, we're progressing with some rather flexible spacing, 
penalty, linebreak extensions but don't want to risk that when not used 
it gives different results (probably not all can be completely 
compatible but that is a side effect of getting rid of some hard coded 
assumptions in the engine). One objective is to make input a bit easier 
and predictable, esp wrt the often needed correction spacing (\, and 
friends).


Anyway, in addition to Mikaels request for input an while ago ... if 
there are 'tex math annoyances' that you think originate in the way tex 
expects input, and you'd like them to be taken into account, let us know.


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] LMTX error processing Adobe Arabic Naskh font

[Idris Samawi Hamid ادريس سماوي حامد via ntg-context]

Problems I and II are apparently solved in the latest update. As for III,  
the following works:


\definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]

\noheaderandfooterlines
\setupwhitespace[big]

% \starttext
\startTEXpage[offset=1ex]
% \setupdirections[bidi=global,method=one]
\righttoleft
% \setupalign[r2l]
% \dontleavehmode \setupalign[r2l]
\ARABICFONT

\utfchar{"062E}\utfchar{"064E}\utfchar{"200D}
\stopTEXpage
% \stoptext

As Hans explained off-list, TEXpage interacts with hmode and vmode in ways  
that may appear unpredictable in some circumstances. In this case the  
circumstance is


% \setupdirections[bidi=global,method=one]

Uncommenting this line will bring the bidi issue back, but it's not needed  
for the desired result.


Best wishes
Idris

On Wed, 10 Nov 2021 09:00:26 -0700, Idris Samawi Hamid ادريس سماوي حامد  
via ntg-context  wrote:



Dear Hans and gang,

Consider the following MWE:

==
\definefont[ARABICFONT][file:Adobe_Naskh.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Amiri-Regular_0.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Scheherazade-Regular.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:UthmanTN1_Ver10.otf*arabic at 28pt]
% \definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]

\disabledirectives[filters.utf.reorder]
\noheaderandfooterlines

\setupwhitespace[big]
% \setupinterlinespace[line=4.2ex]

\starttext
% \startTEXpage[offset=1ex]
\setupdirections[bidi=global,method=one]
\righttoleft
\ARABICFONT

خَ‍ % a

خَل

% \stopTEXpage
\stoptext
==

Three bugs:

I. If we use start|stoptex and comment start|stopTeXpage, then both  
lines 19 and 21 give an error:


===
tex error   > tex error on line 20 in file ./test.tex:

lua error:

	callback error: [string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: attempt to  
index a number value (local 'chainstep')

stack traceback:
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
function <[string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2514>

(...tail calls...)
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2065: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
local 'handler'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:3999: in  
field '?'
	...eXt/tex/texmf-context/tex/context/base/mkxl/node-fnt.lmt:459: in  
upvalue 'nodes_handlers_characters'
	[string "local tonut  = nodes.tonut..."]:23: in function <[string  
"local tonut  = nodes.tonut..."]:12>

(...tail calls...)  

10 \setupwhitespace[big]
11 % \setupinterlinespace[line=4.2ex]
12
13 \starttext
14 % \startTEXpage[offset=1ex]
15 \setupdirections[bidi=global,method=one]
16 \righttoleft
17 \ARABICFONT
18
19 خَ‍
20 >>
21 خَل
22
23 % \stopTEXpage
24 \stoptext
===

Comment line 19 and yu will get virtually the same error.

II. Using start|stopTeXpage, only line 21 gives the error:

===
tex error   > tex error on line 22 in file ./test.tex:

lua error:

	callback error: [string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: attempt to  
index a number value (local 'chainstep')

stack traceback:
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
function <[string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2514>

(...tail calls...)
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2065: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
local 'handler'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:3999: in  
field '?'
	...eXt/tex/texmf-context/tex/context/base/mkxl/node-fnt.lmt:459: in  
upvalue 'nodes_handlers_characters'
	[string "local tonut  = nodes.tonut..."]:23: in function <[string  
"local tonut  = nodes.tonut..."]:12>

(...tail calls...)  

12
13 % \starttext
14 \startTEXpage[offset=1ex]
15 \setupdirections[bidi=global,method=one]
16 \righttoleft
17 \ARABICFONT
18
19 خَ‍ % a
20
21 خَل
22 >>
23 \stopTEXpage
24 % \stoptext
===

III Let us switch to almfixed:

If you comment line 21 and use only line 19, then there is no tex error,  
but the result is rendered incorrectly - see test-broken.pdf.


For the correct result, see test-correct.pdf (add a space and any letter  
- uncomment the end of line 19).


Adobe Naskh is not publicly available. The four commented fonts are  
publicly available and generate no tex errors.


Best wishes
Idris



--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512
___
If your question is of interest to others as 

Re: [NTG-context] LMTX error processing Adobe Arabic Naskh font

[Idris Samawi Hamid ادريس سماوي حامد via ntg-context]

For III: See attached!

On Wed, 10 Nov 2021 09:00:26 -0700, Idris Samawi Hamid ادريس سماوي حامد  
 wrote:



Dear Hans and gang,

Consider the following MWE:

==
\definefont[ARABICFONT][file:Adobe_Naskh.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Amiri-Regular_0.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Scheherazade-Regular.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:UthmanTN1_Ver10.otf*arabic at 28pt]
% \definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]

\disabledirectives[filters.utf.reorder]
\noheaderandfooterlines

\setupwhitespace[big]
% \setupinterlinespace[line=4.2ex]

\starttext
% \startTEXpage[offset=1ex]
\setupdirections[bidi=global,method=one]
\righttoleft
\ARABICFONT

خَ‍ % a

خَل

% \stopTEXpage
\stoptext
==

Three bugs:

I. If we use start|stoptex and comment start|stopTeXpage, then both  
lines 19 and 21 give an error:


===
tex error   > tex error on line 20 in file ./test.tex:

lua error:

	callback error: [string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: attempt to  
index a number value (local 'chainstep')

stack traceback:
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
function <[string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2514>

(...tail calls...)
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2065: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
local 'handler'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:3999: in  
field '?'
	...eXt/tex/texmf-context/tex/context/base/mkxl/node-fnt.lmt:459: in  
upvalue 'nodes_handlers_characters'
	[string "local tonut  = nodes.tonut..."]:23: in function <[string  
"local tonut  = nodes.tonut..."]:12>

(...tail calls...)  

10 \setupwhitespace[big]
11 % \setupinterlinespace[line=4.2ex]
12
13 \starttext
14 % \startTEXpage[offset=1ex]
15 \setupdirections[bidi=global,method=one]
16 \righttoleft
17 \ARABICFONT
18
19 خَ‍
20 >>
21 خَل
22
23 % \stopTEXpage
24 \stoptext
===

Comment line 19 and yu will get virtually the same error.

II. Using start|stopTeXpage, only line 21 gives the error:

===
tex error   > tex error on line 22 in file ./test.tex:

lua error:

	callback error: [string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: attempt to  
index a number value (local 'chainstep')

stack traceback:
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
function <[string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2514>

(...tail calls...)
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2065: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
local 'handler'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:3999: in  
field '?'
	...eXt/tex/texmf-context/tex/context/base/mkxl/node-fnt.lmt:459: in  
upvalue 'nodes_handlers_characters'
	[string "local tonut  = nodes.tonut..."]:23: in function <[string  
"local tonut  = nodes.tonut..."]:12>

(...tail calls...)  

12
13 % \starttext
14 \startTEXpage[offset=1ex]
15 \setupdirections[bidi=global,method=one]
16 \righttoleft
17 \ARABICFONT
18
19 خَ‍ % a
20
21 خَل
22 >>
23 \stopTEXpage
24 % \stoptext
===

III Let us switch to almfixed:

If you comment line 21 and use only line 19, then there is no tex error,  
but the result is rendered incorrectly - see test-broken.pdf.


For the correct result, see test-correct.pdf (add a space and any letter  
- uncomment the end of line 19).


Adobe Naskh is not publicly available. The four commented fonts are  
publicly available and generate no tex errors.


Best wishes
Idris



--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512

test-broken.pdf
Description: Adobe PDF document


test-correct.pdf
Description: Adobe PDF document
___
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] LMTX error processing Adobe Arabic Naskh font

[Idris Samawi Hamid ادريس سماوي حامد via ntg-context]

Dear Hans and gang,

Consider the following MWE:

==
\definefont[ARABICFONT][file:Adobe_Naskh.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Amiri-Regular_0.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Scheherazade-Regular.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:UthmanTN1_Ver10.otf*arabic at 28pt]
% \definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]

\disabledirectives[filters.utf.reorder]
\noheaderandfooterlines

\setupwhitespace[big]
% \setupinterlinespace[line=4.2ex]

\starttext
% \startTEXpage[offset=1ex]
\setupdirections[bidi=global,method=one]
\righttoleft
\ARABICFONT

خَ‍ % a

خَل

% \stopTEXpage
\stoptext
==

Three bugs:

I. If we use start|stoptex and comment start|stopTeXpage, then both lines  
19 and 21 give an error:


===
tex error   > tex error on line 20 in file ./test.tex:

lua error:

	callback error: [string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: attempt to index  
a number value (local 'chainstep')

stack traceback:
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
function <[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2514>

(...tail calls...)
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2065: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
local 'handler'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:3999: in  
field '?'
	...eXt/tex/texmf-context/tex/context/base/mkxl/node-fnt.lmt:459: in  
upvalue 'nodes_handlers_characters'
	[string "local tonut  = nodes.tonut..."]:23: in function <[string "local  
tonut  = nodes.tonut..."]:12>

(...tail calls...)  

10 \setupwhitespace[big]
11 % \setupinterlinespace[line=4.2ex]
12
13 \starttext
14 % \startTEXpage[offset=1ex]
15 \setupdirections[bidi=global,method=one]
16 \righttoleft
17 \ARABICFONT
18
19 خَ‍
20 >>
21 خَل
22
23 % \stopTEXpage
24 \stoptext
===

Comment line 19 and yu will get virtually the same error.

II. Using start|stopTeXpage, only line 21 gives the error:

===
tex error   > tex error on line 22 in file ./test.tex:

lua error:

	callback error: [string  
"C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: attempt to index  
a number value (local 'chainstep')

stack traceback:
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2058: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
function <[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2514>

(...tail calls...)
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2065: in  
upvalue 'chainrun'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:2941: in  
local 'handler'
	[string "C:/ConTeXt/tex/texmf-context/tex/context/base..."]:3999: in  
field '?'
	...eXt/tex/texmf-context/tex/context/base/mkxl/node-fnt.lmt:459: in  
upvalue 'nodes_handlers_characters'
	[string "local tonut  = nodes.tonut..."]:23: in function <[string "local  
tonut  = nodes.tonut..."]:12>

(...tail calls...)  

12
13 % \starttext
14 \startTEXpage[offset=1ex]
15 \setupdirections[bidi=global,method=one]
16 \righttoleft
17 \ARABICFONT
18
19 خَ‍ % a
20
21 خَل
22 >>
23 \stopTEXpage
24 % \stoptext
===

III Let us switch to almfixed:

If you comment line 21 and use only line 19, then there is no tex error,  
but the result is rendered incorrectly - see test-broken.pdf.


For the correct result, see test-correct.pdf (add a space and any letter -  
uncomment the end of line 19).


Adobe Naskh is not publicly available. The four commented fonts are  
publicly available and generate no tex errors.


Best wishes
Idris
--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512
___
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] [lmtx offline?]

[Hans Hagen via ntg-context]

On 9/20/2021 12:34 PM, Floris van Manen via ntg-context wrote:
I try to update my lmtx installation, but it seems that there is no 
contact with the server somehow...

Any hints?
Because our provider stops with web stuff we are in transition. You can 
try again (there was a redirect to https that spoiled the installer).


(Because the provider also ditched all our email adresses and it took a 
while to fix that there can be lost mails.)


Hopefully things are stable after a while (the com address is still in 
transition so that can get temporarily off line but the nl fallbacks 
should work ok.)


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] [lmtx offline?]

[Henning Hraban Ramm via ntg-context]

The server is on its way to the context meeting and got no wifi on the train ;)

HR

PS: nonsense, of course

> Am 20.09.2021 um 12:34 schrieb Floris van Manen via ntg-context 
> :
> 
> I try to update my lmtx installation, but it seems that there is no contact 
> with the server somehow...
> Any hints?
> 
> 
> 
> $ ./install.sh
> mtx-install | provide valid server and instance
> 
> 
> The following settings were used:
> 
>  server   : lmtx.contextgarden.net,lmtx.pragma-ade.com,lmtx.pragma-ade.nl
>  instance : install-lmtx
>  extras   :
>  ownpath  : /home/vm/context
>  platform : linux-64
> 
> 
> ___
> 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
___

[NTG-context] [lmtx offline?]

[Floris van Manen via ntg-context]

I try to update my lmtx installation, but it seems that there is no 
contact with the server somehow...

Any hints?



$ ./install.sh
mtx-install | provide valid server and instance


The following settings were used:

  server   : lmtx.contextgarden.net,lmtx.pragma-ade.com,lmtx.pragma-ade.nl
  instance : install-lmtx
  extras   :
  ownpath  : /home/vm/context
  platform : linux-64


___
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] lmtx update/t-vim (again)

[Aditya Mahajan via ntg-context]

On Mon, 23 Aug 2021, Aditya Mahajan via ntg-context wrote:

> On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
> 
> > This is the setup I have been using, but I'm unsure if the problem could be 
> > related to the other problem I had. (Not scaled to a MWE, but short 
> > enough.) I figured the issue by removing some of the lines.
> 
> I get the same error. Most likely due to some grouping issue because there is 
> also this:
> 
> system  > invalid \starttext ... \stoptext structure
> 
> I'll look into it.

The error was due to the change in job.files.run macro. I have adapted the 
t-filter module to use the new interface. So, the error should go away if you 
update your installed modules.

Thanks for the bug report.

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] lmtx update/t-vim (again)

[Hans Hagen via ntg-context]

On 8/23/2021 7:42 PM, Aditya Mahajan wrote:

On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:


This is the setup I have been using, but I'm unsure if the problem could be 
related to the other problem I had. (Not scaled to a MWE, but short enough.) I 
figured the issue by removing some of the lines.


I get the same error. Most likely due to some grouping issue because there is 
also this:

system  > invalid \starttext ... \stoptext structure

I'll look into it.

Hopefully I didn't mess up something.

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] lmtx update/t-vim (again)

[Aditya Mahajan via ntg-context]

On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:

> This is the setup I have been using, but I'm unsure if the problem could be 
> related to the other problem I had. (Not scaled to a MWE, but short enough.) 
> I figured the issue by removing some of the lines.

I get the same error. Most likely due to some grouping issue because there is 
also this:

system  > invalid \starttext ... \stoptext structure

I'll look into it.

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] lmtx update/t-vim (again)

[Benjamin Buchmuller via ntg-context]

This is the setup I have been using, but I'm unsure if the problem could be 
related to the other problem I had. (Not scaled to a MWE, but short enough.) I 
figured the issue by removing some of the lines.

\usemodule[vim]

\definetextbackground[codebkg]
[
frame=on, 
framecolor=black,
background=,
location=paragraph,
]

\definevimtyping[vimR]
[
syntax=r,
space=off,
lines=split,
numbering=yes,
numberstep=5,
alternative=pscolor,
margin=.5em,
style={\switchtobodyfont[type,small]\setupinterlinespace},
before={\blank[white,small]\startcodebkg},  % a bit of extra space 
after={\stopcodebkg},
directory=vimout/,  % note: you must create this folder yourself!
]

\starttext

\startvimR
#!/usr/bin/env R
included_aa <- list(
  `6d1t` = 2:81,
  `6cnq` = 146:225,
  `6ccg` = 2:81,
  `4lg7` = 76:167,
  `3c2i` = 90:181) %>% enframe() %>% unnest(cols = "value") %>% 
  rename(protein = "name", aa_pos = "value") %>%
  mutate(chain = "A") %>% mutate(include_aa = TRUE)
\stopvimR

\stoptext

So, the first "i", "n" etc. come from "include_aa" after I remove the shebang 
statement. 

The lines with "#" and "$" (in other pieces not shown) cause the complaints.

I also realized that I get output for each vim block, but instead of a 
"vimout", I get a "pdf" (error) and a "log" (some attached) now.

Also, the blocks get recompiled with each run even if their content doesn't 
change which was the previous behavior.




xxx-temp-vimR-0-error.log
Description: Binary data


xxx-temp-vimR-0.log
Description: Binary data


xxx-temp-vimR-1.log
Description: Binary data


> On Aug 23, 2021, at 08:19, Hans Hagen  wrote:
> 
> On 8/23/2021 12:10 AM, Benjamin Buchmuller via ntg-context wrote:
>> Hi,
>> Thanks for having had a look into the t-vim.
>> At least the document compiles fine (I get a PDF), although multiple 
>> complaints from the lua end when I use "$" or "#" in my source, for example
>> #!/usr/bin/bash
>> etc. culminating in
>> Sorry, but I'm not programmed to handle this case;
>> I'll just pretend that you didn''t ask for it.
>> If you're in the wrong mode, you might be able to
>> return to the right one by typing 'I}' or 'I$' or 'I\par'.
>> Seems as if LMTX tried to interpret something literally here …
>> Further, I get a lot of
>> fonts   > beware: no fonts are loaded yet, using 'lm mono' in box
>> fonts   > checking > char i (U+00069) in font '' with id 0: missing
>> fonts   > checking > char n (U+0006E) in font '' with id 0: missing
>> warnings. Maybe some things need to be adjusted?
> THis normally means that you have someting before the \starttext that gets 
> typeset (here the word "in")
> 
> 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] lmtx update

[Hans Hagen via ntg-context]

On 8/23/2021 12:55 AM, Benjamin Buchmuller via ntg-context wrote:

Hi,

Here is another thing which worked previously for me:

ConTeXt  ver: 2021.07.30 00:57 LMTX  fmt: 2021.8.8  int: english/english

Now:

ConTeXt  ver: 2021.08.22 11:54 LMTX  fmt: 2021.8.22  int: english/english

Error:

lua error:

registered function call [396]: 
...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: attempt to 
call a nil value (upvalue 'texgetparstate')
stack traceback:
...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: in function 
<...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1262>
(...tail calls...)  

129 \NC \unit{0.88 angstrom}
130 \NC \unit{2.02 angstrom}
131 \NC \unit{2.03 angstrom}
132 \NC \unit{1.90 angstrom}
133 \NC \unit{4.99 angstrom} % rmsd #1/a:14-61 & backbone to 
#5/a:103-150 & backbone
134 \NC \unit{1.88 angstrom}
135 \NC \unit{5.20 angstrom} % rmsd #1/a:46-55 & backbone to 
#5/a:135-144 & backbone
136 \NC \NR
137 \HL
138 \stoptabulate

The difficulty here is that when I copy the "faulty" part (my table) to another 
document (including all relevant defs etc.) it just works fine. So, I think it must have 
to do something with the placement of the float on the page.

Any hints what has changed?
your luametatex binary seems older than in the lmtx distribution .. what 
platform?


-
  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] lmtx update/t-vim (again)

[Hans Hagen via ntg-context]

On 8/23/2021 12:10 AM, Benjamin Buchmuller via ntg-context wrote:

Hi,

Thanks for having had a look into the t-vim.

At least the document compiles fine (I get a PDF), although multiple complaints from the lua end 
when I use "$" or "#" in my source, for example

#!/usr/bin/bash

etc. culminating in

Sorry, but I'm not programmed to handle this case;
I'll just pretend that you didn''t ask for it.
If you're in the wrong mode, you might be able to
return to the right one by typing 'I}' or 'I$' or 'I\par'.

Seems as if LMTX tried to interpret something literally here …

Further, I get a lot of

fonts   > beware: no fonts are loaded yet, using 'lm mono' in box
fonts   > checking > char i (U+00069) in font '' with id 0: missing
fonts   > checking > char n (U+0006E) in font '' with id 0: missing

warnings. Maybe some things need to be adjusted?
THis normally means that you have someting before the \starttext that 
gets typeset (here the word "in")


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] lmtx update

[Benjamin Buchmuller via ntg-context]

Hi,

Here is another thing which worked previously for me:

ConTeXt  ver: 2021.07.30 00:57 LMTX  fmt: 2021.8.8  int: english/english

Now:

ConTeXt  ver: 2021.08.22 11:54 LMTX  fmt: 2021.8.22  int: english/english

Error:

lua error:

registered function call [396]: 
...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: attempt to 
call a nil value (upvalue 'texgetparstate')
stack traceback:
...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: in 
function <...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1262>
(...tail calls...)  

129 \NC \unit{0.88 angstrom}
130 \NC \unit{2.02 angstrom}
131 \NC \unit{2.03 angstrom}
132 \NC \unit{1.90 angstrom}
133 \NC \unit{4.99 angstrom} % rmsd #1/a:14-61 & backbone to 
#5/a:103-150 & backbone
134 \NC \unit{1.88 angstrom}
135 \NC \unit{5.20 angstrom} % rmsd #1/a:46-55 & backbone to 
#5/a:135-144 & backbone
136 \NC \NR
137 \HL
138 \stoptabulate

The difficulty here is that when I copy the "faulty" part (my table) to another 
document (including all relevant defs etc.) it just works fine. So, I think it 
must have to do something with the placement of the float on the page. 

Any hints what has changed?

Thanks!


Benjamin

> On Aug 20, 2021, at 12:00, ntg-context-requ...@ntg.nl wrote:
> 
> lmtx update

___
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] lmtx update/t-vim (again)

[Wolfgang Schuster via ntg-context]

Benjamin Buchmuller via ntg-context schrieb am 23.08.2021 um 00:10:

Hi,

Thanks for having had a look into the t-vim.

At least the document compiles fine (I get a PDF), although multiple complaints from the lua end 
when I use "$" or "#" in my source, for example

#!/usr/bin/bash

etc. culminating in

Sorry, but I'm not programmed to handle this case;
I'll just pretend that you didn''t ask for it.
If you're in the wrong mode, you might be able to
return to the right one by typing 'I}' or 'I$' or 'I\par'.

Seems as if LMTX tried to interpret something literally here …

Further, I get a lot of

fonts   > beware: no fonts are loaded yet, using 'lm mono' in box
fonts   > checking > char i (U+00069) in font '' with id 0: missing
fonts   > checking > char n (U+0006E) in font '' with id 0: missing

warnings. Maybe some things need to be adjusted?

(Second mail with another error in LMTX follows.)


Can you provide a minimal working (or in your case not working) example 
for the problem.


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
___

[NTG-context] lmtx update/t-vim (again)

[Benjamin Buchmuller via ntg-context]

Hi,

Thanks for having had a look into the t-vim. 

At least the document compiles fine (I get a PDF), although multiple complaints 
from the lua end when I use "$" or "#" in my source, for example 

#!/usr/bin/bash 

etc. culminating in

Sorry, but I'm not programmed to handle this case;
I'll just pretend that you didn''t ask for it.
If you're in the wrong mode, you might be able to
return to the right one by typing 'I}' or 'I$' or 'I\par'.

Seems as if LMTX tried to interpret something literally here …

Further, I get a lot of 

fonts   > beware: no fonts are loaded yet, using 'lm mono' in box
fonts   > checking > char i (U+00069) in font '' with id 0: missing
fonts   > checking > char n (U+0006E) in font '' with id 0: missing

warnings. Maybe some things need to be adjusted?

(Second mail with another error in LMTX follows.)

Cheers


Benjamin

> On Aug 20, 2021, at 12:00, ntg-context-requ...@ntg.nl wrote:
> 
> Hi,
> 
> Here are the highlights of todays update:
> 
> - somewhat more compact tuc files, not for all documents, but it can 
> accumulate; also less memory used then; i could bring down an extreme 2000 
> page 5 column doc tuc file down to 5% -- it was 70 MB; for the luametatex 
> manual it reducec the tuc more than 30%; hard to tell if there will be an 
> associated performance hit, but i'm sure thomas will complain if that's the 
> case
> 
> - more mp-tex-lua interfacing upgraded plus extra preliminary chapter for 
> luametafun about extensions - for taco
> 
> - a slightly more compact cache files for fonts with many (pseudo) ligatures; 
> hopefully no side effects (nothing that can't be fixed fast if noted); quite 
> probably no performance hit and maybe even some room for optimization (not 
> done yet)
> 
> - a split in the cache directory for luametatex so that we can more easilly 
> experiment without interference (so, although the above works in mkiv it's 
> not enabled there currently)
> 
> - some minor things (also in the process of splitting the codebase)
> 
> - no real changes in / additions to the luametatex binary (we're in cosmetics 
> mode now)
> 
> 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] lmtx update

[Hans Hagen via ntg-context]

On 8/19/2021 10:07 PM, Aditya Mahajan via ntg-context wrote:

On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:


Hi,

Here are the highlights of todays update:

- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc more than 30%; hard to tell if
there will be an associated performance hit, but i'm sure thomas will
complain if that's the case


I never realized that tuc files can grow so big. For big documents, would it 
make sense to simply read and write zipped tuc files?
normally they are not that large but when you enable for instance 
mechanisms that need positioning they can grow large .. zipping makes 
for less bytes but still large files and the overhead for serialization 
stays


(to some extend trying to make these things small is like compression 
but in a different way .. could be a nice topic for a ctx meeting)


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] lmtx update

[Aditya Mahajan via ntg-context]

On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:

> Hi,
> 
> Here are the highlights of todays update:
> 
> - somewhat more compact tuc files, not for all documents, but it can 
> accumulate; also less memory used then; i could bring down an extreme 
> 2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the 
> luametatex manual it reducec the tuc more than 30%; hard to tell if 
> there will be an associated performance hit, but i'm sure thomas will 
> complain if that's the case

I never realized that tuc files can grow so big. For big documents, would it 
make sense to simply read and write zipped tuc files?

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
___

[NTG-context] lmtx update

[Hans Hagen via ntg-context]

Hi,

Here are the highlights of todays update:

- somewhat more compact tuc files, not for all documents, but it can 
accumulate; also less memory used then; i could bring down an extreme 
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the 
luametatex manual it reducec the tuc more than 30%; hard to tell if 
there will be an associated performance hit, but i'm sure thomas will 
complain if that's the case


- more mp-tex-lua interfacing upgraded plus extra preliminary chapter 
for luametafun about extensions - for taco


- a slightly more compact cache files for fonts with many (pseudo) 
ligatures; hopefully no side effects (nothing that can't be fixed fast 
if noted); quite probably no performance hit and maybe even some room 
for optimization (not done yet)


- a split in the cache directory for luametatex so that we can more 
easilly experiment without interference (so, although the above works in 
mkiv it's not enabled there currently)


- some minor things (also in the process of splitting the codebase)

- no real changes in / additions to the luametatex binary (we're in 
cosmetics mode now)


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] LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts

[Hans Hagen via ntg-context]

On 7/28/2021 1:45 PM, Henning Hraban Ramm via ntg-context wrote:



Am 28.07.2021 um 11:46 schrieb Hans Hagen :

On 7/28/2021 10:31 AM, Henning Hraban Ramm via ntg-context wrote:

Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context :

On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:

Hello.
I'm trying to get LMTX to use my fonts on Fedora 33 Linux.  I've got LMTX 
installed in the directory /sw/versions/context/lmtx and I've put copies of the 
fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts.  Some of 
them are truetype and some of them are opentype.  When I run
mtxrun --script fonts --reload --force
it says
fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for otf files
fonts   | names | 0 otf files checked,  okay
and later
fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files
fonts   | names | 0 ttf files checked,  okay
Any ideas of what I'm doing wrong?


did you add the /fonts subpath?

  /sw/versions/context/lmtx/tex/texmf-fonts/fonts/data

i normally put them in

   data/whatever/whataverer*.otf

(data is kind of generic, there is no need to distinguish between various font 
types)

When I added your “Lost in fonts” article to the CGJ, I did exactly that with 
the included TYFA* fonts.
They were not recognized in the same folder as the article or in 
texmf-fonts/fonts/data/tyfa, even after several force reloads; they were only 
found when I added them to the system font directory (~/Library/Fonts on MacOS).

did you also do mtxrun --generate beforehand?


I didn’t because that’s part of the install script, isn’t it? I run that more 
or less daily.

But it doesn’t change anything – deleted the fonts from Library, they’re still in 
texmf-fonts, --generate, --reload --force => fonts not found.

Since my texmf-fonts is a symlink (to avoid the same tree in several 
installations), I also checked if a “real” directory solves the problem – no.


No clue ... maybe --verbose helps ... i assume that mtxrun --generate 
shows the path being seen.


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] LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts

[Henning Hraban Ramm via ntg-context]

> Am 28.07.2021 um 11:46 schrieb Hans Hagen :
> 
> On 7/28/2021 10:31 AM, Henning Hraban Ramm via ntg-context wrote:
>>> Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context 
>>> :
>>> 
>>> On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:
 Hello.
 I'm trying to get LMTX to use my fonts on Fedora 33 Linux.  I've got LMTX 
 installed in the directory /sw/versions/context/lmtx and I've put copies 
 of the fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts. 
  Some of them are truetype and some of them are opentype.  When I run
mtxrun --script fonts --reload --force
 it says
fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for otf files
fonts   | names | 0 otf files checked,  okay
 and later
fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files
fonts   | names | 0 ttf files checked,  okay
 Any ideas of what I'm doing wrong?
>>> 
>>> did you add the /fonts subpath?
>>> 
>>>  /sw/versions/context/lmtx/tex/texmf-fonts/fonts/data
>>> 
>>> i normally put them in
>>> 
>>>   data/whatever/whataverer*.otf
>>> 
>>> (data is kind of generic, there is no need to distinguish between various 
>>> font types)
>> When I added your “Lost in fonts” article to the CGJ, I did exactly that 
>> with the included TYFA* fonts.
>> They were not recognized in the same folder as the article or in 
>> texmf-fonts/fonts/data/tyfa, even after several force reloads; they were 
>> only found when I added them to the system font directory (~/Library/Fonts 
>> on MacOS).
> did you also do mtxrun --generate beforehand?

I didn’t because that’s part of the install script, isn’t it? I run that more 
or less daily.

But it doesn’t change anything – deleted the fonts from Library, they’re still 
in texmf-fonts, --generate, --reload --force => fonts not found.

Since my texmf-fonts is a symlink (to avoid the same tree in several 
installations), I also checked if a “real” directory solves the problem – no.

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] LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts

[Hans Hagen via ntg-context]

On 7/28/2021 10:31 AM, Henning Hraban Ramm via ntg-context wrote:



Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context :

On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:

Hello.
I'm trying to get LMTX to use my fonts on Fedora 33 Linux.  I've got LMTX 
installed in the directory /sw/versions/context/lmtx and I've put copies of the 
fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts.  Some of 
them are truetype and some of them are opentype.  When I run
mtxrun --script fonts --reload --force
it says
fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for otf files
fonts   | names | 0 otf files checked,  okay
and later
fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files
fonts   | names | 0 ttf files checked,  okay
Any ideas of what I'm doing wrong?


did you add the /fonts subpath?

  /sw/versions/context/lmtx/tex/texmf-fonts/fonts/data

i normally put them in

   data/whatever/whataverer*.otf

(data is kind of generic, there is no need to distinguish between various font 
types)


When I added your “Lost in fonts” article to the CGJ, I did exactly that with 
the included TYFA* fonts.
They were not recognized in the same folder as the article or in 
texmf-fonts/fonts/data/tyfa, even after several force reloads; they were only 
found when I added them to the system font directory (~/Library/Fonts on MacOS).

did you also do mtxrun --generate beforehand?

-
  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] LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts

[Henning Hraban Ramm via ntg-context]

> Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context 
> :
> 
> On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:
>> Hello.
>> I'm trying to get LMTX to use my fonts on Fedora 33 Linux.  I've got LMTX 
>> installed in the directory /sw/versions/context/lmtx and I've put copies of 
>> the fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts.  
>> Some of them are truetype and some of them are opentype.  When I run
>>mtxrun --script fonts --reload --force
>> it says
>>fonts   | names | scanning path
>>'/sw/versions/context/lmtx/tex/texmf-fonts' for otf files
>>fonts   | names | 0 otf files checked,  okay
>> and later
>>fonts   | names | scanning path
>>'/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files
>>fonts   | names | 0 ttf files checked,  okay
>> Any ideas of what I'm doing wrong?
> 
> did you add the /fonts subpath?
> 
>  /sw/versions/context/lmtx/tex/texmf-fonts/fonts/data
> 
> i normally put them in
> 
>   data/whatever/whataverer*.otf
> 
> (data is kind of generic, there is no need to distinguish between various 
> font types)

When I added your “Lost in fonts” article to the CGJ, I did exactly that with 
the included TYFA* fonts.
They were not recognized in the same folder as the article or in 
texmf-fonts/fonts/data/tyfa, even after several force reloads; they were only 
found when I added them to the system font directory (~/Library/Fonts on MacOS).

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] LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts

[Hans Hagen via ntg-context]

On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:

Hello.

I'm trying to get LMTX to use my fonts on Fedora 33 Linux.  I've got 
LMTX installed in the directory /sw/versions/context/lmtx and I've put 
copies of the fonts I'd like to use in 
/sw/versions/context/lmtx/tex/texmf-fonts.  Some of them are truetype 
and some of them are opentype.  When I run


mtxrun --script fonts --reload --force

it says

fonts           | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for otf files
fonts           | names | 0 otf files checked,  okay

and later

fonts           | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files
fonts           | names | 0 ttf files checked,  okay


Any ideas of what I'm doing wrong?


did you add the /fonts subpath?

  /sw/versions/context/lmtx/tex/texmf-fonts/fonts/data

i normally put them in

   data/whatever/whataverer*.otf

(data is kind of generic, there is no need to distinguish between 
various font types)


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] LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts

[T. Kurt Bond via ntg-context]

Hello.

I'm trying to get LMTX to use my fonts on Fedora 33 Linux.  I've got LMTX
installed in the directory /sw/versions/context/lmtx and I've put copies of
the fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts.
Some of them are truetype and some of them are opentype.  When I run

mtxrun --script fonts --reload --force

it says

fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for otf files
fonts   | names | 0 otf files checked,  okay

and later

fonts   | names | scanning path
'/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files
fonts   | names | 0 ttf files checked,  okay


Any ideas of what I'm doing wrong?
-- 
T. Kurt Bond, tkurtb...@gmail.com, https://tkurtbond.github.io
___
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] LMTX: some alignment issues

[Gerben Wierda]

[still working to somewhat reproduce my old mkii setup in LMTX]

The following is a minimal example that shows the following:
context test2.tex results in
The first line after the initials not as much indented as it should be
Character protrusion in a footnote does not work (see “refer-“ at the end of 
the 5th line of the footnote) (I understand the trouble on the first line
context --mode=OPTIMA test2.tex results in
The first line after the initials not as much indented as it should be
"because” is not hyphenated. Note, I see this is a smaller font setup where 
there is clearly an option to hyphenate, the minimum example shows the same 
effect, but potentially not from the same cause)
Character protrusion in a footnote does not work
context --mode=OPTIMANOVA test2.tex results in
The first line after the initials not as much indented as it should be
Multiple instances of extending beyond the right
Character protrusion in a footnote does not work
Adding \setupalign[hanging,hz] to the Optima Nova example results in ‘because’ 
on the first line to be hyphenated as ‘be-cause’ and pigeonhole in a later line 
as 'pi-geonhole'. 

I am adding a screen shot of part of the Optima Nova result as most will not 
have that font available:



- All show no protrusion in the footnotes
- All show a problem with the first line after the initial
- When using Optima Nova, hyphenation isn’t used while the situation in Optima 
looks nearly identical.

MVP source:

%%%
\definepapersize[smallpaperback][width=5in,height=8in]
\setuppapersize[smallpaperback][smallpaperback]
\setuplayout[location=doublesided]
\setuppagenumbering[alternative=doublesided]
\setupsectionblock[frontpart][page=no]
\setupsectionblock[bodypart][page=no]
\setupsectionblock[appendix][page=no]
\setupsectionblock[backpart][page=no]

\definefontfeature
  [default]
  [default]
  [protrusion=quality,expansion=quality]

\setupbodyfont[default,11pt]
\startmode[OPTIMANOVA]
\definefontfamily
[bookfont]
[ss]
[Optima nova LT Pro]
[tf=style:Regular,
bf=style:Medium,
it=style:Italic,
bi=style:Medium Italic]
\setupbodyfont[bookfont,11pt]
\stopmode
\startmode[OPTIMA]
\definefontfamily
[bookfont]
[ss]
[Optima]
[tf=style:Regular,
bf=style:Bold,
it=style:Italic,
bi=style:Bold Italic]
\setupbodyfont[bookfont,11pt]
\stopmode
\setupalign[hanging] % only protrusion

\showframe

\starttext
\setupindenting[next]
\placeinitial \input tufte

Test footnote\footnote{If you are not technical and terms like
`application server',
`caught exceptions', or `web proxy' in the fragment that follows, do not
immediately get you started, do not worry: there is no need to know what
I am
talking about here in a technical sense. You can read this without
understanding any of the technical references. Just skip over them, their
specifics are not important to the story. They are real enough, though.  You
can trust me on that, or ask your engineers.}
\stoptext
%%%

Gerben Wierda (LinkedIn )
R Enterprise Architecture  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

___
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] LMTX and lettrine

[Wolfgang Schuster]

Pablo Rodriguez schrieb am 18.07.2021 um 18:16:

On 7/18/21 3:35 PM, Gerben Wierda wrote:

I am trying to find out how to move this setup in mkii

23     \usemodule[lettrine]
24 >>  \setuplettrine[Lines=3,
25                    Hang=.5,
26                    Oversize=0,
27                    Raise=0,
28                    Findent=0pt,
29                    Nindent=0em,
30                    Slope=0em,
31                    Ante=,
32                    FontHook=,
33                    TextFont=\sc,
34                    Image=no]

to lmtx. (Basically, ConTeXtgarden gives my mike info for lettrine)

Hi Gerben,

\setupinitial is your friend.

i-context.pdf (included in LMTX) contains the available options
(searching for "\setupinitial [", without quotation marks).


Both commands have different feature sets, e.g. with lettrine you can use
a image for the initial and you can also use the slope option to change the
indentation for letters like A or V.

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] LMTX and lettrine

[Pablo Rodriguez]

On 7/18/21 3:35 PM, Gerben Wierda wrote:
> I am trying to find out how to move this setup in mkii
>
> 23     \usemodule[lettrine]
> 24 >>  \setuplettrine[Lines=3,
> 25                    Hang=.5,
> 26                    Oversize=0,
> 27                    Raise=0,
> 28                    Findent=0pt,
> 29                    Nindent=0em,
> 30                    Slope=0em,
> 31                    Ante=,
> 32                    FontHook=,
> 33                    TextFont=\sc,
> 34                    Image=no]
>
> to lmtx. (Basically, ConTeXtgarden gives my mike info for lettrine)

Hi Gerben,

\setupinitial is your friend.

i-context.pdf (included in LMTX) contains the available options
(searching for "\setupinitial [", without quotation marks).

I hope it helps,

Pablo
--
http://www.ousia.tk
___
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] LMTX and lettrine

[Gerben Wierda]

I am trying to find out how to move this setup in mkii

23 \usemodule[lettrine]
24 >>  \setuplettrine[Lines=3,
25Hang=.5,
26Oversize=0,
27Raise=0,
28Findent=0pt,
29Nindent=0em,
30Slope=0em,
31Ante=,
32FontHook=,
33TextFont=\sc,
34Image=no]

to lmtx. (Basically, ConTeXtgarden gives my mike info for lettrine)

Gerben Wierda (LinkedIn )
R Enterprise Architecture  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

___
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] lmtx install problem

[Henning Hraban Ramm]

> Am 14.07.2021 um 20:26 schrieb jdh :
> 
> 
> I've downloaded and ran the install...sh script from the directory:  
> /opt/context-lmtx

Is this on Linux?

> It indicates that it completed successully, but there is no 'tex' directory 
> anywhere in the resulting /opt/context-lmtxdirectory tree.

But there is a tree? How does it look?
(If your system has the 'tree' command, try 'tree -dL 3'.)

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
___