Ref T9285, add Korean locales per epriestley.
Korean have no PLURAL/GENDER normally, but plural left since
a little strings may need some plural expressions.
Details
- Reviewers
epriestley - Group Reviewers
Blessed Reviewers - Maniphest Tasks
- T9285: Custom locale may fail when pht a sentence with variants
- Commits
- rPHUf923eff2dec1: Add Korean locales
- Have a Korean translation file.
- Go settings, no Korean in language selection
- Apply Patch
- arc liberate, and voila! Now Korean (Republic of Korea) is there
Diff Detail
- Repository
- rPHU libphutil
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Thanks!
I don't speak Korean so it's difficult for me to be confident that this ruleset is correct, but it seems right from other sources I can find discussing Korean localization, like this one:
Don’t fret over plurals in your Korean translation. If you change the source from singular to plural, go ahead and send it over to your Korean translation team to make sure, but don’t be surprised if no change is required.
It looks like Korean does have honorifics, but presumably it's common for software to use some consistent honorific level everywhere? I can't think of any cases where it would be appropriate to change honorifics based on the subject of a sentence.
Well yes, Korean has plural forms in grammar (~들), but when you count something, plural is not used. (So, "7 differential revisions" is just 7 differential revision (tr: 디퍼런셜 리비전 7개) (in Korean grammar terms) when translated.) (See Wiktionary)
So maybe is it better to only use singular?
For honorifics, translations of software is usually honorific because it would make people feel "this software is commanding me!" or such emotional issues. Windows, MediaWiki, almost all programs I saw translated into Korean uses honorific forms. Simply, only think of honorifics, and you'll be fine.