Links converted to unbreakable ones. Last round I hope ?

diff --git a/include/adding-pre-existing-material.html b/include/adding-pre-existing-material.html
index bda9ea57048698c1351c22d9ff4b8f823a98ca19..48055cf7700126025adb185f665f4d1cf608b90f 100644 (file)
--- a/include/adding-pre-existing-material.html
+++ b/include/adding-pre-existing-material.html
@@ -11,7 +11,7 @@
 </ul>
 <p>
   These methods are all equivalent: they open the <a
-  href="/adding-pre-existing-material/import-dialog/">Add Existing Media</a>
+  href="@@import-dialog">Add Existing Media</a>
   dialog.
 </p>
 <p>
@@ -23,4 +23,3 @@
   The file will be imported and copied
   into your session, and placed at the position where the drag ended.
 </p>
-

diff --git a/include/aux-sends.html b/include/aux-sends.html
index fcfb1e72e80502324f96da3ba0bc42380f721c78..5b425d74d0de2841a18f6a159cb8d818a8cc9952 100644 (file)
--- a/include/aux-sends.html
+++ b/include/aux-sends.html
@@ -1,7 +1,7 @@
 
 <p>
   <dfn>Auxilliary sends</dfn> are simple <a
-  href="/working-with-plugins/processor-box/">processors</a> in a bus or
+  href="@@processor-box">processors</a> in a bus or
   track channel strip. They tap the signal at a specific point in the signal
   flow (pre-fader, post-fader, before or after EQs and other plugins, etc.)
   and send a copy of that signal to a bus, without affecting the
@@ -108,4 +108,3 @@
   panner, or to follow it. The latter could be useful for Reverb effects, or
   for in-ear monitor mixes delivered in stereo.
 </p>
-

diff --git a/include/default-keyboard-bindings.html b/include/default-keyboard-bindings.html
index c576039d18ef140eeab0deb6f193f18dda60e021..52d35f433f1f5b45a156f1d5b3c49815c2bc07fb 100644 (file)
--- a/include/default-keyboard-bindings.html
+++ b/include/default-keyboard-bindings.html
@@ -2,7 +2,7 @@
 <p>
   Almost every available function in Ardour can be bound to a keyboard
   shortcut (and those few that cannot will usually respond to an <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/"><abbr
+  href="@@controlling-ardour-with-osc"><abbr
   title="Open Sound Control">OSC</abbr> command</a>). Ardour comes with a
   rich set of default <dfn>key bindings</dfn> for the most commonly used
   functions.
@@ -49,4 +49,3 @@
   class="mod2n"></kbd>, <kbd class="mod3n"></kbd>, etc.) differ among
   platforms, so different default bindings for each are provided.
 </p>
-

diff --git a/include/generic-midi-binding-maps.html b/include/generic-midi-binding-maps.html
index e9117296e64669f2d0400b03f6b06863527d9524..520c9ccd4d8092c0ad0a746765782ab8c97f3cee 100644 (file)
--- a/include/generic-midi-binding-maps.html
+++ b/include/generic-midi-binding-maps.html
@@ -302,7 +302,7 @@ bindings">
 <p>
   You can also bind a sysex or arbitrary message to any of the items
   that occur in Ardour's main menu (and its submenus). The <a
-  href="/appendix/menu-actions-list/">
+  href="@@list-of-menu-actions">
   list of actions</a> shows all available values of <em>action-name</em>.
 <p>
   To create a binding between an arbitrary MIDI message (we'll use a

diff --git a/include/latency-considerations.html b/include/latency-considerations.html
index 9d7b74bf24bb42432f68591a75ab3e98e09766c2..04a93e34d1a2815fbbeef1b300ec5ea12e6ae2cb 100644 (file)
--- a/include/latency-considerations.html
+++ b/include/latency-considerations.html
@@ -4,7 +4,7 @@
   performed with relays and other analog audio switching devices.  Digital
   recorders have the same feature, but may impart some
   <a
-  href="/synchronization/latency-and-latency-compensation/"><dfn>latency</dfn></a>
+  href="@@latency-and-latency-compensation"><dfn>latency</dfn></a>
   (delay) between the time you make a noise and the time that you hear it
   come back from the recorder.
 </p>
@@ -32,4 +32,3 @@
   the digital case you will still have the A-D-A conversion latency of
   1&ndash;2&nbsp;ms.
 </p>
-

diff --git a/include/marker-context-menu.html b/include/marker-context-menu.html
index 6c1a00471b7a91371df4de54653692b65e03b72b..bb260b46e183e96f1bfe6a663408fe21bace87fb 100644 (file)
--- a/include/marker-context-menu.html
+++ b/include/marker-context-menu.html
@@ -16,7 +16,7 @@
   <tr><th>Hide</th>
   <td>Hide this marker from the view. It can be made visible again from the
   <kbd class="menu">Window &gt; Locations</kbd> window or the <a
-  href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges &amp; Marks
+  href="@@the-ranges-and-marks-lists">Ranges &amp; Marks
   list</a>.</td></tr>
   <tr><th>Rename</th>
   <td>Change the name of the marker.</td></tr>
@@ -35,4 +35,3 @@
   and move it to a nearby region boundary, region sync point, or to the
   playhead or mouse.
 </p>
-

diff --git a/include/osc58-controlling-ardour-with-osc.html b/include/osc58-controlling-ardour-with-osc.html
index 1cd7faee2e38592be2a15eaaf2667ef4a2aa034f..f695c0c824ae7832fce9348d79201335073ed470 100644 (file)
--- a/include/osc58-controlling-ardour-with-osc.html
+++ b/include/osc58-controlling-ardour-with-osc.html
@@ -13,7 +13,7 @@
   work with (including bank size) and two new math styles have been added
   to gain controls. If you are using an Ardour version of 4.7 or less,
   please read <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/osc-control-in-ardour-4.7-and-prior/">
+  href="@@osc-control-for-ardour-4.7-and-prior">
   Osc control in ardour 4.7 and prior.</a>
 </p>
 
@@ -46,7 +46,7 @@ here</em>"/&gt;</kbd>
   used to allow talent to adjust their own monitor mix using a tablet
   or phone that can run an OSC controller. For a full explanation of
   how Ardour's feedback works please read <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/feedback-in-osc/">
+  href="@@osc58-feedback">
   OSC feedback In Ardour.</a>
 </p>
 
@@ -74,7 +74,7 @@ here</em>"/&gt;</kbd>
   able to set a port for Ardour to send to. It can also change the
   default setting for set_surface. For more information about Ardour's
   OSC configuration GUI please read <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/osc-setup-dialog/">
+  href="@@osc58-using-the-setup-dialog">
   Ardour's Setup Dialog.</a>
 </p>
 <p>If /set_surface is not sent, the default values are used:
@@ -128,7 +128,7 @@ here</em>"/&gt;</kbd>
   strips.
 </p>
 <p>Please see: <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values/">
+  href="@@osc58-feedback-and-strip-types-values">
   Calculating Feedback and Strip-types Values.</a>
 </p>
 <p class="note">
@@ -140,7 +140,7 @@ here</em>"/&gt;</kbd>
   then adding all those numbers together for a value to send.
 </p>
 <p>Please see: <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values/">
+  href="@@osc58-feedback-and-strip-types-values">
   Calculating Feedback and Strip-types Values.</a></p>
 <p class="note">
        Feedback can also be set with <em>/set_surface/feedback feedback.</em>
@@ -173,7 +173,7 @@ here</em>"/&gt;</kbd>
 <p>
   The control Surface may wish to control the type a frequency of
   updates it receives. It can do this with querying commands. See: <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/querying-ardour-with-osc/">
+  href="@@osc58-querying-ardour">
   Querying Ardour with OSC.</a>
 </p>
 
@@ -181,7 +181,7 @@ here</em>"/&gt;</kbd>
 <p class="note">
        Parameter types show how the value will be used. However, they may
        be sent as a different type if needed, see: <a
-       href="/using-control-surfaces/controlling-ardour-with-osc/parameter-types-in-osc/">
+       href="@@osc58-parameter-types">
        Parameter Types in OSC.</a>
 </p>
 <h3>Master or Global messages</h3>
@@ -386,7 +386,7 @@ here</em>"/&gt;</kbd>
 <p class="note">
   Selected strip operations are complex enough for their own page.
   Please read: <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/selection-considerations-in-osc/">
+  href="@@osc58-selection-and-expansion-considerations">
   Selection Considerations in OSC.</a> This is most important if more
   than one OSC surface is being used with Ardour.
 </p>
@@ -488,7 +488,7 @@ here</em>"/&gt;</kbd>
   are more direct.
 </p>
 <p>
-  The <a href="/appendix/menu-actions-list/"> list of actions</a>
+  The <a href="@@list-of-menu-actions"> list of actions</a>
   shows all available values of <em>action-name</em> for Ardour.
 </p>
 
@@ -532,4 +532,3 @@ Any of these actions that can be moved to session->action calls may reapear.
   <td>Uses edit range as punch range</td></tr>
   <dt><kbd class="osc">/toggle_all_rec_enables</kbd></th>
   <td>(toggles all tracks' recording state)</dd-->
-

diff --git a/include/osc58-feedback.html b/include/osc58-feedback.html
index 8d0092a27c58482e1267ead8cbea2243d6d016a9..0eefcd4de5cb4f7d7925a3e4ebcc2183ab3a741f 100644 (file)
--- a/include/osc58-feedback.html
+++ b/include/osc58-feedback.html
@@ -169,7 +169,7 @@
   below can also be sent as /strip/command/ssid param. Feedback can be
   set to match this with the /set_surface/feedback <em>state</em>
   command. See <a
-  href="/using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values/">
+  href="@@osc58-feedback-and-strip-types-values">
   Calculating Feedback and Strip-types Values.</a>
 </p>
 
@@ -243,4 +243,3 @@
   that OSC does track will show on those OSC controls. Examples of this
   might be track record enable for tracks 1 to 32, play or stop.
 </p>
-

diff --git a/include/signal-routing.html b/include/signal-routing.html
index 4176d02614a146b6cec2f638994a90df61d6a60d..5b7cfb7a2599630edd9ed4943159041cce29e5cb 100644 (file)
--- a/include/signal-routing.html
+++ b/include/signal-routing.html
@@ -4,7 +4,7 @@
   all track and bus inputs and outputs are JACK ports, as are sends and
   inserts, which means they can be tapped into by other JACK clients.
   Only the signal flow inside a track or bus (i.e. from <a
-  href="/working-with-plugins/processor-box/">processor to processor</a>) is
+  href="@@processor-box">processor to processor</a>) is
   handled internally.<br>
   By default, Ardour will create the following connections for you:
 </p>
@@ -40,4 +40,3 @@
   is required. Ardour offers many possibilties for connecting things in the
   way you may need or want them.
 </p>
-

diff --git a/include/the-loop-range.html b/include/the-loop-range.html
index 06b8038acb702c2f2eea0c3ff162cf0750e92502..1f757884ab870c9699ec8d6aa233545b635aa593 100644 (file)
--- a/include/the-loop-range.html
+++ b/include/the-loop-range.html
@@ -5,7 +5,6 @@
 </p>
 <p>
   It can be defined via the timeline or the <a
-  href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges &amp; Marks
+  href="@@the-ranges-and-marks-lists">Ranges &amp; Marks
   list</a>.
 </p>
-

diff --git a/include/the-ranges-and-marks-lists.html b/include/the-ranges-and-marks-lists.html
index 924f74db832375c30c9ba1e55e8bbfbe6b55c078..9d13ab7fbfa34a8f97fa8b48aff079dce70fb14a 100644 (file)
--- a/include/the-ranges-and-marks-lists.html
+++ b/include/the-ranges-and-marks-lists.html
@@ -13,7 +13,7 @@
 
 <p>
   Each section has a set of <dfn>editable <a
-  href="/introducing-ardour/basic-gui-operations/editing-clocks/">clock widgets</a></dfn>
+  href="@@editing-clocks">clock widgets</a></dfn>
   which display the location of a marker, or the start, end, and duration times of a range,
   respectively.
 </p>
@@ -69,4 +69,3 @@
   exported TOC or CUE files. This is relevant for Disk-At-Once recordings
   that may contain audio data between tracks.</td></tr>
 </table>
-

diff --git a/include/track-types.html b/include/track-types.html
index 5d3555a8ec36be4a428cae0cf7b494e007463e6d..eb2c5839654e46dfe935379c07040127319dc95a 100644 (file)
--- a/include/track-types.html
+++ b/include/track-types.html
@@ -105,7 +105,7 @@
   If you have configured Ardour to automatically connect new tracks and
   busses for you, the number of outputs will be determined by the number of
   inputs of the <dfn>master <a
-  href="/introducing-ardour/understanding-basic-concepts-and-terminology/#busses">bus</a></dfn>,
+  href="@@understanding-basic-concepts-and-terminology#busses">bus</a></dfn>,
   to which the track outputs will be connected.<br>
   For example, if you have a two-channel master bus, then a Mono track has one
   input and two outputs; a Stereo track has two inputs and two outputs.