It looks like the Flex SDK compiler supports \uXXXX in MXML even though it doesn't support others like \n and \t. I'll get it fixed.
-- Josh Tynjala Bowler Hat LLC https://bowlerhat.dev/ On Thu, Mar 13, 2025 at 9:09 AM Josh Tynjala <joshtynj...@bowlerhat.dev> wrote: > It's probably this commit: > > > https://github.com/apache/royale-compiler/commit/5dde356731d622fecf61720c3b9d321b5bac743f > > I will double-check to see how the Flex SDK compiler behaves with unicode > escape sequences in MXML. > > You may need to switch to ° instead. > > -- > Josh Tynjala > Bowler Hat LLC > https://bowlerhat.dev/ > > > On Thu, Mar 13, 2025 at 1:00 AM Harbs <harbs.li...@gmail.com> wrote: > >> I have an attribute in MXML which looks like this: >> >> suffix="\u00B0” >> >> This used to correctly set the “suffix” property to the specified unicode >> value. Currently it seems like it’s parsed as a \\u00B0 literal string. >> >> I’m not sure when this changed. > >
