News for hackers. Stuff that matters.
Re:Towards LaTeX in the Browser by Bromskloss on Sunday January 28, 2018 @03:24AM (#16250414)
It's an interesting idea. At what point, though, do we draw the line between what a character set (like Unicode) should handle, and what should be handled by a higher-level layer? I'm thinking that things like boldness, italicisation, and super script aren't really the job for a character set.
Re:Towards LaTeX in the Browser by yorwba on Sunday January 28, 2018 @05:57AM (#16250769)
Unicode already has 𝐛𝐨𝐥𝐝, 𝘪𝘵𝘢𝘭𝘪𝘤 and ˢᵘᵖᵉʳˢᶜʳⁱᵖᵗ variants of the Latin alphabet.
Re:Towards LaTeX in the Browser by colejohnson66 on Sunday January 28, 2018 @06:49AM (#16250894)
Maybe it’s just iOS, but the “bold” characters are serifed and the “superscript” one’s aren’t a consistent size between each other.
Re:Towards LaTeX in the Browser by yorwba on Sunday January 28, 2018 @08:32AM (#16251223)
Unicode only defines the codepoints for characters, it doesn't require anyone to actually make them look good. Since those characters were specifically only included to represent mathematical texts where formatting needs to be preserved, it's unlikely anyone is spending much effort on making them look good as text.

Regarding serifs: there are actually two variants of both bold and italic (and bold italic), one serifed and one not. Wikipedia has a chart of the different options here: https://en.wikipedia.org/wiki/Mathematical_Alphanumeric_Symb...

Re:Towards LaTeX in the Browser by cooper12 on Sunday January 28, 2018 @08:58PM (#16254818)
The bold and italic characters actually belong to the Mathematical Alphanumeric Symbols [0] block, so they're strictly meant for math notation rather than general formatting. The superscripts are part of the Spacing Modifier Letters [1] block, which is used for IPA. You'll also sometimes find other formatting quirks that are deprecated in Unicode and meant for compatibility purposes.

[0]: https://en.wikipedia.org/wiki/Mathematical_Alphanumeric_Symb...

[1]: https://en.wikipedia.org/wiki/Spacing_Modifier_Letters

Re:Towards LaTeX in the Browser by jcelerier on Sunday January 28, 2018 @07:57AM (#16251103)
Re:Towards LaTeX in the Browser by Bromskloss on Sunday January 28, 2018 @10:04AM (#16251542)
Yes, and I'm not convinced that it is the right thing to do.
Re:Towards LaTeX in the Browser by moultano on Sunday January 28, 2018 @11:23AM (#16251883)
I'd say if the formatting changes the meaning of the language, Unicode should support it. So if you are searching through text, any change to your query string that you would like to constrain the text that matches should be supported by Unicode. Unicode should at least support anything that affects the semantic equality of strings.
Re:Towards LaTeX in the Browser by Bromskloss on Sunday January 28, 2018 @04:13PM (#16253535)
I'm thinking of Unicode as a character set, and that text exists on an abstraction level above characters.
Re:Towards LaTeX in the Browser by moultano on Sunday January 28, 2018 @04:37PM (#16253689)
I was thinking that it's analogous to ก็็็็็็็็็็็็็็็็็็็็ where the character dictates how the surrounding characters are rendered.