Merge #569: Bugfix: fix broken Markdown reference-style links

harding · harding · commit c5316d1b60a6 · 2018-06-28T08:10:17.000-04:00
53b8472 Translations: 0.13.1 release: change link to segwit benefits page (David A. Harding) 0e7d61a Travis: fix bug with colored text supressing some output (David A. Harding) 3069b03 Makefile: add test for broken Markdown reference-style links (David A. Harding) f6faef9 Drop untranslated zh_TW Support BIPs page after adding a redirect (David A. Harding) 916a896 Translations Bugfix: repair missing/broken Markdown reference-style links (David A. Harding) 5435c3b Bugfix: repair missing/broken Markdown reference-style links (David A. Harding) Pull request description: If you create a Markdown reference-style link whose target isn't defined, the link definition is rendered unchanged onto the resultant page. E.g. [broken][broken link] This PR adds a test that greps for those broken definitions and fixes all current instances of them. Tree-SHA512: ba481a4491fe236d72a1de91b3e22fc169573a6371edc877374af6ea4b89ef219816e4030291d14ea56b5b303388244fe57fb301da113a8432c08c2447b0e43a
diff --git a/Makefile b/Makefile
@@ -8,6 +8,14 @@ build:
 	bundle exec jekyll clean
 	bundle exec jekyll build --future --drafts --unpublished
 
-test:
-	bundle exec htmlproof --check-html --disable-external --url-ignore '/^\/bin/.*/' ./_site
+test: test-fast test-slow
+
+test-slow:
+	## Check for malformed HTML and broken internal links
+	bundle exec htmlproof --check-html --disable-external --url-ignore '/^\/bin/.*/' ./_site | cat
+	## Check that links on the /en/download page point to the separately-stored binaries in /bin
 	contrib/qa/test-binary-availability.sh && echo "SUCCESS checking URLs for binaries"
+
+test-fast:
+	## Check for broken Markdown reference-style links that are displayed in text unchanged, e.g. [broken][broken link]
+	! find _site/ -name '*.html' | xargs grep ']\[' | grep -v skip-test | grep .
diff --git a/_posts/en/meetings/2015-12-17-meeting.md b/_posts/en/meetings/2015-12-17-meeting.md
@@ -100,4 +100,5 @@ YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
 ## Credits
 
 This summary was originally compiled by Stefan Gilis aka "G1lius" and posted to the [bitcoin-discuss mailing list][meetingsource] with the disclaimer, "Please bear in mind I'm not a developer so some things might be incorrect or plain wrong." and placed copyright in the Public Domain.
+
 [meetingsource]: http://lists.linuxfoundation.org/pipermail/bitcoin-discuss/2015-December/000039.html
diff --git a/_posts/en/meetings/2016-07-21-meeting.md b/_posts/en/meetings/2016-07-21-meeting.md
@@ -126,5 +126,6 @@ This summary was compiled without input from any of the participants in the disc
 [#7081]: https://github.com/bitcoin/bitcoin/pull/7081
 [#8364]: https://github.com/bitcoin/bitcoin/pull/8364
 [#8365]: https://github.com/bitcoin/bitcoin/pull/8365
+[#8388]: https://github.com/bitcoin/bitcoin/pull/8388
 
 {% include _references.md %}
diff --git a/_posts/en/meetings/2016-08-04-meeting.md b/_posts/en/meetings/2016-08-04-meeting.md
@@ -87,7 +87,7 @@ There's no clear cut solution for this.
  
 This summary was compiled without input from any of the participants in the discussion, so any errors are the fault of the summary author and not the discussion participants.
  
-[#8483]: https://github.com/bitcoin/bitcoin/pull/8483
+[#8438]: https://github.com/bitcoin/bitcoin/pull/8438
 [#8365]: https://github.com/bitcoin/bitcoin/pull/8365
 
 {% include _references.md %}
diff --git a/_posts/en/meetings/2016-12-01-meeting.md b/_posts/en/meetings/2016-12-01-meeting.md
@@ -132,6 +132,7 @@ This summary was compiled without input from any of the participants in the disc
 [#9188]: https://github.com/bitcoin/bitcoin/pull/9188
 [#9239]: https://github.com/bitcoin/bitcoin/pull/9239
 [#9252]: https://github.com/bitcoin/bitcoin/pull/9252
+[#9253]: https://github.com/bitcoin/bitcoin/pull/9253
 [#9143]: https://github.com/bitcoin/bitcoin/pull/9143
 [#9256]: https://github.com/bitcoin/bitcoin/pull/9256
 [#8723]: https://github.com/bitcoin/bitcoin/pull/8723
diff --git a/_posts/en/meetings/2016-12-22-meeting.md b/_posts/en/meetings/2016-12-22-meeting.md
@@ -121,5 +121,6 @@ This summary was compiled without input from any of the participants in the disc
 [#9375]: https://github.com/bitcoin/bitcoin/pull/9375
 [#7533]: https://github.com/bitcoin/bitcoin/pull/7533
 [#9138]: https://github.com/bitcoin/bitcoin/pull/9138
+[#8776]: https://github.com/bitcoin/bitcoin/pull/8776
 
 {% include _references.md %}
diff --git a/_posts/en/meetings/2017-04-06-meeting.md b/_posts/en/meetings/2017-04-06-meeting.md
@@ -38,7 +38,7 @@ Since a lot of developers where missing or not focussed on the meeting because o
 - Sipa has been working on things related to database/cache/flush/memory usage.
 - Morcos is coding and recoding fee estimation for months, but it's much more complicated and will be hard to review.
 - Sdaftuar has been working on CreateNewBlock, introducing a way to skip recently added transactions if the block income for doing so is below some theshold.
-- Jtimon worked on some refactoring PRs, like [#9494][], [#10119][] and [#101118][]
+- Jtimon worked on some refactoring PRs, like [#9494][], [#10119][] and [#10118][]
 
 ## High priority review
 
diff --git a/_posts/en/meetings/2017-05-11-meeting.md b/_posts/en/meetings/2017-05-11-meeting.md
@@ -110,7 +110,7 @@ This summary was compiled without input from any of the participants in the disc
 
 [#9343]: https://github.com/bitcoin/bitcoin/pull/9343
 [#10333]: https://github.com/bitcoin/bitcoin/pull/10333
-[#8649]: https://github.com/bitcoin/bitcoin/pull/8649
+[#8694]: https://github.com/bitcoin/bitcoin/pull/8694
 [#10240]: https://github.com/bitcoin/bitcoin/pull/10240
 [#9494]: https://github.com/bitcoin/bitcoin/pull/9494
 [#10195]: https://github.com/bitcoin/bitcoin/pull/10195
diff --git a/_posts/en/pages/2016-01-13-supported-bips.md b/_posts/en/pages/2016-01-13-supported-bips.md
@@ -7,6 +7,8 @@ lang: en
 permalink: /en/bips/
 share: false
 version: 2
+redirect_from:
+  - /zh_TW/bips/
 ---
 Bitcoin Core supports the following [BIPs][BIP1].
 
diff --git a/_posts/en/posts/2016-04-15-release-0-12-1.md b/_posts/en/posts/2016-04-15-release-0-12-1.md
@@ -8,6 +8,10 @@ type: posts
 layout: post
 share: true
 version: 1
+excerpt: >-
+  We are pleased to announce the release of Bitcoin Core 0.12.1.  This
+  maintenance update includes the first soft fork deployment utilising
+  version bits
 ---
 We are pleased to announce the release of Bitcoin Core 0.12.1. This maintenance update includes the first soft fork deployment utilising "[version bits][BIP9]" as part of the [capacity increases](/en/2015/12/23/capacity-increases-faq/) roadmap.
 
diff --git a/_posts/ja/releases/2017-09-01-release-0.15.0.md b/_posts/ja/releases/2017-09-01-release-0.15.0.md
@@ -303,7 +303,7 @@ Coin Age Priorityの削除 {#removal-of-coin-age-priority}
 - #9853 `02bd6e9` Fix error codes from various RPCs (jnewbery)
 - #9842 `598ef9c` Fix RPC failure testing (continuation of #9707) (jnewbery)
 - #10038 `d34995a` Add mallocinfo mode to `getmemoryinfo` RPC (laanwj)
-- #9500 `3568b30` [Qt][RPC] Autocomplete commands for 'help' command in debug console (achow101)
+- #9500 `3568b30` [Qt] \[RPC] Autocomplete commands for 'help' command in debug console (achow101)
 - #10056 `e6156a0` [zmq] Call va_end() on va_start()ed args (kallewoof)
 - #10086 `7438cea` Trivial: move rpcserialversion into RPC option group (jlopp)
 - #10150 `350b224` [rpc] Add logging rpc (jnewbery)
diff --git a/_posts/zh_CN/pages/2016-01-13-supported-bips.md b/_posts/zh_CN/pages/2016-01-13-supported-bips.md
@@ -8,9 +8,9 @@ permalink: /zh_CN/bips/
 share: false
 version: 2
 ---
-比特币核心支持如下[BIPs][BIPS1]：
+比特币核心支持如下[BIPs][BIP1]：
 
 | BIP |Supported since| Title |
 |-----|---------------|-------|
 {% include pages/bips-list.md %}
-{% include _references.md %}
+{% include _references.md %}
diff --git a/_posts/zh_CN/pages/faq/2016-01-21-rbf-faq.md b/_posts/zh_CN/pages/faq/2016-01-21-rbf-faq.md
@@ -122,7 +122,7 @@ Peter最初的工作走的更远并且逻辑上导致了包含激励相容。因
 
 更别说，对交易费的可选择是否比非交易费可选择的对于欺骗性双重花费更有作用还是未知数，至少对于使用复杂工具的攻击者来说是这样的
 
-有些施行未确认可信赖度分析的组织已经明确地表示它们[已经准备好了][@BlockCypher 已经准备好了]， 如果有任何人意识到软件仍然需要改变，告知我们我们很乐意来帮忙
+有些施行未确认可信赖度分析的组织已经明确地表示它们[已经准备好了][blockcypher ready]， 如果有任何人意识到软件仍然需要改变，告知我们我们很乐意来帮忙
 
 [blockcypher ready]: https://twitter.com/BlockCypher/status/670334879565922304
 
diff --git a/_posts/zh_CN/posts/2016-06-08-version-bits-miners.md b/_posts/zh_CN/posts/2016-06-08-version-bits-miners.md
@@ -86,4 +86,4 @@ IsSuperMajority() 或其简写ISM，是一个历史遗留的软分叉触发器
 - <https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki>
 - <https://bitcointalk.org/index.php?topic=1067693.msg11446462#msg11446462>
 
-include _references.md %}
+{% include _references.md %}
diff --git a/_posts/zh_CN/posts/2016-08-23-release-0-13-0.md b/_posts/zh_CN/posts/2016-08-23-release-0-13-0.md
@@ -28,7 +28,7 @@ excerpt: 我们很高兴地宣布比特币核心0.13.0版本正式发布了
 - **为运行在ARM芯片组上的Linux操作系统开发的正式比特币核心二进制可执行文件** 让这些平台的用户能够使用预编译软件的优势，这些软件都是通过Gitian 确定性编译和多重证明过程保证的.
 
 
-比特币核心0.13.0版本所做更改的全面列表，请参阅 [版本发布声明][]. 上文罗列的改进点将在以下章节加以详细描述. 
+比特币核心0.13.0版本所做更改的全面列表，请参阅 [版本发布声明][release notes]. 上文罗列的改进点将在以下章节加以详细描述. 
 
 ## 隔离见证的准备工作
 
diff --git a/_posts/zh_CN/posts/2016-10-27-release-0.13.1.md b/_posts/zh_CN/posts/2016-10-27-release-0.13.1.md
@@ -17,6 +17,7 @@ excerpt: 我们很高兴地宣布比特币核心0.13.1版本正式发布了
 
 
 [版本发布说明]: /zh_CN/releases/0.13.1/
+[release notes]: /zh_CN/releases/0.13.1/
 
 
 我们很高兴地[发布]比特币核心 0.13.1的[版本发布说明]，该版本允许矿工们发布支持隔离见证（segwit）软分叉的信号并指明如果软叉被激活，
@@ -25,7 +26,7 @@ excerpt: 我们很高兴地宣布比特币核心0.13.1版本正式发布了
 
 segwit软分叉完全向后兼容所有比特币钱包，所以无论segwit是否激活，您都能继续安全地发送和接收比特币。如果您是一位矿工，且segwit看起来将激活，
 那您可能需要采取行动；对于所有其他比特币用户，无论现在或是将来您无需针对segwit采取任何行动。 
-然而，如果您想支持segwit或想了解segwit激活所导致的变化的更多细节，请参阅我们的[segwit升级指南][]。
+然而，如果您想支持segwit或想了解segwit激活所导致的变化的更多细节，请参阅我们的[segwit升级指南][segwit upgrade guide]。
 
 Segwit时间轴：
 
@@ -40,37 +41,37 @@ Segwit时间轴：
 
 如果segwit被激活，交易生成软件将能够从被txid覆盖的交易数据中分离（隔离）交易签名（见证）。这会带来几个直接的好处：
 
-1. 对使用隔离见证的交易来说，** [消除了不必要的交易可延展性][] **，使得编写比特币钱包软件更容易并简化比特币智能合约的设计。
+1. 对使用隔离见证的交易来说，** [消除了不必要的交易可延展性][elimination of unwanted transaction malleability] **，使得编写比特币钱包软件更容易并简化比特币智能合约的设计。
 
-2. ** [容量增加][] **允许区块保存比以前更多的交易。
+2. ** [容量增加][capacity increase] **允许区块保存比以前更多的交易。
 
-3. ** [基于对节点性能的影响衡量数据][] **以便允许矿工在区块中长期内不会降低节点性能的部分放置更多的数据。
+3. ** [基于对节点性能的影响衡量数据][weighting data based on how it affects node performance] **以便允许矿工在区块中长期内不会降低节点性能的部分放置更多的数据。
 
-4. ** [签名包括所花費的值][] **以减少安全签名生成器（例如硬件钱包）为创建安全签名所需要执行的步骤数。这使得开发硬件钱包更加容易，
+4. ** [签名包括所花費的值][signature covers value] **以减少安全签名生成器（例如硬件钱包）为创建安全签名所需要执行的步骤数。这使得开发硬件钱包更加容易，
 并能显著地提高现有硬件钱包的速度。
 
-5. ** [sighash的线性缩放操作][] **确保使用segwit的交易不会触发在2015年导致区块需要25秒来验证的问题。
+5. ** [sighash的线性缩放操作][linear scaling of sighash operations] **确保使用segwit的交易不会触发在2015年导致区块需要25秒来验证的问题。
 
-6. ** [增加多签名交易的安全性][] **使安全性从P2SH的大约80位提高到segwit的大约128位---对某些攻击来说安全了大约281万亿倍。
+6. ** [增加多签名交易的安全性][increased security for multisig] **使安全性从P2SH的大约80位提高到segwit的大约128位---对某些攻击来说安全了大约281万亿倍。
 
-7. ** [更高效的“类全节点”安全][] **允许那些愿意放弃一些安全保证的新开始节点无需下载每个区块的所有的数据即可构建一个准确的比特币分类帐副本。
+7. ** [更高效的“类全节点”安全][more efficient almost-full-node security] **允许那些愿意放弃一些安全保证的新开始节点无需下载每个区块的所有的数据即可构建一个准确的比特币分类帐副本。
 （这是一个由segwit实现的功能；Bitcoin Core 0.13.1中不包括。）
 
-8. ** [脚本版本化][] **允许用户分别选择今后在比特币脚本语言上所做的软分叉变更。
+8. ** [脚本版本化][script versioning] **允许用户分别选择今后在比特币脚本语言上所做的软分叉变更。
 
-有关上述每个优点的更多信息，请参阅下面的[segwit好处详解][]章节或本网站上篇幅更长、更加详细的[segwit好处常见问题][]页面。
+有关上述每个优点的更多信息，请参阅下面的[segwit好处详解][detailed segwit benefits]章节或本网站上篇幅更长、更加详细的[segwit好处常见问题][segwit benefits faq]页面。
 
-有关升级到segwit的更多信息，请参阅[segwit升级指南][]。
+有关升级到segwit的更多信息，请参阅[segwit升级指南][segwit upgrade guide]。
 
 
 
-## segwit好处详解
+## segwit好处详解 {#detailed-segwit-benefits}
 
 以下章节更详细地描述了上文所概述的特性。
 
 
 
-### 1.消除不必要的交易可扩展性{＃elimination-malleability}
+### 1.消除不必要的交易可扩展性 {#eliminate-malleability}
 
 隔离见证允许现有和升级的软件无需引用见证(签名)便可计算交易的交易标识符（txid）；交易标识符有时可由第三方（例如矿工）或共同签名人在多签名交易中更改。
 这解决了所有已知的不必要的交易可延展性的问题，这个问题令比特币钱包软件开发更困难，并使智能合约比特币的设计严重地复杂化。
@@ -115,7 +116,7 @@ Segwit时间轴：
 
 ### 7. 更加有效的“类全节点”安全性 {#more-efficient-security}
 
-Satoshi Nakamoto的[原始比特币文件][]描述了一种允许新启动的全节点跳过下载和验证来自受大量工作证明保护的历史块的一些数据的方法。
+Satoshi Nakamoto的[原始比特币文件][original Bitcoin paper]描述了一种允许新启动的全节点跳过下载和验证来自受大量工作证明保护的历史块的一些数据的方法。
 不幸的是，Nakamoto的方法不能保证使用这种方法新启动的节点将会生成比特币当前分类帐（称为UTXO集合）的精准副本，使得节点容易与其他节点不一致。
 
 虽然Nakamoto方法的问题不能在软分叉中解决，segwit实现了一个类似他原来建议的方法：节点在选择性地跳过下载一些区块链数据（特别是隔离的见证）
@@ -149,7 +150,7 @@ segwit不会对任何在segwit激活时不升级的人（除矿工以外）造
 没有发现一致性失误。
 
 
-    也是在2016年5月，二十位比特币核心开发者相聚[在瑞士][]亲自对segwit代码进行了（包括其他活动在内的）评审并确保有足够的测试覆盖面。
+    也是在2016年5月，二十位比特币核心开发者相聚[在瑞士][met in switzerland]亲自对segwit代码进行了（包括其他活动在内的）评审并确保有足够的测试覆盖面。
 
 - ** 2016年6月**完成segwit代码评审；几个经验丰富的比特币开发人员完成了他们的评审并表示支持segwit的代码更改。
 
@@ -181,7 +182,7 @@ segwit不会对任何在segwit激活时不升级的人（除矿工以外）造
 
 ## 结论
 
-有关在比特币核心 0.13.1中所做的所有更改的详细信息，请阅读[版本发布说明][]。请访问[下载页][]或[文件目录][]下载。
+有关在比特币核心 0.13.1中所做的所有更改的详细信息，请阅读[版本发布说明][release notes]。请访问[下载页][download page]或[文件目录][files directory]下载。
 
 
 比特币核心 0.13.1是0.13版本系列中规划的唯一软分叉版本。规划的下一个主要版本是比特币核心0.14.0，
diff --git a/_posts/zh_CN/releases/2016-10-27-release-0.13.1.md b/_posts/zh_CN/releases/2016-10-27-release-0.13.1.md
@@ -99,11 +99,11 @@ Segwit 软分叉的激活是用 BIP9 的 versionbits 来实施的。Segwit 的 v
 日启动之后，节点们就会在 2016 个区块算力重新调整期的开始的时候追踪区块支持 Segwit 的信号。当这两个礼拜的重新调整期内，有
 95%的区块发出信号支持 Segwit，这个软分叉就会被锁定。然后过了另外 2016 个区块后，Segwit 就会被激活。 
 
-如果你想获得关于 Segwit 的更多信息，请参阅 [Segwit FAQ][]，和 Segwit [钱包开发者指导手 册][]  或是 [141][BIP141], [143][BIP143],
+如果你想获得关于 Segwit 的更多信息，请参阅 [隔离见证的好处][Segwit FAQ]，和 Segwit [钱包开发者指导手 册][segwit wallet developers guide]  或是 [141][BIP141], [143][BIP143],
 [144][BIP144] 和 [145][BIP145]。
 如果你是个矿工或是矿池管理员，请看 [versionbits FAQ][] 来了解如何发布支持一个软分叉的信号。
 
-[Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
+[Segwit FAQ]: https://bitcoincore.org/zh_CN/2016/01/26/segwit-benefits/
 [segwit wallet developers guide]: https://bitcoincore.org/en/segwit_wallet_dev/
 [BIP141]: https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
 [BIP143]: https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki
diff --git a/_posts/zh_TW/pages/2016-01-13-supported-bips.md b/_posts/zh_TW/pages/2016-01-13-supported-bips.md
diff --git a/_releases/0.12.1.md b/_releases/0.12.1.md
@@ -69,6 +69,7 @@ This specific backport pull-request can be viewed at
 [BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki
 [BIP68]: https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki
 [BIP112]: https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki
+[BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki
 
 BIP68 soft fork to enforce sequence locks for relative locktime
 ---------------------------------------------------------------
diff --git a/_releases/0.14.0.md b/_releases/0.14.0.md
@@ -99,7 +99,7 @@ shows where each field has been moved to:
 `"blocks"`	   | `getblockchaininfo()["blocks"]`
 `"timeoffset"`	   | `getnetworkinfo()["timeoffset"]`
 `"connections"`	   | `getnetworkinfo()["connections"]`
-`"proxy"`	   | `getnetworkinfo()["networks"][0]["proxy"]`
+`"proxy"`	   | `getnetworkinfo()["networks"][0]["proxy"]` <!--skip-test-->
 `"difficulty"`	   | `getblockchaininfo()["difficulty"]`
 `"testnet"`	   | `getblockchaininfo()["chain"] == "test"`
 `"keypoololdest"`  | `getwalletinfo()["keypoololdest"]`
@@ -127,7 +127,7 @@ command without running the commands separately.
 The nested RPC commands use bracket syntax (i.e. `getwalletinfo()`) and can
 be nested (i.e. `getblock(getblockhash(1))`). Simple queries can be
 done with square brackets where object values are accessed with either an 
-array index or a non-quoted string (i.e. `listunspent()[0][txid]`). Both
+array index or a non-quoted string (i.e. `listunspent()[0][txid]`). <!--skip-test--> Both
 commas and spaces can be used to separate parameters in both the bracket syntax
 and normal RPC command syntax.
 
diff --git a/_releases/0.15.0.md b/_releases/0.15.0.md
@@ -329,7 +329,7 @@ Low-level RPC changes
 - #9853 `02bd6e9` Fix error codes from various RPCs (jnewbery)
 - #9842 `598ef9c` Fix RPC failure testing (continuation of #9707) (jnewbery)
 - #10038 `d34995a` Add mallocinfo mode to `getmemoryinfo` RPC (laanwj)
-- #9500 `3568b30` [Qt][RPC] Autocomplete commands for 'help' command in debug console (achow101)
+- #9500 `3568b30` [Qt] \[RPC] Autocomplete commands for 'help' command in debug console (achow101)
 - #10056 `e6156a0` [zmq] Call va_end() on va_start()ed args (kallewoof)
 - #10086 `7438cea` Trivial: move rpcserialversion into RPC option group (jlopp)
 - #10150 `350b224` [rpc] Add logging rpc (jnewbery)
