From 3db046434e3072b7282e6fe942d798d9ada18d91 Mon Sep 17 00:00:00 2001 From: sorata <136738526+brishtibheja@users.noreply.github.com> Date: Sun, 17 Nov 2024 20:06:56 +0530 Subject: [PATCH] Move to all "Note type" (#299) * update errors.md * update text-files.md * update packaged-decks.md * update browsing.md * update preferences.md * missed one notetype * Update src/templates/errors.md --- src/browsing.md | 8 ++++---- src/importing/packaged-decks.md | 12 ++++++------ src/importing/text-files.md | 20 ++++++++++---------- src/preferences.md | 2 +- src/templates/errors.md | 13 +++++++------ 5 files changed, 28 insertions(+), 27 deletions(-) diff --git a/src/browsing.md b/src/browsing.md index 6c12904a..d277ac2b 100644 --- a/src/browsing.md +++ b/src/browsing.md @@ -164,11 +164,11 @@ the behaviours for both modes. | (Avg.) Ease | The card's ease if it is not new. | The average ease for the note's cards that are not new. | | (Avg.) Interval | The card's interval if the card is in review or relearning. | The average interval for the note's cards that are in review or relearning. | | Lapses | How often the card was rated “Again”. | The total lapses for all cards of the note. | -| Note | The same as in Notes mode for the card's note. | The name of the note's notetype. | +| Note | The same as in Notes mode for the card's note. | The name of the note's note type. | | Note Modified | The same as in Notes mode for the card's note. | The last time the note (e.g. the content of a field) was edited. | | Question | The front side of the card in one line. You can also choose a [custom format](templates/styling.md#browser-appearance) in the card type editor instead. | The same as in Cards mode, only for the first card of the note. | | Reviews | How often the card has been reviewed. | The total review count for all cards of the note. | -| Sort Field | The same as in Notes mode for the card's note. | The content of the note's field that is defined as the notetype's sort field. Only this one field can be displayed and sorted by. You can change the sort field by clicking **Fields...** in the editing area. | +| Sort Field | The same as in Notes mode for the card's note. | The content of the note's field that is defined as the note type's sort field. Only this one field can be displayed and sorted by. You can change the sort field by clicking **Fields...** in the editing area. | | Tags | The same as in Notes mode for the card's note. | The note's tags. | ## Editing Area @@ -217,10 +217,10 @@ they can be found in a submenu of the context menu. | Remove Tags | Enter tags and remove them from all selected notes. | | Clear Unused Tags | Remove all tags from the sidebar that are not used by any notes. | | Toggle Mark | If the current note is marked (i.e., has the _Marked_ tag), unmark all selected notes. If the current is not marked, mark all selected notes. | -| Change Note Type | Convert the selected notes from one type to another. For example, imagine you have a _Russian_ notetype and a _Computer_ notetype, and you accidentally added some computer-related text into a _Russian_ note. You can use this option to fix that mistake. The scheduling of cards is not affected. Changing the type of a note requires a one-way sync. | +| Change Note Type | Convert the selected notes from one type to another. For example, imagine you have a _Russian_ note type and a _Computer_ note type, and you accidentally added some computer-related text into a _Russian_ note. You can use this option to fix that mistake. The scheduling of cards is not affected. Changing the type of a note requires a one-way sync. | | Find Duplicates | Open the [Duplicates](#finding-duplicates) dialog. | | Find and Replace | Open the [Find and Replace](#find-and-replace) dialog. | -| Manage Note Types | Open the [Notetypes](editing.md#adding-a-note-type) dialog. | +| Manage Note Types | Open the [Note Types](editing.md#adding-a-note-type) dialog. | | Delete | Delete all selected notes and their cards. It is not possible to remove individual cards, as individual cards are controlled by the [templates](templates/intro.md). | ### Cards diff --git a/src/importing/packaged-decks.md b/src/importing/packaged-decks.md index 0dad34b5..e64d59cf 100644 --- a/src/importing/packaged-decks.md +++ b/src/importing/packaged-decks.md @@ -2,7 +2,7 @@ -Anki packages (.apkg files) enable you to import decks, notes, notetypes, and cards from +Anki packages (.apkg files) enable you to import decks, notes, note types, and cards from other users. They are commonly shared on [AnkiWeb](https://ankiweb.net/shared/decks). ## Scheduling @@ -26,8 +26,8 @@ already in your collection due to a previous import. If the notes in the file are newer than your local copy, the notes will be updated with the contents of the file by default. -This updating process is generally not possible if the notetype is changed (e.g if either -you or the deck author do things like add an extra field to the notetype). +This updating process is generally not possible if the note type is changed (e.g. if either +you or the deck author do things like add an extra field to the note type). You will still be able to import any missing notes from the file, but notes you have imported previously will not be updated if the deck author has made changes. @@ -35,10 +35,10 @@ has made changes. ### Anki 23.10 and Later Anki 23.10 introduced more flexibility: You can choose to unconditionally -update notes and notetypes, always overwriting your modifications, +update notes and note types, always overwriting your modifications, or, on the other hand, never update existing objects. -Also, if both you and the deck author modified the same notetype, you can now decide to +Also, if both you and the deck author modified the same note type, you can now decide to _merge_ the two versions. This will preserve all templates and fields contained in either one, but will require a full sync, and may mark other existing notes as modified. @@ -49,5 +49,5 @@ If a template or field lacks an id, because it has been created with an earlier release, Anki attempts to find an equivalent by comparing names. See this [this add-on](https://ankiweb.net/shared/info/2063785767) for why it is -advantageous to share notetypes with field and template ids, and how to add them to +advantageous to share note types with field and template ids, and how to add them to existing ones. diff --git a/src/importing/text-files.md b/src/importing/text-files.md index afececdf..6f7b5d6d 100644 --- a/src/importing/text-files.md +++ b/src/importing/text-files.md @@ -174,8 +174,8 @@ this behaviour, to either ignore duplicates completely, or import them as new notes instead of updating existing ones. The 'match scope' setting controls how duplicates are identified. When -'notetype' is selected, Anki will identify a duplicate if another note -with the same notetype has the same first field. When set to 'notetype and deck', +'note type' is selected, Anki will identify a duplicate if another note +with the same note type has the same first field. When set to 'note type and deck', a duplicate will only be flagged if the existing note also happens to be in the deck you are importing into. @@ -205,9 +205,9 @@ You must enable the new importing option in the preferences screen to use this o | `html` | `true`, `false` | Determines whether the file is treated as HTML. | | `tags` | List of tags, separated by spaces | Same as [the old syntax](#adding-tags). | | `columns` | List of names, separated by the previously set separator | Determines the number of columns and shows their given names when importing. | -| `notetype` | Notetype name or id | Presets the notetype, if it exists. | +| `notetype` | Note type name or id | Presets the note type, if it exists. | | `deck` | Deck name or id | Presets the deck, if it exists. | -| `notetype column` | `1`, `2`, `3`, ... | Determines which column contains the notetype name or id of each note, see [Notetype Column](#notetype-column). | +| `notetype column` | `1`, `2`, `3`, ... | Determines which column contains the note type name or id of each note, see [Notetype Column](#notetype-column). | | `deck column` | `1`, `2`, `3`, ... | Determines which column contains the deck name or id of each note, see [Deck Column](#deck-column). | | `tags column` | `1`, `2`, `3`, ... | Determines which column contains the tags of each note. | | `guid column` | `1`, `2`, `3`, ... | Determines which column contains the GUID of each note, see [GUID Column](#guid-column). | @@ -216,15 +216,15 @@ Some headers have further implications. ### Notetype Column -Usually, all notes from a file will be mapped to a single notetype, and you may -choose which column should be mapped to which field of that notetype. +Usually, all notes from a file will be mapped to a single note type, and you may +choose which column should be mapped to which field of that note type. -That changes, if there is a column with notetype names or ids. This allows to -import notes with different notetypes, and their fields will be mapped implicitly: +That changes, if there is a column with note type names or ids. This allows to +import notes with different note types, and their fields will be mapped implicitly: The first regular column is used for the first field of any note regardless of -its notetype, the second regular column for the second field, and so on. +its note type, the second regular column for the second field, and so on. A 'regular column' here being a column that does not contain special information -like decks, tags, notetypes or GUIDs. +like decks, tags, note types or GUIDs. ### Deck Column diff --git a/src/preferences.md b/src/preferences.md index d297bda3..848f8ff5 100644 --- a/src/preferences.md +++ b/src/preferences.md @@ -116,7 +116,7 @@ note type (and opens the add window to the last-used note type when you choose Add). This may be more convenient if you always use a single note type for each deck. -The last used deck/notetype is updated when you add a card. If you change the deck +The last used deck/note type is updated when you add a card. If you change the deck and close the add window without adding a card, it won't be saved. ### Browsing diff --git a/src/templates/errors.md b/src/templates/errors.md index f468b8df..2e57a2d3 100644 --- a/src/templates/errors.md +++ b/src/templates/errors.md @@ -2,7 +2,7 @@ -When you save changes to a notetype or export a deck, Anki 2.1.45+ checks +When you save changes to a note type or export a deck, Anki 2.1.45+ checks for some common errors. These errors will cause issues later on when anyone studies the affected cards, so Anki won't let you proceed before you have fixed them. @@ -10,12 +10,12 @@ the affected cards, so Anki won't let you proceed before you have fixed them. Please see [Key Concepts](../getting-started.md#key-concepts) before reading further. -Most of the errors below will require you to modify your notetype/card template. To do so: +Most of the errors below will require you to modify your note type/card template. To do so: - Open the Browse screen, and look at the items on the left. -- Locate the notetype mentioned in error message. You can use the search bar at the top left +- Locate the note type mentioned in error message. You can use the search bar at the top left if necessary. -- Click on the notetype, to show its cards/notes on the right. +- Click on the note type, to show its cards/notes on the right. - Click the Cards... button at the top of the editing area to open the [templates screen](./intro.md#the-templates-screen). ## Specific Issues @@ -138,9 +138,10 @@ a normal notetype, but this was never a use case that was intended to be support If you want to combine cloze deletions with regular cards, you may find an add-on like the Closet add-on provides some alternatives. -### No Cloze Filter on Cloze Notetype +### No Cloze Filter on Cloze Note Type +
-A Cloze notetype's front and back templates should have a [cloze](../editing.md#cloze-deletion) +A Cloze note type's front and back templates should have a [cloze](../editing.md#cloze-deletion) filter. If one is missing, you will need to add it back so that Anki can create cloze cards correctly.