Hello, updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc. \enabletrackers[resolvers.*] \starttext Readable? \stoptext shows in log some file are "not readable": resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file './type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkiv' is not readable resolvers > resolving > file './type-imp-loc.mkiv' is not readable [...] resolvers > resolving > file 'lpdf-pdx.xml' is not readable resolvers > resolving > file './lpdf-pdx.xml' is not readable I have the same problem with some of my own files (some only), but have noticed even files in the distro are "not readable". Same on windows and linux. Deleting cache didn't help either. What could be the reason? Regards, Jano
On 4/10/2021 3:10 PM, Jano Kula wrote:
Hello,
updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc.
\enabletrackers[resolvers.*] \starttext Readable? \stoptext
shows in log some file are "not readable":
resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file './type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkiv' is not readable resolvers > resolving > file './type-imp-loc.mkiv' is not readable [...] resolvers > resolving > file 'lpdf-pdx.xml' is not readable resolvers > resolving > file './lpdf-pdx.xml' is not readable
I have the same problem with some of my own files (some only), but have noticed even files in the distro are "not readable". Same on windows and linux. Deleting cache didn't help either. What could be the reason? no clue ... they are like ano other file right?
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Hello Hans,
more specific resolver now:
\enabletrackers[resolvers.details]
\starttext
Readable?
\stoptext
On Sat, Apr 10, 2021 at 3:29 PM Hans Hagen
On 4/10/2021 3:10 PM, Jano Kula wrote:
resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file './type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkiv' is not readable resolvers > resolving > file './type-imp-loc.mkiv' is not readable
resolvers > resolving > file 'type-imp-loc.tex' is not readable resolvers > resolving > file './type-imp-loc.tex' is not readable resolvers > resolving > file 'type-imp-loc.tex' is not readable These are not in distribution at all, naturally missing in /tex/texmf-cache/luatex-cache/context/.........../trees/*.lua resolvers > resolving > file 'lm.lfg' is not readable resolvers > resolving > file './lm.lfg' is not readable
resolvers > resolving > file 'lpdf-pdx.xml' is not readable resolvers > resolving > file './lpdf-pdx.xml' is not readable
These are in the distribution with same access rights as other files (linux), also listed in cache files. Again, same windows and linux. Don't you have the same result? Jano
On 4/10/2021 4:54 PM, Jano Kula wrote:
Hello Hans,
more specific resolver now: \enabletrackers[resolvers.details] \starttext Readable? \stoptext
On Sat, Apr 10, 2021 at 3:29 PM Hans Hagen
mailto:j.hagen@xs4all.nl> wrote: On 4/10/2021 3:10 PM, Jano Kula wrote:
> resolvers > resolving > file 'type-imp-loc.mkxl' is not readable > resolvers > resolving > file './type-imp-loc.mkxl' is not readable > resolvers > resolving > file 'type-imp-loc.mkxl' is not readable > resolvers > resolving > file 'type-imp-loc.mkiv' is not readable > resolvers > resolving > file './type-imp-loc.mkiv' is not readable
resolvers > resolving > file 'type-imp-loc.tex' is not readable resolvers > resolving > file './type-imp-loc.tex' is not readable resolvers > resolving > file 'type-imp-loc.tex' is not readable
this is ok, at startup context loads: cont-new.* -- patch file (overwritten by update) cont-loc.* -- local patch / preferences file (not touched by update) cont-exp.* -- local experiments file (for wolfgang and, we can enable new stuff there) the type-imp-loc file for users who want to test / overload fonts or whatever (not in distribution)
These are not in distribution at all, naturally missing in /tex/texmf-cache/luatex-cache/context/.........../trees/*.lua
resolvers > resolving > file 'lm.lfg' is not readable resolvers > resolving > file './lm.lfg' is not readable
weird, should be there (in tex/context/fonts/mkiv)
> resolvers > resolving > file 'lpdf-pdx.xml' is not readable > resolvers > resolving > file './lpdf-pdx.xml' is not readable
idem, but in tex/context/base/mkxl
These are in the distribution with same access rights as other files (linux), also listed in cache files. Again, same windows and linux. Don't you have the same result?
system > 'cont-new.mkxl' loaded open source > level 1, order 1, name 'c:/data/develop/context/sources/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source > level 1, order 1, name 'c:/data/develop/context/sources/cont-new.mkxl' system > 'cont-loc.mkxl' loaded open source > level 1, order 2, name 'c:/data/develop/context/sources/cont-loc.mkxl' close source > level 1, order 2, name 'c:/data/develop/context/sources/cont-loc.mkxl' system > 'cont-exp.mkxl' loaded open source > level 1, order 3, name 'c:/data/develop/context/sources/cont-exp.mkxl' system > beware: running in overload mode 4 system > beware: \forcecolorhacks is disabled system > beware: using metapost fasttrack mode close source > level 1, order 3, name 'c:/data/develop/context/sources/cont-exp.mkxl' system > files > jobname 'oeps', input './oeps', result 'oeps' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 4, name './oeps.tex' fonts > preloading modern-designsize (math) fonts > typescripts > unknown library 'modern-designsize' fonts > 'fallback modern-designsize mm 12pt' is loaded fonts > preloading modern-designsize (mono) fonts > 'fallback modern-designsize tt 12pt' is loaded fonts > defining > font 'ArslanWessam', feature 'locl', script 'arab', no language 'dflt' backend > xmp > using file 'c:/data/develop/context/sources/lpdf-pdx.xml' ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On Sat, Apr 10, 2021 at 5:17 PM Hans Hagen
backend > xmp > using file 'c:/data/develop/context/sources/lpdf-pdx.xml'
looks like lpdf-pdx.xml is used in the end: backend > xmp > using file 'C:/data/context/bin/beta-win64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' only \enabletrackers[resolvers.details] adds the information "file not readable", likely without any real effect. I'm getting different results on windows and linux in more complex setup and "file not readable" was the only difference in log files. That's why I became interested in "file not readable" information, which seems to be misleading. In the end all files are are listed in system > start used files section and context doesn't complain it cannot open or read those files (file not found). The mystery of the log information remains unresolved. Thank you, Jano
participants (2)
-
Hans Hagen
-
Jano Kula