ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: IPA/TIPA support in Context?
Date: Sat, 3 Dec 2005 12:55:09 +0100	[thread overview]
Message-ID: <D37538A3-00AA-49A4-B62C-ECF818D9008B@fiee.net> (raw)
In-Reply-To: <43904FCB.3000100@comp.lancs.ac.uk>

>>> I think the answer is zero or nearly zero. If you have a bit of
>>> patience, I can do a port of tipa.sty (quite easy), but it will
>>> take some time before I can start on it.
>> in the process taco and i can discuss low level support issues as  
>> well; it's all a matter of demand and time; of course after a  
>> port, taco would mildly force you to write an article for the MAPS -)
> I had done some basics with the font/encoding parts before. I  
> solicited feedback on what next parts/features were important to  
> tackle next, and I got nowhere. I'll try to dig this up and send it  
> to you guys in the next few days. (Remind me if you don't hear from  
> me!)

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.


Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)

  reply	other threads:[~2005-12-03 11:55 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 [this message]
2005-12-03 12:00         ` Taco Hoekwater
2005-12-05 16:10           ` Jason Knight
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=D37538A3-00AA-49A4-B62C-ECF818D9008B@fiee.net \
    --to=hraban@fiee.net \
    --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).