[NTG-context] newcolumnsets: Why are settings only applied on left pages?

[Henri Menke]

Dear list,

I want to have columns of different widths in my document.  Therefore I'm using
the newcolumnsets (aka pagegrids).  However, it seems as if my settings are only
applied on right pages.  Why is that?  I tried adding page=left and page=right
but that doesn't do anything.  MWE is below.

Cheers, Henri

---

\usemodule[newcolumnsets,visual]

\definepagegrid[example][n=3,distance=.05\makeupwidth]

\setuppagegrid[example:1][width=.4\makeupwidth]
\setuppagegrid[example:2][width=.25\makeupwidth]
\setuppagegrid[example:3][width=.25\makeupwidth]

\starttext

\startpagegrid[example]
  \dorecurse{6}{\fakewords{50}{75}\column}
\stoppagegrid

\stoptext

test.pdf
Description: Adobe PDF document
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] Build for Alpine Linux

[Aditya Mahajan]

On Fri, 13 Apr 2018, Henning Hraban Ramm wrote:


Am 2018-04-13 um 13:42 schrieb Henri Menke :


Exactly. We have that. And most bits and pieces are in place to allow
that, except for the problem with mtxrun not being able to determine
the platform correctly.


Actually, the musl detection only has to be peformed for downloading
binaries.  Once those binaries are installed, they behave exactly like
the linux-64 binaries.  I would suggest to simply drop musl binaries in
the texmf-linux-64 folder as well. (Who has ConTeXt for multiple
platforms on their computer anyway?) That would render all the funny
business of calling ldd in mtxrun superfluous.


Probably only a few people need different binaries, but think of e.g.
- universities etc. that provide a (SMB/DAV) shared installation on a server
- dual-boot computers (Windows/Linux or OSX/Windows) that use a shared 
installation


But the question is for multiple libc runtimes in linux. So, I think that 
simply installing the musl and glibc in the same directory is ok.


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

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

Re: [NTG-context] Build for Alpine Linux

[Henning Hraban Ramm]

Am 2018-04-13 um 13:42 schrieb Henri Menke :

>> Exactly. We have that. And most bits and pieces are in place to allow
>> that, except for the problem with mtxrun not being able to determine
>> the platform correctly.
> 
> Actually, the musl detection only has to be peformed for downloading
> binaries.  Once those binaries are installed, they behave exactly like
> the linux-64 binaries.  I would suggest to simply drop musl binaries in
> the texmf-linux-64 folder as well. (Who has ConTeXt for multiple
> platforms on their computer anyway?) That would render all the funny
> business of calling ldd in mtxrun superfluous.

Probably only a few people need different binaries, but think of e.g.
- universities etc. that provide a (SMB/DAV) shared installation on a server
- dual-boot computers (Windows/Linux or OSX/Windows) that use a shared 
installation

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
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: [NTG-context] Font fallback scaling

[Magnus J]

That solved it. For reference, I previously used the Texlive versions
bundled with Cygwin and Arch Linux.

/MJO

On Fri, Apr 13, 2018 at 3:44 PM, Hans Hagen  wrote:
> On 4/13/2018 3:38 PM, Magnus J wrote:
>>
>> This is even more weird (same setup as before)
>
> i uploaded a beta .. maybe that one works better (at least we run the same
> then)
>
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] Font fallback scaling

[Hans Hagen]

On 4/13/2018 3:38 PM, Magnus J wrote:

This is even more weird (same setup as before)
i uploaded a beta .. maybe that one works better (at least we run the 
same then)


-
  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] Font fallback scaling

[Magnus J]

This is even more weird (same setup as before)

\starttext

wedge\wedge\footnote{wedge} prime\prime\footnote{prime}   % <-- no
\wedge (question mark) in footnote, but \prime

\page
wedge\wedge\footnote{wedge} prime\prime\footnote{prime}   % <--
\wedge and \prime

\page
wedge\wedge\footnote{wedge} prime\prime\footnote{prime}   % <--
wedge and \prime

\stoptext

On Fri, Apr 13, 2018 at 2:23 PM, Magnus J  wrote:
> Well that's even more odd. Is it visible in the attachment? Tested
> with updated Acrobat Reader and Sumatra pdf viewer without any visible
> \prime or \doubleprime, except in the footnote (where there is no
> \wedge on the other hand)... Note that \prime is visible as a footnote
> symbol, which is also in math mode. If I comment *all* of the
> \definefallbackfamily rows, it shows in the math example (but then
> it's Termes of course). With any of the \definefallbackfamily
> uncommented, it won't show.
>
> Should I disable the fallback for a specific character, i.e., remove
> the characters from one of the fallback ranges? And how is that done?
> I don't care if Termes is used for most of the symbols, but I want to
> keep as much Garamond as possible in math mode, especially for letters
> and number.
>
> /MJO
>
>> On 4/13/2018 12:34 PM, Magnus J wrote:
>>
>> >  $D\prime = 0.98$  % <-- no \prime in output
>> >
>> >  $D\doubleprime = 0.98$% <-- no \doubleprime in output
>> hm, i see primes here
>>
>>
>> -
>>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] Build for Alpine Linux

[Hans Hagen]

On 4/13/2018 1:14 PM, Mojca Miklavec wrote:

On 11 April 2018 at 22:37, Hans Hagen wrote:

On 4/11/2018 10:08 PM, Brian Hunt wrote:


3. Add texlua (and texluac?) to
a. the setup rsync bin/ directories
b. the tex/texmf-linuxmusl(|-ppc|-64)


we don't use texluac, don't need texlua on windows and on linux texlua is
just a symlink


This was entirely my fault which has been fixed in the meantime.


if musl needs different bin then there should be a different initial
download i think because basically we're now talking of: windows, osx,
linux, linuxmusl (a different species)


Exactly. We have that. And most bits and pieces are in place to allow
that, except for the problem with mtxrun not being able to determine
the platform correctly.


4. Update mtxrun

Here's code that ought to work for detecting musl in mtxrun.  Around line
3721 of the mtxrun add:

  if find(architecture,"x86_64",1,true) then
platform="linux-64"
  elseif find(architecture,"ppc",1,true) then
platform="linux-ppc"
  else
platform="linux"
  end
+   if resultof("ldd --version 2>&1"):find("musl") ~= nil then
+ platform = platform:gsub("linux", "linuxmusl")
+   end

how about this one

function resolvers.platform(t,k)
local architecture = os.getenv("HOSTTYPE") or resultof("uname 
-m") or ""

local platform = os.getenv("MTX_PLATFORM")
local musl = find(os.selfdir or "","linuxmusl")
if platform ~= "" then
-- we're done
elseif find(architecture,"x86_64",1,true) then
platform = musl and "linuxmusl" or "linux-64"
elseif find(architecture,"ppc",1,true) then
platform = "linux-ppc"
else
platform = musl and "linuxmusl" or "linux"
end
os.setenv("MTX_PLATFORM",platform)
os.platform = platform
return platform
end

assuming that the user or setuptex sets the path right this will cover 
runtime


that still leaves an issue for the initial mtx-update but that one can 
set MTX_PLATFORM=linuxmusl


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] Font fallback scaling

[Magnus J]

Well that's even more odd. Is it visible in the attachment? Tested
with updated Acrobat Reader and Sumatra pdf viewer without any visible
\prime or \doubleprime, except in the footnote (where there is no
\wedge on the other hand)... Note that \prime is visible as a footnote
symbol, which is also in math mode. If I comment *all* of the
\definefallbackfamily rows, it shows in the math example (but then
it's Termes of course). With any of the \definefallbackfamily
uncommented, it won't show.

Should I disable the fallback for a specific character, i.e., remove
the characters from one of the fallback ranges? And how is that done?
I don't care if Termes is used for most of the symbols, but I want to
keep as much Garamond as possible in math mode, especially for letters
and number.

/MJO

> On 4/13/2018 12:34 PM, Magnus J wrote:
>
> >  $D\prime = 0.98$  % <-- no \prime in output
> >
> >  $D\doubleprime = 0.98$% <-- no \doubleprime in output
> hm, i see primes here
>
>
> -
>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] Build for Alpine Linux

[Henri Menke]

On 04/13/2018 11:14 PM, Mojca Miklavec wrote:
> On 11 April 2018 at 22:37, Hans Hagen wrote:
>> On 4/11/2018 10:08 PM, Brian Hunt wrote:
>>
>>> 3. Add texlua (and texluac?) to
>>>a. the setup rsync bin/ directories
>>>b. the tex/texmf-linuxmusl(|-ppc|-64)
>>
>> we don't use texluac, don't need texlua on windows and on linux texlua is
>> just a symlink
> 
> This was entirely my fault which has been fixed in the meantime.
> 
>> if musl needs different bin then there should be a different initial
>> download i think because basically we're now talking of: windows, osx,
>> linux, linuxmusl (a different species)
> 
> Exactly. We have that. And most bits and pieces are in place to allow
> that, except for the problem with mtxrun not being able to determine
> the platform correctly.

Actually, the musl detection only has to be peformed for downloading
binaries.  Once those binaries are installed, they behave exactly like
the linux-64 binaries.  I would suggest to simply drop musl binaries in
the texmf-linux-64 folder as well. (Who has ConTeXt for multiple
platforms on their computer anyway?) That would render all the funny
business of calling ldd in mtxrun superfluous.

> 
>>> 4. Update mtxrun
>>>
>>> Here's code that ought to work for detecting musl in mtxrun.  Around line
>>> 3721 of the mtxrun add:
>>>
>>>  if find(architecture,"x86_64",1,true) then
>>>platform="linux-64"
>>>  elseif find(architecture,"ppc",1,true) then
>>>platform="linux-ppc"
>>>  else
>>>platform="linux"
>>>  end
>>> +   if resultof("ldd --version 2>&1"):find("musl") ~= nil then
>>> + platform = platform:gsub("linux", "linuxmusl")
>>> +   end
>>
>>
>> that's not going to happen, some system call 9each run) in order to
>> determine what linux species we run ... (there are a few calls but these are
>> never used becasue we use HOSTTYPE (if needed we can set one ourselves on
>> these platforms)
>>
>> isn't there some magic env var that tels if musl is used? do programs and
>> scripts really have to jumpo through such loops
> 
> Hans, we don't really need this code for the sake of minimals
> themselves, it is part of ConTeXt code that needs it and fails.
> 
> The problem is that even if I properly detect the platform upfront,
> your code (mtx-update) will refuse to respect the setting. When
> calling
> ./bin/mtxrun --script ./bin/mtx-update.lua --force --update --make
> --context=beta --platform=linuxmusl-64 --texroot="/some/path"
> from musl linux, the mtx-update will insist in always installing and
> using linux-64 binaries even if they don't work, no matter what else
> we try.
> 
> I still believe that a string like "x86_64-linuxmusl" is something
> that luatex itself should be able to return when asked about what
> platform it is running on (what platform it has been compiled for).
> We've discussed this with Taco many years ago, but this has never been
> implemented.
> 
> 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
> ___
> 

___
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] Build for Alpine Linux

[Mojca Miklavec]

On 11 April 2018 at 22:37, Hans Hagen wrote:
> On 4/11/2018 10:08 PM, Brian Hunt wrote:
>
>> 3. Add texlua (and texluac?) to
>>a. the setup rsync bin/ directories
>>b. the tex/texmf-linuxmusl(|-ppc|-64)
>
> we don't use texluac, don't need texlua on windows and on linux texlua is
> just a symlink

This was entirely my fault which has been fixed in the meantime.

> if musl needs different bin then there should be a different initial
> download i think because basically we're now talking of: windows, osx,
> linux, linuxmusl (a different species)

Exactly. We have that. And most bits and pieces are in place to allow
that, except for the problem with mtxrun not being able to determine
the platform correctly.

>> 4. Update mtxrun
>>
>> Here's code that ought to work for detecting musl in mtxrun.  Around line
>> 3721 of the mtxrun add:
>>
>>  if find(architecture,"x86_64",1,true) then
>>platform="linux-64"
>>  elseif find(architecture,"ppc",1,true) then
>>platform="linux-ppc"
>>  else
>>platform="linux"
>>  end
>> +   if resultof("ldd --version 2>&1"):find("musl") ~= nil then
>> + platform = platform:gsub("linux", "linuxmusl")
>> +   end
>
>
> that's not going to happen, some system call 9each run) in order to
> determine what linux species we run ... (there are a few calls but these are
> never used becasue we use HOSTTYPE (if needed we can set one ourselves on
> these platforms)
>
> isn't there some magic env var that tels if musl is used? do programs and
> scripts really have to jumpo through such loops

Hans, we don't really need this code for the sake of minimals
themselves, it is part of ConTeXt code that needs it and fails.

The problem is that even if I properly detect the platform upfront,
your code (mtx-update) will refuse to respect the setting. When
calling
./bin/mtxrun --script ./bin/mtx-update.lua --force --update --make
--context=beta --platform=linuxmusl-64 --texroot="/some/path"
from musl linux, the mtx-update will insist in always installing and
using linux-64 binaries even if they don't work, no matter what else
we try.

I still believe that a string like "x86_64-linuxmusl" is something
that luatex itself should be able to return when asked about what
platform it is running on (what platform it has been compiled for).
We've discussed this with Taco many years ago, but this has never been
implemented.

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: [NTG-context] Font fallback scaling

[Hans Hagen]

On 4/13/2018 12:34 PM, Magnus J wrote:


 $D\prime = 0.98$  % <-- no \prime in output

 $D\doubleprime = 0.98$% <-- no \doubleprime in output

hm, i see primes here


-
  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] Reference links with focus=standard

[Christoph Reller]

On Fri, 13 Apr 2018 10:45:39 +0100,  Lawrence Bell
 wrote:
> On 13/04/18 07:31, Henri Menke wrote:
>>
>> On Fri, 2018-04-13 at 08:13 +0200, Christoph Reller wrote:
>>>
>>> Please, Hans, I kindly ask you to reconsider. I am aware of your
>>> opinion and reasoning about this issue. But I believe that for many of
>>> us users, today's PDFs need to be both, interactive *and* printable.
>>>
>>> If there is any way I can help or motivate you, then please tell me ;-)
>>>
>> The best way to motivate Hans to implement something you need, is by
>> implementing it yourself and sending him updated core files.
>> Works for me every time ;-)
>>

Well, thank you for this hint Henry, but that works only for those who
can afford the time :-/

>
> Dear Christoph,
>
> I take it from your reply that fixing this problem with interactivity
> would likely cause some trouble with the printability? And therefore,
> it's staying as it is to prioritize printability? That's understandable,
> but a bit frustrating, since I still don't have any clue what the actual
> problem is. Could you possibly explain in some more detail or point me
> to a relevant thread?
>
> Kind regards,
>
> Lawrence
>

Dear Lawrence,

(Sorry for changing to bottom posting style.)

This issue is not about a trade-off between print-ability and
inter-activeness. If I understand Hans' position correctly, then at
least part of his reasoning is the following (please correct me if I'm
wrong): It is easy to produce two versions of a document from one
common source, one version for print and one for the screen. The
former needs no interactive links and the latter should best be viewed
fullscreen, i.e., without scrolling, in which case focus=standard is
unnecessary. While I largely agree with this approach, many of the
ConTeXt users (including myself) are not in a position to decide how
their documents should be published. I believe that many of today's
PDF documents still are meant to be both, viewed on screen and
printed. And it's only for this scenario that focus=standard makes
sense.

Kind regards,

Christoph
___
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] Reference links with focus=standard option

[Christoph Reller]

Fri, 13 Apr 2018 11:48:28 +0200, Hans Hagen  wrote:
> On 4/13/2018 8:13 AM, Christoph Reller wrote:
>>
>> This is a long standing feature request reported multiple times by
>> myself and others with MWEs in
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.
>>
>> Another MWE in which the link is non-functional:
>>
> fixed in next beta (i'm not sure when i will upload that one as i need
> to test some new features first)
>

Thank you Hans!

This is good news. Your work is very much appreciated. I am looking
forward to the next beta.

Regards,
Christoph
___
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] Build for Alpine Linux

[Brian Hunt]

For those interested in reproducing the issues experienced on Alpine, I've
published an image that you should be able to start with:

$ docker run -ti brianmhunt/context-alpine:demo

(You can see the Dockerfile etc here:
https://hub.docker.com/r/brianmhunt/context-alpine/)

That image applies the TODO/workarounds previously posted (sometimes
inelegantly) and brings it to the point where I got stuck, namely luatools
and context erroring with "unknown script base.lua" and "unknown script
context.lua", respectively.


On Wed, 11 Apr 2018 at 19:14 Henri Menke  wrote:

> On Wed, 2018-04-11 at 20:08 +, Brian Hunt wrote:
> > So here's what I've got for a TODO so far to get ConTeXt working on
> Alpine
> > Linux with musl (subject to item #6, mtx-context.lua not being found):
> >
> > 1. Add the musl test to first-setup.sh
> > 2. Add the same musl test to tex/setuptex
> > 3. Add texlua (and texluac?) to
> >   a. the setup rsync bin/ directories
> >   b. the tex/texmf-linuxmusl(|-ppc|-64)
> > 4. Update mtxrun
> >
> > Here's code that ought to work for detecting musl in mtxrun.  Around
> line 3721
> > of the mtxrun add:
> >
> > if find(architecture,"x86_64",1,true) then
> >   platform="linux-64"
> > elseif find(architecture,"ppc",1,true) then
> >   platform="linux-ppc"
> > else
> >   platform="linux"
> > end
> > +   if resultof("ldd --version 2>&1"):find("musl") ~= nil then
> > + platform = platform:gsub("linux", "linuxmusl")
> > +   end
> >
> > 5. Note that in tex/setuptex, there's evidently no way to get the current
> > script so one has to explicitly provide the TeX directory (appears to be
> a
> > BusyBox bug).
>
> Standard POSIX sh has no way to reliably detect sourced invocation of a
> script.
> BusyBox uses POSIX sh underneath and thus suffers from the same
> limitation. See
> StackOverflow for detail:
> https://stackoverflow.com/questions/29832037
>
> > 6. `context` is unable to locate `mtx-context.lua`.  Some tracker output
> sheds
> > some light:
> >   i. context --trackers=resolvers.expansions is identical
> >   ii. context --trackers=resolvers.details,resolvers.details differs,
> with the
> > output attached.  Note that to keep the comparison short I removed lines
> that
> > differed only because `linux` had been changed to `linuxmusl`.
> >
> > Will keep plugging away to see if I can determine why `mtx-context.lua`
> cannot
> > be found on Alpine Linux.
> >
> > Thanks for reading.
> >
> > Brian
> >
> > --
> > from the personal account of:
> > Brian M Hunt 
> > Direct: +1-289-684-4677 <(289)%20684-4677>
> > LinkedIn: https://linkedin.com/in/brianmhunt
> > This e-mail may contain information that is private, privileged,
> confidential
> > and/or exempt from disclosure. Except as per this notice no waiver of
> any kind
> > is intended by sending this e-mail, and this email is intended only for
> the
> > named recipient(s) or the subscribers of a forwarding service the email
> is
> > sent directly to and to which service you are an authorized recipient.
> Use,
> > dissemination or copying without authorization is prohibited. Please
> notify
> > the sender and destroy all copies of this e-mail if you have received
> this
> > email in error.
> >
> __
> > _
> > 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
>
> ___

-- 

*from the personal account of:*

*Brian M Hunt *
Direct: +1-289-684-4677
LinkedIn: https://linkedin.com/in/brianmhunt

*This e-mail may contain information that is private, privileged,
confidential and/or exempt from disclosure. Except as per this notice no
waiver of any kind is intended by sending this e-mail, and this email is
intended only for the named recipient(s) or the subscribers of a forwarding
service the email is sent directly to and to which service you are an
authorized recipient. Use, dissemination or copying without authorization
is prohibited. Please notify the sender and destroy all copies of this
e-mail if 

Re: [NTG-context] Font fallback scaling

[Magnus J]

Thanks, I could have sworn I had tested that. With my new setup, I
still have trouble with some characters in math mode. Specifically, I
don't see the \prime and \doubleprime characters in math mode, and I
can't use \wedge as a footnote symbol.

Consider this commented example, pdf result attached.

/MJO


% define the characters to use for Garamond in math mode
\definefontfamilypreset
[math:somesymbols]

[range={0x0002A-0x0002E,0x000A7,0x000B6,0x000D7,0x000F7,0x02020-0x02021,0x02212,0x02219-0x02226,0x02228-0x02265,0x02012,0x0003C-0x0003E,0x0007C},
tf=style:regular,
offset=lowercasenormal,
]

\definefallbackfamily[mainface][math][Adobe Garamond
Pro][rscale=1.05,range=digitsnormal]
\definefallbackfamily[mainface][math][Adobe Garamond
Pro][rscale=1.05,range=lowercasenormal]
\definefallbackfamily[mainface][math][Adobe Garamond
Pro][rscale=1.05,range=lowercaseitalic]
\definefallbackfamily[mainface][math][Adobe Garamond
Pro][rscale=1.05,range=uppercasenormal]
\definefallbackfamily[mainface][math][Adobe Garamond
Pro][rscale=1.05,range=uppercaseitalic]
\definefallbackfamily[mainface][math][Adobe Garamond
Pro][rscale=1.05,range=math:somesymbols]

\definefontfamily[mainface][serif][Adobe Garamond Pro]
\definefontfamily[mainface][math][TeX Gyre Termes Math][scale=0.9]

\setupbodyfont[mainface,11pt]

% footnotes
\defineconversion[avhset][\m{\wedge},\m{\prime}]
\setupnotation[footnote][way=bypage,numberconversion=avhset]

\enabletrackers[fonts.missing]

\starttext

$D\prime = 0.98$  % <-- no \prime in output

$D\doubleprime = 0.98$% <-- no \doubleprime in output

wedge\wedge\footnote{wedge}   % <-- lua stats  > unknown math
characters: ∧ (U+02227) (n=2)

prime\prime\footnote{prime}   % <--

\stoptext

> On 4/12/2018 6:17 PM, Magnus J wrote:
> > I use Adobe Garamond Pro in combination with Termes Math for math (the
> > latter for missing glyphs, Garamond is not very complete). How can I
> > scale size of Termes Math without decreasing the size of the Garamond
> > glyphs in math mode?
> >
> > /MJO
> >
> >
> >  % define the characters to use for Garamond in math mode
> >  \definefontfamilypreset
> >  [math:somesymbols]
> >
> >
[range={0x0002A-0x0002E,0x000A7,0x000B6,0x000D7,0x000F7,0x02020-0x02021,0=
x02212,0x02219-0x02226,0x02228-0x02265,0x02012,0x0003C-0x0003E,0x0007C},
> >   tf=style:regular,
> >   offset=lowercasenormal,
> >  ]
> >
> >  \definefallbackfamily[mainface][mm][Adobe Garamond
> > Pro][math:digitsnormal]
> >  \definefallbackfamily[mainface][mm][Adobe Garamond
> > Pro][math:lowercasenormal]
> >  \definefallbackfamily[mainface][mm][Adobe Garamond
> > Pro][math:lowercaseitalic]
> >  \definefallbackfamily[mainface][mm][Adobe Garamond
> > Pro][math:uppercasenormal]
> >  \definefallbackfamily[mainface][mm][Adobe Garamond
> > Pro][math:uppercaseitalic]
> >  \definefallbackfamily[mainface][mm][Adobe Garamond
> > Pro][math:somesymbols]
> >
> >  \definefontfamily[mainface][rm][Adobe Garamond Pro]
> >  \definefontfamily[mainface][mm][TeX Gyre Termes Math][scale=0.9]
%
> > <-- scaling here...
> >
> >  \setupbodyfont[mainface,11pt]
> >
> >  \starttext
> >  100
> >
> >  $100$ % <-- leads to math mode that is smaller than text, even for
> > Garamond glyphs
> >  \stoptext
>  \definefallbackfamily[mainface][math][Adobe Garamond
> Pro][rscale=1.05,range=digitsnormal]
>  \definefallbackfamily[mainface][math][Adobe Garamond
> Pro][rscale=1.05,range=lowercasenormal]
>  \definefallbackfamily[mainface][math][Adobe Garamond
> Pro][rscale=1.05,range=lowercaseitalic]
>  \definefallbackfamily[mainface][math][Adobe Garamond
> Pro][rscale=1.05,range=uppercasenormal]
>  \definefallbackfamily[mainface][math][Adobe Garamond
> Pro][rscale=1.05,range=uppercaseitalic]
>  \definefallbackfamily[mainface][math][Adobe Garamond
> Pro][rscale=1.05,range=math:somesymbols]
>
>  \definefontfamily [mainface] [serif] [Adobe Garamond Pro]
>  \definefontfamily [mainface] [math]  [TeX Gyre Termes Math]
>
>  \setupbodyfont[mainface]
>
>
> -
>Hans Hagen | PRAGMA ADE
>Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -


bla.pdf
Description: Adobe PDF document
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Mojca Miklavec]

Dear Michelle,

On 13 April 2018 at 11:13, Rodzis, Michelle wrote:
> Dear Mojca,
>
> obviously I have forgotten to add an important detail - the fonts I want to
> install are TrueType fonts. My bad and apologies!
>
> For installing ttf I've used
> http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (also mentioned in wiki)
> so far, and it worked every time.

You can forget that procedure.
Just copy the fonts, you'll only need a few lines of code for defining
the typescripts (just ask for additional help if you need to get your
fonts working).

TrueType fonts are supported out of the box and should no longer need
that clumsy process.

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: [NTG-context] Reference links with focus=standard option

[Hans Hagen]

On 4/13/2018 8:13 AM, Christoph Reller wrote:

On Wed, 11 Apr 2018 20:27:15 +0100, Lawrence Bell 
 wrote:

Thanks very much for your replies. It's reassuring to see (it seems)
that I've not overlooked some extra option that magically does the job
:) Worst case scenario I'll hack something together, or just settle for
the default focus functionality, which is not the end of the world. Just
feel like there should be a better/more elegant way.

On 11/04/18 19:36, Pablo Rodriguez wrote:

On 04/11/2018 07:14 PM, Pablo Rodriguez wrote:

On 04/11/2018 04:35 PM, Lawrence Bell wrote:

[...]
What's going on here?

I generated an uncompressed PDF document from your source:
http://pdf.ousia.tk/focus-standard.pdf.
[...]
(eq:ref) seems to be missing there. But I have to investigate the issue
further to get a more accurate report.

[...]
Sorry, but I’m afraid that I don’t know exactly what misbehaves here. I
hope Hans can fix it.


Dear all,

This is a long standing feature request reported multiple times by
myself and others with MWEs in
https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.

Another MWE in which the link is non-functional:
fixed in next beta (i'm not sure when i will upload that one as i need 
to test some new features first)


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] Reference links with focus=standard option

[Lawrence Bell]

Dear Christoph,

I take it from your reply that fixing this problem with interactivity
would likely cause some trouble with the printability? And therefore,
it's staying as it is to prioritize printability? That's understandable,
but a bit frustrating, since I still don't have any clue what the actual
problem is. Could you possibly explain in some more detail or point me
to a relevant thread?

Kind regards,

Lawrence


On 13/04/18 07:31, Henri Menke wrote:
> On Fri, 2018-04-13 at 08:13 +0200, Christoph Reller wrote:
>>> On Wed, 11 Apr 2018 20:27:15 +0100, Lawrence Bell >> il.com> wrote:
>>>
>>> Thanks very much for your replies. It's reassuring to see (it seems)
>>> that I've not overlooked some extra option that magically does the job
>>> :) Worst case scenario I'll hack something together, or just settle for
>>> the default focus functionality, which is not the end of the world. Just
>>> feel like there should be a better/more elegant way.
>>>
>>> On 11/04/18 19:36, Pablo Rodriguez wrote:
 On 04/11/2018 07:14 PM, Pablo Rodriguez wrote:
> On 04/11/2018 04:35 PM, Lawrence Bell wrote:
>> [...]
>> What's going on here?
> I generated an uncompressed PDF document from your source:
> http://pdf.ousia.tk/focus-standard.pdf.
> [...]
> (eq:ref) seems to be missing there. But I have to investigate the issue
> further to get a more accurate report.
 [...]
 Sorry, but I’m afraid that I don’t know exactly what misbehaves here. I
 hope Hans can fix it.
>> Dear all,
>>
>> This is a long standing feature request reported multiple times by
>> myself and others with MWEs in
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.
>>
>> Another MWE in which the link is non-functional:
>>
>> \setupexternalfigures[location={local,global,default}]
>> \setupinteraction[state=start, focus=standard]
>> \starttext
>> \about[figure].
>> \page
>> \placefigure[][figure]{Figure}{\externalfigure[cow.pdf]}
>> \stoptext
>>
>> Please, Hans, I kindly ask you to reconsider. I am aware of your
>> opinion and reasoning about this issue. But I believe that for many of
>> us users, today's PDFs need to be both, interactive *and* printable.
>>
>> If there is any way I can help or motivate you, then please tell me ;-)
> The best way to motivate Hans to implement something you need, is by
> implementing it yourself and sending him updated core files.
> Works for me every time ;-)
>
>> Kind regards,
>>
>> Christoph
>> __
>> _
>> 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
> ___

___
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] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Hans Hagen]

On 4/13/2018 11:10 AM, MF wrote:



After setting ConTeXt root everything works fine and as expected.
However, the texfont tool seems to be missing which means I cannot
install new fonts in my container. This seems kind of odd to me since
I thought texfont is available automatically after ConTeXt is
installed.

I also tried Henri's Debian-based Dockerfile, but texfont seems to be
missing there, too.

Any ideas on this? Have I missed something?



I don't know texfont, but i'm using ConTeXt inside a (Debian-based)
Docker container; i put the fonts directly into the image, like this
(this is an excerpt of my Dockerfile):

---
ENV OSFONTDIR
/usr/share/fonts:/usr/local/share/fonts:/opt/context/tex/texmf/fonts
# copy fonts into the system fonts directories
COPY fonts/GaramondPremrPro*.otf /usr/share/fonts/opentype/
COPY fonts/MyriadPro*.otf/usr/share/fonts/opentype/
COPY fonts/Quivira.otf   /usr/share/fonts/opentype/
COPY fonts/GFSNeohellenic*.otf   /usr/share/fonts/opentype/
COPY fonts/FiraSans*.otf /usr/share/fonts/opentype/
COPY fonts/SILEOT*.ttf   /usr/share/fonts/truetype/


or:

/texmf-fonts/fonts/data


# a writable cache for ConTeXt,
# see http://wiki.contextgarden.net/Custom_Configuration
# (i don't know if this part is still needed)
RUN mkdir -p  /var/cache/context/texmf-cache
RUN chmod ugo+rwx /var/cache/context/texmf-cache
COPY texmf.cnf/opt/context/texmf.cnf
COPY texmf.cnf/opt/context/texmfcnf.lua
ENV TEXMFCACHE/var/cache/context/texmf-cache
ENV TEXMF /opt/context/tex/texmf-context
ENV TEXROOT   /opt/context/tex
---

The fonts you want to put in the image are in the "fonts" subdir of the
Dockerfile directory.
For "texmf.cnf" (if it's still needed), see the link in the ConTeXt
wiki.


not needed, we use texmfcnf.lua


Once you build the image and run the container, you find the fonts
already installed. At the first run, ConTeXt will store them in its
cache.

You may write a Dockerfile of a ConTeXt image without fonts, then
another Dockerfile of an image based on the first one, where you add
the fonts you need for a particular job.

In case i had to add some fonts to a running container, i would "docker
cp" them inside it, in the system fonts dirs, and then "docker exec"
this command in the container:
mtxrun --script fonts --reload

Hope it helps,
best wishes,
Massimiliano
___
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: [NTG-context] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Hans Hagen]

On 4/13/2018 11:03 AM, Rodzis, Michelle wrote:

No, I want to use MKIV.

then install with

first_setup.sh --engine=luatex

and you save space too

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] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Rodzis, Michelle]

Dear Mojca,


obviously I have forgotten to add an important detail - the fonts I want to 
install are TrueType fonts. My bad and apologies!


For installing ttf I've used 
http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (also mentioned in wiki) so 
far, and it worked every time.

Best, Michelle


Von: ntg-context  im Auftrag von Mojca Miklavec 

Gesendet: Freitag, 13. April 2018 10:54
An: mailing list for ConTeXt users
Betreff: Re: [NTG-context] Installing fonts in a ConTeXt Docker (texfont tool 
missing?)

On 13 April 2018 at 10:16, Rodzis, Michelle wrote:
> Dear list,
>
> currently I work on a customized Docker container based on Ubuntu 16.04
> where I run ConTeXt standalone. To install ConTeXt, I use the approach
> described in the wiki:
>
>
> RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\
> sh ./first-setup.sh --modules=all
>
> After setting ConTeXt root everything works fine and as expected. However,
> the texfont tool seems to be missing which means I cannot install new fonts
> in my container.

Nowadays texfont is the wrong tool to use. It doesn't actually install
fonts, it merely converts them from, say, Type 1, to a zillion of
8-bit files (meaning that you won't even be able to use more than a
couple accented characters in that font). This was useful before TeX
supported OpenType fonts, but is a complete waste of time and
resources to go through that painful route nowadays.

You can just copy your own OpenType font files to, say,
texmf-fonts/data (and probably update the font database after that
with mtxrun).

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
___
___
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] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[MF]

> After setting ConTeXt root everything works fine and as expected.
> However, the texfont tool seems to be missing which means I cannot
> install new fonts in my container. This seems kind of odd to me since
> I thought texfont is available automatically after ConTeXt is
> installed. 
> 
> I also tried Henri's Debian-based Dockerfile, but texfont seems to be
> missing there, too.
> 
> Any ideas on this? Have I missed something? 
> 

I don't know texfont, but i'm using ConTeXt inside a (Debian-based)
Docker container; i put the fonts directly into the image, like this
(this is an excerpt of my Dockerfile):

---
ENV OSFONTDIR
/usr/share/fonts:/usr/local/share/fonts:/opt/context/tex/texmf/fonts
# copy fonts into the system fonts directories
COPY fonts/GaramondPremrPro*.otf /usr/share/fonts/opentype/
COPY fonts/MyriadPro*.otf/usr/share/fonts/opentype/
COPY fonts/Quivira.otf   /usr/share/fonts/opentype/
COPY fonts/GFSNeohellenic*.otf   /usr/share/fonts/opentype/
COPY fonts/FiraSans*.otf /usr/share/fonts/opentype/
COPY fonts/SILEOT*.ttf   /usr/share/fonts/truetype/

# a writable cache for ConTeXt,
# see http://wiki.contextgarden.net/Custom_Configuration
# (i don't know if this part is still needed)
RUN mkdir -p  /var/cache/context/texmf-cache
RUN chmod ugo+rwx /var/cache/context/texmf-cache
COPY texmf.cnf/opt/context/texmf.cnf
COPY texmf.cnf/opt/context/texmfcnf.lua
ENV TEXMFCACHE/var/cache/context/texmf-cache
ENV TEXMF /opt/context/tex/texmf-context
ENV TEXROOT   /opt/context/tex
---

The fonts you want to put in the image are in the "fonts" subdir of the
Dockerfile directory.
For "texmf.cnf" (if it's still needed), see the link in the ConTeXt
wiki.

Once you build the image and run the container, you find the fonts
already installed. At the first run, ConTeXt will store them in its
cache.

You may write a Dockerfile of a ConTeXt image without fonts, then
another Dockerfile of an image based on the first one, where you add
the fonts you need for a particular job.

In case i had to add some fonts to a running container, i would "docker
cp" them inside it, in the system fonts dirs, and then "docker exec"
this command in the container:
mtxrun --script fonts --reload

Hope it helps,
best wishes,
Massimiliano
___
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] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Rodzis, Michelle]

No, I want to use MKIV.


Best, Michelle


Von: ntg-context  im Auftrag von luigi scarso 

Gesendet: Freitag, 13. April 2018 10:48:21
An: mailing list for ConTeXt users
Betreff: Re: [NTG-context] Installing fonts in a ConTeXt Docker (texfont tool 
missing?)



On Fri, Apr 13, 2018 at 10:16 AM, Rodzis, Michelle 
> wrote:

Dear list,



currently I work on a customized Docker container based on Ubuntu 16.04 where I 
run ConTeXt standalone. To install ConTeXt, I use the approach described in the 
wiki:


RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\
sh ./first-setup.sh --modules=all

After setting ConTeXt root everything works fine and as expected. However, the 
texfont tool seems to be missing which means I cannot install new fonts in my 
container. This seems kind of odd to me since I thought texfont is available 
automatically after ConTeXt is installed.

I also tried Henri's Debian-based Dockerfile, but texfont seems to be missing 
there, too.

Any ideas on this? Have I missed something?


Many thanks in advance and best wishes,
Michelle

hm
Are you using (or do you want to use)  context mkii ?




--
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] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[luigi scarso]

On Fri, Apr 13, 2018 at 10:48 AM, luigi scarso 
wrote:

>
>
> On Fri, Apr 13, 2018 at 10:16 AM, Rodzis, Michelle <
> rod...@sub.uni-goettingen.de> wrote:
>
>> Dear list,
>>
>>
>>
>> currently I work on a customized Docker container based on Ubuntu 16.04
>> where I run ConTeXt standalone. To install ConTeXt, I use the approach
>> described in the wiki:
>>
>>
>> RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\
>> sh ./first-setup.sh --modules=all
>>
>> After setting ConTeXt root everything works fine and as expected.
>> However, the texfont tool seems to be missing which means I cannot install
>> new fonts in my container. This seems kind of odd to me since I thought
>> texfont is available automatically after ConTeXt is installed.
>>
>> I also tried Henri's Debian-based Dockerfile, but texfont seems to be
>> missing there, too.
>>
>> Any ideas on this? Have I missed something?
>>
>>
>> Many thanks in advance and best wishes,
>> Michelle
>>
>
> hm
> Are you using (or do you want to use)  context mkii ?
>
>
> texfont is still shipped
as  you can see in
tex/texmf-context/scripts/context/perl

and you can run it with
$ mtxrun --script texfont  --help

Do, for r mkii you need to provide in some way pdftex, perl and ruby
(for the scripts under tex/texmf-context/scripts/context/ruby)


-- 
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] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Mojca Miklavec]

On 13 April 2018 at 10:16, Rodzis, Michelle wrote:
> Dear list,
>
> currently I work on a customized Docker container based on Ubuntu 16.04
> where I run ConTeXt standalone. To install ConTeXt, I use the approach
> described in the wiki:
>
>
> RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\
> sh ./first-setup.sh --modules=all
>
> After setting ConTeXt root everything works fine and as expected. However,
> the texfont tool seems to be missing which means I cannot install new fonts
> in my container.

Nowadays texfont is the wrong tool to use. It doesn't actually install
fonts, it merely converts them from, say, Type 1, to a zillion of
8-bit files (meaning that you won't even be able to use more than a
couple accented characters in that font). This was useful before TeX
supported OpenType fonts, but is a complete waste of time and
resources to go through that painful route nowadays.

You can just copy your own OpenType font files to, say,
texmf-fonts/data (and probably update the font database after that
with mtxrun).

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: [NTG-context] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[luigi scarso]

On Fri, Apr 13, 2018 at 10:16 AM, Rodzis, Michelle <
rod...@sub.uni-goettingen.de> wrote:

> Dear list,
>
>
>
> currently I work on a customized Docker container based on Ubuntu 16.04
> where I run ConTeXt standalone. To install ConTeXt, I use the approach
> described in the wiki:
>
>
> RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\
> sh ./first-setup.sh --modules=all
>
> After setting ConTeXt root everything works fine and as expected. However,
> the texfont tool seems to be missing which means I cannot install new fonts
> in my container. This seems kind of odd to me since I thought texfont is
> available automatically after ConTeXt is installed.
>
> I also tried Henri's Debian-based Dockerfile, but texfont seems to be
> missing there, too.
>
> Any ideas on this? Have I missed something?
>
>
> Many thanks in advance and best wishes,
> Michelle
>

hm
Are you using (or do you want to use)  context mkii ?




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

[NTG-context] Installing fonts in a ConTeXt Docker (texfont tool missing?)

[Rodzis, Michelle]

Dear list,



currently I work on a customized Docker container based on Ubuntu 16.04 where I 
run ConTeXt standalone. To install ConTeXt, I use the approach described in the 
wiki:


RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\
sh ./first-setup.sh --modules=all

After setting ConTeXt root everything works fine and as expected. However, the 
texfont tool seems to be missing which means I cannot install new fonts in my 
container. This seems kind of odd to me since I thought texfont is available 
automatically after ConTeXt is installed.

I also tried Henri's Debian-based Dockerfile, but texfont seems to be missing 
there, too.

Any ideas on this? Have I missed something?


Many thanks in advance and best wishes,
Michelle

___
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] Reference links with focus=standard option

[Henri Menke]

On Fri, 2018-04-13 at 08:13 +0200, Christoph Reller wrote:
> > 
> > On Wed, 11 Apr 2018 20:27:15 +0100, Lawrence Bell  > il.com> wrote:
> > 
> > Thanks very much for your replies. It's reassuring to see (it seems)
> > that I've not overlooked some extra option that magically does the job
> > :) Worst case scenario I'll hack something together, or just settle for
> > the default focus functionality, which is not the end of the world. Just
> > feel like there should be a better/more elegant way.
> > 
> > On 11/04/18 19:36, Pablo Rodriguez wrote:
> > > 
> > > On 04/11/2018 07:14 PM, Pablo Rodriguez wrote:
> > > > 
> > > > On 04/11/2018 04:35 PM, Lawrence Bell wrote:
> > > > > 
> > > > > [...]
> > > > > What's going on here?
> > > > I generated an uncompressed PDF document from your source:
> > > > http://pdf.ousia.tk/focus-standard.pdf.
> > > > [...]
> > > > (eq:ref) seems to be missing there. But I have to investigate the issue
> > > > further to get a more accurate report.
> > > [...]
> > > Sorry, but I’m afraid that I don’t know exactly what misbehaves here. I
> > > hope Hans can fix it.
> Dear all,
> 
> This is a long standing feature request reported multiple times by
> myself and others with MWEs in
> https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
> https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.
> 
> Another MWE in which the link is non-functional:
> 
> \setupexternalfigures[location={local,global,default}]
> \setupinteraction[state=start, focus=standard]
> \starttext
> \about[figure].
> \page
> \placefigure[][figure]{Figure}{\externalfigure[cow.pdf]}
> \stoptext
> 
> Please, Hans, I kindly ask you to reconsider. I am aware of your
> opinion and reasoning about this issue. But I believe that for many of
> us users, today's PDFs need to be both, interactive *and* printable.
> 
> If there is any way I can help or motivate you, then please tell me ;-)

The best way to motivate Hans to implement something you need, is by
implementing it yourself and sending him updated core files.
Works for me every time ;-)

> 
> Kind regards,
> 
> Christoph
> __
> _
> If your question is of interest to others as well, please add an entry to the
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> __
> _
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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

Re: [NTG-context] Reference links with focus=standard option

[Christoph Reller]

> On Wed, 11 Apr 2018 20:27:15 +0100, Lawrence Bell 
>  wrote:
>
> Thanks very much for your replies. It's reassuring to see (it seems)
> that I've not overlooked some extra option that magically does the job
> :) Worst case scenario I'll hack something together, or just settle for
> the default focus functionality, which is not the end of the world. Just
> feel like there should be a better/more elegant way.
>
> On 11/04/18 19:36, Pablo Rodriguez wrote:
>> On 04/11/2018 07:14 PM, Pablo Rodriguez wrote:
>>> On 04/11/2018 04:35 PM, Lawrence Bell wrote:
 [...]
 What's going on here?
>>> I generated an uncompressed PDF document from your source:
>>> http://pdf.ousia.tk/focus-standard.pdf.
>>> [...]
>>> (eq:ref) seems to be missing there. But I have to investigate the issue
>>> further to get a more accurate report.
>> [...]
>> Sorry, but I’m afraid that I don’t know exactly what misbehaves here. I
>> hope Hans can fix it.

Dear all,

This is a long standing feature request reported multiple times by
myself and others with MWEs in
https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.

Another MWE in which the link is non-functional:

\setupexternalfigures[location={local,global,default}]
\setupinteraction[state=start, focus=standard]
\starttext
\about[figure].
\page
\placefigure[][figure]{Figure}{\externalfigure[cow.pdf]}
\stoptext

Please, Hans, I kindly ask you to reconsider. I am aware of your
opinion and reasoning about this issue. But I believe that for many of
us users, today's PDFs need to be both, interactive *and* printable.

If there is any way I can help or motivate you, then please tell me ;-)

Kind regards,

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