-
Notifications
You must be signed in to change notification settings - Fork 40
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
CHS language update and bug fixes #85
Conversation
Hi, I replied to the wrong email just now. The HOME plugin I replied to in the previous email has the problem of missing icons. The problem with TERA is that your original code is "\r\n"), and the compiled plugin will expand the Pkhex toolbar when used, resulting in no plugins being visible, with only a blank border.
该邮件从移动设备发送
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2024年11月7日(星期四) 凌晨0:51
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [Manu098vm/Tera-Finder] CHS language update and bug fixes (PR #85)
请问下面的代码到底造成了什么错误?
返回的txt不为空文本文件。拆分“\r\n") : [];
删除"\r"使所有文本行组成回车符。结果是这样的:
Imagine.png(在网络上查看)
Imagine.png(在网络上查看)
即使在CHS和CHT语言上,旧代码对我来说也很好用。
Imagine.png(在网络上查看)
Imagine.png(在网络上查看)
我会恢复旧代码,同时如果你能做一个错误报告,说明它导致了什么以及如何重现它,我可以寻找一个合适的修复方法。
-
直接回复这封邮件,在GitHub上查看,或取消订阅.
***@***.*** >
|
I can not reproduce that issue. I'm under the impression your system is changing the way translation files/chars are stored. If so, please post a screenshot of how it looks on your PC. This is how the above build works on my end. |
I tried your previous compiled version and did not encounter this issue. However, my friend and I encountered this problem with our self compiled version before. As you said, it was a problem with our computer system, but it is now resolved by ourselves. The reason why we uploaded it to you before was because if we did not solve this problem, it would hinder the translation work.
该邮件从移动设备发送
…------------------ 原始邮件 ------------------
发件人: "Manu098vm/Tera-Finder" ***@***.***>;
发送时间: 2024年11月7日(星期四) 凌晨1:25
***@***.***>;
***@***.******@***.***>;
主题: Re: [Manu098vm/Tera-Finder] CHS language update and bug fixes (PR #85)
I can not reproduce that issue. I'm under the impression your system is changing the way translation files/chars are stored.
Can you reproduce the issue with the automatic compiled build from my latest commit?
https://github.com/Manu098vm/Tera-Finder/actions/runs/11708197482
If so, please post a screenshot of how it looks on your PC. This is how the above build works on my end.
immagine.png (view on web)
I'm only interested to see if you can reproduce the issue with the automatic build, not with builds that comes from your system, which may have chars coded differently.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
My friend told me that this is a problem with the line breaks in the txt file. His solution is to change all the line breaks in the txt file to recognize the separator \r\n
该邮件从移动设备发送
…------------------ 原始邮件 ------------------
发件人: "Manu098vm/Tera-Finder" ***@***.***>;
发送时间: 2024年11月7日(星期四) 凌晨1:25
***@***.***>;
***@***.******@***.***>;
主题: Re: [Manu098vm/Tera-Finder] CHS language update and bug fixes (PR #85)
I can not reproduce that issue. I'm under the impression your system is changing the way translation files/chars are stored.
Can you reproduce the issue with the automatic compiled build from my latest commit?
https://github.com/Manu098vm/Tera-Finder/actions/runs/11708197482
If so, please post a screenshot of how it looks on your PC. This is how the above build works on my end.
immagine.png (view on web)
I'm only interested to see if you can reproduce the issue with the automatic build, not with builds that comes from your system, which may have chars coded differently.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
No description provided.