- From: r12a <ishida@w3.org>
- Date: Thu, 13 Dec 2018 15:30:38 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2018/12/13-i18n-minutes.html
text extract follows:
- DRAFT -
Internationalization Working Group Teleconference
13 Dec 2018
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2018Dec/0011.html
Attendees
Present
addison, andrewc, richard, atsushi, xfq, David, JcK
Regrets
Chair
Addison Phillips
Scribe
addison
Contents
* [3]Topics
1. [4]Agenda and Minutes
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR and Active Work Review
5. [8]WPUB issue 354
6. [9]Review CSS-Text
7. [10]AOB?
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
Agenda and Minutes
Action Items
[13]https://www.w3.org/International/track/actions/open
[13] https://www.w3.org/International/track/actions/open
action-767?
<trackbot> action-767 -- Richard Ishida to Change the date used
in the member page for the meeting info -- due 2018-12-13 --
OPEN
<trackbot>
[14]https://www.w3.org/International/track/actions/767
[14] https://www.w3.org/International/track/actions/767
close action-767
<trackbot> Closed action-767.
Info Share
RADAR and Active Work Review
[15]https://github.com/w3c/i18n-activity/projects/1
[15] https://github.com/w3c/i18n-activity/projects/1
[16]http://w3c.github.io/i18n-activity/reviews/
[16] http://w3c.github.io/i18n-activity/reviews/
<scribe> ACTION: addison: review css-text-3 comments for
closure opportunities
<trackbot> Created ACTION-768 - Review css-text-3 comments for
closure opportunities [on Addison Phillips - due 2018-12-20].
[17]http://w3c.github.io/i18n-activity/projects/
[17] http://w3c.github.io/i18n-activity/projects/
richard: discused with Katy about article redesign this week
... updated tests about styling, did results page a bit
differently
<r12a>
[18]https://w3c.github.io/i18n-tests/results/css-text-shaping
[18] https://w3c.github.io/i18n-tests/results/css-text-shaping
richard: wrote more like article
... what do you think/
WPUB issue 354
[19]https://github.com/w3c/wpub/issues/354
[19] https://github.com/w3c/wpub/issues/354
(intro)
richard: wrote something up
<r12a>
[20]https://w3c.github.io/wpub/#manifest-default-language-and-d
ir
[20] https://w3c.github.io/wpub/#manifest-default-language-and-dir
richard: they define a way to define a language and direction
for a whole collection
... if data from another place, needs its own lang/dir
... confusing language metadata with language information for a
particular string, maybe?
addison: way to say "this whole 'book' is in a language/dir"
andrewc: 3 ways of describing language
... language of object/metadata, language of book, langauge of
string
... you'll see multiple language, including transliterations
addison: in metadata, manifest
richard: we make those distinctions in our article
<r12a>
[21]https://www.w3.org/International/questions/qa-http-and-lang
.en#metadata
[21]
https://www.w3.org/International/questions/qa-http-and-lang.en#metadata
addison: working on the string level, can declare lang but not
dir, we see as a problem
... a 'dir' attribute wouldn't be associated in a generic RDF
processor with the object's direction
... but who uses a generic RDF processor, lacks business logic?
richard: they say definition of 'auto' is "first strong", but
may not be if surrounded by isolate controls
... further down, once base direction is identified... etc...
... should say "first strong should be determiend according to
UBA"
... doesn't take markup into account either
<scribe> ACTION: addison: write back to Ivan and WPUB stating
our position and asking for clarification for why they can't
accommodte it; also mention FSI issues
<trackbot> Created ACTION-769 - Write back to ivan and wpub
stating our position and asking for clarification for why they
can't accommodte it; also mention si issues [on Addison
Phillips - due 2018-12-20].
Review CSS-Text
<r12a> [22]https://github.com/w3c/csswg-drafts/issues/698
[22] https://github.com/w3c/csswg-drafts/issues/698
richard: propose to close, what causes cursive joining to break
... if you for example highlight an arabic letter in a word and
put a span around it
... conclusion is what is currently in the spec text
<r12a> [23]https://drafts.csswg.org/css-text/#boundary-shaping
[23] https://drafts.csswg.org/css-text/#boundary-shaping
richard: if margin, vertical align, or isolating, breaks
... if you set direction or font style, don't break joining
(unless it's something weird, like trying to color part of a
ligature)
... everything else should continue
najib: want to go back to cursive joining. if you want an image
instead of letter inside word. should it be taken into account
by spec?
richard: can't assume alway a join?
addison: should shape, right?
najib: is this a feature of the spec or not?
... if you try with an image in html, falls into inline element
with no border or padding, so according to spec it should join
richard: another discussion is about drop caps
... some say big letter should have joining form
... and maybe second letter
... that's a different situation fro what's described here
... probably should mention it?
... raise issue?
addison: raise new issue and close other
... any objection to closing other?
richard: tracker links to either our issues list or to theirs
AOB?
<scribe> scribenick: addison
Summary of Action Items
[NEW] ACTION: addison: review css-text-3 comments for closure
opportunities
[NEW] ACTION: addison: write back to Ivan and WPUB stating our
position and asking for clarification for why they can't
accommodte it; also mention FSI issues
Summary of Resolutions
[End of minutes]
Received on Thursday, 13 December 2018 15:30:42 UTC