User talk:LpSamuelm

Welcome

Welcome to Bulbapedia, LpSamuelm! Here are a few links to help you get started:

Manual of Style The Manual of Style, or MoS, outlines the format of all pages on Bulbapedia. Need a hand? Our friendly team of staff are here to help! Talk to them if you have any questions or problems with Bulbapedia.

Signatures On talk pages, please sign your comments with four tildes (~~~~), or by using the "Your signature with a timestamp" () button at the top of the edit window. Userspace Policy On Bulbapedia, the ability to edit personal userpages is a privilege. Per our userpage policy, this must be earned by first making constructive edits to the mainspace. Once you can, remember to keep userspace edits (edits to User:LpSamuelm) to a minimum. For a complete list of policies and editing advice, please see the Welcome Portal.  Thank you, and have a good time editing here!   «ιɴsσмɴιαc» 10:57, 6 June 2010 (UTC)

Monospace/Gen II save data

Do you actually have some "real" reason the tables under checksum shouldn't have the whole cells in monospace? Is there a actually some significant problem with "to" being in the same font? It's the easiest solution; it looks fine. I get that your intention is to put the font on the hex values, but I don't know any reason why it's so terrible that "to" be in the same font. In other cases, I'd be happy to leave "to" out; and that's possible here, but doing it is just more trouble than it's worth (AFAIK). Tiddlywinks (talk) 21:07, 19 April 2016 (UTC)

Well, the reason they're in monospace at all is to set the hex values apart. tags are for just that - setting apart code. Having the entire sentence (which "[x] to [y]" is) in monospace makes it seem like it was taken straight from a .txt. Honestly I would've kept the tags even in the code-only cells in order to keep the formatting uniform, but it doesn't really matter as much there. So basically, to separate text content and code content.

Another formatting that would work, I suppose, would be to split the table up into a table with a "from" column and a "to" column - that'd be fine too, as the code and text would be separated in style in that case too. LpSamuelm (talk) 21:19, 19 April 2016 (UTC)

In lots of text, it's certainly worth setting apart the hex values. But in those tables, it's not (at all) hard to identify the relevant values, even with "to" in the same font. Can I ask you to just do something so that the code tags aren't used in the table? Either setting the whole row monospace again, or making from/to columns, or something. (Honestly, I tried from/to columns before and didn't like it. But...) I'll leave it to you, but those code tag formats are just too out of place in a table.

(P.S. If you removed the welcome template on purpose: please don't.) Tiddlywinks (talk) 21:26, 19 April 2016 (UTC)

I really liked code tags in the table, at least. Felt consistent, and was pretty enough. But sure, if it makes you happy it can't be that bad. LpSamuelm (talk) 21:32, 19 April 2016 (UTC)