Ah, cool. Yeah, I totally understand not wanting to mess up the formatting of the code and that you'd get a lot of false negatives due to the word processor thinking parts of the code are bad grammar. But even tossing the rpy files directly in, it seemed fairly easy to pick up on the dialogue lines that were marked and ignore the coding ones. At least this was the case for Google Docs... not sure about other word processors.Thanks for the kind words and taking the time to let me know of the issues. I'm certainly not immune to making grammar errors, so using a helper tool makes great sense!
Spoiler alert (warning: contains whiny self-justification as to why it's not my fault)
You don't have permission to view the spoiler content. Log in or register now.
Regarding your suggestion, I previously have never used a word processor or grammar checker when doing edits simply because of the risk of accidental formatting changes breaking the code, and "sea of red squiggles" effect due to the renpy commands being too dense to see spelling or grammar concerns.
However your comment has made me revisit, and with a little searching I discovered that the renpy dev launcher has a function to export the dialogue as a TAB file intended for use by translators. I agree this would be perfect to use as a grammar checker pass after the work to "edit where needed to make characters sound like native speakers" is complete, and I will start doing so going forward (and probably go back over the previous chapters too!)
Thanks again for the support![]()
Anyways, glad my suggestion might be helpful.