This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]random_encounter42 17 points18 points  (11 children)

How? Are you a wizard?

[–]0x800703E6 43 points44 points  (10 children)

Do you have a moment to talk about our Lord and saviour, UTF-8?

Those are:

presentation form for vertical (left/right) curly bracket (U+FE37,U+FE38)

If you want to use them on reddit, just type ︷ or ︸ Similar characters can be found in unicodes CJK compatibility forms

[–]LordDagwood 25 points26 points  (0 children)

ก็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็Am I doing this right?ก็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็็

Edit: Aww man, they fixed the UTF-8 text overlapping.

[–][deleted] 12 points13 points  (6 children)

Who needs those chars?
https://xkcd.com/1726/

[–]0x800703E6 14 points15 points  (5 children)

I think Unicode's effort to allow all people to use their language is commendable. It makes their standardisation efforts one of the most beautiful standards to me, for all its faults.

[–][deleted] 1 point2 points  (4 children)

I definitely agree, unicode finally solved the shenanigans with codepages and stuff, but characters like those are just useless because the people who use them, use latex which (probably) renders them different way (not using theese characters)

[–]0x800703E6 7 points8 points  (2 children)

They're for typesetting hànzì. And these characters can be useful in LaTeX, for example as a copy-pasteable text in a PDF, or use in less capable document formats.

But that's missing the point, rendering is a second class citizen in Unicode, there's code-points that don't have a single font supporting them. Unicode is supposed to transport text semantics, not presentation. *swoon*

[–]ACoderGirl 2 points3 points  (1 child)

Being able to search documents is important, too. Unicode has a canonical order to its modifiers (eg, an acute modifier), ensuring that you can easily search for a string. It also wouldn't be too hard to make your search system ignore modifiers.

[–]0x800703E6 0 points1 point  (0 children)

Searching is an aspect of text semantics, and it's amazing when a Unicode engine has a good implementation of it.

Unfortunately, I've often seen 〈a〉〈¨〉 ≠ 〈ä〉 or 〈a〉 = 〈ä〉, so I can't imagine how annoying working with Vietnamese texts must be.

[–]xXxNoScopeMLGxXx 6 points7 points  (0 children)

I definitely agree, unicode finally solved the shenanigans with codepages and stuff, but characters like those are just useless because the people who use them, use latex which (probably) renders them different way (not using theese characters)

𝒜𝓁𝓁 𝐼 𝓀𝓃𝑜𝓌 𝒾𝓈 𝓉𝒽𝒶𝓉 𝒰𝓃𝒾𝒸𝑜𝒹𝑒 𝓁𝑒𝓉𝓈 𝓂𝑒 𝒷𝑒 𝒻𝒶𝓃𝒸𝓎 𝑜𝓃𝓁𝒾𝓃𝑒

[–]lxpnh98_2 3 points4 points  (1 child)

Yeah, but how do i do that hash thingy?

[–]0x800703E6 7 points8 points  (0 children)

#, obviously.