Characters in a computer - Unicode Tutorial UTF-8 (3/3)

This tutorial explains the utf-8 way of representing characters in a computer; later generalizing (high level) how any kind of data can be represented in a computer.

[@kcvinu]

Really appreciate the way you describe the complex stuff very easily and clearly. Thanks a lot. After 9 years, we are waiting for the supplementary video.

[@user-eh5zk5bb9k]

really cool, thank you, 8 years later!

[@angolabharathi486]

Aqqragfhign

[@billh8208]

You sir deserve a medal . Thank you.

[@danalex2991]

You taught the entire concept really well. Kudo!

[@bama2619]

thank you. Great video explaining UTF-8. I have seen so many videos, yours is the best at explaining and graphics.

[@brunoleite9954]

Very good content! First time I was able to picture the use of the famous UTF-8

[@onyiachinedu3010]

This video series was extremely helpful. Thanks!

[@hariomkuntal9520]

Was looking for this across Google. Finally found with such a wonderful explanation. Thankyou!

[@parizer1983]

Nicely done mate, clear and precise!

[@steverock2175]

Very good mini-series, respect!

[@EricCosner]

I always wondered this stuff. Thanks so much! Great videos

[@ParswaNathTheo]

Thanks a lot, I was searching for such a transparent discussion whole day long, finally found yours in evening. Thank you so much.

[@diegopereira8213]

Nzjziksmksksnjwwisnkkxnxkznzijzi diz nzjziksmksksnjwwhindimixjxbxxjxhxuxhhxncicnkmkx.xkkxkkxkkxmxixmxo mi mmxo m o kx m kmoxmxk n jixjnxixmsijdoxkixkxxnxinixndinxnjxixjndinddixniixudnjjdibidjdinjdxndijidbuninijddijijindidndjdbfbufnjijvfhiffubtfthhugtujiigtgbfjjbfhubfhghufhugfvhgbudgjivfbjjvggvxbbjcgbfhjjhc Njifynisnkkxnxkznzijzi xkosjsidjsomsksoksisdoikifjSisjsixxixkxkixnxjdbisje njxixbbd DF dbdfb hx. Bxhxbhxjjbjxuxbxujxixjxijxihixjxjxiix

[@diegopereira8213]

Bjinhos minimiza nxixninjxnxixnjxc

[@Shokukumi]

I have to subscribe to you. The quality of your videos is extreme and if I need to teach my co-workers some basic encoding, I will use these videos.

[@girishmattur8610]

Thanks for the clear explanation..much appreciated!!

[@mrinalraj7166]

Core concept. Thanks. You are amazing.

[@dineshcondur]

Good Stuff! Really like the way you presented them..@ 6:35 How come c) is correct it would need 3 continuation bytes right?

[@marklord7614]

Wow, very enlightening. I really appreciate this video. Thank you!

[@tcbetka]

Makes sense. It's fairly simple to figure it out, given the different upload dates relative to now. But it might make it easier for people not looking at your channel.

[@MrVoayer]

Excellent explanation with good examples ! Great job ! Well done !

[@Tapajara]

A very good video series. You started at a much more basic level than any of my videos on the subject. By the way, I have another KZbin video called "History of ΦText". I was doing something about all of these issues before work began on Unicode. I developed something like UTF-8 back in 1987. In 2009 I updated this text system to be a superset of Unicode.

[@umsha1]

hello Sir! you have explained in a very good way in all 3 videos. Thanks

[@Calebhillary]

Great video which had exactly what I wanted

[@yaolegoleynik]

Its really best tutorial on that point! Thank you!

[@fai..9327]

I had done two classes in web-development but never knew what charset=utf-8 means. Thank you so much.

[@manojkumar-hz3tz]

solid explanation. loved it

[@avinmacha]

Beautifully explained! 👍👍

[@shadabsayeed4121]

Awesome explanation! Thanks

[@smarttrupti2007]

Such a great explanation!! Thank you very much. Sir please try to make more such great videos to clear the concepts of this digital world (core of computations and networks). Thank you once again.🙏

[@arunprashanna7494]

Quite complex stuff explained in the most appropriate way

[@Geekstocks]

A great 3-part series! Thanks so much for your time.

[@lordcjim]

Exceptionally helpful. Thank you very much!

[@bensycamore]

Very well done. This helped me a lot!

[@prem4708]

@dizauvi It's brilliant. Where were you when I was seeking you!!! I read so much on UTF encoding and never got my head around it until Stumbled upon this and I had partial enlightenment. Why partial? because in conclusion of the video you said that you are going to talk about quote "how is a character actually drawn or displayed on screen" unquote. But seriously I can't find that one, and have browsed through entire video of your channel. And also you don't seem to be active for more than a year now???

[@srinivastcs]

Awesome tutorial...... Thank you Sir!!!

[@Tapajara]

To see a 3D animation of how Unicode characters are encoded into UTF-8 byte streams, watch my KZbin video "ϕPPL Learning Series: UTF-8 Stream Encoding". Please note that that the video says that "up to 24 code point planes are supported". Unicode currently only supports 16 code point planes. The primary text system for the ϕPPL (ΦText) is a superset of UTF-32. Support for 24 code point planes is an attempt plan for future compatibility with Unicode.

[@GustavoMartinottoF]

You are a great teacher!

[@Xactant]

Really helpful, thank you.

[@pebre79]

Very clear rxplanation. thanks for posting

[@sciencengyaan5681]

Very nice explanation, u made it simple.

[@htalkies]

awesome work..

[@HiAdrian]

Very helpful, thanks!

[@gauravramrakhyani6286]

Very Nice Explaination, Thanks a lot.

[@simonefrancia5556]

You are a genius, thank you very much

[@shankaraklod]

Thank you so much!...its really helped me to solve some problems in integration area...

[@AD-ng4mz]

very nice tutorial. Thank you.

[@Smmmile]

Really excellent, thank you.

[@prathmeshgujar]

Superb explanation!

[@chandrag2536]

Very good...got a lot clarified...Thank you...

[@fishermand46]

Great video and explanation man!

[@Tapajara]

Also, ΦText is an alternative byte stream encoding method that is more efficient than UTF-8 and includes text property information such as color, attributes (bold, italics, underscore), style and size as well as a large number of extended control codes. Watch my video called "ϕ Tutorial 1: UTF-8 vs. ΦText Byte Stream Encoding File Efficiency". I do not yet have a video explaining the actual encoding.

[@byte_dance]

Brilliant explanation!!!

[@kodexe3298]

Thank u sir, u are way too good at teaching

[@XXRicardoXX2010]

Nice work, thank you so much. That was exactly what I needed :) But one question: If you have the number e.g. 927, you have used an information table to see how big is the last code Point. Is there a fast mathematical way, and I mean a really fast and easy way, to find out how much bits has the next byte and its associated Code Point?

[@angolabharathi486]

Rtfycycgvg

[@justcurious1940]

convert it to binary and u will know exactly how many bits u need to represent it in memory

[@justcurious1940]

thank you brother u are an amazing teacher

[@MrAgent00i]

Very Informative!

[@Boom_bata]

thank you so much for simple explanation

[@jellymelly829]

This is a great logical easy-to-follow video. Thanks very much

[@dhananjayapandau]

thanks sir !! Great explanation ..

[@abdelrhmanahmed1378]

The reasoning why we put marking bit for the countation bytes doesn't add up , why we simply know that this countation byte if not no marking bits are present and if there hence it leading byte

[@adrianserrano6827]

Fascinating video. Thanks!

[@tcbetka]

No problem, glad to be of help. Just finishing your other videos--great stuff. You might want to fix the titles though. The "part 2 of 3" stuff, I mean. It seems that you have, for the 5 numeric storage videos, one "part 1 of 3," two "part 2 of 3," and two "part 3 of 3." I ended up using the dates you uploaded them to keep them straight and go in order--and that worked fine. Anyway, thanks again for all your effort on these. VERY helpful!

[@starc0w]

Great! Thank you very much!

[@vrbilgi]

Thank you man its really helpful for me.

[@minhajansari8272]

The best explanation on the entire internet on utf 32, utf 16 and utf 8 is by this guy

[@arpit280392]

very good explanation......thanks a lot :)

[@181Ravikiran]

how are fonts displaying on screen?? when is that video coming? Thanks a lot

[@Goonzilla1102]

excellent, appreciated!

[@dizauvi]

Yeah sure. I started off thinking that it will be a 3 part series, but the video length increased to the extent that I had to break it up in more parts.

[@abdulmalik5852]

excellent. By the way, what's the animation tool you use for this? Is it powerpoint?

[@JAIGANESH-gd3qj]

i appreciate your work was intutive

[@overunityinventor]

Subscribed, very very very nice videos, all three.

[@eeeekkkk783]

very clear explanation. thanks for your contribution.

[@nishiths9228]

very good explanation

[@monashchhetri2091]

Wow !! Sir its a great video. Please keep adding new contents to your channel about the Computer Science stuffs especially with respect to that of the B.Tech degree in INDIA. As we all know that the quality of Education in PRIVATE ENGINEERING COLLEGES are not up to the mark in here. So with a great instructor like you who is from IIT and have such a huge years of Experience in the Corporate World in Computer Science, your content would really be a great asset to all the students. Thank You.

[@tcbetka]

Very helpful 3-part set! Thank you very much for your effort. The only thing that confused me was your description of little- vs big-endian. Basically, your slide seems to indicate that it's opposite of how it is represented on Wikipedia or the other sites I've seen it explained online. Off to watch your videos on storing floats!

[@sc5shout]

I did not exactly understand html part. You said that if a text is asci and using utf8, a browser will easly display the text, but if the text is e.g. chinese, the browser will not display the text correctly. To display it correctly, the browser should use utf8 (it also used utf8 to asci) and a problem is fixed. The browser used utf8 anyways for asci or chinese, though. I have watched this part 5 times and still cannot get the point. I am sure that I did something wrong. Could you explain it to me, please? Also, I am writing my very simple GUI library in c++ and I want to display different languages. I have found a github example that shows how to use unicodes with freetype (it is a library to read .ttf, I am also using it). Author wrote there that freetype uses unicode as glyph index, so we have to convert it to utf32. Why is that? Why I cannot use utf16 or even utf8 and use multibyte if more space is needed? gist.github.com/er91/e4f8dd352ad6f01a8922.

[@mynameisGYAN]

Hats off. 🙏🙏👍👍

[@gregwoolley]

Excellent.. thank you!

[@rahulgannerlla]

Great Explanation

[@TonyinFL]

Great job!

[@jitu999]

Very Helpful 3-part set, can you do a tutorial on latin1 charset and ISO-8859 family ? how it is different from ASCII and unicode?

[@angurajankathiresan6096]

excellent explanation

[@edwardgrabczewski]

Excellent!

[@dizauvi]

bits marked as x's is where the binary code point data goes

[@nimbostratue]

excellent video

[@MrAnyzen]

Awesome 👏

[@YaJohny_]

The legend

[@thrupthishetty896]

nicely explained

[@gyandhungana7528]

Excellent !!!! you seem to be simply crear with what you say...!!

[@SukeerthiAdigaG]

Good work!!

[@branislavasandrihtodorovic5901]

thank you! your explanations are so clear and detailed, I've learned a lot :)

[@nguyenhohai88]

thanks sir nice tutorial

[@choudharimanasi]

Very useful video....

[@kkssw]

Thank you!

[@vilayatkhan331]

Phew.. I finally get it! Thanks :) You got a subscriber

[@sanmaro91]

thank you!

[@kalpanadevi8738]

Amazing

[@harshavardhans4681]

explained in an easy manner

[@dizauvi]

You are right. Can't believe how I missed that. Thanks for pointing out. I will fix it ASAP, starting with a note there.

[@bitcoindaddy748]

very good video

[@horatioredgreenblue2130]

Thank you