Crates.io | english-lint |
lib.rs | english-lint |
version | 0.1.1 |
source | src |
created_at | 2016-04-19 12:54:53.61597 |
updated_at | 2016-06-12 14:48:31.693654 |
description | Find common stylistic problems in english texts. Works well for technical or scientific documents. |
homepage | https://github.com/killercup/english-lint |
repository | https://github.com/killercup/english-lint |
max_upload_size | |
id | 4790 |
size | 54,942 |
Find common stylistic problems in english texts. Works well for technical or scientific documents. Based on write-good and this article.
This repository contains both a library and a simple CLI tool.
First, install the CLI tool using cargo install english-lint
(assumes you have recent Rust and Cargo versions installed on your system).
You can either pipe text data into it (e.g. echo "Hello world" | english-lint
) or call it with a file name paramter (english-lint my-thesis.md
). It outputs one line for each suggestion containing the name of the lint group and the line number with start/end character indizes. If you don't see any output, english-lint thinks your text is already perfect :)
$ english-lint Readme.md
wordy: 'shall' (22:72-77)
wordy: 'additional' (23:39-49)
First, add english-lint as a dependency to your project (e.g. using cargo add english-lint
using cargo-edit) and include it with extern crate english_lint;
.
Currently, this library only exposes two things: A free function, english_lint::lint
and the struture this function returns, english_lint::Hint
.
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.