<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.languagecreator.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thomas</id>
	<title>Language Creator Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.languagecreator.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thomas"/>
	<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php/Special:Contributions/Thomas"/>
	<updated>2026-07-14T09:04:38Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.40.3</generator>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=70</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=70"/>
		<updated>2025-04-04T12:56:11Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| – || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || – || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[PUNCT]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PERF]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[IMPERF]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[PLUR]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[INS]] || –&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || [[POLITE]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || [[OR]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
===Pre-root===&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[IMPERF]], [[PERF]], [[PUNCT]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
===Post-root===&lt;br /&gt;
* [[QUOT]], [[ne]], [[yo]].  [[QUEST]] could be moved here.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Abandoned===&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=69</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=69"/>
		<updated>2025-04-04T12:55:52Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| – || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || – || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[PUNCT]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PERF]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[IMPERF]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[PLUR]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[INS]] || –&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || [[POLITE]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || [[OR]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
===Pre-root===&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
===Post-root===&lt;br /&gt;
* [[QUOT]], [[ne]], [[yo]].  [[QUEST]] could be moved here.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Abandoned===&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Evocative_compounding&amp;diff=68</id>
		<title>Evocative compounding</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Evocative_compounding&amp;diff=68"/>
		<updated>2025-03-27T14:06:44Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Why Not Descriptive Compounds? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Motivations for Evocative Compounding =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
One of the core design strategies in Sekimoli is the use of &#039;&#039;evocative&#039;&#039; semantic compounds. Rather than aiming for purely descriptive or taxonomic labels (e.g. &amp;quot;string instrument&amp;quot; or &amp;quot;wind instrument&amp;quot;), Sekimoli prioritizes compounds that are emotionally resonant, metaphorically vivid, or culturally iconic (e.g. &amp;quot;bear instrument&amp;quot;, &amp;quot;moon instrument&amp;quot;, &amp;quot;storm drink&amp;quot;, etc.).&lt;br /&gt;
&lt;br /&gt;
This approach is not only aesthetically and mnemonically satisfying — it is also supported by multiple theories in cognitive psychology and language learning. The goal is to create vocabulary that is easier to remember, more fun to use, and semantically distinctive, even among closely related terms.&lt;br /&gt;
&lt;br /&gt;
== Why Not Descriptive Compounds? ==&lt;br /&gt;
Descriptive compounds like &#039;&#039;stor arm streng instrument&#039;&#039; (&amp;quot;large-arm string instrument&amp;quot;) for viola are technically accurate but cognitively bland. They fail to evoke a distinct mental image or emotional reaction. This becomes problematic when learners need to distinguish between many similar words — as is common in domains like plants, animals, tools, or musical instruments.&lt;br /&gt;
&lt;br /&gt;
Of course Sekimoli doesn&#039;t avoid descriptive compounds if they&#039;re memorable and reasonably unique. There&#039;s nothing wrong with &amp;quot;string instrument&amp;quot; – but it should mean &amp;quot;string instrument&amp;quot;, not &amp;quot;violin&amp;quot;. The violin itself needs a memorable word, such as &amp;quot;cat instrument&amp;quot;, &amp;quot;love instrument&amp;quot; or whatever.&lt;br /&gt;
&lt;br /&gt;
== Psychological Principles Behind the Strategy ==&lt;br /&gt;
&lt;br /&gt;
=== Dual Coding Theory ===&lt;br /&gt;
According to Paivio&#039;s Dual Coding Theory, memory is enhanced when information is encoded in both verbal and visual forms. A phrase like &amp;quot;elephant instrument&amp;quot; evokes a concrete mental image that reinforces the verbal label, making it more memorable than &amp;quot;low brass instrument&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Von Restorff Effect ===&lt;br /&gt;
Also known as the Isolation Effect, this principle states that items that stand out from their surroundings are more likely to be remembered. In a list of dry, taxonomic names, a term like &amp;quot;ghost instrument&amp;quot; or &amp;quot;mirror fruit&amp;quot; grabs attention and lodges itself in memory.&lt;br /&gt;
&lt;br /&gt;
=== Affective Encoding ===&lt;br /&gt;
Emotionally charged words and metaphors are more deeply encoded in memory. A name like &amp;quot;grief instrument&amp;quot; does more than describe sound; it taps into the emotional register, creating a lasting connection.&lt;br /&gt;
&lt;br /&gt;
=== Schema Theory ===&lt;br /&gt;
Our brains process and remember new information more easily when it connects to existing mental frameworks (schemas). Animals, emotions, weather, and mythic imagery are all deeply embedded in human experience. Compounds like &amp;quot;swan instrument&amp;quot; or &amp;quot;storm drink&amp;quot; plug into these schemas, helping learners grasp and retain the word more efficiently.&lt;br /&gt;
&lt;br /&gt;
== Linguistic Implications ==&lt;br /&gt;
This approach sacrifices a degree of analytic clarity for mnemonic power and expressive depth. It embraces polysemy, metaphor, and poetic overtones.&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
Evocative compounding is not just a stylistic quirk — it&#039;s a principled, psychologically grounded strategy for making Sekimoli a language that&#039;s easy to learn, fun to speak, and rich in metaphorical resonance.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Evocative_compounding&amp;diff=67</id>
		<title>Evocative compounding</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Evocative_compounding&amp;diff=67"/>
		<updated>2025-03-27T14:03:32Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Linguistic Implications */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Motivations for Evocative Compounding =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
One of the core design strategies in Sekimoli is the use of &#039;&#039;evocative&#039;&#039; semantic compounds. Rather than aiming for purely descriptive or taxonomic labels (e.g. &amp;quot;string instrument&amp;quot; or &amp;quot;wind instrument&amp;quot;), Sekimoli prioritizes compounds that are emotionally resonant, metaphorically vivid, or culturally iconic (e.g. &amp;quot;bear instrument&amp;quot;, &amp;quot;moon instrument&amp;quot;, &amp;quot;storm drink&amp;quot;, etc.).&lt;br /&gt;
&lt;br /&gt;
This approach is not only aesthetically and mnemonically satisfying — it is also supported by multiple theories in cognitive psychology and language learning. The goal is to create vocabulary that is easier to remember, more fun to use, and semantically distinctive, even among closely related terms.&lt;br /&gt;
&lt;br /&gt;
== Why Not Descriptive Compounds? ==&lt;br /&gt;
Descriptive compounds like &#039;&#039;stor arm streng instrument&#039;&#039; (&amp;quot;large-arm string instrument&amp;quot;) for viola are technically accurate but cognitively bland. They fail to evoke a distinct mental image or emotional reaction. This becomes problematic when learners need to distinguish between many similar words — as is common in domains like plants, animals, tools, or musical instruments.&lt;br /&gt;
&lt;br /&gt;
== Psychological Principles Behind the Strategy ==&lt;br /&gt;
&lt;br /&gt;
=== Dual Coding Theory ===&lt;br /&gt;
According to Paivio&#039;s Dual Coding Theory, memory is enhanced when information is encoded in both verbal and visual forms. A phrase like &amp;quot;elephant instrument&amp;quot; evokes a concrete mental image that reinforces the verbal label, making it more memorable than &amp;quot;low brass instrument&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Von Restorff Effect ===&lt;br /&gt;
Also known as the Isolation Effect, this principle states that items that stand out from their surroundings are more likely to be remembered. In a list of dry, taxonomic names, a term like &amp;quot;ghost instrument&amp;quot; or &amp;quot;mirror fruit&amp;quot; grabs attention and lodges itself in memory.&lt;br /&gt;
&lt;br /&gt;
=== Affective Encoding ===&lt;br /&gt;
Emotionally charged words and metaphors are more deeply encoded in memory. A name like &amp;quot;grief instrument&amp;quot; does more than describe sound; it taps into the emotional register, creating a lasting connection.&lt;br /&gt;
&lt;br /&gt;
=== Schema Theory ===&lt;br /&gt;
Our brains process and remember new information more easily when it connects to existing mental frameworks (schemas). Animals, emotions, weather, and mythic imagery are all deeply embedded in human experience. Compounds like &amp;quot;swan instrument&amp;quot; or &amp;quot;storm drink&amp;quot; plug into these schemas, helping learners grasp and retain the word more efficiently.&lt;br /&gt;
&lt;br /&gt;
== Linguistic Implications ==&lt;br /&gt;
This approach sacrifices a degree of analytic clarity for mnemonic power and expressive depth. It embraces polysemy, metaphor, and poetic overtones.&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
Evocative compounding is not just a stylistic quirk — it&#039;s a principled, psychologically grounded strategy for making Sekimoli a language that&#039;s easy to learn, fun to speak, and rich in metaphorical resonance.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Evocative_compounding&amp;diff=66</id>
		<title>Evocative compounding</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Evocative_compounding&amp;diff=66"/>
		<updated>2025-03-27T14:02:26Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;= Motivations for Evocative Compounding =  == Overview == One of the core design strategies in Sekimoli is the use of &amp;#039;&amp;#039;evocative&amp;#039;&amp;#039; semantic compounds. Rather than aiming for purely descriptive or taxonomic labels (e.g. &amp;quot;string instrument&amp;quot; or &amp;quot;wind instrument&amp;quot;), Sekimoli prioritizes compounds that are emotionally resonant, metaphorically vivid, or culturally iconic (e.g. &amp;quot;bear instrument&amp;quot;, &amp;quot;moon instrument&amp;quot;, &amp;quot;storm drink&amp;quot;, etc.).  This approach is not only aesthetically...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Motivations for Evocative Compounding =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
One of the core design strategies in Sekimoli is the use of &#039;&#039;evocative&#039;&#039; semantic compounds. Rather than aiming for purely descriptive or taxonomic labels (e.g. &amp;quot;string instrument&amp;quot; or &amp;quot;wind instrument&amp;quot;), Sekimoli prioritizes compounds that are emotionally resonant, metaphorically vivid, or culturally iconic (e.g. &amp;quot;bear instrument&amp;quot;, &amp;quot;moon instrument&amp;quot;, &amp;quot;storm drink&amp;quot;, etc.).&lt;br /&gt;
&lt;br /&gt;
This approach is not only aesthetically and mnemonically satisfying — it is also supported by multiple theories in cognitive psychology and language learning. The goal is to create vocabulary that is easier to remember, more fun to use, and semantically distinctive, even among closely related terms.&lt;br /&gt;
&lt;br /&gt;
== Why Not Descriptive Compounds? ==&lt;br /&gt;
Descriptive compounds like &#039;&#039;stor arm streng instrument&#039;&#039; (&amp;quot;large-arm string instrument&amp;quot;) for viola are technically accurate but cognitively bland. They fail to evoke a distinct mental image or emotional reaction. This becomes problematic when learners need to distinguish between many similar words — as is common in domains like plants, animals, tools, or musical instruments.&lt;br /&gt;
&lt;br /&gt;
== Psychological Principles Behind the Strategy ==&lt;br /&gt;
&lt;br /&gt;
=== Dual Coding Theory ===&lt;br /&gt;
According to Paivio&#039;s Dual Coding Theory, memory is enhanced when information is encoded in both verbal and visual forms. A phrase like &amp;quot;elephant instrument&amp;quot; evokes a concrete mental image that reinforces the verbal label, making it more memorable than &amp;quot;low brass instrument&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Von Restorff Effect ===&lt;br /&gt;
Also known as the Isolation Effect, this principle states that items that stand out from their surroundings are more likely to be remembered. In a list of dry, taxonomic names, a term like &amp;quot;ghost instrument&amp;quot; or &amp;quot;mirror fruit&amp;quot; grabs attention and lodges itself in memory.&lt;br /&gt;
&lt;br /&gt;
=== Affective Encoding ===&lt;br /&gt;
Emotionally charged words and metaphors are more deeply encoded in memory. A name like &amp;quot;grief instrument&amp;quot; does more than describe sound; it taps into the emotional register, creating a lasting connection.&lt;br /&gt;
&lt;br /&gt;
=== Schema Theory ===&lt;br /&gt;
Our brains process and remember new information more easily when it connects to existing mental frameworks (schemas). Animals, emotions, weather, and mythic imagery are all deeply embedded in human experience. Compounds like &amp;quot;swan instrument&amp;quot; or &amp;quot;storm drink&amp;quot; plug into these schemas, helping learners grasp and retain the word more efficiently.&lt;br /&gt;
&lt;br /&gt;
== Linguistic Implications ==&lt;br /&gt;
This approach sacrifices a degree of analytic clarity for mnemonic power and expressive depth. It embraces polysemy, metaphor, and poetic overtones. Some instruments might have multiple possible compounds (e.g. &amp;quot;sorrow instrument&amp;quot;, &amp;quot;sister instrument&amp;quot;, or &amp;quot;cat instrument&amp;quot; for violin), and that’s not a flaw — it&#039;s a feature. It reflects the richness and flexibility of human meaning-making.&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
Evocative compounding is not just a stylistic quirk — it&#039;s a principled, psychologically grounded strategy for making Sekimoli a language that&#039;s easy to learn, fun to speak, and rich in metaphorical resonance.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=65</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=65"/>
		<updated>2025-03-27T14:02:18Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
* [[Counting objects]]&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
* [[locative nouns]]&lt;br /&gt;
* [[tabelvortoj]]&lt;br /&gt;
&lt;br /&gt;
=== Articles ===&lt;br /&gt;
&lt;br /&gt;
* [[the sign is arbitrary]]&lt;br /&gt;
* [[evocative compounding]]&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
One could work backwards. 300 roots would be enough for 90k simple compounds and 27m three-element ones. Still plenty.  300 roots could be formed through 10 consonants and 3 vowels (CVC). Of course, there&#039;s absolutely no redundancy then, so probably not great for communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
* A [[chat about principles for choosing between a root or a compound]]&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=64</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=64"/>
		<updated>2025-03-26T14:37:11Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Post-root&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| – || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || – || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[GNOM]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PERF]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PUNCT]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[PLUR]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[INS]] || –&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || [[POLITE]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || [[OR]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
===Pre-root===&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
===Post-root===&lt;br /&gt;
* [[QUOT]], [[ne]], [[yo]].  [[QUEST]] could be moved here.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Abandoned===&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=63</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=63"/>
		<updated>2024-11-29T18:17:53Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| – || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || – || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[GNOM]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PERF]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PUNCT]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[PLUR]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[INS]] || –&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || [[POLITE]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || [[OR]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=62</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=62"/>
		<updated>2024-11-29T18:13:55Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || – || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[GNOM]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PERF]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PUNCT]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[PLUR]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[INS]] || –&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || [[POLITE]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || –&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=61</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=61"/>
		<updated>2024-11-29T18:13:01Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[GNOM]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] ||  || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PUNCT]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[PLUR]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[INS]] || –&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || [[POLITE]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || –&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=60</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=60"/>
		<updated>2024-11-29T18:10:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[GNOM]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || – || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PUNCT]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || – || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (–) || –&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=59</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=59"/>
		<updated>2024-11-29T18:07:27Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[GNOM]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PUNCT]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || ki || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PUNCT]], [[PERF]], [[GNOM]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=58</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=58"/>
		<updated>2024-11-29T18:00:52Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[NOMIC]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || [[PART]]&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || ki || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PRES]], [[PERF]], [[NOMIC]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]], [[PART]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=57</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=57"/>
		<updated>2024-11-29T11:54:32Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || [[ADV]] || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[NOMIC]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[REL]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[GEN]] || ki || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time for phonetic reasons.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PRES]], [[PERF]], [[NOMIC]], [[IMP]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]], [[ADV]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Abandoned:&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]]. (Too hard to use – better to use adverbs.)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=56</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=56"/>
		<updated>2024-11-29T10:41:20Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[NOMIC]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PRES]], [[PERF]], [[NOMIC]], [[IMP]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]], [[IRR]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[LOC]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=55</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=55"/>
		<updated>2024-11-29T10:36:29Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || [[NOMIC]]&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || [[IMP]]&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PRES]], [[PERF]], [[NOMIC]], [[IMP]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=IMP&amp;diff=54</id>
		<title>IMP</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=IMP&amp;diff=54"/>
		<updated>2024-11-29T10:35:13Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;IMP: Imperative, like &amp;#039;&amp;#039;Eat that sandwich now!&amp;#039;&amp;#039;&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;IMP: Imperative, like &#039;&#039;Eat that sandwich now!&#039;&#039;&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=NOMIC&amp;diff=53</id>
		<title>NOMIC</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=NOMIC&amp;diff=53"/>
		<updated>2024-11-29T10:34:43Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;NOMIC: A verbalising particle expressing that an action is continuous, like &amp;#039;&amp;#039;The sky is blue above the clouds&amp;#039;&amp;#039; or &amp;#039;&amp;#039;The boys eats sandwiches for lunch&amp;#039;&amp;#039;.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;NOMIC: A verbalising particle expressing that an action is continuous, like &#039;&#039;The sky is blue above the clouds&#039;&#039; or &#039;&#039;The boys eats sandwiches for lunch&#039;&#039;.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=PERF&amp;diff=52</id>
		<title>PERF</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=PERF&amp;diff=52"/>
		<updated>2024-11-29T10:33:32Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;PERF: A verbalising particle expressing that something has finished, such as &amp;#039;&amp;#039;The boy has eaten his sandwich.&amp;#039;&amp;#039;&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;PERF: A verbalising particle expressing that something has finished, such as &#039;&#039;The boy has eaten his sandwich.&#039;&#039;&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=PRES&amp;diff=51</id>
		<title>PRES</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=PRES&amp;diff=51"/>
		<updated>2024-11-29T10:32:43Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;PRES: A verbalising particle expressing an action, like &amp;#039;&amp;#039;the boy is eating a sandwich&amp;#039;&amp;#039;.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;PRES: A verbalising particle expressing an action, like &#039;&#039;the boy is eating a sandwich&#039;&#039;.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=50</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=50"/>
		<updated>2024-11-29T10:31:36Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PERF]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Verbalising:&lt;br /&gt;
* Aspect/mode: [[PRES]], [[PERF]], [[NOMIC]], [[IMP]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]].&lt;br /&gt;
&lt;br /&gt;
Nominalising:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
&lt;br /&gt;
Neutral:&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]]. Maybe [[EACHOTHER]]?&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=49</id>
		<title>The sign is arbitrary</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=49"/>
		<updated>2024-11-28T19:36:19Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Why Arbitrariness Matters */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==The Art of Crafting Memorable Compounds in Constructed Languages==&lt;br /&gt;
&lt;br /&gt;
In the world of constructed languages (conlangs), one of the most creative and enjoyable challenges is forming new words to describe concepts, objects, or creatures. A fundamental principle in linguistics is that the relationship between a word (the sign) and its meaning is arbitrary. This means that words do not inherently carry the essence of what they represent; rather, they are symbols agreed upon by a language community.&lt;br /&gt;
&lt;br /&gt;
When building a conlang, especially one that relies on compound words, it&#039;s essential to focus on making these compounds memorable and engaging. While it&#039;s tempting to strive for descriptiveness, it&#039;s important to acknowledge that no compound can capture the full essence of what it&#039;s describing. Instead, the goal should be to create words that resonate with speakers and spark curiosity.&lt;br /&gt;
&lt;br /&gt;
===Why Arbitrariness Matters===&lt;br /&gt;
The arbitrary nature of signs allows for flexibility and creativity in language development. Since there&#039;s no inherent connection between a word and its meaning, language creators have the freedom to choose words that best fit the aesthetic, phonetic, or cultural aspects of their conlang.&lt;br /&gt;
&lt;br /&gt;
For instance, consider the task of naming various species of whales in a conlang using two-element compounds. The constraints might include:&lt;br /&gt;
&lt;br /&gt;
*The last element must be &amp;quot;whale.&amp;quot;&lt;br /&gt;
*The first element must be a simple, commonly used word.&lt;br /&gt;
*Each compound must be unique and not repeated.&lt;br /&gt;
&lt;br /&gt;
Given these constraints, it&#039;s impossible to create fully descriptive names for each species. However, by embracing arbitrariness, we can craft memorable names that capture a distinctive feature or evoke a particular image associated with the species.&lt;br /&gt;
&lt;br /&gt;
===Cultural Perceptions and &#039;Obvious&#039; Compounds===&lt;br /&gt;
An important consideration in crafting compounds is that what seems like an obvious or natural combination in one language or culture might not be the same in another. Native language and cultural background significantly influence how we perceive and form compounds. For example:&lt;br /&gt;
&lt;br /&gt;
Watermelon: In English, &amp;quot;watermelon&amp;quot; is the common term, which might seem obvious to English speakers due to its high water content. However, in Chinese, the word is &amp;quot;西瓜&amp;quot; (xīguā), which translates to &amp;quot;west melon,&amp;quot; reflecting the fruit&#039;s historical introduction from western regions. In Georgian, it&#039;s called &amp;quot;საზამთრო&amp;quot; (sazamatro), meaning &amp;quot;winter melon,&amp;quot; because it&#039;s harvested in late summer and can be stored until winter.&lt;br /&gt;
These differences highlight how cultural and linguistic contexts shape our associations and language use. When creating compounds in your conlang, it&#039;s valuable to consider:&lt;br /&gt;
&lt;br /&gt;
*Cultural Context: Align compounds with the cultural background or mythology of your conlang&#039;s speakers.&lt;br /&gt;
*Audience Diversity: Be mindful that learners from different linguistic backgrounds may perceive compounds differently.&lt;br /&gt;
*Creative Freedom: Use this diversity as an opportunity to create unique and enriching vocabulary.&lt;br /&gt;
&lt;br /&gt;
===The Power of Memorable Compounds===&lt;br /&gt;
Memorable compounds serve several important functions in a conlang:&lt;br /&gt;
&lt;br /&gt;
*Ease of Learning: Words that are catchy or evoke strong imagery are easier for learners to remember and use.&lt;br /&gt;
*Cultural Depth: Unique compounds can reflect the culture, humor, or values embedded within the language.&lt;br /&gt;
*Engagement: Memorable words invite speakers to explore the language further and discover more about its structure and vocabulary.&lt;br /&gt;
&lt;br /&gt;
===Examples of Creative Compounds===&lt;br /&gt;
Let&#039;s look at some examples where memorability takes precedence over complete descriptiveness:&lt;br /&gt;
&lt;br /&gt;
*Sword Whale: Used for Sowerby&#039;s beaked whale, this name hints at the whale&#039;s elongated teeth resembling swords.&lt;br /&gt;
*Ghost Whale: For the elusive Hubbs&#039; beaked whale, emphasizing its rarity and mysterious nature.&lt;br /&gt;
*Smoke Whale: Representing Gray&#039;s beaked whale, playing on the word &amp;quot;gray&amp;quot; and the ethereal quality of smoke.&lt;br /&gt;
*Sad Whale: Assigned to the critically endangered Vaquita, invoking an emotional response to its plight.&lt;br /&gt;
*Fruit Whale: Denoting the Melon-headed whale, using &amp;quot;fruit&amp;quot; to reflect its melon-shaped head.&lt;br /&gt;
&lt;br /&gt;
These names might not fully describe the species, but they are distinctive and encourage curiosity.&lt;br /&gt;
&lt;br /&gt;
===Embracing Creativity Within Constraints===&lt;br /&gt;
Working within specific constraints can actually enhance creativity. When we limit ourselves to simple words or specific structures, we&#039;re challenged to think outside the box and find innovative solutions. This can lead to the development of a rich and dynamic vocabulary that adds depth to the conlang.&lt;br /&gt;
&lt;br /&gt;
===Conclusion===&lt;br /&gt;
In constructing a language, it&#039;s important to remember that words are tools for communication, and their effectiveness lies in how well they are received and used by speakers. By focusing on creating memorable compounds, language creators can ensure that their conlangs are not only functional but also engaging and enjoyable to learn.&lt;br /&gt;
&lt;br /&gt;
The arbitrariness of signs is not a limitation but an opportunity to infuse the language with personality and charm. So, when crafting compounds, let imagination take the lead, and don&#039;t be afraid to choose words that might seem unconventional. After all, the most memorable words are often those that surprise and delight us.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=48</id>
		<title>The sign is arbitrary</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=48"/>
		<updated>2024-11-28T19:29:29Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==The Art of Crafting Memorable Compounds in Constructed Languages==&lt;br /&gt;
&lt;br /&gt;
In the world of constructed languages (conlangs), one of the most creative and enjoyable challenges is forming new words to describe concepts, objects, or creatures. A fundamental principle in linguistics is that the relationship between a word (the sign) and its meaning is arbitrary. This means that words do not inherently carry the essence of what they represent; rather, they are symbols agreed upon by a language community.&lt;br /&gt;
&lt;br /&gt;
When building a conlang, especially one that relies on compound words, it&#039;s essential to focus on making these compounds memorable and engaging. While it&#039;s tempting to strive for descriptiveness, it&#039;s important to acknowledge that no compound can capture the full essence of what it&#039;s describing. Instead, the goal should be to create words that resonate with speakers and spark curiosity.&lt;br /&gt;
&lt;br /&gt;
===Why Arbitrariness Matters===&lt;br /&gt;
The arbitrary nature of signs allows for flexibility and creativity in language development. Since there&#039;s no inherent connection between a word and its meaning, language creators have the freedom to choose words that best fit the aesthetic, phonetic, or cultural aspects of their conlang.&lt;br /&gt;
&lt;br /&gt;
For instance, consider the task of naming various species of whales in a conlang using two-element compounds. The constraints might include:&lt;br /&gt;
&lt;br /&gt;
*The last element must be &amp;quot;whale.&amp;quot;&lt;br /&gt;
*The first element must be a simple, commonly used word.&lt;br /&gt;
*Each compound must be unique and not repeated.&lt;br /&gt;
&lt;br /&gt;
Given these constraints, it&#039;s impossible to create fully descriptive names for each species. However, by embracing arbitrariness, we can craft memorable names that capture a distinctive feature or evoke a particular image associated with the species.&lt;br /&gt;
&lt;br /&gt;
===The Power of Memorable Compounds===&lt;br /&gt;
Memorable compounds serve several important functions in a conlang:&lt;br /&gt;
&lt;br /&gt;
*Ease of Learning: Words that are catchy or evoke strong imagery are easier for learners to remember and use.&lt;br /&gt;
*Cultural Depth: Unique compounds can reflect the culture, humor, or values embedded within the language.&lt;br /&gt;
*Engagement: Memorable words invite speakers to explore the language further and discover more about its structure and vocabulary.&lt;br /&gt;
&lt;br /&gt;
===Examples of Creative Compounds===&lt;br /&gt;
Let&#039;s look at some examples where memorability takes precedence over complete descriptiveness:&lt;br /&gt;
&lt;br /&gt;
*Sword Whale: Used for Sowerby&#039;s beaked whale, this name hints at the whale&#039;s elongated teeth resembling swords.&lt;br /&gt;
*Ghost Whale: For the elusive Hubbs&#039; beaked whale, emphasizing its rarity and mysterious nature.&lt;br /&gt;
*Smoke Whale: Representing Gray&#039;s beaked whale, playing on the word &amp;quot;gray&amp;quot; and the ethereal quality of smoke.&lt;br /&gt;
*Sad Whale: Assigned to the critically endangered Vaquita, invoking an emotional response to its plight.&lt;br /&gt;
*Fruit Whale: Denoting the Melon-headed whale, using &amp;quot;fruit&amp;quot; to reflect its melon-shaped head.&lt;br /&gt;
&lt;br /&gt;
These names might not fully describe the species, but they are distinctive and encourage curiosity.&lt;br /&gt;
&lt;br /&gt;
===Embracing Creativity Within Constraints===&lt;br /&gt;
Working within specific constraints can actually enhance creativity. When we limit ourselves to simple words or specific structures, we&#039;re challenged to think outside the box and find innovative solutions. This can lead to the development of a rich and dynamic vocabulary that adds depth to the conlang.&lt;br /&gt;
&lt;br /&gt;
===Conclusion===&lt;br /&gt;
In constructing a language, it&#039;s important to remember that words are tools for communication, and their effectiveness lies in how well they are received and used by speakers. By focusing on creating memorable compounds, language creators can ensure that their conlangs are not only functional but also engaging and enjoyable to learn.&lt;br /&gt;
&lt;br /&gt;
The arbitrariness of signs is not a limitation but an opportunity to infuse the language with personality and charm. So, when crafting compounds, let imagination take the lead, and don&#039;t be afraid to choose words that might seem unconventional. After all, the most memorable words are often those that surprise and delight us.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=47</id>
		<title>The sign is arbitrary</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=47"/>
		<updated>2024-11-28T19:27:58Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==The Art of Crafting Memorable Compounds in Constructed Languages==&lt;br /&gt;
&lt;br /&gt;
In the world of constructed languages (conlangs), one of the most creative and enjoyable challenges is forming new words to describe concepts, objects, or creatures. A fundamental principle in linguistics is that the relationship between a word (the sign) and its meaning is arbitrary. This means that words do not inherently carry the essence of what they represent; rather, they are symbols agreed upon by a language community.&lt;br /&gt;
&lt;br /&gt;
When building a conlang, especially one that relies on compound words, it&#039;s essential to focus on making these compounds memorable and engaging. While it&#039;s tempting to strive for descriptiveness, it&#039;s important to acknowledge that no compound can capture the full essence of what it&#039;s describing. Instead, the goal should be to create words that resonate with speakers and spark curiosity.&lt;br /&gt;
&lt;br /&gt;
===Why Arbitrariness Matters===&lt;br /&gt;
The arbitrary nature of signs allows for flexibility and creativity in language development. Since there&#039;s no inherent connection between a word and its meaning, language creators have the freedom to choose words that best fit the aesthetic, phonetic, or cultural aspects of their conlang.&lt;br /&gt;
&lt;br /&gt;
For instance, consider the task of naming various species of whales in a conlang using two-element compounds. The constraints might include:&lt;br /&gt;
&lt;br /&gt;
*The last element must be &amp;quot;whale.&amp;quot;&lt;br /&gt;
*The first element must be a simple, commonly used word.&lt;br /&gt;
*Each compound must be unique and not repeated.&lt;br /&gt;
&lt;br /&gt;
Given these constraints, it&#039;s impossible to create fully descriptive names for each species. However, by embracing arbitrariness, we can craft memorable names that capture a distinctive feature or evoke a particular image associated with the species.&lt;br /&gt;
&lt;br /&gt;
==The Power of Memorable Compounds===&lt;br /&gt;
Memorable compounds serve several important functions in a conlang:&lt;br /&gt;
&lt;br /&gt;
*Ease of Learning: Words that are catchy or evoke strong imagery are easier for learners to remember and use.&lt;br /&gt;
*Cultural Depth: Unique compounds can reflect the culture, humor, or values embedded within the language.&lt;br /&gt;
*Engagement: Memorable words invite speakers to explore the language further and discover more about its structure and vocabulary.&lt;br /&gt;
&lt;br /&gt;
===Examples of Creative Compounds===&lt;br /&gt;
Let&#039;s look at some examples where memorability takes precedence over complete descriptiveness:&lt;br /&gt;
&lt;br /&gt;
*Sword Whale: Used for Sowerby&#039;s beaked whale, this name hints at the whale&#039;s elongated teeth resembling swords.&lt;br /&gt;
*Ghost Whale: For the elusive Hubbs&#039; beaked whale, emphasizing its rarity and mysterious nature.&lt;br /&gt;
*Smoke Whale: Representing Gray&#039;s beaked whale, playing on the word &amp;quot;gray&amp;quot; and the ethereal quality of smoke.&lt;br /&gt;
*Sad Whale: Assigned to the critically endangered Vaquita, invoking an emotional response to its plight.&lt;br /&gt;
*Fruit Whale: Denoting the Melon-headed whale, using &amp;quot;fruit&amp;quot; to reflect its melon-shaped head.&lt;br /&gt;
&lt;br /&gt;
These names might not fully describe the species, but they are distinctive and encourage curiosity.&lt;br /&gt;
&lt;br /&gt;
===Embracing Creativity Within Constraints===&lt;br /&gt;
Working within specific constraints can actually enhance creativity. When we limit ourselves to simple words or specific structures, we&#039;re challenged to think outside the box and find innovative solutions. This can lead to the development of a rich and dynamic vocabulary that adds depth to the conlang.&lt;br /&gt;
&lt;br /&gt;
===Conclusion===&lt;br /&gt;
In constructing a language, it&#039;s important to remember that words are tools for communication, and their effectiveness lies in how well they are received and used by speakers. By focusing on creating memorable compounds, language creators can ensure that their conlangs are not only functional but also engaging and enjoyable to learn.&lt;br /&gt;
&lt;br /&gt;
The arbitrariness of signs is not a limitation but an opportunity to infuse the language with personality and charm. So, when crafting compounds, let imagination take the lead, and don&#039;t be afraid to choose words that might seem unconventional. After all, the most memorable words are often those that surprise and delight us.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=46</id>
		<title>The sign is arbitrary</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=The_sign_is_arbitrary&amp;diff=46"/>
		<updated>2024-11-28T19:26:55Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;==The Art of Crafting Memorable Compounds in Constructed Languages==  In the world of constructed languages (conlangs), one of the most creative and enjoyable challenges is forming new words to describe concepts, objects, or creatures. A fundamental principle in linguistics is that the relationship between a word (the sign) and its meaning is arbitrary. This means that words do not inherently carry the essence of what they represent; rather, they are symbols agreed upon...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==The Art of Crafting Memorable Compounds in Constructed Languages==&lt;br /&gt;
&lt;br /&gt;
In the world of constructed languages (conlangs), one of the most creative and enjoyable challenges is forming new words to describe concepts, objects, or creatures. A fundamental principle in linguistics is that the relationship between a word (the sign) and its meaning is arbitrary. This means that words do not inherently carry the essence of what they represent; rather, they are symbols agreed upon by a language community.&lt;br /&gt;
&lt;br /&gt;
When building a conlang, especially one that relies on compound words, it&#039;s essential to focus on making these compounds memorable and engaging. While it&#039;s tempting to strive for descriptiveness, it&#039;s important to acknowledge that no compound can capture the full essence of what it&#039;s describing. Instead, the goal should be to create words that resonate with speakers and spark curiosity.&lt;br /&gt;
&lt;br /&gt;
===Why Arbitrariness Matters===&lt;br /&gt;
The arbitrary nature of signs allows for flexibility and creativity in language development. Since there&#039;s no inherent connection between a word and its meaning, language creators have the freedom to choose words that best fit the aesthetic, phonetic, or cultural aspects of their conlang.&lt;br /&gt;
&lt;br /&gt;
For instance, consider the task of naming various species of whales in a conlang using two-element compounds. The constraints might include:&lt;br /&gt;
&lt;br /&gt;
The last element must be &amp;quot;whale.&amp;quot;&lt;br /&gt;
The first element must be a simple, commonly used word.&lt;br /&gt;
Each compound must be unique and not repeated.&lt;br /&gt;
Given these constraints, it&#039;s impossible to create fully descriptive names for each species. However, by embracing arbitrariness, we can craft memorable names that capture a distinctive feature or evoke a particular image associated with the species.&lt;br /&gt;
&lt;br /&gt;
The Power of Memorable Compounds&lt;br /&gt;
Memorable compounds serve several important functions in a conlang:&lt;br /&gt;
&lt;br /&gt;
Ease of Learning: Words that are catchy or evoke strong imagery are easier for learners to remember and use.&lt;br /&gt;
Cultural Depth: Unique compounds can reflect the culture, humor, or values embedded within the language.&lt;br /&gt;
Engagement: Memorable words invite speakers to explore the language further and discover more about its structure and vocabulary.&lt;br /&gt;
Examples of Creative Compounds&lt;br /&gt;
Let&#039;s look at some examples where memorability takes precedence over complete descriptiveness:&lt;br /&gt;
&lt;br /&gt;
Sword Whale: Used for Sowerby&#039;s beaked whale, this name hints at the whale&#039;s elongated teeth resembling swords.&lt;br /&gt;
Ghost Whale: For the elusive Hubbs&#039; beaked whale, emphasizing its rarity and mysterious nature.&lt;br /&gt;
Smoke Whale: Representing Gray&#039;s beaked whale, playing on the word &amp;quot;gray&amp;quot; and the ethereal quality of smoke.&lt;br /&gt;
Sad Whale: Assigned to the critically endangered Vaquita, invoking an emotional response to its plight.&lt;br /&gt;
Fruit Whale: Denoting the Melon-headed whale, using &amp;quot;fruit&amp;quot; to reflect its melon-shaped head.&lt;br /&gt;
These names might not fully describe the species, but they are distinctive and encourage curiosity.&lt;br /&gt;
&lt;br /&gt;
Embracing Creativity Within Constraints&lt;br /&gt;
Working within specific constraints can actually enhance creativity. When we limit ourselves to simple words or specific structures, we&#039;re challenged to think outside the box and find innovative solutions. This can lead to the development of a rich and dynamic vocabulary that adds depth to the conlang.&lt;br /&gt;
&lt;br /&gt;
Conclusion&lt;br /&gt;
In constructing a language, it&#039;s important to remember that words are tools for communication, and their effectiveness lies in how well they are received and used by speakers. By focusing on creating memorable compounds, language creators can ensure that their conlangs are not only functional but also engaging and enjoyable to learn.&lt;br /&gt;
&lt;br /&gt;
The arbitrariness of signs is not a limitation but an opportunity to infuse the language with personality and charm. So, when crafting compounds, let imagination take the lead, and don&#039;t be afraid to choose words that might seem unconventional. After all, the most memorable words are often those that surprise and delight us.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=45</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=45"/>
		<updated>2024-11-28T19:26:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Lexicon */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
* [[Counting objects]]&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
* [[locative nouns]]&lt;br /&gt;
* [[tabelvortoj]]&lt;br /&gt;
&lt;br /&gt;
=== Articles ===&lt;br /&gt;
&lt;br /&gt;
* [[the sign is arbitrary]]&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
One could work backwards. 300 roots would be enough for 90k simple compounds and 27m three-element ones. Still plenty.  300 roots could be formed through 10 consonants and 3 vowels (CVC). Of course, there&#039;s absolutely no redundancy then, so probably not great for communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
* A [[chat about principles for choosing between a root or a compound]]&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=44</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=44"/>
		<updated>2024-09-23T12:03:46Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Thoughts and chats */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
* [[Counting objects]]&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
* [[locative nouns]]&lt;br /&gt;
* [[tabelvortoj]]&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
One could work backwards. 300 roots would be enough for 90k simple compounds and 27m three-element ones. Still plenty.  300 roots could be formed through 10 consonants and 3 vowels (CVC). Of course, there&#039;s absolutely no redundancy then, so probably not great for communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
* A [[chat about principles for choosing between a root or a compound]]&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=43</id>
		<title>Counting objects</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=43"/>
		<updated>2024-01-12T13:40:07Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* More thinking */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some languages simply combine numeral + object:&lt;br /&gt;
: three beer&lt;br /&gt;
&lt;br /&gt;
The problem with this is that it makes it impossible to use numbers in compounds, e.g.:&lt;br /&gt;
: three month&lt;br /&gt;
&lt;br /&gt;
Does this mean &#039;&#039;three months&#039;&#039; or &#039;&#039;March&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
On balance, I think being able to use numbers in compounds is more important than being able to use numbers without connectors.&lt;br /&gt;
&lt;br /&gt;
So we need to say something like:&lt;br /&gt;
: three GEN beer&lt;br /&gt;
: beer ADJ three&lt;br /&gt;
&lt;br /&gt;
(I&#039;m really not sure what the head and dependent are meant to be here. It requires some thought.)&lt;br /&gt;
&lt;br /&gt;
Then there&#039;s the case of using counters, like &#039;&#039;three bottles of beer&#039;&#039;. I guess the following could work:&lt;br /&gt;
: three bottle GEN beer&lt;br /&gt;
&lt;br /&gt;
Grammatically speaking, it means that &#039;&#039;three bottle&#039;&#039; is a compound. This isn&#039;t a problem if the counters are well-defined, but how would you say &#039;&#039;a three-month holiday&#039;&#039;?&lt;br /&gt;
: three month GEN holiday&lt;br /&gt;
: holiday ADJ three month&lt;br /&gt;
: holiday ADJ three GEN month&lt;br /&gt;
It&#039;s getting confusing, to be honest. The first one could mean &amp;quot;March of holiday&amp;quot; (which is nonsensical, but not necessarily to beginning learners), the second one could definitely mean &amp;quot;the March holiday&amp;quot;, and the last one could potentially be read as &amp;quot;the month&#039;s third holiday&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
We need a structure that always works, so perhaps we need a new particle so that we can say:&lt;br /&gt;
: three CNT beer&lt;br /&gt;
: three bottle CNT beer (&#039;&#039;or&#039;&#039; three CNT bottle CNT beer?)&lt;br /&gt;
: holiday ADJ three CNT month&lt;br /&gt;
&lt;br /&gt;
It&#039;s still a bit confusing.&lt;br /&gt;
&lt;br /&gt;
== ChatGPT ==&lt;br /&gt;
&lt;br /&gt;
I got ChatGPT to have a look:&lt;br /&gt;
&lt;br /&gt;
 I&#039;ll translate &amp;quot;three bottles of beer&amp;quot; into the specified languages, providing a gloss for each translation to show word order and any linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Mandarin Chinese: 三瓶啤酒 (sān píng píjiǔ)&lt;br /&gt;
&lt;br /&gt;
*三 (sān) = three&lt;br /&gt;
*瓶 (píng) = bottle (measure word)&lt;br /&gt;
*啤酒 (píjiǔ) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Hindi: तीन बोतल बीयर (tīn botal bīyar)&lt;br /&gt;
&lt;br /&gt;
*तीन (tīn) = three&lt;br /&gt;
*बोतल (botal) = bottle&lt;br /&gt;
*बीयर (bīyar) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Spanish: tres botellas de cerveza&lt;br /&gt;
&lt;br /&gt;
*tres = three&lt;br /&gt;
*botellas = bottles&lt;br /&gt;
*de = of&lt;br /&gt;
*cerveza = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Arabic: ثلاثة زجاجات بيرة (thalaatha zajaajaat biirah)&lt;br /&gt;
&lt;br /&gt;
*ثلاثة (thalaatha) = three&lt;br /&gt;
*زجاجات (zajaajaat) = bottles&lt;br /&gt;
*بيرة (biirah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Ancient Greek: τρία βοττίλια οίνου (tría bottília oínou)&lt;br /&gt;
&lt;br /&gt;
*τρία (tría) = three&lt;br /&gt;
*βοττίλια (bottília) = bottles&lt;br /&gt;
*οίνου (oínou) = of wine (note: Ancient Greek didn&#039;t have a specific word for &amp;quot;beer&amp;quot;)&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of wine&amp;quot;&lt;br /&gt;
Russian: три бутылки пива (tri butylki piva)&lt;br /&gt;
&lt;br /&gt;
*три (tri) = three&lt;br /&gt;
*бутылки (butylki) = bottles&lt;br /&gt;
*пива (piva) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Turkish: üç şişe bira&lt;br /&gt;
&lt;br /&gt;
*üç = three&lt;br /&gt;
*şişe = bottle&lt;br /&gt;
*bira = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Indonesian: tiga botol bir&lt;br /&gt;
&lt;br /&gt;
*tiga = three&lt;br /&gt;
*botol = bottle&lt;br /&gt;
*bir = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
German: drei Flaschen Bier&lt;br /&gt;
&lt;br /&gt;
*drei = three&lt;br /&gt;
*Flaschen = bottles&lt;br /&gt;
*Bier = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Swahili: chupa tatu za bia&lt;br /&gt;
&lt;br /&gt;
*chupa = bottles&lt;br /&gt;
*tatu = three&lt;br /&gt;
*za = of&lt;br /&gt;
*bia = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
This comparison shows a variety of structures, with some languages like Spanish, Ancient Greek, and Swahili using a preposition or equivalent (&amp;quot;of&amp;quot;) to link the number and type of container to the content (beer), while others like Mandarin, Hindi, Arabic, Russian, Turkish, Indonesian, and German typically follow a more direct &amp;quot;number container content&amp;quot; format without a linking word.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
The word order is really remarkably similar, given that these languages have very divergent word orders! Could you extend by looking also at Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori and Malagasy?&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, I&#039;ll extend the translation of &amp;quot;three bottles of beer&amp;quot; to include Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori, and Malagasy, with a focus on word order and linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Japanese: ビール三本 (Bīru san-bon)&lt;br /&gt;
&lt;br /&gt;
*ビール (Bīru) = beer&lt;br /&gt;
*三 (san) = three&lt;br /&gt;
*本 (bon) = counter for long, cylindrical things (like bottles)&lt;br /&gt;
*Gloss: &amp;quot;Beer three (bottles)&amp;quot;&lt;br /&gt;
Telugu: మూడు బీరు సీసాలు (Mūḍu bīru sīsālu)&lt;br /&gt;
&lt;br /&gt;
*మూడు (Mūḍu) = three&lt;br /&gt;
*బీరు (bīru) = beer&lt;br /&gt;
*సీసాలు (sīsālu) = bottles&lt;br /&gt;
*Gloss: &amp;quot;Three beer bottles&amp;quot;&lt;br /&gt;
Hebrew: שלוש בקבוקי בירה (Shalosh bakbukei birah)&lt;br /&gt;
&lt;br /&gt;
*שלוש (Shalosh) = three&lt;br /&gt;
*בקבוקי (bakbukei) = bottles (of)&lt;br /&gt;
*בירה (birah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Ewe: ɖekɔwo meɖeka me (Ɖekɔwo meɖeka me)&lt;br /&gt;
&lt;br /&gt;
*ɖekɔwo = bottles&lt;br /&gt;
*meɖeka = three&lt;br /&gt;
*me = of&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of&amp;quot;&lt;br /&gt;
Esperanto: tri boteloj da biero&lt;br /&gt;
&lt;br /&gt;
*tri = three&lt;br /&gt;
*boteloj = bottles&lt;br /&gt;
*da = of (partitive article)&lt;br /&gt;
*biero = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Maori: e toru ngā pounamu pia&lt;br /&gt;
&lt;br /&gt;
*e toru = three&lt;br /&gt;
*ngā = (definite article, plural)&lt;br /&gt;
*pounamu = bottles&lt;br /&gt;
*pia = beer&lt;br /&gt;
*Gloss: &amp;quot;Three the bottles beer&amp;quot;&lt;br /&gt;
Malagasy: tavoahangy telo an&#039;ny labiera&lt;br /&gt;
&lt;br /&gt;
*tavoahangy = bottles&lt;br /&gt;
*telo = three&lt;br /&gt;
*an&#039;ny = of (belonging to)&lt;br /&gt;
*labiera = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
In these additional languages, we still observe a mix of structures. Japanese and Telugu tend to place the object (beer) before the quantity and container, which is different from most of the previously mentioned languages. Hebrew and Esperanto follow a structure similar to Spanish or Swahili, using a word equivalent to &amp;quot;of&amp;quot; to link the bottles and beer. Ewe, Maori, and Malagasy also use a linking word, but place the numeral after the noun, unlike most Indo-European languages. This further illustrates the diverse syntactic structures used across different language families.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Japanese also allows sanbon no biiru, doesn&#039;t it?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, you&#039;re correct. In Japanese, &amp;quot;three bottles of beer&amp;quot; can also be expressed as &amp;quot;三本のビール&amp;quot; (san-bon no bīru). In this phrase:&lt;br /&gt;
&lt;br /&gt;
三本 (san-bon) means &amp;quot;three bottles,&amp;quot; with 三 (san) meaning &amp;quot;three&amp;quot; and 本 (bon) being the counter for long, cylindrical objects, including bottles.&lt;br /&gt;
の (no) is a possessive particle, often used similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
ビール (bīru) is &amp;quot;beer.&amp;quot;&lt;br /&gt;
So, &amp;quot;三本のビール&amp;quot; (san-bon no bīru) translates directly to &amp;quot;three bottles of beer,&amp;quot; with a structure that closely mirrors the English phrase. This variation demonstrates the flexibility in Japanese regarding the placement of the quantity and the object.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
So would you agree that most languages have the word order three - bottle - beer, and if there&#039;s a linking morpheme, it&#039;s typically between bottle and beer, not between three and bottle?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, based on the translations and analysis provided, it appears that in most of these diverse languages, the typical word order for the phrase &amp;quot;three bottles of beer&amp;quot; is indeed &amp;quot;three - bottle - beer.&amp;quot; Additionally, when a linking morpheme or preposition is used, it usually appears between &amp;quot;bottle&amp;quot; and &amp;quot;beer,&amp;quot; rather than between &amp;quot;three&amp;quot; and &amp;quot;bottle.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In languages where a linking morpheme is employed, it tends to function like the English &amp;quot;of&amp;quot; to denote possession or association, connecting the quantity and type of container (bottle) with its content (beer). This is observed in languages like Spanish (tres botellas de cerveza), Hebrew (שלוש בקבוקי בירה), and Esperanto (tri boteloj da biero), among others.&lt;br /&gt;
&lt;br /&gt;
On the other hand, in many languages, especially those with a tendency towards agglutination or no strict requirement for such linking words (like Mandarin, Hindi, Russian, and Japanese), the phrase follows a direct &amp;quot;three - bottle - beer&amp;quot; order without a linking morpheme. This structure reflects a more straightforward concatenation of the numerical quantity, the measure or container word, and the noun representing the content.&lt;br /&gt;
&lt;br /&gt;
This analysis underscores the fascinating variety in linguistic structures across different language families, while also revealing common patterns in how languages handle quantification and the relationship between containers and their contents.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
My problem is that I allow numerals in compounds in my conlang. So &amp;quot;March&amp;quot; is &amp;quot;three month&amp;quot; (like in Japanese), but it means that something like &amp;quot;a three month holiday&amp;quot; becomes quite ambiguous.&lt;br /&gt;
GPT&lt;br /&gt;
Your concern about ambiguity in your conlang, especially with numerals in compounds, is a valid and interesting linguistic challenge. In the case of &amp;quot;March&amp;quot; being &amp;quot;three month&amp;quot; and the potential ambiguity in a phrase like &amp;quot;a three month holiday,&amp;quot; you&#039;re encountering an issue common in language design: how to balance brevity and clarity.&lt;br /&gt;
&lt;br /&gt;
Here are a few strategies you might consider to address this:&lt;br /&gt;
&lt;br /&gt;
Contextual Clues: Rely on the surrounding context to disambiguate. This is common in natural languages, where the meaning of a word or phrase is often clear from the situation or surrounding words. However, this can sometimes lead to confusion if the context isn&#039;t clear.&lt;br /&gt;
&lt;br /&gt;
Modifiers for Compounding: Introduce a specific modifier or marker that differentiates when a numeral is part of a compound versus when it&#039;s quantifying a noun. For example, a slight alteration in pronunciation, a prefix, or a suffix could indicate that &amp;quot;three&amp;quot; in &amp;quot;three month&amp;quot; is a compound (signifying &amp;quot;March&amp;quot;) rather than a quantity.&lt;br /&gt;
&lt;br /&gt;
Structural Rules: Implement structural rules in your conlang for how compounds are formed, especially with numerals. For example, you could establish a rule that numerals at the beginning of a compound have a different function than numerals elsewhere in a phrase.&lt;br /&gt;
&lt;br /&gt;
Lexical Distinctions: Create different words or forms for numbers when they are used in compounds versus when they are used for quantification. This can add complexity to the language but also provides clear differentiation.&lt;br /&gt;
&lt;br /&gt;
Syntax-Based Disambiguation: Use word order or sentence structure to distinguish between a compound and a quantity description. For example, in your conlang, the position of the numeral in a sentence or phrase could determine its role.&lt;br /&gt;
&lt;br /&gt;
Contextual Particles or Markers: Introduce particles or markers that are used to indicate the role of a numeral in a sentence, similar to how articles, prepositions, and case markers are used in natural languages.&lt;br /&gt;
&lt;br /&gt;
Each of these strategies has its own advantages and trade-offs in terms of linguistic complexity, ease of use, and clarity. The choice depends on how you want your conlang to feel and function – whether you prefer it to be more straightforward or more nuanced and complex.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
How would you say &amp;quot;a three-month holiday&amp;quot; in Japanese?&lt;br /&gt;
GPT&lt;br /&gt;
In Japanese, &amp;quot;a three-month holiday&amp;quot; would be expressed as &amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka).&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
三 (san) means &amp;quot;three.&amp;quot;&lt;br /&gt;
ヶ月 (kagetsu) is a counter for months. The &amp;quot;ヶ&amp;quot; (ka) is a special counter used for months, and when combined with &amp;quot;月&amp;quot; (getsu), which means &amp;quot;month,&amp;quot; it denotes the number of months.&lt;br /&gt;
の (no) is a possessive particle, functioning similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
休暇 (kyūka) means &amp;quot;holiday&amp;quot; or &amp;quot;vacation.&amp;quot;&lt;br /&gt;
So, &amp;quot;三ヶ月の休暇&amp;quot; translates directly to &amp;quot;a three-month holiday&amp;quot; or &amp;quot;a holiday of three months&amp;quot; in English.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Yes, so the &amp;quot;ヶ&amp;quot; does quite a lot of work here, because the meaning is very different from  三月の休暇!&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, you&#039;ve highlighted a crucial aspect of Japanese language structure. The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; (san-kagetsu) significantly changes the meaning compared to &amp;quot;三月&amp;quot; (san-gatsu).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka) means &amp;quot;a three-month holiday.&amp;quot; Here, &amp;quot;三ヶ月&amp;quot; (san-kagetsu) refers to a duration of three months, with &amp;quot;ヶ月&amp;quot; (kagetsu) serving as a counter for months.&lt;br /&gt;
On the other hand, &amp;quot;三月の休暇&amp;quot; (san-gatsu no kyūka) means &amp;quot;a holiday in March.&amp;quot; In this case, &amp;quot;三月&amp;quot; (san-gatsu) refers to the month of March (the third month of the year).&lt;br /&gt;
The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; is a key element that transforms the numeral &amp;quot;三&amp;quot; (three) into a duration, rather than a reference to the ordinal position of a month. This distinction is a great example of how small particles and counters in Japanese can significantly alter the meaning of phrases.&lt;br /&gt;
&lt;br /&gt;
== More thinking ==&lt;br /&gt;
&lt;br /&gt;
I guess a partitive article should fix it. The examples above show that&lt;br /&gt;
: three bottle PART beer&lt;br /&gt;
would be an extremely widespread way to express this, and we shouldn&#039;t do weirdness without very good reason.&lt;br /&gt;
&lt;br /&gt;
So a three month holiday must be&lt;br /&gt;
: three month PART holiday&lt;br /&gt;
: &#039;&#039;or&#039;&#039; holiday ADJ three PART month&lt;br /&gt;
: &#039;&#039;or perhaps even&#039;&#039; three PART month PART holiday.&lt;br /&gt;
In all of these, the PART signals that the &#039;&#039;three&#039;&#039; must be read as a number, because &#039;&#039;March PART holiday&#039;&#039; makes no sense.&lt;br /&gt;
&lt;br /&gt;
We should also use the partitive without counters, e.g.:&lt;br /&gt;
: three PART month&lt;br /&gt;
: three PART beer&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=42</id>
		<title>Counting objects</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=42"/>
		<updated>2024-01-12T13:38:28Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* More thinking */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some languages simply combine numeral + object:&lt;br /&gt;
: three beer&lt;br /&gt;
&lt;br /&gt;
The problem with this is that it makes it impossible to use numbers in compounds, e.g.:&lt;br /&gt;
: three month&lt;br /&gt;
&lt;br /&gt;
Does this mean &#039;&#039;three months&#039;&#039; or &#039;&#039;March&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
On balance, I think being able to use numbers in compounds is more important than being able to use numbers without connectors.&lt;br /&gt;
&lt;br /&gt;
So we need to say something like:&lt;br /&gt;
: three GEN beer&lt;br /&gt;
: beer ADJ three&lt;br /&gt;
&lt;br /&gt;
(I&#039;m really not sure what the head and dependent are meant to be here. It requires some thought.)&lt;br /&gt;
&lt;br /&gt;
Then there&#039;s the case of using counters, like &#039;&#039;three bottles of beer&#039;&#039;. I guess the following could work:&lt;br /&gt;
: three bottle GEN beer&lt;br /&gt;
&lt;br /&gt;
Grammatically speaking, it means that &#039;&#039;three bottle&#039;&#039; is a compound. This isn&#039;t a problem if the counters are well-defined, but how would you say &#039;&#039;a three-month holiday&#039;&#039;?&lt;br /&gt;
: three month GEN holiday&lt;br /&gt;
: holiday ADJ three month&lt;br /&gt;
: holiday ADJ three GEN month&lt;br /&gt;
It&#039;s getting confusing, to be honest. The first one could mean &amp;quot;March of holiday&amp;quot; (which is nonsensical, but not necessarily to beginning learners), the second one could definitely mean &amp;quot;the March holiday&amp;quot;, and the last one could potentially be read as &amp;quot;the month&#039;s third holiday&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
We need a structure that always works, so perhaps we need a new particle so that we can say:&lt;br /&gt;
: three CNT beer&lt;br /&gt;
: three bottle CNT beer (&#039;&#039;or&#039;&#039; three CNT bottle CNT beer?)&lt;br /&gt;
: holiday ADJ three CNT month&lt;br /&gt;
&lt;br /&gt;
It&#039;s still a bit confusing.&lt;br /&gt;
&lt;br /&gt;
== ChatGPT ==&lt;br /&gt;
&lt;br /&gt;
I got ChatGPT to have a look:&lt;br /&gt;
&lt;br /&gt;
 I&#039;ll translate &amp;quot;three bottles of beer&amp;quot; into the specified languages, providing a gloss for each translation to show word order and any linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Mandarin Chinese: 三瓶啤酒 (sān píng píjiǔ)&lt;br /&gt;
&lt;br /&gt;
*三 (sān) = three&lt;br /&gt;
*瓶 (píng) = bottle (measure word)&lt;br /&gt;
*啤酒 (píjiǔ) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Hindi: तीन बोतल बीयर (tīn botal bīyar)&lt;br /&gt;
&lt;br /&gt;
*तीन (tīn) = three&lt;br /&gt;
*बोतल (botal) = bottle&lt;br /&gt;
*बीयर (bīyar) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Spanish: tres botellas de cerveza&lt;br /&gt;
&lt;br /&gt;
*tres = three&lt;br /&gt;
*botellas = bottles&lt;br /&gt;
*de = of&lt;br /&gt;
*cerveza = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Arabic: ثلاثة زجاجات بيرة (thalaatha zajaajaat biirah)&lt;br /&gt;
&lt;br /&gt;
*ثلاثة (thalaatha) = three&lt;br /&gt;
*زجاجات (zajaajaat) = bottles&lt;br /&gt;
*بيرة (biirah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Ancient Greek: τρία βοττίλια οίνου (tría bottília oínou)&lt;br /&gt;
&lt;br /&gt;
*τρία (tría) = three&lt;br /&gt;
*βοττίλια (bottília) = bottles&lt;br /&gt;
*οίνου (oínou) = of wine (note: Ancient Greek didn&#039;t have a specific word for &amp;quot;beer&amp;quot;)&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of wine&amp;quot;&lt;br /&gt;
Russian: три бутылки пива (tri butylki piva)&lt;br /&gt;
&lt;br /&gt;
*три (tri) = three&lt;br /&gt;
*бутылки (butylki) = bottles&lt;br /&gt;
*пива (piva) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Turkish: üç şişe bira&lt;br /&gt;
&lt;br /&gt;
*üç = three&lt;br /&gt;
*şişe = bottle&lt;br /&gt;
*bira = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Indonesian: tiga botol bir&lt;br /&gt;
&lt;br /&gt;
*tiga = three&lt;br /&gt;
*botol = bottle&lt;br /&gt;
*bir = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
German: drei Flaschen Bier&lt;br /&gt;
&lt;br /&gt;
*drei = three&lt;br /&gt;
*Flaschen = bottles&lt;br /&gt;
*Bier = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Swahili: chupa tatu za bia&lt;br /&gt;
&lt;br /&gt;
*chupa = bottles&lt;br /&gt;
*tatu = three&lt;br /&gt;
*za = of&lt;br /&gt;
*bia = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
This comparison shows a variety of structures, with some languages like Spanish, Ancient Greek, and Swahili using a preposition or equivalent (&amp;quot;of&amp;quot;) to link the number and type of container to the content (beer), while others like Mandarin, Hindi, Arabic, Russian, Turkish, Indonesian, and German typically follow a more direct &amp;quot;number container content&amp;quot; format without a linking word.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
The word order is really remarkably similar, given that these languages have very divergent word orders! Could you extend by looking also at Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori and Malagasy?&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, I&#039;ll extend the translation of &amp;quot;three bottles of beer&amp;quot; to include Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori, and Malagasy, with a focus on word order and linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Japanese: ビール三本 (Bīru san-bon)&lt;br /&gt;
&lt;br /&gt;
*ビール (Bīru) = beer&lt;br /&gt;
*三 (san) = three&lt;br /&gt;
*本 (bon) = counter for long, cylindrical things (like bottles)&lt;br /&gt;
*Gloss: &amp;quot;Beer three (bottles)&amp;quot;&lt;br /&gt;
Telugu: మూడు బీరు సీసాలు (Mūḍu bīru sīsālu)&lt;br /&gt;
&lt;br /&gt;
*మూడు (Mūḍu) = three&lt;br /&gt;
*బీరు (bīru) = beer&lt;br /&gt;
*సీసాలు (sīsālu) = bottles&lt;br /&gt;
*Gloss: &amp;quot;Three beer bottles&amp;quot;&lt;br /&gt;
Hebrew: שלוש בקבוקי בירה (Shalosh bakbukei birah)&lt;br /&gt;
&lt;br /&gt;
*שלוש (Shalosh) = three&lt;br /&gt;
*בקבוקי (bakbukei) = bottles (of)&lt;br /&gt;
*בירה (birah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Ewe: ɖekɔwo meɖeka me (Ɖekɔwo meɖeka me)&lt;br /&gt;
&lt;br /&gt;
*ɖekɔwo = bottles&lt;br /&gt;
*meɖeka = three&lt;br /&gt;
*me = of&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of&amp;quot;&lt;br /&gt;
Esperanto: tri boteloj da biero&lt;br /&gt;
&lt;br /&gt;
*tri = three&lt;br /&gt;
*boteloj = bottles&lt;br /&gt;
*da = of (partitive article)&lt;br /&gt;
*biero = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Maori: e toru ngā pounamu pia&lt;br /&gt;
&lt;br /&gt;
*e toru = three&lt;br /&gt;
*ngā = (definite article, plural)&lt;br /&gt;
*pounamu = bottles&lt;br /&gt;
*pia = beer&lt;br /&gt;
*Gloss: &amp;quot;Three the bottles beer&amp;quot;&lt;br /&gt;
Malagasy: tavoahangy telo an&#039;ny labiera&lt;br /&gt;
&lt;br /&gt;
*tavoahangy = bottles&lt;br /&gt;
*telo = three&lt;br /&gt;
*an&#039;ny = of (belonging to)&lt;br /&gt;
*labiera = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
In these additional languages, we still observe a mix of structures. Japanese and Telugu tend to place the object (beer) before the quantity and container, which is different from most of the previously mentioned languages. Hebrew and Esperanto follow a structure similar to Spanish or Swahili, using a word equivalent to &amp;quot;of&amp;quot; to link the bottles and beer. Ewe, Maori, and Malagasy also use a linking word, but place the numeral after the noun, unlike most Indo-European languages. This further illustrates the diverse syntactic structures used across different language families.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Japanese also allows sanbon no biiru, doesn&#039;t it?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, you&#039;re correct. In Japanese, &amp;quot;three bottles of beer&amp;quot; can also be expressed as &amp;quot;三本のビール&amp;quot; (san-bon no bīru). In this phrase:&lt;br /&gt;
&lt;br /&gt;
三本 (san-bon) means &amp;quot;three bottles,&amp;quot; with 三 (san) meaning &amp;quot;three&amp;quot; and 本 (bon) being the counter for long, cylindrical objects, including bottles.&lt;br /&gt;
の (no) is a possessive particle, often used similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
ビール (bīru) is &amp;quot;beer.&amp;quot;&lt;br /&gt;
So, &amp;quot;三本のビール&amp;quot; (san-bon no bīru) translates directly to &amp;quot;three bottles of beer,&amp;quot; with a structure that closely mirrors the English phrase. This variation demonstrates the flexibility in Japanese regarding the placement of the quantity and the object.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
So would you agree that most languages have the word order three - bottle - beer, and if there&#039;s a linking morpheme, it&#039;s typically between bottle and beer, not between three and bottle?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, based on the translations and analysis provided, it appears that in most of these diverse languages, the typical word order for the phrase &amp;quot;three bottles of beer&amp;quot; is indeed &amp;quot;three - bottle - beer.&amp;quot; Additionally, when a linking morpheme or preposition is used, it usually appears between &amp;quot;bottle&amp;quot; and &amp;quot;beer,&amp;quot; rather than between &amp;quot;three&amp;quot; and &amp;quot;bottle.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In languages where a linking morpheme is employed, it tends to function like the English &amp;quot;of&amp;quot; to denote possession or association, connecting the quantity and type of container (bottle) with its content (beer). This is observed in languages like Spanish (tres botellas de cerveza), Hebrew (שלוש בקבוקי בירה), and Esperanto (tri boteloj da biero), among others.&lt;br /&gt;
&lt;br /&gt;
On the other hand, in many languages, especially those with a tendency towards agglutination or no strict requirement for such linking words (like Mandarin, Hindi, Russian, and Japanese), the phrase follows a direct &amp;quot;three - bottle - beer&amp;quot; order without a linking morpheme. This structure reflects a more straightforward concatenation of the numerical quantity, the measure or container word, and the noun representing the content.&lt;br /&gt;
&lt;br /&gt;
This analysis underscores the fascinating variety in linguistic structures across different language families, while also revealing common patterns in how languages handle quantification and the relationship between containers and their contents.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
My problem is that I allow numerals in compounds in my conlang. So &amp;quot;March&amp;quot; is &amp;quot;three month&amp;quot; (like in Japanese), but it means that something like &amp;quot;a three month holiday&amp;quot; becomes quite ambiguous.&lt;br /&gt;
GPT&lt;br /&gt;
Your concern about ambiguity in your conlang, especially with numerals in compounds, is a valid and interesting linguistic challenge. In the case of &amp;quot;March&amp;quot; being &amp;quot;three month&amp;quot; and the potential ambiguity in a phrase like &amp;quot;a three month holiday,&amp;quot; you&#039;re encountering an issue common in language design: how to balance brevity and clarity.&lt;br /&gt;
&lt;br /&gt;
Here are a few strategies you might consider to address this:&lt;br /&gt;
&lt;br /&gt;
Contextual Clues: Rely on the surrounding context to disambiguate. This is common in natural languages, where the meaning of a word or phrase is often clear from the situation or surrounding words. However, this can sometimes lead to confusion if the context isn&#039;t clear.&lt;br /&gt;
&lt;br /&gt;
Modifiers for Compounding: Introduce a specific modifier or marker that differentiates when a numeral is part of a compound versus when it&#039;s quantifying a noun. For example, a slight alteration in pronunciation, a prefix, or a suffix could indicate that &amp;quot;three&amp;quot; in &amp;quot;three month&amp;quot; is a compound (signifying &amp;quot;March&amp;quot;) rather than a quantity.&lt;br /&gt;
&lt;br /&gt;
Structural Rules: Implement structural rules in your conlang for how compounds are formed, especially with numerals. For example, you could establish a rule that numerals at the beginning of a compound have a different function than numerals elsewhere in a phrase.&lt;br /&gt;
&lt;br /&gt;
Lexical Distinctions: Create different words or forms for numbers when they are used in compounds versus when they are used for quantification. This can add complexity to the language but also provides clear differentiation.&lt;br /&gt;
&lt;br /&gt;
Syntax-Based Disambiguation: Use word order or sentence structure to distinguish between a compound and a quantity description. For example, in your conlang, the position of the numeral in a sentence or phrase could determine its role.&lt;br /&gt;
&lt;br /&gt;
Contextual Particles or Markers: Introduce particles or markers that are used to indicate the role of a numeral in a sentence, similar to how articles, prepositions, and case markers are used in natural languages.&lt;br /&gt;
&lt;br /&gt;
Each of these strategies has its own advantages and trade-offs in terms of linguistic complexity, ease of use, and clarity. The choice depends on how you want your conlang to feel and function – whether you prefer it to be more straightforward or more nuanced and complex.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
How would you say &amp;quot;a three-month holiday&amp;quot; in Japanese?&lt;br /&gt;
GPT&lt;br /&gt;
In Japanese, &amp;quot;a three-month holiday&amp;quot; would be expressed as &amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka).&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
三 (san) means &amp;quot;three.&amp;quot;&lt;br /&gt;
ヶ月 (kagetsu) is a counter for months. The &amp;quot;ヶ&amp;quot; (ka) is a special counter used for months, and when combined with &amp;quot;月&amp;quot; (getsu), which means &amp;quot;month,&amp;quot; it denotes the number of months.&lt;br /&gt;
の (no) is a possessive particle, functioning similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
休暇 (kyūka) means &amp;quot;holiday&amp;quot; or &amp;quot;vacation.&amp;quot;&lt;br /&gt;
So, &amp;quot;三ヶ月の休暇&amp;quot; translates directly to &amp;quot;a three-month holiday&amp;quot; or &amp;quot;a holiday of three months&amp;quot; in English.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Yes, so the &amp;quot;ヶ&amp;quot; does quite a lot of work here, because the meaning is very different from  三月の休暇!&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, you&#039;ve highlighted a crucial aspect of Japanese language structure. The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; (san-kagetsu) significantly changes the meaning compared to &amp;quot;三月&amp;quot; (san-gatsu).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka) means &amp;quot;a three-month holiday.&amp;quot; Here, &amp;quot;三ヶ月&amp;quot; (san-kagetsu) refers to a duration of three months, with &amp;quot;ヶ月&amp;quot; (kagetsu) serving as a counter for months.&lt;br /&gt;
On the other hand, &amp;quot;三月の休暇&amp;quot; (san-gatsu no kyūka) means &amp;quot;a holiday in March.&amp;quot; In this case, &amp;quot;三月&amp;quot; (san-gatsu) refers to the month of March (the third month of the year).&lt;br /&gt;
The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; is a key element that transforms the numeral &amp;quot;三&amp;quot; (three) into a duration, rather than a reference to the ordinal position of a month. This distinction is a great example of how small particles and counters in Japanese can significantly alter the meaning of phrases.&lt;br /&gt;
&lt;br /&gt;
== More thinking ==&lt;br /&gt;
&lt;br /&gt;
I guess a partitive article should fix it. The examples above show that&lt;br /&gt;
: three bottle PART beer&lt;br /&gt;
would be an extremely widespread way to express this, and we shouldn&#039;t do weirdness without very good reason.&lt;br /&gt;
&lt;br /&gt;
So a three month holiday must be&lt;br /&gt;
: three month PART holiday&lt;br /&gt;
: &#039;&#039;or&#039;&#039; holiday ADJ three PART month&lt;br /&gt;
: &#039;&#039;or perhaps even&#039;&#039; three PART month PART holiday.&lt;br /&gt;
In all of these, the PART signals that the &#039;&#039;three&#039;&#039; must be read as a number, because &#039;&#039;March PART holiday&#039;&#039; makes no sense.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=41</id>
		<title>Counting objects</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=41"/>
		<updated>2024-01-12T13:38:07Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some languages simply combine numeral + object:&lt;br /&gt;
: three beer&lt;br /&gt;
&lt;br /&gt;
The problem with this is that it makes it impossible to use numbers in compounds, e.g.:&lt;br /&gt;
: three month&lt;br /&gt;
&lt;br /&gt;
Does this mean &#039;&#039;three months&#039;&#039; or &#039;&#039;March&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
On balance, I think being able to use numbers in compounds is more important than being able to use numbers without connectors.&lt;br /&gt;
&lt;br /&gt;
So we need to say something like:&lt;br /&gt;
: three GEN beer&lt;br /&gt;
: beer ADJ three&lt;br /&gt;
&lt;br /&gt;
(I&#039;m really not sure what the head and dependent are meant to be here. It requires some thought.)&lt;br /&gt;
&lt;br /&gt;
Then there&#039;s the case of using counters, like &#039;&#039;three bottles of beer&#039;&#039;. I guess the following could work:&lt;br /&gt;
: three bottle GEN beer&lt;br /&gt;
&lt;br /&gt;
Grammatically speaking, it means that &#039;&#039;three bottle&#039;&#039; is a compound. This isn&#039;t a problem if the counters are well-defined, but how would you say &#039;&#039;a three-month holiday&#039;&#039;?&lt;br /&gt;
: three month GEN holiday&lt;br /&gt;
: holiday ADJ three month&lt;br /&gt;
: holiday ADJ three GEN month&lt;br /&gt;
It&#039;s getting confusing, to be honest. The first one could mean &amp;quot;March of holiday&amp;quot; (which is nonsensical, but not necessarily to beginning learners), the second one could definitely mean &amp;quot;the March holiday&amp;quot;, and the last one could potentially be read as &amp;quot;the month&#039;s third holiday&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
We need a structure that always works, so perhaps we need a new particle so that we can say:&lt;br /&gt;
: three CNT beer&lt;br /&gt;
: three bottle CNT beer (&#039;&#039;or&#039;&#039; three CNT bottle CNT beer?)&lt;br /&gt;
: holiday ADJ three CNT month&lt;br /&gt;
&lt;br /&gt;
It&#039;s still a bit confusing.&lt;br /&gt;
&lt;br /&gt;
== ChatGPT ==&lt;br /&gt;
&lt;br /&gt;
I got ChatGPT to have a look:&lt;br /&gt;
&lt;br /&gt;
 I&#039;ll translate &amp;quot;three bottles of beer&amp;quot; into the specified languages, providing a gloss for each translation to show word order and any linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Mandarin Chinese: 三瓶啤酒 (sān píng píjiǔ)&lt;br /&gt;
&lt;br /&gt;
*三 (sān) = three&lt;br /&gt;
*瓶 (píng) = bottle (measure word)&lt;br /&gt;
*啤酒 (píjiǔ) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Hindi: तीन बोतल बीयर (tīn botal bīyar)&lt;br /&gt;
&lt;br /&gt;
*तीन (tīn) = three&lt;br /&gt;
*बोतल (botal) = bottle&lt;br /&gt;
*बीयर (bīyar) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Spanish: tres botellas de cerveza&lt;br /&gt;
&lt;br /&gt;
*tres = three&lt;br /&gt;
*botellas = bottles&lt;br /&gt;
*de = of&lt;br /&gt;
*cerveza = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Arabic: ثلاثة زجاجات بيرة (thalaatha zajaajaat biirah)&lt;br /&gt;
&lt;br /&gt;
*ثلاثة (thalaatha) = three&lt;br /&gt;
*زجاجات (zajaajaat) = bottles&lt;br /&gt;
*بيرة (biirah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Ancient Greek: τρία βοττίλια οίνου (tría bottília oínou)&lt;br /&gt;
&lt;br /&gt;
*τρία (tría) = three&lt;br /&gt;
*βοττίλια (bottília) = bottles&lt;br /&gt;
*οίνου (oínou) = of wine (note: Ancient Greek didn&#039;t have a specific word for &amp;quot;beer&amp;quot;)&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of wine&amp;quot;&lt;br /&gt;
Russian: три бутылки пива (tri butylki piva)&lt;br /&gt;
&lt;br /&gt;
*три (tri) = three&lt;br /&gt;
*бутылки (butylki) = bottles&lt;br /&gt;
*пива (piva) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Turkish: üç şişe bira&lt;br /&gt;
&lt;br /&gt;
*üç = three&lt;br /&gt;
*şişe = bottle&lt;br /&gt;
*bira = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Indonesian: tiga botol bir&lt;br /&gt;
&lt;br /&gt;
*tiga = three&lt;br /&gt;
*botol = bottle&lt;br /&gt;
*bir = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
German: drei Flaschen Bier&lt;br /&gt;
&lt;br /&gt;
*drei = three&lt;br /&gt;
*Flaschen = bottles&lt;br /&gt;
*Bier = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Swahili: chupa tatu za bia&lt;br /&gt;
&lt;br /&gt;
*chupa = bottles&lt;br /&gt;
*tatu = three&lt;br /&gt;
*za = of&lt;br /&gt;
*bia = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
This comparison shows a variety of structures, with some languages like Spanish, Ancient Greek, and Swahili using a preposition or equivalent (&amp;quot;of&amp;quot;) to link the number and type of container to the content (beer), while others like Mandarin, Hindi, Arabic, Russian, Turkish, Indonesian, and German typically follow a more direct &amp;quot;number container content&amp;quot; format without a linking word.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
The word order is really remarkably similar, given that these languages have very divergent word orders! Could you extend by looking also at Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori and Malagasy?&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, I&#039;ll extend the translation of &amp;quot;three bottles of beer&amp;quot; to include Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori, and Malagasy, with a focus on word order and linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Japanese: ビール三本 (Bīru san-bon)&lt;br /&gt;
&lt;br /&gt;
*ビール (Bīru) = beer&lt;br /&gt;
*三 (san) = three&lt;br /&gt;
*本 (bon) = counter for long, cylindrical things (like bottles)&lt;br /&gt;
*Gloss: &amp;quot;Beer three (bottles)&amp;quot;&lt;br /&gt;
Telugu: మూడు బీరు సీసాలు (Mūḍu bīru sīsālu)&lt;br /&gt;
&lt;br /&gt;
*మూడు (Mūḍu) = three&lt;br /&gt;
*బీరు (bīru) = beer&lt;br /&gt;
*సీసాలు (sīsālu) = bottles&lt;br /&gt;
*Gloss: &amp;quot;Three beer bottles&amp;quot;&lt;br /&gt;
Hebrew: שלוש בקבוקי בירה (Shalosh bakbukei birah)&lt;br /&gt;
&lt;br /&gt;
*שלוש (Shalosh) = three&lt;br /&gt;
*בקבוקי (bakbukei) = bottles (of)&lt;br /&gt;
*בירה (birah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Ewe: ɖekɔwo meɖeka me (Ɖekɔwo meɖeka me)&lt;br /&gt;
&lt;br /&gt;
*ɖekɔwo = bottles&lt;br /&gt;
*meɖeka = three&lt;br /&gt;
*me = of&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of&amp;quot;&lt;br /&gt;
Esperanto: tri boteloj da biero&lt;br /&gt;
&lt;br /&gt;
*tri = three&lt;br /&gt;
*boteloj = bottles&lt;br /&gt;
*da = of (partitive article)&lt;br /&gt;
*biero = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Maori: e toru ngā pounamu pia&lt;br /&gt;
&lt;br /&gt;
*e toru = three&lt;br /&gt;
*ngā = (definite article, plural)&lt;br /&gt;
*pounamu = bottles&lt;br /&gt;
*pia = beer&lt;br /&gt;
*Gloss: &amp;quot;Three the bottles beer&amp;quot;&lt;br /&gt;
Malagasy: tavoahangy telo an&#039;ny labiera&lt;br /&gt;
&lt;br /&gt;
*tavoahangy = bottles&lt;br /&gt;
*telo = three&lt;br /&gt;
*an&#039;ny = of (belonging to)&lt;br /&gt;
*labiera = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
In these additional languages, we still observe a mix of structures. Japanese and Telugu tend to place the object (beer) before the quantity and container, which is different from most of the previously mentioned languages. Hebrew and Esperanto follow a structure similar to Spanish or Swahili, using a word equivalent to &amp;quot;of&amp;quot; to link the bottles and beer. Ewe, Maori, and Malagasy also use a linking word, but place the numeral after the noun, unlike most Indo-European languages. This further illustrates the diverse syntactic structures used across different language families.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Japanese also allows sanbon no biiru, doesn&#039;t it?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, you&#039;re correct. In Japanese, &amp;quot;three bottles of beer&amp;quot; can also be expressed as &amp;quot;三本のビール&amp;quot; (san-bon no bīru). In this phrase:&lt;br /&gt;
&lt;br /&gt;
三本 (san-bon) means &amp;quot;three bottles,&amp;quot; with 三 (san) meaning &amp;quot;three&amp;quot; and 本 (bon) being the counter for long, cylindrical objects, including bottles.&lt;br /&gt;
の (no) is a possessive particle, often used similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
ビール (bīru) is &amp;quot;beer.&amp;quot;&lt;br /&gt;
So, &amp;quot;三本のビール&amp;quot; (san-bon no bīru) translates directly to &amp;quot;three bottles of beer,&amp;quot; with a structure that closely mirrors the English phrase. This variation demonstrates the flexibility in Japanese regarding the placement of the quantity and the object.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
So would you agree that most languages have the word order three - bottle - beer, and if there&#039;s a linking morpheme, it&#039;s typically between bottle and beer, not between three and bottle?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, based on the translations and analysis provided, it appears that in most of these diverse languages, the typical word order for the phrase &amp;quot;three bottles of beer&amp;quot; is indeed &amp;quot;three - bottle - beer.&amp;quot; Additionally, when a linking morpheme or preposition is used, it usually appears between &amp;quot;bottle&amp;quot; and &amp;quot;beer,&amp;quot; rather than between &amp;quot;three&amp;quot; and &amp;quot;bottle.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In languages where a linking morpheme is employed, it tends to function like the English &amp;quot;of&amp;quot; to denote possession or association, connecting the quantity and type of container (bottle) with its content (beer). This is observed in languages like Spanish (tres botellas de cerveza), Hebrew (שלוש בקבוקי בירה), and Esperanto (tri boteloj da biero), among others.&lt;br /&gt;
&lt;br /&gt;
On the other hand, in many languages, especially those with a tendency towards agglutination or no strict requirement for such linking words (like Mandarin, Hindi, Russian, and Japanese), the phrase follows a direct &amp;quot;three - bottle - beer&amp;quot; order without a linking morpheme. This structure reflects a more straightforward concatenation of the numerical quantity, the measure or container word, and the noun representing the content.&lt;br /&gt;
&lt;br /&gt;
This analysis underscores the fascinating variety in linguistic structures across different language families, while also revealing common patterns in how languages handle quantification and the relationship between containers and their contents.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
My problem is that I allow numerals in compounds in my conlang. So &amp;quot;March&amp;quot; is &amp;quot;three month&amp;quot; (like in Japanese), but it means that something like &amp;quot;a three month holiday&amp;quot; becomes quite ambiguous.&lt;br /&gt;
GPT&lt;br /&gt;
Your concern about ambiguity in your conlang, especially with numerals in compounds, is a valid and interesting linguistic challenge. In the case of &amp;quot;March&amp;quot; being &amp;quot;three month&amp;quot; and the potential ambiguity in a phrase like &amp;quot;a three month holiday,&amp;quot; you&#039;re encountering an issue common in language design: how to balance brevity and clarity.&lt;br /&gt;
&lt;br /&gt;
Here are a few strategies you might consider to address this:&lt;br /&gt;
&lt;br /&gt;
Contextual Clues: Rely on the surrounding context to disambiguate. This is common in natural languages, where the meaning of a word or phrase is often clear from the situation or surrounding words. However, this can sometimes lead to confusion if the context isn&#039;t clear.&lt;br /&gt;
&lt;br /&gt;
Modifiers for Compounding: Introduce a specific modifier or marker that differentiates when a numeral is part of a compound versus when it&#039;s quantifying a noun. For example, a slight alteration in pronunciation, a prefix, or a suffix could indicate that &amp;quot;three&amp;quot; in &amp;quot;three month&amp;quot; is a compound (signifying &amp;quot;March&amp;quot;) rather than a quantity.&lt;br /&gt;
&lt;br /&gt;
Structural Rules: Implement structural rules in your conlang for how compounds are formed, especially with numerals. For example, you could establish a rule that numerals at the beginning of a compound have a different function than numerals elsewhere in a phrase.&lt;br /&gt;
&lt;br /&gt;
Lexical Distinctions: Create different words or forms for numbers when they are used in compounds versus when they are used for quantification. This can add complexity to the language but also provides clear differentiation.&lt;br /&gt;
&lt;br /&gt;
Syntax-Based Disambiguation: Use word order or sentence structure to distinguish between a compound and a quantity description. For example, in your conlang, the position of the numeral in a sentence or phrase could determine its role.&lt;br /&gt;
&lt;br /&gt;
Contextual Particles or Markers: Introduce particles or markers that are used to indicate the role of a numeral in a sentence, similar to how articles, prepositions, and case markers are used in natural languages.&lt;br /&gt;
&lt;br /&gt;
Each of these strategies has its own advantages and trade-offs in terms of linguistic complexity, ease of use, and clarity. The choice depends on how you want your conlang to feel and function – whether you prefer it to be more straightforward or more nuanced and complex.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
How would you say &amp;quot;a three-month holiday&amp;quot; in Japanese?&lt;br /&gt;
GPT&lt;br /&gt;
In Japanese, &amp;quot;a three-month holiday&amp;quot; would be expressed as &amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka).&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
三 (san) means &amp;quot;three.&amp;quot;&lt;br /&gt;
ヶ月 (kagetsu) is a counter for months. The &amp;quot;ヶ&amp;quot; (ka) is a special counter used for months, and when combined with &amp;quot;月&amp;quot; (getsu), which means &amp;quot;month,&amp;quot; it denotes the number of months.&lt;br /&gt;
の (no) is a possessive particle, functioning similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
休暇 (kyūka) means &amp;quot;holiday&amp;quot; or &amp;quot;vacation.&amp;quot;&lt;br /&gt;
So, &amp;quot;三ヶ月の休暇&amp;quot; translates directly to &amp;quot;a three-month holiday&amp;quot; or &amp;quot;a holiday of three months&amp;quot; in English.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Yes, so the &amp;quot;ヶ&amp;quot; does quite a lot of work here, because the meaning is very different from  三月の休暇!&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, you&#039;ve highlighted a crucial aspect of Japanese language structure. The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; (san-kagetsu) significantly changes the meaning compared to &amp;quot;三月&amp;quot; (san-gatsu).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka) means &amp;quot;a three-month holiday.&amp;quot; Here, &amp;quot;三ヶ月&amp;quot; (san-kagetsu) refers to a duration of three months, with &amp;quot;ヶ月&amp;quot; (kagetsu) serving as a counter for months.&lt;br /&gt;
On the other hand, &amp;quot;三月の休暇&amp;quot; (san-gatsu no kyūka) means &amp;quot;a holiday in March.&amp;quot; In this case, &amp;quot;三月&amp;quot; (san-gatsu) refers to the month of March (the third month of the year).&lt;br /&gt;
The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; is a key element that transforms the numeral &amp;quot;三&amp;quot; (three) into a duration, rather than a reference to the ordinal position of a month. This distinction is a great example of how small particles and counters in Japanese can significantly alter the meaning of phrases.&lt;br /&gt;
&lt;br /&gt;
== More thinking ==&lt;br /&gt;
&lt;br /&gt;
I guess a partitive article should fix it. The examples above show that&lt;br /&gt;
: three bottle PART beer&lt;br /&gt;
would be an extremely widespread way to express this, and we should do weirdness without very good reason.&lt;br /&gt;
&lt;br /&gt;
So a three month holiday must be&lt;br /&gt;
: three month PART holiday&lt;br /&gt;
: &#039;&#039;or&#039;&#039; holiday ADJ three PART month&lt;br /&gt;
: &#039;&#039;or perhaps even&#039;&#039; three PART month PART holiday.&lt;br /&gt;
In all of these, the PART signals that the &#039;&#039;three&#039;&#039; must be read as a number, because &#039;&#039;March PART holiday&#039;&#039; makes no sense.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=40</id>
		<title>Counting objects</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=40"/>
		<updated>2024-01-12T13:32:26Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some languages simply combine numeral + object:&lt;br /&gt;
: three beer&lt;br /&gt;
&lt;br /&gt;
The problem with this is that it makes it impossible to use numbers in compounds, e.g.:&lt;br /&gt;
: three month&lt;br /&gt;
&lt;br /&gt;
Does this mean &#039;&#039;three months&#039;&#039; or &#039;&#039;March&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
On balance, I think being able to use numbers in compounds is more important than being able to use numbers without connectors.&lt;br /&gt;
&lt;br /&gt;
So we need to say something like:&lt;br /&gt;
: three GEN beer&lt;br /&gt;
: beer ADJ three&lt;br /&gt;
&lt;br /&gt;
(I&#039;m really not sure what the head and dependent are meant to be here. It requires some thought.)&lt;br /&gt;
&lt;br /&gt;
Then there&#039;s the case of using counters, like &#039;&#039;three bottles of beer&#039;&#039;. I guess the following could work:&lt;br /&gt;
: three bottle GEN beer&lt;br /&gt;
&lt;br /&gt;
Grammatically speaking, it means that &#039;&#039;three bottle&#039;&#039; is a compound. This isn&#039;t a problem if the counters are well-defined, but how would you say &#039;&#039;a three-month holiday&#039;&#039;?&lt;br /&gt;
: three month GEN holiday&lt;br /&gt;
: holiday ADJ three month&lt;br /&gt;
: holiday ADJ three GEN month&lt;br /&gt;
It&#039;s getting confusing, to be honest. The first one could mean &amp;quot;March of holiday&amp;quot; (which is nonsensical, but not necessarily to beginning learners), the second one could definitely mean &amp;quot;the March holiday&amp;quot;, and the last one could potentially be read as &amp;quot;the month&#039;s third holiday&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
We need a structure that always works, so perhaps we need a new particle so that we can say:&lt;br /&gt;
: three CNT beer&lt;br /&gt;
: three bottle CNT beer (&#039;&#039;or&#039;&#039; three CNT bottle CNT beer?)&lt;br /&gt;
: holiday ADJ three CNT month&lt;br /&gt;
&lt;br /&gt;
It&#039;s still a bit confusing.&lt;br /&gt;
&lt;br /&gt;
== ChatGPT ==&lt;br /&gt;
&lt;br /&gt;
I got ChatGPT to have a look:&lt;br /&gt;
&lt;br /&gt;
 I&#039;ll translate &amp;quot;three bottles of beer&amp;quot; into the specified languages, providing a gloss for each translation to show word order and any linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Mandarin Chinese: 三瓶啤酒 (sān píng píjiǔ)&lt;br /&gt;
&lt;br /&gt;
*三 (sān) = three&lt;br /&gt;
*瓶 (píng) = bottle (measure word)&lt;br /&gt;
*啤酒 (píjiǔ) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Hindi: तीन बोतल बीयर (tīn botal bīyar)&lt;br /&gt;
&lt;br /&gt;
*तीन (tīn) = three&lt;br /&gt;
*बोतल (botal) = bottle&lt;br /&gt;
*बीयर (bīyar) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Spanish: tres botellas de cerveza&lt;br /&gt;
&lt;br /&gt;
*tres = three&lt;br /&gt;
*botellas = bottles&lt;br /&gt;
*de = of&lt;br /&gt;
*cerveza = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Arabic: ثلاثة زجاجات بيرة (thalaatha zajaajaat biirah)&lt;br /&gt;
&lt;br /&gt;
*ثلاثة (thalaatha) = three&lt;br /&gt;
*زجاجات (zajaajaat) = bottles&lt;br /&gt;
*بيرة (biirah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Ancient Greek: τρία βοττίλια οίνου (tría bottília oínou)&lt;br /&gt;
&lt;br /&gt;
*τρία (tría) = three&lt;br /&gt;
*βοττίλια (bottília) = bottles&lt;br /&gt;
*οίνου (oínou) = of wine (note: Ancient Greek didn&#039;t have a specific word for &amp;quot;beer&amp;quot;)&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of wine&amp;quot;&lt;br /&gt;
Russian: три бутылки пива (tri butylki piva)&lt;br /&gt;
&lt;br /&gt;
*три (tri) = three&lt;br /&gt;
*бутылки (butylki) = bottles&lt;br /&gt;
*пива (piva) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Turkish: üç şişe bira&lt;br /&gt;
&lt;br /&gt;
*üç = three&lt;br /&gt;
*şişe = bottle&lt;br /&gt;
*bira = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
Indonesian: tiga botol bir&lt;br /&gt;
&lt;br /&gt;
*tiga = three&lt;br /&gt;
*botol = bottle&lt;br /&gt;
*bir = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottle beer&amp;quot;&lt;br /&gt;
German: drei Flaschen Bier&lt;br /&gt;
&lt;br /&gt;
*drei = three&lt;br /&gt;
*Flaschen = bottles&lt;br /&gt;
*Bier = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles beer&amp;quot;&lt;br /&gt;
Swahili: chupa tatu za bia&lt;br /&gt;
&lt;br /&gt;
*chupa = bottles&lt;br /&gt;
*tatu = three&lt;br /&gt;
*za = of&lt;br /&gt;
*bia = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
This comparison shows a variety of structures, with some languages like Spanish, Ancient Greek, and Swahili using a preposition or equivalent (&amp;quot;of&amp;quot;) to link the number and type of container to the content (beer), while others like Mandarin, Hindi, Arabic, Russian, Turkish, Indonesian, and German typically follow a more direct &amp;quot;number container content&amp;quot; format without a linking word.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
The word order is really remarkably similar, given that these languages have very divergent word orders! Could you extend by looking also at Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori and Malagasy?&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, I&#039;ll extend the translation of &amp;quot;three bottles of beer&amp;quot; to include Japanese, Telugu, Hebrew, Ewe, Esperanto, Maori, and Malagasy, with a focus on word order and linking morphemes.&lt;br /&gt;
&lt;br /&gt;
Japanese: ビール三本 (Bīru san-bon)&lt;br /&gt;
&lt;br /&gt;
*ビール (Bīru) = beer&lt;br /&gt;
*三 (san) = three&lt;br /&gt;
*本 (bon) = counter for long, cylindrical things (like bottles)&lt;br /&gt;
*Gloss: &amp;quot;Beer three (bottles)&amp;quot;&lt;br /&gt;
Telugu: మూడు బీరు సీసాలు (Mūḍu bīru sīsālu)&lt;br /&gt;
&lt;br /&gt;
*మూడు (Mūḍu) = three&lt;br /&gt;
*బీరు (bīru) = beer&lt;br /&gt;
*సీసాలు (sīsālu) = bottles&lt;br /&gt;
*Gloss: &amp;quot;Three beer bottles&amp;quot;&lt;br /&gt;
Hebrew: שלוש בקבוקי בירה (Shalosh bakbukei birah)&lt;br /&gt;
&lt;br /&gt;
*שלוש (Shalosh) = three&lt;br /&gt;
*בקבוקי (bakbukei) = bottles (of)&lt;br /&gt;
*בירה (birah) = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Ewe: ɖekɔwo meɖeka me (Ɖekɔwo meɖeka me)&lt;br /&gt;
&lt;br /&gt;
*ɖekɔwo = bottles&lt;br /&gt;
*meɖeka = three&lt;br /&gt;
*me = of&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of&amp;quot;&lt;br /&gt;
Esperanto: tri boteloj da biero&lt;br /&gt;
&lt;br /&gt;
*tri = three&lt;br /&gt;
*boteloj = bottles&lt;br /&gt;
*da = of (partitive article)&lt;br /&gt;
*biero = beer&lt;br /&gt;
*Gloss: &amp;quot;Three bottles of beer&amp;quot;&lt;br /&gt;
Maori: e toru ngā pounamu pia&lt;br /&gt;
&lt;br /&gt;
*e toru = three&lt;br /&gt;
*ngā = (definite article, plural)&lt;br /&gt;
*pounamu = bottles&lt;br /&gt;
*pia = beer&lt;br /&gt;
*Gloss: &amp;quot;Three the bottles beer&amp;quot;&lt;br /&gt;
Malagasy: tavoahangy telo an&#039;ny labiera&lt;br /&gt;
&lt;br /&gt;
*tavoahangy = bottles&lt;br /&gt;
*telo = three&lt;br /&gt;
*an&#039;ny = of (belonging to)&lt;br /&gt;
*labiera = beer&lt;br /&gt;
*Gloss: &amp;quot;Bottles three of beer&amp;quot;&lt;br /&gt;
In these additional languages, we still observe a mix of structures. Japanese and Telugu tend to place the object (beer) before the quantity and container, which is different from most of the previously mentioned languages. Hebrew and Esperanto follow a structure similar to Spanish or Swahili, using a word equivalent to &amp;quot;of&amp;quot; to link the bottles and beer. Ewe, Maori, and Malagasy also use a linking word, but place the numeral after the noun, unlike most Indo-European languages. This further illustrates the diverse syntactic structures used across different language families.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Japanese also allows sanbon no biiru, doesn&#039;t it?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, you&#039;re correct. In Japanese, &amp;quot;three bottles of beer&amp;quot; can also be expressed as &amp;quot;三本のビール&amp;quot; (san-bon no bīru). In this phrase:&lt;br /&gt;
&lt;br /&gt;
三本 (san-bon) means &amp;quot;three bottles,&amp;quot; with 三 (san) meaning &amp;quot;three&amp;quot; and 本 (bon) being the counter for long, cylindrical objects, including bottles.&lt;br /&gt;
の (no) is a possessive particle, often used similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
ビール (bīru) is &amp;quot;beer.&amp;quot;&lt;br /&gt;
So, &amp;quot;三本のビール&amp;quot; (san-bon no bīru) translates directly to &amp;quot;three bottles of beer,&amp;quot; with a structure that closely mirrors the English phrase. This variation demonstrates the flexibility in Japanese regarding the placement of the quantity and the object.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
So would you agree that most languages have the word order three - bottle - beer, and if there&#039;s a linking morpheme, it&#039;s typically between bottle and beer, not between three and bottle?&lt;br /&gt;
GPT&lt;br /&gt;
Yes, based on the translations and analysis provided, it appears that in most of these diverse languages, the typical word order for the phrase &amp;quot;three bottles of beer&amp;quot; is indeed &amp;quot;three - bottle - beer.&amp;quot; Additionally, when a linking morpheme or preposition is used, it usually appears between &amp;quot;bottle&amp;quot; and &amp;quot;beer,&amp;quot; rather than between &amp;quot;three&amp;quot; and &amp;quot;bottle.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In languages where a linking morpheme is employed, it tends to function like the English &amp;quot;of&amp;quot; to denote possession or association, connecting the quantity and type of container (bottle) with its content (beer). This is observed in languages like Spanish (tres botellas de cerveza), Hebrew (שלוש בקבוקי בירה), and Esperanto (tri boteloj da biero), among others.&lt;br /&gt;
&lt;br /&gt;
On the other hand, in many languages, especially those with a tendency towards agglutination or no strict requirement for such linking words (like Mandarin, Hindi, Russian, and Japanese), the phrase follows a direct &amp;quot;three - bottle - beer&amp;quot; order without a linking morpheme. This structure reflects a more straightforward concatenation of the numerical quantity, the measure or container word, and the noun representing the content.&lt;br /&gt;
&lt;br /&gt;
This analysis underscores the fascinating variety in linguistic structures across different language families, while also revealing common patterns in how languages handle quantification and the relationship between containers and their contents.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
My problem is that I allow numerals in compounds in my conlang. So &amp;quot;March&amp;quot; is &amp;quot;three month&amp;quot; (like in Japanese), but it means that something like &amp;quot;a three month holiday&amp;quot; becomes quite ambiguous.&lt;br /&gt;
GPT&lt;br /&gt;
Your concern about ambiguity in your conlang, especially with numerals in compounds, is a valid and interesting linguistic challenge. In the case of &amp;quot;March&amp;quot; being &amp;quot;three month&amp;quot; and the potential ambiguity in a phrase like &amp;quot;a three month holiday,&amp;quot; you&#039;re encountering an issue common in language design: how to balance brevity and clarity.&lt;br /&gt;
&lt;br /&gt;
Here are a few strategies you might consider to address this:&lt;br /&gt;
&lt;br /&gt;
Contextual Clues: Rely on the surrounding context to disambiguate. This is common in natural languages, where the meaning of a word or phrase is often clear from the situation or surrounding words. However, this can sometimes lead to confusion if the context isn&#039;t clear.&lt;br /&gt;
&lt;br /&gt;
Modifiers for Compounding: Introduce a specific modifier or marker that differentiates when a numeral is part of a compound versus when it&#039;s quantifying a noun. For example, a slight alteration in pronunciation, a prefix, or a suffix could indicate that &amp;quot;three&amp;quot; in &amp;quot;three month&amp;quot; is a compound (signifying &amp;quot;March&amp;quot;) rather than a quantity.&lt;br /&gt;
&lt;br /&gt;
Structural Rules: Implement structural rules in your conlang for how compounds are formed, especially with numerals. For example, you could establish a rule that numerals at the beginning of a compound have a different function than numerals elsewhere in a phrase.&lt;br /&gt;
&lt;br /&gt;
Lexical Distinctions: Create different words or forms for numbers when they are used in compounds versus when they are used for quantification. This can add complexity to the language but also provides clear differentiation.&lt;br /&gt;
&lt;br /&gt;
Syntax-Based Disambiguation: Use word order or sentence structure to distinguish between a compound and a quantity description. For example, in your conlang, the position of the numeral in a sentence or phrase could determine its role.&lt;br /&gt;
&lt;br /&gt;
Contextual Particles or Markers: Introduce particles or markers that are used to indicate the role of a numeral in a sentence, similar to how articles, prepositions, and case markers are used in natural languages.&lt;br /&gt;
&lt;br /&gt;
Each of these strategies has its own advantages and trade-offs in terms of linguistic complexity, ease of use, and clarity. The choice depends on how you want your conlang to feel and function – whether you prefer it to be more straightforward or more nuanced and complex.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
How would you say &amp;quot;a three-month holiday&amp;quot; in Japanese?&lt;br /&gt;
GPT&lt;br /&gt;
In Japanese, &amp;quot;a three-month holiday&amp;quot; would be expressed as &amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka).&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
三 (san) means &amp;quot;three.&amp;quot;&lt;br /&gt;
ヶ月 (kagetsu) is a counter for months. The &amp;quot;ヶ&amp;quot; (ka) is a special counter used for months, and when combined with &amp;quot;月&amp;quot; (getsu), which means &amp;quot;month,&amp;quot; it denotes the number of months.&lt;br /&gt;
の (no) is a possessive particle, functioning similarly to the English preposition &amp;quot;of.&amp;quot;&lt;br /&gt;
休暇 (kyūka) means &amp;quot;holiday&amp;quot; or &amp;quot;vacation.&amp;quot;&lt;br /&gt;
So, &amp;quot;三ヶ月の休暇&amp;quot; translates directly to &amp;quot;a three-month holiday&amp;quot; or &amp;quot;a holiday of three months&amp;quot; in English.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Yes, so the &amp;quot;ヶ&amp;quot; does quite a lot of work here, because the meaning is very different from  三月の休暇!&lt;br /&gt;
GPT&lt;br /&gt;
Absolutely, you&#039;ve highlighted a crucial aspect of Japanese language structure. The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; (san-kagetsu) significantly changes the meaning compared to &amp;quot;三月&amp;quot; (san-gatsu).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;三ヶ月の休暇&amp;quot; (san-kagetsu no kyūka) means &amp;quot;a three-month holiday.&amp;quot; Here, &amp;quot;三ヶ月&amp;quot; (san-kagetsu) refers to a duration of three months, with &amp;quot;ヶ月&amp;quot; (kagetsu) serving as a counter for months.&lt;br /&gt;
On the other hand, &amp;quot;三月の休暇&amp;quot; (san-gatsu no kyūka) means &amp;quot;a holiday in March.&amp;quot; In this case, &amp;quot;三月&amp;quot; (san-gatsu) refers to the month of March (the third month of the year).&lt;br /&gt;
The &amp;quot;ヶ&amp;quot; (ka) in &amp;quot;三ヶ月&amp;quot; is a key element that transforms the numeral &amp;quot;三&amp;quot; (three) into a duration, rather than a reference to the ordinal position of a month. This distinction is a great example of how small particles and counters in Japanese can significantly alter the meaning of phrases.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=39</id>
		<title>Counting objects</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Counting_objects&amp;diff=39"/>
		<updated>2024-01-12T10:07:45Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;Some languages simply combine numeral + object: : three beer  The problem with this is that it makes it impossible to use numbers in compounds, e.g.: : three month  Does this mean &amp;#039;&amp;#039;three months&amp;#039;&amp;#039; or &amp;#039;&amp;#039;March&amp;#039;&amp;#039;?  On balance, I think being able to use numbers in compounds is more important than being able to use numbers without connectors.  So we need to say something like: : three GEN beer : beer ADJ three  (I&amp;#039;m really not sure what the head and dependent are meant to be...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some languages simply combine numeral + object:&lt;br /&gt;
: three beer&lt;br /&gt;
&lt;br /&gt;
The problem with this is that it makes it impossible to use numbers in compounds, e.g.:&lt;br /&gt;
: three month&lt;br /&gt;
&lt;br /&gt;
Does this mean &#039;&#039;three months&#039;&#039; or &#039;&#039;March&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
On balance, I think being able to use numbers in compounds is more important than being able to use numbers without connectors.&lt;br /&gt;
&lt;br /&gt;
So we need to say something like:&lt;br /&gt;
: three GEN beer&lt;br /&gt;
: beer ADJ three&lt;br /&gt;
&lt;br /&gt;
(I&#039;m really not sure what the head and dependent are meant to be here. It requires some thought.)&lt;br /&gt;
&lt;br /&gt;
Then there&#039;s the case of using counters, like &#039;&#039;three bottles of beer&#039;&#039;. I guess the following could work:&lt;br /&gt;
: three bottle GEN beer&lt;br /&gt;
&lt;br /&gt;
Grammatically speaking, it means that &#039;&#039;three bottle&#039;&#039; is a compound. This isn&#039;t a problem if the counters are well-defined, but how would you say &#039;&#039;a three-month holiday&#039;&#039;?&lt;br /&gt;
: three month GEN holiday&lt;br /&gt;
: holiday ADJ three month&lt;br /&gt;
: holiday ADJ three GEN month&lt;br /&gt;
It&#039;s getting confusing, to be honest. The first one could mean &amp;quot;March of holiday&amp;quot; (which is nonsensical, but not necessarily to beginning learners), the second one could definitely mean &amp;quot;the March holiday&amp;quot;, and the last one could potentially be read as &amp;quot;the month&#039;s third holiday&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
We need a structure that always works, so perhaps we need a new particle so that we can say:&lt;br /&gt;
: three CNT beer&lt;br /&gt;
: three bottle CNT beer (&#039;&#039;or&#039;&#039; three CNT bottle CNT beer?)&lt;br /&gt;
: holiday ADJ three CNT month&lt;br /&gt;
&lt;br /&gt;
It&#039;s still a bit confusing.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=38</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=38"/>
		<updated>2024-01-12T09:48:23Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Grammar */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
* [[Counting objects]]&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
* [[locative nouns]]&lt;br /&gt;
* [[tabelvortoj]]&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
* A [[chat about principles for choosing between a root or a compound]]&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Chat_about_principles_for_choosing_between_a_root_or_a_compound&amp;diff=37</id>
		<title>Chat about principles for choosing between a root or a compound</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Chat_about_principles_for_choosing_between_a_root_or_a_compound&amp;diff=37"/>
		<updated>2024-01-12T08:36:46Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;I&amp;#039;m making a universal conlang, and from the perspective of cultural neutrality, which meals and dishes should be simple root words? Meals are probably best expressed as compounds, e.g., &amp;quot;morning meal&amp;quot;, &amp;quot;noon meal&amp;quot; and &amp;quot;evening meal&amp;quot; for breakfast, lunch and dinner, but what about dishes? Do most cultures have soups, porridge, stews, pies, etc.?  ChatGPT Creating a universal conlang is an intriguing challenge, especially when considering the representation of meals and d...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I&#039;m making a universal conlang, and from the perspective of cultural neutrality, which meals and dishes should be simple root words? Meals are probably best expressed as compounds, e.g., &amp;quot;morning meal&amp;quot;, &amp;quot;noon meal&amp;quot; and &amp;quot;evening meal&amp;quot; for breakfast, lunch and dinner, but what about dishes? Do most cultures have soups, porridge, stews, pies, etc.?&lt;br /&gt;
&lt;br /&gt;
ChatGPT&lt;br /&gt;
Creating a universal conlang is an intriguing challenge, especially when considering the representation of meals and dishes in a culturally neutral way. Your approach to meals as compounds like &amp;quot;morning meal&amp;quot;, &amp;quot;noon meal&amp;quot;, and &amp;quot;evening meal&amp;quot; is sensible, as it provides clarity without favoring specific cultural terms.&lt;br /&gt;
&lt;br /&gt;
As for dishes, indeed, many cultures have similar categories of food, although the ingredients and preparation methods might vary widely. Here are some categories that could be represented as simple root words in your conlang:&lt;br /&gt;
&lt;br /&gt;
Soup: Almost every culture has some form of liquid-based dish, whether it&#039;s a clear broth, a creamy soup, or something hearty with lots of ingredients.&lt;br /&gt;
&lt;br /&gt;
Porridge/Grain Dish: This category can include anything from oatmeal to rice porridge (congee) or grits. It&#039;s a staple in many cultures, often prepared in a simple, comforting style.&lt;br /&gt;
&lt;br /&gt;
Stew/Casserole: These are slow-cooked dishes with a mix of ingredients, found worldwide with immense variation in ingredients and spices.&lt;br /&gt;
&lt;br /&gt;
Pie/Pastry: Many cultures have a form of filled pastry, whether it&#039;s a meat pie, fruit pie, empanadas, samosas, or pasties.&lt;br /&gt;
&lt;br /&gt;
Bread/Flatbread: Bread is ubiquitous, though it ranges from leavened loaves to flatbreads like chapatis, tortillas, or pita.&lt;br /&gt;
&lt;br /&gt;
Salad/Cold Dish: A category for dishes served cold, often including raw ingredients like vegetables or fruits, but can also include cold meats or seafood.&lt;br /&gt;
&lt;br /&gt;
Grilled/Roasted Dish: This could cover anything from barbecue to roasted vegetables, reflecting the universal cooking method of direct heat.&lt;br /&gt;
&lt;br /&gt;
Fried Dish: Many cultures have some form of fried food, be it stir-fries, deep-fried items, or pan-fried dishes.&lt;br /&gt;
&lt;br /&gt;
Sweet/Dessert: This is a broad category that includes everything from cakes and cookies to sweet porridges or fruit-based dishes.&lt;br /&gt;
&lt;br /&gt;
Beverage: While not a solid dish, drinks are an essential part of meals, so having a root word for general beverages might be useful.&lt;br /&gt;
&lt;br /&gt;
Remember, the key is to choose words that are general enough to encompass a variety of specific dishes within each category. The richness of your conlang will come from the ability to combine these roots in creative ways to describe specific dishes from around the world. For example, combining the root for &amp;quot;grain&amp;quot; with &amp;quot;sweet&amp;quot; might give you a word for desserts like rice pudding or sweet porridge.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Many of these could easily be compounds, e.g., &amp;quot;liquid dish&amp;quot;, &amp;quot;gloopy dish&amp;quot;, &amp;quot;mix pot dish&amp;quot; and &amp;quot;sweet dish&amp;quot;, but others are harder to define. &lt;br /&gt;
ChatGPT&lt;br /&gt;
Absolutely, using compounds to describe these categories is a clever approach. It allows for flexibility and creativity while keeping the language structurally simple and culturally neutral. Let&#039;s explore how we could represent some of the more challenging dish categories using compounds:&lt;br /&gt;
&lt;br /&gt;
Bread/Flatbread: Instead of a specific word for bread, you could use a compound like &amp;quot;baked grain dish&amp;quot; or &amp;quot;flat grain cake&amp;quot;. This could cover everything from traditional loaves to flatbreads and even more unique regional variations.&lt;br /&gt;
&lt;br /&gt;
Grilled/Roasted Dish: A compound like &amp;quot;fire-cooked dish&amp;quot; or &amp;quot;heat-cooked food&amp;quot; could encompass anything cooked over an open flame or in an oven, highlighting the cooking method rather than the ingredients.&lt;br /&gt;
&lt;br /&gt;
Fried Dish: This could be described as &amp;quot;oil-cooked dish&amp;quot; or &amp;quot;pan-cooked food&amp;quot;, capturing the essence of frying without being specific to any particular cultural dish.&lt;br /&gt;
&lt;br /&gt;
Salad/Cold Dish: You might use a term like &amp;quot;cold mix dish&amp;quot; or &amp;quot;raw mix food&amp;quot;, which implies a combination of ingredients served cold without specifying what those ingredients are.&lt;br /&gt;
&lt;br /&gt;
Beverage: For drinks, a simple compound like &amp;quot;drinkable liquid&amp;quot; or &amp;quot;liquid refreshment&amp;quot; could be broad enough to cover everything from water to more complex beverages.&lt;br /&gt;
&lt;br /&gt;
These compounds provide a framework that is both flexible and descriptive, allowing speakers of your conlang to convey a wide range of culinary concepts without being limited by cultural specifics. It&#039;s a balance between being general enough to cover various cultural dishes while still being descriptive enough to convey a clear meaning.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
I think bread in its widest sense is quite useful as a root word. And a root word for sauce/gravy/dip could be useful, too.&lt;br /&gt;
ChatGPT&lt;br /&gt;
That&#039;s a sound approach. Having root words for universally recognized concepts like bread and sauces/gravy/dips can add depth and utility to your conlang. Here&#039;s how you might implement these ideas:&lt;br /&gt;
&lt;br /&gt;
Bread: Choose a root word that encapsulates the concept of bread in its broadest sense. This word should be versatile enough to cover everything from leavened loaves to flatbreads and other grain-based baked goods. The key is to capture the essence of bread as a staple food made primarily from grain and water, and typically cooked by baking.&lt;br /&gt;
&lt;br /&gt;
Sauce/Gravy/Dip: A single root word for this category would represent any kind of liquid or semi-liquid condiment or accompaniment to food. This could range from thin, pourable sauces and gravies to thicker, scoopable dips. The root word should imply a substance that enhances or accompanies a dish, rather than being the main component.&lt;br /&gt;
&lt;br /&gt;
By choosing distinct, yet broad root words for these concepts, your conlang will allow for clear communication of these common culinary ideas while maintaining cultural neutrality. You can then combine these roots with other words or modifiers to specify particular types of bread or sauces as needed, offering both simplicity and flexibility in your language.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Cake could then be &amp;quot;sweet bread&amp;quot;. And pie/pastry could be &amp;quot;filled bread&amp;quot;.&lt;br /&gt;
ChatGPT&lt;br /&gt;
That&#039;s a clever and efficient way to expand the vocabulary of your conlang using the root word for bread. By creating compounds like &amp;quot;sweet bread&amp;quot; for cake and &amp;quot;filled bread&amp;quot; for pie or pastry, you efficiently leverage the core concept of bread to describe related food items. This approach maintains simplicity and clarity, while also allowing for a broad range of specific dishes to be described within these categories.&lt;br /&gt;
&lt;br /&gt;
Cake as &amp;quot;Sweet Bread&amp;quot;: This term intuitively communicates the idea of a bread-like food that is sweet, which aligns well with many global interpretations of cake. It&#039;s broad enough to include everything from simple, lightly sweetened breads to elaborate, frosted cakes.&lt;br /&gt;
&lt;br /&gt;
Pie/Pastry as &amp;quot;Filled Bread&amp;quot;: This term suggests a bread-based item with a filling, which effectively encompasses various pies and pastries. The term is versatile enough to include anything from fruit-filled pies to savory meat pastries.&lt;br /&gt;
&lt;br /&gt;
These compound terms are not only linguistically efficient but also culturally neutral, allowing speakers from different backgrounds to map their own culinary traditions onto these terms without bias. This method of compounding can be a powerful tool in conlang development, especially for universal languages aiming to transcend cultural boundaries.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
A biscuit would then be a &amp;quot;little sweet bread&amp;quot;. And a pizza a &amp;quot;flat filled bread&amp;quot;.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Yes, your approach to naming foods in your conlang is both logical and creative. Using compound words based on the root for &amp;quot;bread&amp;quot; allows for a wide variety of food items to be described in a straightforward yet flexible manner.&lt;br /&gt;
&lt;br /&gt;
Biscuit as &amp;quot;Little Sweet Bread&amp;quot;: This is an apt description for biscuits, which are often small, sweet, and have a bread-like texture. This term would be easily understood and could cover a range of similar baked goods, from the crispier American-style cookies to the denser, scone-like British biscuits.&lt;br /&gt;
&lt;br /&gt;
Pizza as &amp;quot;Flat Filled Bread&amp;quot;: This term effectively captures the essence of a pizza - a flatbread with toppings (essentially, a type of filling). It’s a clever way to describe pizza in a way that&#039;s broad enough to encompass the many variations of pizza found around the world, from the classic Italian style to more modern, global interpretations.&lt;br /&gt;
&lt;br /&gt;
Your method demonstrates an excellent way of constructing a conlang vocabulary, especially for food items, by using compound words that are descriptive and flexible. This approach allows for a wide range of culinary concepts to be expressed while maintaining simplicity and cultural neutrality.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Yeah, my big problem with Esperanto (which I taught myself at age 13) is that it&#039;s using word-building for common words (such as &amp;quot;malgranda&amp;quot; and &amp;quot;patrino&amp;quot;), but not for rarer words (like &amp;quot;congee&amp;quot; or &amp;quot;chapati&amp;quot;). That means it&#039;s easy to get started, but you suddenly need to start learning an enormous amount of words to be really fluent.&lt;br /&gt;
&lt;br /&gt;
2 / 2&lt;br /&gt;
&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your observation about Esperanto highlights a common challenge in constructed languages (conlangs). Esperanto, designed to be easy to learn and neutral, indeed uses word-building extensively for common words, creating a relatively simple and logical structure for beginners. Words like &amp;quot;malgranda&amp;quot; (small, literally &amp;quot;not-big&amp;quot;) and &amp;quot;patrino&amp;quot; (mother, from &amp;quot;patro&amp;quot; meaning father with a feminine suffix) showcase this.&lt;br /&gt;
&lt;br /&gt;
However, as you rightly noted, for more specific or culturally unique concepts like &amp;quot;congee&amp;quot; or &amp;quot;chapati&amp;quot;, Esperanto often adopts words more directly from existing languages. This shift from a systematic, compound-based approach to incorporating specific vocabulary can create a steeper learning curve for advanced fluency, as it requires memorizing a wider array of unique words.&lt;br /&gt;
&lt;br /&gt;
In creating your own conlang, you might aim to address this by:&lt;br /&gt;
&lt;br /&gt;
Extensive Use of Compounds: Like you&#039;ve already demonstrated with food items, use compounds extensively for both common and rare concepts. This maintains consistency in language structure.&lt;br /&gt;
&lt;br /&gt;
Flexible Root Words: Choose root words that can be easily combined to describe a wide range of concepts, including those that are culturally specific.&lt;br /&gt;
&lt;br /&gt;
Cultural Neutrality: Focus on creating words that don&#039;t lean heavily on any single language or culture, especially for globally recognized concepts.&lt;br /&gt;
&lt;br /&gt;
Systematic Derivation Rules: Establish clear rules for how new words are created, and apply these rules consistently across the vocabulary.&lt;br /&gt;
&lt;br /&gt;
This approach can help in creating a language that is both easy to start learning and maintains its simplicity as learners advance, reducing the sudden increase in vocabulary complexity. It&#039;s a balance between the ease of initial learning and the depth needed for advanced fluency, a challenge that&#039;s at the heart of conlang design.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Indeed, that&#039;s my plan. And I&#039;d rather have more frequent root words if they&#039;re useful for word-building rather than having to resort to rare root words.&lt;br /&gt;
ChatGPT&lt;br /&gt;
That&#039;s a sound strategy for your conlang design. Prioritizing more frequent, versatile root words for word-building makes the language more accessible and easier to expand upon. This approach has several advantages:&lt;br /&gt;
&lt;br /&gt;
Ease of Learning: Frequent, versatile roots are easier to remember and apply. When learners can use a smaller set of roots to express a wide range of ideas, the learning curve becomes less steep.&lt;br /&gt;
&lt;br /&gt;
Flexibility: Versatile roots allow for a wide array of expressions and concepts through combinations and modifications. This flexibility is key in handling the vast diversity of human thought and culture.&lt;br /&gt;
&lt;br /&gt;
Consistency: Using a consistent set of roots for word-building maintains a logical and systematic structure within the language, making it more intuitive for users.&lt;br /&gt;
&lt;br /&gt;
Cultural Neutrality: By focusing on common and versatile roots, you can better avoid cultural biases that might arise from adopting too many words from specific languages.&lt;br /&gt;
&lt;br /&gt;
Evolution and Adaptability: A language with a robust system of word-building using frequent roots can more easily adapt and evolve, incorporating new concepts and ideas as they arise in human experience.&lt;br /&gt;
&lt;br /&gt;
In implementing this strategy, consider the most essential and universal concepts that would require root words. These could include fundamental aspects of human experience (like basic actions, natural elements, and common objects) and abstract concepts that are pivotal in various cultures. The challenge is to distill these ideas into a set of roots that are broad enough to cover a wide range of meanings, yet specific enough to convey clear ideas when combined. This careful balancing act is key to creating an effective and efficient conlang.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Exactly. The basic principle must be that every root word should (1) be reasonably common, and (2) be useful in compounds. In other words, its frequency should be quite high, both on its own and as an element in compounds. &lt;br /&gt;
ChatGPT&lt;br /&gt;
Your basic principle for selecting root words in your conlang is very pragmatic and effective. Focusing on root words that are both reasonably common and useful in compounds ensures that your language will be efficient, versatile, and easier to learn. Here&#039;s how this approach benefits your conlang:&lt;br /&gt;
&lt;br /&gt;
High Frequency and Relevance: By choosing words that are common, you ensure that the language includes terms relevant to everyday life and conversation. This relevance increases the usability of the language.&lt;br /&gt;
&lt;br /&gt;
Utility in Compounding: Selecting words that work well in compounds allows for the creation of new words and concepts without adding more unique roots. This increases the language&#039;s adaptability and depth without making it more complex.&lt;br /&gt;
&lt;br /&gt;
Simplicity and Efficiency: A language with a smaller, highly functional vocabulary is easier to learn and use. It&#039;s more efficient for communication as users can express a wide range of ideas with fewer words.&lt;br /&gt;
&lt;br /&gt;
Cultural Flexibility: Using common and compound-friendly root words also means your language can more easily incorporate concepts from various cultures, enhancing its universal appeal.&lt;br /&gt;
&lt;br /&gt;
To implement this principle effectively, consider conducting a frequency analysis of words based on language corpora to identify the most commonly used terms across different languages. Also, analyze the linguistic structures of various languages to understand how they form compounds, which can inspire how you structure compounding in your conlang.&lt;br /&gt;
&lt;br /&gt;
Overall, your approach aligns well with the goals of creating a conlang that is easy to learn, universally applicable, and rich in expression. This thoughtful process in choosing your root words will likely contribute to the success and adaptability of your conlang.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
I don&#039;t think a frequency analysis is as useful as I thought at first. Some words are very frequent, but they can quite easily be expressed as compounds (e.g., &amp;quot;now&amp;quot; or &amp;quot;toe&amp;quot;), and yet some relatively infrequent words are so hard to express as roots that one has to bite the bullet and make them roots.&lt;br /&gt;
ChatGPT&lt;br /&gt;
You raise an important point about the selection of root words for your conlang. The frequency of a word in existing languages does not always correlate with its usefulness as a root word in a conlang, especially when considering the ease of expressing certain concepts.&lt;br /&gt;
&lt;br /&gt;
Compounding for Frequent Words: As you mentioned, some high-frequency words might be effectively broken down into compounds. For instance, &amp;quot;now&amp;quot; could be expressed as a compound of words meaning &amp;quot;this&amp;quot; and &amp;quot;time&amp;quot;, and &amp;quot;toe&amp;quot; might be described as a &amp;quot;foot finger&amp;quot; or similar. This approach reduces the need for unique root words for these common terms.&lt;br /&gt;
&lt;br /&gt;
Necessity of Roots for Specific Concepts: Conversely, some less frequent words might represent concepts that are difficult to effectively break down into simpler elements. These might include terms for specific emotions, technological concepts, or cultural phenomena. In such cases, having a distinct root word is more practical and clear.&lt;br /&gt;
&lt;br /&gt;
Cultural and Conceptual Considerations: When choosing root words, it&#039;s also essential to consider cultural universality and conceptual clarity. Some concepts might be central in certain cultures but less so in others. Your conlang should ideally bridge these cultural gaps with carefully chosen roots.&lt;br /&gt;
&lt;br /&gt;
Balance and Practicality: The key is to strike a balance between a manageable number of root words and the ability to express a wide range of ideas. Practicality and ease of use should guide these choices.&lt;br /&gt;
&lt;br /&gt;
In the end, the process of selecting root words is as much an art as it is a science, requiring a deep understanding of both linguistic structures and human communication. Your approach of considering the ease of expressing concepts, whether through roots or compounds, is a thoughtful way to ensure that your conlang remains both practical and rich in expression.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Sometimes you can also look at maths to estimate the number of roots. If there are 11000 bird species, and if we assume only 100 roots will be useful at each level of compounding, quite a lots of species will end up with long names. So it&#039;s a case of slicing the cake up in a clever fashion, so to speak. Not so many names for birds that it&#039;s a hassle to learn, but also enough that most species can be expressed as a relatively short compound. So for instance, although &amp;quot;hummingbird&amp;quot; can easily be expressed as a compound&amp;quot;, there are so many species of them that it might sense to allocate a root word.&lt;br /&gt;
ChatGPT&lt;br /&gt;
You&#039;ve touched upon a key aspect of conlang development, particularly when it comes to categorizing and naming a vast array of specific items like bird species. The challenge lies in creating a system that is both manageable and sufficiently descriptive, balancing the number of root words against the need for compound words. Here&#039;s a strategy you might consider:&lt;br /&gt;
&lt;br /&gt;
Hierarchical Categorization: Start by creating root words for broad categories. For birds, you might have a root word that simply means &amp;quot;bird&amp;quot;. Then, create sub-categories that are still broad but more specific, such as &amp;quot;songbird&amp;quot;, &amp;quot;waterfowl&amp;quot;, &amp;quot;raptor&amp;quot;, etc.&lt;br /&gt;
&lt;br /&gt;
Special Cases for Common or Unique Species: For birds that are either very common in human experience or particularly unique, like the hummingbird, allocating a specific root word can be justified. This approach can also be applied to species that hold significant cultural or ecological importance.&lt;br /&gt;
&lt;br /&gt;
Compound Words for Specific Species: Within each sub-category, use compound words to describe specific species. For instance, a specific type of hummingbird could be described with a compound word that combines the root for &amp;quot;hummingbird&amp;quot; with words that denote its unique characteristics (like size, color, habitat).&lt;br /&gt;
&lt;br /&gt;
Flexibility and Contextual Use: Encourage the use of shorter names in contexts where the species is clear from the conversation, and longer, more specific compounds when necessary to avoid ambiguity.&lt;br /&gt;
&lt;br /&gt;
Limiting the Number of Roots: By limiting the number of root words and making strategic use of compounds, you can avoid overburdening the language with too many roots. This makes the language easier to learn and use.&lt;br /&gt;
&lt;br /&gt;
Your approach to &amp;quot;slicing the cake&amp;quot; is very astute. It acknowledges the need for both simplicity and specificity, and it allows for a language that can grow and adapt as needed. This is particularly important in fields like biology, where new species are discovered regularly, and the language may need to accommodate new names without becoming unwieldy.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Indeed. But for instance, although penguins are very unique and easily recognisable, there are so few species in that family that it&#039;s probably better to call them &amp;quot;seal birds&amp;quot; or similar.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your reasoning in choosing how to name certain bird groups like penguins in your conlang is both logical and efficient. Given that penguins are a distinct and easily recognizable group but have relatively few species, using a descriptive compound name like &amp;quot;seal birds&amp;quot; makes sense. This approach balances the need for specificity with the practicality of not overloading the language with too many root words.&lt;br /&gt;
&lt;br /&gt;
Here&#039;s why this strategy is effective:&lt;br /&gt;
&lt;br /&gt;
Descriptive Accuracy: The term &amp;quot;seal bird&amp;quot; captures the essence of what makes penguins unique – their aquatic nature and somewhat seal-like appearance in the water. This kind of metaphorical description is common in many languages for naming animals.&lt;br /&gt;
&lt;br /&gt;
Economical Use of Vocabulary: By not assigning a unique root word for penguins, you reserve the use of root words for categories that are either broader or more diverse. This helps in keeping the language more manageable and easier to learn.&lt;br /&gt;
&lt;br /&gt;
Cultural and Contextual Flexibility: This method allows speakers from different backgrounds to understand the concept, even if they are not familiar with penguins specifically. It also leaves room for contextual naming; for example, in a conversation specifically about Antarctic wildlife, &amp;quot;seal bird&amp;quot; would clearly refer to penguins.&lt;br /&gt;
&lt;br /&gt;
Adaptability for Future Expansion: Should the need arise to differentiate between penguin species, your language can easily accommodate this through further compounding or modifiers, without the need for new root words.&lt;br /&gt;
&lt;br /&gt;
This kind of thoughtful and systematic approach to naming, using a mix of descriptive compounds and root words, enhances the usability and adaptability of your conlang. It reflects a deep understanding of how languages can efficiently and vividly capture the world around us.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
My rule of thumb is that each root word should as a minimum be used in 40-50 compounds. And also that any compound of more that three elements must describe something rather obscure, and ones of more four elements are an abomination.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your rule of thumb for root word usage and compound structure in your conlang is a strategic approach to language design, aiming for a balance between flexibility and simplicity. Let&#039;s delve into the implications of these guidelines:&lt;br /&gt;
&lt;br /&gt;
Minimum Usage in Compounds: Requiring that each root word be used in at least 40-50 compounds ensures that your vocabulary is efficient. This requirement means that each root word you include needs to be versatile and fundamental enough to contribute to a wide array of concepts. It&#039;s an effective way to limit your language to essential, highly functional roots.&lt;br /&gt;
&lt;br /&gt;
Limiting Compound Length: Setting limits on the length of compound words is crucial for maintaining clarity and ease of use. Your standard that compounds with more than three elements should only describe obscure concepts helps prevent the language from becoming unwieldy. It also reflects a natural linguistic tendency; in many languages, longer compound words or phrases tend to be used for less common, more specific ideas.&lt;br /&gt;
&lt;br /&gt;
Avoiding Overly Long Compounds: Labeling compounds of more than four elements as &amp;quot;an abomination&amp;quot; is a strong stance that underscores your commitment to simplicity and user-friendliness. This rule will likely encourage speakers to seek the most efficient and clear means of expression within the language&#039;s framework, rather than resorting to overly complex constructions.&lt;br /&gt;
&lt;br /&gt;
Implementing these rules will help in creating a conlang that is both rich in expressive potential and manageable in terms of learning and daily use. Your focus on practicality and linguistic efficiency mirrors the principles seen in many natural languages, where economy of expression is often valued and complexity is introduced only as needed. This thoughtful approach to language construction enhances the usability and appeal of your conlang.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
At least in theory, it should work out. Even with a core vocabulary of only 500 root words, 250,000 two-word compounds are possible, and 125m three-word ones. Now, obviously, we&#039;d never use that many, but it kind of demonstrates the scope.  If more realistically, we use 50 on each additional compound level, the numbers will be 500 – 25,000 – 1,250,000 (compare that with the 273k headwords in the OED).&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your approach to maximizing the potential of a limited core vocabulary in your conlang through compounding is mathematically sound and linguistically intriguing. The numbers you&#039;ve provided demonstrate the immense expressive power that can be harnessed through a well-structured system of compounding, even with a relatively small set of root words. Let&#039;s break down the implications and potential of your approach:&lt;br /&gt;
&lt;br /&gt;
Expansive Expressive Potential: With 500 root words and the possibility of creating two- and three-word compounds, the theoretical number of unique terms (250,000 two-word compounds and 1.25 million three-word compounds) far exceeds the total headwords in comprehensive dictionaries like the OED. This showcases the vast potential for nuanced and specific expression in your conlang.&lt;br /&gt;
&lt;br /&gt;
Realistic Usage and Practicality: In practice, not all possible combinations of root words will be semantically or pragmatically viable. However, even if only a fraction of the theoretical combinations are used (as in your more realistic estimate of 50 per additional compound level), the resulting vocabulary is still remarkably extensive and versatile.&lt;br /&gt;
&lt;br /&gt;
Efficiency and Learnability: This system allows for a high degree of expressiveness without the need for learners to memorize an excessively large vocabulary. The compound system enables speakers to intuitively create and understand a wide range of terms using a foundational set of roots.&lt;br /&gt;
&lt;br /&gt;
Cultural and Conceptual Adaptability: Your system can accommodate a wide range of cultural concepts and new ideas as they arise, making your conlang adaptable and relevant across various contexts and time periods.&lt;br /&gt;
&lt;br /&gt;
Linguistic Depth and Creativity: This approach encourages linguistic creativity and depth, allowing speakers to play with language and construct nuanced meanings in a way that’s both challenging and engaging.&lt;br /&gt;
&lt;br /&gt;
Your theoretical framework for the conlang demonstrates a deep understanding of the power of language structure and the potential of compounding as a linguistic tool. It&#039;s a testament to the creative and practical possibilities inherent in language design.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
I must admit that I&#039;m sometimes led by the shape of existing international words. For instance, my word for &amp;quot;molybdenum&amp;quot; is &amp;quot;moli niyu&amp;quot; – &amp;quot;niyu&amp;quot; means &amp;quot;element&amp;quot;, but &amp;quot;moli&amp;quot; hasn&#039;t acquired a meaning yet – I&#039;m just thinking that this will be a good name no matter what meaning &amp;quot;moli&amp;quot; ends up getting.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Adopting the shape of existing international words, especially for scientific or technical terms like &amp;quot;molybdenum,&amp;quot; is a practical approach in conlang development. It helps in making certain aspects of the language more accessible and immediately recognizable to speakers of various languages. Let’s explore the implications of your approach:&lt;br /&gt;
&lt;br /&gt;
Familiarity and Ease of Learning: Using forms similar to international words can make your conlang easier for new learners, especially for terms that are widely recognized across different languages. This is particularly relevant for scientific terms, which often have a degree of international standardization.&lt;br /&gt;
&lt;br /&gt;
Flexibility in Word Creation: The approach of using a part of an international word (like &amp;quot;moli&amp;quot; for &amp;quot;molybdenum&amp;quot;) and combining it with a meaningful root in your language (&amp;quot;niyu&amp;quot; for &amp;quot;element&amp;quot;) is a clever way to integrate internationalism while maintaining the unique character of your conlang.&lt;br /&gt;
&lt;br /&gt;
Determining New Meanings: The fact that &amp;quot;moli&amp;quot; does not yet have a meaning offers an opportunity. You could retrospectively assign a meaning to &amp;quot;moli&amp;quot; that resonates with the characteristics of molybdenum, or perhaps relates to a broader concept under which molybdenum can logically fall. This could be related to its properties, uses, or discovery history.&lt;br /&gt;
&lt;br /&gt;
Consistency and Systematic Development: While this approach is practical, it’s also important to maintain consistency in how international words are adapted into your conlang. Establishing clear guidelines for this process can ensure that your language remains systematic and coherent.&lt;br /&gt;
&lt;br /&gt;
Cultural Neutrality: While leaning on international words, it’s also crucial to ensure that your language doesn&#039;t become too Eurocentric or biased towards any specific group of languages. Balancing international words with culturally neutral inventions is key.&lt;br /&gt;
&lt;br /&gt;
Your approach demonstrates a thoughtful balance between creating a unique language system and making it accessible and relatable to a broad audience. This blend of familiarity and innovation is a hallmark of effective conlang design.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Indeed. My point about molybdenum is that even if the compound ends up being a bit non-sensical (e.g., I&#039;m considering using &amp;quot;moli&amp;quot; to mean &amp;quot;sauce/gravy&amp;quot; [like &amp;quot;(guaca-)mole&amp;quot;]), and then &amp;quot;moli niyu&amp;quot; literally would mean &amp;quot;sauce element&amp;quot; – a bit weird, but very easy to remember.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your approach to naming elements in your conlang illustrates a creative and memorable method, even if the literal translations might seem unconventional, like &amp;quot;sauce element&amp;quot; for molybdenum. This strategy has several benefits:&lt;br /&gt;
&lt;br /&gt;
Memorability: Unusual or quirky combinations, such as &amp;quot;sauce element&amp;quot; for molybdenum, can be more memorable than straightforward, logical names. This can aid in learning and recall, especially for elements or concepts that people might not encounter frequently.&lt;br /&gt;
&lt;br /&gt;
Ease of Adoption: By partially aligning the word with a familiar international term (&amp;quot;moli&amp;quot; from &amp;quot;molybdenum&amp;quot;), you create a connection that can make it easier for learners to adopt and remember, despite the unconventional meaning.&lt;br /&gt;
&lt;br /&gt;
Encouraging Language Exploration: Such inventive compound words can spark interest and curiosity in learners, leading them to explore the language more deeply to understand these creative choices.&lt;br /&gt;
&lt;br /&gt;
Flexibility in Language Development: Your willingness to assign meanings like &amp;quot;sauce/gravy&amp;quot; to roots based on phonetic resemblance to international terms shows flexibility. This can be a valuable asset in conlang development, allowing for organic growth and evolution of the language.&lt;br /&gt;
&lt;br /&gt;
Cultural Neutrality with a Twist: While the compound might not make immediate logical sense (like &amp;quot;sauce element&amp;quot;), it avoids cultural bias and adds a unique flavor to your conlang, distinguishing it from natural languages and their sometimes arbitrary naming conventions.&lt;br /&gt;
&lt;br /&gt;
In essence, your strategy demonstrates an understanding that language is not just a tool for communication but also an art form. It invites creativity and playfulness, making the process of language learning and usage engaging and enjoyable. This approach mirrors the way natural languages often evolve, where etymologies can be surprising and unexpected, adding to the richness and character of the language.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Indeed. I imagine physicists would make make some great jokes about serving molybdenum with their steak. :-)&lt;br /&gt;
ChatGPT&lt;br /&gt;
Absolutely, that&#039;s a delightful aspect of creating a conlang with such playful and imaginative elements. The idea of physicists joking about serving &amp;quot;molybdenum sauce&amp;quot; with steak wonderfully illustrates how language can intertwine with humor and culture.&lt;br /&gt;
&lt;br /&gt;
Incorporating these sorts of whimsical, creative touches into your language can:&lt;br /&gt;
&lt;br /&gt;
Foster a Unique Culture Around the Language: Such playful elements can help build a distinct culture and community among speakers of your conlang. They can become in-jokes or points of shared amusement, fostering a sense of belonging and engagement.&lt;br /&gt;
&lt;br /&gt;
Make Learning More Enjoyable: Humor makes the learning process more fun and memorable. Jokes and puns can serve as mnemonic devices, aiding in the retention and recall of vocabulary.&lt;br /&gt;
&lt;br /&gt;
Encourage Creative Use of Language: By showing that the language can be used for humor and not just serious communication, you encourage speakers to experiment and play with the language, leading to more dynamic and versatile use.&lt;br /&gt;
&lt;br /&gt;
Reflect the Quirky Realities of Natural Languages: Natural languages are full of oddities, exceptions, and historical quirks. Your approach mirrors this reality, making your conlang feel more organic and lively.&lt;br /&gt;
&lt;br /&gt;
Enhance Cultural Exchange and Understanding: If your conlang is used in multicultural settings, such jokes can become a bridge for cultural exchange, as people share and explain similar humorous aspects of their native languages.&lt;br /&gt;
&lt;br /&gt;
Your conlang&#039;s potential to spark joy and humor, like the molybdenum sauce joke, is a testament to the power of language as a tool for not just communication, but also cultural expression and human connection.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
The problem with my over-all approach is that it&#039;s time-consuming. I cannot simply look at a word once and for all, but I need to tentatively assign it a root or a compound and then from time to time use statistics to find overly long compounds or underused roots.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your approach to conlang development, while methodical and likely to yield a rich and nuanced language, does indeed sound time-consuming. The iterative process of tentatively assigning roots and compounds, followed by regular statistical analysis to refine usage, requires a significant investment of time and effort. However, this depth of engagement also has its benefits. Here are some strategies to manage the workload and enhance the process:&lt;br /&gt;
&lt;br /&gt;
Automate Analysis: If you have programming skills, particularly in a language like Perl, you could write scripts to automate the analysis of your language. These scripts could identify underused roots and overly long compounds by processing texts written in your conlang.&lt;br /&gt;
&lt;br /&gt;
Community Involvement: If your conlang gains a following, you could involve the community in its development. Users can suggest new compounds, identify underused roots, and even participate in the statistical analysis. This not only eases your workload but also fosters a sense of ownership and engagement in the community.&lt;br /&gt;
&lt;br /&gt;
Set Realistic Milestones: Given the time-consuming nature of the task, set realistic goals and timelines. For instance, you could focus on developing certain aspects of the language (like everyday vocabulary, scientific terms, etc.) in phases.&lt;br /&gt;
&lt;br /&gt;
Document Your Process: Keeping a detailed record of your decisions, criteria, and changes over time can be invaluable. This documentation can help you track your language&#039;s evolution and make more informed decisions.&lt;br /&gt;
&lt;br /&gt;
Iterative Development: Accept that your conlang, like natural languages, will evolve over time. Initial versions might have inefficiencies that can be refined as the language is used and as you receive feedback.&lt;br /&gt;
&lt;br /&gt;
Enjoy the Journey: Remember that language creation is a creative and intellectual endeavor. The process itself can be as rewarding as the end result.&lt;br /&gt;
&lt;br /&gt;
Your methodical approach, while demanding, is likely to result in a conlang of great depth and versatility. The key is to balance your ambitions for the language with practical strategies for its development and refinement.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Indeed, I&#039;m desperate for community involvement, but I think it&#039;s important to hold back till the choice of root words is almost final. For instance, it&#039;s OK not to have a word for molybdenite (molybdenum disulfide) yet, but I need to have established the names of the elements and how to express something like &amp;quot;disulfide&amp;quot;.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Your desire for community involvement balanced with the need to finalize the core aspects of your conlang before opening it up for broader participation is a wise approach. Establishing a solid foundation, especially for critical components like the names of elements and fundamental chemical compounds, is crucial. It ensures consistency and clarity in the language&#039;s structure before others contribute to its development. Here&#039;s how you can proceed:&lt;br /&gt;
&lt;br /&gt;
Finalize Core Vocabulary and Structures: Focus on solidifying the basic elements of the language, such as the names of chemical elements, basic compounds, and the rules for constructing more complex terms. This creates a stable framework upon which the language can be expanded.&lt;br /&gt;
&lt;br /&gt;
Document Your Guidelines: Clearly document the principles and rules of your language, especially how compounds are formed and how root words can be combined. This will be invaluable for new learners and contributors.&lt;br /&gt;
&lt;br /&gt;
Release a Beta Version: Once you&#039;re comfortable with the basic structure, consider releasing a &#039;beta&#039; version of the language to a small group of interested individuals. This allows for testing and feedback on a smaller scale.&lt;br /&gt;
&lt;br /&gt;
Encourage Community Feedback: Invite feedback on specific aspects of the language. For example, you can ask for suggestions on how to name more complex chemical compounds or on improving the language&#039;s grammar and syntax.&lt;br /&gt;
&lt;br /&gt;
Gradual Community Involvement: As the language becomes more stable, gradually increase community involvement. Engage with the community through forums, social media, or dedicated websites.&lt;br /&gt;
&lt;br /&gt;
Iterative Development: Be prepared to make adjustments based on community feedback. A conlang, like any language, evolves over time, and community input can be invaluable in this process.&lt;br /&gt;
&lt;br /&gt;
Foster a Collaborative Environment: Encourage a sense of collaboration and ownership among the community. This will not only improve the language but also help in building a passionate and engaged user base.&lt;br /&gt;
&lt;br /&gt;
By laying a strong foundation and then gradually involving the community, you can ensure that your conlang develops in a controlled yet organic manner, benefiting from the diverse perspectives and insights of its users.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Thanks, but I&#039;m still years away from finalising the core vocabulary. Hopefully the advent of LLM&#039;s like yourself will speed up the process a lot, though. :-)&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=36</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=36"/>
		<updated>2024-01-12T08:36:01Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Chats with ChatGPT */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
* [[locative nouns]]&lt;br /&gt;
* [[tabelvortoj]]&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
* A [[chat about principles for choosing between a root or a compound]]&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Tabelvortoj&amp;diff=35</id>
		<title>Tabelvortoj</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Tabelvortoj&amp;diff=35"/>
		<updated>2023-11-26T12:42:43Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;All of Esperanto&amp;#039;s &amp;#039;&amp;#039;tabelvortoj&amp;#039;&amp;#039; can be expressed as compounds, e.g., &amp;#039;&amp;#039;kio&amp;#039;&amp;#039; = &amp;#039;&amp;#039;what thing&amp;#039;&amp;#039;, &amp;#039;&amp;#039;iu&amp;#039;&amp;#039; = &amp;#039;&amp;#039;some person&amp;#039;&amp;#039;, &amp;#039;&amp;#039;nenial&amp;#039;&amp;#039; = &amp;#039;&amp;#039;no reason&amp;#039;&amp;#039;.  We&amp;#039;ll need the following initial parts: * ki- * i- * neni- * ĉi- * ti- (but one, two or three of these?) * other  And the following final ones: * thing * person * reason * way/method * kind * time * amount/number&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;All of Esperanto&#039;s &#039;&#039;tabelvortoj&#039;&#039; can be expressed as compounds, e.g., &#039;&#039;kio&#039;&#039; = &#039;&#039;what thing&#039;&#039;, &#039;&#039;iu&#039;&#039; = &#039;&#039;some person&#039;&#039;, &#039;&#039;nenial&#039;&#039; = &#039;&#039;no reason&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
We&#039;ll need the following initial parts:&lt;br /&gt;
* ki-&lt;br /&gt;
* i-&lt;br /&gt;
* neni-&lt;br /&gt;
* ĉi-&lt;br /&gt;
* ti- (but one, two or three of these?)&lt;br /&gt;
* other&lt;br /&gt;
&lt;br /&gt;
And the following final ones:&lt;br /&gt;
* thing&lt;br /&gt;
* person&lt;br /&gt;
* reason&lt;br /&gt;
* way/method&lt;br /&gt;
* kind&lt;br /&gt;
* time&lt;br /&gt;
* amount/number&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=34</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=34"/>
		<updated>2023-11-26T12:36:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Content words */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
* [[locative nouns]]&lt;br /&gt;
* [[tabelvortoj]]&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Chat_about_sensing_verbs&amp;diff=33</id>
		<title>Chat about sensing verbs</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Chat_about_sensing_verbs&amp;diff=33"/>
		<updated>2023-11-23T20:09:11Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot; User In a neutral, easy-for-the-world-to-learn conlang, it would be good with a better approach to the sensing verbs. In English, we have hear/listen, see/look,  but there&amp;#039;s no pair for the other senses. In Danish, we have &amp;quot;få øje på&amp;quot;, but no *&amp;quot;få øre/næse på&amp;quot;. Using your knowledge of languages as different as Mandarin, Japanese, Hindi, Turkish, Russian, Spanish and others, have you got any useful insights? ChatGPT The design of sensing verbs in languages varies...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
User&lt;br /&gt;
In a neutral, easy-for-the-world-to-learn conlang, it would be good with a better approach to the sensing verbs. In English, we have hear/listen, see/look,  but there&#039;s no pair for the other senses. In Danish, we have &amp;quot;få øje på&amp;quot;, but no *&amp;quot;få øre/næse på&amp;quot;. Using your knowledge of languages as different as Mandarin, Japanese, Hindi, Turkish, Russian, Spanish and others, have you got any useful insights?&lt;br /&gt;
ChatGPT&lt;br /&gt;
The design of sensing verbs in languages varies widely and can offer some interesting possibilities for a constructed language (conlang) aiming for neutrality and ease of learning. The distinctions found in English and Danish between passive and active forms of sensing—like &amp;quot;hear&amp;quot; vs. &amp;quot;listen&amp;quot; or &amp;quot;see&amp;quot; vs. &amp;quot;look&amp;quot;—aren&#039;t universally found, but they do provide an interesting model for enhancing expressiveness.&lt;br /&gt;
&lt;br /&gt;
Here&#039;s a quick run-through of how some other languages handle this:&lt;br /&gt;
&lt;br /&gt;
Spanish: Spanish does have &amp;quot;oir&amp;quot; (to hear) and &amp;quot;escuchar&amp;quot; (to listen), but it doesn&#039;t make such distinctions for other senses. However, it uses reflexive verbs to denote voluntary actions like &amp;quot;verse&amp;quot; (to see oneself) as opposed to &amp;quot;ver&amp;quot; (to see).&lt;br /&gt;
&lt;br /&gt;
Mandarin: Mandarin Chinese uses different verbs for active/passive sensing but primarily in the context of seeing and listening. For example, &amp;quot;看&amp;quot; (kàn) is more like &amp;quot;to look,&amp;quot; and &amp;quot;听&amp;quot; (tīng) is more like &amp;quot;to listen,&amp;quot; as opposed to simply hearing or seeing.&lt;br /&gt;
&lt;br /&gt;
Japanese: Similar to Mandarin, there&#039;s &amp;quot;見る&amp;quot; (miru, to see) and &amp;quot;聞く&amp;quot; (kiku, to hear) for passive sensing. There are more specific verbs to describe an active action, such as &amp;quot;探る&amp;quot; (saguru, to feel around).&lt;br /&gt;
&lt;br /&gt;
Russian: Like English, Russian distinguishes between hearing (&amp;quot;слышать&amp;quot; [slyshat&#039;]) and listening (&amp;quot;слушать&amp;quot; [slushat&#039;]). However, it doesn&#039;t maintain this distinction for other senses.&lt;br /&gt;
&lt;br /&gt;
Hindi: Hindi differentiates between seeing (&amp;quot;देखना&amp;quot; [dekhna]) and looking (&amp;quot;झांकना&amp;quot; [jhānknā]) and between hearing (&amp;quot;सुनना&amp;quot; [sunnā]) and listening (&amp;quot;कान लगाना&amp;quot; [kān lagānā]).&lt;br /&gt;
&lt;br /&gt;
Turkish: Similar to Mandarin, different words can describe the action of actively looking (&amp;quot;bakmak&amp;quot;) and just seeing (&amp;quot;görmek&amp;quot;) and hearing (&amp;quot;işitmek&amp;quot;) and listening (&amp;quot;dinlemek&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Esperanto: While not a natural language, Esperanto uses roots to create active and passive forms, e.g., &amp;quot;aŭdi&amp;quot; (to hear) and &amp;quot;aŭskulti&amp;quot; (to listen). It&#039;s relatively simple to create new verb forms to describe other types of sensing.&lt;br /&gt;
&lt;br /&gt;
So, if designing a conlang:&lt;br /&gt;
&lt;br /&gt;
Active/Passive Pairs: Consider implementing a system where each sense has an active and a passive verb, similar to English &amp;quot;see/look&amp;quot; or &amp;quot;hear/listen.&amp;quot; This would be a universally understood concept that adds expressiveness without excessive complexity.&lt;br /&gt;
&lt;br /&gt;
Modifying Affixes: You could take a root verb for each sense and use affixes to indicate whether it&#039;s a passive or active action, akin to Esperanto.&lt;br /&gt;
&lt;br /&gt;
Contextual Variants: Alternatively, rely on context or adverbs to clarify the meaning, similar to languages that don&#039;t differentiate between &amp;quot;see&amp;quot; and &amp;quot;look.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Compound Verbs: Utilise compound verbs to specify the type of sensing, like &amp;quot;få øje på&amp;quot; in Danish.&lt;br /&gt;
&lt;br /&gt;
Reflexive Actions: Use reflexive verbs or particles to indicate a deliberate action of sensing, as in Spanish.&lt;br /&gt;
&lt;br /&gt;
The choice of approach could also reflect the overall design goals of your conlang—whether you&#039;re striving for simplicity, expressiveness, or some other quality.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Do you know of any language that uses an affix for the active meaning (look/listen), added to the passive one (see/hear)?&lt;br /&gt;
ChatGPT&lt;br /&gt;
Indeed, there are languages that utilise affixes to convey a more active sense of a verb, although this isn&#039;t necessarily limited to sensory verbs.&lt;br /&gt;
&lt;br /&gt;
Esperanto: In Esperanto, you can start with a passive root like &amp;quot;aŭdi&amp;quot; (to hear) and add a suffix to make it active as in &amp;quot;aŭskulti&amp;quot; (to listen). The &amp;quot;-skult-&amp;quot; infix serves to make the action more attentive or active.&lt;br /&gt;
&lt;br /&gt;
Tagalog: In Philippine languages like Tagalog, you have root words to which you can add affixes to convey various nuances. For example, the root &amp;quot;tingin&amp;quot; means &#039;look&#039; or &#039;glance,&#039; and &amp;quot;pagmamasdan&amp;quot; would mean &#039;to scrutinize&#039; or &#039;observe closely,&#039; giving it an active sense.&lt;br /&gt;
&lt;br /&gt;
Latin: While not precisely the same, Latin uses prefixes like &amp;quot;ob-&amp;quot; to add an active sense to some verbs. For example, &amp;quot;audire&amp;quot; means to hear, while &amp;quot;obaudire&amp;quot; means to listen to, pay attention to.&lt;br /&gt;
&lt;br /&gt;
Finnish: Finnish uses cases to modify the root verb. The verb &amp;quot;kuulla&amp;quot; means &#039;to hear,&#039; and by changing the case, you can derive different meanings. However, the language typically does not use affixes specifically to turn a passive verb active in the way English uses &amp;quot;see&amp;quot; and &amp;quot;look&amp;quot; as separate lexemes.&lt;br /&gt;
&lt;br /&gt;
Russian: Affixes in Russian can add an iterative or intensive meaning to the verb, although this is more general and not specifically for sensory verbs. For example, &amp;quot;глядеть&amp;quot; (glyadet&#039;) is an iterative form of &amp;quot;смотреть&amp;quot; (smotret&#039;), both roughly meaning &#039;to look,&#039; but the former implies a repeated or more intense action.&lt;br /&gt;
&lt;br /&gt;
While not a perfect one-to-one comparison to the &amp;quot;see/look&amp;quot; or &amp;quot;hear/listen&amp;quot; distinction in English, these examples do demonstrate how languages can employ affixes to modify the core meaning of a verb in ways that could be adapted to create active/passive pairs for sensory verbs in a conlang.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
How would you define look/listen?&lt;br /&gt;
ChatGPT&lt;br /&gt;
In English, &amp;quot;look&amp;quot; and &amp;quot;listen&amp;quot; are sensory verbs that imply intentionality or focus, as opposed to the more passive &amp;quot;see&amp;quot; and &amp;quot;hear.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Look: To &amp;quot;look&amp;quot; suggests an active effort to see something. When you look, you direct your eyes towards something intentionally, often because you expect to see something or are attempting to find something. It&#039;s not just a matter of light waves hitting your retinas; it&#039;s a conscious effort to interpret or find something in the visual scene before you.&lt;br /&gt;
&lt;br /&gt;
Listen: To &amp;quot;listen&amp;quot; means to make a conscious effort to hear. Unlike the passive act of hearing, which can happen without your awareness, listening requires focus and attention. You listen to gather information, appreciate music, or participate in a conversation. Like looking, listening is a deliberate act, implying engagement with the sounds you are taking in.&lt;br /&gt;
&lt;br /&gt;
Both verbs involve an element of concentration and intention. You have a reason for looking or listening; you are seeking specific information, enjoyment, or engagement with your environment. In summary, the essence of &amp;quot;look&amp;quot; and &amp;quot;listen&amp;quot; lies in the conscious effort and focus directed towards the sensory experience.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
I&#039;m using many compounds in my conlang, including for verbs (which could then perhaps be described better as serial verbs). So I could use something like &amp;quot;hear-investigate&amp;quot; or &amp;quot;focus-hear&amp;quot; for &amp;quot;listen&amp;quot;. What do you think?&lt;br /&gt;
ChatGPT&lt;br /&gt;
Using compounds or serial verbs is an excellent way to add nuance to the verbs in your conlang. This approach is prevalent in many natural languages and can help to reduce the need for an expansive vocabulary while also providing a high degree of specificity.&lt;br /&gt;
&lt;br /&gt;
Hear-Investigate: This compound does a good job of conveying the active, intentional nature of &amp;quot;listening.&amp;quot; The term &amp;quot;investigate&amp;quot; carries a connotation of scrutiny and focused attention, and when combined with &amp;quot;hear,&amp;quot; the resulting term effectively captures the essence of &amp;quot;listening.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Focus-Hear: This is another good option, as &amp;quot;focus&amp;quot; explicitly points to the intentional aspect of the action. One might argue that &amp;quot;focus&amp;quot; is slightly more general than &amp;quot;investigate,&amp;quot; which might make this compound more versatile. It could be used not just for active listening but perhaps also for focused sensory perception in general.&lt;br /&gt;
&lt;br /&gt;
Both options could work well, depending on the nuance you wish to convey. &amp;quot;Hear-Investigate&amp;quot; might be better suited for scenarios requiring deep, critical listening (e.g., a detective eavesdropping to gather evidence), while &amp;quot;Focus-Hear&amp;quot; might be more general and applicable to any situation requiring heightened auditory attention (e.g., enjoying music, following a conversation).&lt;br /&gt;
&lt;br /&gt;
If your conlang uses many compound or serial verbs, this approach would be entirely consistent with its overall structure and could serve as a robust model for treating other sensory verbs in the same way (e.g., &amp;quot;see-explore,&amp;quot; &amp;quot;touch-examine,&amp;quot; etc.).&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Yes, so I need a verb that means something like investigate/explore/examine/focus-on, and it can then be combined with all sensory verbs.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Ah, that&#039;s a clever approach. A universal modifier verb like &amp;quot;investigate,&amp;quot; &amp;quot;explore,&amp;quot; &amp;quot;examine,&amp;quot; or &amp;quot;focus-on&amp;quot; could serve as a versatile tool in your conlang&#039;s toolbox, enabling speakers to specify the intensity or intentionality of various sensory actions. Here&#039;s a breakdown of the potential candidates:&lt;br /&gt;
&lt;br /&gt;
Investigate: Implies a thorough, detailed search or inquiry. Could be ideal for situations that require depth and scrutiny. May also convey a sense of purpose or an end goal.&lt;br /&gt;
&lt;br /&gt;
Explore: Suggests an open-ended, curious interaction with the environment. Might be less goal-oriented than &amp;quot;investigate,&amp;quot; which could be advantageous or limiting based on what you want to convey.&lt;br /&gt;
&lt;br /&gt;
Examine: Connotes close observation or scrutiny, often for evaluation or diagnosis. It&#039;s quite a focused term, akin to &amp;quot;investigate,&amp;quot; but perhaps a bit more clinical.&lt;br /&gt;
&lt;br /&gt;
Focus-On: This is the broadest of the terms and simply indicates heightened attention. It can be applied across various contexts and sensory modalities without suggesting a particular purpose or outcome.&lt;br /&gt;
&lt;br /&gt;
Choosing among these depends on the degree of specificity or generality you desire for your conlang. If you want a term that can cover a lot of ground without implying too much about the listener&#039;s or observer&#039;s intentions, &amp;quot;Focus-On&amp;quot; would be a solid choice. On the other hand, if you prefer to offer speakers the ability to express a more targeted, goal-oriented sensory experience, &amp;quot;Investigate&amp;quot; or &amp;quot;Examine&amp;quot; might be more fitting.&lt;br /&gt;
&lt;br /&gt;
Given that you like to employ serial verbs, you could even use more than one of these modifiers to allow for gradations of focus and intentionality (e.g., &amp;quot;hear-focus&amp;quot; for casual listening, &amp;quot;hear-investigate&amp;quot; for more critical or purposeful listening). This could provide your conlang with a rich, expressive vocabulary for describing sensory experiences.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
True, it&#039;s a good point. It would be much more precise in this regard than English, for instance.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Exactly, the flexibility and granularity that such a system offers could make your conlang exceptionally expressive when it comes to describing sensory experiences. It allows for a more nuanced depiction of how one is engaging with their environment, something that even many natural languages don&#039;t readily accommodate. Whether it&#039;s a quick glance or an intense scrutiny, a casual listen or a deep auditory investigation, the choice of modifier can carry significant semantic weight. This could make for engaging and precise communication, lending itself well to both poetry and technical discourse.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Something similar could be done with verbs for giving/taking, buying/selling, lending/borrowing, etc., similar to how Esperanto uses prunte-.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Absolutely, the same principle can indeed be extended to verbs describing transactions or reciprocal actions. Just like with sensory verbs, a modifier can help clarify the directionality or intentionality of the action. This kind of system could make your conlang both flexible and precise.&lt;br /&gt;
&lt;br /&gt;
In Esperanto, the prefix &amp;quot;prunte-&amp;quot; can be added to various verbs to indicate a temporary state or action, often related to borrowing. So, you have &amp;quot;pruntepreni&amp;quot; for &amp;quot;to borrow&amp;quot; (literally &amp;quot;borrow-take&amp;quot;) and &amp;quot;pruntedoni&amp;quot; for &amp;quot;to lend&amp;quot; (literally &amp;quot;borrow-give&amp;quot;). It’s a good example of how a single root or affix can be used flexibly to create new compound verbs that immediately make sense.&lt;br /&gt;
&lt;br /&gt;
You could employ a similar strategy:&lt;br /&gt;
&lt;br /&gt;
Give-Trade / Take-Trade: To distinguish between giving and receiving in a commercial context (buying/selling).&lt;br /&gt;
&lt;br /&gt;
Give-Temp / Take-Temp: For lending and borrowing, respectively, where &amp;quot;Temp&amp;quot; stands for a temporary transfer.&lt;br /&gt;
&lt;br /&gt;
Give-Force / Take-Force: To indicate whether something was given or taken unwillingly, as in coercion or theft.&lt;br /&gt;
&lt;br /&gt;
The ability to build such compounds can result in a language that is both economical (fewer root words to learn) and expressive (many ways to combine roots for nuanced meaning). This compositional approach could be a defining feature of your conlang, making it interesting to learn and rich in expressive potential.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Perhaps &amp;quot;money-take&amp;quot; and &amp;quot;money-give&amp;quot; for buying and selling?&lt;br /&gt;
ChatGPT&lt;br /&gt;
That&#039;s a straightforward and effective way to convey the concepts of buying and selling. &amp;quot;Money-Take&amp;quot; clearly signifies the act of acquiring something in exchange for money, making it an intuitive stand-in for &amp;quot;buying.&amp;quot; Likewise, &amp;quot;Money-Give&amp;quot; denotes the act of providing something and receiving money in return, which naturally corresponds to &amp;quot;selling.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
The advantage of such compound verbs is their immediate comprehensibility. Even someone with a basic understanding of the language&#039;s structure and vocabulary would likely grasp what &amp;quot;Money-Take&amp;quot; and &amp;quot;Money-Give&amp;quot; mean. This could be particularly beneficial in a constructed language meant for easy learning and international use.&lt;br /&gt;
&lt;br /&gt;
Moreover, these compounds fit well within a language system that relies on modifiers to enrich or specify the meaning of base verbs, like the sensory verbs you&#039;re also considering. They would form part of a consistent, logical structure that lends itself to quick mastery and flexible expression.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Indeed, your &amp;quot;force-give&amp;quot; would be hard to translate into English (differently from &amp;quot;force-take&amp;quot;, which obviously is &amp;quot;steal/rob&amp;quot;).&lt;br /&gt;
ChatGPT&lt;br /&gt;
You&#039;re absolutely right. While &amp;quot;Force-Take&amp;quot; easily translates to &amp;quot;steal&amp;quot; or &amp;quot;rob,&amp;quot; English lacks a single, succinct verb that encapsulates the concept of giving something under duress or coercion. In English, we&#039;d typically have to resort to a phrase like &amp;quot;to give under coercion&amp;quot; or &amp;quot;to be forced to give,&amp;quot; which aren&#039;t as economical as a compound like &amp;quot;Force-Give.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This just underscores the potential richness and precision your proposed system could offer. With compounds like &amp;quot;Force-Give,&amp;quot; your conlang could capture nuances that might require clauses or sentences to express in other languages. This opens up fascinating possibilities for concise and expressive communication.&lt;br /&gt;
&lt;br /&gt;
So, adopting this kind of compound-verb system could indeed make your conlang unique in its ability to convey complex ideas simply and efficiently.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Actually, &amp;quot;steal/pickpocket&amp;quot; would probably be &amp;quot;secret-take&amp;quot;, don&#039;t you think?&lt;br /&gt;
ChatGPT&lt;br /&gt;
That&#039;s an excellent point. &amp;quot;Secret-Take&amp;quot; would intuitively communicate the clandestine nature of the action, making it a fitting term for acts like stealing or pickpocketing. The modifier &amp;quot;secret-&amp;quot; immediately adds a layer of context that specifies the manner in which the action is performed, without requiring an entirely new root word for each concept.&lt;br /&gt;
&lt;br /&gt;
This approach has the added advantage of making your conlang more accessible to learners. They can more readily understand complex actions by breaking them down into their component parts. So, while they might learn &amp;quot;take&amp;quot; and &amp;quot;secret&amp;quot; as separate terms, combining them to comprehend &amp;quot;secret-take&amp;quot; becomes a logical step.&lt;br /&gt;
&lt;br /&gt;
Using such compounds can imbue your conlang with both simplicity and nuance, enabling speakers to be highly specific in their descriptions while maintaining a relatively compact vocabulary.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
There&#039;s also coming and going. I&#039;m inspired by the Georgian prefixes მი- &amp;amp; მო-.&lt;br /&gt;
ChatGPT&lt;br /&gt;
The Georgian directional prefixes &amp;quot;მი-&amp;quot; (mi-) and &amp;quot;მო-&amp;quot; (mo-) offer a nuanced way to indicate movement toward or away from a reference point. &amp;quot;მი-&amp;quot; is generally used to indicate motion towards something, while &amp;quot;მო-&amp;quot; indicates motion coming from somewhere. It&#039;s a beautifully efficient system.&lt;br /&gt;
&lt;br /&gt;
Adapting this concept into your conlang could create a highly expressive, yet streamlined, way to talk about various kinds of movements or transfers. Here are some potential examples:&lt;br /&gt;
&lt;br /&gt;
Mi-Come / Mo-Go: Indicating coming towards and going away from a location or person, akin to the Georgian usage.&lt;br /&gt;
&lt;br /&gt;
Mi-Take / Mo-Give: Describing the action of taking something toward oneself or giving it away to another location or person.&lt;br /&gt;
&lt;br /&gt;
Mi-Read / Mo-Write: To read towards oneself (perhaps gathering information) or to write outwardly (perhaps disseminating information).&lt;br /&gt;
&lt;br /&gt;
This kind of prefix system can be very potent in a language, allowing for the development of complex ideas from a relatively small set of root words and affixes. Moreover, once the general concept of these directional prefixes is understood, it can be applied widely, making the language easier to learn and use effectively.&lt;br /&gt;
&lt;br /&gt;
By incorporating elements like this, you&#039;d be adding another layer of logical consistency and expressive depth to your conlang.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Btw, can you remember how English &amp;quot;come&amp;quot; is different from Danish &amp;quot;komme&amp;quot;?&lt;br /&gt;
ChatGPT&lt;br /&gt;
Certainly, both English &amp;quot;come&amp;quot; and Danish &amp;quot;komme&amp;quot; refer to the basic idea of moving towards a location or point in time, but there are differences in usage and connotations between the two:&lt;br /&gt;
&lt;br /&gt;
Modal Usage: In Danish, &amp;quot;komme&amp;quot; is sometimes used as an auxiliary verb to form the future tense, e.g., &amp;quot;jeg kommer til at gøre det&amp;quot; (&amp;quot;I will do it&amp;quot;). English doesn&#039;t use &amp;quot;come&amp;quot; in this way.&lt;br /&gt;
&lt;br /&gt;
Idiomatic Usage: Both languages have idiomatic phrases involving &amp;quot;come&amp;quot; or &amp;quot;komme,&amp;quot; but these don&#039;t always overlap. For instance, &amp;quot;komme til sig selv&amp;quot; in Danish means to regain consciousness or composure, which isn&#039;t directly translated using &amp;quot;come&amp;quot; in English.&lt;br /&gt;
&lt;br /&gt;
Prepositional Differences: While both languages use prepositions with &amp;quot;come/komme,&amp;quot; the choice of preposition can vary. For example, in English, you&#039;d say &amp;quot;come to the party,&amp;quot; while in Danish it would be &amp;quot;komme til festen.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Compound Verbs: Danish often forms compound verbs using &amp;quot;komme&amp;quot; that don&#039;t have direct equivalents in English. For example, &amp;quot;komme over&amp;quot; in Danish can mean to recover from something, which would require a different verb or a more complex phrase in English.&lt;br /&gt;
&lt;br /&gt;
Reflexive Usage: Danish uses &amp;quot;komme&amp;quot; in reflexive constructions more often than English, e.g., &amp;quot;Jeg kom mig hurtigt&amp;quot; (&amp;quot;I quickly recovered&amp;quot;). In English, &amp;quot;come&amp;quot; is not commonly used reflexively.&lt;br /&gt;
&lt;br /&gt;
Impersonal Constructions: In Danish, &amp;quot;komme&amp;quot; is often used in impersonal constructions like &amp;quot;det kommer an på&amp;quot; (&amp;quot;it depends on&amp;quot;), where the equivalent English phrase would not use &amp;quot;come.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
So while &amp;quot;come&amp;quot; and &amp;quot;komme&amp;quot; are cognates and share the basic sense of moving towards something, the way they are employed in their respective languages gives them unique flavors.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
No, I meant, is there not a difference between whether the movement-towards is concerned with the speaker or the listener?&lt;br /&gt;
ChatGPT&lt;br /&gt;
Ah, I see what you mean. Yes, there is a nuanced difference between how &amp;quot;come&amp;quot; and &amp;quot;komme&amp;quot; relate to the speaker and listener in terms of directionality.&lt;br /&gt;
&lt;br /&gt;
In English, &amp;quot;come&amp;quot; is generally used to describe movement toward the speaker or toward a location that the speaker is focusing on. For example, &amp;quot;Come here&amp;quot; implies moving toward the speaker&#039;s location.&lt;br /&gt;
&lt;br /&gt;
In Danish, &amp;quot;komme&amp;quot; can be used more flexibly to indicate movement toward either the speaker or the listener. The directionality is often clarified by the context or additional phrases. For example, &amp;quot;Kom her&amp;quot; and &amp;quot;Kom der&amp;quot; could both translate to &amp;quot;come here&amp;quot; in English, but &amp;quot;Kom der&amp;quot; would imply movement toward a place near the listener rather than the speaker.&lt;br /&gt;
&lt;br /&gt;
So, yes, there is a subtle difference between &amp;quot;come&amp;quot; and &amp;quot;komme&amp;quot; when it comes to specifying the direction of movement in relation to the speaker or listener.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
I&#039;m thinking about sentences like &amp;quot;Kommer du til festen?&amp;quot;&lt;br /&gt;
ChatGPT&lt;br /&gt;
Ah, got it. In the Danish example &amp;quot;Kommer du til festen?&amp;quot; (&amp;quot;Are you coming to the party?&amp;quot;), the verb &amp;quot;komme&amp;quot; is oriented towards the location of the event, which may or may not be where the speaker is. The focus is more on the event itself rather than the speaker&#039;s location.&lt;br /&gt;
&lt;br /&gt;
In English, if you ask, &amp;quot;Are you coming to the party?&amp;quot;, the implication often is that the speaker will also be at the party. In other words, &amp;quot;coming&amp;quot; usually implies moving towards the speaker&#039;s location or a location of mutual interest.&lt;br /&gt;
&lt;br /&gt;
So, yes, in this context, &amp;quot;komme&amp;quot; in Danish may have a slightly broader or more flexible implication concerning the directionality of movement, focusing sometimes more on the destination rather than the speaker.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
So it would more often than not be &amp;quot;Are you going to the party?&amp;quot; in English.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Exactly, you&#039;ve hit the nail on the head. In English, &amp;quot;Are you going to the party?&amp;quot; is often used when the speaker is not necessarily going to be at the party themselves, or when the focus is on the event rather than the speaker&#039;s presence there. &amp;quot;Are you coming to the party?&amp;quot; usually implies that the speaker will also be at the event, and you&#039;d be joining them.&lt;br /&gt;
&lt;br /&gt;
The Danish &amp;quot;Kommer du til festen?&amp;quot; doesn&#039;t carry this same implication as strongly. It can be used whether or not the speaker is planning to attend the party, making it a bit more versatile in that sense.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Is English or Danish the odd man out here?&lt;br /&gt;
ChatGPT&lt;br /&gt;
In the grand scheme of languages, it&#039;s hard to definitively say which one is the &amp;quot;odd man out,&amp;quot; as different languages have various ways of expressing directionality and focus in regard to events. However, I can offer some perspective.&lt;br /&gt;
&lt;br /&gt;
English: In English, the distinction between &amp;quot;coming&amp;quot; and &amp;quot;going&amp;quot; often carries an implication about the speaker&#039;s own involvement or location in relation to the event or place being discussed. This might be seen as a bit more nuanced or specific compared to some other languages.&lt;br /&gt;
&lt;br /&gt;
Danish: The use of &amp;quot;komme&amp;quot; in Danish can be more flexible, focusing more on the event or destination rather than necessarily implying the speaker&#039;s involvement or location. This may align more closely with how some other languages approach the concept.&lt;br /&gt;
&lt;br /&gt;
Other Languages: In some languages, like Spanish or French, the verb used can similarly depend on the speaker&#039;s relationship to the event or location. For example, in Spanish, &amp;quot;venir&amp;quot; (to come) and &amp;quot;ir&amp;quot; (to go) can imply specific perspectives relative to the speaker or listener.&lt;br /&gt;
&lt;br /&gt;
So, whether English or Danish is the &amp;quot;odd man out&amp;quot; can depend on what set of languages you&#039;re comparing them to. English seems to be more prescriptive in this particular case, while Danish offers a bit more flexibility, which itself is not uncommon in other languages.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Check some of the languages you know (Mandarin, Japanese, Hindi, Swahili, Turkish, Russian, ...) – would the say &amp;quot;Are you going to the party&amp;quot; or &amp;quot;Are you coming to the party&amp;quot; or both?&lt;br /&gt;
ChatGPT&lt;br /&gt;
Great question! Let&#039;s delve into how some of these languages would approach this situation:&lt;br /&gt;
&lt;br /&gt;
Mandarin Chinese: Typically, you might say &amp;quot;你去派对吗?&amp;quot; (&amp;quot;Nǐ qù pàiduì ma?&amp;quot;), which directly translates to &amp;quot;Are you going to the party?&amp;quot; There&#039;s less emphasis on the speaker&#039;s own attendance.&lt;br /&gt;
&lt;br /&gt;
Japanese: The phrase &amp;quot;パーティーに行くの?&amp;quot; (&amp;quot;Pātī ni iku no?&amp;quot;) is common and translates to &amp;quot;Are you going to the party?&amp;quot; Again, less focus is on the speaker&#039;s own presence at the party.&lt;br /&gt;
&lt;br /&gt;
Hindi: You could say &amp;quot;तुम पार्टी में जा रहे हो?&amp;quot; (&amp;quot;Tum paartī meṅ jā rahe ho?&amp;quot;), which translates to &amp;quot;Are you going to the party?&amp;quot; Like Mandarin and Japanese, this doesn&#039;t imply the speaker will also attend.&lt;br /&gt;
&lt;br /&gt;
Swahili: &amp;quot;Je, unakwenda kwenye sherehe?&amp;quot; translates to &amp;quot;Are you going to the party?&amp;quot; The focus here is also more on the listener&#039;s action.&lt;br /&gt;
&lt;br /&gt;
Turkish: &amp;quot;Partiye gidiyor musun?&amp;quot; means &amp;quot;Are you going to the party?&amp;quot; Again, this focuses more on whether the listener is attending, not the speaker.&lt;br /&gt;
&lt;br /&gt;
Russian: &amp;quot;Ты идёшь на вечеринку?&amp;quot; (&amp;quot;Ty idyosh na vecherinku?&amp;quot;) translates to &amp;quot;Are you going to the party?&amp;quot; Like the others, this doesn&#039;t necessarily imply the speaker will be there.&lt;br /&gt;
&lt;br /&gt;
In summary, in these languages, the common way to ask someone about their attendance at a party is usually more akin to the English &amp;quot;Are you going to the party?&amp;quot; rather than &amp;quot;Are you coming to the party?&amp;quot; So, in this specific context, English might be considered the &amp;quot;odd man out&amp;quot; for often making a distinction based on the speaker&#039;s own attendance.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Surely it&#039;s Danish that&#039;s the odd man out here, if it&#039;s the only language on the planet that uses &amp;quot;come&amp;quot; rather than &amp;quot;go&amp;quot; here.&lt;br /&gt;
ChatGPT&lt;br /&gt;
You&#039;re absolutely right, and I stand corrected. If the common trend among the languages surveyed is to use a verb equivalent to &amp;quot;go,&amp;quot; then Danish would indeed be the outlier for commonly using a verb that translates to &amp;quot;come&amp;quot; in this context. It&#039;s an interesting quirk that sets Danish apart in how it handles directionality and focus relative to events. My apologies for the oversight.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Is Danish similar to Swedish, German, Dutch and perhaps French in this regard?&lt;br /&gt;
ChatGPT&lt;br /&gt;
Ah, let&#039;s explore how these languages handle the &amp;quot;come&amp;quot; versus &amp;quot;go&amp;quot; question when asking about attendance at an event.&lt;br /&gt;
&lt;br /&gt;
Swedish: Similar to Danish, the phrase &amp;quot;Kommer du på festen?&amp;quot; could be used, which translates to &amp;quot;Are you coming to the party?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
German: The language can go both ways. &amp;quot;Kommst du zur Party?&amp;quot; means &amp;quot;Are you coming to the party?&amp;quot; but &amp;quot;Gehst du zur Party?&amp;quot; (&amp;quot;Are you going to the party?&amp;quot;) is also common.&lt;br /&gt;
&lt;br /&gt;
Dutch: It&#039;s more typical to say &amp;quot;Ga je naar het feest?&amp;quot; which translates to &amp;quot;Are you going to the party?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
French: You&#039;d often hear &amp;quot;Tu vas à la fête?&amp;quot; meaning &amp;quot;Are you going to the party?&amp;quot; It is less common to hear &amp;quot;Tu viens à la fête?&amp;quot; unless the speaker is also attending or is already at the location.&lt;br /&gt;
&lt;br /&gt;
So, among these languages, Swedish and German may align more closely with Danish in that they can use a term equivalent to &amp;quot;come&amp;quot; when discussing attendance at an event. Dutch and French, on the other hand, lean more towards the equivalent of &amp;quot;go.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Based on this set, it seems that the &amp;quot;come&amp;quot; approach is not unique to Danish but can be found in some other Germanic languages as well. So, in the context of these closely related languages, Danish wouldn&#039;t be the &amp;quot;odd man out,&amp;quot; but part of a smaller subgroup.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Perhaps it&#039;s related to the fact that Danish doesn&#039;t have a word for &amp;quot;go&amp;quot; (general motion) – you have to use gå/løbe/køre/flyve/svømme/... – or indeed &amp;quot;tage&amp;quot; or &amp;quot;komme&amp;quot;.&lt;br /&gt;
ChatGPT&lt;br /&gt;
That&#039;s an intriguing observation. The absence of a generic &amp;quot;go&amp;quot; verb in Danish could indeed influence how directionality and movement are expressed in the language. The reliance on more specific verbs like &amp;quot;gå&amp;quot; (walk), &amp;quot;løbe&amp;quot; (run), &amp;quot;køre&amp;quot; (drive), &amp;quot;flyve&amp;quot; (fly), &amp;quot;svømme&amp;quot; (swim), etc., might push the language to use &amp;quot;komme&amp;quot; (come) in contexts where English or other languages would use &amp;quot;go.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In languages that have a generic verb for &amp;quot;go,&amp;quot; that verb often carries less implication about the speaker&#039;s or listener&#039;s involvement in the action. On the other hand, using &amp;quot;komme&amp;quot; in Danish might naturally imply a destination or event as a focal point, making it a suitable choice for asking about attendance, regardless of the speaker&#039;s involvement.&lt;br /&gt;
&lt;br /&gt;
So yes, the specific lexical gaps in a language can influence how certain ideas are most naturally expressed. Your observation about Danish lacking a general &amp;quot;go&amp;quot; verb could very well be a factor in this particular usage.&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Let&#039;s face it – the only other way to ask that question in Danish is probably &amp;quot;Tager du (med) til festen?&amp;quot;&lt;br /&gt;
ChatGPT&lt;br /&gt;
You&#039;re spot on. &amp;quot;Tager du (med) til festen?&amp;quot; would be another way to ask about someone&#039;s attendance at a party in Danish. The verb &amp;quot;tage&amp;quot; (to take) in this context often implies a certain level of involvement or action on the part of the person, similar to &amp;quot;going&amp;quot; in English. The optional &amp;quot;med&amp;quot; (along) can emphasize the collective aspect, potentially hinting that others, possibly including the speaker, will also be attending.&lt;br /&gt;
&lt;br /&gt;
So even without a generic &amp;quot;go,&amp;quot; Danish has ways to frame the question that carry slightly different nuances, much like English&#039;s &amp;quot;going&amp;quot; vs. &amp;quot;coming.&amp;quot; Fascinating how languages fill in these gaps, isn&#039;t it?&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
I remember somebody once asked me how to translate English &amp;quot;go&amp;quot; into Danish. I replied &amp;quot;tage&amp;quot;, and they looked like I was weird.&lt;br /&gt;
ChatGPT&lt;br /&gt;
Ah, the perils of cross-linguistic translation! While &amp;quot;tage&amp;quot; does convey the notion of going somewhere, it&#039;s not a one-to-one translation of the English &amp;quot;go.&amp;quot; In English, &amp;quot;go&amp;quot; is a general verb used for all kinds of motion, but &amp;quot;tage&amp;quot; in Danish implies the act of taking or bringing oneself somewhere, often with a sense of purpose. It doesn&#039;t encompass all the various types of movement that &amp;quot;go&amp;quot; does in English. So, while your answer captured a part of the concept, it understandably raised some eyebrows.&lt;br /&gt;
&lt;br /&gt;
This sort of thing happens often when we attempt to map one language&#039;s lexicon onto another&#039;s. Each word carries its own set of nuances, making direct translation a tricky affair. It&#039;s often these little subtleties that make learning a new language both a challenge and a delight, don&#039;t you think?&lt;br /&gt;
&lt;br /&gt;
User&lt;br /&gt;
Very true.&lt;br /&gt;
ChatGPT&lt;br /&gt;
I&#039;m glad you agree. The intricacies of language never cease to amaze, and it&#039;s always enlightening to delve into these nuances. Whether it&#039;s the lack of a generic &amp;quot;go&amp;quot; in Danish or the specific sensory verbs in a constructed language, these details make each linguistic system unique and fascinating.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=32</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=32"/>
		<updated>2023-11-23T20:08:57Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Chats with ChatGPT */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
[[Locative nouns]].&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
* A [[chat about sensing verbs]].&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=31</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=31"/>
		<updated>2023-11-23T18:04:52Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Sorted by function:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
* Tense/aspect: [[PRES]], [[PAST]], [[IRR]].&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
Ideas:&lt;br /&gt;
* Tense/aspect: [[FUT]], [[NOMIC]], [[IMP]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]].&lt;br /&gt;
* Other: [[EACHOTHER]].&lt;br /&gt;
&lt;br /&gt;
Removed because they can be expressed through a full lemma:&lt;br /&gt;
* Causative.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Abugida&amp;diff=30</id>
		<title>Abugida</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Abugida&amp;diff=30"/>
		<updated>2023-11-23T17:19:30Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;Inspired by shorthand and Shavian, use simple shapes for the consonants, ideally moving left to right (like a dash).  &amp;#039;a&amp;#039; is the implicit vowel.  &amp;#039;i&amp;#039; and &amp;#039;u&amp;#039; should attach only to the preceding consonants, given that they always finish a root (apart from proper nouns).  &amp;#039;ā&amp;#039;, &amp;#039;ē&amp;#039;, &amp;#039;ī&amp;#039;, &amp;#039;ō&amp;#039; and &amp;#039;ū&amp;#039; should connect to both sides, given that they can never finish a root.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Inspired by shorthand and Shavian, use simple shapes for the consonants, ideally moving left to right (like a dash).&lt;br /&gt;
&lt;br /&gt;
&#039;a&#039; is the implicit vowel.&lt;br /&gt;
&lt;br /&gt;
&#039;i&#039; and &#039;u&#039; should attach only to the preceding consonants, given that they always finish a root (apart from proper nouns).&lt;br /&gt;
&lt;br /&gt;
&#039;ā&#039;, &#039;ē&#039;, &#039;ī&#039;, &#039;ō&#039; and &#039;ū&#039; should connect to both sides, given that they can never finish a root.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=29</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=29"/>
		<updated>2023-11-23T17:16:25Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Writing system */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
[[Locative nouns]].&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
The [[abugida]].&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=28</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Main_Page&amp;diff=28"/>
		<updated>2023-11-23T17:16:04Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Grammar ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Lexicon ==&lt;br /&gt;
&lt;br /&gt;
=== Particles ===&lt;br /&gt;
&lt;br /&gt;
A [[table of particles]].&lt;br /&gt;
&lt;br /&gt;
=== Content words ===&lt;br /&gt;
&lt;br /&gt;
[[Locative nouns]].&lt;br /&gt;
&lt;br /&gt;
== Writing system==&lt;br /&gt;
&lt;br /&gt;
== Thoughts and chats ==&lt;br /&gt;
&lt;br /&gt;
=== Brief thoughts ===&lt;br /&gt;
&lt;br /&gt;
Even if we only have 1000 roots, this enables 1m simple compounds, of which we&#039;d need perhaps 50k to cover relatively simple meanings, and 1b three-element compounds, which would be more than enough to cover everything in any dictionary. (And realistically, many ideas would be better expressed through longer compounds.) So surely 1000 is more than enough.&lt;br /&gt;
&lt;br /&gt;
=== Chats with ChatGPT ===&lt;br /&gt;
&lt;br /&gt;
* A [[chat on 23/11/23]] about REL for both adjectives and relative phrases, about comitative, and about God.&lt;br /&gt;
&lt;br /&gt;
== Admin stuff==&lt;br /&gt;
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=27</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=27"/>
		<updated>2023-11-23T17:14:50Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Sorted by function:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
* Tense/aspect: [[PRES]], [[PAST]], [[IRR]].&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
Ideas:&lt;br /&gt;
* Tense/aspect: [[FUT]], [[NOMIC]], [[IMP]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]].&lt;br /&gt;
* Other: [[EACHOTHER]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=26</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=26"/>
		<updated>2023-11-23T17:13:13Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Sorted by function:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
* Tense/aspect: [[PRES]], [[PAST]], [[IRR]].&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
Ideas:&lt;br /&gt;
* Tense/aspect: [[FUT]], [[NOMIC]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [[SUPPOS]].&lt;br /&gt;
* Other: [[EACHOTHER]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=25</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=25"/>
		<updated>2023-11-23T17:12:56Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Sorted by function:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
* Tense/aspect: [[PRES]], [[PAST]], [[IRR]].&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;br /&gt;
&lt;br /&gt;
Ideas:&lt;br /&gt;
* Tense/aspect: [[FUT]], [[NOMIC]].&lt;br /&gt;
* Epistemic: [[PROB]], [[DEF]], [[REP]], [SUPPOS]].&lt;br /&gt;
* Other: [[EACHOTHER]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=24</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=24"/>
		<updated>2023-11-23T17:04:24Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Sorted by function:&lt;br /&gt;
* Cases: [[NOM]], [[ACC]], [[DAT]], [[ABL]], [[GEN]], [[INS]], [[VOC]], [[REL]].&lt;br /&gt;
* Tense/aspect: [[PRES]], [[PAST]], [[IRR]].&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=23</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=23"/>
		<updated>2023-11-23T17:04:03Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;br /&gt;
&lt;br /&gt;
Sorted by function:&lt;br /&gt;
* Cases: [[NOM]], [[ACC], [[DAT]], [[ABL]], [[GEN]], [[INS], [[VOC]], [[REL]].&lt;br /&gt;
* Tense/aspect: [[PRES]], [[PAST]], [[IRR]].&lt;br /&gt;
* Personal: [[1P]], [[2P]], [[3P]], [[REFL]].&lt;br /&gt;
* Conjunctions: [[AND]], [[OR]].&lt;br /&gt;
* Politeness: [[POLITE]], [[PEOR]].&lt;br /&gt;
* Other: [[QUEST]], [[NEG]], [[PROP]], [[PLUR]], [[ALSO]].&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=22</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=22"/>
		<updated>2023-11-23T16:59:13Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| ka || [[REL]] || [[QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| [[ALSO]] || (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=21</id>
		<title>Table of particles</title>
		<link rel="alternate" type="text/html" href="https://wiki.languagecreator.org/index.php?title=Table_of_particles&amp;diff=21"/>
		<updated>2023-11-23T16:56:18Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Particles&lt;br /&gt;
|-&lt;br /&gt;
! !! -a !! -i !! -u&lt;br /&gt;
|-&lt;br /&gt;
! j-&lt;br /&gt;
| [[OR]] || ji || [[2P]]&lt;br /&gt;
|-&lt;br /&gt;
! t-&lt;br /&gt;
| [[3P]] || [[PAST]] || [[DAT]]&lt;br /&gt;
|-&lt;br /&gt;
! s-&lt;br /&gt;
| [[NOM]] || [[REFL]] || su&lt;br /&gt;
|-&lt;br /&gt;
! h-&lt;br /&gt;
| [[PEOR]] || hi || [[VOC]]&lt;br /&gt;
|-&lt;br /&gt;
! l-&lt;br /&gt;
| [[PROP]] || [[PLUR]] || lu&lt;br /&gt;
|-&lt;br /&gt;
! m-&lt;br /&gt;
| [[PRES]] || [[1P]] || [[ACC]]&lt;br /&gt;
|-&lt;br /&gt;
! p-&lt;br /&gt;
| [[ABL]] || [[INS]] || pu&lt;br /&gt;
|-&lt;br /&gt;
! v-&lt;br /&gt;
| [[AND]] || [[POLITE]] || [[IRR]]&lt;br /&gt;
|-&lt;br /&gt;
! n-&lt;br /&gt;
| [[GEN]] || [[LOC]] || [[NEG]]&lt;br /&gt;
|-&lt;br /&gt;
! k-&lt;br /&gt;
| [[ALSO]] || [[REL]] || [QUEST]]&lt;br /&gt;
|-&lt;br /&gt;
! c-&lt;br /&gt;
| ca|| (ci) || cu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;ci&#039;&#039; is in brackets because it&#039;s probably not wise to use &#039;&#039;ti&#039;&#039;, &#039;&#039;ki&#039;&#039; and &#039;&#039;ci&#039;&#039; at the same time.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
</feed>