Internationalization Working Group - Activity in 2016
No matches.
TR publications
-
1 document published.
-
Encoding published as a Candidate Recommendation Snapshot. History of Encoding
-
GitHub
w3c/alreq
-
4 issues received 8 new comments.
-
How are underlines positioned in Arabic text? w3c/alreq#86 (4 comments by @behnam, @khaledhosny, @mostafah)
-
-
1 pull request received 1 new comment.
w3c/clreq
-
21 issues closed.
-
Minor Fixes w3c/clreq#2.
-
关于 2.4.2.d w3c/clreq#27.
-
关于科技文献的句号、逗号 w3c/clreq#28.
-
參考文獻的整理與表示 w3c/clreq#36.
-
关于 2.1.3 汉字的配置原则 的两个疑问 w3c/clreq#43.
-
请考虑添加「什么样的人应该阅读本文档」 w3c/clreq#44.
-
line gap definition w3c/clreq#58.
-
meaning of 字面分布 w3c/clreq#59.
-
additional explanation for Parentheses section w3c/clreq#61.
-
description of grid alignment w3c/clreq#65.
-
A possible unrelated note in Zhuyin sec. to be omitted? w3c/clreq#73.
-
Unify the Hant/Hans/original text w3c/clreq#84.
-
Spacing and Hanging Punctuations w3c/clreq#91.
-
Positioning Issue for an Edge Case of Bopomofo w3c/clreq#93.
-
⁇ ‼ 是否需要列在中文標點符號表 w3c/clreq#94.
-
规范文档未遵循规范描述 w3c/clreq#100.
-
对旧有的破折号、连接号用法加入澄清注解 w3c/clreq#101.
-
「臺灣方言音符號」應為「臺灣方音符號」 w3c/clreq#102.
-
附錄A中有兩個標點符號的萬國碼出現筆誤 w3c/clreq#106.
-
-
9 issues received 16 new comments.
-
Should mention position of underline for vertical writing mode w3c/clreq#113 (2 comments by @c933103, @kojiishi)
-
1 pull request merged.
-
Update mixed text composition content to match en text w3c/clreq#111.
-
-
1 pull request received 2 new comments.
-
Update mixed text composition content to match en text w3c/clreq#111 (2 comments by @Artoria2e5, @xhacker)
-
w3c/jlreq
-
2 issues opened.
-
用語集が読みづらいです。 w3c/jlreq#6, by @gtk2k.
-
Fig. 3.63 nakatsuki-ruby and katatsuki-ruby w3c/jlreq#5, by @MurakamiShinyu.
-
-
2 issues received 4 new comments.
w3c/charmod-norm
-
3 pull requests opened.
-
Fixed broken link w3c/charmod-norm#110, by @aphillips.
-
Updated the publication date w3c/charmod-norm#109, by @aphillips.
-
Updates to address remaining open issues in the actual document flow … w3c/charmod-norm#108, by @aphillips.
-
-
3 pull requests merged.
-
Fixed broken link w3c/charmod-norm#110.
-
Updated the publication date w3c/charmod-norm#109.
-
Updates to address remaining open issues in the actual document flow … w3c/charmod-norm#108.
-
w3c/klreq
-
1 issue received 1 new comment.
w3c/i18n-activity
-
22 issues opened.
-
What is an 'appropriate' Unicode code point? w3c/i18n-activity#308, by @r12a.
-
Dead keys and unsupported base characters w3c/i18n-activity#307, by @r12a.
-
Editorial: Use Serbian for key code example w3c/i18n-activity#306, by @r12a.
-
Capital letter equivalents for bicameral scripts w3c/i18n-activity#305, by @r12a.
-
MAY may not be appropriate w3c/i18n-activity#304, by @r12a.
-
Use webfonts for Kanji and Serbian characters w3c/i18n-activity#303, by @r12a.
-
'Key value' terminology is ambiguous and confusing w3c/i18n-activity#302, by @r12a.
-
Are Shift or AltGr fallbacks sufficient? w3c/i18n-activity#301, by @r12a.
-
Use U+ notation to refer to code points w3c/i18n-activity#300, by @r12a.
-
Need to define fields for billing address w3c/i18n-activity#299, by @steveatkin.
-
Why are payment ids restricted to [a-z0-9]? w3c/i18n-activity#298, by @steveatkin.
-
ORDL Information Model 2016-07-09 w3c/i18n-activity#282, by @r12a.
-
WebDriver 2016-10-25 w3c/i18n-activity#280, by @r12a.
-
Hyphenation usages in CJK w3c/i18n-activity#261, by @r12a.
-
Propose to replace "'text-orientation: upright' to cause strong LTR" with author notes how to do it w3c/i18n-activity#260, by @r12a.
-
Default ruby centring for more than just zh w3c/i18n-activity#259, by @r12a.
-
Default styling for chinese annotations w3c/i18n-activity#258, by @r12a.
-
Multiple latin words alignment w3c/i18n-activity#257, by @r12a.
-
Treament of multiple Latin words in space-between & space-around w3c/i18n-activity#256, by @r12a.
-
Descriptions of space-between and space-around w3c/i18n-activity#255, by @r12a.
-
cursive shaping breaks needs better scoping w3c/i18n-activity#254, by @r12a.
-
1 issue closed.
-
Dvorak etc keyboards w3c/i18n-activity#245.
-
-
1 issue received 1 new comment.
w3c/i18n-drafts
-
1 issue opened.
-
articlelist.fr: translating a link to French w3c/i18n-drafts#72, by @notabene.
-
-
1 issue closed.
-
articlelist.fr: translating a link to French w3c/i18n-drafts#72.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fixing 2 lang attributes w3c/i18n-drafts#71, by @notabene.
-
-
2 pull requests merged.
-
Fixing 2 lang attributes w3c/i18n-drafts#71.
-
qa-html-language-declarations French version w3c/i18n-drafts#70.
-
-
2 pull requests received 2 new comments.
w3c/i18n-request
-
34 issues opened.
-
Web Annotation Vocabulary > 2016-05-16 w3c/i18n-request#63, by @r12a.
-
Data on the Web Best Practices > 2016-06-12 w3c/i18n-request#62, by @r12a.
-
HTML 5.1 > 2016-06-15 w3c/i18n-request#61, by @r12a.
-
Activity Streams Vocab > 2016-06-24 w3c/i18n-request#60, by @r12a.
-
Activity Streams Core > 2016-06-24 w3c/i18n-request#59, by @r12a.
-
MicroPub > 2016-12-30 w3c/i18n-request#58, by @r12a.
-
ActivityPub w3c/i18n-request#57, by @r12a.
-
Web Annotation Data Model > 2015-05-16 w3c/i18n-request#56, by @r12a.
-
Payment Request API > 2016-04-21 w3c/i18n-request#27, by @r12a.
-
Linked Data Notifications > 2016-10-11 w3c/i18n-request#68, by @r12a.
-
Accessibility (A11Y) Reqs for People with Low Vision > 2106-03-17 w3c/i18n-request#99, by @r12a.
-
CSS Object Model > 2016-03-23 w3c/i18n-request#81, by @r12a.
-
Resource Timing 2016-04-26 w3c/i18n-request#80, by @r12a.
-
CSS Generated Content > 2019-08-02 w3c/i18n-request#73, by @r12a.
-
Indexed DB 2 2016-08-15 w3c/i18n-request#23, by @r12a.
-
WebRTC > 2016-12-31? w3c/i18n-request#70, by @r12a.
-
XML Path Language (XPath) 3.1 w3c/i18n-request#46, by @r12a.
-
XPath and XQuery Functions and Operators 3.1 w3c/i18n-request#45, by @r12a.
-
XLST and XQuery Data Model 3.1 w3c/i18n-request#44, by @r12a.
-
XLST and XQuery Serialization 3.1 w3c/i18n-request#43, by @r12a.
-
Remote Playback API > 2016-12-31 w3c/i18n-request#69, by @r12a.
-
Pubsub > 2017-01-31 w3c/i18n-request#66, by @r12a.
-
TTML2 > ~2016-12-31 w3c/i18n-request#24, by @r12a.
-
Payment Method Identifiers 2016-04-12 w3c/i18n-request#25, by @r12a.
-
SVG2 > 2016-08-08 w3c/i18n-request#30, by @r12a.
-
Basic Card Payment, 2016-04-21 w3c/i18n-request#38, by @r12a.
-
Web Authentication, > 2016-08-16 w3c/i18n-request#100, by @r12a.
-
UI Events KeyboardEvent key Values, >2016-11-27 w3c/i18n-request#54, by @r12a.
-
UI Events KeyboardEvent code Values, >2016-11-27 w3c/i18n-request#29, by @r12a.
-
Screen Orientation w3c/i18n-request#55, by @r12a.
-
CSS Ruby > 2021-02-21 w3c/i18n-request#82, by @r12a.
-
Input Events 2016-08-23 w3c/i18n-request#26, by @r12a.
-
UI Events, by 2016-11-27 w3c/i18n-request#28, by @r12a.
-
-
4 issues reopened.
-
UI Events KeyboardEvent code Values, >2016-11-27 w3c/i18n-request#29, by @r12a.
-
Basic Card Payment, 2016-04-21 w3c/i18n-request#38, by @r12a.
-
Web Authentication, > 2016-08-16 w3c/i18n-request#100, by @r12a.
-
CSS Ruby > 2021-02-21 w3c/i18n-request#82, by @r12a.
-
-
1 issue received 1 new comment.
w3c/predefined-counter-styles
-
1 issue opened.
-
The "Maghrebian Abjad" sequence w3c/predefined-counter-styles#14, by @ntounsi.
-
-
1 issue received 1 new comment.
w3c/ilreq
-
12 issues received 12 new comments.
-
1 pull request opened.
-
Update index.html w3c/ilreq#29, by @slata.
-
-
1 pull request merged.
-
Update index.html w3c/ilreq#29.
-
TR publications
-
4 documents published.
-
Encoding published as a Candidate Recommendation Snapshot. History of Encoding
-
Ethiopic Layout Requirements published 3 times as a Working Draft. History of Ethiopic Layout Requirements
-
GitHub
w3c/i18n-drafts
-
1 pull request opened.
-
qa-html-language-declarations French version w3c/i18n-drafts#70, by @notabene.
-
-
1 pull request received 4 new comments.
w3c/alreq
-
1 issue opened.
-
How are underlines positioned in Arabic text? w3c/alreq#86, by @r12a.
-
-
1 issue received 5 new comments.
-
How are underlines positioned in Arabic text? w3c/alreq#86 (5 comments by @mostafah, @ntounsi, @r12a)
-
w3c/clreq
-
3 issues opened.
-
Low line or underline? w3c/clreq#115, by @r12a.
-
How are underlines positioned in Chinese text? w3c/clreq#114, by @r12a.
-
Should mention position of underline for vertical writing mode w3c/clreq#113, by @upsuper.
-
-
2 issues received 7 new comments.
-
Should mention position of underline for vertical writing mode w3c/clreq#113 (3 comments by @c933103, @ethantw)
-
1 pull request received 2 new comments.
w3c/predefined-counter-styles
-
2 issues closed.
-
Old Chinese Counting Rods w3c/predefined-counter-styles#12.
-
Names of Arabic counters do not match Unicode/CLDR naming w3c/predefined-counter-styles#1.
-
-
1 issue reopened.
-
Clock face emoji counter style w3c/predefined-counter-styles#9, by @r12a.
-
-
4 issues received 10 new comments.
-
Old Chinese Counting Rods w3c/predefined-counter-styles#12 (5 comments by @Crissov, @r12a, @upsuper)
-
Persian Alphabetic and Persian Abjad also used for Arabic w3c/predefined-counter-styles#13 (2 comments by @ironymark, @r12a)
-
Names of Arabic counters do not match Unicode/CLDR naming w3c/predefined-counter-styles#1 (2 comments by @r12a)
-
-
1 pull request merged.
-
Links w3c/predefined-counter-styles#11.
-
w3c/i18n-activity
-
8 issues opened.
-
[css-ruby-1] Proportional or fullwidth parens? w3c/i18n-activity#253, by @r12a.
-
[css-ruby-1] Generating Parentheses needs more thought w3c/i18n-activity#252, by @r12a.
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/i18n-activity#251, by @r12a.
-
[css-ruby] inlined annotations need to be full size w3c/i18n-activity#250, by @r12a.
-
cursive shaping breaks and typographic characters w3c/i18n-activity#249, by @r12a.
-
Add text language / direction attributes w3c/i18n-activity#248, by @r12a.
-
Arabic glyph transparency overlap w3c/i18n-activity#247, by @r12a.
-
Arabic joining across style changes w3c/i18n-activity#246, by @r12a.
-
-
21 issues closed.
-
[css-ruby] inlined annotations need to be full size w3c/i18n-activity#250.
-
It should be possible to indicate the default base direction for natural language values w3c/i18n-activity#176.
-
Consider removing TextEncoder support for UTF-16 w3c/i18n-activity#116.
-
Default Language Context MAY -> SHOULD #354 w3c/i18n-activity#205.
-
Use of "inbox" w3c/i18n-activity#234.
-
Editorial: Suggestion for spanish translations w3c/i18n-activity#177.
-
Why exclude markup from name? w3c/i18n-activity#178.
-
**Map fields become a SHOULD w3c/i18n-activity#184.
-
no language or direction or localizability of error message? w3c/i18n-activity#183.
-
example in pounds w3c/i18n-activity#181.
-
no way to indicate direction or language of name w3c/i18n-activity#182.
-
'Actor' and language/direction w3c/i18n-activity#227.
-
establishing 'id' uniqueness/identity w3c/i18n-activity#226.
-
No language markup in example 1 (editorial) w3c/i18n-activity#225.
-
Content language negotiation? w3c/i18n-activity#233.
-
processLanguage description improvement suggestion #345 w3c/i18n-activity#203.
-
ed sugg: textDirection #348 w3c/i18n-activity#204.
-
Relationship between dc:language and processing language for multilingual resources #343 w3c/i18n-activity#202.
-
Processing language for mono-lingual and internationalized resources #342 w3c/i18n-activity#201.
-
Clarify principle that features of external resources are not authoritative #339 w3c/i18n-activity#199.
-
The textDirection and processingLanguage properties are not needed #335 w3c/i18n-activity#198.
-
-
7 issues received 7 new comments.
-
no language or direction or localizability of error message? w3c/i18n-activity#183 (1 comment by @r12a)
w3c/i18n-discuss
-
1 issue opened.
-
Use of ZWJ w3c/i18n-discuss#2, by @r12a.
-
-
1 issue received 12 new comments.
-
Use of ZWJ w3c/i18n-discuss#2 (12 comments by @behdad, @duerst, @johnwcowan, @khaledhosny, @ntounsi, @r12a)
-
w3c/typography
-
2 issues opened.
-
Clarification Suggestion on Prevalent Space Symbol for Ethiopic w3c/typography#2, by @dyacob.
-
How are underlines positioned in non-Latin text? w3c/typography#1, by @r12a.
-
-
1 issue received 3 new comments.
-
Clarification Suggestion on Prevalent Space Symbol for Ethiopic w3c/typography#2 (3 comments by @fantasai, @r12a)
-
w3c/elreq
-
2 issues opened.
-
How are underlines positioned in Ethiopic text? w3c/elreq#110, by @r12a.
-
Spec: Unify Transcriptions Under a Single Convention. w3c/elreq#109, by @dyacob.
-
-
3 issues closed.
-
Add a section on punctuation w3c/elreq#89.
-
Spec: Correlate the image references with Figure numbers w3c/elreq#105.
-
Spec: Find image samples for Emphasis Within Prose w3c/elreq#106.
-
-
4 issues received 7 new comments.
-
How are underlines positioned in Ethiopic text? w3c/elreq#110 (4 comments by @dyacob, @moyogo, @r12a)
-
w3c/ilreq
-
15 issues opened.
-
How are underlines positioned in Indic text? w3c/ilreq#28, by @r12a.
-
Additional topics needed w3c/ilreq#27, by @r12a.
-
Replace 5.3.2 heading with text w3c/ilreq#26, by @r12a.
-
Variation in vertical arrangements w3c/ilreq#25, by @r12a.
-
Letter-spacing questions w3c/ilreq#24, by @r12a.
-
Remove heading for section 5 w3c/ilreq#23, by @r12a.
-
Change case 2 example to show intended result w3c/ilreq#22, by @r12a.
-
Hyphenation case 1 and 2 intentions w3c/ilreq#21, by @r12a.
-
Divide section 3 w3c/ilreq#20, by @r12a.
-
Variable terminology: purnaviram/danda w3c/ilreq#19, by @r12a.
-
Two dandas or double danda ? w3c/ilreq#18, by @r12a.
-
Unicode code point values in text w3c/ilreq#17, by @r12a.
-
Variable spelling for purnaviram w3c/ilreq#16, by @r12a.
-
Unicode chart w3c/ilreq#15, by @r12a.
-
Inherent vowel sound or transcription? w3c/ilreq#14, by @r12a.
-
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
editorial suggestions w3c/ilreq#13, by @r12a.
-
Update index.html w3c/ilreq#12, by @slata.
-
-
1 pull request merged.
-
Update index.html w3c/ilreq#12.
-
w3c/jlreq
-
1 issue opened.
-
How are underlines positioned in Japanese text? w3c/jlreq#4, by @r12a.
-
w3c/klreq
-
1 issue opened.
-
How are underlines positioned in Korean text? w3c/klreq#19, by @r12a.
-
w3c/tlreq
-
1 issue opened.
-
How are underlines positioned in Tibetan text? w3c/tlreq#2, by @r12a.
-
w3c/i18n-checker
-
4 issues opened.
-
add link to list of checks w3c/i18n-checker#68, by @r12a.
-
Check style sheets w3c/i18n-checker#67, by @r12a.
-
check for direction differences in attribute values w3c/i18n-checker#66, by @r12a.
-
Check for a mixture of bidi characters w3c/i18n-checker#65, by @r12a.
-
TR publications
-
3 documents published.
-
Ethiopic Layout Requirements published twice as a Working Draft. History of Ethiopic Layout Requirements
-
Internationalization Best Practices for Spec Developers published as a Working Draft. History of Internationalization Best Practices for Spec Developers
-
Participants
-
1 organization left.
-
Sikos Web Consulting left.
-
GitHub
w3c/i18n-activity
-
18 issues opened.
-
Dvorak etc keyboards w3c/i18n-activity#245, by @r12a.
-
Include more international keyboard examples w3c/i18n-activity#244, by @r12a.
-
Faulty references w3c/i18n-activity#243, by @r12a.
-
Arrow keys on Arabic keyboards w3c/i18n-activity#242, by @r12a.
-
printable control characters needs a closer definition w3c/i18n-activity#241, by @r12a.
-
Supplementary characters in ES6 can use code point values w3c/i18n-activity#240, by @r12a.
-
Unicode character encodings are shown w3c/i18n-activity#239, by @r12a.
-
[encoding] Webkit support for GB18030 w3c/i18n-activity#238, by @r12a.
-
support scrolling for vertically rendered text w3c/i18n-activity#237, by @r12a.
-
Allow multiple meta-description elements if they have different lang values? w3c/i18n-activity#236, by @r12a.
-
Test for radar w3c/i18n-activity#235, by @r12a.
-
Use of "inbox" w3c/i18n-activity#234, by @r12a.
-
Content language negotiation? w3c/i18n-activity#233, by @r12a.
-
3.1 Line wrapping for non-Latin scripts w3c/i18n-activity#232, by @r12a.
-
Reference to expired IETF draft w3c/i18n-activity#231, by @fsasaki.
-
LDN should have JSON-LD example which shows string internationalization w3c/i18n-activity#230, by @fsasaki.
-
Section 3.2: Example should include @language w3c/i18n-activity#229, by @aphillips.
-
Example should have charset=UTF-8 w3c/i18n-activity#228, by @aphillips.
-
-
5 issues closed.
-
LDN should have JSON-LD example which shows string internationalization w3c/i18n-activity#230.
-
Reference to expired IETF draft w3c/i18n-activity#231.
-
Example should have charset=UTF-8 w3c/i18n-activity#228.
-
3.1 Line wrapping for non-Latin scripts w3c/i18n-activity#232.
-
Section 3.2: Example should include @language w3c/i18n-activity#229.
-
-
9 issues received 10 new comments.
-
The textDirection and processingLanguage properties are not needed #335 w3c/i18n-activity#198 (1 comment by @r12a)
-
Clarify principle that features of external resources are not authoritative #339 w3c/i18n-activity#199 (1 comment by @r12a)
-
Processing language for mono-lingual and internationalized resources #342 w3c/i18n-activity#201 (1 comment by @r12a)
-
Relationship between dc:language and processing language for multilingual resources #343 w3c/i18n-activity#202 (1 comment by @r12a)
-
Tighten up usages of "compatibilty caseless" comparisons used in the spec w3c/i18n-activity#121 (1 comment by @domenic)
w3c/clreq
-
2 issues opened.
-
In section 2.1.1, "typeface" should be replaced by "glyph". w3c/clreq#110, by @c933103.
-
-
2 pull requests opened.
-
Update subscription links w3c/clreq#112, by @xhacker.
-
Update mixed text composition content to match en text w3c/clreq#111, by @xhacker.
-
-
1 pull request merged.
-
Update subscription links w3c/clreq#112.
-
w3c/alreq
-
3 issues opened.
-
Expand on the “ligatures” section w3c/alreq#82, by @mostafah.
-
3 issues closed.
-
Test w3c/alreq#78.
-
3 issues received 9 new comments.
-
Why are bidi categories of Arabic-indic & Eastern Arabic numbers different? w3c/alreq#85 (3 comments by @duerst, @khaledhosny, @ntounsi)
-
8 pull requests opened.
-
self links added to h2 and h3 (h4 to follow); removed figure captions… w3c/alreq#84, by @r12a.
-
mabsut term in italic with a link to glossary w3c/alreq#83, by @ntounsi.
-
Recover removed texts and links w3c/alreq#81, by @mostafah.
-
Adding text for issue #3 and #4 w3c/alreq#80, by @mostafah.
-
Fixed typos and removed some synonyms w3c/alreq#79, by @ntounsi.
-
Added link source of the images as discussed (Action-68) w3c/alreq#77, by @ntounsi.
-
first attempt at turning discussion points into sections w3c/alreq#76, by @r12a.
-
Consistent HTML tags for section titles w3c/alreq#75, by @mostafah.
-
-
8 pull requests merged.
-
Adding text for issue #3 and #4 w3c/alreq#80.
-
Recover removed texts and links w3c/alreq#81.
-
Fixed typos and removed some synonyms w3c/alreq#79.
-
Added link source of the images as discussed (Action-68) w3c/alreq#77.
-
first attempt at turning discussion points into sections w3c/alreq#76.
-
Consistent HTML tags for section titles w3c/alreq#75.
-
Add Shekasteh Nastaliq to writing styles section w3c/alreq#72.
-
-
2 pull requests closed.
-
Consistent HTML tags for section titles w3c/alreq#71.
-
7 pull requests received 8 new comments.
-
self links added to h2 and h3 (h4 to follow); removed figure captions… w3c/alreq#84 (1 comment by @mostafah)
-
add sentence to cover shekasteh nastaliq, update image source and put urls for images w3c/alreq#74 (1 comment by @shervinafshar)
w3c/i18n-drafts
-
3 issues opened.
-
[questions/qa-html-language-declarations] w3c/i18n-drafts#69, by @xgqfrms-GitHub.
-
[questions/qa-htaccess-charset] w3c/i18n-drafts#67, by @xgqfrms-GitHub.
-
-
2 issues closed.
-
[questions/qa-htaccess-charset] w3c/i18n-drafts#67.
-
1 issue received 1 new comment.
w3c/klreq
-
1 issue opened.
-
Quotation Marks w3c/klreq#17, by @r12a.
-
-
1 issue closed.
-
Quotation Marks w3c/klreq#17.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Fix for issue Quotation Marks #17 w3c/klreq#18, by @moyogo.
-
-
1 pull request merged.
-
Fix for issue Quotation Marks #17 w3c/klreq#18.
-
w3c/elreq
-
4 issues opened.
-
Spec: Develop Test Cases for Space-Wordspace Substitution Rules w3c/elreq#108, by @dyacob.
-
Spec: Find image samples for Emphasis Within Prose w3c/elreq#106, by @dyacob.
-
Spec: Correlate the image references with Figure numbers w3c/elreq#105, by @dyacob.
-
-
11 issues closed.
-
Use a webfont w3c/elreq#88.
-
White-space and stretching w3c/elreq#96.
-
Additional spaces in justification w3c/elreq#97.
-
Use of U+00A1 INVERTED EXCLAMATION MARK w3c/elreq#90.
-
Wordspace at Latin boundaries w3c/elreq#91.
-
Links for counter styles w3c/elreq#99.
-
CSS Counter-style definitions w3c/elreq#100.
-
Suggestions for section ordering w3c/elreq#104.
-
Centring headings w3c/elreq#103.
-
Move headings section? w3c/elreq#102.
-
Is / a counter suffix? w3c/elreq#98.
-
-
2 issues reopened.
-
Add a section on punctuation w3c/elreq#89, by @dyacob.
-
Wordspace at Latin boundaries w3c/elreq#91, by @r12a.
-
-
6 issues received 9 new comments.
w3c/bp-i18n-specdev
-
1 issue opened.
-
Section reorg w3c/bp-i18n-specdev#20, by @r12a.
-
-
1 issue closed.
-
Section reorg w3c/bp-i18n-specdev#20.
-
-
1 issue received 2 new comments.
w3c/charmod-norm
-
1 pull request opened.
-
Edits of 2016-10-05 w3c/charmod-norm#107, by @aphillips.
-
-
1 pull request merged.
-
Edits of 2016-10-05 w3c/charmod-norm#107.
-
TR publications
-
1 document published.
-
Ethiopic Layout Requirements published as a First Public Working Draft. History of Ethiopic Layout Requirements
-
Participants
-
1 organization joined.
-
Intuit joined.
-
-
1 organization left.
-
Cornac Servicios Editoriales left.
-
GitHub
w3c/elreq
-
103 issues opened.
-
Suggestions for section ordering w3c/elreq#104, by @r12a.
-
Centring headings w3c/elreq#103, by @r12a.
-
Move headings section? w3c/elreq#102, by @r12a.
-
አበገደ Lists w3c/elreq#101, by @r12a.
-
CSS Counter-style definitions w3c/elreq#100, by @r12a.
-
Links for counter styles w3c/elreq#99, by @r12a.
-
Is / a counter suffix? w3c/elreq#98, by @r12a.
-
Additional spaces in justification w3c/elreq#97, by @r12a.
-
White-space and stretching w3c/elreq#96, by @r12a.
-
'Word-bounded' or 'word-bound' ? w3c/elreq#95, by @r12a.
-
Word splitting w3c/elreq#94, by @r12a.
-
Line breaking and hyphenation sections w3c/elreq#93, by @r12a.
-
Extraneous spaces in conversions to wordspace w3c/elreq#92, by @r12a.
-
Wordspace at Latin boundaries w3c/elreq#91, by @r12a.
-
Use of U+00A1 INVERTED EXCLAMATION MARK w3c/elreq#90, by @r12a.
-
Add a section on punctuation w3c/elreq#89, by @r12a.
-
Use a webfont w3c/elreq#88, by @r12a.
-
Survey Question: What are formats for other media types? w3c/elreq#85, by @dyacob.
-
Survey Question: What spacing (if any) before and after the dots? w3c/elreq#83, by @dyacob.
-
Survey Question: Are square dots preferable over circular? w3c/elreq#82, by @dyacob.
-
Survey Question: How much spacing between dots is desirable? w3c/elreq#81, by @dyacob.
-
Survey Question: Which ellipsis form is the preferred as the default? w3c/elreq#80, by @dyacob.
-
Survey Question: Do special rules apply for inner expressions? w3c/elreq#70, by @dyacob.
-
Survey Question: When is ኛ" appropriate after an Ethiopic Numeral? w3c/elreq#66, by @dyacob.
-
Survey Question: Are mixed abbreviation markers appropriate? w3c/elreq#61, by @dyacob.
-
Survey Question: Confirm single word abbreviation rule. w3c/elreq#60, by @dyacob.
-
TODO: Correlate the image references with Figure numbers. w3c/elreq#57, by @dyacob.
-
Survey Question: Are there any rules on page number position? w3c/elreq#55, by @dyacob.
-
Survey Question: Does emphasis included a following punctuation? w3c/elreq#54, by @dyacob.
-
Survey Question: Does emphasis included a following wordspace? w3c/elreq#53, by @dyacob.
-
Survey Question: What shade of red for ecclesiastical emphasis? w3c/elreq#51, by @dyacob.
-
How is end of sequence handled in አበገደ lists? w3c/elreq#49, by @dyacob.
-
Survey Question: How is end of sequence handled in ሀለሐመ lists? w3c/elreq#47, by @dyacob.
-
Survey Question: Are there any sublist (nested list) considerations? w3c/elreq#45, by @dyacob.
-
Survey Question: What alignment style(s) do stakeholders desire? w3c/elreq#42, by @dyacob.
-
Survey Question: How much, if any, white space follows the suffix? w3c/elreq#40, by @dyacob.
-
Survey Question: Are lists indented (left margin)? If so, how much? w3c/elreq#38, by @dyacob.
-
Survey Question: What are the preferred bullet shapes? w3c/elreq#34, by @dyacob.
-
Survey Question: Should a new paragraph be indented following a list? w3c/elreq#27, by @dyacob.
-
Survey Question: Should the first paragraph of a section be indented? w3c/elreq#26, by @dyacob.
-
Survey Question: How much should a paragraph be indented? w3c/elreq#25, by @dyacob.
-
Survey Question: Do stakeholders want the option for both styles? w3c/elreq#19, by @dyacob.
-
Survey Question: What symbols benefit from weight change? w3c/elreq#11, by @dyacob.
-
Survey Question: What symbols benefit from shape change? w3c/elreq#10, by @dyacob.
-
TODO: Reduce/Optimize Image Sizes for Web Presentation w3c/elreq#1, by @dyacob.
-
-
6 issues closed.
-
Word splitting w3c/elreq#94.
-
Line breaking and hyphenation sections w3c/elreq#93.
-
'Word-bounded' or 'word-bound' ? w3c/elreq#95.
-
አበገደ Lists w3c/elreq#101.
-
-
1 issue reopened.
-
Use a webfont w3c/elreq#88, by @dyacob.
-
-
7 issues received 14 new comments.
-
Survey Question: How much, if any, white space follows the suffix? w3c/elreq#40 (1 comment by @dyacob)
-
1 pull request opened.
-
various typo fixes and editorial suggestions w3c/elreq#87, by @r12a.
-
-
1 pull request merged.
-
various typo fixes and editorial suggestions w3c/elreq#87.
-
w3c/string-search
-
2 pull requests opened.
-
Additional edits to make document internally consistent w3c/string-search#2, by @aphillips.
-
Created initial document from the rump of charmod-norm w3c/string-search#1, by @aphillips.
-
-
2 pull requests merged.
-
Additional edits to make document internally consistent w3c/string-search#2.
-
Created initial document from the rump of charmod-norm w3c/string-search#1.
-
w3c/charmod-norm
-
1 issue opened.
-
Alter C9 to allow for text transforms w3c/charmod-norm#101, by @aphillips.
-
-
1 issue closed.
-
Case matching example seems wrong w3c/charmod-norm#99.
-
-
1 issue received 2 new comments.
-
5 pull requests opened.
-
Gh pages w3c/charmod-norm#106, by @aphillips.
-
Grr. Really fix the fatal-to-respec change. w3c/charmod-norm#105, by @aphillips.
-
Fix fatal-to-respec edit error w3c/charmod-norm#104, by @aphillips.
-
I18N-ACTION-551: removed section about string searching including oth… w3c/charmod-norm#103, by @aphillips.
-
editorial suggestions for introductory section; reorganization of req… w3c/charmod-norm#102, by @r12a.
-
-
5 pull requests merged.
-
Gh pages w3c/charmod-norm#106.
-
Grr. Really fix the fatal-to-respec change. w3c/charmod-norm#105.
-
Fix fatal-to-respec edit error w3c/charmod-norm#104.
-
I18N-ACTION-551: removed section about string searching including oth… w3c/charmod-norm#103.
-
editorial suggestions for introductory section; reorganization of req… w3c/charmod-norm#102.
-
w3c/i18n-activity
-
12 issues opened.
-
'Actor' and language/direction w3c/i18n-activity#227, by @aphillips.
-
establishing 'id' uniqueness/identity w3c/i18n-activity#226, by @aphillips.
-
No language markup in example 1 (editorial) w3c/i18n-activity#225, by @aphillips.
-
Segment Break Transformation Rules for East Asian Width property of A w3c/i18n-activity#224, by @r12a.
-
titlecasing digraphs w3c/i18n-activity#223, by @r12a.
-
Enclosed alphanumerics and text-align:capitalize w3c/i18n-activity#222, by @r12a.
-
Add 'none' value to line-break for traditional Chinese w3c/i18n-activity#221, by @r12a.
-
rb and rtc element should be removed from the list of obsolete features w3c/i18n-activity#220, by @r12a.
-
definition of character w3c/i18n-activity#219, by @r12a.
-
Rotating text w3c/i18n-activity#218, by @r12a.
-
inline-base direction w3c/i18n-activity#217, by @r12a.
-
UTF-16 code points for addressable characters w3c/i18n-activity#216, by @r12a.
-
-
12 issues closed.
-
section 3.1.2 charset w3c/i18n-activity#166.
-
section 3.2: no character encoding on response examples w3c/i18n-activity#167.
-
Section 3.2: no language support w3c/i18n-activity#168.
-
encoding health warning for x-www-urlencoded w3c/i18n-activity#180.
-
[csvw] instance definitions for direction w3c/i18n-activity#153.
-
Make unicode-bidi: isolate the default for elements with a dir attribute (mozilla) w3c/i18n-activity#26.
-
list of displays: should it address display name, language, etc.? w3c/i18n-activity#113.
-
Possibility for a character to be interpreted differently depending on locale w3c/i18n-activity#114.
-
What Latin means w3c/i18n-activity#47.
-
rb and rtc non-conforming in html5.1 w3c/i18n-activity#215.
-
BP3 should recommend locale-neutral representation w3c/i18n-activity#187.
-
Use of multiple currencies w3c/i18n-activity#213.
-
-
11 issues received 13 new comments.
-
UTF-16 code points for addressable characters w3c/i18n-activity#216 (3 comments by @aphillips, @klensin)
-
i18n-ISSUE-408: Boxed characters and initial letter properties w3c/i18n-activity#63 (1 comment by @fantasai)
-
i18n-ISSUE-354: Questions about letter-spacing for Arabic script w3c/i18n-activity#93 (1 comment by @r12a)
-
Arabic letters connecting between elements with display: inline w3c/i18n-activity#94 (1 comment by @r12a)
-
list of displays: should it address display name, language, etc.? w3c/i18n-activity#113 (1 comment by @r12a)
-
w3c/ilreq
-
1 pull request opened.
-
Addition of Orthographic syllable use cases for Assamese language and… w3c/ilreq#11, by @slata.
-
-
1 pull request merged.
w3c/alreq
-
3 issues opened.
-
ACTION-63: Provide sources and urls for the images w3c/alreq#73, by @ntounsi.
-
Proper tags for titles: H2 or H3? w3c/alreq#69, by @mostafah.
-
-
2 issues closed.
-
ACTION-63: Provide sources and urls for the images w3c/alreq#73.
-
Proper tags for titles: H2 or H3? w3c/alreq#69.
-
-
3 issues received 11 new comments.
-
Proper tags for titles: H2 or H3? w3c/alreq#69 (9 comments by @mostafah, @ntounsi, @r12a, @shervinafshar)
-
-
7 pull requests opened.
-
Add Shekasteh Nastaliq to writing styles section w3c/alreq#72, by @ebraminio.
-
Consistent HTML tags for section titles w3c/alreq#71, by @mostafah.
-
First draft of “4.2 Justification“ w3c/alreq#70, by @mostafah.
-
markup improvements w3c/alreq#68, by @r12a.
-
Tidying Up HTML and Error Fixing w3c/alreq#67, by @shervinafshar.
-
Previous PRs ( pr#48 #64) resubmitted w3c/alreq#65, by @ntounsi.
-
4 pull requests merged.
-
First draft of “4.2 Justification“ w3c/alreq#70.
-
markup improvements w3c/alreq#68.
-
Tidying Up HTML and Error Fixing w3c/alreq#67.
-
Previous PRs ( pr#48 #64) resubmitted w3c/alreq#65.
-
-
4 pull requests received 9 new comments.
-
Add Shekasteh Nastaliq to writing styles section w3c/alreq#72 (6 comments by @ebraminio, @shervinafshar, @zoghal)
-
w3c/i18n-drafts
-
3 issues opened.
-
[questions/qa-floating-times] w3c/i18n-drafts#66, by @joconner.
-
[questions/qa-lang-why] Use lang now w3c/i18n-drafts#65, by @r12a.
-
[questions-qa-personal-names] w3c/i18n-drafts#64, by @Benzi-Junior.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Fix broken close tag in boilerplate-ja w3c/i18n-drafts#63, by @hail2u.
-
Fix broken links w3c/i18n-drafts#62, by @hail2u.
-
Japanese translation for “Declaring character encodings in HTML” w3c/i18n-drafts#61, by @hail2u.
-
-
2 pull requests merged.
-
Fix broken close tag in boilerplate-ja w3c/i18n-drafts#63.
-
Japanese translation for “Declaring character encodings in HTML” w3c/i18n-drafts#61.
-
-
1 pull request closed.
-
Fix broken links w3c/i18n-drafts#62.
-
-
2 pull requests received 8 new comments.
-
Japanese translation for “Declaring character encodings in HTML” w3c/i18n-drafts#61 (7 comments by @hail2u, @r12a)
-
w3c/i18n-checker
-
16 issues opened.
-
Separate the request header rows w3c/i18n-checker#64, by @r12a.
-
Report replacement character w3c/i18n-checker#63, by @r12a.
-
Private use characters w3c/i18n-checker#62, by @r12a.
-
check for rli etc w3c/i18n-checker#61, by @r12a.
-
re-add i18n-checker to Unicorn w3c/i18n-checker#60, by @r12a.
-
update versions w3c/i18n-checker#59, by @r12a.
-
Add more translate attributes w3c/i18n-checker#58, by @r12a.
-
Improve file layout? w3c/i18n-checker#56, by @tripu.
-
orange items with counts should not break across line ends w3c/i18n-checker#55, by @r12a.
-
hreflang language tags not being added to list of lang tags in info field w3c/i18n-checker#54, by @r12a.
-
Refactor longest PHP files w3c/i18n-checker#53, by @tripu.
-
Set up CI with Travis w3c/i18n-checker#52, by @tripu.
-
Show version number, or release, somewhere on the UI w3c/i18n-checker#51, by @tripu.
-
i18n Checker page does not display properly on Safari on Mac w3c/i18n-checker#50, by @stevenatkin.
-
Text missing in UTF-8 BOM disagrees with another declaration w3c/i18n-checker#49, by @stevenatkin.
-
“PHP Fatal error: Uncaught Error: Call to undefined function ‘mb_internal_encoding()’” w3c/i18n-checker#48, by @tripu.
-
-
4 issues closed.
-
Text missing in UTF-8 BOM disagrees with another declaration w3c/i18n-checker#49.
-
Show version number, or release, somewhere on the UI w3c/i18n-checker#51.
-
i18n Checker page does not display properly on Safari on Mac w3c/i18n-checker#50.
-
-
8 issues received 25 new comments.
-
“PHP Fatal error: Uncaught Error: Call to undefined function ‘mb_internal_encoding()’” w3c/i18n-checker#48 (7 comments by @r12a, @tripu)
-
i18n Checker page does not display properly on Safari on Mac w3c/i18n-checker#50 (5 comments by @r12a, @stevenatkin, @tripu)
-
Text missing in UTF-8 BOM disagrees with another declaration w3c/i18n-checker#49 (3 comments by @r12a, @stevenatkin)
-
hreflang language tags not being added to list of lang tags in info field w3c/i18n-checker#54 (1 comment by @adrianbj)
-
-
2 pull requests opened.
-
en.properties, changed "_blank" to '_blank' w3c/i18n-checker#57, by @r12a.
-
Minor fixes w3c/i18n-checker#47, by @tripu.
-
-
2 pull requests merged.
-
en.properties, changed "_blank" to '_blank' w3c/i18n-checker#57.
-
Minor fixes w3c/i18n-checker#47.
-
w3c/clreq
-
3 issues opened.
-
汉语拼音的行间注（分词、分字标注及兒化音） w3c/clreq#108, by @Buernia.
-
附錄A中有兩個標點符號的萬國碼出現筆誤 w3c/clreq#106, by @Man-Ting-Fang.
-
-
1 issue closed.
-
重复了 w3c/clreq#107.
-
-
1 issue received 2 new comments.
w3c/jlreq
-
1 issue opened.
-
Specifying the vertical positioning of the kihon-hanmen w3c/jlreq#3, by @r12a.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Internationalization Best Practices for Spec Developers published as a Working Draft. History of Internationalization Best Practices for Spec Developers
-
GitHub
w3c/i18n-checker
-
30 issues opened.
-
Test for zawgyi pseudo-unicode w3c/i18n-checker#46, by @r12a.
-
Provide a report on elements used w3c/i18n-checker#45, by @r12a.
-
check character references for supplementary characters w3c/i18n-checker#44, by @r12a.
-
Advise use of dir markup rather than styling w3c/i18n-checker#43, by @r12a.
-
check for invalid subtag names w3c/i18n-checker#42, by @r12a.
-
report use of grandfathered language tags w3c/i18n-checker#41, by @r12a.
-
check translate attribute values w3c/i18n-checker#40, by @r12a.
-
move check documentation file to github w3c/i18n-checker#39, by @r12a.
-
move test generator to github w3c/i18n-checker#38, by @r12a.
-
Check datetime formats w3c/i18n-checker#37, by @r12a.
-
Complete update of test suite w3c/i18n-checker#36, by @r12a.
-
check for hreflang w3c/i18n-checker#35, by @r12a.
-
if zh-CN, zh-TW etc are used, suggest zh-Hans and zh-Hant w3c/i18n-checker#34, by @r12a.
-
check for suppressed script, etc. when validating language tags w3c/i18n-checker#33, by @r12a.
-
if language attributes on body but not html tags w3c/i18n-checker#32, by @r12a.
-
check for white-space at the end of elements indicating a change in direction w3c/i18n-checker#31, by @r12a.
-
check for over-use of dir w3c/i18n-checker#30, by @r12a.
-
check for bidi control characters in places where markup would do w3c/i18n-checker#29, by @r12a.
-
check encoding supports logical order for Hebrew w3c/i18n-checker#28, by @r12a.
-
avoid HTML attributes with values of right and left w3c/i18n-checker#26, by @r12a.
-
use of entities in xml w3c/i18n-checker#25, by @r12a.
-
incorrect ncr for euro, or other C2 codes w3c/i18n-checker#24, by @r12a.
-
b and i tags together, only one detected w3c/i18n-checker#23, by @r12a.
-
Parking lot for Checks to add in the future w3c/i18n-checker#22, by @r12a.
-
Start using branches appropriately w3c/i18n-checker#21, by @tripu.
-
Write “README” with basic info w3c/i18n-checker#20, by @tripu.
-
Add check for encoding labels w3c/i18n-checker#19, by @r12a.
-
Add direct input tab w3c/i18n-checker#18, by @r12a.
-
Make further reading links open in new window w3c/i18n-checker#17, by @r12a.
-
-
38 issues closed.
-
Write “README” with basic info w3c/i18n-checker#20.
-
Fix About text w3c/i18n-checker#13.
-
Start using branches appropriately w3c/i18n-checker#21.
-
avoid HTML attributes with values of right and left w3c/i18n-checker#26.
-
check character references for supplementary characters w3c/i18n-checker#44.
-
Provide a report on elements used w3c/i18n-checker#45.
-
check for hreflang w3c/i18n-checker#35.
-
Make further reading links open in new window w3c/i18n-checker#17.
-
Advise use of dir markup rather than styling w3c/i18n-checker#43.
-
check for invalid subtag names w3c/i18n-checker#42.
-
check translate attribute values w3c/i18n-checker#40.
-
test for control characters w3c/i18n-checker#16.
-
if zh-CN, zh-TW etc are used, suggest zh-Hans and zh-Hant w3c/i18n-checker#34.
-
report use of grandfathered language tags w3c/i18n-checker#41.
-
if language attributes on body but not html tags w3c/i18n-checker#32.
-
check encoding supports logical order for Hebrew w3c/i18n-checker#28.
-
check for over-use of dir w3c/i18n-checker#30.
-
incorrect ncr for euro, or other C2 codes w3c/i18n-checker#24.
-
Check for Unicode directional controls closed w3c/i18n-checker#4.
-
check for suppressed script, etc. when validating language tags w3c/i18n-checker#33.
-
Language subtag validity w3c/i18n-checker#6.
-
Complete update of test suite w3c/i18n-checker#36.
-
move test generator to github w3c/i18n-checker#38.
-
move check documentation file to github w3c/i18n-checker#39.
-
Indicate usage of unicode directional controls w3c/i18n-checker#5.
-
use of entities in xml w3c/i18n-checker#25.
-
check for bidi control characters in places where markup would do w3c/i18n-checker#29.
-
Parking lot for Checks to add in the future w3c/i18n-checker#22.
-
Remove distinction between HTML5 and HTML4 w3c/i18n-checker#10.
-
b and i tags together, only one detected w3c/i18n-checker#23.
-
Consider merging with html validator w3c/i18n-checker#1.
-
Fix credits w3c/i18n-checker#12.
-
Make sure bdo doesn't have auto value w3c/i18n-checker#14.
-
Remove panel about doctypes and mime types w3c/i18n-checker#11.
-
Add check for encoding labels w3c/i18n-checker#19.
-
Check encoding values w3c/i18n-checker#7.
-
Revise advice for BOM w3c/i18n-checker#9.
-
-
1 issue reopened.
-
Fix About text w3c/i18n-checker#13, by @tripu.
-
-
37 issues received 64 new comments.
-
Remove distinction between HTML5 and HTML4 w3c/i18n-checker#10 (5 comments by @r12a, @sideshowbarker)
-
if the page is in Arabic, Hebrew, Urdu, Persian, Thaana, check that it starts with dir on html or body w3c/i18n-checker#27 (3 comments by @r12a, @sideshowbarker)
-
check for suppressed script, etc. when validating language tags w3c/i18n-checker#33 (1 comment by @r12a)
-
check for bidi control characters in places where markup would do w3c/i18n-checker#29 (1 comment by @r12a)
w3c/alreq
-
2 issues opened.
-
2.2 Direction needs section about "Numbers" w3c/alreq#62, by @PullFrom.
-
Numerical Fractions w3c/alreq#59, by @shervinafshar.
-
-
3 issues received 8 new comments.
-
2.2 Direction needs section about "Numbers" w3c/alreq#62 (4 comments by @mostafah, @ntounsi, @shervinafshar)
-
-
5 pull requests opened.
-
Action-58: Provide the sources for images of pr#48 w3c/alreq#64, by @ntounsi.
-
Tidying Up HTML w3c/alreq#63, by @shervinafshar.
-
Edits and more text for 4.2 justification section w3c/alreq#61, by @mostafah.
-
Expand the joining section about spacing w3c/alreq#60, by @mostafah.
-
Add an initial draft for “4.2 justification” w3c/alreq#58, by @mostafah.
-
-
4 pull requests merged.
-
Edits and more text for 4.2 justification section w3c/alreq#61.
-
Expand the joining section about spacing w3c/alreq#60.
-
Update generate-glossary.groovy w3c/alreq#55.
-
Add an initial draft for “4.2 justification” w3c/alreq#58.
-
-
3 pull requests closed.
-
Action-58: Provide the sources for images of pr#48 w3c/alreq#64.
-
Tidying Up HTML w3c/alreq#63.
-
Glossary w3c/alreq#54.
-
-
3 pull requests received 3 new comments.
w3c/i18n-activity
-
18 issues opened.
-
rb and rtc non-conforming in html5.1 w3c/i18n-activity#215, by @r12a.
-
Improper use of languageCode w3c/i18n-activity#214, by @stevenatkin.
-
Use of multiple currencies w3c/i18n-activity#213, by @stevenatkin.
-
Prevent the use of currency synonyms w3c/i18n-activity#212, by @stevenatkin.
-
'deleteWordForwards' and 'deleteWordBackwards' not well defined w3c/i18n-activity#211, by @aphillips.
-
"character" is not defined w3c/i18n-activity#210, by @aphillips.
-
'typographic character' should mention grapheme clusters [editorial] w3c/i18n-activity#209, by @aphillips.
-
Display name content rules? w3c/i18n-activity#208, by @aphillips.
-
Examples should include non-ASCII [editorial] w3c/i18n-activity#207, by @aphillips.
-
Re-investigate "compatibility caseless" matching #1666 w3c/i18n-activity#206, by @r12a.
-
Default Language Context MAY -> SHOULD #354 w3c/i18n-activity#205, by @r12a.
-
ed sugg: textDirection #348 w3c/i18n-activity#204, by @r12a.
-
processLanguage description improvement suggestion #345 w3c/i18n-activity#203, by @r12a.
-
Relationship between dc:language and processing language for multilingual resources #343 w3c/i18n-activity#202, by @r12a.
-
Processing language for mono-lingual and internationalized resources #342 w3c/i18n-activity#201, by @r12a.
-
Replace textDirection property with recommendation for including control characters in the text #336 w3c/i18n-activity#200, by @r12a.
-
Clarify principle that features of external resources are not authoritative #339 w3c/i18n-activity#199, by @r12a.
-
The textDirection and processingLanguage properties are not needed #335 w3c/i18n-activity#198, by @r12a.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
Replace textDirection property with recommendation for including control characters in the text #336 w3c/i18n-activity#200 (1 comment by @r12a)
-
w3c/i18n-drafts
-
2 issues opened.
-
[questions/qa-link-lang] Expand information about hreflang to cover search engines w3c/i18n-drafts#60, by @r12a.
-
[articles/inline-bidi-markup/index] Mirroring example w3c/i18n-drafts#59, by @r12a.
-
-
1 issue received 2 new comments.
-
[questions/qa-personal-names] Error in "Middle initials" section w3c/i18n-drafts#58 (2 comments by @lifthrasiir, @r12a)
-
w3c/bp-i18n-specdev
-
1 issue opened.
-
Use locale-neutral data representations w3c/bp-i18n-specdev#19, by @r12a.
-
w3c/clreq
-
2 pull requests opened.
-
Fix some translations for zh-hans. w3c/clreq#105, by @xiaohanyu.
-
Fix some typos w3c/clreq#104, by @xhacker.
-
-
1 pull request merged.
-
Fix some typos w3c/clreq#104.
-
-
1 pull request received 1 new comment.
w3c/charmod-norm
-
1 issue opened.
-
Case matching example seems wrong w3c/charmod-norm#99, by @r12a.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
https://github.com/w3c/charmod-norm/issues/99 w3c/charmod-norm#100, by @aphillips.
-
-
1 pull request merged.
-
https://github.com/w3c/charmod-norm/issues/99 w3c/charmod-norm#100.
-
w3c/predefined-counter-styles
-
2 issues opened.
-
Persian Alphabetic and Persian Abjad also used for Arabic w3c/predefined-counter-styles#13, by @ironymark.
-
Old Chinese Counting Rods w3c/predefined-counter-styles#12, by @Crissov.
-
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Francesco Martino (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Huawei joined.
-
GitHub
w3c/bp-i18n-specdev
-
4 issues opened.
-
Should also mention ALM beside LRM and RLM w3c/bp-i18n-specdev#18, by @lkemmel.
-
Some "problems with control characters" are not exclusive to CC, but also apply to markup w3c/bp-i18n-specdev#17, by @lkemmel.
-
Should include advice on specifying what a letter is. w3c/bp-i18n-specdev#16, by @spemberton.
-
Should include advice on what "White-space" is. w3c/bp-i18n-specdev#15, by @spemberton.
-
-
2 issues received 3 new comments.
-
Should include advice on what "White-space" is. w3c/bp-i18n-specdev#15 (2 comments by @johnwcowan, @spemberton)
-
w3c/i18n-drafts
-
3 issues opened.
-
[questions/qa-personal-names] Error in "Middle initials" section w3c/i18n-drafts#58, by @peremen.
-
[articles/definitions-time/index] w3c/i18n-drafts#57, by @dehildum.
-
[articles/definitions-time/index] w3c/i18n-drafts#56, by @dehildum.
-
-
8 issues closed.
-
[articles/definitions-time/index] w3c/i18n-drafts#56.
-
[articles/definitions-time/index] : Different Calendaring Systems w3c/i18n-drafts#54.
-
[articles/definitions-time/index] outdated link to Olson database w3c/i18n-drafts#53.
-
[articles/definitions-time/index] mention "summer time" in title w3c/i18n-drafts#52.
-
[articles/definitions-time/index] zone offset w3c/i18n-drafts#51.
-
[articles/definitions-time/index] title of time zone rules section w3c/i18n-drafts#50.
-
[articles/definitions-time/index] floating time editorial nits w3c/i18n-drafts#49.
-
[articles/definitions-time/index] incremental time mapping w3c/i18n-drafts#48.
-
-
8 issues received 9 new comments.
-
[articles/definitions-time/index] title of time zone rules section w3c/i18n-drafts#50 (1 comment by @r12a)
-
[articles/definitions-time/index] floating time editorial nits w3c/i18n-drafts#49 (1 comment by @r12a)
-
[articles/definitions-time/index] outdated link to Olson database w3c/i18n-drafts#53 (1 comment by @r12a)
-
[articles/definitions-time/index] mention "summer time" in title w3c/i18n-drafts#52 (1 comment by @r12a)
w3c/i18n-checker
-
16 issues opened.
-
test for control characters w3c/i18n-checker#16, by @r12a.
-
Make it possible to exclude certain reports w3c/i18n-checker#15, by @r12a.
-
Make sure bdo doesn't have auto value w3c/i18n-checker#14, by @r12a.
-
Fix About text w3c/i18n-checker#13, by @r12a.
-
Fix credits w3c/i18n-checker#12, by @r12a.
-
Remove panel about doctypes and mime types w3c/i18n-checker#11, by @r12a.
-
Remove distinction between HTML5 and HTML4 w3c/i18n-checker#10, by @r12a.
-
Revise advice for BOM w3c/i18n-checker#9, by @r12a.
-
Add auto value for dir w3c/i18n-checker#8, by @r12a.
-
Check encoding values w3c/i18n-checker#7, by @r12a.
-
Language subtag validity w3c/i18n-checker#6, by @r12a.
-
Indicate usage of unicode directional controls w3c/i18n-checker#5, by @r12a.
-
Check for Unicode directional controls closed w3c/i18n-checker#4, by @r12a.
-
Complete localization w3c/i18n-checker#3, by @r12a.
-
Add language detection w3c/i18n-checker#2, by @r12a.
-
Consider merging with html validator w3c/i18n-checker#1, by @r12a.
-
-
1 issue closed.
-
Add auto value for dir w3c/i18n-checker#8.
-
-
1 issue received 1 new comment.
w3c/i18n-activity
-
29 issues opened.
-
Authoring requirement for bidi formatting characters seems bogus w3c/i18n-activity#197, by @r12a.
-
Refer to i18n test pages w3c/i18n-activity#196, by @r12a.
-
Ruby clarification on specs w3c/i18n-activity#195, by @r12a.
-
[css-containment]: css-containment needs a label w3c/i18n-activity#194, by @jgw96.
-
A number of vocabulary items need language/direction/etc. metadata w3c/i18n-activity#193, by @aphillips.
-
Country code reference is wrong. w3c/i18n-activity#192, by @aphillips.
-
Reference locale-neutral in BP13? w3c/i18n-activity#191, by @aphillips.
-
Best practice for including language and direction metadata? w3c/i18n-activity#190, by @aphillips.
-
Locale references to BCP47 and CLDR w3c/i18n-activity#189, by @aphillips.
-
Spelling of locale (editorial) w3c/i18n-activity#188, by @aphillips.
-
BP3 should recommend locale-neutral representation w3c/i18n-activity#187, by @aphillips.
-
Encoding of text/plain in example (editorial) w3c/i18n-activity#186, by @aphillips.
-
Should there be a Best Practice to use Unicode and/or UTF-8? w3c/i18n-activity#185, by @aphillips.
-
**Map fields become a SHOULD w3c/i18n-activity#184, by @r12a.
-
no language or direction or localizability of error message? w3c/i18n-activity#183, by @aphillips.
-
no way to indicate direction or language of name w3c/i18n-activity#182, by @aphillips.
-
example in pounds w3c/i18n-activity#181, by @aphillips.
-
encoding health warning for x-www-urlencoded w3c/i18n-activity#180, by @aphillips.
-
Linking to RFC 3339 for duration is dubious w3c/i18n-activity#179, by @r12a.
-
Why exclude markup from name? w3c/i18n-activity#178, by @r12a.
-
Editorial: Suggestion for spanish translations w3c/i18n-activity#177, by @r12a.
-
It should be possible to indicate the default base direction for natural language values w3c/i18n-activity#176, by @r12a.
-
How to know the language of a natural language value when there is no translation? w3c/i18n-activity#175, by @r12a.
-
RFC 5646 listed as informative reference w3c/i18n-activity#174, by @r12a.
-
Use BCP 47 rather than RFC 5646 w3c/i18n-activity#173, by @r12a.
-
Internationalize IRI in example 3 w3c/i18n-activity#172, by @r12a.
-
Clarify that zone offsets in times do not indicate local time #331 w3c/i18n-activity#171, by @r12a.
-
Support css-counter-styles-3 w3c/i18n-activity#170, by @r12a.
-
Character encoding of documents #261 w3c/i18n-activity#169, by @r12a.
-
-
13 issues closed.
-
i18n-ISSUE-480: New role for Ruby? w3c/i18n-activity#83.
-
i18n-ISSUE-402: Broken copy/paste behavior with IRIs w3c/i18n-activity#58.
-
FindText API vs. Charmod-Norm w3c/i18n-activity#106.
-
i18n-ISSUE-493: add sections (non-I18N) w3c/i18n-activity#112.
-
[css-containment]: css-containment needs a label w3c/i18n-activity#194.
-
How to know the language of a natural language value when there is no translation? w3c/i18n-activity#175.
-
i18n-ISSUE-387: AS2.0: Section 3.2: language example issues w3c/i18n-activity#43.
-
Linking to RFC 3339 for duration is dubious w3c/i18n-activity#179.
-
RFC 5646 listed as informative reference w3c/i18n-activity#174.
-
Use BCP 47 rather than RFC 5646 w3c/i18n-activity#173.
-
Internationalize IRI in example 3 w3c/i18n-activity#172.
-
Clarify that zone offsets in times do not indicate local time #331 w3c/i18n-activity#171.
-
-
19 issues received 27 new comments.
-
A number of vocabulary items need language/direction/etc. metadata w3c/i18n-activity#193 (3 comments by @aphillips, @fsasaki)
-
How to know the language of a natural language value when there is no translation? w3c/i18n-activity#175 (2 comments by @r12a)
-
i18n-ISSUE-476: International payment, taxation, delivery and trade restriction practices w3c/i18n-activity#82 (1 comment by @aphillips)
-
Best practice for including language and direction metadata? w3c/i18n-activity#190 (1 comment by @fsasaki)
-
Possibility for a character to be interpreted differently depending on locale w3c/i18n-activity#114 (1 comment by @r12a)
-
list of displays: should it address display name, language, etc.? w3c/i18n-activity#113 (1 comment by @r12a)
-
i18n-ISSUE-387: AS2.0: Section 3.2: language example issues w3c/i18n-activity#43 (1 comment by @r12a)
w3c/jlreq
-
2 issues opened.
-
Fig. 3.83 doesn't match its description w3c/jlreq#2, by @r12a.
-
Fig. 4.9 heading indent mistake w3c/jlreq#1, by @r12a.
-
w3c/alreq
-
1 issue opened.
-
Drafting “justification” w3c/alreq#57, by @mostafah.
-
-
1 issue closed.
-
Drafting “direction” w3c/alreq#28.
-
-
2 issues received 7 new comments.
-
3 pull requests opened.
-
Add section “2.3 direction” w3c/alreq#56, by @mostafah.
-
Update generate-glossary.groovy w3c/alreq#55, by @ntounsi.
-
-
2 pull requests merged.
-
Add section “2.3 direction” w3c/alreq#56.
-
Modified on font and typographical considerations w3c/alreq#48.
-
-
1 pull request closed.
-
Add initial draft for section “2.3 direction” w3c/alreq#53.
-
-
1 pull request reopened.
-
Modified on font and typographical considerations w3c/alreq#48, by @ntounsi.
-
-
1 pull request received 2 new comments.
-
Add initial draft for section “2.3 direction” w3c/alreq#53 (2 comments by @mostafah, @shervinafshar)
-
w3c/predefined-counter-styles
-
6 issues opened.
-
Add examples from css-counter-styles w3c/predefined-counter-styles#10, by @Crissov.
-
Clock face emoji counter style w3c/predefined-counter-styles#9, by @Crissov.
-
Astronomic and astrologic (symbolic/emoji) styles w3c/predefined-counter-styles#8, by @Crissov.
-
Emoji decimal styles w3c/predefined-counter-styles#7, by @Crissov.
-
‘fullwidth-’, ‘circled-’ and similar styles w3c/predefined-counter-styles#6, by @Crissov.
-
`lower-roman` with final j w3c/predefined-counter-styles#5, by @Crissov.
-
-
3 issues closed.
-
Astronomic and astrologic (symbolic/emoji) styles w3c/predefined-counter-styles#8.
-
Add examples from css-counter-styles w3c/predefined-counter-styles#10.
-
Emoji decimal styles w3c/predefined-counter-styles#7.
-
-
5 issues received 6 new comments.
-
Astronomic and astrologic (symbolic/emoji) styles w3c/predefined-counter-styles#8 (1 comment by @r12a)
w3c/clreq
-
2 issues opened.
-
注音符号与汉字的比例 w3c/clreq#103, by @Buernia.
-
「臺灣方言音符號」應為「臺灣方音符號」 w3c/clreq#102, by @glll4678.
-
-
1 issue received 2 new comments.
TR publications
-
2 documents published.
-
Custom Counter Styles published as a Working Draft. History of Custom Counter Styles
-
Internationalization Best Practices for Spec Developers published as a Working Draft. History of Internationalization Best Practices for Spec Developers
-
GitHub
w3c/alreq
-
1 issue opened.
-
1 issue closed.
-
Variant letter shapes w3c/alreq#22.
-
-
3 issues received 21 new comments.
-
Shortcomings of Characters Table w3c/alreq#49 (16 comments by @brawer, @khaledhosny, @mostafah, @ntounsi, @PullFrom, @r12a)
-
Symbols in the language columns of the character tables are confusing w3c/alreq#52 (1 comment by @mostafah)
-
-
3 pull requests opened.
-
Add initial draft for section “2.3 direction” w3c/alreq#53, by @mostafah.
-
Fix minor typo w3c/alreq#51, by @mostafah.
-
Note some characters representing a single letter w3c/alreq#50, by @mostafah.
-
-
2 pull requests merged.
-
Fix minor typo w3c/alreq#51.
-
Note some characters representing a single letter w3c/alreq#50.
-
-
2 pull requests received 4 new comments.
-
Modified on font and typographical considerations w3c/alreq#48 (2 comments by @khaledhosny, @ntounsi)
-
w3c/i18n-activity
-
6 issues opened.
-
Section 3.2: no language support w3c/i18n-activity#168, by @aphillips.
-
section 3.2: no character encoding on response examples w3c/i18n-activity#167, by @aphillips.
-
section 3.1.2 charset w3c/i18n-activity#166, by @aphillips.
-
Line breaking opportunities at the boundary of a white-space:pre inline element #189 w3c/i18n-activity#165, by @r12a.
-
Default <details> heading should be localized #470 w3c/i18n-activity#164, by @r12a.
-
Is input type=datetime implemented? w3c/i18n-activity#163, by @r12a.
-
-
25 issues closed.
-
value on button in submit state is translateable #230 w3c/i18n-activity#128.
-
i18n-ISSUE-343: Type attribute on ol w3c/i18n-activity#33.
-
why is "content language" pragma processing not equivalent to HTTP Content-Language? #261 w3c/i18n-activity#127.
-
Use of dc:language w3c/i18n-activity#146.
-
make definition of a character more precise w3c/i18n-activity#138.
-
Defaults for an Annotation Collection w3c/i18n-activity#144.
-
missing mechanism to express language preferences in the intendend audience field w3c/i18n-activity#140.
-
How is language assigned to an annotation? w3c/i18n-activity#145.
-
update reference for language tags: BCP47 instead of RFC5646 w3c/i18n-activity#137.
-
String body must not have a language associated? w3c/i18n-activity#135.
-
Model is defined in terms of IRIs; Protocol with URI #241 w3c/i18n-activity#162.
-
Normalisation of Text Quote Selector w3c/i18n-activity#141.
-
vague definition of charactor position for text position selector w3c/i18n-activity#132.
-
Request header and language negotiation w3c/i18n-activity#143.
-
exactly 0 or 1 language(s) w3c/i18n-activity#147.
-
Remove "and so forth", clarify utf-8 encoding #237 w3c/i18n-activity#155.
-
Base direction for annotations w3c/i18n-activity#136.
-
have a note on logical and visual order of text for text quote selector implementations w3c/i18n-activity#139.
-
'generated' and 'modified' should use UTC by default w3c/i18n-activity#149.
-
white space normalisation w3c/i18n-activity#142.
-
Reference to text encoding in spec perhaps not appropriate w3c/i18n-activity#154.
-
'generated' and 'modified' date/time properties specific reference and format w3c/i18n-activity#148.
-
TimeState, generated, and modified should recommend all values use UTC w3c/i18n-activity#150.
-
Question about the use of Content-Language as fallback language for lang attribute. w3c/i18n-activity#161.
-
Change how invalid lang codes are to be treated by user agents w3c/i18n-activity#160.
-
-
6 issues received 12 new comments.
-
Remove the use of printable character from accessKey attribute. w3c/i18n-activity#158 (6 comments by @aphillips, @r12a, @stevenatkin)
-
i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) w3c/i18n-activity#122 (1 comment by @aphillips)
-
Question about the use of Content-Language as fallback language for lang attribute. w3c/i18n-activity#161 (1 comment by @r12a)
-
Change how invalid lang codes are to be treated by user agents w3c/i18n-activity#160 (1 comment by @r12a)
-
w3c/i18n-drafts
-
9 issues opened.
-
[questions/qa-what-is-encoding] w3c/i18n-drafts#55, by @sup-engineer.
-
[articles/definitions-time/index] : Different Calendaring Systems w3c/i18n-drafts#54, by @tomerm.
-
[articles/definitions-time/index] outdated link to Olson database w3c/i18n-drafts#53, by @aphillips.
-
[articles/definitions-time/index] mention "summer time" in title w3c/i18n-drafts#52, by @aphillips.
-
[articles/definitions-time/index] zone offset w3c/i18n-drafts#51, by @aphillips.
-
[articles/definitions-time/index] title of time zone rules section w3c/i18n-drafts#50, by @aphillips.
-
[articles/definitions-time/index] floating time editorial nits w3c/i18n-drafts#49, by @aphillips.
-
[articles/definitions-time/index] incremental time mapping w3c/i18n-drafts#48, by @aphillips.
-
Feedback on questions/qa-css-lang w3c/i18n-drafts#47, by @catchmyfame.
-
-
2 issues closed.
-
[tutorials/bidi-xhtml/index] misaligned references to articles w3c/i18n-drafts#42.
-
Feedback on questions/qa-css-lang w3c/i18n-drafts#47.
-
-
1 issue received 1 new comment.
w3c/bp-i18n-specdev
-
10 issues opened.
-
mention the language subtag registry w3c/bp-i18n-specdev#14, by @aphillips.
-
improve description of BCP 47 w3c/bp-i18n-specdev#13, by @aphillips.
-
establish a glossary? w3c/bp-i18n-specdev#12, by @aphillips.
-
Change rule to allow surrogates w3c/bp-i18n-specdev#11, by @stevenatkin.
-
Consider creating a rule regarding rejecting invalid surrogate pairs w3c/bp-i18n-specdev#10, by @stevenatkin.
-
Possibly soften requirements related to logical order over visual order. w3c/bp-i18n-specdev#9, by @stevenatkin.
-
Change the rule for establishing base direction w3c/bp-i18n-specdev#8, by @stevenatkin.
-
Change the rule for assuming text direction from language w3c/bp-i18n-specdev#7, by @stevenatkin.
-
Consider combining defining language value checklist rules w3c/bp-i18n-specdev#6, by @stevenatkin.
-
Mention inheritance when defining default text processing language. w3c/bp-i18n-specdev#5, by @stevenatkin.
-
-
5 issues closed.
-
Change the rule for assuming text direction from language w3c/bp-i18n-specdev#7.
-
Change rule to allow surrogates w3c/bp-i18n-specdev#11.
-
Possibly soften requirements related to logical order over visual order. w3c/bp-i18n-specdev#9.
-
Consider combining defining language value checklist rules w3c/bp-i18n-specdev#6.
-
Spell out internationalization in place of 'i18n' w3c/bp-i18n-specdev#2.
-
-
9 issues received 20 new comments.
-
Possibly soften requirements related to logical order over visual order. w3c/bp-i18n-specdev#9 (5 comments by @andjc, @duerst, @r12a, @stevenatkin, @tomerm)
-
Consider creating a rule regarding rejecting invalid surrogate pairs w3c/bp-i18n-specdev#10 (4 comments by @aphillips, @r12a, @stevenatkin)
-
Change rule to allow surrogates w3c/bp-i18n-specdev#11 (3 comments by @aphillips, @r12a, @stevenatkin)
-
Spell out internationalization in place of 'i18n' w3c/bp-i18n-specdev#2 (2 comments by @aphillips, @r12a)
-
Consider combining defining language value checklist rules w3c/bp-i18n-specdev#6 (2 comments by @r12a, @stevenatkin)
-
Change the rule for assuming text direction from language w3c/bp-i18n-specdev#7 (1 comment by @r12a)
-
-
1 pull request closed.
-
fixing typos w3c/bp-i18n-specdev#4.
-
w3c/predefined-counter-styles
-
1 issue received 1 new comment.
TR publications
-
1 document published.
GitHub
w3c/alreq
-
1 issue opened.
-
Shortcomings of Characters Table w3c/alreq#49, by @PullFrom.
-
-
3 issues closed.
-
Deprecated Arabic presentation forms considered helpful w3c/alreq#32.
-
Drafting "Characters in Use" w3c/alreq#8.
-
Building exemplar charts w3c/alreq#31.
-
-
5 issues received 18 new comments.
-
Shortcomings of Characters Table w3c/alreq#49 (10 comments by @khaledhosny, @mostafah, @PullFrom, @r12a)
-
Deprecated Arabic presentation forms considered helpful w3c/alreq#32 (3 comments by @behnam, @khaledhosny, @shervinafshar)
-
Drafting "Font and Typographical Considerations" w3c/alreq#9 (2 comments by @ntounsi, @shervinafshar)
-
-
5 pull requests opened.
-
Modified on font and typographical considerations w3c/alreq#48, by @ntounsi.
-
Add some text for the diacritics section w3c/alreq#47, by @mostafah.
-
Add a short overview of the characters section w3c/alreq#46, by @mostafah.
-
Add information about the sources of the character tables w3c/alreq#45, by @mostafah.
-
-
4 pull requests merged.
-
Add some text for the diacritics section w3c/alreq#47.
-
Add a short overview of the characters section w3c/alreq#46.
-
-
1 pull request received 1 new comment.
-
Add the rest of character images and improve the look of character tables w3c/alreq#44 (1 comment by @mostafah)
-
w3c/clreq
-
2 issues opened.
-
对旧有的破折号、连接号用法加入澄清注解 w3c/clreq#101, by @Artoria2e5.
-
规范文档未遵循规范描述 w3c/clreq#100, by @ibelem.
-
-
1 issue received 1 new comment.
w3c/i18n-activity
-
39 issues opened.
-
Model is defined in terms of IRIs; Protocol with URI #241 w3c/i18n-activity#162, by @r12a.
-
Question about the use of Content-Language as fallback language for lang attribute. w3c/i18n-activity#161, by @stevenatkin.
-
Change how invalid lang codes are to be treated by user agents w3c/i18n-activity#160, by @stevenatkin.
-
Use of modifier keys for accesskey w3c/i18n-activity#159, by @r12a.
-
Remove the use of printable character from accessKey attribute. w3c/i18n-activity#158, by @stevenatkin.
-
Define or remove the use of the term Plain Unicode String w3c/i18n-activity#157, by @stevenatkin.
-
Should navigator.language and and/or HTTP Accept-Language include locale? w3c/i18n-activity#156, by @r12a.
-
Remove "and so forth", clarify utf-8 encoding #237 w3c/i18n-activity#155, by @r12a.
-
Reference to text encoding in spec perhaps not appropriate w3c/i18n-activity#154, by @r12a.
-
[csvw] instance definitions for direction w3c/i18n-activity#153, by @r12a.
-
Specifying changes to parameters for fallback fonts w3c/i18n-activity#152, by @r12a.
-
example of language detection fallback w3c/i18n-activity#151, by @r12a.
-
TimeState, generated, and modified should recommend all values use UTC w3c/i18n-activity#150, by @aphillips.
-
'generated' and 'modified' should use UTC by default w3c/i18n-activity#149, by @aphillips.
-
'generated' and 'modified' date/time properties specific reference and format w3c/i18n-activity#148, by @aphillips.
-
exactly 0 or 1 language(s) w3c/i18n-activity#147, by @r12a.
-
Use of dc:language w3c/i18n-activity#146, by @r12a.
-
How is language assigned to an annotation? w3c/i18n-activity#145, by @r12a.
-
Defaults for an Annotation Collection w3c/i18n-activity#144, by @r12a.
-
Request header and language negotiation w3c/i18n-activity#143, by @r12a.
-
white space normalisation w3c/i18n-activity#142, by @r12a.
-
Normalisation of Text Quote Selector w3c/i18n-activity#141, by @r12a.
-
missing mechanism to express language preferences in the intendend audience field w3c/i18n-activity#140, by @fsasaki.
-
have a note on logical and visual order of text for text quote selector implementations w3c/i18n-activity#139, by @fsasaki.
-
make definition of a character more precise w3c/i18n-activity#138, by @fsasaki.
-
update reference for language tags: BCP47 instead of RFC5646 w3c/i18n-activity#137, by @fsasaki.
-
Base direction for annotations w3c/i18n-activity#136, by @r12a.
-
String body must not have a language associated? w3c/i18n-activity#135, by @r12a.
-
vague definition of charactor position for text position selector w3c/i18n-activity#134, by @r12a.
-
Improve documentation of i18n issues with input type="number" w3c/i18n-activity#133, by @r12a.
-
vague definition of charactor position for text position selector w3c/i18n-activity#132, by @r12a.
-
Add section on internationalization #53 w3c/i18n-activity#131, by @r12a.
-
add warning/advice about lang attribute use #218 w3c/i18n-activity#130, by @r12a.
-
make any element with an explicit lang attribute (and no dir attribute) bidi-isolated by default #226 w3c/i18n-activity#129, by @r12a.
-
value on button in submit state is translateable #230 w3c/i18n-activity#128, by @r12a.
-
why is "content language" pragma processing not equivalent to HTTP Content-Language? #261 w3c/i18n-activity#127, by @r12a.
-
Sort out issues with [inputmode] w3c/i18n-activity#126, by @r12a.
-
html and head elements should not get new attributes #305 w3c/i18n-activity#125, by @r12a.
-
Default styling for q element w3c/i18n-activity#124, by @r12a.
-
-
7 issues closed.
-
i18n-ISSUE-139: Multilingual q nesting w3c/i18n-activity#32.
-
i18n-ISSUE-119: provide example of language detection fallback w3c/i18n-activity#120.
-
html and head elements should not get new attributes #305 w3c/i18n-activity#125.
-
ISSUE-80: Default rules for the quotes property w3c/i18n-activity#117.
-
add warning/advice about lang attribute use #218 w3c/i18n-activity#130.
-
vague definition of charactor position for text position selector w3c/i18n-activity#134.
-
-
10 issues received 10 new comments.
-
Remove the use of printable character from accessKey attribute. w3c/i18n-activity#158 (1 comment by @r12a)
-
Tighten up usages of "compatibilty caseless" comparisons used in the spec w3c/i18n-activity#121 (1 comment by @aphillips)
-
i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) w3c/i18n-activity#122 (1 comment by @aphillips)
-
make any element with an explicit lang attribute (and no dir attribute) bidi-isolated by default #226 w3c/i18n-activity#129 (1 comment by @r12a)
-
html and head elements should not get new attributes #305 w3c/i18n-activity#125 (1 comment by @r12a)
-
i18n-ISSUE-119: provide example of language detection fallback w3c/i18n-activity#120 (1 comment by @r12a)
-
vague definition of charactor position for text position selector w3c/i18n-activity#134 (1 comment by @r12a)
w3c/predefined-counter-styles
-
2 issues opened.
-
Mixed content in chrome, respec fails w3c/predefined-counter-styles#4, by @tabatkins.
-
Should we add more Latin counter styles? w3c/predefined-counter-styles#3, by @r12a.
-
-
1 issue closed.
-
Mixed content in chrome, respec fails w3c/predefined-counter-styles#4.
-
-
3 issues received 5 new comments.
-
Should we add more Latin counter styles? w3c/predefined-counter-styles#3 (2 comments by @henke37, @prlbr)
-
Mixed content in chrome, respec fails w3c/predefined-counter-styles#4 (2 comments by @r12a, @upsuper)
-
Names of Arabic counters do not match Unicode/CLDR naming w3c/predefined-counter-styles#1 (1 comment by @r12a)
-
w3c/i18n-drafts
-
5 issues opened.
-
broken link [questions/qa-html-language-declarations] w3c/i18n-drafts#46, by @MatthiasApsel.
-
[questions/qa-byte-order-mark] test issue w3c/i18n-drafts#45, by @r12a.
-
[questions/qa-floating-times] w3c/i18n-drafts#44, by @matial.
-
[questions/qa-lang-why]#fonts Inconsistent font style (serif vs. sans, weight) w3c/i18n-drafts#43, by @Artoria2e5.
-
[tutorials/bidi-xhtml/index] misaligned references to articles w3c/i18n-drafts#42, by @johnobe.
-
-
3 issues closed.
-
broken link [questions/qa-html-language-declarations] w3c/i18n-drafts#46.
-
[questions/qa-byte-order-mark] test issue w3c/i18n-drafts#45.
-
[questions/qa-lang-why]#fonts Inconsistent font style (serif vs. sans, weight) w3c/i18n-drafts#43.
-
-
3 issues received 4 new comments.
-
[questions/qa-lang-why]#fonts Inconsistent font style (serif vs. sans, weight) w3c/i18n-drafts#43 (2 comments by @Artoria2e5, @r12a)
-
[tutorials/bidi-xhtml/index] misaligned references to articles w3c/i18n-drafts#42 (1 comment by @r12a)
-
w3c/ilreq
-
2 issues opened.
-
Reduce duplication in orthographic syllable tables w3c/ilreq#7, by @r12a.
-
new-updated-ilreq w3c/ilreq#4, by @slata.
-
-
1 issue closed.
-
new-updated-ilreq w3c/ilreq#4.
-
-
5 pull requests opened.
-
Update index.html w3c/ilreq#10, by @slata.
-
Update index.html w3c/ilreq#9, by @slata.
-
Update index.html w3c/ilreq#8, by @slata.
-
Update index.html w3c/ilreq#6, by @slata.
-
Slata patch 3 w3c/ilreq#5, by @slata.
-
-
5 pull requests merged.
-
Update index.html w3c/ilreq#10.
-
Update index.html w3c/ilreq#9.
-
Update index.html w3c/ilreq#8.
-
Update index.html w3c/ilreq#6.
-
Slata patch 3 w3c/ilreq#5.
-
-
1 pull request closed.
-
Update index.html w3c/ilreq#3.
-
-
1 pull request received 1 new comment.
w3c/i18n-discuss
-
1 issue received 7 new comments.
-
The HTML q element can sometimes be useful. Discuss. w3c/i18n-discuss#1 (7 comments by @aphillips, @asmusf, @johnwcowan, @r12a, @undivaga)
-
w3c/unicode-xml
-
1 issue opened.
-
Browsers ignoring Bidi Embedding Controls is probably not web-compatible w3c/unicode-xml#20, by @SimonSapin.
-
-
1 issue received 3 new comments.
-
Browsers ignoring Bidi Embedding Controls is probably not web-compatible w3c/unicode-xml#20 (3 comments by @duerst, @r12a, @SimonSapin)
-
TR publications
-
1 document published.
Participants
-
1 organization joined.
-
Cornac Servicios Editoriales joined.
-
GitHub
w3c/clreq
-
2 issues opened.
-
“省略号使用英文的三点省略号” Not seen in English version w3c/clreq#98, by @Artoria2e5.
w3c/i18n-discuss
-
1 issue opened.
-
The HTML q element can sometimes be useful. Discuss. w3c/i18n-discuss#1, by @r12a.
-
-
1 issue received 11 new comments.
-
The HTML q element can sometimes be useful. Discuss. w3c/i18n-discuss#1 (11 comments by @asmusf, @johnwcowan, @r12a, @textexin, @undivaga)
-
w3c/i18n-drafts
-
6 issues opened.
-
Feedback on questions/qa-i18n w3c/i18n-drafts#41, by @maciejlew.
-
Feedback on questions/qa-i18n w3c/i18n-drafts#40, by @maciejlew.
-
[articles/ruby/markup] The blank <rt> is not needed in the last example w3c/i18n-drafts#39, by @upsuper.
-
[articles/ruby/markup] Links are broken w3c/i18n-drafts#38, by @upsuper.
-
[tutorials/tutorial-char-enc/index] w3c/i18n-drafts#36, by @DrLopez.
-
[tutorials/tutorial-char-enc/index] w3c/i18n-drafts#35, by @DrLopez.
-
-
7 issues closed.
-
Feedback on questions/qa-i18n w3c/i18n-drafts#41.
-
[articles/ruby] do something about TR/ruby? w3c/i18n-drafts#10.
-
[articles/ruby/markup] Links are broken w3c/i18n-drafts#38.
-
Feedback on questions/qa-i18n w3c/i18n-drafts#40.
-
[articles/ruby/markup] The blank <rt> is not needed in the last example w3c/i18n-drafts#39.
-
[tutorials/tutorial-char-enc/index] w3c/i18n-drafts#35.
-
[tutorials/tutorial-char-enc/index] w3c/i18n-drafts#36.
-
-
6 issues received 7 new comments.
-
[articles/ruby/markup] The blank <rt> is not needed in the last example w3c/i18n-drafts#39 (1 comment by @r12a)
-
1 pull request opened.
-
Replace "girl" with "woman" w3c/i18n-drafts#37, by @jkshapiro.
-
-
1 pull request closed.
-
Replace "girl" with "woman" w3c/i18n-drafts#37.
-
-
1 pull request received 1 new comment.
w3c/alreq
-
1 issue closed.
-
Drafting questions w3c/alreq#38.
-
-
4 issues received 5 new comments.
-
Deprecated Arabic presentation forms considered helpful w3c/alreq#32 (2 comments by @ntounsi, @shervinafshar)
-
-
2 pull requests opened.
-
Char tables w3c/alreq#43, by @mostafah.
-
New section Font and Typographical considerations w3c/alreq#42, by @ntounsi.
-
-
2 pull requests merged.
-
Char tables w3c/alreq#43.
-
New section Font and Typographical considerations w3c/alreq#42.
-
-
1 pull request closed.
-
New section on Font and typographical considerations w3c/alreq#33.
-
-
1 pull request reopened.
-
New section Font and Typographical considerations w3c/alreq#42, by @ntounsi.
-
w3c/i18n-activity
-
7 issues opened.
-
i18n-ISSUE-89: Time zones and local dates and times w3c/i18n-activity#123, by @r12a.
-
i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) w3c/i18n-activity#122, by @r12a.
-
Tighten up usages of "compatibilty caseless" comparisons used in the spec w3c/i18n-activity#121, by @r12a.
-
i18n-ISSUE-119: provide example of language detection fallback w3c/i18n-activity#120, by @r12a.
-
add warning/advice about lang attribute use w3c/i18n-activity#119, by @r12a.
-
make any element with an explicit lang attribute (and no dir attribute) bidi-isolated by default w3c/i18n-activity#118, by @r12a.
-
ISSUE-80: Default rules for the quotes property w3c/i18n-activity#117, by @r12a.
-
-
6 issues closed.
-
i18n-ISSUE-422: start/end linked to left/right w3c/i18n-activity#5.
-
i18n-ISSUE-424: More formal grammar? w3c/i18n-activity#6.
-
i18n-ISSUE-432: 6.2.1 processing model handling of bidi w3c/i18n-activity#10.
-
i18n-ISSUE-434: 3.1 Line wrapping for non-Latin scripts w3c/i18n-activity#11.
-
i18n-ISSUE-436: 6.2.1 line heights w3c/i18n-activity#13.
-
i18n-ISSUE-507: WebVTT alignment cue setting keywords #262 w3c/i18n-activity#14.
-
-
7 issues received 7 new comments.
-
i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) w3c/i18n-activity#122 (1 comment by @r12a)
-
Tighten up usages of "compatibilty caseless" comparisons used in the spec w3c/i18n-activity#121 (1 comment by @r12a)
-
i18n-ISSUE-119: provide example of language detection fallback w3c/i18n-activity#120 (1 comment by @r12a)
w3c/charmod-norm
-
7 issues opened.
-
Limitations of Normalization - Confusion w3c/charmod-norm#88, by @klensin.
-
Confusability vs string matching w3c/charmod-norm#87, by @r12a.
-
[ed] eliminating encoding variation w3c/charmod-norm#86, by @r12a.
-
Removing meaning w3c/charmod-norm#85, by @r12a.
-
[ed] normalization forms w3c/charmod-norm#84, by @r12a.
-
❿ hasn't a compat equiv w3c/charmod-norm#83, by @r12a.
-
Arabic & Hebrew issues with 2.4 w3c/charmod-norm#82, by @r12a.
-
-
9 issues closed.
-
String matching problem (Section 2 introduction) -- types of operations w3c/charmod-norm#65.
-
Definition of "Syntactic content" (section 1.4) w3c/charmod-norm#56.
-
XML use of DTD (Section 1.4, Example 1 in 2016-02-01 Editor's version) w3c/charmod-norm#57.
-
Definition of "natural language content' (Section 1.4) w3c/charmod-norm#58.
-
Section number references to Unicode Standard w3c/charmod-norm#61.
-
Definition of "vocabulary", Section 1.2 w3c/charmod-norm#60.
-
Arabic & Hebrew unique issues associated with sections 2.4 and 2.5 w3c/charmod-norm#80.
-
add section for other kinds of equivalence w3c/charmod-norm#23.
-
[ed] normalization forms w3c/charmod-norm#84.
-
-
17 issues received 43 new comments.
-
Arabic & Hebrew unique issues associated with sections 2.4 and 2.5 w3c/charmod-norm#80 (9 comments by @aphillips, @tomerm)
-
Limitations of Normalization - Confusion w3c/charmod-norm#88 (5 comments by @aphillips, @asmusf, @r12a)
-
2.2.1 Canonical vs. Compatibility Equivalence vs Canonical non-equivalence w3c/charmod-norm#69 (2 comments by @asmusf, @r12a)
-
String matching problem (Section 2 introduction) -- types of operations w3c/charmod-norm#65 (1 comment by @aphillips)
-
XML use of DTD (Section 1.4, Example 1 in 2016-02-01 Editor's version) w3c/charmod-norm#57 (1 comment by @aphillips)
-
Definition of "natural language content' (Section 1.4) w3c/charmod-norm#58 (1 comment by @aphillips)
-
-
10 pull requests opened.
-
Adding text related to expansion of character escapes and includes. w3c/charmod-norm#98, by @aphillips.
-
Removed two old ednote comments from Section 3.2.3 and added text rel… w3c/charmod-norm#97, by @aphillips.
-
issue 88 w3c/charmod-norm#96, by @aphillips.
-
issue 80 w3c/charmod-norm#95, by @aphillips.
-
Address issue 80. Additional edits. w3c/charmod-norm#94, by @aphillips.
-
Addressing additional comments and adding specific bits of text. w3c/charmod-norm#93, by @aphillips.
-
Issue-83 w3c/charmod-norm#92, by @aphillips.
-
Issue-84, Issue-86 w3c/charmod-norm#91, by @aphillips.
-
Addressed issue-86 w3c/charmod-norm#90, by @aphillips.
-
Addressing comments in Issue-88 w3c/charmod-norm#89, by @aphillips.
-
-
10 pull requests merged.
-
Adding text related to expansion of character escapes and includes. w3c/charmod-norm#98.
-
Removed two old ednote comments from Section 3.2.3 and added text rel… w3c/charmod-norm#97.
-
issue 88 w3c/charmod-norm#96.
-
issue 80 w3c/charmod-norm#95.
-
Address issue 80. Additional edits. w3c/charmod-norm#94.
-
Addressing additional comments and adding specific bits of text. w3c/charmod-norm#93.
-
Issue-83 w3c/charmod-norm#92.
-
Issue-84, Issue-86 w3c/charmod-norm#91.
-
Addressed issue-86 w3c/charmod-norm#90.
-
Addressing comments in Issue-88 w3c/charmod-norm#89.
-
w3c/unicode-xml
-
1 issue opened.
-
Make reason for often using characters (and not styling) for single letters clearer w3c/unicode-xml#19, by @duerst.
-
-
1 issue closed.
-
Use of <i> in example w3c/unicode-xml#15.
-
-
2 issues received 2 new comments.
-
Make reason for often using characters (and not styling) for single letters clearer w3c/unicode-xml#19 (1 comment by @r12a)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 March 2018.
-
Participants
-
1 participant joined.
-
Addison Phillips (W3C Invited Experts) joined.
-
-
1 participant left.
-
Addison Phillips (W3C Invited Experts) left.
-
-
1 organization joined.
-
360 joined.
-
GitHub
w3c/i18n-drafts
-
10 issues opened.
-
Feedback on questions/qa-css-lang w3c/i18n-drafts#28, by @ntounsi.
-
[articles/inline-bidi-markup/index] w3c/i18n-drafts#27, by @nickshanks.
-
[questions/qa-escapes] Various things in ‘Use in XHTML’ section w3c/i18n-drafts#25, by @gunnarbittersmann.
-
[questions/qa-chars-vs-markup] missing dates in footer w3c/i18n-drafts#24, by @gunnarbittersmann.
-
[questions/site-conneg] example .var file w3c/i18n-drafts#23, by @gunnarbittersmann.
-
[questions/site-conneg] Note that localStorage requires JavaScript? w3c/i18n-drafts#22, by @gunnarbittersmann.
-
[questions/site-conneg] MultiViews in camel case w3c/i18n-drafts#21, by @gunnarbittersmann.
-
[questions/site-conneg] Arabic script w3c/i18n-drafts#20, by @gunnarbittersmann.
-
[questions/site-conneg] Make URIs consistent w3c/i18n-drafts#19, by @gunnarbittersmann.
-
-
13 issues closed.
-
[articles/inline-bidi-markup/index] w3c/i18n-drafts#27.
-
test w3c/i18n-drafts#26.
-
Feedback on questions/qa-date-format - Promoting YYYY-0MM-DD w3c/i18n-drafts#5.
-
Complete questions/site-conneg w3c/i18n-drafts#6.
-
[questions/qa-escapes] Various things in ‘Use in XHTML’ section w3c/i18n-drafts#25.
-
[questions/qa-chars-vs-markup] missing dates in footer w3c/i18n-drafts#24.
-
[questions/qa-ruby] Update needed w3c/i18n-drafts#8.
-
[questions/qa-who-uses-unicode] Update needed w3c/i18n-drafts#9.
-
[questions/site-conneg] example .var file w3c/i18n-drafts#23.
-
[questions/site-conneg] Note that localStorage requires JavaScript? w3c/i18n-drafts#22.
-
[questions/site-conneg] MultiViews in camel case w3c/i18n-drafts#21.
-
[questions/site-conneg] Arabic script w3c/i18n-drafts#20.
-
[questions/site-conneg] Make URIs consistent w3c/i18n-drafts#19.
-
-
13 issues received 15 new comments.
-
[questions/qa-escapes] Various things in ‘Use in XHTML’ section w3c/i18n-drafts#25 (1 comment by @r12a)
-
[questions/site-conneg] Note that localStorage requires JavaScript? w3c/i18n-drafts#22 (1 comment by @r12a)
-
6 pull requests opened.
-
qa-escapes.de w3c/i18n-drafts#34, by @gunnarbittersmann.
-
qa-escapes.de updated German translation w3c/i18n-drafts#33, by @gunnarbittersmann.
-
Translation contributor credits w3c/i18n-drafts#32, by @gunnarbittersmann.
-
qa-escapes w3c/i18n-drafts#31, by @gunnarbittersmann.
-
boilerplate de w3c/i18n-drafts#30, by @gunnarbittersmann.
-
qa-chars-vs-markup de/pl, qa-site-conneg en/sv minor corrections w3c/i18n-drafts#29, by @gunnarbittersmann.
-
-
1 pull request merged.
-
qa-escapes.de updated German translation w3c/i18n-drafts#33.
-
-
4 pull requests closed.
-
qa-escapes.de w3c/i18n-drafts#34.
-
qa-chars-vs-markup de/pl, qa-site-conneg en/sv minor corrections w3c/i18n-drafts#29.
-
boilerplate de w3c/i18n-drafts#30.
-
qa-escapes w3c/i18n-drafts#31.
-
-
5 pull requests received 5 new comments.
-
qa-chars-vs-markup de/pl, qa-site-conneg en/sv minor corrections w3c/i18n-drafts#29 (1 comment by @r12a)
w3c/unicode-xml
-
18 issues opened.
-
Editorial comments wrt XHTML w3c/unicode-xml#18, by @r12a.
-
HTML5 reference needed w3c/unicode-xml#17, by @r12a.
-
Author vs implementer guidelines w3c/unicode-xml#16, by @r12a.
-
Use of <i> in example w3c/unicode-xml#15, by @r12a.
-
Style properties for tate-chu-yoko w3c/unicode-xml#14, by @r12a.
-
Characters with Compatibility Mappings w3c/unicode-xml#13, by @r12a.
-
Format Characters Suitable for Use with Markup w3c/unicode-xml#12, by @r12a.
-
Preferred alternate encoding may be substituted w3c/unicode-xml#11, by @r12a.
-
Language tag characters and BCP 47 w3c/unicode-xml#10, by @r12a.
-
Reference to ruby model w3c/unicode-xml#9, by @r12a.
-
Update the BOM section w3c/unicode-xml#8, by @r12a.
-
Automatic removal of characters by browsers w3c/unicode-xml#7, by @r12a.
-
Note about bidi markup and CSS versions w3c/unicode-xml#6, by @r12a.
-
'Going beyond HTML for bidi' needs modification w3c/unicode-xml#5, by @r12a.
-
Bidi controls need to reflect isolation changes in Unicode and HTML5 w3c/unicode-xml#4, by @r12a.
-
Line / paragraph separators in pre, textarea, etc w3c/unicode-xml#3, by @r12a.
-
Characters not suitable for use with markup w3c/unicode-xml#2, by @r12a.
-
General Considerations gets in the way w3c/unicode-xml#1, by @r12a.
-
-
5 issues received 6 new comments.
w3c/i18n-activity
-
113 issues opened.
-
Consider removing TextEncoder support for UTF-16 w3c/i18n-activity#116, by @r12a.
-
Possibility for a character to be interpreted differently depending on locale w3c/i18n-activity#114, by @r12a.
-
list of displays: should it address display name, language, etc.? w3c/i18n-activity#113, by @r12a.
-
i18n-ISSUE-493: add sections (non-I18N) w3c/i18n-activity#112, by @r12a.
-
i18n-ISSUE-505: intro discussion of diacritic matching w3c/i18n-activity#111, by @r12a.
-
i18n-ISSUE-504: ascii case fold not useful w3c/i18n-activity#110, by @r12a.
-
i18n-ISSUE-503: order of case fold and normalization operations w3c/i18n-activity#109, by @r12a.
-
i18n-ISSUE-502: Unicode equivalent type all not clear w3c/i18n-activity#108, by @r12a.
-
i18n-ISSUE-501: Unicode equivalence type non-specificity w3c/i18n-activity#107, by @r12a.
-
FindText API vs. Charmod-Norm w3c/i18n-activity#106, by @r12a.
-
definitions of ASCII and Unicode case folds w3c/i18n-activity#105, by @r12a.
-
language-sensitive case fold type needs more information w3c/i18n-activity#104, by @r12a.
-
avoid listing whitespace characters w3c/i18n-activity#103, by @r12a.
-
note about character counts w3c/i18n-activity#102, by @r12a.
-
note about legacy encodings such as windows-1252 is invalid w3c/i18n-activity#101, by @r12a.
-
i18n-ISSUE-492: Honor the HTTP Accept-Language header for selecting the consent language w3c/i18n-activity#100, by @r12a.
-
i18n-ISSUE-491: Change collapse to merge for ruby-merge w3c/i18n-activity#99, by @r12a.
-
i18n-ISSUE-359: Drop ruby-merge in favour of a specific jukugo value w3c/i18n-activity#98, by @r12a.
-
Control Characters Roll Call on implementation w3c/i18n-activity#97, by @r12a.
-
what a whitespace character is w3c/i18n-activity#96, by @r12a.
-
Justifying Korean text w3c/i18n-activity#95, by @r12a.
-
Arabic letters connecting between elements with display: inline w3c/i18n-activity#94, by @r12a.
-
i18n-ISSUE-354: Questions about letter-spacing for Arabic script w3c/i18n-activity#93, by @r12a.
-
i18n-ISSUE-334: 'letter-spacing' and Indic w3c/i18n-activity#92, by @r12a.
-
i18n-ISSUE-316: Line breaking defaults w3c/i18n-activity#91, by @r12a.
-
i18n-ISSUE-487: Consider adding a language tag to indicate the language of an error message w3c/i18n-activity#90, by @r12a.
-
i18n-ISSUE-486: Should units of speed vary in the specification w3c/i18n-activity#89, by @r12a.
-
i18n-ISSUE-485: Inconsistent use of data type for tilts and pans w3c/i18n-activity#88, by @r12a.
-
i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages w3c/i18n-activity#87, by @r12a.
-
i18n-ISSUE-483: Temperature data type for Temperature Interface uses different data types w3c/i18n-activity#86, by @r12a.
-
i18n-ISSUE-482: Inconsistent data type for levels w3c/i18n-activity#85, by @r12a.
-
i18n-ISSUE-481: Inconsistent data type for temperatures w3c/i18n-activity#84, by @r12a.
-
i18n-ISSUE-480: New role for Ruby? w3c/i18n-activity#83, by @r12a.
-
i18n-ISSUE-476: International payment, taxation, delivery and trade restriction practices w3c/i18n-activity#82, by @r12a.
-
i18n-ISSUE-472: geographic variation of terms or availability w3c/i18n-activity#81, by @r12a.
-
i18n-ISSUE-471: identify time zone dependent vs. independent cases w3c/i18n-activity#80, by @r12a.
-
i18n-ISSUE-465: Human readable message not localizable? w3c/i18n-activity#79, by @r12a.
-
i18n-ISSUE-464: 'label' needs direction and language metadata w3c/i18n-activity#78, by @r12a.
-
i18n-ISSUE-459: 2.1.7 privacy issues w3c/i18n-activity#77, by @r12a.
-
i18n-ISSUE-458: 2.1.3 general observation about language identification w3c/i18n-activity#76, by @r12a.
-
i18n-ISSUE-457: 2.1.1 Comment on title or on publication? w3c/i18n-activity#75, by @r12a.
-
i18n-ISSUE-456: 2.1.1 provide a terminology section? [non-I18N] w3c/i18n-activity#74, by @r12a.
-
i18n-ISSUE-433: (editorial nit) spec title w3c/i18n-activity#73, by @r12a.
-
i18n-ISSUE-417: appropriate use of ACI w3c/i18n-activity#72, by @r12a.
-
i18n-ISSUE-416: No direction metadata for 'name' w3c/i18n-activity#71, by @r12a.
-
i18n-ISSUE-415: No language metadata for 'name' w3c/i18n-activity#70, by @r12a.
-
i18n-ISSUE-414: No means of obtaining correctly localized manifest w3c/i18n-activity#69, by @r12a.
-
i18n-ISSUE-413: No localized examples w3c/i18n-activity#68, by @r12a.
-
i18n-ISSUE-412: No localization model w3c/i18n-activity#67, by @r12a.
-
i18n-ISSUE-411: Definition of whitespace should come from Unicode w3c/i18n-activity#66, by @r12a.
-
i18n-ISSUE-410: Language tags should reference BCP 47 w3c/i18n-activity#65, by @r12a.
-
i18n-ISSUE-409: What are the string matching rules in the delete operation w3c/i18n-activity#64, by @r12a.
-
i18n-ISSUE-408: Boxed characters and initial letter properties w3c/i18n-activity#63, by @r12a.
-
i18n-ISSUE-405: clarify embedded image vs. character (editorial) w3c/i18n-activity#62, by @r12a.
-
i18n-ISSUE-397: Interaction of variation selectors and proposed emoji modifiers w3c/i18n-activity#61, by @r12a.
-
i18n-ISSUE-404: Lang matching undefined w3c/i18n-activity#60, by @r12a.
-
i18n-ISSUE-403: Reference to language tag should be to BCP47 w3c/i18n-activity#59, by @r12a.
-
i18n-ISSUE-402: Broken copy/paste behavior with IRIs w3c/i18n-activity#58, by @r12a.
-
Standardizing on IDNA 2003 in the URL Standard w3c/i18n-activity#57, by @r12a.
-
i18n-ISSUE-400: collation lang processing should refer to BCP47 w3c/i18n-activity#56, by @r12a.
-
i18n-ISSUE-399: Provide Guidance on Collation Tailorings w3c/i18n-activity#55, by @r12a.
-
i18n-ISSUE-398: Defining Decimal Formats Permits Only Single Characters w3c/i18n-activity#54, by @r12a.
-
i18n-ISSUE-396: character maps needs a string? w3c/i18n-activity#53, by @r12a.
-
URI developments w3c/i18n-activity#52, by @r12a.
-
i18n-ISSUE-394: decimal-format reference CLDR? w3c/i18n-activity#51, by @r12a.
-
i18n-ISSUE-393: zero-digit replacement? w3c/i18n-activity#50, by @r12a.
-
i18n-ISSUE-392: Decimal Format incomplete? w3c/i18n-activity#49, by @r12a.
-
test issue w3c/i18n-activity#48, by @fizmer.
-
What Latin means w3c/i18n-activity#47, by @r12a.
-
i18n-ISSUE-391: Quotation Marks are Different in Other Languages w3c/i18n-activity#46, by @r12a.
-
i18n-ISSUE-388: Add explicit text about direction's relationship to 'start' and 'end' keywords w3c/i18n-activity#45, by @r12a.
-
i18n-ISSUE-389: English should be given as an example (editorial) w3c/i18n-activity#44, by @r12a.
-
i18n-ISSUE-387: AS2.0: Section 3.2: language example issues w3c/i18n-activity#43, by @r12a.
-
Content language, not document language w3c/i18n-activity#42, by @r12a.
-
i18n-ISSUE-353: Section 2.1 case sensitivity and normalization w3c/i18n-activity#41, by @r12a.
-
i18n-ISSUE-352: normalization of custom property names w3c/i18n-activity#40, by @r12a.
-
i18n-ISSUE-351: Section 6.4.2: restriction to "URI-safe characters" w3c/i18n-activity#39, by @r12a.
-
i18n-ISSUE-350: IRI/non-ASCII not permitted in w3c/i18n-activity#38, by @r12a.
-
i18n-ISSUE-349: Section title for 6.2.7 doesn't match earlier description w3c/i18n-activity#37, by @r12a.
-
i18n-ISSUE-348: Non-ASCII not permitted in extensions w3c/i18n-activity#36, by @r12a.
-
i18n-ISSUE-347: Section 5.2: DNT-extension excludes should spell out control, space, double quote. w3c/i18n-activity#35, by @r12a.
-
i18n-ISSUE-346: Section 5.2 use of %31 and %30 for characters 1 and 0 w3c/i18n-activity#34, by @r12a.
-
i18n-ISSUE-343: Type attribute on ol w3c/i18n-activity#33, by @r12a.
-
i18n-ISSUE-139: Multilingual q nesting w3c/i18n-activity#32, by @r12a.
-
i18n-ISSUE-341: [css3-background] border-left-* and border-right-* w3c/i18n-activity#31, by @r12a.
-
i18n-ISSUE-340: [css3-background] Lack of "start" and "end" keywords w3c/i18n-activity#30, by @r12a.
-
i18n-ISSUE-519: Table of contents does not display properly in Safari browser w3c/i18n-activity#29, by @r12a.
-
i18n-ISSUE-518: Need to explain name matching rules for cache names w3c/i18n-activity#28, by @r12a.
-
Make unicode-bidi: isolate the default for elements with a dir attribute (mozilla) w3c/i18n-activity#26, by @r12a.
-
Halfwidth characters incorrectly rendered in Chrome w3c/i18n-activity#24, by @r12a.
-
Emphasis marks and combining characters w3c/i18n-activity#23, by @r12a.
-
i18n-ISSUE-249: positioning of ruby and emphasis marks together w3c/i18n-activity#22, by @r12a.
-
i18n-ISSUE-248: terminology related to spaces w3c/i18n-activity#21, by @r12a.
-
[css3-text] text-underline-position for Mongolian w3c/i18n-activity#20, by @r12a.
-
Mention the need for metadata in multiple human languages w3c/i18n-activity#19, by @r12a.
-
Roll-up regions and ruby incompatible? #250 w3c/i18n-activity#18, by @r12a.
-
Support character escapes in classes (<c.foo&bar>) #251 w3c/i18n-activity#17, by @r12a.
-
Expose the fallback language in the API #258 w3c/i18n-activity#16, by @r12a.
-
Consider adding 'ruby-align' as a supported CSS property #265 w3c/i18n-activity#15, by @r12a.
-
i18n-ISSUE-507: WebVTT alignment cue setting keywords #262 w3c/i18n-activity#14, by @r12a.
-
i18n-ISSUE-436: 6.2.1 line heights w3c/i18n-activity#13, by @r12a.
-
i18n-ISSUE-435: 3.2 scroll value and vertical writing w3c/i18n-activity#12, by @r12a.
-
i18n-ISSUE-434: 3.1 Line wrapping for non-Latin scripts w3c/i18n-activity#11, by @r12a.
-
i18n-ISSUE-432: 6.2.1 processing model handling of bidi w3c/i18n-activity#10, by @r12a.
-
i18n-ISSUE-431: ruby model incomplete w3c/i18n-activity#9, by @r12a.
-
i18n-ISSUE-429: "valid" language tag w3c/i18n-activity#8, by @r12a.
-
i18n-ISSUE-428: 4.3.2 emphasis spans w3c/i18n-activity#7, by @r12a.
-
i18n-ISSUE-424: More formal grammar? w3c/i18n-activity#6, by @r12a.
-
i18n-ISSUE-422: start/end linked to left/right w3c/i18n-activity#5, by @r12a.
-
i18n-ISSUE-420: no provision for indicating overall content language(s) w3c/i18n-activity#4, by @r12a.
-
-
7 issues closed.
-
i18n-ISSUE-397: Interaction of variation selectors and proposed emoji modifiers w3c/i18n-activity#61.
-
i18n-ISSUE-456: 2.1.1 provide a terminology section? [non-I18N] w3c/i18n-activity#74.
-
note about legacy encodings such as windows-1252 is invalid w3c/i18n-activity#101.
-
note about character counts w3c/i18n-activity#102.
-
i18n-ISSUE-433: (editorial nit) spec title w3c/i18n-activity#73.
-
n/a w3c/i18n-activity#115.
-
test issue w3c/i18n-activity#48.
-
-
19 issues received 20 new comments.
-
i18n-ISSUE-433: (editorial nit) spec title w3c/i18n-activity#73 (2 comments by @aphillips, @marcoscaceres)
-
i18n-ISSUE-397: Interaction of variation selectors and proposed emoji modifiers w3c/i18n-activity#61 (1 comment by @aphillips)
-
i18n-ISSUE-456: 2.1.1 provide a terminology section? [non-I18N] w3c/i18n-activity#74 (1 comment by @aphillips)
-
note about legacy encodings such as windows-1252 is invalid w3c/i18n-activity#101 (1 comment by @aphillips)
-
i18n-ISSUE-414: No means of obtaining correctly localized manifest w3c/i18n-activity#69 (1 comment by @marcoscaceres)
-
Make unicode-bidi: isolate the default for elements with a dir attribute (mozilla) w3c/i18n-activity#26 (1 comment by @r12a)
-
i18n-ISSUE-507: WebVTT alignment cue setting keywords #262 w3c/i18n-activity#14 (1 comment by @r12a)
-
-
1 pull request received 2 new comments.
w3c/alreq
-
1 issue opened.
-
Drafting questions w3c/alreq#38, by @r12a.
-
-
5 issues received 11 new comments.
-
5 pull requests opened.
-
Add gitignore w3c/alreq#41, by @mostafah.
-
Initial text for the direction section w3c/alreq#40, by @mostafah.
-
first draft of questions w3c/alreq#39, by @r12a.
-
Add initial draft of characters tables w3c/alreq#37, by @mostafah.
-
Add script for generating character tables w3c/alreq#36, by @mostafah.
-
-
5 pull requests merged.
-
Add gitignore w3c/alreq#41.
-
Initial text for the direction section w3c/alreq#40.
-
first draft of questions w3c/alreq#39.
-
Add script for generating character tables w3c/alreq#36.
-
Add initial draft of characters tables w3c/alreq#37.
-
-
1 pull request received 1 new comment.
w3c/charmod-norm
-
1 issue opened.
-
table widths w3c/charmod-norm#81, by @r12a.
-
-
1 issue received 2 new comments.
Participants
-
1 organization left.
-
X left.
-
GitHub
w3c/i18n-drafts
-
9 issues opened.
-
[articles/ruby/index] Editorial suggestions w3c/i18n-drafts#18, by @r12a.
-
[questions/qa-bidi-space] w3c/i18n-drafts#17, by @aphillips.
-
[articles/ruby/index] w3c/i18n-drafts#16, by @dyacob.
-
[articles/ruby/index] The example of pinyin ruby w3c/i18n-drafts#15, by @upsuper.
-
[articles/ruby/index] "alongside" incorrect w3c/i18n-drafts#14, by @aphillips.
-
[articles/ruby/index] w3c/i18n-drafts#13, by @arlelommel.
-
[questions/qa-choosing-encodings] warning about PUA and Shift_JIS and GB18030 w3c/i18n-drafts#12, by @r12a.
-
[questions/qa-resizing-backgrounds] update needed w3c/i18n-drafts#11, by @r12a.
-
[articles/ruby] do something about TR/ruby? w3c/i18n-drafts#10, by @aphillips.
-
-
6 issues closed.
-
[questions/qa-bidi-space] w3c/i18n-drafts#17.
-
[articles/ruby/index] Editorial suggestions w3c/i18n-drafts#18.
-
[articles/ruby/index] w3c/i18n-drafts#16.
-
[articles/ruby/index] The example of pinyin ruby w3c/i18n-drafts#15.
-
[articles/ruby/index] w3c/i18n-drafts#13.
-
[articles/ruby/index] "alongside" incorrect w3c/i18n-drafts#14.
-
-
7 issues received 11 new comments.
-
Feedback on questions/qa-date-format - Promoting YYYY-0MM-DD w3c/i18n-drafts#5 (2 comments by @duerst, @dyacob)
w3c/alreq
-
1 issue closed.
-
Which transliteration schemes should we use? w3c/alreq#16.
-
-
3 issues received 5 new comments.
-
2 pull requests opened.
-
Adding RTL cell direction to CSS w3c/alreq#35, by @shervinafshar.
-
Updating the script for generating glossary table w3c/alreq#34, by @shervinafshar.
-
-
2 pull requests merged.
-
[Arabic Script Overview] Add sub-section Encoding w3c/alreq#30.
-
Updating the script for generating glossary table w3c/alreq#34.
-
-
1 pull request closed.
-
Adding RTL cell direction to CSS w3c/alreq#35.
-
w3c/charmod-norm
-
17 issues opened.
-
Arabic & Hebrew unique issues associated with sections 2.4 and 2.5 w3c/charmod-norm#80, by @tomerm.
-
Arabic short vowels and Hebrew pointing in string search w3c/charmod-norm#78, by @aphillips.
-
2.2.1 Canonical vs. Compatibility Equivalence vs Canonical non-equivalence w3c/charmod-norm#69, by @klensin.
-
Case Folding (Section 2.1) - Sharp S example w3c/charmod-norm#68, by @klensin.
-
Case Folding introduction (Section 2.1) w3c/charmod-norm#67, by @klensin.
-
String matching problem (Section 2 introduction) -- types of operations w3c/charmod-norm#65, by @klensin.
-
Section 2 introduction w3c/charmod-norm#64, by @klensin.
-
Conformance (Section 1.5) and RFC 2119 w3c/charmod-norm#63, by @klensin.
-
Terminology example(s) (Section 1.4.1 of 2016-02-01 Editor's version, former Example 3) w3c/charmod-norm#62, by @klensin.
-
Section number references to Unicode Standard w3c/charmod-norm#61, by @klensin.
-
Definition of "vocabulary", Section 1.2 w3c/charmod-norm#60, by @klensin.
-
Definition of "resource" (section 1.4) w3c/charmod-norm#59, by @klensin.
-
Definition of "natural language content' (Section 1.4) w3c/charmod-norm#58, by @klensin.
-
XML use of DTD (Section 1.4, Example 1 in 2016-02-01 Editor's version) w3c/charmod-norm#57, by @klensin.
-
Definition of "Syntactic content" (section 1.4) w3c/charmod-norm#56, by @klensin.
-
Definition of "transcoder" w3c/charmod-norm#55, by @klensin.
-
Do we need to discuss regular expressions? w3c/charmod-norm#54, by @aphillips.
-
-
6 issues closed.
-
Case Folding introduction (Section 2.1) w3c/charmod-norm#67.
-
Case Folding (Section 2.1) - Sharp S example w3c/charmod-norm#68.
-
Definition of "transcoder" w3c/charmod-norm#55.
-
Conformance (Section 1.5) and RFC 2119 w3c/charmod-norm#63.
-
fix requirement C5 (from [I18N-ACTION-487]) w3c/charmod-norm#49.
-
-
17 issues received 39 new comments.
-
Case Folding (Section 2.1) - Sharp S example w3c/charmod-norm#68 (7 comments by @aphillips, @asmusf, @duerst, @klensin)
-
2.2.1 Canonical vs. Compatibility Equivalence vs Canonical non-equivalence w3c/charmod-norm#69 (5 comments by @aphillips, @asmusf)
-
Case Folding introduction (Section 2.1) w3c/charmod-norm#67 (5 comments by @aphillips, @asmusf, @duerst)
-
Arabic short vowels and Hebrew pointing in string search w3c/charmod-norm#78 (3 comments by @aphillips, @asmusf)
-
Arabic & Hebrew unique issues associated with sections 2.4 and 2.5 w3c/charmod-norm#80 (2 comments by @duerst, @tomerm)
-
String matching problem (Section 2 introduction) -- types of operations w3c/charmod-norm#65 (1 comment by @aphillips)
-
Terminology example(s) (Section 1.4.1 of 2016-02-01 Editor's version, former Example 3) w3c/charmod-norm#62 (1 comment by @aphillips)
-
Definition of "natural language content' (Section 1.4) w3c/charmod-norm#58 (1 comment by @aphillips)
-
XML use of DTD (Section 1.4, Example 1 in 2016-02-01 Editor's version) w3c/charmod-norm#57 (1 comment by @aphillips)
-
-
11 pull requests opened.
-
Issue #65: introduction/problem statement w3c/charmod-norm#79, by @aphillips.
-
Issue #67: Fixed typo and or->and w3c/charmod-norm#77, by @aphillips.
-
Issue #68: Address locale vs. language w3c/charmod-norm#76, by @aphillips.
-
Issue#69: Added new document section. w3c/charmod-norm#75, by @aphillips.
-
Issue #69: Added discussion of confusables and limits of normalization. w3c/charmod-norm#74, by @aphillips.
-
Issue #55: remove definition of 'code unit' and update w3c/charmod-norm#73, by @aphillips.
-
Addressed Issues 61-63. w3c/charmod-norm#72, by @aphillips.
-
Added 'issue' boxes for unaddressed issues of John's through #60. w3c/charmod-norm#71, by @aphillips.
-
Additional commits in response to JcK's comments. See inner commit messages. w3c/charmod-norm#70, by @aphillips.
-
Addressed two issues (see commits) from JcK w3c/charmod-norm#66, by @aphillips.
-
Fixed trancoders definition so ReSpec links it automagically. w3c/charmod-norm#53, by @aphillips.
-
-
11 pull requests merged.
-
Issue #65: introduction/problem statement w3c/charmod-norm#79.
-
Issue #67: Fixed typo and or->and w3c/charmod-norm#77.
-
Issue #68: Address locale vs. language w3c/charmod-norm#76.
-
Issue#69: Added new document section. w3c/charmod-norm#75.
-
Issue #69: Added discussion of confusables and limits of normalization. w3c/charmod-norm#74.
-
Issue #55: remove definition of 'code unit' and update w3c/charmod-norm#73.
-
Addressed Issues 61-63. w3c/charmod-norm#72.
-
Added 'issue' boxes for unaddressed issues of John's through #60. w3c/charmod-norm#71.
-
Additional commits in response to JcK's comments. See inner commit messages. w3c/charmod-norm#70.
-
Addressed two issues (see commits) from JcK w3c/charmod-norm#66.
-
Fixed trancoders definition so ReSpec links it automagically. w3c/charmod-norm#53.
-
w3c/clreq
-
1 issue opened.
-
typeface sample pic uses bold w3c/clreq#97, by @dine2014.
-
-
1 issue closed.
-
typeface sample pic uses bold w3c/clreq#97.
-
-
1 issue received 1 new comment.
w3c/i18n-activity
-
1 pull request opened.
-
Enhancing color contrast for headings w3c/i18n-activity#3, by @yatil.
-
GitHub
w3c/i18n-drafts
-
9 issues opened.
-
[questions/qa-who-uses-unicode] Update needed w3c/i18n-drafts#9, by @r12a.
-
[questions/qa-ruby] Update needed w3c/i18n-drafts#8, by @r12a.
-
[questions/qa-date-format] add info about html5 date markup w3c/i18n-drafts#7, by @r12a.
-
Complete questions/site-conneg w3c/i18n-drafts#6, by @r12a.
-
Feedback on questions/qa-date-format - Promoting YYYY-0MM-DD w3c/i18n-drafts#5, by @FBTHFL.
-
Complete "Authoring HTML with bidi localization in mind" w3c/i18n-drafts#4, by @r12a.
-
Feedback on questions/qa-display-capabilities w3c/i18n-drafts#3, by @r12a.
-
Feedback on language-decl/index w3c/i18n-drafts#2, by @fizmer.
-
Feedback on vertical-text w3c/i18n-drafts#1, by @r12a.
-
-
2 issues closed.
-
Feedback on language-decl/index w3c/i18n-drafts#2.
-
Feedback on vertical-text w3c/i18n-drafts#1.
-
-
1 issue received 2 new comments.
-
Feedback on questions/qa-date-format - Promoting YYYY-0MM-DD w3c/i18n-drafts#5 (2 comments by @arlelommel, @r12a)
-
w3c/charmod-norm
-
3 issues opened.
-
fix stylesheet and figure styling from I18N-ACTION-488 w3c/charmod-norm#50, by @aphillips.
-
fix requirement C5 (from [I18N-ACTION-487]) w3c/charmod-norm#49, by @aphillips.
-
Does ZWJ/ZWNJ affect meaning? w3c/charmod-norm#44, by @r12a.
-
-
1 issue closed.
-
fix stylesheet and figure styling from I18N-ACTION-488 w3c/charmod-norm#50.
-
-
2 issues received 11 new comments.
-
Does ZWJ/ZWNJ affect meaning? w3c/charmod-norm#44 (10 comments by @aphillips, @behdad, @duerst, @ebraminio, @johnwcowan, @Ladsgroup)
-
fix stylesheet and figure styling from I18N-ACTION-488 w3c/charmod-norm#50 (1 comment by @aphillips)
-
-
9 pull requests opened.
-
I18N-ACTION-487: Remove Requirement C5 "Normalizing Transcoders" w3c/charmod-norm#52, by @aphillips.
-
Address Issue#50. Restyled tables to use new stylesheet. w3c/charmod-norm#51, by @aphillips.
-
Fixed section 3.2.2 demo per editorial comment now removed. w3c/charmod-norm#48, by @aphillips.
-
Fixed problems with terminology illustration due to new styles. Updat… w3c/charmod-norm#47, by @aphillips.
-
Egregious English grammatical error? I fixed it. w3c/charmod-norm#46, by @aphillips.
-
Changes to Section 2.4 based on discussion of issue #44 w3c/charmod-norm#45, by @aphillips.
-
Fix the ReSpec problem by RTFM and adjusting the dfns. Moved the tran… w3c/charmod-norm#43, by @aphillips.
-
Additional edits related to normalization requirements. w3c/charmod-norm#42, by @aphillips.
-
Implemented changes from WG teleconference of 2016-01-07. w3c/charmod-norm#41, by @aphillips.
-
-
9 pull requests merged.
-
I18N-ACTION-487: Remove Requirement C5 "Normalizing Transcoders" w3c/charmod-norm#52.
-
Address Issue#50. Restyled tables to use new stylesheet. w3c/charmod-norm#51.
-
Fixed section 3.2.2 demo per editorial comment now removed. w3c/charmod-norm#48.
-
Fixed problems with terminology illustration due to new styles. Updat… w3c/charmod-norm#47.
-
Egregious English grammatical error? I fixed it. w3c/charmod-norm#46.
-
Changes to Section 2.4 based on discussion of issue #44 w3c/charmod-norm#45.
-
Fix the ReSpec problem by RTFM and adjusting the dfns. Moved the tran… w3c/charmod-norm#43.
-
Additional edits related to normalization requirements. w3c/charmod-norm#42.
-
Implemented changes from WG teleconference of 2016-01-07. w3c/charmod-norm#41.
-
w3c/alreq
-
4 issues opened.
-
Deprecated Arabic presentation forms considered helpful w3c/alreq#32, by @ntounsi.
-
Building exemplar charts w3c/alreq#31, by @mostafah.
-
[section] List alignment and directions w3c/alreq#29, by @behnam.
-
Drafting “direction” w3c/alreq#28, by @mostafah.
-
-
2 issues closed.
-
"Font and typographical considerations" Draft w3c/alreq#15.
-
How to handle transcriptions in the glossary w3c/alreq#21.
-
-
8 issues received 9 new comments.
-
It should be possible to style a single character without breaking Arabic joining w3c/alreq#4 (1 comment by @behnam)
-
5 pull requests opened.
-
New section on Font and typographical considerations w3c/alreq#33, by @ntounsi.
-
[Arabic Script Overview] Add sub-section Encoding w3c/alreq#30, by @behnam.
-
Fix mistaken text in the list in a previous PR w3c/alreq#27, by @mostafah.
-
Replace literal quotes with spans w3c/alreq#26, by @mostafah.
-
ACTION-29: Processing the glossary for the draft w3c/alreq#25, by @shervinafshar.
-
-
3 pull requests merged.
-
Replace literal quotes with spans w3c/alreq#26.
-
Fix mistaken text in the list in a previous PR w3c/alreq#27.
-
ACTION-29: Processing the glossary for the draft w3c/alreq#25.
-
-
1 pull request reopened.
-
New section on Font and typographical considerations w3c/alreq#33, by @ntounsi.
-
w3c/i18n-activity
-
2 pull requests opened.
-
Update CSS/JS links to HTTPS w3c/i18n-activity#2, by @behnam.
-
Minor fixes to charter text, and remaining issues w3c/i18n-activity#1, by @duerst.
-
-
1 pull request merged.
-
Minor fixes to charter text, and remaining issues w3c/i18n-activity#1.
-
-
1 pull request closed.
-
Update CSS/JS links to HTTPS w3c/i18n-activity#2.
-
-
1 pull request received 4 new comments.
-
Minor fixes to charter text, and remaining issues w3c/i18n-activity#1 (4 comments by @duerst, @r12a)
-