I don't know offhand exactly what the right logic would be, but it does sound complicated and we'll have to test all the possibilities pretty thoroughly. It seems like it'd be nice to keep it as spaces in the database, since that's what really is intended. But then the code that handles URLs should accept either underscore or space, and probably the code that generates the links for wikis should turn spaces into underscores so that format actually is what people see. I might not be thinking of all the issues right now though.
I think % in a name is ok still, because with url-encoding that turns into %25 --- ** [tickets:#7708] Reference wiki pages that contain spaces using underscores** **Status:** open **Milestone:** unreleased **Created:** Mon Sep 22, 2014 05:24 PM UTC by Wayne Davison **Last Updated:** Mon Sep 03, 2018 09:16 AM UTC **Owner:** nobody It would be nice to avoid the ugliness of %20 sequences in wiki URLs for each space. One solution would be to allow the url to contain an underscore for each space character and still be able to find the page. As for potential ambiguity in page names, either the wiki would need to treat the names as identical (so that ambiguous pages could not be created) or it would have to prefer finding a page with more underscore matches. I personally think that the former is preferable, which would mean that if I try to create a page named both "foo_bar" and "foo bar" that I'm told that the page exists. The alterntive is for a request for "foo_bar_baz" to find "foo_bar baz" in preference to "foo bar baz" if "foo_bar_baz" doesn't exist and the other 2 do (due to it having more matching underscores). --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
