Add a link to an easier to follow to readme guide, perheps with a "what not to do" disclaimer.
Also add a some scripts to make sure we have all the prerequisites we need and maybe handle downloading

From a discussion on discourse we noticed that the documentation of String.all and String.any are missing an example for the empty String.

any isDigit "" == False
all isDigit "" == True

Motivation

This issue is about Regexp.ja in a wiki.

以下の全角記号は半角記号に置換
/！”＃＄％＆’（）＊＋，−．／：；＜＞？＠［￥］＾＿｀｛｜｝

It recommends replacing Right double quotation mark(U+201D) to Quotation mark(U+0022)

Еще одно достаточно часто встречающееся слово в разработке софта. Раньше мне оно попадалось в значении как каких-то дефолтных данных для работы системы. Но ангуларовская документация использует его в значении близком к "оснастке".

Examples given in the README.MD no longer work and require editing afterwards. As someone who's new to Swift, it makes it difficult to adopt and use the framework. Although I'm grateful for all the hard work you put into this 👍

create Name <-> tags csv
so one day it would be possible to only get nature related names, or only technical names and so on

While this isn't really a huge problem, you may wish to reformat your docstrings according to the established formats.

PEP 287 recommends that reST (reStructuredText) format be used, but Epytext is popular as well - They're used because Python IDEs are often able to parse them to get more information about

Is it possible to leave the space characters out of the <b> tag so the spac

https://github.com/blog/1184-contributing-guidelines

GitHub will show it when someone try to open an issue or create a pull request, which makes contribute to this project more easier.

Should add the info about "How to add a new dictionary for zdict" which had been mentioned at #28 before.

Hi!

First of all, congratulations on this extremely useful library.

I would like to ask you to improve your documentation regarding custom attributes.

I spent some hours trying to do something that I didn't know if was really possible to do with SoapEngine and with some liberal interpretation of some messages exchanges I ended up finding out how to do it, but it would be SOOOO much easier

There has already been some comments and discussion about this such as FooSoft/yomichan#322, but I'll open it as a new issue for better tracking.

I think the project is becoming so large that it would help new developers and our future selves if we documented the core components and their relationships so that it can be referenced while reading the source code and disc

The define app would benefit from documentation beyond the simple --help flag output, especially with some of its configuration.

To keep with typical standards and expectations, the define app/command should likely have an accompanying man page.

You should order masks by efficiency (occurrences/key_space) because this will lead to the less guesses to crack passwords.

Looking at the top 5:
https://github.com/kaonashi-passwords/Kaonashi/blob/5239bd333ed34993b43126a4499606ba70086034/masks/kaonashi_masks_numbered.txt#L1-L5

And ordering just the 1000 in kaonashi_masks_numbered.txt by efficiency the top 5 are now:

673407:?u?u?u?u

The default for zstd appears to be 27 (the --long option). It would be great if this could be exposed via this module. I believe this is the relevant code from zstandard's code repository: https://github.com/facebook/zstd/blob/fbcae274a4752df2c386778808948e88fb89b295/lib/compress/zstd_ldm.c

Thanks for the awesome work!

Functional imports when using multiple collections is fiddly and messy because you end up with loads of imports to manage in every source file, and you have to use aliasing a lot to account for commonalities among function names (e.g. freeze, get, etc.). I've discovered that a good pattern is to create an internal collections script that imports all of the required functions and exports them a