[03:16:20] @quidditywiki would you mind filing a bug for this? (re @lucaswerkmeister: hm, I might have broken something… I split Z11722 into two functions, Z11722 and Z11834 (after realizing that they behave differ...) [06:45:07] 13600 [06:50:00] is there already a ticket for the search not showing labels for functions? [07:18:46] I keep being confused by the "short descriptions" field, both because I keep being shown text in random languages that I can't understand (e.g. https://www.wikifunctions.org/view/de/Z24 shows me polish), with no indication that it's in another language (it looks like someone mistakenly entered the wrong language in the fields for english), and because that text doesn't seem to be [07:18:47] shown when I click the languages button [07:22:24] and going back to what I was saying the other day about it not making good use of my screen space: showing everything stacked vertically in the dialog which opens when clicking that languages button means I have to scroll unnecessarily to see all the languages [07:30:12] my laptop, for example, doesn't have a lot of space, so I can only see five things before I need to scroll (first screenshot), but if it were displayed more like a table, to take advantage of my screen being wider than it is tall (here I just added display: inline-block, I'd make it into an actual grid if I were doing more than taking this screenshot), I could get all seven with a bit of space left over (second screenshot) : [07:30:14] https://tools-static.wmflabs.org/bridgebot/971a8fdb/file_54866.jpg [07:42:44] the amount of space around the page content on function pages makes it look like something broke : https://tools-static.wmflabs.org/bridgebot/28b59f83/file_54867.jpg [07:42:45] https://tools-static.wmflabs.org/bridgebot/baeac8d7/file_54868.jpg [07:43:44] I'd expect something more like this : https://tools-static.wmflabs.org/bridgebot/11a98e29/file_54869.jpg [10:07:38] Maybe a dumb question: should we really allow title and description of functions in Old and Middle French? (most of the vocabulary didn't exist) [15:25:22] Thank you! Such reports are very timely because we are thinking about redesigning that page in particular soon-ish. (re @Nikki: the amount of space around the page content on function pages makes it look like something broke) [15:28:16] Open to follow suggestions here. I could see similar arguments be made for Latin, and yet we probably would like to have that? I honestly don't know how to choose the set of languages here. (re @Nicolas: Maybe a dumb question: should we really allow title and description of functions in Old and Middle French? (most of the vocabula...) [15:55:40] both are historical languages but : [15:55:41] - Latin is *kind of* alive (it has a Wikipedia, new vocabulary is still created, etc.) [15:55:42] - Old/Middle French is just dead (re @vrandecic: Open to follow suggestions here. I could see similar arguments be made for Latin, and yet we probably would like to have that? I...) [15:57:17] for instance : [15:57:18] - in Latin, computer is "Computatrum" (https://la.wikipedia.org/wiki/Computatrum) [15:57:20] - there is no word in Old French [15:57:21] (same for a lot of other modern words) [15:59:30] you could certainly hack up an Old French word from the Latin one on linguistic principles (re @Nicolas: for instance : [15:59:30] - in Latin, computer is "Computatrum" (https://la.wikipedia.org/wiki/Computatrum) [15:59:32] - there is no word in Old Frenc...) [16:03:14] or even back-form from 'ordinateur' :-) [16:19:40] But we still should be able to generate text in Old French I assume, merely not have the user interface be in Old French? [16:23:18] but that's would be just me inventing stuff, no-one would understood (especially as almost no-one understand Old French anyway) [16:23:18] PS: -eur is a reather modern French suffix, it would be more like "ordinator" (re @mahir256: you could certainly hack up an Old French word from the Latin one on linguistic principles) [16:24:03] yes, for functions inputs/outputs, it makes sense and it's useful [16:24:03] for titles/descriptions, not so much (re @vrandecic: But we still should be able to generate text in Old French I assume, merely not have the user interface be in Old French?) [16:25:47] I liked to keep it a single list in hopes it simplifies things [16:26:09] What are the disadvantages? [16:26:23] It could be a vector for vandalism [16:27:27] Anything else? [16:30:15] no strong disadvantage, just midly annoying to see it appears on the list when I type "French" (and one could misclick if going too fast) [16:31:03] Ah! A better ranking would do the trick then too? [16:32:31] ranking is ok, French is first so al good (re @vrandecic: Ah! A better ranking would do the trick then too?) [16:33:25] I see [16:33:26] that said "frafra" is before "français" when typing just "fra" which is a bit weird, maybe a better ranking could help indeed [20:51:03] Theoretically yes. We can convert French to Middle French using a set of rules. (re @vrandecic: But we still should be able to generate text in Old French I assume, merely not have the user interface be in Old French?) [20:52:15] For example, "ai" becomes "oi" and "oi" becomes "oy". [20:53:01] However, we should restore how we write French diacritics before the 1990 revision. [20:53:27] That is a long story. [22:01:33] Yes. But it's much more complicated than that. [22:01:35] Like "ouvert"@fr becomes "appert"@fro 🤪 (re @Csisc1994: For example, "ai" becomes "oi" and "oi" becomes "oy".) [22:02:28] fr-1990 is actually a very good idea, much more automisable (re @Csisc1994: However, we should restore how we write French diacritics before the 1990 revision.)