From: mohd zamri murah <mohdzamrimurah@gmail.com>
Subject: Re: arabtex support - we broke something
Date: Thu, 24 Feb 2005 23:15:20 +0800 [thread overview]
Message-ID: <511594c305022407153f0f4370@mail.gmail.com> (raw)
In-Reply-To: <421D14E0.7000602@wxs.nl>
Using test.tex and your new m-arabtex.tex, it fail. log and my solution below.
========= test.tex ====================================
\input m-arabtex
\usetypescript[postscript] \switchtotypeface[postscript]
\starttext
\setarab \novocalize
\section{\<mu.hammad>} %short arabic use \< ..>
here is some text in english. here in arabic .\<mu.hammad>. we can mix
them. hurray. we get both of them together. we can see this is fun and
going nowhere.
\startarabic % long arabic
kAjyn ayn mmr.hAl sAtw prwtwtA'yp awntwq mnjAnkn dwkwmn jAwy dry
dwkwmn rwmy .
<hei, I am in english>
ay mggwnAkn kwnsyp pgatwrcArA'n brAsAskn kwmpwnwn .
ay mggwnAkn kwnsyp pgatwrcArA'n brAsAskn kwmpwnwn.
\stoparabic
\stoptext
================================================
error log;
! Extra \else.
\test@space ...\a@@putword \xpa \kill@space \else
\xpa \next@command \fi
<to be read again>
....
my solution;
comment these lines; (near line 402 ). probably the support for hebrew
broke things.
another possibility is that all these 3 files already loaded by
m-arabtex.tex and reload them break things.
% \ReadFile{hebtex.sty}
% \ReadFile{apatch.sty}
% \ReadFile{hepatch.sty}
and the file compile OK.
I don't knew hebrew, however, I will try to understand the hebrew support.
the character "|" and "~" still produce "illegal command" in
\startarabic...\stoprabic. will try to trace this one.
be happy to write the manual later.
zamri
On Thu, 24 Feb 2005 00:42:24 +0100, Hans Hagen <pragma@wxs.nl> wrote:
> Hi,
>
> I cleaned up the files a bit (first step); can you test these?
>
> \input m-arabtex % new version of \usemodule will accept long names
>
> can you also take a loot at hebrew? (if you look in the file you can see the old
> hebrew font def with the strange fontdimen settings;
>
> maybe we should replace \vocalize and such by proper key/val settings (options
> or so); do you have a list of meaningful ones?
>
> we also need a manual then -)
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
>
>
next prev parent reply other threads:[~2005-02-24 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 2:54 arabtex support mohd zamri murah
2005-02-23 8:27 ` Hans Hagen
2005-02-24 3:47 ` mohd zamri murah
2005-02-24 10:40 ` h h extern
[not found] ` <421D14E0.7000602@wxs.nl>
2005-02-24 15:15 ` mohd zamri murah [this message]
2005-02-24 22:00 ` arabtex support - we broke something h h extern
2005-02-25 11:30 ` mzm
2005-02-27 20:55 ` h h extern
2005-03-03 13:13 ` mzm
2005-03-05 23:05 ` h h extern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511594c305022407153f0f4370@mail.gmail.com \
--to=mohdzamrimurah@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).