Agree to what Kasun said. Further can we do this case insensitively.
Because from Denuwanthi's data it seems like a case issue to me.
Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Thu, Jan 19, 2017 at 9:57 PM, KasunG Gajasinghe
Refer to [1]
"White space is not allowed within the tag and all tags are case-
insensitive."
[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.10
Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Thu, Jan 19, 2017 at
@KasunG
We intended 'en-US' as the fall-back locale. But we have done a
case-sensitive comparison (basically not doing a case-insensitive
comparison) when figuring-out the correct locale. Will fix this soon.
On Thu, Jan 19, 2017 at 9:57 PM, KasunG Gajasinghe wrote:
>
> Using
Using the Accept-Language header is fine. But if the header is missing,
there should be a fallback mechanism. You should not simply display the
key. For our purposes, we can treat en-US as the fallback language.
On Thu, Jan 19, 2017 at 8:08 PM, Denuwanthi De Silva
wrote:
>
Hi Shan,
Created a git issue [1].
[1]https://github.com/wso2/carbon-uuf/issues/154
Thanks
On Thu, Jan 19, 2017 at 8:07 PM, Shan Mahanama wrote:
> Hi Denuwanthi,
>
> Value of this headers are different in the two browsers. This might be the
> cause. We will look into this.
Hi Denuwanthi,
Value of this headers are different in the two browsers. This might be the
cause. We will look into this. Can you create a git issue for this at [1]?
[1] https://github.com/wso2/carbon-uuf
Thanks,
Shan.
On Thu, Jan 19, 2017 at 7:44 PM, Denuwanthi De Silva
Hi Denuwanthi,
We check the *Accept-Language* header value in the request to identify the
locale. Can you check on Safari whether this header is added correctly and
it's value is correct? It is possible that in Safari browser, this header
is set to some other locale which does not have a
Hi,
The values we have set from en_US.properties file in 'lang' folder, does
not get properly populated when go through the safari browser.
Instead of showing the value it shows the key as shown in the atatched image
Is this a known issue in UUF or do we have a way to prevent this from