ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jason Knight <jasoneknight@gmail.com>
Subject: Re: IPA/TIPA support in Context?
Date: Mon, 5 Dec 2005 10:10:35 -0600	[thread overview]
Message-ID: <cd8d4b080512050810k6497aa9fl7de97654b6c5069a@mail.gmail.com> (raw)
In-Reply-To: <439188F0.8020601@elvenkind.com>

On 12/3/05, Taco Hoekwater <taco@elvenkind.com> wrote:
> Henning Hraban Ramm wrote:
> >
> > Perhaps this is a stupid question, but do we need more than some
> > definitions in the Unicode encoding vectors and typescripts for some
> > fonts?
> > Is (T)IPA support about more than using some phonetic chars?
> > Please enlighten me.
>
> AFAICT, there are:
>
>    - 2 new font encodings needed (T3 and T3S), with associated
>      named characters
>    - a set of font definitions
>    - unicode tables (for utf input) need extension
>    - there are some macros in IPA for special input
>
> That's about it for the basic TIPA font support, I guess.
>
> For proper linguistic work, you need a large set of extra macros,
> but those are not in the LaTeX tipa.sty either.
>
> Greetings, Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

I've done some work with tipa under LaTeX as a beginning linguistics
student, though I didn't get into the guts at the time.

This threaed gets me thinking: how far away from "proper" is the tipa
package under LaTeX? How much work is a "proper" implementation likely
to be?

I'm in some ways a beginner "under the hood", but I'm pretty motivated
to get proper support in place.

Taco, your list above includes some stuff I'm unfamiliar with (T3
encoding, macros for IPA input), so I don't know how extensive the
work is likely to be. Which would be easier: scrap and re-write or
adapt?

--
Jason Knight
Systems-Analyst-at-large
"They fix 'em, I break 'em. Thus, analysis."

  reply	other threads:[~2005-12-05 16:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 21:12 Jason Knight
2005-12-02  8:45 ` Taco Hoekwater
2005-12-02 13:27   ` Hans Hagen
2005-12-02 13:44     ` Adam Lindsay
2005-12-03 11:55       ` Henning Hraban Ramm
2005-12-03 12:00         ` Taco Hoekwater
2005-12-05 16:10           ` Jason Knight [this message]
2005-12-06  8:15             ` Hans Hagen
2005-12-06 18:59               ` Steve Peter
2005-12-07  7:48                 ` Taco Hoekwater
2005-12-05 15:56     ` Jason Knight
2005-12-01 16:00 Jason Knight

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=cd8d4b080512050810k6497aa9fl7de97654b6c5069a@mail.gmail.com \
    --to=jasoneknight@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).