Meeting minutes
Addressing I18N Horizontal Review Group feedback
Kathy: This is a Daniel topic
Daniel: For the ACT 1.1 format to be recommended we have a horizontal review and the localisation group have provided feedback we are actioning
… we need to work out or include some clarification in 3 pull requests (PR)
Determine if a rule identifier is unique
Daniel: This one is about how we can determine if an identifier is unique, and they explained how this can be done. Kathy made some suggestions and I actioned them just before the call
Kathy: I have a question about the process, like when I had to create a new rule, I used a randomised generator but how can we tell it is unique?
Helen: You can do a quick search
Daniel: No Kathy wanted to know if there is a way for the automation to check though?
Kathy: Can we add it?
Daniel: They also asked if upper or lower case has a difference? So as we use lower case only this is less of an issue
… any other suggestions to the PR?
Kathy: Are we recommending that the IDs are lower case only? Or letting people decide?
Daniel: Yes, Wilco felt it should be this way as easier
Kathy: We do not have a limitation of length implemented?
Daniel: No- there are none yet until Helen makes a long one to prove a point!
Suggestions for rules to be sent for AGWG approval -- taken up
Reinforce that ACT Rules are localizable
Daniel: The format we use to write the rules must be localisable, so the markdown we use is able to be translated
… We will be more explicit to incorporate this
Kathy: I added a comment on this?
Daniel: I added a reply but you cannot see it as I started a review so you won't see it yet
Kathy: Ok we need to add the term "Localisation" (that is Localization if US spellings are used) to our glossary
Daniel: That is a valid point - and we must use US spellings so a Z is used
<Daniel> I18n page with explanations about localization versus internationalization
Daniel: I added a link we can use for our glossary as this is from 2005, we need to check it is still valid#
Add assumption that text has metadata specifying its language and writing direction
Daniel: I assume the group agrees with this and we will merge it
Daniel: They were confused that meeting WCAG does the assumption means the text has metadata specifying the language and writing direction?
… we are already using it so we are fulfilling it and no comments from Kathy
Kathy: Where it says it assumes the text has metadata, so they mean document?
Daniel: Yes it is not the format you are using, but this is something done in the metadata - can you add a comment?
Kathy: I will add a suggestion to use the rule document that will specify this to be actioned
Daniel: Maybe we should say rule not just rule document
… any other comments?
Helen + Sage + Shunguo - looks good
<Kathy> +1 also
<Daniel> proposed resolution: The group agrees to propose these three changes to the i18n working group
RESOLUTION: The group agrees to propose these three changes to the i18n working group