13:25:11 <RRSAgent> RRSAgent has joined #i18n
13:25:15 <RRSAgent> logging to https://www.w3.org/2025/06/26-i18n-irc
13:25:23 <addison> Meeting: Internationalization Working Group Teleconference
13:25:28 <addison> Chair: Addison Phillips
13:25:39 <agendabot> agenda: https://www.w3.org/events/meetings/b7edae68-f52c-4aab-a1a6-3c37459e0786/20250626T150000/
13:25:39 <agendabot> clear agenda
13:25:39 <agendabot> agenda+ Agenda Review
13:25:39 <agendabot> agenda+ Action Items
13:25:42 <agendabot> agenda+ Info Share
13:25:44 <agendabot> agenda+ Review RADAR
13:25:46 <agendabot> agenda+ Pending Issue Review
13:25:49 <agendabot> agenda+ AOB?
13:26:53 <addison> agenda+ Specdev PR 162: Modernize 'choosing character encodings'
13:27:38 <addison> agenda+ i18n-activity#2011: full-width characters in `input type=number`
13:27:39 <gb> https://github.com/w3c/i18n-activity/issues/2011 -> Issue 2011 Define optional normalization of full-width characters in <input type="number"> (by w3cbot) [pending] [tracker] [s:html] [spec-type-issue] [jlreq]
13:27:56 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/26-i18n-minutes.html addison
13:40:33 <addison> addison has joined #i18n
13:58:55 <addison> present+
13:59:52 <addison> present+ Atsushi
14:00:34 <JcK> JcK has joined #i18n
14:01:51 <addison> present+ Bert, Fuqiao, JcK
14:02:42 <addison> present+ Richard
14:02:45 <atsushi> scribe+
14:03:26 <addison> zakim, take up agendum 1
14:03:26 <Zakim> agendum 1 -- Agenda Review -- taken up [from agendabot]
14:03:28 <addison> agenda?
14:03:31 <gb> https://github.com/w3c/i18n-activity/issues/2011 -> Issue 2011 Define optional normalization of full-width characters in <input type="number"> (by w3cbot) [pending] [tracker] [s:html] [spec-type-issue] [jlreq]
14:03:58 <atsushi> addison: added some from me, anything else from wind?
14:04:05 <addison> zakim, take up agendum 2
14:04:05 <Zakim> agendum 2 -- Action Items -- taken up [from agendabot]
14:04:16 <addison> https://github.com/w3c/i18n-actions/issues
14:04:22 <addison> #175
14:04:22 <gb> https://github.com/w3c/i18n-actions/issues/175 -> Action 175  respond to our #2005 (on xfq) due 2025-06-26
14:04:31 <addison> #174
14:04:31 <gb> https://github.com/w3c/i18n-actions/issues/174 -> Action 174  add 'typeface style` to the glossary (on r12a) due 2025-06-19
14:04:48 <atsushi> r12a: created PR, and saw reply
14:05:22 <addison> https://github.com/w3c/i18n-glossary/pull/80
14:05:22 <gb> https://github.com/w3c/i18n-glossary/pull/80 -> Pull Request 80 Update 'glyph' definition (by aphillips)
14:05:25 <atsushi> addison: PR above
14:05:42 <atsushi> r12a: could add for today if want?
14:06:15 <atsushi> [seeking for right PR link]
14:06:49 <addison> #173
14:06:50 <gb> https://github.com/w3c/i18n-actions/issues/173 -> Action 173  ping zainab (on aphillips) due 2025-06-19
14:07:07 <addison> #171
14:07:07 <gb> https://github.com/w3c/i18n-actions/issues/171 -> Action 171 revise local-font-access to exclude localhost and talk more about opt-in model (on ZainabAq) due 2025-05-22
14:07:08 <atsushi> addison: copy list and reply some next week
14:07:16 <addison> #169
14:07:17 <gb> https://github.com/w3c/i18n-actions/issues/169 -> Action 169  reply to html 10843 and css 9832 (on aphillips) due 2025-05-08
14:07:20 <r12a> https://github.com/w3c/i18n-actions/issues/174#issuecomment-2991720581
14:07:21 <gb> https://github.com/w3c/i18n-actions/issues/174 -> Action 174  add 'typeface style` to the glossary (on r12a) due 2025-06-19
14:07:25 <addison> #162
14:07:25 <gb> https://github.com/w3c/i18n-actions/issues/162 -> Action 162  poll I18N/CSS for new day/time (on aphillips) due 2025-03-25
14:07:52 <addison> #157
14:07:53 <gb> https://github.com/w3c/i18n-actions/issues/157 -> Action 157  write glossary proposal identifying options and next steps for those options (on aphillips) due 2025-02-20
14:07:56 <atsushi> addison: will tuckle to #162 after this
14:08:07 <addison> #135
14:08:07 <atsushi> addison: #157, discussed last week, and continue this
14:08:08 <gb> https://github.com/w3c/i18n-actions/issues/135 -> Action 135  follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
14:08:11 <David> David has joined #i18n
14:08:19 <addison> #127
14:08:20 <gb> https://github.com/w3c/i18n-actions/issues/127 -> Action 127  make a list of shared topics of interest between TG2 and W3C-I18N (on aphillips) due 2024-09-30
14:08:24 <addison> #33
14:08:25 <gb> https://github.com/w3c/i18n-actions/issues/33 -> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
14:08:34 <addison> #7
14:08:35 <gb> https://github.com/w3c/i18n-actions/issues/7 -> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023
14:08:44 <addison> #4
14:08:44 <gb> https://github.com/w3c/i18n-actions/issues/4 -> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips) due 27 Jul 2023
14:08:56 <addison> zakim, take up agendum 3
14:08:56 <Zakim> agendum 3 -- Info Share -- taken up [from agendabot]
14:09:06 <addison> present+ David
14:09:12 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/26-i18n-minutes.html addison
14:09:20 <atsushi> [none]
14:09:28 <addison> zakim, take up agendum 4
14:09:28 <Zakim> agendum 4 -- Review RADAR -- taken up [from agendabot]
14:09:35 <addison> https://github.com/orgs/w3c/projects/91/views/1
14:09:47 <atsushi> addison: no new request, nothing for review
14:09:58 <addison> zakim, take up agendum 5
14:09:58 <Zakim> agendum 5 -- Pending Issue Review -- taken up [from agendabot]
14:10:04 <addison> https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending
14:10:27 <atsushi> addison: #2011, added as agenda, quite interesting one
14:10:28 <gb> Issue 2011 not found
14:10:44 <addison> agenda?
14:10:47 <gb> https://github.com/w3c/i18n-activity/issues/2011 -> Issue 2011 Define optional normalization of full-width characters in <input type="number"> (by w3cbot) [pending] [tracker] [s:html] [spec-type-issue] [jlreq]
14:10:50 <addison> zakim, take up agendum 8
14:10:50 <Zakim> agendum 8 -- i18n-activity#2011: full-width characters in `input type=number` -- taken up [from addison]
14:11:09 <addison> https://github.com/whatwg/html/issues/11395
14:11:09 <gb> https://github.com/whatwg/html/issues/11395 -> Issue 11395 Define optional normalization of full-width characters in <input type="number"> (by kyouhei-horizumi) [topic: forms] [i18n-tracker] [needs tests] [i18n-jlreq] [i18n-clreq]
14:11:30 <atsushi> addison: in HTML, write specificlly about wide char input into type=number
14:11:54 <atsushi> ... issue discussed before around IME on/off etc. and for combinience
14:12:10 <addison> Richard's codepen: https://codepen.io/r12a/pen/PwqVJym
14:12:20 <atsushi> r12a: look at codepen
14:12:56 <atsushi> ... type wide full width characters there, you see text grabbled by browser and converted into ascii digits
14:13:32 <atsushi> ... my initial question was in Firefox you type wide character see ascii digit
14:14:10 <atsushi> ... might not be an issue or not, not sure
14:14:17 <addison> ｑ＋
14:14:24 <addison> q+
14:14:37 <atsushi> ... this is a situation full width character is handled
14:14:55 <atsushi> ... for other scripts, you type numeric in arabic, and see how they are displaied
14:15:11 <atsushi> ... if  you increment it, for Japanese it's converted into ascii and work, but not for others
14:15:18 <atsushi> ... not sure, that is good or not
14:16:09 <atsushi> ... problem here, how it works with incrementation or etc.
14:16:24 <addison> q?
14:16:34 <addison> ack next
14:16:44 <atsushi> r12a: don't know what is an answer on this front, but there is some issue/discussion
14:17:18 <atsushi> addison: when you have number input, and you type some, whenyou want to send to the Internet what should happen
14:17:33 <atsushi> ... number format is for display, or internal seriarization
14:17:50 <atsushi> ... there are many local presentation of number
14:18:08 <atsushi> ... immediate problem, I forgot to switch my keyboard, typed fullwidth q+
14:18:22 <atsushi> ... it's nice that browser could tell input status
14:18:41 <atsushi> ... also it's good if browser handles numeric in format other than ascii, like arabic
14:19:15 <atsushi> q+ in Japan, some special condition exists, some site requires full width input for form, on address etc...
14:19:42 <atsushi> addison: it should be good to behave by locale, when you type number
14:19:43 <addison> ack next
14:20:23 <addison> atsushi: in japan a lot of forms require full-width input
14:20:36 <addison> ... so many people have requirement for how we should type numeric values into the form
14:20:50 <addison> ... such a change is probably the background of this request
14:21:07 <addison> ... physical address, must type numerical values including as character, not as ASCII
14:23:28 <atsushi> addison: weird situation
14:23:56 <atsushi> atsushi: per these messy sitaution, I cannot say neither yes or no if this issue is for Japanese
14:24:50 <atsushi> David: if depends on locale for display, for arabic situation, Japanese numeric to be shown depends on locale
14:25:41 <atsushi> ... if I use display locale with Japanese, but site uses locale as arabic, will be shown as arabic?
14:26:09 <atsushi> r12a: if you display in different place, you can use formatting condition for display
14:26:26 <atsushi> ... most discussion here, is how input will be handled
14:27:02 <atsushi> ... after captured by browser, and some operation made like incrementation, what should be happen
14:27:42 <addison> function showNumber (num) {
14:27:42 <addison>   document.getElementById('number').textContent = new Intl.NumberFormat("ja-JP", { style: "currency", currency: "JPY" }).format(
14:27:42 <addison>     num);
14:27:42 <addison> }
14:28:45 <atsushi> addison: how should we do for the issue?
14:29:38 <atsushi> xfq: how about handling digists how chrome is doing now?
14:30:10 <atsushi> addison: this issue is if we type number with full width digits, input to be handled
14:30:28 <xfq> s/how about handling digists how chrome is doing now?/At least the browsers should be able to display and handle native digits, but Chrome currently cannot./
14:31:16 <atsushi> xfq: not sure which level is good for users.
14:31:57 <atsushi> addison: if you type wide digit, and used spinner, you would want to get result with spinned?
14:34:03 <addison> new Intl.NumberFormat(locale).format(num)
14:35:21 <addison> new Intl.NumberFormat(locale, { numberingSystem: 'deva'}).format(num);
14:36:28 <atsushi> addison: will you reply to the issue, or I as char hat on?
14:36:34 <atsushi> r12a: not mind
14:36:48 <addison> action: addison: add WG comment to html 11395
14:36:55 <gb> Created -> action #176 https://github.com/w3c/i18n-actions/issues/176
14:36:58 <addison> agenda?
14:37:01 <gb> https://github.com/w3c/i18n-activity/issues/2011 -> Issue 2011 Define optional normalization of full-width characters in <input type="number"> (by w3cbot) [pending] [tracker] [s:html] [spec-type-issue] [jlreq] [clreq] [i:interaction]
14:37:11 <addison> zakim, take up agendum 7
14:37:11 <Zakim> agendum 7 -- Specdev PR 162: Modernize 'choosing character encodings' -- taken up [from addison]
14:37:31 <addison> https://deploy-preview-162--bp-i18n-specdev.netlify.app/#char_choosing
14:37:37 <atsushi> addison: started working on rewritting section of specdev
14:37:43 <atsushi> ... early draft above
14:38:10 <atsushi> ... as initial set of mustard for encoding
14:42:45 <atsushi> [discussion around mustard text]
14:43:23 <atsushi> addison: third mustard is mostly from charmod-norm
14:47:38 <atsushi> addison: is it better to remove these mustards, most of which says similar thing?
14:48:26 <atsushi> JcK: pieces of mustards, probably says use Unicode, or otherwise useless
14:48:33 <atsushi> addison: make first mustard stronger?
14:49:06 <atsushi> r12a: really rare situation someone might use different than Unicode
14:50:16 <xfq> s/use different than Unicode/use non-UTF-8 encodings/
14:51:29 <atsushi> addison: fourth piece of mustard could be issue
14:51:56 <atsushi> ... guidance elsewhere is you should restrict to UTF-8, but this relax it
14:52:15 <atsushi> ... could rewrote this as specific case
14:52:36 <atsushi> xfq: existing one uses non-UTF-8 encodings
14:53:14 <xfq> s|existing one uses non-UTF-8 encodings|existing encoding mappings can be changed/updated|
14:53:47 <atsushi> addison: saying not use new field named as encoding, but some header specifies
14:54:25 <atsushi> ... could join two items into one
14:56:29 <addison> zakim, take up agendum 6
14:56:29 <Zakim> agendum 6 -- AOB? -- taken up [from agendabot]
14:59:47 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/26-i18n-minutes.html addison