User talk:Erutuon/2019

Hello, Erutuon. I just wanted to let you know that Draft:List of Minnesota wildflowers by family, a page you created, has not been edited in at least 5 months. Draft space is not an indefinite storage location for content that is not appropriate for article space.

If your submission is not edited soon, it could be nominated for deletion under CSD G13. If you would like to attempt to save it, you will need to improve it. You may request userfication of the content if it meets requirements.

If the deletion has already occured, instructions on how you may be able to retrieve it are available here.

Thank you for your submission to Wikipedia. Bot0612 (talk) 00:03, 15 January 2019 (UTC)

Hello, Erutuon. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "Pinus subsection Gerardianae".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. Hhkohh (talk) 08:12, 10 February 2019 (UTC)

Hello, Erutuon. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "List of Minnesota wildflowers by family".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. DannyS712 (talk) 08:08, 13 February 2019 (UTC)

Module:Wiktionary has been nominated for deletion. You are invited to comment on the discussion at the module's entry on the Templates for discussion page. {{3x|p}}ery (talk) 02:36, 19 February 2019 (UTC)

Module:Glossing abbreviations has been nominated for deletion. You are invited to comment on the discussion at the module's entry on the Templates for discussion page. {{3x|p}}ery (talk) 03:09, 1 March 2019 (UTC)

Template:Average temperature table has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Zackmann (^{Talk to me}/_{What I been doing}) 23:08, 8 March 2019 (UTC)

Hi there, this is firstly a quick thank you for the recordings of Latin words you have done, we are using your audio on the Latin course at Wikiversity. If you felt like doing some more, we'd be very grateful! This is just to put the idea into your head: I am looking for volunteers both for words and sentences. Jim Killock (talk) 15:00, 5 April 2019 (UTC)

Module:Ancient Greek has been nominated for merging with Module:Ancient Greek (ALA-LC). You are invited to comment on the discussion at the module's entry on the Templates for discussion page. Thank you. {{3x|p}}ery (talk) 20:27, 9 April 2019 (UTC)

Hi Erutuon. Thanks for your help with Module:Ancient Greek. I noticed your Template:Grc and had a couple of ideas:

1. Is is possible to make it reversible? I made Template:ISO 843 a while ago, which basically does the same thing but not as well. If you know how to make yours reversible, mine could be redirected to yours. I made it primarily for another template which is now broken – I won't need to fix it if your template supersedes it.
2. Could it be used for all versions of the Greek alphabet (i.e. Modern Greek too)? If so, it could be moved to Template:Grek, which is currently a redirect to mine. (Grek is the ISO code for the Greek alphabet, which seems to suit the point of the template more than the code for the Ancient Greek language.) That would be helpful to me as I would like to use the name Template:Grc for another template – since there are no transclusions, it doesn't seem like it would cause any problems.

Cheers, M.Clay1 (talk) 06:52, 23 April 2019 (UTC)

It's not simple to reverse the function in Module:Ancient Greek/typing that is used by {{grc}}, but how would the reversed version be used? I don't see any actual uses of {{ISO 843}}; was it mean to be substituted?

Modern Greek uses a subset of the characters used by Ancient Greek, so {{grc}} could be used for either. What use for {{grc}} are you envisioning? — Eru·tuon 07:14, 23 April 2019 (UTC)

{{ISO 843}} is used in {{Grek-Latn}}, which doesn't work properly anymore and is redundant now that modules can do the job much better. It was basically just for transliterating Greek letters to Latin letters and vice versa (I never ended up implementing it in a useful way). The point of the reversal was so that you could input the transliteration, e.g. Zeús, and it would output the Greek (Ζεύς), which is often easier than using Greek letters. That's useful when you need to use a Greek term in a sentence but don't know the Greek alphabet (the downside is that you still need to know the diacritics in the transliteration). Either way, the idea is that you only need to enter one version to get both, and the other would be displayed in brackets.

I believe grc is the code for the Ancient Greek language, not its alphabet, so it doesn't apply to Modern Greek.

I made this template: {{transl-grc}}. I wanted another template the same as {{grc-transl}} but using the ALA-LC transliteration that is commonly used on Wikipedia (to replace my old redundant templates). It would be simpler than having to use {{grc-transl}} plus a parameter, which would create a lot of extra characters when used many times in an article and would be confusing to most editors who are not familiar with these templates. I haven't decided which template should be called {{grc}} and which should be called {{transl-grc}}. If a template is going to be used a lot, a short name is helpful. M.Clay1 (talk) 14:01, 27 April 2019 (UTC)

Sorry, what I meant was that the function currently invoked by {{grc}} can be used for Modern Greek, not that the name is appropriate. — Eru·tuon 17:36, 27 April 2019 (UTC)

If a template that does the sort of conversion that you describe, from Zeús to Ζεύς, would be useful, I can write a module function to do that. I doubt that I would use it myself, because usually I type Greek using the Beta-Code-like transliteration (Zeu/s). — Eru·tuon 20:14, 27 April 2019 (UTC)

I think it would be useful, if only because most people would be more likely to know only the common transliteration. I often see transliterations in articles with no Greek text – such a template would be an easy way to add the Greek in. M.Clay1 (talk) 12:16, 3 May 2019 (UTC)

Hello Erutuon. I added some sources in that page. The word baleine is pronounced differently at different regions, it's true, please don't remove them, thank you. 138.229.19.202 (talk) 13:46, 16 June 2019 (UTC)

• France [kanada] :
• Québec [kanadɑ] :

Hello Erutuon. In the article of Canada, there is only the French audio, but the Quebec one is not there, can you change it please? 138.229.19.202 (talk) 14:24, 15 July 2019 (UTC)

Sorry, I'm not interested in doing edits on your behalf. Please bring this up on the talk page of Canada. — Eru·tuon 17:11, 15 July 2019 (UTC)

Can you please tell me more about the deprecation of the nowrap attribute? Thanks! —GoldRingChip 20:28, 15 July 2019 (UTC)

@GoldRingChip: Well, it's not included in HTML5 (try searching the HTML5 specification and see W3Schools) and I couldn't find a mention of it on MDN at all (for instance, it isn't in MDN's HTML attribute reference). I don't know what version of HTML included it or when it was removed. — Eru·tuon 21:13, 15 July 2019 (UTC)

Oh! I see… thanks! That's a bit far-afield for me. Can you direct me to a Wikipedia reference that it shouldn't be used, like in a manual of style or such? —GoldRingChip 01:48, 16 July 2019 (UTC)

@GoldRingChip: I don't know if it's explicitly discouraged by Wikipedia policy, but several of the other deprecated or obsolete styling-related HTML attributes are often replaced with inline CSS; align and valign and bgcolor for instance. I found a reference to the nowrap attribute at Help:HTML in wikitext#table, td, tr, where it is noted as "allowed [by the MediaWiki parser, I guess] but obsolete". I'd never seen it in wikitext before today. — Eru·tuon 02:38, 16 July 2019 (UTC)

IPNI have updated their website and the URLs to be used. See also my comments at Wikipedia talk:WikiProject Plants#IPNI have updated their website. This meant that although the 'main' URLs generated by {{IPNI}} redirected correctly, some didn't. I've fixed the template (although the coding can be made more succinct, I think) and updated the documentation.

I have followed {{Taxonbar}} in deprecating picking up the ID from Wikidata. Apologies if you are well aware of the following. What has become even clearer over the years is that the limitations of Wikidata in its handling of taxon items means that it's unwise to rely on information there. We regularly have to choose between linking to the Wikidata taxon item with the same taxon name that we use, and then losing links to other language wikis, or linking to the most popular Wikidata taxon item with a synonymous taxon name, so obtaining the inter-wiki links, but messing up the taxonbar and any other code that obtains an ID and taxon name from Wikidata. The other issue is monotypic taxa, where Wikidata has multiple items and we have one article, but N:1 links are not allowed in Wikidata. Sigh... Peter coxhead (talk) 10:09, 21 July 2019 (UTC)

Clearly you're more fluent in it than I am, so thank you for changing e.g. string.lower(s) to s:lower(). Any idea why changing table.concat(t) to t:concat(), on the other hand, fails ("attempt to call method 'concat' (a nil value)")? ―cobaltcigs 20:43, 17 September 2019 (UTC)

@Cobaltcigs: It's because all strings have a metatable with the value of the __index field equivalent to the string library (roughly as mentioned here, except that in Scribunto the __index value is a copy of the string library and can't be modified), so strings can access string functions as methods, whereas a new table doesn't have a metatable unless you add one. You can make the table library functions available as methods on a table by using setmetatable (local t = setmetatable({}, { __index = table })), or you could use my module, Module:Array, which has other methods that might be useful (see Module:Array/testcases for examples). — Eru·tuon 22:18, 17 September 2019 (UTC)

Wow. Sounds like that means (a) this is not actually analogous to either Javascript prototypes or C# extension methods, (b) it would only affect the behavior of table instances constructed in this specific manner, and (c) it's not possible to direct all strings to use the utf8-aware mw.ustring operations by default. :/ ―cobaltcigs 13:12, 18 September 2019 (UTC)

Well, JavaScript prototypes are fairly similar to Lua metatables, more so (I hear) than class-based object-orientation. JavaScript adds a prototype to {} while Lua doesn't add a metatable; the rough equivalent of Lua {} would be JavaScript Object.create(null).

I guess using the string functions is for compatibility with vanilla Lua. Fortunately, they have better performance than the UTF-8-aware mw.ustring functions, which call into PHP, though that matters more often in Wiktionary than Wikipedia. It would be cool if the mw.ustring functions were available as well, though: for instance, if ("æ"):ustringUpper() were equivalent to mw.ustring.upper("æ"). But I doubt the MediaWiki developers would go for that. — Eru·tuon 18:05, 18 September 2019 (UTC)

A tag has been placed on Module:Array/table requesting that it be speedily deleted from Wikipedia. This has been done under section G4 of the criteria for speedy deletion, because the page appears to be a repost of material that was previously deleted following a deletion discussion, such as at Articles for deletion. When a page has substantially identical content to that of a page deleted after a discussion, and any changes in the content do not address the reasons for which the material was previously deleted, it may be deleted at any time.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. * Pppery * _{it has begun...} 21:47, 22 September 2019 (UTC)

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at the English Wikipedia.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 21:58, 23 November 2019 (UTC)