Update quotes to double straight quotes in spec doc text

spec/src/main/asciidoc/jakarta-stl.adoc

@@ -312,12 +312,12 @@ For each attribute, the following information
 is given: name, dynamic behavior, type, and description.
 
 The _rtexprvalue_ element defined in a TLD is
-covered in this specification with the column titled “Dynamic” that
+covered in this specification with the column titled "Dynamic" that
 captures the dynamic behavior of an attribute. The value can be either
 true or false. A false value in the dynamic column means that only a
 static string value can be specified for the attribute. A true value
 means that a _request-time attribute value_ can be specified. As defined
-in the Jakarta Server Pages specification, a “request-time attribute value” can be either
+in the Jakarta Server Pages specification, a "request-time attribute value" can be either
 a Java expression, an EL expression, or a value set by a
 `<jsp:attribute>`.
 
@@ -364,7 +364,7 @@ significantly reduced. This is why all the Jakarta Standard Tag Library tags exp
 only as Jakarta Server Pages scoped attributes (no scripting variable exposed). These
 exported Jakarta Server Pages scoped attributes are referred to as scoped variables in
 this specification; this helps in preventing too much overloading of the
-term “attribute”.
+term "attribute".
 
 ==== var and scope
 
@@ -540,7 +540,7 @@ if the expected type is a _Number_, the EL will coerce a null value to
 If this rule is applied, it’s because the EL
 could not coerce the null into an appropriate default value. It is
 therefore up to the action to deal with the null value and is documented
-in the “Null & Error Handling” section of the action.
+in the "Null & Error Handling" section of the action.
 
 ** Invalid type – throw an exception
 
@@ -572,8 +572,8 @@ caught exception as the root cause of the _JspException_ it re-throws.
 
 Also, by default, Jakarta Standard Tag Library actions do not catch
 or otherwise handle exceptions that occur during evaluation of their
-body content. If they do, it is documented in their “Null & Error
-Handling” or “Description” section.
+body content. If they do, it is documented in their "Null & Error
+Handling" or "Description" section.
 
 === Configuration Data
 
@@ -615,7 +615,7 @@ transparently manipulates the name of configuration variables so they
 behave as if scopes had their own private name space. Details on the
 name manipulations involved are voluntarily left unspecified and are
 handled transparently by the _Config_ class. This ensures flexibility
-should the “scope name space” issue be addressed in the future by the
+should the "scope name space" issue be addressed in the future by the
 Jakarta Server Pages specification.
 
 When setting configuration data via the
@@ -688,8 +688,8 @@ to display the title of a book.
 
 It is also possible for an attribute to
 contain more than one EL expression, mixed with static text. For
-example, the following would display “Price of productName is
-productPrice” for a list of products.
+example, the following would display "Price of productName is
+productPrice" for a list of products.
 
 ....
 <c:forEach var="product" items="$\{products}">
@@ -749,7 +749,7 @@ the JavaBeans specification, or that represent collections such as
 lists, maps, or arrays.
 
 The EL recognizes the importance of these
-data structures and provides two operators, “.” and “[]”, to make it
+data structures and provides two operators, "." and "[]", to make it
 easy to access the data encapsulated in these objects.
 
 The "." operator can be used as a convenient
@@ -762,7 +762,7 @@ from ${user.address.city},
 thanks for visiting our website!
 ....
 
-The “[]” operator allows for more generalized
+The "[]" operator allows for more generalized
 access, as shown below:
 
 ....
@@ -778,7 +778,7 @@ ${user.preferences["shipping"]}
 
 The operators supported in the EL handle the
 most common data manipulations. The standard relational, arithmetic, and
-logical operators are provided in the EL. A very useful “empty” operator
+logical operators are provided in the EL. A very useful "empty" operator
 is also provided.
 
 The six standard relational operators are
@@ -837,12 +837,12 @@ Jakarta Server Pages are mostly used in presentation.
 Experience suggests that it is important to be able to provide as good a
 presentation as possible, even when simple errors occur in the page. To
 satisfy this requirement, the EL provides default values rather than
-errors when failure to evaluate an expression is deemed “recoverable”.
+errors when failure to evaluate an expression is deemed "recoverable".
 Default values are type-correct values that allow a page to easily
 recover from these error conditions.
 
 In the following example, the expression
-”$\{user.address.city}” evaluates to _null_ rather than throwing a
+"$\{user.address.city}" evaluates to _null_ rather than throwing a
 _NullPointerException_ if there is no address associated with the _user_
 object. This way, a sensible default value can be displayed without
 having to worry about exceptions being thrown by the Jakarta Server Pages page.
@@ -888,7 +888,7 @@ attribute.
 
 The `<c:out>` action also supports the notion
 of default values for cases where the value of an EL expression is null.
-In the example below, the value “unknown” will be displayed if the
+In the example below, the value "unknown" will be displayed if the
 property _city_ is not accessible.
 
 ....
@@ -941,7 +941,7 @@ without requiring the extra `<acme:att1>` tag.
 In the preceding example, the `<c:set>` action
 sets the value of the _att1_ scoped variable to the output of the
 `<acme:foo>` action. `<c:set>` – like all Jakarta Standard Tag Library actions that create scoped
-attributes – creates scoped attributes in “page” scope by default.
+attributes – creates scoped attributes in "page" scope by default.
 
 `<c:set>` may also be used to set the property
 of a JavaBeans object, or add or set a specific element in a
@@ -1029,7 +1029,7 @@ content, then the action trims it and processes it further.
 
 | _escapeXml_ |
 _true_ | _boolean_
-|Deterrmines whether characters <,>,&,’,” in
+|Deterrmines whether characters <,>,&,’," in
 the resulting string should be converted to their corresponding
 character entity codes. Default value is true.
 
@@ -1076,7 +1076,7 @@ character conversions are applied:
 
 |‘ |\&#039;
 
-|‘’ |\&#034;
+|" |\&#034;
 |===
 
 The default value can be specified either via
@@ -1738,7 +1738,7 @@ they should not be used within more than one iteration tag.
 *Deprecated*: Finally,
 _java.lang.String_ objects can be iterated over if the string represents
 a list of comma separated values (e.g.
-“Monday,Tuesday,Wednesday,Thursday,Friday”).footnote:[The proper way to process strings of tokens is via <c:forTokens> or via functions _split_ and _join_.]
+"Monday,Tuesday,Wednesday,Thursday,Friday").footnote:[The proper way to process strings of tokens is via <c:forTokens> or via functions _split_ and _join_.]
 
 Absent from the list of supported types is
 _java.sql.ResultSet_ (which includes _jakarta.sql.RowSet_). The reason
@@ -1933,7 +1933,7 @@ object of the underlying collection.
 
 | _items_ | _true_
 |Any of the supported types described in
-Section “Description” below. |Collection
+Section "Description" below. |Collection
 of items to iterate over.
 
 | _varStatus_ |
@@ -2800,7 +2800,7 @@ action of `<c:import>`, `<c:url>`, `<c:redirect>`.
 
 
 _Syntax 1: Parameter value specified in
-attribute “value”_
+attribute "value"_
 
 ....
 <c:param name="name" value="value"/>
@@ -2929,14 +2929,14 @@ code, along with an optional country codefootnote:[A variant code may also be sp
 
 * Language code +
 The language code is the lower-case
-two-letter code as defined by ISO-639 (e.g. “ca” for Catalan, “zh” for
+two-letter code as defined by ISO-639 (e.g. "ca" for Catalan, "zh" for
 Chinese). The full list of these codes can be found at a number of
 sites, such as: +
 http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt
 
 * Country code +
 The country code is the upper-case two-letter
-code as defined by ISO-3166 (e.g. “IT” for Italy, “CR” for Costa Rica).
+code as defined by ISO-3166 (e.g. "IT" for Italy, "CR" for Costa Rica).
 The full list of these codes can be found at a number of sites, such
 as: +
 http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html.
@@ -2963,8 +2963,8 @@ application. Assuming that French and English are the only languages
 supported by the application, there will be two resource bundles:
 _Registration_fr_ (French language) and _Registration_en_ (English
 language). Depending on the locale associated with the client request,
-the key “greeting” could be mapped to the message “Bonjour” (French) or
-“Hello” (English).
+the key "greeting" could be mapped to the message "Bonjour" (French) or
+"Hello" (English).
 
 ==== <fmt:message>
 
@@ -3195,8 +3195,8 @@ data to take a proper corrective action.
 It is important to note that this algorithm
 gives higher priority to a language match over an exact match that would
 have occurred further down the list of preferred locales. For example,
-if the browser-based locale settings are “en” and “fr_CA”, with resource
-bundles “Messages_en” and “Messages_fr_CA”, the Messages_en bundle will
+if the browser-based locale settings are "en" and "fr_CA", with resource
+bundles "Messages_en" and "Messages_fr_CA", the Messages_en bundle will
 be selected as the resource bundle for the localization context.
 
 The definition of a fallback locale along
@@ -3668,7 +3668,7 @@ processed as if undefined; that is, an error message of the form
 
 * If the i18n localization context that this
 action determines does not have any resource bundle, an error message of
-the form “???<key>???” is produced
+the form "???<key>???" is produced
 
 .*Description*
 
@@ -3731,7 +3731,7 @@ replacement to a containing `<fmt:message>` (see
 
 .*Syntax*
 
-_Syntax 1: value specified via attribute “value”_
+_Syntax 1: value specified via attribute "value"_
 ....
 <fmt:param value="messageParameter"/>
 ....
@@ -4048,7 +4048,7 @@ action may be nested inside a `<fmt:timeZone>` action or supplied with a
 _timeZone_ attribute.
 
 In the following example, the current date
-and time are formatted in the “GMT+1:00” time zone:
+and time are formatted in the "GMT+1:00" time zone:
 
 ....
 <fmt:timeZone value="GMT+1:00">
@@ -4910,7 +4910,7 @@ _type_ is missing or is equal to "date" or "both"); ignored otherwise.
 |Predefined formatting styles for times which
 determines how the time component in the date string is to be parsed.
 Applied only when formatting a time or both a date and time (i.e. if
-_type_ is equal to "time” or "both”); ignored otherwise.
+_type_ is equal to "time" or "both"); ignored otherwise.
 
 |pattern | _true_
 |String |Custom
@@ -5192,7 +5192,7 @@ money between two accounts in one transaction:
 ==== SQL Statement Parameters
 
 The Jakarta Standard Tag Library database actions support
-substituting parameter values for parameter markers (“?”) in SQL
+substituting parameter values for parameter markers ("?") in SQL
 statements (as shown in the previous example). This form of parametric
 replacement is exposed by the _jakarta.servlet.jsp.jstl.sql.SQLExecutionTag_ interface.
 
@@ -5411,7 +5411,7 @@ The SQL query statement may be specified by
 the _sql_ attribute or from the action’s body content.
 
 The query statement may contain parameter
-markers (“?”) identifying JDBC _PreparedStatement_ parameters, whose
+markers ("?") identifying JDBC _PreparedStatement_ parameters, whose
 values must be supplied by nested parameter actions (such as
 <<sql:param>>). The
 `<sql:query>` action implements the _jakarta.servlet.jsp.jstl.sql.SQLExecutionTag_ interface, allowing parameter values
@@ -5443,12 +5443,12 @@ included in the result.
 
 When using _startRow_, it is important to
 note that the order in which rows are returned is not guaranteed between
-RDBMS implementations unless an “order by” clause is specified in the
+RDBMS implementations unless an "order by" clause is specified in the
 query.
 
 _maxRows_ and _startRow_ protect against
 so-called "runaway queries", allow efficient access to the top rows of
-large result sets, and also provide a “poor-man’s way” of paging through
+large result sets, and also provide a "poor-man’s way" of paging through
 a large query result by increasing _startRow_ by _maxRows_ over a
 previous page.
 
@@ -5563,7 +5563,7 @@ The SQL update statement may be specified by
 the _sql_ attribute or from the action’s body content.
 
 The update statement may contain parameter
-markers (“?”) identifying JDBC _PreparedStatement_ parameters, whose
+markers ("?") identifying JDBC _PreparedStatement_ parameters, whose
 values must be supplied by nested parameter actions (such as
 <<sql:param>>). The
 `<sql:update>` action implements the _jakarta.servlet.jsp.jstl.sql.SQLExecutionTag_ interface, allowing the parameter
@@ -5805,14 +5805,14 @@ one can expect from a properly designed _DataSource_ object.
 [[sql:param]]
 === <sql:param>
 
-Sets the values of parameter markers (“?”) in
+Sets the values of parameter markers ("?") in
 a SQL statement. Subtag of _SQLExecutionTag_ actions such as `<sql:query>`
 and `<sql:update>`.
 
 .*Syntax*
 
 _Syntax 1: Parameter value specified in
-attribute “value”_
+attribute "value"_
 ....
 <sql:param value=" _value_ "/>
 ....
@@ -5855,7 +5855,7 @@ the SQL value NULL.
 .*Description*
 
 The `<sql:param>` action substitutes the given
-parameter value for a parameter marker(“?”) in the SQL statement of its
+parameter value for a parameter marker("?") in the SQL statement of its
 enclosing _SQLExecutionTag_ action.
 
 Parameters are substituted in the order
@@ -5874,7 +5874,7 @@ of text type (_CHAR_, _VARCHAR_ or _LONGVARCHAR_).
 
 === <sql:dateParam>
 
-Sets the values of parameter markers (“?”) in
+Sets the values of parameter markers ("?") in
 a SQL statement for values of type _java.util.Date_. Subtag of
 _SQLExecutionTag_ actions, such as `<sql:query>` and `<sql:update>`.
 
@@ -5930,7 +5930,7 @@ appropriate type by calling that type's constructor with a parameter of
 _date.getTime()_, where _date_ is the value of the _value_ attribute.
 
 The `<sql:dateParam>` action substitutes the
-given parameter value for a parameter marker(“?”) in the SQL statement
+given parameter value for a parameter marker("?") in the SQL statement
 of its enclosing _SQLExecutionTag_ action.
 
 Parameters are substituted in the order
@@ -6248,8 +6248,8 @@ using an _EntityResolver_ and _URIResolver_ as necessary
 
 ==== Core Actions
 
-The XML core actions provide “expression
-language support” for XPath. These actions are therefore similar to the
+The XML core actions provide "expression
+language support" for XPath. These actions are therefore similar to the
 EL support actions `<c:out>` and `<c:set>` covered in
 <<General-Purpose Actions: core tag library>>, except that they apply to XPath
 expressions.
@@ -6455,7 +6455,7 @@ _false_ | _String_
 
 | _escapeXml_ |
 _true_ | _boolean_
-|Determines whether characters <,>,&,’,” in
+|Determines whether characters <,>,&,’," in
 the resulting string should be converted to their corresponding
 character entity codes. Default value is true.
 |===
@@ -6489,7 +6489,7 @@ character conversions are applied:
 
 |‘ |\&#039;
 
-|‘’ |\&#034;
+|" |\&#034;
 |===
 
 <<<
@@ -7103,7 +7103,7 @@ of `<x:transform>`.
 .*Syntax*
 
 _Syntax 1: Parameter value specified in
-attribute “value”_
+attribute "value"_
 ....
 <x:param name="name" value="value"/>
 ....
@@ -7159,7 +7159,7 @@ information about which elements, if any, are in violation of its
 specific constraints, along with textual descriptions of the syntactic
 violation.
 
-The Jakarta Standard Tag Library provides TLVs that perform “reusable”
+The Jakarta Standard Tag Library provides TLVs that perform "reusable"
 validation; i.e. generic validation that custom tag-library authors
 might wish to incorporate in their own tag libraries. These tag
 libraries do not necessarily need to be substantial collections of tags;
@@ -7234,7 +7234,7 @@ also be disabled through the use of the _scripting-invalid_
 configuration element (see the JSP specification for details).
 
 Similarly, to restrict a Jakarta Server Pages page to a set of
-permitted tag-libraries (in the example below, the Jakarta Standard Tag Library “EL” tag
+permitted tag-libraries (in the example below, the Jakarta Standard Tag Library "EL" tag
 libraries), a developer could create the following TLD:
 
 ....
@@ -8303,7 +8303,7 @@ descriptor (web.xml) from servlet 2.3 to servlet 2.4.
 * Replace all the JSTL 1.0 EL & RT URIs by the new
 JSTL 1.1 URIs
 
-* Escape all occurrences of “$\{“ in RT actions
+* Escape all occurrences of "$\{" in RT actions
 and template text.
 
 ** See JSP 2.0 specification for details.