The following discussion has been moved from Wiktionary:Requests for moves, mergers and splits.
This discussion is no longer live and is left here as an archive. Please do not modify this conversation, but feel free to discuss its conclusions.
These shouldn't be in the reserved 3-letter language code space (ISO could still assign them). We could move them to {{rfrom}}
and {{rfmms}}
(though I doubt we need this last one as we should encourage the more specific ones). --Bequw → τ 02:14, 11 October 2011 (UTC)
{{rfd}}
, {{rfv}}
and {{rfc}}
. --Mglovesfun (talk) 10:16, 11 October 2011 (UTC)
{{rfm}}
and {{move}}
are identical AFAICT, in which case I suggest one be made a redirect to the other, though I don't care which. We can worry about the ISO codes if and when the time comes. These are not like {{see}}
(which we also dealt with when the time came), which is meant to be on many pages: these are on pagesonly temporarily, so there'll never be more then N of them for some number N. So I don't think we need to worry about ISO codes.—msh210℠ (talk) 02:13, 12 October 2011 (UTC)
{{move}}
, {{merge}}
and {{split}}
, this template attempts to cover all three. NB, {{rfe}}
, {{rfi}}
. Mglovesfun (talk) 06:37, 13 October 2011 (UTC)
It seems strange to me that this template requires a language code when it is meant to be used both in and out of mainspace. What would be the appropriate language code to give, for example, if an RFM were created for Wiktionary:Concordances? Or Template:mention? Using mul (translingual) in all such cases feels to me like a clunky workaround rather than being useful. - excarnateSojourner (talk | contrib) 00:53, 28 April 2022 (UTC)
und
. 70.172.194.25 00:55, 28 April 2022 (UTC)The target ("move-to") doesn't appear if specified in section= or fragment= and doesn't appear if they are not specified. DCDuring (talk) 18:37, 14 September 2023 (UTC)