English grammar and typos

[ghost]

In the SRD, the grammar is inconsistent: armor, defense, color, and favor, yet also favour, travelling, metre (except once).

The Design Mechanism is based in Canada, and as far as I can tell, the Mythras rulebook always used the English grammar standards for Canada, which are the international standards of the Commonwealth, the most of the English-speaking countries.

There are also several issues of text duplication, such as: Character – Step 3: Attributes – Luck Points:

Re-roll the dice, ifdice if they are unfavourableunfavorable.

But it is not present on the srd-mythras-net, so the website must use some different source. Or I don't know. Cheers anyway.

[Unclebaby]

Hello @Eye-of-Argonia,

I hadn't noticed all the other un-American bits Raleel left. I knew he had come for our armoUr though.

However, I have been working on the SRD repo rather than the Imperative one. I thought the public-facing SRD website is the more pressing but I'll come back to look at these when I'm done there.

I'll look at the other -OUR words though. In fact I'll make a semi-duplicate of this issue over there.

I'm not sure how far you are through it but some of what I've done on the SRD is standardising formatting. While it's not necessarily good to have the same format for the website and local text versions we should probably work to some kind of style guide.

[raleel]

As he points out, he’s working on the website repo, and that one is more up to date. The other one has some errors based on me not accepting changes on a word doc before I converted to markdown, so you see things like “Similar toLike” in the text, where the corrected and uncorrected version both appear. I’m going to update that one today, but the website has far too much other work at this point to do that to. So we’ll go through and fix those errors and flog me later.I will note, the classic fantasy one doesn’t have nearly this level of issue, as I had the doc for several months before hand and made many passes and accepted all the changes first. Essentially, I’ve gone through with the Word editor and fixed a lot of errors. Yes, some of it was converting from British English to American English, which is not an error per se, but a preference. However, there was a fair chunk of smoothing out of text, correcting style, spelling errors, and so on. At some point I accepted I was ok with this version not being an identical copy of the TDM published doc. The intent is still there, and we are not making any material changes that put it in conflict with RAW. However, there are some errors where things are straight up missing and required by the rules and we are fixing those. I hope this explains why it is the way it is :)Sent from my iPadOn Feb 18, 2024, at 5:21 AM, Uncle Baby @.***> wrote: Hello @Eye-of-Argonia, I hadn't noticed all the other un-American bits Raleel left. I knew he had come for our armoUr though. However, I have been working on the SRD repo rather than the Imperative one. I thought the public-facing SRD website is the more pressing but I'll come back to look at these when I'm done there. I'll look at the other -OUR words though. In fact I'll make a semi-duplicate of this issue over there. I'm not sure how far you are through it but some of what I've done on the SRD is standardising formatting. While it's not necessarily good to have the same format for the website and local text versions we should probably work to some kind of style guide.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Unclebaby]

If it helps, and if my edits look right, the SRD versions could be copied and pasted back into the Imperative local file version, overwriting the previous.

[raleel]

Possible, but a bit tedious. As you know the website one is broken up into pages. Sent from my iPadOn Feb 18, 2024, at 7:04 AM, Uncle Baby @.***> wrote: If it helps, and if my edits look right, the SRD versions could be copied and pasted back into the Imperative local file version, overwriting the previous.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>