Custom Web Publishing Guide

52 Custom Web Publishing Guide
Setting text encoding for requests
The Web Publishing Engine performs the following steps in the order shown until it determines the encoding
of an XSLT request:
1. Checks if the charset attribute is set in the Content-Type request header.
2. Checks if you specified an encoding with the –encoding query parameter. You can specify this parameter
in a URL or as a statically defined query parameter in the
<?xslt-cwp-query?> processing instruction. The
value of the –encoding parameter indicates the encoding used on the rest of the parameters in the request.
The valid values for this parameter are listed in the following table. For example:
http://192.168.123.101/fmi/xsl/template/my_stylesheet.xsl?-db=products-lay=sales&-grammar=fmresultset
&-encoding=Shift_JIS&-findall
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
Administration Console. See the
FileMaker Server Advanced Web Publishing Installation Guide.
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 Administration 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 61.
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.