To participate you must create an account on apostrophenow.org. If you have already done so, click Login.

Ticket #440 (closed defect: fixed)

Opened 20 months ago

Last modified 19 months ago

The slugifying algorithm should handle non-ASCII characters neatly

Reported by: eneroth Owned by: boutell
Priority: major Milestone: 1.4.1
Component: apostropheBlogPlugin Version: 1.4
Keywords: Cc:
Symfony version: 1.4

Description

When I create an event with non-ASCII characters in the name, say "Hår Hör Här" (just an example, doesn't mean anything in particular), the slug generated is "h-aring-r-h-ouml-r-h-auml-r", while the proper transliteration would be "har-hor-har".

Error: Macro Image([object Object]) failed
Attachment 'ticket:440: [object Object]' does not exist.

Apostrophe itself DOES transliterate correctly, for example when creating a new page. A page named "Hår Hör Här" gets the URL:  http://domain.com/har-hor-har
Screenshot of URL

Consequently, this should be an issue with the apostropheBlogPlugin.

Attachments

har-hor-har.png Download (4.7 KB) - added by anonymous 20 months ago.
Screenshot of event
har-hor-har (URL).png Download (20.8 KB) - added by anonymous 20 months ago.
Screenshot of URL
ss.JPG Download (136.6 KB) - added by kallosz 20 months ago.
Shuld be (Jakaś nazwa ąśźę)
apostropheBlogPlugin.patch Download (0.6 KB) - added by eneroth 19 months ago.
This patch should fix the problem.

Change History

Changed 20 months ago by anonymous

Screenshot of event

Changed 20 months ago by anonymous

Screenshot of URL

Changed 20 months ago by eneroth

  • owner changed from dordille to boutell
  • status changed from new to assigned

Changed 20 months ago by eneroth

  • milestone set to 1.4.1

Changed 20 months ago by eneroth

  • version set to 1.4

Changed 20 months ago by kallosz

Shuld be (Jakaś nazwa ąśźę)

Changed 19 months ago by eneroth

This patch should fix the problem.

Changed 19 months ago by tboutell

  • status changed from assigned to closed
  • resolution set to fixed

Fixed in [1747]. Thanks for the patch, it wasn't quite right but pointed the way to the correct fix. Titles live in Apostrophe plaintext slots, so they are supposed to be preescaped HTML. The correct fix is to take this into account and decode them before calling the slugifier

Note: See TracTickets for help on using tickets.