– DRAFT –
(MEETING TITLE)

1. Further editorial changes done in the principles document of User experience guide for accessibility metadata. (For information purpose) AvneeshSingh]

<AvneeshSingh> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated

AvneeshSingh: reviews and comments on the principle document are welcome. Editor's are still doing some fine tuning here, no major changes.

2. Editors are making progress on techniques.

<AvneeshSingh> w3c/publ-a11y#223

AvneeshSingh: we have a proposal for the form of those documents.

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.

George: we are also trying to maintain a common approach for both ONIX ans Schema technics.

Discussion on localization workflow.

<AvneeshSingh> w3c/publ-a11y#190

AvneeshSingh: we need to discuss how to practically work, where is the folder for localisation, what is the addition workflow.

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)?

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.

rickj_: we first need the canonical set.

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.

<romain> https://help.transifex.com/en/collections/3519116-file-formats

romain: some tools may propose custom language codes allowing for variants of one language

George: may we imagine having different localisations per public?

rickj_: may happen.

rickj_: we can start by creating the structure (the canonical file)

<rickj_> FWIW - we do everything in UTF-8 no BOM

CharlesL1: using a tool will also help to avoid encoding errors and language codes classification.

<romain> as for Weblate, here here the supported input formats: https://docs.weblate.org/en/latest/formats.html

AvneeshSingh: gautier will share a json file with the editors and in the issue tracker..

AvneeshSingh: let the discussion follow in the same issue w3c/publ-a11y#190