Module talk:languages/data/3/e

eky
Please update 'eky':

m["eky"] = { canonicalName = "Eastern Kayah", scripts = {"Kali"}, family = "kar", }

--Octahedron80 (talk) 03:03, 15 June 2016 (UTC)


 * Done. Wyang (talk) 03:07, 15 June 2016 (UTC)

egy sortkey
, I notice from the Egyptian category pages that the theoretical sort order is: ꜣ j y ꜥ w b p f m n r h ḥ ḫ ẖ z s š q k g t ṯ d ḏ Is this actually correct, and if so, should we make them sort that way? If so, I think we'd have to do it with a module; right, ? —*i̯óh₁nC[5] 07:08, 14 December 2017 (UTC)
 * Yes, that’s the standard sort order for Egyptian, and ideally Egyptian entries would sort that way; I’m not sure if alternative Latin-script sort orders are yet possible to implement, though. If so, that’d be great! There’s also the standard Demotic sort order at Template:egx-dem-categoryTOC if it could be done. — Vorziblix (talk · contribs) 07:37, 14 December 2017 (UTC)
 * Hmm, that order is quite different from the Unicode order . It couldn't be achieved by simply replacing a few characters, as can be done for some alphabets that mostly follow the Basic Latin order.
 * In theory, it could be achieved by using dummy characters: replacing that transcriptional "alphabet" with arbitrary series of codepoints that would result in the correct sorting order. (For instance, assigning ꜣ to A, j to B, y to C, and so on.) It could be achieved using the "from" and "to" tables, but a dedicated function would be more efficient. The category headers would be incorrect, but they could be changed to the correct characters with JavaScript. (Of course, they would still display incorrectly for users who have JavaScript disabled.) The links in the table of contents would also have to be changed. (The template allows for this.)
 * It's a very inelegant solution, but seems pretty simple to me. Ideally, this would be implemented on the server side, but as of yet that feature has not been created. — Eru·tuon 08:07, 14 December 2017 (UTC)
 * Sounds good to me. Would this be likely to cause memory problems over at, say, or ? In any case, having the sort order implemented would be nice. — Vorziblix (talk · contribs) 16:53, 14 December 2017 (UTC)
 * No, I believe it would be a pretty inexpensive process. I can start on it soon. The only thing I have to learn is how to keep the module and the header-modifying script in sync: how to request data from a Lua module. — Eru·tuon 20:55, 14 December 2017 (UTC)
 * The sortkey-generating part has been created: see Module:egy-utilities. — Eru·tuon 21:27, 14 December 2017 (UTC)
 * Thanks! It looks like all the test cases are sorting correctly. — Vorziblix (talk · contribs) 22:45, 14 December 2017 (UTC)
 * Hello again; any luck with this? (And in the meantime, do you think it’d be worthwhile to implement the sort order even if the headings are wrong, for the sake of derived terms sections and the like? Or would that be too ugly?) Thanks again for the help! — Vorziblix (talk · contribs) 17:46, 12 January 2018 (UTC)
 * After some thought, I only want to implement the sort order if there's a global JavaScript function to replace the category headers, or people will start coming after me, and that would require Beer Parlour approval. But I can make Module:columns use the sort function so that the sort order is automatically used in and . — Eru·tuon 20:48, 12 January 2018 (UTC)
 * Sure thing, that sounds good to me. Thanks again, — Vorziblix (talk · contribs) 20:54, 12 January 2018 (UTC)
 * Done. — Eru·tuon 21:13, 12 January 2018 (UTC)
 * It may not be working as intended yet; e.g. at the words with initial  sort last rather than first. — Vorziblix (talk · contribs) 21:41, 12 January 2018 (UTC)
 * Gah! Fixed. — Eru·tuon 21:45, 12 January 2018 (UTC)
 * Thanks once more! — Vorziblix (talk · contribs) 21:46, 12 January 2018 (UTC)