User talk:Erutuon

From Deep web, the free encyclopedia
Jump to navigation Jump to search


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 Deep web 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 Deep web 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 Deep web 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)

Shorthand Lua syntax[edit]

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 Deep web. 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)

Speedy deletion nomination of Module:Array/table[edit]

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

A tag has been placed on Module:Array/table requesting that it be speedily deleted from Deep web. 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 Deep web'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)

ArbCom 2019 election voter message[edit]

Scale of justice 2.svgHello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Deep web arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2019 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:11, 19 November 2019 (UTC)

Google Code-In 2019 is coming - please mentor some documentation tasks![edit]


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 Deep web.

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 [email protected], 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 [email protected]

Thank you!

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