<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Ulrike</p>
<p><br>
</p>
<p>This is exactly what parsitex does; you never need to use a lot of code but all you need is built inside the engine. The parsitex takes the TeX--XeT model as a starting point but extends it considerably.</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><span id="x_ms-rterangepaste-start"></span></p>
<div><br>
</div>
<div></div>
<span id="x_ms-rterangepaste-end"></span><br>
<p></p>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> XeTeX <xetex-bounces@tug.org> on behalf of Ulrike Fischer <news3@nililand.de><br>
<b>Sent:</b> Wednesday, November 23, 2016 2:11:22 AM<br>
<b>To:</b> xetex@tug.org<br>
<b>Subject:</b> Re: [XeTeX] Are the new etex changes reflected in XeTeX? (was XeTeX bugs in bidirectional typesetting)</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Am Tue, 22 Nov 2016 13:09:49 +0000 schrieb Vafa Khalighi:<br>
<br>
> Hi David and Ulrike<br>
<br>
> The LuaTeX (omega) model in this case is simply wrong! <br>
<br>
Well as far as I can see the TeX-Xet and TeX--XeT models always put<br>
the parindent box on the *left*. This means this models starts from<br>
left-to-right as the "normal direction" and adds right-to-left as<br>
additional feature on top. From the historical development this is<br>
understandable. <br>
<br>
But if I were part of a right-to-left writing culture I would prefer<br>
a model which tries to handle both directions in the same way and<br>
where writing a right-to-left text doesn't involve tons of codes and<br>
\everypar juggling. <br>
<br>
<br>
<br>
-- <br>
Ulrike Fischer <br>
<a href="http://www.troubleshooting-tex.de/">http://www.troubleshooting-tex.de/</a><br>
<br>
<br>
<br>
--------------------------------------------------<br>
Subscriptions, Archive, and List information, etc.:<br>
<a href="http://tug.org/mailman/listinfo/xetex">http://tug.org/mailman/listinfo/xetex</a><br>
</div>
</span></font>
</body>
</html>