All The Tropes Wiki Project, Part XXI

[Bob Schroeck]

Beach-bound and bouncy?

Out of the water, into our hearts?

[LulzKiller]

How do you use the quote template for quotes between multiple characters? per the wikiquote cleanup?

[LulzKiller]

BTW I did a major step towards cleaning up the Smash Bros page by giving Brawl its own page on the wiki along with moving all subspace emissary examples onto the relevant subpages.

[Black Aeronaut]

Ursula Andress in Dr. No.
Halle Berry in Die Another Day.
Daniel Craig in Casino Royale.
Heather Graham in Austin Powers: The Spy Who Shagged Me.

Somebody walks out of the water, providing Fan Service.

What do we call this trope? (I know what Wikipedia calls it.)

Sexy Swimsuit Service

Descriptive, alliterative, and references Misato Katsuragi going "Service!  Service!" in the next episode previews of NGE.

EDIT: For another dimension of fun, it can be shortened to SSS... like so. "Whew! That swimsuit scene was Triple-S-Rank!"

[robkelk]

How do you use the quote template for quotes between multiple characters? per the wikiquote cleanup?

Manually, like so:

{{quote|'''Sex-shop clerk''': Is this some kind of bust?
'''Lt. Frank Drebin''': It's very impressive.}}

[robkelk]

What trope would this Bob Dylan reference come under? also potentially the fact the wind is forcing them to grab on for dear life?

The wind part is probably Hostile Weather, I think. (I don't see anything more appropriate in this category.)

[LulzKiller]

I mean more specifically the fact that Bob Dylan was referenced in something that matched the song with a visual reference (they're blowing in the wind, the song blowin in the wind)

[robkelk]

In case anybody is wondering why we have a Community Portal where we list things that need to be fixed, instead of just watching the films/shows/cartoons / reading the books/comics and doing the fixes ourselves, I've added this to the top of the Community Portal.

As for why we have these lists instead of simply fixing problems ourselves:

If a person takes in one work of fiction each week (that means, for example, reading an entire novel series or marathoning an entire television series or an entire web comic run, not reading a single book, watching a single episode, or reading a single strip), and that person has 80 years in which he or she can understand and appreciate fiction between becoming literate and becoming senile, then that person can experience 4,160 works - assuming the person never repeats a favourite work.

As of August 29, 2021, this wiki listed 6,375 pages in Category:Film. another 2,912 pages in Category:Literature and more works in the categories for the other media that we cover here.

This means that it is impossible for a single person to experience all works of fiction (without substantial life extension measures that do not appear to be forthcoming any time soon). It's simple grade-school math.

So, no, we cannot go and read or watch it ourselves - life is literally too short for that to be possible. We must rely on people reading and acting on these lists in order to alert people who are already familiar with the works in question that there's an issue.

[robkelk]

I mean more specifically the fact that Bob Dylan was referenced in something that matched the song with a visual reference (they're blowing in the wind, the song blowin in the wind)

Wouldn't that be a Shout-Out?

[LulzKiller]

I mean more specifically the fact that Bob Dylan was referenced in something that matched the song with a visual reference (they're blowing in the wind, the song blowin in the wind)

Wouldn't that be a Shout-Out?

I was thinking that, but when I got confused because that's a category? and is a separate subpage rather than a trope on the mainpage, unless I'm missing something?

[GethN7]

Leaving a note here because I did some changes to fix some busted CSS issues with some of our imported Wikimedia Foundation templates that requires enabling the TemplateStyles extension (this was absolutely necessary because they make use of its parser hooks), else some of our imports have busted code all over the place.

https://www.mediawiki.org/wiki/Extension:TemplateStyles

I do want to add this to fix further issues, but since it opens up another potential content issue going forward, stopping to address that before getting the green light:

https://www.mediawiki.org/wiki/Extension:Translate

This is also extensively called by many of our WMF import templates and modules, but it has another useful purpose that our bilingual editors will appreciate like Rob.

Example

https://allthetropes.org/wiki/Fr/Canada,_Eh%3F

The Translate extension provides a full-featured way to make sure our foreign language pages are kept in orderly sync with our English language pages and encourages those who are wanting to translate our pages to do so in other languages by means of an extension that provides tools to ensure our foreign language pages are created in an orderly fashion.

An example of how they organize foreign language pages can be seen here:

https://www.mediawiki.org/wiki/Extension:Translate/fr

I see no reason we should not have this. It puts us on par with TV Tropes' support of foreign language pages while providing far superior tools and backend support that is kept current with the MediaWiki core and nigh all known extensions. It will not cause us any great issues with our existing content while allowing foreign language pages to be maintained in a far more orderly fashion. We may need to migrate foreign language pages to conform with Translate extensions standards (which is easily done with a page move), but that is all.

Miraheze's own Meta wiki even uses it for similar purposes, so this has excellent precedent for being a wise idea.

However, I'd like opinions before going further.

P.S. - implementing this on pages can be done manually, but with a few minor additions of some parser tags on some of our templates, we can automatically apply Translation capability to almost all content pages, and likely other pages that use our boilerplates, though adding translation markup manually is still a valid option for pages that do not fit Main namespace standards or lack templates at top and bottom of pages we can modify to auto-add translation capability to.

Basic layout and description of how this works here: https://www.mediawiki.org/wiki/Help:Exte...on_example

Companion extension to apply with this proposal so translators can receive notifications and keep each other apprised of them so they can be more efficient:

https://www.mediawiki.org/wiki/Extension...ifications

[robkelk]

I'm actually not bilingual... so, carry on.

[GethN7]

I'm actually not bilingual... so, carry on.

My mistake. Canada is a bilingual country speaking French and English, so I apologize for any presumption.

That said, I believe the above stated will be of massive benefit to non-English speakers who wish to trope and easier on us keeping it organized.

Also, technical note for admins:

https://allthetropes.org/wiki/Special:Log/contentmodel

Some imported CSS pages we use for Module pages may need conversion to "Sanitized CSS" to work properly, they are typically imported in plaintext, which has broken formatting. I have fixed all known CSS style sheets with this problem, just something to keep in mind going forward.

[Bob Schroeck]

In case anybody is wondering why we have a Community Portal where we list things that need to be fixed, instead of just watching the films/shows/cartoons / reading the books/comics and doing the fixes ourselves, I've added this to the top of the Community Portal.

<snip>

So, no, we cannot go and read or watch it ourselves - life is literally too short for that to be possible. We must rely on people reading and acting on these lists in order to alert people who are already familiar with the works in question that there's an issue.

Bravo.

[Bob Schroeck]

Geth, I have no problems with you proceeding to either maintain existing/needed functionality, nor with you implementing the improved foreign language support. (As long as the latter doesn't break anything, of course. <grin>)

[GethN7]

Geth, I have no problems with you proceeding to either maintain existing/needed functionality, nor with you implementing the improved foreign language support.  (As long as the latter doesn't break anything, of course.  <grin>)

Done. I have added the markup, for now, to this page

https://allthetropes.org/wiki/Main_Page

Any new translations will be added to the language selection box at the top that the extension will create automatically, and users can select translations at will. For example, if a page has English, French, and German translations, they can click the language they prefer and switch back at any time. If they default their preferred language via the selector next to their user name to a certain language, any pages serving their preferred language will be provided first for their convenience.

I also intend to eventually add this functionality to the Trope, Work, and Creator pages via adding the top required parser tags to their templates and the bottom end parser tags to the reflist template. All usage of these templates would thus automatically mark all these pages as being able to be translated. More can be added over time, but that was initially proposed pages that would most benefit from this. I do not forsee this causing any major issues, given how those templates are always used in tandem, worst error we might see is stray parser tagging at top or bottom of pages.

I have not set user permissions for translation, it defaults to administrators for now, but I propose all trusted editors be given this right by default.

[Labster]

It looks fine to me -- enabling translation extension won't cost us very much, though I don't expect the feature to be in widespread use, ever.

[GethN7]

Well, had to scratch modifying templates to auto-add translate parser tags, this can cause issues so they have to be added manually, which is likely a better thing in hindsight.

Modified the MediaWiki:Edittools to include all the needed CharInsert markup so they can be added to pages with a few clicks. I removed the emoticons (I added that a long time ago, they are practically never used) to keep the CharInsert bar from getting too big.

This is still restricted to admins only, but before we allowed trusted users translate rights, I believe it may be necessary to make a best practices page for how we use them, especially for TV Tropes users making the jump (They have page names with the country markup in front like Fr/Canada, Eh", Translate has that in reverse).

It's possible to port all of the old ones from the original dump as a base, we'd just need to rename them to conform to the new name standards, or we could just start fresh if need be.

[LulzKiller]

Not against adding translation features.

Who's Gani and why are they adding SQL code in blogposts?

Code:

<vote />
    +    
<!--start text-->
    +    
CREATE TABLE IF NOT EXISTS /*_*/Vote (
    +    
  -- Internal ID to identify between different vote tags on different pages
    +    
  vote_id int(11) NOT NULL PRIMARY KEY auto_increment,
    +    
  -- Key to actor_id for the person who voted
    +    
  vote_actor bigint unsigned NOT NULL,
    +    
  -- Username (if any) of the person who voted
    +    
  username varchar(255) NOT NULL default 0,
    +    
  -- User ID of the person who voted
    +    
  vote_user_id int(11) NOT NULL default 0,
    +    
  -- ID of the page where the vote tag is in
    +    
  vote_page_id int(11) NOT NULL default 0,
    +    
  -- Value of the vote (ranging from 1 to 5)
    +    
  vote_value char(1) character set latin1 collate latin1_bin NOT NULL default '',
    +    
  -- Timestamp when the vote was cast
    +    
  vote_date datetime NOT NULL default '1970-01-01 00:00:01',
    +    
  -- IP address of the user who voted
    +    
  vote_ip varchar(45) NOT NULL default ''
    +    
) /*$wgDBTableOptions*/;
    +    
    +    
CREATE INDEX vote_page_id_index ON /*_*/Vote (vote_page_id);
    +    
CREATE INDEX valueidx ON /*_*/Vote (vote_value);
    +    
CREATE INDEX actoridx ON /*_*/Vote (vote_actor);
    +    
CREATE INDEX usernameidx ON /*_*/Vote (username);
    +    
CREATE INDEX vote_date ON /*_*/Vote (vote_date);
    +    
    +    
    +    
<comments />
    +    
    +    
[[Category:Articles by user Gani]]
    +    
[[Category:30 August 2021]]
    +    
[[Category:Sql]]
    +    
__NOEDITSECTION__

[robkelk]

Not against adding translation features.

Who's Gani and why are they adding SQL code in blogposts?

<snip>

  -- Username (if any) of the person who voted
+
  username varchar(255) NOT NULL default 0,
+
  -- User ID of the person who voted
+
  vote_user_id int(11) NOT NULL default 0,
+

<snip>

  -- IP address of the user who voted
+
  vote_ip varchar(45) NOT NULL default ''

<snip>

That's a lot of personally-identifying information for somebody to be collecting.

That's a hell of a lot of personally-identifying information for somebody new to the wiki to be collecting.

And without informing people that it's being collected, that's a violation of the Personal Information Protection and Electronic Documents Act

Permabanning this account as per ATT:How We Do Bans Around Here:

Some activity needs to be stopped as soon as it's identified. Doing any of these is grounds for permanent termination of editing rights without warning:

• Using the wiki to break the law, including but not limited to:
  

EDIT: Geth did the actual block while I was writing the user talk message.

[GethN7]

Not against adding translation features.

Who's Gani and why are they adding SQL code in blogposts?

Code:

<vote />
    +    
<!--start text-->
    +    
CREATE TABLE IF NOT EXISTS /*_*/Vote (
    +    
  -- Internal ID to identify between different vote tags on different pages
    +    
  vote_id int(11) NOT NULL PRIMARY KEY auto_increment,
    +    
  -- Key to actor_id for the person who voted
    +    
  vote_actor bigint unsigned NOT NULL,
    +    
  -- Username (if any) of the person who voted
    +    
  username varchar(255) NOT NULL default 0,
    +    
  -- User ID of the person who voted
    +    
  vote_user_id int(11) NOT NULL default 0,
    +    
  -- ID of the page where the vote tag is in
    +    
  vote_page_id int(11) NOT NULL default 0,
    +    
  -- Value of the vote (ranging from 1 to 5)
    +    
  vote_value char(1) character set latin1 collate latin1_bin NOT NULL default '',
    +    
  -- Timestamp when the vote was cast
    +    
  vote_date datetime NOT NULL default '1970-01-01 00:00:01',
    +    
  -- IP address of the user who voted
    +    
  vote_ip varchar(45) NOT NULL default ''
    +    
) /*$wgDBTableOptions*/;
    +    
    +    
CREATE INDEX vote_page_id_index ON /*_*/Vote (vote_page_id);
    +    
CREATE INDEX valueidx ON /*_*/Vote (vote_value);
    +    
CREATE INDEX actoridx ON /*_*/Vote (vote_actor);
    +    
CREATE INDEX usernameidx ON /*_*/Vote (username);
    +    
CREATE INDEX vote_date ON /*_*/Vote (vote_date);
    +    
    +    
    +    
<comments />
    +    
    +    
[[Category:Articles by user Gani]]
    +    
[[Category:30 August 2021]]
    +    
[[Category:Sql]]
    +    
__NOEDITSECTION__

I don't know, but that's pretty sus. SQL injection is generally not possible by default unless you allow it (certain extensions allow storage of SQL data), but it's not on topic for our wiki nor is it a good idea to add it without a good reason for security reasons. Rejected the edit. I'm banning the account on security grounds like Rob said, this is a dangerous precedent.

[Bob Schroeck]

I'm sure it's been done already, but if no one nuked the SQL code I'll do so when I get on the wiki in a few.

EDIT: Ah, NM. Sometimes I still forget the existence of the moderation queue.

[LulzKiller]

https://allthetropes.org/wiki/Special:Ce...arget=Gani

They run other wiki's we might need to ask Meta about them.

[robkelk]

Notify, not ask. I'll post a message to the Stewards' Noticeboard. EDIT: And done.

[Bob Schroeck]

Meanwhile, guys, please pay more attention to contributions by Shawn the Logo Boy. The new page he created, Fun Size/YMMV, was initially a word-for-word copy of the corresponding page at TVT, and the edit he made to Hotel Mario turned the text we had into a word-for-word copy of TVT content. I'm about to give him a warning, but for the foreseeable future anyone who reviews his stuff in Moderation needs to check it against TVT just to be sure.