follow up

follow up

[Hans Hagen]

Hi,

We have worked furiously all day kicking-out extra code, and are pleased 
to present a lean-and-mean version of luatex with your favorite ConTeXt. 
Same good taste but only half the calories and a new name: luametatex 
and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
now stand on our own. Of course, good-old luatex and MkIV (as well as 
MkII) will continue to coexist and be maintained. However, now you will 
be able to run ConTeXt lmtx on your smart thermostat or on your 
refrigerator for the Internet of Things - the dawn of a new era!

Stay tuned,

Alan and 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: follow up

[Floris van Manen]

[-- Attachment #1.1: Type: text/plain, Size: 660 bytes --]

H.

> We have worked furiously all day kicking-out extra code, and are pleased to present a lean-and-mean version of luatex with your favorite ConTeXt. Same good taste but only half the calories and a new name: luametatex and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can now stand on our own. Of course, good-old luatex and MkIV (as well as MkII) will continue to coexist and be maintained. However, now you will be able to run ConTeXt lmtx on your smart thermostat or on your refrigerator for the Internet of Things - the dawn of a new era!

That sound like a very good thing indeed !
Is it available for download already?

.F


[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Mojca Miklavec]

On Mon, 1 Apr 2019 at 15:19, Floris van Manen wrote:
>
> H.
>
> > We have worked furiously all day kicking-out extra code, and are pleased to present a lean-and-mean version of luatex with your favorite ConTeXt. Same good taste but only half the calories and a new name: luametatex and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can now stand on our own. Of course, good-old luatex and MkIV (as well as MkII) will continue to coexist and be maintained. However, now you will be able to run ConTeXt lmtx on your smart thermostat or on your refrigerator for the Internet of Things - the dawn of a new era!
>
> That sound like a very good thing indeed !
> Is it available for download already?

I would have already published the link on the server in Slovenia, but
it seems that there was a bug on the thermostat in the server room (I
was apparently too exhausted yesterday to properly test before I fell
in bed) which lead to some hardware failures. You'll probably need to
wait for another server to be set up. I hope the delay won't be too
long. (I'm really sorry for the inconvenience.)

Mojca
___________________________________________________________________________________
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: follow up

[Henning Hraban Ramm]

Am 2019-04-01 um 14:56 schrieb Hans Hagen <j.hagen@xs4all.nl>:

> We have worked furiously all day kicking-out extra code, and are pleased to present a lean-and-mean version of luatex with your favorite ConTeXt. Same good taste but only half the calories and a new name: luametatex and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can now stand on our own. Of course, good-old luatex and MkIV (as well as MkII) will continue to coexist and be maintained. However, now you will be able to run ConTeXt lmtx on your smart thermostat or on your refrigerator for the Internet of Things - the dawn of a new era!

I hacked into Hans’ home automation server via the SpiritInTheSky interface of my dead badger, running Vüdü Linux 6.66, and borrowed the latest omega version. I thought I got it to run, but now the badger is moonstruck and my documents are full of moon phase symbols and fnords. I wouldn’t recommend to try this early version without vaccinating your hardware first. I guess it’s just too meta.


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___________________________________________________________________________________
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: follow up

[Aditya Mahajan]

On Mon, 1 Apr 2019, Hans Hagen wrote:

> Hi,
>
> We have worked furiously all day kicking-out extra code, and are pleased 
> to present a lean-and-mean version of luatex with your favorite ConTeXt. 
> Same good taste but only half the calories and a new name: luametatex 
> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
> now stand on our own. Of course, good-old luatex and MkIV (as well as 
> MkII) will continue to coexist and be maintained. However, now you will 
> be able to run ConTeXt lmtx on your smart thermostat or on your 
> refrigerator for the Internet of Things - the dawn of a new era!

I get an error when using pgfplots:

\usemodule[pgfplots]

\starttext
Hello
\stoptext

gives

tex error       > tex error on line 1 in file 
/opt/luametatex/tex/texmf-modules/tex/generic/pgf/libraries/decorations/pgflibrarydecorations.pathreplacing.code.tex: 
! Undefined control sequence

<write> ... set (\string \pgfplotsset {compat=\mostrecent
                                                   }).

The error is coming from the following code in 
pgfplotssysgeneric.code.tex:


    \pgfplots@message{Package pgfplots notification 'compat/show suggested 
version=true': document has been generated with the most recent feature 
set (\string\pgfplotsset{compat=\mostrecent}).^^J}%

where \pgfplot@message is defined as:

\def\pgfplots@message#1{%
  \immediate\write16{#1}%
}%

To me, it seems like an error in pgfplots (I think that instead of 
\mostrecent, the error message should use 
`\pgfkeysvalueof{/pgfplots/compat/mostrecent}`) and is easily fixable by 
setting `\let\mostrecent=\relax` before loading pgfplots.

What is interesting is that for some reason the error message does not 
show up in ConTeXt MkIV. I couldn't make a minimal example to show the 
difference between the two.

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: follow up

[Hans Hagen]

On 4/2/2019 5:56 PM, Aditya Mahajan wrote:

> To me, it seems like an error in pgfplots (I think that instead of 
> \mostrecent, the error message should use 
> `\pgfkeysvalueof{/pgfplots/compat/mostrecent}`) and is easily fixable by 
> setting `\let\mostrecent=\relax` before loading pgfplots.

if i grep the pgf path then indeed there are files with forward slashes 
and in few plaes with backslashes

> What is interesting is that for some reason the error message does not 
> show up in ConTeXt MkIV. I couldn't make a minimal example to show the 
> difference between the two.
maybe a different file is loaded based on some check ... hard to see 
with so many files loaded

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: follow up

[Jeong Dal]

[-- Attachment #1.1: Type: text/plain, Size: 1490 bytes --]

Dear Otared,

I checked the both cases in the terminal and found that there is no problem in the installation.
It call “mtxrun" in right place depending on MKIV or LMTX.

Actually, files which doesn’t need  files in texmf-local folder are compiled well in both installations.
The problem is occurred when the file tried to read files in texmf-local folder. 
In that case, if it is compiled well in MKIV, then it had a problem in LMTX and vice versa.
I didn’t try to use a symbolic link.

Since I don’t have any problem to compile files under LMTX so far, I will use LMTX mainly.
So I’ll left my previous problem for a while.

Thank you for your help.

Best regards,
Dalyoung



> Subject: Re: [NTG-context] follow up
> Message-ID: <F894514C-8E72-4743-B05D-B438EFE4F332@gmail.com <mailto:F894514C-8E72-4743-B05D-B438EFE4F332@gmail.com>>
> Content-Type: text/plain; charset="utf-8"
> 
> Dear Dalyoung,
> 
> Actually when you have added 
> 
> 	export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
> 
> either in your engine file (using TeXShop), or when typesetting from the Terminal, then you don't need to use mtxrun --autogenerate in order to typeset a file with LuaMetaTeX: you can just have
> 
> 	/context-osx-64/tex/texmf-osx-64/bin/context myfile.tex
> 
> in this way you can use any mode you wish.
> 
> Or have I misunderstood the issue you are asking about?
> 
> Best regards: OK


[-- Attachment #1.2: Type: text/html, Size: 14019 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Otared Kavian]

[-- Attachment #1.1: Type: text/plain, Size: 12129 bytes --]

Dear Dalyoung,

Actually when you have added 

	export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin

either in your engine file (using TeXShop), or when typesetting from the Terminal, then you don't need to use mtxrun --autogenerate in order to typeset a file with LuaMetaTeX: you can just have

	/context-osx-64/tex/texmf-osx-64/bin/context myfile.tex

in this way you can use any mode you wish.

Or have I misunderstood the issue you are asking about?

Best regards: OK

> On 5 Apr 2019, at 16:30, Jeong Dal <haksan@me.com> wrote:
> 
> 
> Dear Hans and Otared,
> 
> Thank you for your help.
> It is OK to use ConTeXt-LMTX in TeXShop and in Atom.
> 
> I’d like to compile it in LMTX mode or in MKIV mode without running "mtxrun —geneate” when I change mode.
> Set path to absolute path of mtxrun in the setting doesn’t help.
> 
> Actually, it is not a problem of ConTeXt.
> 
> I’ll try it once more.
> 
> Thank you.
> 
> Best regards,
> 
> Dalyoung
> 
> 
>> 2019. 4. 5. 오후 7:00, ntg-context-request@ntg.nl 작성:
>> 
>> Send ntg-context mailing list submissions to
>> 	ntg-context@ntg.nl
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://mailman.ntg.nl/mailman/listinfo/ntg-context
>> or, via email, send a message with subject or body 'help' to
>> 	ntg-context-request@ntg.nl
>> 
>> You can reach the person managing the list at
>> 	ntg-context-owner@ntg.nl
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ntg-context digest..."
>> 
>> 
>> Today's Topics:
>> 
>>  1. Re: How to update LMTX? (Hans Hagen)
>>  2. Re: follow up (Hans Hagen)
>>  3. Re: (no subject) (Hans Hagen)
>>  4. Re: follow up (Otared Kavian)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Fri, 5 Apr 2019 00:20:32 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] How to update LMTX?
>> Message-ID: <4ab6b1ec-62cd-90c8-0f54-b303f025c2b6@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>> 
>> On 4/5/2019 12:09 AM, Alan Braslau wrote:
>>> On Thu, 4 Apr 2019 23:11:42 +0200
>>> Hans Hagen <j.hagen@xs4all.nl> wrote:
>>> 
>>>> (we just don't use rsync)
>>> 
>>> As rsync can be problematic for some locations
>>> (TCP port 873 blocked) without the ability to
>>> tunnel.
>> 
>> indeed, especially in schools
>> 
>>> http is most often open.
>> right and rsync is also very unix centric so on windows one has to use 
>> cygwin (bah) or a mingw version (hard to get); also the rsync protocol 
>> is sometimes updated so then you need matching versions
>> 
>> 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
>> -----------------------------------------------------------------
>> 
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Fri, 5 Apr 2019 00:28:19 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] follow up
>> Message-ID: <8f908232-5516-b2a7-df76-51eba0c5140e@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>> 
>> On 4/5/2019 12:17 AM, Jeong Dal wrote:
>>> Dear Hans,
>>> 
>>> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
>>> But I have a problem to run it.
>>> 
>>> If it is OK to run a file in LMTX environment, then I got a following 
>>> error when I run it in MKIV environment.
>>> “I can’t fine a file …../defFonts.tex” even though it is there.
>>> To resolve it, I run “mtxrun —generate” in MKIV.
>>> But it invoke the same type error in LMTX.
>>> Here are the command in Atom editor which I use to run it.
>>> 
>>> LMTX:
>>> source /Users/graph/ConTeXtLMTX/tex/setuptex;
>>> context {filePath}
>>> MKIV:
>>> source /Users/graph/ConTeXt/tex/setuptex;
>>> context {filePath}
>>> 
>>> I may avoid it by adding “mtxrun —generate” before compiling it.
>>> But it isn’t a good solution.
>>> I think that there is a better way to do this.
>>> Would you please tell me how to fix it or what is a better way?
>> Does
>> 
>> <path to>/mtxrun --autogenerate --script context --autopdf {filePath}
>> 
>> work in your editor?
>> 
>> 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
>> -----------------------------------------------------------------
>> 
>> 
>> ------------------------------
>> 
>> Message: 3
>> Date: Fri, 5 Apr 2019 00:37:27 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>, Dmitry
>> 	Starostin <starostin.dmitry@gmail.com>
>> Subject: Re: [NTG-context] (no subject)
>> Message-ID: <2a626d5a-4378-e1f9-2278-d1496f62f810@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>> 
>> On 4/4/2019 9:30 PM, Dmitry Starostin wrote:
>>> In terminal:
>>> 
>>> mtxrun --autogenerate --script context --autopdf Test.tex
>>> 
>>> ->
>>> 
>>> resolvers       | initialization | fatal error: kpse library is accessed 
>>> (key: default_texmfcnf)
>> this normally means that there is no file database ... context mkiv nor 
>> lmtx doesn't use kpse
>> 
>> 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
>> -----------------------------------------------------------------
>> 
>> 
>> ------------------------------
>> 
>> Message: 4
>> Date: Fri, 5 Apr 2019 08:49:00 +0200
>> From: Otared Kavian <otared@gmail.com>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] follow up
>> Message-ID: <84D8FE1D-E7F7-418F-B10F-A141DD6D8CEC@gmail.com>
>> Content-Type: text/plain;	charset=utf-8
>> 
>> Hi Dalyoung,
>> 
>> If this can be of any help, here is what I did in order to install LuaMetaTeX on MacOS in order to use it with TeXShop:
>> 
>> 1) I downloaded from 
>> 	http://www.pragma-ade.nl/install.htm
>> the version of the installer for MacOS and installed a folder named context-osx-64 at an appropriate place (actually at /context-osx-64)
>> 
>> 2) Then I did
>> 	sh install.sh
>> in that folder, and once the download was finished I replaced the directory texmf-local with a symbolic link to my texmf-local directory (which sits somewhere else)
>> 
>> 3) In the directory
>> 	~/Library/TeXShop/Engines
>> I created a new file named LuaMetaTeX.engine containing the following three lines:
>> 
>> #!/bin/bash
>> 
>> export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
>> 
>> /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf "$1" --purgeall 
>> 
>> 4) Then when opening TeXShop, I can choose from the scroll menu which shows up on the top left of each a tex file, the engine LuaMetaTeX (or I can set it as default in the Preferences) in order to typeset with LuaMetaTeX engine.
>> 
>> 5) When I need to update the installation I just run again
>> 	sh install.sh
>> from within the directory /context-osx-64
>> (The symlink to my texmf-local is not destroyed).
>> 
>> 6) If I need to typeset a file from a command line in Terminal, then I need to say
>> 
>> 	export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
>> 
>> before typesetting myfile.tex by saying
>> 
>> 	/context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf myfile.tex
>> 
>> (Note that the above command should be issued when one is already in the directory containing myfile.tex, beacuse otherwise the corresponding pdf file will be created in the wrong place…).
>> 
>> Best regards: OK
>> 
>>> On 5 Apr 2019, at 00:17, Jeong Dal <haksan@me.com> wrote:
>>> 
>>> Dear Hans,
>>> 
>>> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
>>> But I have a problem to run it.
>>> 
>>> If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment.
>>> 	“I can’t fine a file …../defFonts.tex” even though it is there.
>>> To resolve it, I run “mtxrun —generate” in MKIV.
>>> But it invoke the same type error in LMTX.
>>> Here are the command in Atom editor which I use to run it.
>>> 
>>> LMTX:
>>> 	source /Users/graph/ConTeXtLMTX/tex/setuptex; 
>>> 	context {filePath} 
>>> MKIV:
>>> 	source /Users/graph/ConTeXt/tex/setuptex; 
>>> 	context {filePath} 
>>> 
>>> I may avoid it by adding “mtxrun —generate” before compiling it.
>>> But it isn’t a good solution.
>>> I think that there is a better way to do this.
>>> Would you please tell me how to fix it or what is a better way?
>>> 
>>> Thank you for reading.
>>> 
>>> Best regards,
>>> 
>>> Dalyoung
>>> 
>>> 
>>>> 
>>>> Hi,
>>>> 
>>>> We have worked furiously all day kicking-out extra code, and are pleased 
>>>> to present a lean-and-mean version of luatex with your favorite ConTeXt. 
>>>> Same good taste but only half the calories and a new name: luametatex 
>>>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
>>>> now stand on our own. Of course, good-old luatex and MkIV (as well as 
>>>> MkII) will continue to coexist and be maintained. However, now you will 
>>>> be able to run ConTeXt lmtx on your smart thermostat or on your 
>>>> refrigerator for the Internet of Things - the dawn of a new era!
>>>> 
>>>> Stay tuned,
>>>> 
>>>> Alan and Hans
>>> 
>>> ___________________________________________________________________________________
>>> 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
>>> ___________________________________________________________________________________
>> 
>> 
>> 
>> ------------------------------
>> 
>> Subject: Digest Footer
>> 
>> ___________________________________________________________________________________
>> 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://tex.aanhet.net
>> archive  : https://foundry.supelec.fr/projects/contextrev/
>> wiki     : http://contextgarden.net
>> ___________________________________________________________________________________
>> 
>> 
>> ------------------------------
>> 
>> End of ntg-context Digest, Vol 178, Issue 19
>> ********************************************
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 18860 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Jeong Dal]

Dear Hans and Otared,

Thank you for your help.
It is OK to use ConTeXt-LMTX in TeXShop and in Atom.

I’d like to compile it in LMTX mode or in MKIV mode without running "mtxrun —geneate” when I change mode.
Set path to absolute path of mtxrun in the setting doesn’t help.

Actually, it is not a problem of ConTeXt.

I’ll try it once more.

Thank you.

Best regards,

Dalyoung


> 2019. 4. 5. 오후 7:00, ntg-context-request@ntg.nl 작성:
> 
> Send ntg-context mailing list submissions to
> 	ntg-context@ntg.nl
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mailman.ntg.nl/mailman/listinfo/ntg-context
> or, via email, send a message with subject or body 'help' to
> 	ntg-context-request@ntg.nl
> 
> You can reach the person managing the list at
> 	ntg-context-owner@ntg.nl
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ntg-context digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: How to update LMTX? (Hans Hagen)
>   2. Re: follow up (Hans Hagen)
>   3. Re: (no subject) (Hans Hagen)
>   4. Re: follow up (Otared Kavian)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 5 Apr 2019 00:20:32 +0200
> From: Hans Hagen <j.hagen@xs4all.nl>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] How to update LMTX?
> Message-ID: <4ab6b1ec-62cd-90c8-0f54-b303f025c2b6@xs4all.nl>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 4/5/2019 12:09 AM, Alan Braslau wrote:
>> On Thu, 4 Apr 2019 23:11:42 +0200
>> Hans Hagen <j.hagen@xs4all.nl> wrote:
>> 
>>> (we just don't use rsync)
>> 
>> As rsync can be problematic for some locations
>> (TCP port 873 blocked) without the ability to
>> tunnel.
> 
> indeed, especially in schools
> 
>> http is most often open.
> right and rsync is also very unix centric so on windows one has to use 
> cygwin (bah) or a mingw version (hard to get); also the rsync protocol 
> is sometimes updated so then you need matching versions
> 
> 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
> -----------------------------------------------------------------
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 5 Apr 2019 00:28:19 +0200
> From: Hans Hagen <j.hagen@xs4all.nl>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] follow up
> Message-ID: <8f908232-5516-b2a7-df76-51eba0c5140e@xs4all.nl>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 4/5/2019 12:17 AM, Jeong Dal wrote:
>> Dear Hans,
>> 
>> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
>> But I have a problem to run it.
>> 
>> If it is OK to run a file in LMTX environment, then I got a following 
>> error when I run it in MKIV environment.
>> “I can’t fine a file …../defFonts.tex” even though it is there.
>> To resolve it, I run “mtxrun —generate” in MKIV.
>> But it invoke the same type error in LMTX.
>> Here are the command in Atom editor which I use to run it.
>> 
>> LMTX:
>> source /Users/graph/ConTeXtLMTX/tex/setuptex;
>> context {filePath}
>> MKIV:
>> source /Users/graph/ConTeXt/tex/setuptex;
>> context {filePath}
>> 
>> I may avoid it by adding “mtxrun —generate” before compiling it.
>> But it isn’t a good solution.
>> I think that there is a better way to do this.
>> Would you please tell me how to fix it or what is a better way?
> Does
> 
> <path to>/mtxrun --autogenerate --script context --autopdf {filePath}
> 
> work in your editor?
> 
> 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
> -----------------------------------------------------------------
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 5 Apr 2019 00:37:27 +0200
> From: Hans Hagen <j.hagen@xs4all.nl>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>, Dmitry
> 	Starostin <starostin.dmitry@gmail.com>
> Subject: Re: [NTG-context] (no subject)
> Message-ID: <2a626d5a-4378-e1f9-2278-d1496f62f810@xs4all.nl>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 4/4/2019 9:30 PM, Dmitry Starostin wrote:
>> In terminal:
>> 
>> mtxrun --autogenerate --script context --autopdf Test.tex
>> 
>> ->
>> 
>> resolvers       | initialization | fatal error: kpse library is accessed 
>> (key: default_texmfcnf)
> this normally means that there is no file database ... context mkiv nor 
> lmtx doesn't use kpse
> 
> 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
> -----------------------------------------------------------------
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 5 Apr 2019 08:49:00 +0200
> From: Otared Kavian <otared@gmail.com>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] follow up
> Message-ID: <84D8FE1D-E7F7-418F-B10F-A141DD6D8CEC@gmail.com>
> Content-Type: text/plain;	charset=utf-8
> 
> Hi Dalyoung,
> 
> If this can be of any help, here is what I did in order to install LuaMetaTeX on MacOS in order to use it with TeXShop:
> 
> 1) I downloaded from 
> 	http://www.pragma-ade.nl/install.htm
> the version of the installer for MacOS and installed a folder named context-osx-64 at an appropriate place (actually at /context-osx-64)
> 
> 2) Then I did
> 	sh install.sh
> in that folder, and once the download was finished I replaced the directory texmf-local with a symbolic link to my texmf-local directory (which sits somewhere else)
> 
> 3) In the directory
> 	~/Library/TeXShop/Engines
> I created a new file named LuaMetaTeX.engine containing the following three lines:
> 
> #!/bin/bash
> 
> export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
> 
> /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf "$1" --purgeall 
> 
> 4) Then when opening TeXShop, I can choose from the scroll menu which shows up on the top left of each a tex file, the engine LuaMetaTeX (or I can set it as default in the Preferences) in order to typeset with LuaMetaTeX engine.
> 
> 5) When I need to update the installation I just run again
> 	sh install.sh
> from within the directory /context-osx-64
> (The symlink to my texmf-local is not destroyed).
> 
> 6) If I need to typeset a file from a command line in Terminal, then I need to say
> 
> 	export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
> 
> before typesetting myfile.tex by saying
> 
> 	/context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf myfile.tex
> 
> (Note that the above command should be issued when one is already in the directory containing myfile.tex, beacuse otherwise the corresponding pdf file will be created in the wrong place…).
> 
> Best regards: OK
> 
>> On 5 Apr 2019, at 00:17, Jeong Dal <haksan@me.com> wrote:
>> 
>> Dear Hans,
>> 
>> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
>> But I have a problem to run it.
>> 
>> If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment.
>> 	“I can’t fine a file …../defFonts.tex” even though it is there.
>> To resolve it, I run “mtxrun —generate” in MKIV.
>> But it invoke the same type error in LMTX.
>> Here are the command in Atom editor which I use to run it.
>> 
>> LMTX:
>> 	source /Users/graph/ConTeXtLMTX/tex/setuptex; 
>> 	context {filePath} 
>> MKIV:
>> 	source /Users/graph/ConTeXt/tex/setuptex; 
>> 	context {filePath} 
>> 
>> I may avoid it by adding “mtxrun —generate” before compiling it.
>> But it isn’t a good solution.
>> I think that there is a better way to do this.
>> Would you please tell me how to fix it or what is a better way?
>> 
>> Thank you for reading.
>> 
>> Best regards,
>> 
>> Dalyoung
>> 
>> 
>>> 
>>> Hi,
>>> 
>>> We have worked furiously all day kicking-out extra code, and are pleased 
>>> to present a lean-and-mean version of luatex with your favorite ConTeXt. 
>>> Same good taste but only half the calories and a new name: luametatex 
>>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
>>> now stand on our own. Of course, good-old luatex and MkIV (as well as 
>>> MkII) will continue to coexist and be maintained. However, now you will 
>>> be able to run ConTeXt lmtx on your smart thermostat or on your 
>>> refrigerator for the Internet of Things - the dawn of a new era!
>>> 
>>> Stay tuned,
>>> 
>>> Alan and Hans
>> 
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 
> 
> ------------------------------
> 
> End of ntg-context Digest, Vol 178, Issue 19
> ********************************************

___________________________________________________________________________________
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: follow up

[Otared Kavian]

Hi Dalyoung,

If this can be of any help, here is what I did in order to install LuaMetaTeX on MacOS in order to use it with TeXShop:

1) I downloaded from 
	http://www.pragma-ade.nl/install.htm
the version of the installer for MacOS and installed a folder named context-osx-64 at an appropriate place (actually at /context-osx-64)

2) Then I did
	sh install.sh
in that folder, and once the download was finished I replaced the directory texmf-local with a symbolic link to my texmf-local directory (which sits somewhere else)

3) In the directory
	~/Library/TeXShop/Engines
I created a new file named LuaMetaTeX.engine containing the following three lines:

#!/bin/bash

export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin

/context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf "$1" --purgeall 

4) Then when opening TeXShop, I can choose from the scroll menu which shows up on the top left of each a tex file, the engine LuaMetaTeX (or I can set it as default in the Preferences) in order to typeset with LuaMetaTeX engine.

5) When I need to update the installation I just run again
	sh install.sh
from within the directory /context-osx-64
(The symlink to my texmf-local is not destroyed).

6) If I need to typeset a file from a command line in Terminal, then I need to say

	export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin

before typesetting myfile.tex by saying

	/context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf myfile.tex

(Note that the above command should be issued when one is already in the directory containing myfile.tex, beacuse otherwise the corresponding pdf file will be created in the wrong place…).

Best regards: OK

> On 5 Apr 2019, at 00:17, Jeong Dal <haksan@me.com> wrote:
> 
> Dear Hans,
> 
> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
> But I have a problem to run it.
> 
> If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment.
> 	“I can’t fine a file …../defFonts.tex” even though it is there.
> To resolve it, I run “mtxrun —generate” in MKIV.
> But it invoke the same type error in LMTX.
> Here are the command in Atom editor which I use to run it.
> 
> LMTX:
> 	source /Users/graph/ConTeXtLMTX/tex/setuptex; 
> 	context {filePath} 
> MKIV:
> 	source /Users/graph/ConTeXt/tex/setuptex; 
> 	context {filePath} 
> 
> I may avoid it by adding “mtxrun —generate” before compiling it.
> But it isn’t a good solution.
> I think that there is a better way to do this.
> Would you please tell me how to fix it or what is a better way?
> 
> Thank you for reading.
> 
> Best regards,
> 
> Dalyoung
> 
> 
>> 
>> Hi,
>> 
>> We have worked furiously all day kicking-out extra code, and are pleased 
>> to present a lean-and-mean version of luatex with your favorite ConTeXt. 
>> Same good taste but only half the calories and a new name: luametatex 
>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
>> now stand on our own. Of course, good-old luatex and MkIV (as well as 
>> MkII) will continue to coexist and be maintained. However, now you will 
>> be able to run ConTeXt lmtx on your smart thermostat or on your 
>> refrigerator for the Internet of Things - the dawn of a new era!
>> 
>> Stay tuned,
>> 
>> Alan and Hans
> 
> ___________________________________________________________________________________
> 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: follow up

[Hans Hagen]

On 4/5/2019 12:17 AM, Jeong Dal wrote:
> Dear Hans,
> 
> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
> But I have a problem to run it.
> 
> If it is OK to run a file in LMTX environment, then I got a following 
> error when I run it in MKIV environment.
> “I can’t fine a file …../defFonts.tex” even though it is there.
> To resolve it, I run “mtxrun —generate” in MKIV.
> But it invoke the same type error in LMTX.
> Here are the command in Atom editor which I use to run it.
> 
> LMTX:
> source /Users/graph/ConTeXtLMTX/tex/setuptex;
> context {filePath}
> MKIV:
> source /Users/graph/ConTeXt/tex/setuptex;
> context {filePath}
> 
> I may avoid it by adding “mtxrun —generate” before compiling it.
> But it isn’t a good solution.
> I think that there is a better way to do this.
> Would you please tell me how to fix it or what is a better way?
Does

<path to>/mtxrun --autogenerate --script context --autopdf {filePath}

work in your editor?

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: follow up

[Jeong Dal]

[-- Attachment #1.1: Type: text/plain, Size: 1541 bytes --]

Dear Hans,

I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
But I have a problem to run it.

If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment.
	“I can’t fine a file …../defFonts.tex” even though it is there.
To resolve it, I run “mtxrun —generate” in MKIV.
But it invoke the same type error in LMTX.
Here are the command in Atom editor which I use to run it.

LMTX:
	source /Users/graph/ConTeXtLMTX/tex/setuptex; 
	context {filePath} 
MKIV:
	source /Users/graph/ConTeXt/tex/setuptex; 
	context {filePath} 

I may avoid it by adding “mtxrun —generate” before compiling it.
But it isn’t a good solution.
I think that there is a better way to do this.
Would you please tell me how to fix it or what is a better way?

Thank you for reading.

Best regards,

Dalyoung


> 
> Hi,
> 
> We have worked furiously all day kicking-out extra code, and are pleased 
> to present a lean-and-mean version of luatex with your favorite ConTeXt. 
> Same good taste but only half the calories and a new name: luametatex 
> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
> now stand on our own. Of course, good-old luatex and MkIV (as well as 
> MkII) will continue to coexist and be maintained. However, now you will 
> be able to run ConTeXt lmtx on your smart thermostat or on your 
> refrigerator for the Internet of Things - the dawn of a new era!
> 
> Stay tuned,
> 
> Alan and Hans


[-- Attachment #1.2: Type: text/html, Size: 13550 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Hans Hagen]

On 4/3/2019 7:58 AM, Christoph Reller wrote:
> My two cents:
> 
> I don't believe that it is the CIDSet. Both fun.pdf and fun1.pdf have no 
> CIDSet (which is good).
> The (relevant) differences between the two PDFs are:
> - Different ToUnicode
> - Different embedded font stream
> - Minor differences in the font descriptor
> It could be the ToUnicode: If preview is not able to parse the last 
> entry in the ToUnicode table then it may also drop this glyph in its 
> display, although ToUnicode is only relevant for text extraction.

indeed and only very few viewers do that right

> It could be the font stream: In the CFF font file there is a CharSet 
> table that maps character-IDs to glyph-IDs. If preview cannot read the 
> last entry in this table (or the last glyph, glyph nr. 10) then it might 
> drop it.

coul dbe but acrobat is very picky on that as is ghostscript and they work

> By bet is on the ToUnicode, because, usually, if viewers fail to read a 
> font file then they drop the entire font file and not single glyphs.

hm, but i don't think it's different from non lmtx .. i need to check it

> Anyway, both PDFs seem to be valid. But I wonder if the differences in 
> the font descriptor are legitimate (especially StemV):
> Object 9 <-> 7: Different entry Ascent integer value: 1127 <-> 806 in 
> font descriptor dictionary.
> Object 9 <-> 7: Different entry Descent integer value: -280 <-> -194 in 
> font descriptor dictionary.
> Object 9 <-> 7: Different entry StemV integer value: 91 <-> 0 in font 
> descriptor dictionary.

yes, but most of these are bogus and heuristically derived (could be the 
subset or whole font) and quite certainly not used in rendering 
(positioning happens at the pdf level)

we'll see what magic taco has embrained ... he knows apple pdf handling 
in detail so ...

> Cheers,
> Christoph
> 
> On Tue, Apr 2, 2019 at 10:16 PM Hans Hagen <j.hagen@xs4all.nl 
> <mailto:j.hagen@xs4all.nl>> wrote:
> 
>     On 4/2/2019 8:38 PM, Taco Hoekwater wrote:
>      >
>      >
>      >> On 2 Apr 2019, at 17:11, Hans Hagen <j.hagen@xs4all.nl
>     <mailto:j.hagen@xs4all.nl>> wrote:
>      >>
>      >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
>      >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
>      >>>>> indeed on preview no x shows up but it does in other viewers
>      >>>>>
>      >>>>
>      >>>> Not just the x.
>      >>>> In the second example the s will disappear, be shows up if you
>     add some extra digits, and then dropping the 2
>      >>> I don't have a mac and can't reproduce the problem. But the missing
>      >>> char seems to be always the last one in the beginbfchar/endbfchar
>      >>> list.
>      >>>> The OSX preview is flaky but i’d assume the output of both
>     context version would be similar (enough)
>      >>> The new context adds new lines inside the beginbfchar/endbfchar
>      >>> block. Perhaps this confuses preview and it drops the last entry.
>      >> it is indeed the last one that is the issue but changing spacing
>     or adding dummies doesn't help
>      >
>      > More likely the problem it has is due to the omitted /CIDSet in
>     the font descriptor.
>      >
>      > The error is in the display engine, not the text extractor (since
>     cut&paste work ok).
>      > And that means the problem is almost certainly not the cmap. The
>     only other non-trivial
>      > difference I saw in the old vs. new pdf was that no longer
>     present /CIDSet.
>      >
>      > Unf., generating one in the text editor is bit beyond
>     me-on-the-could mode, so I can
>      > not be certain of that although it seems likely (I checked with
>     FF that the two glyphs
>      > are indeed in the embedded font subset and in the exact slots the
>     pdf says they have, so
>      > that is also unlikely to be the problem.)
>     ok, i'll check that tomorrow ... (cidsets are actually obsolete)
> 
>     Hans
> 
>     -----------------------------------------------------------------
>                                                 Hans Hagen | PRAGMA ADE
>                     Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>              tel: 038 477 53 69 | www.pragma-ade.nl
>     <http://www.pragma-ade.nl> | www.pragma-pod.nl
>     <http://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 <mailto: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
> ___________________________________________________________________________________
> 


-- 

-----------------------------------------------------------------
                                           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: follow up

[Christoph Reller]

[-- Attachment #1.1: Type: text/plain, Size: 4047 bytes --]

My two cents:

I don't believe that it is the CIDSet. Both fun.pdf and fun1.pdf have no
CIDSet (which is good).
The (relevant) differences between the two PDFs are:
- Different ToUnicode
- Different embedded font stream
- Minor differences in the font descriptor
It could be the ToUnicode: If preview is not able to parse the last entry
in the ToUnicode table then it may also drop this glyph in its display,
although ToUnicode is only relevant for text extraction.
It could be the font stream: In the CFF font file there is a CharSet table
that maps character-IDs to glyph-IDs. If preview cannot read the last entry
in this table (or the last glyph, glyph nr. 10) then it might drop it.
By bet is on the ToUnicode, because, usually, if viewers fail to read a
font file then they drop the entire font file and not single glyphs.

Anyway, both PDFs seem to be valid. But I wonder if the differences in the
font descriptor are legitimate (especially StemV):
Object 9 <-> 7: Different entry Ascent integer value: 1127 <-> 806 in font
descriptor dictionary.
Object 9 <-> 7: Different entry Descent integer value: -280 <-> -194 in
font descriptor dictionary.
Object 9 <-> 7: Different entry StemV integer value: 91 <-> 0 in font
descriptor dictionary.

Cheers,
Christoph

On Tue, Apr 2, 2019 at 10:16 PM Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 4/2/2019 8:38 PM, Taco Hoekwater wrote:
> >
> >
> >> On 2 Apr 2019, at 17:11, Hans Hagen <j.hagen@xs4all.nl> wrote:
> >>
> >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
> >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
> >>>>> indeed on preview no x shows up but it does in other viewers
> >>>>>
> >>>>
> >>>> Not just the x.
> >>>> In the second example the s will disappear, be shows up if you add
> some extra digits, and then dropping the 2
> >>> I don't have a mac and can't reproduce the problem. But the missing
> >>> char seems to be always the last one in the beginbfchar/endbfchar
> >>> list.
> >>>> The OSX preview is flaky but i’d assume the output of both context
> version would be similar (enough)
> >>> The new context adds new lines inside the beginbfchar/endbfchar
> >>> block. Perhaps this confuses preview and it drops the last entry.
> >> it is indeed the last one that is the issue but changing spacing or
> adding dummies doesn't help
> >
> > More likely the problem it has is due to the omitted /CIDSet in the font
> descriptor.
> >
> > The error is in the display engine, not the text extractor (since
> cut&paste work ok).
> > And that means the problem is almost certainly not the cmap. The only
> other non-trivial
> > difference I saw in the old vs. new pdf was that no longer present
> /CIDSet.
> >
> > Unf., generating one in the text editor is bit beyond me-on-the-could
> mode, so I can
> > not be certain of that although it seems likely (I checked with FF that
> the two glyphs
> > are indeed in the embedded font subset and in the exact slots the pdf
> says they have, so
> > that is also unlikely to be the problem.)
> ok, i'll check that tomorrow ... (cidsets are actually obsolete)
>
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 5538 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Hans Hagen]

On 4/2/2019 8:38 PM, Taco Hoekwater wrote:
> 
> 
>> On 2 Apr 2019, at 17:11, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
>> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
>>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
>>>>> indeed on preview no x shows up but it does in other viewers
>>>>>
>>>>
>>>> Not just the x.
>>>> In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2
>>> I don't have a mac and can't reproduce the problem. But the missing
>>> char seems to be always the last one in the beginbfchar/endbfchar
>>> list.
>>>> The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)
>>> The new context adds new lines inside the beginbfchar/endbfchar
>>> block. Perhaps this confuses preview and it drops the last entry.
>> it is indeed the last one that is the issue but changing spacing or adding dummies doesn't help
> 
> More likely the problem it has is due to the omitted /CIDSet in the font descriptor.
> 
> The error is in the display engine, not the text extractor (since cut&paste work ok).
> And that means the problem is almost certainly not the cmap. The only other non-trivial
> difference I saw in the old vs. new pdf was that no longer present /CIDSet.
> 
> Unf., generating one in the text editor is bit beyond me-on-the-could mode, so I can
> not be certain of that although it seems likely (I checked with FF that the two glyphs
> are indeed in the embedded font subset and in the exact slots the pdf says they have, so
> that is also unlikely to be the problem.)
ok, i'll check that tomorrow ... (cidsets are actually obsolete)

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: follow up

[Floris van Manen]

[-- Attachment #1.1.1: Type: text/plain, Size: 839 bytes --]

> More likely the problem it has is due to the omitted /CIDSet in the font descriptor.
> 
> The error is in the display engine, not the text extractor (since cut&paste work ok).
> And that means the problem is almost certainly not the cmap. The only other non-trivial
> difference I saw in the old vs. new pdf was that no longer present /CIDSet.
> 
> Unf., generating one in the text editor is bit beyond me-on-the-could mode, so I can
> not be certain of that although it seems likely (I checked with FF that the two glyphs
> are indeed in the embedded font subset and in the exact slots the pdf says they have, so
> that is also unlikely to be the problem.)
> 

I’m not familiar with the internals of pdf files.

When i use firefox as pdf viewer, the font information seems to go void in the new version (fun1.pdf).



[-- Attachment #1.1.2: Screen Shot 2019-04-02 at 21.26.52.PNG --]
[-- Type: image/png, Size: 17234 bytes --]

[-- Attachment #1.1.3: Type: text/plain, Size: 2 bytes --]




[-- Attachment #1.1.4: Screen Shot 2019-04-02 at 21.27.03.PNG --]
[-- Type: image/png, Size: 17884 bytes --]

[-- Attachment #1.1.5: Type: text/plain, Size: 2 bytes --]




[-- Attachment #1.1.6: fun.pdf --]
[-- Type: application/pdf, Size: 6173 bytes --]

[-- Attachment #1.1.7: fun1.pdf --]
[-- Type: application/pdf, Size: 4942 bytes --]

[-- Attachment #1.1.8: Type: text/plain, Size: 2 bytes --]




[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Taco Hoekwater]

> On 2 Apr 2019, at 17:11, Hans Hagen <j.hagen@xs4all.nl> wrote:
> 
> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
>>>> indeed on preview no x shows up but it does in other viewers
>>>> 
>>> 
>>> Not just the x.
>>> In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2
>> I don't have a mac and can't reproduce the problem. But the missing
>> char seems to be always the last one in the beginbfchar/endbfchar
>> list.
>>> The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)
>> The new context adds new lines inside the beginbfchar/endbfchar
>> block. Perhaps this confuses preview and it drops the last entry.
> it is indeed the last one that is the issue but changing spacing or adding dummies doesn't help

More likely the problem it has is due to the omitted /CIDSet in the font descriptor. 

The error is in the display engine, not the text extractor (since cut&paste work ok).
And that means the problem is almost certainly not the cmap. The only other non-trivial
difference I saw in the old vs. new pdf was that no longer present /CIDSet. 

Unf., generating one in the text editor is bit beyond me-on-the-could mode, so I can
not be certain of that although it seems likely (I checked with FF that the two glyphs
are indeed in the embedded font subset and in the exact slots the pdf says they have, so 
that is also unlikely to be the problem.)

Best wishes,
Taco

___________________________________________________________________________________
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: follow up

[Hans Hagen]

On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
> 
>>> indeed on preview no x shows up but it does in other viewers
>>>
>>
>> Not just the x.
>> In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2
> 
> I don't have a mac and can't reproduce the problem. But the missing
> char seems to be always the last one in the beginbfchar/endbfchar
> list.
> 
>> The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)
> 
> The new context adds new lines inside the beginbfchar/endbfchar
> block. Perhaps this confuses preview and it drops the last entry.
it is indeed the last one that is the issue but changing spacing or 
adding dummies doesn't 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 / 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: follow up

[Hans Hagen]

On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
> 
>>> indeed on preview no x shows up but it does in other viewers
>>>
>>
>> Not just the x.
>> In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2
> 
> I don't have a mac and can't reproduce the problem. But the missing
> char seems to be always the last one in the beginbfchar/endbfchar
> list.
> 
>> The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)
> 
> The new context adds new lines inside the beginbfchar/endbfchar
> block. Perhaps this confuses preview and it drops the last entry.
Hm, so it has a bad parser then? Could be. I can remove those lines as 
test.

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: follow up

[Hans Hagen]

On 4/2/2019 3:58 PM, Floris van Manen wrote:
>> indeed on preview no x shows up but it does in other viewers
>>
> 
> Not just the x.
> In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2
> 
> The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)
different backend code so there can be differences ... i have no clue 
what matters in the case of preview

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: follow up

[Ulrike Fischer]

Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:

>> indeed on preview no x shows up but it does in other viewers
>> 
> 
> Not just the x.
> In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2

I don't have a mac and can't reproduce the problem. But the missing
char seems to be always the last one in the beginbfchar/endbfchar
list.

> The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)

The new context adds new lines inside the beginbfchar/endbfchar
block. Perhaps this confuses preview and it drops the last entry. 



-- 
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 / 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: follow up

[Floris van Manen]

[-- Attachment #1.1: Type: text/plain, Size: 308 bytes --]

> indeed on preview no x shows up but it does in other viewers
> 

Not just the x.
In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2

The OSX preview is flaky but i’d assume the output of both context version would be similar (enough)

.F

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Hans Hagen]

On 4/2/2019 3:12 PM, Floris van Manen wrote:
>> With osx preview? How small can you make that test (try removing 
>> characters) till it shows up ok.
> 
> yes, OSX 10.11.6 preview
> Most likely an issue with OSX preview.
> The pdf show correct on Ubuntu
indeed on preview no x shows up but it does in other viewers

\nopdfcompression

\setupbodyfont [termes,10pt]

\startTEXpage
     x
\stopTEXpage

as acrobat doesn't complain (and it complains pretty fast) i can't do 
much about 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 / 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: follow up

[Floris van Manen]

[-- Attachment #1.1.1: Type: text/plain, Size: 376 bytes --]

> With osx preview? How small can you make that test (try removing characters) till it shows up ok.

yes, OSX 10.11.6 preview
Most likely an issue with OSX preview.
The pdf show correct on Ubuntu

.F


the error will stay all the way down:

\starttext
conText
\stoptext






\starttext
conTest
\stoptext




\starttext
conTest 123
\stoptext



[-- Attachment #1.1.2.1: Type: text/html, Size: 1933 bytes --]

[-- Attachment #1.1.2.2: Screen Shot 2019-04-02 at 15.08.49.PNG --]
[-- Type: image/png, Size: 5079 bytes --]

[-- Attachment #1.1.2.3: Screen Shot 2019-04-02 at 15.10.39.PNG --]
[-- Type: image/png, Size: 5138 bytes --]

[-- Attachment #1.1.2.4: Screen Shot 2019-04-02 at 15.11.06.PNG --]
[-- Type: image/png, Size: 5927 bytes --]

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Hans Hagen]

On 4/2/2019 2:40 PM, Floris van Manen wrote:
> There seems to be some subtle differences in the pdf output when 
> comparing the old and new context

Hm. Apart from a bit more efficient output there should be no real 
fundamental differences.

> This is the context input:
> 
> \usemodule [vim]
> \setuppapersize [A4]
> \setuplayout [
>    backspace=10mm,
>    topspace=25mm,
>    width=190mm,
>    header=0mm,
>    footer=0mm,
>    height=240mm,
> ]
> 
> \setupheader [state=empty, no]
> \setupbodyfontenvironment [default] [em=italic]
> \definefontfamily [myfamily] [serif] [TeX Gyre Termes]
> \setupbodyfont [myfamily, 10pt]
> \definefontsize [e]
> \definebodyfontenvironment [default] [e=3.5]
> \starttext
> \strut\vfill
> \startalign[center]
> {\tfe conText is fun}
> \blank[10mm]
> {\em ( ijver & vlijt 8+ )}
> 
> \stopalign
> \vfill\strut
> \stoptext
> 
> 
> this is the old version
> this is the new output
With osx preview? How small can you make that test (try removing 
characters) till it shows up 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: follow up

[Floris van Manen]

[-- Attachment #1.1.1: Type: text/plain, Size: 742 bytes --]

There seems to be some subtle differences in the pdf output when comparing the old and new context

This is the context input:

\usemodule [vim]
\setuppapersize [A4]
\setuplayout [
  backspace=10mm,
  topspace=25mm,
  width=190mm,
  header=0mm,
  footer=0mm,
  height=240mm,
]

\setupheader [state=empty, no]
\setupbodyfontenvironment [default] [em=italic]
\definefontfamily [myfamily] [serif] [TeX Gyre Termes]
\setupbodyfont [myfamily, 10pt]
\definefontsize [e]
\definebodyfontenvironment [default] [e=3.5]
\starttext
\strut\vfill
\startalign[center]
{\tfe conText is fun}
\blank[10mm]
{\em ( ijver & vlijt 8+ )}

\stopalign
\vfill\strut
\stoptext


this is the old version

this is the new output




[-- Attachment #1.1.2.1: Type: text/html, Size: 1945 bytes --]

[-- Attachment #1.1.2.2: Screen Shot 2019-04-02 at 14.36.56.PNG --]
[-- Type: image/png, Size: 13329 bytes --]

[-- Attachment #1.1.2.3: Screen Shot 2019-04-02 at 14.36.04.PNG --]
[-- Type: image/png, Size: 16443 bytes --]

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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: follow up

[Hans Hagen]

On 4/2/2019 1:49 PM, Jeong Dal wrote:
> Dear Hans and Alan,
> 
> First, thanks for your wonderful work!
> I followed your instruction to install ConTeXt LMTX.
> For the record, I wrote what I did.  Any comment is welcome to improve 
> my installation.
> 
> - create directory: ConTeXtLMTX
> - download install files.
> - run “sudo sh ./install.sh”
> - after a long lists, installation is done without errors.
> The following settings were used:
> server   : lmtx.contextgarden.net 
> <http://lmtx.contextgarden.net>,lmtx.pragma-ade.com 
> <http://lmtx.pragma-ade.com>,lmtx.pragma-ade.nl <http://lmtx.pragma-ade.nl>
>    instance : install-lmtx
>    extras   :
>    ownpath  : /Users/graph/ConTeXtLTMX
>    platform : osx-64
> 
> - I copied my local files from “texmf-local” in ConTeXt MKIV and run mtxrun
> - Recently, I am using Atom as an editor. I installed “process-pallete” 
> packge and create a command as following:
> source /Users/graph/ConTeXtLMTX/tex/setuptex;
> context {filePath}
> - At the first run, I got "permission denied” message.
> /Users/graph/ConTeXtLTMX/tex/texmf-osx-64/bin/luametatex: Permission denied
> - So I change the permission of luametatex as 755.

hm, that should be done by the installer (Alan is on osx so maybe he knows)

> - After that I tested the sample file which is given in the installation.pdf
> - Also there is no error when I compile my file which is good in ConTeXt 
> MKIV.
> - However, there is no simpleslide module. Of course, there is no 
> "module/third” folder. Thus I couldn’t compile a file in screen mode.

these have to come from the garden (will be done later) ... for the 
moment, just copy texmf-modules from another installation to the lmtx 
tex root and regenerate the file database

> I hope that I have done it right. I have a question.
> Is it better to use"/Users/graph/ConTeXtLTMX/tex/texmf-osx-64/bin/mtxrun 
> --autogenerate --script context --autopdf …" instead of “context 
> {filePath}"?

both work but --autogenerate will remake formats etc when needed after 
an update

> Thank you for reading.
> 
> Best regards,
> 
> Dalyoung
> 
> 
>>
>> Hi,
>>
>> We have worked furiously all day kicking-out extra code, and are pleased
>> to present a lean-and-mean version of luatex with your favorite ConTeXt.
>> Same good taste but only half the calories and a new name: luametatex
>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can
>> now stand on our own. Of course, good-old luatex and MkIV (as well as
>> MkII) will continue to coexist and be maintained. However, now you will
>> be able to run ConTeXt lmtx on your smart thermostat or on your
>> refrigerator for the Internet of Things - the dawn of a new era!
>>
>> Stay tuned,
>>
>> Alan and Hans
> 
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
> 


-- 

-----------------------------------------------------------------
                                           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: follow up

[Jeong Dal]

[-- Attachment #1.1: Type: text/plain, Size: 2253 bytes --]

Dear Hans and Alan,

First, thanks for your wonderful work!
I followed your instruction to install ConTeXt LMTX.
For the record, I wrote what I did.  Any comment is welcome to improve my installation.

- create directory: ConTeXtLMTX
- download install files.
- run “sudo sh ./install.sh”
- after a long lists, installation is done without errors.
	The following settings were used:
	  server   : lmtx.contextgarden.net,lmtx.pragma-ade.com,lmtx.pragma-ade.nl
  instance : install-lmtx
  extras   : 
  ownpath  : /Users/graph/ConTeXtLTMX
  platform : osx-64

- I copied my local files from “texmf-local” in ConTeXt MKIV and run mtxrun
- Recently, I am using Atom as an editor. I installed “process-pallete” packge and create a command as following:
	source /Users/graph/ConTeXtLMTX/tex/setuptex; 
	context {filePath} 
- At the first run, I got "permission denied” message.
/Users/graph/ConTeXtLTMX/tex/texmf-osx-64/bin/luametatex: Permission denied
- So I change the permission of luametatex as 755.
- After that I tested the sample file which is given in the installation.pdf
- Also there is no error when I compile my file which is good in ConTeXt MKIV.
- However, there is no simpleslide module. Of course, there is no "module/third” folder. Thus I couldn’t compile a file in screen mode.

I hope that I have done it right. I have a question.
Is it better to use"/Users/graph/ConTeXtLTMX/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf …" instead of “context {filePath}"?

Thank you for reading.

Best regards,

Dalyoung


> 
> Hi,
> 
> We have worked furiously all day kicking-out extra code, and are pleased 
> to present a lean-and-mean version of luatex with your favorite ConTeXt. 
> Same good taste but only half the calories and a new name: luametatex 
> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can 
> now stand on our own. Of course, good-old luatex and MkIV (as well as 
> MkII) will continue to coexist and be maintained. However, now you will 
> be able to run ConTeXt lmtx on your smart thermostat or on your 
> refrigerator for the Internet of Things - the dawn of a new era!
> 
> Stay tuned,
> 
> Alan and Hans


[-- Attachment #1.2: Type: text/html, Size: 15896 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________