Bugs 101

[Steiner]

My proposal was to guarantee that any use of the {{bug}} template would require a citation, proof that it is a bug so people don't go crazy posting it on every page (I'm only skimming through the posts so it's just broad speculation of the problem at hand).

I don't know if pwiki's goal to to allow the use of the bug template as an opinion or relatable fact. If the latter than requiring a citation would fix a lot of blind uses of the template.

[Aggelakis]

{{bug}} wasn't actually over-used at all. There were a few instances that could have been handled with a regularly-typed note or an {{EdNote}} (however, this wasn't created until fairly recently). There's no need to create solutions for a problem we weren't having.

[Steiner]

{{bug}} wasn't actually over-used at all. There were a few instances that could have been handled with a regularly-typed note or an {{EdNote}} (however, this wasn't created until fairly recently). There's no need to create solutions for a problem we weren't having.

Understood, apologies for branching from the original argument.

[Fleeting Whisper]

We do not use {{bug}} for typos (or should not).

The bug-for-typo comment was in relation to some discussion about directing developers to our wiki to find errors in the game. We already know that they look at Paragonwiki to know what information has been released or put into the in-game lore and what hasn't; extending that to what errors need fixing isn't a huge leap.

I realize we don't use {{bug}} for typos, and I absolutely agree that the current form of {{bug}} shouldn't be used for them. But considering that angle of helping developers find errors, I was suggesting that any modification of {{bug}} for typos should by necessity be extremely unobtrusive.

[Zombie Man]

From the point of view that the Wiki is a reference work for an original work, we *shouldn't* be fixing typos. The professional standard is to leave typos be and put '[sic]' after the typo. And that could be templatified to create a page that lists all the typos.

[iakona]

From the point of view that the Wiki is a reference work for an original work, we *shouldn't* be fixing typos. The professional standard is to leave typos be and put '[sic]' after the typo. And that could be templatified to create a page that lists all the typos.

I agree with this.  I find it rather odd that the wiki editors would fix typos found in the game without any reference to the typo whatsoever.  That definitely seems unusual for a reference site.

[TonyV]

From the point of view that the Wiki is a reference work for an original work, we *shouldn't* be fixing typos. The professional standard is to leave typos be and put '[sic]' after the typo. And that could be templatified to create a page that lists all the typos.

Really, I think of the Wiki more from the point of view of what is useful to a user.  I don't think that most users really care so much about the exact wording in the game, and care a lot more about what it's supposed to say when it comes to typos and such.  Keep in mind that we're not a formal reference.  I want the information to be accurate, but not to the point of distraction, and seeing [sic] after an in-game typo would be distracting to me.  Not "ZOMG I can't read this!" distracting, but I just like it better when errors like that are silently corrected because I really don't care about misspellings.

Having said that, I wouldn't mind having some kind of template that would allow me to, for example, use something like this:

{{bug|message=Malaise's name is misspelled as "Maliase" in the mission description for whoever's whatever mission.|display=no}}

If the display=no parameter is specified, then this wouldn't show anything on the page; maybe it's enclosed in <span style="display:none;"></span> tags or something, but it would show up in the bug category page that devs or anyone else could use to reference if they want a really nitty-gritty list of every mistake that we know of in the game.

[GuyPerfect]

Category:Sics

Make the {{sic}} template invisible.

[Fleeting Whisper]

But then how do you reference exactly what the typo was? A category and an invisible template doesn't show where on a huge page the single wrong word is...

[GuyPerfect]

We could make it visible, and the misspelled word itself is the argument in the {{sic}} parameter.

Okay, HeroName, we've got a situation down at the docks. Turns out a ship is coming in, and {{sic|it's}} cargo is the target for a Wailer raid. I don't know what a Wailer is, but it can't be good.

[Zombie Man]

That would be fine if to a reader it looks something like this...

Okay, HeroName, we've got a situation down at the docks. Turns out a ship is coming in, and it's _[sic] cargo is the target for a Wailer raid. I don't know what a Wailer is, but it can't be good.

[Steiner]

Nice use of subscript!

[eabrace]

That would be fine if to a reader it looks something like this...

Okay, HeroName, we've got a situation down at the docks. Turns out a ship is coming in, and it's _[sic] cargo is the target for a Wailer raid. I don't know what a Wailer is, but it can't be good.

That would be a pretty simple template.  Just have it return the text entered and tag the [sic] on the end.

Code Select Expand

{{{1}}} <sub>[sic]</sub>

Furthermore:  Using a template will also make it easy to compile a list of all pages with typos noted just by using the "What Links Here" feature from the template's page.