26

Run the following SEDE query: https://data.stackexchange.com/japanese/query/178382.

All the tags except kyūjitai-and-shinjitai, renyōkei, あれ, and たい-form get auto-linkified. These happen to also be the only four tags that contain characters outside the standard set of allowed characters [a-z 0-9 + # - .]. It would be nice if these would auto-linkify too.

(I imagine this is even more applicable for other language sites like Russian - if you rerun the query for Russian, you find that well over half the tags don't linkify because they contain Cyrillic characters.)

Improve this question
3
  • We’ve reviewed this request and have moved it to our backlog. I’ve updated the status to status-deferred.
    – V2Blast
    Feb 1 at 16:02
  • @V2Blast what does that mean in this case? No one has time to review my Pull Request and merge it?
    – rene
    Feb 1 at 17:56
  • 3
    @rene: We're triaging the many [status-review] tagged items from 2020 and earlier, so that's just the guidance I was given. I'll check with the relevant dev team about this particular issue :)
    – V2Blast
    Feb 1 at 20:32

2 Answers 2

Reset to default
6
+100

Now that the sites clearly support Unicode tags where appropriate, they should indeed be linkified like the rest.

Assuming no one has any issue with me going a bit overboard to address JavaScript's poor support for Unicode character classes in regular expressions, all of the mentioned tags will be linkified following a pull and redeploy of Data Explorer (some revision > 2014.5.7.25).

Improve this answer
3
  • Please add TagName to the documentation of magic columns, while you're at it. And can you allow the title to be Tag Link, to be consistent with the others? And will this future version allow Unicode in all autolinks? And can I have a unicorn?
    – Gilles 'SO- stop being evil'
    Jul 1, 2014 at 20:50
  • It's actually already mentioned at the bottom. Allowing for Tag Link too is easy enough; the current options are based on the relevant fields you'd pull this information out of.
    – Tim Stone
    Jul 1, 2014 at 22:12
  • 3
    It's not fixed.
    – Laurel
    Feb 21, 2018 at 15:20
5

I've opened a new PR here where I now try to get a fix passed Nick that doesn't introduce a new library. The fix will only work for newer browsers (so IE11 will behave like it did) as it relies on RegExp Unicode support in the browser.

Allow for 6 to 8 weeks to get review feedback and another 6 to 8 weeks for merging and deploying.

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .