StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8142666
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-11-15T20:23:19.277
FavoriteCount
0
LastActivityDate
2011-11-15T20:31:31.027
LastEditDate
2011-11-15T20:31:31.027
LastEditorUserId
31100
OwnerUserId
31100
ParentId
8036168
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
Here's the workflow I used, on a very heavily-trafficked site that had about several dozen long-ish blocks of styled textual content, translated into six languages: <ol> <li>Pick a text-based markup language (we used <a href="http://en.wikipedia.org/wiki/Markdown" rel="noreferrer">Markdown</a>)</li> <li>For long strings, use fixed message IDs like "About_page_intro_markdown" that: <ul> <li>describes the intent of the text</li> <li>makes clear that it will be interpreted in markdown format</li> </ul></li> <li>Have our app render "*_markdown" strings appropriately, making sure to allow only a few safe HTML tags</li> <li>Build a tool for translators that: <ul> <li>shows them their Markdown rendered in realtime (sort of like the <a href="http://daringfireball.net/projects/markdown/dingus" rel="noreferrer">Markdown dingus</a>)</li> <li>makes it easy for them to see the now-authoritative base language translation of the text (since that's no longer in the <code>msgid</code>)</li> </ul></li> <li>Teach translators how to use the new workflow</li> </ol> Pros of this workflow: <ul> <li>Message IDs don't change all the time</li> <li>Because translators are editing in a safe higher-level syntax, hard to mess up HTML</li> <li>Non-technical translators found it very easy to write in Markdown, vs. HTML</li> </ul> Cons of this workflow: <ul> <li>Having static unchanging message IDs means changes in the text need to be transmitted out of band (which we'd do anyway, as long text can raise questions about tone or emphasis)</li> </ul> I'm very happy with the way this workflow operated for our website, and would absolutely recommend it, and use it again. It took a couple of days to get started, but it was easy to build, train, and launch. Hope this helps, and good luck with your project.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTranslating longer texts (view and email templates) with gettext
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAnirvan
UserOwnerUserId
1. USAnirvan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTranslating longer texts (view and email templates) with gettext
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
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.