Talk:Heidelberg Castle
From Wikipedia, the free encyclopedia
[edit] Translation
I'm currently translating the German article on Heidelberg Castle Gnasher72 20:12, 3 December 2006 (UTC)
- Translation done, needs checking (Former Gnasher72 quit WP after 10 days). -Wikid77 20:10, 17 March 2007 (UTC)
[edit] Castle pre-fire
18-March-2007: There was no closeup of the later castle pre-fire, so I plan to extract an enlarged castle view from other images. -Wikid77 11:24, 18 March 2007 (UTC)
[edit] Advanced formatting
29-Dec-2007: The article "Heidelberg Castle" has extensive contents, as derived from the German Wikipedia, and has been changed for advanced formatting. Some advanced techniques include:
- staggering some images left/right: To allow auto-wrapping of text and images on high-resolution screens, some images need to be staggered with alignment to the left ("left|thumb") to avoid large text gaps when stacked images are taller than the parallel text alongside.
- hiding Table-of-Contents: When the show/hide button for the Table-of-Contents is triggered, the text and images must auto-wrap without squeezed text: join words with " " to avoid narrow, squeezed text wrapping as only 2-words-per-line.
- stacking similar-size images: Wiki auto-wrapping has trouble by eclipsing text when wider images are stacked below narrow images, so keep stacked images within 10px of same width to avoid overlay as eclipsed text.
- double-indenting poetry: Because lines of poetry are typically short, those lines need to be indented more, by using multiple lead colons ("::") prefixing each line.
- infobox readability: The width of an infobox restricts the size of images displayed, so image placement must be considered to avoid postage-stamp sized photo images, as Wikipedia is able to quickly display JPEG images over 250px wide.
- avoid ragged intro lines: Many articles have ragged margins on the first few lines, due to wrapping of long words in the article title or long pronunciation text: pad the intro text to typeset the intro lines for even margins (at 800x600), and confirm wider screens will wrap evenly.
- photos priority over maps: Photos generally are more accepted than maps, and should be displayed larger; local users don't need maps since they know the location, so maps should be kept small or avoided until later in the article. The top photo had been a tiny postage-stamp, so I enlarged the photo, lowering the map as a smaller image, lower in the infobox.
Those advanced-formatting techniques should be used when an article grows to include multiple images with extensive text. -Wikid77 (talk) 07:50, 29 December 2007 (UTC)