In order for Dynamo to properly parse documents, the server must know the character encoding of the document before reading it. If your site runs on DAS and uses either JHTML pages or JSPs, the process of determining the encoding is handled by the EncodingTyper component in the Dynamo servlet pipeline. The EncodingTyper can also be used for JHTML pages on a non-DAS server such as BEA WebLogic, because these applications also have access to the Dynamo servlet pipeline.
The EncodingTyper component discerns the encoding of a document according to its directory path, mapping locale-specific directories to the correct encoding. Various components that read in data, such as the page compiler, also use the EncodingTyper to determine the encodings of documents. For more information, see Using the EncodingTyper to Set the Character Encoding.
JSP files on a non-DAS server use the DAF servlet pipeline and do not have access to the Dynamo servlet pipeline; for this reason, they cannot use the EncodingTyper component. For these pages, character encoding is determined by specific tags that you add to the JSP pages. For more information, refer to Setting the Character Encoding in JavaServer Pages.
