g-ir-doc-tool: Create a GIR file specific for testing doc generation

This will also serve as a reference of the syntax that is currently
supported by g-ir-doc-tool.

1 files changed, 0 insertions, 36 deletions

diff --git a/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Transfer.page b/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Transfer.page
deleted file mode 100644
index 9d55aa1e..00000000
--- a/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Transfer.page
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0"?>
-<page id="GIRepository.Transfer"
-      type="guide"
-      style="enum"
-      xmlns="http://projectmallard.org/1.0/"
-      xmlns:ui="http://projectmallard.org/experimental/ui/">
-  <info>
-    <link type="guide" xref="index"/>
-  </info>
-  <title>GIRepository.Transfer</title>
-  <p>The transfer is the exchange of data between two parts, from the callee to
-the caller. The callee is either a function/method/signal or an
-object/interface where a property is defined. The caller is the side
-accessing a property or calling a function.
-<link xref="GIRepository.Transfer">GIRepository.Transfer</link> specifies who's responsible for freeing the resources after the
-ownership transfer is complete. In case of a containing type such as a list,
-an array or a hash table the container itself is specified differently from
-the items within the container itself. Each container is freed differently,
-check the documentation for the types themselves for information on how to
-free them.</p>
-<table>
-<tr>
-<td><p>Transfer.NOTHING :</p></td>
-<td></td>
-</tr>
-<tr>
-<td><p>Transfer.CONTAINER :</p></td>
-<td></td>
-</tr>
-<tr>
-<td><p>Transfer.EVERYTHING :</p></td>
-<td></td>
-</tr>
-</table>
-
-</page>