| FAQ |
| |
|
| Locale |
| |
|
| Q: |
Why do some characters show up as "empty boxes"
instead of the proper character? |
| A: |
The Unicode character set contains over 65,000 characters,
more than 30,000 of which are printable. Most fonts do not contain
artwork for all 30,000 printable characters, so characters that
are not represented by the font are displayed as those "empty
boxes". To display those characters, you will need a font
that contains them. Most fonts only contain the basic Latin
characters, although many of the common fonts that come with
the major operting systems also include the extended Latin,
Greek, Cyrillic, Hebrew, and Arabic character sets, for example
the font used in the demo on the documentation page is the Arial
TrueType font that comes with most operating systems (Windows,
Mac, etc), and is capable of displaying Arabic, Greek, Hebrew,
Cyrillic, and Latin characters, as well as a few other character
sets. |
| |
|
| Q: |
Why can't I unformat certain dates? |
| A: |
Date objects that are formatted to time-only formats lose
their day/month/year values and cannot be converted back into
a Flash Date object. |
| |
|
| Q: |
When I unformat a date, the day/time has changed! |
| A: |
This is most likely because you are using the getDate or a
similar method of the Date object. These methods automatically
apply your local system timezone offset, so a date that was
saved as 6:00 am on Jan 1st will be displayed as 12:00 pm on
Dec 31st if you are in the Central Standard Timezone (GMT-6:00).
All dates are treated as UTC (Universal Time Code, GMT+0:00)
within the Locale object. Formats that omit time will be set
to midnight UTC when converted back into a date object, which
may cause discrepancies if you are using the getDate method
instead of getUTCDate. Locale is independant of time zone, so
all dates and times are treated as UTC in the Locale object
to eliminate problems with dates formatted in one timezone and
unformatted in another. |
| |
|
|
|
