ankidoc
ankidoc is a short python script intended to make writing
anki notes in asciidoc easier.
Synopsis
ankidoc [-h] [ -d | -n | -l ] [-o OUT] [-a ATTR] [-L LV] files
Short introduction
The script can be used to generate a text file for import into anki from notes written in asciidoc.
The asciidoc notes need to be in a specific format in order for the script to
be able to work with them; The idea is that each note -- or at least each of the
notes the user wants to have in one deck -- is assigned a unique ID. It is then
split into two asciidoc files, one with the content of the front side of the
note, and one of the back side. These two files must now be saved as ID.front
and ID.back, ID being the unique note ID that was assigned to the note.
If, for example, two notes, NoteOne and NoteTwo were to be created, four
files would be needed for that:
NoteOne.back
NoteOne.front
NoteTwo.back
NoteTwo.front
Now, the list of .front files desired to be in the final import file can be
passed to ankidoc. The script will then find the corresponding .back files
(which have to be in the same directory), convert all files to HTML and output
a properly formatted anki import file named out. The name and location of the
output file can be adjusted using the -o option.
Anki Import File Format
When importing a file generated with ankidoc into anki, the following points
should be considered
ankidocseparates note fields with a semicolon (;).ankidoccreates all notes with three fields: the previously defined note ID, the front side and the back side. It is recommended to use a note type with three fields in the import, so that the note ID can be used to avoid duplicates and update already present notes instead.
More information
For more information and generally more detailed documentation, please refer to the manual page.
If you want to view the manual page without installing it, clone the repository
and navigate your terminal to it. You can then use the man command on
ankidoc.1 to display the manual page as usual.
Dependencies
Metadata
Release files for ankidoc 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ankidoc-0.2.0.tar.gz | 44.6 kB | Without provenance | Details for ankidoc-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ankidoc-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for ankidoc-0.2.0-py3-none-any.whl |
Total release size: 79.0 kB
Release files / ankidoc-0.2.0.tar.gz
| Download URL | ankidoc-0.2.0.tar.gz |
|---|---|
| Size | 44.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f53a247e3074b8bd1dca648d51698e4c4d4d063b0070aa558ef7d21be5638666
|
|
BLAKE2b-256 checksum How to use checksums |
06d0e166b13d59064fc2a6613571c7a792cd960723bf080945c852849b5694e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / ankidoc-0.2.0-py3-none-any.whl
| Download URL | ankidoc-0.2.0-py3-none-any.whl |
|---|---|
| Size | 34.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53450b7c14210ce0cb2f4e66ccde9d79cdb62191d7bce818e2f74f0a4b4dfdf8
|
|
BLAKE2b-256 checksum How to use checksums |
b8d8447a166a9072820d243b274916c96189333e26a5d2fa0d680a161f933230
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for ankidoc 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.