cannot handle non-ascii characters in image file names
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 331
- Avg merge
- 19h 52m
- Merged PRs (30d)
- 9
Description
For example, I have
content/test.mdandpublic/UPcase测试.png, incontent/test.md,doesn't work, butworks.
Originally posted by @MCredbear in #3252
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report using content/test.md and public/UPcase测试.png, comparing the non-ASCII and lowercase image references. Trace the image path handling from that reproduction and confirm that the original filename resolves successfully; add or run a focused regression check if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100