StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12334387
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-08T20:51:24.040
FavoriteCount
0
LastActivityDate
2016-03-24T15:50:28.563
LastEditDate
2016-03-24T15:50:28.563
LastEditorUserId
479863
OwnerUserId
479863
ParentId
12334183
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
No, there isn't a cleaner way of dealing with this. If you want pull the <code>url</code> out of the string then you're stuck breaking the sentence into four pieces: <ol> <li><code>"Go</code>.</li> <li><code><a href="{{url}}">...</a></code></li> <li><code>'here'</code></li> <li><code>'for expert security advice.'</code></li> </ol> These four pieces are easy to put back together in English but the order might change in other languages and that can change the capitalization of here and cause other problems. To get it right, you'd have to structure things like this: <pre><code>here = "<a href=\"#{url}\">#{t(:expert_security_advice_here)}</a>" whole_thing = t(:expert_security_advice, :here => here) </code></pre> and the two separate strings in your YAML: <pre><code>expert_security_advice_here: "here" expert_security_advice: "Go {{here}} for expert security advice." </code></pre> You'd also have to tell the translators that those two pieces of text go together. If that sort of thing seems cleaner to you then go for it but I wouldn't worry about small bits of HTML in text that needs to be translated, any translator worth talking to will be able to handle it. Never try to take shortcuts with I18N/L10N issues, they will always lead you astray and cause problems: non-DRY code (WET code?) is always better than broken code. <hr> As an aside, I'd recommend that you drop the standard Rails I18N string handling tools in favor of <a href="https://github.com/grosser/gettext_i18n_rails" rel="nofollow">gettext</a>, keeping everything synchronized with gettext is much easier and the code ends up being much easier to read.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails I18n: Better way of interpolating links?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmu is too short
UserOwnerUserId
1. USmu is too short
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.