Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sat, 7 Nov 2009 12:57:23 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id nA7BvMNk005122 for ; Sat, 7 Nov 2009 12:57:23 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id nA7Bs9qg003489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 7 Nov 2009 12:54:09 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id nA79mjm5002519; Sat, 7 Nov 2009 12:54:07 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 353055 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 7 Nov 2009 12:54:07 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id nA7Bs7im030865 for ; Sat, 7 Nov 2009 12:54:07 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id nA7Bs3nm003045 for ; Sat, 7 Nov 2009 12:54:07 +0100 Received: from morse.mittelbach-online.de (p54A85B52.dip.t-dialin.net [84.168.91.82]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0M1RJx-1MHvQg0k4P-00txW9; Sat, 07 Nov 2009 12:54:03 +0100 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id 3B4696EE6C; Sat, 7 Nov 2009 12:54:00 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19189.17593.814557.704925@morse.mittelbach-online.de> <605202f20911070250m4f76f7fcx1e2217837123246@mail.gmail.com> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V01U2FsdGVkX1/8gqiXdKwq1TkRsJfaz+PaQlb/FzTCUpjvpT7 c64zU273En/sn57fEaeM+LYt4g9MozDF7hnTQF2z9BT6hkUoVQ Y601BVCI1hY++Rhtj7r9w== X-Spam-Whitelist-Provider: Message-ID: <19189.24536.52416.632993@morse.mittelbach-online.de> Date: Sat, 7 Nov 2009 12:54:00 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: an object type for heading commands To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <605202f20911070250m4f76f7fcx1e2217837123246@mail.gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -106.599 () BAYES_00,RCVD_IN_DNSWL_MED,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 07 Nov 2009 11:57:23.0274 (UTC) FILETIME=[778022A0:01CA5FA1] Status: R X-Status: X-Keywords: X-UID: 6133 Hi Vafa, > This is the work for LaTeX3 right? if Yes, are you or anyone else of the > LaTeX team plans to add bidirectional support to LaTeX3? Having > bidirectional support in heading commands is vital. And depending on the > engine used, different sort of macro programming is required. all discussions on this list are supposed to concentrate around L3 stuff, so yes to the first question. There is also a yes to the second question. However, as far as a heading interface question is concerned, is there anything that affects that (the interface, not the inner part of an implementation)? I would claim, that no there isn't. the content of an argument to a heading, e.g, the title, etc would need to be able to allow for specifying writing direction, but that would be within the argument and not explicitly specified on the outside. Or not? If so I would would be interested in seeing examples of what you have in mind. thanks frank