Hi Flashers,\r\rI’m doing a Flash MC which loads some dynamic text from a .txt source file. The thing is that if the .txt file, contains special characters like Spanish-French é è á ñ etc, Flash MX does not recognize them when exporting or testing the movie, and instead it displays a "↨"or a missing letter. \rThat did not happen with Flash 5, why is that so? Is there any option I’m missing to avoid it? Haven’t been able to find it. Has anybody experienced something similar??\r\rThank you,\rManare
i url-encoded all the text before import. seemed to do the trick.
It’s possible that you don’t have the outlines included for all characters for the text field. I’ve had that return some unpredictable results before.
Hi,\rNope, somebody from Macromedia posted this somewhere (and it does work) :\r\r----------------\rThe problem is that the Flash Player 6 uses Unicode and your French text is not Unicode. If you do not want to use UTF-8 Unicode, then a simple workaround is to use the following ActionScript on your movie’s first frame: \r\rSystem.useCodepage=true \r\rHere’s some more information from Flash Blog radio.weblogs.com/0102755…ssues.html\r\rInternational Character Support (Gotcha/Lack of Documentation) \r\rIn the authoring tool: In the MX authoring tool, you can enter any characters in your current code page. For English (and other European) systems, this is Latin-1 or MacRoman. The OS doesn’t support the entry of Chinese characters (for example) into entry fields because the code page doesn’t support it. \r\rFor actionscript, you can work around this by #include of an actionscript file. The .as file should be UTF8 and contain the first line: \r\r//!-- UTF8 \r\rso that MX will know its a UTF-8 text file. You can put any characters in any language in that file that you wish, and should be correctly displayed by the Flash Player. \r\rIn the Flash player: The Flash player is completely Unicode. It can display in any language available on your OS, and take input in any language supported by your OS. This varies by OS: NT, 2K, and XP will allow an English system to run a Japanese IME, which will put Japanese characters into dynamic text fields, mixed with any other language you have input support for. Output is supported in any language you have font packs for. (Although it is limited to left to right character sets.) The 9x kernels are somewhat more limited, but still support multi language output in almost all cases. \r\rWhen loading data (via LoadVariables or XML) the Flash 6 player will assume UTF-8 encoding unless system.useCodepage = true, in which case it will load in the current codepage, Latin-1 in the case above. This does mean that if you load Latin-1 data, that contains high ASCII, into a Flash Player 6 without useCodepage set, it will be garbage! The encoding is not set correctly. You need to use UTF-8 data or set useCodepage. \r\r-------------------------\r;)
Nah\r\rJust use word and convert the txt file to unicode when saving save as text document with code, and that´s it