Topic on Talk:Flow/2017 community feedback concerning URLs format

Jump to navigation Jump to search
Geraki (talkcontribs)

The proposals miss that there are wikis with non-latin scripts and the urls are not not really human readable

Taking as example an existing section link in elwiki non-Flow village pump, the url is

Browser address bar displays a readable form up to the section part, but when it is pasted in an edit box or displayed in a page it is not human readable.

Taking as example an existing flow topic in user talk page these are the urls:

1. Topic:Topicname@Pagename/UUID:

2. Topic:Topicname-UUID@Pagename:

3. Topic:UUID/Pagename/Topic:

(keep in mind that the username is in latin script. a non-latin username would result in even bigger urls)

4. The current url is

So if the the plan is to change the current url "to have something more descriptive that will give more context to users", the question should be "where/when it will give this more context?":

  • When the user is already on the topic page, the topic title and page title are displayed on the top of the page itself
  • When the url is copy&pasted in another page it is not human readable in any way.

Keep it like it is.

Trizek (WMF) (talkcontribs)

Thank you for your feedback.

Trizek (WMF) (talkcontribs)

That change will make URLs a little bit confusing on the browser's URL bar (if the browser doesn't displays encoded URLs), but that will change how links are displayed on wikipages.

On a page like that one, Topic:Tizm73nml0pv0ff0 would be replaced with Topic:Tizm73nml0pv0ff0/Συζήτηση_χρήστη:Geraki/Πρότυπο:Κουτί_πληροφοριών_ποδοσφαιρικού_συλλόγου if the format used is Topic:UUID/Page/Topic format. That would be more readable.

Geraki (talkcontribs)

But then, the question is about the link text and not the url.

In Special:EditWatchlist#editwatchlist-ns2600 I already see Topic titles instead of Topic:UUID.

For this Topic I see:

Just make it Topic @ Page and keep linking to the current, unchangeable and unique url. Then make all special pages do the same thing.

On the other hand if one is to link to some topic in a content page, they will probably just copy&past the url because anything else will probably be more complex. Test case: If I need to link to this topic all I needed was to copy&paste the url (or cut it as a plain internal link Topic:Tizm73nml0pv0ff0 or piped). If we would use the Topic:Tizm73nml0pv0ff0/Συζήτηση_χρήστη:Geraki/Πρότυπο:Κουτί_πληροφοριών_ποδοσφαιρικού_συλλόγου format, then it should appear somewhere in the page to be copied...

Geraki (talkcontribs)
Trizek (WMF) (talkcontribs)

The goal is to remplace all cases displaying UUID by something readable. Other cases work and will not be changed as far as I know about. I'll ask.

> If we would use the Topic:Tizm73nml0pv0ff0/Συζήτηση_χρήστη:Geraki/Πρότυπο:Κουτί_πληροφοριών_ποδοσφαιρικού_συλλόγου format, then it should appear somewhere in the page to be copied...

I'm not sure to understand. That permalink is already available in the "..." menu?

> Another example is the way Wikidata displays its own pages: Again, the link text is created on the fly from the entity label, linking to the unique url, and the id just follows it.

Good point. We can copy by that system to improve Special:WhatLinksHere if we decide not to change Flow's URLs.

Geraki (talkcontribs)

> That permalink is already available in the "..." menu?

A permalink is a url. The intended use it to give you a url that can be copied and pasted. But then, it will already be url encoded.

You can test the same concept in any wiki page, for example elwiki village pump. Copy the address from the sidebar link "Permanent link" and paste it anywhere. It is

For this reason users in some wikis use a user script to cut the title part from the url, since it is not really meaningful, it is not really used in this case, and is equally valid and shorter.

Trizek (WMF) (talkcontribs)

The Collaboration team has discussed about that issue.

That browser URL-encoding for non-Latin script is problematic, but it is already broken on non-Flow pages, like on the example you are pointing out.

The 2016 community wishlist has an item about Section heading URLs for non-Latin languages (choice #3). That may solve the problem. Meanwhile, we can hold the deployment of the new Flow URLs on non-Latin scripted wikis, if a change happen.

We are still investigating.

Reply to "Non latin page/topic titles"