One Ancestor, Five Names: Spelling Drift and the Document Chain in Lithuanian Citizenship Claims

A file that arrives at the Migration Department with every required record present can still stall, and the reason is usually mundane. The man born as *Šmuelis Kaganas* in a Kaunas register appears as *Шмуйло Каган* in a Russian imperial entry, as *Szmul Kagan* on a Polish-era document, as *Samuel Kagan* on a New York naturalisation petition and as *Sam Kane* on his death certificate. Five documents, five names, one person — and no single piece of paper says so. The law is not the obstacle here. The obstacle is that identity in the twentieth century was recorded by clerks working in different alphabets, in different states, with no obligation to be consistent.

This is not a marginal problem affecting unusual families. It is the ordinary condition of Lithuanian ancestry cases, because the population of the interwar Republic was multilingual and much of it emigrated into yet another language. Anyone assembling a claim should expect discrepancies as the default and plan for them from the beginning rather than discovering them at submission.

The good news is that the assessment is not mechanical. Officials examining a claim to Lithuanian citizenship for descendants are accustomed to imperfect twentieth-century paperwork, and the question they ask is whether the documents, read together, identify the same person and the same line to a convincing standard. That is why an explained inconsistency behaves very differently from an unexplained one, and why the practical work of pursuing a Lithuanian passport by descent consists largely of building bridges between records rather than hunting for one perfect document.

Where the drift comes from

Four forces account for nearly all of it.

Alphabet transfers. Records passed between Latin, Cyrillic and Hebrew scripts, sometimes twice. Each transfer is a transliteration decision made by someone with no standard to follow. Lithuanian *Š*, *Č* and *Ž* become *Sh*, *Ch* and *Zh* in English, *Sz*, *Cz* and *Ż* in Polish, and something else again in German. *V* and *W* swap. *C* becomes *Ts*. A single vowel length mark disappears and the surname sorts differently.

Grammatical Lithuanianisation. Lithuanian inflects surnames, and interwar clerks routinely adapted foreign forms: Polish *-owicz* becomes *-avičius*, *-ski* becomes *-skas*, and a bare consonant ending acquires *-as*, *-is* or *-us*. The same family therefore appears under two surnames that look unrelated to a non-Lithuanian eye.

Feminine endings. Lithuanian marks marital status in women's surnames. A daughter of *Petraitis* is *Petraitytė*; married, she becomes *Petraitienė*; her husband's family name generates its own set of forms. A researcher searching only for the masculine form will miss every woman in the line. Modern Lithuanian also permits neutral endings, which adds a further variant.

Emigration renaming. Given names were translated, shortened or replaced on arrival — *Chaimas* to *Hyman*, *Jonas* to *John*, *Zelig* to *Sidney*. Sometimes the change was formal; more often it simply happened, leaving no paper trail at all.

Dates that refuse to agree

Name variance is compounded by date variance, which has its own causes. The Julian calendar remained in official use in the Russian Empire until 1918, producing a difference of twelve or thirteen days between religious and civil entries for the same birth. Jewish records may follow the Hebrew calendar. Ages were reported approximately by people who did not know their exact birth date. Emigrants adjusted years to satisfy military, immigration or employment rules, and those adjusted dates then propagated into every later document.

A useful discipline is to treat each date as a claim with a source attached rather than as a fact. When two records disagree, the earlier record, created closer to the event by an authority with no incentive to be wrong, is usually the stronger one — and saying so explicitly in the submission is better than leaving the reader to guess.

The gaps in the chain

Descent must be shown generation by generation, normally through birth, marriage and death certificates. Chains break for predictable reasons: the record office was destroyed, the birth was registered only religiously, a child was born in wartime displacement, a marriage was never civilly registered, or an adoption intervened. Occasionally the certificate exists but names a parent inconsistently with every other document in the file.

The remedies available are real, and choosing among them is a judgement call:

• Substitute official records — baptismal or synagogue register extracts, census returns, residence registers, school enrolment files, military papers, immigration and naturalisation files — which may prove the same relationship.
• Corrected or amended certificates, obtained from the issuing authority where the underlying register supports the correction.
• Sworn affidavits from family members or from a person with direct knowledge, used to explain a variance rather than to invent a fact. An affidavit standing alone rarely persuades; an affidavit corroborated by two independent records often does.
• Name-change or naturalisation documentation from the destination country, which frequently states the former name expressly and is therefore the cleanest possible bridge.
• A court application in Lithuania to establish a fact of legal significance, the formal route where the administrative options are exhausted. It is slower and more expensive, and it is the right answer when the alternative is abandoning the claim.

Getting foreign documents into acceptable form

Records issued abroad generally need legalisation and translation before a Lithuanian authority will act on them. For states party to the Hague Convention that means an apostille from the competent authority of the issuing country; for other states, consular legalisation. Translations into Lithuanian must be done properly, with the translator's certification, and the transliteration choices in the translation should be consistent across the whole file — a translator who renders the same surname two ways across two documents creates a new discrepancy where none existed.

Two points are easy to overlook. Some documents have practical validity windows for official use, so ordering them too early can mean ordering them twice. And Lithuania's rules on how names are written in its own documents have been liberalised in recent years, which affects the form your name may ultimately take on a Lithuanian passport; the current position is worth confirming rather than assuming.

Frequently asked questions

Will a spelling mismatch cause a refusal? Rarely on its own. Unexplained mismatches invite a request for further evidence, which costs months. Address every variance in the submission itself.

How many documents do I need to bridge one gap? There is no fixed number. Two or three independent sources that converge on the same conclusion are far more persuasive than one strong-sounding assertion.

Can I fix a foreign certificate that has my grandfather's name wrong? Sometimes, through the issuing authority. Where you cannot, do not alter the record — explain it and corroborate it.

Does an affidavit from a relative count? As supporting evidence, yes. As the sole proof of a link, generally no.

Should I translate everything? Translate what is submitted, and keep originals available. Over-translating peripheral material adds cost without adding weight.

A practical order of work

Build the chain on paper before you build the application. List every generation, every document that covers it, and every point at which a name, date or place differs from the record before it. What remains after that exercise is a short, specific list of gaps — and each gap has a known remedy. Files fail not because the family history is weak, but because nobody wrote down where the seams were and explained them.