Make sure languages "with two parts" are handled correctly

Question

Make sure languages "with two parts" are handled correctly

elegaanz opened this issue 5 years ago · comments

For instance en-US or pt-BR

trinity-1686a · Answer 1 · Mon May 13 2019 03:22:43 GMT+0800 (China Standard Time)

I think they should be because of https://github.com/Plume-org/rocket_i18n/blob/master/src/with_rocket.rs#L24 and https://github.com/Plume-org/rocket_i18n/blob/master/src/with_actix.rs#L50 ? Or did you mean somewhere else?

Ana Gelez · Answer 2 · Mon May 13 2019 03:27:17 GMT+0800 (China Standard Time)

Yes, but my concern was more about making sure they are working with gettext-macros too, and that the two-parts version is correctly used when needed if the one-part version is also available (not sure if I'm clear, sorry).

Vincent Breitmoser · Answer 3 · Thu Nov 14 2019 20:46:31 GMT+0800 (China Standard Time)

If I'm reading that code right, the locale part (so -Lo out of ln-Lo) is simply ignored?

I believe it is very important to support this because of the Chinese language. The locales "Chinese (Traditional)" and "Chinese (Simplified)" are quite different, but share the zh language prefix.