@matt Please let me know your preferences - do you prefer to edit/discuss SRT file on GitHub (via PR) or use Google Documents? Any other tool?
Sorry, didnāt see your latest post until I posted mine. Iām good with Github if you prefer that. MattJordan (Matt Jordan) Ā· GitHub
But I can also do Google docs as well. Iām pretty flexible.
Well, I think it will be easier to handle discussions in Google Docs, so letās go with it. ^___^
Konstantin,
Maybe I missed something but I didnāt see where to find an existing Google doc to start from. Or am I supposed to create one? I probably should have asked about that yesterday to clarify but I didnāt think to do so. Sorry about that. I did read through the SRT file and I can see that it wonāt take me long to make a few suggestions. So I can probably do a first draft tonight after work if I know where to do it. Apologies again if I missed something obvious.
Hi Matt! No problem!
Yes, can you create a new Google Document please? Thank you for your help!
Okay, here is a first pass in a Google Doc. I took the approach of highlighting a section and giving an alternate suggestion in a comment. Let me know if that doesnāt make sense.
The existing version is very understandable and I think most English readers would have no trouble following along. So my suggestions are really just what I think would be a little more native or natural English. Of course Iām from the USA, so I tried not to over-Americanize it and really just focus on smoothing the flow where I thought it might help. But, like I said, the original isnāt hard to follow and I think I only found one actual typo.
Let me know if anything is unclear, etc. And it wonāt hurt my feelings at all if you donāt use my suggestions. I can also apply any or all of these in a PR against the SRT file if you want. Hereās the link:
Awesome!
I like this approach!
I will review that carefully and write my comments in Doc. Thank you so much!
Hi Matt! I have reviewed all changes - there are just a few places where I put comments, lease check.
Yes, smoothing the flow, catching grammar errors and ensuring the text is clear to understand - thatās what we were after. Thank you!
Yes, it would be really good if you can make a PR with final version here - GitHub - morevnaproject-org/morevna-translations-en
This GitHub repo is intended to be temporary storage for results of our translation activities and I plan to clean up it from time to time. But committing changes there will allow other people who contributed to translation to see the fixes and learn from them.
Sounds good. Iāll either catch up later this evening or first thing tomorrow (Saturday) morning.
Hi, Matt! Any news on this?
Sorry, the weekend has been a little busier than I anticipated, but I should be able to get to it this evening.
Okay, I responded to your questions and comments. I didnāt go ahead and do the PR yet mostly because a couple of my responses gave options. But I can do that tomorrow evening after work if you want. Just let me know. And apologies again for not being able to get to it as quickly as Iād originally hoped this weekend.
Hi! No problem about delays, I just happy the process is moving!
I have responded all comments and added all changes. I think weāre ready for PR now.
Hi Matt! I was unable to accept my edits in Google Docs (because I am not the owner of the document), so I have applied all edits to a separate SRT file and uploaded it to this topic - [Voicing-En] Pepper&Carrot Backstage Vol. 1
You can use this SRT file for PR.
Oh, sorry about that. I probably should have added some permissions or something and didnāt think to do it. Anyway, Iāll open the PR.
No problem, this happens for me too from time to time
Looking forward for PR! Thank you! ^___^
Okay, I think I opened the PR to the right repo and branch. This is the first time doing this outside of my company day job, so let me know if anything went wrong and Iāll try to fix it.
Looks great! Thank you so much for your help! Marking this as āsolvedā.
Glad I could help and thanks for your patience!