User talk:LpSamuelm: Difference between revisions
From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
Tiddlywinks (talk | contribs) m (→Welcome: IDK why that's breaking, but it works fine after being subst'd) |
No edit summary |
||
| Line 1: | Line 1: | ||
==Monospace/Gen II save data== | ==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). [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 21:07, 19 April 2016 (UTC) | 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). [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 21:07, 19 April 2016 (UTC) | ||
:Well, the reason they're in monospace at all is to set the hex values apart. <code><code></code> 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 <code><code></code> 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. [[User:LpSamuelm|LpSamuelm]] ([[User talk:LpSamuelm|talk]]) 21:19, 19 April 2016 (UTC) | |||
Revision as of 21:19, 19 April 2016
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 thetags 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)
