You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gap-analysis/index.html
+17-2Lines changed: 17 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -217,12 +217,27 @@ <h3>Text boundaries & selection</h3>
217
217
218
218
219
219
220
-
<sectionid="quotations" class="basic">
220
+
<sectionid="quotations" class="advanced">
221
221
<h3>Quotations</h3>
222
222
<pclass="status_prompt">Are there any issues when dealing with quotations marks, especially when nested? Should block quotes be indented or handled specially? <ahref="http://w3c.github.io/typography/index#quotations">See available information</a> or <ahref="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Aquotations%20label%3Atype-info-request%20label%3Aarabic">check for currently needed data</a>.</p>
223
+
<sectionid="q_defaults">
224
+
<h4><ahref="#q_defaults">Default quotation marks for q element</a></h4>
225
+
<p>If the <codeclass="kw" translate="no">html</code> tag sets the language of a page, the HTML specification says that the <codeclass="kw" translate="no">q</code> element should by default produce quotation marks according to the information in CLDR for that language.</p>
226
+
<p>For <strong>Arabic</strong>, the default quote marks should be, reading right to left, “...”, and embedded quote marks ‘...’. Firefox produces these but facing in the wrong direction. (Chrome & Safari are ok.) See a <ahref="https://w3c.github.io/i18n-tests/results/the-q-element.html#language">test and results</a>.</p>
227
+
<p>For <strong>Persian</strong>, the default quote marks should be, reading right to left, «...», and embedded quote marks ‹...›. Again, Chrome & Safari are ok, but Firefox produces the wrong quotation marks, since it doesn't change them according to the language set. See a <ahref="https://w3c.github.io/i18n-tests/results/the-q-element.html#language">test and results</a>.</p>
228
+
</section>
229
+
230
+
<sectionid="q_section">
231
+
<h4><ahref="#q_section">Default quotation marks in a new language section</a></h4>
232
+
<p>In addition, the default quotation marks for the <codeclass="kw" translate="no">q</code> element are not set to the appropriate characters by the browser when the element appears inside an Arabic/Persian section of a page that has a different overall language. This is currently per the HTML specification (both W3C and WhatWG). There is <ahref="https://github.com/whatwg/html/issues/3636#issuecomment-384340053">an issue</a> raised against the WhatWG version for this to be changed.</p>
233
+
</section>
223
234
235
+
<sectionid="q_multilingual">
236
+
<h4><ahref="#q_multilingual">Embedded quotations in a different language</a></h4>
237
+
<p>Arabic/Persian quotes embedded in text in another language can also be problematic if the outer language uses different quotation marks. This is due to the browsers choosing default quotation marks based on the language of the <em>quotation</em>, rather than that of the surrounding text. See <ahref="https://w3c.github.io/i18n-tests/results/the-q-element.html#ml_nesting">a test</a>. This behaviour is specified in the WhatWG version of the HTML spec, but no longer in the W3C version. There is <ahref="https://github.com/whatwg/html/issues/3636#issuecomment-384340053">an issue</a> raised against the WhatWG version for this to be changed.</p>
238
+
</section>
224
239
225
-
<p>In HTML and CSS the styling applied to nested multilingual quotations when using the <codeclass="kw" translate="no">q</code> element chooses quotation marks based on the language of the text inside the quotation, rather than outside.</p>
240
+
<p>Marking all the above as advanced, because use of the <codeclass="kw" translate="no">q</code> element is optional (quote characters can be used instead), and it can be styled using CSS for the general case.</p>
<divid="assertion"><bclass="assertion">Assertion:</b> A font will produce ligated forms for 'Allah' for the sequence alef, lam, lam, shadda, superscript alif, heh (or heh goal), but not if shadda and sup. alef are missing.</div>
30
+
<divclass="advice"><bclass="advice">Advice:</b> The right-hand column shows the precomposed character (which ought not to be used). You can change the font for the first row of data using the controls below.</div>
<div><bclass="instructions">Test passes if</b> the text in each cell produces the same elements as listed in the top row (the styling will be different).</div>
0 commit comments