Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 593

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 710

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/45/d96268876/htdocs/elmundo/wp-includes/wp-db.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-includes/cache.php on line 99

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/45/d96268876/htdocs/elmundo/wp-includes/cache.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-includes/theme.php on line 576

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/exec-php.php on line 22

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/manager.php on line 34

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/manager.php on line 35

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/manager.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 42

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 51

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 53

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/ajax.php on line 63

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/cache.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/cache.php on line 42

Warning: Cannot modify header information - headers already sent by (output started at /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php:576) in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/langswitch.php on line 662

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/wp-forum/bbcode.php on line 173

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/wp-forum/bbcode.php on line 962

Warning: Cannot modify header information - headers already sent by (output started at /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php:576) in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/wp-forum/cookie.php on line 21

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/45/d96268876/htdocs/elmundo/wp-includes/plugin.php on line 311
El Mundo Sports - Part 2

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33
20 June 2010

World Cup Preview 32: Spain

Posted by: christopher in Football (Soccer), World Cup

Comments (0)

Deemed the first battle of the World War II, the Spanish Civil War (1936-1939) was fought after the establishment of the Second Spanish Republic, which gave autonomy to Galicia, Catalonia, and the Basque Country. Military General Francisco Franco opposed the new rights and didn’t help Spain’s cause with his anti-democratic policies. Franco oppressed the three autonomous regions, demanding they not speak their own languages or fly their own flags. His tactics were malicious, as he would kill those who opposed him. Due to Franco’s presence, Spain was axed from the United Nations and politically isolated after World War II. It wasn’t until his death in 1975 that life began to improve in the country.

Like many nations, Spain’s internal struggle prohibited the national team from competing in FIFA tournaments until 1950. Coincidentally, the World Cup that year was the team’s best performance to date, as they finished fourth. Since that maiden voyage, the Spaniards have been a consistent qualifier, but La Furia Roja have not been able to live up to enormous expectations. The quarterfinals have been their stumbling block in three of the last six World Cups. After winning their first European Championship in 1964, it wasn’t until 2008 that the national team tasted success again, when they took home the European Championship trophy once again.

For this year’s World Cup, La Furia Roja has arguably the best midfield and striker combinations in the world. Before the tournament started, many pundits said the national team should easily top their group and were named one of few favorites to win the World Cup. Then the tournament started and something extremely unexpected happened. Switzerland played with a compact and organized defense, and Spain couldn’t break it down, losing to the Swiss 1-0. Spain controlled possession as was expected with Xavi Hernandez, Andres Iniesta, and Xabi Alonso running the show, but their offense couldn’t find a way to score against the organized Swiss defense.

So, what does that mean for Spain? Are they not as good as everyone thinks? Should the Iberian Peninsula be worried that the national team is falling short of expectations again? I don’t think so. The midfield constantly proves they can control a game, but David Villa and Fernando Torres didn’t do much in attack. All in all, the Swiss played the game of their lives and lived for the counter attack. Spain’s next opponent, Honduras, will probably be defensive minded too, which won’t make La Furia Roja’s lives any easier. The South American’s probably aren’t as strong as the Swiss and definitely not as organized, so Spain should have some more space to work their magic. The midfield has to feed Villa and Torres better. One key will be getting Xabi Alonso more involved in the attack as he is great at spraying the ball all over the park. Also, David Silva will need to work better with Xavi Hernandez and both need to feed the ball to the forwards to produce goals.

I never thought I would write this, but if Xavi, Iniesta, and Silva can’t create that magic, Spain may be out of the World Cup after the 1st round.

Player to Watch: Xavi Hernandez

Game to Watch: 3rd game against Chile

Predicted World Cup result: Champions

Share/Save

Comments (0)

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33
17 June 2010

World Cup Kit 31: Switzerland

Posted by: christopher in Football (Soccer), World Cup

Comments (0)

Switzerland World Cup Jersey

Switzerland’s jerseys are a bit of a disappointment, not because I expect better for the Swiss, but because Puma has been so creative with the rest of its kits. I mean, the company designed jerseys with watermark symbols representing national flags, animal portraits imprinted on African tops, and some of the more colorful away kits I have ever seen. All they could give the Swiss was this?

I have great ideas for Switzerland’s jersey actually. How about holes all over the jersey representing Swiss cheese? Or what about pictures of pieces of chocolate, melting in someone’s mouth, not there hand? Ok, well maybe not, but Puma should have taken more than 10 minutes between important meetings a few months ago to design this top. The Swiss deserved better than a symbol of a guy kicking at a ball at the Puma symbol across the chest. It’s kind of silly. It’s probably all for not as I don’t see Switzerland progressing anyway.

Share/Save

Comments (0)
« Older Entries
Newer Entries »