Talk:Washington State Route 225/GA1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

GA Review[edit]

Article (edit | visual edit | history) · Article talk (edit | history) · Watch

Reviewer: Arsenikk (talk) 23:33, 31 October 2010 (UTC)[reply]

Comments
  • Remember to state the country.
  • I'm a bit concerned about the conversion in the table. There is no problem with horizontal space, yet the table fails to convert miles to km. Providing the conversion ratios at the bottom just makes things worse: I know very well what the ratio is, but it is a pain to convert.
  • In general, using a backslash is frowned upon and normally an endash is preferred when using disjunctions, although that may not be a suitable issue for a GAN review.
    • I picked the / because if you were to code it using {{jct}} it would show as SR 224 / SR 225
  • Google map needs a accessdate.

The article is short, but I cannot see anything missing, so only the issues above need to be sorted out and it will pass. Arsenikk (talk) 23:33, 31 October 2010 (UTC)[reply]

Just a page stalker making a few quick comments. The conversion situation was discussed at length earlier this year, and the result was the table footer you see. There are many junction/exit lists where horizontal space is at a premium. The related provision from MOS:CONVERSIONS says:

When units are part of the subject of a topic—nautical miles in articles about the history of nautical law, SI units in scientific articles, yards in articles about American football—it can be excessive to provide conversions every time a unit occurs. It could be best to note that this topic will use the units (possibly giving the conversion factor to another familiar unit in a parenthetical note or a footnote), and link the first occurrence of each unit but not give a conversion every time it occurs.

As for the slashes, if you look at MOS:SLASH: "An unspaced slash may be used: ...where a slash occurs in a phrase widely used outside Wikipedia, and a different construction would be inaccurate, unfamiliar, or ambiguous." (The spaces are a technical issue related to how {{jct}} formats its output.) Having said that, both points are addressed by sections of the MOS that are not required by the Good Article criteria which only requires MOS:LEAD, MOS:LAYOUT, WP:W2W, MOS:FICT and WP:EMBED compliance. Imzadi 1979  02:29, 1 November 2010 (UTC)[reply]

Congratulations with a good article. Arsenikk (talk) 12:21, 1 November 2010 (UTC)[reply]