Customize category and tag pages + improving slugs

[JeremieLitzler]

Hi @Mister-Hope

I hope you're doing well.

I'm not sure if I can do it, but, in French, categories or tags like Santé or L'Archipelle don't get evaluated properly.

The issue is that the characters get encoded and the RFC3986 says no, that is, URIs cannot contain unicode characters, only ASCII.

The problem is on the accentuated characters or same specials characters like the apostrophe.

Is that an enhancement that you can do? Or can you point me in the location of the code to update to handle that (here?) ?

I think that using the normalization method could work:

//for accents
const str = "Santé";
const cleaned = str.normalize('NFD').replace(/[\u0300-\u036f]/g, '');
//cleaned => "Sante"

//for special characters
const str2 = "L'archipelle";
const cleaned2 = str2.replace(/[.,\\\/#!$%\^&\*;:{}=\-_\'`~\(\)\"[\|]/g, "-");
//cleaned2 => "L-archipelle"

Also, in French, we say "Catégorie Santé", not "Santé Catégorie". Where can we update that in the page title? Maybe we could use a single method by printing "Catégorie: Santé" or "Category: Health" and it could be good enough for everyone?

Thanks very much.

[Mister-Hope]

I think that blog plugin should encode them well, that should be a bug.

Edited: Maybe there are some problems, I will check thay out later.

[Mister-Hope]

Oh are you talking about the tab title?

[Mister-Hope]

It's a bit complicated to do such things, as we must include extra locale options for these kinds of requests, and I don't think it's worse to do so.

If we are serious about these i18n, then we must provide these locale options:

• category (E.g.: Category)
• categories (E.g.: Categories)
• itemCategory (E.g.: Category :item)

With tag, star, article, timeline and other types, though we have a nicer default i18n now, it would be complicated for both developer and users who want to customize them.

[Mister-Hope]

So my basic point is that I prefer to provide less options (i.e.: only a single category locale option for category)

[JeremieLitzler]

@Mister-Hope

Oh are you talking about the tab title?

Yes, that's the one.

So my basic point is that I prefer to provide less options (i.e.: only a single category locale option for category)

Well, in the case of ${name} ${themeData.locales[localePath].blogLocales.category}, you output Santé Catégorie in French and Health Category in English.

Using ${themeData.locales[localePath].blogLocales.category} - ${name}, you output Catégorie - Santé in French and Category - Health in English.

We could also have ${themeData.locales[localePath].blogLocales.category}: ${name} or ${themeData.locales[localePath].blogLocales.category} / ${name} or any delimiter character...

Same for the tags.

I think that it could be voted from the current users of the theme, what do you think?

[Mister-Hope]

Using ${themeData.locales[localePath].blogLocales.category} - ${name}, you output Catégorie - Santé in French and Category - Health in English.

We could also have ${themeData.locales[localePath].blogLocales.category}: ${name} or ${themeData.locales[localePath].blogLocales.category} / ${name} or any delimiter character...

Makes sense

[Mister-Hope]

587eb6c fixes your problem

[JeremieLitzler]

Hi @Mister-Hope

587eb6c fixes your problem

I'm sorry, but this doesn't fix the issue I had in mind.

I was talking about replacing the UNICODE accentuated characters with ASCII characters (ex: é > e ou ô>o) and also replacing any special characters to the dash character to make a pretty slug value ('>-or?>-`).

I think the slug should only contain [a-zA-Z0-9] and the "-" character.

Is that a request that is doable / acceptable?

I'd understand it could become a complex matter.

Thanks for taking the time to read this.

[Mister-Hope]

the slugify function should be customizable in theme. Check that and open a pr.to.update it's default value.

[JeremieLitzler]

I see. I'll try that

[JeremieLitzler]

@Mister-Hope

Are you sure it exposed to customization?

I don't see it in beta.231.

[JeremieLitzler]

This is a screenshot from theme.ts

[Mister-Hope]

You can open a pr to support this in theme, and you can also improve the default slugify function

[Mister-Hope]

Busy in the passing days, have I support this yet?

[JeremieLitzler]

Hi @Mister-Hope

I have no need of this anymore, having migrated to Hugo, which support out-of-the-box this feature.

Thanks.