-
Notifications
You must be signed in to change notification settings - Fork 21
Feat: Create Apple .dictionary #207
Copy link
Copy link
Closed
Labels
1-enhancement1 Type: New feature or an improvement1 Type: New feature or an improvement2-exporter2 Section: Exporting to various formats2 Section: Exporting to various formats3-python3 Language: Pythonic stuff3 Language: Pythonic stuffp2Priority 2: Should havePriority 2: Should havet2Time: a morning or afternoon (1hr-4hr)Time: a morning or afternoon (1hr-4hr)
Milestone
Metadata
Metadata
Assignees
Labels
1-enhancement1 Type: New feature or an improvement1 Type: New feature or an improvement2-exporter2 Section: Exporting to various formats2 Section: Exporting to various formats3-python3 Language: Pythonic stuff3 Language: Pythonic stuffp2Priority 2: Should havePriority 2: Should havet2Time: a morning or afternoon (1hr-4hr)Time: a morning or afternoon (1hr-4hr)
Type
Projects
Status
Done
Problem Statement
Requiring third party software to use a dictionary
Proposed Solution
Automated Mac
.dictionarybuilds in every releaseAlternative Solutions
Manually convert each release. I've done this, but it was suggested to ask for official support.
User Value
Less barrier to entry. Native integration is almost always more user friendly. More usability options means more people will use it.
Implementation Ideas (optional)
Build with GH Actions, add to each monthly release.
Eg: convert one of the existing files (ie
.txt) to the appropriate XML format. Might need to add a minimal.cssfile and a.plisttoo. Use Apples Dictionary Development Kit (part of xcode cli tools) to convert that to.dictionary.Additional Context
Apple's Creating Dictionaries docs
Sadhu!