Date: Wed, 16 Feb 2022 21:25:10 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 262001] "_italic_" doesn't render as HTML italic when immediately followed by another "_" Message-ID: <bug-262001-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262001 Bug ID: 262001 Summary: "_italic_" doesn't render as HTML italic when immediately followed by another "_" Product: Documentation Version: Latest Hardware: Any URL: https://docs.freebsd.org/en/books/porters-handbook/fla vors/#flavors-using, https://docs.asciidoctor.org/asciidoc/latest/text/trou bleshoot-unconstrained-formatting/ OS: Any Status: New Severity: Affects Some People Priority: --- Component: Documentation Assignee: doc@FreeBSD.org Reporter: pauamma@gundo.com As evidenced by the list in section 7.2.1 of the Porter's Handbook (https://docs.freebsd.org/en/books/porters-handbook/flavors/#flavors-using), the AsciiDoctor toolchain doesn't translate _flavor__CONFLICTS to <em>flavor</em>_CONFLICTS as expected. AllanJude mentioned https://docs.asciidoctor.org/asciidoc/latest/text/troubleshoot-unconstrained-formatting/ in IRC, and I think the start of that section says __flavor___CONFLICTS should work. In other words, when there's a _ immediately after the end marker, wrap the text inside __...__ instead of _..._. This seems to also apply to *...*_ sequences, which should be **...**_ instead. This may affect the web pages as well as the documentation itself, and should IMO be documented in the FDP primer for future-proofing. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262001-9>