I get a different error, using TL 2010 pre-release :
(e:/TeX/Live/2010/texmf-dist/tex/latex/fontspec/fontspec.cfg))
! Undefined control sequence.
\newfontinstance
l.3 \newfontinstance
\dhivehifontA{Mv Elaaf Normal}
Philip Taylor
\documentclass[12pt,letterpaper]{rep
Curiouser and curiouser : I just terminated the run,
and was told :
? exit
No pages of output.
Transcript written on mb-3.log.
I cannot find emacs in the PATH.
E:\TeX\Projects\Tests>
Why on /earth/ is something searching for Emacs ??? !
Philip Taylor (Webmaster, Ret'd) wrote:
I get a differ
@ Dr. Joachim Trinkwitz
I see now the possibilities behind KOMA-Script and memoir. I'll read
the documentation (almost 1000 pages I think) and choose between these
two solutions (the one which is simpler and more customizable).
For now I found a neat solution, in case anyone asked: (just using
ti
On 9/4/2010 8:14 PM, Tak Yato (ZR) wrote:
> The author of sfkanbun package, Shinsaku Fujita, shows some samples
> of kunten typesetting on his web site.
> http://homepage3.nifty.com/xymtex/fujitas/kanbun/kanbunex.html
> You can view more samples by clicking the links to JPG images.
>
Much like
Philip Taylor (Webmaster, Ret'd writes:
> I get a different error, using TL 2010 pre-release :
>
> (e:/TeX/Live/2010/texmf-dist/tex/latex/fontspec/fontspec.cfg))
> ! Undefined control sequence.
> \newfontinstance
This command is deprecated; please use \newfontfamily or \newfontface instead.
Am 05.09.2010 um 05:55 schrieb Mike Maxwell:
I'm trying out some fonts for the Dhivehi language, which has a
unique script.
Thaana, U+0780-U+07BF, can also be found in Code2000, FreeSerif, TITUS
Cyberbit.
The cause is that your code is faulty:
\newfontinstance\dhivehifontA{Mv Elaaf Nor
I agree that the code is weird (and it looks to me
as if it is actually wrong), but I cannot see any
reason to believe that it leads to iteration or
recursion.
Philip Taylor
Peter Dyballa wrote:
The cause is that your code is faulty:
\newfontinstance\dhivehifontA{Mv Elaaf Normal}
^^
Yes, that solves my problem, Will, and removing the
second \newfont{instan|fa}ce solves the original
problem, I think :
\documentclass[12pt,letterpaper]{report}
\usepackage{fontspec}
\newfontface\dhivehifontA{Mv Elaaf Normal}
\newcommand{\dhiA}[1]{{\dhivehifontA #1}}
\begin{document}
\dhiA{ޓީވީއެ
Hi Michiel,
On Sun, 05 Sep 2010 02:02:22 -0700, Michiel Kamermans wrote:
> Much like the gehzu package, why is this not on CTAN... it certainly
> doesn't help people not reinventing the wheel...
sfkanbun.sty is a package for pTeX only and pTeX is not
standard TeX at present (i.e. pTeX is not on
On 9/5/2010 7:28 AM, Philip Taylor (Webmaster, Ret'd) wrote:
Yes, that solves my problem, Will, and removing the
second \newfont{instan|fa}ce solves the original
problem, I think :
\documentclass[12pt,letterpaper]{report}
\usepackage{fontspec}
\newfontface\dhivehifontA{Mv Elaaf Normal}
\newcomma
Hi Philip,
Am 04.09.2010 um 19:33 schrieb Philip Taylor (Webmaster, Ret'd):
> What exactly do you dislike about the use of sans serif for headings ? To my
> mind, and in a scientific as opposed to artistic context, sans serif headings
> with serif prose seem absolutely normal and fine.
Am 04.
What command line options does xelatex allow? Is it more or less the
same as for pdflatex with respect to things like output-directory,
shell-escape etc.? I don't seem to have a man page for it (TeXLive
2009 on Mac OS.)
Thanks
Alan
--
Alan Munn
am...@gmx.com
On Sep 5, 2010, at 6:18 PM, Alan Munn wrote:
> What command line options does xelatex allow? Is it more or less the same as
> for pdflatex with respect to things like output-directory, shell-escape etc.?
> I don't seem to have a man page for it (TeXLive 2009 on Mac OS.)
>
> Thanks
>
> Alan
>
On Sep 5, 2010, at 7:23 PM, Herbert Schulz wrote:
On Sep 5, 2010, at 6:18 PM, Alan Munn wrote:
What command line options does xelatex allow? Is it more or less
the same as for pdflatex with respect to things like output-
directory, shell-escape etc.? I don't seem to have a man page for
it
Hi Alan,
Ahh, thanks. I didn't try that. It would be useful, however, to have
a man page, since that's the normal way such information is found, I
think.
Usually you resort to a man page when the --help readout doesn't
actually tell you anything (like only listing the possible flags withou
15 matches
Mail list logo
