This task should be the place for the final discussion and bike-shedding on names, locations and etc.
A few topics that warrant special attention:
Cursor geometry function
It currently accepts a key parameter that toggles the behaviour between two modes. I kept it this way because this is how it was, though I wonder if it makes more sense to just split it to two functions. cursor_behind_geometry_get and cursor_vertical_geometry_get. The names are bad, but just an idea to get your juices going.
Rename attributes to annotations
I called them attributes because we talked about it elsewhere and that's what people liked. Though things have changed a bit (the design of the interface) and it's really just about annotating the text now (by applying attributes). I'd suggest renaming it back to annotations.
We can't use the Efl.Text namespace because eolian blocks it (it doesn't need to, but this is an argument for another day), so it definitely needs to be moved. In addition, I don't think I like the name, so that needs to change too.
Make sure we are happy with the C function names (c_prefix)
As the title says, just need to make sure we set c_prefix where appropriate.
Efl2.Input.Text is still very raw and needs work.
Discussed separately in T8298
Efl2.Text.Content.Plain should be merged into Efl.Text
Unfortunately Efl.Text is already "stable" so it's something I can't change. So Efl2.Text.Content.Plain should be merged into that (just adds a few properties).
Efl2.Text.Content.Markup needs to be renamed.
Because of the former point, Efl2.Text.Content.Markup is now inconsistently named. It should be renamed to something else, maybe Efl.Text_Markup?
Efl2.Ui.Text has some naming related questions
As the title says, open this file and check the comments/FIXMEs.
Anyhow, the point of this ticket is to make sure people are happy with what's there. Especially from a consistency-with-the-rest-of-the-EFL perspective.