Template talk:Place Summary/Skyrim Other

The UESPWiki – Your source for The Elder Scrolls since 1995
Jump to: navigation, search

nbsp's[edit]

I don't know why all of the non-breaking spaces were added to this template in the first place, but their addition is definitely causing problems, such as this complaint. The nbsp's are forcing the first column of the Place Summary to be much much much too wide. So you get pages such as Skyrim:Arnleif_and_Sons_Trading_Company where first column is forced to take up 75% of the table width, meaning that the each word in the right hand column has to be on a separate line -- so the Gold entry ends up being six lines tall. In particular, this problem occurs at the page width used by iphones/ipads, and therefore the pages look ridiculous on those platforms.

Basically, these lines need to be able to wrap. So I've completely undone the nbsp's. --NepheleTalk 01:26, 18 May 2012 (UTC)

I added them because there is a problem with having the same width for the first column when the information used throughout the template varies. I don't think that particular complaint really warranted changing them (especially without a proposition for a better fix). Obviously, my fix wasn't the best, but it still is better than what we have now. It might be best to either make a table within the table, like we did with the Dragon Shouts, or make the # of list a bulleted list with a colspan=2 like the Buys section of the NPC Summary. Also, I don't think we should be worrying about formatting for iPhones or iPads; our templates won't work with everything like that. elliot (talk) 02:14, 18 May 2012 (UTC)
If something is causing problems when it wasn't before then it needs reverted, and a better solution sought first. You don't leave something in a bad way when it was better before. And it was taking up near a third of my screen (except for the sidebar) or I wouldn't have noticed, and how can we ignore such popular access points as the i-pad and i-pod (and I don't own either). It was making the whole summary table wider, not just fixing something within the summary table. The Silencer has spokenTalk 02:45, 18 May 2012 (UTC)
It was causing problems before, otherwise I wouldn't have fixed it. It got to the point where each of # of entries were two lines long, yet the content of each line was a single number. This is what I meant when I said the information throughout the template varies while they are bound by the same width. Another error is that the width is a percentage, rather than a fixed number. Now, consider Wikipedia's entry on how things should be formatted. 1024×768 is a good number to use (which happens to be the iPad's resolution in landscape). However, phones should not be taken into consideration when formatting templates. elliot (talk) 03:05, 18 May 2012 (UTC)
The problems I described originally were on the iPad in landscape mode. Not that landscape/portrait really matters on an iPad -- iPads and iPhones generate pages with a fixed horizontal resolution regardless of orientation or zoom level. And given that iPhones allow you to view the exact same version of the page as you see on the iPad, I don't see any reason to say that they're irrelevant when considering page layout. The basic point is that having nbsp's in the page ruins the page layout at your recommended 1024 page width.
In my opinion, having each of the "# of" entries being two lines long is not a significant problem, especially compared to forcing the "Gold" entry to be six lines long with one word of the entry on each line. In general, nbsp's should only be used as a last resort to alter formatting/layout because they remove the browser's flexibility in adjusting the page layout based on the reader's preferences. Other fixes/approaches should be considered first. --NepheleTalk 03:46, 18 May 2012 (UTC)
Which is why I proposed them above. elliot (talk) 04:48, 18 May 2012 (UTC)

Line wrapping again[edit]

The recent change to disallow line wrapping makes pages like Skyrim:Faldar's Tooth look really bad on smaller browser width. Why not let the browser decide which lines to break? It knows better than a side wide preference. --Alfwyn (talk) 18:24, 10 January 2013 (GMT)

At narrow browser widths, either the titles or things like the shadowmarks were breaking and it made for unnecessarily long, ugly-looking tables (often with two lines for every single title in the Special Features section. We may need to experiment some more, though...I think even as it is, Faldar's Tooth is an improvement over where it wanted to break automatically, but that's up for debate. I'll invite ABCface to comment as well, cuz I usually use full-screen at 1680 x 1050, so I don't run into these things all that often. Robin Hood  (talk) 22:22, 10 January 2013 (GMT)