<html><head><link rel=StyleSheet href='api-content.css' TYPE='text/css' MEDIA='screen'><title>.Encodings</title> <script> function navToEntry(entry) { window.location.href='api-' + entry + '.html'; } function navToGroup(group) { var f = parent.frames['toc-container']; if (!f) window.open ('sparse-toc.html#' + group, 'toc_container'); else { if (f.location.href.search('abc') != -1) f.location.href = 'sparse-toc.html#' + group; else f.location.hash = group; } } </script> </head><body bgcolor='white'> <!-- -- HEADS UP! This page was *GENERATED* by APIDOC, -- DO NOT EDIT THIS FILE BY HAND! -- See http://www.mozilla.org/projects/apidoc for information on APIDOC -- The original source file was sablot.xml --> <h1 class='title'>Sablotron Guide and Reference</h1> <center><table class='api-entry' width='100%' cellspacing='0'border='1' cellpadding='10'> <tr><td class='entry-heading'> <table class='entry-heading-table' width='100%' cellpadding='5'cellspacing='0'><tr> <td class='entry-title' valign='center'><font size='+5'>Encodings</font></td> <td class='entry-type' align='center' width='25%'>.Implementation Notes</td> </tr></table> </td></tr> <tr><td class='entry-summary'> <h4 class='entry-subhead'>Summary</h4> Sablotron supports a number of input/output encodings and charsets; either internally or through the iconv library. </td></tr> <tr><td class='entry-description'> <h4 class='entry-subhead'>Description</h4> Sablotron handles encoding conversions with the help of iconv library. As a standard part of glibc, iconv is automatically available on many Unix-based systems (including Linux). It's available for most other platforms where Sablotron runs (Windows, Solaris, MacOS X, FreeBSD, etc). See <code><a href='javascript:navToEntry("%2eDependencies");'>.Dependencies</a></code> for more details on iconv. <P> With iconv installed on your system, you can use any encoding it supports (that is, almost any encoding whatsoever) for both the input and the output documents. <P> If iconv is not available, encodings may still be supported internally by Sablotron. At present, the list is of such encodings is rather short: UTF-8, UTF-16, ASCII, iso-8859-1, iso-8859-2 and windows-1250 on input, UTF-8 only on output. <P> Lastly, a user has the option to implement a custom encoding conversion handler, which will be asked to perform any unsupported conversion. See <code><a href='javascript:navToEntry("%2eHandlers");'>.Handlers</a></code> for details. <P> The default input and output encoding is in all cases UTF-8. </td></tr> <tr><td class='entry-seealso'> <h4 class='entry-subhead'>See Also</h4> <table class='seealso-table'> <tr class='seealso-groups'><td>Groups</td> <td>[ <a href='javascript:navToGroup("GROUP_.Implementation Notes")'>.Implementation Notes</a> ]</td></tr> <tr class='seealso-internals'><td>Entries</td> <td>[ <a href='javascript:navToEntry("%2eDependencies");'>.Dependencies</a> | <a href='javascript:navToEntry("%2eHandlers");'>.Handlers</a> ]</td></tr> </table> </td></tr> </table></center><br> © 2002-2003 Ginger Alliance<BR><i>revision 03-06-30</i><BR> <center>This page was generated by <a href='http://www.mozilla.org/projects/apidoc' target='other_window'><b>APIDOC</b></a></center> </body></html>