Of course! Awesome.
Well good job.
![6Pn3tl3[1].png](https://ulmf.org/data/attachments/44/44813-aa9f08f3def272b4c20b43d1371378a4.jpg "6Pn3tl3[1].png")
![cejreTs[1].png](https://ulmf.org/data/attachments/44/44814-0d79fa1366738ce29b48c857bb0afa1e.jpg "cejreTs[1].png")
No worries I'll keep striking the iron so it remains hot
there's still a lot I need to do to pave your (future) way.The answer is in the name, splice.
# not actually
IN = "「#{target}が脱ぐところ、見せてぇ\\H\n ね、#{myname}も裸だし、いいでしょ？\\H」"
# but
IN = [target,
"が脱ぐところ、見せてぇ\\H\n ね、",
myname,
"も裸だし、いいでしょ？\\H"]
# then
for i in IN:
isinstance(i, str) ? SR_Translate(i) : SR_Convert(i)
# I suppose ʕ·ᴥ·ʔ?"\w\x\y\z" == "wxyz" #true...![yEmQCWo[1].png](https://ulmf.org/data/attachments/44/44819-175e3b1c0cad6c239980b475cb0a342c.jpg "yEmQCWo[1].png")
![jApnVd5[1].png](https://ulmf.org/data/attachments/44/44820-aa4169913b55d814344a9c5b22bb0d30.jpg "jApnVd5[1].png")
![Qy8PY7v[1].png](https://ulmf.org/data/attachments/44/44821-1498faf8eef29f4df6fbf3aa1773269e.jpg "Qy8PY7v[1].png")
Well based on my light experience in these kind of stuff when you try to put something between two things connected as far as I remember you need to hook the first and the second and let the base program in the game read the new pattern. I know my technical explanations in english are lacking a lot but is something that I've been always told years ago when I started to "change things" for fun with a with friends. Well time flies.
Maybe you've noticed already but in the CommonEvent files there are things like AP absorption and Sucking if I remeber correctly that they give you an error but the game won't crash.
Yes, these can be fine. I tried 2-3 times before. But you probably used T++ more often and longer than I did. In any case, whatever T++ breaks can be fixed.
「うふふっ♪
いいのかな～、そんな事言っちゃって～❤
他の娘が怒っちゃうよ？」# needs to be run from \Graphics\Battlers\O_MOD
text = []
#lutz - https://stackoverflow.com/questions/954504/how-to-get-files-in-a-directory-including-all-subdirectories
for dirpath, dirnames, filenames in os.walk('./'):
if exists(os.path.join(dirpath, "ability_name.rb")):
print(dirpath)
fp = open(os.path.join(dirpath, "ability_name.rb"), 'r', encoding='utf-8', errors='ignore')
for line in fp:
# write_csv({line.lstrip(" ") : "\"\""}, "ability_names.csv") # also worked out
text.append(line)
text = set(text)
with open("ability_names.rb", 'a+', encoding="utf-8") as file:
for i in text:
# i = "[\"" + i + "\", \"\"],"
file.write(i + "\n")
(+the wielding succubi for reference)
I'm not sure I follow what you're saying here? The word wrap (\n) is currently placed no more than 53 characters in with every line. It's impossible to maintain the same character wrapping as the Japanese version does for every sentence if you mean placing line breaks exactly where they do, so don't get too worked up over that. Some compromises have to be made in the wrapping. But I do try to fit similar line breaks where I can, assuming it's possible with the limited character space.
Interpolation happens before the sentence is displayed. You can have a 14 million character line and nothing would break until it was displayed. It's therefore up to the translator to avoid writing lines that are too long.
Sorry, but I'm making an executive decision to say no on this. While I understand they have a unique appeal because you don't see them in your day-to-day life, they are simply Japanese quotation marks. As such,「」just does not have a place in an English translation.
I add a thing that I noticed aswell. The actual text in the .rb files the dialogues for every character that implement "#(target) and the target is the MC is 95% made for the male protagonist.
It would take rewriting the actual code of the game which I am not particularly interested in. As it is, the translation .csv files do not touch the code at all outside of string interpolation (e.g. {myname}). The patcher also does not modify code, it only adds to it (and in as much of a non-invasive way as possible).
Rewriting codes takes a lot of time too. If I remember correctly there are (myname), (target), (partner), (speaker) and (master). (target) for succubus to succubus talk can be replaced with "you" maybe for all the succubi. I'll check if this is the case for every succubus and the (target) words are all in the 00_System talk folder.
).
action = premess + "<string>"action.gsub!("", "")! call which replaces a substring in the aforementioned actionaction += "" which appends to the end of the current action string.waist = ["random1", "random2", "random3"]
waist.push("random4", "random5")
waist = waist[rand(waist.size)]
#action = (string using the interpolated waist variable, i.e. #{waist})self.bust_translate(action) which is literally just action.gsub!("", "") embedded in SR_Util for some reason.A sound argument (except I do see 「」on most days, esp. now). But I won't mention that again. I do like them but they indeed do nor belong in an English sentence; or arguably, only to emphasize one specific word which must sound 'Foreign' in context.
I'm actually using the 『』 quotation marks in these specific instances since English doesn't have an equivalent. Technically we have a partial equivalent in the form of '' but they aren't all encompassing for the purposes 『』are used for. For example, from the intro: 『Dream Interference』. In English, with the titles of works, we use several different forms of text formatting depending on the work. Some of these aren't available in RGSS unfortunately. I could look at scripting them in, and I might, but this isn't in the cards right now.
You do make a good point about removing quotation marks since dialogue is tagged regardless. This is already done in map dialogue so I'll start doing this in combat dialogue as well actually.
I don't need them personally. If you feel you need them for other code you're running outside of Talk, I've already tagged the line with a comment that removes them. I personally will not be adding them to the .csv files because they're extraneous and the Japanese lines can get long enough as is, with some of them already causing my .csv editor to create a second row with word-wrapping to fit them on the screen.
Yeah, that's the point I'm at. I've duplicated the O_Mod skilltext file and have changed it to 魔_English_MOD_RPG_Skilltext.rb instead to work out of that. There's too many substitute calls to reliably translate the text into English because all of the substitutions were made with Japanese in mind. Doing the same thing with the Talk files isn't possible in this case.
Some write-up of what's going on here would be nice, as I've only continually seen vague allusions to this issue. I've tried digging around through various threads now and have not actually seen anyone talk about what's actually causing this issue in the slice loop or why it's "infamous".
I've alluded to it, there's some talk about that starting page 2. And we'll definitely need to talk about this before you tackle skilltext, and the rest.
This seems like it was blown up into way more of an issue than it actually is. I'll take a look at it in depth tonight.
It was
