-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hexo渲染的博客文章会将类似于 的符号,并不会处理显示为空格,而是以字符的形式显示出来/Blog posts rendered by hexo will display symbols similar to   instead of being displayed as spaces, but as characters #4946
Comments
The https://github.com/hexojs/hexo-util/blob/master/lib/escape_html.js |
git clone [email protected]:volantis-x/community.git && cd community
git reset --hard b96c4289a1833260acfe8252f5cd21bd4fa862d3
git submodule update --init
npm i && hexo s |
git clone [email protected]:volantis-x/community.git && cd community
git reset --hard 54d3585f0fc4dbe44c7935f84429e5268612a8b6
git submodule update --init
npm i && hexo s |
What is the difference between b96c4289a1833260acfe8252f5cd21bd4fa862d3 and 54d3585f0fc4dbe44c7935f84429e5268612a8b6 ? |
May be hexo-renderer-ejs or hexo-renderer-marked or hexo |
确认了 hexo-renderer-marked@4 是正常的 hexo-renderer-marked@5 渲染异常 |
It is indeed possible, thank you for your reply, I will think about it again |
原来如此,这是好早之前的问题了,那一天更新后开始出现。 |
Caused by hexojs/hexo-renderer-marked@9e1c7ad Fixed in hexojs/hexo-util#328 |
Check List
Please check followings before submitting a new issue.
hexo version
to check)Expected behavior
markdown文章中输入类似 的符号在部署后会显示为空格。
Symbols like  entered in markdown articles will be displayed as spaces after deployment.
Actual behavior
markdown文章中输入类似 的符号在部署后会显示为 
Symbols like  entered in markdown articles will be displayed as  after deployment
How to reproduce?
Is the problem still there under "Safe mode"?
Environment & Settings
Node.js & npm version(
node -v && npm -v
)Your site
_config.yml
(Optional)Hexo and Plugin version(
npm ls --depth 0
)Your package.json
package.json
Others
The text was updated successfully, but these errors were encountered: