Samu

Esp/Eng/Ру/日本語.
Future translator/Localizer.
JRPG enjoyer.
Forward, relentlessly.
風林火山

[Samu @Samuelrual]

For those who come after

[AntonioMaestre @AntonioMaestre]

Imagínate que pidiera que los autónomos tengamos los mismos derechos que los asalariados y no que a los asalariados les jodan lo mismo que a los autónomos.

Pero este tipo es de la patronal y del PP por encima de cualquier defensa de los autónomos.

[Reseñas Cortas @ResenasCortas]

He probado ORBITALS en las oficinas de Nintendo.

Y Eric.

@Kepler_Interact @NintendoES @OrbitalsGame

[Serena @Serena_mrn]

Me duele decir esto porque siempre he sido jugadora de esta gran marca, pero actualmente eres una empresa a la que no le importa nada su comunidad.

⏩ 6 días se pasaron en silencio y ayer vuelven como si nada.

⏩ Su CEO vendió 225 000 acciones de sony, dos días después de que anunciarán que iban a descontinuar el formato físico en 2028

⏩ Encima la marca se enfrenta a múltiples demandas, entre ellas, la acusación de que la PlayStation Store es un monopolio.

La PlayStation y Sony de hace unos años si escucharía a su comunidad y revertirían está situación. Se avecinan tiempos oscuros para la marca.

[Juan Martín @JuansalMartin]

Espero que todos aquellos que están criticando duramente a Sony no vuelvan a comprar PlayStation nunca más; pero de verdad

Esta prepotencia solo puede contrarrestarse de una manera

[pyzard2: Rojo Rojez Friki @PizardoSegundo]

Piensa en esto cada vez que pasees por la calle y veas esos carteles propagandísticos de la UE hablando de cómo protegen nuestra libertad de expresión frente a los malvados autoritarismos

[GamesCage - Hype Guy @GamesCage_]

*PLAYSTATION ON PR NIGHTMARE*

*MICROSOFT LAYS OFF 4000+ PPL*

*NINTENDO COWS!!! FUNNY FUCKING COWS!!!!*

[Leona Renee 🐈🌻 @Hatsuu]

though chest phrases are harmless localization sillyness since they're quite out of the way, folks seemed sad about them not being in TOCS1 due to how the text was programmed. the chests saying you have the wrong party in TOCS2, however, were all unique, so...i made a decision :)

[Green Dummy of the Dawn @dumitaph]

It’s what we should always expect when we do work like this.

Stop frowning already, would you?

I’ll stab you as soon as I determine that you’re getting in our way.

[風香 @huka_kiseki]

リィンとクロウで心予報パロ
※音量注意

[🐸 @okbdko123]

,

[Mercer 🌙 @ Daybreak @midn1ghtexigent]

kiseki mona lisa

[David García Abril @Xander_VJ]

Traductor de videojuegos al habla.

Sintiéndolo mucho, Carlos, entiendo vas con buenas intenciones, pero lo que has escrito no es nada serio.

Es una retahíla de topicazos que los localizadores estamos hartos de oír.

Abro hilo. Y agarraos que es largo:👇

[Rekka Alexiel「天地創造」「サムライトルーパー」「グラブル」ファン活動中 @RekkaAlexiel]

So, regarding this, there's a point that I wanted to bring up that I think a lot of people don't take into account...

I wasn't a translator back in the day, so I not exactly sure what the system was like; but I can speak from my own experience working on the English translation. I worked on a MASSIVE excel sheet with various columns for different languages. JP would be the first on the left, next EN with a comment column, followed by various other languages, etc.

The thing that I've noticed most people comment in this thread basically boils down to "They're Japanese level is crap to even begin to translate accurately into English", but I would propose other reasons for this discrepancy that literally has NOTHING to do with language ability.

When you're working on translation, what you're given is often times not in the most easily handled format... ie. excel is not my preferred format to translate. It took enough time just learning the ropes before I could even get to translating anything...

Typically speaking, when we're translating, we used color coded columns (green, yellow, red) to designate whether a cell was completely finished (green), was still in the works (yellow), or needed to be flagged for whatever reason (red). But sometimes the original JP column would CHANGE after I had already translated and finalized a line... but their designations weren't as clear, so we didn't really know when something had been changed so that we knew to update the EN, etc... I don't think this happened all that often, but I do faintly remember being freaked out about it and scrambling to update the EN translation to match.

So, I guess I'd like to say, rather than so readily jumping to conclusions that the translator has less than par knowledge of JP->EN translation, that there are MANY things that take place in between than no consumer is ever going to see or experience unless they do this job themselves. That's why I sometimes feel it necessary to push back on some of these comments here and there. Although I understand the consumer point of view, there's also many unspoken circumstances on the development end that can cause these things to happen.

I can't say what exactly happened to cause this particular issue, as it's clear the subject lies with Cloud rather than Tifa or the other kids... but I kinda get the feeling that something physical with the actual translation document may have caused this issue rather than a blatant translation error. I suppose errors like this aren't impossible, but rather unlikely, so I'd like to think that something else unfortunately converged to reach this conclusion.

My main thing is... I really wish people would stop blaming the translator directly as the source of all discrepancies... as there are MANY variables at play. And people are human. We make mistakes. Not everyone is a multi-year, experienced translator on any given project; but that doesn't mean we don't have many people above us doing the proof-reading and all sorts of other stuff as well.

Granted, we are taught to only 100% greenlight any given cel until after we've checked for errors... but like I said before, we're only human and can make mistakes. That's where it's super helpful to get an editor or two (simply having a different set of eyes is BEYOND helpful, because it's psychologically proven that it's harder to notice typos in your own writing because the brain tends to read beyond what's actually written on the page because it's your own words...)

When we're talking about the PS1 days, I believe it was more common to have a single individual working on the translation (including proofreading, etc.). So, simply going off my experience in the early 2020s... I can only imagine how difficult it was to navigate the documents in the mid to late 90s... It's amazing anything turned out as well as it did!

So, although I think there are moments in which we can point our fingers directly at individual translators, that's not the majority of the industry. There's so much other stuff going on that can affect the overall translation that has nothing to do with the translators involved, so it seems a little disingenuous to consistently blame them all the time.

[pacitra @pacitra_]

furioso.
#libraryofruina #roland

[Soleador @Chessbasssm]

El videojuego es el medio artistico con el peor fandom. Rara vez un lector no disfruta de leer, o un cinefilo no disfruta del recurso audiovisual en una peli, pero los videojuegos estan infestados de gente que odian las mecánicas y solo les importan cosas superficiales del medio.

[Isaac5020 @goats0652]

#MGS
久違的更新，是委託

[K1MI @k1ml_999]

#LibraryofRuina
망설임이 앞으로 나아가게 하지는 않겠지.
Nothing will change if I don’t make a move.
❤️‍🔥🪽

[aqua @aqua_wavez]

🚨🚨!!!ENORMOUS SALE ALERT!!!🚨🚨

In case you missed it, Limbus Company is 100% OFF for the Steam Summer Sale!

Totally FREE!!!!!!!!!!!!!! Don't miss your chance to grab it, this deal won't last forever!!

[Ring Maestro Yume (💍 | 🪶) #ringtwt @ringposting]

Aaand... Here it is! The last definitely-not-specific character dynamic! Yep.