Mojca Miklavec wrote:
On Sun, Jun 21, 2009 at 13:09, Hans Hagen wrote:
Mojca Miklavec wrote:
Hans ... I suspect that ConTeXt MKII (both pdftex and xetex) are
missing from the list ...
indeed. mkiv only as i don't want dependencies on perl/ruby in this case
So ... should I start blackmailing
suspect that ConTeXt MKII (both pdftex and xetex) are
missing from the list ...
Mojca
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http
.
for that i need to rewrite the index sorting in lua (plus a little bit
of tui - tuo handling)
now context script supports --pdftex and --xetex switch, but it still
fall back to texexec and texutils ruby scripts.
sure, time is limited
Hans
for free OpenType fons.
This probably means I'm understanding something completely
wrong... What would that be?
You're right, the concrete fonts are mentioned in the typography chapter
but ConTeXt use now two different versions for XeTeX and LuaTeX and in
the LuaTeX part the old files are removed
supports --pdftex and --xetex switch, but it still
fall back to texexec and texutils ruby scripts.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
the Computer Modern Unicode fonts.
\usetypescriptfile[type-otf]
You don't have to to load 'type-otf', it's always loaded by ConTeXt
itself with XeTeX or LuaTeX.
Wolfgang
___
If your question is of interest to others
Dear list,
I'm part of a design group Open Source Publishing, and we use ConTeXt
for a few months now. The main goal is to produce a 200+ pages multi-
lingual art book for which we have in the past months some exchanges
with kind members of the list about font install and Xetex. I
of the list about font install and
Xetex. I currently work more on the design itself.
To finish on time, avoid loosing time on some hazardous/random
errors, and also learning ConTeXt more from the inside, we're
looking for a person interested to have a commissioned work -for a
fair price
by 'showbodyfont' says I'm
using 'modern'.
Am I missing something? I'm using minimal install,
updated yesterday (although I have this problem for
at least two weeks).
1. Do you use XeTeX to process your file?
2. Do you have the Gentium fonts on your system?
Wolfgang
missing something? I'm using minimal install,
updated yesterday (although I have this problem for
at least two weeks).
1. Do you use XeTeX to process your file?
2. Do you have the Gentium fonts on your system?
I use the minimal install from pragma site, as prescribed
in the 'simple' version
by 'showbodyfont' says I'm
using 'modern'.
Am I missing something? I'm using minimal install,
updated yesterday (although I have this problem for
at least two weeks).
1. Do you use XeTeX to process your file?
2. Do you have the Gentium fonts on your system?
I use the minimal install from pragma site
for the name of the file but the convention
is
to name it type-whatever.tex.
2. what should be the extension for mkiv ? .mkiv ? .tex ? Are both
allowed ?
You could write extra files to follow the different naming conventions
for XeTeX and LuaTeX and name the files type-whatever.mkii/mkiv and
load
need XeTeX to let this work.
You can also use helevetica. Most people will not notice the
difference.
So,
\usetypescript[postscript]
\setupbodyfont[ss, 12pt]
The above changed the font to sans serif, but it doesn't look like
Helvetica (or Arial)
The second line has to be \setupbodyfont
symbol,
so in default mkii, it is being built up from (math) macros,
a bit like how it used to work in plain TeX.
Options are: switch to a different font encoding, switch to
mkiv or xetex, or do something like this:
{\switchtobodyfont[xx]\copyright 2009 Acme Co Ltd}
Best wishes,
Taco
from (math) macros,
a bit like how it used to work in plain TeX.
Options are: switch to a different font encoding, switch to
mkiv or xetex, or do something like this:
{\switchtobodyfont[xx]\copyright 2009 Acme Co Ltd}
Best wishes,
Taco
That works, thanks.
Best regards,
Richard
Anfang der weitergeleiteten E-Mail:
Von: William Adams will.ad...@frycomm.com
Datum: 26. Mai 2009 17:38:29 MESZ
An: Unicode-based TeX for Mac OS X and other platforms xe...@tug.org
Betreff: [XeTeX] ANN: Custom Stories, Inc. using xelatex now live
Antwort an: Unicode-based TeX for Mac OS X
On May 26, 2009, at 1:03 PM, Wolfgang Schuster quoted my having written:
The typesetting is done using XeLaTeX, and I don't believe would've
been as effective using any other tool.
That should probably say:
The typesetting is done using XeTeX, and I don't believe it would've
been
a stretched font
without
disturbing the output routine? I think I can try a narrow font and
re-draw
my pictures.
AFAIK XeTeX has such a feature but is the presentation worth such
tricks.
Wolfgang
___
If your
Corsair wrote:
On Thu, May 21, 2009 at 01:59:14PM +0200, Taco Hoekwater wrote:
Corsair wrote:
On Thu, May 21, 2009 at 11:55:45AM +0200, Hans Hagen wrote:
open type fonts have no italic correction info (except in math)
But I notice that using the same fonts in XeTeX produces italic
On Thu, May 21, 2009 at 11:55:45AM +0200, Hans Hagen wrote:
open type fonts have no italic correction info (except in math)
But I notice that using the same fonts in XeTeX produces italic
correction. Is it fake?
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge
Corsair wrote:
On Thu, May 21, 2009 at 11:55:45AM +0200, Hans Hagen wrote:
open type fonts have no italic correction info (except in math)
But I notice that using the same fonts in XeTeX produces italic
correction. Is it fake?
I guess it is using the glyph boundingbox
On Thu, May 21, 2009 at 01:59:14PM +0200, Taco Hoekwater wrote:
Corsair wrote:
On Thu, May 21, 2009 at 11:55:45AM +0200, Hans Hagen wrote:
open type fonts have no italic correction info (except in math)
But I notice that using the same fonts in XeTeX produces italic
correction
, no output PDF file produced!
MTXrun | fatal error, return code: 70
It happens with other italic URW fonts, such as Palladio.
* Googling a bit the error message, I found a similar error message
but with Xetex (http://www.tug.org/pipermail/xetex/2008-March/009000.html ):
OK, I think I have
monospaced fonts can't have
such problem.
nb: There is no such problem when I use the Xetex engine.
Versions:
This is LuaTeX, Version beta-0.40.1-2009050920 (Web2C 7.5.7)
\write18 enabled.
ConTeXt ver: 2009.05.14 16:44 MKIV fmt: 2009.5.18 int: english/english
test.tex
Description: TeX document
hope attachments are allowed here.
Thanks.
nb: No problem with FreeMono, but I suspect monospaced fonts can't have
such problem.
nb: There is no such problem when I use the Xetex engine.
Versions:
This is LuaTeX, Version beta-0.40.1-2009050920 (Web2C 7.5.7)
\write18 enabled.
ConTeXt
if
LuaTeX (XeTeX too) output looked OK in Adobe reader 7, the print isn't
OK.
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font developer
signature.asc
Description: Digital signature
Not only OOo, InDesign does that too, moreover, someone said even if
LuaTeX (XeTeX too) output looked OK in Adobe reader 7, the print isn't
OK.
On what printer? It's probably a bug in the driver, too. LuaTeX does
exactly according to specification, I discussed this strategy with Taco
years
Hello,
I am using Context Mark II + XeTeX. I would like to know the
following things.
1. How to use opentype font features. I tried the following code but it is
not working.
\definefontfeature[myfontfea][+onum]
\definetypeface[Libertine][rm][Xserif][Linux Libertine
O][default
Arun Dev wrote:
Hello,
I am using Context Mark II + XeTeX. I would like to know the
following things.
1. How to use opentype font features. I tried the following code but it is
not working.
\definefontfeature[myfontfea][+onum]
\definetypeface[Libertine][rm][Xserif][Linux
You asked the same questions a few days ago, what's your problem
with the answers you got last time?
Wolfgang
Am 14.05.2009 um 14:18 schrieb Arun Dev:
Hello,
I am using Context Mark II + XeTeX. I would like to know the
following things.
1. How to use opentype font features. I
files in mem, disk
access etc)
After debugging for half an hour in the morning, finally I know why
this is so slow on both XeTeX and pdfTeX.
This problem is not an operating system issue, But a ConTeXt feature.
in font-mkii, you use the following to define a actual font
(\definefontlocal
Yue Wang wrote:
After debugging for half an hour in the morning, finally I know why
this is so slow on both XeTeX and pdfTeX.
This problem is not an operating system issue, But a ConTeXt feature.
in font-mkii, you use the following to define a actual font
(\definefontlocal
switch to a different font in his greek
module,
in mkiv this is trivia with font fallbacks.
Wolfgang
Just FYI: yes, I do use switchtobodyfont in my Greek module, but I
have more or less given up on XeTeX, so I've never encountered the
problem. The font fallback is great for filling in some
to determine which engine I am running.
If not running MKIV/XeTeX, how to determine which fonts are installed.
What the items from the output of fc-list or mtxrun --script fonts
--list correspond to.
How to use available fonts, nor where to draw valid parameters from
for use in font commands.
How
using MKIV, nor how to determine which engine I am running.
If not running MKIV/XeTeX, how to determine which fonts are installed.
What the items from the output of fc-list or mtxrun --script fonts
--list correspond to.
How to use available fonts, nor where to draw valid parameters from
for use in font
oh, no. better change that to this:
/XYZ @xpos @ypos 0
so xetex and pdftex/luatex will share the same behavior. (it point to
the place a little bit lower, so the behavior is much better than fit)
as to the wrong destination.. I highly suspect that the PDF /Dests is
written right after the box
Luigi, Hans, and Wolfgang, thank you for your responses. I'm still
unclear on several things. (comments on your responses follow
afterwards)
Let me try asking these things as questions. Specifically, could
someone please tell me...
1. How do I determine whether I am using MKII, MKIV, or XeTeX
, MKIV, or XeTeX to
process my documents?
\doifmode {mkiv} { ... }
\ifnum\texengine=\xetexengine .. \fi
mkiv only run son top of luatex (and the context command replaces
texexec there)
2. Given the line from a typescript...
\definefontsynonym[LiberationSerif] [name:liberationserif]
how do
whether I am using MKII, MKIV, or XeTeX to
process my documents?
Depends on how you process your documents.
texexec filename= pdftex engine (mkii)
texexec --pdf filename = pdftex engine (mkii)
texexec --xtx filename = xetex engine (mkii)
texexec --lua filename = luatex engine (mkiv
Am 13.05.2009 um 22:23 schrieb Aditya Mahajan:
On Wed, 13 May 2009, afsmith wrote:
Let me try asking these things as questions. Specifically, could
someone please tell me...
1. How do I determine whether I am using MKII, MKIV, or XeTeX to
process my documents?
Depends on how you process
responses follow
afterwards)
Let me try asking these things as questions. Specifically, could
someone please tell me...
1. How do I determine whether I am using MKII, MKIV, or XeTeX to
process my documents?
I tend to use
\begin{XETEX,OLDTEX,LUATEX}
...
\end{XETEX,OLDTEX,LUATEX}
2. Given the line
Am 11.05.2009 um 14:41 schrieb Yue Wang:
Hi Wolfgang:
nice script.
Can the module meet my needs discussed in
http://www.ntg.nl/pipermail/ntg-context/2009/040831.html ?
or is it possible to extend the support to xetex?
When you take care about font switching in your module it's easy,
large
some testing samples in ConTeXt to test XeTeX. but the result
is quite strange. All benchmark are get from the second run:
Sample 1:
\definefont[a][file:SimSun]
\starttext
\dorecurse{1}{ hello {\a 你好}}
\stoptext
And here is the result:
XeTeX: TeXExec | runtime: 7.25
LuaTeX: MTXrun
for the noise. I am now sure that it is a
context bug, not xetex's.
Yue Wang
2009/5/12 Yue Wang yuleo...@gmail.com:
Hi, Hans and Jonathan:
I made some testing samples in ConTeXt to test XeTeX. but the result
is quite strange. All benchmark are get from the second run:
Sample 1:
\definefont
Yue Wang wrote:
Hi, Hans,
The enco-xtx.tex defination is still wrong...
it behaves very differently compared to unicode-letters.tex
well, it's not supposed to do the same (and we're not going to be latex
compatible anyway)
as we now need mpore 'tables' i've reorganized the xetex code
namespace switch + one font switch but when extensive math
definitions are also involved it might take a few more cycles
anyway .. i cannot comment on runtimes as xetex on my windows box runs
too slow (caching issue) and all examples are slow, no matter how i
specify fonts so i will not look
Hans Hagen wrote:
anyway .. i cannot comment on runtimes as xetex on my windows box runs
too slow (caching issue) and all examples are slow, no matter how i
specify fonts so i will not look into the code till that gets fixed first
The example with the typescript seems logical to me
Taco Hoekwater wrote:
Hans Hagen wrote:
anyway .. i cannot comment on runtimes as xetex on my windows box runs
too slow (caching issue) and all examples are slow, no matter how i
specify fonts so i will not look into the code till that gets fixed first
The example with the typescript seems
=ss]
\setupbodyfont[iwona]
\starttext
foobar
\stoptext
runtime= 6.625. There is a 5 seconds pause after loading
(c:/context/tex/texmf-context/tex/context/base/spec-xet.tex)
But I don't know what xetex is loading.
Test 2:
\definetypeface[iwona][ss][sans] [iwona] [default]
%\definetypeface
Hans Hagen wrote:
Taco Hoekwater wrote:
Hans Hagen wrote:
anyway .. i cannot comment on runtimes as xetex on my windows box runs
too slow (caching issue) and all examples are slow, no matter how i
specify fonts so i will not look into the code till that gets fixed
first
The example
On Tue, May 12, 2009 at 7:26 PM, Taco Hoekwater t...@elvenkind.com wrote:
Hans Hagen wrote:
Taco Hoekwater wrote:
Hans Hagen wrote:
anyway .. i cannot comment on runtimes as xetex on my windows box runs
too slow (caching issue) and all examples are slow, no matter how i
specify fonts so
]
\setupbodyfont[iwona]
\starttext
foobar
\stoptext
runtime= 6.625. There is a 5 seconds pause after loading
(c:/context/tex/texmf-context/tex/context/base/spec-xet.tex)
But I don't know what xetex is loading.
fonts (like the sans and more noticeably math (6 families * 3 sizes = 18
fonts
, and convert the dvi using dvipdfmx
2) using xetex to produce the pdf using xdvipdfmx
the figure is placed at the wrong place. there will be a displacement
for all the metapost figures when xetex is used to produce the
graphics. I attach the wrong result in the mail.
So my question is :
- is this a bug
, and use dvipdfmx to convert the
dvi to pdf.
2) using xetex to produce xdv, and xdvipdfmx that xdv to pdf.
Open the file in Acrobat Reader, Go to page three, and you can see a
hyperlink text Equation 1, it links to page 2. however, the equation
is in page1.
The section 1 or page 4 should point
Yue Wang wrote:
\font\a=[simsun]
\starttext
\dorecurse{1}{ hello {\a 你好}\par}
\stoptext
runtime: TeXExec | runtime: 2.922
\font\a=[simsun.ttf]
\starttext
\dorecurse{1}{ hello {\a 你好}\par}
\stoptext
as taco already mentioned there's a problem with xetex caching fonts
\stoptext
runtime= 6.625. There is a 5 seconds pause after loading
(c:/context/tex/texmf-context/tex/context/base/spec-xet.tex)
But I don't know what xetex is loading.
fonts (like the sans and more noticeably math (6 families * 3 sizes = 18
fonts at least)
but it's pretty fast on mac
Yue Wang wrote:
moreover, can you tell me why pdftex load these fonts so fast? (also 6
families * 3 sizes)
i don't know; as the same code is used so it must be xetex itself then
-
Hans
On Tue, May 12, 2009 at 8:54 PM, Hans Hagen pra...@wxs.nl wrote:
Yue Wang wrote:
moreover, can you tell me why pdftex load these fonts so fast? (also 6
families * 3 sizes)
i don't know; as the same code is used so it must be xetex itself then
Then let me tell you why: ConTeXt tries to load
PM, Hans Hagen pra...@wxs.nl wrote:
Yue Wang wrote:
moreover, can you tell me why pdftex load these fonts so fast? (also 6
families * 3 sizes)
i don't know; as the same code is used so it must be xetex itself then
Then let me tell you why: ConTeXt tries to load lmmono10-regular at
least 6
Yue Wang wrote:
On Tue, May 12, 2009 at 8:54 PM, Hans Hagen pra...@wxs.nl wrote:
Yue Wang wrote:
moreover, can you tell me why pdftex load these fonts so fast? (also 6
families * 3 sizes)
i don't know; as the same code is used so it must be xetex itself then
Then let me tell you why
does not hurt)
don't use the [ ] syntax which is rather engine specific
i moved all xetex code to a separate file font-xtx now (not sure if that
has side effects due to definition order but don't want to mess up the
mkii code)
but it cannot solve the suffix problem nor the name lookup
is used so it must be xetex itself then
Then let me tell you why: ConTeXt tries to load lmmono10-regular at
least 6 times, failed after two testing, then succeed in the end.
However, try to testing whether a loaded font is \nullfont or not is
quite slow in XeTeX (Jonathan already mentioned
moved all xetex code to a separate file font-xtx now (not sure if that
has side effects due to definition order but don't want to mess up the mkii
code)
I see.
but it cannot solve the suffix problem nor the name lookup problems due to
caching
I already reported that feature/bug to Jonathan Kew
Yue Wang wrote:
\def\defaultfontfile{file:lmmono10-regular}
After changing like this, XeTeX runs like a blink. (It wasted 6
seconds for each compile. now it won't)
Does that mean that the near-endless font issues with xetex are
now finally fixed?
Cheers,
Taco
plain definitions also have a
suffix and/or name lookup problem so you'd better make sure that that is
fixed too (if only because we cannot be sure of users always using
filenames)
in the meantime i'll add some lookup caching in the xetex specific
context code (costs a bit of extra hash mem
Taco Hoekwater wrote:
Yue Wang wrote:
\def\defaultfontfile{file:lmmono10-regular}
After changing like this, XeTeX runs like a blink. (It wasted 6
seconds for each compile. now it won't)
Does that mean that the near-endless font issues with xetex are
now finally fixed?
no ... suffix
a font (in
typefaces) is found, it is remembered; for xetex i now added an extra
layer of remembering (the checks) so that misses in lookups might happen
less (it might speed up the MathGamma cases a bit but i didn't notice
much performance gain so it probably depends on other factors as well
On Tue, May 12, 2009 at 11:41 PM, Hans Hagen pra...@wxs.nl wrote:
Taco Hoekwater wrote:
Yue Wang wrote:
\def\defaultfontfile{file:lmmono10-regular}
After changing like this, XeTeX runs like a blink. (It wasted 6
seconds for each compile. now it won't)
Does that mean that the near-endless
Yue Wang wrote:
So why XeTeX is spending 6 seconds aimlessly? since ConTeXt asked it
to search for a non-existed font.
keep in mind that the font (lmmono10-regular) *is* existing, it's ust
that xetex cannot find it as it favors names instead of files (and
praise yourself happy that it's
in the morning, finally I know why
this is so slow on both XeTeX and pdfTeX.
This problem is not an operating system issue, But a ConTeXt feature.
in font-mkii, you use the following to define a actual font
(\definefontlocal and \definefontglobal):
{\expandafter\xdef\csname#1\endcsname
Hello,
I am using Context Mark II + XeTeX. I would like to know the
following things.
1. How to use opentype font features. I tried the following code but it is
not working.
\definefontfeature[myfontfea][+onum]
\definetypeface[Libertine][rm][Xserif][Linux Libertine
O][default
On May 11, 2009, at 4:05 AM, Corsair wrote:
Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body font,
with XeTeX. And I enable the `onum' feature so that all numbers in my
document appear as old-style numbers, which is good. But I also
prefer some of them use the normal capital
Am 10.05.2009 um 14:52 schrieb Arun Dev:
Hello,
I am using Context Mark II + XeTeX. I would like to know the
following things.
1. How to use opentype font features. I tried the following code but
it is not working.
\definefontfeature[myfontfea][+onum]
\definetypeface[Libertine][rm
Am 2009-05-11 um 08:13 schrieb Thomas A. Schmitz:
Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body
font,
with XeTeX. And I enable the `onum' feature so that all numbers in
my
document appear as old-style numbers, which is good. But I also
prefer some of them use the normal
On May 11, 2009, at 8:39 AM, Corsair wrote:
Thanks you for the reply! But it doesn't work for me, because small
cap numbers in Adobe Caslon Pro are themselves old-style...
I don't use XeTeX, but this works in mkiv:
\definefontfeature
[mydefault]
[mode
=
node
,script=latn,language
On Mon, May 11, 2009 at 08:37:46AM +0200, Henning Hraban Ramm wrote:
Am 2009-05-11 um 08:13 schrieb Thomas A. Schmitz:
Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body
font,
with XeTeX. And I enable the `onum' feature so that all numbers in
my
document appear
?
to what extend smallcaps are implemented is font dependent
Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body font,
with XeTeX. And I enable the `onum' feature so that all numbers in my
document appear as old-style numbers, which is good. But I also
prefer some of them use the normal
.
MkII (XeTeX): Write the code to use OpenType math fonts and send it to
Hans.
open type math in mkii is unlikely to happen soon (ok, at some point i
can just generate the symbol etc initializations from the mkiv lua
tables but it has a very low priority)
in mkiv there is some trickery
a module which has the same functionality as the fontspec
package for XeLaTeX.
http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf
Wolfgang
___
If your question is of interest to others as well, please
Hi, Hans:
I am working on Chinese support on XeTeX/ConTeXt and I almost finished
that. I will later upload a module called t-zhspacing to the garden
(or CTAN?). But there is one last problem. Let me explain like this.
Suppost I have two typescripts (typeA and typeB) and both with
complete
Hi Wolfgang:
nice script.
Can the module meet my needs discussed in
http://www.ntg.nl/pipermail/ntg-context/2009/040831.html ?
or is it possible to extend the support to xetex?
Yue Wang
On Mon, May 11, 2009 at 8:23 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Hi all,
I
Wolfgang Schuster wrote:
possible yes but it's a lot of work because the complete fallback mechanism
needs to be written for XeTeX which is available for MkIV since a while.
this is unlikely to happen (unless we add lots of optional code to mkii
to deal with xetex which then probably results
On Mon, May 11, 2009 at 9:48 PM, Hans Hagen pra...@wxs.nl wrote:
Wolfgang Schuster wrote:
possible yes but it's a lot of work because the complete fallback
mechanism
needs to be written for XeTeX which is available for MkIV since a while.
this is unlikely to happen (unless we add lots
Yue Wang wrote:
On Mon, May 11, 2009 at 9:48 PM, Hans Hagen pra...@wxs.nl wrote:
Wolfgang Schuster wrote:
possible yes but it's a lot of work because the complete fallback
mechanism
needs to be written for XeTeX which is available for MkIV since a while.
this is unlikely to happen (unless we
of knowledge of font mechanism)
Yue Wang
On Mon, May 11, 2009 at 8:08 PM, Yue Wang yuleo...@gmail.com wrote:
Hi, Hans:
I am working on Chinese support on XeTeX/ConTeXt and I almost finished
that. I will later upload a module called t-zhspacing to the garden
(or CTAN?). But there is one last
On Mon, May 11, 2009 at 10:33 PM, Hans Hagen pra...@wxs.nl wrote:
Yue Wang wrote:
On Mon, May 11, 2009 at 9:48 PM, Hans Hagen pra...@wxs.nl wrote:
Wolfgang Schuster wrote:
possible yes but it's a lot of work because the complete fallback
mechanism
needs to be written for XeTeX which
Dear list:
Chinese TeX Society is proud to announce the t-zhspacing module to the
ConTeXt society.
The module is developed by Yue Wang based on Yin Dian's zhspacing.sty
macro package and Jonathan Kew's unicode-letters.tex + xetex
interchartoks mechanism.
It is designed for the audience who
to the
ConTeXt society.
The module is developed by Yue Wang based on Yin Dian's zhspacing.sty
macro package and Jonathan Kew's unicode-letters.tex + xetex
interchartoks mechanism.
It is designed for the audience who interested perfect Chinese
typesetting using ConTeXt and XeTeX.
It handles Chinese
Hi, Hans and Mojca:
first, (to Mojca) the first-setup.sh script still deletes fontconfig
cache when updating on windows.
second, (to Hans) unicode-letters.tex is read when we dump plain TeX
or LaTeX format in TeXLive. This file is wrote by Jonathan Kew in
order to initialize XeTeX. It defines
Yue Wang wrote:
second, (to Hans) unicode-letters.tex is read when we dump plain TeX
or LaTeX format in TeXLive. This file is wrote by Jonathan Kew in
order to initialize XeTeX. It defines many important unicode
properties into XeTeX. However, ConTeXt do not load that file when
dumping
Am 11.05.2009 um 16:55 schrieb Yue Wang:
Dear list:
Chinese TeX Society is proud to announce the t-zhspacing module to the
ConTeXt society.
The module is developed by Yue Wang based on Yin Dian's zhspacing.sty
macro package and Jonathan Kew's unicode-letters.tex + xetex
interchartoks
Am 11.05.2009 um 15:48 schrieb Hans Hagen:
Wolfgang Schuster wrote:
possible yes but it's a lot of work because the complete fallback
mechanism
needs to be written for XeTeX which is available for MkIV since a
while.
this is unlikely to happen (unless we add lots of optional code
On Mon, May 11, 2009 at 18:38, Yue Wang wrote:
Hi, Hans and Mojca:
first, (to Mojca) the first-setup.sh script still deletes fontconfig
cache when updating on windows.
Hmmm ... while experimenting a bit and after writing a long answer
explaining that I'll come back to it after a while ... I
Mojca Miklavec wrote:
Hans, does this make sense?
local normalflags = states.get(rsync.flags.normal)
local deleteflags =
if (destination:find(texmf$) or destination:find(context$)) and
(not environment.argument(keep)) then
deleteflags = states.get(rsync.flags.delete)
end
command =
) using xetex to produce xdv, and xdvipdfmx that xdv to pdf.
Open the file in Acrobat Reader, Go to page three, and you can see a
hyperlink text Equation 1, it links to page 2. however, the equation
is in page1.
The section 1 or page 4 should point to page 4, but it point to page 5 now.
So my
Hi, Hans and Jonathan:
I made some testing samples in ConTeXt to test XeTeX. but the result
is quite strange. All benchmark are get from the second run:
Sample 1:
\definefont[a][file:SimSun]
\starttext
\dorecurse{1}{ hello {\a 你好}}
\stoptext
And here is the result:
XeTeX: TeXExec
, when
1) using pdftex to produce the dvi, and convert the dvi using dvipdfmx
2) using xetex to produce the pdf using xdvipdfmx
the figure is placed at the wrong place. there will be a displacement
for all the metapost figures when xetex is used to produce the
graphics. I attach the wrong result
extend smallcaps are implemented is font dependent
Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body font,
with XeTeX. And I enable the `onum' feature so that all numbers in my
document appear as old-style numbers, which is good. But I also
prefer some of them use the normal capital
).
But LM should suffer from the same problem.
How can I speed up math font loading? change add file: suffix (like
[file:rm-iwonar]) won't help :(
Core macros need to be changed somehow if you want to achieve that.
Hans doesn't use XeTeX, so you need strong arguments to convince him
to modify
Hi,
On Sat, Apr 25, 2009 at 5:39 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
On Sat, Apr 25, 2009 at 03:44, Yue Wang wrote:
Hi, Mojca:
However, when comment the second line (\definetypeface [iwona] [mm]
[math] [iwona] [default] [encoding=ec]),
TeXExec | runtime: 1.828
total
601 - 700 of 2328 matches
Mail list logo
