Category talk:Abstract Wikipedia/en-gb
@Quiddity (WMF): If the translation from “en” to “en-GB” is 100% complete, why are there only four sub-categories listed? And what can we do about it?--GrounderUK (talk) 14:09, 27 March 2021 (UTC)
- @GrounderUK: Re: stats: Unfortunately, the "completion" percentage on category pages is only measuring the content on the page itself, i.e. for this page, the single sentence "Content related to [Abstract Wikipedia].". Wider stats about the entire (manually maintained) "aggregate group" of pages related to Abstract Wikipedia is available at https://meta.wikimedia.org/wiki/Special:MessageGroupStats?group=agg-Abstract_Wikipedia&x=D
- Re: contents within this category: I'm not sure whether translating individual content-pages would automagically add them (along with their categories) into the listing on this page, or if that is purely reliant upon translating content on the category-page itself. Out of the 3 methods for organizing content, I've always preferred both using and building the other 2.
- Re: En-gb: Whether to spend time 'translating' from En into En-gb is a complicated topic. I've previously asked about that over at mw:Talk:Localisation#en-gb_and_en-ca_translations, including some reasons as to why it should not be encouraged/prioritized.
- Hope that helps! -- Quiddity (WMF) (talk) 18:58, 30 March 2021 (UTC)
- @Quiddity (WMF): Thanks. That is pretty much what I guessed. I agree we should not trouble ourselves with translations into British English. The fundamental problem is how we fall back to “en”. I prefer my interface language to be en-GB, as the distinction between “license” and “licence” was schooled into me at an early age! Naturally, that leaves me reading content here that is “en” but whose links try to take me to “en-GB”. So long as this does not exist, I fall back happily to “en”. And if “en-GB” actually exists (why?), the untranslated content falls gracefully back to “en”. But not, it appears, on a Category page (well, not for the usable content, the backlinks). We could start the translations into “en-GB” and translate nothing, but that might encourage further pointless translation. Another possibility is the avoidance of Special:MyLanguage where logic dictates that PAGECONTENTLANGUAGE (or whatever) should take precedence. Specifically, an “en” page declares itself to be in the “en” Category, so other pages in the same Category are to be found on the “en” Category page, whatever the interface language happens to be. Just thinking aloud for the general good... (As a pre-Wikipedia WikiZen, I hold that backlinks are the True Way, or MethodZero for your count of three. But, of course, “What links here” doesn’t work with translated pages.\o/ somebody fix that! \o/ )--GrounderUK (talk) 12:42, 31 March 2021 (UTC)
- @GrounderUK: Re: Whatlinkshere, that's phab:T63547, and yeah, it's a frustrating feature-gap.
- Re: fallback: The core complexity, IIUC, is that the entire
<translate>system needs an overhaul, but that is an epic amount of software work, and potentially an epic amount of content-updates. -- So, I've filed a task (phab:T279007) for improving the fallback mechanisms of categories, but it's likely to be low-priority given all the other existing feature-requests or bugs. :-/ -- Personally, I'd suggest temporarily changing your interface language to 'en', at least on wikis that use the<translate>-system. [As a dual British/Canadian citizen, I think I'm allowed to suggest that!? Plus my browser's auto-correct feature is using the default 'en-us' dictionary setting (plus my numerous overrides+additions) so I find it all extra confusing!] - Re: Why en-gb pages exist - I made one of those pages. I usually make 1 "test" translation after marking a page as "ready for translation", in order to confirm that the software is working as expected. (because: we had a few months of problems recently, where it sometimes needed a dummy-edit to nudge the software into action, though I believe that particular bug is now fixed). I'm not sure why the other pages exist, though probably similar reasons.
- HTH. Quiddity (WMF) (talk) 19:34, 31 March 2021 (UTC)
- @Quiddity (WMF): Thanks. That is pretty much what I guessed. I agree we should not trouble ourselves with translations into British English. The fundamental problem is how we fall back to “en”. I prefer my interface language to be en-GB, as the distinction between “license” and “licence” was schooled into me at an early age! Naturally, that leaves me reading content here that is “en” but whose links try to take me to “en-GB”. So long as this does not exist, I fall back happily to “en”. And if “en-GB” actually exists (why?), the untranslated content falls gracefully back to “en”. But not, it appears, on a Category page (well, not for the usable content, the backlinks). We could start the translations into “en-GB” and translate nothing, but that might encourage further pointless translation. Another possibility is the avoidance of Special:MyLanguage where logic dictates that PAGECONTENTLANGUAGE (or whatever) should take precedence. Specifically, an “en” page declares itself to be in the “en” Category, so other pages in the same Category are to be found on the “en” Category page, whatever the interface language happens to be. Just thinking aloud for the general good... (As a pre-Wikipedia WikiZen, I hold that backlinks are the True Way, or MethodZero for your count of three. But, of course, “What links here” doesn’t work with translated pages.\o/ somebody fix that! \o/ )--GrounderUK (talk) 12:42, 31 March 2021 (UTC)