Dictionary Patches for Plover
Dictionary Patches are patch files that allow you to patch JSON dictionaries without editing the original files. This is useful if the base dictionary file is from an external source, such as the default main.json dictionary from Plover.
Format
{
"source": "main.json",
"add": {
"SKWR": "just",
"TKEURBGS": "dictionary"
},
"delete": [
"SHRAOEP/HRES",
"TOED/AS"
]
}
Dictionary patches have the extension dicp. They are written in the JSON format, with three sections:
source: Base JSON file; must be in the same directoryadd: Additions or overwritesdelete: Deleted entries. Note that only outlines are recorded, and they are surrounded in square brackets[]
Usage
When using dictionary patches, you are recommended to disable the base dictionary, since the patch itself will act as a normal dictionary. You can delete and edit entries in Plover's dictionary editor on the patch itself, and the patch file will update accordingly based on the difference between the edited dictionary and the base file.
To update the base file, simply replace the original base file with the updated version with the same file name, and the patch will work as usual.
Converting dictionaries to Patches
If you already have a regular JSON dictionary that contains edits from an original dictionary file, you can create a patch file like this, with a target parameter containing the name of the edited dictionary file.
{
"source": "main.json",
"target": "edited_main.json"
}
The next time you edit the patch, the file will be expanded into its regular additions/deletions format in the example above. You are recommended to keep a backup of the original edited dictionary.
Converting Patches to Dictionaries
If you would like to create a copy of the edited dictionary in JSON format, simply add a generate parameter containing the name of the output file:
{
"generate": "edited_dict.json",
...
}
The edited dictionary will be generated as a JSON dictionary every time you update the patch from within Plover.
Metadata
Release files for plover-dictionary-patch 0.0.4
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 |
|---|---|---|---|---|
| plover-dictionary-patch-0.0.4.tar.gz | 4.4 kB | Without provenance | Details for plover-dictionary-patch-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plover_dictionary_patch-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for plover_dictionary_patch-0.0.4-py3-none-any.whl |
Total release size: 9.6 kB
Release files / plover-dictionary-patch-0.0.4.tar.gz
| Download URL | plover-dictionary-patch-0.0.4.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69a066836960f2c39089be220b321a33462bfe4d0fedde4c81088d40a5fb8387
|
|
BLAKE2b-256 checksum How to use checksums |
824ccaadae3bf59629f83a70c40c5511b3b35e4c12ad0d79153d38df28c00257
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.5.0 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.2
|
Release files / plover_dictionary_patch-0.0.4-py3-none-any.whl
| Download URL | plover_dictionary_patch-0.0.4-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a657e878232d2bdb5ef1a047e6378852041642991224df791779d305ee79dbe9
|
|
BLAKE2b-256 checksum How to use checksums |
baf5032263371e53df54edc70634dc2b9452b9d9308e7e5fa918de90918f5e4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.5.0 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.2
|
Security for plover-dictionary-patch 0.0.4
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.