Skip to content

Make it easier (or document how) to bring your own harfbuzz/ICU #43513

@dnfield

Description

@dnfield

See #40220 (comment) for more context

Some customers would like to bring their own harfbuzz/ICU. Not clear if that would also require bringing their own freetype2. My own explorations around engine modularization have been more focused on networking and Skia - I'm not as famiilar with what it would take to split out some of the text rendering stack (or whether it would actually help things binary size wise).

/cc @jason-simmons @GaryQian who know a lot more about this area.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: existing-appsIntegration with existing apps via the add-to-app flowa: sizeReducing IPA/APK/JS sizesa: typographyText rendering, possibly libtxtc: new featureNothing broken; request for a new capabilityc: performanceRelates to speed or footprint issues (see "perf:" labels)d: api docsIssues with https://api.flutter.dev/engineflutter/engine related. See also e: labels.perf: app sizePerformance issues related to app size (binary/code size) or disk spaceteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions