Repository navigation
Add an editable Arabic and English invoice with included fonts - #75
Merged
Merged
Conversation
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.
Add a runnable Arabic and English invoice with its Noto Sans Arabic regular and bold fonts included. The guide explains logical Unicode text, font registration, RTL blocks, and isolating dates and references; readers can edit the JSON data, CSS, and HTML structure in the download.
The sample requires Fullbleed 2.5.14, which fixes the styled bidi and Unicode-map issues found while building it. It includes a one-page PDF, native and PDFium previews, font provenance and OFL notices, a deterministic ZIP manifest, and retained verification results.
The actual ZIP passed 67 checks against the final 2.5.14 wheel: both reader outputs, embedded fonts, exact-input replay, guide execution, edited data and theme, amount calculation, escaping, and explicit failures for missing glyphs or changed font files. Both final previews were visually inspected. New Windows/Linux jobs require the public package and reproduce the ZIP before checking it. All existing documentation checks remain required for deployment.
The guide documents reader differences and avoids a general language-coverage or standards-conformance claim.