metadata: start adding quotes
@@ -75,7 +75,7 @@ type= int
status= implemented
usedby/plugin= hosts augeas toml
usedby/api= elektraKeyCmpOrder
-description= relative order in the keyset if non-alphabetical order
+description= "relative order in the keyset if non-alphabetical order
is needed. This metadata is only to preserve order as found in
the file. It is an hint to allow complete reconstruction as it
was before.
@@ -83,29 +83,29 @@ description= relative order in the keyset if non-alphabetical order
implementation-defined ordering.
When some knowledge about desired ordering exists, e.g. when
key sets are merged, the keys should to be reordered to avoid
- this.
-note= this will rarely used within specifications, but is directly
+ this."
+note= "this will rarely used within specifications, but is directly
derived from configuration files.
- I.e. only storage plugins set and get this property.
+ I.e. only storage plugins set and get this property."
[comment]
type= string
status= deprecated
usedby/plugin= keytometa
-description= the users comment about the key (mostly its value)
+description= "the users comment about the key (mostly its value)
the first line is the comment after a key-value (in the same line)
further lines are the lines before a key-value
This metadata is deprecated because it assumes line-based comments
- and cannot preserve formatting within comments.
-note= if used within specifications it refers to the specification, not
- the key. Use `description` to refer to the key.
+ and cannot preserve formatting within comments."
+note="if used within specifications it refers to the specification, not
+ the key. Use `description` to refer to the key."
[comment/#]
status= implemented
usedby/plugin= hosts
type= string
-description= A comment preceding or in-line with a key.
+description= "A comment preceding or in-line with a key.
- #0 is the inline comment (in the same line).
- The comment numbering starts from top (#1) to bottom (#n).
@@ -127,15 +127,15 @@ description= A comment preceding or in-line with a key.
The plugin need to take care that only valid characters are
present in the comment.
- E.g. on line-based comments, no newlines must be present.
-note= if used within specifications it refers to the specification, not
- the key. Use `description` to refer to the key.
+ E.g. on line-based comments, no newlines must be present."
+note="if used within specifications it refers to the specification, not
+ the key. Use `description` to refer to the key."
[comment/#/start]
status= implemented
usedby/plugin= hosts
type= string
-description= Determines the character(s) used to start this comment.
+description= "Determines the character(s) used to start this comment.
This metakey is empty if its an empty line/comment.
@@ -144,7 +144,7 @@ description= Determines the character(s) used to start this comment.
The plugin needs to make sure that every comment is actually
commented out. An error needs to be emitted if there is no
- start symbol that will be recognized as comment.
+ start symbol that will be recognized as comment."
example= ;
[comment/#/space]
@@ -250,7 +250,7 @@ type= "enum
string"
status= implemented
usedby/plugin= range type
-description= defines the type of the value, as specified in CORBA
+description= Defines the type of the value, as specified in CORBA
Unlike check/type, type is also used for code generation and within the APIs
example= any
@@ -817,7 +817,7 @@ description= check if value conforms to mathematical expression
[check/ipaddr]
type= enum
-
+ ""
ipv4
ipv6
status = implemented
