Warning, /frameworks/kdoctools/tests/create-from-current-dir-test/docs/kioslave/data/index.docbook is written in an unsupported language. File is not indexed.
0001 <?xml version="1.0" ?> 0002 <!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.5-Based Variant V1.1//EN" 0003 "dtd/kdedbx45.dtd" [ 0004 <!ENTITY % addindex "IGNORE"> 0005 <!ENTITY % English "INCLUDE" > <!-- change language only here --> 0006 ]> 0007 0008 <article lang="&language;" id="data"> 0009 <title>Data URLs</title> 0010 0011 <articleinfo> 0012 <authorgroup> 0013 <author><personname><firstname>Leo</firstname><surname>Savernik</surname></personname> 0014 <address><email>l.savernik@aon.at</email></address> 0015 </author> 0016 <!-- TRANS:ROLES_OF_TRANSLATORS --> 0017 </authorgroup> 0018 0019 <date>2003-02-06</date> 0020 <!--releaseinfo>2.20.00</releaseinfo--> 0021 0022 </articleinfo> 0023 0024 <para>Data URLs allow small document data to be included in the URL itself. 0025 This is useful for very small HTML testcases or other occasions that do not 0026 justify a document of their own.</para> 0027 0028 <para><userinput>data:,foobar</userinput> 0029 (note the comma after the colon) will deliver a text document that contains 0030 nothing but <literal>foobar</literal> 0031 </para> 0032 0033 <para>The last example delivered a text document. For HTML documents one 0034 has to specify the MIME type <literal>text/html</literal>: 0035 <userinput>data:text/html,<title>Testcase</title><p>This 0036 is a testcase</p></userinput>. This will produce exactly the same 0037 output as if the content had been loaded from a document of its own. 0038 </para> 0039 0040 <para>Specifying alternate character sets is also possible. Note that 8-Bit 0041 characters have to be escaped by a percentage sign and their two-digit 0042 hexadecimal codes: 0043 <userinput>data:;charset=iso-8859-1,Gr%FC%DFe aus Schl%E4gl</userinput> 0044 results in 0045 <literal>Grüße aus Schlägl</literal> 0046 whereas omitting the charset attribute might lead to something like 0047 <literal>Gr??e aus Schl?gl</literal> 0048 </para> 0049 0050 <para><ulink url="http://www.ietf.org/rfc/rfc2397.txt">IETF 0051 RFC2397</ulink> provides more information.</para> 0052 0053 </article> 0054