- From: r12a <ishida@w3.org>
- Date: Thu, 24 May 2018 07:06:16 +0100
- To: indic <public-i18n-indic@w3.org>
https://www.w3.org/2018/05/22-ilreq-minutes.html
text extract follows:
– DRAFT –
India International Program Teleconference
22 May 2018
[2]IRC log
[2] https://www.w3.org/2018/05/22-ilreq-irc
Attendees
Present
Akshat, Alolita, Muthu, Neha, r12a, Vivek
Regrets
Chair
Alolita
Scribe
Akshat
Contents
* [3]Meeting Minutes
1. [4]Actions
2. [5]InfoShare
3. [6]Devanagari Gap Analysis
* [7]Summary of Action Items
Meeting Minutes
scribenick Akshat
alolita: last time plan was to look at deva beng and tamil
… links are already shared on agenda.... vivek muthu u got a
chance to take a look at it?
Richard should we just walk thru documents? What is the flow to
be followed?
richard: As you see fit....maybe as per your agenda topics...
alolita: i will go thru the agenda...
Actions
<r12a> [8]https://www.w3.org/International/groups/indic-layout/
track/actions/open
[8]
https://www.w3.org/International/groups/indic-layout/track/actions/open
<r12a> Pipeline: [9]https://github.com/w3c/iip/projects/1
[9] https://github.com/w3c/iip/projects/1
first item was actions open...
... there were two actions against me.... look who all can
additionally participate
... akshat neha you had suggested to add some names.. so had
vivek....
Vivek: shall i suggest names?
alolita: I will follow up with you...
… other agenda items were MD Kulkarni to suggest some more
folks involved?
InfoShare
Akshat: No we could not get change to talk to him... will
update in next meeting...
alolita: sure... any other agenda items?
richard: had agenda item to widen number of participants...
… south east asean Task force was set up differently... we
wanted more participation...
… they were to discuss things on github... and eventually they
may form a document...
… i would be monitoring their activity...
… other was Japanese layout task force...
… idea was to get more people... in terms of eyes to loook at
it and provide feedback....
alolita: idea seems to be good... i have a few questions on
expert network of SEA team
… 1. Is it because of there is not enough mass involved or
priorities are higher over there?
richard: couple of things... we wanted to have more people
involved...
…
… we were finding that people were a bit timid to contribute
due to lack of exp with W3C... they were a bit busy as well...
alolita: so it is more passive way of interaction?
richard: well... yeah... they may contribute in terms of
reviews but not document....
alolita: what are views of the group?
… there are couple of things that concern me...
… as per my exp in working with open source...
… it may become a become noisy...
muthu: I kind of agree... it does create a noise sometimes and
causes discomfort to discussions...
alolita: that is my concern... yes...
… github is quite open platform and if we do not respond it
appears that we do not respond enough...
richard: people can anyway contribute to github...
vivek: i agree with muthu...
… lets get some work going and then see if we need to involve
more people...
… smaller action items might help... people take ownership of
them and get them through...
alolita: i would like to see active backlog maintained...
richard: agree....
… one more thing... in the past notifications came to the
list...
… iip repo...
… now we have ability to mark css etc related issues as well...
alolita: that is great thing to have...
richard: I have done it for css, html, ttml... if you want me
to add more... let me know
alolita: sure.. we can see as we go ahead...
… anything else?
… can we have a walk through with the devanagari document?
… some of the links are still pointing to some other pages...
richard: sure.. these are your documents... you can edit
them...
alolita: ok section 1...introduction...
Devanagari Gap Analysis
<r12a> Objective: For sections 1-3, read and identify missing
parts, provide feedback for discussion
<r12a> Devanagari Gap-Analysis: [10]https://w3c.github.io/iip/
gap-analysis/deva-gap.html
[10] https://w3c.github.io/iip/gap-analysis/deva-gap.html
vivek: may we should not read through.... many have read
them...
alolita: that is fine...
vivek: i did not find them wrong... but needs some additions..
muthu: (some question... how to do this maybe...)
muthu: how other scripts did it? how info was collected?
… i was looking at tamil document....
richard: there are two documents...
… the categories were developed by me...
… we can add categories....but we should go with the headings
which are linked to the systems which produce output
automatically...
… maybe akshat and neha can add something more to that...
alolita: since C-DAC has done initial work... we can base our
work on that...
<r12a> akshat: initially the devanagari document had some info
- we went through headers - we talked to language
representatives and checked web platform specs for mentions
<r12a> ... this reveals whether the issue is just
implementation related or a breaking change
<r12a> ... one tricky item is how to find features in the whole
w3c stack, but sometimes tests helped
<r12a> [11]https://www.w3.org/International/tests/
[11] https://www.w3.org/International/tests/
neha: we went through corpus...and consulted with internal
language experts...
Akshat: we went through the tests to see if a particular
feature is part of the recommendations...
alolita: can we know where are those tests... and who wrote
them
richard: [12]https://www.w3.org/International/tests/
… i wrote them
[12] https://www.w3.org/International/tests/
vivek: can we get reference to where is the source of
information?
neha: we can try to provide links... image support is
needed....
alolita: we can use github...
richard: in this discussion we can also start raising issues
here....
… eg. muthu talked about tamil numerals.. we can have this
issue raised and get that going... we need not wait for call...
<everyone agrees>
... i agree with vivek... we need more links... need more tests
as well... making tests can also be part of this work
... having more evidences always helps...
alolita: any comments?
… feel free to ask as we go along...
richard: guys can point to specs as well
akshat: richard can you please help us with how to navigate
around specs...
<r12a> [13]http://w3c.github.io/typography/
[13] http://w3c.github.io/typography/
richard: you can ask me.... e.g. there is an index for css
spec...
<discussions around drafts and actual specs...>
vivek: i had some questions...
… because this is devanagari.... i do not see language
representation....
… certain behaviours related to punctuations....
… e.g. hindi and kashmiri behave distinctly...
richard: if there are large number of differences.. we can
create different docs...
… but if they are small..we can list them here... in the same
document....
… gap analysis is just pointing to things that do not work...
… requirements document is more oriented towards the
punctuations query...
vivek: i got the answer.... this broadly caters to all the
languages... for specific different feature... it can be
mentioned separately...
… one of the additional comments i had was about encoding
considerations...
… when scripts cuts across languages.. it becomes hard for font
makers....
… second is: glyph control.... there has been some effort in
defining orthography...
… there is no definition of appropriate glyph set....
alolita: in gap analysis it is partly captured...
vivek: i would be happy to come with a document listing these
things...
richard: i think we better do it by raising issues....
muthu: i agree with vivek.... the challenge for font developers
is to decide what all half and full forms to add in fonts...
vivek: yes agree muthu.... there is no document that says how
exactly design a font in terms of glyph sets....
alolita: as we go through these sections, we can have a common
understanding...
vivek: i would be happy to list issues... how to do that?
<r12a> [14]https://github.com/w3c/iip/issues
[14] https://github.com/w3c/iip/issues
richard: we can do it here...
… [15]https://github.com/w3c/iip/issues
… we should keep issues to one particular thing....rather than
mixing them up...
… we can have discussions around that...
[15] https://github.com/w3c/iip/issues
vivek: it seems to be a good way forward...
richard: we can refine it as we go ahead...
alolita: yes it will help a lot.... we are still warming up...
richard: yea.. we want most of the issues...
<r12a> [16]https://rawgit.com/w3c/iip/r12a-taml-quotations/
gap-analysis/taml-gap.html#quotations
[16]
https://rawgit.com/w3c/iip/r12a-taml-quotations/gap-analysis/taml-gap.html#quotations
richard: i have just raised question about tamil quotations...
… [17]https://rawgit.com/w3c/iip/r12a-taml-quotations/
gap-analysis/taml-gap.html#quotations
… we need discussions around it...
[17]
https://rawgit.com/w3c/iip/r12a-taml-quotations/gap-analysis/taml-gap.html#quotations
<r12a> [18]https://github.com/w3c/iip/pull/11/files
[18] https://github.com/w3c/iip/pull/11/files
alolita: sure...
… next call... every alternate thursdays...
… i think we are done for today... anything else ?
richard: i have quick question... need similar section on
devanagari and bengali...
alolita: sure... we can respond on the github...
Action: All review Tamil PR at [19]https://github.com/w3c/iip/
pull/11 with a view to using same section in Devanagari and
Bengali
[19] https://github.com/w3c/iip/pull/11
<trackbot> Error finding 'All'. You can review and register
nicknames at <[20]http://www.w3.org/International/groups/
indic-layout/track/users>.
[20] http://www.w3.org/International/groups/indic-layout/track/users>.
Action: All review Tamil PR at [21]https://github.com/w3c/iip/
pull/11 with a view to using same section in Devanagari and
Bengali
[21] https://github.com/w3c/iip/pull/11
<trackbot> Created ACTION-5 - Review tamil pr at [22]https://
github.com/w3c/iip/pull/11 with a view to using same section in
devanagari and bengali [on Alolita Sharma - due 2018-05-29].
[22] https://github.com/w3c/iip/pull/11
Summary of Action Items
1. [23]All review Tamil PR at https://github.com/w3c/iip/pull/
11 with a view to using same section in Devanagari and
Bengali
2. [24]All review Tamil PR at https://github.com/w3c/iip/pull/
11 with a view to using same section in Devanagari and
Bengali
Received on Thursday, 24 May 2018 06:06:22 UTC