Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setting locale from terminal does not clear the warning of the package manager #1216

Closed
flip111 opened this issue Feb 14, 2017 · 8 comments
Closed

Comments

@flip111
Copy link

flip111 commented Feb 14, 2017

When starting sublime text like

[ myPC: ~/ ] 
bash> LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /home/flip111/programs/sublime_text_3/sublime_text

I still get

image

System:
CentOS 7.3.1611
terminator 0.98
bash 4.2.46
kernel: 3.10.0-514.6.1.el7.x86_64

@wbond
Copy link
Owner

wbond commented Feb 14, 2017

Do you have en_US.UTF-8 installed on your machine?

@flip111
Copy link
Author

flip111 commented Feb 14, 2017

checked with locale -a which lists en_US.utf8

@wbond
Copy link
Owner

wbond commented Feb 15, 2017

I would try that locale in the command instead and see if it works for you.

@flip111
Copy link
Author

flip111 commented Feb 15, 2017

I tried now LANG=en_US.utf8 LC_CTYPE=en_US.utf8 /home/flip111/programs/sublime_text_3/sublime_text and i still get the same dialog

@wbond
Copy link
Owner

wbond commented Feb 15, 2017

I'm not really use why your machine won't properly handle UTF-8 in filenames.

You can play around with different locales until you can get the following code to run in your Sublime Text Console without an error:

os.path.join(sublime.packages_path(), u"fran\u00e7ais")

@flip111
Copy link
Author

flip111 commented Feb 15, 2017

with play around, do you mean try all possible combinations? There are like 15 different locale settings and lots and lots of different locales that can be used. Do you have any specific suggestions of this direction?

@wbond
Copy link
Owner

wbond commented Feb 15, 2017

Not really – this error indicates your machine can't properly handle UTF-8 filenames and is instead using a single-byte character encoding. There are packages and files in packages that use non-ASCII characters. If this test doesn't pass, then your machine could fail in all sorts of different places.

Honestly, as long as you are using a locale that supports UTF-8, you should be good.

@deathaxe
Copy link
Collaborator

Nothing we can do on our end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants