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

Spec markup: carriage return symbol on carriage returns in markdown text #371

Closed
srawlins opened this issue Oct 12, 2015 · 1 comment
Closed

Comments

@srawlins
Copy link
Contributor

In the links section, see example 448 and example 455. The spec discusses in 448 that destinations can't contain line breaks. But it looks like 455 does contain a line break. On second look, its probably that the line is wrapped.

Can the spec portray line breaks with a carriage return symbol maybe, on the left-hand Markdown texts when a newline exists? Similar to the muted bullets that exist to depict space characters.

@jgm
Copy link
Member

jgm commented Oct 12, 2015

+++ Sam Rawlins [Oct 12 15 07:49 ]:

In the links section, see [1]example 448 and [2]example 455. The spec
discusses in 448 that destinations can't contain line breaks. But it
looks like 455 does contain a line break. On second look, its probably
that the line is wrapped.

Yes, it's soft-wrapped. We have css

pre { white-space: pre-wrap }

Can the spec portray line breaks with a [3]carriage return symbol
maybe, on the left-hand Markdown texts when a newline exists? Similar
to the muted bullets that exist to depict space characters.

That's a possibility, but it's important to maintain
cut-and-pasteability, and it would clutter up the visuals.

Other options I can think of:

  • using a shorter example to avoid soft-wrapping
  • using different CSS so a scroll-bar is created in this
    case

Not sure what is best, but thanks for pointing out the issue.

@jgm jgm closed this as completed in ef93684 Dec 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants