Dear Stefan,
Some questions from the non-expert.
I'm also a non-expert. The previous one is only an
experiment. Sorry.
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Dear Akira,
Thanks a lot! This works for the examples I tried and is very helpful!
Some questions from the non-expert. Does the definition of pdftexversion
mean that every texinstallation comes with several versions installed?
Also with several drivers?
Very interesting.
Are there ways to fix t
Dear Stefan,
I filed a bug report, but nothing happend:
http://sourceforge.net/p/pgf/bugs/354/
The issue is related to pgf drivers, pgfsys-xetex.def and
pgfsys-dvipdfmx.def which is called by the former.
Your example works if you use the other driver: pgfsys-dvipdfm.def,
see below. However, d
Hello Anant,
Sorry about the late reply; for some (yet) unknown reason, I don't
receive all messages from the list.
I couldn't see your attachment, which was deleted, but I suppose you
want to type anudatta and svarita (udatta in Unicode terminology).
Those characters don't exist in the k
I've never dealt with Yiddish, but I've worked with a bit of edited
Hebrew, so this response may be of some use.
If you are using Xe(La)TeX, then you will have to use the arabxetex
package, if you want to do ASCII input. But, as far as I know, arabxetex
does not support Hebrew characters.
Yo
On Mon, Jul 2, 2012 at 12:08 AM, Jonathan Kew wrote:
> Yes; you need a semicolon to separate multiple features, not an ampersand.
> So try
> \font\krishnaalt="Krishna Tamil/GR:Classical=True;Pulli=Ring" at 12 pt
> and see if that works better.
Just for the record so someone may get it from the pu
Dear Shriramana,
> Now by further testing the cmap-fixed font, I am happy to note that
> Brahmi is now rendering (hopefully by Graphite, since there is no
> rendering when /GR is not there), but I wonder why a font should have
> OT tables to render Graphite!?!
Graphite uses all kinds of tables fr
On Mon, Jul 2, 2012 at 7:52 AM, Martin Hosken wrote:
> Dear Shriramana,
>
>> Now by further testing the cmap-fixed font, I am happy to note that
>> Brahmi is now rendering (hopefully by Graphite, since there is no
>> rendering when /GR is not there), but I wonder why a font should have
>> OT table
On Mon, Jul 2, 2012 at 3:09 AM, Mojca Miklavec
wrote:
> I tested a few days ago and not with that last link, but on my Mac
> (x86_64-darwin) I only get
>
> ** WARNING ** Invalid CMap mapping entry. (ignored)
> ** WARNING ** Unable to read OpenType/TrueType Unicode cmap table.
> ** WARNING ** Faile
On Sun, Jul 1, 2012 at 8:38 PM, Shriramana Sharma wrote:
> On Sun, Jul 1, 2012 at 11:51 PM, Shriramana Sharma wrote:
>> I wonder if there is some problem with the Graphite handling SMP code
>> points? While typesetting (using Ctrl+T in TeXWorks) I still get the
>> segfault I reported. I hope you p
On Sun, Jul 1, 2012 at 11:51 PM, Shriramana Sharma wrote:
> (Latest PPA from
> https://launchpad.net/~texlive-backports/+archive/ppa/ have been
> updated and are now downloading so I'll test that later.)
I've now upgraded my Texsystem to latest PPA packages (texlive-base,
texlive-latex-base and c
On Mon, Jul 2, 2012 at 12:08 AM, Jonathan Kew wrote:
>> I am also unable to turn on the Tamil features on -- am I doing
>> something wrong in specifying the features?
>
> Yes; you need a semicolon to separate multiple features, not an ampersand.
> So try
>
> \font\krishnaalt="Krishna Tamil/GR:Clas
On Mon, Jul 2, 2012 at 12:08 AM, Shriramana Sharma wrote:
> With /GR included, actually I'm getting some
> rendering, but there are still some boxes. (There is a warning of a
> bad CMAP mapping -- I wonder.)
Well I fixed that CMAP mapping thing (the friend who had added the OT
tables altered some
On Sun, Jul 1, 2012 at 11:51 PM, Shriramana Sharma wrote:
> I wonder if there is some problem with the Graphite handling SMP code
> points? While typesetting (using Ctrl+T in TeXWorks) I still get the
> segfault I reported. I hope you people can reproduce that too.
>
> I note that if I comment out
On 1/7/12 19:21, Shriramana Sharma wrote:
On Tue, Jun 26, 2012 at 8:30 PM, Jonathan Kew wrote:
OTOH, the people who wrote Graphite are still there, and if the graphite
engine is crashing, they may be able to help pinpoint the problem and
suggest a fix that could be applied to the library xetex
On Tue, Jun 26, 2012 at 8:30 PM, Jonathan Kew wrote:
>
> OTOH, the people who wrote Graphite are still there, and if the graphite
> engine is crashing, they may be able to help pinpoint the problem and
> suggest a fix that could be applied to the library xetex is using, and/or a
> way to work arou
2012/6/26 Jonathan Kew :
> On 26/6/12 15:09, Martin Schröder wrote:
>>
>> 2012/6/26 Khaled Hosny:
>>>
>>> XeTeX is still using the old (and more fragile) Graphite engine,
>>> LibreOffice switched to the new (and more robust) one AKA graphite2. So
>>> the segmentation fault is likely from the Graphi
On 26/6/12 15:09, Martin Schröder wrote:
2012/6/26 Khaled Hosny:
XeTeX is still using the old (and more fragile) Graphite engine,
LibreOffice switched to the new (and more robust) one AKA graphite2. So
the segmentation fault is likely from the Graphite engine, so you may
try reporting it to SIL
On Tue, Jun 26, 2012 at 1:56 PM, Ulrike Fischer wrote:
>> I'm also using TeXWorks (on Kubuntu Precise) as a GUI.
>
> The GUI is not so important, but you should mention your TeXSystem.
Sorry, I'll do that hereafter. I'm using latest TeXLive from
https://launchpad.net/~texlive-backports
--
Shrir
Thanks all for your replies. I'll see what can be done and get back later.
--
Shriramana Sharma
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
2012/6/26 Khaled Hosny :
> XeTeX is still using the old (and more fragile) Graphite engine,
> LibreOffice switched to the new (and more robust) one AKA graphite2. So
> the segmentation fault is likely from the Graphite engine, so you may
> try reporting it to SIL people (but sadly, that won't help
2012/6/26 Ulrike Fischer :
> Am Tue, 26 Jun 2012 09:50:18 +0530 schrieb Shriramana Sharma:
>
>> Hello. I need to use (outline fonts,) Unicode and Graphite, so XeTeX
>> is my choice for engine, and I am picky about my layout stuff so
>> ConTeXT is my choice for macro package.
>
> I don't think that
Am Tue, 26 Jun 2012 09:50:18 +0530 schrieb Shriramana Sharma:
> Hello. I need to use (outline fonts,) Unicode and Graphite, so XeTeX
> is my choice for engine, and I am picky about my layout stuff so
> ConTeXT is my choice for macro package.
I don't think that you will have much joy with this com
On Tue, Jun 26, 2012 at 10:21:00AM +0530, Shriramana Sharma wrote:
> Looks like the problem is not limited to ConTeXT (thank goodness, in a
> way!) and Graphite still doesn't work on XeLaTeX. The only difference
> is that XeLaTeX is able to handle OT without resorting to the XeTeX
> \font primitive
Looks like the problem is not limited to ConTeXT (thank goodness, in a
way!) and Graphite still doesn't work on XeLaTeX. The only difference
is that XeLaTeX is able to handle OT without resorting to the XeTeX
\font primitive.
I still don't understand why /GR should cause a segmentation fault. I
do
If you're not used to handle keyboard layouts on OS X, you might want to read
this page:
http://groups.google.com/group/ukelele-users/browse_thread/thread/6ab55e2b54d92c34
Le 28 mai 2012 à 16:36, A u a écrit :
> Hello Yves,
> I have a Mac OS X also, how did you get the विश्व॒दानी॑म् anudatta
Hello Aku,
I think the keyboard layouts which come with the system don't allow to type
svarita or anudatta. But you can use Ukelele to customise them.
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=ukelele
In the disk image you will find a folder named "System Keyboards" and i
Hello Yves,
I have a Mac OS X also, how did you get the विश्व॒दानी॑म् anudatta in Mac.
I have Sanskrit 2003 and it looked at the keyboard layout and could not see
that symbol anywhere.
I would appreciate your help
Aku
On Fri, May 25, 2012 at 4:15 AM, Yves Codet wrote:
> Hello.
>
> I'm not sure
Hello.
The accents that Chandrasekhar needs do exist in Unicode:
udatta U+0951
anudatta U+0952
There are some more signs in "Devanagari Extended":
http://www.unicode.org/charts/PDF/UA8E0.pdf
but according to his post he doesn't need those.
Below is a minimal example which shows udatta and anudat
2012/5/25 Yves Codet :
> Hello.
>
> I'm not sure you can type Vedic accents with the Velthuis encoding, or maybe
> they don't exist in Nakula. Personally I stopped using romanised inputs
> since it became as easy to विश्व॒दानी॑म् type in Devanagari as in Latin
> script on my system (Mac OS X), that
Hello.
I'm not sure you can type Vedic accents with the Velthuis encoding, or maybe
they don't exist in Nakula. Personally I stopped using romanised inputs since
it became as easy to विश्व॒दानी॑म् type in Devanagari as in Latin script on my
system (Mac OS X), that is to say many years ago, I do
On Thu, Sep 29, 2011 at 4:01 PM, Michael Joyner wrote:
>
>
> On Thu, Sep 29, 2011 at 3:17 PM, Arno Trautmann wrote:
>
>> Michael Joyner wrote:
>>
>>> HELP!
>>>
>>> I am getting this on a super-large tex file:
>>>
>>> ** ERROR ** Page number 65536l too large!
>>>
>>> I tried googling it, but did n
On Fri, Sep 30, 2011 at 9:16 AM, Petr Tomasek wrote:
> On Fri, Sep 30, 2011 at 09:13:03AM -0400, Michael Joyner wrote:
> > On Thu, Sep 29, 2011 at 8:43 PM, Wilfred van Rooijen
> > wrote:
> >
> > > But the real question remains: does the topic starter really produce a
> file
> > > with 65000 pages
On Fri, Sep 30, 2011 at 09:13:03AM -0400, Michael Joyner wrote:
> On Thu, Sep 29, 2011 at 8:43 PM, Wilfred van Rooijen
> wrote:
>
> > But the real question remains: does the topic starter really produce a file
> > with 65000 pages? Or is there some other error at play? The topic starter
> > never
On Thu, Sep 29, 2011 at 8:43 PM, Wilfred van Rooijen
wrote:
> But the real question remains: does the topic starter really produce a file
> with 65000 pages? Or is there some other error at play? The topic starter
> never mentioned how large his "large" tex file is
>
My tex file is 885 megs
Dear Heiko,
> * dvitype is ok, it reports
> | there are really 7 pages, not 4464!
In this case total_pages may be written in the dvi as 4464.
I find in tex.web:
@ At the end of the program, we must finish things off by writing the
post\-amble. If |total_pages=0|, the \.{DVI} file was neve
On Thu, Sep 29, 2011 at 09:00:21PM +0100, Jonathan Kew wrote:
> Note that the DVI file format postamble includes a two-byte field for the
> total number of pages present, so if you try to put more than 64K pages in
> a DVI file, the postamble (at least) will necessarily be incorrect, even
> if the
-based TeX for Mac OS X and other platforms
Sent: Friday, September 30, 2011 5:13 AM
Subject: Re: [XeTeX] HELP! ** ERROR ** Page number 65536l too large!
2011/9/29 Jonathan Kew :
> Clearly Knuth didn't think there was any need for such large numbers
> of pages in a single file.
See
On Thu, Sep 29, 2011 at 3:17 PM, Arno Trautmann wrote:
> Michael Joyner wrote:
>
>> HELP!
>>
>> I am getting this on a super-large tex file:
>>
>> ** ERROR ** Page number 65536l too large!
>>
>> I tried googling it, but did not find any references to this error. :(
>>
>
> Maybe if you try to also
On 29 Sep 2011, at 18:59, Michael Joyner wrote:
> HELP!
>
> I am getting this on a super-large tex file:
>
> ** ERROR ** Page number 65536l too large!
>
> I tried googling it, but did not find any references to this error. :(
This error is reported by xdvipdfmx (the PDF-generating output drive
2011/9/29 Jonathan Kew :
> Clearly Knuth didn't think there was any need for such large numbers
> of pages in a single file.
See TeX error #913:
* 28 December 1990
R913. Avoid range check when there are 65536 or more pages (Eberhard Mattes).
> It's possible (though I haven't tried) that pdftex in
On 29 Sep 2011, at 21:01, Michael Joyner wrote:
>
>
> On Thu, Sep 29, 2011 at 3:17 PM, Arno Trautmann wrote:
> Michael Joyner wrote:
> HELP!
>
> I am getting this on a super-large tex file:
>
> ** ERROR ** Page number 65536l too large!
>
> I tried googling it, but did not find any references
On Thu, Sep 29, 2011 at 01:59:18PM -0400, Michael Joyner wrote:
> HELP!
>
> I am getting this on a super-large tex file:
>
> ** ERROR ** Page number 65536l too large!
>
> I tried googling it, but did not find any references to this error. :(
>
> -Mike
Does it happend with XeTeX only?
P.
--
Michael Joyner wrote:
HELP!
I am getting this on a super-large tex file:
** ERROR ** Page number 65536l too large!
I tried googling it, but did not find any references to this error. :(
Maybe if you try to also report what you did, we could have a chance to
help you …
cheers
Arno
--
Am Sun, 9 Jan 2011 19:14:55 +0100 schrieb Bogdan Butnaru:
> OK, thanks everyone.
>
> For the record (in case others have this problem and reach this
> message), using both
>
> \usepackage{fontspec}
> \usepackage{xunicode}
With a recent fontspec you don't need to load xunicode yourself.
fontspec
Explanation of the other replies:
The packages ucs and [utf8x]inputenc are used by LaTeX in order to cope
with utf8 encoded text. This is needed, because LaTeX uses the
TeX-Engine, which copes only with ascii.
That was TeX. But you want to use XeTeX:
XeTeX automatically copes with utf8-encod
OK, thanks everyone.
For the record (in case others have this problem and reach this
message), using both
\usepackage{fontspec}
\usepackage{xunicode}
also works. It’d be nice if someone could explain what’s the
difference between the two.
(After trying a bit more by myself I noticed a warning a
Bogdan Butnaru writes:
> Hello! I’m pretty sure I’m forgetting something stupid, but I hope
> someone can point me in the right direction. Take this very simple
> document (the source is UTF8 encoded):
>
> ***
> \documentclass{memoir}
>
> \usepackage{ucs}
> \usepackage[utf8x]{inpu
Hello,
Change your document to something like
***
\documentclass{memoir}
% \usepackage{ucs} %needed only for LaTeX
% \usepackage[utf8x]{inputenc}
\usepackage{xltxtra}
\begin{document}
\setmainfont[Mapping=tex-text]{Minion Pro} %<--- Choose any font you like
10
49 matches
Mail list logo
