– DRAFT –
I18N ⇔ CSS

Agenda

<gb> Issue 10363 not found

Action Items

<gb> Found actions in w3c/i18n-actions: #99, #68, #35, #16, #11

#99

<gb> Action 99 ping unicode about emphasis skip property (see our #530) (on aphillips) due 2024-05-28

close #99

<gb> Closed issue #99

#68

<gb> Action 68 follow up with florian about testing with kindle (on aphillips) due 2024-01-25

close #68

#35

<gb> Action 35 review quote character edits of CSS #5478 with CSS (on fantasai) due 2023-08-30

<gb> Closed issue #68

florin: did discuss with css, good solution but hasn't been edited in
… are we clear that for 'q' we want parent language. for elements not-'q', is going off the parent correct??
… if you e.g. added open/close quote on say blockquote

fantasai: pull quotes are more common like that

florian: if we never work off element but always off parent

forian: think it might be "it depends"

addison: only quotes?

ACTION: florian: write an issue about quote auto behavior for non-q elements

<gb> Created action #107

close #35

<gb> Closed issue #35

#16

<gb> Action 16 Keep track of line-breaking in Korean for i18n-discuss#11 (on aphillips) due 1 Jan 2024

#11

<gb> Action 11 Triage all css properties to determine which are logical, physical, or na by default (on frivoal) due 18 Jul 2023

<gb> Issue 10363 not found

Info Share and Progress Reports

florian: wg that hosts ruby expires and was extended so we can keep working

addison: we have folks working on a review

florian: did file HR review requests

Reorganization of LREQ documents

<r12a> https://www.w3.org/TR/laoo-gap/

<r12a> https://www.w3.org/TR/laoo-lreq/

richard: just a heads up, just published 3 more of these, kashmiri, uighur, urdu
… a lot of these didn't exist before, some did exist but were manipulated
… couple things going on
… structure of the docs now follows a particular order
… the headers and order is the same across all of them; follows my personal work on orthography
… mostly list of links; some don't go anywhere useful
… standard categories for the links; close to the language enablement index we used to have
… that was not very helpful if you were working on a particular language/ortho
… many sections like to stuff in my orthography notes
… was considering copying my stuff into these docs
… linked instead.

richard: some of these docs are just links at the moment, but if someone decides to write stuff they can

<r12a> https://www.w3.org/TR/alreq/

richard: if you look at alreq stuff
… already had loads of stuff. repurposed
… at beginning of sections

richard: I'm finding it very helpful

florian: two pieces of feedback
… inlining vs. not. this makes sense for editing
… for reading, probably fine. if just looking for info. small feedback, not a strong opinion
… important that info be backed up by w3c systems

richard: interesting idea; had other things ahead in priorities
… in terms of overview
… each one contains the script overview, mainly taken from my stuff
… also still ave laanguage enablement index

richard: didn't include all that stuff for (reasons); some IP concerns

fantasai: plan is to put all content in your docs?

richard: no, what we are doing is pointing to my existing content rather than copying in and maintaining in two places

fantasai: is the plan to maintain in your docs?

<gb> Issue 10363 not found

CSS#10363

csswg-drafts#10363

<gb> Issue 10363 [css-text-3][css-text-4] Japanese small kana and `line-break: normal` (by fantasai) [css-text-3] [css-text-4] [Agenda+] [i18n-tracker] [i18n-jlreq] [Agenda+ i18n]

fantasai: was looking into webkit line breaking
… was inconsistent
… in strict, can't wrap before small kana but can in loose
… this is unexpected from some japanese users, FF is already shipping
… should we just change the default?

florian: in issue called this "proposal B"
… currently not "up to you", you're supposed to break

florian: would support either A or B but prefer B

<fantasai> https://www.w3.org/TR/jlreq/#characters_not_starting_a_line

atsushi: in jlreq

florian: 3.1.7 in jlreq mentions small kana (in princple no line should start...)

<xfq> In principle, no line should begin with [...] small kana (cl-11)

atsushi: need to go back to jlreq folks

florian: please be clear we are only discussing *default* behavior, can still allow

fantasai: currently 50/50 in terms of implementation

ACTION: atsushi: talk to jlreq about *default* behavior of line breaking with small kana (cf. csswg-drafts#10363)

<gb> Cannot create action. Validation failed. Maybe atsushi is not a valid user for w3c/i18n-actions?

ACTION: himoren: talk to jlreq about *default* behavior of line breaking with small kana (cf. csswg-drafts#10363)

<gb> Cannot create action. Validation failed. Maybe himoren is not a valid user for w3c/i18n-actions?

gb, atsushi is himoren

ACTION: himorin: talk to jlreq about *default* behavior of line breaking with small kana (cf. csswg-drafts#10363)

<gb> Created action #108

gb, atsushi is himorin

<r12a> #108 note w3c/csswg-drafts#10363

<gb> Added comment

<r12a> #108 note https://www.w3.org/TR/css-text-3/#line-break-property

<gb> Added comment

<r12a> #108 note https://www.w3.org/TR/jlreq/#characters_not_starting_a_line

<gb> Added comment

<gb> Issue 10363 not found

Emphasis Skip

<xfq> addison: the issue about the code points emphasis marks should skip

... about maintaining the list in Unicode
… we can't change General_Category
… but maybe we could add a property
… there are differences between punctuation and symbol
… that occured in Unicode many years ago
… maybe there's a path forward about it

florian: I don't know
… I'm not excessively concerned about trying to write an initial version of it
… if we create a base set to start from there, I think we can help with that
… but the whole point to have Unicode maintain it is that they can maintain it

addison: it might be more visible in the Unicode space if they were maintaining it
… other text applications that we don't know about would come along

florian: absolutely
… in principle, it's generic
… if we're more specific than we should be, I don't think it's intentional

addison: OK

florian: the ability to switch on and off and make exceptions and tweak it in one way or another, that's on us
… but the basis about what is it supposed to apply to ought to be generic

addison: I agree

florian: I have a very small update
… about CSS text-wrap: balance
… Chrome had not implmented yet
… I did reach out
… they say it's scheduled
… they're gonna try and fix it somewhere in autumn

florian: in the future if there's any long living property that you want to suggest should be split into a bunch of longhands and become a shorthand
… this is not always trivial
… for object model reasons
… the WG is trying to find general solutions to that problem
… whether we will succeed remains to be seen
… it's a case by case problem at the moment