From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: mplib & undefined commands
Date: Sun, 13 Apr 2008 13:23:12 +0200 [thread overview]
Message-ID: <6faad9f00804130423u2c30e384jcb6a60636c42b6b3@mail.gmail.com> (raw)
In-Reply-To: <480066FC.7060609@wxs.nl>
Hi,
On Sat, Apr 12, 2008 at 9:38 AM, Hans Hagen wrote:
>
> > 2.) undefined command
> > \forceMPTEXcheck{put_text}
>
> ok, i will add a fake
Thanks.
>
> > I have now used a wrapper to skip that line in LuaTeX (btw: what's the
> > suggested \if clause or \beginNOLUATEX to check for luatex/mkiv?) Does
> > it make sense to define \let\forceMPTEXcheck\empty in mkiv perhaps?
>
> best make a
>
> yourmodule.tex
> yourmodule.mkii
> yourmodule.mkiv
>
> and in the tex file adds:
>
> \loadmarkfile{yourmodule}
OK, once I rewrite some more code than a few lines, I will split it
(but now there are really only minor, one-line patches).
> > 3.) undefined command \obeyMPlines. I actually forgot why I needed it,
> > but according to the comment:
> > \obeyMPlines % <- no longer a problem
> > \def\obeyedline{}% <- thanks to this
> > I simply commented out the first line and hoped for no problems in mkii
>
> ok, another fake
Thanks. Still - I don't know if it's still needed at all and what
exactly it was used for (maybe metapost has complained about too long
lines long time ago).
> > 4.) It seems to work without problems now, except for one tiny detail
> > that I get in the final PDF.
> > [do we need TeXtexts in MkIV]
> >
> > What is that supposed to mean?
>
> well, that everything now can be 'textext'
>
>
> > I need to admit that I have the following piece of code in the module
> > (in case that matters). Maybe I'm the only one who uses it, so if you
> > have any idea how to modify the macros to make
> > \sometxt[gp][iwona,14pt]{text} work in mkiv, I will happily drop the
> > old code/replace it for mkiv.
>
> hm, so \sometxt is not working? i thought that i tested it (maybe not
> ... too much to test)
\sometxt is working, only some Aditya's extensions complain. I will
test a bit, try to rewrite some bits and pieces, collect the missing
parts and report back.
>
> > \long\def\redofiltersometxt[#1]%
> > {\doifnextcharelse[{\reredofiltersometxt[#1]}{\redodofiltersometxt[#1]}}
> >
> > \long\def\redodofiltersometxt[#1]#2%
> > {\increment\txtcounter
> > \TeXtext[#1]\txtcounter{#2}%
> > \filtersometxt}
> >
> > \long\def\reredofiltersometxt[#1][#2]#3%
> > {\increment\txtcounter
> > \TeXtext[#1]\txtcounter{\switchtobodyfont[#2]\strut#3}%
> > \filtersometxt}
>
> i think that we have it in the core
You have added the ability to use
\sometxt[something]{abc}
with a background definition of:
\definetextext[something]{\strut}
but I wanted to have two square brackets and Aditya has written a
small patch which does that. Let me explore a bit more in the new mkiv
sources and report back.
> anyhow, just collects what does not work
>
> (btw, i fixed something in textext ... i used to work only for code
> passed as mpgraphic, but now it works also with libraries and so)
Thanks :) I didn't notice any weird behaviour so far, but I'm glad
that it's away before I started complaining about it :) :P
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-13 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 15:39 Mojca Miklavec
2008-04-12 7:38 ` Hans Hagen
2008-04-13 11:23 ` Mojca Miklavec [this message]
2008-04-13 11:29 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6faad9f00804130423u2c30e384jcb6a60636c42b6b3@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).