Reference
Intl Comparison
Why Intl.DateTimeFormat does not cover the full Bangladesh-first story, and where Tarikh fills the gaps.
Start Here
Intl.DateTimeFormat is useful, but it does not cover the full Bangladesh-first date experience.
What Tarikh Adds
Tarikh fills in the parts that matter when users expect Bangla dates, Hijri dates, or mixed-language output.
| Gap | What happens with Intl | What Tarikh adds |
|---|---|---|
| Bangla calendar conversion | Not supported | Gregorian to Bangla calendar conversion |
| Hijri calendar output | Partial support depending on environment | Canonical Hijri conversion with supported time zones |
| Bangla digits in dates | Partial or inconsistent | Localized digits in formatted output |
| Hybrid formatting | Not supported | Mixed English and Bangla output in one string |
| Bangla calendar parsing | Not supported | Bangla date strings can be parsed back to Date |
| Relative time in Bangla | Not supported | Localized relative time helpers |
| SSR-safe React output | N/A | Semantic <time> components |
Practical Impact
- Bangladeshi apps need month names like
বৈশাখandচৈত্র, not only Gregorian month names - User-facing strings often mix English and Bangla in the same sentence
- Calendar conversion and date parsing need to round-trip cleanly on both client and server
- React output should stay semantic and cheap to render
Tarikh still uses the platform where it helps, but it fills the gaps that matter for Bangla-first applications.