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

The file name encoding is abnormal after copying the image and pasting it #11246

Closed
3 tasks done
zhoutaosheng opened this issue May 4, 2024 · 1 comment
Closed
3 tasks done
Assignees
Labels
Milestone

Comments

@zhoutaosheng
Copy link

zhoutaosheng commented May 4, 2024

一个小bug:复制带空格命名的资源,带%20,从而导致出现在丢失的资源文件中

Is there an existing issue for this?

  • I have searched the existing issues

Can the issue be reproduced with the default theme (daylight/midnight)?

  • I was able to reproduce the issue with the default theme

Could the issue be due to extensions?

  • I've ruled out the possibility that the extension is causing the problem.

Describe the problem

重现步骤:
比如一个图片, 命名为 How TCP Works.gif

  • 拖进思源后为 How TCP Works-**********.gif
  • 然后复制一下,文件名为 How%20TCP%20Works-**********.gif
    最后出现在丢失的资源文件中
    image

Expected result

复制的时候,不要将空格改为 %20,已有的资源丢失,我自己改对。
另外希望顺便检查其他windows环境下,允许作为命名的特殊字符是否存在问题,感谢

Screenshot or screen recording presentation

No response

Version environment

- Version: 3.0.12
- Operating System: Win11
- Browser (if used):

Log file

More information

No response

@88250 88250 self-assigned this May 5, 2024
@88250
Copy link
Member

88250 commented May 5, 2024

另外希望顺便检查其他windows环境下,允许作为命名的特殊字符是否存在问题

这个在插入资源文件的时候检查过的。

@88250 88250 added the Bug label May 5, 2024
@88250 88250 added this to the 3.0.13 milestone May 5, 2024
@88250 88250 changed the title 一个小bug:复制带空格命名的资源,带%20,从而导致出现在丢失的资源文件中 The file name encoding is abnormal after copying the image and pasting it May 5, 2024
@88250 88250 closed this as completed May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants