15:52:49 RRSAgent has joined #pcg-a11y 15:52:54 logging to https://www.w3.org/2024/01/11-pcg-a11y-irc 15:53:07 Zakim has joined #pcg-a11y 15:53:31 zakim, this will be pcg-a11y 15:53:31 ok, AvneeshSingh 15:55:40 present+ 15:55:48 chair: AvneeshSingh 15:56:20 agenda+ 1. Further editorial changes done in the principles document of User experience guide for accessibility metadata. (For information purpose) 15:56:35 agenda+ 2. Editors are making progress on techniques. 15:57:12 agenda+ Discussion on localization workflow. 15:57:15 gpellegrino has joined #pcg-a11y 15:58:53 present+ 15:59:18 gautierchomel has joined #pcg-a11y 16:00:39 George has joined #pcg-a11y 16:00:39 Naomi has joined #pcg-a11y 16:00:56 present+ 16:00:57 present+ 16:01:15 present+ 16:01:41 CharlesL has joined #pcg-a11y 16:01:58 present+ 16:02:13 scribe+ gautierchomel 16:02:17 present+ 16:02:32 zakim, next agendum 16:02:32 agendum 1 -- 1. Further editorial changes done in the principles document of User experience guide for accessibility metadata. (For information purpose) -- taken up [from 16:02:35 ... AvneeshSingh] 16:02:48 https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated 16:03:18 JonasLillqvist has joined #pcg-a11y 16:03:33 AvneeshSingh: reviews and comments on the principle document are welcome. Editor's are still doing some fine tuning here, no major changes. 16:03:42 zakim, next agendum 16:03:42 agendum 2 -- 2. Editors are making progress on techniques. -- taken up [from AvneeshSingh] 16:03:53 Miia has joined #pcg-a11y 16:04:08 https://github.com/w3c/publ-a11y/pull/223 16:04:29 Bill_Kasdorf has joined #pcg-a11y 16:04:31 present+ 16:04:46 AvneeshSingh: we have a proposal for the form of those documents. 16:08:58 gpellegrino: before the end of year break we agreed to use a pseudo code approach. I made some proposals in the ONIX technics document on how to present the instructions. Among editors we agreed with a syntax (IF, AND, etc). We are searching for the best HTML markup to provide a nice reading experience in visual and non visual reading. We are near to a good result but still need some twicks. As soon as we are ready we'll make a proposal. 16:10:05 q? 16:10:17 George: we are also trying to maintain a common approach for both ONIX ans Schema technics. 16:10:37 zakim, next agendum 16:10:37 agendum 3 -- Discussion on localization workflow. -- taken up [from AvneeshSingh] 16:10:53 https://github.com/w3c/publ-a11y/issues/190 16:11:53 AvneeshSingh: we need to discuss how to practically work, where is the folder for localisation, what is the addition workflow. 16:16:12 romain has joined #pcg-a11y 16:16:45 q? 16:17:39 rickj_ has joined #pcg-a11y 16:17:45 present+ 16:18:05 q? 16:18:10 q+ 16:18:20 gautierchomel: three question : where do we store the localisations, in which format and which workflow (pull request or help from a service like transifex or gitlocalisation)? 16:20:43 q? 16:20:50 George: english is the main source. We should have it in the main repo. Then PR can be proposed by anyone with a github account. We should not judge the quality of the proposed vocabulary. 16:21:05 ack next 16:22:26 rickj_: we first need the canonical set. 16:26:26 CharlesL1 has joined #pcg-a11y 16:26:30 romain: in epubcheck we use transifex service, it provides an UI to people translating. All strings are stored in propeties files java specific format which is syncronised by transifex. The service also syncronise back to github. DIfferent similar services exists and most may have free service for open source projects. There are details to check but it's very simple for the user. 16:27:17 https://help.transifex.com/en/collections/3519116-file-formats 16:27:22 q? 16:29:13 romain: some tools may propose custom language codes allowing for variants of one language 16:29:16 q? 16:29:35 q+ 16:30:12 ack next 16:30:35 q+ 16:31:07 ack gaut 16:33:36 George: may we imagine having different localisations per public? 16:35:30 rickj_: may happen. 16:35:30 q? 16:36:37 rickj_: we can start by creating the structure (the canonical file) 16:36:52 q? 16:39:00 q? 16:39:47 q+ 16:40:02 ack char 16:41:43 FWIW - we do everything in UTF-8 no BOM 16:41:46 CharlesL1: using a tool will also help to avoid encoding errors and language codes classification. 16:43:08 as for Weblate, here here the supported input formats: https://docs.weblate.org/en/latest/formats.html 16:44:46 AvneeshSingh: gautier will share a json file with the editors and in the issue tracker.. 16:45:22 q? 16:45:24 AvneeshSingh: let the discussion follow in the same issue https://github.com/w3c/publ-a11y/issues/190 16:46:50 rrsagent, make minutes 16:46:51 I have made the request to generate https://www.w3.org/2024/01/11-pcg-a11y-minutes.html AvneeshSingh 16:47:03 rrsagent, make logs public 16:47:52 zakim, leave 16:47:52 leaving. As of this point the attendees have been AvneeshSingh, gpellegrino, Naomi, ChrisOliverOttawa, George, CharlesL, gautierchomel, Bill_Kasdorf, rickj_ 16:47:52 Zakim has left #pcg-a11y 16:50:15 George_ has joined #pcg-a11y 16:52:42 George_ has joined #pcg-a11y 17:03:33 George has joined #pcg-a11y 17:03:40 CharlesL1 has left #pcg-a11y 17:09:33 George has joined #pcg-a11y