StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16554596
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-05-14T23:51:14.393
FavoriteCount
0
LastActivityDate
2013-05-15T13:38:19.040
LastEditDate
2013-05-15T13:38:19.040
LastEditorUserId
2364547
OwnerUserId
2364547
ParentId
16553695
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You could fix the widths of the menu items, and then having the text wrap to extra lines within each link. So the nav bar remains one line, but the buttons get deeper. Two possible drawbacks and their solution: Problem: Depending on your CSS, really long words will either break out of the fixed width, or will be forced to wrap in mid-word. Solution: Accept the mid-word break, or have your translator use different, shorter words. It's possible to do that in just about any language, as long as you're not hellbent on using the exact same wording in both languages. Problem: One-line nav links don't automatically adjust to the depth of two-line buttons, so your nav could look uneven if your links have borders or otherwise show their individual height. Solution: Multiple. <ul> <li>Make all the links a fixed height that can accomodate two lines, and either vertically center the type (you can use "display:table-cell;" to do this) or let it stay top-aligned.</li> <li>Use jQuery to measure the tallest link (or the height of the containing div) and make all the links the same height.</li> </ul> When building multilingual sites, I usually try to avoid the problem through design -- by leaving plenty of empty space in the nav bar for words to grow, and by having the translator use shorter words. Edit: To get the URL in PHP, use $_SERVER['REQUEST_URI'] <pre><code><?php $url = $_SERVER['REQUEST_URI']; if(strpos($url,'/es/')) { ?> <style type="text/css"> .menu a { letter-spacing: 0; } </style> <?php } ?> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONavigation bar extends to second row when translated
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSteve Ray
UserOwnerUserId
1. USSteve Ray
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThis looks like a perfect solution! Could you add this CSS to the above? I tried it myself but nothing changed. .menu a { letter-spacing: 0; }
 singulars
 PostPostId
 PO
 UserUserId
 USCullen Webb
2. COUpdated the answer to add your CSS.
 singulars
 PostPostId
 PO
 UserUserId
 USSteve Ray

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.