Add folio v0.9.1 bindings and rebuild native libraries#6
Merged
Conversation
Bind the five C ABI functions added since the v0.7.1 engine (folio v0.8.0– v0.9.1) and surface them in the public API: - folio_document_set_language -> Document.Builder.language(String) - folio_font_parse_for_language -> Font.parseForLanguage(byte[], String) - folio_paragraph_measure_lines -> Paragraph.measureLines(double) - folio_paragraph_measure_height-> Paragraph.measureHeight(double) - folio_paragraph_split_after_line -> Paragraph.splitAfterLine(int, double) returning Paragraph.Split(head, tail) Bump build-natives.yml to Go 1.25 (required by folio v0.9.1). Add Folio091BindingsTest covering all five. Native libraries are rebuilt from folio v0.9.1 in a follow-up commit.
Rebuild the five bundled native libraries against the folio v0.9.1 engine so the SDK ships the 0.8.0/0.9.0/0.9.1 fixes (border-radius, paged media, list pagination + counters, table rowspan, QR encoder, shaping) and exposes the five new C ABI symbols the bindings depend on. macos-aarch64, linux-x86_64, linux-aarch64, windows-x86_64 are built by the build-natives workflow (Go 1.25); macos-x86_64 is cross-compiled locally (clang -arch x86_64) and verified to carry the new symbols.
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
1 participant
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
Bumps the bundled folio engine v0.7.1 → v0.9.1 and binds the five new C ABI functions added across folio 0.8.0/0.9.0/0.9.1. Targets SDK release 0.3.0.
New bindings + public API
folio_document_set_languageDocument.Builder.language(String)folio_font_parse_for_languageFont.parseForLanguage(byte[], String)folio_paragraph_measure_linesParagraph.measureLines(double)folio_paragraph_measure_heightParagraph.measureHeight(double)folio_paragraph_split_after_lineParagraph.splitAfterLine(int, double)→Paragraph.Split(head, tail)After this,
FolioNativebinds 393/393 of the v0.9.1 C ABI (100% coverage). The C ABI grew by exactly these 5 between v0.7.1 and v0.9.1 — everything else in those releases was engine bug fixes (shipped via the rebuilt native lib) or Go-only surface.Native libraries
All five rebuilt from folio v0.9.1, so the SDK ships the 0.8.0/0.9.0/0.9.1 engine work (border-radius,
@page/position:fixed/margin boxes, list pagination + multi-level CSS-counter numbering, table rowspan, scannable QR encoder, shaping fixes).build-natives.ymlbumped to Go 1.25 (required by folio v0.9.1). macOS x86_64 was cross-compiled locally (clang -arch x86_64) to avoid a stuck Intel runner; the other four are from the build-natives workflow. All five verified to carry the new symbols.Tests
Folio091BindingsTestcovers all five new methods (language metadata, parse-for-language face selection, measure lines/height, split head+tail). Full suite green locally against the v0.9.1 macOS lib.Notes
[0.3.0]added.