ar old
installation update?); of course users can also decide to completely do
it themselves (check out etc) but for a local project-specific run one
doesn't want all those gigs
So, each approach has pros and cons, and we need to prevent lock into
some specifi
> though
> I define \startEndnote. This causes issues with the linter (mtxrun --script
> check
> ) but seems otherwise harmless.
>
> I am sure that others more versed in ConTeXt can find some ways to fix this
> and
define \startEndnote. This causes issues with the linter
(mtxrun --script check ) but seems otherwise harmless.
I am sure that others more versed in ConTeXt can find some ways to fix
this and improve the overall approach. I welcome suggestions
news, there is now an abstracts page with lots of talk topics added
>> by Hans himself. Check that out as well!
>
> In other news the early bird deadline in the table header row on the linked
> page is 11th July.
You are not even the first person to p
gistration form today or at the very
> last
> tomorrow, if you want to be eligible for the early bird discount.
>
> https://meeting.contextgarden.net/
>
> In other news, there is now an abstracts page with lots of talk topics added
> by Hans himself. Check that out as we
a list entry, with page numbers
and so?
indeed
And, something seems to e wrong with the numbering of the notes:
The endnote marks in the text are correct.
i need to check that, we actually need a dedicated list handler
Hans
for the early bird discount.
https://meeting.contextgarden.net/
In other news, there is now an abstracts page with lots of talk topics added
by Hans himself. Check that out as well!
https://meeting.contextgarden.net/2021/abstracts.shtml
Finally: this year for the first time we do have a (small
ontext] new upload lmtx
>
> On 6/18/21 11:46 PM, Hans Hagen wrote:
> > Hi,
> >
> > End of the week so time to wrap up.
> > [...]
> > (2) (Pablo:) There is some progress with facing floats that Thomas
> > will check out for real usage. So, still experimenta
inux if HOSTNAME is not known (did that change?)
> > > > -- on sunos always (does anyone know an env var?)
> > > > -- on freebsd always (does anyone know an env var?)
> > > >
> > > >
> > >
> -- on freebsd always (does anyone know an env var?)
> >
> >
> > Tbh I don't know. I'm on Ubuntu 20.04 and I haven't made any
> important
> > changes on the OS. In case it helps, only the latest LMTX
>
gt; > -- on freebsd always (does anyone know an env var?)
> > >
> > >
> > > Tbh I don't know. I'm on Ubuntu 20.04 and I haven't made any
> > important
> > > changes on the OS. In case it helps, only the latest LMTX
&g
> > changes on the OS. In case it helps, only the latest LMTX produces this
> > error.
> >
> > (the 'rb' looks suspicious ... i'll check that)
> what does
>
> echo $HOSTTYPE
>
>
The same as uname -m: x86_64
> report?
>
> ---
case it helps, only the latest LMTX produces this
error.
> (the 'rb' looks suspicious ... i'll check that)
>
> Hans
>
> -
>Hans Hagen | PRAGMA ADE
>Ridderstraa
?)
-- on freebsd always (does anyone know an env var?)
(the 'rb' looks suspicious ... i'll check that)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
t; > No existe el archivo o el directorio
> > cp: no se puede efectuar `stat' sobre
> >
> '/home/coragyps/lmtx/tex/texmf-context/scripts/context/lua/mtx-install.lua':
>
> > No existe el archivo o el directorio
> >
> > Messages in Spanish say the directory or
> > No existe el archivo o el directorio
> >
> > Messages in Spanish say the directory or file doesn't exist. Am I
> > missing something? Thanks in advance
> can you check what is missing by adding a print?
>
-context/scripts/context/lua/mtx-install.lua':
No existe el archivo o el directorio
Messages in Spanish say the directory or file doesn't exist. Am I
missing something? Thanks in advance
can you check what is missing by adding a print?
local popen=io.popen if popen then function print
On 6/18/21 11:46 PM, Hans Hagen wrote:
> Hi,
>
> End of the week so time to wrap up.
> [...]
> (2) (Pablo:) There is some progress with facing floats that Thomas will
> check out for real usage. So, still experimental.
Excellent news, Hans.
Many thanks for your work, Hans
}\par}
{\addff{uppercasing} \samplefile{tufte}\par}
{\addff{lowercasing} \samplefile{tufte}\par}
{\addff{primes} 123'345''\par}
\stopTEXpage
\stoptext
(2) (Pablo:) There is some pogress with facing floats that Thomas will
check out for real usage. So, still experimental
hing
> > > to do with signatures.
>
> Here is a description:
> https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=4.35
> (link should work with Firefox).
Thanks a bunch! I wonder why PDF 2.0 still isn't uploaded there, but
probably it's now ISO only
bjects is a very special term in PDF parlance. It has nothing
>> to do with signatures.
Here is a description:
https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=4.35
(link should work with Firefox).
But you might check yourself with the following sample:
\setuppap
e error in Tex Live 2021 is:
>
> tex error > tex error on line 48 in file
> /usr/local/texlive/2021/texmf-
> dist/tex/generic/pgfplots/pgfplots.code.tex: ! I can't find file
> `pgflibrarypgfplots.contourlua.code.tex’.
> l.48 \usepgfplotslibrary{
also be using
>> \definefontfamily [praise][serif][junicode]
>> but, the above min via behavior I couldn't get to work at live.contextgarden
>
> You need proper quotation mark (as shown in my example below) sand not
> ". Another option is to use the \quotation command and en
n via behavior I couldn't get to work at live.contextgarden
You need proper quotation mark (as shown in my example below) sand not
". Another option is to use the \quotation command and enable the
protrusion option for (see \setupquotation).
When you have a text with a lot of quotation
logging to trace a problem and
realize that \writeline is gone mute -
that is, the output of subsequent logging lines now gets joined up in
the same line, very hard to read...
i'll check it
___
If your question
at runtime, thereby providing an excellent
place for hacks,
%D patches, extensions and new features. There can be local
overloads in cont-loc
%D (which has always been the case) and experimental code in
cont-exp (which is also
%D so old that I need to remind myself to check
for hacks,
%D patches, extensions and new features. There can be local
overloads in cont-loc
%D (which has always been the case) and experimental code in
cont-exp (which is also
%D so old that I need to remind myself to check it occasionally, so
here is the
%D reminder).
I tried
first have to
check if we need to add some to the xml definitions
(btw, the lmt metapost commands i.e. the key/value macros fit in well in
the optional argument appeoach, the more low level ones more resemble
the low level context commands for which we have specific definitions)
Whatever you
On 5/28/2021 6:05 PM, Werner Hennrich wrote:
Hello everyone,
I'm looking into my environment's logging to trace a problem and realize
that \writeline is gone mute -
that is, the output of subsequent logging lines now gets joined up in
the same line, very hard to read...
i'll check
\usemodule[newmml]
> > \starttext
> > \xmlprocessdata{}{
> >
> >E
> >
> > π
> >
> >
> > }{}
> > \stoptext
> >
> > The π symbol does not show in red.
> Kind of trivial ... i'll send you a patched module.
On 5/27/2021 6:30 PM, Duncan Hothersall wrote:
Apologies Hans.
MWE:
\usemodule[newmml]
\starttext
\xmlprocessdata{}{
E
π
}{}
\stoptext
The π symbol does not show in red.
Kind of trivial ... i'll send you a patched module.
If you want you can check with the standard
that we can do better. This and the above are reasons to come
up with a variant memory model that permits playing with additional
features more easily. The existing storage model is stil there (after
all it's tex) but for those willing to check the alternative, in
page-ins.mkxl one can uncomment
. This and the above are reasons to come up
with a variant memory model that permits playing with additional
features more easily. The existing storage model is stil there (after
all it's tex) but for those willing to check the alternative, in
page-ins.mkxl one can uncomment
% \insertmode\plustwo
On 5/26/2021 7:17 PM, Pablo Rodriguez wrote:
On 5/25/21 6:20 PM, Hans Hagen wrote:
[...] but for those willing to check the alternative, in
page-ins.mkxl one can uncomment
% \insertmode\plustwo
Many thanks for the new upload, Hans.
I’m extremely interested in testing this.
How can we
On 5/25/21 6:20 PM, Hans Hagen wrote:
> [...] but for those willing to check the alternative, in
> page-ins.mkxl one can uncomment
>
> % \insertmode\plustwo
Many thanks for the new upload, Hans.
I’m extremely interested in testing this.
How can we enable this feature in a perma
Hi,
I uploaded a new version of lmtx. Apart from some small fixes, the
configuration file is hopefully okay too. I'm sure MF will check it.
However, the biggest change is hidden. In traditional tex, inserts (used
for footnotes) are implemented using a quadruple of registers. In
context
that I can also make 'property' a valid usage (alias)
>
> (btw often features like this are described in articles or wrapups inm
> documents in the distribution or even mentioned here but as usual with
> tex these things only make sense trigger usage when one really needs it)
>
>
rcle shifted up scaled 5mm;
draw fulltriangle shifted (up+1/2right) scaled 5mm;
]==]
local function chicken(value)
if value == "value" or value == drawme_code then
no need to check for "value" unless you also want:
\the\chicken
context.metafun.start()
context.metafun(drawing);
c
. Does this mean my
'path' command didn't work (and why not? It should have) or do I still need to
run a setup before I try to compile?
You don't say which Linux you are using so I would first check to see that
/home/me/bin/context/tex/texmf-linux-64/bin/mtxrun
is executable.
I assume that you
Not pedantic, just correct. I should have said Linux Mint 21! I'll check
the status of mtxrun but I thought all that would be automatic
On Sun, 23 May 2021, 5:54 pm Bruce Horrocks, wrote:
> On 23 May 2021, at 07:52, jbf wrote:
> >
> > Someone will quickly clarify what I am d
t say which Linux you are using so I would first check to see that
/home/me/bin/context/tex/texmf-linux-64/bin/mtxrun
is executable.
I assume that you followed the instructions on the wiki page here?
<https://wiki.contextgarden.net/Installation>
(Sorry to be so pedantic but it helps
s modeled after \type{visualizepaths} from
%D \filename{mp-tool}.
def sketchypaths =
let draw = sketchdraw ;
let fill = sketchfill ;
enddef ;
%D Check if \filename{mp-tool} is loaded
if not known context_tool :
let normaldraw = draw;
let normalfill = fill;
def naturalizepaths =
-context | main context file:
/usr/local/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.05.19 18:22
hm, maybe some missing file or so .. i'll check it
Hans
—generate
context —make
context —version still showed ver. 2021.04.29
when I ran
sh install.sh
again, the result was the same. The version installed was still 2021.04.29
Any suggestion to fix this?
maybe some hickup in th eupload ... will check tomorrow
On 5/19/2021 6:49 PM, Thomas A. Schmitz wrote:
On 19.05.21 18:34, Hans Hagen wrote:
Can you check the latest upload? You should be able to go way higher.
Yes, with 2021.05.19 18:22, the file compiles again in lmtx! I'm also
trying your suggestions for improving the Lua code and rethinking
On 19.05.21 18:34, Hans Hagen wrote:
Can you check the latest upload? You should be able to go way higher.
Yes, with 2021.05.19 18:22, the file compiles again in lmtx! I'm also
trying your suggestions for improving the Lua code and rethinking my
tables for analyzing the vocabulary. Thank
rry [reference count=32767]
Can you check the latest upload? You should be able to go way higher.
If you're worried about your lua macros performance you can always run
with:
--profile
and look at the luatex-profile.log file ... it gives a rough impression.
be prepared for a slow run (altho
elf. Sorry for the disturbance…
> irr texshoip has soem setting for it (you need to check with Dick) which
> relates to a change in synctex
>
> anyway, this whole synctex thing is a mess ... it's rather bound to the way
> latex does things and way to complex due to these heuris
not allowed in
> > Type2 where the limit is at 48.
>
> a rather low limit right from the start (we can assume only rrcurveto is
> affected)
>
> > It would be great if ConTeXt could check for this and insert additional
> > rrcuveto operators when necessary to avoid this issu
see for yourself. Sorry for the disturbance…
> irr texshoip has soem setting for it (you need to check with Dick)
> which relates to a change in synctex
It works just fine. Add this line at the top of your document:
% !TEX useOldSyncParser
I also have:
\setupsynctex[state=start,method
to the right location
in the source file.
Has something changed in the way synctex used to work ?
Below I am sending you a test file with its PDF and .synctex files, for you to
see for yourself. Sorry for the disturbance…
btw, maybe you can check with texshop for the version ... there was at
some
to the right location
in the source file.
Has something changed in the way synctex used to work ?
Below I am sending you a test file with its PDF and .synctex files, for you to
see for yourself. Sorry for the disturbance…
irr texshoip has soem setting for it (you need to check with Dick) which
ke draw and fill sketchy
%D ...
%D naturalizepaths; % Restore the value of draw and fill
%D ...
%Dendfig
%D \stoptyping
%D
%D The code is heavily inspired by Hans Hagen's Metafun macros.
%D
%D The macro \type{sketchypaths} is modeled after \type{visualizepaths} from
%D \filename{mp-
l sketchy
%D ...
%D naturalizepaths; % Restore the value of draw and fill
%D ...
%Dendfig
%D \stoptyping
%D
%D The code is heavily inspired by Hans Hagen's Metafun macros.
%D
%D The macro \type{sketchypaths} is modeled after \type{visualizepaths} from
%D \filename{mp-tool}.
.
a rather low limit right from the start (we can assume only rrcurveto is
affected)
It would be great if ConTeXt could check for this and insert additional
rrcuveto operators when necessary to avoid this issue.
after some experiments ... attached
(no upload yet as i'm renaming some low level
could check for this and insert additional
rrcuveto operators when necessary to avoid this issue.
hm, i can try but not today -)
Additionally we got a report that inkscape 1.0 seems to be incompatible
with the way commmands are passed to it for SVG files. Hendrik Seliger
suggested to set
CharString is invalid. The CFF2 CharStrings of this
glyph invokes the rrcurveto operator with 63 arguments, which is
allowed in CFF2 where the argument limit is 513, but not allowed in
Type2 where the limit is at 48.
It would be great if ConTeXt could check for this and insert additional
rrcuveto operators
;> Also, it is a bit of a shame that the XXX-webfont.ttf has postscript glyph
>> names that map to the
>> online cheat sheet, but these names are not preserved in the tma file (at
>> least not in my lmtx
>> version). Keeping those would make the whole typset-a
ld make the whole typset-a-specific-glyph procedure
be a lot less
error-prone, at least.
i suppose you noted the message -)
can you confirm / check that we can safely assume zero length names to
be okay?
local length = readbyte(f)
;%OWNPATH%tex\texmf-%PLATFORM%\bin" /M
)
)
)
rem EOF
Another possibility would be to define CONTEXT_HOME as an unexpanded value
added to both the system environment variables and the PATH variable. For
example (haven't tried it):
setx CONTEXT_HOME "%OWNPATH%tex\texmf-%PLATFORM%\bin"
On 5/9/2021 6:09 PM, Pablo Rodriguez wrote:
On 5/9/21 4:40 PM, Hans Hagen wrote:
On 5/8/2021 7:55 PM, Pablo Rodriguez wrote:
I wonder whether this might be caused by a bug or the code should be
adapted to current latest.
hm, i'll check it ... looks like some lua closure side effect
Many
On 5/9/21 4:40 PM, Hans Hagen wrote:
> On 5/8/2021 7:55 PM, Pablo Rodriguez wrote:
>
>> I wonder whether this might be caused by a bug or the code should be
>> adapted to current latest.
> hm, i'll check it ... looks like some lua closure side effect
Many thanks for your
On 5/8/2021 7:55 PM, Pablo Rodriguez wrote:
I wonder whether this might be caused by a bug or the code should be
adapted to current latest.
hm, i'll check it ... looks like some lua closure side effect
Hans
tainer as the /src directory.[2]
Once you are in the container run these commands to process the hello world
document:
# cd /src
# context hello_world.tex
There's no PDF viewer installed so you'll need to view it from the host in
"sources". On the Mac this works as expected. O
irectives[overloadmode=warning]
or even
\enabledirectives[overloadmode=error]
just in case you want to check if your own macros clash or harm the system.
Hans
-
Hans Hagen | PRAGMA ADE
i Adam,
>
> I’m on a Linux computer, so I’m not able to check this now.
>
> If the signature isn’t working, you mean that the output PDF document
> from fields-007.tex cannot be signed with Acrobat DC, don’t you?
>
> Sorry for asking the obvious question, but this worke
On 5/2/21 12:20 AM, Adam Reviczky wrote:
> Hi,
>
> I cannot get the signature working either, but almost certain it did
> work in February this year, as I have done some with MKIV.
> [...]
Hi Adam,
I’m on a Linux computer, so I’m not able to check this now.
If the signature isn
e this
%VARTEXFONTS = $TEXMFVAR/fonts
% and do not mention it in TEXMFDBS (but _do_ mention TEXMFVAR).
%
% Remove $VARTEXFONTS from TEXMFDBS if the VARTEXFONTS directory is below
% one of the TEXMF directories (avoids overlapping ls-R files).
%%%
On 4/30/2021 5:47 PM, Alan Bowen wrote:
I removed and then reinstalled luametex: the problem persists.
The stix fonts changed names (again) so the 2 in the names are gone and
text is in the filenames ...
Can you check if your names.tma has 2 in names?
Here it works ok with 'two's.
Hans
inimal example because I'm unable to reproduce it (copy all font settings
> to a new document and run ConTeXt).
>
> Can you also check if the font files are found by ConTeXt:
>
> mtxrun --scr
have create a
minimal example because I'm unable to reproduce it (copy all font
settings to a new document and run ConTeXt).
Can you also check if the font files are found by ConTeXt:
mtxrun --script fonts --list --all stixtwotext*
Wolfgang
relevant files? AFAIK only cmarrows and .mf
files in
> the cm source folder are involved. I hope you can check it if a
solution
> is possible and not too demanding. Thanks beforehand.
you can make a minimal failure example but I gues sthat the solution
has
to be i
On 4/27/2021 9:23 AM, Jairo A. del Rio wrote:
So, should I share relevant files? AFAIK only cmarrows and .mf files in
the cm source folder are involved. I hope you can check it if a solution
is possible and not too demanding. Thanks beforehand.
you can make a minimal failure example but I gues
So, should I share relevant files? AFAIK only cmarrows and .mf files in the
cm source folder are involved. I hope you can check it if a solution is
possible and not too demanding. Thanks beforehand.
Regards,
Jairo
El lun, 26 de abr. de 2021 a la(s) 03:56, Hans Hagen (j.ha...@xs4all.nl)
escribió
On 4/26/2021 12:37 PM, Hans van der Meer wrote:
I get the following message in the log (latest beta):
fonts > !
fonts > ! check count_components with mkiv !
fonts > !
These are my font settings:
\definefontfeature [default] [default] [itlc=yes]
\setu
I get the following message in the log (latest beta):
fonts > !
fonts > ! check count_components with mkiv !
fonts > !
These are my font settings:
\definefontfeature [default] [default] [itlc=yes]
\setupbodyfont[schola,10pt]
\setupitaliccorrection [text]
Output may be incorrect.
> > Error: stream Length incorrect.
> > Output may be incorrect.
>
> I'll check it
>
>
> -
>Hans Hagen | PRAG
On 4/24/2021 3:05 PM, Jairo A. del Rio wrote:
gives
Error: stream Length incorrect.
Output may be incorrect.
Error: stream Length incorrect.
Output may be incorrect.
I'll check
in the ConTeXt file with
\enabletrackers[hyphenation.applied]. Then, you can run the script with
lua check-hyphens.lua input_file whitelist.ending
As we assume .log for the input_file, the input file should be supplied without
file ending. For the (optional) whitelist a file ending has
or[red]{=} c \startcolor[blue]=\stopcolor d $\par
$ \sin \color[green]{(x)} = \sin {(x)}$\par
\stopTEXpage
The 'simplegroups' experiment enables a more hybrid grouping model but
we (read: Wolfgang, Aditya and I, but input is welcome) need to check
for side effects carefully.
The 'math
gt;
> > MWE where I expect the word "ett" instead of "1":
> > \mainlanguage[sv]
> > \starttext
> > \convertnumber{words}{1}
> > \stoptext
> You have to remake the format:
>
> context --make
>
> (I'll check the code and add it to the distribut
d
point me in the right direction. There must be some step that I'm
missing.
Thank you.
MWE where I expect the word "ett" instead of "1":
\mainlanguage[sv]
\starttext
\convertnumber{words}{1}
\stoptext
You have to remake the format:
context --make
(I'll check the code and add it to
On 4/15/2021 4:20 AM, Thangalin wrote:
A regression?
probably side effect of opacity check ... i'll fix it but no upload today
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27
the attached word list. The resulting list of words is
not huge. That corpus gives us a list of about 790 words. I’ll need to check
whether they already are in the goodies file or if I need to add them.
Anyway, I was thinking about making such a script more generic. Think of
something along the lines
brittle because the code cannot know what makes for a valid luatex-cache
directory:
private boolean reinitialize() {
// variable assignments ... exists = check for luatex-cache directory
mArgs.clear();
mArgs.add( TYPESETTER.getName() );
if( exists ) {
mArgs.add
are some 5+ % faster than the cross compiled ones.
However, because it is still somewhat experimental, the installation
uses the ming ones. (Running the test suite went down from 1350 sec
cross compiled to 1200 seconds native.)
If you want to check this out, fetch the binaries from the build server
s that DWDS ... i can write some code to deal with it (i'd rather
>> start
>> from the source than from some interpretation; who know what more there
>> is to uncover)
>
> As it turn out, the linguists that helped with the selnolig package did use
> an
ted in a PATH
directory. The second line attempts to change the luatex-cache
directory. The remaining lines configure the command-line arguments
prior to running ConTeXt.
Fearing flaming wrath from users, an additional mtxrun call is required,
which incurs overhead:
* Check for mtxrun
nsures that "context" is an executable located in a PATH
directory. The second line attempts to change the luatex-cache directory.
The remaining lines configure the command-line arguments prior to running
ConTeXt.
Fearing flaming wrath from users, an additional mtxrun call is required,
which incurs ov
Wörterbuch der deutschen Sprache). That should produce us a more
> > complete list of words where ligatures must be suppressed.
>
> where is that DWDS ... i can write some code to deal with it (i'd rather start
> from the sour
terbuch der deutschen Sprache). That should produce us a more
> > complete list of words where ligatures must be suppressed.
>
> where is that DWDS ... i can write some code to deal with it (i'd rather start
> from the source than from some interpretation; who know what more t
r[svg][conversion=mp]}
\stoptext
% EOF
Expected: Light cyan rectangle, no border (it's transparent).
Actual: Light cyan rectangle with visible border.
i'll check it .. if I forget, remind me.
3. Inkscape font specification
We discussed this previously: Inkscape extends the SVG specification
with
{#1}{/*/tag()}}
\MMLcreset
\xmlsetup{#1}{mml:relation:\xmlattdef{#1}{align}{\MMLrelationalign}}
\stopxmlsetups
can you also check
\startxmlsetups mml:apply:inverse
\settrue\xmlinversefunction
\xmlsetup{#1}{mml:\xmlfilter{#1}{/mml:apply/*[2]/tag()}}
\stopxmlsetups
his breaks the ligature completely.
\replaceword[ligs][begrifflich][begrif{fl}ich] is not correct either (doesn't
do anything).
Or with exceptions:
\startexceptions[de]
begri{ff-}{l}{ffl}(ff\zwnj l)ich
\stopexceptions
But that also breaks the ligature completely.
only in lmtx ... i'll check it
ve tried the numbercommand as well, but that also just makes the
>> formula number disappear, unless I am doing something wrong.
>> >
>> > The framing as per the math manual (manuals/math/math-framing.tex)
>> however do
.
Thanks for the PDF spec file. I will check it out for any hints about
non-standard metadata.
Alan
On Tue, Mar 23, 2021 at 4:33 PM Pablo Rodriguez wrote:
> On 3/23/21 8:25 PM, Alan Bowen wrote:
> > I should like to set the PDf properties so that the Document Info panel
> ha
> Are your margins actually non-zero? (\setuplayout)
> Maybe check with \showlayout
>
> Hraban
>
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
ex) however
> does work, so not sure:
> \setupformula[numbercommand={\inframed[framecolor=green]}]
Are your margins actually non-zero? (\setuplayout)
Maybe check with \showlayout
Hraban
___
If your question is
? Like so, or similar:
hyhenated > around line 244 ( "our marvelous and everyday capacity to
select") in file hup.tex: every-day
As said, normally you have that info (I can probably add the offset but
i assume that one is not going to check every hyphenation.)
In any case, t
> work when the character is not in the font itself. Is that the case?
> > Is this a bug or a feature?
> >
> > \starttext
> >
> >
> \definefontfallback[fall][dejavusansmono][0-0xf][check=yes,force=no]
> > \definefontsynonym[Test][file:Mikhak-Medium.ttf][f
701 - 800 of 4501 matches
Mail list logo
