 
<translate> Ezubere ya maka ndakọrịta azụ na ASCII. A na-eji koodu ole na ole na-eji obere ọnụọgụ ọnụọgụ, nke na-emekarị ka ọ na-emekarị, jiri obere bytes. Ihe odide 128 mbụ nke Unicode, nke kwekọrọ na ASCII, na-eji otu octet nwere otu ọnụọgụ abụọ dị ka ASCII, nke mere na ederede ASCII dị mma bụ Unicode UTF-8 dị mma. Ebe ọ bụ na ASCII bytes anaghị eme mgbe ị na-ezipụ koodu ndị na-abụghị ASCII na UTF-8, UTF-8 dị mma iji mee ihe n'ọtụtụ mmemme na asụsụ ederede nke na-akọwa ụfọdụ mkpụrụedemede ASCII n'ụzọ pụrụ iche, dị ka "/" na aha faịlụ, "\" na usoro mgbapụ, na "%" na printf.  Ebee ka ihe odide ASCII dị na koodu UTF-8? Azịza ya bụ 128 mbụ <eng> It was designed for backward compatibility with ASCII. Code points with lower numerical values, which tend to occur more frequently, are encoded using fewer bytes. The first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single octet with the same binary value as ASCII, so that valid ASCII text is valid UTF-8-encoded Unicode as well. Since ASCII bytes do not occur when encoding non-ASCII code points into UTF-8, UTF-8 is safe to use within most programming and document languages that interpret certain ASCII characters in a special way, such as "/" in filenames, "\" in escape sequences, and "%" in printf.

Where are the ascii characters found in the utf-8 code points?
The answer is The first 128 