This is an automated email from the ASF dual-hosted git repository.
joshtynjala pushed a commit to branch flexdoc
in repository https://gitbox.apache.org/repos/asf/flex-site.git
commit 72622495dd1b605fa01fca54a1ede3f872294b84
Author: Josh Tynjala <joshtynj...@bowlerhat.dev>
AuthorDate: Tue Aug 5 15:35:31 2025 -0700
switch to straight double quotes instead of curly
Some of the code examples were using curly, which won't compile.
---
.../doc/flex/using/flx_about_dataproviders_ab.html | 8 ++--
content/doc/flex/using/flx_accessible_ac.html | 42 ++++++++++-----------
.../doc/flex/using/flx_apollo_components_ap.html | 36 +++++++++---------
content/doc/flex/using/flx_app_container_apc.html | 6 +--
.../flex/using/flx_ascomponents_advanced_asa.html | 4 +-
content/doc/flex/using/flx_asdoc_asd.html | 6 +--
content/doc/flex/using/flx_cellrenderer_cr.html | 2 +-
.../flex/using/flx_charts_displayingdata_chd.html | 6 +--
.../using/flx_charts_eventsandeffects_che.html | 12 +++---
.../doc/flex/using/flx_charts_formatting_chf.html | 2 +-
content/doc/flex/using/flx_charts_intro_chi.html | 2 +-
content/doc/flex/using/flx_charts_types_cht.html | 2 +-
content/doc/flex/using/flx_compilers_cpl.html | 16 ++++----
content/doc/flex/using/flx_components_cmp.html | 4 +-
.../flex/using/flx_configuring_environment_co.html | 2 +-
.../doc/flex/using/flx_containers_intro_cn.html | 4 +-
content/doc/flex/using/flx_controls_ctr.html | 4 +-
.../flex/using/flx_createcomps_basicas_cca.html | 2 +-
content/doc/flex/using/flx_createevents_cre.html | 4 +-
.../doc/flex/using/flx_createformatters_cf.html | 2 +-
content/doc/flex/using/flx_databinding_db.html | 4 +-
content/doc/flex/using/flx_debugging_de.html | 10 ++---
content/doc/flex/using/flx_deep_linking_dl.html | 20 +++++-----
content/doc/flex/using/flx_dpcontrols_dpc.html | 6 +--
content/doc/flex/using/flx_dragdrop_dd.html | 4 +-
content/doc/flex/using/flx_embed_em.html | 6 +--
content/doc/flex/using/flx_events_ev.html | 4 +-
content/doc/flex/using/flx_fonts_ft.html | 12 +++---
content/doc/flex/using/flx_formatters_fm.html | 20 +++++-----
.../flex/using/flx_functest_components2_fc.html | 18 ++++-----
content/doc/flex/using/flx_fxg_fx.html | 32 ++++++++--------
content/doc/flex/using/flx_gumboskinning_gs.html | 44 +++++++++++-----------
content/doc/flex/using/flx_halo_effects_hf.html | 4 +-
content/doc/flex/using/flx_l10n_ln.html | 14 +++----
.../doc/flex/using/flx_layoutperformance_lp.html | 2 +-
.../flex/using/flx_loading_applications_la.html | 4 +-
content/doc/flex/using/flx_logging_lg.html | 20 +++++-----
content/doc/flex/using/flx_menucontrols_mc.html | 14 +++----
content/doc/flex/using/flx_metadata_me.html | 6 +--
content/doc/flex/using/flx_mirroring_mr.html | 2 +-
content/doc/flex/using/flx_modular_md.html | 2 +-
content/doc/flex/using/flx_mxmlSyntax_sy.html | 2 +-
content/doc/flex/using/flx_mxml_mx.html | 4 +-
content/doc/flex/using/flx_performance_pe.html | 6 +--
content/doc/flex/using/flx_rsl_rsl.html | 16 ++++----
content/doc/flex/using/flx_security2_se.html | 32 ++++++++--------
content/doc/flex/using/flx_size_position_sp.html | 2 +-
content/doc/flex/using/flx_skinning_sk.html | 4 +-
.../doc/flex/using/flx_sparktextcontrols_stc.html | 40 ++++++++++----------
content/doc/flex/using/flx_styles_st.html | 22 +++++------
content/doc/flex/using/flx_textcontrols_tc.html | 4 +-
content/doc/flex/using/flx_tooltips_tt.html | 18 ++++-----
content/doc/flex/using/flx_using_states_us.html | 4 +-
content/doc/flex/using/flx_usingas_ua.html | 14 +++----
content/doc/flex/using/flx_validators_va.html | 4 +-
content/doc/flex/using/flx_wrapper_wr.html | 14 +++----
56 files changed, 300 insertions(+), 300 deletions(-)
diff --git a/content/doc/flex/using/flx_about_dataproviders_ab.html
b/content/doc/flex/using/flx_about_dataproviders_ab.html
index 821603fae..8880d4be4 100644
--- a/content/doc/flex/using/flx_about_dataproviders_ab.html
+++ b/content/doc/flex/using/flx_about_dataproviders_ab.html
@@ -3067,11 +3067,11 @@ data objects</a>, instead of using an <samp
class="codeph"><fx:Model></sam
XML-based tags support data binding to elements, and the DefaultDataDescriptor
class supports all well-structured XML. Therefore you can use a
more natural structure, where node names can represent their function,
-and you do not have to artificially name nodes “children.” </p>
+and you do not have to artificially name nodes "children." </p>
<p>To use an <samp class="codeph"><fx:Model></samp> tag
as the data provider
for a control that uses the DefaultDataDescriptor class, all child
-nodes must be named “children.” This requirement differs from the
+nodes must be named "children." This requirement differs from the
structure that you use with an Object, where the array that contains
the child objects is named "children".</p>
@@ -3566,7 +3566,7 @@ to use the <samp class="codeph">showRoot</samp> property.
</p>
<li>
<p>When you use an XML, XMLList, or XMLListCollection object
as the tree data provider, you must specify the <samp
class="codeph">labelField</samp> property,
-even if it is “label”, if the field is an XML attribute. You must
+even if it is "label", if the field is an XML attribute. You must
do this because you must use the @ sign to signify an attribute. </p>
</li>
@@ -3871,7 +3871,7 @@ a particular item might be pulled down from the server
and released from
memory repeatedly. Every time the item is pulled into memory, a
new object is created to represent the item. If you need to compare
items for equality, Flex should consider all objects that represent
-the same item to be the same “thing.” </p>
+the same item to be the same "thing." </p>
<p>More common than the case where you must implement the IUID
interface
is the case where you can improve processing efficiency by doing
diff --git a/content/doc/flex/using/flx_accessible_ac.html
b/content/doc/flex/using/flx_accessible_ac.html
index ef18a2710..1dbb8f183 100644
--- a/content/doc/flex/using/flx_accessible_ac.html
+++ b/content/doc/flex/using/flx_accessible_ac.html
@@ -577,7 +577,7 @@ the IAccessible interface exposed by the Flash Player for
that component
instance. The request is passed through to the <samp
class="codeph">get_accDefaultAction()</samp> method
of the mx.accessibility.ButtonAccImpl accessibility implementation
class instance, which returns the appropriate default action String
-for a button control, which is “Press.” The article Custom Accessibility
+for a button control, which is "Press." The article Custom Accessibility
Implementations explains in more detail how to build custom accessibility
implementations for Flex components.</p>
@@ -1424,8 +1424,8 @@ a screen reader in Forms mode, use the same keystrokes as
for keyboard
navigation.</p>
<p>When a screen reader encounters a DateChooser
-control in Forms mode, it announces the control as “DropDown Calendar
<em>currentDate</em>,
-to open press Control Down, ComboBox,” where <em>currentDate</em> is
+control in Forms mode, it announces the control as "DropDown Calendar
<em>currentDate</em>,
+to open press Control Down, ComboBox," where <em>currentDate</em> is
the currently selected date. </p>
<p>For more information on keyboard
@@ -2524,7 +2524,7 @@ test it with the latest versions of screen readers.</p>
<p>This article explains how to define a custom accessibility
implementation
for a component. For this example, we'll add an accessibility implementation
to the mx.controls.PopUpButton and, by extension, the
mx.controls.PopUpMenuButton
-class. First, create a new Flex project named “PopUpMenuButton.”
+class. First, create a new Flex project named "PopUpMenuButton."
Be sure to enable accessibility in the project using one of the
methods explained in <a
href="flx_accessible_ac.html#WS2db454920e96a9e51e63e3d11c0bf69084-7da1_verapache">Configuring
Flex applications for accessibility</a>. Follow along with the
@@ -2774,7 +2774,7 @@ Ancestors: none [false] : tool bar : normal
the role <samp class="codeph">split button</samp> and one child named <samp
class="codeph">Open</samp> with
the role <samp class="codeph">drop down button</samp>. When you mouse over
the control or give it keyboard focus, the control’s state is <samp
class="codeph">hot tracked</samp>.
-In Flash terminology, “hot tracked” is a mouseover, or the button “over”
+In Flash terminology, "hot tracked" is a mouseover, or the button "over"
state. A search on http://msdn.microsoft.com/ for "SplitButton accessibility"
returns a more detailed and useful description of the SplitButton
control's accessibiliy implementation: Working with Active Accessibility
@@ -3069,8 +3069,8 @@ which represents the PopUpButton's child drop‑down button
element.Update
the <samp class="codeph">get_accDefaultAction()</samp> method at line 410 to
return the appropriate default action for the master component or
for one of its children. For the PopUpButton component itself, the
-method returns “Press”. For the component's child drop‑down button,
-the method returns “Open.”</p>
+method returns "Press". For the component's child drop‑down button,
+the method returns "Open."</p>
<div class="p">
<pre class="codeblock">...
@@ -3192,8 +3192,8 @@ to read as follows:</p>
name for the master component or for one of its children. For the
PopUpButton component itself, the method should return its label
property as its name. The component's child drop‑down button returns
-either “Open” or “Close”, depending on whether or not the popUp
-is showing. For the PopUpButton, this method also adds “Context”
+either "Open" or "Close", depending on whether or not the popUp
+is showing. For the PopUpButton, this method also adds "Context"
as the name of the popUp menu if no other name has been defined.Add
the following <samp class="codeph">accLocation()</samp> method at line 498:
</p>
@@ -3408,14 +3408,14 @@ Ancestors: none [mnfd] : client : focusable
</div>
<p>Inspect32 reveals how the PopUpButton Accessibility
Implementation
-exposes itself to MSAA, as an object with the role “split button,”,
-with name and value equal to “Paste,” having the default action
-“Press.”</p>
-
- <p>The object's state includes “focused” and “hot tracked”. It
contains
-a single child with the role “drop down button,” that has the name
-“Open.” The child object's state includes “hot tracked” and “has
-popup.” Inspect32 also allows you to test navigation and interaction
+exposes itself to MSAA, as an object with the role "split button,",
+with name and value equal to "Paste," having the default action
+"Press."</p>
+
+ <p>The object's state includes "focused" and "hot tracked". It
contains
+a single child with the role "drop down button," that has the name
+"Open." The child object's state includes "hot tracked" and "has
+popup." Inspect32 also allows you to test navigation and interaction
programmatically.</p>
<p>For example, with the application in focus, type Ctrl+Shift+F12
@@ -3424,8 +3424,8 @@ to the previous item in the MSAA hierarchy. Use
Ctrl+Shift+F12 and/or
Ctrl+Shift+F11 to set focus on the PopUpMenuButton instance's child
drop down button. Type Ctrl+Shift+F2 to execute the default action
for the drop down button. This action should open the popUp menu.
-The drop down button name should change to “Close,” and its state should
-indicate “pressed.” Type Ctrl+Shift+F2 again to close the menu. </p>
+The drop down button name should change to "Close," and its state should
+indicate "pressed." Type Ctrl+Shift+F2 again to close the menu. </p>
<p>Once you're fairly confident that your accessibility
implementation
is returning appropriate values for its IAccessible methods, you
@@ -3493,8 +3493,8 @@ Flex project to read:</p>
</div>
<p>Another peculiarity of JAWS is that it announces the role of
-the PopUpMenuButton component as a “button” as opposed to a “split
-button.” Even if you are providing a correct accessibility implementation
+the PopUpMenuButton component as a "button" as opposed to a "split
+button." Even if you are providing a correct accessibility implementation
to MSAA, if it is of a system role that does not have a precedent
in Flex or Flash, like the PopUpButton, the screen reader may not
have been scripted to understand how to interpret an object with that
diff --git a/content/doc/flex/using/flx_apollo_components_ap.html
b/content/doc/flex/using/flx_apollo_components_ap.html
index d9c0ac91a..dd7098155 100644
--- a/content/doc/flex/using/flx_apollo_components_ap.html
+++ b/content/doc/flex/using/flx_apollo_components_ap.html
@@ -287,7 +287,7 @@ the value to a property or variable, or by setting the
property
in ActionScript. When you set the <samp class="codeph">directory</samp>
property,
the data provider of the underlying combo box is automatically populated.
By default the <samp class="codeph">directory</samp> property is set to the
-root “Computer” directory, which has no ancestor directories and
+root "Computer" directory, which has no ancestor directories and
hence shows no selectable directories in the combo box’s drop-down
list.</p>
@@ -426,7 +426,7 @@ When you set the <samp class="codeph">directory</samp>
property, the data provid
of the underlying tree control is automatically populated. The specified
directory isn’t displayed in the tree—its child files or directories
are shown as the top-level nodes of the tree. By default the <samp
class="codeph">directory</samp> property
-is set to the root “Computer” directory. Consequently, its children
+is set to the root "Computer" directory. Consequently, its children
(the drive or drives attached to the computer) are displayed as
the top branches of the tree.</p>
@@ -509,7 +509,7 @@ When you set the <samp class="codeph">directory</samp>
property, the data provid
of the underlying list control is automatically populated. The specified
directory isn’t displayed in the list—its child files or directories
are shown as the items in the list. By default the <samp
class="codeph">directory</samp> property
-is set to the root “Computer” directory. In that case its children,
+is set to the root "Computer" directory. In that case its children,
which are the drive or drives attached to the computer, are displayed
as the items in the list.</p>
@@ -603,7 +603,7 @@ When you set the <samp class="codeph">directory</samp>
property the data provide
of the underlying data grid control is automatically populated.
The specified directory isn’t displayed in the grid—its child files
or directories are shown as the rows in the grid. By default the <samp
class="codeph">directory</samp> property
-is set to the root “Computer” directory. In that case its children,
+is set to the root "Computer" directory. In that case its children,
the drive or drives attached to the computer, are displayed as the
items in the grid.</p>
@@ -651,8 +651,8 @@ other directories using the mouse or keyboard. The user can
change
the directory by double-clicking a subdirectory, by pressing Enter
or Ctrl-Down when a subdirectory is selected, by pressing Ctrl-Up
when the control isn't displaying the COMPUTER directory, by pressing
-Ctrl-Left when there is a “previous” directory to navigate back
-to, or by pressing Ctrl-Right when there is a “next” directory to
+Ctrl-Left when there is a "previous" directory to navigate back
+to, or by pressing Ctrl-Right when there is a "next" directory to
navigate forward to. </p>
<p>If the user attempts to change the directory being displayed,
@@ -857,11 +857,11 @@ the <samp class="codeph">location</samp> property.</p>
<p>The following example demonstrates the use of an HTML control
in a simple application. The HTML control’s <samp
class="codeph">location</samp> property
-is set to “http://labs.adobe.com/”, so that URL is opened in the
-control when it loads. In addition, when the “back” and “forward”
+is set to "http://labs.adobe.com/";, so that URL is opened in the
+control when it loads. In addition, when the "back" and "forward"
are clicked they call the control’s <samp class="codeph">historyBack()</samp>
and <samp class="codeph">historyForward()</samp> methods.
A TextInput control allows the user to enter a URL location. When
-a third “go” button is clicked, the HTML control’s <samp
class="codeph">location</samp> property
+a third "go" button is clicked, the HTML control’s <samp
class="codeph">location</samp> property
is set to the <samp class="codeph">text</samp> property of the input text
field.</p>
<pre class="noswf"><?xml version="1.0" encoding="utf-8"?>
@@ -986,7 +986,7 @@ the items within the menu. Likewise, those menu items can
contain
items, in which case the menu item is a submenu. When the user selects
the menu item it expands its own menu items. For example, the following
image shows a window menu with three menu items (plus an additional
-separator menu item). The item with the label “SubMenuItem A-3”
+separator menu item). The item with the label "SubMenuItem A-3"
in turn contains three menu items, so SubMenuItem A-3 is treated
as a submenu. (The code to create this menu is provided later.)</p>
@@ -2299,11 +2299,11 @@ item’s label, then presses return to select the item.
</p>
The
simplest way to specify a mnemonic for a menu item in a FlexNativeMenu
component
-is to include an underscore character (“_”) in the menu item’s label field,
+is to include an underscore character ("_") in the menu item’s label field,
immediately to the left of the letter that serves as the mnemonic
for that menu item. For instance, if the following XML node is used
in a data provider for a FlexNativeMenu, the mnemonic for the command
-is the first character of the second word (the letter “A”):</p>
+is the first character of the second word (the letter "A"):</p>
<pre class="codeblock"><menuitem label="Save _As"/></pre>
@@ -2311,7 +2311,7 @@ is the first character of the second word (the letter
“A”):</p>
not included in the label. Instead, the character following the
underscore becomes the mnemonic for the menu item. To include a
literal underscore character in a menu item’s name, use two underscore
-characters (“__”). This sequence is converted to one underscore
+characters ("__"). This sequence is converted to one underscore
in the menu item label.</p>
<p>As an alternative to using underscore characters in label names,
@@ -2886,7 +2886,7 @@ system window to appear on the user’s display.</p>
The example includes two MXML files. The first uses a WindowedApplication
container and is the initial window of the application. The second
uses the Window container to define a secondary window for the application.
-In this example, the main window simulates a “splash screen” for
+In this example, the main window simulates a "splash screen" for
the application. After a set time (4 seconds) it closes the splash
screen and opens the second window. In order to make a splash screen
window with no window chrome, in the application.xml file the <samp
class="codeph">systemChrome</samp> tag
@@ -3060,11 +3060,11 @@ hide the status bar by using the <samp
class="codeph">showStatusBar</samp> prope
<p>How the chrome is represented depends on the setting of the
<samp class="codeph">systemChrome</samp> attribute,
which is defined in the application .xml file for a WindowedApplication
container,
or in the Window container’s <samp class="codeph">systemChrome</samp> property.
-If <samp class="codeph">systemChrome</samp> is set to “standard” in the
application
+If <samp class="codeph">systemChrome</samp> is set to "standard" in the
application
.xml file (or <samp
class="codeph">flash.display.NativeWindowSystemChrome.STANDARD</samp> in
ActionScript) the operating system renders the chrome.</p>
- <p>If <samp class="codeph">systemChrome</samp> is set to “none”
(<samp class="codeph">NativeWindowSystemChrome.NONE</samp>) the
+ <p>If <samp class="codeph">systemChrome</samp> is set to "none"
(<samp class="codeph">NativeWindowSystemChrome.NONE</samp>) the
Window and WindowedApplication container can either use the Flex chrome,
use the WindowedApplicationSkin class to define the chrome, or define no
chrome at all. When you do not use any chrome, the application shows
@@ -3074,7 +3074,7 @@ only a background color. </p>
skin class in the spark.skins.spark package. The following example
sets the <samp class="codeph">skinClass</samp> style of the WindowedApplication
to specify to use the Flex chrome. This example assumes that you
-set <samp class="codeph">systemChrome</samp> to “none” in the application’s
+set <samp class="codeph">systemChrome</samp> to "none" in the application’s
.xml file:<pre class="noswf"><?xml version="1.0" encoding="utf-8"?>
<!-- aircomponents/src/WindowSimpleChrome.mxml -->
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009";
@@ -3099,7 +3099,7 @@ and Window containers that defines just a border and
status bar,
but no gripper button, title bar, or title bar buttons. The following
example assigns this skin to the WindowedApplication container.
This example assumes that you set <samp class="codeph">systemChrome</samp> to
-“none” in the application’s .xml file: <pre class="noswf"><?xml
version="1.0" encoding="utf-8"?>
+"none" in the application’s .xml file: <pre class="noswf"><?xml
version="1.0" encoding="utf-8"?>
<!-- aircomponents/src/WindowSimpleChromeWindowed.mxml -->
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
diff --git a/content/doc/flex/using/flx_app_container_apc.html
b/content/doc/flex/using/flx_app_container_apc.html
index 7c5b068fe..89aff9287 100644
--- a/content/doc/flex/using/flx_app_container_apc.html
+++ b/content/doc/flex/using/flx_app_container_apc.html
@@ -1537,7 +1537,7 @@ provide utility functions that any of the components can
access.</p>
<p>For
example, suppose that you store the user’s name at the application
level and implement a utility function, <samp
class="codeph">getSalutation()</samp>,
-which returns the string “Hi, <em>userName</em>”. The following example
+which returns the string "Hi, <em>userName</em>". The following example
MyApplication.mxml file shows the application source that defines
the <samp class="codeph">getSalutation()</samp> method:</p>
@@ -1758,8 +1758,8 @@ the initialization phase: </p>
</div>
<p>The MX download progress bar supports text. The bar displays
-the text “Downloading app” during the SWF download. It displays
-the text “Initializing app” during application initialization.</p>
+the text "Downloading app" during the SWF download. It displays
+the text "Initializing app" during application initialization.</p>
<p>The download progress bar is not displayed if the SWF file is
on your local host or if it is already cached. If the SWF file is
diff --git a/content/doc/flex/using/flx_ascomponents_advanced_asa.html
b/content/doc/flex/using/flx_ascomponents_advanced_asa.html
index 965ed9eb4..769e145a5 100644
--- a/content/doc/flex/using/flx_ascomponents_advanced_asa.html
+++ b/content/doc/flex/using/flx_ascomponents_advanced_asa.html
@@ -2597,7 +2597,7 @@ this control:</p>
<div>
<div class="section"
id="WS2db454920e96a9e51e63e3d11c0bf68641-7fe3_verapache__WS2db454920e96a9e51e63e3d11c0bf68641-7fe2_verapache"><a
name="WS2db454920e96a9e51e63e3d11c0bf68641-7fe3_verapache__WS2db454920e96a9e51e63e3d11c0bf68641-7fe2_verapache"><!--
--></a><h3 class="sectiontitle">I
-get an error “don't know how to parse…” when I try to use the component
+get an error "don't know how to parse…" when I try to use the component
from MXML.</h3>
<p>This means that the compiler could not find
@@ -2619,7 +2619,7 @@ compilers</a>.</p>
</div>
<div class="section"
id="WS2db454920e96a9e51e63e3d11c0bf68641-7fe3_verapache__WS2db454920e96a9e51e63e3d11c0bf68641-7ff8_verapache"><a
name="WS2db454920e96a9e51e63e3d11c0bf68641-7fe3_verapache__WS2db454920e96a9e51e63e3d11c0bf68641-7ff8_verapache"><!--
--></a><h3 class="sectiontitle">I
-get an error “xxx is not a valid attribute…” when I try to use the
+get an error "xxx is not a valid attribute…" when I try to use the
component from MXML.</h3>
<p>Ensure that the attribute is spelled
diff --git a/content/doc/flex/using/flx_asdoc_asd.html
b/content/doc/flex/using/flx_asdoc_asd.html
index bc79daff4..8eb899905 100644
--- a/content/doc/flex/using/flx_asdoc_asd.html
+++ b/content/doc/flex/using/flx_asdoc_asd.html
@@ -1506,7 +1506,7 @@ formatting is preserved and the code is displayed in a
gray, horizontally
scrolling box. </p>
<p>If the code inside the <samp
class="codeph"><listing></samp> tags
-uses literal “<“, “>”, or”&” characters, convert them
+uses literal "<", ">", or"&" characters, convert them
to the HTML character-code equivalent.</p>
</td>
@@ -2526,7 +2526,7 @@ Ensure that you include the final semicolon (;).</p>
</td>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d51287e2593 ">
- <p>Do not use a literal “*” character in the
+ <p>Do not use a literal "*" character in the
body of a comment; instead, insert the HTML character code &#42;.</p>
</td>
@@ -2909,7 +2909,7 @@ has the following format: <pre
class="codeblock"><overviews>
</div>
<p>Notice that the HTML tag for bold text is entered by using the
-HTML character code for the “<“ and “>” characters. </p>
+HTML character code for the "<" and ">" characters. </p>
</div>
diff --git a/content/doc/flex/using/flx_cellrenderer_cr.html
b/content/doc/flex/using/flx_cellrenderer_cr.html
index a6116a8f1..2ded6dd94 100644
--- a/content/doc/flex/using/flx_cellrenderer_cr.html
+++ b/content/doc/flex/using/flx_cellrenderer_cr.html
@@ -3006,7 +3006,7 @@ price, as the following item renderer shows: </p>
</mx:HBox></pre>
<p>This item renderer uses a <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/controls/Label.html";
target="_blank">Label</a> control
-to insert the text “Sale Price!” and an Image control to insert
+to insert the text "Sale Price!" and an Image control to insert
an icon in the column header. </p>
<p>The following example shows the main application:</p>
diff --git a/content/doc/flex/using/flx_charts_displayingdata_chd.html
b/content/doc/flex/using/flx_charts_displayingdata_chd.html
index 18604eb47..4c0dde12e 100644
--- a/content/doc/flex/using/flx_charts_displayingdata_chd.html
+++ b/content/doc/flex/using/flx_charts_displayingdata_chd.html
@@ -615,8 +615,8 @@ Typically, it is a String representing some form of a date.
You
cannot override this parameter or add additional parameters.</p>
<p>The following example shows a parsing method that creates a Date
-object from String values in the data provider that match the “YYYY,
-MM, DD” pattern:</p>
+object from String values in the data provider that match the "YYYY,
+MM, DD" pattern:</p>
<pre class="codeblock"><?xml version="1.0"?>
<!-- charts/DateTimeAxisParseFunction.mxml -->
@@ -4572,7 +4572,7 @@ two values on the axis for each data point in an area;
for example:</p>
</s:Application></pre>
<p>The resulting <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/charts/chartClasses/DataTip.html";
target="_blank">DataTip</a> labels
-the current value “high” and the <samp class="codeph">minField</samp> value
“low.”
+the current value "high" and the <samp class="codeph">minField</samp> value
"low."
The following example shows an <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/charts/AreaChart.html";
target="_blank">AreaChart</a> that
defines the base of each column:</p>
diff --git a/content/doc/flex/using/flx_charts_eventsandeffects_che.html
b/content/doc/flex/using/flx_charts_eventsandeffects_che.html
index 855c82584..145e0eabf 100644
--- a/content/doc/flex/using/flx_charts_eventsandeffects_che.html
+++ b/content/doc/flex/using/flx_charts_eventsandeffects_che.html
@@ -949,7 +949,7 @@ the dataToLocal() method</h5>
<p>The <samp class="codeph">dataToLocal()</samp> method
converts a set of values to x and y coordinates on the screen.
-The values you give the method are in the “data space” of the chart; this
+The values you give the method are in the "data space" of the chart; this
method converts these values to coordinates. The <em>data space</em> is
the collection of all possible combinations of data values that
a chart can represent.</p>
@@ -1325,9 +1325,9 @@ defines the effect that Flex uses as it moves the current
data into
its final position on the screen.</p>
<p>Because Flex triggers the effects associated with <samp
class="codeph">hideDataEffect</samp> and <samp
class="codeph">showDataEffect</samp> when
-the data changes, there is “old” data and “new” data. The effect
+the data changes, there is "old" data and "new" data. The effect
associated with the <samp class="codeph">hideDataEffect</samp> trigger is the
-“old” data that will be replaced by the new data.</p>
+"old" data that will be replaced by the new data.</p>
<p>The order of events is:</p>
@@ -1460,9 +1460,9 @@ in the axis labels during the effect.</p>
<p>Changing a data provider first triggers the <samp
class="codeph">hideDataEffect</samp> effect
on the original data provider, which causes that data provider to
-“slide out,” and then triggers the <samp class="codeph">showDataEffect</samp>
effect
-on the new data provider, which causes that data provider to “slide
-in.” </p>
+"slide out," and then triggers the <samp class="codeph">showDataEffect</samp>
effect
+on the new data provider, which causes that data provider to "slide
+in." </p>
<div class="note"><span class="notetitle">Note:</span> If you set
the data provider on the series and
not the chart control, you must change it on the series and not
diff --git a/content/doc/flex/using/flx_charts_formatting_chf.html
b/content/doc/flex/using/flx_charts_formatting_chf.html
index 1a4273563..e82b25115 100644
--- a/content/doc/flex/using/flx_charts_formatting_chf.html
+++ b/content/doc/flex/using/flx_charts_formatting_chf.html
@@ -550,7 +550,7 @@ rather than define a new style in CSS. </p>
of the horizontal axis to 7:</p>
<pre class="codeblock"> <mx:horizontalAxisRenderers>
- <mx:AxisRenderer fontSize="7" axis=”{h1}”/>
+ <mx:AxisRenderer fontSize="7" axis="{h1}"/>
</mx:horizontalAxisRenderers></pre>
<p>Notice that any time you want to use an AxisRenderer, you must
diff --git a/content/doc/flex/using/flx_charts_intro_chi.html
b/content/doc/flex/using/flx_charts_intro_chi.html
index f4d936cd2..bb5901a43 100644
--- a/content/doc/flex/using/flx_charts_intro_chi.html
+++ b/content/doc/flex/using/flx_charts_intro_chi.html
@@ -803,7 +803,7 @@ charts</a>. </p>
<p>Most charts use only one kind of series. However, you can specify
multiple types of series for a chart. For example, you can create
a chart that has a series of bars in addition to a trend line that
-“floats” over it. This is useful for rendering trend-lines or showing
+"floats" over it. This is useful for rendering trend-lines or showing
different types of data on a single chart for comparison analysis. For
more information, see <a
href="flx_charts_types_cht.html#WS2db454920e96a9e51e63e3d11c0bf69084-7c6c_verapache">Using
multiple data series</a>.</p>
diff --git a/content/doc/flex/using/flx_charts_types_cht.html
b/content/doc/flex/using/flx_charts_types_cht.html
index 25b20ff82..417d9488a 100644
--- a/content/doc/flex/using/flx_charts_types_cht.html
+++ b/content/doc/flex/using/flx_charts_types_cht.html
@@ -2932,7 +2932,7 @@ PieChart control, as the following example shows: </p>
</s:Application></pre>
<p>The value of the <samp class="codeph">innerRadius</samp>
property is a percentage
-value of the “hole” compared to the entire pie’s radius. Valid values
+value of the "hole" compared to the entire pie’s radius. Valid values
range from 0 to 1.</p>
</div>
diff --git a/content/doc/flex/using/flx_compilers_cpl.html
b/content/doc/flex/using/flx_compilers_cpl.html
index b2c825c9a..266c9253d 100644
--- a/content/doc/flex/using/flx_compilers_cpl.html
+++ b/content/doc/flex/using/flx_compilers_cpl.html
@@ -333,7 +333,7 @@ the command-line compilers</a>.</p>
<pre class="codeblock"> compc [options] -include-classes class
[...]</pre>
<p>The default option for compc is <samp
class="codeph">include-classes</samp>.
-At least one of the “include-” options is required.</p>
+At least one of the "include-" options is required.</p>
<p>To see a list of supported options for compc, you can use
the <samp class="codeph">help</samp>
<samp class="codeph">list</samp> option, as
@@ -2636,10 +2636,10 @@ that value of the <samp class="codeph">ouput</samp>
option.</p>
application. The value must be the name of a class that implements
the IPreloaderDisplay interface.</p>
- <p>The default value is
“mx.preloaders.SparkDownloadProgressBar”
+ <p>The default value is
"mx.preloaders.SparkDownloadProgressBar"
when <samp class="codeph">compatibility-version</samp> is 4.0.0 or greater.
When <samp class="codeph">compatibility-version</samp> is less than 4.0.0,
-the default value is “mx.preloaders.DownloadProgressBar”.</p>
+the default value is "mx.preloaders.DownloadProgressBar".</p>
<p>For
more information, see <a
href="flx_app_container_apc.html#WS2db454920e96a9e51e63e3d11c0bf69084-7e3c_verapache">Showing
@@ -3273,7 +3273,7 @@ version of Flash Player that shipped with the SDK. </p>
<p>This option
is useful if your application’s audience has a specific Player and cannot
-upgrade. You can use this option to “downgrade” your application
+upgrade. You can use this option to "downgrade" your application
for that audience. </p>
<p>For more information, see <a
href="flx_versioning_ve.html#WS2db454920e96a9e51e63e3d11c0bf69084-7ee0_verapache">Targeting
@@ -4395,7 +4395,7 @@ and classes</h3>
In
many cases, you have one or more components that you use in your
applications, but you do not have them in a package structure. You
-want to be able to use them in the generic namespace (“*”) inside
+want to be able to use them in the generic namespace ("*") inside
your applications. In these cases, you use the <samp
class="codeph">include-classes</samp> option
to add the components to your SWC file.</p>
@@ -4463,7 +4463,7 @@ the components compiled in the previous example:</p>
...
</s:Application></pre>
- <p>To use the generic namespace of “*” rather than a namespace that
+ <p>To use the generic namespace of "*" rather than a namespace that
includes a component’s directory structure, you can include the
directory in the <samp class="codeph">source-path</samp> as the following
command-line
example shows:</p>
@@ -4651,13 +4651,13 @@ file with the <samp
class="codeph">include-namespaces</samp> option; for example
<pre class="codeblock"> -include-namespaces
http://mynamespace</pre>
<p>The <samp class="codeph">namespace</samp> option matches a
namespace (such
-as “http://ns.adobe.com/mxml/2009”) with a manifest file. The <samp
class="codeph">include-namespaces</samp> option
+as "http://ns.adobe.com/mxml/2009";) with a manifest file. The <samp
class="codeph">include-namespaces</samp> option
instructs compc to include all the components listed in that namespace’s
manifest file in the SWC file.</p>
<p>After you define the manifest file, you can compile the SWC
file.
The following command-line example compiles the components into
-the “http://mynamespace” namespace:</p>
+the "http://mynamespace"; namespace:</p>
<pre class="codeblock"> compc -source-path .
-output c:/jrun4/servers/flex/WEB-INF/flex/user_classes/MyButtons.swc
diff --git a/content/doc/flex/using/flx_components_cmp.html
b/content/doc/flex/using/flx_components_cmp.html
index 0e6f4720f..a5843c0d7 100644
--- a/content/doc/flex/using/flx_components_cmp.html
+++ b/content/doc/flex/using/flx_components_cmp.html
@@ -1781,7 +1781,7 @@ there is a Spark Button component (in the
spark.components.* package)
and a MX Button component (in the mx.controls.* package). To distinguish
between different components that share the same name, you specify
namespaces in your CSS that apply to types. The preceding example
-defines the MX s namespace and uses “<samp class="codeph">s</samp>” as an
identifier:</p>
+defines the MX s namespace and uses "<samp class="codeph">s</samp>" as an
identifier:</p>
<p>For more information on styles, see <a
href="flx_styles_st.html#WS2db454920e96a9e51e63e3d11c0bf69084-7fee_verapache">Styles
and themes</a>. </p>
@@ -1865,7 +1865,7 @@ skins that are simpler.</p>
<p>Skin classes have a contract with a component that enforces certain
rules that the skin class and its host component must follow. For
-example, if a component uses states (such as “mouseOver” or “mouseDown”),
+example, if a component uses states (such as "mouseOver" or "mouseDown"),
the skin class must define the appearance of these states. If a
component uses subcomponents (such as a down or up arrow on a slider),
the skin class must define these as skin parts.</p>
diff --git a/content/doc/flex/using/flx_configuring_environment_co.html
b/content/doc/flex/using/flx_configuring_environment_co.html
index 85ea029d9..80d7997d7 100644
--- a/content/doc/flex/using/flx_configuring_environment_co.html
+++ b/content/doc/flex/using/flx_configuring_environment_co.html
@@ -145,7 +145,7 @@ option to point to its new location.</p>
<p>You can also use a local configuration file that overrides the
compiler options of the flex-config.xml file. You give this local
-configuration file the same name as the MXML file, plus “-config.xml”
+configuration file the same name as the MXML file, plus "-config.xml"
and store it in the same directory. For example, MyApp-config.xml.
When you compile your MXML file, the compiler looks for a local
configuration file first, then the flex-config.xml file.</p>
diff --git a/content/doc/flex/using/flx_containers_intro_cn.html
b/content/doc/flex/using/flx_containers_intro_cn.html
index ced394a09..8aaffc2b6 100644
--- a/content/doc/flex/using/flx_containers_intro_cn.html
+++ b/content/doc/flex/using/flx_containers_intro_cn.html
@@ -3214,8 +3214,8 @@ such as its border and the background image. </p>
and accessor methods let you count and access only child components.
However, the container might contain style elements and skins, such
as the border and background. The container’s <samp
class="codeph">rawChildren</samp> property
-lets you access all children of a container, including the component “content
-children” and the skin and style “display children.” The object
+lets you access all children of a container, including the component "content
+children" and the skin and style "display children." The object
returned by the <samp class="codeph">rawChildren</samp> property implements
the IChildList interface. You then use methods and properties of
this interface, such as <samp class="codeph">getChildAt()</samp>, to access and
diff --git a/content/doc/flex/using/flx_controls_ctr.html
b/content/doc/flex/using/flx_controls_ctr.html
index 523156674..1d942d2cc 100644
--- a/content/doc/flex/using/flx_controls_ctr.html
+++ b/content/doc/flex/using/flx_controls_ctr.html
@@ -1341,7 +1341,7 @@ in MXML by using the <samp
class="codeph"><s:Button></samp> tag, as the fo
example shows. Specify an <samp class="codeph">id</samp> value if you intend
to refer to the button elsewhere in your MXML, either in another
tag or in an ActionScript block. The following code creates a Button
-control with the label “Hello world!”: </p>
+control with the label "Hello world!": </p>
<pre class="codeblock"><?xml version="1.0"?>
<!-- controls\button\ButtonLabel.mxml -->
@@ -3060,7 +3060,7 @@ control</h3>
<p>You can use the <samp class="codeph">formatString</samp>
property
of the <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/controls/DateField.html";
target="_blank">DateField</a> control
to format the string in the control’s text field. The <samp
class="codeph">formatString</samp> property
-can contain any combination of "MM", "DD", "YY", “YYYY”, delimiter,
+can contain any combination of "MM", "DD", "YY", "YYYY", delimiter,
and punctuation characters. The default value is "MM/DD/YYYY".</p>
<p>In the following example, you select a value for the <samp
class="codeph">formatString</samp> property from
diff --git a/content/doc/flex/using/flx_createcomps_basicas_cca.html
b/content/doc/flex/using/flx_createcomps_basicas_cca.html
index efbbd1a6e..17bd5ae0e 100644
--- a/content/doc/flex/using/flx_createcomps_basicas_cca.html
+++ b/content/doc/flex/using/flx_createcomps_basicas_cca.html
@@ -540,7 +540,7 @@ the following example shows: </p>
// Method definition
}</pre>
- <p>If the method takes a variable number of arguments, use the
“...”
+ <p>If the method takes a variable number of arguments, use the
"..."
syntax, as the following example shows: </p>
<pre class="codeblock"> function foo(n:Number, ... rest):void {
diff --git a/content/doc/flex/using/flx_createevents_cre.html
b/content/doc/flex/using/flx_createevents_cre.html
index 14f35d0c3..3c034d774 100644
--- a/content/doc/flex/using/flx_createevents_cre.html
+++ b/content/doc/flex/using/flx_createevents_cre.html
@@ -170,7 +170,7 @@ The Event class implements these properties using getter
methods. </p>
</td>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d164204e153 ">
- <p>The name of the event; for example, <samp
class="codeph">“click”</samp>.
+ <p>The name of the event; for example, <samp
class="codeph">"click"</samp>.
The event constructor sets this property. </p>
</td>
@@ -521,7 +521,7 @@ of an MXML file.</p>
<p>The <samp class="codeph">Event</samp> metadata keyword has the
following
syntax:</p>
- <pre class="codeblock"> [Event(name=”eventName”,
type=”package.eventType”)]</pre>
+ <pre class="codeblock"> [Event(name="eventName",
type="package.eventType")]</pre>
<p>The <em>eventName</em> argument specifies the name of the event.
The <em>eventType</em> argument specifies the class name, including
diff --git a/content/doc/flex/using/flx_createformatters_cf.html
b/content/doc/flex/using/flx_createformatters_cf.html
index 5b5d3e00b..93f3f62e7 100644
--- a/content/doc/flex/using/flx_createformatters_cf.html
+++ b/content/doc/flex/using/flx_createformatters_cf.html
@@ -211,7 +211,7 @@ class: </p>
<dt class="dlterm">Format string </dt>
<dd>
- <p>The Social Security number is: ###-##-####” </p>
+ <p>The Social Security number is: ###-##-####" </p>
</dd>
diff --git a/content/doc/flex/using/flx_databinding_db.html
b/content/doc/flex/using/flx_databinding_db.html
index 784a4149c..303dd4ac6 100644
--- a/content/doc/flex/using/flx_databinding_db.html
+++ b/content/doc/flex/using/flx_databinding_db.html
@@ -253,7 +253,7 @@ Flash<sup>®</sup> Platform</a>
of a data binding expression includes the following statement in
its description:</p>
- <p>“This property can be used as the source for data binding.” </p>
+ <p>"This property can be used as the source for data binding." </p>
<div class="section"
id="WS2db454920e96a9e51e63e3d11c0bf64c3d-7ffd_verapache__WS2db454920e96a9e51e63e3d11c0bf64c3d-7ffc_verapache"><a
name="WS2db454920e96a9e51e63e3d11c0bf64c3d-7ffd_verapache__WS2db454920e96a9e51e63e3d11c0bf64c3d-7ffc_verapache"><!--
--></a><h4 class="sectiontitle">Using
read-only properties as the source for data binding</h4>
@@ -799,7 +799,7 @@ as a one-way binding:<pre class="codeblock"><mx:String
id="str">test</m
</div>
<p>Flex 3 set the Text component’s <samp
class="codeph">text</samp> property
-to “test”, but the value of the String component did not change
+to "test", but the value of the String component did not change
if the Text component’s <samp class="codeph">text</samp> property changed.</p>
<p>In Flex 4 and later, this code is interpreted as a
bidirectional
diff --git a/content/doc/flex/using/flx_debugging_de.html
b/content/doc/flex/using/flx_debugging_de.html
index a3d3fa13c..a2657e04e 100644
--- a/content/doc/flex/using/flx_debugging_de.html
+++ b/content/doc/flex/using/flx_debugging_de.html
@@ -261,8 +261,8 @@ the Internet Explorer application.</p>
</li>
<li>
- <p>Select the “Internet Explorer should check to see
whether
-it is the default browser” option, and click OK.</p>
+ <p>Select the "Internet Explorer should check to see
whether
+it is the default browser" option, and click OK.</p>
<p>The next
time you start Internet Explorer, Internet Explorer prompts you
@@ -299,8 +299,8 @@ Explorer is already your default browser.</p>
</li>
<li>
- <p>Select the “Firefox should check to see if it is the
default
-browser when starting” option, and click OK.</p>
+ <p>Select the "Firefox should check to see if it is the
default
+browser when starting" option, and click OK.</p>
<p>The next time
you start FireFox, FireFox prompts you to make it the default browser.
@@ -1924,7 +1924,7 @@ stops the debugger. For example, TypeError:<pre
class="codeblock">(fdb) catch Ty
</div>
<div class="p">To halt the debugger on any exception, you can use
a wildcard
-(“*”), as the following example shows:<pre class="codeblock">(fdb) catch
*</pre>
+("*"), as the following example shows:<pre class="codeblock">(fdb) catch
*</pre>
</div>
diff --git a/content/doc/flex/using/flx_deep_linking_dl.html
b/content/doc/flex/using/flx_deep_linking_dl.html
index a4f2b60f2..1da532355 100644
--- a/content/doc/flex/using/flx_deep_linking_dl.html
+++ b/content/doc/flex/using/flx_deep_linking_dl.html
@@ -76,7 +76,7 @@ visited application states</p>
<p>Losing the ability to couple a browser-managed URL to a specific
state of an application can be a fairly big drawback when creating
-applications. Deep linking adds URL-mapping or “bookmarking” capabilities
+applications. Deep linking adds URL-mapping or "bookmarking" capabilities
to applications. At the high level, deep linking lets you do the
following:</p>
@@ -154,7 +154,7 @@ write it back to the browser.</p>
<p>To use deep linking, you write ActionScript that sets and gets
portions of the URL to determine which state the application is
in. These portions are called fragments, and occur after the pound
-sign (“#”) in the URL. In the following example, <samp
class="codeph">view=1</samp> is
+sign ("#") in the URL. In the following example, <samp
class="codeph">view=1</samp> is
the fragment:</p>
<pre class="codeblock"> http://my.domain.com#view=1</pre>
@@ -266,7 +266,7 @@ for the current page.</p>
the <samp class="codeph">parseURL()</samp> method to listen for <samp
class="codeph">browserURLChange</samp> events,
and calls the <samp class="codeph">init()</samp> method with a blank fragment
as the default fragment. It sets the value of the page’s title to
-“Test Deep Linking”:</p>
+"Test Deep Linking":</p>
<pre class="codeblock"> private function initApp():void {
browserManager = BrowserManager.getInstance();
@@ -282,7 +282,7 @@ when the URL changes, the URL with the default fragment
will be
entered in the browser’s history. This way, if the user clicks the
Back button or in some other way accesses this page from the browser’s
history, this fragment will be used. Also, the BrowserManager returns
-the default fragment if there is nothing after the pound sign (“#”)
+the default fragment if there is nothing after the pound sign ("#")
in the URL.</p>
</div>
@@ -585,7 +585,7 @@ HTML page according to which panel is opened.</p>
</s:Application></pre>
- <p>This example has one major drawback: it does not “remember” the
+ <p>This example has one major drawback: it does not "remember" the
state of the panel that is not in the current view. If you copy
the bookmark and open it in a new browser, the view that you were
last looking at, and the state of the CheckBox on that view, are
@@ -717,7 +717,7 @@ Back buttons in your browser. In both cases, you also
trigger a <samp class="cod
a <samp class="codeph">browserURLChange</samp> event but does not trigger a
page reload in FireFox or Internet Explorer 7. In Internet Explorer
version 6 and earlier, changing the part of the address that is
-to the right of the pound sign (“#”) <em>does</em> trigger a page reload.</p>
+to the right of the pound sign ("#") <em>does</em> trigger a page reload.</p>
</div>
@@ -737,7 +737,7 @@ initialize the BrowserManager, you set the value of the
title in
the second parameter to the <samp class="codeph">init()</samp> method.</p>
<p>The following example sets the initial value of the title to
-“Welcome”. It then changes the title depending on the name and hometown
+"Welcome". It then changes the title depending on the name and hometown
that you enter in the TextInput fields.</p>
<pre class="noswf"><?xml version="1.0" encoding="utf-8"?>
@@ -805,7 +805,7 @@ data with flashVars properties</a>.</p>
<p>The BrowserManager also provides a method of accessing values
from a URL inside your application. You do this by accessing the
URL fragments that deep linking uses. By default, you can append
-any Strings after the pound sign (“#”) in the URL and be able to
+any Strings after the pound sign ("#") in the URL and be able to
access them as semi-colon-separated name/value pairs. For example,
with a URL like the following, you can access the <samp
class="codeph">firstName</samp> and <samp class="codeph">lastName</samp> values
once you convert the fragment to an object:</p>
@@ -817,8 +817,8 @@ then use the URLUtil class’s <samp
class="codeph">stringToObject()</samp> meth
You then access <samp class="codeph">firstName</samp> and <samp
class="codeph">lastName</samp> as
properties on that new object.</p>
- <p>To make the URL more “URL-like”, you can separate the fragments
-with an ampersand (“&”). When you convert the fragment to an
+ <p>To make the URL more "URL-like", you can separate the fragments
+with an ampersand ("&"). When you convert the fragment to an
object with the <samp class="codeph">stringToObject()</samp> method, you
specify
the new delimiter.</p>
diff --git a/content/doc/flex/using/flx_dpcontrols_dpc.html
b/content/doc/flex/using/flx_dpcontrols_dpc.html
index b86177e90..2b2df7cb6 100644
--- a/content/doc/flex/using/flx_dpcontrols_dpc.html
+++ b/content/doc/flex/using/flx_dpcontrols_dpc.html
@@ -1890,8 +1890,8 @@ control. For example, when a web service operation
returns an Array
of strings, you can use the following format to display each string
as a row of a ComboBox control:</p>
- <pre class="codeblock"> <mx:ArrayCollection id=”resultAC”
- source=”mx.utils.ArrayUtil.toArray(service.operation.lastResult);”
+ <pre class="codeblock"> <mx:ArrayCollection id="resultAC"
+ source="mx.utils.ArrayUtil.toArray(service.operation.lastResult);"
<mx:ComboBox dataProvider="{resultAC}" /></pre>
<p>In general, you should use an ArrayCollection for web service
@@ -3406,7 +3406,7 @@ a Tree control displays a node of a non-XML data
provider, by default,
it displays the value of the <samp class="codeph">label</samp> property of
the node as the text label. When you use an E4X XML-based data provider,
however, you must specify the label field, even if the label is
-identified by an attribute named “label”. To specify the label field,
+identified by an attribute named "label". To specify the label field,
use the <samp class="codeph">labelField</samp> property; for example, if the
label field is the label attribute, specify <samp
class="codeph">labelField="@label"</samp>.</p>
diff --git a/content/doc/flex/using/flx_dragdrop_dd.html
b/content/doc/flex/using/flx_dragdrop_dd.html
index c456b2ae1..b12c1f948 100644
--- a/content/doc/flex/using/flx_dragdrop_dd.html
+++ b/content/doc/flex/using/flx_dragdrop_dd.html
@@ -595,7 +595,7 @@ the ITreeDataProvider API interface. </p>
<li>
<p>The index of the item that was clicked
by the mouse. The
-format string of the index is “<samp class="codeph">caretIndex</samp>”. The
+format string of the index is "<samp class="codeph">caretIndex</samp>". The
index is relative to the items in the drag data. Therefore, if the
drag data contains three items, the index is a value between 0 and
2. By default, only the Spark list-based controls working as a drop
@@ -1965,7 +1965,7 @@ For the Tree control, the format String is "<samp
class="codeph">treeItems</samp
<p>For
Spark controls only, the DragSource object also contains the index
of the item in the drag initiator that was clicked by the mouse.
-The format string of the index is “<samp class="codeph">caretIndex</samp>”.
+The format string of the index is "<samp class="codeph">caretIndex</samp>".
The index is relative to the items in the drag data. Therefore,
if the drag data contains three items, the index is a value between
0 and 2.</p>
diff --git a/content/doc/flex/using/flx_embed_em.html
b/content/doc/flex/using/flx_embed_em.html
index 4a278d81b..4357029ef 100644
--- a/content/doc/flex/using/flx_embed_em.html
+++ b/content/doc/flex/using/flx_embed_em.html
@@ -566,10 +566,10 @@ assets; the only difference is where you use them in your
application.</p>
<div>
<p>You can use the slash character (\) to escape the at sign
character (@) when you want to use a literal @ character. For example,
-the string “\@Embed(foo)” means the literal string “@Embed(foo)”).
+the string "\@Embed(foo)" means the literal string "@Embed(foo)").
You use two slash characters (\\) to escape a single backslash character.
-For example, use the character string “\@” to specify the literal
-strings “\@”.</p>
+For example, use the character string "\@" to specify the literal
+strings "\@".</p>
</div>
diff --git a/content/doc/flex/using/flx_events_ev.html
b/content/doc/flex/using/flx_events_ev.html
index 863785076..9666bdbaf 100644
--- a/content/doc/flex/using/flx_events_ev.html
+++ b/content/doc/flex/using/flx_events_ev.html
@@ -56,7 +56,7 @@ of a component or when the component is resized.</p>
<p>Any user interaction with your application can generate events.
Events can also occur without any direct user interaction, such
as when data finishes loading from a server or when an attached
-camera becomes active. You can “handle” these events in your code
+camera becomes active. You can "handle" these events in your code
by adding an event handler. <em>Event handlers</em> are the functions
or methods that you write to respond to specific events. They are
also sometimes referred to as <em>event listeners</em>. </p>
@@ -871,7 +871,7 @@ signature:</p>
<em>event_type</em>
</samp> argument is the kind of
event that this component dispatches. This can be either the event
-type String (for example, “click” or “mouseOut”) or the event type
+type String (for example, "click" or "mouseOut") or the event type
static constant (such as <samp class="codeph">MouseEvent.CLICK</samp> or <samp
class="codeph">MouseEvent.MOUSE_OUT</samp>).
This argument is required.</p>
diff --git a/content/doc/flex/using/flx_fonts_ft.html
b/content/doc/flex/using/flx_fonts_ft.html
index 6b7fd25d7..874707657 100644
--- a/content/doc/flex/using/flx_fonts_ft.html
+++ b/content/doc/flex/using/flx_fonts_ft.html
@@ -375,7 +375,7 @@ Embedded fonts have the following limitations and
drawbacks:</p>
<ul>
<li>
- <p>Embed only TrueType or OpenType fonts and related
“collection”
+ <p>Embed only TrueType or OpenType fonts and related
"collection"
formats. To embed other font types such as Type 1 PostScript fonts,
embed that font in a SWF file that you create in Flash or with the
fontswf utility, and then embed that SWF file in your application.
@@ -416,7 +416,7 @@ fonts with MX components</a>.</p>
</p>
<p>You typically use Cascading Style Sheets (CSS) syntax for embedding
-fonts in applications. You use the <samp class="codeph">@font-face</samp>
“at-rule”
+fonts in applications. You use the <samp class="codeph">@font-face</samp>
"at-rule"
declaration to specify the source of the embedded font and then
define the name of the font by using the <samp
class="codeph">fontFamily</samp> property.
You typically specify the <samp class="codeph">@font-face</samp> declaration
@@ -708,12 +708,12 @@ as the font in the VGroup type selector:</p>
</p>
<p>When you run this example, you might notice that the label on
-the MX Button (in the “mx” namespace) disappears. This is because
+the MX Button (in the "mx" namespace) disappears. This is because
the default style of an MX Button control’s label uses a bold typeface.
However, the embedded font’s typeface (Myriad Web Pro) does not
contain a definition for the bold typeface. </p>
- <p>The Spark Button (in the “s” namespace) control’s label renders
+ <p>The Spark Button (in the "s" namespace) control’s label renders
with the embedded font because it does not require a bold faced
font.</p>
@@ -931,7 +931,7 @@ character ranges</a>.</p>
<div>
<p>When the <samp class="codeph">@font-face src</samp>
property points
-to a file that is a “container” of several fonts (such as a *.ttc
+to a file that is a "container" of several fonts (such as a *.ttc
or *.dfont file), you use the <samp class="codeph">fontFamily</samp> property
to
select the precise font face you want out of the collection. The
value of the <samp class="codeph">fontFamily</samp> property should be the
@@ -1535,7 +1535,7 @@ font’s family name. </p>
<p>Sets the included character range.</p>
<p>The
-default value is “*”, which includes all characters.</p>
+default value is "*", which includes all characters.</p>
<p>For information
on using character ranges, see <a
href="flx_fonts_ft.html#WS2db454920e96a9e51e63e3d11c0bf69084-7e04_verapache">Setting
diff --git a/content/doc/flex/using/flx_formatters_fm.html
b/content/doc/flex/using/flx_formatters_fm.html
index ee9109a50..77980b5d1 100644
--- a/content/doc/flex/using/flx_formatters_fm.html
+++ b/content/doc/flex/using/flx_formatters_fm.html
@@ -635,7 +635,7 @@ is unable to parse the String into a Date object, it
returns <samp class="codeph
of the <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/spark/formatters/DateTimeFormatter.html";
target="_blank">DateTimeFormatter</a> class
to specify the string of pattern letters that determine the appropriate
formatting. You compose a pattern string by using specific letter
-sequences. For example, “yyyy/MM”. </p>
+sequences. For example, "yyyy/MM". </p>
<div class="p">
<div class="note"><span class="notetitle">Note:</span> By
omitting a pattern
@@ -649,7 +649,7 @@ the formatted string is fixed by the specified pattern
string.</div>
<p>You
can include text and punctuation in the pattern string. However
-the characters from “a” to “z” and from “A” to “Z” are reserved
+the characters from "a" to "z" and from "A" to "Z" are reserved
as syntax characters. Enclose these characters in single quotes
to include them in the formatted output string. To include a single
quote, use two single quotes. The two single quotes may appear inside
@@ -660,16 +660,16 @@ create a pattern string, you usually repeat pattern
letters. The
number of repeated letters determines the presentation. For numeric
values, the number of pattern letters is the minimum number of digits;
shorter numbers are zero-padded to this amount. For example, the
-four-letter pattern string “yyyy” corresponds to a four-digit year
+four-letter pattern string "yyyy" corresponds to a four-digit year
value. </p>
<p>In cases where there is a corresponding mapping of
a text description—for example, the name of a month—the full form
is used if the number of pattern letters is four or more; otherwise,
a short or abbreviated form is used, if available. For example,
-if you specify the pattern string “MMMM” for month, the formatter requires
-the full month name, such as “December”, instead of the abbreviated month
-name, such as “Dec”. </p>
+if you specify the pattern string "MMMM" for month, the formatter requires
+the full month name, such as "December", instead of the abbreviated month
+name, such as "Dec". </p>
<p>For time values, a single pattern letter
is interpreted as one or two digits. Two pattern letters are interpreted
@@ -1174,16 +1174,16 @@ you create a pattern string, you usually repeat pattern
letters.
The number of repeated letters determines the presentation. For
numeric values, the number of pattern letters is the minimum number
of digits; shorter numbers are zero-padded to this amount. For example,
-the four-letter pattern string “YYYY” corresponds to a four-digit
+the four-letter pattern string "YYYY" corresponds to a four-digit
year value.</p>
<p>In cases where there is a corresponding mapping
of a text description—for instance, the name of a month—the full
form is used if the number of pattern letters is four or more; otherwise,
a short or abbreviated form is used, if available. For example,
-if you specify the pattern string “MMMM” for month, the formatter requires
-the full month name, such as “December”, instead of the abbreviated month
-name, such as “Dec”. </p>
+if you specify the pattern string "MMMM" for month, the formatter requires
+the full month name, such as "December", instead of the abbreviated month
+name, such as "Dec". </p>
<p>For time values, a single pattern letter
is interpreted as one or two digits. Two pattern letters are interpreted
diff --git a/content/doc/flex/using/flx_functest_components2_fc.html
b/content/doc/flex/using/flx_functest_components2_fc.html
index 0b653f12a..d9ce815f5 100644
--- a/content/doc/flex/using/flx_functest_components2_fc.html
+++ b/content/doc/flex/using/flx_functest_components2_fc.html
@@ -539,7 +539,7 @@ command line compiler or write your own batch file.</p>
<div>
<p>As a Flex developer, there are some techniques that you
-can employ to make applications as “test friendly” as possible.
+can employ to make applications as "test friendly" as possible.
One of the most important tasks that you can perform is to make
sure that objects are identifiable in the testing tool’s scripts.
This means that you should explicitly set the value of the <samp
class="codeph">id</samp> property
@@ -2007,8 +2007,8 @@ that can be tested.</p>
which is specific to the QTP automation tool. This file is included
in the Flex Automation Package.</p>
- <p>The TEAFlex.xml file is located in the
“<em>QTP_plugin_install</em>/Adobe
-Flex 4 Plug-in for HP QuickTest Pro” directory. QTP recognizes any
+ <p>The TEAFlex.xml file is located in the
"<em>QTP_plugin_install</em>/Adobe
+Flex 4 Plug-in for HP QuickTest Pro" directory. QTP recognizes any
file in that directory that matches the pattern TEAFlex*.xml, where
* can be any string. This directory also contains a TEAFlexCustom.xml
file that you can use as a starting point for adding custom component
@@ -2255,8 +2255,8 @@ with several arguments to the Button control:</p>
<p>When you finish editing the class definitions file, you must
distribute the new file to the automation tool users. For QTP, users
-must copy this file manually to the “<em>QTP_plugin_install</em>\Adobe
-Flex 4 Plug-in for HP QuickTest Pro” directory. When you replace
+must copy this file manually to the "<em>QTP_plugin_install</em>\Adobe
+Flex 4 Plug-in for HP QuickTest Pro" directory. When you replace
the class definitions file in the QTP environment, you must restart QTP.</p>
</div>
@@ -2278,8 +2278,8 @@ is not always the case.</p>
<p>For some components, Flex sets the value of the <samp
class="codeph">automationName</samp> property
to a recognizable attribute of that component. This helps QC professionals
recognize
-that component in their scripts. For example, a Spark Button labeled “Process
-Form Now” appears in the testing scripts as <samp
class="codeph">SparkButton("Process Form Now")</samp>.</p>
+that component in their scripts. For example, a Spark Button labeled "Process
+Form Now" appears in the testing scripts as <samp
class="codeph">SparkButton("Process Form Now")</samp>.</p>
<p>If you implement a new component, or subclass an existing
component,
you might want to override the default value of the <samp
class="codeph">automationName</samp> property.
@@ -2288,9 +2288,9 @@ the component’s <samp class="codeph">id</samp> property
by default, but some
components use their own methods of setting its value.</p>
<p>The following example sets the <samp
class="codeph">automationName</samp> property
-of the ComboBox control to “Credit Card List”; rather than using
+of the ComboBox control to "Credit Card List"; rather than using
the <samp class="codeph">id</samp> property, the testing tool typically uses
-“Credit Card List” to identify the ComboBox in its scripts:</p>
+"Credit Card List" to identify the ComboBox in its scripts:</p>
<pre class="noswf"><?xml version="1.0"?>
<!-- agent/SimpleComboBox.mxml -->
diff --git a/content/doc/flex/using/flx_fxg_fx.html
b/content/doc/flex/using/flx_fxg_fx.html
index ac178a502..50a2556c1 100644
--- a/content/doc/flex/using/flx_fxg_fx.html
+++ b/content/doc/flex/using/flx_fxg_fx.html
@@ -1582,8 +1582,8 @@ location, you must add the location to the compiler’s
source path.</p>
<li>
<p>Declare a namespace for the component. For example, if
the
FXG file is in the same directory as the main application that uses
-it, you can declare a namespace of “*”. If the FXG file is in a
-directory called comps, you can declare a namespace of “comps.*”.</p>
+it, you can declare a namespace of "*". If the FXG file is in a
+directory called comps, you can declare a namespace of "comps.*".</p>
</li>
@@ -1748,7 +1748,7 @@ edit and export the FXG again from a graphics tool. </p>
<p>One disadvantage to using an FXG file as a standalone
component
is that you cannot get a reference to individual elements in it.
-The FXG component itself is a “black box”; you cannot interact with
+The FXG component itself is a "black box"; you cannot interact with
individual elements from your application or other components. You
can, however, still apply effects, resize, position, and trigger
events from interaction with the FXG component itself.</p>
@@ -1808,7 +1808,7 @@ attributes will be prefixed in these namespaces.</p>
and <samp class="codeph"><Private></samp> elements. They must use the
MXML 2009 language namespace (http://ns.adobe.com/mxml/2009). If
you remove a namespace prefix on the tag, you can usually just add
-the “fx:” prefix to each of these elements.</p>
+the "fx:" prefix to each of these elements.</p>
</li>
@@ -1822,10 +1822,10 @@ it and remove the FXG <samp
class="codeph"><Library></samp> tag. </p>
</li>
<li>
- <p>For library definitions, add the “fx:” prefix to
their tags
+ <p>For library definitions, add the "fx:" prefix to
their tags
in the body of the MXML file. In MXML 2009 documents, library definitions
are actually in the language namespace. For example, the <samp
class="codeph"><fx:Definition name="BlueCircle"></samp> tag
-references to a definition that must also be in the “fx” namespace;
+references to a definition that must also be in the "fx" namespace;
for example, <samp class="codeph"><fx:BlueCircle></samp>.</p>
</li>
@@ -1840,9 +1840,9 @@ generated the FXG.</p>
<li>
<p>Update the namespace prefix of the FXG elements.
There is
-likely to be an “s:” prefix already mapped to the Spark component
+likely to be an "s:" prefix already mapped to the Spark component
namespace on the MXML document’s root tag
(xmlns:s="library://ns.adobe.com/flex/spark").
-Add the “s:” prefix to all of the FXG graphical elements. For example,
+Add the "s:" prefix to all of the FXG graphical elements. For example,
change <samp class="codeph"><Graphic></samp> to <samp
class="codeph"><s:Graphic></samp>.</p>
</li>
@@ -1855,7 +1855,7 @@ change <samp class="codeph"><Graphic></samp> to
<samp class="codeph"><s
<p>Convert <samp
class="codeph"><TextGraphic></samp> elements
to <samp class="codeph"><s:RichText></samp>. This does not apply to FXG
2.0 documents, which use the <samp class="codeph"><RichText></samp> tag.
-In that case, you just add the “s:” prefix to the <samp
class="codeph"><RichText></samp> tag
+In that case, you just add the "s:" prefix to the <samp
class="codeph"><RichText></samp> tag
to make it conform to MXML syntax.</p>
</li>
@@ -1863,7 +1863,7 @@ to make it conform to MXML syntax.</p>
<li>
<p>Convert <samp
class="codeph"><BitmapGraphic></samp> elements to <samp
class="codeph"><s:BitmapImage></samp>.
This does not apply to FXG 2.0 documents, which use the <samp
class="codeph"><BitmapImage></samp> tag.
-In that case, you just add the “s:” prefix to the <samp
class="codeph"><BitmapImage></samp> tag
+In that case, you just add the "s:" prefix to the <samp
class="codeph"><BitmapImage></samp> tag
to make it conform to MXML syntax.</p>
</li>
@@ -2007,12 +2007,12 @@ xmlns:d="http://ns.adobe.com/fxg/2008/dt";</pre>
</li>
<li>
- <p>Add the “s:” prefix to all elements.</p>
+ <p>Add the "s:" prefix to all elements.</p>
</li>
<li>
- <p>Because the “d” and “ai” namespace definitions are
intact,
+ <p>Because the "d" and "ai" namespace definitions are
intact,
you do not have to remove the attributes specific to these namespaces.
The attributes <samp class="codeph">type</samp> and <samp
class="codeph">userLabel</samp>,
for example, appear on the <samp class="codeph"><Group></samp> tag from
@@ -2215,14 +2215,14 @@ of 0.05882352941176471 to 0.06.</p>
</div>
<div class="nested3"
id="WS19f279b149e7481c19e0d29912b7d17c948-7ffd_verapache"><a
name="WS19f279b149e7481c19e0d29912b7d17c948-7ffd_verapache"><!-- --></a>
- <h4 class="topictitle4">Remove blendMode=”normal”</h4>
+ <h4 class="topictitle4">Remove blendMode="normal"</h4>
<div>
<p>By default on graphic elements, the <samp
class="codeph">blendMode</samp> is
-“auto”. When the <samp class="codeph">blendMode</samp> property is “auto”,
+"auto". When the <samp class="codeph">blendMode</samp> property is "auto",
Flash Player correctly determines whether the element needs to use
-the “layer” <samp class="codeph">blendMode</samp> based on the <samp
class="codeph">alpha</samp> value.</p>
+the "layer" <samp class="codeph">blendMode</samp> based on the <samp
class="codeph">alpha</samp> value.</p>
</div>
@@ -2790,7 +2790,7 @@ the Move segment type to reposition the pen without
drawing a line.</p>
<p>The Path syntax is nearly identical to the SVG path syntax. This
makes it easy to convert SVG paths to FXG or MXML graphics. There
-is one exception: FXG and MXML graphics do not support an “A” or
+is one exception: FXG and MXML graphics do not support an "A" or
Arc segment. To create an arc (elliptical, parabolic, or otherwise),
use the the cubic Bezier and quadratic Bezier control points to
achieve any sort of arc.</p>
diff --git a/content/doc/flex/using/flx_gumboskinning_gs.html
b/content/doc/flex/using/flx_gumboskinning_gs.html
index 7df7abb81..0c6be9a50 100644
--- a/content/doc/flex/using/flx_gumboskinning_gs.html
+++ b/content/doc/flex/using/flx_gumboskinning_gs.html
@@ -112,7 +112,7 @@ property to apply a skin to a component, as the following
example
shows:</p>
<pre class="codeblock">s|Button {
- skinClass: ClassReference(“com.mycompany.skins.MyButtonSkin”);
+ skinClass: ClassReference("com.mycompany.skins.MyButtonSkin");
}</pre>
<p>When applying skins with MXML, you specify the name of the skin
@@ -399,7 +399,7 @@ with Flex 4:
<td class="cellrowborder" valign="top" width="NaN%"
headers="d262787e440 ">
<p>A simplified theme for developing applications
-with a “prototype” look to them. To use wireframe skins, you can
+with a "prototype" look to them. To use wireframe skins, you can
apply the wireframe theme or apply the skins on a per-component
basis.</p>
@@ -673,7 +673,7 @@ tag with the following syntax:</p>
<p>For example:</p>
<pre class="codeblock"><fx:Metadata>
- [HostComponent(“spark.components.Button”)]
+ [HostComponent("spark.components.Button")]
</fx:Metadata></pre>
<p>When a skin defines this metadata, Flex creates the typed
property <samp class="codeph">hostComponent</samp> on
@@ -748,15 +748,15 @@ that it supports. To identify a skin state in the
component’s class,
you use the <samp class="codeph">[SkinState]</samp> metadata tag. This tag
has the following syntax:</p>
- <pre class="codeblock">[SkinState(“state”)]</pre>
+ <pre class="codeblock">[SkinState("state")]</pre>
<p>You specify the metadata before the class definition. The
following
example defines four skin states for the Button control:</p>
- <pre class="codeblock">[SkinState(“up”)]
-[SkinState(“over”)]
-[SkinState(“down”)]
-[SkinState(“disabled”)]
+ <pre class="codeblock">[SkinState("up")]
+[SkinState("over")]
+[SkinState("down")]
+[SkinState("disabled")]
public class Button extends Component { .. } </pre>
</div>
@@ -803,10 +803,10 @@ skin class:</p>
<pre class="codeblock"><s:Skin ...>
<s:states>
- <s:State name=”up”/>
- <s:State name=”over”/>
- <s:State name=”down”/>
- <s:State name=”disabled”/>
+ <s:State name="up"/>
+ <s:State name="over"/>
+ <s:State name="down"/>
+ <s:State name="disabled"/>
</s:states>
...
</s:Skin></pre>
@@ -1253,7 +1253,7 @@ For example, if you have the following declaration in
your component:</p>
public var textInput:TextInput;</pre>
<p>The skin class sets the <samp class="codeph">id</samp>
attribute of a TextInput
-instance to “textInput”, as the following example shows:</p>
+instance to "textInput", as the following example shows:</p>
<pre class="codeblock"><s:TextInput id="textInput" ...
/></pre>
@@ -1325,14 +1325,14 @@ with all Panel containers by using a type selector:</p>
<pre class="codeblock">@namespace s
"library://ns.adobe.com/flex/spark";
s|Panel {
- skinClass:ClassReference(“mySkins.NewPanelSkin“);
+ skinClass:ClassReference("mySkins.NewPanelSkin");
}</pre>
<p>The following example associates the mySkins.CustomButtonSkin
class with all components that use the myButtonStyle class selector:</p>
<pre class="codeblock">.myButtonStyle {
- skinClass:ClassReference(“mySkins.CustomButtonSkin”);
+ skinClass:ClassReference("mySkins.CustomButtonSkin");
}
...
<s:Button label="Spark Button" className="myButtonStyle"/></pre>
@@ -1342,13 +1342,13 @@ of the <samp class="codeph">skinClass</samp> property
inline. The following
example applies the mySkins.NewPanelSkin class to this instance
of the Panel container:</p>
- <pre class="codeblock"><s:Panel
skinClass=”mySkins.NewPanelSkin”/></pre>
+ <pre class="codeblock"><s:Panel
skinClass="mySkins.NewPanelSkin"/></pre>
<p>The advantage to applying skins with CSS is that with CSS you
can use type and class selectors to apply the skin to all components
of a particular type (such as all Buttons) or all classes that are
in a particular class (such as all components with the style name
-“myButtonStyle”).</p>
+"myButtonStyle").</p>
<p>CSS supports inheritance. If you apply a skin class to a
Button
control in the Button type selector, the skin applies to all Button
@@ -1483,7 +1483,7 @@ as the following example shows:</p>
<pre class="codeblock">/**
* Up state of the button.
*/
-[SkinState(“up”)]</pre>
+[SkinState("up")]</pre>
<p>To document a <samp class="codeph">[SkinPart]</samp> metadata
tag, the ASDoc
utility uses the description of the variable from the component’s
@@ -1496,9 +1496,9 @@ as the following example shows:</p>
*/
public var labelDisplay:TextGraphicElement;</pre>
- <p>The ASDoc utility adds skin state documentation to the “Skin
-States” section of the class’s documentation. It adds skin part
-documentation to the “Skin Parts” section of the class’s documentation.</p>
+ <p>The ASDoc utility adds skin state documentation to the "Skin
+States" section of the class’s documentation. It adds skin part
+documentation to the "Skin Parts" section of the class’s documentation.</p>
<p>For more information about the ASDoc utility, see <a
href="flx_asdoc_asd.html#WSd0ded3821e0d52fe1e63e3d11c2f44bb7b-7fe7_verapache">ASDoc</a>.</p>
@@ -1518,7 +1518,7 @@ started is to use the source of an existing skin of a
similar type
as your base class. You can use the default Spark skins as a good
starting point for creating skins, or the skins in the Wireframe
theme. The Wireframe theme defines a set of simple skins that provide a
-“prototype” look to the application. They are lighter weight than
+"prototype" look to the application. They are lighter weight than
the default skins but have less functionality.</p>
<p>The default Spark skins are more heavyweight than the Wireframe
diff --git a/content/doc/flex/using/flx_halo_effects_hf.html
b/content/doc/flex/using/flx_halo_effects_hf.html
index 0b42717f8..a9726eb67 100644
--- a/content/doc/flex/using/flx_halo_effects_hf.html
+++ b/content/doc/flex/using/flx_halo_effects_hf.html
@@ -402,8 +402,8 @@ The following example creates the WipeLeft effect in
ActionScript: <pre class="c
<p>This example still uses an event to invoke the effect. To play
an effect programmatically, you call the effect’s <samp
class="codeph">play()</samp> method.
For information on using ActionScript to configure and invoke effects,
-and for more information on using MXML, see “Applying behaviors
-in MXML” on page 130.</p>
+and for more information on using MXML, see "Applying behaviors
+in MXML" on page 130.</p>
</div>
diff --git a/content/doc/flex/using/flx_l10n_ln.html
b/content/doc/flex/using/flx_l10n_ln.html
index 509fafa3d..7187d52c7 100644
--- a/content/doc/flex/using/flx_l10n_ln.html
+++ b/content/doc/flex/using/flx_l10n_ln.html
@@ -57,8 +57,8 @@ Britain) are different locales and therefore use different
sets
of assets. In this case, both locales use the English language,
but the country code indicates that they are different locales,
and might therefor use different assets. For example, an application
-in the en_US locale might spell the word “color”, whereas the word
-would be “colour” in the en_GB locale. Also, units of currency would
+in the en_US locale might spell the word "color", whereas the word
+would be "colour" in the en_GB locale. Also, units of currency would
be represented in dollars or pounds, depending on the locale, and
the format of dates and times would also be different.</p>
@@ -203,7 +203,7 @@ then all components in that application inherit that style,
unless
they specifically override it. If you do not set the <samp
class="codeph">locale</samp> style
property, the compiler uses the global defaults that are defined
in the defaults.css style sheet. In this case, the default value
-is “en”.</p>
+is "en".</p>
<div class="p">The following example sets the value of the
application’s <samp class="codeph">locale</samp> style
property to the <samp class="codeph">LocaleID.DEFAULT</samp> constant. When
@@ -563,8 +563,8 @@ string to all lower case:<pre class="codeblock"><?xml
version="1.0" encoding=
<p>Note that some characters for some languages do not have the
same character length before and after case conversion. For example,
-the lower case sharp-s (“ß”) is represented with two characters,
-“SS”, when converted to upper case in the German language.</p>
+the lower case sharp-s ("ß") is represented with two characters,
+"SS", when converted to upper case in the German language.</p>
</div>
@@ -578,8 +578,8 @@ the lower case sharp-s (“ß”) is represented with two
characters,
<p>When ordering a list that is presented visually to the
user, it is essential to follow the user’s expectations. It is not
just a question of aesthetics: expecting it at the end of the list,
-a Swedish user might fail to find an element that begins with “ö”
-if placed next to the plain “o”. Fortunately, avoiding that problem
+a Swedish user might fail to find an element that begins with "ö"
+if placed next to the plain "o". Fortunately, avoiding that problem
is easy: sort the list with a Sort or SortingCollator class that
is configured for the user’s locale.</p>
diff --git a/content/doc/flex/using/flx_layoutperformance_lp.html
b/content/doc/flex/using/flx_layoutperformance_lp.html
index 96261e3a5..d1a284a46 100644
--- a/content/doc/flex/using/flx_layoutperformance_lp.html
+++ b/content/doc/flex/using/flx_layoutperformance_lp.html
@@ -736,7 +736,7 @@ you can pass to that function.</p>
<p>The following example defers the invocation of the <samp
class="codeph">doSomething()</samp> method, but
when it is opened, Flex passes the <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/events/Event.html";
target="_blank">Event</a> object
-and the “Product Description” String in an Array to that function:</p>
+and the "Product Description" String in an Array to that function:</p>
<pre class="codeblock"> callLater(doSomething, [event, "Product
Description"]);
...
diff --git a/content/doc/flex/using/flx_loading_applications_la.html
b/content/doc/flex/using/flx_loading_applications_la.html
index c900f80ef..3b3744433 100644
--- a/content/doc/flex/using/flx_loading_applications_la.html
+++ b/content/doc/flex/using/flx_loading_applications_la.html
@@ -1312,7 +1312,7 @@ and the sub-application is on www2.domainA.com, then the
sub-application
is considered untrusted by default. To load data from the sub-application,
the sub-application’s domain would require a policy file.</p>
- <p>Cross-domain applications can be “import loaded,” which means
+ <p>Cross-domain applications can be "import loaded," which means
that they are loaded into the same security domain as the main application.
You do this by setting the <samp class="codeph">trustContent</samp> flag to
<samp class="codeph">true</samp> on
the SWFLoader, or by specifying that the application load into the
@@ -2712,7 +2712,7 @@ must embed the font to use it.</p>
<div>
<p>The <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/managers/FocusManager.html";
target="_blank">FocusManager</a> class
in the main application and sub-application integrate to create
-a seamless focus scheme. Users can “tab through” the sub-application,
regardless
+a seamless focus scheme. Users can "tab through" the sub-application,
regardless
of whether the application is in the same or a different security domain
as the main application. Shift tabbing also works. The FocusManager class
is one of the few manager classes that supports interoperability
diff --git a/content/doc/flex/using/flx_logging_lg.html
b/content/doc/flex/using/flx_logging_lg.html
index dfd122296..8a4d5c3f8 100644
--- a/content/doc/flex/using/flx_logging_lg.html
+++ b/content/doc/flex/using/flx_logging_lg.html
@@ -269,7 +269,7 @@ Support/Macromedia</p>
</p>
<p>The
-default value is “c:\Documents and settings\<em>username</em>”.</p>
+default value is "c:\Documents and settings\<em>username</em>".</p>
<p>Your
system administrator might map the home directory to a shared network
@@ -292,7 +292,7 @@ how to configure your debugger Player.</p>
</p>
<p>The
-default value is “c:\Users\<em>username</em>”.</p>
+default value is "c:\Users\<em>username</em>".</p>
<p>Your system administrator
might map the home directory to a shared network drive. In that
@@ -879,12 +879,12 @@ and call methods on the <a
href="http://help.adobe.com/en_US/FlashPlatform/refer
of information used to filter a message are category and level.
Each logger operates under a category. A <em>category</em> is a string
used to filter all messages sent from that logger. For example,
-a logger can be acquired with the category “orange”. Any message
-sent using the “orange” logger only reaches those targets that are
-listening for the “orange” category. In contrast to the category
+a logger can be acquired with the category "orange". Any message
+sent using the "orange" logger only reaches those targets that are
+listening for the "orange" category. In contrast to the category
that is applied to all messages sent with a logger, the <em>level</em>
provides additional
filtering on a per-message basis. For example, to indicate that
-an error occurred within the “orange” subsystem, you can use the
+an error occurred within the "orange" subsystem, you can use the
error level when logging the message. The supported levels are defined
by the LogEventLevel class. The Flex framework classes that use
the logging API set the category to the fully qualified class name
@@ -1135,7 +1135,7 @@ files.</p>
<p>The log level lets you restrict the amount
of messages sent to any running targets. Whatever log level you
-specify, all “lower” levels of messages are written to the log.
+specify, all "lower" levels of messages are written to the log.
For example, if you set the log level to <samp class="codeph">DEBUG</samp>,
all log levels are included. If you set the log level to <samp
class="codeph">WARNING</samp>,
only <samp class="codeph">WARNING</samp>, <samp class="codeph">ERROR</samp>,
and <samp class="codeph">FATAL</samp> messages
@@ -1503,7 +1503,7 @@ the message. </p>
within the Flex framework, you can restrict this to a certain package
or packages, or to other classes. To restrict the logging to your
custom class only, add the category specified when the logger was
-acquired (“MyCustomLogger”) to the <samp class="codeph">filters</samp> Array,
+acquired ("MyCustomLogger") to the <samp class="codeph">filters</samp> Array,
as the following example shows:</p>
<pre class="codeblock"> <mx:filters>
@@ -1530,9 +1530,9 @@ be any String that falls within the filters definitions.
</div>
<p>The value of the category must fall within the definition of
at least one of the filters for the log message to be logged. For
example, if you set the <samp class="codeph">filters</samp> property to
something
-other than “*” and you use <samp
class="codeph">Log.getLogger("MyCustomLogger")</samp>,
+other than "*" and you use <samp
class="codeph">Log.getLogger("MyCustomLogger")</samp>,
the filter Array must include an entry that matches MyCustomLogger,
-such as “MyCustomLogger” or “My*”. </p>
+such as "MyCustomLogger" or "My*". </p>
<p>You can include the logger’s category in your log message, if
you set the logger’s <samp class="codeph">includeCategory</samp> property to
<samp class="codeph">true</samp>. </p>
diff --git a/content/doc/flex/using/flx_menucontrols_mc.html
b/content/doc/flex/using/flx_menucontrols_mc.html
index 8c5caa4ea..9486f54bb 100644
--- a/content/doc/flex/using/flx_menucontrols_mc.html
+++ b/content/doc/flex/using/flx_menucontrols_mc.html
@@ -280,7 +280,7 @@ a check mark in the menu next to the item’s label. </p>
<p>Items with the <samp class="codeph">radio</samp>
type operate in groups,
much like RadioButton controls; you can select only one radio menu
item in each group at a time. The example in this section defines
-three submenu items as radio buttons within the group “one”. </p>
+three submenu items as radio buttons within the group "one". </p>
<p>When
a radio button is selected, the radio item’s <samp
class="codeph">toggled</samp> property
@@ -1864,10 +1864,10 @@ buttons. </p>
<li>
<p>If your data provider has a label attribute (even if it is
-called “label”), you must set the MenuBar control’s <samp
class="codeph">labelField</samp> property
+called "label"), you must set the MenuBar control’s <samp
class="codeph">labelField</samp> property
and use the E4X @ notation for the label; for example:</p>
- <pre class="codeblock"> labelField=”@label”</pre>
+ <pre class="codeblock"> labelField="@label"</pre>
</li>
@@ -2133,10 +2133,10 @@ on the main button, and overrides any label from the
pop-up menu
that is determined by the <samp class="codeph">labelField</samp> or <samp
class="codeph">labelFunction</samp> property.
The <samp class="codeph">label</samp> property is useful for creating a main
button label with fixed and a variable parts; for example, a mail
-“Send to:” button where only the destination text is controlled by
-the pop-up menu, so the main button could say “Send to: Inbox” or
-“Send to: Trash” based on the selection from a menu that lists “Menu”
-and “Trash.” </p>
+"Send to:" button where only the destination text is controlled by
+the pop-up menu, so the main button could say "Send to: Inbox" or
+"Send to: Trash" based on the selection from a menu that lists "Menu"
+and "Trash." </p>
<p>To use a dynamic <samp class="codeph">label</samp> property,
use a PopUpMenuButton control <samp class="codeph">change</samp> event listener
diff --git a/content/doc/flex/using/flx_metadata_me.html
b/content/doc/flex/using/flx_metadata_me.html
index b92928e5c..fd60f2895 100644
--- a/content/doc/flex/using/flx_metadata_me.html
+++ b/content/doc/flex/using/flx_metadata_me.html
@@ -1338,7 +1338,7 @@ tag has the following syntax:</p>
<p>For example:</p>
<pre class="codeblock"><Metadata>
- [HostComponent(“spark.components.Button”)]
+ [HostComponent("spark.components.Button")]
</Metadata></pre>
<p>As a result of this metadata, Flex creates the property <samp
class="codeph">hostComponent</samp> on
@@ -1476,7 +1476,7 @@ tag has the following syntaxes:</p>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d296857e2035 ">
<p>Groups the property into a specific subcategory
in the Property inspector of the Flash Builder user interface. The
-default category is <samp class="codeph">"Other"</samp>. Specify a value of
<samp class="codeph">"Common"</samp>, <samp class="codeph">"Effects"</samp>,
<samp class="codeph">"Events"</samp>, <samp class="codeph">"Layout
Constraints"</samp>, <samp class="codeph">"Size"</samp>, <samp
class="codeph">"Styles"</samp>, <samp class="codeph">“Text”,</samp> or <samp
class="codeph">"Other"</samp>.</p>
+default category is <samp class="codeph">"Other"</samp>. Specify a value of
<samp class="codeph">"Common"</samp>, <samp class="codeph">"Effects"</samp>,
<samp class="codeph">"Events"</samp>, <samp class="codeph">"Layout
Constraints"</samp>, <samp class="codeph">"Size"</samp>, <samp
class="codeph">"Styles"</samp>, <samp class="codeph">"Text",</samp> or <samp
class="codeph">"Other"</samp>.</p>
</td>
@@ -2200,7 +2200,7 @@ values for the style property.</p>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d296857e2971 ">
<p>Specifies the units of the property. For
-example, if you specify <samp class="codeph">type</samp> as <samp
class="codeph">“Number”</samp>, you
+example, if you specify <samp class="codeph">type</samp> as <samp
class="codeph">"Number"</samp>, you
might specify <samp class="codeph">format="Length"</samp> if the style defines
a length measured in pixels. Or, if you specify <samp
class="codeph">type="uint"</samp>,
you might set <samp class="codeph">format="Color"</samp> if the style defines
an
diff --git a/content/doc/flex/using/flx_mirroring_mr.html
b/content/doc/flex/using/flx_mirroring_mr.html
index 084be58b1..9ad85a3b3 100644
--- a/content/doc/flex/using/flx_mirroring_mr.html
+++ b/content/doc/flex/using/flx_mirroring_mr.html
@@ -1808,7 +1808,7 @@ behavior of images or videos is that the contents are not
mirrored. </p>
<p>You can override this behavior in most cases, so that the
contents
of these controls is mirrored. You do this by setting the value
-of the <samp class="codeph">layoutDirection</samp> property to “rtl” directly
+of the <samp class="codeph">layoutDirection</samp> property to "rtl" directly
on the control. This is true for all the controls mentioned except
Spark Image. The Spark Image control does not mirror its contents regardless
of the value of the <samp class="codeph">layoutDirection</samp> property
because
diff --git a/content/doc/flex/using/flx_modular_md.html
b/content/doc/flex/using/flx_modular_md.html
index 0addf138a..3b9d5075b 100644
--- a/content/doc/flex/using/flx_modular_md.html
+++ b/content/doc/flex/using/flx_modular_md.html
@@ -202,7 +202,7 @@ resources. </p>
<li>
<p>Better encapsulation of related aspects of an application.
-For example, a “reporting” feature can be separated into a module
+For example, a "reporting" feature can be separated into a module
that you can then work on independently.</p>
</li>
diff --git a/content/doc/flex/using/flx_mxmlSyntax_sy.html
b/content/doc/flex/using/flx_mxmlSyntax_sy.html
index 1bfcc1e15..5c0dbf714 100644
--- a/content/doc/flex/using/flx_mxmlSyntax_sy.html
+++ b/content/doc/flex/using/flx_mxmlSyntax_sy.html
@@ -552,7 +552,7 @@ tags, as the following example shows: <pre
class="codeblock"><?xml version="1
<p>In this example, the <samp
class="codeph">RichText.content</samp> property
is of type Object. The property value contains values defined by <samp
class="codeph"><fx:String></samp> tag,
-and by character data (“Hello Flex!”). Character data is almost
+and by character data ("Hello Flex!"). Character data is almost
always converted to a value of type String. However, an Array property
may be defined to support an explicit data type for its values.
In that case, the compiler converts the character data to the appropriate
diff --git a/content/doc/flex/using/flx_mxml_mx.html
b/content/doc/flex/using/flx_mxml_mx.html
index 4625b44c0..7cb5c1701 100644
--- a/content/doc/flex/using/flx_mxml_mx.html
+++ b/content/doc/flex/using/flx_mxml_mx.html
@@ -118,7 +118,7 @@ environments. You can write MXML code in a simple text
editor, a dedicated
XML editor, or an integrated development environment (IDE) that supports
text editing.</p>
- <p>The following example shows a simple “Hello World” application
+ <p>The following example shows a simple "Hello World" application
that contains just an <samp class="codeph"><s:Application></samp> tag
and three child tags, the <samp class="codeph"><s:Panel></samp> tag and
the <samp class="codeph"><s:Label></samp> tags,
plus a <samp class="codeph"><s:layout></samp> tag. The <samp
class="codeph"><s:Application></samp> tag defines
@@ -327,7 +327,7 @@ by using the following MXML statement:</p>
<p>When you declare a control using an MXML tag, you create an
instance
of that class. This MXML statement creates a Button object, and
initializes the <samp class="codeph">label</samp> property of the Button object
-to the string <samp class="codeph">“Submit”</samp>.</p>
+to the string <samp class="codeph">"Submit"</samp>.</p>
<p>An MXML tag that corresponds to an ActionScript class uses the
same naming conventions as the ActionScript class. Class names begin
diff --git a/content/doc/flex/using/flx_performance_pe.html
b/content/doc/flex/using/flx_performance_pe.html
index 4aa62a6a7..cb55a9c57 100644
--- a/content/doc/flex/using/flx_performance_pe.html
+++ b/content/doc/flex/using/flx_performance_pe.html
@@ -574,7 +574,7 @@ cache. </p>
<p>If the date and time in the If-Modified-Since request header
matches the date and time in the Last-Modified response header,
the browser loads the SWF file from its cache. Then the server returns
-the “304 Not Modified” message. If the Last-Modified header is more
+the "304 Not Modified" message. If the Last-Modified header is more
recent, the server returns the SWF file.</p>
<p>You can use the following techniques to disable client-side
caching:</p>
@@ -612,7 +612,7 @@ shows how to set headers that prevent caching in JSP:</p>
response.header("Last-Modified", new Date());</pre>
<p>Note
-that in some cases, setting the <samp class="codeph">Pragma</samp> header to
<samp class="codeph">“no-cache”</samp> can cause
+that in some cases, setting the <samp class="codeph">Pragma</samp> header to
<samp class="codeph">"no-cache"</samp> can cause
a runtime error with GET requests over SSL with the HTTPService
class. In this case, setting just the <samp
class="codeph">Cache-control</samp> header
should work. </p>
@@ -1429,7 +1429,7 @@ follows:<ul>
</div>
- <p>You can specify “i” to
+ <p>You can specify "i" to
see all the SWC files that have an inheritance dependency on a SWC
file. Some or all of the dependent SWC files must be RSLs; as a
result, be sure that the required classes are loaded before the
diff --git a/content/doc/flex/using/flx_rsl_rsl.html
b/content/doc/flex/using/flx_rsl_rsl.html
index a29e01ea6..99f7d1955 100644
--- a/content/doc/flex/using/flx_rsl_rsl.html
+++ b/content/doc/flex/using/flx_rsl_rsl.html
@@ -379,7 +379,7 @@ compiling your application. You do this with the <samp
class="codeph">force-rsls
option.</p>
<p>Forcing RSLs to load can be useful if you use classes that
are
-only referenced indirectly (sometimes referred to as “soft references”),
+only referenced indirectly (sometimes referred to as "soft references"),
so the compiler might not know they are needed.</p>
<p>When forcing RSLs to load, you must configure them in the
<samp class="codeph">runtime-shared-library-path</samp> option
@@ -614,11 +614,11 @@ The downside to this is that when the module or
sub-application
is unloaded, the RSL is not unloaded.</p>
<p>To prevent a framework
-RSL from being loaded into the main application, you can specify <samp
class="codeph">“current”</samp> for
+RSL from being loaded into the main application, you can specify <samp
class="codeph">"current"</samp> for
the application domain. This loads the RSL into the module or sub-application’s
application domain. When the module or sub-application is unloaded,
so is the RSL. Other modules or sub-applications will not have access
-to it. You should not specify <samp class="codeph">“current”</samp> for the
+to it. You should not specify <samp class="codeph">"current"</samp> for the
application domain when loading the OSMF or MX RSLs. These RSLs
are always loaded into the root application.</p>
@@ -634,7 +634,7 @@ but only with child sub-applications or modules that it
loads.</p>
<p>To
load a custom RSL into an application domain so that it can then
-be shared with other modules and sub-applications, you specify <samp
class="codeph">“top-level”</samp> for
+be shared with other modules and sub-applications, you specify <samp
class="codeph">"top-level"</samp> for
the application domain. This loads the custom RSL into the main
application. All modules and sub-applications will then be able
to access that RSL.</p>
@@ -1783,8 +1783,8 @@ compiled into a SWC file and can be used by any
application at compile
time.</p>
<p>The value of the <samp
class="codeph">rsl-url</samp> argument can
-be a relative URL, such as “../libraries/library.swf”, or an absolute URL,
-such as “http://www.mydomain.com/libraries/library.swf”. If it is
+be a relative URL, such as "../libraries/library.swf", or an absolute URL,
+such as "http://www.mydomain.com/libraries/library.swf";. If it is
on a different server, it must be a cross-domain or framework RSL.
Standard RSLs can only be loaded from the same domain as the application.</p>
@@ -2440,11 +2440,11 @@ the framework RSLs</a>.</p>
<p>It can also occur if Flash Player
tries to load a custom RSL that is not available. For example, if
-you specified only “mylib.swf” as the value of the <samp
class="codeph">rsl-url</samp> parameter
+you specified only "mylib.swf" as the value of the <samp
class="codeph">rsl-url</samp> parameter
to the <samp class="codeph">runtime-shared-library-path</samp> option, but
the SWF file is actually in a sub-directory such as /rsls, then
you must either recompile your application and update the value
-of the <samp class="codeph">rsl-url</samp> parameter to “rsls/mylib.swf”, or
+of the <samp class="codeph">rsl-url</samp> parameter to "rsls/mylib.swf", or
move mylib.swf to the same directory as the application’s SWF file.</p>
</td>
diff --git a/content/doc/flex/using/flx_security2_se.html
b/content/doc/flex/using/flx_security2_se.html
index 59b8f3713..dbc441cf2 100644
--- a/content/doc/flex/using/flx_security2_se.html
+++ b/content/doc/flex/using/flx_security2_se.html
@@ -893,7 +893,7 @@ wrapper:</p>
Expires: -1</pre>
<p>Note that in some cases, setting the <samp
class="codeph">Pragma</samp> header
-to <samp class="codeph">“no-cache”</samp> can cause a runtime error with GET
+to <samp class="codeph">"no-cache"</samp> can cause a runtime error with GET
requests over SSL with the HTTPService class. In this case, setting
just the <samp class="codeph">Cache-control</samp> header should work. </p>
@@ -972,10 +972,10 @@ to access additional data from other domains by explicit
website
and author permissions. </p>
<p>A local SWF file describes any file
-referenced by using the “file” protocol or a UNC path, which does
-not include an IP address or a qualifying domain. For example,
“\\test\test.swf”
-and “file:\test.swf” are considered local files, while “\\test.com\test.swf”
-and “\192.168.0.1\test.swf” are not considered local files.</p>
+referenced by using the "file" protocol or a UNC path, which does
+not include an IP address or a qualifying domain. For example,
"\\test\test.swf"
+and "file:\test.swf" are considered local files, while "\\test.com\test.swf"
+and "\192.168.0.1\test.swf" are not considered local files.</p>
<p>
Local SWF files from local origins, such
@@ -1527,7 +1527,7 @@ processes the form. </p>
<p>The results are submitted to the container’s JAAS system with
base-64 encoding, which means they can be read by anyone that can
view the TCP/IP traffic. Use encryption to prevent these so-called
-“man-in-the-middle” attacks. In both BASIC and FORM authentication,
+"man-in-the-middle" attacks. In both BASIC and FORM authentication,
if the user accessed the resource through SSL, the username and
password submission are encrypted, as is all traffic during that exchange.</p>
@@ -1539,8 +1539,8 @@ used. </p>
<p>When a user fails an authentication attempt with invalid
credentials,
be sure not to return information about which item was incorrect.
-Instead, use a generic message such as “Your login information was
-invalid.” </p>
+Instead, use a generic message such as "Your login information was
+invalid." </p>
</div>
@@ -1855,7 +1855,7 @@ SWF file to the server. For more information about RFC
1321, see <a href="http:/
<p>
To access HTTP
services or web services through HTTPS, you can specify the protocols
-using “https” in the <samp class="codeph">wsdl</samp> or <samp
class="codeph">url</samp> properties;
+using "https" in the <samp class="codeph">wsdl</samp> or <samp
class="codeph">url</samp> properties;
for example: </p>
<pre class="codeblock"> <mx:WebService
url="https://myservice.com"; .../>
@@ -2104,11 +2104,11 @@ out dollar sign ($), quotation mark ("), semi-colon (;)
and apostrophe
(') characters because they have special meaning in most programming
languages. Because Flex also renders HTML in some controls, also
filter out characters that can be used to inject script into HTML,
-such as the left and right angle brackets (“<” and “>”), by converting
-these characters to their HTML entities “&lt;” and “&gt;”.
-Also filter out the left and right parentheses (“(”and “)”) by translating
-them to “&#40;” and “&#41;”, and the pound sign (“#”) and
-ampersand (“&”) by translating them to “&#35” (#) and “&#38”
+such as the left and right angle brackets ("<" and ">"), by converting
+these characters to their HTML entities "&lt;" and "&gt;".
+Also filter out the left and right parentheses ("("and ")") by translating
+them to "&#40;" and "&#41;", and the pound sign ("#") and
+ampersand ("&") by translating them to "&#35" (#) and "&#38"
(&). </p>
<p>
@@ -2873,7 +2873,7 @@ Resource Center</p>
<tr>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d846557e3484 ">
- <p>“Flash Player Security” </p>
+ <p>"Flash Player Security" </p>
</td>
@@ -2888,7 +2888,7 @@ Resource Center</p>
<tr>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d846557e3484 ">
- <p>“Networking and Communications” </p>
+ <p>"Networking and Communications" </p>
</td>
diff --git a/content/doc/flex/using/flx_size_position_sp.html
b/content/doc/flex/using/flx_size_position_sp.html
index 3b01ab020..26487217c 100644
--- a/content/doc/flex/using/flx_size_position_sp.html
+++ b/content/doc/flex/using/flx_size_position_sp.html
@@ -1045,7 +1045,7 @@ other.</p>
<p>In
MXML tags only, setting the <samp class="codeph">height</samp> and <samp
class="codeph">width</samp> properties
-to percentage string values, such as “50%”, also sets the <samp
class="codeph">percentHeight</samp> and <samp
class="codeph">percentWidth</samp> properties.</p>
+to percentage string values, such as "50%", also sets the <samp
class="codeph">percentHeight</samp> and <samp
class="codeph">percentWidth</samp> properties.</p>
</td>
diff --git a/content/doc/flex/using/flx_skinning_sk.html
b/content/doc/flex/using/flx_skinning_sk.html
index f10e754cd..916067ab4 100644
--- a/content/doc/flex/using/flx_skinning_sk.html
+++ b/content/doc/flex/using/flx_skinning_sk.html
@@ -2894,8 +2894,8 @@ Flash Platform</a>
</em>. For example, all stateful skin properties
contain a sentence in the form shown below for the <samp
class="codeph">TitleWindow.closeButtonSkin</samp> property: </p>
- <p>“You can use the <samp class="codeph">closeButtonSkin</samp> style
to assign
-the skin for the following skin states: disabled, down, over, up.”</p>
+ <p>"You can use the <samp class="codeph">closeButtonSkin</samp> style
to assign
+the skin for the following skin states: disabled, down, over, up."</p>
<p>To function as a stateful skin, the skin must implement the
IStateClient
interface. Because that interface is implemented by the UIComponent
diff --git a/content/doc/flex/using/flx_sparktextcontrols_stc.html
b/content/doc/flex/using/flx_sparktextcontrols_stc.html
index 76cd85345..fb37bf4a3 100644
--- a/content/doc/flex/using/flx_sparktextcontrols_stc.html
+++ b/content/doc/flex/using/flx_sparktextcontrols_stc.html
@@ -1975,7 +1975,7 @@ you can set it to a String, a FlowElement, or an Array of
Strings
and FlowElement objects. </p>
<div class="p">In the following example, the <samp
class="codeph"><span></samp> tag
-is one FlowElement, and the character data “<samp class="codeph">World</samp>”
+is one FlowElement, and the character data "<samp class="codeph">World</samp>"
is treated as if it were wrapped in a <samp
class="codeph"><String></samp> tag:<pre class="codeblock"><s:RichText
fontSize="12" xmlns="library://ns.adobe.com/flex/spark">
<span fontWeight="bold">Hello</span>World
</s:RichText></pre>
@@ -3811,7 +3811,7 @@ elements. If you were creating the text flow with HTML
markup, you
would specify the value of the <samp class="codeph">id</samp> property in the
HTML tag (for example, <samp class="codeph"><span
id="span1"></samp>).</p>
- <p>Another way to “walk the tree” of a TextFlow object is to use
+ <p>Another way to "walk the tree" of a TextFlow object is to use
the methods of the ParagraphElement class. This class helps you
access low-level items such as atoms and words. For example, you
can use the <samp class="codeph">findNextWordBoundary()</samp> and <samp
class="codeph">findPreviousWordBoundary()</samp> methods
@@ -3917,8 +3917,8 @@ as a GIF, JPG, or PNG file. </p>
<p>You specify the location of the image by using the <samp
class="codeph">source</samp> property.
The location can be relative to the deployed location of the application
-(for example, “images/butterfly.gif”) or it can be a full path to
-the image (for example, “http://yourserver.com/images/butterfly.gif”).</p>
+(for example, "images/butterfly.gif") or it can be a full path to
+the image (for example, "http://yourserver.com/images/butterfly.gif";).</p>
<div class="p">The following example loads a simple image from a
local location:<pre class="codeblock"><?xml version="1.0"?>
<!-- sparktextcontrols/SimpleInlineGraphic.mxml -->
@@ -4319,20 +4319,20 @@ example shows:<pre class="codeblock"><?xml
version="1.0"?>
<p>You use the constants defined by the
flashx.textLayout.formats.Float
class to set the value of the <samp class="codeph">float</samp> property. The
-values “left” and “right” indicate that the image should be left-aligned
-or right-aligned within the text. The values of “start” and “end”
+values "left" and "right" indicate that the image should be left-aligned
+or right-aligned within the text. The values of "start" and "end"
are similar, in that they left- and right-align the image, but the meanings
of them depend on the direction of the text (RTL or LTR). For RTL
-text, for example, “end” means the end of the line, which is typically
-the left side and “start” means the start of the line, which is
-typically the right side. The value of “none” means that no text
-should flow around the image. The default value is “none”.</p>
+text, for example, "end" means the end of the line, which is typically
+the left side and "start" means the start of the line, which is
+typically the right side. The value of "none" means that no text
+should flow around the image. The default value is "none".</p>
<div class="p">The <samp class="codeph">clearFloats</samp>
property controls the placement
of the paragraph elements relative to the <samp class="codeph">float</samp>.
For example, if you want to ensure that a second paragraph after
a floating image starts below the image, you might set <samp
class="codeph">clearFloats</samp> on
-the second paragraph to “both” or “left”, as the following example
+the second paragraph to "both" or "left", as the following example
shows:<pre class="codeblock"><?xml version="1.0"?>
<!-- sparktextcontrols/TLFClearFloats.mxml -->
<s:Application
@@ -4376,13 +4376,13 @@ shows:<pre class="codeblock"><?xml version="1.0"?>
<p>You use the constants defined by the <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flashx/textLayout/formats/ClearFloats.html";
target="_blank">flashx.textLayout.formats.ClearFloats</a> class to
set the value of the <samp class="codeph">clearFloats</samp> property. The
-values “left” and “right” indicate that the new paragraph should
+values "left" and "right" indicate that the new paragraph should
be placed after any float that appears on the left or right. As
-with the <samp class="codeph">float</samp> property, the “start” and “end”
+with the <samp class="codeph">float</samp> property, the "start" and "end"
values are dependent on the direction of the text in the paragraph.
-A value of “both” causes text to appear after all floats. A value
-of “none” lets the text appear next to the float. The default value
-is “none”.</p>
+A value of "both" causes text to appear after all floats. A value
+of "none" lets the text appear next to the float. The default value
+is "none".</p>
<p>Note that you can also set the <samp
class="codeph">clearFloats</samp> property
as a style on the TLF-based text controls such as RichEditableText
@@ -5396,10 +5396,10 @@ various marker types and a custom increment:<pre
class="codeblock"><?xml vers
<p>You can further customize the appearance of the markers in your
lists by using the <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flashx/textLayout/formats/ListMarkerFormat.html";
target="_blank">ListMarkerFormat</a> class
-to define “before” and “after” content. This is content that appears
+to define "before" and "after" content. This is content that appears
before and after the content of the marker.</p>
- <div class="p">The following example adds the word “Chapter”
before the marker,
+ <div class="p">The following example adds the word "Chapter"
before the marker,
and a colon after the marker. The marker, or content, is ordered
upper-case Roman numerals.<pre class="codeblock"><?xml version="1.0"?>
<!-- sparktextcontrols/TLFListsBeforeAfter.mxml -->
@@ -5449,7 +5449,7 @@ upper-case Roman numerals.<pre class="codeblock"><?xml
version="1.0"?>
to insert a suffix: a string that appears after the marker, but
before the <samp class="codeph">afterContent</samp>. To insert this string
when providing XML content to the flow, wrap the string in <samp
class="codeph">&quote;</samp> HTML
-entities rather than quotation marks (<samp
class="codeph">“<<em>string</em>>”</samp>).
+entities rather than quotation marks (<samp
class="codeph">"<<em>string</em>>"</samp>).
The previous example inserted an empty string.</p>
</div>
@@ -5466,7 +5466,7 @@ The previous example inserted an empty string.</p>
<p>The Spark TextInput and TextArea controls support a <samp
class="codeph">prompt</samp> property
that lets you specify text that helps users know what to enter.
For example, an input field might include prompt text that says
-“Search”.</p>
+"Search".</p>
<p>Prompt text appears when the text control is first created. Prompt
text disappears when the control gets focus or when the control’s <samp
class="codeph">text</samp> property
diff --git a/content/doc/flex/using/flx_styles_st.html
b/content/doc/flex/using/flx_styles_st.html
index a2c13f91b..619592668 100644
--- a/content/doc/flex/using/flx_styles_st.html
+++ b/content/doc/flex/using/flx_styles_st.html
@@ -352,8 +352,8 @@ instance:</p>
</s:Application></pre>
<p>In an MXML tag, you must use the camel-case version of the style
-property. For example, you must use “<samp class="codeph">fontSize</samp>”
-rather than “<samp class="codeph">font-size</samp>” (the CSS convention) in
+property. For example, you must use "<samp class="codeph">fontSize</samp>"
+rather than "<samp class="codeph">font-size</samp>" (the CSS convention) in
the previous example. For more information on style property names,
see <a
href="flx_styles_st.html#WS2db454920e96a9e51e63e3d11c0bf69084-7e88_verapache">About
selector names</a>.</p>
@@ -1375,7 +1375,7 @@ name, you specify namespaces in your CSS that apply to
types. </p>
to all components in the Spark namespace only. To specify a namespace
in CSS, you declare the namespace with the @namespace directive,
followed by the namespace’s library in quotation marks. The following
-example defines the Spark namespace and uses the “s” as an identifier:<pre
class="codeblock">@namespace s "library://ns.adobe.com/flex/spark";</pre>
+example defines the Spark namespace and uses the "s" as an identifier:<pre
class="codeblock">@namespace s "library://ns.adobe.com/flex/spark";</pre>
</div>
@@ -1453,7 +1453,7 @@ namespace:<pre class="codeblock"><fx:Style>
<div class="p">For custom components, you can define your own
style namespace;
that style namespace must match the component’s namespace. For example,
-components in the myComponents package use the style namespace
“myComponents.*”,
+components in the myComponents package use the style namespace
"myComponents.*",
as the following example shows:<pre class="codeblock"><?xml
version="1.0"?>
<!-- styles/CustomComponentsNamespace.mxml -->
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009";
@@ -1474,8 +1474,8 @@ as the following example shows:<pre
class="codeblock"><?xml version="1.0"?>
</div>
<p>For custom components that are in the top level package, you
-can use an “*” for the namespace. However, you cannot use wildcard
-namespace prefixes, such as “*|” to match any namespace.</p>
+can use an "*" for the namespace. However, you cannot use wildcard
+namespace prefixes, such as "*|" to match any namespace.</p>
<div class="p">You can create your own namespace. This can be
useful if you
want to defines type selectors for custom components. The following
@@ -1646,7 +1646,7 @@ of CSS and the CSS specification:</p>
you specify a Box type selector, Flex applies the styles to all
subclasses of Box, including VBox and HBox. This applies to all
classes in the Flex framework’s class hierarchy below UIComponent.
-In this case, UIComponent is considered a “stop class.”</p>
+In this case, UIComponent is considered a "stop class."</p>
</li>
@@ -1700,7 +1700,7 @@ external style sheet.</p>
<li>
<p>The implementation of the CSS Media Query feature in Flex
-supports only the “screen” type. No other media types are supported.</p>
+supports only the "screen" type. No other media types are supported.</p>
</li>
@@ -2069,8 +2069,8 @@ the style of the most closely-related ancestor. If there
are nested
descendant selectors, the component uses the styles defined by the
selector that most closely matches its line of ancestors. For example,
a Spark Button control within a VGroup within another VGroup matches
-a descendant selector for “s|VGroup s|VGroup s|Button” rather than
-a descendant selector for “s|VGroup s|Button”.</p>
+a descendant selector for "s|VGroup s|VGroup s|Button" rather than
+a descendant selector for "s|VGroup s|Button".</p>
<div class="p">The following example shows four selectors. The
first class selector
applies to all Button instances. The first descendant selector applies
@@ -6015,7 +6015,7 @@ JPEG file.</p>
<p>An alternate theme for the Spark components.
This theme gives a simple, wireframe appearance to an application.
It might be appropriate to use it when developing a prototype or
-“proof of concept” application. This theme is also useful as a starting
+"proof of concept" application. This theme is also useful as a starting
point to write custom skins, particularly if they are not styleable.
This is because the skin classes in the Wireframe theme file are
simpler than their Spark counterparts.</p>
diff --git a/content/doc/flex/using/flx_textcontrols_tc.html
b/content/doc/flex/using/flx_textcontrols_tc.html
index da44372cd..10526b114 100644
--- a/content/doc/flex/using/flx_textcontrols_tc.html
+++ b/content/doc/flex/using/flx_textcontrols_tc.html
@@ -1012,7 +1012,7 @@ that is loading the page.</p>
into.</p>
<p>For example, the following HTML snippet creates the
-link “Go Home” to the Adobe Web site.</p>
+link "Go Home" to the Adobe Web site.</p>
<pre class="codeblock"> <a
href='http://www.adobe.com' target='_blank'>Go Home</a></pre>
@@ -1887,7 +1887,7 @@ of the<a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/
to get a TextRange when a user selects some text, and use <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/controls/textClasses/TextRange.html";
target="_blank">TextRange</a> properties
to get and change the characteristics of the selected text. To use
the example, select a range of text with your mouse. When you release
-the mouse button, the string “This is replacement text. ”, formatted
+the mouse button, the string "This is replacement text. ", formatted
in fuchsia Courier 20-point font replaces the selection and the
text area reports on the original and replacement text.</p>
diff --git a/content/doc/flex/using/flx_tooltips_tt.html
b/content/doc/flex/using/flx_tooltips_tt.html
index 651d1829e..d9de31fcb 100644
--- a/content/doc/flex/using/flx_tooltips_tt.html
+++ b/content/doc/flex/using/flx_tooltips_tt.html
@@ -85,7 +85,7 @@ ToolTip text</a>.</p>
you can add a ToolTip to the RichEditableText component, but not
the RichText control.</p>
- <p>Some components have their own ToolTip-like “data tips.” These
+ <p>Some components have their own ToolTip-like "data tips." These
components include the List control, most chart controls, and DataGrid
control. For more information, see that component’s documentation.</p>
@@ -191,9 +191,9 @@ the value of the child’s <samp
class="codeph">toolTip</samp> property.</p>
</s:Application></pre>
<p>When the mouse pointer is over button b1, the ToolTip displays
-“Button ToolTip”. When the mouse pointer is over button b2 or anywhere
+"Button ToolTip". When the mouse pointer is over button b2 or anywhere
in the VGroup container except over button b1, the ToolTip displays
-“VGroup ToolTip”.</p>
+"VGroup ToolTip".</p>
<p>The <a
href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/containers/TabNavigator.html";
target="_blank">TabNavigator</a> container
uses the ToolTips that are on its children. If you add a ToolTip
@@ -994,7 +994,7 @@ pointer over the Button control:</p>
<p>In this example, if the user enters
<strong>f...@fred.com</strong> in the
TextInput box, and then moves the mouse pointer over the button,
-Flex displays the message “Send e-mail to f...@fred.com” in the
+Flex displays the message "Send e-mail to f...@fred.com" in the
ToolTip box.</p>
<p>Another approach to creating dynamic text for ToolTips is to
@@ -1086,8 +1086,8 @@ container. </p>
the location of the pointer on the error tip. This parameter is
optional. If you specify the value of the <samp
class="codeph">errorTipBorderStyle</samp> parameter
in the <samp class="codeph">createToolTip()</samp> method, Flex styles the
-ToolTip as an error tip. Valid values are <samp
class="codeph">“errorTipRight”</samp>, <samp
class="codeph">“errorTipAbove”</samp>,
-or <samp class="codeph">“errorTipBelow”</samp>, and indicate the location of
+ToolTip as an error tip. Valid values are <samp
class="codeph">"errorTipRight"</samp>, <samp
class="codeph">"errorTipAbove"</samp>,
+or <samp class="codeph">"errorTipBelow"</samp>, and indicate the location of
the error tip relative to the component. If you set the <samp
class="codeph">errorTipBorderStyle</samp> parameter
to <samp class="codeph">null</samp>, then the ToolTip is a normal ToolTip,
not an error tip. </p>
@@ -1607,7 +1607,7 @@ to create a custom validation warning mechanism.</p>
<p>You can trigger an error tip to appear on any control when you
set its <samp class="codeph">errorString</samp> property to anything other
-than an empty String (“”).</p>
+than an empty String ("").</p>
<p>The styles of an error tip are defined in the defaults.css file,
which is in the framework.swc file. It specifies the following default
@@ -1634,7 +1634,7 @@ themes, see <a
href="flx_styles_st.html#WS2db454920e96a9e51e63e3d11c0bf69084-7f8
themes</a>.</p>
<p>You can also set the <samp class="codeph">errorColor</samp>
property of
-any UIComponent. This defines the color of the “halo” around a component
+any UIComponent. This defines the color of the "halo" around a component
that has an error tip. The ErrorSkin class handles the logic that
draws this glow around the target component.</p>
@@ -1899,7 +1899,7 @@ shows:</p>
<li>
<p>Edit the class file to change the appearance of the
ToolTip.
-You do this by editing the “toolTip” case in the <samp
class="codeph">updateDisplayList()</samp> method.
+You do this by editing the "toolTip" case in the <samp
class="codeph">updateDisplayList()</samp> method.
That is the method that draws the ToolTip’s border and sets the
default styles. Most commonly, you change the arguments of the <samp
class="codeph">drawRoundRect()</samp> method to
change the appearance of the ToolTip.</p>
diff --git a/content/doc/flex/using/flx_using_states_us.html
b/content/doc/flex/using/flx_using_states_us.html
index 6df2047a9..47f943804 100644
--- a/content/doc/flex/using/flx_using_states_us.html
+++ b/content/doc/flex/using/flx_using_states_us.html
@@ -59,7 +59,7 @@ view. View states let you easily implement such applications.
</p>
<p>At its simplest, a view state defines a particular view of a
component. For example, a product thumbnail could have two view
-states; a default view state with minimal information, and a “rich”
+states; a default view state with minimal information, and a "rich"
state with links for more information. The following figure shows
two view states for a component:</p>
@@ -449,7 +449,7 @@ view state, as the following example shows:<pre
class="codeblock"><s:Button <
</div>
<p>The value of the <samp class="codeph">label</samp> property
qualified by
-“State2” specifies the value for the property in that view state.
+"State2" specifies the value for the property in that view state.
The unqualified property definition, the one that omits the dot
notation, defines the value of the property for all view states
where you do not explicitly define an override. </p>
diff --git a/content/doc/flex/using/flx_usingas_ua.html
b/content/doc/flex/using/flx_usingas_ua.html
index e32125f7c..34d3151b3 100644
--- a/content/doc/flex/using/flx_usingas_ua.html
+++ b/content/doc/flex/using/flx_usingas_ua.html
@@ -196,8 +196,8 @@ or inside tags, executes with the <samp
class="codeph">this</samp> keyword
referring to an instance of the subclass.</p>
<p>The public properties and methods of the class are accessible
-by ActionScript code in other components, as long as that code “dots
-down” (for example, <samp
class="codeph">myCheckoutAccordion.myAddressForm.firstNameTextInput.text</samp>)
+by ActionScript code in other components, as long as that code "dots
+down" (for example, <samp
class="codeph">myCheckoutAccordion.myAddressForm.firstNameTextInput.text</samp>)
or reaches up using the <samp class="codeph">parentDocument</samp>, <samp
class="codeph">parentApplication</samp>,
or <samp class="codeph">FlexGlobals.topLevelApplication</samp> properties to
specify which component the property or method exists on.</p>
@@ -249,7 +249,7 @@ generates the following event handler method:</p>
}</pre>
<p>When the user clicks the button, this code sets the value of
-the TextArea control’s <samp class="codeph">text</samp> property to the String
<samp class="codeph">“Hello World</samp>.<samp class="codeph">” </samp> In
+the TextArea control’s <samp class="codeph">text</samp> property to the String
<samp class="codeph">"Hello World</samp>.<samp class="codeph">" </samp> In
most cases, you do not need to look at the generated code, but it
is useful to understand what happens when you write an inline event
handler. </p>
@@ -792,7 +792,7 @@ you use the <samp class="codeph">removeChild()</samp> or
<samp class="codeph">re
You can also use the <samp class="codeph">removeAllChildren()</samp> method
to remove all child controls from a container. </p>
- <p>Calling the “remove” methods does not actually delete the
objects
+ <p>Calling the "remove" methods does not actually delete the
objects
from memory. If you do not have any other references to the child,
Flash Player includes the object in garbage collection at some future
point. But if you have a reference to that child, the child is not
@@ -915,7 +915,7 @@ the main application from sub-applications</a>.</p>
<p>If you write ActionScript in a component’s event listener, the
scope is not the component but rather the application. For example,
-the following code changes the label of the Button control to <samp
class="codeph">“Clicked”</samp> once
+the following code changes the label of the Button control to <samp
class="codeph">"Clicked"</samp> once
the Button control is pressed:</p>
<pre class="codeblock"><?xml version="1.0"?>
@@ -1238,8 +1238,8 @@ URLs, such as http://www.macromedia.com or
file:///C|/site_flashteam/foo.gif.</p
<p>Relative URLs, such as ../myscript.as. A relative URL
that
does not start with a slash is resolved relative to the file that
uses it. If the tag <samp class="codeph"><fx:Script
source="../IncludedFile.as"></samp> is
-included in “mysite/myfiles/myapp.mxml,” the system searches for
-“mysite/IncludedFile.as”.</p>
+included in "mysite/myfiles/myapp.mxml," the system searches for
+"mysite/IncludedFile.as".</p>
</li>
diff --git a/content/doc/flex/using/flx_validators_va.html
b/content/doc/flex/using/flx_validators_va.html
index 78a8e532f..1bf39fed3 100644
--- a/content/doc/flex/using/flx_validators_va.html
+++ b/content/doc/flex/using/flx_validators_va.html
@@ -2867,8 +2867,8 @@ that the following information is provided:</p>
digits and the formatting characters that the <samp
class="codeph">allowedFormatChars</samp> property
specifies, including the slash (/), backslash (\), dash (-), and
period (.) characters. By default, the input format of the date
-in a String is “mm/dd/yyyy” where “mm” is the month, “dd” is the
-day, and “yyyy” is the year. You can use the <samp
class="codeph">inputFormat</samp> property
+in a String is "mm/dd/yyyy" where "mm" is the month, "dd" is the
+day, and "yyyy" is the year. You can use the <samp
class="codeph">inputFormat</samp> property
to specify a different format.</p>
<p>You can also specify to validate a date represented by a single
diff --git a/content/doc/flex/using/flx_wrapper_wr.html
b/content/doc/flex/using/flx_wrapper_wr.html
index ae076d48c..d06918518 100644
--- a/content/doc/flex/using/flx_wrapper_wr.html
+++ b/content/doc/flex/using/flx_wrapper_wr.html
@@ -209,7 +209,7 @@ in the SWFObject 2 logic.</p>
SWF file.</p>
<p>To enable Express Install, set this property to
-“playerProductIntsall.swf”. To disable Express Install, set this
+"playerProductIntsall.swf". To disable Express Install, set this
property to an empty string. If you enable Express Install, you
must also deploy this SWF file with your application built with
Flex.</p>
@@ -307,7 +307,7 @@ in the browser’s title bar when the user requests the HTML
page. </p>
<p>Enables deep linking for the embedded SWF
file.</p>
- <p>To enable deep linking, set this property to
“--”. To
+ <p>To enable deep linking, set this property to
"--". To
disable deep linking, remove the token and the <samp
class="codeph"><script></samp> tags
that follow it. </p>
@@ -454,7 +454,7 @@ a number of properties and objects, and then passes them to
the <samp class="cod
in an HTML wrapper:</p>
<div class="p">
- <pre class="codeblock">swfobject.embedSWF("TestProject.swf",
"flashContent","100%", "100%", “10.0.0”, “playerProductInstall.swf”, flashvars,
params, attributes);</pre>
+ <pre class="codeblock">swfobject.embedSWF("TestProject.swf",
"flashContent","100%", "100%", "10.0.0", "playerProductInstall.swf", flashvars,
params, attributes);</pre>
</div>
@@ -560,7 +560,7 @@ Flex.</p>
<td class="cellrowborder" valign="top" width="NaN%"
headers="d939457e613 ">
<p>The minimum version of Flash Player that
is required to run the application built with Flex. The default
-value is “10.0.0”. Set this property to “0” to disable version detection. </p>
+value is "10.0.0". Set this property to "0" to disable version detection. </p>
</td>
@@ -577,7 +577,7 @@ value is “10.0.0”. Set this property to “0” to disable
version detection
<td class="cellrowborder" valign="top" width="NaN%"
headers="d939457e613 ">
<p>Enables Express Install. Set this argument
to the location of the playerProductInstall.swf file. The default
-value is “playerProductInstall.swf”. This SWF file is in the same
+value is "playerProductInstall.swf". This SWF file is in the same
directory as the HTML wrapper. If you deploy it to another location,
change the value of the <samp class="codeph">xiSwfUrlStr</samp> argument to
the new path.</p>
@@ -1153,8 +1153,8 @@ with the wrapper</a>.</p>
<li>
<p>Do not put the contents of the JavaScript file directly in
the HTML page. This causes Internet Explorer to prompt the user
-before enabling Flash Player. If the client has “Disable Script
-Debugging (Internet Explorer)” unchecked in Internet Explorer’s
+before enabling Flash Player. If the client has "Disable Script
+Debugging (Internet Explorer)" unchecked in Internet Explorer’s
advanced settings, the browser still prompts the user to load the
ActiveX plug-in before running it.</p>
![http://yourserver.com/images/butterfly.gif"](http://yourserver.com/images/butterfly.gif"){kind=link}