For now, simplify API and usage

• Zero config, eliminate need for a config
  • Eliminate datasets via config
  • Replace datasets by cataloging current datasets and versions inside cihai's DB
• Allow for minor configuration via YAML to override database and file locations
• SQLite db backend by default
• UNIHAN by default (#3)

Plugin system

Database architecture

https://github.com/cihai/unihan-db vs automap

Look at examples of SQLAlchemy enterprise architecture to find
a pattern that allows maximize flexibility. We want to pick a good,
composeable pattern for our long term expansion, testability and
understanding, and for our downstream users (whether software
libraries or private projects)

Examples:

• https://github.com/openstack/oslo.db
• https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/models.py
• https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py

Related

#131

https://docs.python.org/3/library/doctest.html

Tested documentation examples

install cihai and try the following code, but get this

Traceback (most recent call last):
  File "test_hanyuDict.py", line 6, in <module>
    c.unihan.bootstrap(unihan_options)
NameError: name 'unihan_options' is not defined

code details:

 from cihai.core import Cihai

 c = Cihai()

 if not c.unihan.is_bootstrapped:  # download and install Unihan to db
     c.unihan.bootstrap(unihan_options)

 query = c.unihan.lookup_char('好')
 glyph = query.first()
 print("lookup for 好: %s" % glyph.kDefinition)
 # lookup for 好: good, excellent, fine; well

 query = c.unihan.reverse_char('good')
 print('matches for "good": %s ' % ', '.join([glph.char for glph in query]))
 # matches for "good": 㑘, 㑤, 㓛, 㘬, 㙉, 㚃, 㚒, 㚥, 㛦, 㜴, 㜺, 㝖, 㤛, 㦝, ...

https://endoflife.date/python

Python 3.7 ends on June 27th, 2023

It also has less typing support than 3.8 does. This avoids having to use typing_extensions for TypedDict and Protocol

See also:

• cihai/unihan-etl#306

Hi 👊

This is my first visit to this fine repo, but it seems you have been working hard to keep all dependencies updated so far.

Once you have closed this issue, I'll create separate pull requests for every update as soon as I find one.

That's it for now!

Happy merging! 🤖

https://www.mdbg.net/chinese/dictionary?page=cc-cedict

Is there a way to lookup the radicals or meaningful components that make up a character? For example, 嚴 should breakdown into 口、厂、敢。

Related: Strict mypy #324

See also:

• https://docs.sqlalchemy.org/en/20/changelog/migration_20.html
• https://docs.sqlalchemy.org/en/20/changelog/whatsnew_20.html
• This also has a built-in mypy plugin https://docs.sqlalchemy.org/en/20/orm/extensions/mypy.html

In order to get cihai working easily out of the box, data from UNIHAN must be incorporated in some way:

1. Generating an index for the glyphs via iterating through the Codes by regex: https://github.com/cihai/cihai/blob/0a28ce182c5e34e69dbdab8c0c42bef0bc3b1e0d/tests/test_datasets.py

2. When packages cihai, download cihai and pick out some default fields (like kDictionary) to include with the main set.

3. Make all versions of cihai download the full UNIHAN.zip afterwords and include the data

Stepping stone to 2.0 in #339

https://docs.sqlalchemy.org/en/14/changelog/migration_14.html

Hi,

I wrote some simple scripts to explore variants of Hanzi and the structure of the simplified<->traditional mapping. I was wondering if some of the things I am doing with Alchemy here and the parsing of lists of variant characters would make a useful addition to the API of cihai? What do you think?

https://github.com/frankier/STIFF/blob/master/explore/difficulties.py
https://github.com/frankier/STIFF/blob/master/explore/variants.py
https://github.com/frankier/STIFF/blob/master/explore/utils.py

It may be better to centralize datasets into this project. So https://github.com/cihai/cihaidata-unihan may come into the fold here.

I would like to translate Hanzi (KyuJiTai) to kanji (ShinJiTai).
There is no function that allows for direct conversion like that.