WJHB

Talked to a professional translator about it and they didn't know either, lol. I'll keep going and come back to it eventually.

Unfortunately I've hit my first roadblock: Keika and her friends' conversation in the 4th chapter is really confusing to me. I think I've generally been able to make sense of it, but I didn't know what the deal was with these lines. https://pastebin.com/7sTDkZN6 I understand what the words mean typically, but I figure they're using some colloquialisms because it doesn't make too much sense to me in context. I might leave it until I can get another opinion. I fixed this but gitgud seems to be down for maintenance so I haven't pushed my changes yet. Edit: Pushed them.

In my winter break ennui-fueled translation spree I've finished the second hypnosis scene. Again, criticism welcome, and again, don't expect me to maintain this pace once the semester starts. https://gitgud.io/WJHB/saimin-yuugi-translation/-/tree/rui I haven't bothered to merge the upstream changes back into my branch or significantly modify my workflow (I don't mind doing word wrap manually and the commas fuck up the spacing anyway.)

What advantage does that have over just using newlines? Is it for organizational purposes?

Update: I've finished the first two scripts in Rui route (about 700 lines and covers her first hypnosis scene.) If anyone notices mistakes or wants to give feedback let me know. I probably won't be able to maintain this pace once I go back to college but I'll try to be consistent and work on it for at least half an hour or so a day. https://drive.google.com/file/d/1a3irdhvHpJbu75BD3EnkwRYXq03jetV1/view?usp=sharing

Could just go with data9.pack then. I wonder if there's some way to put the TL in the same .pack as the UI stuff, though.

I've been using (and vote for) no quotation marks, since a lot of VNs do that, and also because there are several inline quoted phrases that I'd have to use single quotes for otherwise. No strong preference, though. I'll try to figure out how to rework my fork around the new structure. Edit: One other thing with regard to the engine is that I can't get the ö in Schrödinger to display properly. It just gets changed to a normal o when I pack it. Haven't managed to get Sisulizer's scripts working so I haven't tried those. It's not the end of the world but it'll bug me if I don't fix it. Also I might suggest that the folder in the repo be named data8.pack since that's what I've been packing it as. Seems better to just use a higher number instead of renaming the old data6.pack to make room for the new one.

For the sake of organization: who here actually knows Japanese and is willing to work on the translation? I received a DM from someone who wants to hire a freelance translator to help, but I want to make sure things are reasonably coordinated.

I'd really rather not use Google Translate for the patch, even if it means slowing down the release. If that's what someone wanted to play, they could just use Textractor. That's what I did when I didn't know as much Japanese as I do now, but now I've read the game in full without it. Once we have more done we'd definitely need editors and such, though, so there'd be room for you to help out.

That actually turned up when I googled a phrase from the route, lol. I looked at it a bit but I had a lot of changes I wanted to make.

Haven't found much time to mess around with them because I'm with my family for Christmas, but I'll make sure to keep you posted when I take a look.

I figured whether or not the text is dialogue would be obvious by the name of the speaker, but if other people think quotation marks are better, that's fine too. I think we should go with some variation of English quotation marks instead of Japanese ones if we do that option, though. Also, does anyone know if QLiE has comment functionality? I'd like somewhere to keep notes on my translation decisions. I guess I could just switch over to using the format Sisulizer suggested.

I'm still using the .s files. I'll look at the txt stuff when I get home tomorrow, but I don't mind working with the .s files directly. Whatever's easier for everyone else. Here's my fork: https://gitgud.io/WJHB/saimin-yuugi-translation/-/tree/rui Should I make a merge request now and just leave it open or wait until I'm done to open the request?

What could be worth ironing out are stylistic choices for the translation. I've generally adhered to what HMFan did, which included: - Present tense narration - Leaving a space after ellipses - Leaving honorifics in - Leaving "Sensei" untranslated when used to address Rui, though I'd occasionally replace it with "you," since 2nd person pronouns are more common in English Like I mentioned earlier, I decided to use an alternate comma symbol (，) since QLiE doesn't work well with normal commas, but that's easy enough to do a find and replace on after the translation is more complete.

What I've been doing is using GarBRO to extract the scenarios from data6.pack in the game files, changing the Japanese lines to English in the .s files, then using the tool that was linked earlier (https://github.com/amayra/arc_conv) to repack them. The command is just arc_conv.exe --pack qlie [UNPACKED DATA FOLDER] [DESTINATION PATH] This produces a patched version of data6.pack that can replace the original. It only took me all of one hour to figure this out, so I really don't think onboarding/hacking will be a roadblock at all. The tools for patching QLiE already exist, so we won't need to do much reverse engineering. Due to that, I expect the translation will take MUCH longer than the programming. I haven't messed around with the stuff Sisulizer linked yet, but I doubt it's that complex either.

Oh, I forgot to mention, but I got arc_conv working for script repacking. Translating a Schrodinger's cat line feels like a rite of passage as a VN translator. I guess I should switch it to have the dots above the o though.

I guess I'll copy my changes to those scripts as well. Also, I've never used git on Windows before, only Linux. I set it to commit CRLF as CRLF instead of converting to LF, since I assume this isn't a cross-platform project. Is that the right option?

I'll just go ahead and get started on Rui's route then. I noticed QLiE doesn't play nice with commas (also that it's whitespace agnostic which is painfully retarded for a VN scripting engine imo,) and that HMFan got around it by using the Japanese comma instead. I think that looks bad so I went with "，" which looks a lot nicer. I can't unpack HMFan's patch with GarBRO myself, but the scripts are in the file in plaintext, so I could still extract and edit them. As an aside: Jesus Christ are sex scenes annoying to translate. I don't know how to make 悶える not sound stupid when Octopus uses it every three lines.