ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: TIPA in Context
Date: Fri, 4 Jun 2004 11:18:21 +0100	[thread overview]
Message-ID: <20040604111821.15636@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <1085645454.40b5a28e9169c@webmail.zonnet.nl>

[-- Attachment #1: Type: text/plain, Size: 3003 bytes --]

sjoerdsiebinga@zonnet.nl said this at Thu, 27 May 2004 10:10:54 +0200:

>Citeren Adam Lindsay <atl@comp.lancs.ac.uk>:
>> 
>> First off, for your dictionary, what do you use for input?
>> is it "F@n" or "\textphi\textschwa n"?
>>
>Al my input is in commands like " \textschwa".


Okay, that's useful to know. Getting the encoding right was my first priority.

>> Are all of your IPA commands contained within a \textipa{} macro?
>>
>Only a minority of my commands are within the \textipa{} macro.

Okay. I do wonder how you set off your phonetic spellings from your main
text, though.
 
>> Which of the special macros do you use? \* \; \: \!
>>
>None

Good. We'll leave them for later. :)
 
>> Do you use the \super macro much? Does it ever get nested? (Hans's
>> \high{} macro acts a little differently.)
>> 
>I use the \super macro quite often but it is not nested in the \textipa{}
>macro.

I meant "Does the super macro ever get nested within another super macro?
" \high{\high{}} doesn't act exactly like \super{\super{}}, but we'll
leave that until later.

>
>> ...but I presume you want deeper support than that. Which do you need
>> first?
>
>A great number of symbols I use (especially the Indo-European ones) are
>only available through the IPA 
>commands, therefore it seems that I need some deeper support.  I read

Hmm. Maybe yes, maybe no. I'm a bit concerned about the TS3 encoding (the
tipx supplemental fonts). That'll take a bit more work.

>your UnicodeSymbol pdf  about unicode 
>mapping and wondered if there might be a similar way to map the TIPA font?

mmm... yes... I wonder the same thing. Does Unicode have all the coverage
you need, first of all?
In any case, Unicode support will be a bit more work than supporting the
nice TIPA fonts.

Last night I made an encoding, a typescript, and a couple quick "smart"
switches. I handle the basic character glyphs, but haven't touched the
accents yet. It would help to know where we need coverage there.

You can test the attached three files by running 'texexec --mode=demo m-tipa'.

Usage, for the time being, is:

\usemodule[tipa]
\usetypescript[tipa]
\setupbodyfont[reset]
\setupbodyfont[cmr,rm]
\starttext
Blah blah {\Phonetic bl@ Bl2} Blah.

Blah blah \textipa{bl\textschwa\ \textbeta l\textturnv} Blah.

{\bsx Blah blah {\Phonetic bl\textschwa\ \textbeta l\textturnv} Blah.}

\stoptext

Don't be silly and try to use math with this module, but please do try it
with a representative sample of your markup, and let me know which we
need to handle next.


Cheers,
adam
(Part of my interest in this is with fonts, sure, but I also have an
amateur interest in historical linguistics, and the link with english is
pretty clear... )

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay                      atl@comp.lancs.ac.uk
 Computing Dept, Lancaster University   +44(0)1524/594.537
 Lancaster, LA1 4YR, UK             Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[-- Attachment #2: m-tipa.zip --]
[-- Type: application/zip, Size: 8612 bytes --]

  reply	other threads:[~2004-06-04 10:18 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
2004-05-27  8:10   ` sjoerdsiebinga
2004-06-04 10:18     ` Adam Lindsay [this message]
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=20040604111821.15636@mail.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).