5. The music has started. Teacher, welcome to the Excel lecture. I want to learn how to input special characters in Excel, so I invited a close friend. We are newbies, and the teacher asked me how to input special characters in Excel. I really like it when I receive a question, so I shared it with my friend. Now, our teacher has become our 17th subscriber. So, from now on, I will try to learn about special character input through this lecture. Also, I want to try something different, which is often used in my YouTube comments lately. In this case, it's about using special characters in Jiyoon's code. Before Unicode, there was ASCII code. Let's find out the ASCII code values through Excel functions. And now, let's talk about Unicode and how to encode Unicode, like UTF-8, a lot.

I suggested you to see it, but you couldn't do it well for 9 minutes. So, let's look into the differences between these two, and through the Excel's Unicode function, let's extract the Unicode value for the current cell, and then use that value to extract characters again. I will discuss these contents. First, let's look into special character input. Special characters can be entered by typing a consonant in Hangul input mode and then pressing the Hanja key. When you visit the special characters, you can input shapes. These are commonly used and below you can find these shapes. Also, commonly used is the symbol ᅣ which is often used when entering the circle character, and similarly, I use it a lot when using the symbol ᅩ. I can't explain each one individually, but if you look here, there are various special characters corresponding to runes, so please take a look. If you scroll down, you can also enter Japanese.

It is possible. You can enter special characters as needed. This file will be provided at the top and bottom of the screen, so please download and use it. Nowadays, many people use YouTube tech a lot, starting from number one. Let's talk about the emoticons. Now, we mainly press the keys at the scooter office and type a period. When you call up this window, you can see the same emoticons. On the far left, it shows the recent ones used, then there are smileys, animals, and various other things, so you can select what you want to input. You can even change the skin color of a person's face. Congratulations and related things like food, transportation, and keys are arranged like this, so you can enter what you need. Like hearts, there are cute things in the 4th edition.

If there are many choices like this, unfortunately, in applications such as Notepad or Excel, color support is no longer available, so input in color is not possible. However, when executed in applications with color support such as web browsers or Paint, it is confirmed that it will be displayed beautifully in color. Let's revisit this issue once again. When you look at the side, it was called Kao, but it's actually an emoticon. Also, regarding emoticons, if you look here, you can see various emoticons such as recently used emoticons, classic emoticons, happy emoticons, greeting emoticons, acting cute emoticons, sad emoticons, surprised emoticons, and more, so you can use them as needed. Let's just try entering something simple in this classic port once again.

I will do it. Well, at the very end of the title, there are keywords. Since there are many overlapping characters with special characters now, you can enter them from the special characters or enter them here, whichever is more convenient for you. It may not be well supported. Now, what you need to know here is that if there is a character a and then the character 가 next, each of these will be represented by a single code value. In the case of emoticons, it will probably use three code values, but the rest will each have their own values. Regarding this, we will handle it in Unicode, but before dealing with Unicode in the code, there was ASCII code. Let's take a look at the ASCII content first. ASCII code is described as the U.S. standard code for information exchange. So, with our seven bits.

Now, we have unfolded one character. The number of combinations that can be expressed comfortably with 7 facts is understood to be 127, so we can assign characters up to 127. In the first column, you can see characters from 0 to 30. These are not actual characters. I will explain yesterday's experience. So, here and there, you can turn the page, press Enter, or press the Tab key, etc. These are experiences that users enter. Starting from 32, now for special characters, for example, in the case of 32, pressing the space key corresponds to 18, which is written in Jeju language. When you press 0 on the keyboard, internally, it is actually 17 that is input, not 18. Similarly, for special characters like '태운 짜이' (taeun jjai), it has a code value of 65, and '소문 짜인' (somun jjain) has a value of 97. So, when we sort in the file manager, you will see 'a' first.

You can organize it by looking at the code value. From the computer's perspective, when I press 'a', it doesn't recognize it as 'a' but as the number 65, recognizing it as an even number. ASCII code started with 7 bits, and from the 1960s, it began to develop and later expanded to 8 bits. So, with the extended ASCII code, it can express characters up to 255. In order to display these characters, I used a function called CHAR in Excel, which returns the character corresponding to the code value. As you can see, from 0 to 117, there is no difference in ASCII code values. However, when you look at some characters from 118 to 255 in the extended ASCII code, from 118 to 159, they came out as spaces.

Yesterday, if you consider it as a space used in a text message, from 118 to 250, there has been a slight change in this code, not the original extended ASCII code. There is a method called AGGA GR Team Method. You need to press the numbers on the keypad and return to the state where number input is possible. Especially in the state of holding down the left Ctrl key, if you write like this 6 here, most likely 짜이 will be entered. Let me try it myself. Press the Alt key and then press U and it seems that 게임은 is entered. Similarly, if you press the Alt key, then type 662, 피 will be entered. Then, press the Alt key again, type 48, and release your hand, 영 will be entered. Next, press the RTK again, type 쿠 10 치지, and when you select it, 소문 짜이 will be entered. In this way, you can now retrieve the ASCII code values. The one I use the most is Alt.

183, and when you want to call a point in the middle now, the subject of yesterday and now is computer information. After pressing Alt 183, if you write 터 there, you can use the middle dot like now to indicate the subject. If you want to remember the bullet more, you can press the Alt key and then press 133 to bring up the Alt + Enter table. You can also enter numbers up to 255 here, and when you want to confirm by entering a number larger than that, you should edit the registry keys. However, it is too broad to explain that part, so I will skip that part. Please look it up on your own. This time, we will look into Unicode, which allows you to handle all characters in the world easily. The Unicode started with 2 bytes at the beginning, so even though the whole world is covered, if it's a 2-byte, it's 16 squared, so 65536, but still.

I thought it would be convenient and that all characters would be included, but when I looked closely, some characters were missing. So, with the upgrade of Unicode, now it is represented in 4 bytes. Officially, it is referred to as a 30-bit character set, but so far, it is known that all characters can be represented within 21 bits. There is plenty of room for flexibility. When we think about representing a character, if we say it is done in 4 bytes, in the case of ASCII, which only requires 1 byte, there is a waste in the system. To express a character, it is necessary to use from 1 byte to 4 bytes. In the case of ASCII, the first bit starts with 0, so when it starts with English, it recognizes ASCII code and processes it in 1 byte. If the bit value starts with 110, it means it processes 2 bytes, reads up to the second byte, and continues.

It's a way of representing one character in bytes. In this case, three bytes are grouped together to represent one character more conveniently. If it's 1111 0, you can think of it as a method of representing it with four bytes. To understand more specifically, there is a site called Online Unicode Viewer. Let me show you here. When you look here, it says UTF-8, click on it, and let me write 'a' in Unicode. Now, if I write 'a' here, when it's converted to UTF-8, it will be represented as '97,' which is a 16-digit value, and when converted to decimal, it will be 65. This is how it's processed in one byte. The same goes for '0,' which was 48 earlier, but when converted to hexadecimal, it will be 30, and when converted to decimal, it will be 48. This way, when we input characters like Korean, it originally has a code of '2c 00' in Python.

If you have it, when you see it now, you can see that it is saved in 3 bytes. When you see the last letter in Korean, 희 (Hee) or 용 (Yong), it also saves 3 bytes. In the case of Korean, when using UTF-8, one syllable generates 1 byte. However, when we process the leaf, we usually convert it to UTF-8, so most encodings end up using UTF-8. If a document contains a mix of English and Korean and there is a lot of English, if you have a situation where there are many English characters, you can save storage space a bit. Let's try entering 이 뭐지 (What is this) once. In my case, you can see that everything is processed in bytes. So, depending on the code range, you can see that UTF-8 is processed variably. Let's try entering a special character. As for special characters, you can see that they are processed in 3 bytes, depending on the type of special character.

You can think of it as different. Now, let's take a look at UTF-16 for a moment. I will try entering 'a' in UTF-16. When I entered 'a,' you can see that 0041 and 2 bytes were processed. For 'a,' it corresponds to one byte in Unicode, and when saved in UTF-16, it is saved with these bytes. When entering '가' (ka), you can see that more space is allocated compared to 'a.' I'm not sure about the pronunciation of '희영 이희호' (Hee-young, Hee-ho). Likewise, you can confirm that the bytes are being saved for the third '가' (ka). Lastly, let's take a look at UTF-32. When entering 'a' in UTF-32, it always requires 4 bytes for processing, which leads to some space waste. Naturally, if it's 4 bytes for 'a,' it will be the same for '가' (ka). To summarize, you can consider Unicode as a table assigned to each character worldwide for one-to-one correspondence.

There is an encoding method called UTF-8 that saves Unicode, and there is an encoding method called UTF-16 and another coding method called New Camp 32. In particular, in the case of UTF-8 that we use, the length varies depending on the code range. Now, through Unicode functions, we will look at Unicode values. First, let's write the uppercase letter 'A'. We will try writing '2' as well. Next, let's try '한' and '영'. Shall we look at the hexadecimal value of '한' again? Oh, I forgot to mention earlier that the actual representation varies depending on the operating system. When it comes to this side, my Unicode 2, Unicode table is displayed. If you look here, you can see that it varies significantly from one operating system to another.

So, you sent me this picture to think about, and this is how you could also receive it. So, when you look here, there is a z2 script shown, and according to this disk option, I created icons for each operating system. You can see that the icons have slight differences. Some are quite different. For example, the shape of the Hi icon and the Year icon are different, and the shape of the Eye Car icon also varies depending on the operating system. Let's go back to the Excel function. Now, let's try entering a special character. Finally, let's input the percentage at the first position. If you write 'Eunyo', there is a character, and then there is Unicode. Let's select Unicode. We will check the code value for the denominator and you will see the result is 60. How do we represent hexadecimal numbers?

Because our code values are getting too long, in Unicode, we express them in hexadecimal and proceed with 'u+' followed by the hexadecimal value. Now, let's try converting this code into a 16-bit floating-point number. So, let's see, for this value of 7F3D, do you notice something? Let's copy these two blocks below. As you can see now, for 2 bytes, we have values ranging from 0 to 65535. Here, in cases like this, we can confirm that it has a 3-byte value step. When converted to hexadecimal, we can easily confirm a 3-byte value like this for responsiveness. Now, as you can see, we used to have ASCII code values, and you can also confirm a 1-byte value like this for 1 byte. For special characters like '*', you can see that for special characters like '*', it requires 2 bytes for processing. This way, through the Unicode table, we can confirm Unicode values using the Unicode function, and you can copy the code values.

On this side, it says hexadecimal value, I will put it down. When you paste it, you can't just paste it, press the right button and select it from here. It says Bucheon Opie, so let's bring it in as a value. Now, the same number value has been entered here. Now, this time, Jae-yoon's character, you briefly saw earlier, commonly looks at the character through ASCII code to see what problem this code value might have. Oh, this won't work. Since it's hexadecimal, to convert it to decimal, you need to send it to Hex to Decimal, call the opposite function, and now it says it's printed here. Since the fo button doesn't work, I'll just write it directly. I said to press the Enter key twice, and you can see the letter 'a' appearing. Through Unicode, you can find out the code value, and through the UI character, when we have that code, we can see the character.

You can think of it as being able to check. Now, let's organize. Through today's lecture, we learned that each character has an individual code value. Initially, we could see that Unicode evolved based on ASCII code. Although I didn't explain that in today's lecture, there are numerous codes in between. In order to express Korean, it was impossible within the 1-byte range, so we started using 2 bytes to represent 3rd-grade Chinese characters. There are two methods, combining and completing, to overcome this limitation. There have been many conflicts over this issue. Similarly, in Japan, they also combined two bytes to make Japanese more convenient. China did the same, as well as Vietnam, France, and other countries. Each country has its own way of expressing characters, conducting research, and creating codes. As a result, various conflicts and services like the contrast of the world emerged.

When it starts, if there are multiple languages in a document, it becomes impossible to express it. So now, as you might have seen earlier, research on Unicode has started. Even though thousands of people around the world speak different languages, there are various ways to represent characters in computers. It is almost unified through Unicode now. If you think about it that way, today's lecture is a bit challenging, and I feel like I have prepared this explanation with many shortcomings. If there are any incorrect points, please leave a comment. When you leave a comment, please include your name or special characters so that I can recognize it. I feel like I might miss it. Thank you for listening to the lecture today, and I will see you in the next class. Goodbye.

Unicode, UTF-8, ASCII, 이모지, 특수문자 입력

Unicode, UTF-8, ASCII, 이모지, 특수문자 입력

Scripts