The original project separates scripts into locally named fonts
Ek Type’s original repository describes a single-weight, heavy spurless display project with ten script-specific fonts, each paired with Latin coverage. Its mapping includes Baloo for Devanagari, Bhai for Gujarati, Bhaijaan for Urdu, Bhaina for Odia, Chettan for Malayalam, Da for Bengali, Paaji for Gurmukhi, Tamma for Kannada, Tammudu for Telugu and Thambi for Tamil. These names identify separate script packages rather than ten interchangeable weight names.
The successor expands the design but retains local identities
The Baloo 2 repository describes additional glyphs, engineering improvements and five weights from Regular through ExtraBold. That README lists nine Indic families plus Latin, Latin Extended and Vietnamese coverage within each. Keep this repository’s scope separate from the original ten-script list; do not infer that the unqualified family name Baloo 2 contains every script. The linked specimen covers the specifically named Devanagari family.
Plan a multilingual heading using actual translations
List the required scripts before selecting fonts. Prepare the full translated headings, dates and instructions rather than judging all languages from a Latin sample. Compare apparent size and the space required above and below lines, then give each translation sufficient room. Keep reading order clear and choose emphasis that performs the same role across languages. A visual match should support the content without forcing different writing systems into identical shapes.
Preserve the version and local family during handoff
The Baloo 2 specimen is a named successor resource; Fredoka and Source Sans 3 are independent comparisons. Record the project version, exact local family and selected weight for each part of an actual multilingual layout. A missing-script fallback can look plausible while changing the intended design, so the production specification should identify each writing system explicitly rather than relying on the short label Baloo alone.
Your questions, answered.
Does Baloo 2 alone contain every script in the project?
No. The project documentation organizes script-specific families under local names.
Should an original single-weight file be treated as the complete successor?
No. Preserve the project version and selected files; a broader successor style range does not change what an older package contains.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.