Skip to content
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

Support complex text layout (bidi, shaping, ordering) #2619

Open
18 tasks
bsweeney opened this issue Oct 27, 2021 · 2 comments · May be fixed by #2107
Open
18 tasks

Support complex text layout (bidi, shaping, ordering) #2619

bsweeney opened this issue Oct 27, 2021 · 2 comments · May be fixed by #2107

Comments

@bsweeney
Copy link
Member

bsweeney commented Oct 27, 2021

In order to correctly render text from some writing system (Arabic, Brahmic) the text must be processed for bidirectionality, shaping, and ordering. Because Dompdf lacks this functionality users must pre-process their text before feeding to Dompdf. In order to better support rendering in these writing systems Dompdf should come with support for this type of functionality baked in.

The totality of functionality required to fully support rendering in various languages is complex so this will be a parent ticket. Checklist items and child tickets will be added as we go.

Functional support:

Language support (when font with supporting glyphs is available):

@bsweeney bsweeney added this to the 2.0.0 milestone Oct 27, 2021
@bsweeney
Copy link
Member Author

The current library we're looking at utilizing for underlying functionality is tc-lib-unicode.

@bsweeney bsweeney linked a pull request Oct 27, 2021 that will close this issue
@bsweeney bsweeney modified the milestones: 2.0.0, 2.1.0 Nov 8, 2021
@bsweeney
Copy link
Member Author

Microsoft has decent reference documentation on features required for various languages: https://docs.microsoft.com/en-us/typography/script-development/use

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant