Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

75%
+7 −1
Q&A Should HTML entities be supported in titles?

I just noticed that HTML entities (such as &aleph; for ℵ or &mdash; for —) seem not to be supported in titles. Should they be? Clarification: I'm not asking for general HTML support in t...

1 answer  ·  posted 3y ago by celtschk‭  ·  last activity 3y ago by Monica Cellio‭

#3: Post edited by user avatar celtschk‭ · 2021-05-18T06:10:26Z (over 3 years ago)
Fixed a typo
  • I just noticed that HTML entities (such as &amp;aleph; for &aleph; or &amp;mdash; for &mdash;) seem not to be supported in titles.
  • Should they be?
  • **Clarification:**
  • I'm not asking for general HTML support in titles, just of HTML entities. Note that entities cannot encode anything that you won't find in the Unicode character set, so anything you can do with them can already be done by adding those characters directly, just with more effort.
  • An example where this would be handy (and where I noticed that they are not supported) is in [this question on Languages & Linguistics](https://languages.codidact.com/posts/281765) where I used the character “&aleph;“ in the title (as well as the uppercase Greek “&Alpha;”, but there I could have gone with just using a normal uppercase A instead). I ended up copy/pasting it from the actual question text (where entities are supported), but that meant additional effort that could have been avoided.
  • For me it would also be sufficient to support named entities; If I figure out the Unicode code point of a character, it's no more effort to type the character itself using that number than it is to type the corresponding numeric HTML entity. I don't know if all relevant systems support character entry by code point, though.
  • **Note:** I've added the feature-request tag to this post.
  • I just noticed that HTML entities (such as &amp;aleph; for &aleph; or &amp;mdash; for &mdash;) seem not to be supported in titles.
  • Should they be?
  • **Clarification:**
  • I'm not asking for general HTML support in titles, just of HTML entities. Note that entities cannot encode anything that you won't find in the Unicode character set, so anything you can do with them can already be done by adding those characters directly, just with more effort.
  • An example where this would be handy (and where I noticed that they are not supported) is in [this question on Languages & Linguistics](https://languages.codidact.com/posts/281765) where I used the character “&aleph;“ in the title (as well as the uppercase Greek “&Alpha;”, but there I could have gone with just using a normal uppercase A instead). I ended up copy/pasting it from the actual question text (where entities are supported), but that meant additional effort that could have been avoided.
  • For me it would also be sufficient to support named entities; if I figure out the Unicode code point of a character, it's no more effort to type the character itself using that number than it is to type the corresponding numeric HTML entity. I don't know if all relevant systems support character entry by code point, though.
  • **Note:** I've added the feature-request tag to this post.
#2: Post edited by user avatar celtschk‭ · 2021-05-18T06:08:02Z (over 3 years ago)
Added clarification and feature-request tag
  • I just noticed that HTML entities (such as &amp;aleph; for &aleph; or &amp;mdash; for &mdash;) seem not to be supported in titles.
  • Should they be?
  • I just noticed that HTML entities (such as &amp;aleph; for &aleph; or &amp;mdash; for &mdash;) seem not to be supported in titles.
  • Should they be?
  • **Clarification:**
  • I'm not asking for general HTML support in titles, just of HTML entities. Note that entities cannot encode anything that you won't find in the Unicode character set, so anything you can do with them can already be done by adding those characters directly, just with more effort.
  • An example where this would be handy (and where I noticed that they are not supported) is in [this question on Languages & Linguistics](https://languages.codidact.com/posts/281765) where I used the character “&aleph;“ in the title (as well as the uppercase Greek “&Alpha;”, but there I could have gone with just using a normal uppercase A instead). I ended up copy/pasting it from the actual question text (where entities are supported), but that meant additional effort that could have been avoided.
  • For me it would also be sufficient to support named entities; If I figure out the Unicode code point of a character, it's no more effort to type the character itself using that number than it is to type the corresponding numeric HTML entity. I don't know if all relevant systems support character entry by code point, though.
  • **Note:** I've added the feature-request tag to this post.
#1: Initial revision by user avatar celtschk‭ · 2021-05-14T13:40:24Z (over 3 years ago)
Should HTML entities be supported in titles?
I just noticed that HTML entities (such as &amp;aleph; for &aleph; or &amp;mdash; for &mdash;) seem not to be supported in titles.

Should they be?