From: Hans Hagen <pragma@wxs.nl>
Subject: Re: TIPA in Context
Date: Wed, 26 May 2004 18:32:27 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040526183117.02dd0280@server-1> (raw)
In-Reply-To: <20040526133241.6549@mail.comp.lancs.ac.uk>
At 15:32 26/05/2004, Adam Lindsay wrote:
>Interesting problem.
indeed
>I just looked at <http://www.tug.org/TUGboat/Articles/tb17-2/tb51rei.pdf>
>
>Yes, it sounds like there's a way of using the TIPA *font* in ConTeXt.
>However, it seems like the job of adapting all of the TIPA package and
>the T3 encoding for ConTeXt is not trivial. Still, it seems like some
>degree of support can be hacked.
>
>First off, for your dictionary, what do you use for input?
>is it "F@n" or "\textphi\textschwa n"?
that's the right approach: what do you want, what interface suits best; i
can provide hooks/low level features if needed; so go ahead !
Hans
next prev parent reply other threads:[~2004-05-26 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 12:32 sjoerdsiebinga
2004-05-26 13:32 ` Adam Lindsay
2004-05-26 16:32 ` Hans Hagen [this message]
2004-05-27 8:10 ` sjoerdsiebinga
2004-06-04 10:18 ` Adam Lindsay
2004-06-05 7:08 ` Henning Hraban Ramm
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=6.0.1.1.2.20040526183117.02dd0280@server-1 \
--to=pragma@wxs.nl \
--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).