Internationalization Working Group - Activity in 2017
No matches.
TR publications
-
1 document published.
-
Requirements for Chinese Text Layout 中文排版需求 published as a Working Draft. History of Requirements for Chinese Text Layout 中文排版需求
-
Participants
-
1 participant joined.
-
Alolita Sharma (Amazon) joined.
-
GitHub
w3c/clreq
-
4 issues opened.
-
Typefaces for Chinese Characters w3c/clreq#164, by @c933103.
-
Translate the glossary w3c/clreq#163, by @xfq.
-
Fullwidth full stop or half width full stop? w3c/clreq#161, by @c933103.
-
Style for counter in ordered list using Chinese character. w3c/clreq#158, by @c933103.
-
-
6 issues closed.
-
Translate the glossary w3c/clreq#163.
-
About the two glossary formats w3c/clreq#155.
-
L2/14-006，关于中文标点的 standardized variant w3c/clreq#121.
-
Horizontal lines in vertical text w3c/clreq#151.
-
單雙引號的解釋 w3c/clreq#117.
-
刪節號中文的敘述 w3c/clreq#116.
-
-
1 issue reopened.
-
Fullwidth full stop or half width full stop? w3c/clreq#161, by @xfq.
-
-
9 issues received 20 new comments.
-
Fullwidth full stop or half width full stop? w3c/clreq#161 (5 comments by @c933103, @ryukeikun, @upsuper, @xfq)
-
3 pull requests opened.
-
Add Hui Jing as an editor w3c/clreq#162, by @xfq.
-
Translate "tab" w3c/clreq#160, by @xfq.
-
Translate "typography" w3c/clreq#159, by @xfq.
-
-
5 pull requests merged.
-
Add Hui Jing as an editor w3c/clreq#162.
-
Translate "typography" w3c/clreq#159.
-
Translate some sentences to SC w3c/clreq#148.
-
Change "惊叹号" to "叹号" w3c/clreq#157.
-
Proof-reading up to 4.1.5 w3c/clreq#150.
-
-
1 pull request closed.
-
Translate "tab" w3c/clreq#160.
-
-
6 pull requests received 10 new comments.
w3c/charmod-norm
-
4 issues opened.
-
Add code points to example 11 w3c/charmod-norm#157, by @aphillips.
-
Discouraging Legacy Character Encodings w3c/charmod-norm#155, by @stpeter.
-
Various Editorial Suggestions w3c/charmod-norm#154, by @stpeter.
-
Editorial comments on http://aphillips.github.io/charmod-norm/ w3c/charmod-norm#152, by @r12a.
-
-
2 issues closed.
-
Various Editorial Suggestions w3c/charmod-norm#154.
-
Editorial comments on http://aphillips.github.io/charmod-norm/ w3c/charmod-norm#152.
-
-
3 issues received 4 new comments.
-
4 pull requests opened.
-
Address #157 (Add code points to Example 11) w3c/charmod-norm#159, by @aphillips.
-
Update changelog. Add a missed citation. w3c/charmod-norm#158, by @aphillips.
-
Fixes #154 w3c/charmod-norm#156, by @aphillips.
-
Merging changes to mainline w3c/charmod-norm#153, by @aphillips.
-
-
4 pull requests merged.
-
Address #157 (Add code points to Example 11) w3c/charmod-norm#159.
-
Update changelog. Add a missed citation. w3c/charmod-norm#158.
-
Fixes #154 w3c/charmod-norm#156.
-
Merging changes to mainline w3c/charmod-norm#153.
-
w3c/jlreq
-
3 issues opened.
-
Missing condition in section 3.3.8, first "f." w3c/jlreq#15, by @emuller-amazon.
-
List style type. w3c/jlreq#12, by @c933103.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Fix typo: 統合類 → 等号類 w3c/jlreq#13, by @mashabow.
-
w3c/alreq
-
1 issue opened.
-
Section on Ellipsis and other Truncations w3c/alreq#156, by @kojiishi.
-
w3c/i18n-activity
-
5 issues opened.
-
Abstract wording inexact w3c/i18n-activity#521, by @aphillips.
-
What should autocapitalize default be w3c/i18n-activity#519, by @r12a.
-
Allow multiple meta-description elements if they have different lang values? w3c/i18n-activity#518, by @r12a.
-
Use HTML rather than PDF w3c/i18n-activity#517, by @r12a.
-
[projects] mongolian summary link is broken w3c/i18n-activity#516, by @behnam.
-
-
3 issues closed.
-
i18n-ISSUE-249: positioning of ruby and emphasis marks together w3c/i18n-activity#22.
-
i18n-ISSUE-248: terminology related to spaces w3c/i18n-activity#21.
-
[projects] mongolian summary link is broken w3c/i18n-activity#516.
-
-
25 issues received 28 new comments.
-
Use of fillLineGap might cause glyph collisons w3c/i18n-activity#399 (2 comments by @nigelmegitt, @skynavga)
-
i18n-ISSUE-249: positioning of ruby and emphasis marks together w3c/i18n-activity#22 (2 comments by @r12a)
-
i18n-ISSUE-248: terminology related to spaces w3c/i18n-activity#21 (2 comments by @aphillips, @r12a)
-
`text-decoration-skip: ink` should allow not to skip for CJK and certain ideographic scripts w3c/i18n-activity#390 (1 comment by @r12a)
-
text-decoration-skip: ink should allow not to skip for CJK and certain ideographic scripts w3c/i18n-activity#435 (1 comment by @r12a)
-
default position for text-decoration-line in vertical text w3c/i18n-activity#394 (1 comment by @r12a)
-
w3c/predefined-counter-styles
-
4 issues opened.
-
New counting style proposal: japanese-hitotsu w3c/predefined-counter-styles#20, by @c933103.
-
New counting style proposal: Ideographic counting mark w3c/predefined-counter-styles#19, by @c933103.
-
New counting style proposal: cjk-stem-branch w3c/predefined-counter-styles#18, by @c933103.
-
description for greek counter w3c/predefined-counter-styles#17, by @c933103.
-
w3c/i18n-request
-
1 issue opened.
-
CSS Writing Modes Level 4 > Ongoing w3c/i18n-request#71, by @aphillips.
-
w3c/klreq
-
1 issue opened.
-
Style for counter in ordered list using Korean character. w3c/klreq#22, by @c933103.
-
w3c/ilreq
-
7 issues closed.
-
Letter-spacing questions w3c/ilreq#24.
-
Hyphenation case 1 and 2 intentions w3c/ilreq#21.
-
Variable terminology: purnaviram/danda w3c/ilreq#19.
-
Two dandas or double danda ? w3c/ilreq#18.
-
Unicode code point values in text w3c/ilreq#17.
-
Variable spelling for purnaviram w3c/ilreq#16.
-
Unicode chart w3c/ilreq#15.
-
-
8 issues received 11 new comments.
-
When does the ABNF work for Tamil consonant clusters? w3c/ilreq#31 (4 comments by @miloush, @r12a, @Richard57)
-
w3c/i18n-drafts
-
2 issues opened.
-
[questions/qa-bidi-unicode-controls] w3c/i18n-drafts#131, by @faceless2.
-
[articles/inline-bidi-markup] General update w3c/i18n-drafts#130, by @r12a.
-
-
1 issue closed.
-
[questions/qa-bidi-unicode-controls] w3c/i18n-drafts#131.
-
-
2 issues received 5 new comments.
-
[questions/qa-bidi-unicode-controls] w3c/i18n-drafts#131 (4 comments by @aphillips, @faceless2, @r12a)
-
[techniques/authoring-html] Make the text in the <summary> elements not selectable? w3c/i18n-drafts#123 (1 comment by @xfq)
-
-
1 pull request opened.
-
Update Firefox icon w3c/i18n-drafts#129, by @xfq.
-
-
1 pull request merged.
-
Update Firefox icon w3c/i18n-drafts#129.
-
w3c/bp-i18n-specdev
-
1 pull request merged.
-
Update some links w3c/bp-i18n-specdev#27.
-
w3c/typography
-
1 pull request merged.
-
language-matrix, trivial markup fix w3c/typography#53.
-
w3c/string-search
-
1 issue opened.
-
Include the NoToFu font? w3c/string-search#6, by @xfq.
-
-
2 pull requests opened.
-
http -> https w3c/string-search#5, by @xfq.
-
See attached commits. Updating string-search and fixing Respec issues. w3c/string-search#4, by @aphillips.
-
-
2 pull requests merged.
-
http -> https w3c/string-search#5.
-
See attached commits. Updating string-search and fixing Respec issues. w3c/string-search#4.
-
Participants
-
1 participant joined.
-
Florian Rivoal (W3C Invited Experts) joined.
-
GitHub
w3c/charmod-norm
-
2 issues opened.
-
User values w3c/charmod-norm#143, by @r12a.
-
Other Types of Equivalence are other types of equivalence w3c/charmod-norm#139, by @r12a.
-
-
4 issues closed.
-
Example 7 shouldn't be in a panel w3c/charmod-norm#130.
-
Show ES6 escapes w3c/charmod-norm#129.
-
NFC doesn't combine 'any' combining mark w3c/charmod-norm#125.
-
Example 4 table w3c/charmod-norm#123.
-
-
11 issues received 24 new comments.
-
which characters, exactly, should be removed in the matching algorithm? w3c/charmod-norm#117 (1 comment by @aphillips)
-
Other Types of Equivalence are other types of equivalence w3c/charmod-norm#139 (1 comment by @aphillips)
-
11 pull requests opened.
-
Fix the exampleChar style to have named fonts ahead of NoToFu w3c/charmod-norm#151, by @aphillips.
-
Addressed JCK's comments (see email thread at https://lists.w3.org/Ar… w3c/charmod-norm#150, by @aphillips.
-
Fixing remaining character examples. Updated the compatibility mappin… w3c/charmod-norm#149, by @aphillips.
-
Address #54. Edited text to better address @asmusf's comment. w3c/charmod-norm#148, by @aphillips.
-
Address #126: replace the colorful table with a new example block and… w3c/charmod-norm#147, by @aphillips.
-
Address #139 (other types of equivalence) w3c/charmod-norm#146, by @aphillips.
-
Changed 'user value(s)' to 'user-supplied value(s)' Addresses #143 w3c/charmod-norm#145, by @aphillips.
-
Turn off hyphenation in terminology example. w3c/charmod-norm#144, by @aphillips.
-
Attempting to fix the terminology illustration. Added line numbers an… w3c/charmod-norm#142, by @aphillips.
-
bringing W3C copy into sync with ED w3c/charmod-norm#141, by @aphillips.
-
Extensive edits including TPAC discussion w3c/charmod-norm#140, by @aphillips.
-
-
11 pull requests merged.
-
Fix the exampleChar style to have named fonts ahead of NoToFu w3c/charmod-norm#151.
-
Addressed JCK's comments (see email thread at https://lists.w3.org/Ar… w3c/charmod-norm#150.
-
Fixing remaining character examples. Updated the compatibility mappin… w3c/charmod-norm#149.
-
Address #54. Edited text to better address @asmusf's comment. w3c/charmod-norm#148.
-
Address #126: replace the colorful table with a new example block and… w3c/charmod-norm#147.
-
Address #139 (other types of equivalence) w3c/charmod-norm#146.
-
Changed 'user value(s)' to 'user-supplied value(s)' Addresses #143 w3c/charmod-norm#145.
-
Turn off hyphenation in terminology example. w3c/charmod-norm#144.
-
Attempting to fix the terminology illustration. Added line numbers an… w3c/charmod-norm#142.
-
bringing W3C copy into sync with ED w3c/charmod-norm#141.
-
Extensive edits including TPAC discussion w3c/charmod-norm#140.
-
-
1 pull request received 8 new comments.
-
Attempting to fix the terminology illustration. Added line numbers an… w3c/charmod-norm#142 (8 comments by @aphillips, @r12a)
-
w3c/i18n-drafts
-
5 issues opened.
-
[tutorials/bidi-xhtml/index] w3c/i18n-drafts#128, by @nicholaspretorius.
-
[tutorials/bidi-xhtml/index] w3c/i18n-drafts#127, by @nicholaspretorius.
-
[questions/qa-http-and-lang] w3c/i18n-drafts#125, by @CecilWard.
-
[techniques/authoring-html] Make the text in the <summary> elements not selectable? w3c/i18n-drafts#123, by @xfq.
-
[techniques/authoring-html] Broken links to tests w3c/i18n-drafts#122, by @xfq.
-
-
2 issues closed.
-
[tutorials/bidi-xhtml/index] w3c/i18n-drafts#128.
-
[tutorials/bidi-xhtml/index] w3c/i18n-drafts#127.
-
-
4 issues received 7 new comments.
-
[techniques/authoring-html] Make the text in the <summary> elements not selectable? w3c/i18n-drafts#123 (3 comments by @r12a, @xfq)
-
-
3 pull requests opened.
-
qa-personal-names.en, added note for Filipino middle names w3c/i18n-drafts#126, by @lgaa.
-
Use rel="license" instead of rel="copyright" w3c/i18n-drafts#124, by @xfq.
-
Trivial fixes for techniques page w3c/i18n-drafts#121, by @xfq.
-
-
1 pull request merged.
-
Trivial fixes for techniques page w3c/i18n-drafts#121.
-
-
1 pull request received 1 new comment.
w3c/typography
-
1 pull request opened.
-
language-matrix, trivial markup fix w3c/typography#53, by @xfq.
-
-
1 pull request merged.
w3c/bp-i18n-specdev
-
1 pull request opened.
-
Update some links w3c/bp-i18n-specdev#27, by @xfq.
-
w3c/clreq
-
1 issue opened.
-
About the two glossary formats w3c/clreq#155, by @xfq.
-
-
3 issues closed.
-
Does ruby cover the full text? w3c/clreq#154.
-
ruby: phonetics only? w3c/clreq#153.
-
Half-size han characters w3c/clreq#152.
-
-
5 issues received 15 new comments.
-
Does ruby cover the full text? w3c/clreq#154 (4 comments by @bobbytung, @murata2makoto, @realfish, @upsuper)
-
Position of ruby, text-emphasis, under/overline, etc in vertical-LR writing mode w3c/clreq#136 (1 comment by @fantasai)
-
2 pull requests opened.
-
Change "惊叹号" to "叹号" w3c/clreq#157, by @xfq.
-
[WIP] Add some English names to Appendix A w3c/clreq#156, by @xfq.
-
-
1 pull request received 28 new comments.
w3c/i18n-activity
-
1 issue opened.
-
Support for isolation & dir=auto in Edge w3c/i18n-activity#515, by @r12a.
-
-
6 issues received 7 new comments.
-
Should text-decoration-skip apply to overline and line-through? w3c/i18n-activity#458 (1 comment by @fantasai)
-
Proposal for the 'text-emphasis-position' property syntax values w3c/i18n-activity#387 (1 comment by @fantasai)
w3c/string-meta
-
1 issue opened.
-
Clarify what JSON-LD does and doesn't do w3c/string-meta#11, by @r12a.
-
-
3 issues received 3 new comments.
-
Would language +(sometimes) script information suffice for ambiguous cases? w3c/string-meta#9 (1 comment by @aphillips)
-
1 pull request opened.
-
Proposed edits arising from review w3c/string-meta#10, by @r12a.
-
-
1 pull request merged.
-
Proposed edits arising from review w3c/string-meta#10.
-
-
1 pull request received 1 new comment.
w3c/klreq
-
4 issues received 9 new comments.
w3c/type-samples
-
2 issues opened.
-
hang ko mockup inline-notes w3c/type-samples#66, by @r12a.
-
hang ko software inline-notes w3c/type-samples#65, by @r12a.
-
w3c/alreq
-
2 issues opened.
-
Expand sections on Diacratics w3c/alreq#155, by @behnam.
-
Section on Abjad w3c/alreq#154, by @behnam.
-
-
4 issues received 7 new comments.
-
Add Western Arabic Numerals (ASCII) to A.3 Numeral characters w3c/alreq#151 (1 comment by @shervinafshar)
w3c/i18n-request
-
1 issue opened.
-
CSS Text Decoration > Ongoing w3c/i18n-request#98, by @aphillips.
-
w3c/ilreq
-
1 issue opened.
-
Intrasyllabic character spacing w3c/ilreq#39, by @dscorbett.
-
-
1 issue closed.
-
Hard to read explanatory text w3c/ilreq#36.
-
-
1 issue received 1 new comment.
w3c/i18n-discuss
-
1 issue opened.
-
Does the html attribute "lang" implies the unicode script in the font? w3c/i18n-discuss#10, by @Pecita.
-
GitHub
w3c/alreq
-
4 issues opened.
-
Add Western Arabic Numerals (ASCII) to A.3 Numeral characters w3c/alreq#151, by @behnam.
-
Document styling fixes w3c/alreq#150, by @behnam.
-
Using variable font axis for Arabic joining segment elongation w3c/alreq#148, by @behnam.
-
Arabic Hamza bellow with Kasra break fonts. w3c/alreq#147, by @ntounsi.
-
-
2 issues closed.
-
Section on languages and locales w3c/alreq#96.
-
-
7 issues received 32 new comments.
-
Arabic Hamza bellow with Kasra break fonts. w3c/alreq#147 (14 comments by @asmusf, @behdad, @khaledhosny, @ntounsi, @r12a)
-
Review Proposed Draft: Unicode Technical Report #53: Unicode Arabic Mark Ordering Algorithm w3c/alreq#143 (7 comments by @behnam, @khaledhosny, @r12a, @shervinafshar)
-
Add Western Arabic Numerals (ASCII) to A.3 Numeral characters w3c/alreq#151 (4 comments by @behnam, @brawer, @r12a)
-
-
3 pull requests opened.
-
Add Section 1.2 Languages w3c/alreq#153, by @behnam.
-
Review Section 3.8 Numbers w3c/alreq#152, by @behnam.
-
Drop h_ from section ids w3c/alreq#149, by @behnam.
-
-
4 pull requests merged.
-
Review Section 3.8 Numbers w3c/alreq#152.
-
Add Section 1.2 Languages w3c/alreq#153.
-
Use dfn/h5 instead of span/em/strong w3c/alreq#146.
-
Use span+unicode-bidi:isolate instead of bdi tag w3c/alreq#145.
-
-
1 pull request closed.
-
Drop h_ from section ids w3c/alreq#149.
-
-
4 pull requests received 15 new comments.
w3c/clreq
-
4 issues opened.
-
Does ruby cover the full text? w3c/clreq#154, by @murata2makoto.
-
ruby: phonetics only? w3c/clreq#153, by @murata2makoto.
-
Half-size han characters w3c/clreq#152, by @r12a.
-
Horizontal lines in vertical text w3c/clreq#151, by @r12a.
-
-
2 issues received 6 new comments.
-
1 pull request opened.
-
Proof-reading up to 4.1.5 w3c/clreq#150, by @huijing.
-
-
1 pull request received 87 new comments.
-
Proof-reading up to 4.1.5 w3c/clreq#150 (87 comments by @ethantw, @huijing, @r12a, @ryukeikun, @xfq)
-
w3c/i18n-activity
-
18 issues opened.
-
Does ruby cover the full text? w3c/i18n-activity#513, by @r12a.
-
Bad link to RTL script information w3c/i18n-activity#511, by @r12a.
-
Diregarding status: language negotiation needed? w3c/i18n-activity#510, by @aphillips.
-
Tracking exception 'name' and 'explantation' fields not localized. w3c/i18n-activity#509, by @aphillips.
-
DNT Extension syntax unclear; exclude apostrophe? w3c/i18n-activity#508, by @aphillips.
-
Stylesheet in rendering section should use logical properties for margins etc w3c/i18n-activity#507, by @r12a.
-
UAs may have somewhat more liberal handling of the dir attribute than the spec does w3c/i18n-activity#506, by @r12a.
-
Add navigator.locales to expose additional locale details w3c/i18n-activity#505, by @r12a.
-
Add a timezonechange event to Window/WorkerGlobalScope w3c/i18n-activity#504, by @r12a.
-
Text decorations other than italic, underline or bold w3c/i18n-activity#503, by @bert-github.
-
Analogue of hyphenation in scripts that do not hyphenate w3c/i18n-activity#502, by @bert-github.
-
Description of columns in vertical text w3c/i18n-activity#501, by @bert-github.
-
Left-right scripts vs left-right languages w3c/i18n-activity#500, by @bert-github.
-
Scope of UTR #53 vs the algorithm UAOA w3c/i18n-activity#499, by @behnam.
-
Use of CGJ w3c/i18n-activity#498, by @r12a.
-
Use of Arabic Reordering in text editing w3c/i18n-activity#497, by @behnam.
-
UAOA is not clear about justification and scope w3c/i18n-activity#496, by @behnam.
-
Check compatibility of UAOA with NFC w3c/i18n-activity#495, by @behnam.
-
-
8 issues closed.
-
i18n-ISSUE-349: Section title for 6.2.7 doesn't match earlier description w3c/i18n-activity#37.
-
i18n-ISSUE-348: Non-ASCII not permitted in extensions w3c/i18n-activity#36.
-
i18n-ISSUE-346: Section 5.2 use of %31 and %30 for characters 1 and 0 w3c/i18n-activity#34.
-
i18n-ISSUE-351: Section 6.4.2: restriction to "URI-safe characters" w3c/i18n-activity#39.
-
i18n-ISSUE-350: IRI/non-ASCII not permitted in w3c/i18n-activity#38.
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/i18n-activity#334.
-
Unicode Normalization health warning needed? w3c/i18n-activity#410.
-
-
4 issues reopened.
-
Check compatibility of UAOA with NFC w3c/i18n-activity#495, by @r12a.
-
UAOA is not clear about justification and scope w3c/i18n-activity#496, by @r12a.
-
Scope of UTR #53 vs the algorithm UAOA w3c/i18n-activity#499, by @r12a.
-
Use of Arabic Reordering in text editing w3c/i18n-activity#497, by @r12a.
-
-
25 issues received 53 new comments.
-
How much can be fixed using font rules or CGJ? w3c/i18n-activity#493 (5 comments by @behnam, @khaledhosny, @r12a)
-
UAOA is not clear about justification and scope w3c/i18n-activity#496 (4 comments by @behnam, @khaledhosny, @r12a)
-
DNT Extension syntax unclear; exclude apostrophe? w3c/i18n-activity#508 (3 comments by @aphillips, @royfielding)
-
i18n-ISSUE-349: Section title for 6.2.7 doesn't match earlier description w3c/i18n-activity#37 (2 comments by @r12a)
-
i18n-ISSUE-347: Section 5.2: DNT-extension excludes should spell out control, space, double quote. w3c/i18n-activity#35 (2 comments by @r12a)
-
i18n-ISSUE-346: Section 5.2 use of %31 and %30 for characters 1 and 0 w3c/i18n-activity#34 (2 comments by @r12a)
-
i18n-ISSUE-351: Section 6.4.2: restriction to "URI-safe characters" w3c/i18n-activity#39 (2 comments by @r12a)
-
Tracking exception 'name' and 'explantation' fields not localized. w3c/i18n-activity#509 (1 comment by @dwsinger)
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/i18n-activity#334 (1 comment by @r12a)
-
w3c/charmod-norm
-
10 issues opened.
-
Example 7 shouldn't be in a panel w3c/charmod-norm#130, by @r12a.
-
Show ES6 escapes w3c/charmod-norm#129, by @r12a.
-
Why see charmod 4.6? w3c/charmod-norm#128, by @r12a.
-
Confusable definition w3c/charmod-norm#127, by @r12a.
-
Figure 1 needs a colour key w3c/charmod-norm#126, by @r12a.
-
NFC doesn't combine 'any' combining mark w3c/charmod-norm#125, by @r12a.
-
Example 4 table w3c/charmod-norm#123, by @r12a.
-
Better exampling for case folding section w3c/charmod-norm#122, by @r12a.
-
Terminology examples fonts w3c/charmod-norm#121, by @r12a.
-
-
1 issue closed.
-
Terminology examples fonts w3c/charmod-norm#121.
-
-
12 issues received 30 new comments.
-
8 pull requests opened.
-
Extensive work on the examples, addition of new examples, styling, an… w3c/charmod-norm#138, by @aphillips.
-
Work on #122: added examples for case folding, including additional f… w3c/charmod-norm#137, by @aphillips.
-
Fixes #121 (spelling error in 'monospace') w3c/charmod-norm#136, by @aphillips.
-
Fixed the publish date w3c/charmod-norm#135, by @aphillips.
-
Fixes to 64, 123, 125, 126, 129, 130 w3c/charmod-norm#134, by @aphillips.
-
Fixed 128, 129. Started on 126 w3c/charmod-norm#133, by @aphillips.
-
Issue 130; also fixed http->https for ReSpec. w3c/charmod-norm#132, by @aphillips.
-
Merging changes and syncing trees for editing w3c/charmod-norm#131, by @aphillips.
-
-
8 pull requests merged.
-
Extensive work on the examples, addition of new examples, styling, an… w3c/charmod-norm#138.
-
Work on #122: added examples for case folding, including additional f… w3c/charmod-norm#137.
-
Fixes #121 (spelling error in 'monospace') w3c/charmod-norm#136.
-
Fixed the publish date w3c/charmod-norm#135.
-
Fixes to 64, 123, 125, 126, 129, 130 w3c/charmod-norm#134.
-
Fixed 128, 129. Started on 126 w3c/charmod-norm#133.
-
Issue 130; also fixed http->https for ReSpec. w3c/charmod-norm#132.
-
Merging changes and syncing trees for editing w3c/charmod-norm#131.
-
w3c/type-samples
-
1 issue received 1 new comment.
w3c/i18n-request
-
1 issue opened.
-
Device and Sensors Reviews (6 docs) > 2017-12-31 w3c/i18n-request#49, by @aphillips.
-
-
1 issue received 4 new comments.
w3c/i18n-drafts
-
3 issues opened.
-
[questions/qa-lang-priorities] w3c/i18n-drafts#119, by @fbfb016.
-
[articles/inline-bidi-markup/uba-basics] Point to solution for figure 13 w3c/i18n-drafts#118, by @enaayat.
-
[articles/vertical-text/index] BRIEF_TITLE_GOES_HERE w3c/i18n-drafts#117, by @Senkrecht.
-
-
2 issues closed.
-
[questions/qa-lang-priorities] w3c/i18n-drafts#119.
-
[articles/vertical-text/index] BRIEF_TITLE_GOES_HERE w3c/i18n-drafts#117.
-
-
1 issue received 1 new comment.
-
[articles/inline-bidi-markup/uba-basics] Point to solution for figure 13 w3c/i18n-drafts#118 (1 comment by @r12a)
-
-
1 pull request opened.
-
Fix links to the i18n checker w3c/i18n-drafts#120, by @xfq.
-
-
1 pull request merged.
-
Fix links to the i18n checker w3c/i18n-drafts#120.
-
w3c/klreq
-
3 issues received 8 new comments.
-
Are emphasis marks used for Korean, and if so, which side? w3c/klreq#20 (4 comments by @fantasai, @jihyerish)
-
w3c/typography
-
3 pull requests opened.
-
Revising and expanding on notes for diacritics and italic this time on JS file. w3c/typography#52, by @shervinafshar.
-
Some improvement on the textual comments for the Hungarian data w3c/typography#51, by @iherman.
-
Updated the Hungarian data w3c/typography#50, by @iherman.
-
-
2 pull requests merged.
-
Some improvement on the textual comments for the Hungarian data w3c/typography#51.
-
Updated the Hungarian data w3c/typography#50.
-
-
1 pull request closed.
-
Revising and expanding on notes for diacritics and italic. w3c/typography#49.
-
w3c/bp-i18n-specdev
-
1 pull request opened.
-
Updates to language basics w3c/bp-i18n-specdev#26, by @r12a.
-
-
1 pull request merged.
-
Updates to language basics w3c/bp-i18n-specdev#26.
-
w3c/ilreq
-
2 issues closed.
-
Reduce duplication in orthographic syllable tables w3c/ilreq#7.
w3c/mlreq
-
2 issues closed.
-
A isol 1 not decomposed, when A isol 3 is w3c/mlreq#12.
-
U+1822 medi missing glyph in 1.2.2 w3c/mlreq#14.
-
w3c/elreq
-
3 issues received 3 new comments.
-
Survey Question: What Ethiopic letter should be applied as a height reference point for alignment? w3c/elreq#2 (1 comment by @dyacob)
GitHub
w3c/i18n-activity
-
16 issues opened.
-
How much can be fixed using font rules or CGJ? w3c/i18n-activity#493, by @r12a.
-
When should UAOA be used? w3c/i18n-activity#492, by @r12a.
-
Shadda display position w3c/i18n-activity#491, by @r12a.
-
AMOA rather than UAOA ? w3c/i18n-activity#490, by @r12a.
-
Is ruby text used with Korean? w3c/i18n-activity#489, by @r12a.
-
rootMargin may need to be directionally sensitive w3c/i18n-activity#488, by @r12a.
-
What do 'character key' and 'printable' mean? w3c/i18n-activity#484, by @r12a.
-
Please always use charset and lang for your documents. w3c/i18n-activity#483, by @r12a.
-
Why reduce accesskey values to a single code point? w3c/i18n-activity#482, by @r12a.
-
Normalization and accesskey w3c/i18n-activity#481, by @r12a.
-
Adapting Text: Line height and leading w3c/i18n-activity#480, by @r12a.
-
Adapting Text: font-family w3c/i18n-activity#479, by @r12a.
-
Adapting Text: Letter spacing w3c/i18n-activity#478, by @r12a.
-
Purpose of Purpose of Controls w3c/i18n-activity#477, by @r12a.
-
Are emphasis marks used for Korean, and if so, which side? w3c/i18n-activity#476, by @r12a.
-
Do emphasis marks swap sides when JA is embedded in ZH? w3c/i18n-activity#475, by @r12a.
-
-
7 issues closed.
-
Content Negotiation doesn't mention language as a negotiating point w3c/i18n-activity#379.
-
description of time zone w3c/i18n-activity#401.
-
DTD vs. DT example comments w3c/i18n-activity#405.
-
week number is actually culturally linked w3c/i18n-activity#402.
-
English idiom (non-I18N)(editorial) w3c/i18n-activity#323.
-
Subscription request needs to define UTF-8 w3c/i18n-activity#324.
-
Definition of "Hub" suggests that only 1 hub exists w3c/i18n-activity#378.
-
-
28 issues received 33 new comments.
-
Proposal for the 'text-emphasis-position' property syntax values w3c/i18n-activity#387 (3 comments by @r12a)
-
Content Negotiation doesn't mention language as a negotiating point w3c/i18n-activity#379 (2 comments by @r12a)
-
Doesn't example 3 in text-underline-position break current UA behavior? w3c/i18n-activity#388 (1 comment by @r12a)
-
'deleteWordForwards' and 'deleteWordBackwards' not well defined w3c/i18n-activity#211 (1 comment by @r12a)
-
How to carry directional information with a string and handle insertion w3c/i18n-activity#350 (1 comment by @r12a)
-
Should UTF-8 'as specified in' point to the Encoding spec? w3c/i18n-activity#413 (1 comment by @r12a)
-
Tighten up usages of "compatibilty caseless" comparisons used in the spec w3c/i18n-activity#121 (1 comment by @r12a)
-
w3c/i18n-drafts
-
4 issues opened.
-
Wrong RFC link w3c/i18n-drafts#115, by @xfq.
-
[questions/qa-css-lang] update needed w3c/i18n-drafts#114, by @r12a.
-
[questions/qa-html-encoding-declarations] w3c/i18n-drafts#113, by @mbanyar033.
-
could not use an html tag around Arabic character w3c/i18n-drafts#112, by @inDiscover.
-
-
2 issues closed.
-
Wrong RFC link w3c/i18n-drafts#115.
-
[questions/qa-html-encoding-declarations] w3c/i18n-drafts#113.
-
-
5 issues received 7 new comments.
-
could not use an html tag around Arabic character w3c/i18n-drafts#112 (2 comments by @behnam, @r12a)
-
[questions/qa-floating-times] opinions/discussion on the examples and advice given w3c/i18n-drafts#108 (1 comment by @aphillips)
-
[questions/qa-html-css-normalization] Normalization and security notes w3c/i18n-drafts#87 (1 comment by @mikesamuel)
-
1 pull request opened.
-
Updates to the QA floating times article w3c/i18n-drafts#111, by @aphillips.
-
w3c/i18n-request
-
4 issues opened.
-
UTR #53, Unicode Arabic Mark Ordering Algorithm w3c/i18n-request#106, by @r12a.
-
Review request: changes to CR of DNT (tracking-dnt) w3c/i18n-request#105, by @r12a.
-
I18N review request for WCAG 2.1 w3c/i18n-request#103, by @r12a.
-
Intersection Observer review w3c/i18n-request#102, by @LJWatson.
-
-
1 issue received 2 new comments.
w3c/clreq
-
1 issue opened.
-
Do emphasis marks swap sides when JA is embedded in ZH? w3c/clreq#149, by @r12a.
-
-
1 issue closed.
-
Duplicate definitions in the Glossary w3c/clreq#147.
-
-
3 issues received 5 new comments.
-
Attention needed for subscript characters w3c/clreq#146 (2 comments by @celestialphineas, @ryukeikun)
-
Do emphasis marks swap sides when JA is embedded in ZH? w3c/clreq#149 (2 comments by @r12a, @upsuper)
-
-
1 pull request merged.
-
Format character sizing information into tables w3c/clreq#144.
-
-
2 pull requests received 5 new comments.
-
Format character sizing information into tables w3c/clreq#144 (4 comments by @ethantw, @ryukeikun, @xfq)
-
w3c/alreq
-
3 issues opened.
-
[tidy] Fix bdi formatting w3c/alreq#144, by @behnam.
-
Vertical text handling in Unicode w3c/alreq#140, by @r12a.
-
-
1 issue closed.
-
Vertical Arabic w3c/alreq#102.
-
-
4 issues received 13 new comments.
-
Review Proposed Draft: Unicode Technical Report #53: Unicode Arabic Mark Ordering Algorithm w3c/alreq#143 (5 comments by @behnam, @shervinafshar)
-
-
4 pull requests opened.
-
Use dfn/h5 instead of span/em/strong w3c/alreq#146, by @behnam.
-
Use span+unicode-bidi:isolate instead of bdi tag w3c/alreq#145, by @behnam.
-
Add .editorconfig w3c/alreq#141, by @behnam.
-
-
1 pull request merged.
-
Tidy w3c/alreq#142.
-
-
1 pull request closed.
-
Add .editorconfig w3c/alreq#141.
-
-
1 pull request reopened.
-
Tidy w3c/alreq#142, by @shervinafshar.
-
-
3 pull requests received 3 new comments.
w3c/klreq
-
2 issues opened.
-
Is ruby text used with Korean? w3c/klreq#21, by @r12a.
-
Are emphasis marks used for Korean, and if so, which side? w3c/klreq#20, by @r12a.
-
-
2 issues received 2 new comments.
w3c/ilreq
-
2 issues opened.
-
X1 and XN not clear w3c/ilreq#37, by @r12a.
-
Hard to read explanatory text w3c/ilreq#36, by @r12a.
-
-
5 issues closed.
-
Divide section 3 w3c/ilreq#20.
-
Change case 2 example to show intended result w3c/ilreq#22.
-
Remove heading for section 5 w3c/ilreq#23.
-
Replace 5.3.2 heading with text w3c/ilreq#26.
-
Issues related to 'Initial letter styling' w3c/ilreq#33.
-
-
2 issues reopened.
-
Letter-spacing questions w3c/ilreq#24, by @r12a.
-
Variation in vertical arrangements w3c/ilreq#25, by @r12a.
-
-
7 issues received 8 new comments.
-
2 pull requests opened.
-
Rewrite of "Vertical arrangements of characters" w3c/ilreq#38, by @r12a.
-
Update index.html w3c/ilreq#35, by @slata.
-
-
1 pull request merged.
-
Update index.html w3c/ilreq#35.
-
w3c/typography
-
1 issue opened.
-
Italic or oblique faces in Chinese w3c/typography#45, by @xfq.
-
-
1 issue closed.
-
Italic or oblique faces in Chinese w3c/typography#45.
-
-
6 pull requests opened.
-
Revising and expanding on notes for diacritics and italic. w3c/typography#49, by @shervinafshar.
-
gap-analysis/zh, first draft w3c/typography#48, by @xfq.
-
More links to clreq w3c/typography#47, by @xfq.
-
Fix a broken link w3c/typography#46, by @xfq.
-
Use the correct repo for issues w3c/typography#44, by @xfq.
-
Change some links to HTTPS w3c/typography#43, by @xfq.
-
-
5 pull requests merged.
-
More links to clreq w3c/typography#47.
-
Fix a broken link w3c/typography#46.
-
Use the correct repo for issues w3c/typography#44.
-
Change some links to HTTPS w3c/typography#43.
-
gap-analysis/zh, first draft w3c/typography#48.
-
-
5 pull requests received 7 new comments.
-
Revising and expanding on notes for diacritics and italic. w3c/typography#49 (1 comment by @shervinafshar)
w3c/i18n-discuss
-
4 pull requests opened.
-
Complete the Chinese rows of the language matrix w3c/i18n-discuss#9, by @xfq.
-
Add lang="en" to the html start tag w3c/i18n-discuss#8, by @xfq.
-
Fix an incorrect link w3c/i18n-discuss#7, by @xfq.
-
Change some links to HTTPS w3c/i18n-discuss#6, by @xfq.
-
-
1 pull request merged.
-
Add lang="en" to the html start tag w3c/i18n-discuss#8.
-
-
3 pull requests closed.
-
Fix an incorrect link w3c/i18n-discuss#7.
-
Change some links to HTTPS w3c/i18n-discuss#6.
-
Complete the Chinese rows of the language matrix w3c/i18n-discuss#9.
-
-
3 pull requests received 4 new comments.
w3c/mlreq
-
3 issues opened.
-
U+1822 medi missing glyph in 1.2.2 w3c/mlreq#14, by @r12a.
-
Missing glyph from U+1821 E in 1.2.2 ? w3c/mlreq#13, by @r12a.
-
A isol 1 not decomposed, when A isol 3 is w3c/mlreq#12, by @r12a.
-
-
1 issue closed.
-
Missing glyph from U+1821 E in 1.2.2 ? w3c/mlreq#13.
-
-
3 issues received 6 new comments.
w3c/type-samples
-
1 issue opened.
-
hang ko book text-decoration w3c/type-samples#64, by @r12a.
-
w3c/hlreq
-
1 issue received 1 new comment.
-
Hebrew emphasizing text via bold font or spaces added between letters w3c/hlreq#2 (1 comment by @r12a)
-
w3c/jlreq
-
1 issue opened.
-
Do emphasis marks swap sides when JA is embedded in ZH? w3c/jlreq#11, by @r12a.
-
Participants
-
1 participant joined.
-
Fuqiao Xue (W3C) joined.
-
-
1 organization joined.
-
HM Government joined.
-
-
2 organizations left.
-
360 left.
-
Verisign, Inc. left.
-
GitHub
w3c/i18n-activity
-
5 issues opened.
-
Simple outline of baseline section w3c/i18n-activity#474, by @r12a.
-
Use of word justify w3c/i18n-activity#473, by @r12a.
-
Hinting at a translation language for outgoing links w3c/i18n-activity#472, by @r12a.
-
Can CLDR capture data on counter-styles? w3c/i18n-activity#471, by @r12a.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/i18n-activity#467, by @r12a.
-
-
8 issues closed.
-
Can <named-item> altText have xml:lang? w3c/i18n-activity#327.
-
Please provide more illustrations and examples for the ruby sections w3c/i18n-activity#337.
-
tts:writingMode example is not helpful w3c/i18n-activity#331.
-
How to space base characters where shiftRuby kicks in for group ruby? w3c/i18n-activity#339.
-
It should be easier to specify direction for RTL script users w3c/i18n-activity#345.
-
Should we allow more overhang for Chinese? w3c/i18n-activity#342.
-
Support for bopomofo ruby needed w3c/i18n-activity#333.
-
RDF text strings & language w3c/i18n-activity#369.
-
-
9 issues received 10 new comments.
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/i18n-activity#334 (2 comments by @r12a)
-
-
3 pull requests opened.
-
guidelines/process, minor fixes w3c/i18n-activity#470, by @xfq.
-
Fix telecon time w3c/i18n-activity#469, by @xfq.
-
Minor updates to the github guidelines w3c/i18n-activity#468, by @xfq.
-
-
3 pull requests merged.
-
guidelines/process, minor fixes w3c/i18n-activity#470.
-
Fix telecon time w3c/i18n-activity#469.
-
Minor updates to the github guidelines w3c/i18n-activity#468.
-
-
1 pull request received 1 new comment.
w3c/i18n-drafts
-
8 issues opened.
-
[questions/qa-floating-times] example typo? w3c/i18n-drafts#110, by @r12a.
-
[questions/qa-floating-times] textContent won't change w3c/i18n-drafts#109, by @r12a.
-
[questions/qa-floating-times] opinions/discussion on the examples and advice given w3c/i18n-drafts#108, by @galund.
-
[articles/strings-and-bidi/index] Transcriptions not clear w3c/i18n-drafts#107, by @r12a.
-
[questions/qa-escapes] Multiple escaped characters in CSS w3c/i18n-drafts#106, by @r12a.
-
[articles/strings-and-bidi/index] editorial: "usually never" w3c/i18n-drafts#105, by @matial.
-
[articles/strings-and-bidi/index] Minor proof-reading edits w3c/i18n-drafts#104, by @huijing.
-
[strings-and-bidi] Would language+script information suffice for ambiguous cases? w3c/i18n-drafts#103, by @r12a.
-
-
7 issues closed.
-
add scripting to point to canonical version w3c/i18n-drafts#95.
-
[questions/qa-escapes] Multiple escaped characters in CSS w3c/i18n-drafts#106.
-
[questions/qa-floating-times] w3c/i18n-drafts#66.
-
[articles/strings-and-bidi/index] Transcriptions not clear w3c/i18n-drafts#107.
-
[articles/strings-and-bidi/index] editorial: "usually never" w3c/i18n-drafts#105.
-
[strings-and-bidi] Would language+script information suffice for ambiguous cases? w3c/i18n-drafts#103.
-
[articles/strings-and-bidi/index] Minor proof-reading edits w3c/i18n-drafts#104.
-
-
7 issues received 12 new comments.
-
[strings-and-bidi] Would language+script information suffice for ambiguous cases? w3c/i18n-drafts#103 (3 comments by @r12a)
-
[questions/qa-floating-times] textContent won't change w3c/i18n-drafts#109 (2 comments by @aphillips, @r12a)
-
[articles/strings-and-bidi/index] Transcriptions not clear w3c/i18n-drafts#107 (2 comments by @matial, @r12a)
-
[articles/strings-and-bidi/index] Minor proof-reading edits w3c/i18n-drafts#104 (2 comments by @huijing, @r12a)
-
[articles/strings-and-bidi/index] editorial: "usually never" w3c/i18n-drafts#105 (1 comment by @r12a)
-
w3c/alreq
-
1 issue opened.
-
Which set of digits should be used for Pashto? w3c/alreq#136, by @ebraminio.
-
-
2 issues received 5 new comments.
-
Which set of digits should be used for Pashto? w3c/alreq#136 (2 comments by @ebraminio, @shervinafshar)
-
3 pull requests opened.
-
Editorial suggestions for Najib's number text w3c/alreq#138, by @r12a.
-
Starting the Review of Section on Numbers (Per #101) w3c/alreq#137, by @shervinafshar.
-
3 pull requests merged.
-
Editorial suggestions for Najib's number text w3c/alreq#138.
-
Starting the Review of Section on Numbers (Per #101) w3c/alreq#137.
-
1 pull request received 5 new comments.
w3c/hlreq
-
3 issues opened.
-
Punctuation w3c/hlreq#11, by @lkemmel.
-
Quotation marks w3c/hlreq#10, by @lkemmel.
-
Justification w3c/hlreq#9, by @r12a.
-
-
1 issue reopened.
-
Quotation marks w3c/hlreq#10, by @lkemmel.
-
-
3 issues received 6 new comments.
w3c/i18n-request
-
1 issue received 2 new comments.
w3c/string-meta
-
2 issues opened.
-
Would language +(sometimes) script information suffice for ambiguous cases? w3c/string-meta#9, by @r12a.
-
Editorial suggestions from Najib w3c/string-meta#7, by @r12a.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Changes to document to create the terminology section, tighten w3c/string-meta#8, by @aphillips.
-
-
1 pull request merged.
-
Changes to document to create the terminology section, tighten w3c/string-meta#8.
-
-
1 pull request received 4 new comments.
-
Changes to document to create the terminology section, tighten w3c/string-meta#8 (4 comments by @aphillips, @r12a)
-
w3c/clreq
-
1 issue opened.
-
Duplicate definitions in the Glossary w3c/clreq#147, by @xfq.
-
-
2 issues received 3 new comments.
-
Typo: duplicate simplified Chinese text in the section “Book Title Mark” w3c/clreq#145 (1 comment by @xfq)
-
1 pull request opened.
-
Translate some sentences to SC w3c/clreq#148, by @xfq.
-
-
1 pull request closed.
-
Fix an untranslated sentence w3c/clreq#133.
-
w3c/jlreq
-
1 issue opened.
w3c/predefined-counter-styles
-
1 pull request opened.
-
Numeric emoji styles w3c/predefined-counter-styles#16, by @Crissov.
-
w3c/bp-i18n-specdev
-
2 issues opened.
-
Bidi for strings w3c/bp-i18n-specdev#25, by @r12a.
-
Personal names section w3c/bp-i18n-specdev#24, by @r12a.
-
-
1 issue received 2 new comments.
TR publications
-
1 document published.
GitHub
w3c/type-samples
-
4 issues opened.
-
arab ar book justification w3c/type-samples#63, by @ntounsi.
-
arab ar signage vertical-text w3c/type-samples#62, by @ntounsi.
-
arab ar newsprint data-formats w3c/type-samples#61, by @r12a.
-
ethi am book punctuation-etc w3c/type-samples#60, by @r12a.
-
w3c/string-meta
-
2 issues opened.
-
TAG discussion pointer w3c/string-meta#4, by @r12a.
-
Is script covered? w3c/string-meta#2, by @murata2makoto.
-
-
1 issue received 1 new comment.
-
4 pull requests opened.
-
Editorial: spelling w3c/string-meta#6, by @tobie.
-
Additions to description of Unicode language tags w3c/string-meta#5, by @r12a.
-
typos from Mati w3c/string-meta#3, by @r12a.
-
Proposed changes to first draft w3c/string-meta#1, by @r12a.
-
-
4 pull requests merged.
-
Editorial: spelling w3c/string-meta#6.
-
Additions to description of Unicode language tags w3c/string-meta#5.
-
typos from Mati w3c/string-meta#3.
-
Proposed changes to first draft w3c/string-meta#1.
-
-
1 pull request received 3 new comments.
w3c/i18n-activity
-
38 issues opened.
-
When does the ABNF work for Tamil consonant clusters? w3c/i18n-activity#466, by @r12a.
-
Which side of the line do Mongolian ruby annotations appear normally? w3c/i18n-activity#465, by @r12a.
-
Should traditional mongolian text in horizontal writing modes be horizontal or vertical? w3c/i18n-activity#464, by @r12a.
-
Text emphasis examples needed w3c/i18n-activity#463, by @r12a.
-
Underline and NNBSP w3c/i18n-activity#462, by @r12a.
-
Mongolian text decoration styling w3c/i18n-activity#461, by @r12a.
-
Make dir isolate by default w3c/i18n-activity#460, by @r12a.
-
Emphasis marks and auto-hiding ruby annotation w3c/i18n-activity#459, by @r12a.
-
Should text-decoration-skip apply to overline and line-through? w3c/i18n-activity#458, by @r12a.
-
How are underlines positioned in Arabic text? w3c/i18n-activity#457, by @r12a.
-
How are underlines positioned in Indic text? w3c/i18n-activity#456, by @r12a.
-
How are underlines positioned in Korean text? w3c/i18n-activity#455, by @r12a.
-
How are underlines positioned in Ethiopic text? w3c/i18n-activity#454, by @r12a.
-
Korean line breaking information required w3c/i18n-activity#453, by @r12a.
-
Korean justification information required w3c/i18n-activity#452, by @r12a.
-
Should we add more Latin counter styles? w3c/i18n-activity#451, by @r12a.
-
Handling long annotations over adjacent characters in Chinese w3c/i18n-activity#450, by @r12a.
-
How to handle multisyllable/multiword ruby annotations in Chinese w3c/i18n-activity#449, by @r12a.
-
How much space around in space-around w3c/i18n-activity#448, by @r12a.
-
Are chinese ruby annotations ever start or end aligned? w3c/i18n-activity#447, by @r12a.
-
How to handle wide annotations in Mongolian ruby? w3c/i18n-activity#446, by @r12a.
-
Mongolian ruby requirements w3c/i18n-activity#445, by @r12a.
-
Which side of the line do Mongolian ruby annotations appear normally? w3c/i18n-activity#444, by @r12a.
-
How does line start/end overflow work for Chinese romanised phonetic annotations? w3c/i18n-activity#443, by @r12a.
-
Can long 'ruby text' overlap non-Hanzi characters in Chinese, and how much? w3c/i18n-activity#442, by @r12a.
-
An Observation on Punctuation Symmetry w3c/i18n-activity#441, by @r12a.
-
Underline and NNBSP w3c/i18n-activity#440, by @r12a.
-
Where does underline go relative to ruby? w3c/i18n-activity#439, by @r12a.
-
Combining ruby and emphasis marks w3c/i18n-activity#438, by @r12a.
-
Position of ruby, text-emphasis, under/overline, etc in vertical-LR writing mode w3c/i18n-activity#437, by @r12a.
-
Clarify text-spacing: punctuation w3c/i18n-activity#436, by @r12a.
-
text-decoration-skip: ink should allow not to skip for CJK and certain ideographic scripts w3c/i18n-activity#435, by @r12a.
-
Add auto value for text-decoration-skip w3c/i18n-activity#434, by @r12a.
-
Text underlines' positions cannot be fine-tuned w3c/i18n-activity#433, by @r12a.
-
No way to set the underline width/thickness w3c/i18n-activity#432, by @r12a.
-
Browsers must maintain cursive connections across ruby element boundaries w3c/i18n-activity#431, by @r12a.
-
emphasis-position vs CSS text-emphasis-position + Mongolian w3c/i18n-activity#430, by @r12a.
-
Vertical text support in forms w3c/i18n-activity#429, by @r12a.
-
-
5 issues closed.
-
empty segments allowed? (non-I18N) w3c/i18n-activity#367.
-
Serialization of Dublin Core terms in XML is not defined w3c/i18n-activity#412.
-
Ambiguity in JSON-LD between human- and machine-readable strings for DC terms w3c/i18n-activity#411.
-
cursive shaping breaks needs better scoping w3c/i18n-activity#254.
-
-
1 issue reopened.
-
Vertical text support in forms w3c/i18n-activity#429, by @r12a.
-
-
10 issues received 10 new comments.
-
Ambiguity in JSON-LD between human- and machine-readable strings for DC terms w3c/i18n-activity#411 (1 comment by @bert-github)
-
Serialization of Dublin Core terms in XML is not defined w3c/i18n-activity#412 (1 comment by @bert-github)
-
Make unicode-bidi:isolate the default for an element with a dir attribute (instead of unicode-bidi:embed) (chrome) w3c/i18n-activity#27 (1 comment by @r12a)
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/i18n-activity#334 (1 comment by @r12a)
w3c/i18n-request
-
2 issues opened.
-
TTML2 > 2017-09-30 w3c/i18n-request#31, by @aphillips.
-
CSS Logical Properties and Values Level 1 > 2021-02-21 w3c/i18n-request#79, by @r12a.
-
-
2 issues received 4 new comments.
w3c/alreq
-
5 issues opened.
-
Section on Text Authoring/Editing UX w3c/alreq#134, by @behnam.
-
Section on Numerical Separators and their Bidi behavior w3c/alreq#133, by @behnam.
-
Section on Background of Arabic Numerals w3c/alreq#131, by @behnam.
-
Missing terms in glossary w3c/alreq#130, by @r12a.
-
Section on Line Alignment w3c/alreq#129, by @behnam.
-
-
4 issues received 18 new comments.
-
2 pull requests opened.
-
Updating glossary from the spreadsheet w3c/alreq#135, by @shervinafshar.
-
Added new terms to the glossary w3c/alreq#132, by @ntounsi.
-
-
1 pull request merged.
-
Updating glossary from the spreadsheet w3c/alreq#135.
-
-
1 pull request closed.
-
Added new terms to the glossary w3c/alreq#132.
-
-
2 pull requests received 3 new comments.
w3c/i18n-drafts
-
9 issues opened.
-
[questions/qa-personal-names] w3c/i18n-drafts#102, by @quiddity-wp.
-
[techniques/authoring-html] w3c/i18n-drafts#101, by @SmithaBijoy.
-
[questions/qa-floating-times] Review comments w3c/i18n-drafts#100, by @r12a.
-
[questions/qa-floating-times] w3c/i18n-drafts#99, by @chaals.
-
[articles/definitions-time/index] w3c/i18n-drafts#98, by @wsdwl.
-
es-005 langtag? w3c/i18n-drafts#97, by @ryanve.
-
[articles/ruby/index] Old ruby article redirects out of date w3c/i18n-drafts#96, by @mwil.
-
add scripting to point to canonical version w3c/i18n-drafts#95, by @r12a.
-
[articles/ruby/markup] link issues w3c/i18n-drafts#94, by @mwil.
-
-
4 issues closed.
-
[techniques/authoring-html] w3c/i18n-drafts#101.
-
[articles/ruby/index] Old ruby article redirects out of date w3c/i18n-drafts#96.
-
es-005 langtag? w3c/i18n-drafts#97.
-
[articles/ruby/markup] link issues w3c/i18n-drafts#94.
-
-
3 issues received 5 new comments.
-
[articles/ruby/index] Old ruby article redirects out of date w3c/i18n-drafts#96 (2 comments by @r12a)
-
w3c/typography
-
7 issues opened.
-
Arabic glyph transparency overlap w3c/typography#42, by @r12a.
-
Arabic joining across style changes w3c/typography#41, by @r12a.
-
Vertical text support in forms w3c/typography#40, by @r12a.
-
rubyAlign withBase w3c/typography#39, by @r12a.
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/typography#38, by @r12a.
-
emphasis-position vs CSS text-emphasis-position + Mongolian w3c/typography#37, by @r12a.
-
Position of ruby, text-emphasis, under/overline, etc in vertical-LR writing mode w3c/typography#36, by @r12a.
-
-
38 issues closed.
-
How are underlines positioned in non-Latin text? w3c/typography#1.
-
Emphasis marks and auto-hiding ruby annotation w3c/typography#4.
-
Should text-decoration-skip apply to overline and line-through? w3c/typography#7.
-
How are underlines positioned in Arabic text? w3c/typography#10.
-
How are underlines positioned in Indic text? w3c/typography#11.
-
How are underlines positioned in Korean text? w3c/typography#12.
-
How are underlines positioned in Ethiopic text? w3c/typography#13.
-
Korean line breaking information required w3c/typography#14.
-
Korean justification information required w3c/typography#15.
-
Should mention position of underline for vertical writing mode w3c/typography#16.
-
Should we add more Latin counter styles? w3c/typography#17.
-
Handling long annotations over adjacent characters in Chinese w3c/typography#19.
-
How to handle multisyllable/multiword ruby annotations in Chinese w3c/typography#20.
-
How much space around in space-around w3c/typography#21.
-
Are chinese ruby annotations ever start or end aligned? w3c/typography#22.
-
How to handle wide annotations in Mongolian ruby? w3c/typography#24.
-
Mongolian ruby requirements w3c/typography#23.
-
Which side of the line do Mongolian ruby annotations appear normally? w3c/typography#29.
-
Can long 'ruby text' overlap non-Hanzi characters in Chinese, and how much? w3c/typography#31.
-
An Observation on Punctuation Symmetry w3c/typography#32.
-
Underline and NNBSP w3c/typography#33.
-
Where does underline go relative to ruby? w3c/typography#34.
-
Combining ruby and emphasis marks w3c/typography#35.
-
Clarify text-spacing: punctuation w3c/typography#3.
-
Add auto value for text-decoration-skip w3c/typography#6.
-
Text underlines' positions cannot be fine-tuned w3c/typography#8.
-
Requests to implement CSS Counter Styles w3c/typography#18.
-
No way to set the underline width/thickness w3c/typography#9.
-
emphasis-position vs CSS text-emphasis-position + Mongolian w3c/typography#37.
-
Browsers must maintain cursive connections across ruby element boundaries w3c/typography#25.
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/typography#38.
-
rubyAlign withBase w3c/typography#39.
-
Vertical text support in forms w3c/typography#40.
-
Arabic joining across style changes w3c/typography#41.
-
Arabic glyph transparency overlap w3c/typography#42.
-
w3c/unicode-xml
-
1 pull request opened.
-
[I18N-ACTION-632] Added a large red deprecation box to the document. w3c/unicode-xml#22, by @aphillips.
-
-
1 pull request merged.
-
[I18N-ACTION-632] Added a large red deprecation box to the document. w3c/unicode-xml#22.
-
GitHub
w3c/alreq
-
4 issues opened.
-
Characters from Presentation Form blocks legitimate to use in text w3c/alreq#128, by @behnam.
-
Firefox handles (Bidi) closing matching parenthesis the right way w3c/alreq#121, by @ntounsi.
-
-
2 issues closed.
-
Monospaced fonts in arabic w3c/alreq#117.
-
-
9 issues received 33 new comments.
-
Firefox handles (Bidi) closing matching parenthesis the right way w3c/alreq#121 (10 comments by @behnam, @khaledhosny, @ntounsi, @r12a)
-
Characters from Presentation Form blocks legitimate to use in text w3c/alreq#128 (6 comments by @behnam, @khaledhosny)
-
U+FDF2 'ARABIC LIGATURE ALLAH ISOLATED FORM' not always rendered correctly w3c/alreq#125 (5 comments by @behnam, @khaledhosny, @ntounsi)
-
Slanted font styles (Italic, Oblique, Iranic, ...) w3c/alreq#93 (3 comments by @behnam, @khaledhosny, @r12a)
-
-
4 pull requests opened.
-
Vertical text section edits w3c/alreq#126, by @ntounsi.
-
Vertical text section edits w3c/alreq#124, by @r12a.
-
Drafted Arabic vertical text section w3c/alreq#122, by @ntounsi.
-
-
4 pull requests merged.
-
Vertical text section edits w3c/alreq#126.
-
Vertical text section edits w3c/alreq#124.
-
Drafted Arabic vertical text section w3c/alreq#122.
-
-
2 pull requests received 3 new comments.
-
ACTION-64: Converting note boxes to issues and issue-questions with s… w3c/alreq#120 (2 comments by @behnam, @shervinafshar)
-
ACTION-64 replacing note divs and question/issue lists to boxed issue divs w3c/alreq#123 (1 comment by @behnam)
-
w3c/i18n-activity
-
4 issues opened.
-
Index & repo w3c/i18n-activity#425, by @r12a.
-
What type of equality checking is being performed for options. w3c/i18n-activity#424, by @stevenatkin.
-
Support throwing exception from text method during UTF-8 decode w3c/i18n-activity#423, by @stevenatkin.
-
2 issues closed.
-
Arabic w3c/i18n-activity#426.
-
Index & repo w3c/i18n-activity#425.
-
-
3 issues received 3 new comments.
w3c/i18n-request
-
2 issues opened.
-
CSS Align > 2017-06-30 w3c/i18n-request#97, by @aphillips.
-
Semantic Sensor Network Ontology > Urgent w3c/i18n-request#52, by @aphillips.
-
-
2 issues received 4 new comments.
w3c/i18n-checker
-
1 issue opened.
-
report mismatches between HTTP Content-Language and html lang w3c/i18n-checker#74, by @r12a.
-
w3c/i18n-drafts
-
1 issue closed.
-
[questions/qa-floating-times] w3c/i18n-drafts#44.
-
-
2 issues received 2 new comments.
-
3 pull requests opened.
-
Fixed a minor grammatical error in the "accumulation" section. w3c/i18n-drafts#93, by @aphillips.
-
Changed 'eight hours' to 'two to three hours' to be consistent w3c/i18n-drafts#92, by @aphillips.
-
Addressed #44 by re-writing the section on data aggregation. w3c/i18n-drafts#91, by @aphillips.
-
-
3 pull requests merged.
-
Fixed a minor grammatical error in the "accumulation" section. w3c/i18n-drafts#93.
-
Changed 'eight hours' to 'two to three hours' to be consistent w3c/i18n-drafts#92.
-
Addressed #44 by re-writing the section on data aggregation. w3c/i18n-drafts#91.
-
w3c/charmod-norm
-
10 issues closed.
-
Confusability vs string matching w3c/charmod-norm#87.
-
Limitations of Normalization - Confusion w3c/charmod-norm#88.
-
Does ZWJ/ZWNJ affect meaning? w3c/charmod-norm#44.
-
Definition of "resource" (section 1.4) w3c/charmod-norm#59.
-
table widths w3c/charmod-norm#81.
-
Arabic & Hebrew issues with 2.4 w3c/charmod-norm#82.
-
❿ hasn't a compat equiv w3c/charmod-norm#83.
-
Removing meaning w3c/charmod-norm#85.
-
[ed] eliminating encoding variation w3c/charmod-norm#86.
-
Alter C9 to allow for text transforms w3c/charmod-norm#101.
-
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Bert Bos (W3C) joined.
-
-
1 participant left.
-
Felix Sasaki (SAP SE) left.
-
GitHub
w3c/alreq
-
4 issues opened.
-
Rules for Arabic numerals in numbered lists w3c/alreq#118, by @tomerm.
-
Monospaced fonts in arabic w3c/alreq#117, by @r12a.
-
1 issue closed.
-
Rules for Arabic numerals in numbered lists w3c/alreq#118.
-
-
10 issues received 16 new comments.
-
Realms in which display of Bidi data is not guided by UBA ( i.e. zOS, Adobe Reader) w3c/alreq#119 (3 comments by @khaledhosny, @shervinafshar, @tomerm)
-
Section on Identifying boundaries of graphemes, words and larger groupings w3c/alreq#115 (1 comment by @shervinafshar)
-
-
3 pull requests opened.
-
Corrected a typo and added Transliteration w3c/alreq#116, by @ntounsi.
-
Added some new terms into the glossary w3c/alreq#114, by @ntounsi.
-
2 pull requests merged.
-
Corrected a typo and added Transliteration w3c/alreq#116.
-
Added some new terms into the glossary w3c/alreq#114.
-
-
1 pull request closed.
-
1 pull request received 8 new comments.
-
Added some new terms into the glossary w3c/alreq#114 (8 comments by @behnam, @mostafah, @ntounsi, @r12a)
-
w3c/clreq
-
2 issues opened.
-
Attention needed for subscript characters w3c/clreq#146, by @celestialphineas.
-
-
2 issues received 2 new comments.
w3c/i18n-activity
-
18 issues opened.
-
Recommended Character Sets considered harmful w3c/i18n-activity#420, by @aphillips.
-
Clarify the charset constraints on email addresses w3c/i18n-activity#419, by @r12a.
-
allow input type="email" to accept unicode values w3c/i18n-activity#418, by @r12a.
-
"valid email address" doesn't allow IDNs… w3c/i18n-activity#417, by @r12a.
-
Directionality of title element w3c/i18n-activity#416, by @r12a.
-
Why exclude hebrew and arabic proportional reference fonts? w3c/i18n-activity#415, by @r12a.
-
Should the character sets be minimum font requirements? w3c/i18n-activity#414, by @r12a.
-
Should UTF-8 'as specified in' point to the Encoding spec? w3c/i18n-activity#413, by @r12a.
-
Serialization of Dublin Core terms in XML is not defined w3c/i18n-activity#412, by @bert-github.
-
Ambiguity in JSON-LD between human- and machine-readable strings for DC terms w3c/i18n-activity#411, by @bert-github.
-
Unicode Normalization health warning needed? w3c/i18n-activity#410, by @bert-github.
-
Accept WHATWG change to drop restrictions on the Bidi algorithm? w3c/i18n-activity#409, by @r12a.
-
DTD vs. DT example comments w3c/i18n-activity#405, by @aphillips.
-
Should generalYear (etc.) be gregorianYear (etc.)? w3c/i18n-activity#404, by @aphillips.
-
decimal values for integral units unclear w3c/i18n-activity#403, by @aphillips.
-
week number is actually culturally linked w3c/i18n-activity#402, by @aphillips.
-
description of time zone w3c/i18n-activity#401, by @aphillips.
-
convertability to Gregorian w3c/i18n-activity#400, by @aphillips.
-
-
1 issue closed.
-
Accept WHATWG change to drop restrictions on the Bidi algorithm? w3c/i18n-activity#409.
-
-
11 issues received 13 new comments.
-
Use of fillLineGap might cause glyph collisons w3c/i18n-activity#399 (2 comments by @klensin, @r12a)
-
Metadata examples do not include xml:lang (editorial) w3c/i18n-activity#325 (2 comments by @aphillips, @r12a)
-
Should UTF-8 'as specified in' point to the Encoding spec? w3c/i18n-activity#413 (1 comment by @r12a)
-
Should the character sets be minimum font requirements? w3c/i18n-activity#414 (1 comment by @klensin)
-
Accept WHATWG change to drop restrictions on the Bidi algorithm? w3c/i18n-activity#409 (1 comment by @r12a)
-
It should be easier to specify direction for RTL script users w3c/i18n-activity#345 (1 comment by @r12a)
-
How to space base characters where shiftRuby kicks in for group ruby? w3c/i18n-activity#339 (1 comment by @r12a)
-
Please provide more illustrations and examples for the ruby sections w3c/i18n-activity#337 (1 comment by @r12a)
-
-
1 pull request opened.
-
link README to the Internationalization activity w3c/i18n-activity#407, by @chaals.
-
-
1 pull request merged.
-
link README to the Internationalization activity w3c/i18n-activity#407.
-
-
1 pull request closed.
-
Fix a typo in sample URL and some auto formatting improvements w3c/i18n-activity#381.
-
-
1 pull request received 2 new comments.
-
Fix a typo in sample URL and some auto formatting improvements w3c/i18n-activity#381 (2 comments by @behnam, @r12a)
-
w3c/i18n-checker
-
2 issues opened.
-
check rtl text in title element w3c/i18n-checker#73, by @r12a.
-
report dir on the body but not the html tag w3c/i18n-checker#72, by @r12a.
-
w3c/i18n-drafts
-
3 issues opened.
-
[questions/qa-forms-utf-8] w3c/i18n-drafts#90, by @bkdotcom.
-
[techniques/authoring-html] w3c/i18n-drafts#89, by @darkkaligla.
-
[questions/qa-html-css-normalization] Normalization and security notes w3c/i18n-drafts#87, by @r12a.
-
-
1 issue closed.
-
[techniques/authoring-html] w3c/i18n-drafts#89.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Edits to make the text flow (moving the "Martina" sentence down) w3c/i18n-drafts#86, by @aphillips.
-
-
2 pull requests merged.
-
Edits to make the text flow (moving the "Martina" sentence down) w3c/i18n-drafts#86.
-
Minor text edits. w3c/i18n-drafts#85.
-
w3c/i18n-discuss
-
2 pull requests opened.
-
Added ACTION-612 document to README.md w3c/i18n-discuss#5, by @aphillips.
-
Merging to W3C w3c/i18n-discuss#4, by @aphillips.
-
-
2 pull requests merged.
-
Added ACTION-612 document to README.md w3c/i18n-discuss#5.
-
Merging to W3C w3c/i18n-discuss#4.
-
w3c/i18n-request
-
2 issues opened.
-
Microdata > 2017-08-01 w3c/i18n-request#42, by @aphillips.
-
Push API > 2017-06-16 w3c/i18n-request#104, by @aphillips.
-
-
3 issues received 9 new comments.
w3c/jlreq
-
1 issue closed.
-
Links to each requirement w3c/jlreq#7.
-
-
1 issue received 1 new comment.
w3c/bp-i18n-specdev
-
3 issues opened.
-
Example interactive checklist w3c/bp-i18n-specdev#23, by @r12a.
-
provide downloadable version w3c/bp-i18n-specdev#22, by @chaals.
-
Value of default direction w3c/bp-i18n-specdev#21, by @r12a.
-
-
3 issues received 8 new comments.
w3c/charmod-norm
-
5 issues received 13 new comments.
-
2.2.1 Canonical vs. Compatibility Equivalence vs Canonical non-equivalence w3c/charmod-norm#69 (1 comment by @klensin)
-
3 pull requests opened.
-
Addressed @kleinsin's comment in #88 w3c/charmod-norm#120, by @aphillips.
-
Addresses emoji issue in #44 w3c/charmod-norm#119, by @aphillips.
-
Addresses #88 w3c/charmod-norm#118, by @aphillips.
-
-
3 pull requests merged.
-
Addressed @kleinsin's comment in #88 w3c/charmod-norm#120.
-
Addresses emoji issue in #44 w3c/charmod-norm#119.
-
Addresses #88 w3c/charmod-norm#118.
-
w3c/unicode-xml
-
1 pull request opened.
-
I18N-ACTION-616 Update unicode-xml to indicate current status w3c/unicode-xml#21, by @aphillips.
-
-
1 pull request merged.
-
I18N-ACTION-616 Update unicode-xml to indicate current status w3c/unicode-xml#21.
-
TR publications
-
1 document published.
-
Encoding published as a Candidate Recommendation Snapshot. History of Encoding
-
GitHub
w3c/i18n-drafts
-
1 issue opened.
-
[questions/qa-personal-names] Chinese name transliteration w3c/i18n-drafts#84, by @Kakurady.
-
-
1 issue closed.
-
[articles/typography/justification] w3c/i18n-drafts#82.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Minor text edits. w3c/i18n-drafts#85, by @aphillips.
-
-
1 pull request received 1 new comment.
w3c/clreq
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Format character sizing information into tables w3c/clreq#144, by @huijing.
-
Refine scripts and styles for appendix tables, etc w3c/clreq#143, by @ethantw.
-
-
2 pull requests merged.
-
Refine scripts and styles for appendix tables, etc w3c/clreq#143.
-
Proof read and edit English translation from 1–2.3 w3c/clreq#139.
-
-
2 pull requests received 6 new comments.
-
Refine scripts and styles for appendix tables, etc w3c/clreq#143 (3 comments by @ethantw, @r12a, @ryukeikun)
-
w3c/alreq
-
7 issues opened.
-
Programming language (i.e. Java) code editor and Arabic text w3c/alreq#113, by @tomerm.
-
Joining Context cases and examples w3c/alreq#112, by @behnam.
-
Section on Footnotes and Endnotes w3c/alreq#109, by @behnam.
-
Hyphenation in Arabic script writing systems w3c/alreq#108, by @behnam.
-
Review of the characters table and the changes needed for CLDR w3c/alreq#107, by @ntounsi.
-
Improvements for the Persian transliteration w3c/alreq#106, by @behnam.
-
Uniform font family and size in sample images w3c/alreq#105, by @behnam.
-
-
2 issues closed.
-
Programming language (i.e. Java) code editor and Arabic text w3c/alreq#113.
-
How to expose external links w3c/alreq#103.
-
-
1 issue reopened.
-
Review of the characters table and the changes needed for CLDR w3c/alreq#107, by @behnam.
-
-
11 issues received 59 new comments.
-
Hyphenation in Arabic script writing systems w3c/alreq#108 (16 comments by @behnam, @fantasai, @khaledhosny, @ntounsi, @r12a)
-
Review of the characters table and the changes needed for CLDR w3c/alreq#107 (15 comments by @behnam, @khaledhosny, @mostafah, @ntounsi)
-
How are underlines positioned in Arabic text? w3c/alreq#86 (6 comments by @behnam, @khaledhosny, @ntounsi)
-
Programming language (i.e. Java) code editor and Arabic text w3c/alreq#113 (2 comments by @behnam, @tomerm)
-
-
3 pull requests opened.
-
Add SVG version of the images and their typefaces w3c/alreq#111, by @mostafah.
-
Expanding section on Joining w3c/alreq#110, by @behnam.
-
Use ReSpec bibliography to manage external references w3c/alreq#104, by @behnam.
-
-
3 pull requests merged.
-
Add SVG version of the images and their typefaces w3c/alreq#111.
-
Expanding section on Joining w3c/alreq#110.
-
Use ReSpec bibliography to manage external references w3c/alreq#104.
-
-
1 pull request received 1 new comment.
w3c/charmod-norm
-
1 issue closed.
-
Arabic short vowels and Hebrew pointing in string search w3c/charmod-norm#78.
-
-
2 issues received 2 new comments.
-
Arabic short vowels and Hebrew pointing in string search w3c/charmod-norm#78 (1 comment by @aphillips)
-
w3c/string-search
-
1 issue opened.
-
Arabic vowels and Hebrew pointing in string search w3c/string-search#3, by @aphillips.
-
w3c/i18n-activity
-
18 issues opened.
-
Use of fillLineGap might cause glyph collisons w3c/i18n-activity#399, by @steveatkin.
-
Matching input to datalist values w3c/i18n-activity#396, by @r12a.
-
Minimum width for unskipped lines? w3c/i18n-activity#395, by @r12a.
-
default position for text-decoration-line in vertical text w3c/i18n-activity#394, by @r12a.
-
skip space and Ethiopic word space w3c/i18n-activity#393, by @r12a.
-
ink skipping should conform to glyph shape w3c/i18n-activity#392, by @r12a.
-
Results for text-underline-position: under w3c/i18n-activity#391, by @r12a.
-
`text-decoration-skip: ink` should allow not to skip for CJK and certain ideographic scripts w3c/i18n-activity#390, by @r12a.
-
Underline position for Japanese text with ruby w3c/i18n-activity#389, by @r12a.
-
Doesn't example 3 in text-underline-position break current UA behavior? w3c/i18n-activity#388, by @r12a.
-
Proposal for the 'text-emphasis-position' property syntax values w3c/i18n-activity#387, by @r12a.
-
Emphasis marks and font variant w3c/i18n-activity#386, by @r12a.
-
Default UA stylesheet for emphasis marks w3c/i18n-activity#385, by @r12a.
-
Orientation of emphasis marks for sideways text w3c/i18n-activity#384, by @r12a.
-
Emphasis mark and ruby w3c/i18n-activity#383, by @r12a.
-
[css-text-decor] Add auto value for text-decoration-skip w3c/i18n-activity#382, by @r12a.
-
Content Negotiation doesn't mention language as a negotiating point w3c/i18n-activity#379, by @joconner.
-
Definition of "Hub" suggests that only 1 hub exists w3c/i18n-activity#378, by @joconner.
-
-
7 issues closed.
-
i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) w3c/i18n-activity#122.
-
Minor concerns related to phrasing of text in input type=number w3c/i18n-activity#312.
-
Improve documentation of i18n issues with input type="number" w3c/i18n-activity#133.
-
example of language detection fallback w3c/i18n-activity#151.
-
add warning/advice about lang attribute use w3c/i18n-activity#119.
-
i18n-ISSUE-89: Time zones and local dates and times w3c/i18n-activity#123.
-
-
14 issues received 17 new comments.
-
i18n-ISSUE-89: Time zones and local dates and times w3c/i18n-activity#123 (2 comments by @aphillips, @r12a)
-
default position for text-decoration-line in vertical text w3c/i18n-activity#394 (1 comment by @r12a)
-
`text-decoration-skip: ink` should allow not to skip for CJK and certain ideographic scripts w3c/i18n-activity#390 (1 comment by @r12a)
-
Doesn't example 3 in text-underline-position break current UA behavior? w3c/i18n-activity#388 (1 comment by @r12a)
-
Proposal for the 'text-emphasis-position' property syntax values w3c/i18n-activity#387 (1 comment by @r12a)
-
1 pull request opened.
-
Fix a typo in sample URL and some auto formatting improvements w3c/i18n-activity#381, by @behnam.
-
w3c/i18n-request
-
3 issues opened.
-
OWL-Time > Urgently w3c/i18n-request#67, by @aphillips.
-
ORDL Information Model (+1 more) > 2017-05-15 w3c/i18n-request#37, by @aphillips.
-
HTML 5.2 > 2017-05-26 w3c/i18n-request#64, by @aphillips.
-
-
2 issues received 2 new comments.
w3c/ilreq
-
4 issues opened.
-
Sunken and raised initial letters w3c/ilreq#34, by @miloush.
-
Issues related to 'Initial letter styling' w3c/ilreq#33, by @r12a.
-
Introduction of ABNF in section 2.2 should be streamlined. w3c/ilreq#32, by @asmusf.
-
When does the ABNF work for Tamil consonant clusters? w3c/ilreq#31, by @r12a.
-
-
3 issues closed.
-
Inherent vowel sound or transcription? w3c/ilreq#14.
-
15 issues received 19 new comments.
-
When does the ABNF work for Tamil consonant clusters? w3c/ilreq#31 (4 comments by @miloush, @r12a, @Richard57)
-
w3c/typography
-
3 issues opened.
-
Combining ruby and emphasis marks w3c/typography#35, by @r12a.
-
Where does underline go relative to ruby? w3c/typography#34, by @r12a.
-
Underline and NNBSP w3c/typography#33, by @r12a.
-
w3c/mlreq
-
3 issues opened.
-
Mongolian text decoration styling w3c/mlreq#11, by @r12a.
-
Mongolian text decoration styles w3c/mlreq#10, by @r12a.
-
Underline and NNBSP w3c/mlreq#9, by @r12a.
-
-
1 issue closed.
-
Mongolian text decoration styles w3c/mlreq#10.
-
-
4 issues received 11 new comments.
w3c/jlreq
-
2 issues opened.
-
Where does underline go relative to ruby? w3c/jlreq#9, by @r12a.
-
Combining ruby and emphasis marks w3c/jlreq#8, by @r12a.
-
w3c/type-samples
-
3 issues opened.
-
hang ko signage inline-notes w3c/type-samples#59, by @dbaron.
-
mong mn book text-decoration w3c/type-samples#58, by @r12a.
-
hebr he printedmatter book numbers w3c/type-samples#57, by @tomerm.
-
-
1 issue received 2 new comments.
w3c/i18n-checker
-
1 issue closed.
-
Print Friendly w3c/i18n-checker#69.
-
w3c/i18n-discuss
-
1 issue opened.
-
[notes/string-base-direction] Using RLI...PDI wrapper w3c/i18n-discuss#3, by @r12a.
-
-
1 issue received 2 new comments.
TR publications
-
2 documents published.
GitHub
w3c/clreq
-
5 issues opened.
-
Type size equivalents between 号 and "point" w3c/clreq#142, by @ryukeikun.
-
Suggest to format type size equivalents in a table format w3c/clreq#141, by @huijing.
-
Suggestion to include figures for illustrating running heads w3c/clreq#140, by @huijing.
-
Is bopomofo needed for on-screen captions? w3c/clreq#135, by @r12a.
-
-
4 issues closed.
-
字体范例的选择 w3c/clreq#29.
-
Adding definitions to the glossary w3c/clreq#78.
-
"extend to the top of adjacent base text" w3c/clreq#119.
-
Translation fix needed: Extend over not to w3c/clreq#123.
-
-
10 issues received 13 new comments.
-
Position of ruby, text-emphasis, under/overline, etc in vertical-LR writing mode w3c/clreq#136 (4 comments by @huchunming, @huijing, @r12a)
-
Suggestion to include figures for illustrating running heads w3c/clreq#140 (1 comment by @ryukeikun)
-
-
6 pull requests opened.
-
Proof read and edit English translation from 1–2.3 w3c/clreq#139, by @huijing.
-
Add definitions to glossary table w3c/clreq#138, by @ethantw.
-
Replace fig. of the Four Typefaces w3c/clreq#137, by @ethantw.
-
Small translation fix w3c/clreq#134, by @r12a.
-
Fix an untranslated sentence w3c/clreq#133, by @xfq.
-
Punctuation fix w3c/clreq#132, by @xfq.
-
-
5 pull requests merged.
-
Add definitions to glossary table w3c/clreq#138.
-
Replace fig. of the Four Typefaces w3c/clreq#137.
-
補齊術語表的定義 w3c/clreq#131.
-
Punctuation fix w3c/clreq#132.
-
Small translation fix w3c/clreq#134.
-
-
1 pull request received 18 new comments.
-
Proof read and edit English translation from 1–2.3 w3c/clreq#139 (18 comments by @ethantw, @huijing, @r12a)
-
w3c/i18n-activity
-
27 issues opened.
-
Message text not localizable w3c/i18n-activity#377, by @aphillips.
-
Given and family are better than first and last w3c/i18n-activity#375, by @r12a.
-
Reference for BCP47 w3c/i18n-activity#374, by @r12a.
-
String without the notion of a character w3c/i18n-activity#373, by @r12a.
-
Define the terms language range and the matching approach w3c/i18n-activity#372, by @r12a.
-
Handling of meaningful multiple values w3c/i18n-activity#371, by @r12a.
-
Standardized way to add indications of text direction w3c/i18n-activity#370, by @r12a.
-
RDF text strings & language w3c/i18n-activity#369, by @r12a.
-
index sorting w3c/i18n-activity#368, by @aphillips.
-
empty segments allowed? (non-I18N) w3c/i18n-activity#367, by @aphillips.
-
ASCII character code (editorial) w3c/i18n-activity#366, by @aphillips.
-
list of records ascending order w3c/i18n-activity#365, by @aphillips.
-
name content issues? w3c/i18n-activity#364, by @aphillips.
-
opaque string comparison health warning? w3c/i18n-activity#363, by @aphillips.
-
sorted list by code unit w3c/i18n-activity#362, by @aphillips.
-
Examples have no language or direction w3c/i18n-activity#361, by @aphillips.
-
where unique key goes [non-I18N] w3c/i18n-activity#360, by @aphillips.
-
Upright orientation involves more than just glyph orientation w3c/i18n-activity#359, by @r12a.
-
Sideways shouldn't be tied to tblr vs tbrl w3c/i18n-activity#358, by @r12a.
-
Default directions in mixed textOrientation should use TR50 w3c/i18n-activity#357, by @r12a.
-
Incorporate CSS advances into TTML vertical text handling w3c/i18n-activity#356, by @r12a.
-
tts:textCombine and combining characters w3c/i18n-activity#355, by @r12a.
-
Add an illustration of pinyin for ruby align w3c/i18n-activity#354, by @r12a.
-
Show better mappings between base and annotation in figures w3c/i18n-activity#353, by @r12a.
-
formatFontColor values of rtl etc w3c/i18n-activity#351, by @r12a.
-
How to carry directional information with a string and handle insertion w3c/i18n-activity#350, by @r12a.
-
Code points and graphemes in backward deletion w3c/i18n-activity#349, by @r12a.
-
-
3 issues closed.
-
Default <details> heading should be localized #470 w3c/i18n-activity#164.
-
i18n-ISSUE-354: Questions about letter-spacing for Arabic script w3c/i18n-activity#93.
-
i18n-ISSUE-334: 'letter-spacing' and Indic w3c/i18n-activity#92.
-
-
17 issues received 23 new comments.
-
i18n-ISSUE-354: Questions about letter-spacing for Arabic script w3c/i18n-activity#93 (2 comments by @r12a)
-
Default directions in mixed textOrientation should use TR50 w3c/i18n-activity#357 (2 comments by @matial, @r12a)
-
Incorporate CSS advances into TTML vertical text handling w3c/i18n-activity#356 (1 comment by @fantasai)
-
Authoring requirement for bidi formatting characters seems bogus w3c/i18n-activity#197 (1 comment by @r12a)
w3c/i18n-drafts
-
3 issues opened.
-
[articles/typography/justification] w3c/i18n-drafts#82, by @ntounsi.
-
[articles/vertical-text] Making RTL text top to bottom w3c/i18n-drafts#81, by @khaledhosny.
-
[articles/vertical-text] markup -> mark up w3c/i18n-drafts#80, by @johnwcowan.
-
-
4 issues closed.
-
[articles/typography/justification] Add some pictures w3c/i18n-drafts#76.
-
[articles/vertical-text] Making RTL text top to bottom w3c/i18n-drafts#81.
-
[articles/vertical-text] markup -> mark up w3c/i18n-drafts#80.
-
[articles/vertical-text] block start/end w3c/i18n-drafts#74.
-
-
3 issues received 11 new comments.
-
[articles/vertical-text] Making RTL text top to bottom w3c/i18n-drafts#81 (9 comments by @asmusf, @khaledhosny, @ntounsi, @r12a)
-
w3c/i18n-request
-
2 issues opened.
-
IMSC 1.0.1 > 2017-05-07 w3c/i18n-request#50, by @aphillips.
-
Data Shapes SHACL > 2017-03-02 w3c/i18n-request#65, by @aphillips.
-
-
2 issues received 4 new comments.
w3c/mlreq
-
2 issues opened.
-
A Chinese standard available for reference w3c/mlreq#8, by @KrasnayaPloshchad.
-
Text emphasis examples needed w3c/mlreq#7, by @r12a.
-
-
2 issues received 2 new comments.
-
Should traditional mongolian text in horizontal writing modes be horizontal or vertical? w3c/mlreq#6 (1 comment by @aronsoyol)
w3c/bp-i18n-specdev
-
1 issue received 10 new comments.
-
Should include advice on what "White-space" is. w3c/bp-i18n-specdev#15 (10 comments by @johnwcowan, @r12a, @spemberton)
-
w3c/type-samples
-
16 issues opened.
-
hani cmn: Straight and wavy lines alongside vertical text w3c/type-samples#56, by @r12a.
-
mong mn webpage text-decoration w3c/type-samples#55, by @r12a.
-
hebr he (proper) Hebrew Hyphen w3c/type-samples#54, by @Weigern.
-
hebr he printedmatter glyphs w3c/type-samples#53, by @Weigern.
-
deva hi signage vertical-text w3c/type-samples#52, by @r12a.
-
mong mn book lists w3c/type-samples#51, by @r12a.
-
jpan ja magazine lists data-formats w3c/type-samples#50, by @r12a.
-
hebr he printedmatter book numbers w3c/type-samples#49, by @tomerm.
-
hebr he software numbers w3c/type-samples#48, by @tomerm.
-
hebr he software lists w3c/type-samples#47, by @tomerm.
-
hebr he webpage data-formats w3c/type-samples#46, by @tomerm.
-
hebr he webpage data-formats w3c/type-samples#45, by @tomerm.
-
hebr he printedmatter data-formats w3c/type-samples#44, by @tomerm.
-
grek el newsprint initials quotations w3c/type-samples#43, by @r12a.
-
deva hi newsprint initials w3c/type-samples#42, by @r12a.
-
hebr he printedmatter numbers w3c/type-samples#41, by @tomerm.
-
-
1 issue closed.
-
hebr he (proper) Hebrew Hyphen w3c/type-samples#54.
-
-
1 issue received 4 new comments.
w3c/jlreq
-
1 issue received 8 new comments.
w3c/alreq
-
5 issues opened.
-
How to expose external links w3c/alreq#103, by @behnam.
-
Vertical Arabic w3c/alreq#102, by @ntounsi.
-
Section on Numbers w3c/alreq#101, by @behnam.
-
Layout (flow direction) of math formula w3c/alreq#100, by @tomerm.
-
Section on spacings w3c/alreq#99, by @behnam.
-
-
3 issues closed.
-
Shortcomings of Characters Table w3c/alreq#49.
-
-
6 issues received 15 new comments.
-
Layout (flow direction) of math formula w3c/alreq#100 (6 comments by @behnam, @khaledhosny, @ntounsi, @r12a, @tomerm)
-
Why are bidi categories of Arabic-indic & Eastern Arabic numbers different? w3c/alreq#85 (1 comment by @ebraminio)
-
-
1 pull request merged.
-
Updates to character tables w3c/alreq#89.
-
-
1 pull request received 1 new comment.
w3c/hlreq
-
3 issues opened.
-
Hebrew Hyphen w3c/hlreq#8, by @r12a.
-
Mathematics expressions in Hebrew w3c/hlreq#7, by @tomerm.
-
-
1 issue closed.
-
2 issues received 9 new comments.
w3c/i18n-checker
-
3 issues closed.
-
update versions w3c/i18n-checker#59.
-
add link to list of checks w3c/i18n-checker#68.
-
Improve file layout? w3c/i18n-checker#56.
-
-
3 issues received 3 new comments.
-
2 pull requests opened.
-
Various fixes after merging #70 w3c/i18n-checker#71, by @tripu.
-
Various patches w3c/i18n-checker#70, by @r12a.
-
-
2 pull requests merged.
-
Various fixes after merging #70 w3c/i18n-checker#71.
-
Various patches w3c/i18n-checker#70.
-
-
1 pull request received 1 new comment.
w3c/typography
-
1 issue opened.
-
An Observation on Punctuation Symmetry w3c/typography#32, by @r12a.
-
-
3 issues closed.
-
Hebrew, with ascender w3c/typography#28.
-
Thai, Base with multiple combining characters above w3c/typography#27.
-
Underline, Urdu w3c/typography#26.
-
w3c/elreq
-
1 issue opened.
-
An Observation on Punctuation Symmetry w3c/elreq#111, by @r12a.
-
TR publications
-
6 documents published.
-
Indic Layout Requirements published as a Working Draft. History of Indic Layout Requirements
-
Requirements for Chinese Text Layout 中文排版需求 published as a Working Draft. History of Requirements for Chinese Text Layout 中文排版需求
-
Ready-made Counter Styles published twice as a Working Draft. History of Ready-made Counter Styles
-
International text layout and typography index published as a First Public Working Draft. History of International text layout and typography index
-
Ready-made Counter Styles published as a Note. History of Ready-made Counter Styles
-
Participants
-
1 participant joined.
-
Elika Etemad (Apple Inc.) joined.
-
-
1 participant left.
-
Elika Etemad (Apple Inc.) left.
-
GitHub
w3c/hlreq
-
5 issues opened.
-
Where are the Hebrew samples published at w3c/typography ? w3c/hlreq#5, by @tomerm.
-
Hebrew Rashi script w3c/hlreq#4, by @r12a.
-
Hebrew Stam letters (Ketav Stam) w3c/hlreq#3, by @r12a.
-
Hebrew diacritical marks (aka vocalization marks) w3c/hlreq#1, by @r12a.
-
-
2 issues received 4 new comments.
-
Where are the Hebrew samples published at w3c/typography ? w3c/hlreq#5 (2 comments by @r12a, @tomerm)
-
Hebrew emphasizing text via bold font or spaces added between letters w3c/hlreq#2 (2 comments by @lkemmel, @r12a)
-
w3c/alreq
-
5 issues opened.
-
Ditto Mark in Arabic script w3c/alreq#98, by @behnam.
-
Section on ZWNJ and ZWJ w3c/alreq#97, by @behnam.
-
Section on languages and locales w3c/alreq#96, by @behnam.
-
Slanted font styles (Italic, Oblique, Iranic, ...) w3c/alreq#93, by @behnam.
-
Section on Counter Styles w3c/alreq#92, by @behnam.
-
-
1 issue closed.
-
6 issues received 25 new comments.
-
Drafting “justification” w3c/alreq#57 (7 comments by @behnam, @khaledhosny, @mostafah, @ntounsi, @r12a)
-
Change the title to reflect that this is Arabic script, not Arabic Language w3c/alreq#88 (1 comment by @r12a)
-
-
2 pull requests opened.
-
Use HTTPS for w3.org and github.io links w3c/alreq#95, by @behnam.
-
Glossary Update and Adding Acknowledgments w3c/alreq#94, by @shervinafshar.
-
-
3 pull requests merged.
-
Use HTTPS for w3.org and github.io links w3c/alreq#95.
-
mabsut term in italic with a link to glossary w3c/alreq#83.
-
Glossary Update and Adding Acknowledgments w3c/alreq#94.
-
-
2 pull requests received 2 new comments.
w3c/mlreq
-
6 issues opened.
-
Non-Mongolian characters in vertical Mongolian text w3c/mlreq#5, by @r12a.
-
How to handle wide annotations in Mongolian ruby? w3c/mlreq#2, by @r12a.
-
Mongolian ruby requirements w3c/mlreq#1, by @r12a.
-
4 issues received 9 new comments.
-
Should traditional mongolian text in horizontal writing modes be horizontal or vertical? w3c/mlreq#6 (6 comments by @r12a)
-
Browsers must maintain cursive connections across ruby element boundaries w3c/mlreq#3 (1 comment by @upsuper)
-
Which side of the line do Mongolian ruby annotations appear normally? w3c/mlreq#4 (1 comment by @r12a)
-
w3c/type-samples
-
40 issues opened.
-
mong mn webpage vertical-text w3c/type-samples#40, by @r12a.
-
mong mn book vertical-text w3c/type-samples#39, by @r12a.
-
mong mn book vertical-text w3c/type-samples#38, by @r12a.
-
mong mn book punctuation-etc lists w3c/type-samples#37, by @r12a.
-
bopo zh-hant book inline-notes w3c/type-samples#36, by @r12a.
-
hani zh-hant: Right-to-left Chinese titles and captions in vertical text w3c/type-samples#35, by @r12a.
-
hebr he newsprint initials w3c/type-samples#34, by @r12a.
-
arab ar book text-decoration w3c/type-samples#33, by @r12a.
-
hebr he book glyphs w3c/type-samples#32, by @r12a.
-
hebr he book glyphs w3c/type-samples#31, by @r12a.
-
hebr he book glyphs w3c/type-samples#30, by @r12a.
-
hebr he newsprint font-style boundaries w3c/type-samples#29, by @r12a.
-
mong mn webpage vertical-text lists w3c/type-samples#28, by @r12a.
-
mong mn webpage vertical-text punctuation-etc w3c/type-samples#27, by @r12a.
-
mong mn webpage vertical-text w3c/type-samples#26, by @r12a.
-
hebr he book justification w3c/type-samples#25, by @tomerm.
-
hebr he book fonts w3c/type-samples#24, by @tomerm.
-
hebr he book fonts w3c/type-samples#23, by @tomerm.
-
hebr he book glyphs w3c/type-samples#22, by @tomerm.
-
Latin samples? w3c/type-samples#21, by @frivoal.
-
hebr he book spacing w3c/type-samples#19, by @tomerm.
-
hebr he newsprint hyphenation w3c/type-samples#18, by @r12a.
-
hebr he book hyphenation w3c/type-samples#17, by @tomerm.
-
Relationship to testing w3c/type-samples#15, by @dauwhe.
-
arab ar newsprint font-style punctuation-etc w3c/type-samples#14, by @r12a.
-
arab ar newsprint punctuation-etc fonts quotations w3c/type-samples#13, by @r12a.
-
arab ar newsprint justification w3c/type-samples#12, by @r12a.
-
arab ar signage justification spacing cursive w3c/type-samples#11, by @r12a.
-
Arabic, cursive characters with colour changes w3c/type-samples#10, by @r12a.
-
tibt bo book justification w3c/type-samples#9, by @r12a.
-
ethi am book justification w3c/type-samples#8, by @r12a.
-
ethi am book justification w3c/type-samples#7, by @r12a.
-
jpan ja mockup inline-notes w3c/type-samples#6, by @r12a.
-
mong mn mockup inline-notes w3c/type-samples#5, by @r12a.
-
arab ur newsprint text-decoration w3c/type-samples#4, by @r12a.
-
thai th newsprint initials w3c/type-samples#3, by @r12a.
-
hebr he newsprint initials w3c/type-samples#2, by @r12a.
-
arab ar inscription fonts w3c/type-samples#1, by @r12a.
-
-
1 issue closed.
-
Arabic, cursive characters with colour changes w3c/type-samples#10.
-
-
6 issues received 16 new comments.
w3c/i18n-activity
-
32 issues opened.
-
No mention of isolation for directional controls w3c/i18n-activity#346, by @r12a.
-
It should be easier to specify direction for RTL script users w3c/i18n-activity#345, by @r12a.
-
Use a more typical example for tts:direction w3c/i18n-activity#344, by @r12a.
-
Link from tts:direction to tts:writing-mode w3c/i18n-activity#343, by @r12a.
-
Should we allow more overhang for Chinese? w3c/i18n-activity#342, by @r12a.
-
Should rubyOverhang:allow overlap ideographs in Japanese? w3c/i18n-activity#341, by @r12a.
-
Simplify description of shiftRuby w3c/i18n-activity#340, by @r12a.
-
How to space base characters where shiftRuby kicks in for group ruby? w3c/i18n-activity#339, by @r12a.
-
Make it clearer that tts:rubyOverflow only applies to text that is at the end of a line w3c/i18n-activity#338, by @r12a.
-
Please provide more illustrations and examples for the ruby sections w3c/i18n-activity#337, by @r12a.
-
The default ruby-position for vertical-lr text may not be over w3c/i18n-activity#336, by @r12a.
-
How would someone display ruby inline? w3c/i18n-activity#335, by @r12a.
-
Default ruby position may be on the wrong side for tblr (eg. mongolian) w3c/i18n-activity#334, by @r12a.
-
Support for bopomofo ruby needed w3c/i18n-activity#333, by @r12a.
-
rubyOffset and line-spacing w3c/i18n-activity#332, by @r12a.
-
tts:writingMode example is not helpful w3c/i18n-activity#331, by @aphillips.
-
tts:displayAlign should mention right-to-left effects w3c/i18n-activity#330, by @aphillips.
-
Styling using tts:direction: should there be an auto value? w3c/i18n-activity#328, by @aphillips.
-
Can <named-item> altText have xml:lang? w3c/i18n-activity#327, by @aphillips.
-
Should there be a direction attribute? w3c/i18n-activity#326, by @aphillips.
-
Metadata examples do not include xml:lang (editorial) w3c/i18n-activity#325, by @aphillips.
-
Subscription request needs to define UTF-8 w3c/i18n-activity#324, by @aphillips.
-
English idiom (non-I18N)(editorial) w3c/i18n-activity#323, by @aphillips.
-
Handling non-kana text for rubyAlign with spaceAround or spaceBetween w3c/i18n-activity#320, by @r12a.
-
rubyAlign and wide ruby text w3c/i18n-activity#319, by @r12a.
-
NR is less than NB and NB is equal to 1 w3c/i18n-activity#318, by @r12a.
-
rubyAlign withBase w3c/i18n-activity#317, by @r12a.
-
How to handle mismatched sequences in complex ruby w3c/i18n-activity#316, by @r12a.
-
Complex ruby is usually both mono and group ruby w3c/i18n-activity#315, by @r12a.
-
Ruby based on outdated Annotation spec w3c/i18n-activity#314, by @r12a.
-
Why not use elements for ruby? w3c/i18n-activity#313, by @r12a.
-
Minor concerns related to phrasing of text in input type=number w3c/i18n-activity#312, by @r12a.
-
-
12 issues closed.
-
tts:displayAlign should mention right-to-left effects w3c/i18n-activity#330.
-
Should there be a direction attribute? w3c/i18n-activity#326.
-
Ruby based on outdated Annotation spec w3c/i18n-activity#314.
-
Use U+ notation to refer to code points w3c/i18n-activity#300.
-
Faulty references w3c/i18n-activity#243.
-
Supplementary characters in ES6 can use code point values w3c/i18n-activity#240.
-
Unicode character encodings are shown w3c/i18n-activity#239.
-
'Key value' terminology is ambiguous and confusing w3c/i18n-activity#302.
-
What is an 'appropriate' Unicode code point? w3c/i18n-activity#308.
-
printable control characters needs a closer definition w3c/i18n-activity#241.
-
Capital letter equivalents for bicameral scripts w3c/i18n-activity#305.
-
MAY may not be appropriate w3c/i18n-activity#304.
-
-
6 issues received 7 new comments.
-
tts:displayAlign should mention right-to-left effects w3c/i18n-activity#330 (2 comments by @aphillips, @r12a)
-
i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) w3c/i18n-activity#122 (1 comment by @aphillips)
-
Styling using tts:direction: should there be an auto value? w3c/i18n-activity#328 (1 comment by @r12a)
-
Improve documentation of i18n issues with input type="number" w3c/i18n-activity#133 (1 comment by @aphillips)
-
-
1 pull request opened.
-
[alreq] Fix typo in name w3c/i18n-activity#329, by @behnam.
-
-
1 pull request merged.
-
[alreq] Fix typo in name w3c/i18n-activity#329.
-
w3c/i18n-request
-
3 issues opened.
-
SLIM (IETF) > 2017-02-22 w3c/i18n-request#47, by @aphillips.
-
Browser Payment API > 2017-02-22 w3c/i18n-request#101, by @aphillips.
-
ARIA > 2017-04-30 w3c/i18n-request#53, by @aphillips.
-
w3c/i18n-drafts
-
2 issues opened.
-
[articles/language-tags/index] Found tiny typo w3c/i18n-drafts#79, by @ghost.
-
[questions/qa-http-and-lang] Blocking inheritance of lang w3c/i18n-drafts#78, by @ghost.
-
-
5 issues closed.
-
[articles/language-tags/index] Found tiny typo w3c/i18n-drafts#79.
-
[articles/typography/justification] Advice for implementers/authors section w3c/i18n-drafts#77.
-
[articles/definitions-time/index] w3c/i18n-drafts#57.
-
[questions/qa-personal-names] Error in "Middle initials" section w3c/i18n-drafts#58.
-
[questions-qa-personal-names] w3c/i18n-drafts#64.
-
-
7 issues received 9 new comments.
-
[questions/qa-http-and-lang] Blocking inheritance of lang w3c/i18n-drafts#78 (3 comments by @ghost, @r12a)
-
[articles/typography/justification] Advice for implementers/authors section w3c/i18n-drafts#77 (1 comment by @r12a)
-
[questions/qa-personal-names] Error in "Middle initials" section w3c/i18n-drafts#58 (1 comment by @r12a)
-
w3c/clreq
-
9 issues opened.
-
兒化音的注音符號標示方式 w3c/clreq#130, by @YuRen-tw.
-
Can long 'ruby text' overlap non-Hanzi characters, and how much? w3c/clreq#129, by @r12a.
-
How does line start/end overflow work for romanised phonetic annotations? w3c/clreq#128, by @r12a.
-
Are chinese ruby annotations ever start or end aligned? w3c/clreq#127, by @r12a.
-
How much space around in space-around? w3c/clreq#126, by @r12a.
-
How to handle multisyllable/multiword ruby annotations in Chinese w3c/clreq#125, by @r12a.
-
Handling long annotations over adjacent characters in Chinese w3c/clreq#124, by @r12a.
-
Translation fix needed: Extend over not to w3c/clreq#123, by @r12a.
-
加入断行算法优先在标点处断行的建议 w3c/clreq#122, by @Artoria2e5.
-
-
2 issues closed.
-
Multiple-word annotations? w3c/clreq#120.
-
加入断行算法优先在标点处断行的建议 w3c/clreq#122.
-
-
4 issues received 7 new comments.
w3c/ilreq
-
1 pull request closed.
-
editorial suggestions w3c/ilreq#13.
-
w3c/i18n-checker
-
1 issue opened.
-
Print Friendly w3c/i18n-checker#69, by @nitinkaveriappa.
-
-
1 issue received 1 new comment.
w3c/jlreq
-
1 issue opened.
-
Links to each requirement w3c/jlreq#7, by @murata2makoto.
-
w3c/typography
-
15 issues opened.
-
Can long 'ruby text' overlap non-Hanzi characters in Chinese, and how much? w3c/typography#31, by @r12a.
-
How does line start/end overflow work for Chinese romanised phonetic annotations? w3c/typography#30, by @r12a.
-
Which side of the line do Mongolian ruby annotations appear normally? w3c/typography#29, by @r12a.
-
Hebrew, with ascender w3c/typography#28, by @r12a.
-
Thai, Base with multiple combining characters above w3c/typography#27, by @r12a.
-
Underline, Urdu w3c/typography#26, by @r12a.
-
Browsers must maintain cursive connections across ruby element boundaries w3c/typography#25, by @r12a.
-
How to handle wide annotations in Mongolian ruby? w3c/typography#24, by @r12a.
-
Mongolian ruby requirements w3c/typography#23, by @r12a.
-
Are chinese ruby annotations ever start or end aligned? w3c/typography#22, by @r12a.
-
How much space around in space-around w3c/typography#21, by @r12a.
-
How to handle multisyllable/multiword ruby annotations in Chinese w3c/typography#20, by @r12a.
-
Handling long annotations over adjacent characters in Chinese w3c/typography#19, by @r12a.
-
Requests to implement CSS Counter Styles w3c/typography#18, by @r12a.
-
Should we add more Latin counter styles? w3c/typography#17, by @r12a.
-
-
1 issue received 1 new comment.
w3c/elreq
-
1 issue received 2 new comments.
w3c/predefined-counter-styles
-
6 issues closed.
-
Joining letters put in wrong position in the comments w3c/predefined-counter-styles#2.
-
Persian Alphabetic and Persian Abjad also used for Arabic w3c/predefined-counter-styles#13.
-
The "Maghrebian Abjad" sequence w3c/predefined-counter-styles#14.
-
‘fullwidth-’, ‘circled-’ and similar styles w3c/predefined-counter-styles#6.
-
Clock face emoji counter style w3c/predefined-counter-styles#9.
-
Add circled numbers w3c/predefined-counter-styles#15.
-
-
5 issues received 7 new comments.
-
‘fullwidth-’, ‘circled-’ and similar styles w3c/predefined-counter-styles#6 (2 comments by @Crissov, @r12a)
-
Persian Alphabetic and Persian Abjad also used for Arabic w3c/predefined-counter-styles#13 (1 comment by @r12a)
Participants
-
1 participant left.
-
Francesco Martino (W3C Invited Experts) left.
-
GitHub
w3c/alreq
-
3 issues opened.
-
Section on Abbreviation w3c/alreq#91, by @behnam.
-
Section on overlapping letter glyphs w3c/alreq#87, by @behnam.
-
-
6 issues received 37 new comments.
-
Drafting “justification” w3c/alreq#57 (14 comments by @behnam, @khaledhosny, @mostafah, @ntounsi, @shahab32mohsen, @zoghal)
-
Symbols in the language columns of the character tables are confusing w3c/alreq#52 (8 comments by @behnam, @mostafah, @ntounsi, @r12a)
-
Change the title to reflect that this is Arabic script, not Arabic Language w3c/alreq#88 (8 comments by @behnam, @ntounsi, @r12a, @shervinafshar)
-
-
2 pull requests opened.
-
Remove duplicate title w3c/alreq#90, by @mostafah.
-
Updates to character tables w3c/alreq#89, by @mostafah.
-
-
1 pull request merged.
-
Remove duplicate title w3c/alreq#90.
-
-
1 pull request received 1 new comment.
w3c/typography
-
14 issues opened.
-
Should mention position of underline for vertical writing mode w3c/typography#16, by @r12a.
-
Korean justification information required w3c/typography#15, by @r12a.
-
Korean line breaking information required w3c/typography#14, by @r12a.
-
How are underlines positioned in Ethiopic text? w3c/typography#13, by @r12a.
-
How are underlines positioned in Korean text? w3c/typography#12, by @r12a.
-
How are underlines positioned in Indic text? w3c/typography#11, by @r12a.
-
How are underlines positioned in Arabic text? w3c/typography#10, by @r12a.
-
No way to set the underline width/thickness w3c/typography#9, by @r12a.
-
Text underlines' positions cannot be fine-tuned w3c/typography#8, by @r12a.
-
Should text-decoration-skip apply to overline and line-through? w3c/typography#7, by @r12a.
-
Add auto value for text-decoration-skip w3c/typography#6, by @r12a.
-
Emphasis marks and auto-hiding ruby annotation w3c/typography#4, by @r12a.
-
Clarify text-spacing: punctuation w3c/typography#3, by @r12a.
-
-
1 issue closed.
-
Clarification Suggestion on Prevalent Space Symbol for Ethiopic w3c/typography#2.
-
-
1 issue received 1 new comment.
-
Clarification Suggestion on Prevalent Space Symbol for Ethiopic w3c/typography#2 (1 comment by @r12a)
-
w3c/i18n-drafts
-
4 issues opened.
-
[articles/typography/justification] Advice for implementers/authors section w3c/i18n-drafts#77, by @r12a.
-
[articles/typography/justification] Add some pictures w3c/i18n-drafts#76, by @r12a.
-
[articles/ruby/markup] Zhuyin & pinyin image substitution w3c/i18n-drafts#75, by @r12a.
-
[articles/vertical-text] block start/end w3c/i18n-drafts#74, by @r12a.
-
-
1 issue received 1 new comment.
-
[articles/typography/justification] Advice for implementers/authors section w3c/i18n-drafts#77 (1 comment by @asmusf)
-
w3c/charmod-norm
-
3 issues opened.
-
which characters, exactly, should be removed in the matching algorithm? w3c/charmod-norm#117, by @aphillips.
-
Formatting, not control characters w3c/charmod-norm#112, by @r12a.
-
Make coeng homonyms look better w3c/charmod-norm#111, by @r12a.
-
-
2 issues closed.
-
Make coeng homonyms look better w3c/charmod-norm#111.
-
Formatting, not control characters w3c/charmod-norm#112.
-
-
14 issues received 17 new comments.
-
which characters, exactly, should be removed in the matching algorithm? w3c/charmod-norm#117 (2 comments by @asmusf)
-
Arabic short vowels and Hebrew pointing in string search w3c/charmod-norm#78 (1 comment by @aphillips)
-
-
4 pull requests opened.
-
Fixed broken link to invisbles section. Added list of characters to r… w3c/charmod-norm#116, by @aphillips.
-
Fixed typos, cleaned up a few sentences, and moved the closing paragr… w3c/charmod-norm#115, by @aphillips.
-
Fixed #111: Changed text to a list, added character Unicode names, ad… w3c/charmod-norm#114, by @aphillips.
-
Pull of changes since 22 December w3c/charmod-norm#113, by @aphillips.
-
-
4 pull requests merged.
-
Fixed broken link to invisbles section. Added list of characters to r… w3c/charmod-norm#116.
-
Fixed typos, cleaned up a few sentences, and moved the closing paragr… w3c/charmod-norm#115.
-
Fixed #111: Changed text to a list, added character Unicode names, ad… w3c/charmod-norm#114.
-
Pull of changes since 22 December w3c/charmod-norm#113.
-
w3c/clreq
-
6 issues opened.
-
L2/14-006，关于中文标点的 standardized variant w3c/clreq#121, by @lianghai.
-
Multiple-word annotations? w3c/clreq#120, by @r12a.
-
"extend to the top of adjacent base text" w3c/clreq#119, by @r12a.
-
Clarify writing mode for romanization annotations w3c/clreq#118, by @r12a.
-
-
1 issue reopened.
-
弯引号在直排中的处理 w3c/clreq#41, by @bobbytung.
-
-
3 issues received 8 new comments.
w3c/i18n-activity
-
2 issues opened.
-
Meaning of 'glyph area descendant' w3c/i18n-activity#311, by @r12a.
-
Should we add the ability to query by language or country to watchAvailability() w3c/i18n-activity#310, by @stevenatkin.
-
-
4 issues closed.
-
Typos w3c/i18n-activity#309.
-
Halfwidth characters incorrectly rendered in Chrome w3c/i18n-activity#24.
-
Why are payment ids restricted to [a-z0-9]? w3c/i18n-activity#298.
-
Need to define fields for billing address w3c/i18n-activity#299.
-
-
13 issues received 14 new comments.
-
Should we add the ability to query by language or country to watchAvailability() w3c/i18n-activity#310 (2 comments by @duerst, @stevenatkin)
-
Supplementary characters in ES6 can use code point values w3c/i18n-activity#240 (1 comment by @r12a)
-
w3c/predefined-counter-styles
-
1 issue opened.
-
Add circled numbers w3c/predefined-counter-styles#15, by @r12a.
-
w3c/ilreq
-
1 issue opened.
-
Distinguish languages and scripts clearly w3c/ilreq#30, by @lianghai.
-
-
18 issues received 18 new comments.
-
I18N-ISSUE-401: Clarify initial letter requirements and alignment points w3c/ilreq#1 (1 comment by @lianghai)