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.
Cross-Linguistic Data Format (CLDF) is a framework for storing cross-linguistic data, ensuring compatibility and ease of data exchange between different linguistic datasets see Forkel et al. (2018) <doi:10.1038/sdata.2018.205>. The 'rcldf' package is designed to facilitate the manipulation and analysis of these datasets by simplifying the loading, querying, and visualisation of CLDF datasets making it easier to conduct comparative linguistic analyses, manage language data, and apply statistical methods directly within R.
Version: | 1.5.1 |
Imports: | archive, bib2df (≥ 1.1.1), csvwr, digest, dplyr, jsonlite, logger, magrittr, purrr, readr, remotes, rlang, tools, urltools, utils |
Suggests: | ggplot2, patchwork, testthat, mockthat, spelling, covr, knitr, rmarkdown, qpdf |
Published: | 2025-09-30 |
DOI: | 10.32614/CRAN.package.rcldf |
Author: | Simon J. Greenhill [aut, cre] |
Maintainer: | Simon J. Greenhill <simon at simon.net.nz> |
BugReports: | https://github.com/SimonGreenhill/rcldf/issues |
License: | Apache License (≥ 2.0) |
URL: | https://github.com/SimonGreenhill/rcldf |
NeedsCompilation: | no |
Language: | en-US |
Materials: | README |
CRAN checks: | rcldf results |
Reference manual: | rcldf.html , rcldf.pdf |
Vignettes: |
Using rcldf to work with Cross-Linguistic Data Format datasets (source, R code) |
Package source: | rcldf_1.5.1.tar.gz |
Windows binaries: | r-devel: rcldf_1.5.1.zip, r-release: rcldf_1.5.1.zip, r-oldrel: rcldf_1.5.1.zip |
macOS binaries: | r-release (arm64): rcldf_1.5.1.tgz, r-oldrel (arm64): not available, r-release (x86_64): rcldf_1.5.1.tgz, r-oldrel (x86_64): rcldf_1.5.1.tgz |
Please use the canonical form https://CRAN.R-project.org/package=rcldf 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.