Re: [NTG-context] [NTG-CONTEXT] LTMX crashes on OpenBSD 6.5 amd64

2019-10-21 Thread Hans Hagen

On 10/21/2019 2:51 PM, Damien Thiriet wrote:


I tried a system-wide install of luametatex,
but having my binaries in a disk mounted with w^xallowed
did not change anything.

32 bit or 64 bit

-
  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] luametatex install as root in OpenBSD

2019-10-21 Thread Damien Thiriet
Hello,


When I installed luametatex as root under OpenBSD amd64 this morning,
I first had "no permission" to launch context.

So I checked my /usr/local/context file (where I unpacked the zip).
The symlink context had the right permissions after install process
(-rwxr-xr-x root wheel) but not luametatex.
I changed permissions for luametatex to -rwxr-xr-x root wheel
but maybe it should be introduced at install script level?

Btw, context.lua and mtxrun.lua are both installed with permissions
-rwxr--r-- root wheel
Are those lua script only called by root?
Should I change their permissions as well to -rwxr-xr-x?

Greetings,


Damien Thiriet
___
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] [NTG-CONTEXT] LTMX crashes on OpenBSD 6.5 amd64

2019-10-21 Thread Damien Thiriet
Hello,


I tried a system-wide install of luametatex,
but having my binaries in a disk mounted with w^xallowed
did not change anything.

I tried to compile different files, but cannot guess yet
where do the crash come from. 
If it can help, I uploaded the luametatex.core file and files
that were compiled during the crash at this adress:

http://www.normalesup.org/~dthiriet/luametatex/

When I compiled this file, I had the first crash at page 12.
Retrying to compile made it crash at page 3.
I did not wipe the cache between compilations, nor made
mtxrun --generate and context --make.

Thanks,

Damien Thiriet
___
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] columns and footnotes

2019-10-21 Thread Hans Hagen

Hi,

just a remark:

\startlinecorrection
\stoplinecorrection

is meant for stuff like

\startlinecorrection
\framed{}
\stoplinecorrection

\startlinecorrection
\externalfigure[...]
\stoplinecorrection

\startlinecorrection
\startMPcode
...
\stopMPcode
\stoplinecorrection

in the main text flow, i.e. boxed material with some visual boundary, 
which then gets boxed again with some heuristic before/after spacing and 
therefore it will not work well when hooked into before/after for heads 
and such that do their own spacing ... it's simply not meant for that 
(and its behaviour will not change)


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] columns and footnotes

2019-10-21 Thread Hans Hagen

On 10/20/2019 3:51 PM, Henning Hraban Ramm wrote:

Hi again,
I’m testing columns again, and before I publish an article on the subject, I’d 
like to check with you.

Find attached my testing environment, env_test.tex, and columns.tex, a 
"product", as well as the result of compiling with —mode=oldcolumns,grid and 
—mode=grid

The "oldcolumns" example shows the result of \usemodule[old-columns] and looks 
like it should. The new columns code still has errors:

Previously it wasn’t possible to start (new) columns mid-page, i.e. after an 
image or chapter/intro like in the example.
This works now (progress!), but the pre-columns stuff is still shifted to the 
right. (And I don’t know where the yellow box comes from.)

Additionally, footnotes in old-columns use the whole width and don’t interfere 
with the text columns, while in new columns, footnotes start in their column 
but use the whole width anyway and thus interfere with the main text.
I tried \setupnotes[footnote][location=columns] (and other options) but saw no 
change.

Many more options to check…
yes but best check them indepedently (i have to turn these into small 
simple examples only settigm things that matter)


anyway, the shift at the top is a side effect of tracing options enabled:

\gdef\page_grids_add_to_mix_indeed#1%
  {\begingroup
   \resetvisualizers
   \global\setbox#1\vpack{\noindent\backgroundline[layout:mix]{\box#1}}%
   \endgroup}

needs an \noindent (or maybe a forgetall elsewhere but that is more 
drastic)


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] PDF viewer poll

2019-10-21 Thread Hans Hagen

On 10/20/2019 10:15 PM, Marcin Borkowski wrote:


Maybe Lua is, but every scriptable program is a risk.
LuaTeX and write18 _are_ dangerous.
It would be very easy to spread malicious TeX code, since everyone uses CTAN 
(LaTeX) packages without checking them first.
But it wouldn’t come far, I guess, for it needs a while for a package to become 
known and in wide use, and that still means only in a subset of the (La)TeX 
community, where there are enough expert hackers who would find this malicious 
code.


Assuming that they would search for it.  I'm less of an optimist here.

no problem getting a hit on a search

https://www.usenix.org/system/files/login/articles/73506-checkoway.pdf

-
  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] columns and footnotes

2019-10-21 Thread luigi scarso
On Mon, Oct 21, 2019 at 8:24 AM Henning Hraban Ramm  wrote:

> Hi again,
> I’m testing columns again, and before I publish an article on the subject,
> I’d like to check with you.
> Best, Hraban
>

Hi Hraban,
the attachment are  >100K,  I have made an exception but please try to stay
under 100K next time.

-- 
luigi
___
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] PDF viewer poll

2019-10-21 Thread Marcin Borkowski

On 2019-10-19, at 12:21, Henning Hraban Ramm  wrote:

>> Am 2019-10-15 um 08:17 schrieb Marcin Borkowski :
 Basically javascript can be limited to (1) setting annotation properties, 
 like toggling layers or button renditions, and (2) some simple 
 calculations (for forms). Constructing pdf runtime using javascript is 
 pretty braindead (use html instead then).
>>>
>>> D’accord.
>>
>> Of course you are aware that limiting a powerful language is not an easy
>> task?
>
> I am. But JS in PDF is completely different from PDF in browsers anyway (no 
> DOM!), so they don’t need a complete interpreter and could have limited PDF 
> scripting to a few commands, in JS syntax or anything else.

Fair enough, although I don't have an association JS <-> browser
ingrained so much - for me, JS is a general purpose language which
happens to be embedded in browsers, but also many other places.  Most of
my JS code runs either on a server (backend code) or in a development
environment (various, let's call it, DevOps-ish scripts).  Only now and
then I write JS for browsers, and then it is often crippled JS, full of
things like "var" (because old browsers etc.)

 It is one of the puzzling areas to me: no problem in browsers and 
 elsewhere but not in open source pdf viewers. It's not the most complex 
 stuff so it probably indicates that no one cares much about these features.
>>>
>>> I wouldn’t say "no problem", because JS causes security problems everywhere.
>>
>> It's not JS that causes problems.  Any other (powerful enough) language
>> not specifically designed with browser environment in mind could be
>> problematic here.  I guess that having Perl, Python or Ruby instead of
>> JS would create a similar set of problems.  (Lua might be an exception
>> due to its design and a possibility to whitelist functions for eval,
>> AFAIR.)
>
> Of course any programming language is a security risk. More so if it runs in 
> an ubiquitous program like a browser. And since they created JavaScript for 
> that, JS causes problems.
>
> When I read "Java runs on millions of devices" I don’t feel that’s good 
> advertising, but it remembers me that each of those devices is at risk.

I like this approach:-).  There is also that old joke than "every time
you install Java it gets moved from another device to yours", since the
installer has been saying that "3 billion devices run Java" for almost
two decades now.

>> Just 2 cents from a JS programmer who actually thinks that JS is not the
>> worst Lisp dialect out there.
>
> I didn’t say JS is bad. For me it’s a necessary evil.
> I don’t think my beloved Python would be a better choice for client scripts.

Python is a worse Lisp dialect than JS, but still nice.  (Disclaimer:
i have only written less than 1000 lines of Python in my life.)

> Maybe Lua is, but every scriptable program is a risk.
> LuaTeX and write18 _are_ dangerous.
> It would be very easy to spread malicious TeX code, since everyone uses CTAN 
> (LaTeX) packages without checking them first.
> But it wouldn’t come far, I guess, for it needs a while for a package to 
> become known and in wide use, and that still means only in a subset of the 
> (La)TeX community, where there are enough expert hackers who would find this 
> malicious code.

Assuming that they would search for it.  I'm less of an optimist here.

> And you can count the people on one hand who would be able to publish a 
> malicious ConTeXt module… Malicious code snippets in our wiki or ML also 
> wouldn’t come far.

That's interesting.  It would be enough to have a "plain TeX virus",
probably.  I guess the main reason malicious ConTeXt code does not exist
(assuming this is the case!) is that it is not economically viable - the
ConTeXt community is too small.

>
> There was PDF malware (using JS or media stuff). There also was PostScript 
> malware in its time. The latter didn’t make a lot of sense, except it could 
> destroy RIP hardware. The RIP technician at the newspaper where I worked told 
> me stories, e.g. there was an evil EPS (some faulty customer logo, no 
> deliberate malware) that caused the deletion of important parts of the RIP 
> software. At my time there was a PS ghost: somehow a page got installed on 
> one of the printers and got printed at odd times. Reboot didn’t help, we 
> never found the cause.

That's absolutely fascinating!

Best,

--
Marcin Borkowski
http://mbork.pl
___
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
___