Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
git-svn(zh_HANS-CN): avoid bogus
file://
link
The way the description is currently written, there is no space after the `file://` in the translation, even if there is a space there in the original. This is important because the way AsciiDoc is parsed, a missing space will mistake the text for being an actual hyperlink, see e.g.: https://github.com/jnavila/git-html-l10n/blob/171352a71363/zh_HANS-CN/git-svn.html#L1198 At the time of writing, this bogus link can be experienced here: https://git-scm.com/docs/git-svn/zh_HANS-CN#git-svn-svn-remoteltgtrewriteRoot However, the "domain name" is quite bogus seeing as it reads, according to Bing Translate: access), but want to publish in metadata with public which is obviously not a valid domain name. Firefox is smart enough to realize that this is not a valid domain name, and "auto-fixes" it to `file:///`. However, Edge (and therefore most likely Chrome, too), as well as link checkers such as Lychee (https://lychee.cli.rs/) translate this into an internationalized domain name starting with the "ASCII-Compatible Encoding" prefix "xn--" (see https://en.wikipedia.org/wiki/Internationalized_domain_name) and is immediately followed by a closing parenthesis, which is not a valid character in internet host/domain names, but at least Lychee tries to follow it nevertheless: file://xn--),-ry2c56bzyech9a071b11ispsycrp191dutgptg8hx808c0kpb/ Let's clearly separate `file://` from the next word and avoid letting AsciiDoc mark this as a hyperlink. Signed-off-by: Johannes Schindelin <[email protected]>
- Loading branch information