From: Drazen Baic <dpeterx@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \useURL not working with '#' and '_' in URL in newest beta
Date: Wed, 22 Apr 2009 17:40:07 +0200 [thread overview]
Message-ID: <6607a2f30904220840v5b6def01u7b9cdc2765780171@mail.gmail.com> (raw)
In-Reply-To: <49EEBD57.6040102@wxs.nl>
On Wed, Apr 22, 2009 at 8:46 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Mojca Miklavec wrote:
>>
>> On Tue, Apr 21, 2009 at 18:45, Drazen Baic wrote:
>>>
>>> Hello,
>>>
>>> URLs with '#' or '_' in the URL worked fine with LuaTeX, Version
>>> snapshot-0.37.0-2009033116 and ConTeXt 2009.04.06 21:42
>>> and still work with the newest beta LuaTeX, Version
>>> snapshot-0.39.0-2009041623 and ConTeXt 2009.04.21 16:11 when
>>> compiled with '--xtx'. When compiled with '--lua' I got this error:
>>
>> I don't know if this is related, but when I tried to recompile some
>> mkiv document today, lots of characters have been missing from output.
>> Example:
>>
>> \starttext
>> \startMPcode
>> u := 1cm;
>> draw \sometxt{a\{b\}} shifted(1u,0u); % no braces
>> \stopMPcode
>> \stoptext
>>
>> I remember having problems with at least {, }, #, & and with the usage
>> of the following macro inside metapost:
>>
>> % outside:
>> \def\combine#1{\hbox to .5em{}\hbox to
>> 0pt{\hss\color[red]{\mframed[frame=off]{#1}}\hss}\hbox to
>> 0pt{\hss\color[darkgray]{o}\hss}}
>>
>> % usage inside \sometxt in metapost:
>> \combine{\textcaron}
>>
>> But I had no time to debug.
>
> --lua ? don't you use 'context' ? (as context will call texexec when the
> topline mentiones pdftex/xetex as engine, i now always use it in calls from
> the editor instead of texexec)
thank you for the tip. I was always using texexec --lua in my vim/macvim config.
> if you're in a hurry you can use \nonknuthmode (makes _ ^ in textmode normal
> letters, while \donknuthmode reverts them)
>
> Hans
I'm not in a hurry but thanks again. I was just testing the newest
beta to see if
index creation is working again.
Regards,
Drazen
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2009-04-22 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 16:45 Drazen Baic
2009-04-22 1:19 ` Mojca Miklavec
2009-04-22 6:46 ` Hans Hagen
2009-04-22 15:40 ` Drazen Baic [this message]
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=6607a2f30904220840v5b6def01u7b9cdc2765780171@mail.gmail.com \
--to=dpeterx@googlemail.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).