Portuguese translation confusion #6561
Comments
|
Yes, +1 for that. We shouldn't need a pt_PT file if we have a pt; The likely_subtags is wrong in this case. |
|
Does the SS4 auth rewrite fix this or is it still relevant? |
|
bump |
|
No it still needs to be fixed. |
tractorcow
pushed a commit
to open-sausages/silverstripe-framework
that referenced
this issue
Nov 27, 2017
|
Fix at #7643 Treating as patch enhancement |
tractorcow
added
change/patch
complexity/low
impact/low
type/enhancement
and removed
affects/v3
labels
|
Not critical an issue necessary to back-port to 3.x; Users can update with config if they wish. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Interface language cannot be set to Portuguese (Portugal) in Security section, Member profile. However all modules have both pt and pt_BR translations.
According to Unicode CLDR, pt is aliased with pt_BR, so it does in
i18n.likely_subtagsconfig.so, to enable pt as pt_PT translation we need to change
i18n.likely_subtagsalias or rename translation files into pt_PT.ymlThe text was updated successfully, but these errors were encountered: