W3C

- DRAFT -

IIP telecon

21 Jul 2019

Agenda

Attendees

Present
Alolita, Vivek, Muthu, atsushi
Regrets
Abhijit, r12a
Chair
Alolita
Scribe
atsushi

Contents


<alolita> https://w3c.github.io/typography/gap-analysis/language-matrix.html

<alolita> Taml

<vivek> https://github.com/w3c/i18n-discuss/wiki/Analysing-support-for-text-layout-on-the-Web

<Muthu> Tamil Sangam MN

<Muthu> Nirmala UI

<Muthu> Tamil MN

<inserted> scribe: atsushi

fonts supports for tamil on browser

(trying to scribe, but not fully catching/understanding discussions...)

<Muthu> We can hear you Vivek

vivek: we created opentype rendering software, still opentype based

alolita: adding it to 3.4, on glyph shaping
... every font engineer need AAT on opentype, do you feel it makes font grue better

Muthu: AAT gives a lot of control
... both opentype and AAT, you can do shaping on both, and interoperatable
... if you want to render indic fonts, and going through this library, shaping will be performed even for opentype

vivek: exact same suggestion was put from @@@ in the past,

muthu: now we are discussing how to include shaping onto font

alolita: it not a kind of type layout, not unicode
... that spec is not like a spec, shaping tric
... this is a gray area between typesetting and shaping, not issue in unicode nor encoding

muthu: missing gap, all items are for display, but we need to be editable
... because of conbining, editing is another big issue
... between two clusters, and if you delete wihtin, it is a big problem

alolita: in points of this layout spec, would note behavior of editing to be included into spec (???)

vivek: if you want to read document, before that the document need to be created, so editing is also important

muthu: issue on editing is included in current document is a question

section 3.6

all: agreed not applicable

section 3.7

alolita: discussion we had before, we did breakdown and added subsections
... double/triple click selection

vivek: click selection is only for display, you may want to move cursor also or drug by mouse
... mouse selection is also two way, clicking and drug over

muthu: by both, we should be possible to do the same thing

alolita: fall selection by grapheme is a question

muthu: is there a need of select by cluster?

alolita: why not.

vivek: usually what happen, you end up to select cluster but not one character, for joining ones
... by adding control, you can select one character by one, but not usual

alolita: you should be able to select the entire graphme cluster

vivek: mostly its base and @@@2

alolita: only two exceptions

closing and next

<vivek> Looks like we have had a super useful discussion today!

<alolita> excellent discussion - we covered a fair bit

<alolita> Atsushi san - thank you for the minutes

<alolita> bye

<alolita> quit

Alolita: will send out schedule call email; next call is next week (Jul 29)

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/07/22 03:44:35 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: i/topic: /scribe: atsushi
Succeeded: i/Looks like we have/topic: closing and next
Present: Alolita Vivek Muthu atsushi
Regrets: Abhijit r12a
Found Scribe: atsushi
Inferring ScribeNick: atsushi
Agenda: https://lists.w3.org/Archives/Public/public-iip-admin/2019JulSep/0003.html
WARNING: Bad day of month "2019" (should be >0 && <32): 2019 Jul 22
Date command/format should be like "Date: 31 Jan 2004"

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]