Sophie: lib64sablotron-devel-1.0.3-7mdv2010.0 x86

lib64sablotron-devel-1.0.3-7mdv2010.0.x86_64.rpm

<html><head><link rel=StyleSheet href='api-content.css' TYPE='text/css' MEDIA='screen'><title>.URIs</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'>URIs</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 can handle two URI schemes natively: 'file' and 'arg'.
</td></tr>
<tr><td class='entry-description'>
<h4 class='entry-subhead'>Description</h4>
Only two URI schemes are built-in: 'file' and 'arg' (see 
<code><a href='javascript:navToEntry("%2eNamed%20buffers");'>.Named buffers</a></code>). Moreover, it is possible to use the function 
<code><a href='javascript:navToEntry("SablotRegHandler");'>SablotRegHandler</a></code> to register an external scheme handler which 
will receive requests in all other schemes. See <code><a href='javascript:navToEntry("%2eHandlers");'>.Handlers</a></code>
and sablot.h and shandler.h files for details.
<P>
Relative URI references are resolved in conformance to RFC 2396. 
The base URI is well defined when the relative reference appears inside 
a XML document; when invoking <code><a href='javascript:navToEntry("sabcmd");'>sabcmd</a></code>, the base URI is taken to 
correspond to the current working directory.
<P>
When specifying filenames, the following rules are in effect:<BR>
* specify the "file:" scheme for any standard files, i.e. refer to 
stdin as file://stdin etc.<BR>
* slashes and backslashes work equally fine, in Windows as well as 
Linux.<BR>
* to include a drive letter under Windows (e.g. C:\doc.xml), it is 
necessary to say file://c:/doc.xml.<BR>
</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("%2eHandlers");'>.Handlers</a> | <a href='javascript:navToEntry("%2eNamed%20buffers");'>.Named buffers</a> | <a href='javascript:navToEntry("SablotRegHandler");'>SablotRegHandler</a> | <a href='javascript:navToEntry("sabcmd");'>sabcmd</a> ]</td></tr>

</table>
</td></tr>
</table></center><br>
&copy; 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>