14:49:51 RRSAgent has joined #i18n 14:49:51 logging to https://www.w3.org/2021/01/14-i18n-irc 14:50:23 trackbot, prepare teleconference 14:50:26 RRSAgent, make logs public 14:50:29 Meeting: Internationalization Working Group Teleconference 14:50:29 Date: 14 January 2021 14:50:47 Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2021Jan/0002.html 14:50:48 addison, sorry, I did not recognize any agenda in https://lists.w3.org/Archives/Member/member-i18n-core/2021Jan/0002.html 14:50:55 Chair: Addison Phillips 14:51:00 agenda+ Agenda 14:51:04 agenda+ Action Items 14:51:08 agenda+ Info Share 14:51:12 agenda+ Radar 14:51:28 agenda+ COGA icon review 14:51:42 agenda+ Charmod case folding etc. 14:51:58 agenda+ MiniApp I18N design discussion 14:52:01 agenda+ AOB? 14:52:07 I have made the request to generate https://www.w3.org/2021/01/14-i18n-minutes.html addison 14:52:26 xfq has joined #i18n 14:59:53 fsasaki has joined #i18n 14:59:55 present+ Addison, Richard, Fuqiao 15:00:08 present+ Martin Alvarez 15:00:21 JcK has joined #i18n 15:00:24 I have made the request to generate https://www.w3.org/2021/01/14-i18n-minutes.html addison 15:01:07 martin has joined #i18n 15:01:15 present+ martin_alvarez 15:01:19 present+ 15:01:56 atsushi has joined #i18n 15:02:01 present+ 15:02:03 present+ JcK 15:02:25 present+ 15:02:57 present+ Yongjing Zhang (Miniapp) 15:03:18 present+ Wangzitao (Miniapp) 15:04:59 agenda? 15:05:04 zakim, take up agendum 1 15:05:04 agendum 1 -- Agenda -- taken up [from addison] 15:05:34 David has joined #I18n 15:05:51 scribe+ 15:05:57 zakim, take up agendum 12 15:05:57 agendum 12 -- MiniApp I18N design discussion -- taken up [from addison] 15:06:29 https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3As%3Aminiapp 15:06:30 https://github.com/w3c/miniapp/issues/149 15:06:46 addison: Welcome to the miniapp people. Fuqiao, can you intro the topic? 15:06:50 zakim, present+ 15:07:28 xfq: We discussed issues last week, mostly about manifest: bidi, localization 15:07:55 ... addison filed an issue about how to make apps in multiple languages. 15:08:45 ... Can miniapp editors explain the i18n architecture of miniapps? 15:09:23 addison: Esp. the design goals. The bigger picture may help us understand better and give more targeted comments. 15:09:50 ... How does a miniapp author make an app localized in multiple languages? 15:10:22 yongjing_zhang: Thanks for the comments and issues. 15:10:33 ... We haven't thought deeply aboiut i18n issues. 15:10:49 ... I didn't understand the the full question at first. 15:11:16 ... The design is not complete. We did think a bit. We first focused on localization in-app. 15:11:32 ... There would be a number of JSON files in the package, for the pages inside the app. 15:11:50 ... We did not think about localizing the manifest. 15:12:14 ... For the time being requires separate app for each language. 15:12:39 ... We could think about localizing the manifest to have localized apps in a single package. 15:13:10 ... I'm editor, but I cannot speak for the whole group, as we haven't discussed it. So this is just personal. 15:13:56 ... Martin and I discussed a bit. Could have several manifests and a single "main" manifest, that links to the others. 15:14:02 q+ 15:14:25 ack addison 15:15:19 addison: I think you have to think as an app author and what the maintenance would be like. My company typically makes apps in some 30-35 languages. 15:15:36 ... Have to consider thinks like default size, default orientation. 15:15:54 ... Doing the same 35 times becomes hard to maintain. 15:16:24 ... How can you recycle the settings across multiple files. 15:16:51 ... But maybe these can files can generated, in which case it is less of an issue. 15:17:51 ... Separete packages for each language is also hard for users, who have to pick among 30 apps and maybe switch apps just to change language. 15:18:27 q+ 15:18:47 q+ to talk about language negotiation 15:19:00 yongjing_zhang: Thanks for those comments. We maybe don't have to duplicate things in all manifests. But just initial thoughts for now. 15:19:23 ack martin 15:19:28 ... We will discuss in the group. Appreciate more guidance. 15:19:46 martin: We have been in touch with WebApps WG to be compatible with manifests. 15:20:12 ... We haven't thought about solutions for localize the metadata in the manifest yet. 15:20:33 ack addison 15:20:33 addison, you wanted to talk about language negotiation 15:20:36 ... But we are interested in the issue and will discuss it. 15:21:01 addison: Language Negotiation may be something else to think about. 15:21:44 ... You may be able to leave it to frameworks and not be precise about it, but good to say something. 15:22:33 ... Imagine getting a request for Mexican Spanish which you don't have, but have a close match. 15:22:44 ... Think about infrastructure. 15:24:09 yongjing_zhang: The miniapp design comes from different existing implementations in the Chinese market. We are trying to find a common solution. Different styles. Android style and others. 15:25:34 addison: You may not have to decide the implementation details. But you probably need to think about a common infrastructure, e.g., a common attribute for the locale, that app authors can use. There may be more happening at run time that you don't have to specify. 15:26:02 ... Get to a standard that is interoperable. Otherwise not really a standard. 15:26:33 q+ 15:26:34 yongjing_zhang: We'll discuss. I imagine it will be hard. 15:27:03 addison: What do you want next? Come back and discuss here? Discuss via GitHub? 15:28:01 yongjing_zhang: After a discussion in the group and some deeped understanding we'll come to you for more comments on a proposal. 15:28:13 s/deeped/deeper/ 15:28:24 ack r12a 15:28:53 https://github.com/w3c/miniapp/issues/106 15:29:15 r12a: We talked about localization. But I had the impression there was also a question about applying different directions to strings within a single app. 15:29:56 ... There is a way to declare a direction at the top level in the manifest. But what if a single app contains strings in two languages? 15:30:35 yongjing_zhang: We should address the two issues together, the localization and the two languages in one app. 15:31:30 r12a: Specifying per language not enough. Have to specify it per string. 15:32:13 ... Also each string may need a language, apart from the single toplevel language. 15:33:10 addison: We generally think that is a requirement: top-level lang and direction and also per-string language and direction. 15:33:45 ... Maybe a common structure for each string that includes the text, the direction and a language. 15:33:55 I have made the request to generate https://www.w3.org/2021/01/14-i18n-minutes.html addison 15:34:49 r12a: It is a good idea to have a top-level lang and direction, and the possibility to override it for a particular string. 15:35:29 ... Language may affect various things: choosing the font, line wrapping... 15:35:47 q+ 15:36:00 ack fsasaki 15:36:05 yongjing_zhang: We will note it and discuss. 15:36:55 fsasaki: It's a typical problem for packaging. Do we have existing examples we can point to? 15:38:03 addison: There are examples, maybe in Android or iOS. I don't have a standard example off the top of my head. 15:38:07 https://www.w3.org/TR/appmanifest/ 15:38:37 i18n issues in WAM: https://github.com/w3c/manifest/issues?q=is%3Aopen+is%3Aissue+label%3Ai18n-tracker 15:38:38 https://w3c.github.io/string-meta/ 15:38:38 r12a: Ditto. But let me put a link to string-meta. 15:38:46 https://w3c.github.io/string-meta/ 15:38:49 (mostly localization issues rather than string-meta issues) 15:39:20 r12a: Ir is probably a good idea for us to look for examples... 15:40:42 David: When taking a multi-file approach, it is is good to look at a way to only encode the differences. A bit like the way CSS rules override other rules. 15:41:20 martin: App manifest only declares a top level language now. 15:41:37 https://w3c.github.io/pub-manifest/ 15:41:58 r12a: Maybe Ivan can help, Publication manifest for EPUB has similar things, 15:42:42 yongjing_zhang: This seems not just related to miniapp, but also webapp. We should look for a common solution. 15:43:13 agenda? 15:43:54 yongjing_zhang: Thanks for your input. We need input from experts. 15:44:38 addison: I'm always ready to schedule a telcon, even if timezones may be difficult. 15:47:24 Topic: Case folding 15:48:01 Bert: r12a's suggestion to do NFD and casefold, without NFC, might work, I think. 15:48:17 addison: I've been thinking about that as well. 15:48:33 ... But Unicode specifies it the other way. 15:48:48 ... I tried some code. too. 15:49:10 ... And why does Unicode specify it like that? 15:50:40 r12a: Normalize first and then case-fold and then normalize: that works. But I think I cocluded a few months ago that NFD and case-fold only work, too. 15:50:58 addison: The subscript iota is the difficult case. 15:51:46 ... We would look for cases. 15:52:13 r12a: I think doing NFD first "levels the playing field". 15:52:27 addison: So why does UNicode specify NFC? 15:52:59 ... Maybe doing NFC at the end is just to make it nice. 15:53:45 stpeter has joined #i18n 15:53:51 r12a: I think I did something in Uniview... Could run the tables through the algo ans see if they are different. 15:54:48 addison: I did that. I cannot think of combining marks that case-fold. I may write to Unicode to ask. 15:55:05 s/ ans / and / 15:55:19 action: addison: check TUS and if necessary ping Unicode folks about D145 normalization case fold ordering questions 15:55:19 Created ACTION-989 - Check tus and if necessary ping unicode folks about d145 normalization case fold ordering questions [on Addison Phillips - due 2021-01-21]. 15:55:37 zakim, take up agendum 10 15:55:37 agendum 10 -- COGA icon review -- taken up [from addison] 15:55:42 https://github.com/w3c/i18n-activity/issues/1008 15:56:15 https://www.w3.org/TR/coga-usable/#summary 15:56:58 r12a: Lisa raised the issue in the i18n repo and somebody started answering there. So I updated the boilerplate text to make it clearer what the expected process is. 15:57:26 xfq: Yes, people are aware now. 15:58:18 r12a: The issue^^^ shows the things I noticed about the icons. 15:59:34 addison: Seems they are trying to give a kind of best practice, not standardize the icons. Seems to be based a lot on using metaphors. 16:00:08 David: Several concepts involve hands and gestures, which may be cultural. 16:02:25 addison: Not sure how to advise them. 16:02:56 .. What shall we do? You want to send comments to them? 16:03:15 r12a: I can add text to my issue and send that. 16:03:56 addison: Any other opinions? 16:04:21 Topic: AOB? 16:05:32 I have made the request to generate https://www.w3.org/2021/01/14-i18n-minutes.html addison 16:05:34 zakim, bye 16:05:34 leaving. As of this point the attendees have been addison, Atsushi, Fuqiao, Felix, JcK, Richard, Martin, Alvarez, martin_alvarez, Bert, fsasaki, Yongjing, Zhang, (Miniapp), 16:05:34 Zakim has left #i18n