Bulgarian to Klingon pIqaD: translation comes before the change of alphabet
pIqaD changes the writing system, not the source language
The pIqaD option requests Klingon written in the character system commonly associated with the fictional culture. It is not a decorative font for Bulgarian words. A Bulgarian phrase must first acquire Klingon vocabulary and grammar; representing that result in pIqaD is a separate writing step. Microsoft lists Latin-script Klingon and pIqaD Klingon as distinct translation options.
For example, Bulgarian кораб means “ship.” The Klingon word is Duj in the standard romanization. Putting Bulgarian Cyrillic sounds into unfamiliar glyphs would retain the Bulgarian word rather than translate it. Similarly, голям кораб means “a big ship,” whose Klingon reading aid is Duj tIn. The target noun phrase orders the description differently from the Bulgarian original before any pIqaD characters are displayed.
Romanized letter groups are not separate pIqaD slots
The Klingon Language Institute explains that combinations such as tlh and ng represent single Klingon sounds or letters in the conventional romanization. A conversion that assigns one pIqaD character to each individual Latin character would therefore segment the writing incorrectly. The three Roman characters in tlh should not automatically be interpreted as three independent letters of the target alphabet.
This differs from treating a Bulgarian multi-letter sequence as a simple list of Cyrillic letters for transliteration. The input alphabet and the Klingon romanization organize their sounds differently. Even when a romanized result looks familiar enough to copy, converting it accurately requires its Klingon letter boundaries rather than Bulgarian pronunciation habits.
Capitalization and the apostrophe carry contrasts
Klingon romanization distinguishes q from Q as different sounds. Its apostrophe is also a full letter, representing a consonant. These distinctions need to survive whatever pIqaD representation is used. They cannot be removed as cosmetic capitalization or quotation punctuation before the conversion.
Bulgarian sentence capitalization does not normally turn a lowercase consonant into a separate phoneme, and an apostrophe is not used as a consonant letter in its ordinary alphabet. Those source-language expectations are consequently unsafe guides to interpreting a Klingon reading aid. A conversion that lowercases everything first can lose information even though the resulting glyph string still looks convincingly Klingon.
The script has conventions, rather than Bulgarian punctuation rules
KLI distinguishes Okrand’s official romanization from the character mapping used by its members for pIqaD. It describes a convention of horizontal left-to-right writing, often with each sentence on its own centered line. Its discussion also notes the absence of punctuation characters in the displayed character set. These are specific writing-system facts, not evidence that Klingon lacks sentence structure.
For a Bulgarian quotation or short caption, the sentence divisions should therefore remain intelligible even if ordinary Bulgarian comma and full-stop conventions are not reproduced as matching pIqaD glyphs. The visual representation also depends on available character and font support. A blank box indicates a display problem; an attractive glyph does not establish correct vocabulary or grammar. Keeping the romanized reading alongside a pIqaD design, when the format permits it, preserves an inspectable record of the actual Klingon words rather than only their visual appearance.
Language references