- From: Daniel Yacob <yacob@geez.org>
- Date: Wed, 13 Jan 2016 21:34:50 +0000
- To: "public-i18n-ethiopic@w3.org" <public-i18n-ethiopic@w3.org>
- Message-ID: <CACvO6KBuwQB5HNf6ezkjBX4Vo-LuQmjP7dT7AvS6S6azwpVyzA@mail.gmail.com>
Selam Berhanu and Elias, I've more or less completed an initial knowledge dump of the layout issues that I can think of. They are captured in the team document here: http://w3c.github.io/elreq/ (downloadable via github here: http://w3c.github.io/elreq/ ). I feel I am forgetting a few things that I won't recall until I re-experience them again, so I expect to add to it still. Presently the document aims to summarize layout topics and raise issues that would be answered via the survey that we've talked about. So it contains more questions than answers, but that is the goal pre-survey. Please add any additional topics that you can think of, and make any changes and corrections that you see are needed. It took me a month or more of almost daily use to really get comfortable with git and github so I understand it will a barrier. Contact me offline and I can assist and even serve as a proxy. Regarding the survey; following a wave of updates and refinements to the requirements page I'd like us to get back to forming the survey document. The "Issues" lists that you will find in most sections of the requirements document I intend to be used to pose survey questions. As you add new sections, please also add the questions that should be put to stakeholders on the topic. I expect we'll need lots of examples to go with the survey questions, be on constant watch for good samples to use. As I have time, I'll be working to further refine and organize the text of the document. Many sections will need clarification and overall coherence suffers at this early stage. Please let me know what sections are in need of clarification, as it may not be obvious to me. thank you, -Daniel
Received on Wednesday, 13 January 2016 21:36:08 UTC