[elreq] Ethiopic Script Resources page (#135)

r12a has just created a new issue for https://github.com/w3c/elreq:

== Ethiopic Script Resources page ==
I'm hoping to publish a new FPWD called Ethiopic Script Resources, in line with all other scripts currently being worked on in our Language Enablement program. See a [list of documents](https://github.com/w3c/i18n-activity/wiki/LReq-documents). I wanted to bring your attention to this page in case you have any questions or comments. I hope to publish it on 23 July.

Going forward, all documents with a short name ending in -lreq (with an actual hyphen in the name) will be focused on a script, rather than a specific language. These -lreq docs point to requirements and script descriptions, tests, GitHub discussions, type samples, and more, organised by topic. The proposed Japanese page will, of course, point to jlreq, jlreq-d, simple-ruby, and any other relevant documents produced by the jlreq group, and can be viewed at:

https://w3c.github.io/jlreq/jpan/

The page is particularly useful for gap analysis work (bringing together many of the resources needed to create a gap report), and will be regularly updated as new resources become available. (Updates to discussions, tests, and type samples are updated automatically.)

In addition, these -lreq documents have a set of headings that are standardised across all other -lreq docs, as well as -gap documents, the Language Matrix, the Language Enablement Index, and the various GH issue labels in the many repos. That document structure has been applied to the Arabic, the Tibetan, and Mongolian layout requirements docs already. I plan to apply it also to the Korean and Ethiopic layout requirements docs, and at the request of the folks in the clreq group i'm working on restructuring the Chinese Layout Requirements along similar lines.

Please let me know if you have any comments or questions. Thanks.

Please view or discuss this issue at https://github.com/w3c/elreq/issues/135 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 July 2024 12:42:37 UTC