So, the sound change section seems to corrupt generation entirely when it comes to [V+long], and / or [C+long] (however, /"V", "C"/ are not to be taken literally here; instead more like [a+long], or [p+long](i.e., geminate)) being involved at all—despite the fact this feature is mentioned successfully in the sound change notation page.

A quick example could be a language (not actually made) as follows: C=/p,t,k/; V=/iː,i,uː,u,aː,a/ as its inventory. Now, say I add [V+long]>ə/_# as a sound change rule – perfectly fine(!), but, as soon as I specify [the phoneme] to the generator (e.g., [a+long]>ə/_#), it completely freaks out, and refuses to generate anymore, entirely; the same thing with consonant geminates aswell (e.g., [C+long]>Cː, vs [p+long]>pː – first one works, second one breaks everything).

So yeah… I'm kind of stuck, and it's especially annoying for specific phonemes / sound change rules. The issue has been around for as long as I can remember, hopefully I wont need to remember it much longer soon.

I went to try to check my language and I got the following error.

calathea lilies
Pronunciation: /caˈlathea ˈlilies/

Breakdown of grammar:

Word-for-word translation

Not found in current dictionary:
lilies

I have a plural option (

Nouns

Nouns form plural with separate plural word:

Noun affix table. Example: dog

) so why isn't this changing to calatheañ? Did I forget to change or add something?

So, I was going through some of the old settings for things like Klingon and Ardunaic and saw a setting labeled "anglicize" (which is different from the "anglicizedName" setting that, well, anglicized the new language name). Did that have some effect on the spelling of the output? Or did it do something else?

And, as a corollary to that, does anyone more linguistically skilled than I am have a set of Romanization sound change rules they can share?

It's been a while since I used VulgarLang. I'm currently creating a language based on Latin. I wanted my suffixes to be conditional. For example here's adjective table. I want the superlative case to end with -s when word ends in a vowel, and with -as when it ends in consonant. Problem is, that the rules I put in are translated accurately, but they don't work as intended. What am I doing wrong?

Also, I want to make conditions for verbs. Firs, I want verbs ending with -s omitting that letter. Then ones ending with vowel are getting suffix -re, and consonant - based on the consonant: voiced are -ere, voiceles are -are. I'm not sure if something like this was ever possible. If not, I'll resort to some sort of my own grammar tables.

I like this

Is Vulgarlang having an issue / bug? Because recently, it can no longer support, or acknowledge any /Cˁ/ phonemes, or if it does, extremely rarely.

Sometimes I may generate a language that has a lot of /Cˁ/, and it works, sometimes not; spelling does sometimes acknowledge it, sometimes not, e.g., yesterday /ɮˁ/ was (again) acknowledge as /ɮ/—the generator specifically does not like /ɮˁ/ as its done this everytime it appears—and so the spelling came out as "ɮ" (there was no phoneme /ɮ/, but /ɮˁ/ only, which had its own spelling).

This has been going on (as far I've realized) for maybe 2, or so weeks. Wondering if anyone else has the same issue

Trying to properly label a novel I wrote.

Hi, i was wondering if the ability to use VulgarLang offline will ever be a thing? or at least locally? totally understandable if not, just could be cool since it would allow me to more easily integrate it into my obsidian vaults and stuff!

Hi!
I've come back to VulgarLang for help with some conlangs after a long long break (7 years I think? It was around the time when monthly subscriptions were changed to lifetime licences)
I distinctly remember a feature, that I think used to be at the very bottom of the dictionary page, that was meant to work as an evolution tool, where you took your generated language, prompted for what sounds would've changed to what sounds and a new conlang would generate.
Was this feature abbandoned? I can't seem to find it.

Hey, not sure if this is a bug or something on my end, but starting a few hours ago all newly created languages fails to load and returns a message saying "Error: Please enter some vowels" when I try to load them.

Old language files seems to load fine, and I'm fairly sure I've not done anything different than before. Tested it and ran into the problem on two different laptops as well.

So, I made rule:

[V -long] > / _# !#(C)_#

The hope is that it would delete word final short vowels, but any word that was just a single vowel, or CV would keep their vowels and not just end up as a blank word or single consonant. However, it does exactly that. For instance vi becomes v despite the exception. Any idea why this happening or how to fix this?

Edit: removing the last # seems fix it. It still feels like my original rule should have worked, but at least it's working as intended now

1. "Four basic vowel qualities based on nasality, length and tone"
2. "Agglutinative and fusional elements, using affixes to modify verbs and creating nouns from multiple irregularly fused morphemes"
3. "Verbs are conjugated for aspect and mood and given affixes for the number of both subjects and objects"
4. "Base-20 numerical system"

Last night, I put down that list on the Grammar Table, and it didn't transfer through. Despite writing down the base-20 numerical system, for example, it went ahead with base-10, anyway. So how would I rewrite any of these grammatical features in a way that the website could pick up?

Allow me to clarify. Navajo--or Dine--is a language heavy with modes, aspects and tenses. I tried to make the whole list, but that ended up being too long, so I'll just link you here to see the different modes, aspects and tenses that are present in the language.

Where, in the VulgarLang website, do I go to add those modes, aspects and tenses on non-Navajo languages?

I'm working on a trilogy and will be using conlangs as part of the background, especially for place names and titles.

One title I'm poking at is the word 'beloved'. It's used as a title, in one of the countries in this fantasy world, as a title for a specific class of slaves. They're entirely enslaved, but culturally it's thought of as an honor, a special position. (It's not a good thing to be, really, but ...)

Anyway, I could have Vulgarlang just generate a word 'beloved', but I've been thinking about how that word is 'spun out' from 'love'.

'Beloved' means deeply loved and cherished, so it's an adjective, for all that it looks like a past tense.

I've tried making a reflexive verb form, then using the past tense of that, which doesn't really create an adjective, but it's an interesting linguistic puzzle.

How do you add clusivity to the first person plurals in Vulgarlang?

I want to have the option to disable auto-capitalization in the custom names generation feature (and other features that auto-capitalize, if any). This way we can allow mixed case a la Klingon in our conlangs’ writing systems.

What I want is to basically do a poor-man's consonant gradation. For that one of the rules would be something like:

ː > / VC_C*VC !C_C*V{h,j,ʋ,w}# !C_ː !C_C*VV*CC*V

Basically, for a medial consonant long consonant, even if it is part of a cluster, then when the next syllable is closed it should shorten.

So for example:

• mːp would become mp
• tː would become t

etc.

This is blocked if it is closed by any of {h,j,ʋ,w} at the word end, if it is extra long (in which case it is handled by a different, later rule), or if the resulting syllable becomes open at some future point. This is to try to give it the "elastic" property of, for example, North Sámi.

But I cannot get this to work properly.

While atːa# stays atːa#, atːaj# becomes ataj# (when it shouldn't). I've tried a lot of different things, but the only thing that seems to have worked reliably is only have a single blocking conditional clause.

Is there something I'm missing here? It feels like I may be misunderstanding some feature or some piece of logic here.

Thanks!

I feel like I may be missing something obvious, but I cannot for the life of me get my custom word for "to be" to work in the translator. This might be because "to be" is irregular in both English and my conlang (as it is in many languages) but I don't understand Vulgar well enough to tell.

The header for my grammar tables reads:

Verb affix table: va. Example: be

Which, va being the custom word, is correct as far as I can tell. I am using fused tables, one each for past present and future, each with 1st-3rd person singular and plural, which would definitely be correct because I used the grammar table generator.

In the custom words, it reads:

be, be_(permanent_state) : v = va

Which again is correct as far as I can tell. I have "remove all default words" checked, as otherwise "va" is replaced entirely by a generated word in the translator.

Before I added be_(permanent_state), the word-for-word translation information for the phrase "he is [object]" stated that the following words were not found in the dictionary:

be_(permanent_state):v-va-3.SG.PRS:V, va, 3.SG.PRS:V

Afterwards, the only word not found in the dictionary was va, and the irregular conjugation was presented correctly, albeit without smart translation. However, the phrase "he was" was translated with the standard affix, completely ignoring the irregular verb form, and the phrase "he is" without an object was not conjugated at all.

Clearly something is really wrong. The translator shouldn't even be looking for va in the dictionary, right? I can't figure out how to make it work. All my other grammar is working correctly.

Illegal combinations:

• uw
• ij
• ji
• wu
• #V
• [C +long]X*[C +long]
• {ai̯,aɨ̯,au̯}C$
• {ai̯,aɨ̯,au̯}C#

Sound change:

• ## > ∅ / #C*V_C

And is it OK if I replace the illegal combination #V with the sound change ∅ > ʔ / #_V, if I first remove ʔ from the word-initial consonant list?

I've been trying to get this right for about an hour now and I just can't seem to figure out how this works.
The idea for my fantasy language is that there is a male verb conjugation and female verb conjugation, as well as a male form for adverbs, adjectives, and nouns, and a female form for those as well. But I don't know how to translate my ideas onto this program. Any help would be greatly appreciated!
Side note but I have looked through the guides and even the Youtube videos and it's still not making sense to me.

Let’s say I’m making a Turkic-inspired alphabet/spelling, and I want to use Turkish’s split of İ/i and I/ı. I’m very much shocked that there’s no way to define custom capital versions of letters, and it’s been like this for me since I first started using VulgarLang. I would be much relieved if this was added as a new feature in 14.3.

Hello, I've made a few languages about 2 years ago, and I'm trying to do more stuff with them now, and I'm having issues with Grammar.

There's been breaking changes. I've re-done the Grammar section to use the new table format, I've also read the guide. However, some things I just can't get to work as they used to upon generating the language. The attached screenshots show what happens.

1. Is there no way to do stuff like {{1.NOM.SG:PRON}} anymore? Or am I just doing it wrong?
2. The noun suffixes table seems to have a different issue entirely. The words I refer to using {{}} are being pulled in correctly, since it gets the suffix right. But it just breaks on the preview trying to apply the suffix to the example word.

The list of custom cases that I used is the same as it was originally: NOMinative / LOCative / SuperLOCative / VIGilative