There's definately an SDK (or flash player?) related bug regarding trace().
With some SDK's, tracing special characters works fine in others it doesn't
(using the same FlashBuilder version).
var chars:String = "éàçè";
trace(" - characters: ", chars);
SDK 4.1:
// Constole output
- characters: éàçè
SDK 4.5.1:
// Console output
- characters: ���
Not sure what will turn up in the email, but the above shows 3 squares.
SDK 4.9.1
// Console output
- characters: éàçè
I don't have 4.10 installed (because AIR 3.8 is broken), so I can't test with
4.10 atm.
----- Original Message -----
From: "Mark Line" <markl...@gmail.com>
To: <users@flex.apache.org>
Sent: Thursday, August 29, 2013 3:19 PM
Subject: RE: Pb with special characters and accents
I think é is turning into é because trace() only outputs in UTF-8 while
the input of is probably in latin1. Which means the way the characters are
stored as binary data with differ.
I don't think you will get a bug fixed or similar trace is just a low level
function of flash player used for debugging/development.
Maybe write your own logger? That's what I currently do in a large project
and dependant on the target (fp/air/mobile) do different things with the
output. EG on Air create a rolling log file
-----Original Message-----
From: manitas manitas [mailto:manitas0...@gmail.com]
Sent: 29 August 2013 12:26
To: users
Subject: Re: Pb with special characters and accents
Thank you so much Mark, it works with the escape function.
This workaround works but doesn't help me to understand the whole thing,
does it means URLVariables use a different default charset ? how to change
it ? Is it relevant create a bug report for that ?
and I still have my 2 others questions :
Why the output of trace("omé") is omé ? Is it relevant create a bug report
for that ?
Where I can find documentation to know how to manage charset in a flex app ?
Thanks in advance for your support.
