1-js/02-first-steps/08-comparison #50

lcx-seima · 2018-04-20T12:50:27Z

完成翻译 resolve #8

Starriers · 2018-04-23T01:21:23Z

Starriers

Starriers · 2018-04-23T01:25:09Z

1-js/02-first-steps/08-comparison/article.md

- Values `null` and `undefined` equal `==` each other and do not equal any other value.
- Be careful when using comparisons like `>` or `<` with variables that can occasionally be `null/undefined`. Making a separate check for `null/undefined` is a good idea.
+- 比较操作符始终返回逻辑值。
+- 字符串间按词典顺序逐字符比较大小。


字典加引号！可以尊重一波原文

Starriers · 2018-04-23T01:31:49Z

1-js/02-first-steps/08-comparison/article.md


-Just treat any comparison with `undefined/null` except the strict equality `===` with exceptional care.
+除了严格相等 `===` 外，其他凡是有 `undefined/null` 参与的比较，我们都需要额外 “关照”。


原文没有着重强调，但如果想那么翻译，前面也不应该有空格

Starriers · 2018-04-23T01:41:21Z

1-js/02-first-steps/08-comparison/article.md


-The reason is that an equality check `==` and comparisons `> < >= <=` work differently. Comparisons convert `null` to a number, hence treat it as `0`. That's why (3) `null >= 0` is true and (1) `null > 0` is false.
+为什么会出现这种反常结果，这是因为相等性检测 `==` 和普通比较符 `> < >= <=` 的代码逻辑是相互独立的。进行值的比较会把 `null` 转为数字，因此它被转为了 `0`。这就是为什么（3）中 `null >= 0` 返回 true，（1）中 `null > 0` 返回 false。


手机上看的（1）前面是不是有空格，有的话是不需要的

Starriers · 2018-04-23T01:42:33Z

1-js/02-first-steps/08-comparison/article.md


 ```js run
 alert( null > 0 );  // (1) false
 alert( null == 0 ); // (2) false
 alert( null >= 0 ); // (3) *!*true*/!*
 ```

-Yeah, mathematically that's strange. The last result states that "`null` is greater than or equal to zero". Then one of the comparisons above must be correct, but they are both false.
+是的，上面的结果完全打破了你对数学的认识。在最后一行代码显示 "`null` 大于等于 0" 的情况下，前两行代码中一定会有一个是正确的，然而事实表明它们的结果都是 false。


引号中包含了中文，所以换中文的

Starriers · 2018-04-23T01:43:54Z

1-js/02-first-steps/08-comparison/article.md


-Now let's see funny things that happen when we apply those rules. And, what's more important, how to not fall into a trap with these features.
+下面让我们看看，这些规则会带来什么有趣的现象。同时更重要的是，我们需要从中学会如何远离这些特性带来的 “陷阱”。


陷阱不要加空格

Starriers · 2018-04-23T01:50:15Z

1-js/02-first-steps/08-comparison/article.md

 ```

-There also exists a "strict non-equality" operator `!==`, as an analogy for `!=`.
+同样的，与 “不相等” 符号 `!=` 类似，“严格不相等” 表示为 `!==`。


不相等前后不要空格

后面同理

Starriers · 2018-04-23T01:53:57Z

1-js/02-first-steps/08-comparison/article.md


-The strict equality check operator is a bit longer to write, but makes it obvious what's going on and leaves less space for errors.
+严格相等的操作符虽然略为冗长，但是它很清楚地显示了比较的意图，让你更少 “犯错”。


让你更少犯错 =>降低你犯错的可能性。或者你把空格去掉

Starriers · 2018-04-23T02:01:10Z

1-js/02-first-steps/08-comparison/article.md


-To see which string is greater than the other, the so-called "dictionary" or "lexicographical" order is used.
+在比较字符串的大小时，会使用 “字典” 或 “词典” 顺序进行判定。


这两个引号都不要前后空格

@leviding 麻烦看看这个 case。我翻阅了我翻译的或者其他人的翻译，存在为了照顾格式在 “” 前后添加空格的，也有不添加的，但是都通过了校对。你这边有无意见？

@lcx-seima 引号里内容是中文的则不加空格，为英文则加空格。之前没有太注意这个问题。

@leviding 好的，可以更新这条rule到wiki

@lcx-seima 好，感谢提醒 😆

Starriers · 2018-04-23T02:02:57Z

1-js/02-first-steps/08-comparison/article.md


- `true` -- means "yes", "correct" or "the truth".
- `false` -- means "no", "wrong" or "a lie".
+- `true` —— 表示 “yes（是）”，“correct（正确）” 或 “the truth（真理）”。


包含了中文用中文引号下文同理

这里译者用的是中文引号了吧

因为内容是译者自己加的，本来的纯英文引用，导致了混合中文。再用英文的引号，肯定不合适。所以我的想法是应该用中文的，或者直接去掉自己的注释（这样的单词，对于开发者来说，如果不理解，个人建议是 —— 转行）。

@Starriers 此处译者用的引号已经是中文的引号了，你认真看看，我明白你的意思。

这儿就这样吧，这一行不用改，其他的校对意见照常修改。

Starriers · 2018-04-23T02:04:44Z

1-js/02-first-steps/08-comparison/article.md


-## Boolean is the result
+## “比较” 终为 Boolean


比较值为 Boolean 类型或者你去掉空格

meloalright · 2018-04-23T02:35:56Z

@leviding 校对认领~

leviding · 2018-04-23T04:02:41Z

@meloalright ok

meloalright

@lcx-seima 出色的译者 + 出色的校对者楼上我这边的建议不多啦

meloalright · 2018-04-23T09:42:51Z

1-js/02-first-steps/08-comparison/article.md


-## Boolean is the result
+## “比较” 终为 Boolean


这里感觉可以直接意译就好了 =>『比较结果为 Boolean 类型』

meloalright · 2018-04-23T09:45:04Z

@lcx-seima @leviding 校对完成

leviding · 2018-04-23T13:40:59Z

改完上面的就行了

lcx-seima · 2018-04-26T02:30:59Z

@Starriers @meloalright 感谢细心校对

@leviding 已修改完

feat: 完成翻译

78db7dd

leviding added the 校对认领 label Apr 21, 2018

leviding mentioned this pull request Apr 21, 2018

1-js/02-first-steps/08-comparison #8

Closed

Starriers reviewed Apr 23, 2018

View reviewed changes

leviding added 正在校对 and removed 校对认领 labels Apr 23, 2018

meloalright reviewed Apr 23, 2018

View reviewed changes

update: 完成校对修改

50284b1

leviding approved these changes Apr 26, 2018

View reviewed changes

leviding merged commit a36aa33 into javascript-tutorial:zh-hans Apr 26, 2018

leviding added 翻译完成 and removed 正在校对 labels Apr 26, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

1-js/02-first-steps/08-comparison #50

1-js/02-first-steps/08-comparison #50

lcx-seima commented Apr 20, 2018

Starriers commented Apr 23, 2018

Starriers left a comment

Starriers Apr 23, 2018

Starriers Apr 23, 2018

Starriers Apr 23, 2018

Starriers Apr 23, 2018

Starriers Apr 23, 2018

Starriers Apr 23, 2018 •

edited by leviding

Starriers Apr 23, 2018

Starriers Apr 23, 2018

Starriers Apr 23, 2018

lcx-seima Apr 25, 2018

leviding Apr 26, 2018

lcx-seima Apr 26, 2018

leviding Apr 26, 2018

Starriers Apr 23, 2018

leviding Apr 23, 2018

Starriers Apr 23, 2018

leviding Apr 23, 2018 •

edited

leviding Apr 23, 2018

Starriers Apr 23, 2018

meloalright commented Apr 23, 2018

leviding commented Apr 23, 2018

meloalright left a comment

meloalright Apr 23, 2018 •

edited

meloalright commented Apr 23, 2018

leviding commented Apr 23, 2018

lcx-seima commented Apr 26, 2018


		Just treat any comparison with `undefined/null` except the strict equality `===` with exceptional care.
		除了严格相等 `===` 外，其他凡是有 `undefined/null` 参与的比较，我们都需要额外 “关照”。


		The reason is that an equality check `==` and comparisons `> < >= <=` work differently. Comparisons convert `null` to a number, hence treat it as `0`. That's why (3) `null >= 0` is true and (1) `null > 0` is false.
		为什么会出现这种反常结果，这是因为相等性检测 `==` 和普通比较符 `> < >= <=` 的代码逻辑是相互独立的。进行值的比较会把 `null` 转为数字，因此它被转为了 `0`。这就是为什么（3）中 `null >= 0` 返回 true，（1）中 `null > 0` 返回 false。


		Now let's see funny things that happen when we apply those rules. And, what's more important, how to not fall into a trap with these features.
		下面让我们看看，这些规则会带来什么有趣的现象。同时更重要的是，我们需要从中学会如何远离这些特性带来的 “陷阱”。


		The strict equality check operator is a bit longer to write, but makes it obvious what's going on and leaves less space for errors.
		严格相等的操作符虽然略为冗长，但是它很清楚地显示了比较的意图，让你更少 “犯错”。


		To see which string is greater than the other, the so-called "dictionary" or "lexicographical" order is used.
		在比较字符串的大小时，会使用 “字典” 或 “词典” 顺序进行判定。

1-js/02-first-steps/08-comparison #50

1-js/02-first-steps/08-comparison #50

Conversation

lcx-seima commented Apr 20, 2018

Starriers commented Apr 23, 2018

Starriers left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Starriers Apr 23, 2018 • edited by leviding

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

leviding Apr 23, 2018 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

meloalright commented Apr 23, 2018

leviding commented Apr 23, 2018

meloalright left a comment

Choose a reason for hiding this comment

meloalright Apr 23, 2018 • edited

Choose a reason for hiding this comment

meloalright commented Apr 23, 2018

leviding commented Apr 23, 2018

lcx-seima commented Apr 26, 2018

Starriers Apr 23, 2018 •

edited by leviding

leviding Apr 23, 2018 •

edited

meloalright Apr 23, 2018 •

edited