Saturday, 26 December 2015
Thursday, 17 December 2015
Tuesday, 15 December 2015
Thursday, 10 December 2015
Thursday, 3 December 2015
Monday, 23 November 2015
Thursday, 19 November 2015
- I18N-ACTION-483: Review close marked webvtt issues and close if satisfied
- I18N-ACTION-482: Follow up with david s. to get name for repo and set up said repo
- I18N-ISSUE-512: Mention the need for metadata in multiple human languages â?? [data-on-web-best-practices]
Monday, 16 November 2015
- I18N-ISSUE-511: Roll-up regions and ruby incompatible? #250 â?£ [webvtt1]
- I18N-ISSUE-510: Support character escapes in classes (<c.foo&bar>) #251 â?£ [webvtt1]
- I18N-ISSUE-509: Expose the fallback language in the API #258 â?£ [webvtt1]
- I18N-ISSUE-508: Consider adding 'ruby-align' as a supported CSS property #265 â?£ [webvtt1]
- I18N-ISSUE-507: WebVTT alignment cue setting keywords #262 [webvtt1]
Thursday, 12 November 2015
- I18N-ACTION-481: Respond to presentation-api issue 506 with discussed set of comments
- I18N-ACTION-480: Write back to timed text and note that we've reviewed their charter
Tuesday, 10 November 2015
Monday, 9 November 2015
Thursday, 5 November 2015
Tuesday, 3 November 2015
Thursday, 29 October 2015
- Re: [XSLT30] collection lang processing should refer to BCP47 [I18N-ISSUE-400][I18N-ACTION-467]
- [Bug 27615] [XSLT30] Should decimal-format reference CLDR? [I18N-ISSUE-394]
Thursday, 22 October 2015
- Re: I18N-ISSUE-505: intro discussion of diacritic matching [find-text]
- I18N-ISSUE-505: intro discussion of diacritic matching [find-text]
- I18N-ISSUE-504: ascii case fold not useful [find-text]
Wednesday, 21 October 2015
- Comment(s) on "Data on the Web Best Practices" draft
- On "Solicit input from xliff, its, bpmlod about json/plain text i18n metadata"
- CANCELED [Was: Call for Exclusions: Internationalization Best Practices for Spec Developers]
Tuesday, 20 October 2015
- Call for Exclusions: Internationalization Best Practices for Spec Developers
- Call for Exclusions: Encoding
Friday, 16 October 2015
- I18N-ISSUE-503: order of case fold and normalization operations â?? [find-text]
- I18N-ISSUE-502: Unicode equivalent type all not clear â?? [find-text]
- I18N-ISSUE-501: Unicode equivalence type non-specificity â?? [find-text]
- I18N-ISSUE-500: FindText API vs. Charmod-Norm â?? [find-text]
- I18N-ISSUE-499: definitions of ASCII and Unicode case folds â?? [find-text]
- I18N-ISSUE-498: language-sensitive case fold type needs more information â?? [find-text]
Thursday, 15 October 2015
- I18N-ISSUE-497: avoid listing whitespace characters â?? [find-text]
- I18N-ISSUE-496: note about character counts â?? [find-text]
- I18N-ISSUE-495: note about windows-1252 is invalid â?? [find-text]
- I18N-ISSUE-494: list of displays: should it address display name, language, etc.? â?? [presentation-api]
- I18N-ISSUE-493: add sections (non-I18N) [presentation-api]
- I18N-ACTION-478: Solicit input from xliff, its, bpmlod about json/plain text i18n metadata
- I18N-ACTION-477: Add i18n metadata for json to list of projects
- I18N-ACTION-476: Write back to media capture saying that we'll continue to work on problem but they can publish in the meantime
- I18N-ACTION-475: Close writing-mode issues unless final comments are received beforehand
- Re: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- Re: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
Wednesday, 14 October 2015
- RE: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- Re: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
Monday, 12 October 2015
- RE: [DPUB-ANNOTATION-UC] Annotations for accessibility use case
- Re: [DPUB-ANNOTATION-UC] Annotations for accessibility use case
Sunday, 11 October 2015
- RE: [DPUB-ANNOTATION-UC] Annotations for accessibility use case
- RE: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- Re: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- Re: [DPUB-ANNOTATION-UC] Annotations for accessibility use case
- RE: [DPUB-ANNOTATION-UC] Comment on title or on publication? [I18N-ISSUE-457]
- RE: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- RE: [DPUB-ANNOTATION-UC] Annotations for accessibility use case
- Re: [DPUB-ANNOTATION-UC] Annotations for accessibility use case
- Re: [DPUB-ANNOTATION-UC] Comment on title or on publication? [I18N-ISSUE-457]
- [DPUB-ANNOTATION-UC] Annotations for accessibility use case
- Re: [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- Re: [DPUB-ANNOTATION-UC] Comment on title or on publication? [I18N-ISSUE-457]
Saturday, 10 October 2015
- Re: [Moderator Action] [Activity Streams] AS2.0: Section 3.2: language example issues [I18N-ISSUE-387][I18N-ACTION-469]
- [DPUB-ANNOTATION-UC] Comment on title or on publication? [I18N-ISSUE-457]
- [DPUB-ANNOTATION-UC] 2.1.3 general observation about language identification [I18N-ISSUE-458]
- [DPUB-ANNOTATION-UC] 2.1.7 privacy issues [I18N-ISSUE-459][I18N-ACTION-464]
- [XSLT30] collection lang processing should refer to BCP47 [I18N-ISSUE-400][I18N-ACTION-467]
- [Activity Streams] AS2.0: Section 3.2: language example issues [I18N-ISSUE-387][I18N-ACTION-469]
Thursday, 8 October 2015
- I18N-ACTION-474: Prepare and publish fpwd of best practices for specification developers
- I18N-ACTION-473: Ensure we have a meeting number set up for next week