From: Alan Bowen <acbowen@princeton.edu>
Subject: Re: Re[2]: Greek font in Footnote problem
Date: Thu, 20 Jan 2005 18:01:47 -0500 [thread overview]
Message-ID: <42FE5D22-6B37-11D9-831D-00306544E64E@princeton.edu> (raw)
In-Reply-To: <1156143079.20050119130558@iol.it>
Guiseppe and Thomas—
A quick run though with my test file indicates that
\def\localgreek#1{\scantokens{\Gf\enablegreek#1}}
will work in the body text, but only if one enters the Greek code using
double braces as follows:
{\localgreek{Greek code}}
With single braces either the Greek turns on and stays on thereafter or
the breathings get messed up with initial spaces.
Still no Greek in the footnotes, though.
Alan
On Jan 19, 2005, at 7:05 AM, Giuseppe Bilotta wrote:
> Wednesday, January 19, 2005 Thomas A.Schmitz wrote:
>
>
>> On Jan 17, 2005, at 4:54 PM, Giuseppe Bilotta wrote:
>
>>> enablegreek relies on catcode changes, so it cannot work inside
>>> commands. It should be redefined to make use of e-TeX's
>>> \scantoken feature so that it can re-parse its input.
>
>> Giuseppe,
>
>> I'll be too bust the next three weeks to look into this, but would
>> love
>> to correct my quick and dirty hack. Can you give me a hint where I can
>> learn more about \scantoken and how I can implement it for my Greek
>> stuff?
>
> Ehehehe. The reason why I was so generic in my answer is
> precisely the same :)
>
> Something like
>
> \def\localgreek#1{\scantokens{\Gf\enablegreek#1}}
>
> could work.
>
> --
> Giuseppe "Oblomov" Bilotta
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-01-20 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 12:31 Alan Bowen
2005-01-17 15:54 ` Giuseppe Bilotta
2005-01-19 9:52 ` Thomas A.Schmitz
2005-01-19 12:05 ` Re[2]: " Giuseppe Bilotta
2005-01-20 23:01 ` Alan Bowen [this message]
2005-01-21 19:29 ` h h extern
2005-01-22 8:18 ` Thomas A.Schmitz
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=42FE5D22-6B37-11D9-831D-00306544E64E@princeton.edu \
--to=acbowen@princeton.edu \
--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).