Repository navigation
Document wptexturize() behavior in punctuation README - #31
Merged
Merged
Conversation
Adds a clarifying note explaining that WordPress core automatically transforms certain source punctuation into typographic equivalents in rendered post content via wptexturize(). This addresses a gap where the style guide's recommendations apply to source text but do not mention how that text is transformed when rendered.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I realised that there was a gap between what's recommended in the style guide vs. what's actually rendered in WordPress.
What changed
Adds a clarifying note to the punctuation section README explaining that WordPress core's
wptexturize()function automatically transforms certain source punctuation into typographic equivalents in rendered post content.Why
The current punctuation guidance recommends straight characters (apostrophes, quotation marks, etc.) but doesn't mention that
wptexturize()converts them to typographic equivalents in post titles, content, excerpts, and comments. This can be confusing for contributors who follow the style guide and then see different characters rendered to readers. The note adds context without changing any of the existing recommendations.Visual impact
N/A — documentation-only change.