{"id":1472,"date":"2009-04-20T04:20:14","date_gmt":"2009-04-20T02:20:14","guid":{"rendered":"http:\/\/blog.ginchen.de\/?p=1472"},"modified":"2011-09-01T18:20:18","modified_gmt":"2011-09-01T16:20:18","slug":"datumsformatierung-mit-qtranslate","status":"publish","type":"post","link":"http:\/\/blog.ginchen.de\/en\/2009\/04\/20\/datumsformatierung-mit-qtranslate\/","title":{"rendered":"Date formatting with qTranslate"},"content":{"rendered":"

Almost a year ago I described here<\/a> how I had managed to set up two different date formats for German and English in my WordPress theme. That's why especially users of the plugin \"qTranslate<\/a>\" ended up here frequently, because I had found a - rather muddled, but working - solution to show each language in its own format, since the method recommended by the author didn't work for me then. Eleven months later however, the plugin has developed quite a bit and offers four options for date formatting.<\/p>\r\n\r\n\r\n\r\n

I will show you how I proceeded for this site. First I checked the box \"Use emulated date function\" in the advanced qTranslate settings. That means that you can now use the_date()<\/code> in your templates as usual, but qTranslate will automatically convert things like weekdays or month names to the current language. You do not<\/em> have to use the qTranslate function qtrans_formatPostDateTime()<\/code> as it used to be!<\/ins> This setting seems the most comfortable to me.<\/p>\r\n\r\n

A plain date display without additional text (like \"Sunday, 19th April 2009\u201d) could look like this:\r\n\r\n

the_date('l, jS F Y');<\/pre>\r\n\r\n
For this site, I wanted it to be displayed like \"19. Apr 2009\". That is done as follows:<\/p>\r\n\r\n
the_date('j. M Y');<\/pre>\r\n\r\n
After that, I added a line break between those three:<\/p>\r\n\r\n
the_date('j.MY');<\/pre>\r\n\r\n
The \"r\" must be protected by a backslash, because it is already reserved by the date()<\/code> function. You generally have to mind if the additional text in your date format contains letters that are being recognized by the function as formatting parameters. They all have to be escaped. Example:<\/p>\r\n\r\n
the_date('l, jS F Y \\a\\t g:i a');<\/pre>\r\n\r\n
In such a case you have to escape all the letters of the word \"at\", because otherwise they would be interpreted by the date()<\/code> function and produce a mess:<\/p>\r\n\r\n
Sunday, 2nd November 2008 am 30 7:04 am<\/pre>\r\n\r\n
Now, if you would like to have the words \"at\" and \"am\"\/\u201cpm\" in your English date, but \"um\" and \"Uhr\" in the German one, you can simply specify two different formats thanks to the (relatively) new qTranslate quicktags<\/a>:<\/p>\r\n\r\n
the_date('[:en]l, jS F Y \\a\\t g:i a[:de]l, j. F Y \\u\\m G:i \\U\\h\\r');<\/pre>\r\n\r\n
This example would output something like \"Sunday, 19th April 2009 at 4:18 am\" in English and \"Sonntag, 19. April 2009 um 4:18 Uhr\" in German.<\/p>\r\n\r\n
A list of all parameters of the date()<\/code> function can be found on php.net<\/a>.<\/p>\r\n\r\n\r\n
P.S.: Accordingly, the old qTranslate function qtrans_formatCommentDateTime()<\/code> isn't needed anymore either. You can use the standard WordPress function comment_date()<\/code> instead, e. g.:<\/p>\r\n\r\n
comment_date('[:de]j. F Y[:en]jS F, Y');<\/pre>\r\n<\/ins>","protected":false},"excerpt":{"rendered":"Almost a year ago I described here how I had managed to set up two different date formats for German and English in my WordPress theme. That's why especially users of the plugin \"qTranslate\" ended up here frequently, because I had found a - rather muddled, but working - solution to show each language in […]","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[77],"tags":[78,81,84,323,82,79,606],"_links":{"self":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/1472"}],"collection":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/comments?post=1472"}],"version-history":[{"count":5,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/1472\/revisions"}],"predecessor-version":[{"id":1495,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/1472\/revisions\/1495"}],"wp:attachment":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/media?parent=1472"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/categories?post=1472"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/tags?post=1472"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}