10
66
Fork
You've already forked fcft
14

Add UTF-8 versions of the rasterize functions #46

Open
opened 2022年02月05日 19:10:50 +01:00 by dnkl · 3 comments
Owner
Copy link

The API currently requires UTF-32 input. Converting from UTF-8 to UTF-32 is trivial, but tedious.

We can do this in fcft, making it easier for applications to render UTF-8 strings.

The API currently requires UTF-32 input. Converting from UTF-8 to UTF-32 is trivial, but tedious. We can do this in fcft, making it easier for applications to render UTF-8 strings.

wouldn't something like this require the dependency of utf8proc?

wouldn't something like this require the dependency of utf8proc?
Author
Owner
Copy link

No, that wouldn't be necessary, depending on what your requirements are. It's very easy to convert from UTF-8 to Unicode/UTF-32. It's also very easy to eliminate a large portion of invalid codepoints (large ranges defined to not map to any codepoints).

We wouldn't be able to guarantee the codepoints are valid. But then, that's not something we do in the current API; we expect the user to provide valid codepoints (at worst, we'll not find any glyphs).

No, that wouldn't be necessary, depending on what your requirements are. It's very easy to convert from UTF-8 to Unicode/UTF-32. It's also very easy to eliminate a large portion of invalid codepoints (large ranges defined to not map to any codepoints). We wouldn't be able to _guarantee_ the codepoints are valid. But then, that's not something we do in the current API; we expect the user to provide valid codepoints (at worst, we'll not find any glyphs).

What is the status on this?

What is the status on this?
Sign in to join this conversation.
No Branch/Tag specified
master
colrv1
releases/3.3
rasterize-utf8
spacing
releases/3.2
releases/3.1
releases/3.0
releases/2.5
releases/2.4
releases/2.3
releases/2.2
releases/2.1
releases/2.0
releases/1.0
3.3.3
3.3.2
3.3.1
3.3.0
3.2.0
3.1.10
3.1.9
3.1.8
3.1.7
3.1.6
3.1.5
3.1.4
3.1.3
3.1.2
3.1.1
3.1.0
3.0.1
3.0.0
2.5.1
2.5.0
2.4.6
2.4.5
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
2.3.3
2.3.2
2.3.1
2.3.0
2.2.92
2.2.91
2.2.90
2.2.7
2.2.6
2.2.5
2.2.4
2.2.3
2.2.2
2.2.1
2.2.0
2.1.3
2.1.2
2.1.1
2.1.0
2.0.0
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.1
1.0.0
0.4.3
0.4.2
0.4.1
0.4.0
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.0
0.1.1
0.1.0
0.0.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/fcft#46
Reference in a new issue
dnkl/fcft
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?