<alolita> akshat: I'm Akshat Joshi I work at CDAC with Mahesh Kulkarni Some of the major work I've been working on is internationalization of domain names
<alolita> ... happy to be on this taskforce
<alolita> muthu: I'm Muthu Neduraman from Malaysia working on fonts for Indo-Chinese and Indic languages
<alolita> ... does Indo-Chinese include Tibetan
<alolita> ... do you know Javanese - No
<alolita> r12a: I'm Richard Ishida, W3C lead and particularly interested in typography outside the realm of fonts
<alolita> ... we will be involved in developing some of that information
<alolita> Neha: I'm Neha Gupta working at CDAC on NLP projects, keyboards for Indian languages, IDN
<alolita> ... Happy to be involved with this effort
<alolita> Vivek: I'm Vivek Pani working with internationalization and am getting involved with standardization again
<alolita> ... I'm interested in looking at font standardization
alolita: Involved in language tech for some years now - happy to see start of this work around indian languages
… v happy to have a diverse group here
… missing Anshu and Kalika
… I work on NLP and machines learning at Amazon
https://w3c.github.io/i18n-activity/guidelines/process.html
<alolita> r12a: We've been walking through the processes in the meeting which have developed over several years
<alolita> ... these tools have been used and let's learn these tools and processes to be effective
<alolita> ... does anyone have any questions
<alolita> ... i imagine the questions will come up as we make progress
Objective: discuss best ways to focus as a team to work on the first 3 language scripts - Devanagari, Tamil and Bengali. A transparent, iterative approach will all work done by the team hosted on GitHub would be ideal.
Requirements document template
https://w3c.github.io/iip/templates/lreq_doc/
Gap analysis template
https://w3c.github.io/iip/templates/gap-analysis
scribenick r12a
r12a: in the language matrix there are some typographic features on top - down the left hand side the scripts are ordered alphabetically by number of speakers is a list of languages
...
does the web work for that feature where are the gaps - where are the pain points
...
provide tests and pictures to provide where those parts are broken
...
In addition to that document (gap-analysis) we have the layout requirements doc e.g. if grapheme clusters are broken then outline gap in gap analysis doc and then add requirements as to how they should work in the Devanagari Layout requirements document
...
How should it work neutrally
...
the reqs doc should serve as a long-term reference
...
IIP will develop new docs which will replace the old existing ilreq doc We should use the old doc as a source where it has useful information but will create a new document
akshat: wr the color convention, sometimes it was tough to take a call
...
on syllable clusters is it a Unicode text segmentation is the text segmentation rule broken keep in mind:
r12a: does the web work for a user
...
In the Gap analysis doc we are looking to see if it is being described look at HTML and CSS specifications - verifying in the browser specs are the implementations out of sync in other cases - implementations may not be handling it the same way
alolita: Propose focus on deva, beng and taml at the start
… cdac has been working on gap analysis for other languages
… akshat & neha what are your thoughts on other languages?
akshat: initially planned 5 scripts, including guju and guru
… we have covered 3 scripts - currently working on 2 more
… the gap analysis doc has many different aspects - 20% of the subsections are still tbd
… we might need more perspective on how to flag issues
… looking for more advice from r12a to guide future working
neha: maybe by next week we'll have gap analysis docs for Tamil and XXX
alolita: we're leveraging some of the work that CDAC has already done
… you have seen the links to these documents
http://w3c.github.io/typography/gap-analysis/language-matrix.html
alolita: the idea was use that as a framework
https://w3c.github.io/iip/gap-analysis/deva-gap
alolita: what documents should we work on? should we work in parallel?
muthu: let's see what's available already, and fill that in first
… then in meetings we can look at additional features and decide how to work
… i think we can look at all three scripts for what has been done up to now
… then after that decide whether to work script by script
akshat: best to work on all three at same time - because other scripts can bring in perspectives that devanagari is missing
vivek: if we all know devanagari it might be good to focus on that
neha: i agree with akshat
alolita: listening to this, i like Muthu's idea of reviewing exising information across all 3 scripts
… then decide about how to move forward
… we can always tune the process based on what will work for all of us
Alolita: please everyone look at the documents that exist
… and review before we next meet
… also i'm thinking of a biweekly call to discuss docs and manage the work
… does that workf or everyone
all agree
Alolita: re: Time for call bi-weekly to accommodate others like Anshu
Muthu: flexible, in malaysia we work around the clock
Neha: 730am-7pm morning is ok, but not after 7pm
r12a: 6.30am ok
<Akshat> maybe i am not audible
<Akshat> i am ok with anything that works for majority
Action: Alolita to send out doodle poll for regular meeting times
alolita: Please all look at the repo
https://github.com/w3c/iip/
<Akshat> My audio dropped off... trying to connect...
Action: Alolita to send out doodle poll for regular meeting times
<trackbot> Created ACTION-4 - Send out doodle poll for regular meeting times [on Alolita Sharma - due 2018-04-20].