Final Fantasy Wiki
Register
Advertisement
FFWiki forum logo
Forums: Index > Rin's Travel Agency > Archive > Adding Japanese to tables


Is it ok to add Japanese to info tables for game like DFFOO, FFBE, FFRK? Other websites dedicated to these games have two languages for both JP and global version and our wiki seems to be less useful compared to the other sites because of this. I know this is an English wiki, but there're many people who play these mobile FFs on JP server for newer and more updated content.

Here's an example:

Current table
Image Name Grade CP Effect
DFFOO Force Stealer (VII) Force Stealer (VII) 5★ (EX) 70 Equips the EX Ability Meteorain.
DFFOO Rune Blade (VII) Rune Blade (VII) 5★ 35 Increases the potency of Finishing Touch.

Increases its max uses by 1. Grants Small Max BRV Up, Small Physical Attack Up and Small Critical Rate Up for 5 turns.

DFFOO Crimson Edge (VII) Crimson Edge (VII) 5★ 15 Removes one buff from the target when a command ability deals a critical hit.
New table
Image Name Grade CP Effect
DFFOO Force Stealer (VII) Force Stealer (VII)
フォーススティーラー (VII)
5★ (EX) 70 Equips the EX Ability Meteorain.
DFFOO Rune Blade (VII) Rune Blade (VII)
ルーンブレイド (VII)
5★ 35 Increases the potency of Finishing Touch.

Increases its max uses by 1. Grants Small Max BRV Up, Small Physical Attack Up and Small Critical Rate Up for 5 turns.

DFFOO Crimson Edge (VII) Crimson Edge (VII)
クリムゾンエッチ (VII)
5★ 15 Removes one buff from the target when a command ability deals a critical hit.

Monterossa (talk) 09:52, November 19, 2018 (UTC)

It would be difficult for an average contributor to add the JP names, or to see if they are correct or not, but if quality could be preserved and it made the tables more useful, seems like a good addition.Keltainentoukokuu (talk) 10:34, November 19, 2018 (UTC)
We used to include Japanese in lists but they were removed on the idea that it's overkill to include Japanese names everywhere. So since then we've switched to just using Japanese names when the ability name has a different meaning to the English name.
I disagree with that idea because list/table-entries pages are essentially the main articles for things like abilities and so including all the information we have about it there makes sense. Currently users will have to navigate to the Translations page (and know about that page's existence), which is craaazy.
If we do include Japanese names we should still include the romanisation in some form, be it ruby, mouseover, or whatever. JBed (talk) 11:44, November 19, 2018 (UTC)
Seems unnecessary. This is an English wiki, we have no reason to include Japanese names. Including Japanese names seems as useless as including names for other translations, as it makes the table less readable for the sake of a minority of readers.
If you're going to include them, make sure it doesn't screw over the mobile display and it should be fine.--Magicite-ffvi-ios Technobliterator TC 12:44, November 19, 2018 (UTC)
So did we reach a verdict on this? Monterossa and I started adding Japanese terms to DFFOO pages since we're already restructuring them. My thoughts: Because the nature of this (and other gacha games) is Japan having new content first, there will be periods of time when the content is JP-exclusive without localization. DFFOO's translation page is already heavy with several subpage splits and still many more terms to cover. I don't mind having Japanese text present to save the hassle of scouring long lists. Even though there's a Global release, JP is ahead in content and even new gameplay mechanics so it wouldn't hurt to have text citing where it came from. Mierna 12:00, December 2, 2018 (UTC)

I am well aware that are Translations subpages for mobile games leave much to desire, but they exist and should be updated. Putting JP names on equipment (and other) lists seems like an overkill considering we have quite a wealth of Translations subpages.—Kaimi (999,999 CP/5 TP) ∙ 12:25, December 2, 2018 (UTC)

The JP can be in both the tables and the Translation pages.Keltainentoukokuu (talk) 16:29, December 2, 2018 (UTC)

Advertisement