-
Notifications
You must be signed in to change notification settings - Fork 279
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
Chinese language support! #294
Comments
Oh yeah there might not be utf8 support. Can you try using python3?
From: Younger <[email protected]>
Reply-To: facebook/PathPicker <[email protected]>
Date: Wednesday, November 21, 2018 at 7:31 PM
To: facebook/PathPicker <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [facebook/PathPicker] Chinese language support! (#294)
Hey,
I'm Chinese, and my system language of CentOS is Chinese yet. I use fpp with git status, but all of Chinese character are become messy code, it's very unfriendly. Is there has any solution to solve it? THX very much~
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#294>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABFRn_C2UD95O01qHrbF0sgOv0huQiSDks5uxgxhgaJpZM4Yuj42>.
|
Oh, thanks a lot. I modify the fpp scripts that 'python' to 'python36', then this problem has disappeared. |
Still NOT work with mkdir fpp-chinese-test
cd fpp-chinese-test
echo "test" > 测试.txt
git init
git status | fpp =>
Note: fpp v0.9.2 Please reopen this issue. |
It's actually a problem of using regex to match a filename that includes unicode. I see most regex are PathPicker/src/pathpicker/parse.py Line 32 in e0d5cfc
In Python3
if change the regex to Additionally, there is a filename-regex package in javascript. It uses more looser regex.
|
Hey,
I'm Chinese, and my system language of CentOS is Chinese yet. I use fpp with
git status
, but all of Chinese character are become messy code, it's very unfriendly. Is there has any solution to solve it? THX very much~The text was updated successfully, but these errors were encountered: