Custom Web Publishing Guide
Table Of Contents
- Chapter 1 Introducing Custom Web Publishing
- Chapter 2 Preparing databases for Custom Web Publishing
- Chapter 3 Accessing XML data with the Web Publishing Engine
- Using Custom Web Publishing with XML
- General process for accessing XML data from the Web Publishing Engine
- About the URL syntax for XML data and container objects
- Accessing XML data via the Web Publishing Engine
- Using the fmresultset grammar
- Using other FileMaker XML grammars
- About UTF-8 encoded data
- Using FileMaker query strings to request XML data
- Switching layouts for an XML response
- Understanding how an XML request is processed
- Using server-side and client-side processing of stylesheets
- Troubleshooting XML document access
- Chapter 4 Introduction to Custom Web Publishing with XSLT
- Chapter 5 Developing FileMaker XSLT stylesheets
- Using XSLT stylesheets with the Web Publishing Engine
- About the FileMaker XSLT Extension Function Reference
- About the URL syntax for FileMaker XSLT stylesheets
- About the URL syntax for FileMaker container objects in XSLT solutions
- Using query strings in FileMaker XSLT stylesheets
- Specifying an XML grammar for a FileMaker XSLT stylesheet
- About namespaces and prefixes for FileMaker XSLT stylesheets
- Using statically defined query commands and query parameters
- Setting text encoding for requests
- Specifying an output method and encoding
- About the encoding of XSLT stylesheets
- Processing XSLT requests that do not query FileMaker Server
- Using tokens to pass information between stylesheets
- Using the FileMaker XSLT extension functions and parameters
- About the FileMaker-specific XSLT parameters set by the Web Publishing Engine
- Accessing the query information in a request
- Obtaining client information
- Using the Web Publishing Engine base URI parameter
- Using the authenticated base URI parameter
- Loading additional documents
- Using a database’s layout information in a stylesheet
- Using content buffering
- Using Web Publishing Engine sessions to store information between requests
- Using the session extension functions
- Sending email messages from the Web Publishing Engine
- Using the header functions
- Using the cookie extension functions
- Using the string manipulation extension functions
- Comparing strings using Perl 5 regular expressions
- Checking for values in a field formatted as a checkbox
- Using the date, time, and day extension functions
- Checking the error status of extension functions
- Using logging
- Using server-side processing of scripting languages
- Chapter 6 Testing and monitoring a site
- Appendix A Valid names used in query strings
- About the query commands and parameters
- Using the query commands
- -dbnames (Database names) query command
- -delete (Delete record) query command
- -dup (Duplicate record) query command
- -edit (Edit record) query command
- -find, -findall, or -findany (Find records) query commands
- -layoutnames (Layout names) query command
- -new (New record) query command
- -process (Process XSLT stylesheets)
- -scriptnames (Script names) query command
- -view (View layout information) query command
- Using the query parameters
- -db (Database name) query parameter
- -encoding (Encoding XSLT request) query parameter
- -field (Container field name) query parameter
- fieldname (Non-container field name) query parameter
- fieldname.op (Comparison operator) query parameter
- -grammar (Grammar for XSLT stylesheets) query parameter
- -lay (Layout) query parameter
- -lay.response (Switch layout for response) query parameter
- -lop (Logical operator) query parameter
- -max (Maximum records) query parameter
- -modid (Modification ID) query parameter
- -recid (Record ID) query parameter
- -script (Script) query parameter
- -script.param (Pass parameter to Script) query parameter
- -script.prefind (Script before Find) query parameter
- -script.prefind.param (Pass parameter to Script before Find) query parameter
- -script.presort (Script before Sort) query parameter
- -script.presort.param (Pass parameter to Script before Sort) query parameter
- -skip (Skip records) query parameter
- -sortfield (Sort field) query parameter
- -sortorder (Sort order) query parameter
- -stylehref (Style href) query parameter
- -styletype (Style type) query parameter
- -token.[string] (Pass values between XSLT stylesheets) query parameter
- Appendix B Error codes for Custom Web Publishing
- Appendix C Converting CDML solutions to FileMaker XSLT
- About the process of converting CDML solutions to FileMaker XSLT solutions
- Conversion of CDML action tags, variable tags, and URLs
- Conversion of the -error and -errornum CDML variable tags
- Conversion of obsolete CDML action tags
- Conversion of supported CDML action tags
- Conversion of obsolete CDML variable tags
- Conversion of supported CDML variable tags
- Conversion of CDML boolean parameters to XPath boolean parameters
- Conversion of CDML boolean operators to XPath
- Conversion of CDML intratag parameters to XSLT-CWP
- Manually fixing CDML conversion errors
- Conversion of CDML replacement tags to XSLT-CWP
- Index
Chapter 5
|
Developing FileMaker XSLT stylesheets 57
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 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.