It was a deliberate change

Care to expand or link to something where this was discussed and we could get an idea of the reasons behind?

(I looked through 18 pages of "alias" related Github issues before posting the above, could not find anything)

In any case, the url(s) that were created in J3 will not be modified

Hi @infograf768 :)

You're right, existing aliases won't be modified, except in edge cases where articles or menu items are deleted and then re-created for instance.

So this likely is not a general B/C break I guess.

#32924

@brianteeman OK, I see. I can see it kind of works ok for the English language, not so much for french where the apostrophe is often going to be at the start (d'évaluer and dévaluer really are not the same word for instance).

Too late to change now anyway.

Not tested but can't the custom transliterate function in a language pack address this https://docs.joomla.org/J3.x:Making_a_Language_Pack_for_Joomla#Example_2_-_Custom_transliteration_implemented

It should, the call to transliterate() happens before the regular expression that drops anything but latin alphanumeric.

That's likely where the change should have happened, in the en-* localise.php files.

I'll suggest that to the French localization team.

PS: I noticed that your change was done in src/j4/libraries/src/Filter/OutputFilter.php but not in the vendored folder: src/j4/libraries/vendor/joomla/filter/src/OutputFilter.php, so there's likely an inconsistency risk down the line, right?

OK, this kind of work but won't likely with multilingual sites.

The thing is, the transliterator called is the one corresponding to the current admin language.

So if the backend is displayed in French and you create a French article (language set to FR in the article options), then the transliterate() method in fr-FR.localise.php is used and I can put change there to preserve apostrophe.

However, if the backend is set to English and I create/edit the same article, then the default localise.php file is used, and my custom transliteration for French is not applied.

So for most people I guess adding ' ' => '\'', at the top of the $glyph_array in transliterate() will do the job.

For multilingual sites, they'll be better off adding a transliterate method in localize.php, so that it applies to all items.

Again, I'd think this should be done in per language transliterate but it's too late now for 4.x.

Again, I'd think this should be done in per language transliterate but it's too late now for 4.x.

is there anything left to do here or should it be closed