Site Forum

Discussing with FireNBeers on what the standard should be as it doesn't seem to be defined there are two pieces that need a clear rule to follow.  As far as I can tell there isn't anything in the FAQ or the set creation instructions.  I'm using Pokemon as an example but this probably affects a lot more.

1) How to name a foreign set.  I'm thinking one of these.  The top one makes most sense to me and glancing around seems to be what is done on other categories

2023 Pokémon Scarlet & Violet Pokémon Card 151 (Japanese)
2023 Pokémon Japanese Scarlet & Violet Pokémon Card 151 (Japanese)
2023 Pokémon Scarlet & Violet Pokémon Card 151 Japanese

2) Card name matching card or in language card is printed in.  I understand if it was proper names it would be the English lettering of the persons name.  This one I don't know if I have a clear opinion on other than if the card name is entered in the language the card displays that an alias is used to link it to the same name entry.  This could maybe get out of hand with lots of other language cards entering the database but cards that may not even have an English translation would still end up in the foreign language.

Ex: Bulbasaur with alias of フシギダネ

@FireNBeers if you have any other input on it.

Thanks for bringing this up to the forums, I have been thinking about how to standardize the foreign naming schemes of the Gaming category for some time now.  Throughout the years, some inconsistencies exist.  Having a consensus would be ideal.

As far as the card printing in the language that it is printed in, I think that is probably preferred.  The only question I would have is if the English translation is needed in the Note2 field.  I know there is a proposed New Feature regarding a translation from Japanese to English.  This might need to be expanded to include a number of other languages.

For naming foreign set, name based on packaging. The site doesn't have rules for Transliteration vs Romanization and this would be something that would need to be put into print because people tend to use one vs the other.

For subjects themselves, should be actual text with international name in Note2. So フシギダネ  in name and Bulbasaur in Note2. However for this type of decision I think that it is important to get guidance for Admin on how it should be done. Because the primary reason for having foreign language support on a website (beyond information accuracy) is if there is any wish to draw in that native audience. As i can say as an example, having the Japanese text on the Harukanaru Toki no Naka de 3 set will only serve to benefit maybe a handful of people outside of Japan.

Using Pokemon as the example may not work well enough. You should take into account a few more sets so that you can make sure whatever ruleset you come up with works properly with all set types, not just Pokemon.

Priority for card naming:
1. card itself
2. checklist card
3. official checklist online somewhere
4. unofficial checklist online somewhere

Sometimes it is impossible to find some Japanese checklists online and there are only foreign sources that use incorrect names. As I ran into these type of situations, I just refrain from trying to make a checklist to put on here.

Also in regards to subjects, if Admin defines whether transliteration or romanisation is to be used, then that will solve the situation of needing to know English words for Japanese only subjects.

Set naming I was more looking for how to indicate language when there are sets named the same in multiple languages or to just indicate it is not an English set.

Whenever I add a foreign (non-English) set/checklist, I use the language present on the card as the name of the card. I also make an effort to add associated aliases to the appropriate PIDs. Given this approach, I do not add the English name in Note2, as the PID linking serves this purpose.

Here is a recent example:
https://www.tcdb.com/ViewSet.cfm/sid/378925/2012-Bandai-Digimon-Digital-Monsters-Super-Bromaido

My advice, based on what I know about these sets, TCDb, and databases in general (all my personal opinions):

Set name should be structured as:
[Year] [Branding, if applicable] [set name] ([language, only when available in multiple languages])

If a set is only in Japanese or French, there is no need to point that out.

Card Names:
What is on the card (or as close to it as humanly possible)

If that is "Energía del Agua", then use that, but add it as an alias for "Water Energy". Then it can be found, using any language the card's subject comes in. That's why alias exists, and why we can now add multiple aliases. Let's use what we have available to us.

Ok seems the consensus is the following:

1) Set titles that are named the same but in different languages should have the non-English language in parenthesis in the end.
        [Year] [Branding, if applicable] [set name] ([language, only when available in multiple languages])
  Ex: 2022 Pokémon Sword and Shield Pokémon GO (Japanese)

2) Card names should match what is on the card in the same language as the card.  The primary name entry should be English with any language variants added as an alias to the name entry.
  Ex: Bulbasaur with an alias フシギダネ

Here is the card in your example

https://page.auctions.yahoo.co.jp/jp/auction/n1101556480

The card name would be フシギダネ

which is what vroooooomed said above " What is on the card "

Yes sorry if I didn't explain it properly.

Card name on set would be フシギダネ

For the global name entry it would be Bulbasaur and an alias added to it of フシギダネ