Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CE4FB10248 for ; Fri, 21 Mar 2014 22:54:54 +0000 (UTC) Received: (qmail 56882 invoked by uid 500); 21 Mar 2014 22:54:53 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 56847 invoked by uid 500); 21 Mar 2014 22:54:53 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 56839 invoked by uid 99); 21 Mar 2014 22:54:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 22:54:53 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of maurice.amsellem@systar.com designates 66.129.85.153 as permitted sender) Received: from [66.129.85.153] (HELO smtp02.myhostedservice.com) (66.129.85.153) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 22:54:47 +0000 Received: from EXHUB04.netplexity.local (172.29.211.24) by smtp02.myhostedservice.com (172.29.211.12) with Microsoft SMTP Server (TLS) id 14.2.347.0; Fri, 21 Mar 2014 18:54:00 -0400 Received: from EXMBX05.netplexity.local ([fe80::cc58:cfe7:ba3b:fae]) by exhub04 ([172.29.211.24]) with mapi id 14.03.0146.000; Fri, 21 Mar 2014 18:54:24 -0400 From: Maurice Amsellem To: "dev@flex.apache.org" Subject: RE: RTL support in mobile apps Thread-Topic: RTL support in mobile apps Thread-Index: Ac9FUn6bFrI7V5yWQnW++Z0K/8ysYAABdfdA Date: Fri, 21 Mar 2014 22:54:23 +0000 Message-ID: <2095F5EBE04D59409DFCE91FFCEBF7AFAF2DA94E@EXMBX05.netplexity.local> References: <2095F5EBE04D59409DFCE91FFCEBF7AFAF2DA925@EXMBX05.netplexity.local> In-Reply-To: <2095F5EBE04D59409DFCE91FFCEBF7AFAF2DA925@EXMBX05.netplexity.local> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.29.211.35] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org And this one on StyleableTextField:=20 http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c698e85712b301= 1fe73-7fff.html#WS19f279b149e7481c7c94ce7c12b30152f48-7ffc -----Message d'origine----- De=A0: Maurice Amsellem [mailto:maurice.amsellem@systar.com]=20 Envoy=E9=A0: vendredi 21 mars 2014 23:41 =C0=A0: dev@flex.apache.org Objet=A0: RTL support in mobile apps Hi Team, Ori Segal has reported a problem in TextInput default skin with RTL (Hebrew= , arabic) layout. I have fixed this problem. Now he has reported a problem in TextInput "prompt" text not being displaye= d in RTL. So I did a small test: set layoutDirection=3D"rtl" to a sample mobile app (= with buttons, mobilegrid, etc..) and almost every text disappeared. The only texts that seem to be displayed correctly are: - TextInput / TextArea with the default text (that is using native StageTex= t) - spark Label, that is using TextLine (and the new FTE/TLF engine). Everything else, that uses the mobile-optimized StyleableTextField, will no= t display RTL (apparently because it's based on the old TextField engine). Reading the articles below, it seems clear enough that RTL is NOT supported= on AIR mobile (with a few exceptions): http://sourceforge.net/adobe/flexsdk/wiki/Mobile%20Text%20Components/=20 http://help.adobe.com/en_US/flex/using/WS02f7d8d4857b1677-165a04e1126951a2d= 98-7ffe.html=20 http://help.adobe.com/en_US/flex/using/WS02f7d8d4857b1677-165a04e1126951a2d= 98-7ffd.html Alex, as you seem to have been involved in that, do you confirm? Something else: The first article says: " Primarily for performance reasons and support for native predictive text = input and editing, mobile will use TextField-based text in all critical are= as. This is expected to be a short-term solution until a performant version= of FTE arrives on mobile." So has FTE been optimized for mobile since the article was written , for ex= ample in AIR 4.0?=20 Thanks=20 Maurice=20