• Forum Moderator applications are now open! If you're interested in joining an active team of moderators for one of the biggest Pokémon forums on the internet, click here for info.

Bulbapedia Suggestions, ideas, and problems

Thespeon said:
Hey, if you are making a page intended for the mainspace, placing {{mainspace}} at the top of the page will add it to the category of those pages that are under construction. When you feel it is finished, add the parameter status=complete to it, so it reads {{mainspace|status=complete}}
Staff will then get around to reviewing it to see if it meets the required standards for the mainspace.
Hope this helps!
Click to expand...
OK, thank you for letting me know!
 
The Bulletin Board should be mentioned somewhere on the Editor’s Hub, the only mention I’ve seen is on the Message from the Editor section and that changes every couple of months. It could possibly be put in the empty space from Wanted articles and Pages needing improvement sections due to Latest changes length.
 
Handium said:
The Bulletin Board should be mentioned somewhere on the Editor’s Hub, the only mention I’ve seen is on the Message from the Editor section and that changes every couple of months. It could possibly be put in the empty space from Wanted articles and Pages needing improvement sections due to Latest changes length.
Click to expand...
You're right! We actually also have a refreshed Editor's Hub in the works, you've just caught us in the middle of all of these updates.

I appreciate the suggestion though. Keep up the engagement!
 
I’ve been rereading the first volume of the adventures manga on Libby and I’m curious if it could be used as a source for adventure scans because the ones on Libby seem to be higher quality of the ones on bulbapedia
IMG_3194.png
IMG_3193.png
 
Handium said:
I’ve been rereading the first volume of the adventures manga on Libby and I’m curious if it could be used as a source for adventure scans because the ones on Libby seem to be higher quality of the ones on bulbapedia
Click to expand...
Using higher quality scans would be useful since some in Bulbapedia are simply the user taking low quality photos like the ones related to the Genesect movie Manga.
 
Two questions about the TCG Pocket cards on Bulbapedia wiki:

1: will the cards be added to the general list of cards featuring a specific pokemon? e.g. should Bulbasaur_(TCG) include Bulbasaur_(Genetic_Apex_1)? It's currently only featured in the Bulbasaur_(TCG_Pocket) page. I think the Bulbasaur (TCG) could link to the Bulbasaur (TCG Pocket) page. Something like "for information about cards in the TCG Pocket game, see Bulbasaur (TCG Pocket)"

2: should the page for each specific card mention it that it only exists in the Pokémon TCG Pocket game? Bulbasaur (Genetic Apex 1) has a banner that says "This article is about a card in Pokémon Trading Card Game Pocket...", but other pages like Kabutops (Genetic Apex 159) don't have it yet. I think it should also be included in the text. Something like "It is part of the Genetic Apex expansion, as part of the Pokémon TCG Pocket game."
 
Mateussf said:
Two questions about the TCG Pocket cards on Bulbapedia wiki:

1: will the cards be added to the general list of cards featuring a specific pokemon? e.g. should Bulbasaur_(TCG) include Bulbasaur_(Genetic_Apex_1)? It's currently only featured in the Bulbasaur_(TCG_Pocket) page. I think the Bulbasaur (TCG) could link to the Bulbasaur (TCG Pocket) page. Something like "for information about cards in the TCG Pocket game, see Bulbasaur (TCG Pocket)"

2: should the page for each specific card mention it that it only exists in the Pokémon TCG Pocket game? Bulbasaur (Genetic Apex 1) has a banner that says "This article is about a card in Pokémon Trading Card Game Pocket...", but other pages like Kabutops (Genetic Apex 159) don't have it yet. I think it should also be included in the text. Something like "It is part of the Genetic Apex expansion, as part of the Pokémon TCG Pocket game."
Click to expand...
people may confuse the TCG pocket cards for physical cards on the main TCG page for the Pokémon; I’ve brought this to other staff as I do not work on the TCG Pocket pages.

There are currently plans to update the TCG template that will add this, there may be a replace text to fix other said issues, but it’s still on the planner!

Yes, there are plans for a more obvious mention of it being a TCG Pocket card.

I apologize if I didn’t answer any other questions you have! Feel free to mention any others you have either on the Forums or the Discord!
 
Hello! I am a long-time user of Bulbapedia, a linguist, and a new editor of Bulbapedia. I made my account just today! Over a lot of time using the wiki, I noticed a few improvements I could offer as an editor, and got to work today on improving transcriptions and romanizations regarding Korean.
Bulbapedia's Pokémon pages handle Japanese names and translations very gracefully. Displaying Kana with hoverable romanization, and the officially trademarked translation beneath it. I was initially confused coming across some trademarked names, but after finding the documentation here I appreciate this really good system now for not leaving room for any ambiguity for the most prominent part of the wiki. I also observed that my favorite part of Bulbapedia pages, the "Other Languages" section, seemed to abide by the same set of rules, broadened beyond Japanese.

Korean doesn't have a complete list of trademarked, Latin-script names for all Pokémon. Based on the standard set in the Infobox template linked above I thought using good, well-interpreted translations was the way to go for those without trademarked names. But Inkay did have a trademarked name translated from Korean: Okijing. I was disappointed to implement this into the Other Languages table on Inkay's page, because "Okijing" does not represent all the sounds in 오케이징 Okeijing, and it was replacing a better representation in "Okayjing", a good translation incorporating "OK". This is when I looked into the Other Languages table template to verify the documentation, and discovered that although de-facto all Other Languages tables used trademarks and user-made translations, the documentation specifically asks for Romanizations for all non-Latin scripts, including Japanese. In Korean's case, it specifically links to the Wikipedia page on Revised Romanization, meaning that's what's meant to be used, not the trademarks or translations used across the wiki.

Alakazam - Where フーディン should receive Fūdin, it has Foodin™. Where 후딘 should get Hudin, it has Fudin™
Floette - Where 플라엣테 had Floette, which I altered to a more interpretive Fla'ette, it should've always had Peulla'ette

I would estimate there are currently ZERO "In Other Languages" sections on Bulbapedia's catalog of Pokémon species articles which use Romaji as prescribed in the documentation instead of the trademarked translation, and further the precedent set by the Japanese-language standard has influenced all other languages in the table to have translations instead of their Romanizations or Transcriptions prescribed in the documentation.

Right now, the guidelines are at odds with execution. This is contradictory and ambiguous. A solution would be to change the usage of the template to fit the de-facto usage up to this point. For every non-Latin script the Other Languages template would suggest to use a trademarked name, if one is available (please link to these lists!), and failing that to translate that name in the style of keeping the approximate sounds or likely intended Latin spelling.
pros:
  • This is already what most editors have done.
  • All current Japanese names have a trademarked translation.
  • Some other languages' names have trademarked translations.
cons:
  • This is not how this has worked or will work for Chinese languages. A different standard would be in concurrent usage for these, as de-facto there is already.
  • Translating names is a non-rigid process. there is a lot of room for ambiguity and interpretation which editors will disagree over. (i.e. Floette)
  • Translating names into English-like words/names likely means sacrificing a faithful representation of native pronunciation.
  • Translating names into English-like words/names requires editors to make definitive choices on what wordplay, name origin components, and spellings get represented. Confirmation for the inspiration and source words in use is scarce, but in this style some feature will need to be upheld. If a Pokémon's name features a native-language pun on an English-language homophone, a choice has to be made on which part of the homophone gets spelled out.
  • I don't believe that people are looking at the Other Languages section looking for trademark names.

A different solution would be to reaffirm the old prescription, and all Other Languages tables would have academic romanizations instead of trademarked names.
pros:
  • There is no ambiguity for this. Any non-Latin script name can be converted into Latin script representatively.
  • This will be most familiar to people who can transcribe these languages.
  • Romanizations are created to most accurately represent a different orthography in Latin script.
  • This could be consistently applied to every language equally, creating a coherent standard.
  • This was apparently the intention of the documentation's author(s).
  • Makes more efficient use of the "Notes" section of the table, which can explain wordplay and/or name origin.
cons:
  • manhours.
  • upheaves current convention. (i don't want to understate that these two are very big cons)

I have a preference for Romanization, normally, but I don't actually hold a settled opinion on if it's right for Bulbapedia. My only issue is that now there is a conflict between what is prescribed and what is done. I think it is appropriate for this to be discussed and whether people prefer an Interpretive Style or a Literal Style.
 
First of all, Bulbapedia got rid of the "Did you know..." section from the Main Page 13½ years ago. And second of all, the term "Trivia" is useless because it is written in a low effort. But the good news—I've come up with the solution: we should bring the "Did you know..." term back to Bulbapedia by renaming the "Trivia" section the "Did you know?" section on each article. Maybe that will solve the problem, similar to how the Super Mario Wiki renamed the "Trivia" section the "Notes" section.
 
Last edited:
I've been doing research on rescue team dx and found some interesting data, as well as things not listed in any respected sources, like bulbapedia, and I've got a couple things to ask about:

1) how do I go about adding things to pages that I've researched myself? Do I need to publish my spreadsheets on reddit to cite as a source or something of the sort before doing the edit, or is there a place on bulbapedia where I can publish the sheets? Would the forums here be just fine?

2) I think the mystery dungeon community would benefit greatly from splitting the current pages into "main series" - "mystery dungeon". Having games as big and complex as mystery dungeon be a footnote on other pages limits how much info we can add. For example move pages, "Energy ball" and "Energy ball (mystery dungeon series)" would give us the space we need to properly talk about the move without cluttering further the current page. (Aside: RTDX seems to not be included in many moves' pages. I should go ahead and add the info I have, right?)

3) I found this gamefaqs forum post on rare qualities. I haven't reviewed the info on it myself, but, while citing it as a source, would it be okay to add its findings to the appropriate pages?
 
I was doing research on Electric Soldier Porygon (JP episode 38) & saw it had a Mandarin Chinese name listed. I find this very odd & i've tried using the Chinese name on BaiDu (popular chinese search engine) & found nothing so i was wondering what is the source of Mandarin name?
 
I think we can launch a Proposals policy pages on both Bulbapedia and Bulbagarden Archives, just like how the Super Mario Wiki and WiKirby have their own respective Proposals pages. The Proposals pages on the Bulbagarden wikis are where users can come up with ideas on new features (such as an extension), the removal of previously added features that have tired out, or new policies that need to be approved via consensus before any action is taken. The rules are simple:
  • Only registered, autoconfirmed users can create, comment, or vote (e.g. Support, Oppose, Option 1+) on proposals.
  • Proposals expire at the end of the day (23:59) two weeks after voting begins (all times UTC)
  • Every vote must have a strong and sensible reason accompanying it.
  • Users who make a vote and are subsequently blocked for any amount of time will have their vote removed. However, users in question who have their block expired will have the right to cast their vote again.
  • Proposals can only overturn the decision of a previous proposal that is 6 weeks (42 days) or older.
  • All proposals are archived.
  • Proposals can only be improved or canceled by their proposer within the first six days of their creation.
  • No proposal can be made about promotions and demotions.
  • Joke proposals are never permitted, as any of them will be vetoed on sight; proposals are serious wiki matters and must be handled professionally.
  • Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.
Do you think that the Proposals pages on the Bulbagarden wikis will be a great idea?
 
Hidden data like:

{{tt|20...34|Only when enjoyment is between 20 and 34 points.}}

is impossible to view if you're not using a desktop PC. Considering the mobile users, data such as these should be openly written instead.
 
MarshiyanMisutaa said:
Hidden data like:
{{tt|20...34|Only when enjoyment is between 20 and 34 points.}}
is impossible to view if you're not using a desktop PC. Considering the mobile users, data such as these should be openly written instead.
Click to expand...

Since the Previews extension was installed on the wiki recently, we're now actively working towards solutions for mobile.
Such tooltips using the {{tt}} template above can be replaced by footnotes by using the <ref> tags.
 
nickpsych said:
Hi, Makuhita/Hariyama can learn Drain Punch, but the Drain Punch page on the wiki does not list them Drain Punch (move)
Click to expand...
Hi again! I checked the species pages of Makuhita and Hariyama, and Drain Punch is learnable by TM in Scarlet and Violet, so added this to the Drain Punch page. Thanks for pointing this out!
 
I’m a little confused as to why some of the human characters’ Gallery sections seem so lacking. Each Pokémon’s gallery is full of so much miscellaneous stuff, from merchandise to promotional images (which rules) but there’s rarely anything beyond sprites and one official artwork for most of the human characters in that tab. Not sure if this is the best thread for this, but it’s smth that’s been on my mind for a while and I just don’t know why it is the way it is and if it could be done differently.
 
Back
Top Bottom