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
This is a request from the W3C i18n WG that the HTML Standard define character entities to cover key invisible/ambiguous Unicode characters.
The following is a list of candidates that we are proposing, including (for convenience) a list of already existing named entities. The latter are marked in bold. Entity names are proposed after the character name, and are based on abbreviations used by Unicode, where they exist. Lower priority items are italicised.
Latin 1 Supplement — Latin-1 punctuation and symbols
U+00A0 NO-BREAK SPACE
U+00AD SOFT HYPHEN­
Combining Diacritical Marks — Grapheme joiner
U+034F COMBINING GRAPHEME JOINER &cgj;
Arabic — Format character
U+061C ARABIC LETTER MARK &alm;
Hangul Jamo — Old initial consonants
U+115F HANGUL CHOSEONG FILLER&hcf;
Hangul Jamo — Medial vowels
U+1160 HANGUL JUNGSEONG FILLER&hjf;
Ogham — Space
U+1680 OGHAM SPACE MARK &osm;
Mongolian — Format controls
U+180B MONGOLIAN FREE VARIATION SELECTOR ONE &fvs1;
U+180C MONGOLIAN FREE VARIATION SELECTOR TWO &fvs2;
Create the review comment you want to propose by replacing the prompts above these instructions, but LEAVE ALL THE INSTRUCTIONS INTACT
Add one or more t:... labels. These should use ids from specdev establish a link to that doc.
Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.
Ask the i18n WG to review your comment.
After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-*lreq label(s).
Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use [...](...) notation – you need to delete the placeholder, then paste the URL.
Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue.
If you added an *lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.
Edit this issue to REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT, ie. the line below that is '---' and all the text before it to the very start of the issue.
This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:
§ url_for_the_issue_raised
The text was updated successfully, but these errors were encountered:
r12a
added
pending
Issue not yet sent to WG, or raised by tracker tool & needing labels.
s:html
https://html.spec.whatwg.org/multipage/
t:char_ref
Referring to Unicode characters
labels
Mar 28, 2024
This is a request from the W3C i18n WG that the HTML Standard define character entities to cover key invisible/ambiguous Unicode characters.
The following is a list of candidates that we are proposing, including (for convenience) a list of already existing named entities. The latter are marked in bold. Entity names are proposed after the character name, and are based on abbreviations used by Unicode, where they exist. Lower priority items are italicised.
Latin 1 Supplement — Latin-1 punctuation and symbols
­
Combining Diacritical Marks — Grapheme joiner
&cgj;
Arabic — Format character
&alm;
Hangul Jamo — Old initial consonants
&hcf;
Hangul Jamo — Medial vowels
&hjf;
Ogham — Space
&osm;
Mongolian — Format controls
&fvs1;
&fvs2;
&fvs3;
&mvs;
&fvs4;
General Punctuation — Spaces
&nqsp;
&mqsp;
 
 
 
 
&6msp;
 
 
 
AND 
 
AND 
AND part of  
(U+0205F U+200A)General Punctuation — Format character
​
AND​
AND​
AND​
AND​
‌
‍
‎
‏
&lri;
&rli;
&fsi;
&pdi;
&lro;
&rlo;
⁠
&lre;
&rle;
&pdf;
General Punctuation — Separators
&lsep;
&psep;
General Punctuation — Space
&nnbsp;
 
AND part of  
(U+205F U+200A)General Punctuation — Invisible operators
⁡
AND⁡
⁢
⁣
AND⁣
&InvisiblePlus;
&aafs;
CJK Symbols And Punctuation — CJK symbols and punctuation
&idsp;
Hangul Compatibility Jamo — Special character
&hf;
Halfwidth And Fullwidth Forms — Halfwidth Hangul variants
&hwhf;
Shorthand Format Controls — Shorthand format controls
Musical Symbols — Beams and slurs
Emoji Variation Selectors - turns on and off colour
&vs15;
&vs16;
We would also like to have a &zwsp; alias in addition to
​
for U+200B.Instructions:
This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html
Create the review comment you want to propose by replacing the prompts above these instructions, but LEAVE ALL THE INSTRUCTIONS INTACT
Add one or more t:... labels. These should use ids from specdev establish a link to that doc.
Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.
Ask the i18n WG to review your comment.
After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-*lreq label(s).
Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use [...](...) notation – you need to delete the placeholder, then paste the URL.
Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue.
If you added an *lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.
Edit this issue to REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT, ie. the line below that is '---' and all the text before it to the very start of the issue.
This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:
§ url_for_the_issue_raised
The text was updated successfully, but these errors were encountered: