-
Notifications
You must be signed in to change notification settings - Fork 14
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
Let's form a working-group to finish these documents #109
Comments
cc @khaledhosny |
cc @jfkthame |
cc @davelab6 |
How much overlap in scope is there between this proposition and what is being proposed in w3c/font-text-cg#11? Unless you have something else in mind than I read at first blush, it looks like this issue is probably a duplicate of that one and it would be better to discuss how the work gets organized over there. |
I don’t mind splitting the procedural discussion at w3c/font-text-cg#11 from this. But yeah, if possible, it may be easier for others to keep an eye on if we concentrate on as few as possible threads. Considering my bad productivity I can’t commit much time to this project, especially since I still need to work on the badly delayed font-side documentation, http://github.com/typotheque/text-shaping. But I’ll be happy to join any discussions. |
Happy to help as well. I'm terrible at technical writing but can help with contributing illustrations, code snippets, proof-reading, etc. |
@kalapi Always happy to have proofing! And illustrations! IDK about code snippets, since the mandate for this repo was to avoid stuff that could be cut-and-pasted without first being understood. BUT there are definitely a number of descriptions of algorithms and other such pseudo-code and I'm positive they would benefit from additional sets of eyes giving them scrutiny. |
I'm happy to offer time to finish these. We should use these as basis to replace the need for OpenType script specifications. Who can offer time? I can meet on video to discuss issues, and review changes.
cc @simoncozens @lianghai
The text was updated successfully, but these errors were encountered: