-
Notifications
You must be signed in to change notification settings - Fork 25.6k
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
Using title_separator: "|", page title doesn't display correctly #760
Comments
I haven't tested this yet, but this could be related to YAML. I know you can use stats: |
65 Home Runs
0.278 Batting Average Perhaps it's ignoring |
Did some testing and it does seem like YAML or Liquid or Jekyll is removing the vertical pipe title_separator: "|" Will give you something like: <title>Welcome to Jekyll | Minimal Mistakes</title> |
+1. Thanks! I was going to try an HTML entity next. Thanks for checking this out so quickly.
… On Jan 9, 2017, at 9:09 PM, Michael Rose ***@***.***> wrote:
Did some testing and it does seem like YAML or Liquid or Jekyll is removing the vertical pipe |. What you can do instead is declare it as a HTML entity and then it'll work.
title_separator: "|"
Will give you something like:
<title>Welcome to Jekyll | Minimal Mistakes</title>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
bundle update
.bundle exec jekyll build
.Environment informations
github-pages
orjekyll
gem version: Jekyll gem 3.3.1, Ruby 2.4Expected behavior
Expected to see the "|" character display as a separator in the page breadcrumb path when bookmarking in my browser. What appears instead is a blank space.
Steps to reproduce the behavior
_config.yml
, add this line:title_separator: "|"
bundle exec jekyll serve
and open browser tolocalhost:4000
Interestingly, if I pick a character other than
"|"
as the title separator, the feature works as expected. E.g.title_separator: "•"
workstitle_separator: "&&"
workstitle_separator: "|"
:-(The text was updated successfully, but these errors were encountered: