You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Important: CHANGE THE VERSION NUMBER (Follow this example: 30e0ec7 )
For PCT (e.g., Help > Show version number...) → update version number at corpustools\__init__.py
For documentation (e.g., the copyright year at the buttom of each page) → CorpusTools\docs\source\conf.py and then change copyright year (lines 69-70) and version number (lines 76-79)
pronunciation variants issues (Pronunciation variants #751) cf. we have a separate branch for this: 'pronunciation_variants' [pron.vars. in CSV is an enhancement, not a bug; okay for release]
phono search result should be cumulative (e.g., if the user conducts the same search many times, each search should generate a separate row in the result window.)
ipa2spe issues [solved!]
Enhancement
Additional filters for phonological search (Branch 'phono_search_improvement'). Make sure:
1. For PCT 1.5
corpustools\__init__.py
CorpusTools\docs\source\conf.py
and then change copyright year (lines 69-70) and version number (lines 76-79)Bug fix
Enhancement
Additional filters for phonological search (Branch 'phono_search_improvement'). Make sure:
In creating corpus from a file, the number column should be 'frequency' by default. #784
Syllabified example corpus
Documentation
Write up a new section for bigram selection, and update 'mutual information' and 'transitional probability' to refer to it.
Update screenshots
"Working with transcriptions and feature systems":user generated 'SPE-like' feature system would be better to include 'cons'Phonological search
Mutual informationenvrionment selection optionin-word pairwise MITransitional probabilityLoading in corpora > Saving and exporting a corpus or feature fileadd how to export a corpus with syllable delimiterWrite the release notes
Introduction page (version x.x differs from ... version y.y ... )
decide about command line utility -- add notes in documentation that say "Not actively supported with v. 1.5 and later"
Functional load:
2. Not now
already fixed? or simply leave as 'known issues'?
The text was updated successfully, but these errors were encountered: