Willi Egger submitted the new
Date driven lists or lists driven by date-intervals
package.
Version number: 2022-08-13
License type: Public Domain
Wants to be in ConTeXt distribution: yes
Wants to be synced with CTAN: yes
Summary description: Lists based on a given date interval
Willi Egger submitted an update to the
Date driven lists or lists driven by date-intervals
package.
Version number: 2023-.04.25
License type: Public Domain
Wants to be in ConTeXt distribution: no
Wants to be synced with CTAN: yes
Summary description: Lists based on a given date
Willi Egger submitted an update to the
Date driven lists or lists driven by date-intervals
package.
Version number: 2023.04.15
License type: Public Domain
Wants to be in ConTeXt distribution: yes
Wants to be synced with CTAN: yes
Summary description: Lists based on a given date
ixed a few others. The problem arose because of the switch
> from tar.gz to zip for the unversioned symlink.
Many thanks for your fast fix, Taco.
Best wishes for the holidays,
Pablo
_______
dev-context mailing list -- dev-context@ntg.nl
To unsubscrib
Karl Berry wrote:
I find the characterization of the situation of ConTeXt and TL quite
inaccurate. However, there seems no point in debating it. I've had the
feeling for some time that you would rather have your own distribution
you completely control according to your own needs and desires
, and have a different extension. Is there some way
this can be corrected at the packaging end?
I will take a look at that, but note that the
context-doc-nonfree
packages has NOT been updated in a while, so it probably is in a bad
state wrt organization. Next upload will ship pdf
On Mi, 16 Apr 2008, Hans Hagen wrote:
well, it may work with the old fonts (depends on how old), in
font-syn.tex you will find
Well it is the last release before the renaming of the fonts, as I said
1.01x.
etc. so older fonts are ok for context/luatex; while for xetex new fonts
are needed
On Mi, 16 Apr 2008, Mojca Miklavec wrote:
For XeLaTeX you indeed need to update fontspec, but if you're
reluctant to upgrade the rest of XeTeX, a fix of fontspec to support
the latest LM fonts is so minor, that it's really not worth having a
broken ConTeXt+XeTeX. fontspec might need only a few
installation from it. You can only use it
to upgrade LuaTeX/ConTeXt or to install additional packages on top of
existing installation.
OK. Tried to update a fresh TL installation:
sudo tlmgr --repository http://tlcontrib.metatex.org/2010/ update --all
%%% OUTPUT
I am converting myself to MkIV, and ran into the following error:
! LuaTeX error /usr/share/texmf/tex/context/base/meta-pdf.lua:355: attempt to
call global 'pdfgrayliteral' (a nil value)
stack traceback:
/usr/share/texmf/tex/context/base/meta-pdf.lua:355: in function
/usr/share
Correction: looks OK in xpdf, looks bad in kpdf.
Same here: fine in xpdf, bad in kpdf. Also it's fine in gs 8.50. I'm
using Ubuntu/i386 with pdftex 1.40 and the Debian context packages (so
2007.01.23).
Not sure whether the difference between xpdf and kpdf means that it's
a kpdf bug or a bug
On Tuesday 06 February 2007 18:46, Sanjoy Mahajan wrote:
I just tried it on a nearby Mac OS 10.3 machine with its built-in
Preview viewer. Preview complains that it cannot recognize the file
format! As a check, I tried a bunch of other ConTeXt-produced
documents, including a 100-page math
Hi Sanjoy,
I'm really sorry, there is a typo in line 319 of enco-agr.tex.
Correct greeldasiavaria to greekdasiavaria, and you should be in
business...
I'm afraid your document doesn't compile at all with my version of
ConTeXt
ConTeXt ver: 2007.01.23 13:32 MKII fmt: 2007.2.6 int
Hello,
As a (delayed) part of my duty I'm now writing the report about the
Discussion on improving ConTeXt documentation.
One of ideas was to add a short footer to each mail on the mailing
list, which would encourage more people to reply after they get a
solution to their feature request
Norbert Preining wrote:
forwarded 447559 dev-context@ntg.nl
thanks
Hi Hans, hi all!
We got the following bug report for the Debian package, but I guess that
should be fixed upstream:
for latex, ppchtex is loaded via ppchtex.noc which says ...
\let\normalunexpanded\unexpanded
\input
-regular,
[lmroman12-oblique]= lmromanslant12-regular,
etc. so older fonts are ok for context/luatex; while for xetex new fonts
are needed.
So if we ship the old or the new one there is no problem with the one or
the other?
not for luatex/context
Hans
the context situation).
ConTeXt would be happy to have the \supressfontnotfounderror fix
available (which means: happy to have a binary version of XeTeX later
than the one in TL 2007), but should work OK with the old one with
some semi-serious time penalty. If one also forgets all the other nice
bug
;-))) It does not
happen often anyway.
I really wonder how (if at all) LuaTeX is going to work on MikTeX ...
:) ConTeXt is broken there already, and ConTeXt is the only tool that
really benefits from LuaTeX (apart from some of your tools on TL). The
new search capabilities are likely to break
--generate
LuaTools | loading configuration file
/Users/mojca/context/tex/texmf/web2c/texmfcnf.lua
LuaTools | loading
/Users/mojca/context/tex/texmf/web2c/texmf.cnfShould I create the
cache path /texmf-cache? [yes|no] [no]
every time, independent on whether I answer with yes or no. And
everytime cache
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman
Am 22.08.2009 um 13:47 schrieb Oliver Buerschaper:
What's more important, the exit status of the context command is 0
(via echo $?) indicating that there was no problem at all! This
might turn out problematic as soon as documents are processed in a
batch run ... (like e.g. a regression
*You* want to write a test suite for ConTeXt?
The test suite is there. There is even a script in the test suit
that compares the outputs of two versions at pixel level. All we
need is people to submit tests and then someone to monitor the test
suite. See
http://wiki.contextgarden.net
hi,
context in combination with luatex is quite the way to go for me, but i have
one thing that i would love to see inside context:
unicode-mathhttp://github.com/wspr/unicode-math!
the guys there are making a good job of mapping tons of unicode sequences to
latex commands, so we should really
and then rebuild the format.
I can revisit it now for luatex:
this should still work for TeX macros but not for Lua functions, I
believe.
already there for a while:
context --dumphash yourfile
context --dumpdelta yourfile
of course undocumented apart from context --help --expert
yes, but what
at the beginning of context.tex and then rebuild the format.
I can revisit it now for luatex:
this should still work for TeX macros but not for Lua functions, I
believe.
already there for a while:
context --dumphash yourfile
context --dumpdelta yourfile
of course undocumented apart from context --help
On Fri, Oct 8, 2010 at 10:58, Norbert Preining prein...@logic.at wrote:
On Fr, 08 Okt 2010, Taco Hoekwater wrote:
right? (there *is* the weirdness that for texlive, the texmfcnf.lua
lives in the 'luatex' package, not in 'context', but that is just
a minor packaging issue).
I think we
Hi,
the pgfplots module t-pgfplots.tex lacks an \unprotect \protect
pair, which causes a catcode error in the file
numtable/pgfplotstable.code.tex on lines 1042-1045:
{
\catcode`\^^I=12
\gdef\pgfplotstablesave@impl@TAB{^^I}
}
Suggested fix:
--- texmf-modules/tex/context/third
On Di, 25 Dez 2012, Martin Schröder wrote:
First report: Current context from TeX Live breaks with this luatex:
$ context test.tex
/usr/bin/mtxrun:15228: attempt to index field 'loaders' (a nil value)
A known fallout of lua 5.2
Hansfixed in next beta/Hans
Better to be fixed
On 6/30/2013 4:24 PM, Sanjoy Mahajan wrote:
Partly to test Norbert's TeXLive 2013 packages for Debian, I just
installed the whole set of packages, which include Context MkIV
2013.04.20. With it I get an error not present with the older (2012)
format, namely that the internal conversion of mps
}
Wolfgang
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
--
-
Hans Hagen | PRAGMA ADE
the sources via anonymous svn:
svn co --username anonsvn --password anonsvn \
https://foundry.supelec.fr/svn/luatex/tags/beta-0.85.0
Bugs and feature requests can be added to the issue tracker at
http://tracker.luatex.org
When you use context or latex you need
On 7/23/2016 9:46 AM, Wolfgang Schuster wrote:
Hi Hans,
I saw you added \beginvbox (line 2928) etc. to the file, can you also
add \beginvtop etc.
sure. btw, these changed / additions are mostly because i'm cleaning up
the context namespace ... so 'context' has a limited set of functions
rttext
\starttestdescription{Ward}
\input ward
\stoptestdescription
\stoptext
%% end example
Wolfgang
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-c
Idris Samawi Hamid ادريس سماوي حامد <mailto:idris.ha...@colostate.edu>
17. Mai 2017 um 20:21
On Wed, 17 May 2017 08:15:11 -0600, Wolfgang Schuster
<schuster.wolfg...@gmail.com> wrote:
This is what I get from running
context x-setups-generate.mkiv
varia
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
derstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----
> ___
> dev-context mailing list
> dev-context@ntg.nl
> https://mailman.ntg.nl/mailman/listinfo/dev-context
>
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
Hi,
From my understanding, there are some superfluous quotes in
context/base/mkiv/grph-con.lua, cancelling the proper quoting done by
validcommand in context/base/mkiv/util-sbx.lua.
For my document, it tries to run something like (the space in the
'Google Drive' directory breaks the generation
nature of xml processing via lua, that is
not really an option for me, but even if I could make that work for me,
I do not like having to write
context(‘{‘)
...
context(‘}‘)
in a cld file. To me, that feels like it sort of defeats the purpose.
I can easily define a command, of course, like this:
processing via lua, that is
not really an option for me, but even if I could make that work for me,
I do not like having to write
context(‘{‘)
...
context(‘}‘)
in a cld file. To me, that feels like it sort of defeats the purpose.
I can easily define a command, of course, like this:
\def
question is. Is there besides codes any documentation how
linenumber placement works inside context and how far the backend
exporter hooks into this process at all? If codes only which source
files should i read to understand how things work. And how things
change between pdf and xml/xhtml export
Hi,
> On 3 Nov 2020, at 18:21, Tomas Hala wrote:
>
> Hi all,
>
> recently, in the ConTeXt list someone asked how to install Esperanto.
>
> I wanted to advise him, so I tried to do it on my computer and
> I came across the following problem:
>
> According to th
been implemented in late November.
Ah, ok. Thanks!
>
> Marco
> _______
> dev-context mailing list
> dev-context@ntg.nl
> https://mailman.ntg.nl/mailman/listinfo/dev-context
—
Taco Hoekwater E: t...@bittext.nl
genderfluid (all pronouns)
____
is the right way to do it.
Many thanks for your excellent work,
Pablo
--- /context/tex/texmf-context/doc/context/sources/general/manuals/xml/xml-mkiv-expressions.tex 2021-07-27 19:40:31.249792000 +0200
+++ /xml-mkiv-expressions.tex 2022-05-21 18:33:10.172268738 +0200
@@ -103,14 +103,14
Dear Mojca (and also Hans, off-list),
thank you for your helpful feedback. We updated LaTeX3, so that it
detects ConTeXt by the existence of the `\contextversion` command:
- https://github.com/latex3/latex3/pull/1114
- https://github.com/latex3/latex3/pull/1117
Best,
Vit
On Sat, Jul 23, 2022
Max Chernoff submitted an update to the
lua-widow-control
package.
Version number: v3.0.0
License type: Mozilla Public License v2.0
Wants to be in ConTeXt distribution: yes
Wants to be synced with CTAN: yes
Summary description: Automatically remove widows and orphans from any
way
this can be corrected at the packaging end?
I will take a look at that, but note that the
context-doc-nonfree
packages has NOT been updated in a while, so it probably is in a bad
state wrt organization. Next upload will ship pdf uncompressed, and
hopefully fix these issues.
Can you
On Sat, 25 Jan 2020 23:58:27 +0100
Mojca Miklavec wrote:
> On Sat, 25 Jan 2020 at 23:40, Henri Menke wrote:
> >
> > > It would be really cool if ConTeXt LMTX had a/the official repository.
> >
> > There will never be an “official repository” for ConTeXt.
>
>
On 9/12/2021 1:15 AM, Sylvain Hubert wrote:
Dear ConTeXt Devs,
Here's a problem that I reported last year
(https://mailman.ntg.nl/pipermail/ntg-context/2020/099862.html
<https://mailman.ntg.nl/pipermail/ntg-context/2020/099862.html>) with a
wrong description. I thought that it had som
Hi,
I am still running this one:
ConTeXt ver: 2021.10.28 10:19 LMTX fmt: 2021.11.1 int: english/english
This is LuaMetaTeX, Version 2.09.26
because that matches the version installed on the wiki. So this may well be
outdated news, but
I noticed that on my machine (macos 11), using
Hans,
I attach a diff file correcting some typos in the sources of the “TeX
it” manual.
I hope it helps,
Pablo
--
http://www.ousia.tk
diff -u ctxbeta/tex/texmf-context/doc/context/sources/general/manuals/texit/texit-introduction.tex texit/texit-introduction.tex
--- ctxbeta/tex/texmf-context
Thanks for the hints, Hans. But the problem has been reproduced multiple
times after the last update.
The bug turns out to be not from within context. I just tried `touch
context-lmtx/tex` (in which there are texmf/, texmf-context/, etc.) and the
very same problem appears.
This is very weird
Gerben Wierda wrote:
Hans Taco,
There is a potental problem with ConTeXt on TL2007 and the € symbol
havig to do with changes in marvosym.
Charles,
could you make a non gtamacfonts test file and see if that works?
Because I do not kow how ConTeXt works. If you have such a file
Hi all!
Before leaving againg for 3 weeks in mountainous isolation I have
updated context and luatex. For luatex there is also an etch version.
Current versions:
luatex 0.22.0.svn080220-1.np.etch.1
context 2008.01.28-1
As usual, here is the full list:
texlive
at the usual location
deb http://people.debian.org/~preining/TeX/ context/
deb-src http://people.debian.org/~preining/TeX/ context/
Please give it a try.
I made tests and it passed all context/pdftex tests and the simple
context/luatex I am using.
Taco/Hans: Do you require
On Fr, 18 Apr 2008, Taco Hoekwater wrote:
I have just uploaded the archives for luatex 0.25.3, yet
On Fr, 18 Apr 2008, Taco Hoekwater wrote:
Hot on the heels of the luatex 0.25.3 release Hans has released
(yet another) new context current (the sixth or seventh this week).
Debian packages
\pdfmapline{=cmsy10 LMMathSymbols10-Italic enclmmathsy ReEncodeFont
lm-mathsy.enc lmsy10.pfb }
(it has to come after the font initialization, hence the ugly place)
Perhaps the minimals should ship the traditional math fonts (cc
dev-context), otherwise we could re-create the euler virtual fonts
Hi ConteXt people,
here a problem report from Herbert on MacOS, but it is the same on Linux
in tlpretest.
Thanks
Norbert
On Wed, 03 May 2017, Herbert Schulz wrote:
> Howdy,
>
> I know virtually nothing about ConTeXt but have a few very simple test files
> that I picked up fr
On 5/7/2019 9:10 AM, Hans Hagen wrote:
On 5/7/2019 6:42 AM, Wolfgang Schuster wrote:
Hi,
when I add new commands, options etc. to interface files I often run
context on the file itself to create a PDF to check the content but
for Luametatex this doesn't work anymore.
When I run ConTeXt
On 5/7/2019 9:15 AM, Wolfgang Schuster wrote:
Hans Hagen mailto:j.ha...@xs4all.nl>> schrieb am
Di., 7. Mai 2019, 09:10:
On 5/7/2019 6:42 AM, Wolfgang Schuster wrote:
> Hi,
>
> when I add new commands, options etc. to interface files I often run
> c
On 5/7/2019 6:42 AM, Wolfgang Schuster wrote:
Hi,
when I add new commands, options etc. to interface files I often run
context on the file itself to create a PDF to check the content but for
Luametatex this doesn't work anymore.
When I run ConTeXt like this
context i-framed.xml
I
On 4/19/2019 9:06 PM, Kevin Boulain wrote:
Hi,
From my understanding, there are some superfluous quotes in
context/base/mkiv/grph-con.lua, cancelling the proper quoting done by
validcommand in context/base/mkiv/util-sbx.lua.
For my document, it tries to run something like (the space
ff-topic stuff that they don't
> understand anyway. But that's just a wild guess.) In any case it's
> true that most of the discussions happen on ntg-context. And it's also
> true that the volume is relatively high there.
As of now, I know nearly nothing about ConTeXt, so I would not
understand most
[option=xml]{}
\stopTEXpage
\stoptext
Many thanks for your help,
Pablo
--- scite-context-lexer-xml.lua 2022-06-01 17:24:38.625976000 +0200
+++ context/tex/texmf-context/context/data/scite/context/lexers/scite-context-lexer-xml.lua 2022-06-02 16:37:30.112824947 +0200
@@ -13,7 +13,7 @@
-- todo
appended the *FULL* diff
Yes.
Can you please send me the defective pdf file AND the log file, and make
sure that you are running the current context installation.
Please find both attached, and also the test.tex.
b83544c506921438246ff26625569db9
/usr/share/texmf/fonts/enc/dvips/lm/lm-mathsy.enc
)
#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+
Status: Open
Priority: 3
Submitted By: Aditya Mahajan (adityam)
Assigned to: Nobody (None)
Summary: texexec --module does not honor --result
Resolution: None
Version: None
Category: scripts
Initial Comment:
texexec --module --mode=color --color tex/context
for pdftex.
After I finally managed to download test a bit, I'm really glad to
tell you that you were wrong this time ;)
Formats are now properly placed under xetex and pdftex subfolders (and
generated when one first compiles a document), so ConTeXt works with
both engines without any problems
| sort -u
done
$ utils/find-missfonts.sh
== ./tex/context/base/unic-037.tex/missfont.log ==
mktextfm UnicodeRegular25
[from logfile]
...
kpathsea: Running mktextfm UnicodeRegular25
/usr/share/texmf/web2c/mktexnam: Could not map source abbreviation U for
UnicodeRegular25.
/usr/share/texmf/web2c
Sanjoy Mahajan wrote:
It won't solve the issue during regression testing, because the
regression tests use the entire context tree as of a certain date (a
tex version of chroot). That includes using the ruby scripts from
that version. That's why I made the run-it.py wrapper despite knowing
On Mon, 5 Feb 2007, Sanjoy Mahajan wrote:
Here are output differences between 20070112 and 20070123, mostly to
test the regression tests. Here's how to decode it. The line
WARN: tex/context/base/math-pln.tex/test-001-20070112-20070123.report
means tex/context/base/math-pln.tex/test-001
that myself right now.
It is bad luck that the last-minute update to marvosym in texlive
breaks the marvosym support in context, but there is no way to fix
that any more.
Sorry for that, but in fact I didn't think about that ConTeXt us the old
marvosym interface? So it could have been broken since
be OK!
Proposed changes:
* doc/taspresent - doc/context/third/taspresent
This really is important!
* tpm/t-taspresent.tpm is absent
I believe I wrote down how to create one in the Epen binder,
the file is important because it acts as a manifest.
* the source for the user manual
Hi Hans!
I am packaging up the latest context release for Debian, and have some
questions before releasing it:
- luatools and mtxtools is missing from scripts/context/unix/stubs, is
this by intention or by error?
- the debian packages ship additional stubs for:
pdftrimwhite texfind
Hi all!
I am trying to compile luatexref-t.tex from svn source but:
$ texexec luatexref-t.tex
...
(mpgraph.mp
! Number is too large (1).
l.4 _special_div_ := 1
;
I have
luatex 0.11.2
context 2007.09.28
metapost 1.00
Any idea where this is coming from?
Best
to
control the execution of those scripts (mktextfm, mktexmf, mktexfmt,
mktexpk) from C code without patching kpathsea.
I believe all of those scripts should be off on a modern installation.
and the second one (without that setting int exmf.cnf) still remains:
ConTeXt constantly complains about
produced!
I am using luatex snapshot-0.23.0-2008031110 and ConTeXt 2008.03.04
Works here without problems.
ConTeXt ver: 2008.03.11 14:48 MKIV fmt: 2008.3.11 int: english/english
This is LuaTeX, Version snapshot-0.23.0-2008030910
Thanks for checking. Must be something wrong in my setup. I
will ship context
2008.04.11 with this bug, since I cannot expect people to fix their
documents for a specific version.
So I will wait before making new packages.
Thanks and all the best
Norbert
---
Dr. Norbert Preining
Duncan Hothersall wrote:
only run the setuptex script in the shell in which you want to run
ConTeXt. These environment variables aren't meant to be set globally
(again, AFAIK), they are meant to be set for the session. To me this is
what makes the minimals highly portable and easy
===
This test also did not work with my previous context installation (the
2008.05.21 packages). With either the current or previous packages, the
equation comes out in Euler but as a^2 b^2 + c^2: (i.e. missing equals
sign, and the period replaced by a colon).
Works for me
It works fine with context, BTW.
On Wed, Jun 10, 2009 at 02:49:46PM +0300, Khaled Hosny wrote:
The following sample would crash luatex using context distriputed
luatex-plain format:
%%%
\font\arab=SimpleNaskhi.ttf:script=arab;language=dflt;mode=node;+init;+medi;+fina;+rlig;+liga;+mark\arab
Aditya Mahajan wrote:
When I started using context, I was surprised that context did not have
anything for optional arguments. We could have something like
\definesinglearugment\foo[#1]#2{...}
to be equal to
\def\foo{\dosingleargument\dofoo}
\def\dofoo[#1]#2{...}
and
\definesingleempty
Dear wise guys,
the other day I found myself caught in a trap that might be a frequent source
of puzzlement for the casual ConTeXt user :-)
I had replaced an OpenType font in the usual OS directory by a new version.
Typesetting documents using that font produced surprising results... the PDF
On Fri, Jun 18, 2010 at 10:05, luigi scarso wrote:
I mean: one should not simply copy an opentype font into (context)
system and expected things to work.
Why not? (Do you really want to make things more difficult than they
can be on purpose? Who is going to install polish fonts then ... ?)
I
On 18-6-2010 11:05, Mojca Miklavec wrote:
On Fri, Jun 18, 2010 at 10:48, Hans Hagen wrote:
is there unique info in the font file that we can use? version number that
is guaranteed unique? if so, we can pass that to the backend
That almost reminds me on version numbers in ConTeXt files
Am 30.06.10 12:57, schrieb Marius:
Hello,
I think that the best way is to put command syntax description just
before its definition in the context file. This way it will be easier
to keep it always in sync with the code. And most important point here
is that it must be in sync always
and the same will happen
with the system you suggest.
That's why I'm eventually going to do this:
http://archive.contextgarden.net/message/20100508.204345.b5003312.en.html
Perhaps using tex-files like this:
http://pmrb.free.fr/tmp/context-commands/
Perhaps in this directory:
http://foundry.supelec.fr
On 2 July 2010 10:41, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 30.06.10 12:57, schrieb Marius:
Hello,
I think that the best way is to put command syntax description just
before its definition in the context file. This way it will be easier
to keep it always in sync
On Mi, 06 Okt 2010, Aditya Mahajan wrote:
restrictions that you mention, or is this also the right place to upload
normal context modules. If so, is this going to eventually replace
modules.contextgarden.net upload system?
context modules preferrably are uploaded to CTAN and thus will
find
Hi,
On 10/06/2010 12:50 PM, Mojca Miklavec wrote:
Taco, once you are back to this ... the repository works much better
now, but ConTeXt doesn't. I thought at first that
/usr/local/texlive/2010/texmfcnf.lua
was not adapted yet, but then I figured out that I have
/usr/local/texlive
be tested with an existing minimal:
- delete the context path under texmf-cache
- unzip cont-tmf.zip in texmf-context
- copy mtxrun.lua from the scripts path to the bin path
- update the texmfcnf.lua file (just copy contextcnf.lua)
- remake the file database
In logs you will notice prefixes like
Math accents seems to be broken in all OpenType math fonts:
* wide accents don't show at all; ConTeXt is looking for non-existent
characters (U+FE302 for example).
* regular accents don't work with Asana because ConTeXt is looking for
the spacing accents which it does not have
I think
Hi,
For those with access to it, I've put a new beta on the ftp server. The
main 'change' is that I changed all (still left) tex.sprint etc calls
into calls in the context namespace. Todo is to create a namespace for
helpers. The advantage (and reason for doing it) is that tracing
On 11/4/2012 10:50 AM, Wolfgang Schuster wrote:
Hi Hans,
the scripts to generate the documentation from Lua files don’t work in the beta.
When I run
context --ctx=x-ldx x-ldx.lua
not even the xml file “x-ldx.ldx” is generated.
When I use the two step method with
mtxrun --internal x
Hi Taco,
On Mo, 24 Dez 2012, Taco Hoekwater wrote:
I have just uploaded the archives for a new luatex release, 0.74.0.
First report: Current context from TeX Live breaks with this luatex:
$ context test.tex
/usr/bin/mtxrun:15228: attempt to index field 'loaders' (a nil value)
$
I guess
instead of the normal
local flush = texsprint
That way, I can look in dumpfile.txt to make sure that the correct ConTeXt
code is generated. Is there any chance that you could offer a
tracker/messaging
feature with similar functionality? Patching cldf-ini.lua is not nice ;)
\enabletrackers
Hans,
in some printers in which duplex printing is enabled by default, a
"single" value for duplex printing is required to disable it.
I attach the patch that implements this.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
--- 11192015ctxbeta/tex/texmf-context/tex/context
Hi Hans,
I just tried this with a fairly new ConTeXt:
\starttext
\message{pdfannot: [\meaning \pdfannot] pdflastannot: [\meaning \pdflastannot]
\stoptext
reports
pdfannot: [\relax] pdflastannot: [\count1160]
which is not really useful. It actually hit me inside a file
On Mon, Oct 10, 2016 at 1:54 PM, luigi scarso <luigi.sca...@gmail.com> wrote:
> tex/texmf-context/tex/context/interface/mkiv$ xmllint *.xml >/dev/null
> i-common-value.xml:14: parser error : Opening and ending tag mismatch:
> parameter line 10 and define
>
>
df.majorversion()
Many thanks for your fix, Hans.
>> This is LuajitTeX, Version 1.05.0 (TeX Live 2017)
>>
>> Is this also an issue with more recent LuaTeX versions?
>
> Unrelated . The engine as well are context are made ready for pdf
> version 2 so that's why you
On 1/31/2018 7:14 PM, Pablo Rodriguez wrote:
Hans,
the attached patch comes from code that Christoph Reller kindly provided
me with to fix comments in TeX, MP and Lua
(https://bitbucket.org/philexander/context-highlight/issues/2/highlight-for-tex).
* It formats the whole comment (both
Alan Braslau writes:
> Being open source does not require that there be a "repository",
> rather that the source (to Context) be freely available.
Yes, being open source is not equivalent to having an official
repository. On the other hand, official repositories with pull acc
901 - 1000 of 2156 matches
Mail list logo
