From f207706a7ca2050ae86a468b416f45309cbfc591 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Fri, 16 Oct 2020 12:12:14 +0200 Subject: Fix HTML character entities in documentation Not all of these actually show up in the output, but it's unnecessary to use these in Markdown anyway. --- lv2/presets/presets.meta.ttl | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'lv2/presets/presets.meta.ttl') diff --git a/lv2/presets/presets.meta.ttl b/lv2/presets/presets.meta.ttl index cc6d33a..8ff25c1 100644 --- a/lv2/presets/presets.meta.ttl +++ b/lv2/presets/presets.meta.ttl @@ -78,7 +78,7 @@ bundle containing presets should list them like so: eg:mypreset a pset:Preset ; lv2:appliesTo eg:myplugin ; - rdfs:seeAlso <mypreset.ttl> . + rdfs:seeAlso . """^^lv2:Markdown . @@ -90,7 +90,7 @@ predicates can be used to describe any data associated with the preset. For example: :::turtle - @prefix eg: <http://example.org/> . + @prefix eg: . eg:mypreset a pset:Preset ; @@ -108,10 +108,9 @@ A Preset SHOULD have at least one lv2:appliesTo property. Each Port on a Preset MUST have at least a lv2:symbol property and a pset:value property. Hosts SHOULD save user presets to a bundle in the user-local LV2 directory (for -example `~/.lv2`) with a name like -`<Plugin_Name>_<Preset_Name>.preset.lv2` (for example -`LV2_Amp_At_Eleven.preset.lv2`), where names are transformed to be valid LV2 -symbols for maximum compatibility. +example `~/.lv2`) with a name like `_.preset.lv2` +(for example `LV2_Amp_At_Eleven.preset.lv2`), where names are transformed to be +valid LV2 symbols for maximum compatibility. """^^lv2:Markdown . -- cgit v1.2.1