/usr/share/doc/kde/HTML/en/kioslave/data/index.docbook is in kdelibs5-data 4:4.14.16-0ubuntu3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 | <?xml version="1.0" ?>
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
"dtd/kdex.dtd" [
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
]>
<article lang="&language;" id="data">
<title>Data URLs</title>
<articleinfo>
<authorgroup>
<author><personname><firstname>Leo</firstname><surname>Savernik</surname></personname>
<address><email>l.savernik@aon.at</email></address>
</author>
<!-- TRANS:ROLES_OF_TRANSLATORS -->
</authorgroup>
<date>2003-02-06</date>
<!--releaseinfo>2.20.00</releaseinfo-->
</articleinfo>
<para>Data URLs allow small document data to be included in the URL itself.
This is useful for very small HTML testcases or other occasions that do not
justify a document of their own.</para>
<para><userinput>data:,foobar</userinput>
(note the comma after the colon) will deliver a text document that contains
nothing but <literal>foobar</literal>
</para>
<para>The last example delivered a text document. For HTML documents one
has to specify the MIME type <literal>text/html</literal>:
<userinput>data:text/html,<title>Testcase</title><p>This
is a testcase</p></userinput>. This will produce exactly the same
output as if the content had been loaded from a document of its own.
</para>
<para>Specifying alternate character sets is also possible. Note that 8-Bit
characters have to be escaped by a percentage sign and their two-digit
hexadecimal codes:
<userinput>data:;charset=iso-8859-1,Gr%FC%DFe aus Schl%E4gl</userinput>
results in
<literal>Grüße aus Schlägl</literal>
whereas omitting the charset attribute might lead to something like
<literal>Gr??e aus Schl?gl</literal>
</para>
<para><ulink url="http://www.ietf.org/rfc/rfc2397.txt">IETF
RFC2397</ulink> provides more information.</para>
</article>
|