-
-
Notifications
You must be signed in to change notification settings - Fork 39
Add Rust stacked area chart rendering #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
shps951023
wants to merge
2
commits into
mini-software:main
from
shps951023:improve/auto-visual-parity-20260907
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
🔎 Supported by static analysis
🤖 get_repo_knowledge executed:
get_repo_knowledge mini-software/MiniPdf /tmp/coderabbit-repo-knowledge/mini-software-minipdf-2049b7d3/conventionsLength of output: 2945
🏁 Script executed:
Repository: mini-software/MiniPdf
Length of output: 14205
🏁 Script executed:
Repository: mini-software/MiniPdf
Length of output: 10203
🏁 Script executed:
Repository: mini-software/MiniPdf
Length of output: 12373
🏁 Script executed:
Repository: mini-software/MiniPdf
Length of output: 7603
🌐 Web query:
OpenType specification OTTO CFF FontFile3 CIDFontType0 PDF reference FontFile2 CIDFontType2💡 Result:
The terms mentioned relate to the technical intersection of OpenType font specifications and their embedding within PDF documents. OpenType Specification and 'OTTO' The OpenType specification defines a font file format that supports two primary outline technologies: TrueType (quadratic Bézier curves) and Compact Font Format (CFF) (cubic Bézier curves) [1][2]. An OpenType font file containing CFF data is identified by the 'OTTO' tag (the value 0x4F54544F) in the sfntVersion field of the font header [1][2]. PDF Embedding and FontFile Types The PDF specification (ISO 32000) defines mechanisms for embedding font programs into PDF files using FontFile entries within a FontDescriptor dictionary [3][4]. FontFile2 and CIDFontType2 FontFile2 is used for embedding TrueType-based fonts [5]. It is typically associated with a CIDFontType2 dictionary, which is used when the embedded font program contains a 'glyf' table (the standard TrueType outline table) [5]. FontFile3 and CIDFontType0 FontFile3 is a more versatile mechanism used for embedding font formats that are not natively represented by FontFile or FontFile2, such as CFF and OpenType [5][6]. - CIDFontType0: This refers to a CIDFont dictionary that uses CFF data [5][3]. - Subtypes for FontFile3: When embedding CFF-based fonts in PDF via FontFile3, the /Subtype entry can vary based on the data structure [5][6]: - /CIDFontType0C: Used for a bare CFF font program (not wrapped in an OpenType 'sfnt' structure) that contains CIDFont operators [5][6]. - /OpenType: Used when the entire OpenType font file (the 'OTTO' sfnt wrapper and its tables) is embedded [5][6]. This subtype can be used for CIDFontType0 dictionaries if the embedded CFF table within the OpenType file contains CIDFont operators [5][7]. In practice, some PDF consumers may require specific embedding strategies (e.g., stripping the OpenType wrapper to provide a bare /CIDFontType0C) to ensure consistent rendering across different PDF viewers due to how they interpret CID mappings [8][9].
Citations:
Make CFF support reachable and PDF-compatible.
font_supportsrejects theOTTOsignature before it checks for theCFFtable. Therefore, standalone OpenType CFF fonts cannot reach the CFF branch. The test uses a0x00010000SFNT signature and callsfont_has_subsettable_outlinesdirectly, so it does not cover this path. If CFF support is intended, acceptOTTOand emit CFF-compatible PDF objects instead of/FontFile2and/CIDFontType2. Otherwise, removeCFFfrom the supported-outline predicate and update the test.🤖 Prompt for AI Agents
Source: MCP tools