- XML Publishing with AxKit
- Preface
- 1. XML as a Publishing Technology
- 2. Installing AxKit
- 3. Your First XML Web Site
- 4. Points of Style
- Adding Transformation Language Modules
- Defining Style Processors
- Dynamically Choosing Style Transformations
- Style Processor Configuration Cheatsheet
- Rule 1: Style Processors at the Same Lexical Level Are Evaluated in Configuration-File Order
- Rule 2: Conditional Processing Directives Are Evaluated Only Against the Original XML Source
- Rule 3: Style Processors Are Prepended to the Processing Chain as You Descend into the Directory Hierarchy
- Rule 4: Processors in the Named BlocksAre Always Evaluated Last
- 5. Transforming XML Content with XSLT
- 6. Transforming XML Content with XPathScript
- 7. Serving Dynamic XML Content
- 8. Extending AxKit
- AxKit’s Architecture
- Custom Plug-ins
- Custom Providers
- Custom Language Modules
- Custom ConfigReaders
- ConfigReader API
- get_config( )
- StyleMap( )
- CacheDir( )
- ContentProviderClass( )
- StyleProviderClass( )
- DependencyChecks( )
- PreferredStyle( )
- PreferredMedia( )
- CacheModule( )
- DebugLevel( )
- LogDeclines( )
- HandleDirs( )
- IgnoreStylePI( )
- AllowOutputCharset( )
- OutputCharset( )
- ErrorStyles( )
- GzipOutput( )
- DoGzip( )
- GetMatchingProcessors( )
- XSPTaglibs( )
- OutputTransformers( )
- Plugins( )
- ConfigReader API
- Getting More Information
- 9. Integrating AxKit with Other Tools
- A. AxKit Configuration Directive Reference
- AxCacheDir
- AxNoCache
- AxDebugLevel
- AxTraceIntermediate
- AxDebugTidy
- AxStackTrace
- AxLogDeclines
- AxAddPlugin
- AxGzipOutput
- AxTranslateOutput
- AxOutputCharset
- AxExternalEncoding
- AxAddOutputTransformer
- AxResetOutputTransformers
- AxErrorStylesheet
- AxAddXSPTaglib
- AxIgnoreStylePI
- AxHandleDirs
- AxStyle
- AxMedia
- AxAddStyleMap
- AxResetStyleMap
- AxAddProcessor
- AxAddDocTypeProcessor
- AxAddDTDProcessor
- AxAddRootProcessor
- AxAddURIProcessor
- AxResetProcessors
- <AxMediaType>
- <AxStyleName>
- Index
- Colophon
This fixes the output character set, rather than using either UTF-8 or the user’s preference from the Accept-Charset HTTP header. With this option present, all output occurs in the chosen character set. The conversion uses the iconv library, which is part of GNU glibc and/or most modern Unix Systems. Do not use this option if you can avoid it. This option is enabled only if you also enable AxTranslateOutput.
AxOutputCharset iso-8859-1
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.