Bonjour.
Should not the anuswâra be over the o in such a case?
Regards,
Yves
Le 26 août 14 à 17:37, François Patte a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
How can I get this ligature: दोऽंश
It seems that the anusvara cannot be put over the avagraha...
Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 27/08/2014 08:20, Yves Codet a écrit :
Bonjour.
Should not the anuswâra be over the o in such a case?
No, I don't think so: it a sandhi rule: one word ended by aḥ gives o
if the following word begins by a voiced letter, in case of this
letter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 26/08/2014 18:00, Jonathan Kew a écrit :
On 26/8/14 16:37, François Patte wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Bonjour,
How can I get this ligature: दोऽंश
It seems that the anusvara cannot be put over the avagraha...
I know this rule :) But avagraha doesn't stand for any sound, it only
marks elision (or contraction) and can be omitted, that's why it can't
bear anuswâra, which would explain why fonts don't have any rule to
place an anuswâra over an avagraha. If you have John Smith's
electronic edition
One of our people is getting a crash in xetex, which I can't reproduce.
It's very odd, since afaik we're both using the same input files, the
same instance of xetex, the same TeXLive 2014 files, and so forth, and
running on the same machine. Clearly s.t. is different, but I'm not
sure what,
It may be so, it looks like a postscript error message and run is a
postscript operator that executes a file contents.
2014-08-27 23:27 GMT+02:00 maxwell maxw...@umiacs.umd.edu:
One of our people is getting a crash in xetex, which I can't reproduce.
It's very odd, since afaik we're both using
Hi Mike,
On 28/08/2014, at 7:27 AM, maxwell wrote:
One of our people is getting a crash in xetex, which I can't reproduce. It's
very odd, since afaik we're both using the same input files, the same
instance of xetex, the same TeXLive 2014 files, and so forth, and running on
the same
The problem is that unlike TeX, postscript error messages show the
contents of the stack but not the operator that triggered the error
message. You can see that the top of the stac contains font related
objects. The font itself is a dictionary (--dict--) and it contains
other dictionaries.
On 2014-08-27 17:51, Ross Moore wrote:
The problem looks to be with Ghostscript.
You may be using different versions, so check that first.
Thanks! (and to Zdenek for the similar suggestion)
That certainly makes sense. We do have two versions of ghostscript on
our linux machine, 8.70 and
On 27/8/14 22:51, Ross Moore wrote:
Hi Mike,
On 28/08/2014, at 7:27 AM, maxwell wrote:
One of our people is getting a crash in xetex, which I can't reproduce. It's
very odd, since afaik we're both using the same input files, the same instance
of xetex, the same TeXLive 2014 files, and so
In the past I experimented with postscript. I used to write PS code
directly in my text editor and interpret it by ghostscript so I know
how the error messages look like.
2014-08-28 0:16 GMT+02:00 maxwell maxw...@umiacs.umd.edu:
On 2014-08-27 17:51, Ross Moore wrote:
The problem looks to be
On 2014-08-27 18:16, Jonathan Kew wrote:
I'm curious why Ghostscript is being run at all. Is it trying to
convert a PostScript or EPS graphic, when you intended to use a PDF
directly? Maybe one of the users has a different version of the
graphics package, or even just a configuration file, in a
12 matches
Mail list logo
