You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,12 +36,12 @@ These three special files also nest in sub directories, so it's not just the roo
36
36
### File Syntax
37
37
38
38
All files follow the same basic syntax: `[[key]] value ... [[otherkey]] value`.
39
-
Whitespace is not significant between keys and the first non-whitespace character between a key and a value.
39
+
Whitespace is not significant between keys and the first non-whitespace character of a value.
40
40
You can think of this as building a dictionary of keys and values, where the value is all the text you wrote after the key, including whitespace, but then trimmed at the front and end of any excess whitespace.
41
41
The strings `[[`, `]]`, `{{`, `}}` are reserved and must be escaped in order to use the literal values, e.g. `\{{`.
42
42
You don't escape individual characters of the string, but the string in total.
43
43
The double brackets are used for macro expansion.
44
-
Assuming you have a macro appropriate defined, then `[[key]] {{macroname}}` will replace `{{macroname}}` with whatever the value for that macro key is.
44
+
Assuming you have a macro appropriately defined, then `[[key]] {{macroname}}` will replace `{{macroname}}` with whatever the value for that macro key is.
45
45
46
46
This syntax is used for all files, including the special files `model`, `macros`, and `options`.
47
47
Note that key names are context sensitive, so `Front` is a different key than `front`.
@@ -100,14 +100,19 @@ You can not, and should not define this field in your notes.
100
100
This field is forced upon any model you define and is used to determine if two notes are the same.
101
101
The field holds not just the filename but the relative path from the root directory to its location.
102
102
103
+
Finally, there is a special field `tags`.
104
+
You are allowed to define this field in your model if you choose, but it assumes the same syntax as a `model` files fields.
105
+
That is, space separated words.
106
+
Each word in the value of the key `[[tags]]` will be added as a tag to the note.
107
+
103
108
## After Importing
104
109
105
110
Once you've imported your collection of notes into Anki it is advised that you don't make any changes to the notes inside Anki itself.
106
111
Obviously, the entire point of this plugin is for you to make those changes on the file system, so doing it inside Anki would kind of defeat the purpose.
107
112
108
113
However, every imported card has an `ffsi:owned` tag.
109
114
If you wish to take a given note for yourself yet still use the importer for other notes, then remove this tag.
110
-
The importer can still find the card and note if it remains in the deck, but will never delete notes that it does not claim to own.
115
+
The importer can still find the card and note if it remains in the deck (and thus potentially change it), but it will never delete notes that it does not claim to own.
111
116
There are two other tags that will be of use as well: `ffsi:added` and `ffsi:changed`.
112
117
These tags are set at import-time to brand new notes or notes were either the model or the field data has changed.
113
118
These offer a quick way to preview all of the changes you've made and correct mistakes.
0 commit comments