### ----------------------------------------------------
### -- Rakuast::RakuDoc::Render
### -- Licenses: Artistic-2.0
### -- Authors: Richard Hainsworth
### -- File: resources/compliance-rendering/rakudociem-ipsum.md
### ----------------------------------------------------

# Proving a renderer

	A file with many RakuDoc components and some idea about what is expected.

----

## Table of Contents

<a href="#SYNOPSIS">SYNOPSIS</a>   
<a href="#Purpose">Purpose</a>   
<a href="#Short_table_of_contents">Short table of contents</a>   
<a href="#A_short_index">A short index</a>   
<a href="#This_is_a_first_heading">This is a first heading</a>   
&nbsp;&nbsp;- <a href="#This_is_a_second_level_heading">This is a second level heading</a>   
&nbsp;&nbsp;&nbsp;&nbsp;- <a href="#This_is_third_level_heading">This is third level heading</a>   
<a href="#This_is_a_numbered_heading,_level_1">This is a numbered heading, level 1</a>   
&nbsp;&nbsp;- <a href="#This_is_a_second_level_heading_0">This is a second level heading</a>   
&nbsp;&nbsp;&nbsp;&nbsp;- <a href="#A_third_level">A third level</a>   
&nbsp;&nbsp;&nbsp;&nbsp;- <a href="#Another_third_level">Another third level</a>   
&nbsp;&nbsp;- <a href="#Back_to_second">Back to second</a>   
&nbsp;&nbsp;&nbsp;&nbsp;- <a href="#A_third_level_0">A third level</a>   
&nbsp;&nbsp;&nbsp;&nbsp;- <a href="#Another_third_level_0">Another third level</a>   
<a href="#Lists">Lists</a>   
&nbsp;&nbsp;- <a href="#Taking_a_bullet">Taking a bullet</a>   
<a href="#Blocks_that_are_processed_differently">Blocks that are processed differently</a>   
&nbsp;&nbsp;- <a href="#Unrelenting_hype">Unrelenting hype</a>   
<a href="#Formula_cannot_be_rendered">Fabulous identity</a>   
&nbsp;&nbsp;- <a href="#A_customised_block">A customised block</a>   
<a href="#This_is_an_extraordinary_paragraph">This is an extraordinary paragraph</a>   
<a href="#Some_tables">Some tables</a>   
&nbsp;&nbsp;- <a href="#A_visual_table">A visual table</a>   
&nbsp;&nbsp;- <a href="#A_visual_table_with_a_stupendously_long_caption">A visual table with a stupendously long caption</a>   
&nbsp;&nbsp;- <a href="#A_procedural_table">A procedural table</a>   
<a href="#Adding_index_entries_to_your_text">Adding index entries to your text</a>   
<a href="#Scoping_examples">Scoping examples</a>   
<a href="#Placements">Placements</a>   
&nbsp;&nbsp;- <a href="#Text_placement">Text placement</a>   
&nbsp;&nbsp;- <a href="#RakuDoc_placement">RakuDoc placement</a>   
<a href="#A_ware">A ware</a>   
<a href="#B_ware">B ware</a>   
&nbsp;&nbsp;- <a href="#HTML_placement">HTML placement</a>   
&nbsp;&nbsp;- <a href="#JPEG_image_placement">JPEG image placement</a>   
&nbsp;&nbsp;- <a href="#Png_image_placement">Png image placement</a>   
<a href="#Credits">Credits</a>   
<a href="#LICENSE_0">LICENSE</a>   


<div id="SYNOPSIS"></div>

## SYNOPSIS
<span class="para" id="a615aad"></span>Assuming a new renderer has been developed and installed (eg using *zef*) at **Rakudoc::To::MyRender**, the render this file using a `raku --rakudoc=MyRenderer` terminal command. The renderer will be consistent with the RakuDoc v2 specification if all the blocks are rendered appropriately, and warnings are generated by the statements marked as incorrect below. 



<div id="Purpose"></div>

## Purpose
<span class="para" id="289b7b1"></span>This file is intended to prove a RakuDoc v2 renderer. It can be used in several ways: 



&nbsp;&nbsp;• to generate the AST representation of all the RakuDoc components in the specification  
&nbsp;&nbsp;• to prove a renderer that a new renderer should be able to process this file  
&nbsp;&nbsp;• to visualise how the final output of a RakuDoc source will look after processing  
<span class="para" id="a1f56c2"></span>An attempt has been made to utilise all RakuDoc components, it is not an exhaustive test of all components in all possible combinations. Please suggest additional combinations if they turn out to have unusual effects. 

<span class="para" id="357bb2a"></span>Several *mistakes* have been included where the RakuDoc v2 specification indicates how inconsistent behaviours or unknown components should be handled. 

<span class="para" id="d6a1df2"></span>The the end of the rendering of this source file, a number of warning messages should be included. 


<div id="Short table of contents"></div><div id="Short_table_of_contents"></div>

## Short table of contents
<a href="#SYNOPSIS">SYNOPSIS</a>   
<a href="#Purpose">Purpose</a>   
<a href="#Short_table_of_contents">Short table of contents</a>   
<a href="#A_short_index">A short index</a>   
<a href="#This_is_a_first_heading">This is a first heading</a>   
<a href="#This_is_a_numbered_heading,_level_1">This is a numbered heading, level 1</a>   
<a href="#Lists">Lists</a>   
<a href="#Blocks_that_are_processed_differently">Blocks that are processed differently</a>   
<a href="#Formula_cannot_be_rendered">Fabulous identity</a>   
<a href="#This_is_an_extraordinary_paragraph">This is an extraordinary paragraph</a>   
<a href="#Some_tables">Some tables</a>   
<a href="#Adding_index_entries_to_your_text">Adding index entries to your text</a>   
<a href="#Scoping_examples">Scoping examples</a>   
<a href="#Placements">Placements</a>   
<a href="#A_ware">A ware</a>   
<a href="#B_ware">B ware</a>   
<a href="#Credits">Credits</a>   
<a href="#LICENSE_0">LICENSE</a>   





<div id="A short index"></div><div id="A_short_index"></div>

## A short index
<span style="background-color: antiquewhite; font-weight: 600;">elements to be placed</span>: <a href="#index-entry-elements_to_be_placed">This is third level heading</a>

<span style="background-color: antiquewhite; font-weight: 600;">formatting code</span>: <a href="#index-entry-formatting_code">Adding index entries to your text</a>

<span style="background-color: antiquewhite; font-weight: 600;">index</span>: <a href="#index-entry-index_entry">Adding index entries to your text</a>, <a href="#index-entry-index">Adding index entries to your text</a>, <a href="#index-entry-Index_entries">Adding index entries to your text</a>, <a href="#index-entry-subentries">Adding index entries to your text</a>, <a href="#index-entry-multilevel_subentries">Adding index entries to your text</a>, <a href="#index-entry-first_level">Adding index entries to your text</a>, <a href="#index-entry-two_or_more_separate_entries_in_the_index">Adding index entries to your text</a>, <a href="#index-entry-two_or_more_separate_entries_in_the_index">Adding index entries to your text</a>, <a href="#index-entry-two_or_more_separate_entries_in_the_index">Adding index entries to your text</a>

<span style="background-color: antiquewhite; font-weight: 600;">inline formatting</span>: <a href="#index-entry-formatting_code">Adding index entries to your text</a>






<div id="This is a first heading"></div><div id="This_is_a_first_heading"></div>

## This is a first heading
<span class="para" id="170d167"></span>text 


<div id="This is a second level heading"></div><div id="This_is_a_second_level_heading"></div>

### This is a second level heading
<span class="para" id="170d167"></span>text 


<div id="This is third level heading"></div><div id="This_is_third_level_heading"></div><span style="color: white; background-color: #ff7b25;">developers can attach notes to blocks associated with versions</span><span style="color: white; background-color: #d64161;"> for v2</span>



#### This is third level heading
<span class="para" id="6d48c47"></span>A paragraph to illustrate **Basis type** formatting. 

<span class="para" id="9e4b2c8"></span>A paragraph to illustrate *Important type* formatting. 

<span class="para" id="eb35b7c"></span>A paragraph to illustrate __Unusual type__ formatting. 

<span class="para" id="7f14702"></span>A paragraph to illustrate ~~Strikethrough type~~ formatting. 

<span class="para" id="9897186"></span>A paragraph to illustrate <sup>Superscript type</sup> formatting. (For text output, many terminals do not support superscript/subscript font positions, so consider using a colouration as well.) 

<span class="para" id="3f77594"></span>A paragraph to illustrate <sub>Subscript type</sub> formatting. 

<span class="para" id="325e6b7"></span>A paragraph to illustrate `Code type` formatting. It can contain other markup, eg. `A<> markup`. 

<span class="para" id="94d5440"></span>A paragraph to illustrate Verbatim type formatting. It can contain other RakuDoc, eg. P<defn:Happy> without executing it. 

<span class="para" id="80d1b0c"></span>A paragraph to illustrate some >< formatting (in the source has Z<Zero width> between >< ). 

<span class="para" id="a77e8a7"></span>A paragraph to illustrate ***Keyboard*** formatting. 

<span class="para" id="3e0ea31"></span>A paragraph to illustrate **__Replacement__** formatting. 

<span class="para" id="7a58ef8"></span>A paragraph to illustrate ***__Terminal__*** formatting. 

<span class="para" id="3c4cf2d"></span>A paragraph to illustrate several `G<G undefined type>`, `Q<Q undefined type>`, `W<W undefined type>`, `Y<Y undefined type>` formatting; warnings are expected. 

<span class="para" id="55df88f"></span>Various entities are possible such as « or the same thing using unicode «. Entities can be double unicodes, such as 🇺🇦, which is the Ukrainian flag. 

<span class="para" id="1c04399"></span>In case you have forgotten, here is something aliased at the start: Do not consider this a disquisition of possible combinations. 

<span class="para" id="e83fbc8"></span>This is an example of an Alias where A<DECLARATION> was replaced by the contents of the =alias directive. Aliases are scoped, see below, but cannot be specified before being used in the document. Here is an undeclared forward reference, which was written as A<an undeclared|XXX>. The use of an undeclared alias causes a warning. 

<span class="para" id="e362c54"></span>We can also make an inline <span style="font-weight: 600; font-style: italic">definition</span>. This whole paragraph will be referenced later. 

<span class="para" id="e8fea2b"></span>A developer note <span style="background-color: #feb236;">can be attached</span><span style="color: white; background-color: #ff7b25;"> highly deprecated</span><span style="color: white; background-color: #d64161;">[for v1.2.3 ^.. v2.0.0]</span> to text. A renderer may show the text or only show it for contexts compliant with the version. 

<span class="para" id="3f70975"></span>But a note without meta no versioning here is ignored and a warning generated. 

<span class="para" id="9569ffb"></span>When we want a formula `\sum \frac{1}{n^{2}} = \frac{\pi^{2}}{6}` use F<> markup. 

<span class="para" id="f65ea69"></span>Links can be made internally [say to the first heading](This is a first heading) or externally [say to the raku documentation site](https://docs.raku.org). 

<span class="para" id="bf769a1"></span>A renderer should provide the opportunity to customise text using M<...|..,..;...> markup. The renderer `should not recognise this functionality` and issue a warning. 

<span class="para" id="9de2db6"></span>A note <a id="N<such_as_this_one>" href="#fn_target_N<such_as_this_one>"><sup>[ 1 ]</sup></a> will not itself be rendered inline, but the text will be rendered in a footnote or popup. A marker or number will be rendered to point to the text. 

<span class="para" id="7d18724"></span>Suppose we want to place the definition <span style="font-weight: 600; font-style: italic">Im-a-doppelganger</span>
⦗<span class="para" id="e362c54"></span>We can also make an inline <span style="font-weight: 600; font-style: italic">definition</span>. This whole paragraph will be referenced later. 


⦘ here. And to confound pedants, here is a definition <span style="font-weight: 600; font-style: italic">Happy</span>
⦗<span style="font-weight: 600; font-style: italic">Happy</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">when not blue </span>


⦘ defined using a `=defn` block. 

<span class="para" id="839cb63"></span>Normally extra spaces are removed with paragraphs, but sometimes we truly dot dot dot&nbsp;&nbsp; dash dash dash&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; want them. 

<span class="para" id="b0f6e39"></span>Good text will contain <span id="index-entry-elements_to_be_placed"><span style="color:green; background-color: antiquewhite;">elements to be placed</span></span> in an index. The index has already been placed at the start of the document, although content is generated here. 


<div id="｢heading_This_is_a_numbered_heading,_level_1 UNAVAILABLE｣ This is a numbered heading, level 1"></div><div id="This_is_a_numbered_heading,_level_1"></div>

## 1. This is a numbered heading, level 1
<span class="para" id="170d167"></span>text 


<div id="｢heading_This_is_a_second_level_heading_0 UNAVAILABLE｣ This is a second level heading"></div><div id="This_is_a_second_level_heading_0"></div>

### 1.1. This is a second level heading
<span class="para" id="170d167"></span>text 


<div id="｢heading_A_third_level UNAVAILABLE｣ A third level"></div><div id="A_third_level"></div>

#### 1.1.1. A third level
<span class="para" id="170d167"></span>text 


<div id="｢heading_Another_third_level UNAVAILABLE｣ Another third level"></div><div id="Another_third_level"></div>

#### 1.1.2. Another third level
<span class="para" id="170d167"></span>text 


<div id="｢heading_Back_to_second UNAVAILABLE｣ Back to second"></div><div id="Back_to_second"></div>

### 1.2. Back to second
<span class="para" id="170d167"></span>text 


<div id="｢heading_A_third_level_0 UNAVAILABLE｣ A third level"></div><div id="A_third_level_0"></div>

#### 1.2.1. A third level
<span class="para" id="d834d1b"></span>Although this heading has the same text in the heading, the Table of Contents should provide a unique target for it (this may not be possible in some formats such as MarkDown) 


<div id="｢heading_Another_third_level_0 UNAVAILABLE｣ Another third level"></div><div id="Another_third_level_0"></div>

#### 1.2.2. Another third level
<span class="para" id="170d167"></span>text 

<div id="Lists"></div>

## Lists
<span class="para" id="55bb607"></span>Unnumbered up to four levels of bulleting are required, a renderer can offer more. 



&nbsp;&nbsp;• The start of a unnumbered item list  
&nbsp;&nbsp;• Next item  
&nbsp;&nbsp;&nbsp;&nbsp;▹ now next level  
&nbsp;&nbsp;&nbsp;&nbsp;▹ another at two  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;‣ a third level  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;⁃ fourth level  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;⁃ fourth level  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;∙ level five  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;∙ level six  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;∙ level seven  
&nbsp;&nbsp;• reset to level one  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;‣ jump levels  


<span class="para" id="ad539eb"></span>to put space between lists, probably a `=para` without text is needed. 





1. The start of a numbered item list  

2. Next item  

2.1. now next level  

2.2. another at two  

2.2.1. a third level  

3. reset to level one  

3.0.1. jump levels  



&nbsp;&nbsp;• an unnumbered item  


3.1. but we can resume after a break  




<span style="font-weight: 600; font-style: italic">Definitions</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">can be placed in lists </span>

<span style="font-weight: 600; font-style: italic">Happy</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">when not blue </span>

<span style="font-weight: 600; font-style: italic">Blue</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">when not happy </span>

<span style="font-weight: 600; font-style: italic">Being assertive</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;"><span class="para" id="2e02a7a"></span>Just **shout** why don't you? 

</span>



<span class="para" id="9cbaca5"></span>This is an ordinary paragraph 


<span style="font-weight: 600; font-style: italic">1.&nbsp;Lemma 1</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">do not make trouble </span>

<span style="font-weight: 600; font-style: italic">2.&nbsp;Lemma 2</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">do not shout at people </span>

<span style="font-weight: 600; font-style: italic">3.&nbsp;Lemma 3</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">just phone the SWAT team </span>

<span class="para" id="84e6def"></span>An ordinary paragraph creates the definition list. 


<span style="font-weight: 600; font-style: italic">4.&nbsp;Lemma 4</span>

&nbsp;&nbsp;<span style="background-color: lightgrey;">Claim you are the victim here </span>


<div id="Taking a bullet"></div><div id="Taking_a_bullet"></div>

### Taking a bullet
<span class="para" id="93c18bc"></span>The project originally consisted of five phases, of which two are already complete and two have been abandoned: 



&nbsp;&nbsp;☑ Investigate existing solutions  
&nbsp;&nbsp;☑ Define a minimal initial feature set  
&nbsp;&nbsp;☐ Implement this minimal set of features  
&nbsp;&nbsp;☒ Secure 100 million in venture capital  
&nbsp;&nbsp;☒ Abscond to the Bahamas with the cash  
<span class="para" id="ff4b3ca"></span>The major sources of sustainable energy are: 



&nbsp;&nbsp;🌍 wind  
&nbsp;&nbsp;🌍 hydroelectric  
&nbsp;&nbsp;🌍 solar  
&nbsp;&nbsp;🌍 geothermal  
&nbsp;&nbsp;🌍 fusion  
&nbsp;&nbsp;&nbsp;&nbsp;🤞 (eventually)  


<div id="Blocks that are processed differently"></div><div id="Blocks_that_are_processed_differently"></div>

## Blocks that are processed differently

```
my $x = 2;
# a brilliant program!
```

```
my $x = 3;
# a renderer should observe the basis markup
# and the markup but render R<markup> verbatim
```

```
# indenting causes an implicit code block
my $raku = 'fantastic';
```

```
  --- input --- 
This is a text with basis markup that conserves
all spacing      when trying    to get column
just using       white spaces   naively
better           to             use tables
```

```
  --- output --- 
This is almost the same as input
but may have a different styling
```
> <span class="para" id="72145a8"></span>Occasionally some text that is inset from the margin is required. So enclose it in a nested block. 



<span class="para" id="ccd64b2"></span>The following semantic block was included at the beginning in source, but it is now included here. 


<div id="Unrelenting hype"></div><div id="Unrelenting_hype"></div>

### Unrelenting hype
Richard Hainsworth, aka finanalyst




<div id="Fabulous identity"></div><div id="Formula_cannot_be_rendered"></div>

## Fabulous identity
e^{i\pi}+1=0


<div id="Unknown MyBlock"></div><div id="A_customised_block"></div>

## Unknown MyBlock
```
=begin MyBlock :caption<A customised block> :headlevel(2)

Actually it fails because no customisation has been made.
It
should
be
rendered without spaces      being chewed up.
=end MyBlock
```

<span class="para" id="This_is_an_extraordinary_paragraph"></span><span class="para" id="399bd99"></span>Some silly text which will have its own **extraordinary** ToC entry 



<span class="para" id="b660fd8"></span>You are reminded that: Do not consider this a disquisition of possible combinations. 


<div id="Some tables"></div><div id="Some_tables"></div>

## Some tables


### A visual table<div id="A_visual_table"> </div>
| **Animal** | **Legs** | **Eats** |
| :----:  | :----:  | :----: |
| Zebra  |   4  | Cookies |
 | Human  |   2  |   Pizza |
 | Shark  |   0  |    Fish |



### A visual table with a stupendously long caption<div id="A_visual_table_with_a_stupendously_long_caption"> </div>
| **Animal** | **Legs** | **Eats** |
| :----:  | :----:  | :----: |
| Zebra  |   4  | Cookies |
 | Human  |   2  |   Pizza |
 | Shark  |   0  |    Fish |



### A procedural table<div id="A_procedural_table"> </div>
 | **Date** | &nbsp; | **Samples** | &nbsp; | **Mean** |
| :---: | :---: | :---: | :---: | :---: |
 | &nbsp; | **<span class="para" id="f8c6c9e"></span>*Sample 1*** | **<span class="para" id="75140bc"></span>*Sample 2*** | **<span class="para" id="9037e3c"></span>*Sample 3*** | &nbsp; |
 | 2023-03-08 | 0.4 | 0.1 | 0.3 | 0.26667 |
 | 2023-04-14 | 0.8 | 0.6 | 0.5 | 0.63333 |
 | 2023-06-23 | 0.2 | 0.9 | 0.0 | 0.36667 |
 | **Mean:** | 0.46667 | 0.53333 | 0.26667 | 0.42222 |

<div id="Adding index entries to your text"></div><div id="Adding_index_entries_to_your_text"></div>

## Adding index entries to your text
<span class="para" id="3d8b013"></span>An <span id="index-entry-index_entry"><span style="color:green; background-color: antiquewhite;">index entry</span></span> is an inline <span id="index-entry-formatting_code"><span style="color:green; background-color: antiquewhite;">formatting code</span></span> that is rendered normally (i.e. with no special identifying styling) within the text, but which is also added to the <span id="index-entry-index"><span style="color:green; background-color: antiquewhite;">index</span></span>. <span id="index-entry-Index_entries"><span style="color:green; background-color: antiquewhite;">Index entries</span></span> may be specified with <span id="index-entry-subentries"><span style="color:green; background-color: antiquewhite;">subentries</span></span>, including <span id="index-entry-multilevel_subentries"><span style="color:green; background-color: antiquewhite;">multilevel subentries</span></span>, though a renderer is not required to represent anything more than the <span id="index-entry-first_level"><span style="color:green; background-color: antiquewhite;">first level</span></span>. A single index entry can specify <span id="index-entry-two_or_more_separate_entries_in_the_index"><span style="color:green; background-color: antiquewhite;">two or more separate entries in the index</span></span>, all of which will refer back to the same point in the text. 


<div id="Scoping examples"></div><div id="Scoping_examples"></div>

## Scoping examples
<span class="para" id="6019325"></span>Configuration and aliases are scoped. 

<span class="para" id="d5f5128"></span>Without configuration `embedded B<markup> is rendered` verbatim. 

<span class="para" id="60c295b"></span>With configuration `embedded basis markup` is rendered. 

<span class="para" id="77125d7"></span>How short the season when roses are red. 


<span class="para" id="25ba73a"></span>But configuration directives `only B<apply> inside` a block scope. 

<span class="para" id="fda2c59"></span>Did I mention before that: Do not consider this a disquisition of possible combinations. 

<div id="Placements"></div>

## Placements
<span class="para" id="bef1786"></span>Renderers are required to place text and RakuDoc sources, but may fallback to text messages for other formats. 


<div id="Text placement"></div><div id="Text_placement"></div>

### Text placement
ABSOLUTELY NO WARRANTY IS IMPLIED. NOT EVEN OF ANY KIND. WE HAVE SOLD
YOU THIS SOFTWARE WITH NO HINT OF A SUGGESTION THAT IT IS EITHER USEFUL
OR USABLE. AS FOR GUARANTEES OF CORRECTNESS...DON'T MAKE US LAUGH! AT
SOME TIME IN THE FUTURE WE MIGHT DEIGN TO SELL YOU UPGRADES THAT PURPORT
TO ADDRESS SOME OF THE APPLICATION'S MANY DEFICIENCIES, BUT NO PROMISES
THERE EITHER. WE HAVE MORE LAWYERS ON STAFF THAN YOU HAVE TOTAL
EMPLOYEES, SO DON'T EVEN *THINK* ABOUT SUING US. HAVE A NICE DAY.



<div id="RakuDoc placement"></div><div id="RakuDoc_placement"></div>

### RakuDoc placement

<div id="A ware"></div><div id="A_ware"></div>

## A ware
<span class="para" id="c36d969"></span>Absolutely no warranty is implied. **Not even of any kind**. We have sold you this `software` with no hint of a suggestion that it is either useful or usable. As for guarantees of correctness...don't make us laugh! 


<div id="B ware"></div><div id="B_ware"></div>

## B ware
<span class="para" id="3c2fb22"></span>At __some__ time in the future we might deign to sell you upgrades that purport to address some of the application's many deficiencies, but no promises there either. We have more lawyers on staff than you have total employees, so don't even ***think*** about suing us. 

<span class="para" id="573ec25"></span>Have a nice day. ☺ 




<div id="HTML placement"></div><div id="HTML_placement"></div>

### HTML placement
<html>
<head>
    <meta content-type="text/html; charset=utf-8" />
    <title>Complete disclaimer</title>
</head>
<body>
<h1>A ware</h1>

Absolutely no warranty is implied. <B>Not even of any kind</B>. We have sold
you this <code>software</code> with no hint of a suggestion that it is either useful
or usable. As for guarantees of correctness...don't make us laugh!

<h1>B ware</h1>

At <U>some</U> time in the future we might deign to sell you upgrades that purport
to address some of the application's many deficiencies, but no promises
there either. We have more lawyers on staff than you have total
employees, so don't even <B>think</B> about suing us.

Have a nice day. &#x263A;
</body>
</html>


<div id="JPEG image placement"></div><div id="JPEG_image_placement"></div>

### JPEG image placement
![JPEG image placement](https://github.com/Raku/RakuDoc-GAMMA/raw/main/compliance-files/camelia.jpeg)


<div id="Png image placement"></div><div id="Png_image_placement"></div>

### Png image placement
![Png image placement](https://github.com/Raku/RakuDoc-GAMMA/raw/main/compliance-files/camelia.png)

<span class="para" id="8ec3517"></span>Text finishes after version number 

<div id="Credits"></div>

## Credits
Richard Hainsworth, aka finanalyst




<div id="LICENSE"></div><div id="LICENSE_0"></div>

## LICENSE
Artistic-2.0




<div id="VERSION"></div><div id="VERSION_0"></div>

## VERSION
 <div class="rakudoc-version">v0.2.1</div> 

----

## Footnotes
1<a id=".<fnTarget>" href="#N<such_as_this_one>"> |^| </a>such as this one


----

## Index

<span style="background-color: antiquewhite; font-weight: 600;">elements to be placed</span>: <a href="#index-entry-elements_to_be_placed">This is third level heading</a>

<span style="background-color: antiquewhite; font-weight: 600;">formatting code</span>: <a href="#index-entry-formatting_code">Adding index entries to your text</a>

<span style="background-color: antiquewhite; font-weight: 600;">index</span>: <a href="#index-entry-index_entry">Adding index entries to your text</a>, <a href="#index-entry-index">Adding index entries to your text</a>, <a href="#index-entry-Index_entries">Adding index entries to your text</a>, <a href="#index-entry-subentries">Adding index entries to your text</a>, <a href="#index-entry-multilevel_subentries">Adding index entries to your text</a>, <a href="#index-entry-first_level">Adding index entries to your text</a>, <a href="#index-entry-two_or_more_separate_entries_in_the_index">Adding index entries to your text</a>, <a href="#index-entry-two_or_more_separate_entries_in_the_index">Adding index entries to your text</a>, <a href="#index-entry-two_or_more_separate_entries_in_the_index">Adding index entries to your text</a>

<span style="background-color: antiquewhite; font-weight: 600;">inline formatting</span>: <a href="#index-entry-formatting_code">Adding index entries to your text</a>




----

----

Rendered from docs/samples/rakudociem-ipsum.rakudoc/rakudociem-ipsum at 13:46 UTC on 2024-12-19

Source last modified at 21:59 UTC on 2024-11-25



----

----

## WARNINGS

1: ｢G｣ is not defined, but is reserved for future use in block ｢rakudoc｣ with heading ｢This is third level heading｣.

2: ｢Q｣ is not defined, but is reserved for future use in block ｢rakudoc｣ with heading ｢This is third level heading｣.

3: ｢W｣ is not defined, but is reserved for future use in block ｢rakudoc｣ with heading ｢This is third level heading｣.

4: ｢Y｣ is not defined, but is reserved for future use in block ｢rakudoc｣ with heading ｢This is third level heading｣.

5: Unknown or as yet undeclared alias ｢XXX｣ in block ｢rakudoc｣ with heading ｢This is third level heading｣ over-riden by ｢an undeclared｣

6: Δ<> markup ignored because it has no version/note content ｢Δ<no versioning here>｣ in block ｢rakudoc｣ with heading ｢This is third level heading｣.

7: Markup-M failed: template ｢PayMeMoreApp｣ does not exist. Got ｢M<should not recognise this functionality|PayMeMoreApp; user-id>｣

8: No template exists for custom block ｢MyBlock｣. It has been rendered as unknown in block ｢MyBlock｣ with heading ｢MyBlock｣.



