Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feat]: Vietnamese translation

Closed
  • Is something wrong?
#1,313 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@HongTin2104 is already working on this.

Since Oct 28, 2026.

  • #1329 by @HongTin2104 — merged

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
internationalization

Research direction

Start with packages/web-ui/src/i18n/locales/en.json, then check config.ts, localeBackend.ts, language.ts, registryLocale.ts, and the tests in packages/web-ui/tests/i18n/. Add the Vietnamese locale and wire it into language selection and detection; confirm the locale has every English key, placeholders and plural forms work, and the relevant i18n tests pass.

Written by the indexing model from the issue text.

Description

feature request good first issue
Prerequisites
  • I have written a descriptive issue title
  • I have searched existing issues to ensure the feature has not already been requested
🚀 Feature Proposal

Tabularis is available in 11 languages. I'd like to add Vietnamese (vi, shown as Tiếng Việt in the language picker).

Motivation

Vietnam has a large and fast-growing developer community, and many developers there prefer tools in their own language. A full Vietnamese translation makes Tabularis much more approachable for them.

Example

In Settings → General → Language, Tiếng Việt is listed. Selecting it switches the whole interface to Vietnamese, and a system language of vi or vi-VN selects it automatically on first launch.

Acceptance criteria
  • packages/web-ui/src/i18n/locales/vi.json contains every key of en.json.
  • Vietnamese is selectable in the language picker as Tiếng Việt.
  • vi and vi-VN system languages are detected automatically.
  • Placeholders and plural forms work in the translated strings.
  • Existing i18n tests pass and cover the new language where relevant.
Where to start
  • packages/web-ui/src/i18n/locales/: copy en.json to the new file and translate the values (never the keys).
  • packages/web-ui/src/i18n/config.ts: add the language to SUPPORTED_LANGUAGES.
  • packages/web-ui/src/i18n/localeBackend.ts: register the lazy import of the new file.
  • packages/web-ui/src/i18n/language.ts and registryLocale.ts: check how browser languages and registry locales are mapped.
  • packages/web-ui/tests/i18n/: existing tests for language detection and the locale backend.
Contributor notes
  • Follow the repo rules in .rules/ (TypeScript, testing).
  • Please translate by hand or carefully review any machine translation: technical terms (query, schema, primary key, ...) should read the way local developers actually say them.
  • Keep placeholders such as {{count}} and {{table}} unchanged, and keep plural suffixes (_one, _other) consistent with the language rules.
  • Run pnpm test and pnpm lint before opening the PR.
  • Questions? Ask here or on Discord.
Dominant language
TypeScript
Stars
5.1k
Forks
335
Avg merge
1d 6h
Merged PRs (30d)
260

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TabularisDB/tabularis

All issues in TabularisDB/tabularis

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.