StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1172599
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-23T15:28:49.483
FavoriteCount
0
LastActivityDate
2009-07-23T15:28:49.483
LastEditDate
LastEditorUserId
0
OwnerUserId
137115
ParentId
1084191
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
There is no argument for setting the output character encoding directly, but this should in pratice not be a problem, as your PO editor will automatically use an appropriate character encoding when saving the PO file (one that supports all the characters used in the translation), and replace <code>CHARSET</code> in the file with the name of the encoding. If it doesn’t, file a bug. The only problem would be if the POT file contained non-ASCII characters, but <code>xgettext</code> does have a <code>--from-code</code> argument for this, which specifies the encoding of the input files. If the input contains non-ASCII characters and <code>--from-code</code> is set to the correct encoding, the output POT file will have the character encoding set to UTF-8 (this need not be equal to the input character encoding). However, if the input files only contain ASCII characters, <code>--from-code=UTF-8</code> will unfortunately have no effect. <code>msginit</code> does in fact automatically set the character encoding to something ‘appropriate’ for the chosen target locale. However, the list of locale to character encoding pairs seems outdated; UTF-8 is now really the best choice for all languages. An alternative would be to use <a href="http://translate.sourceforge.net/wiki/toolkit/pot2po" rel="noreferrer"><code>pot2po</code></a> instead of <code>msginit</code>. This always uses UTF-8 automatically, AFAICS. However, unlike <code>msginit</code>, it does not automatically fill out the plural forms of the PO file, which may or may not be a problem (some think it is the job of the PO editor to do this).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCommand or option for the xgettext, msginit, msgfmt sequence for setting the MIME type?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKarl Ove Hufthammer
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
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
 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.