El oct 27, 2011, a las 3:32 a.m., Kattamuri Ekanadham escribió:
Last year, we prepared itrans-tel.map and itrans-tel.tec files and Shrisha
Rao has uploaded them to the CTAN library and should be available there.
(see note below). I use XeLatex regularly to compose Telugu and Sanskrit. If
On 27 October 2011 16:52, Shrisha Rao sh...@nyx.net wrote:
Being able to use UTF-8 codings in such scripts to produce outputs in other
scripts would require n × n mappings, as against 1 × n if the input is only
in ITRANS.
Actually, 1×n is all that is required, as long as the mappings are
El oct 27, 2011, a las 12:36 p.m., Andrew Moschou escribió:
On 27 October 2011 16:52, Shrisha Rao sh...@nyx.net wrote:
Being able to use UTF-8 codings in such scripts to produce outputs in other
scripts would require n × n mappings, as against 1 × n if the input is only
in ITRANS.
On Thu, Oct 27, 2011 at 1:01 PM, Andy Lin kir...@gmail.com wrote:
I've looked at the tipa code, and basically what they did was redefine
\:, etc. to produce the characters. With that in mind...
Add this to your tex document...
Thank you for your hard work on my behalf. And thank you for the
Hi Phillip,
We are not talking about native English speakers here, but legal language.
How a court will decide, depends on many factors.
Either way, we can only speculate what will happen and we do not know
the true intension of the author.
regards
Keith.
Am 26.10.2011 um 10:49
On Thu, Oct 27, 2011 at 5:16 PM, Peter Dyballa peter_dyba...@web.de wrote:
Because it's too late then.
Thank you for your explanation.
In that case then I think I will define the map file with the TIPA
standard \:t, but I will also define /:t. The \:t (in conformance with
TIPA 1.3) can be used
Am Thu, 27 Oct 2011 16:06:52 +0800 schrieb Daniel Greenhoe:
If I can do this conversion from the command line, why can't fontspec
handle it correctly? That is, before fontspec tries to interpret a
sequence beginning with \ as a command, why can't it first check to
see if the sequence is up