Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dialogue Errors Found During After Story and Prologue #8

Closed
Wandering-Heiho opened this issue Jan 28, 2021 · 1 comment
Closed

Dialogue Errors Found During After Story and Prologue #8

Wandering-Heiho opened this issue Jan 28, 2021 · 1 comment

Comments

@Wandering-Heiho
Copy link

@Wandering-Heiho Wandering-Heiho commented Jan 28, 2021

After Story

I think based on his dialogue before and after this, Ax means to use "your" instead of "our".
NPJH50625_00000
line 195 in script/input/mp_0117.tsv


Considering that Lupus brings up that Noi has lost her memory immediately after this, I believe he is supposed to be referring to the Sea Ruins, as that's where Noi landed this time (or it could be changed to just "ruins", as there are multiple in the sea).
NPJH50625_00001
NPJH50625_00002
line 205 in script/input/mp_0000.tsv


Just a small inconsistency with a quest name. Started and completed text call it "Offering for Ancestors", but the mailbox and quest menu calls it "Ancestral Offering".
NPJH50625_00003
NPJH50625_00004


Despite giving Cygna the title at earlier points in this conversation, Noi does not refer to him as "Lord Cygna" here.
NPJH50625_00006
line 77 in script/input/mp_8100b.tsv


Prologue

I think this would flow better if "much" was changed to "many".
NPJH50625_00000
line 212 in script/input/mp_0001.tsv


I think Nayuta meant to say "Hey, girl, wanna come over to my house?".
NPJH50625_00001
line 176 in script/input/mp_0001.tsv


Fairly certain that "should" and "we" are supposed to be in the opposite order here.
NPJH50625_00002
line 93 in script/input/mp_0004.tsv


I believe there should be an "is" after "This".
NPJH50625_00003
line 476 in script/input/mp_0004.tsv


"to" doesn't really work in this statement followed by "gotta" in my opinion.
NPJH50625_00004
line 349 in script/input/mp_0003.tsv

@dackst
Copy link
Owner

@dackst dackst commented Jan 29, 2021

(or it could be changed to just "ruins", as there are multiple in the sea).

The Japanese line is "突如光とともに遺跡に降ってきた妖精ノイ。", which as far as I can determine, doesn't specify either the Sea Ruins (海上の遺跡) or the tower (遺跡塔). The tower thing was carried over from the original translation, which for some reason specified "ruined tower". So you're right, and it should be just ruins.

Just a small inconsistency with a quest name. Started and completed text call it "Offering for Ancestors", but the mailbox and quest menu calls it "Ancestral Offering".

I was sure that I went and made them all consistent, but I guess I must have shortened "Offering for Ancestors" to prevent text overlapping in the mailbox at some point after that.

Despite giving Cygna the title at earlier points in this conversation, Noi does not refer to him as "Lord Cygna" here.

This particular line in Japanese starts with "Kureha-sama to Siguna" (クレハ様とシグナ……). I rechecked the scenes immediately before this where she uses "Lord Cygna", and in Japanese, they mostly appear as "Kureha-sama-tachi". I don't want to say "Lady Creha and the others" here when there's only one other, everyone knows who it is, and one doesn't seem to take much priority over the others (I can remember a lot of Zext-tachis before Selam's name is revealed that were shortened to either Zext or just "them"). She uses "Siguna-sama" (シグナ様) in other lines.

But then I noticed that "Siguna-sama" is only used when she doesn't have her memories, so maybe it's supposed to indicate she doesn't personally know Cygna, and then she drops the "sama" after regaining them? Not something that I realized before. Anyway, I'll get rid of every other "Lord" after she regains her memories instead.

I think this would flow better if "much" was changed to "many".

This was something I couldn't figure out which was correct, and everything I could find that said "much people" is absolutely bad weren't using it in the same way in their examples. But might as well change it to "many" anyway, I haven't seen anything that says "many people" is bad.

dackst added a commit that referenced this issue Jan 29, 2021
@dackst dackst closed this Jan 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants