User talk:Pyrrhus

From MEpedia, a crowd-sourced encyclopedia of ME and CFS science and history
Jump to: navigation, search

Welcome to Pyrrhus’s Talk page.[new][edit source][reply]

Feel free to talk with me here about MEpedia.

Just add a new comment to the beginning of this page.

You can reply to an existing comment by beginning your comment with the Horizontal Line button, or by indenting your reply using colons.

And please remember to end your comment with four tilde characters "~~~~" on a line by itself, which signs your name to the comment.

Thanks!

Pyrrhus (talk) 19:13, 10 February 2019 (EST)

Timeless skin - path[new][edit source][reply]

Do you know the path to the Timeless skin folks on the server? Especially the .less and css files (there will be several), and the images folder? Eg /resources/screen-common.less and resources/images? User:Pyrrhus ~Njt (talk) 08:31, November 12, 2019 (EST)

Njt I don't know, I'm sorry...
Pyrrhus (talk) 12:18, November 12, 2019 (EST)
Is OK, I found it by guessing, it's https://www.me-pedia.org/skins/Timeless/resources/screen-common.less etc ~Njt (talk) 18:59, November 12, 2019 (EST)

Translating ND/NC License Templates[new][edit source][reply]

Please check - these are new system messages to add in German, French, Spanish plus I thought it worth adding Dutch, English examples above. All wording comes from the relevant Creative Commons license page, or from pasting the correct link and license name over the top of an existing SA or CC-BY message for that language. I *might* be able to morph these into a XML file for importing so they won't need doing individually. I'm finding this is using a lot of concentration to do. CC-BY-SA-4.0 messages don't exist in Spanish (installing that Localization extension would create them for us, plus any others that are missing). I need to check these for invisible characters too notjusttired (talk) 08:08, August 15, 2019 (EDT)

Okey dokey. I will check all these today or tomorrow and try to put together an XML file. Thanks User:Notjusttired for all your hard work! I will also add a draft developer task to run the LocalisationUpdate maintenance script to retrieve translations from translatewiki.net. (The LocalisationUpdate extension came bundled with our MediaWiki software.)
Pyrrhus (talk) 14:07, August 15, 2019 (EDT)
I think it's worth holding off on those for the moment. I've asked User:JaimeS to look at our choice on copyright licenses to confirm if we are keeping the Non-commercial and No-Derivs - it turns out we are only using then for 3 files at the moment. Plus asked her about continuing with the "Used with permission" exceptions - mostly used for advocates uploading selfies plus Millions Missing type photos. I had a quick look into the XML files. Looks easier than I thought - but would be important to run through an online XML validator before trying to import.
What about the extra system messages you created for the 3 languages for Donate? You or I could put together a long (very long) list of pages names to cover those for all languages, so they can be exported (those that exist). notjusttired (talk) 17:38, August 15, 2019 (EDT)
Okay, I'll hold off on these until you say otherwise. I found this message for "donate", but it's only translated into a few languages: MediaWiki:project-localized-name-donatewiki. I guess we should double-check that all these messages are really fully translated...
Pyrrhus (talk) 23:23, August 15, 2019 (EDT)
CC-BY-ND-4.0 translations
wm-license-cc-by-nd-4.0-text
This file is licensed under the [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nd/4.0/ Attribution-NoDerivatives 4.0 International] license.

wm-license-cc-by-nd-4.0-text/de
Diese Datei ist lizenziert unter der [[{{int:wm-license-cc-wiki-link}}|Creative-Commons]]-Lizenz [//creativecommons.org/licenses/by-nd/4.0/deed.de „Namensnennung - Keine Bearbeitungen 4.0 International“.]

wm-license-cc-by-nd-4.0-text/es
Este archivo se encuentra bajo la licencia [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nd/4.0/deed.es_ES Reconocimiento-SinObraDerivada 4.0 Internacional].

wm-license-cc-by-nd-4.0-text/fr
Ce fichier est sous la licence [[{{int:wm-license-cc-wiki-link}}|Créative Commons]] [//creativecommons.org/licenses/by-nd/4.0/deed.fr Attribution - Pas de Modification 4.0 International].

wm-license-cc-by-nd-4.0-text/nl
Dit bestand is gelicenseerd onder de [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nd/4.0/deed.nl Naamsvermelding-GeenAfgeleideWerken 4.0 Internationaal] licentie.

wm-license-cc-conditions-no_derivs-header
NoDerivatives
wm-license-cc-conditions-no_derivs-header/de
Keine Bearbeitungen
wm-license-cc-conditions-no_derivs-header/es
SinObraDerivada
wm-license-cc-conditions-no_derivs-header/fr
Pas de modifications
wm-license-cc-conditions-no_derivs-header/nl
GeenAfgeleideWerken —

wm-license-cc-conditions-no_derivs-text
If you remix, transform, or build upon the material, you may not distribute the modified material.
wm-license-cc-conditions-no_derivs-text/de
Wenn Sie das Material remixen, verändern oder darauf anderweitig direkt aufbauen, dürfen Sie die bearbeitete Fassung des Materials nicht verbreiten.
wm-license-cc-conditions-no_derivs-text/es
Si remezcla, transforma o crea a partir del material, no puede difundir el material modificado.
wm-license-cc-conditions-no_derivs-text/fr
Dans le cas où vous effectuez un remix, que vous transformez, ou créez à partir du matériel composant l'Oeuvre originale, vous n'êtes pas autorisé à distribuer ou mettre à disposition l'Oeuvre modifiée.
wm-license-cc-conditions-no_derivs-text/nl
Je mag het veranderde materiaal niet verspreiden als je het werk hebt geremixt, veranderd, of op het werk hebt voortgebouwd.
BY-NC-4.0

Same again but Non-commercial (we only have files in the v4.0 category so I haven't done the others, although they are currently options to choose).

wm-license-cc-by-nc-4.0-text
This file is licensed under the [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nc/4.0/ Attribution-NonCommercial 4.0 International] license.

wm-license-cc-conditions-noncommercial-header
NonCommercial

wm-license-cc-conditions-noncommercial-text
You may not use the material for commercial purposes.

wm-license-cc-by-nc-4.0-text/de
Diese Datei ist lizenziert unter der [[{{int:wm-license-cc-wiki-link}}|Creative-Commons]]-Lizenz [//creativecommons.org/licenses/by-nc/4.0/deed.de „Namensnennung-Nicht kommerziell 4.0 International“.]

wm-license-cc-conditions-noncommercial-header/de
Nicht kommerziell 

wm-license-cc-conditions-noncommercial-text/de
Sie dürfen das Material nicht für kommerzielle Zwecke nutzen.

wm-license-cc-by-nc-4.0-text/es
Este archivo se encuentra bajo la licencia [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nc/4.0/deed.es Atribución-NoComercial 4.0 Internacional].

wm-license-cc-conditions-noncommercial-header/es
NoComercial

wm-license-cc-conditions-noncommercial-text/es
Usted no puede hacer uso del material con propósitos comerciales.

wm-license-cc-by-nc-4.0-text/fr
[[{{int:wm-license-cc-wiki-link}}|Créative Commons]] [//creativecommons.org/licenses/by-nc/4.0/deed.fr Attribution - Pas d’Utilisation Commerciale 4.0 International].

wm-license-cc-conditions-noncommercial-header/fr
Pas d’Utilisation Commerciale

wm-license-cc-conditions-noncommercial-text/fr
Vous n'êtes pas autorisé à faire un usage commercial de cette Oeuvre, tout ou partie du matériel la composant.

wm-license-cc-by-nc-4.0-text/nl
Dit bestand is gelicenseerd onder de [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nc/4.0/deed.nl Naamsvermelding-NietCommercieel 4.0 Internationaal] licentie. 

wm-license-cc-conditions-noncommercial-header/nl
NietCommercieel

wm-license-cc-conditions-noncommercial-text/nl
Je mag het werk niet gebruiken voor commerciële doeleinden.
BY-NC-ND-4.0

Same again, but nothing needed for the lower part of the license since it just lists both Non-commercial and No-Derivs, which already exist

wm-license-cc-by-nc-nd-4.0-text
This file is licensed under the [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nc-nd/4.0/ Attribution-NonCommercial-NoDerivatives 4.0 International] license.

wm-license-cc-by-nc-nd-4.0-text/de
Diese Datei ist lizenziert unter der [[{{int:wm-license-cc-wiki-link}}|Creative-Commons]]-Lizenz [//creativecommons.org/licenses/by-nc-nd/4.0/deed.de „Namensnennung - Nicht kommerziell - Keine Bearbeitungen 4.0 International“.]

wm-license-cc-by-nc-nd-4.0-text/es
Este archivo se encuentra bajo la licencia [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nc-nd/4.0/deed.es Atribución-NoComercial-SinDerivadas 4.0 Internacional].

wm-license-cc-by-nc-nd-4.0-text/fr
[[{{int:wm-license-cc-wiki-link}}|Créative Commons]] [//creativecommons.org/licenses/by-nc-nd/4.0/deed.fr Attribution - Pas d'Utilisation Commerciale - Pas de Modification 4.0 International].

wm-license-cc-by-nc-nd-4.0-text/nl
Dit bestand is gelicenseerd onder de [[{{int:wm-license-cc-wiki-link}}|Creative Commons]] [//creativecommons.org/licenses/by-nc-nd/4.0/deed.nl Naamsvermelding-NietCommercieel-GeenAfgeleideWerken 4.0 Internationaal] licentie. 

Persistent Infection Page[new][edit source][reply]

So great to see you here! I think it would be useful to create a page on persistent infection that has sections re: the ways (and evidence) for persistent infection in different families of viruses (and perhaps other pathogens) that also links to the main pages for those viruses. We could use this page: https://me-pedia.org/wiki/Persistent_infection_hypothesis or create a page on persistent infection that is a bit broader and not specifically about the evidence for/against its role in ME/CFS. I propose the latter. https://me-pedia.org/wiki/Persistent_infection --JenB (talk) 09:53, 20 February 2019 (EST)

Good to see you back! I'll take your suggestion and go with the latter page. Please be patient, it may take me a while, but I'll get there eventually.
Pyrrhus (talk) 22:09, 20 February 2019 (EST)

Citoid version -- notjusttired (talk) 05:42, July 16, 2019 (EDT)[new][edit source][reply]

Hi. Can you explain how Citoid fixed work? Does the extension need updating to include them? How do we know which patches / fixes need a code update and which are for an external service? I noticed some fixed are labeled as waiting for deploy notjusttired (talk) 05:42, July 16, 2019 (EDT)

I can share my understanding, but my understanding may be incomplete:
    • There is an external citoid server which performs the actual conversion from URL to citation.
    • The citoid extension mostly exists just to connect the VisualEditor to the external citoid server.
    • The default citoid server that the citoid extension connects to is probably https://en.wikipedia.org/api/rest_v1/#!/Citation/getCitation but I'm not sure about that. Thanks to the Wikimedia Foundation for providing this free service.
    • Zotero is a non-profit that develops citation management software that includes a "Translation server" to convert URL's to citations.
    • Wikimedia Foundation has adapted Zotero's "Translation server" as the code for the citoid server.
    • Although the non-profit Zotero frequently updates their "Translation server", Wikimedia Foundation doesn't implement the updates that frequently. More info: https://www.mediawiki.org/wiki/Citoid/Determining_if_a_URL_has_a_translator_in_Zotero
    • Wikimedia Foundation currently stores their citoid server code on Phabricator: https://phabricator.wikimedia.org/project/profile/62/
    • I assume that when a bug on Phabricator is moved from "Waiting for deploy" to "Resolved", it means that the fix has been deployed from Phabricator to the external citoid server.
    • The Citoid extension should only be updated when the MediaWiki software itself is updated, as each version of MediaWiki requires its own version of the citoid extension.
Hope this helps
Pyrrhus (talk) 23:34, July 17, 2019 (EDT)


old messages[new][edit source][reply]

old messages

File upload bug[new][edit source][reply]

I'm not seeing this issue. Does refresh / reload the page show the newer version? Is it only the thumbnail that is incorrect, rather than the enlarged image when you click on it? There might be a configuration setting that could be set to an hour instead. ~Njt (talk) 19:06, November 3, 2019 (EST)

Njt Go to this page to see the problem: File:ME-CFS-neutological-not-MUS.jpg. The page makes it look like there is no difference between the version that you uploaded and the version that I uploaded over a week ago. (The version that you uploaded says "ME-pedia.org" at the bottom and the version that I uploaded says "Quote: Action for ME, Image: ME-pedia.org". Fortunately, the image shows up correctly on the mainspace pages. (This is the second time I have noticed this bug.)
Pyrrhus (talk) 20:07, November 3, 2019 (EST)
Now I am going to try including the image in this page to see which version shows up: Pyrrhus (talk) 20:09, November 3, 2019 (EST)

--content removed--

I only see the newest version for each. You may want to check another browser, or your browser settings in case it is caching files for some time. ~Njt (talk) 09:28, November 4, 2019 (EST)
You're right Njt, I only see this problem in my browser that uploaded the new version, not in other browsers. I'll go update the bug report.
Pyrrhus (talk) 13:29, November 4, 2019 (EST)

New copyright system messages[new][edit source][reply]

We already have translations for nearly all of these as system messages, from the Wikimedia messages pack, as used by Template:CC-by-sa-layout and Template:Cc-by-layout. Translations are in many languages, not just the ones we added individually. User:Pyrrhus

See also MediaWiki_talk:Copyright-used-with-permission#Low_priority_tasks and wm-licenses messages 11:26, October 31, 2019 (EDT)

Great! Thanks User:Notjusttired for reminding me where those messages were! I was just copying from your MediaWiki:Licenses/de, etc. (if you're curious, our previous attempts to use these messages were foiled by an extra whitespace that Karen accidentally inserted in MediaWiki:Licenses)
Pyrrhus (talk) 13:38, October 31, 2019 (EDT)
I thought a change was needed too - at the back end? Or did that get done? I remember you posting about it on Slack. I have not yet found a way to search for system messages in a way that brings up existing ones rather than just those that are changed. Going to create some talk pages for the more useful creative Commons license messages, then they are easier to find. ~Njt (talk) 18:05, October 31, 2019 (EDT)
As it turns out, no change was needed at the back end, we just had to avoid adding extra whitespace to MediaWiki:Licenses, that's all! Some of the above messages couldn't be used because they had links in them, and the links didn't show up correctly in the dropdown menu. Hope this helps. User:Notjusttired
Pyrrhus (talk) 13:34, November 3, 2019 (EST)
Argh! Frustrating! Glad it's sorted though. ~Njt (talk) 19:06, November 3, 2019 (EST)

Import messages for translations[new][edit source][reply]

I hope you are doing OK. When you are able to can you please do

Code can be found User_talk:Notjusttired/cleanup#Mediawiki:No-reason here and I have responded to / fixed the queries you had. Thanks ~Njt (talk) 15:22, October 21, 2019 (EDT)

I can't figure out what those four bullet points refer to. Can you separate those four requests into separate pages so I can figure out what you're talking about?
Pyrrhus (talk) 23:25, October 21, 2019 (EDT)
I made a link for each. I hope that's clearer now User:Pyrrhus ~Njt (talk) 11:52, October 22, 2019 (EDT)
I still can't figure out what they refer to. The first two links go to the same place, and the last two links go nowhere.
Pyrrhus (talk) 20:33, October 23, 2019 (EDT)

Easier translations[new][edit source][reply]

I have found a much quicker / easier way to import translations that does not involve creating code directly. It can only be done for standard messages like the pagetriage- ones. Basically it involves using [1] and pasting in the list of system messages, saving the file and doing an import of it. It will ask for an interwiki reference - if there isn’t one “tw” could be used. Below is a last of file names to paste into the Export box. The import with Special:Import. Any missing messages are skipped. I have split them into two lists to make the import more manageable. ~Njt (talk) 23:33, October 6, 2019 (EDT)

User:Pyrrhus this is ready to go now, I just added a few missing from last night's import. As before, it's best to copy from the page view rather than source editor. It should import 94. Thanks ~Njt (talk) 08:17, October 8, 2019 (EDT)
✓ Done 48 pages imported. Please check the imported pages to make sure all pages were imported correctly.
Pyrrhus (talk) 00:45, October 11, 2019 (EDT)
Thanks for doing both of those! There are 7 more that were either missed off the list or did not get imported. Can you do these in the same with, exporting from Transwiki.net then importing. ~Njt (talk) 20:07, October 11, 2019 (EDT)
✓ Done 5 pages imported. Please check the imported pages to make sure all pages were imported correctly.
Thank you, I've checked all these so now sorted. ~Njt (talk) 08:25, October 21, 2019 (EDT)

--content removed--

pl onwards to export/import[new][edit source][reply]

User:Pyrrhus This is ready to export from translatewiki using Special:Export, and then Special:Import. It's probably best to do in 2 different files so I put a gap in the middle. ~Njt (talk) 18:21, October 8, 2019 (EDT)

✓ Done 25 pages imported. Please review the pages to make sure that all pages were imported correctly.
Pyrrhus (talk) 00:51, October 11, 2019 (EDT)

--content removed--

Translations: Chinese[new][edit source][reply]

I just want to check on Chinese, you listed zh as a language we should translate all templates into, but I want to check if you actually mean zh-hant (Chinese traditional). I don't think there is a general "zh" for Chinese, I see zh-hant or zh-hans (Chinese Simplified) only in translatewiki. Zh-hant seems more widely used. Njt (talk) 17:52, September 25, 2019 (EDT)

Hi Njt. The prioritized language codes are listed here: mepedia:All_languages_codes#Prioritizing_languages_for_translation. Note that I recommend zh-hans, not zh-hant. Zh-hans is the written language used in mainland china and is understood by many chinese outside mainland china. Zh-hant, however, is used in taiwan and is not well known on mainland china. Zh-hant may appear to be used more, but that is only because taiwanese are more connected to the internet. I believe the taiwanese should be able to read zh-hans as well. That’s why I recommend zh-hans, not zh-hant. Also note that are also two written languages for norwegian as well. “nb” is bokmal, which is used by 80% of norwegians, and “nn” is nynorsk, which is the written language taught in schools and is used by about 20% of norwegians. Since all norwegians should be able to understand both nb and nn, it probably doesn’t matter which we use. Hope this helps.
Pyrrhus (talk) 18:50, September 25, 2019 (EDT)
Oh, and my father recommended some tips if you ever have to use automated translation: help:Foreign_languages#Tips.2Fcaution_regarding_automated_translation. Hope this helps Njt.
Pyrrhus (talk) 18:55, September 25, 2019 (EDT)
I read the opposite for Chinese, it's contradictory depending where you check online. I'm happy to do either though. If you could update the language codes referred to that would help. There is also no for Norwegian, which seems to have more translations on translatewiki.net. Can you again update for which you want using. Njt (talk) 19:03, September 25, 2019 (EDT)
Njt, in that case we should probably do both zh-hans and zh-hant, so no one can say that we are choosing sides in a political matter. Note that wikipedia accepts articles in either zh-hans or zh-hant, and then does an automatic conversion to make sure that all content is available in both zh-hans and zh-hant equally.
Pyrrhus (talk) 19:19, September 25, 2019 (EDT)
Ok, Njt now I’m confused. I just set my language preference to “zh” and everything showed up in “zh-hans”. Does MediaWiki treat “zh” as equal to “zh-hans”?
Pyrrhus (talk) 20:05, September 25, 2019 (EDT)
Someone on Wikipedia reported the same in July, and said it should fall back to zh-hant not zh-hans. Looks like a php change for fallback languages. To be honest I don't think it's worth getting into this. We should just decide on either zh-hant or zh-hans, plus which Norwegian one we want, and go with that. Users can let us know if there's a problem, but at the moment there aren't any pages translated into those languages. Also when the LocalizationUpdate extension is installed all all missing system messages that are available will be added. We only need to check what's missing after the extension is installed, I don't know when that will be. Njt (talk) 20:38, September 25, 2019 (EDT)
That makes sense, Njt. I’ll do both zh-hans and zh-hant, but if you want to just pick one, that makes sense, too. For norwegian, I’ll just do “no”, even though I have no idea if that means “nb” or “nn”. Thanks for raising this!
Pyrrhus (talk) 20:46, September 25, 2019 (EDT)
zh-hant plus no sounds good to me, with zh-hans being added (hopefully). Translatewiki has a lot of "no" translations. I have not seen any way to monitor language choices of users, but many browsers these days have Autotranslate features / extensions. Btw, the Cleanup templates will be taking some time to do, and rely on LocalizationUpdate plus some custom system messages I am creating. It's a lot of templates, a lot of languages for each, and categories for each template. So if I haven't updated the translation table it means that some aren't yet covered. Template_talk:Cleanup contains a lot of the new system message names, some like the Lqt_noreason just say non-specific things like "No reason given" and belong to am extension we don't plan to install. It means far less mistakes than the Google translate nightmare. Njt (talk) 20:58, September 25, 2019 (EDT)
Sounds good! Thanks!
Pyrrhus (talk) 21:19, September 25, 2019 (EDT)

System message suggestions -- notjusttired (talk) 16:21, August 15, 2019 (EDT)[new][edit source][reply]

  1. MediaWiki:Inputbox-searchfulltext translations already exist on MEpedia, this could be used for the Search everywhere box in the home page, if the English and English British ones were updated new the new wording.
  2. MediaWiki:Inputbox-tryexact transnational already exist for the second search button

notjusttired (talk) 16:21, August 15, 2019 (EDT)

Great finds! We should definitely use these!
Pyrrhus (talk) 22:47, August 15, 2019 (EDT)
  1. mediawiki:Gettingstarted-lightbulb-heading could be used for "Pages in need" translations https://www.mediawiki.org/wiki/MediaWiki:Gettingstarted-lightbulb-heading/fr
  2. MediaWiki:Externalguidance-machine-translation-contribute-link - Learn how to contribute - or MediaWiki:Externalguidance-specialpage-contribute-title Ways to contribute could be used for "How to contribute" - I can't see any translation for that so I assume it's not translated right now
Are you in favor of getting the LocalizationUpdate extension installed? It will automatically grab all translations for any system message we add in English, as long as we don't change the English wording. notjusttired (talk) 14:55, August 23, 2019 (EDT)
Ooh, that mediawiki:Gettingstarted-lightbulb-heading is a great find, let's definitely use all of those! I have added the LocalisationUpdate script to the DRAFT Developer tasks for the next round of developer tasks. I don't know how much of a load on the server the LocalisationUpdate script is, so I'll request it to run nightly, but we can also run it weekly if it causes performance problems. notjusttired
Pyrrhus (talk) 21:22, August 27, 2019 (EDT)
Translations won't be updated that often. I think it best to run the task interactively the first time, after that weekly at most. It will only grab messages that we already have an English version of. notjusttired (talk) 16:35, September 4, 2019 (EDT)

System messages to use[new][edit source][reply]

Instead of creating new system messages, these already exist on MEpedia and could be useful

Despite the fact the pages come up as red links all these already exist as system messages.

I haven't checked if these have translations, and I don't know which system message contains the disclaimer about medical advice or the heading message we customize. With the heading message, we can keep it in English so it's always up to update.

notjusttired (talk) 17:44, August 15, 2019 (EDT)

Great finds! Let's definitely use these! However, I can't find MediaWiki:Externalguidance-specialpage-contribute-title. Where did you see this one? I saw MediaWiki:Qbbrowse before, but it's magically disappeared now! Oh well, we can import those two from MediaWiki if we have to. As for the other customized interface messages, I will add them to the table in MEpedia:User interface translation.
Pyrrhus (talk) 22:57, August 15, 2019 (EDT)
Both are on Commons - Externalguidance-specialpage-contribute-title qbbrowse
Some system messages can't be exported with Special:Export because they come from extra language files added by particular extensions. The translations for those either need to be found by searching then adding one by one, or by finding the extension source code - but normally they are in over a dozen separate files eg en.json, de.json - I don't know an easy way to import from json either. notjusttired (talk) 15:05, August 23, 2019 (EDT)
Yeah, I noticed that too! Fortunately, the extension developers typically use translatewiki.net to create those .json files, so you may be able to export the messages from translatewiki.net. What I did for the sidebar translations was to first create an XML file by exporting from translatewiki.net, and then I did a find-and-replace to change the extension message names to our own message names: “qbbrowse” becomes “browse”, “Externalguidance-specialpage-contribute-title” becomes “become_an_editor”, etc. This way, if the extension developer later changes the message, it won’t affect us.
Pyrrhus (talk) 18:20, August 28, 2019 (EDT)

Collapsing lists[new][edit source][reply]

Hey, I noticed your query about collapsing lists and thought I'd leave you some links with info about formatting those in source editor as well as Wikipedia guidance on using them or not. It's not my area of expertise but generally speaking, I believe WP recommends against using them in mainspace (unless the collapsed/hidden info is truly only supplementary rather than essential to the topic) because of some accessibility issues, and that instead it's best to split off pages when lists become unwieldy. So that would recommend for making the Contents page into a clean list of major overhead categories, and then each would have a subpage. But, like I say, not usually among the questions I deal with so, yes, in case the details here can be of any use:

Hope that may be of help! Canele (talk) 19:25, 10 April 2019 (EDT)

Wow, that’s incredibly helpful! Thanks!
Pyrrhus (talk) 19:38, 10 April 2019 (EDT)
My pleasure! (Truth is I have considerably more wiki than ME/CFS expertise so if I can help out at least on that score, in terms of tools for organizing information and starting up basic pages that people with more scientific expertise may be able to come along behind and fill in a little more easily, well I'm just glad I can make a contribution.) Canele (talk) 00:56, 11 April 2019 (EDT)
Hi. Some time ago I copied collapsible list templates from several other wikis. It was a total nightmare to get them working to be honest but there's an example here:
Common_symptoms_in_ME/CFS#Long_list_of_symptoms
If they look expanded rather than collapsed by default then check my user CSS - it needed a few extra styles adding, I requested these to be added to the site Common.css but I can't remember if they were done or not. There's a similar thing on Template:Read_more - I was hoping to use it to partially hide the Quote field in certain references. The quote field might well increase visits since some of them are pretty controversial. E.g. Wessely contradicting his previous work then reverting back depending on the audience.
A search for Templates created in the last year will come up with a lot of those recently copied from WikiMedia's Commons or Wikipedia if you are looking for extra features. notjusttired (talk) 19:16, 11 April 2019 (EDT)
Thanks, Njt! That's certainly helpful. Sorry it was such a nightmare to get the collapsible lists working. But you gave me some good sources to investigate! Thanks.
Pyrrhus (talk) 20:07, 11 April 2019 (EDT)

Changes to Primers[new][edit source][reply]

Thanks for making clarity changes on the Primers. There are five Primers and if you could make the changes to all five, that would be helpful.

Primer for doctors and researchers

Primer for family, friends and care providers

Primer for journalists

Primer for patients

Primer for the public

--77.111.245.5 18:04, 15 February 2019 (EST)


Thanks for letting me know!

I'll go do that, and in the future I'll make changes to all 5 primers as appropriate.

Thanks.

Pyrrhus (talk) 18:45, 15 February 2019 (EST)

Add topic re updates[new][edit source][reply]

I made the changes you requested. Let me know if everything is to your liking. The programming work you have been doing has been outstanding! Thanks so much Kmdenmark (talk) 18:02, 17 May 2019 (EDT)

Pivot skin fixes[new][edit source][reply]

[new][edit source][reply]

Can you copy these to your pivot.css and see if they work on desktop / larger screens? Donate seems fine to me, I'm less sure on the footer bleed issue. Thanks notjusttired (talk) 08:03, 20 May 2019 (EDT)

Thanks User:Notjusttired! For some reason, the MediaWiki software refuses to recognize my pivot.css page as CSS code. Maybe I need the "editmycssjs" right given(?) Did you ever receive this user right? Or is the MediaWiki software just confused?
Pyrrhus (talk) 20:28, 20 May 2019 (EDT)
Never mind! I just went to Special:ChangeContentModel to specify that my pivot.css page is CSS code. Now I can see that the Donate button looks like a button again! Thanks! (But the footer still bleeds left.)
Pyrrhus (talk) 20:32, 20 May 2019 (EDT)
Strange problem with the CSS! Does the footer bleed less than before? How many characters wide is the box that bleeds? notjusttired (talk) 04:38, 21 May 2019 (EDT)
I just edited the footer code below, which should hopefully fix the issue. The powered by mediawiki logo I'm going to hide too. notjusttired (talk) 13:28, 21 May 2019 (EDT)
Thanks User:Notjusttired! The change doesn’t seem to have affected the footer row, it still bleeds as before :(
I love the idea of hiding the second column in that footer row, the column containing “Powered by MediaWiki”. That should give the first column more space to expand.
The first column in that footer row uses unordered lists to display the lines, which makes the text vertically long. Do you know if there is any CSS hack to make the list items display with inline flow, so the list items stack horizontally?
Pyrrhus (talk) 15:22, 21 May 2019 (EDT)
I guess try using !important on the footer margins (as below). If that doesn't work I'm stumped... although removing the background color/setting to the same as the side bar would probably make it look ok. I haven't been able to remove the "poweredbyico" - I think it needs doing in LocalSettings.php - but I am not sure if the space will be freed up that way. It might be better to put the MEAction logo in that space. There is a "hlist" class we already have for horizontal lists. I think it's in MediaWiki:Common.css, but you really would want to adapt that to use something other than commas to space things out. This hlist template could be copied over, we don't use our existing hlist template. To be honest though, Wikipedia and mediawiki look messy even on small screens. notjusttired (talk) 15:54, 21 May 2019 (EDT)
Thanks User:Notjusttired! I'll try that.
Pyrrhus (talk) 16:15, 21 May 2019 (EDT)
Holy S**t, User:Notjusttired! That fixed it. Just adding "!important" made the footer no longer bleed into the sidebar! Great hack!
Pyrrhus (talk) 16:20, 21 May 2019 (EDT)
/* fix footer bleed by fixing negative padding   */
footer { margin-left: 0!important; margin-right: 0!important;}

/* make donate look like button */
#n-donate {
 margin-left: 0.25em;
}
#n-donate a {
 display:inline-block;
}

Centering footer[new][edit source][reply]

Powered by was actually under the test of the footer and is finally hidden. Disclaimers and Cookie statement had both been given a line each, I've moved them to the same line. They don't seem to join with the previous line though. Adding some centering too. The footer always begins right of the sidebar too. notjusttired (talk) 17:33, 21 May 2019 (EDT)

#footer-developers,
 #footer-cookiestatement {
 padding-right: 2rem;
 display: inline;
 text-align: center;
} 
#footer-left,
 #footer-places,
 #footer-disclaimers,
 #footer-privacypolicy,
 #footer-about {
  display: inline;
  text-align: center;
}
/* removed powered by mediawiki - which has several different names oddly */
#footer-poweredbyico,
 #footer-poweredby,
.poweredby { 
   display:none; 
}
/* center block - won't overlap sidebar */
#footer-left {
 display: inline-block;
 width: 100%!important;
 text-align: center;
 padding-right:8px;
}
This looks great, User:Notjusttired! Could you take a look at the CSS I am testing? (Below). Maybe this can be merged with the code above? I’m still not sure if I like the footer text centered or not... Thanks!
Pyrrhus (talk) 19:38, 21 May 2019 (EDT)
/* UNTESTED CODE */

/* make donate look like button */
#n-donate {
 margin-left: 0.25em;
}
#n-donate a {
 display:inline-block;
}

/* center donate button in sidebar */
#n-donate {
 text-align: center;
}

/* fix footer bleed by fixing negative padding   */
footer { margin-left: 0!important; margin-right: 0!important;}

/* expand footer-left and hide footer-right */
#footer-right-icons {
 display: none;
}
#div-footer-left {
 width: 100%;
}

/* make text lines into a paragraph */
li#footer-lastmod,
 li#footer-viewcount {
 float: left;
 margin-right: 0.5em;
}

/* make links all in a row */
li#footer-privacy,
 li#footer-about,
 li#footer-disclaimer,
 li#footer-developers,
 li#footer-cookiestatement {
 float: left;
 margin-right: 2em;
}

/* center footer text */
ul#footer-left {
 text-align: center;
}

/* END UNTESTED CODE */

Disambiguation template and __DISAMBIG__[new][edit source][reply]

Hi. The disambiguation template already includes the magic word __DISAMBIG__ so there's no need to add it. A page containing {{disambiguation}} means add the contents of the disambiguation page, including any magic words that are in it. (Three curly brackets {{{ }}} around something pass a parameter value into any templates, in case you see that. notjusttired (talk) 09:03, 24 May 2019 (EDT)

Excellent, that’s good to know! I’ll go fix the documentation to make it clear that only the {{Disambiguation}} is required. Thanks for catching that!
Pyrrhus (talk) 12:39, May 24, 2019 (EDT)

-- notjusttired (talk) 21:08, June 2, 2019 (EDT)[new][edit source][reply]

Hi. Check out MediaWiki_talk:Vector.css - now with the "What is this page?" info put in a template. Any template can be added to a page using {{ }} - just like you would if marking a page as a stub. The remaining bits are the parameters (values passed in that control what it does) eg {{lowercase|HELLO}} would use a template called "lowercase" and pass it the parameter {{{1}}} (1 - with 3 curly brackets) - which would have the value HELLO. Some templates to check out are Template:Tmbox and Template:imbox - of documentation is missing you can find it on the same pages at wikimedia Commons or Wikipedia.
Anything in the "noinclude" tags is not displayed - so that's a great place to add categories or instructions.
Advantages are less repeateding of the same info, so easier to update just one version, and easier to skip over the template description of you know what it does, and they can automatically be added to categories at the same time. Also - with CSS there is also the option to have user css. Hope this is helpful. notjusttired (talk) 21:08, June 2, 2019 (EDT)

I saw that! Very cool! I read the doc on Imbox, it could come in very helpful. Thanks for the great info!
Pyrrhus (talk) 23:36, June 2, 2019 (EDT)

Pivot code[new][edit source][reply]

If you have time can you give this a test. Should change small screens to call the website #MEPEDIA not MEPEDIA. Also a small layout change for main page too. Thanks for your last feedback on pivot. Many changes to follow yet on Timeless - mostly for editing tools and pages used by editors. Surprisingly timeless does not allow mobile users to edit on Wikipedia - lots of layout issues for mobiles. notjusttired (talk) 19:34, June 9, 2019 (EDT)

Done. The “#” is showing up correctly. Haven’t noticed any changes on the main page, but I’m not sure what I should be looking for...
Pyrrhus (talk) 19:15, June 10, 2019 (EDT)

section#middle-nav .title a::before { 
  content: "#";
  font-family: Oswald, sans-serif;
  font-style: italic;
  font-variant: normal;
  margin-right: -0.15em;
}

.mw-body li.gallerybox div.thumb {
 padding: 0;
}

/* main page centering contents list in wikitable at top */

.wikitable > * th > p { 
 text-align: center;
}

out of date extensions -- notjusttired (talk) 07:06, July 16, 2019 (EDT)[new][edit source][reply]

Some particular ones that look worth upgrading:

  • citoid (possibly wait for next release)
  • codeeditor - icon changes that look relevant to the mobile improving I'm making on skins, use WikiEditor toggle tool
  • disambiguator - remove disambiguator pages from Special:AncientPages
  • scribunto - works the Lua modules, although I don't see any particular bug fix that's relevant
  • categorytree - fix categories with numeric names, this extension is key for searches etc although didn't see any important fix
  • parserfunctions - really key extension used in many templates
  • graph - icon changes and other fixes, I think this is worth doing
  • templatedata - don't see anything worth updating this for but obviously it's well used
  • hitcounter - number of views out if date
  • pagesimages - images not always showing
  • smitespam - couldn't see any particular change, User:Kmdenmark mentioned it often flags images but an upgrade may not fix this
  • dismissablesitnotice - use session storage instead of cookies

These seem worth doing before the upgrade of MediaWiki. Obviously there's an argument for updating every extension to the latest version rather than just these. Most include many translation or localization updates. Some are clearly going to be very low priority. Most date from September 2017 - Special:Version Thoughts? 07:06, July 16, 2019 (EDT)

Any extension with a “compatibility policy” of “release branches” must be updated with any new version of MediaWiki. These include Echo, Scribunto, TemplateData, PageImages, Citoid, VisualEditor. So we can't update those extensions until we update the MediaWiki software.
Some of the others might be worth updating but since they released MediaWiki version 1.33 they are no longer offering downloads for our version of MediaWiki, so these will also have to wait until MEdiaWiki is updated. (I don't think codeeditor or smitespam are important enough to update.) Hope this helps.
Pyrrhus (talk) 23:58, July 17, 2019 (EDT)

Pages in need - Articles needing an image[new][edit source][reply]

Articles needing an image is currently not helpful / too hard to see what's important or what to focus on. I thought it might be helpful to split this page into sections by main category (researchers, treatments etc) and have longest pages listed first.

I wondered if you wanted to update this, link to escape codes below. Perhaps the first 10 longest posts at the top of the page, then subheadings for researchers, potential treatments, etc, the contents would let people jump to the category they are interested in User:Notjusttired#Pages_in_need

I don’t understand what you’re trying to say/ask, so I copied your code to the page: Category:Articles that need an image or photo. I hope that’s what you meant.
Pyrrhus (talk) 22:14, August 9, 2019 (EDT)

Translations to check -- notjusttired (talk) 19:20, August 23, 2019 (EDT)[new][edit source][reply]

I think I remember you you speak some German or other languages. If you are able to check any of these that would be great. Particularly I wouldn't want them to accidentally read "no cleanup has been specified / provided " - they should say "No reason given." and be part of the message on the cleanup template, underneath "this page may require a cleanup". I don't remember which languages you speak so have included them all notjusttired (talk) 19:20, August 23, 2019 (EDT)

  • No reason given.
  • No reason given.
  • No reason given.
  • No reason given.
I'm not a native speaker of any of those, but if I had to translate it into spanish and german myself, I would say:
    • Spanish: No se proporcionó ninguna razón para las correcciones.
    • German: Es wurde kein Grund für die Korrektur angegeben.
Hope this helps!
Pyrrhus (talk) 21:51, August 27, 2019 (EDT)

Category split[new][edit source][reply]

Hi, I have opened a discussion at Category talk:People with ME, CFS, and/or FMS. Guido den Broeder (talk) 20:40, September 2, 2019 (EDT)

Teamwork[new][edit source][reply]

Hi, it is probably worth mentioning somewhere that the ME/CVS-Stichting, the ME/cvs Vereniging and the Steungroep ME en Arbeidsongeschiktheid usually work in concert. (That way they get 3-6 people at the table to one or none from the ME Vereniging Nederland, rendering ME advocacy in the Netherlands an uphill battle.) Guido den Broeder (talk) 05:26, September 12, 2019 (EDT)

upload of language file -- Kmdenmark (talk) 15:40, September 12, 2019 (EDT)[new][edit source][reply]

The file upload worked!!!!! (Hopefully) Let me know if this meets your needs. Kmdenmark (talk) 15:40, September 12, 2019 (EDT)

Guidelines and policies -- Njt (talk) 21:56, September 20, 2019 (EDT)[new][edit source][reply]

Hi. A number of different templates, system messages and possibly Modules refer to Category:MEpedia guidelines, or possibly Category:MEpedia documentation - can we instead just add new policies to the existing guidelines instead? Or list then there. It will be a lot of work to find all the links and will take some time to get everything working without it. Njt (talk) 21:56, September 20, 2019 (EDT)

Hi Njt. The template, messages, etc that I know of that link to guidelines probably don't need to refer to our policies as well. Policies are generally legal/bureaucratic matters, unrelated to routine editing issues. Can you think of any templates, messages, etc that would need to refer to policies? I thought about creating a combined "Guidelines and policies" category, but decided against it because people don't need to constantly refer back to the policies like they have to refer back to the guidelines. I have created links to our policies category from the guidelines category and from the tutorial, so the policies should be easy to find from there if need be. Maybe I'll add a link from the Help category as well. But I am certainly open to considering other alternatives...
Oh, and by the way, I changed Module:Asbox so that stubs in the "Help:" and "MEpedia:" namespaces are finally also added to the "Stubs" category! After the DynamicPageList 24-hour delay, they should begin showing up in lists of stub pages...
Pyrrhus (talk) 22:22, September 20, 2019 (EDT)
Sounds good! For some reason I thought you were renaming the guidelines categories rather than the policies. Btw: I have found a system message translation for "stub" at last, although we've done several languages already . XML import works so I think that will keep me busy for a while. Njt (talk) 19:14, September 21, 2019 (EDT)

ME/CFS - An acronym that combines myalgic encephalomyelitis with chronic fatigue syndrome. Sometimes they are combined because people have trouble distinguishing one from the other. Sometimes they are combined because people see them as synonyms of each other.

Myalgic encephalomyelitis (ME) - A disease often marked by neurological symptoms, but fatigue is sometimes a symptom as well. Some diagnostic criteria distinguish it from chronic fatigue syndrome, while other diagnostic criteria consider it to be a synonym for chronic fatigue syndrome. A defining characteristic of ME is post-exertional malaise (PEM), or post-exertional neuroimmune exhaustion (PENE), which is a notable exacerbation of symptoms brought on by small exertions. PEM can last for days or weeks. Symptoms can include cognitive impairments, muscle pain (myalgia), trouble remaining upright (orthostatic intolerance), sleep abnormalities, and gastro-intestinal impairments, among others. An estimated 25% of those suffering from ME are housebound or bedbound. The World Health Organization (WHO) classifies ME as a neurological disease.

The information provided at this site is not intended to diagnose or treat any illness.
From MEpedia, a crowd-sourced encyclopedia of ME and CFS science and history.