Talk:ct

RFD

The following information passed a request for deletion.

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.

---

ct

Not unicode. --Æ&Œ (talk) 03:27, 25 September 2014 (UTC)

Move to . — I.S.M.E.T.A. 14:36, 25 September 2014 (UTC)

Delete The entry is absolutely useless. Firstly, the title is wrong (should be Unsupported titles/ct ligature) and its current state is totally redundant - any user who can find this has already figured out that c͡t = ct - and secondly, it's just a stylistic thing and conveys no extra meaning (unlike, say, ß or IJ). With no Unicode representation, I don't see any reason to have this entry. Smurrayinchester (talk) 15:02, 25 September 2014 (UTC)

Where the entry is now, I agree. However, if it is moved to U+EEC5, it will be useful, since the only confusion that is likely to arise from this is if someone comes across a MUFI-compliant text but lacks a font that supports this ligature at that codepoint. — I.S.M.E.T.A. 16:47, 25 September 2014 (UTC)

U+EEC5 is a Korean character piece for me; ct is U+E03D (). I don't see any reason for us to start encoding the mess of PUA standards.--Prosfilaes (talk) 18:47, 25 September 2014 (UTC)

Delete as just plain wrong. Renard Migrant (talk) 11:34, 26 September 2014 (UTC)

Delete per Smurrayinchester and Prosfilaes. - -sche (discuss) 02:02, 29 September 2014 (UTC)

Deleted. bd2412 T 20:47, 12 November 2014 (UTC)