Register - Login
Views: 99352184
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-21-22 07:03:41 PM
Jul - The Cutting Room Floor - Formatting guidelines New poll - New thread - New reply
Next newer thread | Next older thread
Liliana
"A horrible person". That's what it says. "A horrible person."

We weren't even testing for that.


Level: NaN


Posts: 2878/-3841
EXP: NaN
For next: 0

Since: 07-23-07


Since last post: 10.2 years
Last activity: 10.1 years
Posted on 06-14-11 12:55:39 PM Link | Quote
We don't have any. This sucks. I'd like to change that!

Two things that seem to be the most troubling:

1. The game's name. Should it be bolded, italicized, or even both? I've seen all possible variants, and nobody seems to know what it should be like, so it's best if we have it fixed somewhere.

2. Should the clear tag appear right after the intro/bob? It has the annoying side effect of leaving a huge whitespace, depending on the length of the bob template, which is especially noticable if you use a higher resolution. On the other hand, there's the obvious problem with images. Again, nobody knows what to do, so people just go by their mind, which is bad.

If we decide on something here, we should add it to the wiki too, on one of the countless help pages.

____________________
Xkeeper

Level: 263


Posts: 19057/25343
EXP: 296649925
For next: 2310528

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 6 days
Last activity: 16 hours
Posted on 06-14-11 11:14:09 PM Link | Quote
1. Bold + Italic in the header, italic elsewhere.

2. No. Images to the left fit best. If there really isn't any way to avoid the text getting crushed between the image and the bob, stuff the TOC above it, clear it, and hope for the best.


"Countless" help pages is funny, because we actually have almost none of them.
rabidabid
Member
Level: 27


Posts: 34/135
EXP: 102339
For next: 13820

Since: 08-25-10


Since last post: 21 days
Last activity: 4 days
Posted on 06-17-11 03:01:09 AM Link | Quote
Another minor inconsistency I noticed is with article names for games that weren't released in the US. I brought it up on Talk:Tsumi to Batsu: Hoshi no Keishousha. I dunno how to go about quoting it so uh... you can read that there.
Liliana
"A horrible person". That's what it says. "A horrible person."

We weren't even testing for that.


Level: NaN


Posts: 2898/-3841
EXP: NaN
For next: 0

Since: 07-23-07


Since last post: 10.2 years
Last activity: 10.1 years
Posted on 06-17-11 03:54:12 AM Link | Quote
Originally posted by rabidabid
Another minor inconsistency I noticed is with article names for games that weren't released in the US. I brought it up on Talk:Tsumi to Batsu: Hoshi no Keishousha. I dunno how to go about quoting it so uh... you can read that there.

I had been thinking you'd use the Japanese name if the game wasn't released in the US. We shouldn't trust fan translations too much, since we don't know if the developer team actually had this name in mind.

____________________
Rachel Mae

Creature of Chaos
Level: 141


Posts: 4129/5929
EXP: 33568268
For next: 551746

Since: 07-03-07

Pronouns: she/her
From: Foxglen

Since last post: 9 days
Last activity: 2 hours
Posted on 06-17-11 05:57:33 AM Link | Quote
Save the article under the original Japanese name, then add redirects for whatever other names it usually goes by outside of Japan.

____________________
YK

Permabanned!
At some point you just have to cease and de-racist.

Level: NaN


Posts: 600/-665
EXP: NaN
For next: 0

Since: 06-25-10

From: Oregon

Since last post: 10.6 years
Last activity: 9.7 years
Posted on 06-19-11 01:00:13 AM Link | Quote
Originally posted by Waffle Ryebread
Save the article under the original Japanese name, then add redirects for whatever other names it usually goes by outside of Japan.


I did that with the Rudra no Hihou page. It was never released in English, so I used the Japanese name, and used the fan translation name ("Treasure of the Rudras") as a redirect. Seems to work best that way. But I'm beginning to wonder if we should put sub-titles in the page name... seems like *every* Japanese game has one, and quite a few English games, too. They're technically part of the title, but they're so rarely *used*...

____________________
Liliana
"A horrible person". That's what it says. "A horrible person."

We weren't even testing for that.


Level: NaN


Posts: 2906/-3841
EXP: NaN
For next: 0

Since: 07-23-07


Since last post: 10.2 years
Last activity: 10.1 years
Posted on 06-19-11 01:01:53 AM Link | Quote
Help:New pages:

If the game has a long title or subtitle, it's a good idea to shorten it as long as you don't make the game unrecognizable (e.g. The Fintstones: The Rescue of Dino & Hoppy is much more suited to being The Flintstones.)

This should answer your question.

____________________
Rachel Mae

Creature of Chaos
Level: 141


Posts: 4135/5929
EXP: 33568268
For next: 551746

Since: 07-03-07

Pronouns: she/her
From: Foxglen

Since last post: 9 days
Last activity: 2 hours
Posted on 06-19-11 01:45:34 AM Link | Quote
If it's very obviously a subtitle, just leave it out. No need to clutter up the game listings with mostly useless .

On the other hand, if it's a sequel and doesn't actually have a "2" or "II" in the title (e.g. "The Flintstones: The Surprise At Dinosaur Peak"), then go ahead and use it.

____________________
Next newer thread | Next older thread
Jul - The Cutting Room Floor - Formatting guidelines New poll - New thread - New reply


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

29 database queries.
Query execution time:  0.083911 seconds
Script execution time:  0.016158 seconds
Total render time:  0.100069 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 272 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 192 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 190 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 192 column 9 - Warning: missing <tr>
line 210 column 13 - Warning: missing <tr>
line 211 column 102 - Warning: unescaped & or unknown entity "&postid"
line 221 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 223 column 9 - Warning: missing <tr>
line 241 column 13 - Warning: missing <tr>
line 242 column 102 - Warning: unescaped & or unknown entity "&postid"
line 247 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 249 column 9 - Warning: missing <tr>
line 267 column 13 - Warning: missing <tr>
line 268 column 102 - Warning: unescaped & or unknown entity "&postid"
line 270 column 192 - Warning: missing </span> before <blockquote>
line 270 column 254 - Warning: inserting implicit <span>
line 270 column 254 - Warning: missing </span> before <hr>
line 270 column 320 - Warning: inserting implicit <span>
line 270 column 320 - Warning: missing </span> before <hr>
line 271 column 1 - Warning: inserting implicit <span>
line 274 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 276 column 9 - Warning: missing <tr>
line 294 column 13 - Warning: missing <tr>
line 295 column 102 - Warning: unescaped & or unknown entity "&postid"
line 297 column 74 - Warning: <style> isn't allowed in <td> elements
line 297 column 9 - Info: <td> previously mentioned
line 300 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 302 column 9 - Warning: missing <tr>
line 320 column 13 - Warning: missing <tr>
line 321 column 102 - Warning: unescaped & or unknown entity "&postid"
line 328 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 330 column 9 - Warning: missing <tr>
line 348 column 13 - Warning: missing <tr>
line 349 column 102 - Warning: unescaped & or unknown entity "&postid"
line 358 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 360 column 9 - Warning: missing <tr>
line 378 column 13 - Warning: missing <tr>
line 379 column 102 - Warning: unescaped & or unknown entity "&postid"
line 381 column 74 - Warning: <style> isn't allowed in <td> elements
line 381 column 9 - Info: <td> previously mentioned
line 386 column 17 - Warning: missing <tr>
line 386 column 17 - Warning: discarding unexpected <table>
line 389 column 35 - Warning: missing <tr>
line 389 column 50 - Warning: missing </font> before </td>
line 389 column 91 - Warning: missing </font> before </table>
line 391 column 35 - Warning: missing <tr>
line 391 column 50 - Warning: missing </font> before </td>
line 392 column 37 - Warning: unescaped & or unknown entity "&id"
line 391 column 192 - Warning: missing </font> before </table>
line 393 column 17 - Warning: discarding unexpected </textarea>
line 393 column 28 - Warning: discarding unexpected </form>
line 393 column 35 - Warning: discarding unexpected </embed>
line 393 column 43 - Warning: discarding unexpected </noembed>
line 393 column 53 - Warning: discarding unexpected </noscript>
line 393 column 64 - Warning: discarding unexpected </noembed>
line 393 column 74 - Warning: discarding unexpected </embed>
line 393 column 82 - Warning: discarding unexpected </table>
line 393 column 90 - Warning: discarding unexpected </table>
line 395 column 9 - Warning: missing </font> before <table>
line 407 column 25 - Warning: discarding unexpected </font>
line 416 column 37 - Warning: discarding unexpected </font>
line 394 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 23 - Warning: <img> lacks "alt" attribute
line 161 column 64 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 187 column 1215 - Warning: <img> lacks "alt" attribute
line 195 column 23 - Warning: <img> lacks "alt" attribute
line 195 column 64 - Warning: <img> lacks "alt" attribute
line 195 column 113 - Warning: <img> lacks "alt" attribute
line 195 column 163 - Warning: <img> lacks "alt" attribute
line 196 column 11 - Warning: <img> lacks "alt" attribute
line 206 column 15 - Warning: <img> lacks "alt" attribute
line 226 column 22 - Warning: <img> lacks "alt" attribute
line 226 column 63 - Warning: <img> lacks "alt" attribute
line 226 column 113 - Warning: <img> lacks "alt" attribute
line 227 column 11 - Warning: <img> lacks "alt" attribute
line 237 column 15 - Warning: <img> lacks "alt" attribute
line 252 column 23 - Warning: <img> lacks "alt" attribute
line 252 column 64 - Warning: <img> lacks "alt" attribute
line 263 column 15 - Warning: <img> lacks "alt" attribute
line 271 column 1032 - Warning: <img> lacks "alt" attribute
line 278 column 11 - Warning: <img> lacks "alt" attribute
line 279 column 23 - Warning: <img> lacks "alt" attribute
line 279 column 64 - Warning: <img> lacks "alt" attribute
line 279 column 113 - Warning: <img> lacks "alt" attribute
line 279 column 163 - Warning: <img> lacks "alt" attribute
line 280 column 11 - Warning: <img> lacks "alt" attribute
line 290 column 15 - Warning: <img> lacks "alt" attribute
line 305 column 23 - Warning: <img> lacks "alt" attribute
line 305 column 64 - Warning: <img> lacks "alt" attribute
line 306 column 11 - Warning: <img> lacks "alt" attribute
line 316 column 15 - Warning: <img> lacks "alt" attribute
line 325 column 779 - Warning: <img> lacks "alt" attribute
line 333 column 23 - Warning: <img> lacks "alt" attribute
line 333 column 64 - Warning: <img> lacks "alt" attribute
line 344 column 15 - Warning: <img> lacks "alt" attribute
line 355 column 772 - Warning: <img> lacks "alt" attribute
line 362 column 11 - Warning: <img> lacks "alt" attribute
line 363 column 23 - Warning: <img> lacks "alt" attribute
line 363 column 64 - Warning: <img> lacks "alt" attribute
line 363 column 113 - Warning: <img> lacks "alt" attribute
line 363 column 163 - Warning: <img> lacks "alt" attribute
line 364 column 11 - Warning: <img> lacks "alt" attribute
line 374 column 15 - Warning: <img> lacks "alt" attribute
line 381 column 2471 - Warning: <img> proprietary attribute value "absmiddle"
line 381 column 2471 - Warning: <img> lacks "alt" attribute
line 392 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 392 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 392 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 401 column 25 - Warning: <img> lacks "alt" attribute
line 406 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 270 column 192 - Warning: trimming empty <span>
line 386 column 17 - Warning: trimming empty <tr>
line 389 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 179 column 74 - Warning: <div> proprietary attribute "width"
line 187 column 1078 - Warning: <div> proprietary attribute "width"
line 211 column 27 - Warning: <nobr> is not approved by W3C
line 242 column 27 - Warning: <nobr> is not approved by W3C
line 268 column 27 - Warning: <nobr> is not approved by W3C
line 270 column 74 - Warning: <div> proprietary attribute "width"
line 271 column 895 - Warning: <div> proprietary attribute "width"
line 295 column 27 - Warning: <nobr> is not approved by W3C
line 321 column 27 - Warning: <nobr> is not approved by W3C
line 349 column 27 - Warning: <nobr> is not approved by W3C
line 351 column 74 - Warning: <div> proprietary attribute "width"
line 355 column 635 - Warning: <div> proprietary attribute "width"
line 379 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 154 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md