Skip to content
This repository has been archived by the owner on Aug 8, 2022. It is now read-only.

docs: update blod symbols #49

Closed
wants to merge 12 commits into from
Closed

docs: update blod symbols #49

wants to merge 12 commits into from

Conversation

veaba
Copy link
Member

@veaba veaba commented Sep 14, 2020

  • 全局更新,将冒号迁移到加粗符号右侧,这个更新来自,wiki 关于加粗和斜体格式的约定
    • 理由是:当加粗段落最后一个是等时候,markdown 将无法渲染,必须 最右侧的**右侧的汉字有一个空格。
    • 为了与此前的都协调,现作出变更,统一将逗号,句号,冒号都移到右侧。

如下所示:

- **你好,**世界   // 失败
- **你好,** 世界  // 成功
- **你好**,世界   // 成功
--------------
- **你好。**世界  // 失败
- **你好。** 世界 // 成功
- **你好**。世界  // 成功
--------------
- **你好:**世界  // 失败
- **你好:** 世界 // 成功
- **你好**:世界  // 成功

效果截图将如下:
image

@veaba veaba mentioned this pull request Sep 14, 2020
@veaba veaba requested review from Jinjiang and Justineo September 15, 2020 07:07

在挂载开始之前被调用:相关的 `render` 函数首次被调用。

**该钩子在服务器端渲染期间不被调用。**
**该钩子在服务器端渲染期间不被调用**。
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Justineo 这里我想稍微发起一个小讨论,比如这个 case 里,标点符号写在星号里面似乎不影响解析和渲染,这种情况下我们是否需要刻意并统一把标点符号移到外部?
谢谢

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Justineo 这里我想稍微发起一个小讨论,比如这个 case 里,标点符号写在星号里面似乎不影响解析和渲染,这种情况下我们是否需要刻意并统一把标点符号移到外部?
谢谢

我也遇到过这个问题,如果右边没有汉字的话,似乎是可以考虑含盖在里面,这似乎影响不大。

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

我个人建议在 markdown 解析出现问题的情况下再调整标点符号的位置。因为:

  • 由于 markdown 本身语法的关系,这里要么是渲染不正确,要么是对原文产生了细微的调整 (即便是少强调了一个标点符号)。两者都应该尽量避免。
  • 而且为了统一格式把整句话留一个标点符号在星号外面确实很奇怪,一定会引发更多的讨论和争议。

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

我个人建议在 markdown 解析出现问题的情况下再调整标点符号的位置。

赞同。

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

讨论已有结果,参见:#78

@veaba
Copy link
Member Author

veaba commented Sep 22, 2020

经过#78 讨论,将放弃 该 PR 的更改,现将 close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants