Upvoted just because your link to U+203E OVERLINE lead me to finding out the difference between it and the macron¹.<p>If I understand correctly though, you’re saying to get around the automatic capitalization of submitted titles by using an overline as the first character? So this title would look like this instead:<p>‾tvOS for Developers<p>…but that doesn’t really seem very elegant to me. Perhaps you could achieve a similar affect by using an invisible character at the beginning of the sentence instead, such as U+200B ZERO WIDTH SPACE². Since it’s not in Unicode’s &#x27;Zs&#x27; (Separator, space) character category—in addition to its &#x27;Wspace&#x27; key having the value &#x27;N&#x27;—it’s unlikely that if HN’s code strips leading and trailing whitespace from submitted titles, U+200B ZERO WIDTH SPACE will be stripped.<p>I guess if that doesn’t work, you could always replace U+0054 LATIN CAPITAL LETTER T with a similar looking lowercase equivalent such as U+0288 LATIN SMALL LETTER T WITH RETROFLEX HOOK³ or even U+1D5CD MATHEMATICAL SANS-SERIF SMALL T⁴ (that’s assuming you’re fine with some people not being able to view it due to not having a font installed with a glyph for that character)… but I’d avoid misusing the semantic significance of those characters like that.<p>――――――<p>¹ — <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Overline" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Overline</a><p>² — <a href="http:&#x2F;&#x2F;graphemica.com&#x2F;200B" rel="nofollow">http:&#x2F;&#x2F;graphemica.com&#x2F;200B</a><p>³ — <a href="http:&#x2F;&#x2F;graphemica.com&#x2F;%CA%88" rel="nofollow">http:&#x2F;&#x2F;graphemica.com&#x2F;%CA%88</a><p>⁴ — <a href="http:&#x2F;&#x2F;graphemica.com&#x2F;%F0%9D%97%8D" rel="nofollow">http:&#x2F;&#x2F;graphemica.com&#x2F;%F0%9D%97%8D</a>