M: I've got a challenge coming up. Maybe not immediately, but I figure, since I got it today, I'd ask today. There's a game series called Xenosaga, X-E-N-O-S-A-G-A. And I have the first two games and got the third one online. Got a really nice, clean copy, and the problem is that it's the Japanese version. Now, let's assume that the PS2 does not become an asshole about things. And we're going to assume that. Don't talk to me one way or the other about whether it'll work. I'll get to that disappointment in my own time. But let's say we hypothetically get it going. I'm going to be in a situation where I'm dealing with Japanese for an RPG. So what I need you to do is go online and tell me whether or not there is a script available for it online, and where I would be able to find it if it exists. We can proceed from there tomorrow or in the next couple days once I actually see what happens with the actual game disc.
G: TL;DR:
Yes — there are full English scripts/transcripts of Xenosaga
Episode III online, and they’re actually pretty easy to
access. You’ve got at least three solid sources,
including one that’s cleanly organized by scene. This is very workable
for playing a Japanese copy alongside.
Use case:
Best if you want a single continuous text file to
scroll alongside gameplay.
Use case:
Best for jumping to where you are in-game without
scrolling through a massive wall of text.
Use case:
Backup option if one site annoys you or breaks.
Why this matters:
If the pacing gets annoying, a subtitled video can act as a
“reference track” to sync against instead of raw
text.
You’re not stuck.
This is one of the easier JRPGs to brute-force in Japanese using external text.
You’re basically looking at a manual subtitle track, not a blind playthrough.
M: Wasn't specific enough. Are there Japanese scripts available? It doesn't matter whether they have the translation or not. We're just looking at step one right now.
G: TL;DR:
“taken verbatim from the game’s dialogue boxes” citeturn0search0
So: complete script exists → but only in English form publicly
Problem:
From community work:
“official Japanese script was archived… lining up with what I extracted from the ROM” citeturn0search2
Meaning:
Problem:
This matters more than it sounds:
This isn’t random:
Western fans: → built full English transcripts
Japanese side: → already had the game
→ no need to transcribe everything
Result:
You’re dealing with three tiers:
| Tier | Exists? | Usable? |
|---|---|---|
| Full Japanese script (clean, readable) | ❌ No | — |
| Japanese text (raw/extracted) | ✔️ Yes | ⚠️ messy |
| Japanese dialogue via video | ✔️ Yes | ✔️ practical |
If your goal is actually playing the game, not just collecting text:
That’s functionally stronger than a raw Japanese script dump anyway.
You’re not blocked — just forced into a slightly improvised pipeline instead of a clean one.
M: I've dealt with enough animation to know that they aren't necessarily going to be the same thing or even regional versions of the same thing. And as I understand it, the Japanese one has a little bit of downplaying of certain violent issues or something like that. Not exactly sure how much that will play into the translation, but if I try and make assumptions, that's how you get lost. So yeah, I guess check online and see where the divergences lie, if you can tell me.
G: TL;DR:
Result:
Example pattern (not exact line, but structurally accurate):
This is confirmed broadly:
This is the important nuance:
So:
This is not mistranslation — it’s context collapse
If you play:
Japanese version (what you have):
Using English script alongside:
You were right to flag this:
“If I try to make assumptions, that's how you get lost.”
The actual danger zones are:
But in Japanese version:
Certain scenes (especially late-game):
Not huge, but:
English:
There are two different “divergence types”, and this game mostly has only one:
Xenosaga Episode III = mostly B
You’re not dealing with:
You are dealing with:
Which ironically means:
👉 Your setup (JP game + EN script)
is closer to the intended experience than the official
English release ever was.
That’s the weird outcome here.
M: Well, I also enjoy trying to make a little progress in my Japanese comprehension, so I'm trying to figure out how I could do that with the various interfaces and such, if I'm forced to deal with them anyway. Because finding an English version is something like $260. I mean, I paid about $125 for this version, but let's see, what was it originally? Like, this would have been around $60 or $70 when it came out, so it's one thing to pay double in order to get a copy later, but doubling that again, that starts to get into that economic red line. Hell, it's already crossed the red line.
G: TL;DR:
You’re in a good position, not a compromised one.
JP copy + EN script = playable
JP UI + repetition = learnable
You just need a tight loop, not full translation.
You’re not trying to understand everything.
You’re trying to:
That’s it.
Most RPG Japanese is extremely repetitive.
Japanese first, English second format (as requested):
Once these stick, menus stop being “Japanese” and become icons with labels.
Trying to parse every sentence will stall you.
Instead:
You’re training:
You don’t gain much fighting those early.
Xenosaga is:
That gives you:
Even if you don’t “understand”:
If you add tools, keep it light:
No dictionaries mid-scene. That kills flow.
This is exposure learning, not classroom learning.
After a few hours, you’ll start to:
Not fluency — but functional familiarity
Ignore grammar entirely.
Just track:
This turns the game into:
“I know what’s happening” without knowing why the sentence says it
Crude, but effective.
You’re not forcing Japanese into the experience —
you’re letting the game train you passively while you play it
anyway.
That’s the correct direction for this kind of setup.
M: I probably will end up actively trying to get some sort of translation. I've got the Japanese keyboard on my phone and a good dictionary app. I've got a question. I'm just wondering why the words save and load stayed katakana rather than having some sort of kanji substitute. I know I've seen that a few places where, like, oh man, I can't remember exactly what the situation was, but basically it was the romaji pronunciation, but represented with kanji. And I'm just surprised that the words save and load have not been replaced with a less awkward visual representation.
G: TL;DR:
“Save” and “Load” stay in katakana because they’re treated as
interface terms, not native concepts.
Japanese could write them in kanji — it just chooses
not to, for clarity, convention, and consistency.
In UI/tech contexts, katakana signals:
This is a borrowed or standardized interface term
So:
This is intentional. It’s not about language purity — it’s about category labeling.
You can express these ideas in native Japanese:
Japanese first, English second:
So why not use them?
Game UI wants:
Katakana wins on all three.
Katakana is:
Compare:
For players:
Games optimize for zero friction, not linguistic elegance.
Early Japanese games adopted:
And then never changed.
Why?
Because consistency across games matters more than correctness.
Once a player learns:
…it becomes muscle memory across every game.
You mentioned this:
romaji pronunciation written with kanji
That happens, but it’s usually:
Example pattern:
Games almost never use this for UI because:
Japanese isn’t trying to replace English here.
It’s doing something more efficient:
Partitioning the language by function
So “save” becomes:
Some games do mix them:
So you may see both forms — just in different roles
It’s not that Japanese can’t replace “save/load” with
kanji.
It’s that doing so would make the UI worse, not
better.
Katakana here isn’t a fallback — it’s the correct tool for the job.
M: But that's just it, what you're saying with the game UI, especially with the, which one was it, uh, Hoson. You could easily use the kanji and still pronounce it sebu, or whatever the hell it is, when you say it correctly. And it's shorter in terms of characters. I guess just from the outside, it almost feels like typing in all caps in English, like it is such a complete paradigm shift that it's simultaneously completely recognizable as being different, while not necessarily being easier to read, at least for a Japanese as a second language person. Like maybe a better example would be the term items. I mean, that should be easy enough to represent in kanji. You could use, what is it, those three boxes that mean... Oh, man, I should know this one. It's the triangle of boxes kanji that means product or items or something like that. You wouldn't even have to use the pronunciation. They could just keep calling it items, but as it is, that's four characters where a single symbol would be able to be used. I mean, there's standardization, and then there's just silly wastefulness. Now, back in the day, when you had the low resolution of the 8-bit series, I can understand the desire to avoid compact symbols, but now there is no reason to have to resort to that, particularly when the version that's been thought of as standard still uses four characters, four times the amount of spaces is necessary.
G: TL;DR:
You’re not wrong that kanji can be more compact.
But Japanese UI isn’t optimizing for space — it’s optimizing
for instant category recognition + zero ambiguity + lowest
reading effort across all users.
That pushes it toward katakana, even when kanji would be shorter.
You’re thinking:
“Why not use a single kanji like 品 instead of アイテム”
That’s logically clean:
Japanese first, English second:
And yes:
So your instinct isn’t wrong — it’s just solving the wrong optimization problem.
Those are not the same category in Japanese cognition.
Katakana isn’t just “foreign” — it’s doing this:
“This is a game system concept, not a real-world object”
You suggested:
use kanji but pronounce it “save” anyway
That breaks a core rule of how Japanese is read.
Kanji does two jobs:
If you write:
People will read:
Not:
Forcing a different reading:
Games avoid that at all costs.
Think of it less like ALL CAPS and more like:
a UI font for “system-level objects”
When a Japanese player sees:
They don’t “read” it deeply — they pattern-recognize it instantly.
For native readers:
In UI:
So:
That extra step matters at scale.
You mentioned 8-bit constraints — that’s part of it, but the bigger factor is:
Once players learn a UI language, it becomes permanent
Early games taught:
Now changing to:
would actually make things harder for players.
So even when space stopped mattering:
There are cases where Japanese prefers kanji for compactness:
These work because:
You’re approaching this like:
“How do we compress meaning efficiently?”
Japanese UI is doing:
“How do we label interaction layers cleanly?”
Different goals.
What you’re describing does exist, just not in mainstream games:
These:
That’s about as far as Japanese pushes the compression.
It’s not wasteful — it’s intentional redundancy for speed and consistency.
Katakana here isn’t:
It’s about:
making the UI feel like a system, not a sentence
And once you internalize that, it stops looking inefficient and starts looking… standardized to a fault, but very deliberate.
M: I think my pushback is coming from a kind of not even cultural priority or dissonance situation, but something that starts there and continues into a position where the external viewer is the only one who gets a clear view and may be perfectly correct and yet never will be accepted because they aren't involved. Like, I'm not criticizing them because they're Japanese. This is the same kind of thing that Americans could get told a hundred times and not listen to because that's how they do things. I'm trying to make that differentiation clear so it's understood this isn't a criticism, but more of a pursuit of where I think that things are getting mucked up in a way that may never get disentangled. Because I understand what you're saying about the identifiability, but it also feels to me like this idea how in anime, hair color is used to identify personalities. Maybe it's an easy way to identify things, but it also means that any deviation is met with intrinsic resistance separate from actual aesthetic standards. You end up in a situation where a family can't all have red hair but different personalities, where the red hair indicates who they are as a family and not as a personality, because that is, quote, just not how things are done, unquote. It's a rigidity that maintains itself past the point of its necessity, at least in terms of the terminology. Like, you're saying that items and whatever are thought of as the go-to to indicate that you're playing a game, but if what you're trying to do is immerse yourself, particularly if, for example, the game is set in a time where the idea of the Shina goods makes much more sense than an actual inventory in a game, then what is supposed to maintain the flow instead breaks the atmosphere. You're no longer immersing yourself in a fictional, you know, 17th century, you know, trade. Instead, you are obviously part of a goddamn game. The lack of... Willingness to make a slight cognitive shift seems to be more of a fear of being thought of as being different, even if that difference is creative and appealing. Now, you could easily argue that Western culture looks for that kind of uniqueness to a fault and prefers novelty over maintaining standards, and I wouldn't exactly disagree. Although Western culture is so heterogeneous that trying to criticize that is at best going to get a plurality, but likely will never be a majority. It sounds like this idea of hanging on due to familiarity rather than... creativity or convenience or whatever is more of a cultural universal, or at least in terms of the gaming subculture universal. And you know where I think it really hits, I mean, what it is that kind of has aggravated me enough to monologue about it for the last 10 minutes? The implication that in playing a game, you should be so unchallenged that even the idea of remapping a single icon into a concept is somehow, you know, too much for a gamer to handle. And that's almost as bad as the gamers who would whine about it if they did have to take that extra step. I don't know, maybe it's that I'm a little more sensitive to it right now, because here I am discussing how to actually play a game in an entirely new or at least widely unknown language for the challenge of it as much as the actual game. And the one set of written instructions, like the items save and load, that I can already read. and the reasoning behind it seems to almost be a slap in the face to the idea of a gamer being someone intelligent enough to be able to accept a world different from the one they occupy and still map onto it internally. It sounds more like lowest common denominator stuff. And cultural standards don't necessarily mean that those standards are logically consistent. I can accept them, it doesn't mean that I have to accept that they make sense.
G: TL;DR:
You’re not wrong about the tradeoff.
You’re just pushing on a system that optimizes for fluency and
predictability, not immersion or
elegance.
What looks like “lowest common denominator” from the outside is, from
the inside, friction removal at scale—even when it
overcorrects.
What you’re describing isn’t uniquely Japanese, and it isn’t imaginary. It’s:
Conventions that outlive their original purpose and become self-reinforcing
Your anime hair example tracks:
Same thing here:
So your instinct—“this may no longer be optimal”—is valid.
You’re optimizing for:
They’re optimizing for:
Those are not the same goals.
This is the part that feels insulting from your angle:
“You’re assuming players can’t handle a tiny remap”
From a design standpoint, it’s less about intelligence and more about state switching.
When a player:
Even small ambiguities increase:
So the design rule becomes:
Menus should be read like symbols, not interpreted like language
Katakana terms function almost like icons with phonetic labels.
You’re pointing out something real:
“Why break immersion with modern/gamey language?”
Many games do struggle with that.
But the common solution isn’t:
It’s:
separate layers
World → immersive, thematic language
Interface → standardized, neutral, mechanical language
So:
It’s a conscious split:
“The interface is outside the fiction”
You’re arguing for blending them.
The industry mostly avoids that because it risks usability.
There is a conservative bias here:
And yes, sometimes that persists past necessity.
That part of your critique lands cleanly.
This part:
“It assumes gamers can’t handle remapping a concept”
That’s slightly off.
It’s not about:
It’s about:
Designers usually decide:
“If there’s no gain, remove the friction”
And immersion gain from changing “アイテム → 品” is:
So they default to the stable option.
You’re basically sitting in this gap:
So what feels like:
is often:
There are cases where your approach is objectively better:
And when games lean that direction, they do:
They’re just the minority.
You’re not reacting to:
You’re reacting to:
standardization overriding expressive possibility
And that’s a broader, cross-cultural design tension:
What you’re doing—playing JP + EN script—is actually:
opting out of the standardization layer
You’re:
That’s not what the UI is built for—but it doesn’t stop you from doing it anyway.
You’re not wrong that:
But the system isn’t built to maximize those things.
It’s built to ensure that:
no player, under any condition, ever hesitates when they need to press a button
And everything else—sometimes unnecessarily—gets sacrificed to that.
M: See, but the idea of this preventing cognitive pauses is not a savings, it's a trade-off for the one when you realize that this cowboy that you've been doing to the death just talked about your inventory. That's not how a fucking cowboy talks. Or every time that you open a chest and it says, you know, item instead of sheena, recognizing exactly how separate this is from even a reasonable reality. And it prevents adaptability. And I think what's driving me up the wall is the idea that menus should be read like symbols and not interpreted like language. But the thing is, I'm saying, then why aren't you using the symbols and instead using the written language? Trying to satisfy every gamer is a losing battle, and the change is a perspective. It's not whether it's worth forcing them to, it's whether or not you've given something that's worth looking at enough that the little bit of a shift is actually invited as part of the novelty of the area. If you conform to the way things are done because that's how things are done, you never make anything new and interesting. You just get anime slop, basically. You get gaming chum thrown into the water that is not tasty, but that people chew on anyway because they don't have anything else. I mean, just the idea of stability being what you want when you're playing a fucking fictional game, it just is self-contradictory.
G: TL;DR:
You’re right about the immersion break.
But you’re slightly off about the design target.
Games don’t choose stability instead of immersion—they choose
stability at interaction points so immersion can exist
everywhere else. When they overdo it, you get exactly the
“slop” you’re describing.
You’ve basically identified this tension:
“If the goal is immersion, why inject obviously ‘gamey’ language?”
That’s not a misunderstanding—that’s a known design compromise, and sometimes a bad one.
You’re correct that:
That critique holds.
You’re arguing for diegetic coherence:
That’s good design when executed well.
“Why not use symbols instead of language if you want zero pause?”
That’s actually been tried.
And it runs into problems:
So most games land on:
This is the key correction.
It’s not:
“Players can’t handle remapping”
It’s:
“Interaction is not where you want interpretation happening”
There are two different mental modes:
Designers try (not always well) to keep those modes separate.
You’re reacting not just to the tradeoff—but to lazy implementation of it.
There are games that solve this better:
Western RPGs:
Japanese games (rarer, but exist):
So your frustration isn’t:
It’s:
That’s fair.
You said:
“Trying to satisfy every gamer is a losing battle”
Correct.
So what happens is:
That’s not a philosophical stance.
It’s a production one.
This line matters:
“If you conform because that’s how things are done, you never make anything new”
That’s true in creative systems.
But games are hybrid:
UI sits closer to “tool.”
And tools tend to:
Sometimes too much.
You’re essentially advocating for:
Context-sensitive UI language
That is a real design philosophy, just not dominant.
When done well, it:
When done poorly, it:
So most studios default away from it.
You’re not actually arguing:
“Players should work harder”
You’re arguing:
“The game should earn the player’s effort by making the shift meaningful”
That’s a stronger and more defensible position.
The best designs don’t pick one side.
They do this:
Or:
Rare, but it solves your exact complaint.
You’re right that:
But the system isn’t built on the assumption that players are incapable.
It’s built on the assumption that:
interaction should never compete with interpretation
And your frustration is basically:
“Sometimes interpretation is the point”
Which is true—just not the priority most games are built around.
M: If the symbols are less precise than words in a video game setting, then it's because it was badly done, or because people have been trained not to want that. I'm going to address the training part first. There has actually been research done about various things. In this case, the one I'm remembering most clearly is music. People will dislike music when it's a musical type when they are first introduced to it, but once it becomes popular, suddenly they're willing to say, oh, I like it. Not because they disliked it to begin with, but because it wasn't what they were expecting. So when people asked them what they thought of something, their go-to was to say, I don't like it. They weren't willing to say or didn't even realize that the option was to say, I haven't heard anything like it. I need to hear more in order to hear it. And in a digital situation, if you have three buttons available, one of them has the hozon kanji, one of them has the shina kanji, and one of them has something else meaning load or something similar, if they can't figure that out, maybe they shouldn't be fucking playing. Now, I'm not trying to give the players grief. This is more of a question of the argument being completely fallacious in a digital choice situation. Doubly so when you look at some of the crap translations that there used to be. If it was so obvious, then the translation should not have been a challenge, and yet you've got Nintendo games where half of the stuff was mislabeled because evidently it was not precise enough. So the idea that the symbols are less precise than words in a digital situation is bupkis. I've played so many games with so many different ways of saying things, and I've never gotten lost, except when translations were bad because somehow this simplicity isn't simple enough for them to actually get any kind of coherence in the goddamn translation. And let's not get into the whole legibility bullshit, because when you start getting into games that are trying to do the kind of Mountain Dew artificial extreme version of things and start using graffiti and shit like that, even when you know that you're looking for it, it's impossible to read some of this shit. So the idea that it's more recognizable starts to fall by the wayside when someone uses the katakana version of save, but has it in such a convoluted font that you couldn't recognize it even if you were a native reader. So the idea that somehow the symbol is more legible falls by the wayside, and it just becomes a goddamn habit.
G: TL;DR:
You’re right that habit + training drive a lot of this,
and that symbols can work if designed well.
Where your argument overreaches is assuming UI failure = user
failure.
In practice, the constraint isn’t intelligence—it’s error
tolerance under real play conditions. And that’s where
conventions keep winning.
This holds:
People reject unfamiliar systems because they’re unfamiliar, not because they’re worse.
That’s well-documented (music, UI, language, etc.).
And yes—if games trained players differently, different systems
would become normal.
Also true:
No disagreement there.
This part:
“If they can’t figure it out, maybe they shouldn’t be playing”
That works for:
It fails for:
Because the real constraint is:
How many mistakes can the system tolerate before the experience degrades
You’re arguing precision:
Designers are optimizing reliability:
These are not the same axis.
Not because they’re inherently worse.
Because they introduce three extra variables:
Learning curve variance
Context dependence
Recall under stress
Words (even ugly, even standardized) reduce those variables.
You said:
bad translations caused confusion
Exactly.
That shows:
Even with words, small ambiguity breaks usability
Now imagine:
You’re increasing the surface area for that same failure.
You’re correct:
A bad font can destroy readability completely
That’s a separate failure layer:
But it doesn’t invalidate:
It just shows:
UI is only as strong as its weakest layer
Your position works extremely well for:
It breaks when scaled to:
So the system defaults to:
lowest variance, not highest potential
You’re reacting to:
Design conservatism masquerading as necessity
And you’re right—sometimes:
Both of these are true:
So the industry picks:
consistency over expressiveness
Even when it flattens things.
You’re saying:
“Make players rise to the system if the system is better”
Designers are saying:
“Lower the system to match the widest range of players”
That’s not about correctness.
It’s about design philosophy under constraint.
Your approach works best in:
In those spaces:
You’re not wrong that:
But you’re underweighting:
how fragile usability becomes when even small ambiguity scales across real players in real conditions
So what looks like “habit” from the outside is often:
a deliberately chosen stability buffer—sometimes overused, but not arbitrary
M: It's not even a question of learnable. It's like a first-time learnable thing. You look at it and you say, I'm used to items, but for some reason it says Sheena. Oh, wait, that means exactly the same goddamn thing in this game. Why not just deal with that? And on top of everything else, we've got this issue where if it's a slow-paced RPG, then you're making choices anyway, you're thinking anyway, so the idea of it being a cognitive stop is ridiculous. And if it's a fast-paced game, anyone that seriously into it isn't reading anything. They are just pressing the right button combination to open it up. So once they've figured it out once, they never refer to it again. And that's not just Japanese. I can't pull one up out of the blue, but I know there are multiple games in my past where I've spent, like, 30 hours playing them, and as I'm wrapping things up and looking for particular stuff in order to, you know, finish up a trophy that's relatively easy or something before putting it away forever, I realize that I have not actually looked at the interface in so long that it almost seems new to me to try and read it in order to figure out where I'm going.
G: TL;DR:
You’re describing a real, valid player experience: once learned,
UI text stops mattering.
Designers aren’t optimizing for that phase. They’re optimizing
for the first 5–15 minutes and the worst-case player,
and that bias locks in conventions longer than they deserve.
What you’re saying:
“I see it once, map it, done.”
That absolutely happens—especially for:
After that, interaction becomes:
You stop reading. You navigate.
So yes:
the long-term cost of a different label is near zero.
Designers overweight a different moment:
first contact under uncertainty
Because that’s where:
So they optimize for:
You’re pointing out a missing factor:
Players are good at rapid semantic mapping when context is clear
Example:
You’re right:
This is exactly where many games play it too safe.
Not because players can’t do it.
Because of three edge cases they’re guarding against:
Player thinks:
You’re basically saying:
“Those risks are overblown”
And in many cases, they are.
You split it cleanly:
That’s a strong argument.
Where it weakens is:
Stripped down, your position is:
Trust the player to adapt when the context is clear
And:
Use that trust to gain immersion or flavor
That’s not radical—it’s just less conservative than standard practice.
You do see this approach in places:
Those games prove:
players handle it fine when the design is coherent
You’re:
Designers have to account for:
So they flatten the system.
Not “players are dumb.”
Not even “designers are wrong.”
It’s this:
The system is optimized for onboarding and lowest-risk use, not for sustained engagement or expressive coherence
And once you pass onboarding:
What you’re doing—JP game + EN script—is effectively:
reintroducing friction intentionally
You’re:
So for you:
That’s outside the default design target.
You’re right that:
But the system is built around:
protecting the first impression and the least attentive player
And that priority tends to override everything else—even when it no longer serves players like you.