[Bug] Router Warning with CJK filename(unencoded characters)

[wafer-li]

Describe the bug

Router will complain the CJK filename.

Screenshots

Additional context

Add any other context about the problem here. Especially the issue occurs in certain OS, browser or configuation.

[wafer-li]

I think, it is the framework's duty to use a encodedURI().

Or is there some bug with encodedURI() fucntion?

[Mister-Hope]

See https://vuepress-theme-hope.github.io/zh/FAQ/#%E8%AE%BF%E9%97%AE%E9%83%A8%E5%88%86%E9%93%BE%E6%8E%A5-404

I have done all I could.

[wafer-li]

Sorry for my blind eye.

I checked that your branch is still ahead of the origin remote.

Therefore you could try to publish your own npm package under your namespace.

And use the fixed version to resolve this problem.

[Mister-Hope]

I checked that your branch is still ahead of the origin remote.

What do you mean here? What is the origin remote, my main branch aligning to vuepress@2? My code is nothing related to vuepress-plugin-blog

Therefore you could try to publish your own npm package under your namespace.
And use the fixed version to resolve this problem.

You are just triggering a warning, and it will have no effect in production mode.

The only problem is that you cannot directly navigate to a category or tag page, but that' a rare case. Also vuepress2 is on the way.

So I have no interest in forking a copy of vuepress-plugin-blog and maintain by my own. Remember that's an official plugin, which means the official has dropped vuepress v1 support. (Also vuepress has only less than 30 commits last year while 10 of them belong to docs)

[wafer-li]

I have tinkered this problem the whole night.

Even though I found out some solutions, neither of them is better than yours.

For now, we could only expect the vuepress2 release might be solving the problem.

The explanations to the misunderstanding containing my naive thoughts

What do you mean here? What is the origin remote, my main branch aligning to vuepress@2? My code is nothing related to vuepress-plugin-blog

I mean that you already make a PR of fix to vuepress-plugin-blog, that means you already have a fork of this plugin.

Then you could just publish a fixed version of vuepress-plugin-blog and use it as dependency in this theme.

[Mister-Hope]

See vuepress/vuepress-plugin-blog#95 (comment)

If it's not been replyed in 3 days, I will publish a version.

[wafer-li]

And there is another approach, check vuepress-reco/vuepress-theme-reco@8fefc9f

It seems that it is still problematic. It is better not to modify the router stuff. Check https://github.com/vuepress-reco/vuepress-theme-reco/issues/364

[Mister-Hope]

This problem must be fixed on plugin-blog side, becase /tag/使用指南/ is just what they are registing.