Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a25cdde64a26c78f

Jump to content

Talk:Tae-min

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 year ago by Arbitrarily0 in topic Requested move 26 January 2025

Requested move 26 January 2025

[edit]
The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved. Arbitrarily0 (talk) 21:51, 2 February 2025 (UTC)Reply


Tae-min (name)Tae-min – Unnecessary disambiguation. Tae-min currently redirects to Taemin, but the subject of that article is not commonly known as "Tae-min", with the hyphen, in general usage.

The pageview stats for the redirect shows the article "Taemin" was accessed using the Tae-min redirect only 62 times over the last 12 months, averaging 0.16 times per day. Likely best to eliminate the unused redirect and unnecessary disambiguator on the name article.

There is past precedent for leaving the hyphenated name article at the root, while also having someone with the unhyphenated mononym. See: Jimin and Ji-min, Soyeon and So-yeon, Miyeon and Mi-yeon, Jisoo and Ji-soo, etc. RachelTensions (talk) 21:35, 26 January 2025 (UTC)Reply

Support per nom seefooddiet (talk) 10:06, 27 January 2025 (UTC)Reply
Support per nom - Yolo4A4Lo (talk) 00:40, 28 January 2025 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.