<Lisa> topic : editors call

<Lisa> added erics issue tracking to https://docs.google.com/document/d/1xnoNFwfjJZbfadFiU-qOW49n4-gODbd_4ff5UDyYFTM/edit

<julierawe> https://docs.google.com/document/d/18rqamyGgYF1DAUHLhsXmR20FtN9AQSaPc9zpFNN1xgM/edit?pli=1#heading=h.527yvnol81gl

style guide

<scribe> Meeting: COGA Internationalization Subgroup

<Lisa> trigger paper is at https://docs.google.com/document/d/19RdKrd2aUJkZcm9FmIOvZ2jfn9JgYpFcqT5mubyQUAQ/edit#heading=h.p1q1f5jvv2f

Review the minutes from the June 20, 2024 Internationalization Subgroup meeting: https://www.w3.org/2024/06/20-coga-minutes

<tburtin> I joined the Color contrast related subgroup and brought up cognitive chunking by use of color. So like a background color behind a section that may not be seen by all users.

Gather feedback on how to address internationalization concerns within the new COGA structure (Lisa's request)

Lisa: We are putting together a new structure for COGA and we need to determine how to represent Internationalization.
... We want to make it clear that internationalization is a priority and we want a way to get feedback for where we might have missed patterns that need internationalization attention.
... We would like to show this at TPAC.
... We need to have a note or linked text that points to additional information about internationalization (find out more details in different languages, etc.) - this could link to a Wiki page or a Google Doc.
... When we put the structure together, we need to identify how we will handle additional information for certain patterns.
... For example, for use simple tense - we would want a pull-out box that would give information on how to address that patten in different languages. We would also want an editor's note that would tag a pattern as having internationalization issues, and there would be a link to additional information

<kirkwood> proof of concept, prior to prototype?

Lisa: I think we need 2 Google Docs - or maybe the pattern spreadsheet, where we could seek information from others for feedback.

<Lisa> scribe+ jan, lisa

<Lisa> jan do you have links ?

<Lisa> not latest version https://docs.google.com/presentation/d/1kKejFDuW0aTpQpR8Umvgp6NWGQM0v0lNzO60UpLRnTk/edit#slide=id.g2cb45388596_0_49

Lisa: Proposal 1: under the "How To" heading, we could add a link to a resource with how to implement the pattern within different languages or geographies. This could be as simple as a google doc.
... I think we would need link text on the how to for examples in different languages
... Proposal 2: Put an editor's note - a box that says, "This has been flagged for Internationalization Issues" and from there, we link to the pattern spreadsheet
... An editor's draft is a feedback mechanism, but it's a prototype so that we can see if this is usable.
... We would use the GitHub process to gather information on the Editor's draft.
... The Google Doc linked from the "How To" section in the new structure would be a resource document and have examples for how to implement patterns in different languages. We could add a link for how to contact the group if you're developing resources in different languages.

Please +1 if you're okay with taking this idea to Rain to have this included in the prototype:

+1

<Lisa> +1

<kirkwood> +1

<kirkwood> I am able to participate

<Frankie> +1

Review edited version of Lisa's recruiting email draft: https://docs.google.com/document/d/14urDbLrdkARcfQhDRUItUUYGm23bY5FAWnKx4xjpAM4/edit?usp=sharing

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: tburtn, EA, Rain, kirkwood, DavidSwallow, Lisa, kevin, Roy, tburtin, shawn, Jan, Jennie_Delisi, Eric_hind, JMcSorley, rashmi, julierawe, Frankie, JohnRochford, Chuck, LenB, Bmonteleone
Present: tburtn, EA, Rain, kirkwood, DavidSwallow, Lisa, kevin, Roy, tburtin, shawn, Jan, Jennie_Delisi, Eric_hind, JMcSorley, rashmi, julierawe, Frankie, JohnRochford, Chuck, LenB, Bmonteleone
Regrets: Julie
No ScribeNick specified.  Guessing ScribeNick: JMcSorley
Inferring Scribes: JMcSorley
WARNING: Could not parse date.  Unknown month name "07": 18 07 2024
Format should be like "Date: 31 Jan 2004"

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)