1.易读的
2.值得一读的
1.easy and pleasant to read
2.writing that is readable is clear and able to be read
1.Imagine if you could glance at a namespace-riddled XML document and easily comprehend it; imagine if it really was human readable.
设想一下，如果看一眼受名称空间困扰的XML文档，就能够很容易地理解它，或者说，如果它确实是人类可读的，那该多好啊。
2.However, this should not always be considered a bad thing as it tends to make the message more readable to humans.
不过，这不应该总是被看作一件坏事，因为它有助于使消息具有更好的人类可读性。
3.The list-construction operators in Scala make the return conditions for both cases quite readable and easy to understand.
Scala中的列表构造操作符使得这两种情况下的返回条件变得非常易读、易于理解。
4.This is a basic rule of the Semantic Web, but it has always been a fact of metadata usage in machine-readable form.
这是语义网的基本规则，这也是一直以来用机器可读的方式使用元数据的事实。
5.Use it to beautify your code or to reformat legacy code you've inherited to make it more readable.
它使用美化您的代码或重新格式化您已经继承以使其更具可读性的旧代码。
6.Again, the format should be machine-readable and -verifiable and easy to produce automatically (e. g. from a build system).
再次指出，文件格式应该是机器可读并可验证的，同时也应该是容易自动生成的（比如从构建系统生成）。
7.The strnlen_user function first checks to see that the user buffer is readable through a call to access_ok.
strnlen_user函数首先通过调用access_ok检查用户缓冲区是否可读。
8.It might be readable, maybe funny, he said, and "not just smell like a regular autobiography. "
他说，这可能是值得一读的，也许是幽默搞笑的，但“不会有一般自传的那股味道。”
9.Gateway form using decision, fork, merge, and joins is often more readable for models that only model control flow.
网关形式使用decision、fork、merge和join元素，对于只包含控制流的模型而言，此形式通常更易于理解。
10.It's easy to understand, human readable, and not dependent on any particular language or framework.
这很容易理解，具有很好的可读性，而且不依赖于任何特定的语言或框架。