Add Vietnamese translation and VND currency support

[duongcamcute]

Hi there,

First of all, thank you for creating such an amazing application!

I have completed the Vietnamese translation for the app based on the en.json file. I have attached the translated file below. I would be very grateful if you could merge this into the project to support Vietnamese users.

Additionally, could you please add support for VND (Vietnamese Đồng) as a currency option in the app?

Thank you for your time and hard work!

---

Note for the author: Please find the attached translated file below:
[Drag and drop your en.json file here]
vi (2).json

[ulsklyc]

Thank you so much for contributing this — and for the kind words! 🙏

I have merged your translation into the project. A few missing keys (WebDAV backup, crop dialog, sidebar collapse, password toggle — all added after your original submission) were filled in to bring the file to full parity with the reference locale.

Vietnamese is now available in:

• the app (Settings → Language → Tiếng Việt)
• the web installer wizard
• the CLI installer (bash install.sh --lang vi)

VND (Vietnamese Đồng) has also been added to the currency picker in Settings → Budget.

Everything is tracked in PR #310 and will ship with the next release. Thanks again!

[duongcamcute]

Thank you so much for your Update.
About VND. When I select VND, the notice: Ungültige Währung. Erlaubt: AED, AUD, BRL, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HUF, INR, JPY, KZT, NOK, PLN, RUB, SAR, SEK, TRY, UAH, USD

[moonlight8978]

@ulsklyc Hi, thanks for your awesome work!

the currency has been deleted in #340, but was never added back. could you please re-add support for VND currency?

c106800#diff-d056d9594d8efe91874bce993cbbe3380c9a32f6eff4c9fb4c159aa9cb1298a7L16

c106800#diff-043b75ca233d66a006bd339f17da78b592c6e590f4afe7ba8dc9ac85ce70f64bR4-R7

[ulsklyc]

@moonlight8978 You are right, and thank you for the precise pointer - the two commit links made this a five-minute diagnosis instead of an afternoon.

What happened. VND was added here in June, as this thread says. In #340 the currency list was unified: it had existed as four literal copies (household settings, subscriptions, the preferences route, shared expenses), held together by two guards that compared the four source files by regex. Consolidating them into one shared list was the right move - it is why adding a currency is one line today. But the merge lost VND on the way, and nothing noticed, because the guards that survived compare the list against itself.

The tell was sitting in the code the whole time. server/services/split-expenses.js still listed VND: 0 among the currencies that carry no decimal places. So the app knew how to calculate in dong and refused to let anyone choose it. Meanwhile vi.json kept shipping - a Vietnamese household could run the entire app in its own language and not pick its own currency. That went two months without a report, which is the part that bothers me more than the missing line.

Fixed, and the fix is wider than the report. VND is back in the shared list. Checking why nothing caught it turned up a second gap: of the 24 shipped languages, three had no region preset at all - Greek, Hungarian and Vietnamese. A region preset is the thing that sets currency, date format and time format together, so those three languages always landed on "Custom" and made people guess all three values one by one. Hungarian is the sharpest case, because HUF was in the currency list the entire time and simply had nowhere to be selected from.

All three now exist, with the values taken from each locale's CLDR default rather than guessed:

Region	Currency	Date	Time
el-GR	EUR	DD/MM/YYYY	12h
hu-HU	HUF	YYYY.MM.DD	24h
vi-VN	VND	DD/MM/YYYY	24h

Greek surprised me - CLDR has it on a 12-hour clock (2:30 μ.μ.) while the countries around it write 24h. Hungarian writes the year first and is the first region in the app to use that format.

And a guard, so the next one is caught by a test rather than by a user. It is a rule over the codebase, not a list of files: every shipped locale must have at least one region preset. Together with the existing check - every preset must name a selectable currency - that closes the loop this fell through. A language with no region could not demand a currency, so nobody noticed its currency was gone. I broke both directions to confirm they actually fail: remove the Greek preset and it reports el; remove VND again and it reports vi-VN: invalid currency VND.

Not released yet - it will be in the next release, and I will not close this thread until it is out. Thanks again for coming back to a thread that had been closed for two months; that is exactly where these get lost.

[ulsklyc]

Released in v2.59.0. @moonlight8978 - VND is back in the currency picker, and vi-VN now exists as a region preset (VND · DD/MM/YYYY · 24h), so a Vietnamese household no longer has to configure currency, date and time individually.

@duongcamcute - your original report from June is finally correct again, and I am sorry it took this long. Your translation kept shipping the whole time; it was the currency that quietly fell out.

Greek and Hungarian were in the same state and got their presets in the same release. The guard that would have caught this - every shipped language must have at least one region - is now in the test suite.

This thread has been closed since July; I am leaving it that way rather than reopening it just to close it again. If anything about the Vietnamese setup still looks wrong after updating, please open a new discussion and I will pick it up there.