Tuesday, 31 August 2010
- Re: [Bug 10479] add role=radiogroup to details element
- [Bug 10518] Add example showing how to use <a> elements in image maps
- [Bug 10478] modify table, tr and td roles
- [Bug 10479] add role=radiogroup to details element
- [Bug 10481] Default role of <IMG> should be "img"
- [Bug 10484] default roles for figcaption and caption: Make it simple to achieve accessibility
- [Bug 10485] The img element with non-empty alt should default to the img aria role
- [Bug 10486] References to "image" ARIA role should be "img"
- [Bug 10493] "ARIA restricts usage of this role to one per page" is an unclear statement
- [Bug 10494] modify aria example and fix spelling
- [Bug 10496] fix error in aria conformance checker advice
- {Announcement} Media accessibility user requirements overview, Thu Sep 2
- Re: Update "HTML 5 differences from HTML 4"
- [Bug 9280] Add default button option/attribute for forms
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
- [Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs
- [Bug 9214] Allow role="presentation" img as conformance Criteria
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level
- [Bug 9113] re: "axis on td and th elements" text could say "Use the scope attribute on the relevant th"
- [Bug 9098] Correct the img element definition. Replace with suggested text.
- [Bug 8885] Fallback mechanism for embedded content
- [Bug 8872] split out and modify parts of Section 4.8.2.1 the img element
- [Bug 9061] allow image maps on the canvas element.
- [Bug 8000] ARIA roles added to the a element should be conforming in HTML5
- [Bug 10252] HTML5 hard-binds "Action" to accesskey key-press
- [Bug 10251] Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element
- [Bug 10251] Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element
- [Bug 10252] HTML5 hard-binds "Action" to accesskey key-press
- [Bug 10077] The <embed> should support an alt attribute. While the embedded content should provide for accessilibility of the embedded object, the developer doesn't always have control over those content, some embeddable formats are inherently less accessible, and th
- [Bug 10249] Canvas requires a content selection method
- [Bug 10248] Canvas requires a Caret Drawing call method
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
- [Bug 9623] <details> and <summary> are missing from the "strong aria semantics" table
Monday, 30 August 2010
Sunday, 29 August 2010
Saturday, 28 August 2010
- [Bug 8554] <progress> element should be labelable with a label
- [Bug 8144] Is a 'visibility: hidden' element being rendered?
- [Bug 8747] Defining how a license applies to elements
- Bug 8747
- DOM Level 3 Events Last Call schedule
Friday, 27 August 2010
- [Bug 10462] merge ARIA mapping tables and list
- [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference
- [Bug 10464] provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
- [Bug 10465] provide correct aria mapping and role info for the table element
- [Bug 10467] provide headings in the WAI-ARIA section of the spec to make it easier to understand
Thursday, 26 August 2010
- Re: link relation metadata considerations, also ACTION-186
- RE: Media Accessibility User Requirements Published
- [Bug 10444] ARIA section does not list elements that have no default role or role restrictions
- Media Accessibility User Requirements Published
- [Bug 10452] Consider documenting attributes that map to ARIA properties in a separate table
- [Bug 10451] Consider restricting the roles allowed for the label element
- [Bug 10450] Allow lists to be used as menus or tab sets
- [Bug 10449] Consider allowing various command-like ARIA roles for h1-h6
- [Bug 10448] Consider broadening the set of allowed roles for command elements
- [Bug 10447] <output> should have no role by default instead of status role
- [Bug 10446] Consider limiting the roles of certain media and plugin elements
- [Bug 10445] Certain elements with no role should have that as a strong semantic
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- [Bug 10441] <link> that represents a hyperlink should probably have no role by default
- [Bug 10440] menu type=context should have "menu" role
- [Bug 10439] <input type=file> has "button" role, but is typically a compound control
- [Bug 10438] math should be changed changed from no role to "math" role
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- RE: ISSUE-116: Would a separate document work?
Wednesday, 25 August 2010
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- Re: ISSUE-116: Would a separate document work?
- ISSUE-117 (deprecate-noscript): Chairs Solicit Proposals
- ISSUE-116: Would a separate document work?
- rel="longdesc" (was: providing a long description using the summary and details elements.)
- RE: providing a long description using the summary and details elements.
- Re: method for providing programmatically associated long description
- RE: providing a long description using the summary and details elements.
- Re: method for providing programmatically associated long description
- Re: method for providing programmatically associated long description
- Re: providing a long description using the summary and details elements.
- RE: Formal Objection to ISSUE-30 (Was: Letter to the Team Contact - ISSUE-30.)
- Re: method for providing programmatically associated long description
- Re: providing a long description using the summary and details elements.
- method for providing programmatically associated long description
- Re: providing a long description using the summary and details elements.
- Re: providing a long description using the summary and details elements.
- Input values across type changes
- Re: providing a long description using the summary and details elements.
Tuesday, 24 August 2010
- Re: More ISSUE 30 @longdesc use cases
- Re: providing a long description using the summary and details elements.
- Re: providing a long description using the summary and details elements.
- Re: providing a long description using the summary and details elements.
- Re: providing a long description using the summary and details elements.
- Re: providing a long description using the summary and details elements.
- More ISSUE 30 @longdesc use cases
- Re: providing a long description using the summary and details elements.
- Re: providing a long description using the summary and details elements.
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: providing a long description using the summary and details elements.
- providing a long description using the summary and details elements.
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- HTML5 Suggested UIs for making title attribute content accessible
- Why is there a rendering rule for col[valign] ?
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- RE: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- RE: ISSUE 30 @longdesc use cases
Monday, 23 August 2010
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- RE: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Formal Objection to ISSUE-30 (Was: Letter to the Team Contact - ISSUE-30.)
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- Re: ISSUE 30 @longdesc use cases
- ISSUE 30 @longdesc use cases
- MathML3 Proposed Recommendation
Sunday, 22 August 2010
- [Bug 10068] Suggest making noscript obsolete but conforming
- SVG and CSS thoughts from Doug S - FYI
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- [Bug 10412] restriction of "bookmark" to <a>/<area> is arbitrary
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
Saturday, 21 August 2010
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: link relation metadata considerations, also ACTION-186
- Re: Report on testing of the link relations registry
- WHATWG IRC chat about link relations (ISSUE-27)
- Re: Status of Leif's Appeal / Issue 30 Objections
Thursday, 19 August 2010
- Action-55 - ARIA in HTML5 draft text and change proposal
- Status of Leif's Appeal / Issue 30 Objections
- RE: {minutes} HTML WG telecon 2010-08-19: WG decisions, Decision Policy, TF reports
- Re: Working Group Decision on ISSUE-30 longdesc
Wednesday, 18 August 2010
- [Bug 9214] Allow role="presentation" img as conformance Criteria
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
Tuesday, 17 August 2010
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: ISSUE-41: extensibility change proposal advocates
- [Bug 7543] Consensus on ietf-http-wg was that repetition of relations is meaningless and we should rather use numbering (e.g. "up2"), names (e.g. "great-grandparent") or an attribute (e.g. level="3").
- [Bug 10172] nofollow/noreferrer not allowed on <link>
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- [Bug 9845] provide reference and info about HTML5: Techniques for providing useful text alternatives in html5 spec
- ISSUE-27 and microformats process, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: change proposal: Specification of authoring conformance requirments in HTML5
- ISSUE-116, was: change proposal: Specification of authoring conformance requirments in HTML5
- Re: ISSUE-27, was: Report on testing of the link relations registry
- [Bug 9845] provide reference and info about HTML5: Techniques for providing useful text alternatives in html5 spec
- change proposal: Specification of authoring conformance requirments in HTML5
- Re: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: ISSUE-27, was: Report on testing of the link relations registry
- Re: [whatwg] Using BugZilla for non-W3C spec issues
- Re: Report on testing of the link relations registry
- Using BugZilla for non-W3C spec issues
- RE: Working Group Decision on ISSUE-30 longdesc
Monday, 16 August 2010
- Re: Update on Issue-27, was: ACTION-182 and Issue-27
- Re: Report on testing of the link relations registry
- [Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations
- [Bug 10068] Suggest making noscript obsolete but conforming
- [Bug 10276] change spellcheck IDL attribute back to boolean
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- ISSUE-27, was: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- [Bug 10332] Shipping browsers don't have form.action reflect the DOM attribute exactly. Specifically, if the content attribute is the empty string, they generally return "" on an IDL get, not the current address. This contradicts the spec, but it would be confusing
- [Bug 10366] please ban <input type=file> if the form's enctype is application/x-www-form-urlencoded, as this seems an authoring error
Sunday, 15 August 2010
- ISSUE-27, Re: Report on testing of the link relations registry
- Re: Report on testing of the link relations registry
- Report on testing of the link relations registry
- Re: Letter to the Team Contact - ISSUE-30.
Saturday, 14 August 2010
- RE: ISSUE-109: aria-section-title - Straw Poll for Objections
- Re: ISSUE-109: aria-section-title - Straw Poll for Objections
- RE: ISSUE-109: aria-section-title - Straw Poll for Objections
- Re: ISSUE-4: html-versioning / ISSUE-84: legacy-doctypes - Straw Poll for Objections
- RE: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: ISSUE-4: html-versioning / ISSUE-84: legacy-doctypes - Straw Poll for Objections
- Re: Letter to the Team Contact - ISSUE-30.
Friday, 13 August 2010
- Re: ISSUE-4: html-versioning / ISSUE-84: legacy-doctypes - Straw Poll for Objections
- Re: Letter to the Team Contact - ISSUE-30.
- RE: Letter to the Team Contact - ISSUE-30.
- RE: Update on Issue-27, was: ACTION-182 and Issue-27
- Re: Letter to the Team Contact - ISSUE-30.
- RE: Letter to the Team Contact - ISSUE-30.
- RE: Letter to the Team Contact - ISSUE-30.
- Re: Letter to the Team Contact - ISSUE-30.
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Letter to the Team Contact - ISSUE-30.
- Letter to the Team Contact - ISSUE-30.
- Re: ISSUE-4: html-versioning / ISSUE-84: legacy-doctypes - Straw Poll for Objections
- Re: Working Group Decision on ISSUE-30 longdesc
- link relation metadata considerations, was: Update on Issue-27, was: ACTION-182 and Issue-27
- Re: ACTION-182 and Issue-27
- Re: Update on Issue-27, was: ACTION-182 and Issue-27
- RE: Update on Issue-27, was: ACTION-182 and Issue-27
- Update on Issue-27, was: ACTION-182 and Issue-27
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
Thursday, 12 August 2010
- Re: <select> element @size default
- <select> element @size default
- Re: ISSUE-4: html-versioning / ISSUE-84: legacy-doctypes - Straw Poll for Objections
- Re: ISSUE-4: html-versioning / ISSUE-84: legacy-doctypes - Straw Poll for Objections
- ACTION-103, Re: some conformance questions
- Re: document.load: History and a proposal
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
- Re: Working Group Decision on ISSUE-30 longdesc
Wednesday, 11 August 2010
- Re: Working Group Decision on ISSUE-30 longdesc
- RE: ISSUE-41: extensibility change proposal advocates
- Re: ISSUE-100 and convergence of specs
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- ISSUE-109: aria-section-title - Straw Poll for Objections
- Working Group Decision on ISSUE-30 longdesc
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: request to re-open http://www.w3.org/html/wg/tracker/issues/116
- Re: ISSUE-100 and convergence of specs
Tuesday, 10 August 2010
- Re: ISSUE-100 and convergence of specs
- Re: [html5] r5258 - [e] (0) Some more references to UTF-8.
- Re: ISSUE-110 sandbox-type-owner - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: [html5] r5258 - [e] (0) Some more references to UTF-8.
- ISSUE-100 and convergence of specs
- Re: [html5] r5258 - [e] (0) Some more references to UTF-8.
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: <meta http-equiv="Link"> question
Monday, 9 August 2010
- Re: <meta http-equiv="Link"> question
- Re: <meta http-equiv="Link"> question
- Re: <meta http-equiv="Link"> question
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: ISSUE-41: extensibility change proposal advocates
Sunday, 8 August 2010
- Re: thoughts about a visible caret
- request to re-open http://www.w3.org/html/wg/tracker/issues/116
- [Bug 10301] HTMLOptionElement.text should not be identical to .textContent - causes interop issues with web content
- [Bug 10306] Why is <01> not OK? It would make the parser simpler and allows zero-padding when using more than 9 voices.
- [Bug 10132] A CanvasPattern object should have a way to offset the repitition of an image.
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: thoughts about a visible caret
Saturday, 7 August 2010
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: thoughts about a visible caret
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- Re: Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
- thoughts about a visible caret
- Specific points of controversy relating to alt text (ISSUE-31, ISSUE-80)
Friday, 6 August 2010
Thursday, 5 August 2010
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- RE: ISSUE-41: extensibility change proposal advocates
- RE: {minutes} HTML WG telecon 2010-08-04 [task force week]
- link relation "external", was: Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Link relation types and validity in <link>, was: ACTION-182 and Issue-27
- Re: ISSUE-41: extensibility change proposal advocates
- Re: ISSUE-41: extensibility change proposal advocates
Wednesday, 4 August 2010
- Re: ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-41: extensibility change proposal advocates
- Re: <meta http-equiv="Link"> question
- Re: <meta http-equiv="Link"> question
- Re: ISSUE-41: extensibility change proposal advocates
- Re: <meta http-equiv="Link"> question
- Re: ISSUE-89 idioms - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-100: srcdoc - Straw Poll for Objections
- Re: <meta http-equiv="Link"> question
- Re: <meta http-equiv="Link"> question
- ISSUE-41: extensibility change proposal advocates
- Re: HTML Media Capture draft from Device APIs and Policy Working Group
- ISSUE-110 sandbox-type-owner - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-89 idioms - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: HTML Media Capture draft from Device APIs and Policy Working Group
- Re: HTML Media Capture draft from Device APIs and Policy Working Group
- Re: HTML Media Capture draft from Device APIs and Policy Working Group
- Re: HTML Media Capture draft from Device APIs and Policy Working Group
- [Bug 9785] Add a "filter" attribute. If set, the user agent will filter the datalist. If not, filter won't be filtered automatically (unless you do some sort of filtering by javascript or/and server-side)
- [Bug 9741] enctype, formenctype, method and formmethod IDL attributes should be limited to only known values
- [Bug 9726] Spec the features argument
- [Bug 9584] drawImage() shouldn't throw INVALID_STATE_ERR
- [Bug 9663] Should sequences of bytes be replaced by a single U+FFFD, or one U+FFFD per input byte?
- [Bug 9649] It doesn't look like any browser supports document.innerHTML
- [Bug 9602] That autofocus attribute will wreak security havok. What an ignorant idea to bring more logic to HTML. I think I know a couple of ways to abuse it, since it actually is some sort of flow control, which only scripting languages should be capable of. I hope
- [Bug 9579] An element should not suffer from pattern mismatch if the pattern attribute value is the empty string
- [Bug 9577] Define the x and y attributes. Both Gecko and WebKit have them and apparently some sites depend on them :/
- [Bug 9573] spec input.onsearch
- [Bug 9546] computing atom:updated
- [Bug 9542] Recommended rendering for table alignment does not match reality
- [Bug 9514] Specify Selection.modify()
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource
- [Bug 9439] UA should not change values of input elements in telephone state
- [Bug 7543] Consensus on ietf-http-wg was that repetition of relations is meaningless and we should rather use numbering (e.g. "up2"), names (e.g. "great-grandparent") or an attribute (e.g. level="3").
- Re: <meta http-equiv="Link"> question
- [Bug 9578] On http-state it was mentioned that browsers support Set-Cookie here. Ugh!
- [Bug 9797] <meta http-equiv="Link"> not addressed by spec
- <meta http-equiv="Link"> question
Tuesday, 3 August 2010
Monday, 2 August 2010
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: i18n Polyglot Markup/Encodings
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: Polyglot Markup/XML encoding declaration
- Re: i18n Polyglot Markup/Encodings