Custom Web Publishing with XML and XSLT

Chapter 6
|
Developing FileMaker XSLT stylesheets 57
3. Uses the current setting for the request and output pages default text encoding option for the Web
Publishing Engine. When the Web Publishing Engine is first installed, the initial default text encoding
setting for requests is UTF-8. You can change the Web Publishing Engine’s text encoding settings by
using the Admin Console. See FileMaker
Server Help.
After the Web Publishing Engine determines the encoding, that encoding is used and no further steps are
taken to determine the encoding. For example, if the charset attribute is set in the Content-Type request
header, the Web Publishing Engine does not use the value of the –encoding query parameter.
The text encoding that is specified via any of the methods above must use one of the following encodings:
Notes
1 When the Web Publishing Engine is first installed, the initial default text encoding setting for output
pages is UTF-8. See the next section,
“Specifying an output method and encoding.” For email messages,
the Web Publishing Engine uses an initial default text encoding setting of ISO-8859-1. You can change
these settings by using the Admin Console.
1 You can also set email message encoding by using the fmxslt:send_email(String smtpFields, String body, String
encoding) extension function. See
“Sending email messages from the Web Publishing Engine” on page 65.
Specifying an output method and encoding
You can specify an output method and encoding of output pages by using the method and encoding attributes
of the <xsl:output> element. Both of these attributes are optional.
The method attribute specifies the type of output, which can be “html”, “text”, or “xml”. No other method
types are supported. If you don’t specify a method, the Web Publishing Engine uses the “html” method.
The encoding attribute specifies the encoding of the output pages. You can specify any of the encodings
listed in the table in the previous section. If you don’t specify an encoding, the Web Publishing Engine uses
its default text encoding setting for output pages.
For example:
<xsl:output method="html" encoding="ISO-8859-1"/>
If you don’t use the <xsl:output> element in a stylesheet, the Web Publishing Engine outputs HTML pages
using the current default text encoding setting for output pages.
Encoding Description
US-ASCII The basic ASCII character set that is typically used for plain text English email.
ISO-8859-1 The Latin 1 character set that is typically used for roman character based web pages and email
messages requiring upper ASCII characters.
ISO-8859-15 The Latin 9 character set, which is almost the same as the Latin 1 character set with the addition of
the Euro € symbol.
ISO-2022-JP The ISO Japanese encoding that is typically used for Japanese email messages.
Shift_JIS The Japanese encoding that is typically used for Japanese web pages.
UTF-8 The eight-bit encoding of Unicode. Using UTF-8 for email messages and web pages is growing in
popularity as major browsers and email clients have added support. Because UTF-8 supports the
full range of Unicode characters, it can handle pages for any language.