Re: [XeTeX] avagraha+anusvara ligature in devanagari
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 you - -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEUEARECAAYFAlP8qc0ACgkQdE6C2dhV2JU0vwCfdQprkg2EKxTDXGC/2Tr07J1k bGgAljtkLDBDByYf3yvqTUzIV0Xuh74= =B5HU -END PGP SIGNATURE- -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] avagraha+anusvara ligature in devanagari
-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 is a a, it is dropped and replace by an avagraha so: छेदः अंशः becomes चेदो ऽंशः and it will not be correct if the anusvara would be on the o. - -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlP9mqUACgkQdE6C2dhV2JUuVgCgo6FbEgNDb+tTJQztMFlgjCL6 b6IAoKJoKNcLzkwuq0Sge8qHkuGTGxs0 =skWY -END PGP SIGNATURE- -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] avagraha+anusvara ligature in devanagari
-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...
It probably depends on the font you're using. Experiment with some
alternatives... and if that fails, provide a minimal but complete
example for people to try.
No, it seems to depend on xelatex from texlive 2013:
$ xelatex -v
XeTeX 3.1415926-2.5-0..3-2013060708 (TeX Live 2013)
kpathsea version 6.1.1
couic
Primary author of XeTeX: Jonathan Kew.
Compiled with ICU version 51.1; using 51.1
Compiled with zlib version 1.2.7; using 1.2.7
Compiled with FreeType2 version 2.4.11; using 2.4.11
Compiled with Graphite2 version 1.2.1; using 1.2.1
Compiled with HarfBuzz version 0.9.15; using 0.9.15
Compiled with fontconfig version 2.10.93; using 2.11.0
Compiled with libpng version 1.5.16; using 1.5.16
Compiled with poppler version 0.22.2
And seems to be corrected in texlive 2014
Here is a MWE:
\documentclass[a4paper,11pt]{report}
\usepackage{fontspec}
\usepackage{polyglossia}
\setdefaultlanguage{english}
\setotherlanguage{sanskrit}
\setmainfont[Script=Latin]{FreeSerif}
\newfontfamily{\sanskritdmtrois}[Script=Devanagari,Mapping=velthuis-sanskrit]{%
Sanskrit 2003}
\newfontfamily{\freetype}[%
Script=Devanagari,%
UprightFeatures={Language=Sanskrit},%
BoldFeatures={Language=Sanskrit},%
Mapping=velthuis-sanskrit]{%
FreeSerif%
}
\newfontfamily{\nakula}[Mapping=velthuis-sanskrit]{%
Nakula%
}
\newfontfamily{\sahadeva}[Mapping=velthuis-sanskrit]{%
Sahadeva%
}
\newfontfamily{\siddhanta}[Script=Devanagari,Mapping=velthuis-sanskrit]{%
Siddhanta%
}
\newfontfamily{\english}{FreeSerif}
\begin{document}
{\Large \english Free Serif : } \hspace{5mm} {\Huge \freetype
chedo.a.msa}
\bigskip
{\Large \english Sanskrit 2003 : } \hspace{5mm} {\Huge
\sanskritdmtrois chedo.a.msa}
\bigskip
{\Large \english Sahadeva : } \hspace{5mm} {\Huge \sahadeva
chedo.a.msa}
\bigskip
{\Large \english Nakula : } \hspace{5mm} {\Huge \nakula chedo.a.msa}
\bigskip
{\Large \english Siddhanta : } \hspace{5mm} {\Huge \siddhanta
chedo.a.msa}
\end{document}
- --
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlP9nj0ACgkQdE6C2dhV2JXyOgCfRDxuHHbn+Mfc7VKlwG4UqHZ2
3twAnipDuQ1CE7zkyGQX1g87lcbbGVPj
=1KMn
-END PGP SIGNATURE-
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] avagraha+anusvara ligature in devanagari
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 of the Mahâbhârata, you will easily find several occurences of the particular case you're dealing with, for instance: 01058049a अथ ते सर्वशोंऽशैः स्वैर्गन्तुं भूमिं कृतक्षणाः Le 27 août 14 à 10:45, François Patte a écrit : -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 is a a, it is dropped and replace by an avagraha so: छेदः अंशः becomes चेदो ऽंशः and it will not be correct if the anusvara would be on the o. - -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlP9mqUACgkQdE6C2dhV2JUuVgCgo6FbEgNDb+tTJQztMFlgjCL6 b6IAoKJoKNcLzkwuq0Sge8qHkuGTGxs0 =skWY -END PGP SIGNATURE- -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] rangecheck in --run--
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, and this email is a query about what I should be looking for.
The error msg is:
--
Error: /rangecheck in --run--
Operand stack:
--dict:11/20(L)-- TT0 1 FontObject --dict:8/8(L)--
--dict:8/8(L)-- TimesNewRomanPSMT --dict:13/13(L)-- Times-Roman
Times-Roman
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1862 1 3
%oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop
--nostringval-- --nostringval-- 2 1 1 --nostringval--
%for_pos_int_continue --nostringval-- --nostringval-- false 1
%stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:1/20(G)-- --dict:76/200(L)--
--dict:76/200(L)-- --dict:106/127(ro)(G)-- --dict:286/300(ro)(G)--
--dict:22/25(L)-- --dict:4/6(L)-- --dict:26/40(L)--
Current allocation mode is local
Command /groups/tools/texlive/2014/bin/x86_64-linux/xelatex
-halt-on-error -output-directory=./LinguistInABox/output/latex
./LinguistInABox/output/latex/linguistInABoxGrammar.xetex -no-pdf died
with signal 13, without coredump
Signal 13 is Write on a pipe with no reader, Broken pipe.
I believe the crash is happening at the point xelatex is trying to embed
an existing PDF. If I'm right (we're going to verify it tomorrow), the
command that crashes is
--
\imgexists{list_intonation.pdf}{{\imgevalsize{list_intonation.pdf}{\includegraphics[width=\imgwidth,height=\imgheight,keepaspectratio=true]{list_intonation.pdf{}
-
Googling this:
xetex OR xelatex rangecheck in --run--
brings up about six msgs from 2011, which seem to be the same thread,
and afaict are irrelevant.
We're running the version of xetex that came with TeXLive 2014
(3.14159265-2.6-0.1) on Linux.
Any suggestions as to what I should be looking for?
Mike Maxwell
University of Maryland
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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 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, and
this email is a query about what I should be looking for.
The error msg is:
--
Error: /rangecheck in --run--
Operand stack:
--dict:11/20(L)-- TT0 1 FontObject --dict:8/8(L)--
--dict:8/8(L)-- TimesNewRomanPSMT --dict:13/13(L)-- Times-Roman
Times-Roman
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop
1861 1 3 %oparray_pop 1845 1 3 %oparray_pop --nostringval--
--nostringval-- 2 1 1 --nostringval-- %for_pos_int_continue
--nostringval-- --nostringval-- false 1 %stopped_push
--nostringval-- --nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:1/20(G)-- --dict:76/200(L)--
--dict:76/200(L)-- --dict:106/127(ro)(G)-- --dict:286/300(ro)(G)--
--dict:22/25(L)-- --dict:4/6(L)-- --dict:26/40(L)--
Current allocation mode is local
Command /groups/tools/texlive/2014/bin/x86_64-linux/xelatex -halt-on-error
-output-directory=./LinguistInABox/output/latex
./LinguistInABox/output/latex/linguistInABoxGrammar.xetex -no-pdf died with
signal 13, without coredump
Signal 13 is Write on a pipe with no reader, Broken pipe.
I believe the crash is happening at the point xelatex is trying to embed an
existing PDF. If I'm right (we're going to verify it tomorrow), the command
that crashes is
--
\imgexists{list_intonation.pdf}{{\imgevalsize{list_intonation.pdf}{\includegraphics[width=\imgwidth,height=\imgheight,keepaspectratio=true]{list_intonation.pdf{}
-
Googling this:
xetex OR xelatex rangecheck in --run--
brings up about six msgs from 2011, which seem to be the same thread, and
afaict are irrelevant.
We're running the version of xetex that came with TeXLive 2014
(3.14159265-2.6-0.1) on Linux.
Any suggestions as to what I should be looking for?
Mike Maxwell
University of Maryland
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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 machine. Clearly s.t. is different, but I'm not sure what, and this
email is a query about what I should be looking for.
The error msg is:
--
Error: /rangecheck in --run--
Operand stack:
--dict:11/20(L)-- TT0 1 FontObject --dict:8/8(L)--
--dict:8/8(L)-- TimesNewRomanPSMT --dict:13/13(L)-- Times-Roman
Times-Roman
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop
1861 1 3 %oparray_pop 1845 1 3 %oparray_pop --nostringval--
--nostringval-- 2 1 1 --nostringval-- %for_pos_int_continue
--nostringval-- --nostringval-- false 1 %stopped_push
--nostringval-- --nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:1/20(G)-- --dict:76/200(L)--
--dict:76/200(L)-- --dict:106/127(ro)(G)-- --dict:286/300(ro)(G)--
--dict:22/25(L)-- --dict:4/6(L)-- --dict:26/40(L)--
Current allocation mode is local
Command /groups/tools/texlive/2014/bin/x86_64-linux/xelatex -halt-on-error
-output-directory=./LinguistInABox/output/latex
./LinguistInABox/output/latex/linguistInABoxGrammar.xetex -no-pdf died with
signal 13, without coredump
The problem looks to be with Ghostscript.
You may be using different versions, so check that first.
Signal 13 is Write on a pipe with no reader, Broken pipe.
I believe the crash is happening at the point xelatex is trying to embed an
existing PDF.
Yes. That PDF presumably has some text in it, using Times font as
TimesNewRomanPSMT .
Others used to using XeTeX under Linux may be able to offer a more detailed
understanding
of the specific kind of error.
If I'm right (we're going to verify it tomorrow), the command that crashes is
--
\imgexists{list_intonation.pdf}{{\imgevalsize{list_intonation.pdf}{\includegraphics[width=\imgwidth,height=\imgheight,keepaspectratio=true]{list_intonation.pdf{}
-
Googling this:
xetex OR xelatex rangecheck in --run--
brings up about six msgs from 2011, which seem to be the same thread, and
afaict are irrelevant.
We're running the version of xetex that came with TeXLive 2014
(3.14159265-2.6-0.1) on Linux.
Any suggestions as to what I should be looking for?
Mike Maxwell
University of Maryland
Hope this helps,
Ross
Ross Moore ross.mo...@mq.edu.au
Mathematics Department office: E7A-206
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia 2109 fax: +61 (0)2 9850 8114
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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. /rangecheck occurs if an operator tries to access
and array element or a substring but the index is out of bounds. It is
not easy to give a more specific explanation.
2014-08-27 23:51 GMT+02:00 Ross Moore ross.mo...@mq.edu.au:
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 machine. Clearly s.t. is different, but I'm not sure what, and
this email is a query about what I should be looking for.
The error msg is:
--
Error: /rangecheck in --run--
Operand stack:
--dict:11/20(L)-- TT0 1 FontObject --dict:8/8(L)--
--dict:8/8(L)-- TimesNewRomanPSMT --dict:13/13(L)-- Times-Roman
Times-Roman
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop
1861 1 3 %oparray_pop 1845 1 3 %oparray_pop --nostringval--
--nostringval-- 2 1 1 --nostringval-- %for_pos_int_continue
--nostringval-- --nostringval-- false 1 %stopped_push
--nostringval-- --nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:1/20(G)-- --dict:76/200(L)--
--dict:76/200(L)-- --dict:106/127(ro)(G)-- --dict:286/300(ro)(G)--
--dict:22/25(L)-- --dict:4/6(L)-- --dict:26/40(L)--
Current allocation mode is local
Command /groups/tools/texlive/2014/bin/x86_64-linux/xelatex -halt-on-error
-output-directory=./LinguistInABox/output/latex
./LinguistInABox/output/latex/linguistInABoxGrammar.xetex -no-pdf died with
signal 13, without coredump
The problem looks to be with Ghostscript.
You may be using different versions, so check that first.
Signal 13 is Write on a pipe with no reader, Broken pipe.
I believe the crash is happening at the point xelatex is trying to embed an
existing PDF.
Yes. That PDF presumably has some text in it, using Times font as
TimesNewRomanPSMT .
Others used to using XeTeX under Linux may be able to offer a more detailed
understanding
of the specific kind of error.
If I'm right (we're going to verify it tomorrow), the command that crashes is
--
\imgexists{list_intonation.pdf}{{\imgevalsize{list_intonation.pdf}{\includegraphics[width=\imgwidth,height=\imgheight,keepaspectratio=true]{list_intonation.pdf{}
-
Googling this:
xetex OR xelatex rangecheck in --run--
brings up about six msgs from 2011, which seem to be the same thread, and
afaict are irrelevant.
We're running the version of xetex that came with TeXLive 2014
(3.14159265-2.6-0.1) on Linux.
Any suggestions as to what I should be looking for?
Mike Maxwell
University of Maryland
Hope this helps,
Ross
Ross Moore ross.mo...@mq.edu.au
Mathematics Department office: E7A-206
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia 2109 fax: +61 (0)2 9850 8114
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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 9.06. I don't know if this--
http://bugs.ghostscript.com/show_bug.cgi?id=692177
is the particular error we're getting, but it seems plausible. It was
fixed in v9.04. I'm not sure why the other user's account calls the old
version and mine the newer ('which gs' on my machine returns a v8.71,
and 'which ghostscript' returns v8.70); but at least we have s.t. to
look at.
But--how did you figure this out? I see no mention of
Ghostscript/Postscript in the error msg.
Mike Maxwell
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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 forth, and running on the same
machine. Clearly s.t. is different, but I'm not sure what, and this email is a
query about what I should be looking for.
The error msg is:
--
Error: /rangecheck in --run--
Operand stack:
--dict:11/20(L)-- TT0 1 FontObject --dict:8/8(L)-- --dict:8/8(L)--
TimesNewRomanPSMT --dict:13/13(L)-- Times-Roman Times-Roman
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop
1861 1 3 %oparray_pop 1845 1 3 %oparray_pop --nostringval--
--nostringval-- 2 1 1 --nostringval-- %for_pos_int_continue
--nostringval-- --nostringval-- false 1 %stopped_push --nostringval--
--nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:1/20(G)-- --dict:76/200(L)--
--dict:76/200(L)-- --dict:106/127(ro)(G)-- --dict:286/300(ro)(G)--
--dict:22/25(L)-- --dict:4/6(L)-- --dict:26/40(L)--
Current allocation mode is local
Command /groups/tools/texlive/2014/bin/x86_64-linux/xelatex -halt-on-error
-output-directory=./LinguistInABox/output/latex
./LinguistInABox/output/latex/linguistInABoxGrammar.xetex -no-pdf died with
signal 13, without coredump
The problem looks to be with Ghostscript.
You may be using different versions, so check that first.
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 personal location? Does one of
the users have a pre-converted .pdf version of the graphic, but the
other only has access to an .eps original?
JK
Signal 13 is Write on a pipe with no reader, Broken pipe.
I believe the crash is happening at the point xelatex is trying to embed an
existing PDF.
Yes. That PDF presumably has some text in it, using Times font as
TimesNewRomanPSMT .
Others used to using XeTeX under Linux may be able to offer a more detailed
understanding
of the specific kind of error.
If I'm right (we're going to verify it tomorrow), the command that crashes is
--
\imgexists{list_intonation.pdf}{{\imgevalsize{list_intonation.pdf}{\includegraphics[width=\imgwidth,height=\imgheight,keepaspectratio=true]{list_intonation.pdf{}
-
Googling this:
xetex OR xelatex rangecheck in --run--
brings up about six msgs from 2011, which seem to be the same thread, and
afaict are irrelevant.
We're running the version of xetex that came with TeXLive 2014
(3.14159265-2.6-0.1) on Linux.
Any suggestions as to what I should be looking for?
Mike Maxwell
University of Maryland
Hope this helps,
Ross
Ross Moore ross.mo...@mq.edu.au
Mathematics Department office: E7A-206
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia 2109 fax: +61 (0)2 9850 8114
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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 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 9.06. I don't know if this--
http://bugs.ghostscript.com/show_bug.cgi?id=692177
is the particular error we're getting, but it seems plausible. It was fixed
in v9.04. I'm not sure why the other user's account calls the old version
and mine the newer ('which gs' on my machine returns a v8.71, and 'which
ghostscript' returns v8.70); but at least we have s.t. to look at.
But--how did you figure this out? I see no mention of
Ghostscript/Postscript in the error msg.
Mike Maxwell
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] rangecheck in --run--
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 personal location? Does one of the users have a pre-converted .pdf version of the graphic, but the other only has access to an .eps original? We do have a -D flag on the xdvipdfmx command line, which points to v9.06 of ghostscript. But that's the same for both this other user and me (it's run from a script). And I presume it's irrelevant to this error, since the crash happens when xelatex is running, not (unless I'm misunderstanding how this works) when xdvipdfmx runs. So under what circumstances would xelatex (not xdvipdfmx) be calling ghostscript? Maybe one of the users has a different version of the graphics package, or even just a configuration file, in a personal location? That seems the most likely explanation, although how that results in ghostscript getting called, I don't know. In the past we have used pdf2ps and ps2pdf (script which call gs) to convert some problematic versions of pdfs into acceptable versions. But that's s.t. we do once, off-line, and we simply retain the acceptable pdfs. So I don't think that's what's going on here. Does one of the users have a pre-converted .pdf version of the graphic, but the other only has access to an .eps original? I don't think so, but I'll certainly check when this other user gets back (Wednesday). Mike Maxwell -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
