I put in some code to handle whitespace chars. Or do we need to handle
all chars in some unicode ranges?
-Alex
On 3/9/17, 10:42 AM, "Harbs" wrote:
>Here’s one of them:
>
>static private const anyPrintChar:RegExp =
>/[^\u0009\u000a\u000d\u0020]/g;
>
>outputs:
>
>org.apache.flex.textLayout.eleme
Here’s one of them:
static private const anyPrintChar:RegExp = /[^\u0009\u000a\u000d\u0020]/g;
outputs:
org.apache.flex.textLayout.elements.SpanElement.anyPrintChar = /[^
]/g;
> On Mar 9, 2017, at 8:20 PM, Harbs wrote:
>
> Yes. These are from TLF. The strings are evaluated by Java. T
Yes. These are from TLF. The strings are evaluated by Java. There’s no error
except on the Javascript side because the string literals become non-sensical.
We had a similar issue when porting our app. I think we used
String.fromCharCode() to get around the problem there.
Basically, we need some
Are these from TLF? What error are you getting? Falcon compiles TLF as
part of the integration tests. Is it the JS output that is broken?
Thanks,
-Alex
On 3/9/17, 1:18 AM, "Harbs" wrote:
>I’ve come across quite a few regex patterns which break compilation.
>Here’s some examples:
>
>private s
