hangil131

I'm not sure inertia is correct for this. I think the reason is there are no needs for non-english charactered programming languages. Let's think about there are perfect program language made with Korean. If you are programmer, then you already know program languages made with English even if you are not a native speaker. Now you have to learn "New" program languages. You are native Korean so maybe have some advantage but it is still new thing. If you are not programmer yet. You have to learn program language, in this case most users are already using traditional program languages so you can't skip Python or C or Java.

It is "韓(Han)" not "汉(Han)" just same pronouns. Currently, The short name of "Korea" in korean is "한국(Hanguk)" it means "Han contry" so all the identity of korea is in "han"

Hello, interesting project. I’m a native Korean speaker, so I wanted to share a quick perspective from Korean.

Nouns translate fairly naturally, but standalone verb commands in English need more care. In English, a verb like "find" can stand alone, but in Korean a verb usually needs an ending, and different endings can sound quite different or awkward depending on context. For example, "find" could become 찾다, 찾기, or 찾음, but those are not interchangeable.

Plural forms are also tricky. English distinguishes strongly between singular and plural, but Korean usually does not. Explicit plurals like “단어들” often sound unnatural unless the individuality of each item is important.And it feel same with "단어목록"

Overall, this is a very interesting project with real potential. I think it could become even stronger if it considers the structural differences between English and Korean, rather than treating it as simple keyword substitution.

I’ve been working on a project called *Mimesis Protocol* — a structured semantic representation model for natural language.

The basic idea is that an utterance often has a gap between its surface form and its actual function in context. For example, a sentence like “Do you know what time it is?” may look like a question, but pragmatically function as criticism, pressure, or a prompt for reflection.

Mimesis tries to represent an utterance not just as text, but as a structured object with separate layers for: - `core`: semantic meaning and emotion - `will`: communicative purpose and influence - `flow`: discourse framing / progression - `exp`: surface realization

I’ve put together: - an English/Korean whitepaper - a schema spec - a working interactive demo

Still early, but I’m interested in whether something like this is useful as an intermediate representation layer for LLM systems, agent workflows, or discourse analysis.

Repo: https://github.com/hangil131/Mimesis-Protocol Demo: https://chatgpt.com/g/g-681be5f72cc4819191c2b12c9d89b336-mim...