Export vector PDF pages: ink as paths, text as text, images as images - #95
Open
marcosqlbi wants to merge 1 commit into
Open
Export vector PDF pages: ink as paths, text as text, images as images#95marcosqlbi wants to merge 1 commit into
marcosqlbi wants to merge 1 commit into
Conversation
Page content gains Vector beside the exact picture. A vector page reuses the editable slide's elements, with the ink as strokes in their own z-order: each stroke is the sweep of the nib WPF uses, the convex hull of the nib at consecutive points joined into one path and filled once, so a translucent highlighter does not darken over itself. Text is laid out line by line in the language's font, wrapped at the container's width, and embedded as subsets of Segoe UI and Consolas read from the Windows fonts folder. The page stays sharp at any zoom and the code can be selected and copied. Co-Authored-By: Claude Fable 5.1 <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.
Why
Phase E4 of docs/export.md, on top of #94 (base is the E3 branch; retarget to
mainonce it merges). A picture page is exact but soft under zoom and dead to selection. A reader who wants to copy the DAX off a page, or print at any size, needs the text to be text and the ink to be paths.What it does
Where the code is
SQLBI.Whiteboard.Export/ExportPage.cs:SlideInkElement,SlideStroke,SlidePoint.PdfDocumentWriter: draws elements into the rectangle the picture would have used; the font resolver serves both families in four styles.EditableSlidebuilds strokes in z-order when asked;ExportSettingsand the dialog gain the page content choice.The smaller calls are under E4 in docs/export-decisions.md; decision 26 is updated.
🤖 Generated with Claude Code