Fusion locales only when getting String

[Shallowmallow]

I had added an en.properties but somehow when I was under en_US locale
I didn't see the "translated version" which is in lower case

The reason was that only once you parsed en_US strings, it would add the "parent" strings. But my last parsed file one was as an "en" one and not an "en_US" one, so en strings were not added to en_US ones.

The solution I thought was to "fusion" en and en_US strings only in getStrings. Not only does it fix the bug but it saves space, as you don't have duplicate strings in en and en_US

[ianharrigan]

Its weird, i thought this already happened somehow, like if you it couldnt find a string in en_US it would look in en or something? Maybe i misremembered?

Also, can we call it "mergedLocale" or something... "fusioned" sounds odd

[Shallowmallow]

Renamed.

Maybe i misremembered?

Looking at the code, It happens when you don't have the same language, if no chinese, it will look for en locale. Maybe you're thinking of this ?