Meeting minutes
acribe+
Agenda Review
Action Items
<gb> Found actions in w3c/i18n-actions: #58, #57, #56, #53, #47, #43, #35, #33, #18, #16, #12, #11, #8, #7, #5, #4
<addison> #58
<gb> Action 58 revise localizable-manifests in light of tpac conversation and new explainer (on aphillips) due 2023-11-09
addison: agenda item for today, working on
<addison> close #58
<addison> #57\
<gb> Closed action #58
<gb> Action 57 add localizable content definition to the glossary (on xfq) due 2023-11-09
xfq: raised a PR for this, PR is still open
addison: let's review today
<addison> close #57
<gb> Closed action #57
<addison> #56
<gb> Action 56 check on permissions with w3ctag and follow up with plh on looking for notifications (on xfq) due 2023-11-02
<addison> close #56
<gb> Closed action #56
<addison> #53
xfq: done for permission at w3ctag
<gb> Action 53 come up with a set of information CSS want the i18n group to provide support for generic font families (on frivoal, fantasai) due 2023-11-01
<addison> #47
<gb> Action 47 make the CSSWG aware of Warichu (on frivoal) due 2023-10-04
<addison> #43
<gb> Action 43 pull together the list of win/mac/etc apis for setting base direction and/or language (on aphillips) due 2023-09-18
addison: 53 and 47 is CSS
<addison> #35
<gb> Action 35 make the edits of CSS #5478 (on fantasai) due 2023-08-30
addison: started on 43 but still working, pending
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
addison: 33, keep working on closing ones marked as close?
… added as agenda item
<addison> #18
<gb> Action 18 Have informal explanation sessions about counter style translations with csswg members (on frivoal, fantasai)
<addison> #16
<gb> Action 16 Keep track of line-breaking in Korean for i18n-discuss#11 (on aphillips)
<addison> #12
<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips)
<addison> #11
<gb> Action 11 Triage all css properties to determine which are logical, physical, or na by default (on frivoal)
addison: 12, working, finish up with cleaning things, keeping alive for a while
<addison> #8
<gb> Action 8 Create pr against canvas formatted text (on aphillips)
<addison> #7
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github)
<addison> #5
<gb> Action 5 Check into how to list questions at the top of a digest and/or improve lang enablement communications (on r12a)
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on r12a)
Info Share
<addison> https://
addison: had call yesterday with COGA colleages, minutes above
… reasonable start with them
r12a: got with them on interesting action items, seeking for another opportunity incl. finding experts for input to there
<gb> Cannot create action. Validation failed. Maybe addision is not a valid user for w3c/i18n-actions?
ACTION: addison: follow up with julie rowe on next steps with coga such as a work plan
<gb> Created action #59
<r12a> https://
r12a: post on mastdon above, on supporting fonts
[r12a described about images and backgrounds]
RADAR Review
<addison> https://
addison: nothing here
… some in awaiting comment resolution could be marked as completed...
review localizable content PR
<xfq> w3c/
xfq: PR above
xfq: added localizable content entry to glossary
<xfq> https://
xfq: definition is adopted from localizable text
… didnot merged two entries, since both are used for different envoirnment
r12a: second 'contents' should be single form?
addison: depending on what 'document' is
addison: localizable text could be string content or text content
xfq: will update text around document
Working with Time and Timezones
<addison> https://
addison: have a WG note, long standing one on timezone
<addison> https://
addison: working for revision on this note
addison: couple of things wanted to do, publish WG draft over WG note, for getting comments
addison: super happy to get feedback on this document
[silent for comment]
r12a: is there any used styling in 2.4?
addison: historical. just glossary one
<r12a> https://
addison: we will want to go through this article
r12a: don't want to change, but perform checking
Localizable Manifests
<addison> https://
addison: deploy preview as above
… some material should go to another document, but not yet
addison: both miniapp and manifest are active, and we need to update /TR/ one
… number of addition as 2.1
… section 3 is new, indicating language and direction
addison: some part could live in string-meta, but need to be in specific document alos
xfq: some text are mentioned as in string-meta, but @@@@
addison: merge this and publish to /TR/?
<xfq> https://
xfq: +1 to merge
… added a PR for definitions
addison: all in glossary one
Needs Attention issues for WG review
<addison> i18n-activity#1763
<gb> Issue 1763 Make computation of directionality account for Shadow DOM. (by w3cbot) [close?] [tracker] [s:html] [needs-attention] [i:bidi-text] [alreq] [hlreq] [t:bidi_markup]
addison: issues marked as close? but asking for review around
addison: 1763, has middle sized thread with implementation issues
r12a: to consult with fantasai?
<addison> i18n-activity#1361
<gb> Issue 1361 input-purpose `language` should reference BCP47 (by w3cbot) [close?] [needs-attention] [needs-resolution] [s:adapt] [t:lang_values]
addison: older issue related to CR or something
… question is whether something needs to be performed?
addison: associated to long thread in whatwg/html#6519
<gb> Issue 6519 [not found]
<gb> Issue 6519 [not found]
<gb> Issue 6519 4.10.18.7 Autofill & the language value (by johnfoliot) [i18n-tracker]
<addison> i18n-activity#1006
<gb> Issue 1006 Informal spellings in specifications (by w3cbot) [close?] [tracker] [needs-attention]
addison: 1006, CSS general purpose one in spellings
… just to look into from translations point of view
xfq: will take this
… English usage in CSS specs
RESOLUTION: We consider informal spellings to be typos to be fixed when found and avoided if possible
addison: or maybe more general usage
r12a: this is CSS resolution, but not of us
… sounds good to me
<addison> i18n-activity#404
<gb> Issue 404 Should generalYear (etc.) be gregorianYear (etc.)? (by aphillips) [close?] [s:owl-time] [needs-attention] [needs-resolution] [t:loc_time]
addison: 404 is old one, on naming
… if they use general, many other calendars exist
… it seems they did not consider my comment
<addison> sdw#888
<r12a> +1 to close from me
+1 to close, looking at spec text...
xfq: from the last comment, it seems they support only gregorian, but not others
addison: they tended to support others, but not included yet
xfq: spec text says, not limited to number used for gregorian
<xfq> +1 to close
addison: moving on?
<addison> i18n-activity#370
<gb> Issue 370 Standardized way to add indications of text direction (by r12a) [close?] [s:shacl] [needs-attention] [needs-resolution] [t:lang_declaration]
addison: this is about standalization of text direction in data-shapes
… quite old as 2017
<addison> close i18n-activity#370
<gb> Cannot close issue #370. Forbidden.
r12a: I think we've discussed with them whether this is ok or not
<addison> https://
addison: item in above email, comment in next call
AOB?
Using GH Discussions
r12a: kida-san is interested in Discussions feature
… discussions in thread, could be interested for us also
… can have comments, and comments to a comment
… could be useful for jlreq-d discussions
… one issue is notification, and xfq and I are talking with Dom for notification email
<xfq> https://
addison: in message format group, we are using issue and discussion, also
… had some success in past, but tend not to use recently
r12a: having some wiki pages, but cannot have comments there
xfq: will talk with Dom
ACTION: xfq: follow up with dom about github discussion notifications
<gb> Created action #60
r12a: any info for upward arrow?
xfq: there are also thumb-up button etc.
<xfq> https://
addison: will be shown as order with clicking 'top'