mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
Merge pull request #11633 from LazyWolfLin/7-command-line-tools-for-writers
Translated 7 command line tools for writers.
This commit is contained in:
Xingyu.Wang
GitHub
commit
870b2f6b9a
@ -1,75 +0,0 @@
|
||||
Translating by LazyWolfLin
|
||||
|
||||
7 command-line tools for writers | Opensource.com
|
||||
======
|
||||
Put away your word processor and start writing from the command line using these open source tools.
|
||||
|
||||
|
||||
For most people (especially non-techies), the act of writing means tapping out words using LibreOffice Writer or another GUI word processing application. But there are many other options available to help anyone communicate their message in writing, especially for the growing number of writers [embracing plaintext][1].
|
||||
|
||||
There's also room in a GUI writer's world for command line tools that can help them write, check their writing, and more—regardless of whether they're banging out an article, blog post, or story; writing a README; or prepping technical documentation.
|
||||
|
||||
Here's a look at some command-line tools that any writer will find useful.
|
||||
|
||||
### Editors
|
||||
|
||||
Yes, you _can_ do actual writing at the command line. I know writers who do their work using editors like [Nano][2], [Vim][3], [Emacs][4], and [Jove][5] in a terminal window. And those editors [aren't the only games in town][6]. Text editors are great because they (at a basic level, anyway) are easy to use and distraction free. They're perfect for tapping out a first draft of anything or even completing a long and complicated writing project.
|
||||
|
||||
If you want a more word processor-like experience at the command line, take a look at [WordGrinder][7] . WordGrinder is a bare-bones word processor, but it has more than enough features for writing and publishing your work. It supports basic formatting and styles, and you can export your writing to formats like Markdown, ODT, LaTeX, and HTML.
|
||||
|
||||
### Spell checkers
|
||||
|
||||
Every writer does (or at least should do) a spelling check on their work at least once. Why? An immutable law of the writing universe states that, no matter how many times you look over your manuscript, a spelling mistake or typo will creep in.
|
||||
|
||||
My favorite command-line spelling checker is [GNU Aspell][8], which I previously [looked at][9] in detail. Aspell checks plaintext documents interactively and not only highlights errors but often puts the best correction at the top of its list of suggestions. Aspell also ignores many markup languages while doing its thing.
|
||||
|
||||
A much older but still useful alternative is [Ispell][10]. It's a bit slower than Aspell, but both utilities work the same way. As you interact with your text file, Ispell suggests corrections. Ispell also has good support for foreign languages.
|
||||
|
||||
### Prose linters
|
||||
|
||||
Software developers use [linters][11] to check their code for errors or bugs. There are also linters for prose that check for style and syntax errors; think of them as the _Elements of Style_ for the command line. While any writer can (and probably should) use one, a prose linter is especially useful for team documentation projects that require a consistent voice and style.
|
||||
|
||||
[Proselint][12] is a comprehensive tool for checking what you're writing. It looks for jargon, hyperbole, incorrect date and time format, misused terms, and [much more][13]. It's also easy to run and ignores markup in a plaintext file.
|
||||
|
||||
[Alex][14] is a simple yet powerful prose linter. Run it against a plaintext document or one formatted with Markdown or HTML. Alex pumps out warnings of "gender favouring, polarising, race related, religion inconsiderate, or other unequal phrasing in text." If you want to give Alex a test drive, there's an [online demo][15].
|
||||
|
||||
### Other tools
|
||||
|
||||
Sometimes you just can't find the right synonym for a word. But you don't need to grab a "dead tree" thesaurus or go to a dedicated website to perfect your word choice. Just run [Aiksaurus][16] against the word you want to replace, and it does the work for you. This utility's main drawback, though, is that it supports English only.
|
||||
|
||||
Even writers with few (if any) technical skills are embracing [Markdown][17] to quickly and easily format their work. Sometimes, though, you need to convert files formatted with Markdown to something else. That's where [Pandoc][18] comes in. You can use it to convert your documents to HTML, Word, LibreOffice Writer, LaTeX, EPUB, and other formats. You can even use Pandoc to produce books and [research papers][19].
|
||||
|
||||
Do you have a favorite command-line tool for writing? Share it with the Opensource.com community by leaving a comment.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/11/command-line-tools-writers
|
||||
|
||||
作者：[Scott Nesbitt][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/scottnesbitt
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://plaintextproject.online
|
||||
[2]: https://www.nano-editor.org/
|
||||
[3]: https://www.vim.org
|
||||
[4]: https://www.gnu.org/software/emacs/
|
||||
[5]: https://opensource.com/article/17/1/jove-lightweight-alternative-vim
|
||||
[6]: https://en.wikipedia.org/wiki/List_of_text_editors#Text_user_interface
|
||||
[7]: https://cowlark.com/wordgrinder/
|
||||
[8]: http://aspell.net/
|
||||
[9]: https://opensource.com/article/18/2/how-check-spelling-linux-command-line-aspell
|
||||
[10]: https://www.cs.hmc.edu/~geoff/ispell.html
|
||||
[11]: https://en.wikipedia.org/wiki/Lint_(software)
|
||||
[12]: http://proselint.com/
|
||||
[13]: http://proselint.com/checks/
|
||||
[14]: https://github.com/get-alex/alex
|
||||
[15]: https://alexjs.com/#demo
|
||||
[16]: http://aiksaurus.sourceforge.net/
|
||||
[17]: https://en.wikipedia.org/wiki/Markdown
|
||||
[18]: https://pandoc.org
|
||||
[19]: https://opensource.com/article/18/9/pandoc-research-paper
|
||||
@ -0,0 +1,73 @@
|
||||
给写作者们的 7 个命令行工具 | Opensource.com
|
||||
======
|
||||
扔掉你的打字机，然后使用这些开源工具在命令行上写作吧。
|
||||
|
||||
|
||||
对于大多数人（尤其是非技术人员），写作意味着在 LibreOffice Writer 或者其他带图形界面的文本编辑器上编辑文本。但是还有许多可行的方法可以让任何人通过文本传递他们的信息，尤其是越来越多的作者选择[拥抱纯文本][1]。
|
||||
|
||||
在使用图形界面写作的世界同样有命令行工具的一席之地。这些命令行工具可以帮助他们进行写作，检查他们的拼写等等——无论是在写一篇文章、博客或者故事；写一个 README 文件；或者准备一份技术文档的时候。
|
||||
|
||||
下面是一些在任何写作情况下都有用的命令行工具。
|
||||
|
||||
### 编辑器
|
||||
|
||||
没错，你可以在命令行进行真正的写作。我知道一些写作者会使用 [Nano][2]、[Vim][3]、[Emacs][4]、以及 [Jove][5] 等编辑器在终端窗口中进行工作。而这些编辑器[并非屈指可数][6]。文本编辑器的优势在于它们简单易用以及更专注于文本。非常适合用于编辑任何文本的初稿甚至完成一个漫长而复杂的写作项目。
|
||||
|
||||
如果你想在命令行中获得更像文字编辑器的体验，不妨了解一下 [WordGrinder][7]。WordGrinder 是一款简单但拥有足够的编写和发布功能的文字编辑器。它支持基本的格式和样式，并且你可以将你的文字以 Markdown，ODT，LaTeX，或者 HTML 等格式导出。
|
||||
|
||||
### 拼写检查
|
||||
|
||||
每个写作者在完成他们的工作前至少要（或者说应该要）进行一次拼写检查。为什么呢？在写作的世界里有个永恒的定律，无论你检查了多少次手稿，拼写错误和错字依然会存在。
|
||||
|
||||
我曾经详细[介绍][9]过我最喜欢的命令行拼写检查工具 [GNU Aspell][8]。交互式检测文本文档的 Aspell 不仅能够高亮显示拼写错误还能在拼写错误的上方提供正确的拼写建议。Aspell 在进行拼写检查时同样能够忽略许多语法标记。
|
||||
|
||||
另一个够老但仍然有用的代替品是 [Ispell][10]。虽然它比 Aspell 稍慢一点，但它们都以相同的方式工作。当你在你的文本文件上工作时，Ispell 将提供正确的建议。Ispell 同样也对英语以外的语言提供了良好的支持。
|
||||
|
||||
### Prose linters
|
||||
|
||||
软件开发人员使用 [linters][11] 来检查他们的代码是否存在错误或者 bugs。同样也有用于检查文本样式或语法错误的 linters；而命令行会认为这些错误是样式元素。任何写作者都可以（也应该）使用它，一个 prose linter 对于要求文档风格和样式一致的文档团队项目而言尤其有用。
|
||||
|
||||
[Proselint][12] 是一款全能的实时检查工具。它会找出行话，大话，不正确日期和时间格式，滥用的术语[等等][13]。它也很容易运行并忽略文本中的标记。
|
||||
|
||||
[Alex][14] 是一个简单但有用的 prose linter。 对明文文本或者格式为 Markdown 或 HTML 的文档使用它。Alex 会对“性别偏好，极端主义，种族相关，宗教，或者文章中其他不平等的措辞”产生警告。如果你想要试试看 Alex，这里有一个在线 [demo][15]。
|
||||
|
||||
### 其他工具
|
||||
|
||||
有时候你找不到一个单词的恰当的同义词。但你不需要去呆板的词库中抓取或者去专门的网站完善你的单词完整。仅仅需要对你想要替换的单词运行 [Aiksaurus][16]，然后它就会为你完成这个工作。但是，这个程序最大的缺点是它只支持英语。
|
||||
|
||||
即使是只会很少（甚至只有一项）技术技能的写作者都能接受 [Markdown][17] 来快速而简单地格式化他们的作品。但是，有时候你也需要将使用 Markdown 格式的文件转换成其他格式。这就是 [Pandoc][18] 的用武之地。你可以用它来将你的文档转换成 HTML，Word，LibreOffice Writer，LaTeX，EPUB 以及其他格式。你甚至可以用 Pandoc 来生成书籍和[研究论文][19]。
|
||||
|
||||
你有最喜欢的命令行写作工具吗？在 Opensource.com 社区发表评论分享它吧。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/11/command-line-tools-writers
|
||||
|
||||
作者：[Scott Nesbitt][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[LazyWolfLin](https://github.com/LazyWolfLin)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/scottnesbitt
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://plaintextproject.online
|
||||
[2]: https://www.nano-editor.org/
|
||||
[3]: https://www.vim.org
|
||||
[4]: https://www.gnu.org/software/emacs/
|
||||
[5]: https://opensource.com/article/17/1/jove-lightweight-alternative-vim
|
||||
[6]: https://en.wikipedia.org/wiki/List_of_text_editors#Text_user_interface
|
||||
[7]: https://cowlark.com/wordgrinder/
|
||||
[8]: http://aspell.net/
|
||||
[9]: https://opensource.com/article/18/2/how-check-spelling-linux-command-line-aspell
|
||||
[10]: https://www.cs.hmc.edu/~geoff/ispell.html
|
||||
[11]: https://en.wikipedia.org/wiki/Lint_(software)
|
||||
[12]: http://proselint.com/
|
||||
[13]: http://proselint.com/checks/
|
||||
[14]: https://github.com/get-alex/alex
|
||||
[15]: https://alexjs.com/#demo
|
||||
[16]: http://aiksaurus.sourceforge.net/
|
||||
[17]: https://en.wikipedia.org/wiki/Markdown
|
||||
[18]: https://pandoc.org
|
||||
[19]: https://opensource.com/article/18/9/pandoc-research-paper
|
||||
Loading…
Reference in New Issue
Block a user