Baltimore Type Foundry
Open-knowledge reference entry
There have been two, unrelated firms using the name Baltimore Type Foundry.
First Baltimore Type Foundry
The first Baltimore Type Foundry, considered to be the second oldest type foundry in the United States, was founded around 1799 by Samuel Sower and was continued by his son-in-law, Richard Spaulding. In 1832, the business was sold to Fielding Lucas Jr., and it remained in the Lucas family until 1879 when it was sold to Henry Lafayette Pelouze, owner of the Richmond Type Foundry, and it operated as a branch of that foundry until 1883. It was subsequently purchased by Charles J. Carey & Co. and operated independently until it was merged into American Type Founders at its formation in 1892. A year after A. P. Luse died in 1891, the foundry became one of the twenty-three foundries that merged to become American Type Founders.
Typefaces
These foundry types were originally cast by the first Baltimore Type Foundry:
Baltotype
The second Baltimore Type & Composition Co., better known as Baltotype, or just Balto, was founded in the early twentieth century by the Czarnowski family and remained in business until at least 1978. It was a "secondary foundry", mostly casting from matrixes made by Lanston Monotype Company or British Monotype, though they also cut a few faces of their own. A subsidiary, Baltimore Matrix, made these available to other secondary foundries in various cities.
Typefaces
These foundry types were cast by the first Baltimore Type Foundry.
“Baltimore Type Foundry” enters the record as open-knowledge reference entry. Crown Archives preserves that source wording while asking what Baltimore, Type and Foundry can confirm, complicate or overturn.
Why this record matters
“Baltimore Type Foundry” is worth following because a concise public description often conceals a longer documentary argument. Here, Baltimore, Type and Foundry provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jun 14, 2026. The linked authority identifier is Q96373030. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1799, 1832, 1879 and 1883.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Baltimore Type Foundry”, its source revision and the description used here.
- Expand the search: follow Baltimore Type Foundry primary sources, Baltimore Type Foundry archive and Baltimore research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Baltimore Type Foundry”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Baltimore Type Foundry” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.