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

Slug generation for title with non-ASCII characters #1

Open
jsliang opened this Issue Feb 15, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@jsliang
Owner

jsliang commented Feb 15, 2013

If the title contains non-ASCII characters, SublimePelican's slug generation just omits these non-ASCII character.
If the title is full of non-ASCII characters (say, a Chinese title), the generated slug would be an empty string.

Pelican transforms non-ASCII characters to ASCII ones with unidecode module.
However, I tried using iki/unidecode@7b3e322 but it doesn't seem to work in Sublime Packages environment... :(

@jsliang

This comment has been minimized.

Show comment
Hide comment
@jsliang

jsliang Feb 21, 2013

Owner

Moved to jsliang/SublimePelican#1

Owner

jsliang commented Feb 21, 2013

Moved to jsliang/SublimePelican#1

@jsliang jsliang closed this Feb 21, 2013

@jsliang jsliang reopened this Feb 22, 2013

@jsliang

This comment has been minimized.

Show comment
Hide comment
@jsliang

jsliang May 1, 2014

Owner

The behavior is different in ST3. ST3 preserves non-ASCII code characters. For example, Title: 20140501 五一勞動節 放假一天 is generated as Slug: 20140501-五一勞動節-放假一天.

Owner

jsliang commented May 1, 2014

The behavior is different in ST3. ST3 preserves non-ASCII code characters. For example, Title: 20140501 五一勞動節 放假一天 is generated as Slug: 20140501-五一勞動節-放假一天.

jsliang pushed a commit that referenced this issue Mar 24, 2017

Merge pull request #1 from jmartindf/master
Removing site specific setting from the plugin
@Kristinita

This comment has been minimized.

Show comment
Hide comment
@Kristinita

Kristinita Apr 21, 2017

@jsliang , issue can be closed?

Thanks.

Kristinita commented Apr 21, 2017

@jsliang , issue can be closed?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment