W3C

- DRAFT -

India International Program Teleconference

27 Jul 2018

Attendees

Present
Regrets
Chair
SV_MEETING_CHAIR
Scribe
r12a

Contents


Devanagari

https://lists.w3.org/Archives/Public/public-iip-admin/2018JulSep/0002.html

“2.1 the recent proposals on is 16350 discussion, the use of zwj or zwnj for alternate shapes was being discouraged. Not sure if this factors here. The standards document recommended use of zwj and zwnj to represent alternate shapes.”

<alolita> zwj or zwnj combinations were provided by c-dac team influencing mobile keyboards is a suggestion not an implementation guideline

<alolita> People want to use complex characters and cannot do so with current implementations. 16350 doesn’t recommend the use of zwj and zwnj because they are not adequate.

<alolita> <add use cases>

<scribe> ACTION: Richard to add issue about ZWJ/ZWNJ stuff to begin fleshing out the problem

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<alolita> 2.7.1 Devanagari Numerals Generally Latin Numerals are acceptable in Devanagari text. Most of the user community identifies with them. However, there could be cases where certain web-pages would prefer to have numerals in Devanagari to cater to mono-lingual (mono-script rather) readers. This is particularly required for input types number and date. It would be useful if the input type values are augmented with the script mnemonics e.g. number_deva or date_[CUT]

<alolita> e.g. number_deva or date_deva instead of changing it for entire page through some locale setting. There could be cases where a user may require both kinds of numbering in the same web-page. AI—>Add use cases

<scribe> ACTION: r12a to add issue about ZWJ/ZWNJ stuff to begin fleshing out the problem

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<alolita> 2.8 for the languages in context as per the Gap analysis table, the cluster definition can be borrowed from IS13194. However, this also links to the fonts. Thoughts are needed. But if this is done, 2.6 also gets addressed perhaps.

<scribe> ACTION: r12a to add issue about devanagari numerals to help provide use case examples

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

https://archive.org/details/gov.in.is.13194.1991

http://w3c.github.io/ilreq/#h_indic_orthographic_syllable_boundaries

<alolita> AI—> Lreq document - action item to add GH issue to http://w3c.github.io/ilreq/#h_indic_orthographic_syllable_boundaries

https://github.com/w3c/ilreq/issues/31

<alolita> AI: Akshat

<alolita> for section 2.8

<scribe> ACTION: Akshat to add text to 2.8 about general problems for segmentation

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<alolita> https://w3c.github.io/iip/gap-analysis/deva-gap.html

<alolita> 3.5 First letter styling was not usually seen in Indian language publishing. The letter designs especially with those that use shiro Rekha, actually become odd. This is however being borrowed in recent text books from English. And even with single letter clusters, the behaviour is not aesthetic. Not sure this needs addressing. Muthu may suggest.

http://w3c.github.io/ilreq/#h_initial_letter_styling

<C-DACTeam> https://w3c.github.io/ilreq/#h_initial_letter_styling

next meeting 10th August, same time

Summary of Action Items

[NEW] ACTION: Akshat to add text to 2.8 about general problems for segmentation
[NEW] ACTION: r12a to add issue about devanagari numerals to help provide use case examples
[NEW] ACTION: r12a to add issue about ZWJ/ZWNJ stuff to begin fleshing out the problem
[NEW] ACTION: Richard to add issue about ZWJ/ZWNJ stuff to begin fleshing out the problem
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/07/27 06:43:51 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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: s/Devangari/Devanagari/

WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: r12a
Inferring Scribes: r12a

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 27 Jul 2018
People with action items: akshat r12a richard

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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]