The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

sylcount: Syllable Counting and Readability Measurements

An English language syllable counter, plus readability score measure-er. For readability, we support 'Flesch' Reading Ease and 'Flesch-Kincaid' Grade Level ('Kincaid' 'et al'. 1975) <https://stars.library.ucf.edu/cgi/viewcontent.cgi?article=1055&context=istlibrary>, Automated Readability Index ('Senter' and Smith 1967) <https://apps.dtic.mil/sti/citations/AD0667273>, Simple Measure of Gobbledygook (McLaughlin 1969), and 'Coleman-Liau' (Coleman and 'Liau' 1975) <doi:10.1037/h0076540>. The package has been carefully optimized and should be very efficient, both in terms of run time performance and memory consumption. The main methods are 'vectorized' by document, and scores for multiple documents are computed in parallel via 'OpenMP'.

Version: 0.2-6
Depends: R (≥ 3.0.0)
Published: 2023-12-10
DOI: 10.32614/CRAN.package.sylcount
Author: Drew Schmidt [aut, cre]
Maintainer: Drew Schmidt <wrathematics at gmail.com>
BugReports: https://github.com/wrathematics/sylcount/issues
License: BSD 2-clause License + file LICENSE
URL: https://github.com/wrathematics/sylcount
NeedsCompilation: yes
Materials: README ChangeLog
CRAN checks: sylcount results

Documentation:

Reference manual: sylcount.pdf

Downloads:

Package source: sylcount_0.2-6.tar.gz
Windows binaries: r-devel: sylcount_0.2-6.zip, r-release: sylcount_0.2-6.zip, r-oldrel: sylcount_0.2-6.zip
macOS binaries: r-release (arm64): sylcount_0.2-6.tgz, r-oldrel (arm64): sylcount_0.2-6.tgz, r-release (x86_64): sylcount_0.2-6.tgz, r-oldrel (x86_64): sylcount_0.2-6.tgz
Old sources: sylcount archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=sylcount to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.