Kankana

Рет қаралды 2,365

Schwar

Күн бұрын

Пікірлер: 27

@declup Жыл бұрын

"Because I could. That's why." -- The hodgepodge of human civilization in a nutshell.

@セキひろあき Жыл бұрын

Not gonna lie I wasn't even mad at the end.

@aruba1911 Жыл бұрын

I died when you said "invented by me" hahaha I wasn't expecting that, it's so interesting. I hope you can continue making more videos, I love them so much✨

@Cjco102 Жыл бұрын

Also there’s a push in Bolivia for Aymara to be written with Hangul as well

@heironic8547 9 ай бұрын

As soon as I started learning Japanese and conjugation I thought of doing this. Glad someone already thought this out

@impendio 2 ай бұрын

This both proves and refutes every attempt of switching japanese to hiragana and stuff

@D__Ujjwal 2 күн бұрын

I always wondered this that koreans created hanguk after interaction with brahmi script , but japanese didn't use that and went for hiragana\katakana type system

@FieldLing639 Жыл бұрын

But can you make it work for Ubykh is the question

@TrueSchwar Жыл бұрын

Challenge accepted

@user-sl5cl5xq4o 4 ай бұрын

Would 行く and 行う not become the exact same?

@undrew_yw Жыл бұрын

interesting idea. could the mixed script distinguish between words like 戻す/戻る where the only difference is the final consonant of the verb root?

@TrueSchwar Жыл бұрын

In the mixed script with my standard, maybe, as I'm thinking giving each word an independent but related kanji. In mixed script with current standards, no, they'll be distinguished by context only.

@impendio 2 ай бұрын

This is kind of why there has never been a good japanese reform, more than other languages with tons of loan words and derivatives, japanese has _so_ few phonemes and _too_ many homophones, that kanji is kinda needed. You’d say bUT ConTeXt, and that is the catch, spoken japanese and written japanese are kind of two separate languages, and that is the realization, its been so long that you cant separate one from the other and everything has been normalized, but it still works like code switching and spanglish, but with two languages with vastly different ancestries and structures, nowadays its is kinda like three languages stapled together with all the modern european loans and wasei eigo.

@popeyeolive-vj1qg Жыл бұрын

You had a such a great idea. As a person who is japanese native speaker and korean learner it will work enough but why did you choose ㅌfor D, ㅍfor b, ㅋ for g ,어 for お and more You mess it up voiceless sounds and voiced sounds?

@TrueSchwar Жыл бұрын

I originally planned for ㅃ ㄸ ㄲ ㅆ to be the voiced equivalents, however ㄸ and ㅆ can't be placed as a Batchim in typing. So the only other option was to use ㅋ ㅍ and ㅌ. Since ㄱ ㄷ ㅂ are the basic characters, I used them for the voiceless "basic" stop consonants. 어 is used for お only because of 워/wo digraph.

@popeyeolive-vj1qg Жыл бұрын

@@TrueSchwar Thank you for response I understood your opinion This is one of the best way to write japanese hiragana and katakana are easy for japanese but for learners these are little bit complex Japanese language +Korean writing system is such a nice

@poproporpo Жыл бұрын

Agreed. Most adaptations I've seen have opted to use ㄱ for 'g' and ㅋ for 'k' as approximations instead.

@georgerussell2947 Жыл бұрын

why not 오 for /o/? and 위 for /wi/? also using ㅂㄷㄱ for voiced consonants and ㅍㅌㅋ for voiceless consonants may be more intuitive since [b] [d] [g] are allophones of ㅂㄷㄱ

@TrueSchwar Жыл бұрын

copied from another comment. I originally planned for ㅃ ㄸ ㄲ ㅆ to be the voiced equivalents, however ㄸ and ㅆ can't be placed as a Batchim in typing. So the only other option was to use ㅋ ㅍ and ㅌ. Since ㄱ ㄷ ㅂ are the basic characters, I used them for the voiceless "basic" stop consonants. 어 is used for お only because of 워/wo digraph.

@thondertv Жыл бұрын

@@TrueSchwarI would like it more if it uses ㅂㄷㄱ for the non-aspirated consonants and ㅍㅌㅋ for the aspirated consonants. Because in my opinion, ㅂㄷㄱ is for voiced consonants, ㅃㄸㄲ is for non-aspirated voiceless consonants, and ㅍㅌㅋ is for aspirated voiceless consonants.