-
Notifications
You must be signed in to change notification settings - Fork 82
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
Incorrect encoding (possiblely due to #505) #547
Comments
@fengzyf any ideas? |
The latest commit 3d1f44d uses Win32:: GetACP() to retrieve the code page of the Windows system, thereby obtaining the system default encoding. Users do not need to specify the encoding. |
Implemented as of https://github.com/cmhughes/latexindent.pl/releases/tag/V3.24.2, thanks again to @fengzyf |
emmm It seems that there is still some bug... console output (no log file is generated): (console is encoded with cp936, if this matters.)
When path does not contain Chinese, it works. The file context is already encoded in UTF-8. Possible bug analysis?
|
@qiancy98 It works fine on my computer, please check whether the read permission of the file |
Sorry, it seems that this is not problem of In I will try to ask VS Code for this problem. Thank you very much. |
Please provide the following when posting an issue:
original .tex code
Please paste your .tex code here. Please note in answering your issue, I may add the code you provide to the test-cases directory. Please detail explicitly if you would prefer me not to do so..
yaml settings
encoding: GB2312
paths:
actual/given output
file
D:\Google 锟狡讹拷硬锟斤拷\锟斤拷锟斤拷师锟斤拷锟斤拷锟斤拷\Hydra_QCY - partial (Edition 0821)\hydra-2 240525
desired or expected output
The file located in
D:\Google 云端硬盘\吴老师的论文\Hydra_QCY - partial (Edition 0821)\hydra-2 240525\hydra2.tex
being indented.anything else
I am not sure if #505 breaks my program... (yesterday I found that my miktex packages was not updated since 2024/01, and after I updated my packages, the indent program breaks.)
Besides, this bug will not be reproduced on Ubuntu, as Ubuntu encodes everything in UTF-8, and windows encodes paths in GB2312.
The text was updated successfully, but these errors were encountered: