A wiki is needed for AnkiLink due to the increasing complexity.
The tool is becoming powerful, yet we have to keep it simple.
So a simplified tutorial for the majority and a detailed document for those advanced users are required.

AnkiImporter is a name used by many.
To distinguish this tool from others, I'd like to come up with a unique name.
The core feature to come is #11 and for that, the name "AnkiLink" is elected.

Export notes directly from your clipboard.

Package the main functions into a module.

I just imported from the given "ExampleDeck.apkg" and it couldn't work correctly.

After AnkiIn#25 is finished, this would be rather easy.

AnkiLink would first read a config file and load it into the config system.

Translate README for a Chinese version.

When I run the cmd with no params

>AnkiLink.exe test1.md
Warning: Config File config.toml doesn't exist!
Starting...
file: test1.md
Done.
All done.

It create an Deck in my anki. It's default name is "Export".

But when I run the cmd with " --deck targetDeck"

>AnkiLink.exe test1.md  --deck targetDeck
Warning: Config File config.toml doesn't exist!
Starting...
file: test1.md
Done.
All done.

Nothing happened in my anki.

• LaTeX brackets replacing
• Export Deck
• Export Tag
• and so on...

command-line params and config file.

should be added as a requirement.

在我这里, 选项的顺序永远只有一种

比如选择题的选项是:

A 施工现场管理人员
B 作业人员
C 项目专职安全生产管理人员
D 项目负责人

在使用Anki的过程中, 总是以如下顺序给出

A 作业人员
B 项目专职安全生产管理人员
C 项目负责人
D 施工现场管理人员

所有题目都是把选项向前移动一位的顺序.

我本以为随机是每次看到题目时, 选项的排列顺序都不一样. 现在结果有点不在我的预想范围内.

Due to #13 Dynamic NoteType Loading, AnkiLink will no longer be a one-file script.

By #36 , we will still provide a one-file distribution with some note types built-in.

Load from the running directory.

Some note types should be built in.

AnkiIn

MIT License.

What the feature is

The alphabet starts with {{c1::a}} {{c2::b}} {{c1::a}}

=>

one card:

The alphabet starts with [...] b [...]

and another card:

The alphabet starts with a [...] c

The c1 clozes are blocked out together.

Now AnkiLink has already supported import from markdown, and in the long run, will support export to markdown.

However, it is worth thinking that while exporting, the original structure may be disturbed.
The ideal approach is to append an ID for each block just like #11 said. I'd think it over.

Another problem is that some text may be lost after converting the note to Anki and transform it back. It can be avoided by linking each markdown block with an Anki card and only perform updates to the original file.

Additionally, the original markdown text of a card should be somewhere saved.
I'm considering integrating this with the Anki add-on [anki-auto-markdown[(https://github.com/natfarleydev/anki-auto-markdown).

When using -o, if no output filename is provided, use the H1 title as the filename.
If there's no title in the target file, use the source file's name as the output filename.