From d2fa4f8292a50b47864d561c33ced39c55c89254 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Thu, 3 Nov 2011 22:36:43 +0000 Subject: Syntax highlight C and Turtle code in documentation. --- ext/persist.lv2/persist.ttl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'ext/persist.lv2/persist.ttl') diff --git a/ext/persist.lv2/persist.ttl b/ext/persist.lv2/persist.ttl index bb70e8e..1c02cc2 100644 --- a/ext/persist.lv2/persist.ttl +++ b/ext/persist.lv2/persist.ttl @@ -82,7 +82,7 @@ possible. Extensions may define a dynamic mechanism for accessing plugin state, or conventional state keys likely to be useful to several implementations.

In pseudo code, a typical use case in a plugin is:

-
+
 #define NS_EG   "http://example.org/"
 #define NS_ATOM "http://lv2plug.in/ns/ext/atom#"
 #define NS_XSD  "http://www.w3.org/2001/XMLSchema#"
@@ -139,7 +139,7 @@ void my_restore(LV2_Handle                    instance,
 

Similarly, a typical use case in a host is:

-
+
 int store_callback(void*       callback_data,
                    uint32_t    key,
                    const void* value,
@@ -193,7 +193,7 @@ wherever the state of a particular plugin instance needs to be represented.
 Note that the domain of this property is unspecified, since LV2 does not define
 any RDF class for plugin instance. This predicate may be used wherever it makes
 sense to do so, e.g.:
-
+
 @prefix eg: <http://example.org/> .
 
 <plugininstance> persist:instanceState [
-- 
cgit v1.2.1