[04:19:28] [discord] Is there any way to hotfix it via scripts before the next version rolls out or is it going to be a waiting game? [04:27:18] [discord] possible but I don't think Miraheze do have enough resouces to perform a fix like that fast [04:50:10] [discord] I mean locally through JS scripts [04:50:41] [discord] Not possible [04:50:57] [discord] It's inside the software itself [04:51:11] [discord] The issue is inside the software itself (edited) [04:55:30] [discord] (I would also suggest use either `zh-hans, zh-hant, zh-hk` or `zh` only for page translations.) [05:01:27] [discord] `$wgTranslateLanguageFallbacks` doesn't seem to work, so it's hard to fix it before the Special:MyLanguage redirection. [05:02:09] [discord] `$wgTranslateLanguageFallbacks` doesn't seem to work, so it's hard to fix it, especially when need to fix it before the Special:MyLanguage redirection. [05:03:12] [discord] I'm not sure whether Miraheze backport patches, though. [05:30:59] [discord] Well, you can wait for 1.39 update, backporting is only for ppl who didn't upgrade frequently [05:31:03] [discord] https://phabricator.miraheze.org/T9446 [05:31:03] [url] ⚓ T9446 Upgrade to MediaWiki 1.39.0 | phabricator.miraheze.org [05:57:22] [discord] *Wikimedia backport window be like:* [06:11:07] Hello Guest! If you have any questions, feel free to ask and someone should answer soon. [07:23:19] [discord] @Winston Sung we don't maintain any custom backports [07:23:40] [discord] well we might but not regularly, usually only because we have to [07:23:54] [discord] You'd be best getting the patch backported upstream [07:24:20] [discord] Wikimedia backport windows aren't for the same purpose. It's normally to make the train run smoother. [07:28:04] [discord] Ok. Thanks for the information. [13:25:17] [discord] I currently disabled all variants except for `zh` main, coz I really don't think content translation is needed for the other variants as for the content on our wiki (main language is `zh`, when the main content is constructed well enough most `zh` pages will be opened up for translation, and no point in allowing variant translation) [13:39:41] [discord] Oh, so it's `zh` as source language? [15:03:55] [discord] source language is both `zh` and `en`, coz some documents (with expired copyright) have source languages in `en` instead of `zh` [15:06:27] [discord] I think that can only solved by waiting the MediaWiki 1.39 upgrade. [15:07:07] [discord] I think that can only solved in the MediaWiki 1.39 upgrade. [15:08:31] [discord] I think that can only solved within the MediaWiki 1.39 upgrade. [23:05:42] [discord] can help me [23:05:42] [discord] There is something wrong [23:05:43] [discord] Some of the images on my wiki have SVG Files [23:05:44] [discord] As far as I know there is a link that says image resolution that will lead to the PNG File version of SVG [23:05:46] [discord] But why does my wiki go directly to the SVG file [23:06:34] [discord] We let your web browser render SVG files directly which means that those links don't do anything because web browsers can't convert SVGs to PNGs [23:08:15] [discord] Yes