Logo of letter V with bug antennae

Vocabug
docs

Version: 0.5.0

Contents

  1. About Vocabug
  2. Interface
    1. Options
    2. File save / load
  3. Overall structure
    1. Comments
    2. About graphemes
    3. Null grapheme
    4. Escaping characters
      1. Word creation character escape
      2. Transform character escape
    5. Named escape
  4. Categories
    1. Categories inside categories and category-sets
  5. Building words
    1. Words
    2. Units
    3. Pick-one-set
    4. Optional-set
      1. Optional weight
    5. Supra-set
      1. Supra-set weight
  6. Default distributions
  7. Assigning weights
  8. The alphabet directive
  9. The invisible directive
  10. The graphemes directive
  11. The stage directive
  12. The change
    1. Concurrent change
    2. Merging change
    3. Reject
  13. Insertion and deletion
  14. The condition
    1. Multiple conditions in one rule
    2. Word boundary
    3. Syllable boundary
  15. The exception
  16. Using categories
  17. Features
    1. Pro-feature
    2. Anti-feature
    3. Para-feature
    4. Referencing features inside features
    5. Using features
    6. The feature-field directive
  18. Alternator and Optionalator
    1. Alternator-set
    2. Optionalator-set
  19. Cluster-field
  20. Wildcards and quantifiers
    1. Quantifier
    2. Bounded quantifier
    3. Kleene-star
    4. Geminate-mark
    5. Wildcard
    6. Anythings-mark
      1. Laziness and cowardliness
  21. Advanced rules
    1. Routine
    2. Target-mark
    3. Metathesis-mark
    4. Empty-mark
    5. Reference
      1. Reference of singular grapheme
      2. Reference of grapheme sequence
    6. Associatemes
  22. Questions and answers

1About Vocabug

This is the complete documentation for Vocabug, version: 0.5.0. Vocabug randomly generates vocabulary from a given definition of graphemes and word patterns. It can be used to generate words for a constructed language, original nicknames or passwords, or just for fun.

This word generator is designed to be a successor to the Williams' Lexifer and to the legendary Awkwords. You can find Vocabug's repository here. You can also install Vocabug to be used in your own projects or as a command-line-interface here. If you want a "modern" user interface, albeit with limited features, check out Vocabug-lite.

2Interface

2.1Options

2.2File save / load

3Overall structure

A definition-build is comprised of two top-level concepts: 'directives' and 'decorators'.

Directives are laid out like blocks and define the functions of Vocabug. The primary directives are the words directive, which creates each word, and the stage directive, which modifies each word with transforms. The other directives define concepts that are used by these primary directives.

Directives are written with their name on a newline, followed by a colon : on the same line, then followed by a newline. The payload after declaring a directive is interpreted according to the directive's semantics. A directive ends when a new directive begins, or when there are no more lines in the definition-build. For example:

words:
example

Decorators change a property of a directive to modify the directive's behaviour.

Decorators start on a new line above the directive they are modifying with an at sign @, followed by the directive, a ., the property, optional whitespace, =, optional whitespace, and then the new value of the property. For example:

@words.distribution = flat
words:
example

3.1Comments

If a line contains a semicolon ; everything after it on that line is ignored and not interpreted as Vocabug syntax -- unless ; is escaped. You can use this to leave notes about what something does or why you made certain decisions.

3.2About graphemes

Graphemes are indivisible meaningful characters that make a generated word in Vocabug. Phonemes can be thought of as graphemes. If we use English words sky and shy as examples to illustrate this, sky is made up by the graphemes s + k + y, while shy is made up by sh + y.

3.3Escaping characters

A single-length character following the syntax character \ ignores any meaning it might have had in the generator, including backslashes themselves. This way, anything including capital letters that have already been defined as categories, brackets, even spaces can be graphemes.

3.3.1Word creation character escape

These are the characters you must escape if you want to use them in categories, units and the words directive:

3.3.2Transform character escape

These are the characters you must escape if you want to use them in the stage directive:

3.4Named escape

Named escapes, enclosed in &[ and ] allow space and combining diacritics to be used without needing to insert these characters.

The supported characters are:

If you are using this, you should be very interested in the Compose routine.

4Categories

Categories are declared inside the categories directive on a line each. A category is a set of graphemes with a key. The key is a singular-length capital letter. For example:

categories:
C = t, n, k, m, ch, l,, s, r, d, h, w, b, y, p, g F = n, l,, t, k, r, p V = a, i, e, u, o

This creates three groups of graphemes. C is the group of all consonants, V is the group of all vowels, and F is the group of some of the consonants that will be used syllable finally.

These graphemes are separated by commas, however an alternative is to use spaces: C = t n k m ch l ꞌ s r d h w b y p g.

By default, the graphemes' frequencies decrease as they go to the right, according to the Gusein-Zade distribution. You can change this distribution with a decorator on the words directive, read how to do this here. In the above example, when Vocabug needs to choose a V, it will choose a the most at 43%, i the second-most at 26%, e the third-most at 17%, u the fourth-most at 10%, and o the fifth most at 4%.

Need more than 26 categories? Vocabug supports the following additional characters as the key of a category or unit: Á Ć É Ǵ Í Ḱ Ĺ Ḿ Ń Ó Ṕ Ŕ Ś Ú Ẃ Ý Ź À È Ì Ǹ Ò Ù Ẁ Ỳ Ǎ Č Ď Ě Ǧ Ȟ Ǐ Ǩ Ľ Ň Ǒ Ř Š Ť Ǔ Ž Ä Ë Ḧ Ï Ö Ü Ẅ Ẍ Ÿ Γ Δ Θ Λ Ξ Π Σ Φ Ψ Ω

4.1Categories inside categories and set-categories

You can use categories inside categories, as long as the referenced category has previously been defined. For example:

@categories.distribution = flat categories: L = aa, ii, ee, oo V = a, i, e, o, L

In the example above, V has a 20% chance of being a long vowel.

You can also enclose a set of graphemes in curly braces { and }. This is called a 'set-category'. This set will be treated as if it were a reference to a category in terms of frequency. For example, we could write the same example as this:

@categories.distribution = flat categories: V = a, i, e, o, {aa, ii, ee, oo}

Assigning weights to categories in categories and set-categories is possible.

Categories inside categories and set-categories CANNOT be a part of any sequence. for example C = Xz or C = x{c, d} or C = {a, b}{c, d} will not give the results you might want. To get sequence-like behaviour like that, you will need to use units.

4.2Null grapheme

If a word is built using the syntax character ^, it will disappear in the generated word. In other words ^ is a null grapheme. If you want to use ^ as a grapheme, you will need to escape it. To use other syntax characters as graphemes, they must be escaped too.

5Building words

5.1Words

The words directive defines a set of 'word-shapes' that Vocabug will choose from to create words. A word-shape can consist of individual graphemes, categories, units or a mixture of both.

Word-shapes are separated by a comma, space, or a newline.

By default, words are selected using the Zipf distribution. The first word-shape will be chosen the most often, then the second word-shape the second most often and so on. You can change this distribution. Below is a very simple example that will generate words with one to three CV syllables:

categories: C = t, n, k, m, l, s, r, d, h, w, b, j, p, g V = a, i, o, e, u words: CV,
CVCV, CVCVCV, ; This is a comment
V

5.2Units

Units are a system that provides an abbreviation of parts of a word-shape. Typically you use it to define the shape of a syllable. Units are defined similarly to categories, but with several important differences:

For example you could write the last example like so:

categories: C = t, n, k, m, l, s, r, d, h, w, b, j, p, g V = a, i, o, e, u units: $ = CV
Vowel-only = V words: <$><$>, <$>, <$><$><$>, <Vowel-only>

You can put units inside units. For example: Example = $$

5.3Pick-one-set

A pick-one-set is a group of graphemes and categories separated by spaces or commas, enclosed in curly braces { and }. Vocabug will pick an option from that pick-one just like it would from a unit. For example:

categories: V = a, u words: t{V, x}

This will produce either ta, tu or tx.

Pick-one-sets can be nested inside each other.

Anything inside the pick-one can be assigned a weight, and a pick-one itself can be assigned a weight as well if it is nested inside another set:

words: {a*1, b*2, {c, d}*2}

5.4Optional-set

Using round brackets, ( and ), optional-set works the same way as pick-one-set, the only difference is that what's inside them can either appear in the word or not. The probability of each of these variants is 10% by default.

words: ta(n, t, l)

In the above example, there is a 10% chance of getting one of tan, tat or tal, but a 90% chance of ta.

5.4.1Optionals weight

By default, an optional-set has a 10% chance of being included in the word. You can change this probability with a decorator.

@words.optionals-weight = 10%
words:
example

5.5Supra-set

A 'supra-set', is applied over the entire word, and there can only be one supra set. Square brackets [ and ], denotes each item in the supra-set and their location in the word. The items of a supra-set can only be a category, or the null grapheme ^. Only one item in the supra-set will be picked for that generated word.

Supra-set is a feature designed to help generate words with stress systems, pitch accent systems, or other word-based suprasegmentals. Here is an example where it is used for a stress system:

categories: C = t
V = a
X = ' words: ([X]CV)[X]CV

This produces any of the following words: 'ta, ta'ta, 'tata, never any words with more than one '. Notice here that ta is not possible -- A supra-set item is only chosen after dealing with any sets that the supra-set items are nested in.

See the "Romance-like" example for a language that uses supra-set for its stress system.

5.5.1Supra-set weight

You can set the weights of supra-set items like so:

categories: R = r units: X = o[R*8]
Y = e[R*2] words: <X><Y>

The above example has an 80% chance of generating ore and a 20% chance of generating oer.

Supra-set item weights support a sentinel value -- a 'super-heavy' value s. This s will ensure the supra-set item attached to this weight is always chosen over others. For example: [V*s]

6Default distributions

The ordering of items matters in categories, units and word-shapes. The first item will be chosen the most often, the second grapheme the second most often, and so on.

You can change these default distributions (another name for this might be "default drop-off", but I digress). For categories, the default is gusein-zade and you change it with the @categories.distribution decorator. For the separate decorator for word-shapes, the default is zipfian and you change it with the @words.distribution decorator. The distribution will be applied to each item in a set, and then recursively to any set that set is nested in (treating the nested set as an item), then applied at the surface level.

The values of the property distribution can be either: Distribution graph

7Assigning weights

If you want to set your own frequency for graphemes in a category or category-set, items in a pick-one-set, or optional-set, or word-shapes in the words directive, you can use an asterisk * to specify the weight for each item, like so:

categories: V = a*5, e*4, i*3, o*2, u*1 units: $ = {V*8, x*2} words: <$>*2, y

V has approximately the following probabilities: a: 33%, e: 27%, i: 20%, o: 13%, u: 7%. The pick-one-set in the $ unit has an 80% chance of producing a V category over the x grapheme. And the first word-shape in the words directive has twice the chance of being chosen over the next word-shape.

As you might have noticed in the example above, in a sequence that has at least one weighted option, it overwrites any default distributions. Also important to note is that any other option that you had not given a weight (inside that set, or on the surface level), is given a weight of 1.

8The alphabet directive

The alphabet directive gives Vocabug a custom alphabetisation order for words, when the sort words checkbox is selected.

alphabet: a, b, c, e, f, h, i, k, l, m, n, o, p, p', r, s, t, t', y

This would order generated words like so: cat, chat, cumin, frog, tray, t'a, yanny

9The invisible directive

Sometimes you will want characters, such as syllable dividers, to be invisible to alphabetisation. You can do this by listing these characters in the invisible: directive.

invisible: ., '

This will make these generated words: za'ta, 'ba.ta, 'za.ta be reordered into: 'ba.ta, za'ta, 'za.ta

10The graphemes directive

The graphemes directive tells Vocabug which (multi)graphs, including character + combining diacritics, are to be treated as grapheme units when using transformations.

graphemes: a, b, c, ch, e, f, h, i, k, l, m, n, o, p, p', r, s, t, t', y

In the above example, we defined ch as a grapheme. This would stop a rule such as c -> g changing the word chat into ghat, but it will make cobra change into gobra.

Which graphemes are 'associatemes' of their 'bases' are declared in the graphemes directive. Read more about this in this section of the documentation.

11The stage directive

Once words are generated, you might want to modify them to prevent certain sequences, outright reject certain words, or simulate historical sound changes. This is the purpose of transforms, which are all declared in the stage directive:

stage: ; Your transforms go here

The default transform is a rule. These should be familiar to anyone who knows a little about phonological rules. The two other types of transforms are cluster-fields and routines.

A rule can be summarised as four fields: CHANGE / CONDITION ! EXCEPTION. The characters / and ! that precede each field (except for the CHANGE) are necessary for signalling each field. For example, including a ! will signal that this rule contains an exception, and all text following it until the next field marker will be interpreted as such.

Every rule begins on a new line and must contain a CHANGE. The CONDITION or EXCEPTION fields are optional.

If you want to capture graphemes that are normally syntax characters in transforms, you will need to escape them.

When this document uses examples to explain transformations, the last comment shows an example word transforming. For example ; amda ==> ampa means the rule will transform the word amda into ampa

12The change

The format of a rule's CHANGE can be expressed as TARGET -> REPLACEMENT.

Let's look at a simple unconditional rule:

; Replace every [o] with [x]
o -> x
; bodido ==> bxdidx

In this rule, we see every instance of o become x.

12.1Concurrent change

Concurrent change is achieved by listing multiple graphemes in TARGET separated by commas, and listing the same amount of replacement graphemes in REPLACEMENT separated by commas. Changes in a concurrent change execute at the same time:

; Switch [o] and [a] around
o, a -> a, o
; boda ==> bado

Notice that the above example is different to the example below:

o -> a
a -> o
; boda ==> bodo

where each change is on its own line. We can see o merge with a, then a becomes o.

12.2Merging change

Instead of listing each REPLACEMENT in a concurrent change, we can instead list just one that all the TARGETs will merge into:

; Merge [o] and [a] into [x]
o, a -> x
; boda ==> bxdx

This is equivalent to:

; Merge [o] and [a] into [x]
o, a -> x, x
; boda ==> bxdx

12.3Reject

To remove, or in other words, reject a word, you use a zero 0 in REPLACEMENT:

a, bi -> 0

In the above example, any word that contains a or bi will be rejected.

13Insertion and deletion

Insertion requires a condition to be present, and for a caret ^ to be present in TARGET, representing nothing.

; Insert [a] in between [b] and [t] ^ -> a / b_t ; bt ==> bat

Deletion happens when ^ is present in REPLACEMENT:

; Delete every [b] b -> ^ ; bubda ==> uda

14The condition

Conditions follow the change and are placed after a forward slash. When a transform has a condition, the target must meet the environment described in the condition to execute.

The format of a condition is / BEFORE_AFTER

For example:

; Change [o] into [x] only when it is between [p]s
o -> x / p_p
; opoptot ==> opxptot

14.1Multiple conditions in one rule

Multiple conditions for a single rule can be made by separating each condition with additional forward slashes. The change will happen if it meets either, or both of the conditions:

; Change [o] into [x] only when it is between [p]s or [t]s
o -> x / p_p / t_t
; opoptot ==> opxptxt

14.2Word boundary

Hash # matches to word boundaries. Either the beginning of the word if it is in BEFORE, or the end of the word if it is in AFTER

o -> x / p_p#
; opoppop ==> opoppxp

14.3Syllable boundary

Dollar-sign $ matches to either the character . or if no match, tries to match word boundaries. Either the beginning of the word if it is in BEFORE, or the end of the word if it is in AFTER

o -> x / p_p$
; o.pop.pop ==> o.pxp.pxp

15The exception

Exceptions are placed following an exclamation mark ! and go after the condition, if there is one. Exceptions function exactly like the opposite of the condition -- when a rule has an exception, the target must meet the environment described in the exception to prevent execution:

aa -> a ! _#

In the above example, the transformation will not execute if aa is at the end of the word.

If there are multiple exceptions, the transform must meet all of the exceptions for it not to execute.

An alternative to using an exclamation mark is to use two forward slashes //.

16Using categories

You can reference categories in transforms. The category will behave in the same way as an alternator set:

categories: B = x, y, z
stage:
B -> ^
; xapay ==> apa

If the category is part of a target, it MUST be inside an alternator set:

categories: B = x, y, z stage: {B}v -> ^
; xvapay ==> apay

17Features

Let's say you had the grapheme, or rather, phoneme /i/ and wanted to capture it by its distinctive vowel features, +high, -round and +front, and turn it into a phoneme marked with +high, -round and +back features, perhaps /ɯ/. Vocabug's features directive and feature matrices let you do this. Vocabug's features can be described as binary and 'non-carryover'.

The key of all features must consist of lowercase letters a to z, uppercase letters a to z, ., - or +

17.1Pro-feature

A feature prepended with a plus sign + is a 'pro-feature'. For example +voice. We can define a set of graphemes that are marked by this feature by using this pro-feature. For example:

features: +voice = b, d, g, v, z

17.2Anti-feature

A feature prepended with a minus sign - is an 'anti-feature'. For example -voice. We can define a set of graphemes that are marked by a lack of this feature by using this anti-feature. For example:

features: -voice = p, t, k, f, s

17.3Para-feature

A feature prepended with a greater-than-sign > is a 'para-feature'. A para-feature is simply a pro-feature where the graphemes marked as the anti-feature of this feature are the graphemes in the graphemes: directive that are not not marked by this para-feature:

graphemes: a, b, h, i, k, n, o, t features: >voice = a, i, o

Is equivalent to the below example:

features: +vowel = a, i, o
-vowel = b, h, k, n, t

'Where does this leave graphemes that are not marked by either the pro-feature or the anti-feature of a feature?', you might ask. Such graphemes are unmarked by that feature.

17.4Referencing features inside features

Features can be referenced inside features. For example:

features: +vowel = a, i, o
+non-yod = +vowel, ^i

Use a caret in front of a grapheme to ensure that that grapheme is not part of the pro/anti/para-feature. In the example above, the pro-feature '+non-yod' is composed of the graphemes a and o -- the grapheme i is not part of this pro-feature. Due to the recursive nature of nested features, this removed grapheme will be removed... aggressively. For example, If +non-yod were to be referenced in a different feature, that feature would always not have i as a grapheme.

17.5Using Features

To capture graphemes that are marked by features in a transform, the features must be listed in a 'feature-matrix' surrounded by [ and ]. The graphemes in a word must be marked by each pro-/anti-feature in the feature-matrix to be captured. For example if a feature-matrix [+high, +back] captures the graphemes: u, ɯ, another feature-matrix [+high, +back, -round] would capture ɯ only.

The very simple example below is written to change all voiceless graphemes that have a voiced counterpart into their voiced counterparts:

features: -voice = p, t, k, f, s +voice = b, d, g, v, z stage: [-voice] -> [+voice] ; tamefa ==> dameva

In this rule, in REPLACEMENT, [+voice] has a symmetrical one-to-one change of graphemes from the graphemes in [-voice] in TARGET, leading to a concurrent change. Let's quickly imagine a scenario where the only [+voice] grapheme was b. The result will be a merging of all -voice graphemes into b: tamepfa ==> bamebba.

It should be noted that feature-matrices in TARGET have no carryover to feature-matrices in REPLACEMENT. For example, in a bogus rule such as o -> [+high] Vocabug will not try to transform <o> into it's [+high] counterpart, it will try and replace <o> with some grapheme marked as [+high] and will probably fail unless only one grapheme is marked as [+high].

If the feature-matrix is part of a target, i.e: it has tokens on either side of it, it MUST be inside an alternator set.

17.6The feature-field directive

Feature-fields allow graphemes to be easily marked by multiple features in table format.

The graphemes being marked by the features are listed on the first row. The features are listed in the first column.

For example:

feature-field: m n p b t d k g s h l j voice + + - + - + - + - - + + plosive - - + + + + + + - - - - nasal + + - - - - - - - - - - fricative - - - - - - - - + + - - approx - - - - - - - - - - + + labial + - + + - - - - - - - - alveolar - + - - + + - - + - + - palatal - - - - - - - - - - - + velar - - - - - - + + - - - - glottal - - - - - - - - - + - - feature-field: a e i o high - - + - mid - + - + low + - - - front - + + - back + - - + round - - - +

Here are some matrices of these features and which graphemes they would capture:

18Alternator and Optionalator

These cannot be nested.

18.1Alternator-set

Enclosed in curly braces, { and }, only one Item in an alternator set will be part of each sequence. For example:

p{w, j} -> pp

The above example is equivalent to:

pw, pj -> pp

These can also be used in exceptions and conditions.

18.2Optionalator-set

Items in an optionalator, enclosed in ( and ) can be captured whether or not they appear as part of a grapheme or as part of a sequence of graphemes:

; Merge [x] and [xw] into [k]
x(w) -> k
; xwaxaħa ==> kakaħa

Optional-set can also attach to an alternator-set:

; Merge [x], [xw], [ħ] and [ħw] into [k]
{x, ħ}(w) -> k
; xwaxaħa ==> kakaka

Optionalator-set cannot be used on its own, it must be connected to other content.

19Cluster-field

Cluster-field is a way to target sequences of graphemes and change them. They are laid out as tables, and start with < followed by a space. The first part of a sequence is in the first column, and the second part is in the first row. The clusterfield ends with a > on its own line. For example:

< p t k m n m + nt nk + mm n mp + + nn + >

20Wildcards and quantifiers

Wildcards and the like in this section are special tokens that can represent arbitrary amounts of arbitrary graphemes, which is especially useful when you don't know precisely how many, or of what kind of grapheme there will be between two target graphemes in a word.

20.1Quantifier

Quantifier, using +, will match once or as many times as possible to the grapheme to the left of it. Quantifier cannot be used in REPLACEMENT:

a+ -> o
; raraaaaa ==> roro

20.2Bounded quantifier

The bounded quantifier matches as many times its digit(s), enclosed in ?[ and ], to the things to the left.

; Change [o] into [x] only when preceded by three [r]s
o -> x / r?[3]_ ; ororrro ==> ororrrx

The digits in the quantifier can also be a range:

; Change a sequence of 2 to 4 [o]s into [x]
o?[2,4] -> x ; tootooooo ==> txtxo

At the beginning of the list, , represents all the possible numbers lower than the number to the right, not including zero.

; Change a sequence of 1 to 4 [o]s into [x]
o?[,4] -> x ; tootooooo ==> txtx

And finally at the end of the list, , represents all possible numbers larger than the number to the the left

; Change a sequence of 4 to as many as possible [o]s into [x]
o?[4,] -> x ; toootooooo ==> toootx

20.3Geminate-mark

Geminate-mark using colon :, will duplicate the grapheme, or grapheme from a set or category, to the left of it. In other words, you can capture an item only when it is geminated using the geminate-mark:

a: -> o
; aaata => oata

Unlike quantifier, a geminate mark can be used in REPLACEMENT:

a -> a:
; tat => taat

20.4Kleene-star

Occasionally, you may want to match a grapheme whether it exists, there is one of it, or there is multiple of it consecutively, known as a "Kleene-star". There is no dedicated character for a Kleene star. Instead, you wrap the content followed by a quantifier, in an optionalator:

u(a+) -> o
; ruaruaaaaa ==> roro

20.5Wildcard

Wildcard, using asterisk *, will match once to any grapheme. Wildcard does not match word boundaries. Wildcard cannot be used in REPLACEMENT:

; Any grapheme becomes [x] when any grapheme follows it
* -> x / _*
; aomp ==> xxxp

Wildcard can be placed by itself inside an optionalator (*), thereby allowing it to match nothing as well.

20.6Anythings-mark

The anythings-mark uses percent sign % and a pair of square brackets [ and ]. It will match as many (but not zero) times to any grapheme. For example:

b%[] -> x
; abitto => ax

As we can see, the rule matched b and greedily matched every and any grapheme after it.

The example below uses an anythings-mark in the condition:

; Simulate spreading of nasality to vowels
a, i, u ->,,/ {,,}%[]_
; pabãdruliga ==> pabãdrũlĩgã

20.6.1Laziness and cowardliness

By listing graphemes and grapheme sequences inside the square brackets, we can alter the "greedy" behaviour of an anythings-mark with degrees of "laziness" and 'cowardliness'.

Consuming negative lookahead, AKA "laziness":

Sometimes it is necessary to for the anythings mark to consume graphemes we are monitoring for, and then stop consuming:

b%[t, d] -> x
; babitto => xto

As we can see, the rule matched b followed by anything else until it reached the first t, consumed that, then stopped matching. This behaviour in Regular Expression terminology is called "lazy".

As already stated, the items to check for greediness can be a sequence of graphemes:

b%[tr, d] -> x
; batitro => xo

Sets, categories and features can also be used when monitoring for laziness and cowardliness:

; capture up to a plosive + [r] cluster %[{p,t,k}r] -> x ; kotatros -> xos

Negative lookahead, AKA 'cowardliness':

Sometimes it is necessary for graphemes to block the spread without having them be consumed, which I have dubbed 'cowardliness'. To do this put a pipe | between the lazy and cowardly items. For example we might want the graphemes k or g to prevent the rightward spread of nasal vowels to non nasal vowels:

a, i, u ->,,/ {,,}%[| k, g]_
; pabãdruliga ==> pabãdrũlĩga

21Advanced transforms

21.1Routine

The routine transform provides useful functions that you can call at any point in the transform block. You call a routine on a newline with <routine, optional space, =, optional space, the routine, and a closing >.

The routines are:

21.2Target-mark

A target-mark is a reference to the captured TARGET graphemes. It cannot be used in TARGET. This uses a less-than sign and a capital t &T.

Here are some examples where target-mark is employed:

Full reduplication:

& -> &T&T ; malak ==> malakmalak

"Haplology":

{C}{V}(B) -> ^ / _&T ; haplology ==> haplogy

Reject a word when a word-initial consonant is identical to the next consonant:

C -> 0 / #_&[C]&T

21.3Metathesis-mark

Simple metathesis involves a less-than-sign and a capital m &M in REPLACEMENT. This will swap the first and last grapheme from the captured TARGET graphemes:

; Swap a plosive and nasal stop {p, t, k}{m, n} -> &M
; apma ==> ampa

Since metathesis reference is swapping the first and last grapheme, we can effectively simulate long-distance metathesis using an anythings-mark:

; Simulate Old Spanish "Hyperthesis" r&l -> &M
; parabla ==> palabra

21.4Empty-mark

An Empty-mark using &E, inserts an 'empty' grapheme into the captured TARGET graphemes. It is only allowed in TARGET

One use for it is a trick to make one-place long-distance metathesis work, for example:

; The [r] of a plosive + [r] cluster is moved ; between a word initial plosive and a vowel &E{a,e,i,o,u}&[^{p,t,k}r]{p,t,k}r -> &M / #{p,t,k}_ ; kotatros -> krotatos

Another use for it is in a romanisation or deromanisation system using a cluster-field:

& p t k j y &E p t c y ü

21.5Reference

Sometimes graphemes must be copied or asserted to be a certain grapheme between other graphemes. This is the purpose of 'reference'. Reference is fairly straightforward, but there is a lot of jargon and different behaviour between fields to explain.

21.5.1Reference of singular grapheme

A grapheme (or graphemes) are bound to a reference using a 'reference-capture', to the right of some grapheme. A reference-capture looks like = followed by a single-digit positive number. This number is called the 'reference-key' of the reference. The grapheme (or graphemes) bound to the reference is called the 'reference-value'.

The key behaviours of reference-capture are:

The captured grapheme can then be reproduced elsewhere in the rule with a 'reference-mark', even before the reference-capture. The reference-mark invokes the reference-key of a reference.

The key behaviours of reference-mark are:

Here are some examples:

; Delete [ʔ] between identical vowels ʔ -> ^ / [+vowel]=1_1 ; baʔaʔe ==> baaʔe

In the rule above, we are binding the [+vowel] feature-matrix to the reference 1, by appending =1 to it. Whatever this grapheme from [+vowel] is when the condition is met, is captured as the value of 1. Then the value of backrefence 1 is inserted into AFTER by invoking its reference-mark.

; Insert an 'echo vowel' at the end of [ʔ] final words ^ -> 1 / {V}=1ʔ_# ; foobaʔ ==> foobaʔa

In the rule above, we are binding the V category to the reference 1, by appending =1 to it. Whatever this grapheme from V is when the condition is met is the value of 1. Then the value of 1 is inserted into REPLACEMENT by invoking its reference-mark.

21.5.2Reference of grapheme sequence

Now that 'reference-capture' and 'reference-mark' has been (hopefully) introduced and explained adequately, let's explain how to capture and reference a sequence of graphemes.

To start capturing a sequence, you use a 'start-reference-capture', &= before the graphmemes to be captured. Then at the end of the graphemes to be captured, a 'reference-capture' is used to bind those graphemes to a reference:

; Insert an 'echo double vowel' at the end of vowel + vowel + [ʔ] final words ^ -> 1 / &={V}{V}=1ʔ_# ; foobaaʔ ==> foobaaʔaa

21.6Associatemes

If your language encodes tone, stress, breathy voice, or other phonological features directly on vowels, you'll often need to target a particular grapheme across its variants.

One method is to target each variant manually:

{a, á, à} -> {e, é, è}
; daná ==> dené

This workaround uses alternators, but lacks semantic clarity and scalability, and is outright tedious.

To solve this, are 'associatemes' -- aligned graphemes associated with their base grapheme, and other associated graphemes -- other SCAs might use the terms "floating diacritics" or "autosegmentals". These allow you to target all forms of a grapheme with a single token. To set up associatemes, they must be stated in the graphemes directive with the base associateme set inside curly braces, and each associateme set in curly braces with a < to the left of the base set, or another set, like so:

graphemes: {a, e, i, o, u}<{á, é, í, ó, ú}<{à, è, ì, ò, ù}

The behaviour of associatemes are:

In a rule, you then put a tilde after the grapheme to mark it as a base associateme:

graphemes: {a, e, i, o, u}<{á, é, í, ó, ú}<{à, è, ì, ò, ù} stage: a~ -> e~
; daná ==> dené

This transform targets all variants of a and carries over that association to e.

22Questions and answers

Here are some common questions and answers about Vocabug:

The Generate button is greyed out

This means Vocabug is busy generating words for you, and will eventually become clickable again. If you think this is taking too long, perhaps you have force word limit accidentally on.

I received the error "Invalid regular expression"

This error occurs because you are using Vocabug in an old browser or old browser version that does not support lookbehind. You can check if this applies to you here.

What is a natural frequency for consonants in a language?

There is no one-size-fits-all answer to this question, and different analyses of word lists may produce different data on what the general expectation is. For example, in English, /ð/ is very uncommon among all the words in English, however it is a common phoneme among sentences because of the prevalence of the words this, that, those and the. And indeed, morphology, historical sound changes and word borrowing can skew any initial control you might have over frequencies.

However, a good rule of thumb is that phonemes that are easy to pronounce and distinguish will be the most common.

How do I weight an individual optional-set?

Using the @words.optionals-weight decorator affects the weight of all optional-sets. As of version 1, there is no direct way to weight an individual optional-set. You can however, use ^ as an item in an alternator, like a{b, c, ^*3}