Fun Translator

Hollowscript Translator

Translate from Normal Language to Bug like phonetics

Last updated: September 2025

Normal Language

Bug like phonetics

Gray highlighted text indicates translated content that differs from the original

Most frequent keywords:

Translation History

About the Hollowscript

Built for fan fiction, tabletop roleplay, and creative writing, Hollowscript outputs Bug like phonetics from your Normal Language input. Treat it as a strong creative-draft tool with optional review against fan resources for canonical accuracy.

Output works well for short phrases, full paragraphs, dialogue, captions, lyrics, and longer prose. For very long inputs, break the text into paragraphs and translate one at a time for the most consistent style.

Vocabulary (300 Words, 200 Unique) The Hallowscript translator is built around a 300-word English-to-Hallowscript vocabulary, provided in three 100-word lists, though the second and third lists are identical, resulting in 200 unique words. These words cover pronouns (e.g., “I” → “ego{{pronoun}}”), nouns (e.g., “knight” → “nefige{{noun}}”), verbs (e.g., “love” → “amo{{verb}}”), adjectives (e.g., “good” → “ba{{adjective}}”), question words (e.g., “what” → “kwe{{question}}”), and other categories like prepositions and conjunctions (e.g., “and” → “et{{other}}”). The words were selected for conversational utility, drawing from high-frequency English terms and Hollow Knight’s lore (e.g., “nail” → “stri{{noun}}” for the Knight’s weapon, “infection” → “radi{{noun}}” for the Radiance’s plague). Each Hallowscript word is tagged with its grammatical role ({{noun}}, {{verb}}, {{adjective}}, {{pronoun}}, {{question}}, {{place}}, {{other}}) in the Language 2 column to support LingoJam’s “Word Order Rules” feature for forward translation. Tags ensure proper reordering, such as swapping “adjective noun” (e.g., “good knight”) to “noun adjective” (e.g., “nefigeos ba”). The vocabulary is entered in LingoJam’s “Words” tab, with English in the first column and tagged Hallowscript words in the second, processed after phrases but before other rules. Phrases Although not explicitly provided in the conversation, phrases are a critical component of the translator, as they take priority over single-word translations in LingoJam’s rule-based system. Example phrases like “What language do you speak?” → “Kwe lingua tu lingoa?” or “How are you?” → “Kwe tu a?” are assumed to be part of the setup, entered in the “Phrases” tab. Phrases ensure multi-word expressions (e.g., greetings, questions) are translated as a unit before individual words are processed, preserving Hollow Knight’s dialogue style. For example, “peace be with you” might translate to “Pax kun tu a,” reflecting the conlang’s topic-comment structure. Phrases are entered first in the rule editor, with “Whole Word” and “Case Sensitive” options enabled to avoid partial matches. Prefixes (20 Rules) The “Word Beginnings” section includes 20 English-to-Hallowscript prefix rules to transform the start of words, applied after phrases and words. These rules target common English prefixes and align with Hallowscript’s grammar: “good” → “ba” (e.g., “goodhope” → “ba-akalos”). “bad” → “na” (e.g., “badlove” → “na-amo”). “pre” → “ante” (e.g., “prepare” → “ante-pari”). “re” → “itera” (e.g., “return” → “itera-veni”). “un” → “ne” (e.g., “unlike” → “ne-simi”). “mis” → “erra” (e.g., “mistake” → “erra-faci”). “over” → “supra” (e.g., “overlook” → “supra-spekti”). “under” → “suba” (e.g., “understand” → “suba-sapi”). “dis” → “dis” (e.g., “disappear” → “dis-pari”). “in” → “en” (e.g., “inside” → “en-loko”). “anti” → “kontra” (e.g., “antihero” → “kontra-heros”). “super” → “ultra” (e.g., “superstrong” → “ultra-forta”). “ex” → “ex” (e.g., “exclude” → “ex-kluda”). “inter” → “inter” (e.g., “interact” → “inter-acti”). “sub” → “sub” (e.g., “submerge” → “sub-mergi”). “pro” → “pro” (e.g., “protect” → “pro-tekti”). “con” → “kun” (e.g., “connect” → “kun-nekti”). “de” → “de” (e.g., “destroy” → “de-strui”). “mid” → “medi” (e.g., “midnight” → “medi-nokto”). “out” → “fora” (e.g., “outshine” → “fora-luma”). These prefixes add bug-like phonetics (e.g., “z” buzzes, “x” hisses) and are entered in the “Word Beginnings” section, with “Whole Word” unchecked, to apply to word starts only. Endings (10 Rules) The “Word Endings” section includes 10 rules to transform English word endings into Hallowscript equivalents, applied after prefixes: “ing” → “a” (e.g., “hoping” → “akalosa”). “ed” → “i” (e.g., “loved” → “amoi”). “s” → “oo” (e.g., “siblings” → “troos”). “ies” → “iioo” (e.g., “enemies” → “enemiioo”). “ly” → “e” (e.g., “quickly” → “rapide”). “er” → “or” (e.g., “worker” → “laboror”). “est” → “issa” (e.g., “fastest” → “rapidissa”). “ment” → “menta” (e.g., “moment” → “momentamenta”). “ion” → “io” (e.g., “infection” → “radiio”). “able” → “bila” (e.g., “capable” → “kapabila”). These endings handle verb tenses, plurals, adverbs, and noun forms, entered in the “Word Endings” section with “Whole Word” unchecked. Letter Groups (10 Rules) The “Letter Groups” section includes 10 rules to replace specific letter sequences within words, adding Hallowscript’s bug-like phonetics: “s” → “z” (e.g., “sibling” → “zibling”, overridden by “tros”). “oo” → “uu” (e.g., “pool” → “puul”). “th” → “t” (e.g., “think” → “tink” → “pensara”). “sh” → “x” (e.g., “shine” → “xine” → “luma”). “ch” → “k” (e.g., “charge” → “karge” → “shaw”). “qu” → “kw” (e.g., “quick” → “kwick” → “rapide”). “er” → “ar” (e.g., “worker” → “workar” → “laboror”). “ai” → “ey” (e.g., “wait” → “weyt” → “atenda”). “ea” → “i” (e.g., “speak” → “spik” → “lingoa”). “gh” → “g” (e.g., “light” → “ligt” → “luma”). These rules, entered in the “Letter Groups” section, apply last to avoid conflicts with words (e.g., “sibling” → “tros” overrides “s” → “z”). Regular Expressions (Forward: 10 Rules, Reverse: 10 Rules) The “Regular Expressions” section includes 10 forward (English to Hallowscript) and 10 reverse (Hallowscript to English) regex rules for complex transformations: Forward: “(\w+)ing\b” → “$1a” (e.g., “running” → “kursa”). “(\w+)ed\b” → “$1i” (e.g., “walked” → “ambuli”). “will (\w+)\b” → “$1o” (e.g., “will hope” → “akaloso”). “the (\w+)\b” → “$1os” (e.g., “the knight” → “nefigeos”). “(\w+)s\b” → “$1oo” (e.g., “knights” → “nefigeoo”). “(\w+)ies\b” → “$1iioo” (e.g., “enemies” → “enemiioo”). “(\w+)ly\b” → “$1e” (e.g., “quickly” → “rapide”). “my (\w+)\b” → “$1yn” (e.g., “my name” → “nomyn”). “(\w+)er\b” → “$1or” (e.g., “worker” → “laboror”). “(\w+)est\b” → “$1issa” (e.g., “fastest” → “rapidissa”). Reverse: “(\w+)a\b” → “$1ing” (e.g., “kursa” → “running”). “(\w+)i\b” → “$1ed” (e.g., “ambuli” → “walked”). “(\w+)o\b” → “will $1” (e.g., “akaloso” → “will hope”). “(\w+)os\b” → “the $1” (e.g., “nefigeos” → “the knight”). “(\w+)oo\b” → “$1s” (e.g., “nefigeoo” → “knights”). “(\w+)iioo\b” → “$1ies” (e.g., “enemiioo” → “enemies”). “(\w+)e\b” → “$1ly” (e.g., “rapide” → “quickly”). “(\w+)yn\b” → “my $1” (e.g., “nomyn” → “my name”). “(\w+)or\b” → “$1er” (e.g., “laboror” → “worker”). “(\w+)issa\b” → “$1est” (e.g., “rapidissa” → “fastest”). These rules, entered in the respective “Regular Expressions” sections, handle verb tenses, noun cases, plurals, and adverbs, with “\b” ensuring word boundaries. Word Order Rules (5 Rules) The “Word Order Rules” section, a new LingoJam feature, uses tags ({{noun}}, {{verb}}, {{adjective}}, {{pronoun}}, {{question}}, {{place}}, {{other}}) on Hallowscript words to reorder sentences for forward translation: “adjective noun” → “noun adjective” (e.g., “good knight” → “nefigeos ba”). “verb noun” → “noun verb” (e.g., “love knight” → “nefigeos amo”). “pronoun verb” → “pronoun verb” (retains order, e.g., “I love” → “ego amoa”). “question noun” → “question noun” (retains order, e.g., “what knight” → “kwe nefige”). “adjective verb” → “verb adjective” (e.g., “good love” → “amoa ba”). These rules, entered in the “Word Order Rules” section, apply last to enforce Hallowscript’s topic-comment structure (e.g., “Ego ba a” for “I am good”).

When to use it

  • YouTube and TikTok lore content. Caption lore videos, theory threads, and analysis content in the source register.
  • Tabletop RPG sessions. Add immersive language to in-game dialogue, notes, and player handouts.
  • Fan fiction and worldbuilding. Match the canonical register of the source media for fan-written stories.
  • Cosplay and convention skits. Draft authentic-feeling in-universe dialogue for performances.

Tips for best results

  • For long passages, translate paragraph by paragraph for the most consistent style.
  • Constructed languages have varying canon documentation; output captures recognizable patterns, not every fandom detail.

Frequently asked questions

Is the Hollowscript free to use?

Yes. The Hollowscript is free, requires no signup, has no daily limit, and adds no watermark. You can use the translations for personal or commercial projects.

Can I use this for fan projects?

Yes — fan fiction, RPG, cosplay, fan art, and personal projects are all valid uses. For commercial fan-adjacent products, check the IP holder fan-content guidelines.

How long can my input be?

Each translation supports up to roughly 4,000 tokens of output, about 2,500-3,000 English words. For longer texts, break the input into paragraphs and translate one at a time.

Is the output canonical?

Constructed languages are rarely documented in full canon. The Hollowscript produces the recognizable patterns documented by the fandom and source material; treat it as the strongest practical approximation rather than a verified canonical resource.

Why do I get slightly different output each time?

The translator runs at a moderate creative temperature, so identical inputs produce varied outputs by design. Run it two or three times and pick the version that fits best.

Embed This Translator On Your Website

Copy and paste this code to add this free translator to your website:

<iframe src="https://funtranslator.com/translators/hollowscript-1" width="100%" height="600" frameborder="0"></iframe>

More Translators

Comments