Revision history [back]

The locale is set to POSIX in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-* language, then all accented characters are incorrect within tmux. I imagine there could be other issues.

However, I'm not sure about the benefits of POSIX, and I guess there are reasons for it to be default. What am I missing? Is it safe to manually change the locale on the Jolla using the following?

LANG="en_GB.UTF-8"
export LANG

If so, is there a reason why changing the language in the SFOS UI doesn't automatically change the locale to its UTF-8 equivalent (specific needs could be changed in command line still).

The locale is set to POSIX in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-* UTF-8 language, then all accented characters are incorrect within tmux. I imagine there could be other issues.

However, I'm not sure about the benefits of POSIX, and I guess there are reasons for it to be default. What am I missing? Is it safe to manually change the locale on the Jolla using the following?

LANG="en_GB.UTF-8"
export LANG

If so, is there a reason why changing the language in the SFOS UI doesn't automatically change the locale to its UTF-8 equivalent (specific needs could be changed in command line still).

The locale is set to POSIX in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-8 language, then all accented characters are incorrect within tmux. I imagine there could be other issues.

However, I'm not sure about the benefits of POSIX, and I guess there are reasons for it to be default. What am I missing? Is it safe to manually change the locale on the Jolla using the following?

LANG="en_GB.UTF-8"
export LANG

If so, is there a reason why changing the language in the SFOS UI doesn't automatically change the locale to its UTF-8 equivalent (specific needs could be changed in command line still).still)?

[Edit] According to RFC documents, *-UTF-8 is the standard. In most cases, using *.utf8 should be equally recognized, but my humble tests show that there are some apps that expect only the standard format and will fail to display any UTF-8 characters if the locale is set using the *-utf8 formatting.

The locale is set to POSIX xx_XX.utf8 in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-8 language, language with this specific extension formatting, then all accented characters are incorrect within tmux. I imagine there could be other issues.

However, I'm not sure about the benefits of POSIX, and I guess there are reasons for it to be default. What am I missing? Is it safe to Setting my language in my environment manually change the locale on the Jolla using the following?as follows solves it:

LANG="en_GB.UTF-8"
export LANG

If so, is Is there a reason why changing the language in the SFOS UI doesn't automatically change the locale to its UTF-8 equivalent (specific needs could be changed in command line still)?sets it to xx_XX.utf8? This format should work in most cases on Linux, but there are some issues that the standard format should prevent.

[Edit] According to RFC documents, *-UTF-8 is the standard. In most cases, using *.utf8 should be equally recognized, but my humble tests show that there are some apps that expect only the standard format and will fail to display any UTF-8 characters if the locale is set using the *-utf8 formatting. formatting.

The locale is set to xx_XX.utf8 in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-8 language with this specific extension formatting, then all accented characters are incorrect within tmux. I imagine there could be other issues.

Setting my language in my environment manually as follows solves it:

LANG="en_GB.UTF-8"
export LANG

Is there a reason why changing the language in the SFOS UI sets it to xx_XX.utf8? This format should work in most cases on Linux, but there are some issues that the standard format should prevent.

[Edit] According to RFC documents, *-UTF-8 is the standard. In most cases, using *.utf8 should be equally recognized, but my humble tests show that there are some apps that expect only the standard format and will fail to display any UTF-8 characters if the locale is set using the *-utf8 formatting.

The locale is set to xx_XX.utf8 in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-8 language with this specific extension formatting, then all accented characters are incorrect within tmux. I imagine there could be other issues. I found another app (currently being ported to SFOS) that also works fine when the locale is set using the RFC standard, but not otherwise.

Setting my language in my environment manually as follows solves it:

LANG="en_GB.UTF-8"
export LANG

Is there a reason why changing the language in the SFOS UI sets it to xx_XX.utf8? This format should work in most cases on Linux, but there are some issues that the standard format should prevent.

[Edit] According to RFC documents, *-UTF-8 is the standard. In most cases, using *.utf8 should be equally recognized, but my humble tests show suggest that there are some apps that expect only the standard format and will fail to display any UTF-8 characters if the locale is set using the *-utf8 formatting.

The locale is set to xx_XX.utf8 in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-8 language with this specific extension formatting, then all accented characters are incorrect within tmux. I imagine there could be other issues. I found another app (currently being ported to SFOS) that also works fine when the locale is set using the RFC standard, but not otherwise.

Setting my language in my environment manually as follows solves it:

LANG="en_GB.UTF-8"
export LANG

Is there a reason why changing the language in the SFOS UI sets it to xx_XX.utf8? This format should work in most cases on Linux, but there are some issues that the standard format should prevent.

[Edit] According to RFC documents, *-UTF-8 is the standard. In most cases, using *.utf8 should be equally recognized, but my humble tests suggest that there are some apps that expect only the standard format and will fail to display any UTF-8 characters if the locale is set using the *-utf8 formatting.

The locale is set to xx_XX.utf8 in Sailfish. This causes issues when using things like tmux, because tmux guesses from the environment if it should enable UTF-8 support or not. When the locale is not set to a UTF-8 language with this specific extension formatting, then all accented characters are incorrect within tmux. I imagine there could be other issues. I found another app (currently being ported to SFOS) that also works fine when the locale is set using the RFC standard, but not otherwise.issue in some applications.

Setting my language in my environment manually as follows solves it:it because it overrides the default locale name:

LANG="en_GB.UTF-8"
export LANG

Is there a reason why changing the language in the SFOS UI sets it to xx_XX.utf8? This format should work in most cases on Linux, but there are some issues that the standard format should prevent.