Skip to content
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

<foo>'s <bar> is a sentance that doesn't render correctly #1514

Open
ge0ffrey opened this issue Oct 15, 2015 · 1 comment
Open

<foo>'s <bar> is a sentance that doesn't render correctly #1514

ge0ffrey opened this issue Oct 15, 2015 · 1 comment
Milestone

Comments

@ge0ffrey
Copy link

Try this line:

   `<foo>`'s `<bar>` is a sentance that doesn't render correctly

The code style spans from foo to bar, instead of rendering 2 separate code style spans.

@mojavelinux
Copy link
Member

The only way to fix this right now is to double up the backticks on the first instance (because of the trailing single quote).

``<foo>``'s `<bar>`

It's close to impossible to fix this until we switch to an inline parser. There's just no way the current regex-based parsing can detect these scenarios without lots and lots of passes over the text. We basically have tricks in place to handle the most blatant situations, but that's really just to tide us over until we can parse in a more intelligent way. Hence the relationship to #61.

@mojavelinux mojavelinux added this to the v2.0.0 milestone Oct 15, 2015
@mojavelinux mojavelinux modified the milestones: v2.0.0, M1 Mar 13, 2019
EliasZ added a commit to EliasZ/spring-cloud-kubernetes that referenced this issue Jan 5, 2023
ryanjbaxter pushed a commit to spring-cloud/spring-cloud-kubernetes that referenced this issue Jan 5, 2023
TurekBot pushed a commit to TurekBot/jenkins.io that referenced this issue Oct 25, 2023
The code formatting was broken when the backtick was immediately
followed by an apostrophe.

It looks like this is a known issue with asciidoc and the workaround is
to double up the backticks.

Refs: asciidoctor/asciidoctor#1514
TurekBot added a commit to TurekBot/jenkins.io that referenced this issue Oct 25, 2023
The code formatting was broken when the backtick was immediately
followed by an apostrophe.

It looks like this is a known issue with asciidoc and the workaround is
to double up the backticks.

Refs: asciidoctor/asciidoctor#1514
MarkEWaite added a commit to jenkins-infra/jenkins.io that referenced this issue Nov 1, 2023
* docs: add missing "as"

* docs: replace hyphens masquerading as em dashes

Refs: https://www.thepunctuationguide.com/em-dash.html

* docs: allow diagram to be opened full screen

* docs: add missing comma

* docs: fix code formatting next to apostrophe

The code formatting was broken when the backtick was immediately
followed by an apostrophe.

It looks like this is a known issue with asciidoc and the workaround is
to double up the backticks.

Refs: asciidoctor/asciidoctor#1514

* docs: restore missing callout number

* Do not link to the image

Co-authored-by: Kevin Martens <99040580+kmartens27@users.noreply.github.com>

---------

Co-authored-by: Mark Waite <mark.earl.waite@gmail.com>
Co-authored-by: Kevin Martens <99040580+kmartens27@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants