The real purpose of unicode was that it managed to come up with a good character compression sceme that was trivial to implement with backwards compatibility for almost any language and computer system. You see, every localisation had its own character sets, either defined as 7-8bits, 16bits or something inbetween. So the unicode solution to add control bits that could tell the decoder which localisation the character set was from, made it so that backwards compatibility meant adding a single byte would correctly translate the entire localisation. This technique shares some similarities with lazy allocation. You're truncating all whitespace until you decide to allocate something to that whitespace, a special character, then you use that whitespace.
A problem with variable length encoding is that, it makes it difficult to index characters, Since indexing works on the principle of calculating offset number of bytes from current position, we have to read each character, to index them : ( which is very slow in terms of time complexity
but how program know if text should be treated as en or ar for example in a file in en and ar it will read byte(s) properly and print text properly without treating ar as en. i thought it will answer this.
Wake up, babe, that cool channel just uploaded again.
The real purpose of unicode was that it managed to come up with a good character compression sceme that was trivial to implement with backwards compatibility for almost any language and computer system. You see, every localisation had its own character sets, either defined as 7-8bits, 16bits or something inbetween. So the unicode solution to add control bits that could tell the decoder which localisation the character set was from, made it so that backwards compatibility meant adding a single byte would correctly translate the entire localisation.
This technique shares some similarities with lazy allocation. You're truncating all whitespace until you decide to allocate something to that whitespace, a special character, then you use that whitespace.
Excellent vid, welcome back!
Magnificent video as always Bartek!
Great video man, you are really good at this
Great vid as always! Truly enjoy the style
Fantastic video as always! Visuals are on point
Very nice animations and good condensed knowledge. Tak trzymaj!
Great video! Simple explanation and amazing animation!
Nice man! It’s base64 that clicked with me
Great content, hope to see your videos more frequently
Amazing video that covered a ton!
I really enjoyed this video!
simple and to the point, thank you :)
bro just drops bangers
A problem with variable length encoding is that, it makes it difficult to index characters,
Since indexing works on the principle of calculating offset number of bytes from current position,
we have to read each character, to index them : (
which is very slow in terms of time complexity
Lovely video!
So helpful, so appreciated
Great video. What do you use for the animations?
Thank you! This was done in After Effects
This video is beautiful :)
Dope video! 🤗 ❤️
I wonder how you made the animations. 😶
Edit: probably Motion Canvas here too.
Thank you!
but how program know if text should be treated as en or ar for example in a file in en and ar it will read byte(s) properly and print text properly without treating ar as en. i thought it will answer this.