10
66
Fork
You've already forked fcft
14

Expose text run direction? #26

Open
opened 2021年05月05日 12:39:22 +02:00 by dnkl · 1 comment
Owner
Copy link

Should we expose the direction in struct fcft_text_run?

Since you can feed any kind of mixed LTR/RTL strings to fcft_text_run_rasterize(), and fcft will typically be able to emit something that appears sane, you can technically have both LTR and RTL in the same text run.

So, should we expose a single direction for the entire run? Which one? The first one detect?

Or do we add an array? Kind of like the cluster array. Here, we'd map cluster ranges to LTR/RTL.

Should we expose the direction in `struct fcft_text_run`? Since you can feed any kind of mixed LTR/RTL strings to `fcft_text_run_rasterize()`, and fcft will typically be able to emit something that appears sane, you can technically have both LTR and RTL in the same text run. So, should we expose a single direction for the entire run? Which one? The first one detect? Or do we add an array? Kind of like the `cluster` array. Here, we'd map cluster ranges to LTR/RTL.
dnkl added this to the 2.4 milestone 2021年05月05日 12:39:22 +02:00
Author
Owner
Copy link

Let's hold off for a while with this one. I want to see some usage of the new API first.

Let's hold off for a while with this one. I want to see some usage of the new API first.
dnkl removed this from the 2.4 milestone 2021年05月07日 11:06:56 +02:00
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
1 participant
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#26
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?