Suggestions for translate terms to remove and terms to add: requested by developers

[Mayoyama]

Having done quite a bit with JP.. theres a few things you mentioned should be removed, but they actually do get used.

Controller:
This whole category.

The O and X are actually used to indicate yes (O) and no (X) to JP

Keyboard:
This whole category.

Game terms:
- Ability (we have "Job Ability")
- Fortifications (too Campaign-specific)
- Log (too... un-specific. We have "Woodworking" already)
- Mercenary Rank (every Assault rank has its own term already)
- Physical (physical what?)
- Skill (we have "Weapon Skill" and "Skillchain")
- Treasure

<Log><Please check it> (Log means chat log not log of wood afaik)
<Enemy><Physical><Attack><Take care> (take care actually translates into "be careful" in JP.. not "see you later")
<Mercenary rank><What?>
<Sword><Skill><Level><What?>
<Treasure><You can have this>

Trade:
No removals, but a suggested change:
- Change the terms "Buy?" and "Sell?" into terms that make it more clear as to what the speaker wants to do, such as perhaps "Looking to buy:" and "Looking to sell:", similar to how "Reward:" was made to distinguish from the JA "Reward". It's possible that these terms are only ambiguous on the English client but have clearer meaning on other clients.

This is quite ambiguous... I have had many cases where I thought someone was buying something but instead wanted to sell to me ><

Place Names:
- Open sea route to Al Zahbi (I'm sure not all the ship routes get their own AT entries, so why does this one have one?)
- Open sea route to Mhaura (same deal here)
- Silver Sea route to Al Zahbi (same deal here)
- Silver Sea route to Nashmau (same deal here)

Fishing routes

Equipment:
Honestly, this entire category can go. People use the specific names for an equipment slot or a specific piece of equipment that goes in it, not these generic terms.

A few that should stay: Artifact, armor, earring, racial gear (RSE), Ring

[Sarick]

Starting a new topic specifically for feedback regarding this:



Top priority for cuts (almost completely useless):
{Hat Shop}
{Bastok Residential Area}
{San d'Oria Residential Area}
{Windurst Residential Area}
{Jeuno Residential Area}
{President}
{Prince}
{Princess}
{Specialty Vendor}
{Goods Store}
All 12 real-life months
{Day after tomorrow}
{Day before yesterday}
{Last week}
{Company}
{Courage}
{Course}
{Dream}
{Government}
{Liberty}
{Bastard Sword} (from the default list; it's not funny anymore)

I use these.

Secondary priority for cuts:
Analog Stick
Directional button
Directional pad
Expansion port
L1 button
L2 button
L3 button
R1 button
R2 button
R3 button
SELECT button
START button
Trigger
Xbox Guide button
✕ button
◯ button
□ button
△ button

The X's and O's are a nice way to get KEYs into the text.. These will be missed if removed but i'd use (/yes) and (/no) in their place.

Trigger is used to say things like (Notorious Monster) (Trigger) (Item) (I'm Interested)

Top priority for additions:
{Weapon}
{Seal}
{Relic}
{Mythic}
{Empyrean}
{Abyssea}
Names of all 8 game days
{Magian Trial}
{Blue Magic}
All new weapon skills
All relic weapon skills
{Walk of Echoes}
{Please wait.}
{Alexander}
{Odin}
{Wyvern} (For the love of God, give us wyvern)

Wait? I just use (/wait) (Please)

Secondary priority for additions:
{Embrava}
{Kaustra}
Names of all 10 Abyssea areas
Names of all 3 Abyssea expansions

Tertiary priority for additions:
{Expansion}
{Perfect Defense}
{Zantetsuken}
All new blood pacts, JAs, and spells (especially ones that don't exist as a scroll, like Quad. Continuum)

Would like Wide Scan to be added to that list.

[Sargent]

Regarding O and X, maybe just include those two without the "button" part, but scrap the rest of the controller/keyboard category.

Remove:
{In what order shall we use our weapon skills?} - Most people don't even know what a skillchain is anymore
{Heal!} or {Healing!}
{Reward} or {Reward:}
{Setting Home Point}
{Mercenary Assessment}/{Mercenary Rank} - Maybe even both
Ballista related stuff in Game Terms, except {Ballista}
Maybe the whole Race catagory, people can abbreviate these like TT, HM, GK etc
Settings & Setup... - {Filter}, {Patch}, {TV} (esp TV, it's the same in every language)

Add:
Was said, {Abyssea} and {Dynamis} would save on spaces for auto translate stuff. Add {Walk of Echoes} and {Provenance}. Keep spaces reserved for Adoulin.
Spells/JAs/Avatars are a given.
Was never actually included: Relic Weapon Skills and Empyrean Weapon Skills.
Game Terms: {Atma}, {Voidwatch}, {Curor}, {Dominion}, {Fields of Valor}, {Grounds of Valor} at the least. Don't really need {Bastion} if your trying to conserve space, depends on what the devs plan to add with Adoulin.

[Demon6324236]

Regarding O and X, maybe just include those two without the "button" part, but scrap the rest of the controller/keyboard category.

Or just add a simple yes and no, I don't understand how that was not put in in the first place!

[Fynlar]

The O and X are actually used to indicate yes (O) and no (X) to JP

Last I checked, there are actually O and X keys on our keyboards

<Log><Please check it> (Log means chat log not log of wood afaik)

Then it should be clarified as such. I've personally never seen {Log} used to refer to anything other than Voidwatch.

<Enemy><Physical><Attack><Take care> (take care actually translates into "be careful" in JP.. not "see you later")

Most people just say {Incredibly tough} or {Impossible to gauge} when referring to a particularly difficult enemy.

Also, the {Physical} probably refers to the category of chocobo attributes and not to physical attacks, since there is also a {Mental}. But I still think that neither of those need to be there. Terms for the actual attributes, like {Endurance}, is ok; these two aren't needed.

<Sword><Skill><Level><What?>

Eh, fair enough.

Fishing routes

Again, not all the possible routes are even listed there. Nor do I think there is enough of a reason to have them all listed there.

A few that should stay: Artifact, armor, earring, racial gear (RSE), Ring

Yeah, that kind of stuff is fine. Things like {Bastard Sword} or {Baselard} or {Tunic} though, way too specific to be worth keeping around (and we all know what {Bastard Sword} ever gets used for anyway, and it's not to refer to the actual weapon)

I use these.

The point isn't whether one person uses these, the point is what isn't relevant enough to the game to be worth keeping in, because at this point we've been going for literally years without having actual game-relevant terms (such as the post-75 blue magic spells, for one thing) added to the translate. From a gameplay standpoint, this is far more important than you being able to translate the RL months or being able to quote Cartoon Link.

[Sarick]

Or just add a simple yes and no, I don't understand how that was not put in in the first place!

Yes and no do exsist in translate table.

/yes

/no

These are emotes commands.

[Modoru]

{Reward} or {Reward:}

These are actually pretty relevant, since "Reward" is a Beastmaster ability, and "Reward:" signifies an actual compensation for a service in-game. It makes a difference to JP players.

[Mirage]

{In what order shall we use our weapon skills?} - Most people don't even know what a skillchain is anymore

And in the few cases we actually want to do a skillchain, we can use {Weaponskillone} -> {Weaponskilltwo} -> {Skillchainname} {Yes, please} to communicate this with foreign players.

To list a few things myself (even if many of them have been mentioned already):

A lot (most) of the controller/keyboard terms. Instead of O-button and X-button to communicate yes/no, we can use {Yes, please} or {No, thanks}. I think {Trigger} can stay, because it is used for pop items/weakness targeting (i think), but you could remove that if you added real terms for pop items and weakness targeting.

Here is an idea, though. Would it be possible for SE to take perhaps a month's worth of chat logs and run them through a sort of log parser and have that program automatically generate a list over the most/least used auto-translate words? I realize this is a *lot* of chat log to parse, but I guess this is what would give the most accurate picture of which terms are used or not.

I think it's pretty safe to entirely remove terms that haven't been used even once in an entire month by the entire player base, for example. Maybe terms that are used less than 1% too.