User talk:ArrowHead294

D&D's guide edits

Hey there. Thanks for taking so much interest in D&D's Guide to RTT.

Also, I don't know the origin of your user name, but it makes me think of Sagittal notation, which is the other thing Dave Keenan helped to create and that I spend a lot of my time helping him with. (Sagittal notation is all about arrows; Sagittarius is the mythological archer.) I tried contacting you on Discord but got no reply, so I'm trying here now.

I was wondering if you were done making your pass across the Guide, making all those little formatting changes? When you're done, I was thinking I would scan over the whole thing and take screenshots of where things look different, and ask if/why those differences are important to you so we can discuss. Or if they're not important or intentional for you and they are important to me, then I would like them changed back.

I'm sure there will be some improvements because I recently re-read the whole thing before presenting on it at a conference and was noticing all sorts of little issues but didn't have the time to patch them. But I was somewhat following along the past month or so when you were making all those changes, and many of them I wasn't sure about.

--Cmloegcmluin (talk) 04:33, 22 October 2024 (UTC)

Hi again. I see you edited this page soon after I added this, so you must have seen the above message. But you have resumed modifying the guide without responding to me here. Please let me know what you're thinking. Thank you. --Cmloegcmluin (talk) 23:35, 26 October 2024 (UTC)

Sorry for waiting so long.

On these pages, I've been mostly:

• Tweaking the Wiki markup according to what I've seen to be best practices, in particular:
  • Adding spaces to section headers and markup for tables to make them easier to read for those making edits (without them the markup looks cluttered, especially in tables)
  • Putting {{nowrap}} around many non-TeX mathematical expressions so that they stay intact
  • Capitalising things that weren't (or didn't seem to be) properly capitalised
• Adding \left and \right to LaTeX-typeset formulæ in order to make brackets show up correctly
• Removing some linebreaks that I think are or were unnecessary
• Wrapping pre-formatted text in <pre> tags to make them easier to distinguish when looking at the source

I've also been told that inline LaTeX formulæ can look messy at times.

You can compare and contrast what the markup for the page in the revision history. If you have any questions, feel free to reach out to me.

UPDATE November 2024: I've also made use of {{subpage}} to try to remove the need to type out the guide's full name every time you link to another part of it. [math]\overrightarrow{\,\,\scriptsize\text{ArrowHead294}\,\,\,}[/math] (speak to me) 16:13, 1 November 2024 (UTC)

Please fix the broken \abs and \norm LaTeX that you introduced into https://en.xen.wiki/w/Dave_Keenan_%26_Douglas_Blumeyer's_guide_to_RTT/Tuning_computation and anywhere else you might have used them. I notice that \cdot works here, but I found it broken in one of our D&D articles recently and so I just changed it back to the literal unicode character "·". You might want to fix that too, if you haven't already. -- Dave Keenan (talk) 01:07, 12 November 2024 (UTC)

Done. [math]\overrightarrow{\,\,\scriptsize\text{ArrowHead294}\,\,\,}[/math] (speak to me) 13:29, 12 November 2024 (UTC)

Template edit question

Could you plz explain what problem is solved by changes like this? Thanks in advance. FloraC (talk) 15:04, 17 December 2024 (UTC)

Often times, what'll happen if you put categories inside of an <includeonly> tag on a template and then show it on the documentation page, is that the categories will show up on the template page itself despite the tags. The stuff inside the <includeonly> tags will be visible on the transcluded page, and the template will be put into categories it's not meant to be in.

For example, on Template:Who, if Category:Pages with unattributed statements had just an <includeonly> tag without the #if: statement, the template and its associated documentation page would get put inside the category even though they themselves aren't supposed to be there.

The #if: statements I've added explicity check the name of the page (including the Template namespace) in order to exclude the tcategory from its page and the associated documentation. [math]\overrightarrow{\,\,\scriptsize\text{ArrowHead294}\,\,\,}[/math] (speak to me) 15:11, 17 December 2024 (UTC)