Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Max Chernoff via ntg-context
Hi Carlos,

I think that you may be installing the old ConTeXt MkIV distribution
instead of the new ConTeXt LMTX. ConTeXt LMTX doesn't distribute
"texlua" at all, and running 
"./install --modules=all" doesn't make sense with LMTX (since the
installer can't install modules).

From what link did you download your ConTeXt? If it started with
"minimals.contextgarden.net", then that's the old ConTeXt; if it started
with "lmtx.pragma-ade.com" then it's the new LMTX. The wiki page that
you want is

   https://wiki.contextgarden.net/Installation#Unix
   
All the other wiki pages are outdated. 

This is just a wild guess, so I may be very wrong here.

If this doesn't work, then what do you get when you run

   type -ap context
   type -ap luatex
   type -ap texlua
   type -ap luametatex
   /full/path/to/texlive/2023/context --version
   /full/path/to/context/standalone/context --version
   ls -la /full/path/to/texlive/2023/context
   ls -la /full/path/to/context/standalone/context

(I'll also add that I have both the ConTeXt and TeX Live versions of
"context" installed on Linux, so it's definitely possible.)

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

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


Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Alan Braslau via ntg-context
On Mon, 10 Apr 2023 20:51:58 -0400 (EDT)
Aditya Mahajan via ntg-context  wrote:

> Did you source the `setuptex` script, which sets the correct path.

My PATH is set to
PATH=./context/tex/texmf-freebsd-amd64/bin:/home/MyAccount/context/tex/texmf-freebsd-amd64/bin:...

If my current working directory ("./") is a project that contains its
very own subdirectory ./context/, then this is used to typeset the
project. If not, it falls back on my own general standalone
$HOME/context/, and if that does not exist, then it falls back on, say,
a systemwide TeXlive installation.

This is all that is needed to have many versions coexist.

Alan

P.S. It can be a good practice to keep a ConTeXt standalone version
associated with each project, which can be "frozen" with the project,
assuring that the sources can always be typeset in the future "as is".

P.P.S. This per-project ./context/ subdirectory can include multiple
tex/texmf-system-architecture subdirectories and the project shared
between different machines, all in happy coexistence. (Hans told me a
while ago that they all use unique luametatex caches.)
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

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


Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Carlos via ntg-context
On Mon, Apr 10, 2023 at 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote:
> On Mon, 10 Apr 2023, Carlos via ntg-context wrote:
> 
> > I'm just following some of the standalone installation instructions
> > as per the wiki alongside  a TeX Live installation,  but there are a
> > few things that don't add up or I can't seem to add them up :).
> > 
> > first, while I was trying to mtxrun --generate it returned
> > 
> > /usr/bin/env texlua no such file or directory
> > 
> > So I thought heck, perhaps by creating a symbolic link we'll call it
> > a day, but that wasn't enough, nope.
> > 
> > This is is circa 21st century ladies and gentlemen!
> > 
> > so I thought, alright, since there seems ot be a a problem with texlua,
> > let's also add it to path somehow.
> 
> Did you source the `setuptex` script, which sets the correct path.
> 
> > So with that out of the way, we'll move on to the next step and change
> > to a directory and try to call out mtxrun --generate again
> > 
> > It returns:
> > 
> > mtxrun --generate resolvers   | resolving | variable 'SELFAUTOLOC'
> > set to '/home/ce/context/bin' resolvers   | resolving | variable
> 
> This appears to be the wrong mtxrun binary. You should include the PATH 
> variable listed as part of the installation. It should point to 
> `/home/ce/context/texmf-linux-64/bin` or something similar.

with texmfcnf.lua and the contextbinary from just hte TeX Live infrastructure
there is an interesting conflict with the same ol' same ol' 

anyhow

[2/2, 00:02/02:56] install: context [92021k]
running mktexlsr ...
done running mktexlsr.
running mtxrun --generate ...
done running mtxrun --generate.
running context --luatex --generate ...
done running context --luatex --generate.
running updmap-sys ...
done running updmap-sys.

then

context 

mtxrun  | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'

context --luatex --generate 

mtxrun  | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'

same as with

context --generate

mtxrun  | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'

so it's an either or. texmfcnf.lua in place mtxrun would definitely
go through but breaks context calls, while without it, a context call
is just ostracized to a

context --generate --luatex
mtx-context | redirect luametatex -> luatex: luatex --luaonly 
"/opt/texlive/2023/bin/x86_64-linux/mtxrun.lua" --generate --redirected

but that's not what I had in mind.

mtxrun --script cache --erase

mtxrun  | unknown script 'cache.lua' or 'mtx-cache.lua'


-- 
Real Programmers think better when playing Adventure or Rogue.

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

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


Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Carlos via ntg-context
On Mon, Apr 10, 2023 at 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote:
> On Mon, 10 Apr 2023, Carlos via ntg-context wrote:
> 
> > I'm just following some of the standalone installation instructions
> > as per the wiki alongside  a TeX Live installation,  but there are a
> > few things that don't add up or I can't seem to add them up :).
> > 
> > first, while I was trying to mtxrun --generate it returned
> > 
> > /usr/bin/env texlua no such file or directory
> > 
> > So I thought heck, perhaps by creating a symbolic link we'll call it
> > a day, but that wasn't enough, nope.
> > 
> > This is is circa 21st century ladies and gentlemen!
> > 
> > so I thought, alright, since there seems ot be a a problem with texlua,
> > let's also add it to path somehow.
> 
> Did you source the `setuptex` script, which sets the correct path.
> 
> > So with that out of the way, we'll move on to the next step and change
> > to a directory and try to call out mtxrun --generate again
> > 
> > It returns:
> > 
> > mtxrun --generate resolvers   | resolving | variable 'SELFAUTOLOC'
> > set to '/home/ce/context/bin' resolvers   | resolving | variable
> 
> This appears to be the wrong mtxrun binary. You should include the PATH 
> variable listed as part of the installation. It should point to 
> `/home/ce/context/texmf-linux-64/bin` or something similar.
> 
> Aditya


Is there any rationale not to have texmfcnf.lua alongside context.cnf
and contextcnf.lua under web2c with the current standalone
installation?  

Because on TeX Live infrastructure alone, I have my doubts that that file
will be somehow generated magically. would it?

Of course I could probably scrounge it off somewhere but it's also
besides the point 

On the current installation of a standalone relying solely on what
tewmf/webc holds is… well.  




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

-- 
Time sharing: The use of many people by the computer.

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

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


Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Carlos via ntg-context
On Mon, Apr 10, 2023 at 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote:
> On Mon, 10 Apr 2023, Carlos via ntg-context wrote:
> 
> > I'm just following some of the standalone installation instructions
> > as per the wiki alongside  a TeX Live installation,  but there are a
> > few things that don't add up or I can't seem to add them up :).
> > 
> > first, while I was trying to mtxrun --generate it returned
> > 
> > /usr/bin/env texlua no such file or directory
> > 
> > So I thought heck, perhaps by creating a symbolic link we'll call it
> > a day, but that wasn't enough, nope.
> > 
> > This is is circa 21st century ladies and gentlemen!
> > 
> > so I thought, alright, since there seems ot be a a problem with texlua,
> > let's also add it to path somehow.
> 
> Did you source the `setuptex` script, which sets the correct path.

Of course I sourced it and complains about plain.tex
> 
> > So with that out of the way, we'll move on to the next step and change
> > to a directory and try to call out mtxrun --generate again
> > 
> > It returns:
> > 
> > mtxrun --generate resolvers   | resolving | variable 'SELFAUTOLOC'
> > set to '/home/ce/context/bin' resolvers   | resolving | variable
> 
> This appears to be the wrong mtxrun binary. You should include the PATH 
> variable listed as part of the installation. It should point to 
> `/home/ce/context/texmf-linux-64/bin` or something similar.

binaries. 

Let's start over for the simple reason that texmfcnf.lua does not exist.

Not through a TeX Live infrastructure only installation anyway. 

let's run ./install --modules=all and it rightly reports that 

mtx-update  | updating mtxrun for linux-64: rsync -tgo --chmod=a+x
'/home/ce/context-install/tex/texmf-context/scripts/context/lua/mtxrun.lua'
'/home/ce/context-install/tex/texmf-linux-64/bin/mtxrun'
mtx-update  | run, rsync -tgo --chmod=a+x 
'/home/ce/context-install/tex/texmf-context/scripts/context/lua/mtxrun.lua'
'/home/ce/context-install/tex/texmf-linux-64/bin/mtxrun'
rsync: [Receiver] change_dir#3 
"/home/ce/context-install/tex/texmf-linux-64/bin" failed: No such file or 
directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(827) 
[Receiver=3.2.7]
resolvers   | tds | no 'texmf-linux-64' under tree 
'/home/ce/context-install/tex'

Now. Let's add the directories, correct? 

If you were to look at the following 

resolvers   | resolving | using configuration specification 
'home:texmf/web2c;{selfautoloc:,selfautoloc:/share/texmf-local/web2c,selfautoloc:/share/texmf-dist/web2c,selfautoloc:/share/texmf/web2c,selfautoloc:/texmf-local/web2c,selfautoloc:/texmf-dist/web2c,selfautoloc:/texmf/web2c,selfautodir:,selfautodir:/share/texmf-local/web2c,selfautodir:/share/texmf-dist/web2c,selfautodir:/share/texmf/web2c,selfautodir:/texmf-local/web2c,selfautodir:/texmf-dist/web2c,selfautodir:/texmf/web2c,$SELFAUTOGRANDPARENT/texmf-local/web2c,selfautoparent:,selfautoparent:/share/texmf-local/web2c,selfautoparent:/share/texmf-dist/web2c,selfautoparent:/share/texmf/web2c,selfautoparent:/texmf-local/web2c,selfautoparent:/texmf-dist/web2c,selfautoparent:/texmf/web2c}'
resolvers   | resolving |
resolvers   | resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/texmf/web2c' from specification 'home:texmf/web2c'
resolvers   | resolving | looking for regular 'texmfcnf.lua' on weird path
'/home/ce/context-install/tex/texmf-linux-64/bin' from specification 
'selfautoloc:'


you'd notice that is looking over and over for a texmfcnf.lua 

But where is my texmfcnf.lua? Would you know? :) Because I don't. The
only instance of a texmfcnf.lua dates back to a prepackaged
installation that is no longer there anyway

it points to a prepackaged texlive which I'm not using and not planning
to. 

and what I have under TEXMFHOME which doesn't amount to much anyway , or what's
important for the current issue is 

amiga-pl.tcx  cp8bit.tcx   il2-t1.tcxmktex.opt tcvn-t5.tcx
cp1250cs.tcx  empty.tcxkam-cs.tcxmktexdir  texmf.cnf
cp1250pl.tcx  fmtutil-hdr.cnf  kam-t1.tcxmktexdir.opt  updmap-hdr.cfg
cp1250t1.tcx  fmtutil.cnf  macce-pl.tcx  mktexnam  updmap.cfg
cp227.tcx il1-t1.tcx   macce-t1.tcx  mktexnam.opt  viscii-t5.tcx
cp852-cs.tcx  il2-cs.tcx   maz-pl.tcxmktexupd
cp852-pl.tcx  il2-pl.tcx   mktex.cnf natural.tcx

which as you fully know, it doesn't help

What is TeX Live infrastructure doing is the question

It's besides the point to call out ./tlmgr install context here because
 mtx is no longer there anyway 

for what's worth

Welcome to TeX Live!

See ../texlive/2023/index.html for links to documentation.
The TeX Live web site (https://tug.org/texlive/) contains any updates and 
corrections. TeX Live is a joint project of the TeX user groups around the 
world; please consider supporting it by joining the group best for you. The 
list of groups is available on the web at 

Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Aditya Mahajan via ntg-context
On Mon, 10 Apr 2023, Carlos via ntg-context wrote:

> I'm just following some of the standalone installation instructions
> as per the wiki alongside  a TeX Live installation,  but there are a
> few things that don't add up or I can't seem to add them up :).
> 
> first, while I was trying to mtxrun --generate it returned
> 
> /usr/bin/env texlua no such file or directory
> 
> So I thought heck, perhaps by creating a symbolic link we'll call it
> a day, but that wasn't enough, nope.
> 
> This is is circa 21st century ladies and gentlemen!
> 
> so I thought, alright, since there seems ot be a a problem with texlua,
> let's also add it to path somehow.

Did you source the `setuptex` script, which sets the correct path.

> So with that out of the way, we'll move on to the next step and change
> to a directory and try to call out mtxrun --generate again
> 
> It returns:
> 
> mtxrun --generate resolvers   | resolving | variable 'SELFAUTOLOC'
> set to '/home/ce/context/bin' resolvers   | resolving | variable

This appears to be the wrong mtxrun binary. You should include the PATH 
variable listed as part of the installation. It should point to 
`/home/ce/context/texmf-linux-64/bin` or something similar.

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

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


[NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex

2023-04-10 Thread Carlos via ntg-context
I'm just following some of the standalone installation instructions
as per the wiki alongside  a TeX Live installation,  but there are a
few things that don't add up or I can't seem to add them up :).

first, while I was trying to mtxrun --generate it returned

/usr/bin/env texlua no such file or directory

So I thought heck, perhaps by creating a symbolic link we'll call it
a day, but that wasn't enough, nope.

This is is circa 21st century ladies and gentlemen!

so I thought, alright, since there seems ot be a a problem with texlua,
let's also add it to path somehow.

So with that out of the way, we'll move on to the next step and change
to a directory and try to call out mtxrun --generate again

It returns:

mtxrun --generate resolvers   | resolving | variable 'SELFAUTOLOC'
set to '/home/ce/context/bin' resolvers   | resolving | variable
'SELFAUTODIR' set to '/home/ce/context' resolvers   | resolving
| variable 'SELFAUTOPARENT' set to '/home/ce' resolvers   |
resolving | variable 'TEXMFCNF' set to '' resolvers   |
resolving | variable 'TEXMF' set to '' resolvers   | resolving
| variable 'TEXOS' set to 'context' resolvers   | resolving
| resolvers   | resolving | using configuration specification
'home:texmf/web2c;{selfautoloc:,selfautoloc:/share/texmf-local/web2c,selfautoloc:/share/texmf-dist/web2c,selfautoloc:/share/texmf/web2c,selfautoloc:/texmf-local/web2c,selfautoloc:/texmf-dist/web2c,selfautoloc:/texmf/web2c,selfautodir:,selfautodir:/share/texmf-local/web2c,selfautodir:/share/texmf-dist/web2c,selfautodir:/share/texmf/web2c,selfautodir:/texmf-local/web2c,selfautodir:/texmf-dist/web2c,selfautodir:/texmf/web2c,$SELFAUTOGRANDPARENT/texmf-local/web2c,selfautoparent:,selfautoparent:/share/texmf-local/web2c,selfautoparent:/share/texmf-dist/web2c,selfautoparent:/share/texmf/web2c,selfautoparent:/texmf-local/web2c,selfautoparent:/texmf-dist/web2c,selfautoparent:/texmf/web2c}'
resolvers   | resolving | resolvers   | resolving | looking
for regular 'texmfcnf.lua' on given path '/home/ce/texmf/web2c'
from specification 'home:texmf/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on weird path
'/home/ce/context/bin' from specification 'selfautoloc:'
resolvers   | resolving | looking for regular 'texmfcnf.lua'
on given path '/home/ce/context/bin/share/texmf-local/web2c'
from specification 'selfautoloc:/share/texmf-local/web2c'
resolvers   | resolving | looking for regular 'texmfcnf.lua'
on given path '/home/ce/context/bin/share/texmf-dist/web2c'
from specification 'selfautoloc:/share/texmf-dist/web2c'
resolvers   | resolving | looking for regular 'texmfcnf.lua'
on given path '/home/ce/context/bin/share/texmf/web2c' from
specification 'selfautoloc:/share/texmf/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/bin/texmf-local/web2c' from specification
'selfautoloc:/texmf-local/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/bin/texmf-dist/web2c' from specification
'selfautoloc:/texmf-dist/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given
path '/home/ce/context/bin/texmf/web2c' from specification
'selfautoloc:/texmf/web2c' resolvers   | resolving | looking
for regular 'texmfcnf.lua' on weird path '/home/ce/context'
from specification 'selfautodir:' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/share/texmf-local/web2c' from specification
'selfautodir:/share/texmf-local/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/share/texmf-dist/web2c' from specification
'selfautodir:/share/texmf-dist/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/share/texmf/web2c' from specification
'selfautodir:/share/texmf/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/texmf-local/web2c' from specification
'selfautodir:/texmf-local/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given
path '/home/ce/context/texmf-dist/web2c' from specification
'selfautodir:/texmf-dist/web2c' resolvers   | resolving | looking
for regular 'texmfcnf.lua' on given path '/home/ce/context/texmf/web2c'
from specification 'selfautodir:/texmf/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given path
'$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification
'$SELFAUTOGRANDPARENT/texmf-local/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on weird path
'/home/ce' from specification 'selfautoparent:' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given
path '/home/ce/share/texmf-local/web2c' from specification
'selfautoparent:/share/texmf-local/web2c' resolvers   |
resolving | looking for regular 'texmfcnf.lua' on given
path 

[NTG-context] Trial to use LibreOffice Calc (+ python) to build ConTeXt customized environnements files

2023-04-10 Thread Garulfo via ntg-context

Hi all,

I started an attempt to help producing customized environnements files 
with LibreOffice Calc and macro with python, to see if and how it can 
helps newcomers (after viewing video about batch commander from Ricardo 
Lafuente and Kaveh Bazargan).


It is very early stage (and very quick and dirty), but any feedback is 
welcome.


=

Currently working:

- one sheet to setup colors  ==> env_A05_color.tex
  - after clicking on button Go!, colors are actually shown
deduced from hsv parameter

- one sheet to setup sectionning ==> env_B14_section.tex
  - Options are categorized
- 01-Style
- 02-Numbering
- 03-Position (not yet clear)
- 04-Insert
- 05-Reference
- 06-commands

- one sheet to setup layout  ==> env_A01_layout.tex

- one sheet to setup font==> env_A04_fonts.tex
  - thanks to mtxrun --script font it provides
- the list of available font families
  - after 1st clic on fonts button
- the list of available font names
  - after selecting families and 2nd clic on fonts button
  - it can help to produce simple typescripts in 1min

=
Package can be found at 
https://wiki.contextgarden.net/images/7/73/SetupContext_with_libreoffice_v00.04.zip


4 files

1/ SetupContext_with_libreoffice.py ---
Python file that should be put in
- gnu+linux : ~/.config/libreoffice/4/user/Scripts/python
- win : C:\Users\x\AppData\Roaming\OpenOffice\4\user\Scripts\python
- mac : /Applications//LibreOffice\ 
Vanilla.app/Contents/Resources/Scripts/python/


def Initialization(): should be adapted for
 ContextPath = "path to …/tex/texmf-linux-64/bin/"

2/ readme.tex 
Basic document with content and ref to global environnement file

3/ env_00.tex 
environnement file that refers to other specific environnement files
which are produced by the macro

4/ gui_v04.ods 
LibreOffice Calc as interface for user

=
examples of output env files are attached.




\setuplayout
  [
   backspace=37mm,
   width=136mm,
   topspace=12mm,
   height=273mm,
   margindistance=5mm,
   leftmargin=20mm,
   rightmargin=20mm,
   edgedistance=2mm,
   leftedge=5mm,
   rightedge=5mm,
   headerdistance=5mm,
   header=10mm,
   footerdistance=5mm,
   footer=10mm,
   topdistance=2mm,
   top=5mm,
   bottomdistance=2mm,
   bottom=5mm,
   grid=no,
  ]





\setuppapersize[A4]



\starttypescript [serif] [myfont]
\setups[font:fallback:serif]
  \definefontsynonym [Serif] [name:palatinoltstdlight]   [features=default]
  \definefontsynonym [SerifItalic]   [name:palatinoltstdlightitalic] [features=default]
  \definefontsynonym [SerifBold] [name:palatinoltstdmedium]  [features=default]
  \definefontsynonym [SerifBoldItalic]   [name:palatinoltstdmediumitalic][features=default]
\stoptypescript

\starttypescript [sans] [myfont]
\setups[font:fallback:sans]
  \definefontsynonym [Sans] [name:ibmplexsans]  [features=default]
  \definefontsynonym [SansItalic]   [name:ibmplexsansitalic][features=default]
  \definefontsynonym [SansBold] [name:ibmplexsansbold]  [features=default]
  \definefontsynonym [SansBoldItalic]   [name:ibmplexsansbolditalic][features=default]
\stoptypescript

\starttypescript [mono] [myfont]
\setups[font:fallback:mono]
  \definefontsynonym [Mono] [name:sourcecodeprolight]   [features=default]
  \definefontsynonym [MonoItalic]   [name:sourcecodeprolightit] [features=default]
  \definefontsynonym [MonoBold] [name:sourcecodeprobold][features=default]
  \definefontsynonym [MonoBoldItalic]   [name:sourcecodeproblackit] [features=default]
\stoptypescript

\starttypescript [math] [myfont]
\setups[font:fallback:math]
  \definefontsynonym [Math] [name:lmroman10regular] [features=default]
  \definefontsynonym [MathItalic]   [name:lmroman10italic]  [features=default]
  \definefontsynonym [MathBold] [name:lmroman10bold][features=default]
  \definefontsynonym [MathBoldItalic]   [name:lmroman10bolditalic]  [features=default]
\stoptypescript

\starttypescript [handwriting] [myfont]
\setups[font:fallback:handwriting]
  \definefontsynonym [Handwriting] [name:snellroundhandltstdscr]   [features=default]
  

[NTG-context] Help with typesetting footnotes in an HTML document

2023-04-10 Thread Keith McKay via ntg-context

Hi,

I have been puzzling over how to typeset footnotes in a HTML document, 
most elements have been relatively easy to typeset but I'm stumped with 
footnotes.  I have been studying the the xml manual in particular 
Chapter  7.4 Cross Referencing, but I'm still struggling to get 
xmlsetups which come anywhere near working. Any hints  to a solution 
would be greatly appreciated.


Best Wishes

Keith McKay

%%%

Here is a snippet of the HTML document with footnotes


http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;>
http://www.w3.org/1999/xhtml; xml:lang="en">

  


  ‘What is a weed? A plant whose virtues have 
not been discovered,’ wrote Ralph Waldo Emersonclass="footnote">data-fnref="53-1">. Those delicate crucifers with their 
manifold faces of four pink or lilac petals striated with veins of 
deeper lavender are the perfect introduction to flowers for children. So 
delicate and yet hardy.
  I spend some of April abroad, travelling by 
road from an unseasonably snowy Austria (‘dieses Wetter ist 
verrückt!’data-fnref="53-2"> as an elderly lady exclaimed to me) to 
northern France, and when I come home, it’s to a landscape responding to 
substantially increased light levels and temperatures.
  This was the early sixties. Like many 
thousands, we were rehoused from Maryhill in the heart of urban Glasgow 
to this peripheral housing scheme which completely changed the character 
of what had been a village. Within a decade those glasshouses were 
abandoned, glass broken in the frames, and a row of shops that included 
a chippy and a betting shop soon replaced them, betting ‘off’ licensed 
race-tracks having become legal in 1961.class="footnote-indirect" data-fnref="75-1">

  
    
    
  Emerson, R.W. (1878) Fortune of the Republic, p.3 quoted 
in Oxford Dictionary of Quotations, Rev Fourth Edition (1996).

    
    
  ‘Crazy weather!’
    
    
  href="http://www.independent.co.uk/sport/racing/our-national-love-affair-a-history-of-the-betting-shop-804966.html; 
data-url="http://www.independent.co.uk/sport/racing/our-national-love-affair-a-history-of-the-betting-shop-804966.html;>class="import-Hyperlink">http://www.independent.co.uk/sport/racing/our-national-love-affair-a-history-of-the-betting-shop-804966.html 
[accessed 11 Dec 2017]

    
  



%%

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

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