Philippine Language and Region Settings

[anobongjimwel]

Hi, I would like to request inclusion of the following please:

1. Philippine English / English (Philippines)
2. Filipino (Pilipinas) -> If I can assist on making this possible like having me a translation file or what, I can.
3. Philippine Peso (₱) for Philippine Currency.
4. Custom Currency (would be better, should other currencies are not indicated yet)

Thank you.

[ulsklyc]

Shipped in v1.78.0. Points 1 to 3 are all in:

1. English (Philippines) and Filipino (Pilipinas) are both selectable under Settings → Appearance → Region. They set the Philippine date convention (MM/DD/YYYY) and a 12-hour clock, taken from the region's own CLDR data rather than guessed.
2. Filipino is the 24th interface language, selectable in the language picker. All 3581 strings are translated, and so are the web installer and the command-line installer.
3. PHP (Philippine peso) is now a selectable currency, in the household setting as well as in Subscriptions and Split Expenses. Amounts render as ₱1,234.50.

The same release added every currency in use across the Americas, so the list went from 29 to 54 codes and the region list from 30 to 64.

A note on the Filipino translation: I wrote it, and I am not a native speaker. If anything reads awkwardly, a PR against public/locales/fil.json or just a list of corrections here is very welcome. Your offer to help is appreciated and still stands. One thing worth flagging, since it looks like a bug otherwise: CLDR puts 2, 3, 5, 10 and 11 in the one plural category for Filipino and only 4, 6 and 9 in other. A wording that differs between the two would therefore switch back and forth for no visible reason, so every plural variant in fil.json is deliberately worded identically. The na/ng ligature after a numeral is dropped for the same reason: it follows the spoken number (isa → isang, apat → apat na) and cannot be expressed in a template.

On point 4, custom currencies: not implemented. With 54 codes covering the Americas, Europe, Asia and the Middle East the gap should be much smaller now, but if a currency you need is still missing, open an issue naming the ISO 4217 code and it is a small change. A free-text currency field is a bigger piece of work, since the code is validated server-side in four places and an unknown code would have to fall back cleanly in every amount formatter.

Closing this as resolved. Thanks for the clear, well-structured request.

[ulsklyc]

All three of the concrete items are in v1.78.0.

• English (Philippines) and Filipino (Philippines) are both available under Settings → Appearance → Region, each defaulting to MM/DD/YYYY, a 12-hour clock and the peso.
• PHP is selectable as the household currency and in Subscriptions and Split Expenses alike. It arrived together with 24 other currencies covering the Americas, bringing the list from 29 to 54.
• Filipino is now the 24th interface language, translated across the app, the web installer and the command-line installer.

On your offer to help with the translation

The translation is already in, so there is nothing blocking. But you offered as a speaker of the language, and that is worth more at this point than it would have been before: the file carries 3,581 strings, and the ones that read fine to a non-speaker are exactly the ones nobody can check. If you run it and something sounds wrong, stiff, or like it was translated word for word, please say so. Corrections to individual strings are easy to land.

A few terms were deliberately left in English because they seemed to be the words actually used rather than their Tagalog equivalents: Error, Changelog, Link, Tag, Board. If any of those should be translated after all, that is exactly the kind of note worth having.

One thing you asked for that did not make it

A free-text custom currency field is still not there. Real currency codes let the formatting rules, the symbol and its placement come from the platform for every locale; a hand-typed code would have to carry all of that itself. With the list now at 54 the gap it was meant to cover is much smaller, so the practical route stays the same: name a missing currency and it goes in.

Worth recording: fil-PH also turned up a bug. The server checked language tags for a two-letter code, so any three-letter one was rejected as invalid and never reached the number and currency formatting. That check existed in five places and was wrong in all five. Your request found it.