fix escaping breaking out over line wrap

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96

[KyleMit]

Here's what the markdown is supposed to look like:

But here's what the same section looks like on the live docs site:

If we look at the markdown source, we can see the inline code block is opened on line 55 and then the text is automatically wrapped to fit into 80 character column width.

Which means whatever is converting the markdown to markup is not escaping the <pkg> tag on line 56 and opens up a tag that is never closed. Here's proof via inspect element on the live docs page:

Whatever script automatically wrapped at 80 chars may have caused other issues as well that only show up depending on the engine rendering the markdown

[Alhadis]

You know what's funny?

That page is still more readable than your ugly manpages. 😁

[kenany]

A fix for this already landed in release-next: #96

[zkat]

Closing as a duplicate of #96