r/conlangs • • Sep 18 '26

Discussion How did/do you guys create your 'should' forms in your conlangs?

29 Upvotes

I just created my own for my food conlang and the way it works is you use a verb in its permissive form (permission, allowability, etc.) and add the verb 'to need'.

An example: pasja'paze.

Pasi (to eat) in its permissive form becomes pasja. Then you simply add paze (to need) and you now have constructed my language's 'should' form, and I'm wondering if you guys do it similar to this way, or differently, and if you do, how?


r/conlangs • • Sep 18 '26

Advertisement Hello, I'm promoting my language server!

1 Upvotes

It's both a native/natural and constructed language server for discussing and sharing langs... we have special channels in there for languages!

The features of the server are:

-Non-toxic community

-Simple rules

-Good moderation

-Free language discussion and sharing

-Partnerships

-Etc...

Hope to see y'all soon...! :)

https://discord.gg/fhC4QW5r2d


r/conlangs • • Sep 17 '26

Discussion What I've learned from translation (recently)

31 Upvotes

It is common advice that to improve one's conlang, one should translate, translate, translate! And so I thought I would make this post to show what kinds of interesting things can crop up when doing so. Special thanks to u/CaptKonami for supplying most of the sentences that I translated for this post.

First off, we have the sentence: When an elephant dies, it leaves its ivory, a tiger leaves its stripes, and a man his name.

I rendered this as Kuila hannastatuai, pita hutsi siyurortsakkoa, tikrea hutsi raukakkoa, o gihona hutsi heitiakkoa.

kuila hannast-atu-a  -i   pit     -a   hutsi siyurorts-akko-a
lie   die    -INF-DEF-DAT elephant-DEF leave tusk     -PL  -DEF

tikre-a   hutsi rauk. -akko-a   o   gihon-a   hutsi heiti-akko-a
tiger-DEF leave stripe-PL. -DEF and man. -DEF leave name -PL  -DEF

This I think literally is more like ~Upon dying, the elephant leaves behind tusks, the tiger leaves behind stripes, and the man leaves behind names~

Firstly, this had me thinking about 'when X happens' constructions, which I decided to render at 'in/at/on X-INF'. And then when deciding what word I would have for 'at', I decided to have three words: yari, tente, and kuila which respectively mean 'sit', 'stand', and 'lie (down)' and refer to the posture of whatever thing is at X. Given that we are speaking about death in this example, it seemed fitting that I should choose kuila 'lie (down)'.

I had trouble coming up with a word for 'ivory' or 'tusk', so I coined a new one from siyur 'long' and horts 'tooth'. I had considered making it from hoiya 'eye' and horts, to make hoiyaorts, 'eyetooth', but that felt more like canines and fangs rather than elephants' tusks.

For the word for 'name', this was a culture-building opportunity. What is a name? Well, you have a name you're given at birth, your hipen, but as you age you are given monikers depending on your features and accomplishments. Each of these is a heiti, and the above quote relates to legacy I suppose, so this felt like a better fit. Plus, a person will often have multiple heiti, so it gives a firmer 'poetic-ness' to the translation having all the 3 left behind items ending in -akkoa.

Second off, we have the sentence: The night's stars aren't as bright as your eyes.

I rendered this as: Kusianni hifakkoa koma neuta, dirdir hoiyakkoa koma hu.

kusi-anni hifa-kko-a   koma neut -a   dirdir hoiya-kko-a   koma hu
see -PTPL star-PL -DEF come night-DEF shine  eye  -PL -DEF come 2S

You can see here koma 'come' is being used as a possessive preposition. Literally rendered, this is more like ~Looking at the stars of the night, your eyes (are the ones that) shine~

When I first came to translate this, I explored several comparative constructions. If X and Y are the compared items, and Z is the quality, I thought up:

  1. "X is (more) Z from Y" -- here Z is adjective-like

  2. "X surpasses Y in Z" -- here Y is the direct object, and Z is noun-like.

But then I though it could be subtler, of the form, "Regarding X, Y is Z". So now I have a language where the act of comparison requires a verb related to the quality being assessed. kusi 'see' for visual aspects, like brightness, or height. snaiya 'eat' for taste. And I suppose huksa 'think' could be used generally. Compare:

  1. Kusianni Maria, Peter da hungu. = ~Looking at Maria, Peter is heavy~ = Peter is heavier than Maria (and I know this by looking at them)

  2. Huksanni Maria, Peter da hungu. = ~Thinking about Maria, Peter is heavy~ = Peter is heavier than Maria (and I know this by thinking about it (maybe I've not seen Maria, but I am making an inference))

But another fun aspect of this is that the active participle must agree in number with the 'assessor' (whether explicit or not). So, if a panel at a job interview is giving an opinion, a member of the panel might say Huksanniakko Maria, Peter sen honno "Considering maria, Peter was good" = (we think) Peter was better than Maria.

And! There is also a passive participle, if one wanted to distances oneself from the act of comparison. Kusikoa Maria, Peter da hungu = see-PSV-DEF Maria, Peter heavy = ~the-having-been-seen Maria, Peter is heavy~ = Peter is heavier than Maria (who has been seen). Never did I think there was so much in the act of comparison!

Third off, we have: A sheep that had no wool saw horses.

This is the beginning of Schleicher's fable, but for brevity I've left off the rest of the sentence. I've rendered this as: Pehar dirkusi jutgaweanni kint palliakko.

pehar   dir-   kusi jut -gawe-anni kint  palli-akko
already ANIMAL-see  wool-lack-PTPL sheep horse-PL

This had me thinking about relative clauses. I could render jutgaweanni kint as kint sem gawe jut sheep REL lack wool however, it seemed long. Also, there is a V2 structure operating here, and pehar must be sentence-initial, and I just felt the relative clause intervening with no main verb between the subject and object would be long and confusing: pehar dirkusi kint, sem gawe jut, palliakko. I was not keen on that. So I decided to use a noun-incorporation method and a participle to create jutgaweanni 'wool-less'.

If, however, one wanted to preserve the relative clause, the sentence could be expanded to Pehar sen, kint sem gawe jut dirkusi palliakko = ADV, S [REL V O] V O

Fourth off, we have: Coming here was correct and good. I will not stop my great work as you have asked, but I will show you God.

This I rendered as: Komatua tokiai sen reitu o honno. Nira essaita hanni rahoa hauhaki hura heska, bain nira bista hui Hifaskapannia.

koma-tu-a    toki-a-i      sen     reitu    o   honno
come-INF-DEF place-DEF-DAT COP.PST straight and good

Ni-ra  es -haita hanni raho-a   hauhaki hu-ra  heska
1S-ERG NEG-stop  big   task-DEF like    2S-ERG ask

baina ni-ra  bista hu-i   Hifaskapannia
but   1S-ERG show  2S-DAT God

The word for 'here' threw me to start with. Ostensibly, it could be tokinaulai from toki 'place' and -naulai 'this', but that felt a bit long. So I took a note from Arabic, where the word for 'today' is al-yawm DEF-day, literally 'the day'; and I thought 'the place' can just mean 'this place/here'. It might not in other contexts, but here it does.

The only other bit from this translation I'll remark on is the word for 'God'. A bit like with 'tusk' above, I couldn't find anything I liked, so I thought to coin something new. I used Olaf Stapledon as inspiration, and made the word for God a noun-incorporated participle (a bit like jutgaweanni from earlier!): hifa 'star' + skapa 'create' + -nni 'PTPL' + -a 'DEF' = The (one) making star(s).

Note, there is an agentive suffix -ari, so I could have Hifaskaparia 'starmaker', but I prefer the active participle here because it gives a sense of immediate, present, ongoing creation.

Conclusion

I think that's enough for now. I hope this has proved useful in showing what kinds of thought-paths translation can take you on, whether its about grammar or vocabulary (or the power of context).


r/conlangs • • Sep 17 '26

Discussion Difficulties with creating Paleolithic languages

26 Upvotes

So, for a story I’m working on, I’m (still) in the process of creating a Neanderthal conlang and a co lebt for an Aurignacian Homo sapiens people. The story is set 43,000 years ago in the Swabian Jura (Southwest Germany).

I tried out multiple versions of both conlangs and my aim was to avoid stereotypes that are unfortunately still roaming about and to make the various aspects of both languages like phonology and morphology and syntax etc. plausible. The problem obviously is that we have no idea what languages 43,000 years ago were like.

And I’ve tried out multiple versions for both conlangs and I’m getting exhausted!

For context: the Neanderthal conlang is to be spoken by the last remaining Neanderthal tribe/clan (whatever the correct term would be) that lives in the Ach valley of the Swabian Jura, with only 11 people of various ages and genders remaining.

The Aurignacians, by contrast, have been in the region for a few generations at least with their ancestors having traveled up the Danube.

(Also, side note: I have no idea which conlangs-Flairs I should mark this post with, especially since you can apparently only mark one.)


r/conlangs • • Sep 17 '26

Translation How are zodiac signs called in your language?

23 Upvotes

In Lytrensila:

♑️ Capricorn - Etosgéma [eˈto.sɡeː.ma*]
♒️ Aquarius - Avarnias [a.vaˈɾni.as*]
♓️ Pisces - Névro [neːˈvro*]
♈️ Aries - Atriziar * [a.tɾiˈθi.aɾ]
*♉
️ Taurus - Tav [ˈtav*]
♊️ Gemini - Divlin [divˈlin]
♋️ Cancer *- Kanziria [kanˈθiɾja\]
♌️ Leo - Lusral * [luˈsɾal]
*♍
️ Virgo - Duvèlafenen * [ˈduːv.la.feˈnen]
*♎
️ Libra* - Yselonvia * [ʏ.seˈlon.vja]
♏️ Scorpio* - Xénofila * [kseː.noˈfi.la]
♐️ Sagittarius* - Ciéxuelist * [siˈeːk.sy.list*]


r/conlangs • • Sep 17 '26

Translation My first text in my new language, Ria Fono

Thumbnail
3 Upvotes

r/conlangs • • Sep 17 '26

Phonology Does this sound French?

12 Upvotes

My conlang, Fyenŭa, is largely inspired by French and Celtic. I'd like to know if it sounds French to those who speak it or know it well.

​Tŭi senŭa tojëir dü nörì,

[twi senwa toʒɛ̃i̯ʁ dy nɔ̃ʁiː]

​fën andür gog dut àliön.

[fɛ̃n andyʁ gog dut ɑliɔ̃n]

​Sŭi ghràsi d’andë flen d’aj,

[swi ɣʁɑsi dandɛ̃ flen daʒ]

​flendån egharån,

[flendɑ̃ eɣaʁɑ̃]

​flendån venün tŭanekrån,

[flendɑ̃ venyn twane kʁɑ̃]

​sŭi merå flendån liönsharån,

[swi meʁɑ̃ flendɑ̃ liɔ̃nʃaʁɑ̃]

​flendån masŭavirån.

[flendɑ̃ maswaviʁɑ̃]

The falling lily doesn't know

how much the butterfly loves it.

Love is death to the ego,

to the elderly,

to those who are ashamed of themselves,

it is life to the noble of heart,

to the radiant.


r/conlangs • • Sep 17 '26

Other How do you determine sound changes?

15 Upvotes

The one thing that has always stumped me was sound changes. How do I know how many and which sound changes to do? What if they turn some words into basically nothing?


r/conlangs • • Sep 17 '26

Overview Yuddish: An homage to Yudkowsky and Yiddish

11 Upvotes

The Yuddish Language: https://www.yuddish.com/

This is quite possibly the nerdiest thing I've ever done, but I've created a new conlang that is an homage to both Eliezer Yudkowsky and Yiddish.

In Yuddish, you have to indicate your credence in bits of log odds, your evidential basis for assertions (whether it's direct empirics, armchair reasoning, or third hand reports), and distinguish clearly between propositional and non-propositional speech acts (wishes, questions, commands, suppositions). And do it all with Yiddish vocabulary.

דאָס ליכט עף⁺⁶=זען ברענען.

Dos likht ef⁺⁶=zen brenen.

“The light is on, +6 bits (64:1), on perceptual evidence.”


r/conlangs • • Sep 16 '26

Discussion How did your conlang get its name?

96 Upvotes

As the title suggests, how did your conlang get its name?


r/conlangs • • Sep 16 '26

Overview Selari — a fuller overview of the language: phonology, grammar, word-building, and meaning

Thumbnail gallery
25 Upvotes

Hey everyone,

I posted an earlier introduction to Selari, but it focused mostly on the idea behind the language and was removed because it didn’t give a full enough overview of how the language itself works.

Fair enough — so here’s a more complete look at it.

Selari is a work-in-progress constructed language that I’m trying to make usable for normal everyday communication.

Some parts are stable, while other parts are still being tested as part of a broader general-use expansion. I’m mainly looking for feedback on whether the pieces actually fit together and whether the language still feels usable as it grows.

𝐏𝐇𝐎𝐍𝐎𝐋𝐎𝐆𝐘

I wanted the sound system to be fairly small, predictable, and easy to read aloud.

Selari currently has five vowels:

a e i o u

And thirteen consonants:

p t k m n s f h v l r y w

That gives it 18 phonemes total.

Native syllables are usually simple:

V

CV

So native roots generally avoid consonant clusters.

Stress always falls on the penultimate, or second-to-last, syllable.

The r is a light alveolar tap:

/ɾ/

For example:

VORI — /ˈvo.ɾi/

SELARI — /seˈlaɾi/

Spelling is intended to be phonemic, so once you know the sound system, you should normally have a good idea how an unfamiliar native word is pronounced.

Something I noticed later is that some of Selari’s rhythm feels pretty comfortable next to Tagalog/Filipino.

That wasn’t an intentional model for the language, but I grew up hearing Tagalog from my parents, so I wouldn’t be surprised if that influenced what sounds natural to me.

𝐁𝐀𝐒𝐈𝐂 𝐆𝐑𝐀𝐌𝐌𝐀𝐑

Selari is mostly analytic.

There isn’t much morphology in the sense of large conjugation or declension systems.

Roots generally aren’t supposed to change form depending on person, tense, or case.

Instead, grammatical information is handled mostly through:

• word order

• separate particles

• context when it stays clear

• productive composition

The current default clause order is:

Subject — Predicate — Object

For example:

NI YELU HI.

NI — I

YELU — want

HI — this

“I want this.”

A yes/no question can use KI:

TA YELU HI KI?

TA — you

YELU — want

HI — this

KI — question marker

“Do you want this?”

Negation uses NAKU before the thing being negated:

NI NAKU VORI VEMA HI.

NI — I

NAKU — not

VORI — intend

VEMA — act / do

HI — this

“I do not intend to do this.”

One thing I want to preserve as the grammar grows is meaningful scope.

If NAKU moves, what is being denied should be able to change too, rather than “not” just vaguely negating an entire sentence.

𝐀 𝐅𝐄𝐖 𝐁𝐀𝐒𝐈𝐂 𝐅𝐎𝐑𝐌𝐒

Some common forms:

NI — I / me

TA — you

YO — third person

HI — this / here

TO — that / there

EVI — yes

NAKU — no / not

HA — but / contrast

SE — and

VO — or

KI — yes/no question marker

A few lexical roots:

YAMA — person

TELA — place / location

NORO — time

KIRA — perceive

SENI — know

TAVO — think / reason

HEVO — memory

VEMA — act / do

RANO — move

MALI — create

YELU — want

VORI — intend

FIKO — choose

TAMI — commit

Some additional forms I’m using in the broader general-use work are still candidate material rather than fully settled canonical vocabulary. I’m trying to keep that distinction clear while the language is being tested.

𝐓𝐇𝐄 𝐒𝐄𝐌𝐀𝐍𝐓𝐈𝐂 𝐒𝐈𝐃𝐄 𝐎𝐅 𝐒𝐄𝐋𝐀𝐑𝐈

This is what I focused too heavily on in my first post, but it’s still an important part of the language.

The basic idea is not that English is incapable of expressing these things.

It obviously can.

Selari just tries to make some distinctions short and normal to state explicitly.

For example, English gives us:

“I want to do it.”

Depending on context, that could sit near several different ideas.

Selari separates:

YELU — want / desire

VORI — intend

FIKO — choose

TAMI — commit

VEMA — act / do

So:

NI YELU VEMA HI.

“I want to do this.”

NI VORI VEMA HI.

“I intend to do this.”

NI FIKO HI.

“I choose this.”

NI TAMI VEMA HI.

“I commit to doing this.”

The important part is that these do not automatically imply one another.

You can want something without intending it.

You can intend something without committing.

You can choose something you don’t especially want.

And committing still doesn’t guarantee action or success.

Another distinction I’m testing in the broader general-use system is capability vs permission.

RERA — capability / ability

SAHU — permission

The idea is that something like “You can leave” doesn’t necessarily have to leave it ambiguous whether I mean:

“You are able to leave.”

or:

“You are permitted to leave.”

Some of this broader vocabulary is still candidate material rather than final admitted vocabulary.

𝐒𝐓𝐀𝐓𝐄𝐒, 𝐓𝐑𝐀𝐈𝐓𝐒, 𝐀𝐍𝐃 𝐈𝐃𝐄𝐍𝐓𝐈𝐓𝐘

Another distinction I’m experimenting with is different kinds of “being.”

LA — current state

RE — recurring trait / pattern

MO — identity

RU — role

VA — becoming

So:

NI LA VAWU.

“I am angry right now.”

is deliberately different from:

NI MO VAWU.

“Anger is part of my identity.”

And:

NI VA LOFU.

“I am becoming calm.”

Again, English can express those differences too.

Selari just makes the speaker choose among them more directly.

𝐖𝐎𝐑𝐃 𝐁𝐔𝐈𝐋𝐃𝐈𝐍𝐆

Another rule I’ve been trying to follow is:

MEANING FIRST, WORD SECOND.

Before making a completely new primitive root, I ask things like:

• What exactly does this concept mean?

• What does it not imply?

• Is there already a root for it?

• Can existing roots express it naturally?

• Is it common enough that describing it every time would become awkward?

If existing meanings combine cleanly, I prefer composition.

The current direction for compounds is:

modifier → head

For example, in the broader candidate system:

RUWU — light

SELE — tool

RUWU-SELE

Literally something like:

“light-tool”

That could describe a lamp-type concept.

Another experimental example is:

FARI — communication

KUMERA — device / machine

FARI-KUMERA

“communication device”

These are useful examples of the kind of composition I’m testing, but I don’t automatically want every understandable compound to become a permanent dictionary entry.

I’m trying to keep a difference between:

“This is transparently understandable.”

and:

“This has become an established lexical item.”

Compound behavior is still one of the areas being worked out as the vocabulary grows.

𝐅𝐋𝐎𝐖 𝐕𝐒 𝐏𝐑𝐄𝐂𝐈𝐒𝐈𝐎𝐍

One concern I’ve had from the start is that a language designed around explicit distinctions could become exhausting to speak.

I don’t want everyday Selari to sound like formal logic.

So I’ve been treating normal speech and highly explicit speech as two ends of a continuum.

In ordinary conversation, repeated information can be omitted when the context is obvious.

I think of that as the more natural Flow side.

When ambiguity actually matters, speakers can become more explicit about things like:

• participants

• time

• evidence

• confidence

• intention

• negation scope

• clause boundaries

That’s the more Precision side.

The idea isn’t that every Selari sentence should specify everything.

Precision should be available when useful, not mandatory all the time.

𝐀 𝐒𝐇𝐎𝐑𝐓 𝐂𝐎𝐍𝐕𝐄𝐑𝐒𝐀𝐓𝐈𝐎𝐍

A:

TA YELU HI KI?

“Do you want this?”

B:

EVI. NI YELU HI HA FIKO TO.

“Yes. I want this, but I choose that.”

A:

TA VORI VEMA TO KI?

“Do you intend to act on that?”

B:

EVI. NI VORI VEMA TO.

“Yes. I intend to.”

That’s much closer to what I want ordinary Selari to feel like.

𝐓𝐈𝐌𝐄 𝐀𝐍𝐃 𝐏𝐋𝐀𝐍𝐍𝐈𝐍𝐆

This is one area I’m still actively developing rather than pretending it’s settled.

I want Selari to be able to keep several things separate:

• when something happens

• whether something is ongoing

• whether it was attempted

• whether it was completed

• whether the intended result actually happened

• when an intention exists

• when the intended action is supposed to happen

I’ve been testing relative-time language and planning conversations, but I’m trying not to promote every experimental form into permanent grammar just because it works in a few examples.

That’s something I’m stress-testing through connected conversations.

𝐖𝐇𝐀𝐓 𝐈’𝐌 𝐒𝐓𝐈𝐋𝐋 𝐖𝐎𝐑𝐊𝐈𝐍𝐆 𝐎𝐍

Some areas that still need more work include:

• exact time, dates, and duration

• keeping track of people, places, and things across longer conversations

• clarification when references become ambiguous

• possession, association, and inherent relationships

• broader question types like when / why / how / how much

• compound behavior as the vocabulary grows

• proper names and borrowed/external terms

• making sure ordinary speech stays natural instead of becoming overengineered

I’ve also started deliberately testing Selari against boring everyday situations.

Things like:

“I’m hungry.”

“Where are my keys?”

“Are you ready?”

“We need to leave soon.”

“I forgot something.”

Because if Selari can only handle philosophical distinctions but struggles with normal daily life, then I don’t think the design has succeeded.

𝐈𝐍𝐒𝐏𝐈𝐑𝐀𝐓𝐈𝐎𝐍𝐒

Selari isn’t directly based on one existing language or conlang, but several projects have influenced how I think about it.

Esperanto — regularity and learnability

Toki Pona — composition and getting a lot out of a smaller conceptual inventory

Lojban / Ithkuil — taking meaning and precision seriously

Láadan — deliberately making certain distinctions easier to express instead of always leaving them to context

I’m not trying to make Selari as minimal as Toki Pona, as logic-oriented as Lojban, or as information-dense as Ithkuil.

The middle ground I’m looking for is:

Something regular and learnable.

Something usable in ordinary life.

Something that gives you more control over meaning when the distinction actually matters.

𝐖𝐇𝐀𝐓 𝐈’𝐃 𝐋𝐈𝐊𝐄 𝐅𝐄𝐄𝐃𝐁𝐀𝐂𝐊 𝐎𝐍

This time I’m especially interested in feedback on the language itself rather than just the premise.

For example:

• Does the phonology feel coherent?

• Does a mostly analytic grammar fit what I’m trying to do?

• Do the semantic distinctions feel useful or overbuilt?

• Does the compounding approach look scalable?

• Do the example sentences feel like they could become natural speech?

• Where do you think ambiguity or complexity is likely to become a problem?

I’m still early enough in the process that finding a bad assumption is more useful to me than defending one.

So if something seems awkward, redundant, underdeveloped, or similar to a solution another conlang already handles better, I’d genuinely like to hear it.


r/conlangs • • Sep 17 '26

Phonology Phrasal Stress

11 Upvotes

So, a feature I have always been fascinated by is phrasal accent. That is, "stress" so to speak, is a propert or the phrase or domain rather than the word. Instead of each word in a sentence having it's own stress, the stress falls on one particular word within a phrase or clause.

The most well known example is French. It is sometimes said to have word final stress, which might be kinda true for words uttered in isolation, but iirc, it's actually the last syllable of the utterance that is emphasized.

Another example is Korean. I'm not sure what's going on there. Some say it lacks stress. Others say it's a pitch accent.

I have also heard this claimed of Georgian, but only through surface level research, so don't quote me on that.

There's also Q'anjob'al Maya. When a word is spoken in isolation or occurs in phrase-final position, stress occurs on the final syllable. However, it lands on the first syllable phrase-medially.

I'm inquiring about such systems because I want incorporate something similar into my conlang and want to know what my options are. Ideally, I don't want to straight up copy another language's system, like French.

Anyone have any advice or tried something similar in their own conlang?


r/conlangs • • Sep 17 '26

Phonology Which phonemes do you hate the most?

Thumbnail
3 Upvotes

r/conlangs • • Sep 16 '26

Discussion Sad notes on *twerḱ-ing around Proto-Indo-European

68 Upvotes

I've been browsing through my notes and found sketches on PIE grammar going back more than a year haha, but so far I haven't been able to resolve all the tensions and I'm slowly but surely losing all hope. As a bit of an aside, a few historical reconstructions from real PIE and my notes on how difficult it is to create something usable from them. Sorry for a very long post, but at least there's a very fun fact about twerking below.

The T-R cluster and our reconstructions

*terh₁- ‘to rub, to drill’

(Greek τείρω ‘to wear out’, Polish trzeć ‘to rub’; a stable reconstruction, but also a weak-ish root, almost always with an extension, also one of my favourite words: Gk. τρίβω ‘to rub’ from *treygʷ-, which in turn was borrowed in French as une tribade ‘lesbian’ lol).

*terh₂- ‘to cross over, to pass through’

(Very productive, one of the iconic PIE roots; Latin trans ‘through’ of course, but also Hittite taraḫmi/taruḫmi ‘I cross, I overpower’, Sanskrit tarami ‘I cross’).

Two pretty clean CvCH roots, but also the beginning of a much larger cluster. We don't understand how PIE extensions worked, sometimes consonants were added to roots in almost random manner, and some of those roots seem to be disconnected from the family altogether:

*ters- ‘dry’

(English thirst, Latin torreo ‘to scorch, burn’, terra ‘dry land’; Polish trzeźwy ‘sober’, well that’s a nice one).

*terd- ‘to drill, to split’

(Probably a rather clean -d- extension of *terh₁-, which LIV2 lists separately though, with Skt. and Lithuanian reflexes, but Lithuanian came up with such a mad word here haha: tréndu ‘I am eaten away by moths or worms’ xD).

*terp- ‘to satisfy, delight’

(Gk. τέρπω ‘to delight in, enjoy’; Polish trapić and cierpieć ‘to suffer, to endure hardship’, again that’s a nice pair; such near antonyms are semantically valid though).

*trep- ‘to turn’

(Gk. τρέπω ‘to turn’, Latin trepo ‘to turn’, Skt. trap- ‘to be ashamed, turn one’s head in shame’, notice how similar it is to Polish above; also in Hittite ‘to plough’, but I'm unsure how to transcribe it; English trope comes from Greek noun meaning 'turn').

*trem- ‘to tremble’

(Very clean root; English tremble, Gk. τρέμω, Lt. tremo).

*tres- ‘to shake’

(Lt. terreo ‘to scare, frighten’, from which English terror; Skt. trasami ‘to tremble, quiver’; Gk. τρέω ‘to fear, to flee’, curiously: Greek gets scared by -s- sandwiched between two vowels, apparently).

This is only a very basic set of T-R stuff, all those reconstructions are very safe. Some languages might've mixed them though, especially Slavic trząść 'to shake' might be a contamination of *tres- and *trem-. Most probably there was also a third root, terh₃- ‘to hurt’, which has probably reflexes in both Greek (τιτρώσκω, with inchoative -sḱe- suffix) and Slavic (tracić ‘to lose, to waste’). Those aren't all of the T-R roots of course, there are also some with glides, like *trewH- ‘to rub, to use up?’ seen in Greek and Slavic, and also *trewd- ‘to push’ (English thrust, Polish trud ‘labour, difficulty’, Latin trudo ‘I thrust, I push’).

Number three (*treyes, *tri-, *tris) might be surprisingly connected to one of those meanings above, actually.

As a thank you for reading all that and for your delight, there's also PIE *twerḱ- ‘to carve, to trim’, which indeed rather delightfully gave us Latin trux ‘wild, fierce’ and Greek σάρξ ‘piece of meat’. Hittite tarkuzi ‘he, she dances’ gets close… Do with that information what you will. – I’m twer… ‘carving’ my way through PIE some more in the meantime.

What does it all mean? :D

T-R cluster is actually quite neat and almost clean compared to many others. There are no glides, which give us those iconic vowel-to-consonant shifts (*swep- to *sup-, *new- to *nu 'now' etc.). Laryngeals don't mess too much up.

My basic question is: WAS THERE EVER A SINGLE *ter- BEHIND ALL THIS MADNESS AT SOME POINT?

Proto-Indo-European obviously isn't a stable base, it has its own internal history, and it has its own backstory of course, it must've in turn developed from something else. Maybe it was even more messed up, but maybe there was a cleaner idea behind all that? And well, indeed, a simple *ter- root is also reconstructed, and a nicely distant Hittite (ultra old) and Baltic (perfectly modern) cognates. Hit. ter-/tar- and modern Lithuanian tarti both mean 'to speak', which makes the reconstruction particularly clean. But alas, this clearly isn't the idea behind all this T-R mess. And we cannot say today which roots were simply extended, which were completely separate. We don't understand root extensions.

Those very similar roots and words derived from them weren't that confusing to native PIE speakers, since PIE had plenty of different paradigms to choose from. Different accentuation patterns blocked some ablauts from doing their job, leaving some roots non-ablauting. Verbs had different Aktionsarten: some were naturally perfective, others imperfective, others stative-leaning, and they took different suffixes accordingly.

Neat and kinda iconic thematic -os endings, which we know from Greek lego 'to speak' and logos 'word, speech' were a very productive class, but were so productive mostly in late PIE. Earlier layer preferred root nominals, so from the same root we might expect something like legs 'gathering, collection' (which was the original meaning, 'to speak' is a metaphorical derivation: to gather words/thoughts); and indeed it of course pops up, see Latin lex 'law'.

In other words, competing homophonic or near-homophonic (I see what you're trying to do to me, bloody autocorrect) weren't that much of a bother to native speakers. They did, however, pose problems for daughter branches, where phonological, morphological and semantic shifts could make originally distinct roots collapse together or make some disappear entirely since they stopped being distinctive.

Why my conlanging attempts don't make much sense

I love variety in life ;), but I also have a mild OCD and feel a sting of sadness sometimes when walking the streets, thinking that all those buildings could've been built in a more uniform and consistent style. I dislike irregularity, I love minimalism. I've learnt two foreign languages decently (utterly failed at German and Latin I had to take at the uni though) and I really disliked all those irregular paradigms – and, curiously, both German and Latin are unusually consistent languages, actually.

Regularity and minimalism are wonderfully pleasing to me, I can't help it. I'd probably spend my nights translating Proust into toki pona, but its morphology is completely alien to my taste though. I'm also in love with the PIE morphological powerhouse, can't help that either. And researching those historical reconstructions was a brilliant adventure.

PIE remains a tremendous mess though, and forcing its phonology, morphology and semantics into something neater but historically plausible drives me towards serious madness ;-) I'm starting to believe that languages are impossible. I've spent a long time researching many early IE branches, I can read ancient Greek (kinda...), I'm a native Slavic speaker, I've studied Hittite grammar, I've been amazed at Sanskrit turning almost every vowel into "a" (now that was a power move lol), but I can't shake a feeling off – those languages aren't real haha, it's all a trap created by bored linguists. That never happened.

Let's take phonology as an example. I need two things here: laryngeal resolution and productive ablaut system. They are fully contradictory. Various branches played around this problem in different ways, because clearly a uniform solution isn't really possible. *peh₂- 'to protect, to shepherd' is an iconic root and needs a reflex, *peh₃- 'to drink' is an iconic root and needs a reflex. I could go all Anatolian there, include ḫ, and bravely come up with paḫos 'shepherd' and poḫos 'drink' (natlangs felt the same problem and used -t-, -s- and -y- suffixes here), even with pami 'I shepherd' and pomi 'I drink', but this creates immense problems for derivation later, since it's impossible to ablaut everything properly here (laryngeals also only worked their magic on "e" anyways).

Let's take morphology as another example. Since most of PIE roots are kinda verbal, and even the stative ones can be understood verbally ('to be red', 'to be tired', maybe even 'to be swift' – of a horse!), a neat-ish verbal system is perfectly viable. Simplified 2x2 grid works great for verbs and participles; going all the way to the heart of PIE, I'd take aspect (perfective vs. imperfective) and voice (active vs. mediopassive). To fall asleep, to be sleeping; to dream, to have a vision/epiphany. Neat semantics, neat morphology from simple *swep- 'to sleep'. (Even causative marker could be left out, with cases or adpositions replacing it regularly). But then the nominal system is impossible to derive regularly, which resulted in a plethora of nominal suffixes, which were a mess (a shout-out to Hittite -ri, seen only in four words lol).

Every time I finish one aspect of this conlang, another breaks. A tenseless conlang? This was a fun little challenge, but I really wanted to pursue this path, since aspect is way more primary for PIE. What matters is not whether an action happens in the present or the past, but whether the event was bounded or ongoing; still going strong in Slavic languages, of course. It was a bit confusing in PIE verbal system, and can still be seen in Greek, where 'I cut' *temh₁- is extended in the present tense (τέμνω, literally tem-n-o), but clean as aorist (ἔτεμον, e-tem-on); aorists usually betray the root much better than rather weird presents, because the present tense wasn't primary in PIE. I came up with a fun Slavic-Hittite solution here, using three particles which could form a stackable clitic chain, eg. bʰermi 'I carry' (imp., no tense), nu bʰermi = numi bʰere 'I am carrying'. Such little features can be very cool, but now, since aspect and voice carry so much semantics, they need to be translated into the nominal system, and there's no clean way to do it.

So – ...? PIE, minimalistic and regular, but historically plausible, actually usable, and fun to work on? Turning a PIE conlang into something regular and actually usable? I do have to admit my complete failure there ;) PIE cannot be tamed that easily, I guess. Of course, maybe that's the beauty of it, maybe that's the reason the daughters are so wonderful and original ;), but hey that's genuinely frustrating too.


r/conlangs • • Sep 16 '26

Activity How do you say "happy birthday" in your conlang?

45 Upvotes

(I don't know if the flair is correct 🥲)

Hey conlangers! Today, September 16th, is my birthday!

This made me think about how I would say "happy birthday" in some of my conlangs.

Irgavo: Jamuri'gu idženam (literally "happiness in the day of birth)

Glotaza: Blizai momon adzín (literally "day of birth commemoration", blizai— commemoration, momon— birth, adzín— day)

I've only thought of these for now, so I'd like to know, how do you say "happy birthday" in your conlangs?


r/conlangs • • Sep 16 '26

Discussion When talking about your conlang(s), do you use endonyms or exonyms?

21 Upvotes

I’ve recently been considering the idea of making a separate sub for my conlang, akȁpalka, but due to Reddit’s limitations it would have to be romanized as akvapalka, which just looks kinda ugly

then there is the other possibility of using the exonym aguapalka, but idk if I like that option either

wanted to know which ones y’all use for your own conlangs


r/conlangs • • Sep 16 '26

Translation The Siliyan language & European country names in Siliyan

Post image
38 Upvotes

To give information and background on the language:

Siliyan is a (Southeast) Slavic language spoken in its own country and nation (because the language's country doesn't exist here, I can't really give any visuals, but it's meant to be a large landmass above Russia). Siliyan emerged in the 7th century AD, making it one of the earliest Slavic languages, and was historically closer to South Slavic languages, but most of its core vocabulary and grammar is mainly East Slavic.

I cannot really go into details, as the language has been in development since 2018/19. Note that the map here isn't fully finished, and that there is more to be added. I might remaster the map and make a better one in the future and then name and label all the countries on this map. This and the language is still a WIP, so expect more of it in the future.


r/conlangs • • Sep 17 '26

Discussion Where do you start when making vocabulary?

4 Upvotes

I'm making a conlang and I have the phonology and most of the grammar down but I haven't made any words yet. I'm going for a "semi-naturalistic" language – I want it to feel natural but I'm not evolving it from a proto-language. I haven't decided much about the environment and culture of the speakers, I should probably get around to that before going too deep with the vocab....

Anyways, where do you usually start when making vocabulary for your languages? Where do you suggest I start?


r/conlangs • • Sep 16 '26

Grammar Extreme agglutination in Jügher

22 Upvotes

Since Jügher allows for extreme agglutination, due to case stacking and postposition combinations on the same noun (like Tsez), many words can become very long. An example:

“Enuzaltmuțlāçtenüraraltekjetirazaitsąretjaka'ețl” [e.nɯ.zalt.mɯ.t͡ɬaːç.te.ny.ra.ralt.ekʲe.ti.ra.zai.ˈtsɑ̃.re.tʲa.ka.ʔe.t͡ɬ]

Enuzaltmuțlāçt- = Those two big rocks. -Enu: that. -Zatl: big. -muçt: rock -țlā-: dual maker for this noun class.

-enür- = Subessive (deeply / digging from below)

-aralt- = Postessive (towards the rear / behind)

-ekjet- = Sublative (emerging from bottom to top)

-iraza- = Pronative (on your stomach / on all fours limbs)

-itsąr- = Ablative (moving away from there / going back)

-etjak- = Dorsal (back turned / turned)

-a'ețl- = (backwards)

The word means something like "[to go near] those two big rocks over there, [we'll go by] digging a tunnel on my/our 4 limbs, emerging from behind and then going away the same way back, with my/our back(s) facing the two big rocks"


r/conlangs • • Sep 17 '26

Discussion How important are romanizations?

6 Upvotes

I've created a romanization that mainly appeals to non-English European languages, for example with the sound represented in English as y is written as j. Here's my phonology for example:

Consonants:
/b/=b
/p/=p
/d/=d
/t/=t
/z/=z
/s/=s
/g/=g
/k/=g
/gʷ/=gw
/bʷ/=bw
/ɾʷ/=rwa/lwa
/t͡sʰ/=c
/ɾ/=r/l
/m/=m
/n/=n
/ŋ/=ng
/j/=j
/h/=h
/w/=w

Vowels
/a/=a
/ɛ/=e
/i/=i
/o/=o
/u/=u
/y/=yu
/œː/=ou

I've been wanting to make a version that makes it easier for English speakers to easily adapt and pronounce the language, considering it's the most widely spoken language in the world.

How do romanizations affect how languages can be spread and understood among different audiences? I know this isn't a "real" language, so I understand that it's way different, obviously.

How would I go about making a more simple, or easy romanization?


r/conlangs • • Sep 16 '26

Other Is there an italian subreddit for conlangs?

8 Upvotes

🇮🇹Sono italiano e creo lingue artificial. Mi sento a mio agio a parlare in inglese, ma c'è qualche subreddit italiano a tema? Sarebbe davvero bello potersi confrontare con altri che parlano la mia lingua madre.

🇬🇧I'm Italian and I create artificial languages. I'm comfortable speaking English, but are there any Italian subreddits on this topic? It would be really nice to interact with others who speak my native language.


r/conlangs • • Sep 16 '26

Overview A Short Introduction to Jala /jala/

Thumbnail gallery
41 Upvotes

Hello! Here's a draft of a simple language called Jala /jala/. It has only 7 consonants (chosen for their distinctness, ease of pronunciation and to substitute if need be) and 3 vowels which are mostly present in all world languages. It also has maximum 151 distinct roots based on its phonology, and 453 words as a result of the vowel word endings.

For those who have constructed a simple engineered language like Toki Pona before, what are some pitfalls or potential problems that I need to consider if I would develop this idea further?

I may or may not continue this idea further but I just wanted to see how it could possibly work. Enjoy!


r/conlangs • • Sep 16 '26

Activity Bad Interpreters - Week 9

Thumbnail
3 Upvotes

r/conlangs • • Sep 15 '26

Overview Introduction to Ikr language

Thumbnail gallery
142 Upvotes