- From: Richard Ishida <ishida@w3.org>
- Date: Wed, 28 May 2014 17:34:08 +0100
- To: www International <www-international@w3.org>
http://www.w3.org/2014/04/24-i18n-minutes.html
Text version:
Internationalization Working Group Teleconference
24 Apr 2014
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2014Apr/0011.html
See also: [3]IRC log
[3] http://www.w3.org/2014/04/24-i18n-irc
Attendees
Present
Richard, aphillip, David, koji, JcK, matial
Regrets
Felix
Chair
Addison Phillips
Scribe
Addison Phillips
Contents
* [4]Topics
1. [5]Agenda
2. [6]Action Items
3. [7]Info Share
4. [8]radar
5. [9]publish two documents
6. [10]IRI Status, URLs, and Universal Access
7. [11]Time Zone IDs and HTML5.x
8. [12]CSS Text responses
* [13]Summary of Action Items
__________________________________________________________
Agenda
Action Items
[14]http://www.w3.org/International/track/actions/open
[14] http://www.w3.org/International/track/actions/open
close action-300
<trackbot> Closed action-300.
action-301
<trackbot> action-301 -- Addison Phillips to Add action items
link to agenda -- due 2014-04-03 -- OPEN
<trackbot>
[15]http://www.w3.org/International/track/actions/301
[15] http://www.w3.org/International/track/actions/301
close action-301
<trackbot> Closed action-301.
Info Share
JcK: Precis LC closed yesterday
... IESG will vote on shortly
... URNbis WG published draft on removing URN from URI
... all quiet on URN list
... but more notice on other lists
... "usual suspects saying usual things"
richard: good news on Chinese layout task force
richard: ... finished ruby part and now working on additional
chapters
richard: asked for english version for review
... also contacted layout experts on Uighur
... and Tibetan and Mongolian
richard: once enough done will have seminar before end of june
on layout of major Chinese languages
... mentioned TLD universal acceptance meeting in Oman
... they volunteered to help with travel
radar
[16]https://www.w3.org/International/wiki/Review_radar
[16] https://www.w3.org/International/wiki/Review_radar
publish two documents
<r12a> Authoring HTML: Handling Right-to-left Scripts
<r12a> [17]http://www.w3.org/International/docs/bp-html-bidi/
[17] http://www.w3.org/International/docs/bp-html-bidi/
<r12a> Authoring HTML: Language declarations
<r12a> [18]http://www.w3.org/International/docs/bp-html-lang/
[18] http://www.w3.org/International/docs/bp-html-lang/
richard: would like to publish as updates to the existing WG
Notes
<scribe> chair: all in favor of publishing both documents?
<r12a> +1
addison: +1
<David> +1
<JcK> +1
<matial> +1
<scribe> chair: resolved to publish
<scribe> ACTION: richard: publish two updated "Authoring HTML"
WG Notes [recorded in
[19]http://www.w3.org/2014/04/24-i18n-minutes.html#action01]
<trackbot> Created ACTION-302 - Publish two updated "authoring
html" wg notes [on Richard Ishida - due 2014-05-01].
IRI Status, URLs, and Universal Access
[20]https://www.w3.org/International/wiki/IRIStatus
[20] https://www.w3.org/International/wiki/IRIStatus
(addison gives a summary)
addison: turn this into what? blog post originally, but maybe
"requirements for IRI"?
JcK: stepping into large mess
richard: might be too formal as a note
... one suggestion
... title should change
... should say "URLs"?
"Requirements for internationalized URLs"
JcK: "what's happening with I18N in URLs"?
addison: okay, can go with that
<David> How about "Internationalisation, IRIs, URIs and URLs"
Time Zone IDs and HTML5.x
[21]https://www.w3.org/International/wiki/HTML5TimeZone
[21] https://www.w3.org/International/wiki/HTML5TimeZone
1979-10-14T12: 00:00.001@America/New_York
... 00:00.001-04:00
CSS Text responses
koji: responded to the easy feedback :-)
... either fixed or not fixed items
... plan is that I will make another pass
... then in week of 6 May
... will be in SF to work with fantasai
... to work on the hard ones
... so reply to issues in my response
addison: problem with kashida: mentioned but then ignores
issue-335
<trackbot> issue-335 -- health warnings for when language not
known -- open
<trackbot> [22]http://www.w3.org/International/track/issues/335
[22] http://www.w3.org/International/track/issues/335
addison: how can this be tested if non-specific
... very flexible
koji: text not necessarily interoperable
... like one UA does kashida but not antoher
... if we know requirements very well
richard: there are different styles of arabic
... naskh, nastaliq, ruqk
... some you do not do kashida
... if true, need a switch for kashida
r12a: kashida a lot lot lot more complicated than that
koji: depends on fonts?
richard: on the style of the font
koji: if a value, need to describe how to implement
addison: can implement "off" quite easily :-)
koji: spec mentions text elongation for arabic--that's
"kashida" right?
richard: there is a Unicode character called kashida or tatweel
... the real meaning is "elongation"
... two different ways to using the word
... but not addition of baseline characters
<matial> ??P35 is me
koji: kashida only between letters
<matial> zkim, ??P35 is me
koji: not to spaces
<aphillips> richard: ruqha vs. naskh
<aphillips> ... one has space effects and the other prefers
inside words
<koji> Justification adjusts spacing at word separators only
(effectively varying the used ‘word-spacing’ on the line).
<koji> [23]http://dev.w3.org/csswg/css-text/#text-justify
[23] http://dev.w3.org/csswg/css-text/#text-justify
<koji> Word-separator characters are characters whose purpose
and general usage is to separate words. In [UNICODE] this
includes the space (U+0020), the no-break space (U+00A0), the
Ethiopic word space (U+1361), the Aegean word separators
(U+10100,U+10101), the Ugaritic word divider (U+1039F), and the
Phoenician Word Separator (U+1091F). If there are no
word-separator characters, or if a word-separating character
has a zero advance width (such as the zero width space U+20
<koji> 0B) then the user agent must not create an additional
spacing between words. General punctuation and fixed-width
spaces (such as U+3000 and U+2000 through U+200A) are not
considered word-separator characters.
<koji> [24]http://dev.w3.org/csswg/css-text/#word-separator
[24] http://dev.w3.org/csswg/css-text/#word-separator
<aphillips> koji: would be great feedback if you could make it
<aphillips> richard: phrase separators
<aphillips> issue-313
<trackbot> issue-313 -- Definition of grapheme clusters -- open
<trackbot> [25]http://www.w3.org/International/track/issues/313
[25] http://www.w3.org/International/track/issues/313
<aphillips> richard: helpful to do both at same time
<aphillips> issue-308
<trackbot> issue-308 -- Definition of 'grapheme cluster' --
open
<trackbot> [26]http://www.w3.org/International/track/issues/308
[26] http://www.w3.org/International/track/issues/308
<aphillips> koji: current wording is intentional
<koji> A grapheme cluster is what a language user considers to
be a character or a basic unit of the script. The term is
described in detail in the Unicode Technical Report: Text
Boundaries [UAX29]. This specification uses the extended
grapheme cluster definition in [UAX29] (not the legacy grapheme
cluster definition). The UA may further tailor the definition
as required by typographical tradition.
<koji> Within this specification, the ambiguous term character
is used as a friendlier synonym for grapheme cluster. See
Characters and Properties for how to determine the Unicode
properties of a character.
<matial> bye
Summary of Action Items
[NEW] ACTION: richard: publish two updated "Authoring HTML" WG
Notes [recorded in
[27]http://www.w3.org/2014/04/24-i18n-minutes.html#action01]
[End of minutes]
Received on Wednesday, 28 May 2014 16:34:36 UTC