78
edits
User talk:LpSamuelm: Difference between revisions
m
That's a syntax thing.
(-> Gen III character encoding) |
m (That's a syntax thing.) |
||
| Line 124: | Line 124: | ||
::: '''"Iterational"''' isn't just "not without problems", the fact that it's a made-up word makes its very existence a problem. Change "version" to something else if you ''really'' want to, just don't choose a word that doesn't exist. | ::: '''"Iterational"''' isn't just "not without problems", the fact that it's a made-up word makes its very existence a problem. Change "version" to something else if you ''really'' want to, just don't choose a word that doesn't exist. | ||
::: '''"Earlier games":''' It's important that the text mentions that the dark gray characters display as spaces not only in Emerald, but also in FireRed and LeafGreen. In your version of the text, that is mentioned literally nowhere. Not only that, but even if it were mentioned later, it is incredibly misleading to say that they display as Japanese characters in "earlier games" - FireRed and LeafGreen came out earlier than Emerald did, yet they don't contain the Japanese characters. Why even be so vague - "earlier games" - when you can simply say "Ruby and Sapphire" and be both accurate and concise? Don't. | ::: '''"Earlier games":''' It's important that the text mentions that the dark gray characters display as spaces not only in Emerald, but also in FireRed and LeafGreen. In your version of the text, that is mentioned literally nowhere. Not only that, but even if it were mentioned later, it is incredibly misleading to say that they display as Japanese characters in "earlier games" - FireRed and LeafGreen came out earlier than Emerald did, yet they don't contain the Japanese characters. Why even be so vague - "earlier games" - when you can simply say "Ruby and Sapphire" and be both accurate and concise? Don't. | ||
::: '''Dotted underline:''' The characters do have a dotted underline. The fact that it's implemented as a border on a span is irrelevant. To the reader's eyes, the characters do have an underline that's slightly wider than the character itself. I should point out, too, that the boxes in fact don't have underlines. That'd be a | ::: '''Dotted underline:''' The characters do have a dotted underline. The fact that it's implemented as a border on a span is irrelevant. To the reader's eyes, the characters do have an underline that's slightly wider than the character itself. I should point out, too, that the boxes in fact don't have underlines. That'd be a <code>border-bottom</code> on the actual table cell, which isn't the case. | ||
::: '''Quotation marks information:''' Mentioning it where it's actually detailed makes the most sense, of course. Don't remove clarity and information just to make an article shorter. "Concise" and "short" aren't the same thing - you're actively ''hurting'' the clarity and information content of the article by removing paragraphs like that one. Pointing out differences and their implications specifically beyond the contents of a table is not a bad thing; leave it. | ::: '''Quotation marks information:''' Mentioning it where it's actually detailed makes the most sense, of course. Don't remove clarity and information just to make an article shorter. "Concise" and "short" aren't the same thing - you're actively ''hurting'' the clarity and information content of the article by removing paragraphs like that one. Pointing out differences and their implications specifically beyond the contents of a table is not a bad thing; leave it. | ||
::: '''2-dot leader:''' Yes, I am also on Firefox. Feel free to change the 2-dot leader to look more like a 2-dot leader on your computer. Don't leave it simply as "・・", however, as that simply doesn't reflect how the character looks in-game. Decrease the 0.5em value to 0.33em or something, perhaps (preview: "<span style="letter-spacing: -0.33em;"><small>・・</small></span>"). | ::: '''2-dot leader:''' Yes, I am also on Firefox. Feel free to change the 2-dot leader to look more like a 2-dot leader on your computer. Don't leave it simply as "・・", however, as that simply doesn't reflect how the character looks in-game. Decrease the 0.5em value to 0.33em or something, perhaps (preview: "<span style="letter-spacing: -0.33em;"><small>・・</small></span>"). | ||
::: '''"Displays as":''' I'm very whatever about that whole thing. "Displays as" sounds entirely natural to my ears: if you put <code>0x01</code> in a nickname, it displays as "À". Mixing up "prints", "prints as", "displays as", and "is" (which is also used in the article) leads to less repetition and a more varied language, which of course is a good thing. If you'd like to change that based on your whims, however, sure. It doesn't matter a whole lot. | ::: '''"Displays as":''' I'm very whatever about that whole thing. "Displays as" sounds entirely natural to my ears: if you put <code>0x01</code> in a nickname, it displays as "À". Mixing up "prints", "prints as", "displays as", and "is" (which is also used in the article) leads to less repetition and a more varied language, which of course is a good thing. If you'd like to change that based on your whims, however, sure. It doesn't matter a whole lot. | ||
:::[[User:LpSamuelm|LpSamuelm]] ([[User talk:LpSamuelm|talk]]) 03:17, 16 April 2017 (UTC) | :::[[User:LpSamuelm|LpSamuelm]] ([[User talk:LpSamuelm|talk]]) 03:17, 16 April 2017 (UTC) | ||