Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GetText::Tools::MsgInit limiting locale format due to Locale library #51

Open
mcfilib opened this issue Jan 5, 2017 · 1 comment
Open

Comments

@mcfilib
Copy link

mcfilib commented Jan 5, 2017

According to the gettext docs, a locale may include additional information after an @ symbol:

Some locale names use ll_CC.@variant instead of ll_CC. The @variant can denote any kind of characteristics that is not already implied by the language ll and the country CC. It can denote a particular monetary unit. For example, on glibc systems, de_DE@euro denotes the locale that uses the Euro currency, in contrast to the older locale de_DE which implies the use of the currency before 2002. It can also denote a dialect of the language, or the script used to write text (for example, ‘sr_RS@latin’ uses the Latin script, whereas ‘sr_RS’ uses the Cyrillic script to write Serbian), or the orthography rules, or similar.

The same functionality is supported by other translation tooling e.g. weblate, which seems to at least suggest it's not completely unheard of.

At work, we're using gettext in our application and have recently had to add more fine-grained locales to our product, e.g. en_GB@education, in order to specialise for a particular markets but we've hit an impasse with ruby-gettext via its use of the locale library because it effectively throws away any information after the secondary code.

Is there any reason why this can't be supported? Would you consider a patch for this?

@kou
Copy link
Member

kou commented Jan 6, 2017

Is there any reason why this can't be supported?

Because we didn't have use cases for the case.

Would you consider a patch for this?

Sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants