Ask questionsPackage Generator: Fix and Verify the process to create a new dictionary
The build process must depend upon the type of resulting dictionary.
*.txt.gzfile, then we want to build it each time.
*.trie.gzfile, then we only want to build it by hand because it can take a very long time.
testscript depends upon the type of source, for a hunspell file, we need to use the hunspell reader, for a text file, a standard
headwill work. Example Test Text
Example Test Hunspell
"test": "head -n 100 \"go.txt\" | cspell -v -c ./cspell-ext.json --local=* --languageId=go stdin",
"test": "hunspell-reader words -n 1000 \"French.dic\" | cspell -v -c ./cspell-ext.json --local=fr --languageId=* stdin",
npm run buildwill fail from the package directory if
hunspell-readerare not installed globally.
Answer questions d2s
Yeah, noticed the same problem with missing
cspell-tools when doing some improvements to the companies dictionary https://github.com/streetsidesoftware/cspell-dicts/pull/106 earlier today.
It might be a good early step to add pointer to this issue from the
README.md, together with a mention that
hunspell-reader are required for building packages.