08:00:12 RRSAgent has joined #i18n 08:00:12 logging to http://www.w3.org/2016/09/22-i18n-irc 08:00:31 Meeting: TPAC 2016: Internationalization WG 08:00:35 encoding spec w3c? 08:00:38 Chair: Addison Phillips 08:00:42 Scribe: Addison Phillips 08:00:48 ScribeNick: addison 08:00:49 https://www.w3.org/TR/encoding/ ? 08:01:06 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 08:01:25 myle https://github.com/whatwg/encoding/issues/62 08:02:12 Agenda: https://www.w3.org/International/wiki/TPAC2016_Agenda 08:02:16 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 08:02:41 present+ Addison, Richard, Felix, Frencesco 08:02:51 present+ Chunming 08:03:01 present+ Myles 08:03:35 chunming has joined #i18n 08:03:56 fsasaki has joined #i18n 08:04:59 felix: discussions with schema.org 08:05:46 tantek has joined #i18n 08:07:12 Topic: Upcoming Agenda 08:09:04 Zakim has joined #i18n 08:09:21 agenda? 08:09:24 q? 08:10:00 Present+ Richard, Felix, Chunming, Francesco, Myles, Addison 08:11:57 present+ Angel 08:13:42 Francesco has joined #i18n 08:14:12 https://www.w3.org/International/wiki/TPAC2016_Agenda 08:14:32 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 08:17:57 angel has joined #i18n 08:18:12 present+ felix 08:18:35 scribe: fsasaki 08:19:41 Myles: here to observe what is going on 08:21:05 present+ bobby 08:21:40 bobbytung has joined #i18n 08:24:29 Topic: Chinese Layout Task Force 08:25:07 https://www.w3.org/International/wiki/TPAC2016_Agenda 08:25:22 rhiaro, see link above 08:25:45 bobbytung has joined #i18n 08:25:47 sure 08:26:40 https://github.com/w3c/clreq 08:27:35 richard introduces layout requirements documents 08:28:26 Chinese, Mongolian, Tibetan, Uighur 08:28:45 richard: goal to review state of various languages and potential next steps 08:29:08 ... we have not moved forward since last TPAC 08:29:40 ... we published FPWD for chinese document. We were close to publish simplified chinese doc, but never got it reviewed for accuracy 08:30:09 ... nothing has happened for a year. what do you think, what will / should happen next? 08:30:48 bobby: on github we have issues, not so important. Apologies for the delay of the year, this time I will get the issues cleared. 08:31:13 ... we want extension to clreq, some editors may have opinions but not expressed on github 08:31:35 ... some parts are not done, we want to extend the sections in november 08:32:10 ... we should have a gap document for clreq 08:32:45 richard: does it make sense to work on gap document at the same time or should we finish clreq first? 08:33:20 addison: with jlreq document experience, I think having a gap document helps 08:34:06 ... helpful to produce a complete as possible set of clreq requirements, we can use that to produce gap document(s) 08:34:29 richard: bobby has some specific issues they like to have addressed soon 08:34:53 addison: clreq describes things that you like to get done? 08:34:55 bobby: yes 08:35:04 addison: don't think we need a formal doc to do that 08:35:41 discussion on how to have the list of gap filling in clreq 08:36:32 richard: a gap document would be helpful, just wondering if it would take a lot longer 08:36:51 addison: do you have one example? 08:36:55 richard: font fallback 08:37:17 addison: if we could produce a list of specific requests we could produce issues 08:37:39 richard: the gap document would say: this is what currently happens. could be in the issue but can be a lot of text 08:38:00 ... e.g. "safari does this ..." 08:38:22 addison: can be a living doc as the discussion goes on 08:38:48 ... worried that if we build one gap doc it will take time. we are not progressing clreq 08:39:12 ... on font fallback: that discussion will be fairly mature in the beginning 08:40:16 ... other items will need more documentation work 08:40:53 myles: CSS group is very interested in supporting chinese text 08:41:22 ... if we in CSS get things wrong, some items may be more important than others 08:41:40 ... would be good to know what to focus on 08:42:18 richard: for that it would be good to structure the items 08:42:27 myles: a mail would be good for me to start with 08:42:43 bobby: I should list the issues I wrote last year / this year 08:43:10 ... e.g. text area topic - kojii is working on that already 08:43:27 bobbytung has joined #i18n 08:43:51 discussion on how to structure the discussion 08:45:06 myles: happy to help, to put together what CSS needs = turning i18n group outcomes into input to CSS WG 08:45:33 Chunming: we have layout document for many languages 08:45:36 rrsagent, draft minutes 08:45:36 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html angel 08:46:22 ... programmers who want to follow clreq need examples. general content creator wants to know how to write the CSS style rules 08:46:36 ... this is different than gap analysis 08:47:05 ... another layer of work - collection of best practices that could be met by current web tech 08:47:22 ... not sure if this has been done by other layout docs, e.g. latin 08:47:39 addison: jlreq wrote a nearly perfect model on how japanese print publication works 08:47:55 ... you then could write an authoring guide for CSS 08:48:13 ... in some cases there are gaps 08:48:36 ... if we do the same with clreq, it would say: here is a description how the layout works 08:48:54 ... then e.g. you say: justification works like this: ... 08:49:24 ... in other areas, e.g. ruby, we had a long discussion on how to do this and then how to close gaps 08:49:32 https://www.w3.org/TR/ruby-use-cases/ 08:50:08 .... that is normal process: people say "I can't do ...". Then we say "describe what you want to do". Then we may have more keywords in CSS or s.t. else 08:50:54 myles: a web author wants to know: "what do I need to do to make ruby happen?" 08:51:17 ... in some cases there is a simple answer, in others it is more complex, e.g. a list of properties 08:51:38 ... I have not seen such docs by W3C, but in other places (blog posts ...) by industry 08:52:04 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 08:52:25 richard: for ruby, we created a WG note that showed all that stuff, on an adhoc basis 08:52:40 ... we just need to keep track of things 08:53:05 addison: not loose track of being able to finish work 08:54:33 chunming: for clreq we will continue maintenance 08:54:45 ... not sure if we want to publish a snapshot of clreq every year? 08:55:13 richard: we did not publish since simplified chinese had not been reviewed 08:55:57 ... I propose a different way: we have echidna , so as soon as there is a github commit the TR version is updated automatically 08:56:07 ... I recently ported jlreq into respec 08:56:42 ... for jlreq I decided to have two documents, you can still have parallel comparison 08:57:03 ... they don't we split clreq into three docs: traditional chinese, simplified, english 08:57:15 s/they/why/ 08:57:49 ... at the moment we cannot publish anything because different progress 08:58:10 angel: how do you synchronize? 08:58:14 richard: manually 09:00:30 addison has joined #i18n 09:00:30 myles has joined #i18n 09:00:39 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 09:00:42 fsasaki_ has joined #i18n 09:01:01 chunming: all issues may be discussed in chinese 09:01:31 ... I'd suggest to have both in same doc, since english doc will be a bit later. 09:02:35 angel: simplified chinese editor is not so familiar with github, so my team did significant efforts to back her up 09:03:06 addison: can we mark what is out of sync? 09:03:13 richard: with CSS classes 09:04:07 addison: with echidna we can have publish a draft as push 09:04:29 richard: with separate documents you have to do more review 09:05:07 ... we should agree that we publish one doc with three languages and make clear that they don't always say the same thing 09:05:11 ... or that we publish three docs 09:05:37 chunming: currently we only have 30+ issue open, not big issues 09:06:06 ... we just need to go through open issues and see what we fix before we publish 09:07:04 chunming: I see two ways to publish: 1) english doc, then two separate chinese docs 2) have one page with three languages referenced 09:07:08 Francesco has joined #i18n 09:07:22 .. for our audience it is preferred to have one doc 09:07:42 ... for publishing process, currently we need to have editors keep consistency manually 09:07:58 ... editors need to have some effort to assure consistency 09:08:03 ... I would prefer to publish one doc 09:08:04 q+ 09:08:22 chunming: one doc would be more useful to the audience to follow discussion 09:08:32 myles: who is audience? 09:08:47 chunming: digital publishing / web site content providers in china 09:08:59 najib has joined #i18n 09:08:59 ... ebook providers on mobile phones 09:09:11 ... browser providers, like myles 09:09:24 richard: CSS and similar WGs 09:10:36 chunming: would be good to have a best practices doc on how to follow requirement. propose to keep this in one doc so that this audience has a clear understanding of requirements 09:11:04 richard: we have gone over a year without update, you seem to agree to publish rather soon? 09:11:13 chunming: yes 09:11:49 chunming has joined #i18n 09:12:06 angel: I see concerns from chunming. if we spit into three, we may have problems with patent policy 09:12:18 rrsagent, draft minutes 09:12:18 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html chunming 09:12:19 ... see jlreq: japanese standards go first 09:12:55 .... if people look for original language doc and try to make a national standard, they have an issue 09:13:07 ... we try to avoid the possible harmonization problem for the future 09:13:38 richard: the patent policy does not apply, since the docs are not on the rec track 09:13:53 angel: yes, but there are restrictions 09:14:21 present+ Najib 09:14:28 ... only english is authoritive, the other versions should go through translation process which is very complex 09:14:43 angel: in jlreq case, there was national standard 09:14:49 JIS 4051 09:15:12 angel: our people may be hesitant if English doc is authoritive 09:16:46 addison: we want to document as good as possible how chinese works so that the technology works 09:17:07 ... point of this is to be descriptive, not normative, so that we can build other standards out of that 09:17:19 richard: we have resolved to keep the three languages together 09:17:21 angel: yes 09:17:23 q- 09:18:11 richard: will set up clreq to publish with echidna in TR space 09:18:23 ... will take an action to prepare that 09:18:27 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 09:19:22 richard: tibetan has been ready for publishing for a year, want to discuss that 09:19:52 s/japanese standards/japanese national standards 09:19:55 chunming: we set up the task force and talked about how we organise this. china government does not want to split this language, china is multi ethnic nation 09:20:36 chunming: if we want to do this in china, and get more input from experts, then we keep document creation in the layout task force 09:20:51 ... we exchanged the idea with government agency, so I don't want this to be changed 09:21:00 s/our people/Chinese Chinese layout people who finally realize the value of such a document and decide to make a version of their naitonal standard out of it 09:21:19 ... another example: korea is used in china in some provinces 09:21:30 ... that is ok, there is klreq already 09:22:03 ... for mongolian, AFAIK, chinese scholars have good links 09:22:16 richard: there is no mongolian task force, just a mailing list 09:22:32 ... there is two problems: first, tibetan is not just a chinese language 09:22:50 ... if I talk to people outside china, people have resistance to participate 09:23:16 ... as W3C we have to take a global point of view. Tibetan is spoken in china but also in other countries 09:23:25 ... the other issue is: nothing is happening 09:23:45 ... we cannot move requirements forward without regular meetings 09:24:09 ... we did have the meetings for jlreq and now for alreq 09:24:21 ... so asking: would it make sense to have a task force for tibetan? 09:24:55 angel: we want to avoid unnecessary tension 09:25:45 ... would be good to have a neutral home 09:26:14 addison: other task forces are organized on a per language basis. 09:26:40 ... task force is not a language of a particular place 09:27:10 ... a task force does not say: the language goes with a certain state 09:28:44 chunming: we want to collect information of layout from different languages and want to publish that as different documents 09:28:53 ... the only concern is about organising the work 09:29:03 ... you are right, tlreq is not pushing fast 09:30:22 ... before last tpac, our contact was one professor in mongolian univ. 09:30:29 ... now seems not be very active 09:30:45 ... but some engineers from our members show interest in mongolian 09:30:59 ... currently we don't have first draft, just email discussion 09:31:11 richard: email discussion is mostly on unicode topics 09:32:59 angel: clreq is all fine, chinese can mean mandarin. for us chinese means all the languages spoken in china. we can change the chinese title into saying: mandarin requirements. 09:33:21 ... then these people don't have to join the chinese task force 09:33:53 s/mandarin/hanzu/ 09:34:09 s/requirements/requirements (in chinese title)/ 09:34:50 angel: get another task force to join and change the name of this task force 09:35:45 s/hanzu/hanzi 09:35:57 bobby: could it be possible to share some infos between docs? 09:36:04 addison: I thought we produce separate docs? 09:36:51 agreement from the room 09:37:34 angel: goal to close all issues by the end of this year 09:37:36 bobby: agree 09:38:15 chunming: can we push for official clreq by end of this year? 09:38:23 richard: if you tell us that the doc is complete, sure 09:38:30 angel: should this be a living doc? 09:38:55 addison: we can publish drafts again and again, and then a note 09:39:14 ... a new note then would be version two, etc. 09:40:40 discussion on tibetan 09:40:59 addison: in jlreq, mixed layouts was important topic 09:42:22 chunming: status report of tibetan 09:42:31 ... offline mail discussion, does not reflect back to github 09:42:44 ... we found people working in publishing house for tibetan content 09:42:55 ... we got support of national standards WG in china 09:42:58 http://w3c.github.io/tlreq/ 09:43:08 ... also from @@@ university 09:43:15 s/@@/Lasa 09:43:24 ... those people are happy to make review of document 09:44:03 ... also found a publishing house in china and china mobile, experts that are happy to contribute 09:44:43 ... that is human resource status. Bottleneck is me - we need to set up those people, organize f2f meetings 09:44:56 ... so that we can build trust and relationships with them 09:45:22 ... according to our previous schedule I am happy to held f2f after this TPAC 09:45:54 ... my target is to have first version reflect back to w3c github, open to public document 09:46:18 richard: after last TPAC we agreed that I update doc, you were to translate it and publish as FWPD 09:46:30 ... that doc is ready in english, then needs translation 09:46:41 ... they may change it completely, but good to have s.t. to look at 09:46:55 chunming: one of my students is working on translation 09:47:02 ... need to update it back to html 09:47:07 richard: can I help? 09:47:17 chunming: I can do it asap 09:47:51 angel: similar issue like with simplified chinese - editor works in work 09:48:22 s/works in work/ not familar with github 09:48:22 addison: concerns about separate work modes. 09:48:55 chunming: HTML is not a problem. we want to identify right person to take the editor role. 09:49:07 ... they should be familiar with github, html etc. 09:49:47 ... for tlreq, there is english and chinese, need to update to make it english - chinese version on github 09:50:09 ... chunming we have f2f meeting with editors / reviewers, so that they can have f2f discussion on each item 09:50:19 ... after that we can reach to first public WD 09:50:51 richard: I just want to make publication asap. Is discussion necessary before publication? 09:51:22 chunming: want to build trust and a relationship with editors, will set up offline f2f, what the next steps are 09:51:34 ... want to have whole day f2f meeting to invite some reviewers 09:51:58 ... to give a full review of current version, to make sure a more reliable version is released 09:52:36 richard: better to have something than nothing. So I want to set a date on the discussions and FPWD 09:52:46 chunming: we can have FPWD by end of this year 09:53:14 ... before that, we will have small group meetings 09:54:15 agreement on how to proceed 09:54:31 mongolian as a topic to be discussed later 09:55:35 chunming: we have national standard for mongolian, not fully reflected to our requirements 09:55:58 richard: if you need help to create first draft I can help 09:56:20 chunming: this doc will share same outline as clreq or klreq. structure is quite clear 09:57:17 angel: will see if there is formal version of national standard is available. 09:58:42 richard: there will be discussion on moving task forces to community group - whether it is feasible etc. 09:58:49 angel: happy to join discussion 10:04:50 bobbytung has joined #i18n 10:11:10 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 10:13:00 myles has joined #i18n 10:13:43 present+ Rebecca 10:13:59 Topic: Break 10:14:10 Topic: Issue Triage 10:14:21 fsasaki_ has joined #i18n 10:14:23 exuent: chunming, bobbytun, angel 10:14:33 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 10:14:38 scribe: addison 10:15:00 rebeca: (self introduction) 10:15:10 ... improve latin layout requirements 10:15:24 andreas: andreas tai from munich 10:15:33 ... work mostly with captions and subtitles 10:15:46 present+ Andreas 10:16:28 andreas: timed text has ways to markup bidi, kind of mystical 10:16:33 ... interested in what this wg does 10:19:05 Topic: JSON and Bidi 10:19:43 atai2 has joined #i18n 10:19:48 Rebeca has joined #i18n 10:20:03 http://w3c.github.io/i18n-discuss/notes/json-bidi.html 10:20:07 s/Rebecca/Rebeca/ 10:20:24 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 10:21:45 richard: (introducing topic) 10:21:57 ... the paragraph direction of the string as a whole 10:22:11 ... reason that complex is that base direction isn't expressed int he string 10:22:17 ... might be expressed in the htnml document 10:22:25 ... like in a form 10:22:32 ... going to be submitted, etc. 10:22:44 ... text would go from rtl because html file says dir=rtl 10:22:51 ... looks rtl oriented because of that 10:23:00 ... but when typing in english document 10:23:10 s/htnml/html/ 10:23:11 ... doesn't look right, so user sets direction on form element 10:23:21 ... surrounding "stuff" contains the knowledge 10:23:25 ... string doesn't encode it 10:23:35 ... and associate it in some way with the string 10:23:45 ... so consumer can apply correct direction 10:23:54 ... how do we do that association 10:24:05 ... direction property in an annotation 10:24:21 ... people like tantek don't like that direction 10:28:11 addison: strings want to carry metadata (dir and lang) 10:28:26 richard: producers == people putting text into a json string 10:28:34 ... consumer == people reading the json 10:28:41 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 10:29:17 richard: 3 basic approaches 10:29:22 ... 1. first strong 10:29:29 .... 2. insert markers into string 10:29:35 ... 3. property that comes with property 10:29:44 richard: look at storing base direction 10:50:09 Rebeca has joined #i18n 10:59:34 this is how an RDF language tag looks like in json-ld = the same as the direction property currently being discussed: "http://example.com/myproperty": { "@language": "en", "@value": "That Seventies Show" } 11:00:18 "content": "mystring"@@en-US^^rtl 11:03:01 "content":"mycontent", "content-dir": "ltr" 11:03:06 this may be addison's wiki page on the issue: https://www.w3.org/International/wiki/ContentMetadataJavaScriptDiscussion 11:08:51 https://www.w3.org/TR/activitystreams-core/#h-biditext 11:58:13 addison has joined #i18n 11:58:19 Topic: Lunch 11:58:24 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 12:07:30 tantek has joined #i18n 12:23:23 barryleiba has joined #i18n 12:25:05 r12a has joined #i18n 12:25:33 r12a has joined #i18n 12:25:54 r12a has joined #i18n 12:29:28 https://www.w3.org/International/wiki/TPAC2016_Agenda#Thursday.2C_22_September 12:29:58 atai2 has joined #i18n 12:32:31 question: webannotation: are we doing the right thing 12:32:56 Topic: JSON bidi further discussion 12:33:16 fsasaki has joined #i18n 12:33:25 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 12:36:23 - webannotation: changes 12:36:40 - do we need another serialization scheme (pursue standards)? 12:43:03 https://www.w3.org/International/wiki/ContentMetadataJavaScriptDiscussion 12:43:08 Zakim has left #i18n 12:43:16 Zakim has joined #i18n 12:47:56 najib has joined #i18n 12:52:48 alala 12:53:00 "cue": "alala" 12:53:09 "RLMalala" 12:53:27 atai2_ has joined #i18n 12:53:32 dae has joined #i18n 12:54:01 "cue": { dir: rtl lang:ar text:alala} 13:00:08 addison has joined #i18n 13:00:17 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 13:01:55 https://www.w3.org/International/wiki/TPAC2016_Agenda 13:02:20 fsasaki_ has joined #i18n 13:05:19 http://json-ld.org/ 13:05:56 action: addison: write to json-ld about potential for a serialization form for natural language strings to address issues with dir and lang 13:05:57 Created ACTION-552 - Write to json-ld about potential for a serialization form for natural language strings to address issues with dir and lang [on Addison Phillips - due 2016-09-29]. 13:09:05 discussion of webannotation vs. activitystreams 13:09:43 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html fsasaki 13:10:34 richard: for external resources (uris), doesn't make sense to include direction? 13:15:46 https://github.com/w3c/web-annotation/issues/335 13:18:15 najib has joined #i18n 13:20:07 myles has joined #i18n 13:20:43 https://github.com/w3c/web-annotation/issues/335#issuecomment-237636530 13:24:02 Francesco has joined #i18n 13:24:17 https://github.com/w3c/web-annotation/issues/335#issuecomment-237895142 13:28:18 jasnell has joined #i18n 13:33:11 action: addison: work with richard to develop a pros/cons document describing the different bidi-in-json handling proposals 13:33:11 Created ACTION-553 - Work with richard to develop a pros/cons document describing the different bidi-in-json handling proposals [on Addison Phillips - due 2016-09-29]. 13:33:40 Topic: Issues Triage 13:33:46 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 13:33:55 http://w3c.github.io/i18n-activity/reviews/ 13:34:25 [just for reference, discussion of the json issue in the XLIFF tc: https://lists.oasis-open.org/archives/xliff/201510/msg00009.html ] 13:34:59 • rb and rtc non-conforming in html5.1 https://github.com/w3c/i18n-activity/issues/215 13:37:04 close 13:37:22 https://github.com/whatwg/html/issues/1771 13:39:03 okay, don't close and track whatwg 1771 in that issue 13:39:54 • BP3 should recommend locale-neutral representation https://github.com/w3c/i18n-activity/issues/187 13:41:37 http://w3c.github.io/dwbp/bp.html#locale_parameter 13:43:54 https://www.w3.org/Mail/flatten/index?subject=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-dwbp-comments%2F2016Jul%2F0028.html&list=public-dwbp-comments#msg23 13:44:18 http://w3c.github.io/dwbp/bp.html#LocaleParametersMetadata 13:45:01 close 13:45:51 • What Latin means https://github.com/w3c/i18n-activity/issues/47 13:46:19 https://github.com/w3c/dpub-pagination/issues/6 13:47:03 changed text to: "... books that use the Latin script, based on ... 13:47:09 close 13:47:32 • Possibility for a character to be interpreted differently depending on locale https://github.com/w3c/i18n-activity/issues/114 13:47:51 https://github.com/w3c/presentation-api/issues/218 13:48:40 https://github.com/w3c/presentation-api/pull/280 13:49:28 https://github.com/w3c/presentation-api/commit/a6f555345a7b98016c6954ff0465b6b45cef7ec8 13:50:22 addison: prefer language to locale in several places in the text, but okayy 13:50:31 close 13:50:46 • list of displays: should it address display name, language, etc.? https://github.com/w3c/i18n-activity/issues/113 13:52:10 https://github.com/w3c/presentation-api/commit/c19d0570ace9494192694ceee94d25ccaee31b49 13:52:59 close as stale 13:53:01 jasnell has joined #i18n 13:53:04 • Make unicode-bidi: isolate the default for elements with a dir attribute (mozilla) https://github.com/w3c/i18n-activity/issues/26 13:53:36 they did it 13:53:37 close 13:53:50 • [csvw] instance definitions for direction https://github.com/w3c/i18n-activity/issues/153 13:54:47 close 13:55:02 • Consider removing TextEncoder support for UTF-16 https://github.com/w3c/i18n-activity/issues/116 13:55:17 skipped 13:58:42 Topic: Coffee Break 13:58:47 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 13:59:42 nigel has joined #i18n 14:17:40 q? 14:17:55 present+ fantasai 14:18:02 I have made the request to generate http://www.w3.org/2016/09/22-i18n-minutes.html addison 14:25:24 dae has joined #i18n 14:31:07 myles has joined #i18n 14:31:55 atai has joined #i18n 14:36:07