Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Bold/emphasis fails when closing delimiter is preceded by a closing bracket and followed by a non-punctuation character

Aperta
  • Qualcosa non va?
#840 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation

Direzione di ricerca

Start with CommonMark spec §6.2 and reproduce the examples using the GitHub Markdown API command in the issue. Compare the delimiter rules for closing punctuation against the listed expected and actual results. Done means reaching agreement on the proposed Unicode Pe rule and updating the relevant specification behavior and coverage.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Strong emphasis (bold) is not rendered when a ** closing delimiter is
immediately preceded by a closing bracket (e.g. ), ], ") and followed
by a non-punctuation, non-whitespace character such as a letter or digit.

Reproduction

Verified on GitHub.com via the Markdown API:

curl -s -X POST \
  -H "Content-Type: application/json" \
  -d '{"text": "**)**a\n", "mode": "gfm"}' \
  https://api.github.com/markdown
# => <p>**)**a</p>   ← not bold
Input Expected Actual
**)**a **)**a (bold) **)**a (literal)
**)**1 **)**1 (bold) **)**1 (literal)
**]**a **]**a (bold) **]**a (literal)
**"**a **"**a (bold) **"**a (literal)
**)**! )! (bold) ✅ correct
**)** a )·a (bold) ✅ correct (with space)

Root Cause

The CommonMark spec §6.2 defines a right-flanking delimiter run as:

(1) not preceded by Unicode whitespace, and
(2a) not preceded by a Unicode punctuation character, OR
(2b) preceded by a Unicode punctuation character AND followed by
Unicode whitespace or a Unicode punctuation character.

For **)**a, the closing ** has:

  • before = ) → unicode.IsPunct = true
  • after = a → neither whitespace nor punctuation

Applying the rule:
!false && (!true || false || false) = false
→ The closing ** is not right-flanking → bold is not rendered.

Why this is a spec issue

Closing brackets (Unicode category Pe: ), ], }, ", », etc.)
are punctuation by Unicode definition, yet they are semantically
word-terminating — the character following them is logically separate
from the bracketed content. The current rule treats them the same as
opening punctuation like ( or ", which causes the asymmetry:

**(note)**  is bold   ✅  (after = space)
**(note)**. is bold   ✅  (after = punctuation)
**(note)**a is NOT    ❌  (after = letter)

This is counterintuitive: a user writing see **(RFC 9110)**section 5
would reasonably expect bold to apply.

Suggested fix

Amend condition (2b) to exclude closing punctuation (Unicode category Pe)
from the "preceded by punctuation" restriction:

(2b) preceded by a Unicode punctuation character other than a closing
bracket (category Pe), AND followed by Unicode whitespace or
a Unicode punctuation character.

Or equivalently: treat Unicode Pe characters as non-punctuation for the
purpose of the right-flanking delimiter rule only.

References

Lingua principale
Python
Stelle
5.2k
Fork
360
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di commonmark/commonmark-spec

Tutte le issue di commonmark/commonmark-spec

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.