Closed wubinwww closed 1 year ago
Don't just delete PRs to start over. Fix the existing PR next time. While the text displays correctly on GitHub it is incorrect in the Visual Studio. On the last PR, I attempted to fix the text by copying what was on GitHub to Visual Studio and it displayed correctly for me in PKHeX. Did those changes appear correctly for you when you compiled the code and put it in PKHeX?
My friend also encountered the problem of incorrect display when you accepted my pull, and the English computer system problem. No matter what form, the source files given to you by my Chinese computer system will appear garbled on your Visual Studio. However, the localization of TXT text will not have this problem. Unfortunately, I wanted to help you with this translation, but I had to give up because of this problem.
Going to merge in this "fixed" version based on the text GitHub shows and rely on the version you and @Sadlamulk maintain to support those who this one doesn't.
Hello, I have synchronized your updates to my pull and downloaded them to my computer to check. "It's true that from your perspective, it's garbled code or even bird language, but it has nothing to do with the display of Pkhex. I will continue to translate this for you in the future."
该邮件从移动设备发送
------------------ 原始邮件 ------------------ 发件人: "Jonathan @.>; 发送时间: 2023年3月30日(星期四) 晚上9:50 收件人: @.>; 抄送: @.>; "State @.>; 主题: Re: [foohyfooh/PKHeXPluginPile] PKHeXPluginPile CHS translate (PR #2)
Merged #2 into master.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
Please delete yesterday's CHS translation pull and change to this