Restore code formatting lost from Tekton Pro Bold runs in docx#48
Merged
Conversation
Cross-referenced document_formatted.xml (the docx XML source) against the chapter markdown files to find words that were styled in Tekton Pro Bold in the original Word doc but lost their code formatting during the pandoc conversion. Wrapped those phrases in backticks (or the existing <code>/<var> equivalents where appropriate). Touches block names, menu/option labels, and identifier-style text across chapters 01, 02, 05-08, and 10-12. Bulk of the changes are in chapter 12 (UI elements: settings menu, cloud menu, context-menu options, sprite-corral options, watcher options, stage options). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
_support/conversion/document_formatted.xml(the original Word doc XML) against the chapter markdown files. Words/phrases styled in Tekton Pro Bold in the docx are the convention for inline code, but pandoc didn't preserve all of them in the conversion.<code>,<kbd>,<var>, fenced code blocks, MyST{…}directives, and URLs).What's affected
throw/catch,cascade,butfirst/bf,rational?/infinite?/numerator/real-part,case-independent comparisons,change by x: y:,distance to,move 100 steps,repeat 3,if/else,call w/continuation,split by blocks,my blocks,my categories,custom? of block,replace item,definition of, etc.Restore unsaved project,Costumes…/Backgrounds…/Sounds…,Login…/Signup…/Logout/Change password…,Language…/Zoom blocks.../Fade blocks…/Stage size…,Plain prototype labels,Thread safe scripts,HSL pen color model,script pic…/result pic…/scripts pic…,redrop/clean up/add comment/make a block…,delete/duplicate/export block definition…,slider min…/slider max…/raw data…/export…,parent…/pic…/svg…, etc.:::{index} \speak` block`).Italic and bold formatting from the docx came through pandoc cleanly, so no separate fix-up was needed for those styles — only the Tekton Pro Bold → backtick mapping required cleanup.
Test plan
throw/catchreferences were re-coded🤖 Generated with Claude Code