locked
Localization Issue - Locale specification is too restrictive RRS feed

  • Question

  • I have a resource file client.lang-fr-FR.resjson and I have set the language to 'French (France)' and the app works fine. But if I change the language to 'French (Belgium)' then the app doesn't localize any more. Is this the normal behavior? I would expect that LS would be smart enough to pick up fr-FR resource file instead, otherwise one has to have a resource file for Belgium, one for Canada, one for Caribbean, one for Monaco, one for Switzerland and one for Luxemburg as they all have French language! Or am I missing something here?

    Frank

    Wednesday, September 18, 2013 4:00 PM

Answers

  • fr-FR implies specific sub-culture/locale. Is it possible in LS to use neutral culture by dropping the -FR part?
    • Marked as answer by TChiang Wednesday, September 18, 2013 7:12 PM
    Wednesday, September 18, 2013 5:32 PM

All replies

  • fr-FR implies specific sub-culture/locale. Is it possible in LS to use neutral culture by dropping the -FR part?
    • Marked as answer by TChiang Wednesday, September 18, 2013 7:12 PM
    Wednesday, September 18, 2013 5:32 PM
  • Yes,

    That's how it actually works. Thanks. I was following the walk-through and this part is not explicitly explained.


    Frank

    Wednesday, September 18, 2013 7:12 PM