Ilda Khaki wrote:
Hi,
This is the macro for Jalali Calendar taken from xepersian
\newif\i...@leap \newif\i...@kabiseh
\newcount...@i \newcount...@y \newcount...@m \newcount...@d
\newcount...@latini\newcount...@persiani
Am 22.02.2009 um 16:00 schrieb John Devereux:
I would like to use texexec to post-process a large pdf file, so as to
prepare it for double sided printing. The existing file has a large
left hand margin on each page, so as to allow binding.
I would like to change this so that odd (right) pages
Otared Kavian wrote:
Hi Hans, Khaled, and Idris,
If a humble opinion from an ordinary user may be issued, I agree with
Khaled that it would be extremely useful to have some basic default
settings for Arabic fonts, and even more generally for any particular
fonts used for other languages.
Khaled Hosny wrote:
I totally agree with you, more ever I hop that at some point in the
future, just selecting certain language will be enough to get proper
display of it, some thing like:
\mainlanguage[arabic]
\startext
أهلا بالعالم!
\stoptext
to some extend that can already be done with
On Mon, Feb 23, 2009 at 11:53:30AM +0100, Hans Hagen wrote:
\setupbodyfont[arabic=foo,latin=bar]
for that we have the fallbacks mechanism; of course one can mix any font
but even then it always demands tuning, i.e. foo and bar can look
completely weird when combined without relative
On Feb 23, 2009, at 1:09 PM, Khaled Hosny wrote:
For scaling, we can specify a size, some thing like:
\setupbodyfont[arabic=foo,20pt,latin=bar,18pt]
or so.
I don't know Arabic, but I've done similar things for Greek, and that
is not a good interface. You want a scaling factor, so users
On Mon, Feb 23, 2009 at 11:42:41AM +0100, Hans Hagen wrote:
Otared Kavian wrote:
Hi Hans, Khaled, and Idris,
If a humble opinion from an ordinary user may be issued, I agree with
Khaled that it would be extremely useful to have some basic default
settings for Arabic fonts, and even more
Thomas A. Schmitz wrote:
On Feb 23, 2009, at 1:09 PM, Khaled Hosny wrote:
For scaling, we can specify a size, some thing like:
\setupbodyfont[arabic=foo,20pt,latin=bar,18pt]
or so.
I don't know Arabic, but I've done similar things for Greek, and that is
not a good interface. You want a
On Mon, Feb 23, 2009 at 01:17:42PM +0100, Thomas A. Schmitz wrote:
On Feb 23, 2009, at 1:09 PM, Khaled Hosny wrote:
For scaling, we can specify a size, some thing like:
\setupbodyfont[arabic=foo,20pt,latin=bar,18pt]
or so.
I don't know Arabic, but I've done similar things for Greek, and
Thanks, Aditya,
You said that there was no problem in compiling your test file with
MKII. So, MKII is finding t-ancientgreek. But kpsewhich does not
find it.
When you compile the file in MKII, which t-ancientgreek is being
used (the whole path should be in the log file.
On Mon, Feb 23, 2009 at 02:25:15PM +0200, Khaled Hosny wrote:
so, it seems to depend on calt but turning on calt by default is *not*
what the ms spec recommends for arabtype
you see the problem?
I think is is arabtype's problem if they suggest turning calt off by
default, if I've
Khaled Hosny wrote:
I think is is arabtype's problem if they suggest turning calt off by
default, if I've contextual alternatives in my font this means I think
those alternatives are necessary to render text correctly, otherwise I
would have used a stylistic set.
it's not arabtype that
On Mon, 23 Feb 2009, Alan Bowen wrote:
Thanks, Aditya,
You said that there was no problem in compiling your test file with MKII.
So, MKII is finding t-ancientgreek. But kpsewhich does not find it.
When you compile the file in MKII, which t-ancientgreek is being used (the
whole path
Hello,
Where can I find a description of what happens between (Lua)TeX runs ?
Thanks,
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
Alan Stone wrote:
Hello,
Where can I find a description of what happens between (Lua)TeX runs ?
in mtx-context.lua
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH
On Mon, Feb 23, 2009 at 3:58 PM, Hans Hagen pra...@wxs.nl wrote:
Alan Stone wrote:
Hello,
Where can I find a description of what happens between (Lua)TeX runs ?
in mtx-context.lua
Euh... I meant: in english. ;O)
Alan
On Mon, 23 Feb 2009 05:02:39 -0700, Khaled Hosny khaledho...@eglug.org
wrote:
I'm not very fond if Scheherazade as it has many wrong glyphs (most of
the Quranic glyphs are completely wrong) and it doesn't even have an الله
ligature, which most Arabic users won't accept.
There is a hadith
Alan Stone wrote:
On Mon, Feb 23, 2009 at 3:58 PM, Hans Hagen pra...@wxs.nl wrote:
Alan Stone wrote:
Hello,
Where can I find a description of what happens between (Lua)TeX runs ?
in mtx-context.lua
Euh... I meant: in english. ;O)
it does the same as texexec but a bit less (no mp runs
On Sun, Feb 22, 2009 at 22:00, Alan Bowen wrote:
Thanks, Thomas.
I have moved HOMETEXMF to ~/temf and have set HOMETEXMF = ~/texmf in my
configuration file (in ConTeXtMinimals/tex/texmf-local/web2c/).
When I first set this up with Mocja, I (we?) had HOMETEXMF =
~/Library/texmf.
Hello,
I did not try to analyze how the following macros work (they are too
complex), but they somehow fail in mkiv. (I don't need the F
kerning, so that portion of code may go away, but the macro itself is
very very handy.)
All I want is to have a macro that converts _{...} into \low{...}
and
Hello (Hans, Aditya),
I know that neither of you is interested in mkii at the moment, but
there's a nasty bug that probably has a trivial fix in alignment
environments. Unicode characters have some problems inside
\intertext{...}
\startformula\startalign
\intertext{še če je že}
Am 23.02.2009 um 17:21 schrieb Mojca Miklavec:
Hello,
I did not try to analyze how the following macros work (they are too
complex), but they somehow fail in mkiv. (I don't need the F
kerning, so that portion of code may go away, but the macro itself is
very very handy.)
All I want is to
On Mon, Feb 23, 2009 at 01:28:23PM +0100, Hans Hagen wrote:
Thomas A. Schmitz wrote:
On Feb 23, 2009, at 1:09 PM, Khaled Hosny wrote:
For scaling, we can specify a size, some thing like:
\setupbodyfont[arabic=foo,20pt,latin=bar,18pt]
or so.
I don't know Arabic, but I've done similar
I believe you should write
عربي 1234 عربي ({\language[en] English 1234 English (English) English}) عربي.
then the font switch can be made to do something sensible with the font
(and/or font callbacks).
Best wishes,
Taco
Wolfgang Schuster schuster.wolfg...@googlemail.com writes:
Am 22.02.2009 um 16:00 schrieb John Devereux:
I would like to use texexec to post-process a large pdf file, so as to
prepare it for double sided printing. The existing file has a large
left hand margin on each page, so as to allow
This is a problem with math support in a particular beta version a few
weeks ago. It has been fixed in the meantime; the latest beta works
normally, but in order to install it, you will have to either wait for
Taco to make a new snapshot of luatex available at supelec.fr or
compile luatex
Aditya—
I have tried symlinks (as you indicate) and even just putting my texmf
folder into /Applications/ConTeXtMinimals/tex/texmf-project and
neither worked.
BUT putting the contents of my personal texmf folder into /
Applications/ConTeXtMinimals/tex/texmf-project did make the Greek
- does using \doifundefined{myMacro}{...} shorten tex runs/compile time ?
- what are the features to avoid for shortest compile times ?
--
Alan
___
If your question is of interest to others as well, please add an
On Mon, Feb 23, 2009 at 06:01:35PM +0100, Taco Hoekwater wrote:
I believe you should write
عربي 1234 عربي ({\language[en] English 1234 English (English) English})
عربي.
then the font switch can be made to do something sensible with the font
(and/or font callbacks).
Sure I can do,
Am 23.02.2009 um 18:04 schrieb John Devereux:
Wolfgang Schuster schuster.wolfg...@googlemail.com writes:
Am 22.02.2009 um 16:00 schrieb John Devereux:
I would like to use texexec to post-process a large pdf file, so
as to
prepare it for double sided printing. The existing file has a
Am 23.02.2009 um 18:16 schrieb Alan Stone:
- does using \doifundefined{myMacro}{...} shorten tex runs/compile
time ?
In which way?
- what are the features to avoid for shortest compile times ?
Depends on your document and what do you want.
To give you a better answer speak in complete
On Mon, 23 Feb 2009 10:15:02 -0700, Khaled Hosny khaledho...@eglug.org
wrote:
The key point is that SIL has taken care to support nearly every
Arabic-script language, not just Arabic, so this gives us a platform
that
all Arabic-script users can use by default until other free fonts -- or
Thanks, Thomas. This is a great help.
But one question before I do this: if I remove the --context=beta
switch will running first-setup.sh install the last stable minimal
version?
Alan
On Feb 23, 2009, at 12;40,14 , Thomas A. Schmitz wrote:
This is a problem with math support in a
On Mon, Feb 23, 2009 at 5:52 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.02.2009 um 17:21 schrieb Mojca Miklavec:
Hello,
I did not try to analyze how the following macros work (they are too
complex), but they somehow fail in mkiv. (I don't need the F
kerning, so
But one question before I do this: if I remove the --context=beta switch
will running first-setup.sh install the last stable minimal version?
yes, (it's written near the end of first-setup.sh)
--
luigi
___
If your
Alan Stone wrote:
- what are the features to avoid for shortest compile times ?
Typesetting and macro expansion. Together they are good for
at least 90% of your running time :)
Seriously: it depends, but watch out for unnecessary use of
\switchtobodyfont.
Best wishes,
Taco
Thanks, Luigi.
A.
On Feb 23, 2009, at 13;26,48 , luigi scarso wrote:
But one question before I do this: if I remove the --context=beta
switch
will running first-setup.sh install the last stable minimal version?
yes, (it's written near the end of first-setup.sh)
--
luigi
Wolfgang Schuster schuster.wolfg...@googlemail.com writes:
Am 23.02.2009 um 18:04 schrieb John Devereux:
Wolfgang Schuster schuster.wolfg...@googlemail.com writes:
Am 22.02.2009 um 16:00 schrieb John Devereux:
I would like to use texexec to post-process a large pdf file, so
as to
prepare
When opening ConTeXt generated pdf's in Windows Vista, a message window pops
up saying something as (translated to english):
- title: preparation of document contents
- message: please wait while the contents of your document is being
prepared + progress bar page x of total pages
This doesn't
On Mon, Feb 23, 2009 at 6:54 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.02.2009 um 18:16 schrieb Alan Stone:
- does using \doifundefined{myMacro}{...} shorten tex runs/compile time ?
In which way?
As I don't know/understand what happens between (Lua)TeX runs,
I have run the ./first-setup.sh without the switch --context=beta and
I still get what I had before
ConTeXt ver: 2009.01.18 14:39 MKII fmt: 2009.2.23 int: english/
english
a beta version (I gather) which in any case does not work.
Apparently there is no easy way to go back. So what about
On Mon, Feb 23, 2009 at 9:03 PM, Alan Bowen acbo...@princeton.edu wrote:
I have run the ./first-setup.sh without the switch --context=beta and I
still get what I had before
ConTeXt ver: 2009.01.18 14:39 MKII fmt: 2009.2.23 int: english/english
a beta version (I gather) which in any case
On Mon, 23 Feb 2009, luigi scarso wrote:
On Mon, Feb 23, 2009 at 9:03 PM, Alan Bowen acbo...@princeton.edu wrote:
I have run the ./first-setup.sh without the switch --context=beta and I
still get what I had before
ConTeXt ver: 2009.01.18 14:39 MKII fmt: 2009.2.23 int: english/english
a beta
On Mon, Feb 23, 2009 at 8:57 PM, Alan Stone
software.list.1e...@gmail.comwrote:
On Mon, Feb 23, 2009 at 6:54 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.02.2009 um 18:16 schrieb Alan Stone:
- does using \doifundefined{myMacro}{...} shorten tex runs/compile time ?
On Mon, Feb 23, 2009 at 9:26 PM, Alan Stone
software.list.1e...@gmail.com wrote:
On Mon, Feb 23, 2009 at 8:57 PM, Alan Stone software.list.1e...@gmail.com
wrote:
On Mon, Feb 23, 2009 at 6:54 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.02.2009 um 18:16 schrieb Alan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo all!
The following lines demonstrates my problem:
{
\setupspacing[packed]
\startalignment[right]
.
.
.
.
.\space{}
.
Am 23.02.2009 um 21:52 schrieb Bernd Kosubek:
If I run texexec over this, the last three line are longer
than the first line AND they have the same lengths.
What have I not understand -- or is it a known problem or a
bug?
You get what you write.
2. Sentence: \space{} = 2 spaces because of
Am 23.02.2009 um 20:57 schrieb Alan Stone:
- does using \doifundefined{myMacro}{...} shorten tex runs/compile
time ?
In which way?
As I don't know/understand what happens between (Lua)TeX runs, to
keep macro
definitions in memory.
The only way to use information from a previous run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 23. Februar 2009 21:56 schrieb Wolfgang Schuster:
Am 23.02.2009 um 21:52 schrieb Bernd Kosubek:
If I run texexec over this, the last three line are
longer than the first line AND they have the same
lengths.
What have I not
Am 23.02.2009 um 22:35 schrieb Bernd Kosubek:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 23. Februar 2009 21:56 schrieb Wolfgang Schuster:
Am 23.02.2009 um 21:52 schrieb Bernd Kosubek:
If I run texexec over this, the last three line are
longer than the first line AND they have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 23. Februar 2009 22:34 schrieb Wolfgang Schuster:
Nonsense, the first \space produce a space and the
whitespace in the input between \space and is
gobbled from the macro.
The empty group after the second space prevents TeX from
Aditya and Luigi—many thanks.
I will reinstall the minimals just as soon as ./first-setup.sh can get
to a stable version. Your advice about texmf-project seems good to me.
I now have two shells (one for stable ConTeXt and one for betas) as
well.
Cheers, Alan
On Feb 23, 2009, at 15;24,20
On Mon, 23 Feb 2009, Alan Bowen wrote:
Aditya and Luigi—many thanks.
I will reinstall the minimals just as soon as ./first-setup.sh can get to a
stable version.
In first-setup.sh, remove --context=beta from the last line.
On Mon, Feb 23, 2009 at 10:56:07AM -0700, Idris Samawi Hamid wrote:
So just start with Arabic, then Farsi, and forget the rest for now. No
need for perfection at the outset ;-)
Actually, I suggest forgetting about ligatures etc. for now, and just get
the basics done for Scheherazade. We
Am 23.02.2009 um 17:27 schrieb Mojca Miklavec:
Hello (Hans, Aditya),
I know that neither of you is interested in mkii at the moment, but
there's a nasty bug that probably has a trivial fix in alignment
environments. Unicode characters have some problems inside
\intertext{...}
On Mon, 23 Feb 2009 15:51:13 -0700, Khaled Hosny khaledho...@eglug.org
wrote:
On Mon, Feb 23, 2009 at 10:56:07AM -0700, Idris Samawi Hamid wrote:
So just start with Arabic, then Farsi, and forget the rest for now. No
need for perfection at the outset ;-)
Actually, I suggest forgetting about
Khaled Hosny wrote:
On Mon, Feb 23, 2009 at 01:28:23PM +0100, Hans Hagen wrote:
Thomas A. Schmitz wrote:
On Feb 23, 2009, at 1:09 PM, Khaled Hosny wrote:
For scaling, we can specify a size, some thing like:
\setupbodyfont[arabic=foo,20pt,latin=bar,18pt]
or so.
I don't know Arabic, but I've
Alan Stone wrote:
- does using \doifundefined{myMacro}{...} shorten tex runs/compile time ?
not that much
- what are the features to avoid for shortest compile times ?
most code is rather optimized
you can best avoid redundant font switches
Alan Stone wrote:
When opening ConTeXt generated pdf's in Windows Vista, a message window pops
up saying something as (translated to english):
- title: preparation of document contents
- message: please wait while the contents of your document is being
prepared + progress bar page x of total
Alan Stone wrote:
Correction: to avoid spending time redefining macros in case their
definitions are kept in memory between Lua(TeX) runs.
i'm not sure what you mean, but defining a bunch of macros at runtime is
not that time consuming
Hans
Mojca Miklavec wrote:
Hello,
Maybe this is just one incompatibility I need to live with, but maybe
it could be fixed. You can try to compare results in mkii and mkiv.
The text Section is called is desplayed in black in mkii and in red
in mkiv. (It made some of my documents look funny. I can fix
Thomas A. Schmitz wrote:
On Feb 21, 2009, at 12:07 AM, Alan Bowen wrote:
Aditya—
luatools --expand-var TEXMF gets
Am 24.02.2009 um 00:48 schrieb Hans Hagen:
Mojca Miklavec wrote:
Hello,
Maybe this is just one incompatibility I need to live with, but maybe
it could be fixed. You can try to compare results in mkii and mkiv.
The text Section is called is desplayed in black in mkii and in red
in mkiv. (It
Hi,
I'm using ConTeXt to create a small table of
unicode characters. Below is my current test. The
codes are:
U+2019 is a single quotation mark
U+2610 should be a ballot box
U+226b should be a much greater than ()
U+2115 should be the N as used to represent the natural numbers
I get 2019
Hi Thomas,
thank you very much, this works fine. But, something must have been
changed, that my old program settings suddenly didn't work.
Greetings
Albrecht
On Fri, 20 Feb 2009, Thomas Floeren wrote:
Hi Albrecht,
have you tried my proposal from 13.2.08?
maybe someone should research LuaJIT; http://luajit.org/
lua vs luajit;
http://shootout.alioth.debian.org/u32q/benchmark.php?test=alllang=luajitlang2=luabox=1
thoughts?
Alan Stone wrote:
- does using \doifundefined{myMacro}{...} shorten tex runs/compile time ?
- what are the features to
66 matches
Mail list logo