Merge pull request #150 from Dyalog/pdf-glitches

Fix dangling links etc thrown up by PDF conversion

Author: xpqz

dotnet-interface/docs/aplscript/introduction.md

@@ -8,6 +8,6 @@
 
 `APLScript` files employ Unicode encoding so you need a Unicode font with APL symbols, such as APL385 Unicode, to view them. In order to type Dyalog symbols into an `APLScript` file, you also need the Dyalog Input Method Editor (IME), or other APL compatible keyboard.
 
-If you choose to use the Dyalog IME it can be configured from the Dyalog *Configuration* dialog. You may change the associated `.DIN` file and various other options. See [Unicode Input Tab (Unicode Edition Only)](../../userguide/the-apl-environment/configuration-dialog.md).
+If you choose to use the Dyalog IME it can be configured from the Dyalog *Configuration* dialog. You may change the associated `.DIN` file and various other options. See *Unicode Input Tab (Unicode Edition Only)*.
 
 There are basically three types of APLScript files that may be identified by three different file extensions. APLScript files with the extension `.aspx` and `.asmx` specify .NET classes that represent ASP.NET Web Pages and Web Services respectively. APLScript files with the extension `.apl` may specify .NET classes or may simply represent an APL application in a script format as opposed to a workspace format. Such applications do not necessarily require the Microsoft .NET Framework.

dotnet-interface/docs/writing-web-services/sample-web-service-eg2.md

@@ -10,7 +10,7 @@ The entire file, viewed in `Notepad`, is shown below.
 
 Given this instruction, ASP.NET will locate the `APLServices.Example` Web Service by searching the `bin` sub-directory for assemblies. Therefore, to make this work, we have only to create a .NET assembly in `samples\asp.net\aplservices\bin`. The assembly should contain a .NET Namespace named `APLServices`, which in turn defines a class named `Example`.
 
-The procedure for creating .NET classes and assemblies in Dyalog APL was discussed in [Writing .NET Classes in Dyalog APL](../writing-net-classes/chapter-heading.md). Making a WebService class is done in exactly the same way.
+The procedure for creating .NET classes and assemblies in Dyalog APL was discussed in [Writing .NET Classes in Dyalog APL](../writing-net-classes/introduction.md). Making a WebService class is done in exactly the same way.
 
 Note that the sub-directory `samples\asp.net\aplservices\bin` already contains copies of the dependent Dyalog DLLs that are required to execute the code.
 

dotnet-interface/docs/writing-web-services/web-service-asmx-scripts.md

@@ -1,6 +1,6 @@
 <h1 class="heading"><span class="name">Web Service (.asmx) Scripts</span></h1>
 
-Web Services may be written in a variety of languages, including `APLScript`, the scripting version of Dyalog APL. See [APLScript](../aplscript/chapter-heading.md).
+Web Services may be written in a variety of languages, including `APLScript`, the scripting version of Dyalog APL. See [APLScript](../aplscript/introduction.md).
 
 The first statement in the script file declares the language and the name of the service. For example, the following statement declares a Dyalog APL Web Service named `GolfService`.
 ```xml

interface-guide/docs/grid-object/chapter-heading.md

@@ -1,6 +1,6 @@
 <h1 class="heading"><span class="name">Displaying and Editing Values in Grid Cells</span></h1>
 
-The Grid can display the value in a cell directly (as illustrated by [The components of the Grid object ](chapter-heading.md)) or indirectly via an *associated object*. You do not (as you might first expect) define input and validation characteristics for the cells directly, instead you do so *indirectly* through associated objects. Objects are associated with Grid cells by the Input property. If a cell has an associated object, its value is displayed and edited using that object. Several types of object may be associated with Grid cells, including Edit, Label, Button (Push, Radio and Check), and Combo objects. You can use a single associated object for the entire Grid, or you can associate different objects with individual cells.
+The Grid can display the value in a cell directly (as illustrated by [The Components of the Grid Object](using-the-grid-object.md)) or indirectly via an *associated object*. You do not (as you might first expect) define input and validation characteristics for the cells directly, instead you do so *indirectly* through associated objects. Objects are associated with Grid cells by the Input property. If a cell has an associated object, its value is displayed and edited using that object. Several types of object may be associated with Grid cells, including Edit, Label, Button (Push, Radio and Check), and Combo objects. You can use a single associated object for the entire Grid, or you can associate different objects with individual cells.
 
 Edit and Label objects impose formatting on the cells with which they are associated according to the values of their FieldType and Decimal properties (for numbers, dates and time) and their Justify property (for text). In addition, Label objects protect cells (because a Label has no input mechanism), while Edit objects impose input validation. If you use an Edit object with a FieldType of Numeric, the user may only enter numbers into the corresponding cells of the Grid. For both Edit and Label objects, the FieldType and Decimals properties of the object are used to format the data displayed in the corresponding cells of the Grid. For example, if the FieldType property of the associated object is Date, the numeric elements in Values will be displayed as dates.
 
@@ -12,7 +12,7 @@ Associated Edit, Label and Combo objects may be *external* to the Grid (for exam
 
 ## Using a Floating Edit Field
 
-If the Edit object specified by Input is owned by (that is, is a child of) the Grid itself, the Edit object *floats* from cell to cell as the user moves around the Grid. For example, if the user clicks on the cell addressed by row 4, column 3, the Edit object is automatically moved to that location and the data in that cell is copied into it ready for editing. When the user moves the focus away from this cell, the data in the Edit object is copied back into it (and into the corresponding element of the Values property) before the Edit object is moved away to the new cell location. This mechanism provides *in-situ* editing. Continuing the example illustrated by [The components of the Grid object ](chapter-heading.md), in-situ editing could be achieved as follows:
+If the Edit object specified by Input is owned by (that is, is a child of) the Grid itself, the Edit object *floats* from cell to cell as the user moves around the Grid. For example, if the user clicks on the cell addressed by row 4, column 3, the Edit object is automatically moved to that location and the data in that cell is copied into it ready for editing. When the user moves the focus away from this cell, the data in the Edit object is copied back into it (and into the corresponding element of the Values property) before the Edit object is moved away to the new cell location. This mechanism provides *in-situ* editing. Continuing the example illustrated by [The Components of the Grid Object](using-the-grid-object.md), in-situ editing could be achieved as follows:
 ```apl
       'Test.G.ED' ⎕WC 'Edit' ('FieldType' 'Numeric')
       'Test.G'    ⎕WS 'Input' 'Test.G.ED'
@@ -22,7 +22,7 @@ In-situ editing provides two input modes; Scroll and InCell. In Scroll mode the
 
 ## Using a Fixed Edit Field
 
-A different style of editing may be provided by specifying the name of an external Edit object that you have created. This can be any Edit object you wish to use; it need not even be owned by the same Form as the Grid. In this case, the Edit object remains stationary  (wherever you have positioned it), but as the user moves the focus from cell to cell, the cell contents are copied into it and made available for editing. The current cell is identified by a thick border. When the user shifts the focus, the data is copied out from the Edit object into the corresponding cell before data in the newly selected one is copied in. Continuing the example illustrated by [The components of the Grid object ](chapter-heading.md), external editing could be achieved as follows:
+A different style of editing may be provided by specifying the name of an external Edit object that you have created. This can be any Edit object you wish to use; it need not even be owned by the same Form as the Grid. In this case, the Edit object remains stationary  (wherever you have positioned it), but as the user moves the focus from cell to cell, the cell contents are copied into it and made available for editing. The current cell is identified by a thick border. When the user shifts the focus, the data is copied out from the Edit object into the corresponding cell before data in the newly selected one is copied in. Continuing the example illustrated in [The Components of the Grid Object](using-the-grid-object.md), external editing could be achieved as follows:
 ```apl
       'Test.ED'   ⎕WC 'Edit' ('FieldType' 'Numeric')
       'Test.G'    ⎕WS 'Input' 'Test.ED'

interface-guide/docs/grid-object/displaying-and-editing-values-in-grid.md

@@ -0,0 +1,5 @@
+<h1 class="heading"><span class="name">Using the Grid Object</span></h1>
+
+The Grid object allows you to display information in a series of rows and columns and lets the user input and change the data. The Grid has four main components; a matrix of cells that represents the data, a set of row titles, a set of column titles, and a pair of scroll bars. The following picture illustrates these components. The scroll bars scroll the data cells and either the row or column titles. The row titles remain fixed in place when the data cells scroll horizontally and the column titles stay fixed when the data is scrolled vertically.
+
+![](../img/grid-components.png)

interface-guide/docs/grid-object/using-the-grid-object.md

@@ -106,6 +106,7 @@ nav:
       - Using Tips: hints-and-tips/using-tips.md
       - Hints and Tips Combined: hints-and-tips/hints-and-tips-combined.md
   - Grid Object:
+      - Using the Grid Object: grid-object/using-the-grid-object.md
       - Defining Overall Appearance: grid-object/defining-overall-appearance.md
       - Row and Column Titles: grid-object/row-and-column-titles.md
       - Displaying and Editing Values in Grid Cells: grid-object/displaying-and-editing-values-in-grid.md

interface-guide/mkdocs.yml

@@ -2,7 +2,7 @@
 
 `⎕R` (Replace) and `⎕S` (Search) are system operators which take search pattern(s) as their left arguments and transformation rule(s) as their right arguments; the derived function operates on text data to perform either a **search**, or a search and **replace** operation.
 
-The search patterns may include *Regular Expressions* so that complex searches may be performed. `⎕R` and `⎕S` utilise the open-source regular-expression search engine PCRE, which is built into Dyalog APL and distributed according to the [PCRE licence](../appendices/pcre-license.md) which is published separately.
+The search patterns may include *Regular Expressions* so that complex searches may be performed. `⎕R` and `⎕S` utilise the open-source regular-expression search engine PCRE, which is built into Dyalog APL and distributed according to the [PCRE licence](https://www.pcre.org/original/license.txt).
 
 The transformation rules are applied to the text which matches the search patterns; they may be given as a simple character vector, numeric codes, or  a function.
 

language-reference-guide/docs/system-functions/r.md

@@ -95,6 +95,7 @@ nav:
       - Metafile Object: objects/metafile.md
       - MsgBox Object: objects/msgbox.md
       - NetClient Object: objects/netclient.md
+      - NetControl Object: objects/netcontrol.md
       - NetType Object: objects/nettype.md
       - OCXClass Object: objects/ocxclass.md
       - OLEClient Object: objects/oleclient.md
@@ -1395,3 +1396,45 @@ nav:
       - XRange Property: properties/xrange.md
       - Yield Property: properties/yield.md
       - YRange Property: properties/yrange.md
+  - Examples:
+      - examples/calendar-example-1.md
+      - examples/calendar-example-2.md
+      - examples/calendar-example-3.md
+      - examples/coolbar-example-1.md
+      - examples/coolbar-example-2.md
+      - examples/splitter-example-1.md
+      - examples/splitter-example-2.md
+      - examples/splitter-example-3.md
+      - examples/splitter-example-4.md
+      - examples/splitter-example-5.md
+      - examples/tabcontrol-example-1.md
+      - examples/tabcontrol-example-2.md
+      - examples/tabcontrol-example-3.md
+      - examples/tabcontrol-example-3a.md
+      - examples/tabcontrol-example-4.md
+      - examples/tabcontrol-example-5.md
+      - examples/tabcontrol-example-6.md
+      - examples/tabcontrol-example-7.md
+      - examples/tabcontrol-example-8.md
+      - examples/tabcontrol-example-9.md
+      - examples/tabcontrol-example-10.md
+      - examples/tabcontrol-example-11.md
+      - examples/tabcontrol-example-12.md
+      - examples/tabcontrol-example-13.md
+      - examples/toolbutton-example-1.md
+      - examples/toolcontrol-example-1.md
+      - examples/toolcontrol-example-2.md
+      - examples/toolcontrol-example-3.md
+      - examples/toolcontrol-example-4.md
+  - Miscellaneous:
+      - Class Identifier: miscellaneous/class-identifier-clsid.md
+      - COM Data Types: miscellaneous/com-data-types.md
+      - DISPID: miscellaneous/dispid.md
+      - GUID: miscellaneous/globally-unique-identifier-guid.md
+      - International Day Number: miscellaneous/international-day-number.md
+      - Native Look and Feel: miscellaneous/windows-xp-look-and-feel.md
+      - Port Number: miscellaneous/port-number.md
+      - Stream Sockets: miscellaneous/stream-sockets.md
+      - Twips: miscellaneous/twips.md
+      - UDP: miscellaneous/user-datagram-protocol-udp.md
+  

object-reference/mkdocs.yml

@@ -45,6 +45,4 @@ For example, to define a Class named `Duck` that derives from a `Poly` object, t
 :EndClass
 ```
 
-The Base Constructor for such a Class is the `⎕WC` system function.
-
-For further details see [Dyalog GUI Classes](../oo-and-the-dyalog-gui/guiclasses.md).
+The Base Constructor for such a Class is the `⎕WC` system function.