Skip to content

Try to handle "codepoints" instead of "characters". - #56

Merged
prepare merged 2 commits into
LayoutFarm:masterfrom
samhocevar-forks:support-surrogate-pairs
Oct 6, 2017
Merged

prepare merged 2 commits into
LayoutFarm:masterfrom
samhocevar-forks:support-surrogate-pairs

Conversation

@samhocevar

Copy link
Copy Markdown
Contributor

In many places, "char" is not a valid type to handle characters, because it
only supports 16 bits. In order to handle the full range of Unicode characters,
we need to use "int".

This allows characters such as 🙌 or 𐐷 to be treated as single codepoints even
though they are encoded as two "char"s in a C# string.

In many places, "char" is not a valid type to handle characters, because it
only supports 16 bits. In order to handle the full range of Unicode characters,
we need to use "int".

This allows characters such as 🙌 or 𐐷 to be treated as single codepoints even
though they are encoded as two "char"s in a C# string.
@samhocevar

Copy link
Copy Markdown
Contributor Author

Here is how the above sentence looked like:
image

This is how it is rendered now. Of course, the glyphs are still not found, but this is probably a necessary step:
image

@prepare

prepare commented Oct 6, 2017

Copy link
Copy Markdown
Member

@samhocevar

Thank you for the PRs

all are in my testing process

:)

@prepare

prepare commented Oct 6, 2017

Copy link
Copy Markdown
Member

Render with 'Century Normal'

09f8fcf

typo_codepoints

@prepare
prepare merged commit aa5ac96 into LayoutFarm:master Oct 6, 2017
@prepare prepare mentioned this pull request Oct 7, 2017
@samhocevar
samhocevar deleted the support-surrogate-pairs branch October 24, 2017 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants