Artweb-design adva cms

Comments and changes to this ticket

• 

  Sven Fuchs October 6th, 2008 @ 12:28 PM

  • Assigned user changed from “Sven Fuchs” to “Clemens Kofler”
• 

  Sven Fuchs October 6th, 2008 @ 03:28 PM

  • Milestone set to “Sprint #2”
• 

  Sven Fuchs October 13th, 2008 @ 11:01 AM

  • Milestone changed from “Sprint #2” to “Release 0.1.0”
  • Tag changed from “feature, permalink, plugins” to “feature, permalink, plugins”
• 

  Sven Fuchs January 9th, 2009 @ 11:10 AM

  • Milestone cleared.
  • State changed from “new” to “open”
  • Assigned user changed from “Clemens Kofler” to “Marko Seppä”

  Look at other plugins that do the same like permalink_fu but maybe in a more extensible manner.

  Should be i18n aware and maybe allow to encode the ID in the permalink.

  Maybe http://github.com/norbauer/salty... is an option, maybe we need to do our own thing.

• 

  Marko Seppä June 18th, 2009 @ 10:34 AM

  Added to product backlog.

• 

  Marko Seppä July 23rd, 2009 @ 09:39 AM

  Tested for categories and contents, umlauts "öäü" works perfectly, except for section permalinks.
  Special characters like §$%/() do not work with categories and contents.

  But I presume we can safely ignore those special characters for now.

  Help texts for permalinks are updated, I will close this ticket after section permalinks are working again.

• 

  Marko Seppä July 23rd, 2009 @ 02:16 PM

  • State changed from “open” to “resolved”

  umlauts aka 'öäü' works now with section permalinks.

  so, umlauts works now on sections, categories, sets and content permalinks. special characters like $%§& seems to only work on content permalinks, but their use is not advised anywhere else, not even on content.

• 

  Sven Fuchs July 24th, 2009 @ 12:38 PM

  I'm not quite sure I understand what this means :)

  How exactly does it work? What does "works" mean?

• 

  Marko Seppä July 24th, 2009 @ 02:02 PM

  so when you have a section with permalink öäü for example and go to frontend to url mypage.com/öäü you see the section.. previously this raised a routing error because it did not find the route for that.

  so sections, contents, categories and sets can have permalinks with umlauts and you can still access them on the frontend.

• 

  Sven Fuchs July 24th, 2009 @ 04:50 PM

  Hmmm, let's say I create a new Section called "Hävie Metäl". What will
  the initial permalink be? Will it be "hävie-metäl" or "haevie-metael"?

  Because I think the default behaviour really should be a
  transliteration to "haevie-metael". That's because most people don't
  have any umlauts on their keyboard so you're basically making your
  URLs less accessible by putting umlauts into it.

  stringex should do this transliteration for us. I've replaced
  permalink-fu with stringex some while ago.

• 

  Priit Tamboom July 25th, 2009 @ 10:07 AM

  I think you worry too much, cos for example Wikipedia is doing exactly that and no complains. When I'm using umlauts then this section/article is targeted to local market where those letters are present. For example, in Estonia we don't translate ä to ae, but we just use a, but any Estonian would be trilled to use real ä as it is.

  Moreover, when Chinese users, they for sure would like to see characters instead as well.

  Just my 2 cents.

• 

  Priit Tamboom July 25th, 2009 @ 10:08 AM

  • no changes were found...
• 

  Sven Fuchs July 25th, 2009 @ 12:41 PM

  Sure, that's what "transliteration" means. Depending on the locale
  you'd transliterate non-latin characters differently. I believe that
  StringEx already does that ( or at least our patch of it does). So, I
  just want to make sure we don't accidentally change that behaviour
  here. Also, this is just the default behaviour. We might add a config
  option or something later, but IMO should continue doing it this way
  because that's what most users expect from a permalink.

  Aren't there any tests for it? If not, we definitely should add some
  and document this behaviour.

• 

  Clemens Kofler July 26th, 2009 @ 01:53 PM

  Well, that kind behavior tends to create problems for exactly the reason that Priit mentioned: Transliterations are done differently depending on the users locale.

  To throw in an idea I already mentioned some time ago: Translated permalinks would solve this problem at its root. In English, per se, hardly any title will ever contain umlauts whereas in other languages they wouldn't need to be transliterated because English-speaking people have their own English version with a proper English permalink that fits the respective title.

• 

  Sven Fuchs July 27th, 2009 @ 09:07 AM

  Hey, Clemens, did you read my comments at all :))

  Our StringEx version does locale aware transliterations. Contents are locale aware, too, so I can't see what the problem should be here.

  I'm not opposed to translated permalinks (as a plugin), but they're a different layer of behaviour. Transliterations should still happen because that's what users expect from a blog, wiki, forum, ... pick any ... and we can easily do that. (Also, I believe it already was there.)

• You flagged this item as spam.
  

  ava james March 17th, 2023 @ 04:17 PM

  Nice post thanks for sharing this check this Lightinthebox Discount Code