translated

This commit is contained in:
geekpi 2018-08-09 08:47:00 +08:00
parent a99d571380
commit ce30ec5f56
2 changed files with 69 additions and 71 deletions

View File

@ -1,71 +0,0 @@
translating---geekpi
Linux command line tools for working with non-Linux users
======
![](https://images.techhive.com/images/article/2016/06/linux-shell-100666628-large.jpg)
I spend most of my computing life in the Shell (command line, terminal or whatever you want to call it on your platform of choice). This can be a bit challenging, though, when I need to work with large groups of other people, especially in big enterprise companies that -- well -- use anything but the Shell.
The problems that crop up are made worse when other people within your company use a different platform than you. I tend to use Linux. If I'm doing a lot of my daily work from a Linux terminal and the bulk of my co-workers use Windows 10 (entirely from the GUI side), things can get … problematic.
**Also on Network World:**[ **11 pointless but awesome Linux terminal tricks**][1]
Luckily, over the past few years, I've figured out how to deal with these problems. I've found ways to make using a Linux (or other Unix-like systems) Shell much more doable within a non-Unix, corporate environment. These tools/tips apply equally well for SysAdmins working on a company's servers as they do for developers or marketing people.
## Command line tools for working with non-Linux users
Let's start by focusing on the two areas that seem to be the hardest to solve for many people in big companies: document compatibility and enterprise instant messaging.
### Document compatibility between Linux and non-Linux systems
One of the biggest issues that crops up is that of simple word processing document compatibility.
Let's say your company has standardized on Microsoft Office. This makes you sad. But do not lose hope! There are ways to make this (mostly) work -- even from the Shell.
Two tools are critical in my arsenal: [Pandoc][2] and [Wordgrinder][3].
Wordgrinder is a simple, straight-to-the-point word processor. It may not be as full-featured as LibreOffice (or, really, any major GUI word-processing application), but it's fast. It's stable. And it supports just enough features (and file formats) to get the job done. In fact, I write the majority of my articles and books entirely in Wordgrinder.
But there's a problem (you knew there had to be).
Wordgrinder doesn't support .doc (or .docx) files. That means it can't read most files that your Windows- and MS Office-using co-workers send you.
That's where Pandoc comes in. It's a simple document converter that takes a wide range of files as input (MS Word, LibreOffice, HTML, markdown, etc.) and converts them to something else. The number of formats supported here is absolutely phenomenal -- PDF, ePub, various slideshow formats. It really makes converting documents between formats a breeze.
That's not to say I don't occasionally encounter formatting or feature issues. Converting a Word document that has a lot of custom formatting, some scripting, and an embedded chart? Yeah, a lot of that will be lost in the process.
But in practical terms, the combination of Pandoc (for converting files) and Wordgrinder (for document editing) has proven quite capable and powerful.
### Corporate instant messaging between Linux and non-Linux systems
Every company likes to standardize on an instant messaging system -- something for all employees to use to keep in real-time contact.
From the command line, this can get tricky. What if your company uses Google Hangouts? Or how about Novell GroupWise Messenger? Neither have officially supported, terminal-based clients.
Thank goodness, then, for [Finch & Hangups][4].
Finch is sort of the terminal version of Pidgin (the open-source, multi-protocol messenger client). It supports a wide variety of protocols, including Novell GroupWise, (the soon to be dead) AOL Instant Messenger, and a bunch of others.
And Hangups is an open implementation of a Google Hangouts client -- complete with message history and a nice tabbed interface.
Neither of these solutions will provide you with voice or video chat capabilities, but for text-based messaging, they work delightfully well. They aren't perfect (the user interface of Finch takes some getting used to), but they're definitely good enough to keep in touch with your co-workers.
Will these solutions allow you to spend your entire work day within the comforts of a text-only Shell? Probably not. Personally, I find that (with these tools, and others) I can comfortably spend roughly 80 percent of my day in a text-only interface.
Which feels pretty darn great.
--------------------------------------------------------------------------------
via: https://www.networkworld.com/article/3235688/linux/linux-command-line-tools-for-working-with-non-linux-users.html
作者:[Bryan Lunduke][a]
译者:[译者ID](https://github.com/译者ID)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
[a]:https://www.networkworld.com/author/Bryan-Lunduke/
[1]:http://www.networkworld.com/article/2926630/linux/11-pointless-but-awesome-linux-terminal-tricks.html#tk.nww-fsb
[2]:https://www.youtube.com/watch?v=BkTYHChkDoE
[3]:https://www.youtube.com/watch?v=WnMyamBgKFE
[4]:https://www.youtube.com/watch?v=19lbWnYOsTc

View File

@ -0,0 +1,69 @@
用于与非 Linux 用户合作的 Linux 命令行工具
======
![](https://images.techhive.com/images/article/2016/06/linux-shell-100666628-large.jpg)
我大部分时间都在使用 Shell命令行终端或其他不管在你使用的平台上的名称上。但是当我需要与大量其他人合作时这可能会有点挑战特别是在大型企业公司中 - 除了 shell 外其他都使用。
当公司内的其他人使用与你不同的平台时,问题就会变得更加严重。我倾向于使用 Linux。如果我在 Linux 终端上做了很多日常工作,而我的大多数同事都使用 Windows 10完全使用 GUI 端),那么事情就会变得有问题。
**Network World 上另外一篇文章:**[**11 个没用但很酷的 Linux 终端技巧**][1]
幸运的是,在过去的几年里,我已经想出如何处理这些问题。我已经找到了在非 Unix 的企业环境中使用 Linux或其他类 Unix 系统Shell 的方法。这些工具/技巧同样适用于在公司服务器上工作的系统管理员s就像对开发人员或营销人员一样。。
## 用于与非 Linux 用户合作的 Linux 命令行工具
让我们首先关注对于大公司中的许多人来说似乎最难解决的两个方面:文档兼容性和企业即时消息。
### Linux 和非 Linux 系统之间的文档兼容性
出现的最大问题之一是简单的文字处理文档兼容性。
假设你的公司已在 Microsoft Office 上进行了标准化。这让你难过。但不要失去希望!有很多方法可以使它(基本)可用 - 甚至在 shell 中。
两个工具在我的武器库中至关重要:[Pandoc][2] 和 [Wordgrinder][3]。
Wordgrinder 是一个简单,直观的文字处理器。它可能不像 LibreOffice 那样功能齐全(或者,实际上,任何主要的 GUI 文字处理应用程序),但速度很快。它很稳定。它有足够的功能(和文件格式)来完成工作。事实上,我完全在 Wordgrinder 中写了我的大部分文章和书籍。
但是有一个问题(你知道肯定会有)。
Wordgrinder 不支持 .doc或 .docx文件。这意味着它无法读取使用 Windows 和 MS Office 的同事发送给你的大多数文件。
这就是P andoc 的用武之地。它是一个简单的文档转换器可以将各种文件作为输入MS Word、LibreOffice、HTML、markdown 等)并将它们转换为其他内容。它支持的格式数量绝对是惊人的 - PDF、ePub、各种幻灯片格式。它确实使格式之间的文档转换变得轻而易举。
这并不是说我不会偶尔遇到格式或功能问题。转换有大量自定义格式,某些脚本和嵌入式图表的 Word 文档?是的,在这个过程中会丢失很多。
但实际上Pandoc用于转换文件和 Wordgrinder用于文档编辑的组合已经证明非常有用和强大。
### Linux 和非 Linux 系统之间的企业即时消息传递
每家公司都喜欢在即时通讯系统上实现标准化 - 所有员工都可以使用它来保持实时联系。
在命令行中,这可能会变得棘手。如果贵公司使用 Google 环聊怎么办?或者 Novell GroupWise Messenger 怎么样?既没有官方支持,也没有基于终端的客户端。
谢天谢地,还有[ Finch 和 Hangups][4]。
Finch 是 Pidgin开源多协议消息客户端的终端版本。它支持各种协议包括 Novell GroupWise、很快会死AOL Instant Messenger 以及其他一些协议。
而 Hangups 是 Google Hangouts 客户端的开源实现 - 包含消息历史记录和精美的标签界面。
这些方案都不会为你提供语音或视频聊天功能但对于基于文本的消息它们的工作得非常好。它们并不完美Finch 的用户界面需要时间习惯),但它们肯定足以与你的同事保持联系。
这些方案能否让你在纯文本 shell 中舒适地过完一个工作日?可能不会。就个人而言,我发现(使用这些工具和其他工具)我可以轻松地将 80 的时间花在纯文本界面上。
这感觉很棒。
--------------------------------------------------------------------------------
via: https://www.networkworld.com/article/3235688/linux/linux-command-line-tools-for-working-with-non-linux-users.html
作者:[Bryan Lunduke][a]
译者:[geekpi](https://github.com/geekpi)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
[a]:https://www.networkworld.com/author/Bryan-Lunduke/
[1]:http://www.networkworld.com/article/2926630/linux/11-pointless-but-awesome-linux-terminal-tricks.html#tk.nww-fsb
[2]:https://www.youtube.com/watch?v=BkTYHChkDoE
[3]:https://www.youtube.com/watch?v=WnMyamBgKFE
[4]:https://www.youtube.com/watch?v=19lbWnYOsTc