Talk:SMS Erzherzog Karl

Latest comment: 5 years ago by Parsecboy in topic Image available
Good articleSMS Erzherzog Karl has been listed as one of the Warfare good articles under the good article criteria. If you can improve it further, please do so. If it no longer meets these criteria, you can reassess it.
Good topic starSMS Erzherzog Karl is part of the Battleships of Austria-Hungary series, a good topic. This is identified as among the best series of articles produced by the Wikipedia community. If you can update or improve it, please do so.
Article milestones
DateProcessResult
October 10, 2010Good article nomineeListed
December 6, 2010Good topic candidatePromoted
Did You Know
A fact from this article appeared on Wikipedia's Main Page in the "Did you know?" column on June 1, 2010.
The text of the entry was: Did you know ... that the three Erzherzog Karl class battleships, SMS Erzherzog Karl,Erzherzog Ferdinand Max and Erzherzog Friedrich helped quell a mutiny at Cattaro in 1918?
Current status: Good article

GA Review

edit
GA toolbox
Reviewing
This review is transcluded from Talk:SMS Erzherzog Karl/GA1. The edit link for this section can be used to add comments to the review.

Reviewer: JonCatalán(Talk) 22:36, 10 October 2010 (UTC)Reply

Comments:

  • Fairly standard, and follows the usual layout. So, in that, all good.
  • I inserted a few commas, and did some other light copyediting. Anything you may disagree with, feel free to revert.
  • The major thing, for future reference, are very slight spelling errors (for example, "hat" instead of "that"), which understandably occur when typing.
  • Images check out.
  • Referencing is good, but the second book in the bibliography needs a date and location (if it has one).

JonCatalán(Talk) 22:45, 10 October 2010 (UTC)Reply

Image available

edit

There's a nice illustration of the ship by Oscar Parkes available in this journal that can be uploaded to en.wiki (Parkes died in 1958, so they won't be PD in the UK until 2028). Parsecboy (talk) 19:19, 21 March 2019 (UTC)Reply