-- Softaculous SQL Dump
-- http://www.softaculous.com
--




--
-- Database: `monster_1`
--

-- --------------------------------------------------------

--
-- Table structure for table`wp_commentmeta`
--

CREATE TABLE `wp_commentmeta` (
  `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `comment_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext,
  PRIMARY KEY (`meta_id`),
  KEY `comment_id` (`comment_id`),
  KEY `meta_key` (`meta_key`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_comments`
--

CREATE TABLE `wp_comments` (
  `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0',
  `comment_author` tinytext NOT NULL,
  `comment_author_email` varchar(100) NOT NULL DEFAULT '',
  `comment_author_url` varchar(200) NOT NULL DEFAULT '',
  `comment_author_IP` varchar(100) NOT NULL DEFAULT '',
  `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_content` text NOT NULL,
  `comment_karma` int(11) NOT NULL DEFAULT '0',
  `comment_approved` varchar(20) NOT NULL DEFAULT '1',
  `comment_agent` varchar(255) NOT NULL DEFAULT '',
  `comment_type` varchar(20) NOT NULL DEFAULT '',
  `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0',
  `user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`comment_ID`),
  KEY `comment_post_ID` (`comment_post_ID`),
  KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
  KEY `comment_date_gmt` (`comment_date_gmt`),
  KEY `comment_parent` (`comment_parent`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 AUTO_INCREMENT=2 ;

--
-- Dumping data for table 'wp_comments'
--

INSERT INTO `wp_comments` VALUES
(1, 1, 'Mr WordPress', '', 'http://wordpress.org/', '', '2014-01-27 14:57:12', '2014-01-27 14:57:12', 'Hi, this is a comment.\nTo delete a comment, just log in and view the post&#039;s comments. There you will have the option to edit or delete them.', 0, '1', '', '', 0, 0);

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_content_status`
--

CREATE TABLE `wp_icl_content_status` (
  `rid` bigint(20) NOT NULL,
  `nid` bigint(20) NOT NULL,
  `timestamp` datetime NOT NULL,
  `md5` varchar(32) NOT NULL,
  PRIMARY KEY (`rid`),
  KEY `nid` (`nid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_core_status`
--

CREATE TABLE `wp_icl_core_status` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) NOT NULL,
  `module` varchar(16) NOT NULL,
  `origin` varchar(64) NOT NULL,
  `target` varchar(64) NOT NULL,
  `status` smallint(6) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `rid` (`rid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_flags`
--

CREATE TABLE `wp_icl_flags` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `lang_code` varchar(10) NOT NULL,
  `flag` varchar(32) NOT NULL,
  `from_template` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `lang_code` (`lang_code`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=65 ;

--
-- Dumping data for table 'wp_icl_flags'
--

INSERT INTO `wp_icl_flags` VALUES
(1, 'ar', 'ar.png', 0),
(2, 'bg', 'bg.png', 0),
(3, 'bs', 'bs.png', 0),
(4, 'ca', 'ca.png', 0),
(5, 'cs', 'cs.png', 0),
(6, 'cy', 'cy.png', 0),
(7, 'da', 'da.png', 0),
(8, 'de', 'de.png', 0),
(9, 'el', 'el.png', 0),
(10, 'en', 'en.png', 0),
(11, 'eo', 'eo.png', 0),
(12, 'es', 'es.png', 0),
(13, 'et', 'et.png', 0),
(14, 'eu', 'eu.png', 0),
(15, 'fa', 'fa.png', 0),
(16, 'fi', 'fi.png', 0),
(17, 'fr', 'fr.png', 0),
(18, 'ga', 'ga.png', 0),
(19, 'he', 'he.png', 0),
(20, 'hi', 'hi.png', 0),
(21, 'hr', 'hr.png', 0),
(22, 'hu', 'hu.png', 0),
(23, 'hy', 'hy.png', 0),
(24, 'id', 'id.png', 0),
(25, 'is', 'is.png', 0),
(26, 'it', 'it.png', 0),
(27, 'ja', 'ja.png', 0),
(28, 'ko', 'ko.png', 0),
(29, 'ku', 'ku.png', 0),
(30, 'la', 'la.png', 0),
(31, 'lt', 'lt.png', 0),
(32, 'lv', 'lv.png', 0),
(33, 'mk', 'mk.png', 0),
(34, 'mn', 'mn.png', 0),
(35, 'mo', 'mo.png', 0),
(36, 'ms', 'ms.png', 0),
(37, 'mt', 'mt.png', 0),
(38, 'nb', 'nb.png', 0),
(39, 'ne', 'ne.png', 0),
(40, 'nl', 'nl.png', 0),
(41, 'pa', 'pa.png', 0),
(42, 'pl', 'pl.png', 0),
(43, 'pt-br', 'pt-br.png', 0),
(44, 'pt-pt', 'pt-pt.png', 0),
(45, 'qu', 'qu.png', 0),
(46, 'ro', 'ro.png', 0),
(47, 'ru', 'ru.png', 0),
(48, 'sk', 'sk.png', 0),
(49, 'sl', 'sl.png', 0),
(50, 'so', 'so.png', 0),
(51, 'sq', 'sq.png', 0),
(52, 'sr', 'sr.png', 0),
(53, 'sv', 'sv.png', 0),
(54, 'ta', 'ta.png', 0),
(55, 'th', 'th.png', 0),
(56, 'tr', 'tr.png', 0),
(57, 'uk', 'uk.png', 0),
(58, 'ur', 'ur.png', 0),
(59, 'uz', 'uz.png', 0),
(60, 'vi', 'vi.png', 0),
(61, 'yi', 'yi.png', 0),
(62, 'zh-hans', 'zh-hans.png', 0),
(63, 'zh-hant', 'zh-hant.png', 0),
(64, 'zu', 'zu.png', 0);

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_languages`
--

CREATE TABLE `wp_icl_languages` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `code` varchar(7) NOT NULL,
  `english_name` varchar(128) NOT NULL,
  `major` tinyint(4) NOT NULL DEFAULT '0',
  `active` tinyint(4) NOT NULL,
  `default_locale` varchar(8) DEFAULT NULL,
  `tag` varchar(8) DEFAULT NULL,
  `encode_url` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `code` (`code`),
  UNIQUE KEY `english_name` (`english_name`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=65 ;

--
-- Dumping data for table 'wp_icl_languages'
--

INSERT INTO `wp_icl_languages` VALUES
(1, 'en', 'English', 1, 1, 'en_US', 'en-US', 0),
(2, 'es', 'Spanish', 1, 0, 'es_ES', 'es-ES', 0),
(3, 'de', 'German', 1, 0, 'de_DE', 'de-DE', 0),
(4, 'fr', 'French', 1, 1, 'fr_FR', 'fr-FR', 0),
(5, 'ar', 'Arabic', 0, 0, 'ar', 'ar', 0),
(6, 'bs', 'Bosnian', 0, 0, '', '', 0),
(7, 'bg', 'Bulgarian', 0, 0, 'bg_BG', 'bg-BG', 0),
(8, 'ca', 'Catalan', 0, 0, 'ca', 'ca', 0),
(9, 'cs', 'Czech', 0, 0, 'cs_CZ', 'cs-CZ', 0),
(10, 'sk', 'Slovak', 0, 0, 'sk_SK', 'sk-SK', 0),
(11, 'cy', 'Welsh', 0, 0, 'cy', 'cy', 0),
(12, 'da', 'Danish', 1, 0, 'da_DK', 'da-DK', 0),
(13, 'el', 'Greek', 0, 0, 'el', 'el', 0),
(14, 'eo', 'Esperanto', 0, 0, 'eo', 'eo', 0),
(15, 'et', 'Estonian', 0, 0, 'et', 'et', 0),
(16, 'eu', 'Basque', 0, 0, 'eu', 'eu', 0),
(17, 'fa', 'Persian', 0, 0, 'fa_IR', 'fa-IR', 0),
(18, 'fi', 'Finnish', 0, 0, 'fi', 'fi', 0),
(19, 'ga', 'Irish', 0, 0, '', '', 0),
(20, 'he', 'Hebrew', 0, 0, 'he_IL', 'he-IL', 0),
(21, 'hi', 'Hindi', 0, 0, '', '', 0),
(22, 'hr', 'Croatian', 0, 0, 'hr', 'hr', 0),
(23, 'hu', 'Hungarian', 0, 0, 'hu_HU', 'hu-HU', 0),
(24, 'hy', 'Armenian', 0, 0, '', '', 0),
(25, 'id', 'Indonesian', 0, 0, 'id_ID', 'id-ID', 0),
(26, 'is', 'Icelandic', 0, 0, 'is_IS', 'is-IS', 0),
(27, 'it', 'Italian', 1, 1, 'it_IT', 'it-IT', 0),
(28, 'ja', 'Japanese', 1, 0, 'ja', 'ja', 0),
(29, 'ko', 'Korean', 0, 0, 'ko_KR', 'ko-KR', 0),
(30, 'ku', 'Kurdish', 0, 0, 'ku', 'ku', 0),
(31, 'la', 'Latin', 0, 0, '', '', 0),
(32, 'lv', 'Latvian', 0, 0, 'lv', 'lv', 0),
(33, 'lt', 'Lithuanian', 0, 0, 'lt', 'lt', 0),
(34, 'mk', 'Macedonian', 0, 0, 'mk_MK', 'mk-MK', 0),
(35, 'mt', 'Maltese', 0, 0, '', '', 0),
(36, 'mo', 'Moldavian', 0, 0, '', '', 0),
(37, 'mn', 'Mongolian', 0, 0, '', '', 0),
(38, 'ne', 'Nepali', 0, 0, '', '', 0),
(39, 'nl', 'Dutch', 1, 0, 'nl_NL', 'nl-NL', 0),
(40, 'nb', 'Norwegian Bokmål', 0, 0, 'nb_NO', 'nb-NO', 0),
(41, 'pa', 'Punjabi', 0, 0, '', '', 0),
(42, 'pl', 'Polish', 0, 0, 'pl_PL', 'pl-PL', 0),
(43, 'pt-pt', 'Portuguese, Portugal', 0, 0, 'pt_PT', 'pt-PT', 0),
(44, 'pt-br', 'Portuguese, Brazil', 0, 0, 'pt_BR', 'pt-BR', 0),
(45, 'qu', 'Quechua', 0, 0, '', '', 0),
(46, 'ro', 'Romanian', 0, 0, 'ro_RO', 'ro-RO', 0),
(47, 'ru', 'Russian', 1, 1, 'ru_RU', 'ru-RU', 0),
(48, 'sl', 'Slovenian', 0, 0, 'sl_SI', 'sl-SI', 0),
(49, 'so', 'Somali', 0, 0, '', '', 0),
(50, 'sq', 'Albanian', 0, 0, '', '', 0),
(51, 'sr', 'Serbian', 0, 0, 'sr_RS', 'sr-RS', 0),
(52, 'sv', 'Swedish', 0, 0, 'sv_SE', 'sv-SE', 0),
(53, 'ta', 'Tamil', 0, 0, '', '', 0),
(54, 'th', 'Thai', 0, 0, 'th', 'th', 0),
(55, 'tr', 'Turkish', 0, 0, 'tr', 'tr', 0),
(56, 'uk', 'Ukrainian', 0, 0, 'uk_UA', 'uk-UA', 0),
(57, 'ur', 'Urdu', 0, 0, '', '', 0),
(58, 'uz', 'Uzbek', 0, 0, 'uz_UZ', 'uz-UZ', 0),
(59, 'vi', 'Vietnamese', 0, 0, 'vi', 'vi', 0),
(60, 'yi', 'Yiddish', 0, 0, '', '', 0),
(61, 'zh-hans', 'Chinese (Simplified)', 1, 0, 'zh_CN', 'zh-CN', 0),
(62, 'zu', 'Zulu', 0, 0, '', '', 0),
(63, 'zh-hant', 'Chinese (Traditional)', 1, 0, 'zh_TW', 'zh-TW', 0),
(64, 'ms', 'Malay', 0, 0, 'ms_MY', 'ms-MY', 0);

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_languages_translations`
--

CREATE TABLE `wp_icl_languages_translations` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `language_code` varchar(7) NOT NULL,
  `display_language_code` varchar(7) NOT NULL,
  `name` varchar(255) NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `language_code` (`language_code`,`display_language_code`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=4097 ;

--
-- Dumping data for table 'wp_icl_languages_translations'
--

INSERT INTO `wp_icl_languages_translations` VALUES
(1, 'en', 'en', 'English'),
(2, 'en', 'es', 'Inglés'),
(3, 'en', 'de', 'Englisch'),
(4, 'en', 'fr', 'Anglais'),
(5, 'en', 'ar', 'الإنجليزية'),
(6, 'en', 'bs', 'English'),
(7, 'en', 'bg', 'English'),
(8, 'en', 'ca', 'English'),
(9, 'en', 'cs', 'English'),
(10, 'en', 'sk', 'Angličtina'),
(11, 'en', 'cy', 'English'),
(12, 'en', 'da', 'English'),
(13, 'en', 'el', 'Αγγλικα'),
(14, 'en', 'eo', 'English'),
(15, 'en', 'et', 'English'),
(16, 'en', 'eu', 'English'),
(17, 'en', 'fa', 'English'),
(18, 'en', 'fi', 'englanti'),
(19, 'en', 'ga', 'English'),
(20, 'en', 'he', 'אנגלית'),
(21, 'en', 'hi', 'English'),
(22, 'en', 'hr', 'English'),
(23, 'en', 'hu', 'angol'),
(24, 'en', 'hy', 'English'),
(25, 'en', 'id', 'English'),
(26, 'en', 'is', 'English'),
(27, 'en', 'it', 'Inglese'),
(28, 'en', 'ja', '英語'),
(29, 'en', 'ko', '영어'),
(30, 'en', 'ku', 'English'),
(31, 'en', 'la', 'English'),
(32, 'en', 'lv', 'English'),
(33, 'en', 'lt', 'English'),
(34, 'en', 'mk', 'English'),
(35, 'en', 'mt', 'English'),
(36, 'en', 'mo', 'English'),
(37, 'en', 'mn', 'English'),
(38, 'en', 'ne', 'English'),
(39, 'en', 'nl', 'Engels'),
(40, 'en', 'nb', 'English'),
(41, 'en', 'pa', 'English'),
(42, 'en', 'pl', 'angielski'),
(43, 'en', 'pt-pt', 'Inglês'),
(44, 'en', 'pt-br', 'Inglês'),
(45, 'en', 'qu', 'English'),
(46, 'en', 'ro', 'Engleză'),
(47, 'en', 'ru', 'Английский'),
(48, 'en', 'sl', 'English'),
(49, 'en', 'so', 'English'),
(50, 'en', 'sq', 'English'),
(51, 'en', 'sr', 'English'),
(52, 'en', 'sv', 'Engelska'),
(53, 'en', 'ta', 'English'),
(54, 'en', 'th', 'อังกฤษ'),
(55, 'en', 'tr', 'İngilizce'),
(56, 'en', 'uk', 'English'),
(57, 'en', 'ur', 'English'),
(58, 'en', 'uz', 'English'),
(59, 'en', 'vi', 'English'),
(60, 'en', 'yi', 'English'),
(61, 'en', 'zh-hans', '英语'),
(62, 'en', 'zu', 'English'),
(63, 'en', 'zh-hant', '英語'),
(64, 'en', 'ms', 'English'),
(65, 'es', 'en', 'Spanish'),
(66, 'es', 'es', 'Español'),
(67, 'es', 'de', 'Spanisch'),
(68, 'es', 'fr', 'Espagnol'),
(69, 'es', 'ar', 'الأسبانية'),
(70, 'es', 'bs', 'Spanish'),
(71, 'es', 'bg', 'Spanish'),
(72, 'es', 'ca', 'Spanish'),
(73, 'es', 'cs', 'Spanish'),
(74, 'es', 'sk', 'Španielčina'),
(75, 'es', 'cy', 'Spanish'),
(76, 'es', 'da', 'Spanish'),
(77, 'es', 'el', 'Ισπανικα'),
(78, 'es', 'eo', 'Spanish'),
(79, 'es', 'et', 'Spanish'),
(80, 'es', 'eu', 'Spanish'),
(81, 'es', 'fa', 'Spanish'),
(82, 'es', 'fi', 'espanja'),
(83, 'es', 'ga', 'Spanish'),
(84, 'es', 'he', 'ספרדית'),
(85, 'es', 'hi', 'Spanish'),
(86, 'es', 'hr', 'Spanish'),
(87, 'es', 'hu', 'spanyol'),
(88, 'es', 'hy', 'Spanish'),
(89, 'es', 'id', 'Spanish'),
(90, 'es', 'is', 'Spanish'),
(91, 'es', 'it', 'Spagnolo'),
(92, 'es', 'ja', 'スペイン語'),
(93, 'es', 'ko', '스페인어'),
(94, 'es', 'ku', 'Spanish'),
(95, 'es', 'la', 'Spanish'),
(96, 'es', 'lv', 'Spanish'),
(97, 'es', 'lt', 'Spanish'),
(98, 'es', 'mk', 'Spanish'),
(99, 'es', 'mt', 'Spanish'),
(100, 'es', 'mo', 'Spanish'),
(101, 'es', 'mn', 'Spanish'),
(102, 'es', 'ne', 'Spanish'),
(103, 'es', 'nl', 'Spaans'),
(104, 'es', 'nb', 'Spanish'),
(105, 'es', 'pa', 'Spanish'),
(106, 'es', 'pl', 'hiszpański'),
(107, 'es', 'pt-pt', 'Espanhol'),
(108, 'es', 'pt-br', 'Espanhol'),
(109, 'es', 'qu', 'Spanish'),
(110, 'es', 'ro', 'Spaniolă'),
(111, 'es', 'ru', 'Испанский'),
(112, 'es', 'sl', 'Spanish'),
(113, 'es', 'so', 'Spanish'),
(114, 'es', 'sq', 'Spanish'),
(115, 'es', 'sr', 'Spanish'),
(116, 'es', 'sv', 'Spanska'),
(117, 'es', 'ta', 'Spanish'),
(118, 'es', 'th', 'สเปน'),
(119, 'es', 'tr', 'İspanyolca'),
(120, 'es', 'uk', 'Spanish'),
(121, 'es', 'ur', 'Spanish'),
(122, 'es', 'uz', 'Spanish'),
(123, 'es', 'vi', 'Spanish'),
(124, 'es', 'yi', 'Spanish'),
(125, 'es', 'zh-hans', '西班牙语'),
(126, 'es', 'zu', 'Spanish'),
(127, 'es', 'zh-hant', '西班牙語'),
(128, 'es', 'ms', 'Spanish'),
(129, 'de', 'en', 'German'),
(130, 'de', 'es', 'Alemán'),
(131, 'de', 'de', 'Deutsch'),
(132, 'de', 'fr', 'Allemand'),
(133, 'de', 'ar', 'الألمانية'),
(134, 'de', 'bs', 'German'),
(135, 'de', 'bg', 'German'),
(136, 'de', 'ca', 'German'),
(137, 'de', 'cs', 'German'),
(138, 'de', 'sk', 'Nemčina'),
(139, 'de', 'cy', 'German'),
(140, 'de', 'da', 'German'),
(141, 'de', 'el', 'Γερμανικα'),
(142, 'de', 'eo', 'German'),
(143, 'de', 'et', 'German'),
(144, 'de', 'eu', 'German'),
(145, 'de', 'fa', 'German'),
(146, 'de', 'fi', 'saksa'),
(147, 'de', 'ga', 'German'),
(148, 'de', 'he', 'גרמנית'),
(149, 'de', 'hi', 'German'),
(150, 'de', 'hr', 'German'),
(151, 'de', 'hu', 'német'),
(152, 'de', 'hy', 'German'),
(153, 'de', 'id', 'German'),
(154, 'de', 'is', 'German'),
(155, 'de', 'it', 'Tedesco'),
(156, 'de', 'ja', 'ドイツ語'),
(157, 'de', 'ko', '독어'),
(158, 'de', 'ku', 'German'),
(159, 'de', 'la', 'German'),
(160, 'de', 'lv', 'German'),
(161, 'de', 'lt', 'German'),
(162, 'de', 'mk', 'German'),
(163, 'de', 'mt', 'German'),
(164, 'de', 'mo', 'German'),
(165, 'de', 'mn', 'German'),
(166, 'de', 'ne', 'German'),
(167, 'de', 'nl', 'Duits'),
(168, 'de', 'nb', 'German'),
(169, 'de', 'pa', 'German'),
(170, 'de', 'pl', 'niemiecki'),
(171, 'de', 'pt-pt', 'Alemão'),
(172, 'de', 'pt-br', 'Alemão'),
(173, 'de', 'qu', 'German'),
(174, 'de', 'ro', 'Germană'),
(175, 'de', 'ru', 'Немецкий'),
(176, 'de', 'sl', 'German'),
(177, 'de', 'so', 'German'),
(178, 'de', 'sq', 'German'),
(179, 'de', 'sr', 'German'),
(180, 'de', 'sv', 'Tyska'),
(181, 'de', 'ta', 'German'),
(182, 'de', 'th', 'เยอรมัน'),
(183, 'de', 'tr', 'Almanca'),
(184, 'de', 'uk', 'German'),
(185, 'de', 'ur', 'German'),
(186, 'de', 'uz', 'German'),
(187, 'de', 'vi', 'German'),
(188, 'de', 'yi', 'German'),
(189, 'de', 'zh-hans', '德语'),
(190, 'de', 'zu', 'German'),
(191, 'de', 'zh-hant', '德語'),
(192, 'de', 'ms', 'German'),
(193, 'fr', 'en', 'French'),
(194, 'fr', 'es', 'Francés'),
(195, 'fr', 'de', 'Französisch'),
(196, 'fr', 'fr', 'Français'),
(197, 'fr', 'ar', 'الفرنسية'),
(198, 'fr', 'bs', 'French'),
(199, 'fr', 'bg', 'French'),
(200, 'fr', 'ca', 'French'),
(201, 'fr', 'cs', 'French'),
(202, 'fr', 'sk', 'Francúzština'),
(203, 'fr', 'cy', 'French'),
(204, 'fr', 'da', 'French'),
(205, 'fr', 'el', 'Γαλλικα'),
(206, 'fr', 'eo', 'French'),
(207, 'fr', 'et', 'French'),
(208, 'fr', 'eu', 'French'),
(209, 'fr', 'fa', 'French'),
(210, 'fr', 'fi', 'ranska'),
(211, 'fr', 'ga', 'French'),
(212, 'fr', 'he', 'צרפתית'),
(213, 'fr', 'hi', 'French'),
(214, 'fr', 'hr', 'French'),
(215, 'fr', 'hu', 'francia'),
(216, 'fr', 'hy', 'French'),
(217, 'fr', 'id', 'French'),
(218, 'fr', 'is', 'French'),
(219, 'fr', 'it', 'Francese'),
(220, 'fr', 'ja', 'フランス語'),
(221, 'fr', 'ko', '불어'),
(222, 'fr', 'ku', 'French'),
(223, 'fr', 'la', 'French'),
(224, 'fr', 'lv', 'French'),
(225, 'fr', 'lt', 'French'),
(226, 'fr', 'mk', 'French'),
(227, 'fr', 'mt', 'French'),
(228, 'fr', 'mo', 'French'),
(229, 'fr', 'mn', 'French'),
(230, 'fr', 'ne', 'French'),
(231, 'fr', 'nl', 'Frans'),
(232, 'fr', 'nb', 'French'),
(233, 'fr', 'pa', 'French'),
(234, 'fr', 'pl', 'francuski'),
(235, 'fr', 'pt-pt', 'Francês'),
(236, 'fr', 'pt-br', 'Francês'),
(237, 'fr', 'qu', 'French'),
(238, 'fr', 'ro', 'Franceză'),
(239, 'fr', 'ru', 'Французский'),
(240, 'fr', 'sl', 'French'),
(241, 'fr', 'so', 'French'),
(242, 'fr', 'sq', 'French'),
(243, 'fr', 'sr', 'French'),
(244, 'fr', 'sv', 'Franska'),
(245, 'fr', 'ta', 'French'),
(246, 'fr', 'th', 'ฝรั่งเศส'),
(247, 'fr', 'tr', 'Fransızca'),
(248, 'fr', 'uk', 'French'),
(249, 'fr', 'ur', 'French'),
(250, 'fr', 'uz', 'French'),
(251, 'fr', 'vi', 'French'),
(252, 'fr', 'yi', 'French'),
(253, 'fr', 'zh-hans', '法语'),
(254, 'fr', 'zu', 'French'),
(255, 'fr', 'zh-hant', '法語'),
(256, 'fr', 'ms', 'French'),
(257, 'ar', 'en', 'Arabic'),
(258, 'ar', 'es', 'Árabe'),
(259, 'ar', 'de', 'Arabisch'),
(260, 'ar', 'fr', 'Arabe'),
(261, 'ar', 'ar', 'العربية'),
(262, 'ar', 'bs', 'Arabic'),
(263, 'ar', 'bg', 'Arabic'),
(264, 'ar', 'ca', 'Arabic'),
(265, 'ar', 'cs', 'Arabic'),
(266, 'ar', 'sk', 'Arabčina'),
(267, 'ar', 'cy', 'Arabic'),
(268, 'ar', 'da', 'Arabic'),
(269, 'ar', 'el', 'Αραβικα'),
(270, 'ar', 'eo', 'Arabic'),
(271, 'ar', 'et', 'Arabic'),
(272, 'ar', 'eu', 'Arabic'),
(273, 'ar', 'fa', 'Arabic'),
(274, 'ar', 'fi', 'arabia'),
(275, 'ar', 'ga', 'Arabic'),
(276, 'ar', 'he', 'ערבית'),
(277, 'ar', 'hi', 'Arabic'),
(278, 'ar', 'hr', 'Arabic'),
(279, 'ar', 'hu', 'arab'),
(280, 'ar', 'hy', 'Arabic'),
(281, 'ar', 'id', 'Arabic'),
(282, 'ar', 'is', 'Arabic'),
(283, 'ar', 'it', 'Arabo'),
(284, 'ar', 'ja', 'アラビア語'),
(285, 'ar', 'ko', '아랍어'),
(286, 'ar', 'ku', 'Arabic'),
(287, 'ar', 'la', 'Arabic'),
(288, 'ar', 'lv', 'Arabic'),
(289, 'ar', 'lt', 'Arabic'),
(290, 'ar', 'mk', 'Arabic'),
(291, 'ar', 'mt', 'Arabic'),
(292, 'ar', 'mo', 'Arabic'),
(293, 'ar', 'mn', 'Arabic'),
(294, 'ar', 'ne', 'Arabic'),
(295, 'ar', 'nl', 'Arabisch'),
(296, 'ar', 'nb', 'Arabic'),
(297, 'ar', 'pa', 'Arabic'),
(298, 'ar', 'pl', 'arabski'),
(299, 'ar', 'pt-pt', 'Árabe'),
(300, 'ar', 'pt-br', 'Árabe'),
(301, 'ar', 'qu', 'Arabic'),
(302, 'ar', 'ro', 'Arabică'),
(303, 'ar', 'ru', 'Арабский'),
(304, 'ar', 'sl', 'Arabic'),
(305, 'ar', 'so', 'Arabic'),
(306, 'ar', 'sq', 'Arabic'),
(307, 'ar', 'sr', 'Arabic'),
(308, 'ar', 'sv', 'Arabiska'),
(309, 'ar', 'ta', 'Arabic'),
(310, 'ar', 'th', 'อารบิก'),
(311, 'ar', 'tr', 'Arapça'),
(312, 'ar', 'uk', 'Arabic'),
(313, 'ar', 'ur', 'Arabic'),
(314, 'ar', 'uz', 'Arabic'),
(315, 'ar', 'vi', 'Arabic'),
(316, 'ar', 'yi', 'Arabic'),
(317, 'ar', 'zh-hans', '阿拉伯语'),
(318, 'ar', 'zu', 'Arabic'),
(319, 'ar', 'zh-hant', '阿拉伯語'),
(320, 'ar', 'ms', 'Arabic'),
(321, 'bs', 'en', 'Bosnian'),
(322, 'bs', 'es', 'Bosnio'),
(323, 'bs', 'de', 'Bosnisch'),
(324, 'bs', 'fr', 'Bosnien'),
(325, 'bs', 'ar', 'البوسنية'),
(326, 'bs', 'bs', 'Bosnian'),
(327, 'bs', 'bg', 'Bosnian'),
(328, 'bs', 'ca', 'Bosnian'),
(329, 'bs', 'cs', 'Bosnian'),
(330, 'bs', 'sk', 'Bosniačtina'),
(331, 'bs', 'cy', 'Bosnian'),
(332, 'bs', 'da', 'Bosnian'),
(333, 'bs', 'el', 'Βοσνιακα'),
(334, 'bs', 'eo', 'Bosnian'),
(335, 'bs', 'et', 'Bosnian'),
(336, 'bs', 'eu', 'Bosnian'),
(337, 'bs', 'fa', 'Bosnian'),
(338, 'bs', 'fi', 'bosnia'),
(339, 'bs', 'ga', 'Bosnian'),
(340, 'bs', 'he', 'Bosnian'),
(341, 'bs', 'hi', 'Bosnian'),
(342, 'bs', 'hr', 'Bosnian'),
(343, 'bs', 'hu', 'bosnyák'),
(344, 'bs', 'hy', 'Bosnian'),
(345, 'bs', 'id', 'Bosnian'),
(346, 'bs', 'is', 'Bosnian'),
(347, 'bs', 'it', 'Bosniaco'),
(348, 'bs', 'ja', 'ボスニア語'),
(349, 'bs', 'ko', '보즈니아어'),
(350, 'bs', 'ku', 'Bosnian'),
(351, 'bs', 'la', 'Bosnian'),
(352, 'bs', 'lv', 'Bosnian'),
(353, 'bs', 'lt', 'Bosnian'),
(354, 'bs', 'mk', 'Bosnian'),
(355, 'bs', 'mt', 'Bosnian'),
(356, 'bs', 'mo', 'Bosnian'),
(357, 'bs', 'mn', 'Bosnian'),
(358, 'bs', 'ne', 'Bosnian'),
(359, 'bs', 'nl', 'Bosnisch'),
(360, 'bs', 'nb', 'Bosnian'),
(361, 'bs', 'pa', 'Bosnian'),
(362, 'bs', 'pl', 'bośniacki'),
(363, 'bs', 'pt-pt', 'Bósnio'),
(364, 'bs', 'pt-br', 'Bósnio'),
(365, 'bs', 'qu', 'Bosnian'),
(366, 'bs', 'ro', 'Bosniacă'),
(367, 'bs', 'ru', 'Боснийский'),
(368, 'bs', 'sl', 'Bosnian'),
(369, 'bs', 'so', 'Bosnian'),
(370, 'bs', 'sq', 'Bosnian'),
(371, 'bs', 'sr', 'Bosnian'),
(372, 'bs', 'sv', 'Bosniska'),
(373, 'bs', 'ta', 'Bosnian'),
(374, 'bs', 'th', 'บอสเนียน'),
(375, 'bs', 'tr', 'Boşnakça'),
(376, 'bs', 'uk', 'Bosnian'),
(377, 'bs', 'ur', 'Bosnian'),
(378, 'bs', 'uz', 'Bosnian'),
(379, 'bs', 'vi', 'Bosnian'),
(380, 'bs', 'yi', 'Bosnian'),
(381, 'bs', 'zh-hans', '波斯尼亚语'),
(382, 'bs', 'zu', 'Bosnian'),
(383, 'bs', 'zh-hant', '波士尼亞語'),
(384, 'bs', 'ms', 'Bosnian'),
(385, 'bg', 'en', 'Bulgarian'),
(386, 'bg', 'es', 'Búlgaro'),
(387, 'bg', 'de', 'Bulgarisch'),
(388, 'bg', 'fr', 'Bulgare'),
(389, 'bg', 'ar', 'البلغارية'),
(390, 'bg', 'bs', 'Bulgarian'),
(391, 'bg', 'bg', 'Bulgarian'),
(392, 'bg', 'ca', 'Bulgarian'),
(393, 'bg', 'cs', 'Bulgarian'),
(394, 'bg', 'sk', 'Bulharčina'),
(395, 'bg', 'cy', 'Bulgarian'),
(396, 'bg', 'da', 'Bulgarian'),
(397, 'bg', 'el', 'Βουλγαρικα'),
(398, 'bg', 'eo', 'Bulgarian'),
(399, 'bg', 'et', 'Bulgarian'),
(400, 'bg', 'eu', 'Bulgarian'),
(401, 'bg', 'fa', 'Bulgarian'),
(402, 'bg', 'fi', 'bulgaria'),
(403, 'bg', 'ga', 'Bulgarian'),
(404, 'bg', 'he', 'Bulgarian'),
(405, 'bg', 'hi', 'Bulgarian'),
(406, 'bg', 'hr', 'Bulgarian'),
(407, 'bg', 'hu', 'bolgár'),
(408, 'bg', 'hy', 'Bulgarian'),
(409, 'bg', 'id', 'Bulgarian'),
(410, 'bg', 'is', 'Bulgarian'),
(411, 'bg', 'it', 'Bulgaro'),
(412, 'bg', 'ja', 'ブルガリア語'),
(413, 'bg', 'ko', '불가리아어'),
(414, 'bg', 'ku', 'Bulgarian'),
(415, 'bg', 'la', 'Bulgarian'),
(416, 'bg', 'lv', 'Bulgarian'),
(417, 'bg', 'lt', 'Bulgarian'),
(418, 'bg', 'mk', 'Bulgarian'),
(419, 'bg', 'mt', 'Bulgarian'),
(420, 'bg', 'mo', 'Bulgarian'),
(421, 'bg', 'mn', 'Bulgarian'),
(422, 'bg', 'ne', 'Bulgarian'),
(423, 'bg', 'nl', 'Bulgaars'),
(424, 'bg', 'nb', 'Bulgarian'),
(425, 'bg', 'pa', 'Bulgarian'),
(426, 'bg', 'pl', 'bułgarski'),
(427, 'bg', 'pt-pt', 'Búlgaro'),
(428, 'bg', 'pt-br', 'Búlgaro'),
(429, 'bg', 'qu', 'Bulgarian'),
(430, 'bg', 'ro', 'Bulgară'),
(431, 'bg', 'ru', 'Болгарский'),
(432, 'bg', 'sl', 'Bulgarian'),
(433, 'bg', 'so', 'Bulgarian'),
(434, 'bg', 'sq', 'Bulgarian'),
(435, 'bg', 'sr', 'Bulgarian'),
(436, 'bg', 'sv', 'Bulgariska'),
(437, 'bg', 'ta', 'Bulgarian'),
(438, 'bg', 'th', 'บัลแกเรียน'),
(439, 'bg', 'tr', 'Bulgarca'),
(440, 'bg', 'uk', 'Bulgarian'),
(441, 'bg', 'ur', 'Bulgarian'),
(442, 'bg', 'uz', 'Bulgarian'),
(443, 'bg', 'vi', 'Bulgarian'),
(444, 'bg', 'yi', 'Bulgarian'),
(445, 'bg', 'zh-hans', '保加利亚语'),
(446, 'bg', 'zu', 'Bulgarian'),
(447, 'bg', 'zh-hant', '保加利亞語'),
(448, 'bg', 'ms', 'Bulgarian'),
(449, 'ca', 'en', 'Catalan'),
(450, 'ca', 'es', 'Catalán'),
(451, 'ca', 'de', 'Katalanisch'),
(452, 'ca', 'fr', 'Catalan'),
(453, 'ca', 'ar', 'الكاتالوينية'),
(454, 'ca', 'bs', 'Catalan'),
(455, 'ca', 'bg', 'Catalan'),
(456, 'ca', 'ca', 'Català'),
(457, 'ca', 'cs', 'Catalan'),
(458, 'ca', 'sk', 'Katalánčina'),
(459, 'ca', 'cy', 'Catalan'),
(460, 'ca', 'da', 'Catalan'),
(461, 'ca', 'el', 'Καταλανικα'),
(462, 'ca', 'eo', 'Catalan'),
(463, 'ca', 'et', 'Catalan'),
(464, 'ca', 'eu', 'Catalan'),
(465, 'ca', 'fa', 'Catalan'),
(466, 'ca', 'fi', 'katalaani'),
(467, 'ca', 'ga', 'Catalan'),
(468, 'ca', 'he', 'Catalan'),
(469, 'ca', 'hi', 'Catalan'),
(470, 'ca', 'hr', 'Catalan'),
(471, 'ca', 'hu', 'katalán'),
(472, 'ca', 'hy', 'Catalan'),
(473, 'ca', 'id', 'Catalan'),
(474, 'ca', 'is', 'Catalan'),
(475, 'ca', 'it', 'Catalano'),
(476, 'ca', 'ja', 'カタルーニャ語'),
(477, 'ca', 'ko', '카탈로니아어'),
(478, 'ca', 'ku', 'Catalan'),
(479, 'ca', 'la', 'Catalan'),
(480, 'ca', 'lv', 'Catalan'),
(481, 'ca', 'lt', 'Catalan'),
(482, 'ca', 'mk', 'Catalan'),
(483, 'ca', 'mt', 'Catalan'),
(484, 'ca', 'mo', 'Catalan'),
(485, 'ca', 'mn', 'Catalan'),
(486, 'ca', 'ne', 'Catalan'),
(487, 'ca', 'nl', 'Catalaans'),
(488, 'ca', 'nb', 'Catalan'),
(489, 'ca', 'pa', 'Catalan'),
(490, 'ca', 'pl', 'kataloński'),
(491, 'ca', 'pt-pt', 'Catalão'),
(492, 'ca', 'pt-br', 'Catalão'),
(493, 'ca', 'qu', 'Catalan'),
(494, 'ca', 'ro', 'Catalană'),
(495, 'ca', 'ru', 'Каталанский'),
(496, 'ca', 'sl', 'Catalan'),
(497, 'ca', 'so', 'Catalan'),
(498, 'ca', 'sq', 'Catalan'),
(499, 'ca', 'sr', 'Catalan'),
(500, 'ca', 'sv', 'Katalanska'),
(501, 'ca', 'ta', 'Catalan'),
(502, 'ca', 'th', 'คะตะลาน'),
(503, 'ca', 'tr', 'Katalan dili'),
(504, 'ca', 'uk', 'Catalan'),
(505, 'ca', 'ur', 'Catalan'),
(506, 'ca', 'uz', 'Catalan'),
(507, 'ca', 'vi', 'Catalan'),
(508, 'ca', 'yi', 'Catalan'),
(509, 'ca', 'zh-hans', '加泰罗尼亚语'),
(510, 'ca', 'zu', 'Catalan'),
(511, 'ca', 'zh-hant', '加泰羅尼亞語'),
(512, 'ca', 'ms', 'Catalan'),
(513, 'cs', 'en', 'Czech'),
(514, 'cs', 'es', 'Checo'),
(515, 'cs', 'de', 'Tschechisch'),
(516, 'cs', 'fr', 'Tchèque'),
(517, 'cs', 'ar', 'التشيكية'),
(518, 'cs', 'bs', 'Czech'),
(519, 'cs', 'bg', 'Czech'),
(520, 'cs', 'ca', 'Czech'),
(521, 'cs', 'cs', 'Čeština'),
(522, 'cs', 'sk', 'Čeština'),
(523, 'cs', 'cy', 'Czech'),
(524, 'cs', 'da', 'Czech'),
(525, 'cs', 'el', 'Τσεχικη'),
(526, 'cs', 'eo', 'Czech'),
(527, 'cs', 'et', 'Czech'),
(528, 'cs', 'eu', 'Czech'),
(529, 'cs', 'fa', 'Czech'),
(530, 'cs', 'fi', 'tsekki'),
(531, 'cs', 'ga', 'Czech'),
(532, 'cs', 'he', 'Czech'),
(533, 'cs', 'hi', 'Czech'),
(534, 'cs', 'hr', 'Czech'),
(535, 'cs', 'hu', 'cseh'),
(536, 'cs', 'hy', 'Czech'),
(537, 'cs', 'id', 'Czech'),
(538, 'cs', 'is', 'Czech'),
(539, 'cs', 'it', 'Ceco'),
(540, 'cs', 'ja', 'チェコ語'),
(541, 'cs', 'ko', '체코슬로바키아어'),
(542, 'cs', 'ku', 'Czech'),
(543, 'cs', 'la', 'Czech'),
(544, 'cs', 'lv', 'Czech'),
(545, 'cs', 'lt', 'Czech'),
(546, 'cs', 'mk', 'Czech'),
(547, 'cs', 'mt', 'Czech'),
(548, 'cs', 'mo', 'Czech'),
(549, 'cs', 'mn', 'Czech'),
(550, 'cs', 'ne', 'Czech'),
(551, 'cs', 'nl', 'Tsjechisch'),
(552, 'cs', 'nb', 'Czech'),
(553, 'cs', 'pa', 'Czech'),
(554, 'cs', 'pl', 'czeski'),
(555, 'cs', 'pt-pt', 'Checa'),
(556, 'cs', 'pt-br', 'Checa'),
(557, 'cs', 'qu', 'Czech'),
(558, 'cs', 'ro', 'Cehă'),
(559, 'cs', 'ru', 'Чешский'),
(560, 'cs', 'sl', 'Czech'),
(561, 'cs', 'so', 'Czech'),
(562, 'cs', 'sq', 'Czech'),
(563, 'cs', 'sr', 'Czech'),
(564, 'cs', 'sv', 'Tjeckiska'),
(565, 'cs', 'ta', 'Czech'),
(566, 'cs', 'th', 'เช็ก'),
(567, 'cs', 'tr', 'Çekçe'),
(568, 'cs', 'uk', 'Czech'),
(569, 'cs', 'ur', 'Czech'),
(570, 'cs', 'uz', 'Czech'),
(571, 'cs', 'vi', 'Czech'),
(572, 'cs', 'yi', 'Czech'),
(573, 'cs', 'zh-hans', '捷克语'),
(574, 'cs', 'zu', 'Czech'),
(575, 'cs', 'zh-hant', '捷克語'),
(576, 'cs', 'ms', 'Czech'),
(577, 'sk', 'en', 'Slovak'),
(578, 'sk', 'es', 'Eslavo'),
(579, 'sk', 'de', 'Slawisch'),
(580, 'sk', 'fr', 'Slave'),
(581, 'sk', 'ar', 'السلافية'),
(582, 'sk', 'bs', 'Slovak'),
(583, 'sk', 'bg', 'Slovak'),
(584, 'sk', 'ca', 'Slovak'),
(585, 'sk', 'cs', 'Slovak'),
(586, 'sk', 'sk', 'Slovenčina'),
(587, 'sk', 'cy', 'Slovak'),
(588, 'sk', 'da', 'Slovak'),
(589, 'sk', 'el', 'Σλαβικη'),
(590, 'sk', 'eo', 'Slovak'),
(591, 'sk', 'et', 'Slovak'),
(592, 'sk', 'eu', 'Slovak'),
(593, 'sk', 'fa', 'Slovak'),
(594, 'sk', 'fi', 'slaavi'),
(595, 'sk', 'ga', 'Slovak'),
(596, 'sk', 'he', 'Slavic'),
(597, 'sk', 'hi', 'Slovak'),
(598, 'sk', 'hr', 'Slovak'),
(599, 'sk', 'hu', 'szláv'),
(600, 'sk', 'hy', 'Slovak'),
(601, 'sk', 'id', 'Slovak'),
(602, 'sk', 'is', 'Slovak'),
(603, 'sk', 'it', 'Slavo'),
(604, 'sk', 'ja', 'スラヴ語派'),
(605, 'sk', 'ko', '슬라브어'),
(606, 'sk', 'ku', 'Slovak'),
(607, 'sk', 'la', 'Slovak'),
(608, 'sk', 'lv', 'Slovak'),
(609, 'sk', 'lt', 'Slovak'),
(610, 'sk', 'mk', 'Slovak'),
(611, 'sk', 'mt', 'Slovak'),
(612, 'sk', 'mo', 'Slovak'),
(613, 'sk', 'mn', 'Slovak'),
(614, 'sk', 'ne', 'Slovak'),
(615, 'sk', 'nl', 'Slavisch'),
(616, 'sk', 'nb', 'Slovak'),
(617, 'sk', 'pa', 'Slovak'),
(618, 'sk', 'pl', 'słowiański'),
(619, 'sk', 'pt-pt', 'Eslava'),
(620, 'sk', 'pt-br', 'Eslava'),
(621, 'sk', 'qu', 'Slovak'),
(622, 'sk', 'ro', 'Slavă'),
(623, 'sk', 'ru', 'Славянский'),
(624, 'sk', 'sl', 'Slovak'),
(625, 'sk', 'so', 'Slovak'),
(626, 'sk', 'sq', 'Slovak'),
(627, 'sk', 'sr', 'Slovak'),
(628, 'sk', 'sv', 'Slavisk'),
(629, 'sk', 'ta', 'Slovak'),
(630, 'sk', 'th', 'สลาวิก'),
(631, 'sk', 'tr', 'Slav dili'),
(632, 'sk', 'uk', 'Slovak'),
(633, 'sk', 'ur', 'Slovak'),
(634, 'sk', 'uz', 'Slovak'),
(635, 'sk', 'vi', 'Slovak'),
(636, 'sk', 'yi', 'Slovak'),
(637, 'sk', 'zh-hans', '斯拉夫语'),
(638, 'sk', 'zu', 'Slovak'),
(639, 'sk', 'zh-hant', '斯拉夫語'),
(640, 'sk', 'ms', 'Slovak'),
(641, 'cy', 'en', 'Welsh'),
(642, 'cy', 'es', 'Galés'),
(643, 'cy', 'de', 'Walisisch'),
(644, 'cy', 'fr', 'Gallois'),
(645, 'cy', 'ar', 'الولزية'),
(646, 'cy', 'bs', 'Welsh'),
(647, 'cy', 'bg', 'Welsh'),
(648, 'cy', 'ca', 'Welsh'),
(649, 'cy', 'cs', 'Welsh'),
(650, 'cy', 'sk', 'Welština'),
(651, 'cy', 'cy', 'Cymraeg'),
(652, 'cy', 'da', 'Welsh'),
(653, 'cy', 'el', 'Welsh'),
(654, 'cy', 'eo', 'Welsh'),
(655, 'cy', 'et', 'Welsh'),
(656, 'cy', 'eu', 'Welsh'),
(657, 'cy', 'fa', 'Welsh'),
(658, 'cy', 'fi', 'kymri'),
(659, 'cy', 'ga', 'Welsh'),
(660, 'cy', 'he', 'Welsh'),
(661, 'cy', 'hi', 'Welsh'),
(662, 'cy', 'hr', 'Welsh'),
(663, 'cy', 'hu', 'vels'),
(664, 'cy', 'hy', 'Welsh'),
(665, 'cy', 'id', 'Welsh'),
(666, 'cy', 'is', 'Welsh'),
(667, 'cy', 'it', 'Gallese'),
(668, 'cy', 'ja', 'ウェールズ語'),
(669, 'cy', 'ko', '웨일즈어'),
(670, 'cy', 'ku', 'Welsh'),
(671, 'cy', 'la', 'Welsh'),
(672, 'cy', 'lv', 'Welsh'),
(673, 'cy', 'lt', 'Welsh'),
(674, 'cy', 'mk', 'Welsh'),
(675, 'cy', 'mt', 'Welsh'),
(676, 'cy', 'mo', 'Welsh'),
(677, 'cy', 'mn', 'Welsh'),
(678, 'cy', 'ne', 'Welsh'),
(679, 'cy', 'nl', 'Welsh'),
(680, 'cy', 'nb', 'Welsh'),
(681, 'cy', 'pa', 'Welsh'),
(682, 'cy', 'pl', 'walijski'),
(683, 'cy', 'pt-pt', 'Welsh'),
(684, 'cy', 'pt-br', 'Welsh'),
(685, 'cy', 'qu', 'Welsh'),
(686, 'cy', 'ro', 'Galeză'),
(687, 'cy', 'ru', 'Валлийский'),
(688, 'cy', 'sl', 'Welsh'),
(689, 'cy', 'so', 'Welsh'),
(690, 'cy', 'sq', 'Welsh'),
(691, 'cy', 'sr', 'Welsh'),
(692, 'cy', 'sv', 'Walesiska'),
(693, 'cy', 'ta', 'Welsh'),
(694, 'cy', 'th', 'เวลช์'),
(695, 'cy', 'tr', 'Galce'),
(696, 'cy', 'uk', 'Welsh'),
(697, 'cy', 'ur', 'Welsh'),
(698, 'cy', 'uz', 'Welsh'),
(699, 'cy', 'vi', 'Welsh'),
(700, 'cy', 'yi', 'Welsh'),
(701, 'cy', 'zh-hans', '威尔士语'),
(702, 'cy', 'zu', 'Welsh'),
(703, 'cy', 'zh-hant', '威爾士語'),
(704, 'cy', 'ms', 'Welsh'),
(705, 'da', 'en', 'Danish'),
(706, 'da', 'es', 'Danés'),
(707, 'da', 'de', 'Dänisch'),
(708, 'da', 'fr', 'Danois'),
(709, 'da', 'ar', 'الدانماركية'),
(710, 'da', 'bs', 'Danish'),
(711, 'da', 'bg', 'Danish'),
(712, 'da', 'ca', 'Danish'),
(713, 'da', 'cs', 'Danish'),
(714, 'da', 'sk', 'Dánčina'),
(715, 'da', 'cy', 'Danish'),
(716, 'da', 'da', 'Dansk'),
(717, 'da', 'el', 'Δανεζικα'),
(718, 'da', 'eo', 'Danish'),
(719, 'da', 'et', 'Danish'),
(720, 'da', 'eu', 'Danish'),
(721, 'da', 'fa', 'Danish'),
(722, 'da', 'fi', 'tanska'),
(723, 'da', 'ga', 'Danish'),
(724, 'da', 'he', 'דנית'),
(725, 'da', 'hi', 'Danish'),
(726, 'da', 'hr', 'Danish'),
(727, 'da', 'hu', 'dán'),
(728, 'da', 'hy', 'Danish'),
(729, 'da', 'id', 'Danish'),
(730, 'da', 'is', 'Danish'),
(731, 'da', 'it', 'Danese'),
(732, 'da', 'ja', 'デンマーク語'),
(733, 'da', 'ko', '덴마크어'),
(734, 'da', 'ku', 'Danish'),
(735, 'da', 'la', 'Danish'),
(736, 'da', 'lv', 'Danish'),
(737, 'da', 'lt', 'Danish'),
(738, 'da', 'mk', 'Danish'),
(739, 'da', 'mt', 'Danish'),
(740, 'da', 'mo', 'Danish'),
(741, 'da', 'mn', 'Danish'),
(742, 'da', 'ne', 'Danish'),
(743, 'da', 'nl', 'Deens'),
(744, 'da', 'nb', 'Danish'),
(745, 'da', 'pa', 'Danish'),
(746, 'da', 'pl', 'duński'),
(747, 'da', 'pt-pt', 'Dinamarquês'),
(748, 'da', 'pt-br', 'Dinamarquês'),
(749, 'da', 'qu', 'Danish'),
(750, 'da', 'ro', 'Daneză'),
(751, 'da', 'ru', 'Датский'),
(752, 'da', 'sl', 'Danish'),
(753, 'da', 'so', 'Danish'),
(754, 'da', 'sq', 'Danish'),
(755, 'da', 'sr', 'Danish'),
(756, 'da', 'sv', 'Danska'),
(757, 'da', 'ta', 'Danish'),
(758, 'da', 'th', 'เดนมาร์ก'),
(759, 'da', 'tr', 'Danca'),
(760, 'da', 'uk', 'Danish'),
(761, 'da', 'ur', 'Danish'),
(762, 'da', 'uz', 'Danish'),
(763, 'da', 'vi', 'Danish'),
(764, 'da', 'yi', 'Danish'),
(765, 'da', 'zh-hans', '丹麦语'),
(766, 'da', 'zu', 'Danish'),
(767, 'da', 'zh-hant', '丹麥語'),
(768, 'da', 'ms', 'Danish'),
(769, 'el', 'en', 'Greek'),
(770, 'el', 'es', 'Griego'),
(771, 'el', 'de', 'Griechisch'),
(772, 'el', 'fr', 'Grec moderne'),
(773, 'el', 'ar', 'اليونانية'),
(774, 'el', 'bs', 'Greek'),
(775, 'el', 'bg', 'Greek'),
(776, 'el', 'ca', 'Greek'),
(777, 'el', 'cs', 'Greek'),
(778, 'el', 'sk', 'Gréčtina'),
(779, 'el', 'cy', 'Greek'),
(780, 'el', 'da', 'Greek'),
(781, 'el', 'el', 'Ελληνικα'),
(782, 'el', 'eo', 'Greek'),
(783, 'el', 'et', 'Greek'),
(784, 'el', 'eu', 'Greek'),
(785, 'el', 'fa', 'Greek'),
(786, 'el', 'fi', 'kreikka'),
(787, 'el', 'ga', 'Greek'),
(788, 'el', 'he', 'יוונית'),
(789, 'el', 'hi', 'Greek'),
(790, 'el', 'hr', 'Greek'),
(791, 'el', 'hu', 'görög'),
(792, 'el', 'hy', 'Greek'),
(793, 'el', 'id', 'Greek'),
(794, 'el', 'is', 'Greek'),
(795, 'el', 'it', 'Greco'),
(796, 'el', 'ja', 'ギリシア語'),
(797, 'el', 'ko', '그리스어'),
(798, 'el', 'ku', 'Greek'),
(799, 'el', 'la', 'Greek'),
(800, 'el', 'lv', 'Greek'),
(801, 'el', 'lt', 'Greek'),
(802, 'el', 'mk', 'Greek'),
(803, 'el', 'mt', 'Greek'),
(804, 'el', 'mo', 'Greek'),
(805, 'el', 'mn', 'Greek'),
(806, 'el', 'ne', 'Greek'),
(807, 'el', 'nl', 'Grieks'),
(808, 'el', 'nb', 'Greek'),
(809, 'el', 'pa', 'Greek'),
(810, 'el', 'pl', 'grecki'),
(811, 'el', 'pt-pt', 'Grego'),
(812, 'el', 'pt-br', 'Grego'),
(813, 'el', 'qu', 'Greek'),
(814, 'el', 'ro', 'Greacă'),
(815, 'el', 'ru', 'Греческий'),
(816, 'el', 'sl', 'Greek'),
(817, 'el', 'so', 'Greek'),
(818, 'el', 'sq', 'Greek'),
(819, 'el', 'sr', 'Greek'),
(820, 'el', 'sv', 'Grekiska'),
(821, 'el', 'ta', 'Greek'),
(822, 'el', 'th', 'กรีก'),
(823, 'el', 'tr', 'Yunanca'),
(824, 'el', 'uk', 'Greek'),
(825, 'el', 'ur', 'Greek'),
(826, 'el', 'uz', 'Greek'),
(827, 'el', 'vi', 'Greek'),
(828, 'el', 'yi', 'Greek'),
(829, 'el', 'zh-hans', '希腊语'),
(830, 'el', 'zu', 'Greek'),
(831, 'el', 'zh-hant', '希臘語'),
(832, 'el', 'ms', 'Greek'),
(833, 'eo', 'en', 'Esperanto'),
(834, 'eo', 'es', 'Esperanto'),
(835, 'eo', 'de', 'Esperanto'),
(836, 'eo', 'fr', 'Espéranto'),
(837, 'eo', 'ar', 'الاسبرانتو'),
(838, 'eo', 'bs', 'Esperanto'),
(839, 'eo', 'bg', 'Esperanto'),
(840, 'eo', 'ca', 'Esperanto'),
(841, 'eo', 'cs', 'Esperanto'),
(842, 'eo', 'sk', 'Esperanto'),
(843, 'eo', 'cy', 'Esperanto'),
(844, 'eo', 'da', 'Esperanto'),
(845, 'eo', 'el', 'Εσπεραντο'),
(846, 'eo', 'eo', 'Esperanto'),
(847, 'eo', 'et', 'Esperanto'),
(848, 'eo', 'eu', 'Esperanto'),
(849, 'eo', 'fa', 'Esperanto'),
(850, 'eo', 'fi', 'esperanto'),
(851, 'eo', 'ga', 'Esperanto'),
(852, 'eo', 'he', 'Esperanto'),
(853, 'eo', 'hi', 'Esperanto'),
(854, 'eo', 'hr', 'Esperanto'),
(855, 'eo', 'hu', 'eszperantó'),
(856, 'eo', 'hy', 'Esperanto'),
(857, 'eo', 'id', 'Esperanto'),
(858, 'eo', 'is', 'Esperanto'),
(859, 'eo', 'it', 'Esperanto'),
(860, 'eo', 'ja', 'エスペラント語'),
(861, 'eo', 'ko', '에스페란토어'),
(862, 'eo', 'ku', 'Esperanto'),
(863, 'eo', 'la', 'Esperanto'),
(864, 'eo', 'lv', 'Esperanto'),
(865, 'eo', 'lt', 'Esperanto'),
(866, 'eo', 'mk', 'Esperanto'),
(867, 'eo', 'mt', 'Esperanto'),
(868, 'eo', 'mo', 'Esperanto'),
(869, 'eo', 'mn', 'Esperanto'),
(870, 'eo', 'ne', 'Esperanto'),
(871, 'eo', 'nl', 'Esperanto'),
(872, 'eo', 'nb', 'Esperanto'),
(873, 'eo', 'pa', 'Esperanto'),
(874, 'eo', 'pl', 'esperanto'),
(875, 'eo', 'pt-pt', 'Esperanto'),
(876, 'eo', 'pt-br', 'Esperanto'),
(877, 'eo', 'qu', 'Esperanto'),
(878, 'eo', 'ro', 'Esperanto'),
(879, 'eo', 'ru', 'Эсперанто'),
(880, 'eo', 'sl', 'Esperanto'),
(881, 'eo', 'so', 'Esperanto'),
(882, 'eo', 'sq', 'Esperanto'),
(883, 'eo', 'sr', 'Esperanto'),
(884, 'eo', 'sv', 'Esperanto'),
(885, 'eo', 'ta', 'Esperanto'),
(886, 'eo', 'th', 'เอสเปอรันโต'),
(887, 'eo', 'tr', 'Esperanto'),
(888, 'eo', 'uk', 'Esperanto'),
(889, 'eo', 'ur', 'Esperanto'),
(890, 'eo', 'uz', 'Esperanto'),
(891, 'eo', 'vi', 'Esperanto'),
(892, 'eo', 'yi', 'Esperanto'),
(893, 'eo', 'zh-hans', '世界语'),
(894, 'eo', 'zu', 'Esperanto'),
(895, 'eo', 'zh-hant', '世界語'),
(896, 'eo', 'ms', 'Esperanto'),
(897, 'et', 'en', 'Estonian'),
(898, 'et', 'es', 'Estonio'),
(899, 'et', 'de', 'Estnisch'),
(900, 'et', 'fr', 'Estonien'),
(901, 'et', 'ar', 'الأستونية'),
(902, 'et', 'bs', 'Estonian'),
(903, 'et', 'bg', 'Estonian'),
(904, 'et', 'ca', 'Estonian'),
(905, 'et', 'cs', 'Estonian'),
(906, 'et', 'sk', 'Estónčina'),
(907, 'et', 'cy', 'Estonian'),
(908, 'et', 'da', 'Estonian'),
(909, 'et', 'el', 'Εσθονικα'),
(910, 'et', 'eo', 'Estonian'),
(911, 'et', 'et', 'Eesti'),
(912, 'et', 'eu', 'Estonian'),
(913, 'et', 'fa', 'Estonian'),
(914, 'et', 'fi', 'eesti'),
(915, 'et', 'ga', 'Estonian'),
(916, 'et', 'he', 'Estonian'),
(917, 'et', 'hi', 'Estonian'),
(918, 'et', 'hr', 'Estonian'),
(919, 'et', 'hu', 'észt'),
(920, 'et', 'hy', 'Estonian'),
(921, 'et', 'id', 'Estonian'),
(922, 'et', 'is', 'Estonian'),
(923, 'et', 'it', 'Estone'),
(924, 'et', 'ja', 'エストニア語'),
(925, 'et', 'ko', '에스토니아어'),
(926, 'et', 'ku', 'Estonian'),
(927, 'et', 'la', 'Estonian'),
(928, 'et', 'lv', 'Estonian'),
(929, 'et', 'lt', 'Estonian'),
(930, 'et', 'mk', 'Estonian'),
(931, 'et', 'mt', 'Estonian'),
(932, 'et', 'mo', 'Estonian'),
(933, 'et', 'mn', 'Estonian'),
(934, 'et', 'ne', 'Estonian'),
(935, 'et', 'nl', 'Ests'),
(936, 'et', 'nb', 'Estonian'),
(937, 'et', 'pa', 'Estonian'),
(938, 'et', 'pl', 'estoński'),
(939, 'et', 'pt-pt', 'Estoniano'),
(940, 'et', 'pt-br', 'Estoniano'),
(941, 'et', 'qu', 'Estonian'),
(942, 'et', 'ro', 'Estoniană'),
(943, 'et', 'ru', 'Эстонский'),
(944, 'et', 'sl', 'Estonian'),
(945, 'et', 'so', 'Estonian'),
(946, 'et', 'sq', 'Estonian'),
(947, 'et', 'sr', 'Estonian'),
(948, 'et', 'sv', 'Estniska'),
(949, 'et', 'ta', 'Estonian'),
(950, 'et', 'th', 'เอสโตเนียน'),
(951, 'et', 'tr', 'Estonya dili'),
(952, 'et', 'uk', 'Estonian'),
(953, 'et', 'ur', 'Estonian'),
(954, 'et', 'uz', 'Estonian'),
(955, 'et', 'vi', 'Estonian'),
(956, 'et', 'yi', 'Estonian'),
(957, 'et', 'zh-hans', '爱沙尼亚语'),
(958, 'et', 'zu', 'Estonian'),
(959, 'et', 'zh-hant', '愛沙尼亞語'),
(960, 'et', 'ms', 'Estonian'),
(961, 'eu', 'en', 'Basque'),
(962, 'eu', 'es', 'Euskera'),
(963, 'eu', 'de', 'Baskisch'),
(964, 'eu', 'fr', 'Basque'),
(965, 'eu', 'ar', 'لغة الباسك'),
(966, 'eu', 'bs', 'Basque'),
(967, 'eu', 'bg', 'Basque'),
(968, 'eu', 'ca', 'Basque'),
(969, 'eu', 'cs', 'Basque'),
(970, 'eu', 'sk', 'Baskičtina'),
(971, 'eu', 'cy', 'Basque'),
(972, 'eu', 'da', 'Basque'),
(973, 'eu', 'el', 'Βασκικα'),
(974, 'eu', 'eo', 'Basque'),
(975, 'eu', 'et', 'Basque'),
(976, 'eu', 'eu', 'Euskara'),
(977, 'eu', 'fa', 'Basque'),
(978, 'eu', 'fi', 'baski'),
(979, 'eu', 'ga', 'Basque'),
(980, 'eu', 'he', 'Basque'),
(981, 'eu', 'hi', 'Basque'),
(982, 'eu', 'hr', 'Basque'),
(983, 'eu', 'hu', 'baszk'),
(984, 'eu', 'hy', 'Basque'),
(985, 'eu', 'id', 'Basque'),
(986, 'eu', 'is', 'Basque'),
(987, 'eu', 'it', 'Basco'),
(988, 'eu', 'ja', 'バスク語'),
(989, 'eu', 'ko', '바스크어'),
(990, 'eu', 'ku', 'Basque'),
(991, 'eu', 'la', 'Basque'),
(992, 'eu', 'lv', 'Basque'),
(993, 'eu', 'lt', 'Basque'),
(994, 'eu', 'mk', 'Basque'),
(995, 'eu', 'mt', 'Basque'),
(996, 'eu', 'mo', 'Basque'),
(997, 'eu', 'mn', 'Basque'),
(998, 'eu', 'ne', 'Basque'),
(999, 'eu', 'nl', 'Baskisch'),
(1000, 'eu', 'nb', 'Basque'),
(1001, 'eu', 'pa', 'Basque'),
(1002, 'eu', 'pl', 'baskijski'),
(1003, 'eu', 'pt-pt', 'Basco'),
(1004, 'eu', 'pt-br', 'Basco'),
(1005, 'eu', 'qu', 'Basque'),
(1006, 'eu', 'ro', 'Bască'),
(1007, 'eu', 'ru', 'Баскский'),
(1008, 'eu', 'sl', 'Basque'),
(1009, 'eu', 'so', 'Basque'),
(1010, 'eu', 'sq', 'Basque'),
(1011, 'eu', 'sr', 'Basque'),
(1012, 'eu', 'sv', 'Baskiska'),
(1013, 'eu', 'ta', 'Basque'),
(1014, 'eu', 'th', 'บาสค์'),
(1015, 'eu', 'tr', 'Bask dili'),
(1016, 'eu', 'uk', 'Basque'),
(1017, 'eu', 'ur', 'Basque'),
(1018, 'eu', 'uz', 'Basque'),
(1019, 'eu', 'vi', 'Basque'),
(1020, 'eu', 'yi', 'Basque'),
(1021, 'eu', 'zh-hans', '巴斯克语'),
(1022, 'eu', 'zu', 'Basque'),
(1023, 'eu', 'zh-hant', '巴斯克語'),
(1024, 'eu', 'ms', 'Basque'),
(1025, 'fa', 'en', 'Persian'),
(1026, 'fa', 'es', 'Persa'),
(1027, 'fa', 'de', 'Persisch'),
(1028, 'fa', 'fr', 'Perse'),
(1029, 'fa', 'ar', 'الفارسية'),
(1030, 'fa', 'bs', 'Persian'),
(1031, 'fa', 'bg', 'Persian'),
(1032, 'fa', 'ca', 'Persian'),
(1033, 'fa', 'cs', 'Persian'),
(1034, 'fa', 'sk', 'Perzština'),
(1035, 'fa', 'cy', 'Persian'),
(1036, 'fa', 'da', 'Persian'),
(1037, 'fa', 'el', 'Περσικος'),
(1038, 'fa', 'eo', 'Persian'),
(1039, 'fa', 'et', 'Persian'),
(1040, 'fa', 'eu', 'Persian'),
(1041, 'fa', 'fa', 'پارسی'),
(1042, 'fa', 'fi', 'persia'),
(1043, 'fa', 'ga', 'Persian'),
(1044, 'fa', 'he', 'פרסית'),
(1045, 'fa', 'hi', 'Persian'),
(1046, 'fa', 'hr', 'Persian'),
(1047, 'fa', 'hu', 'perzsa'),
(1048, 'fa', 'hy', 'Persian'),
(1049, 'fa', 'id', 'Persian'),
(1050, 'fa', 'is', 'Persian'),
(1051, 'fa', 'it', 'Persiano'),
(1052, 'fa', 'ja', 'ペルシア語'),
(1053, 'fa', 'ko', '페르시아어'),
(1054, 'fa', 'ku', 'Persian'),
(1055, 'fa', 'la', 'Persian'),
(1056, 'fa', 'lv', 'Persian'),
(1057, 'fa', 'lt', 'Persian'),
(1058, 'fa', 'mk', 'Persian'),
(1059, 'fa', 'mt', 'Persian'),
(1060, 'fa', 'mo', 'Persian'),
(1061, 'fa', 'mn', 'Persian'),
(1062, 'fa', 'ne', 'Persian'),
(1063, 'fa', 'nl', 'Perzisch'),
(1064, 'fa', 'nb', 'Persian'),
(1065, 'fa', 'pa', 'Persian'),
(1066, 'fa', 'pl', 'perski'),
(1067, 'fa', 'pt-pt', 'Persa'),
(1068, 'fa', 'pt-br', 'Persa'),
(1069, 'fa', 'qu', 'Persian'),
(1070, 'fa', 'ro', 'Persană'),
(1071, 'fa', 'ru', 'Персидский'),
(1072, 'fa', 'sl', 'Persian'),
(1073, 'fa', 'so', 'Persian'),
(1074, 'fa', 'sq', 'Persian'),
(1075, 'fa', 'sr', 'Persian'),
(1076, 'fa', 'sv', 'Persiska'),
(1077, 'fa', 'ta', 'Persian'),
(1078, 'fa', 'th', 'เปอร์เซียน'),
(1079, 'fa', 'tr', 'Farsça'),
(1080, 'fa', 'uk', 'Persian'),
(1081, 'fa', 'ur', 'Persian'),
(1082, 'fa', 'uz', 'Persian'),
(1083, 'fa', 'vi', 'Persian'),
(1084, 'fa', 'yi', 'Persian'),
(1085, 'fa', 'zh-hans', '波斯语'),
(1086, 'fa', 'zu', 'Persian'),
(1087, 'fa', 'zh-hant', '波斯語'),
(1088, 'fa', 'ms', 'Persian'),
(1089, 'fi', 'en', 'Finnish'),
(1090, 'fi', 'es', 'Finlandés'),
(1091, 'fi', 'de', 'Finnisch'),
(1092, 'fi', 'fr', 'Finnois'),
(1093, 'fi', 'ar', 'الفنلندية'),
(1094, 'fi', 'bs', 'Finnish'),
(1095, 'fi', 'bg', 'Finnish'),
(1096, 'fi', 'ca', 'Finnish'),
(1097, 'fi', 'cs', 'Finnish'),
(1098, 'fi', 'sk', 'Fínština'),
(1099, 'fi', 'cy', 'Finnish'),
(1100, 'fi', 'da', 'Finnish'),
(1101, 'fi', 'el', 'Φινλανδικη'),
(1102, 'fi', 'eo', 'Finnish'),
(1103, 'fi', 'et', 'Finnish'),
(1104, 'fi', 'eu', 'Finnish'),
(1105, 'fi', 'fa', 'Finnish'),
(1106, 'fi', 'fi', 'Suomi'),
(1107, 'fi', 'ga', 'Finnish'),
(1108, 'fi', 'he', 'פינית'),
(1109, 'fi', 'hi', 'Finnish'),
(1110, 'fi', 'hr', 'Finnish'),
(1111, 'fi', 'hu', 'finn'),
(1112, 'fi', 'hy', 'Finnish'),
(1113, 'fi', 'id', 'Finnish'),
(1114, 'fi', 'is', 'Finnish'),
(1115, 'fi', 'it', 'Finlandese'),
(1116, 'fi', 'ja', 'フィンランド語'),
(1117, 'fi', 'ko', '핀란드어'),
(1118, 'fi', 'ku', 'Finnish'),
(1119, 'fi', 'la', 'Finnish'),
(1120, 'fi', 'lv', 'Finnish'),
(1121, 'fi', 'lt', 'Finnish'),
(1122, 'fi', 'mk', 'Finnish'),
(1123, 'fi', 'mt', 'Finnish'),
(1124, 'fi', 'mo', 'Finnish'),
(1125, 'fi', 'mn', 'Finnish'),
(1126, 'fi', 'ne', 'Finnish'),
(1127, 'fi', 'nl', 'Fins'),
(1128, 'fi', 'nb', 'Finnish'),
(1129, 'fi', 'pa', 'Finnish'),
(1130, 'fi', 'pl', 'fiński'),
(1131, 'fi', 'pt-pt', 'Finlandês'),
(1132, 'fi', 'pt-br', 'Finlandês'),
(1133, 'fi', 'qu', 'Finnish'),
(1134, 'fi', 'ro', 'Finlandeză'),
(1135, 'fi', 'ru', 'Финский'),
(1136, 'fi', 'sl', 'Finnish'),
(1137, 'fi', 'so', 'Finnish'),
(1138, 'fi', 'sq', 'Finnish'),
(1139, 'fi', 'sr', 'Finnish'),
(1140, 'fi', 'sv', 'Finska'),
(1141, 'fi', 'ta', 'Finnish'),
(1142, 'fi', 'th', 'ฟินนิช'),
(1143, 'fi', 'tr', 'Fince'),
(1144, 'fi', 'uk', 'Finnish'),
(1145, 'fi', 'ur', 'Finnish'),
(1146, 'fi', 'uz', 'Finnish'),
(1147, 'fi', 'vi', 'Finnish'),
(1148, 'fi', 'yi', 'Finnish'),
(1149, 'fi', 'zh-hans', '芬兰语'),
(1150, 'fi', 'zu', 'Finnish'),
(1151, 'fi', 'zh-hant', '芬蘭語'),
(1152, 'fi', 'ms', 'Finnish'),
(1153, 'ga', 'en', 'Irish'),
(1154, 'ga', 'es', 'Irlandés'),
(1155, 'ga', 'de', 'Irisch'),
(1156, 'ga', 'fr', 'Irlandais'),
(1157, 'ga', 'ar', 'الأيرلندية'),
(1158, 'ga', 'bs', 'Irish'),
(1159, 'ga', 'bg', 'Irish'),
(1160, 'ga', 'ca', 'Irish'),
(1161, 'ga', 'cs', 'Irish'),
(1162, 'ga', 'sk', 'Írština'),
(1163, 'ga', 'cy', 'Irish'),
(1164, 'ga', 'da', 'Irish'),
(1165, 'ga', 'el', 'Ιρλανδικα'),
(1166, 'ga', 'eo', 'Irish'),
(1167, 'ga', 'et', 'Irish'),
(1168, 'ga', 'eu', 'Irish'),
(1169, 'ga', 'fa', 'Irish'),
(1170, 'ga', 'fi', 'iiri'),
(1171, 'ga', 'ga', 'Gaeilge'),
(1172, 'ga', 'he', 'אירית'),
(1173, 'ga', 'hi', 'Irish'),
(1174, 'ga', 'hr', 'Irish'),
(1175, 'ga', 'hu', 'ír'),
(1176, 'ga', 'hy', 'Irish'),
(1177, 'ga', 'id', 'Irish'),
(1178, 'ga', 'is', 'Irish'),
(1179, 'ga', 'it', 'Irlandese'),
(1180, 'ga', 'ja', 'アイルランド語'),
(1181, 'ga', 'ko', '아일랜드어'),
(1182, 'ga', 'ku', 'Irish'),
(1183, 'ga', 'la', 'Irish'),
(1184, 'ga', 'lv', 'Irish'),
(1185, 'ga', 'lt', 'Irish'),
(1186, 'ga', 'mk', 'Irish'),
(1187, 'ga', 'mt', 'Irish'),
(1188, 'ga', 'mo', 'Irish'),
(1189, 'ga', 'mn', 'Irish'),
(1190, 'ga', 'ne', 'Irish'),
(1191, 'ga', 'nl', 'Iers'),
(1192, 'ga', 'nb', 'Irish'),
(1193, 'ga', 'pa', 'Irish'),
(1194, 'ga', 'pl', 'irlandzki'),
(1195, 'ga', 'pt-pt', 'Irlandês'),
(1196, 'ga', 'pt-br', 'Irlandês'),
(1197, 'ga', 'qu', 'Irish'),
(1198, 'ga', 'ro', 'Irlandeză'),
(1199, 'ga', 'ru', 'Ирландский'),
(1200, 'ga', 'sl', 'Irish'),
(1201, 'ga', 'so', 'Irish'),
(1202, 'ga', 'sq', 'Irish'),
(1203, 'ga', 'sr', 'Irish'),
(1204, 'ga', 'sv', 'Irländska'),
(1205, 'ga', 'ta', 'Irish'),
(1206, 'ga', 'th', 'ไอริช'),
(1207, 'ga', 'tr', 'İrlanda dili'),
(1208, 'ga', 'uk', 'Irish'),
(1209, 'ga', 'ur', 'Irish'),
(1210, 'ga', 'uz', 'Irish'),
(1211, 'ga', 'vi', 'Irish'),
(1212, 'ga', 'yi', 'Irish'),
(1213, 'ga', 'zh-hans', '爱尔兰语'),
(1214, 'ga', 'zu', 'Irish'),
(1215, 'ga', 'zh-hant', '愛爾蘭語'),
(1216, 'ga', 'ms', 'Irish'),
(1217, 'he', 'en', 'Hebrew'),
(1218, 'he', 'es', 'Hebreo'),
(1219, 'he', 'de', 'Hebräisch'),
(1220, 'he', 'fr', 'Hébreu'),
(1221, 'he', 'ar', 'العبرية'),
(1222, 'he', 'bs', 'Hebrew'),
(1223, 'he', 'bg', 'Hebrew'),
(1224, 'he', 'ca', 'Hebrew'),
(1225, 'he', 'cs', 'Hebrew'),
(1226, 'he', 'sk', 'Hebrejčina'),
(1227, 'he', 'cy', 'Hebrew'),
(1228, 'he', 'da', 'Hebrew'),
(1229, 'he', 'el', 'Εβραικα'),
(1230, 'he', 'eo', 'Hebrew'),
(1231, 'he', 'et', 'Hebrew'),
(1232, 'he', 'eu', 'Hebrew'),
(1233, 'he', 'fa', 'Hebrew'),
(1234, 'he', 'fi', 'heprea'),
(1235, 'he', 'ga', 'Hebrew'),
(1236, 'he', 'he', 'עברית'),
(1237, 'he', 'hi', 'Hebrew'),
(1238, 'he', 'hr', 'Hebrew'),
(1239, 'he', 'hu', 'héber'),
(1240, 'he', 'hy', 'Hebrew'),
(1241, 'he', 'id', 'Hebrew'),
(1242, 'he', 'is', 'Hebrew'),
(1243, 'he', 'it', 'Ebraico'),
(1244, 'he', 'ja', 'ヘブライ語'),
(1245, 'he', 'ko', '히브리어'),
(1246, 'he', 'ku', 'Hebrew'),
(1247, 'he', 'la', 'Hebrew'),
(1248, 'he', 'lv', 'Hebrew'),
(1249, 'he', 'lt', 'Hebrew'),
(1250, 'he', 'mk', 'Hebrew'),
(1251, 'he', 'mt', 'Hebrew'),
(1252, 'he', 'mo', 'Hebrew'),
(1253, 'he', 'mn', 'Hebrew'),
(1254, 'he', 'ne', 'Hebrew'),
(1255, 'he', 'nl', 'Hebreeuws'),
(1256, 'he', 'nb', 'Hebrew'),
(1257, 'he', 'pa', 'Hebrew'),
(1258, 'he', 'pl', 'hebrajski'),
(1259, 'he', 'pt-pt', 'Hebraico'),
(1260, 'he', 'pt-br', 'Hebraico'),
(1261, 'he', 'qu', 'Hebrew'),
(1262, 'he', 'ro', 'Ebraică'),
(1263, 'he', 'ru', 'Иврит'),
(1264, 'he', 'sl', 'Hebrew'),
(1265, 'he', 'so', 'Hebrew'),
(1266, 'he', 'sq', 'Hebrew'),
(1267, 'he', 'sr', 'Hebrew'),
(1268, 'he', 'sv', 'Hebreiska'),
(1269, 'he', 'ta', 'Hebrew'),
(1270, 'he', 'th', 'ฮิบรู'),
(1271, 'he', 'tr', 'İbranice'),
(1272, 'he', 'uk', 'Hebrew'),
(1273, 'he', 'ur', 'Hebrew'),
(1274, 'he', 'uz', 'Hebrew'),
(1275, 'he', 'vi', 'Hebrew'),
(1276, 'he', 'yi', 'Hebrew'),
(1277, 'he', 'zh-hans', '希伯来语'),
(1278, 'he', 'zu', 'Hebrew'),
(1279, 'he', 'zh-hant', '希伯來語'),
(1280, 'he', 'ms', 'Hebrew'),
(1281, 'hi', 'en', 'Hindi'),
(1282, 'hi', 'es', 'Hindi'),
(1283, 'hi', 'de', 'Hindi'),
(1284, 'hi', 'fr', 'Hindi'),
(1285, 'hi', 'ar', 'الهندية'),
(1286, 'hi', 'bs', 'Hindi'),
(1287, 'hi', 'bg', 'Hindi'),
(1288, 'hi', 'ca', 'Hindi'),
(1289, 'hi', 'cs', 'Hindi'),
(1290, 'hi', 'sk', 'Hindčina'),
(1291, 'hi', 'cy', 'Hindi'),
(1292, 'hi', 'da', 'Hindi'),
(1293, 'hi', 'el', 'Ινδικα'),
(1294, 'hi', 'eo', 'Hindi'),
(1295, 'hi', 'et', 'Hindi'),
(1296, 'hi', 'eu', 'Hindi'),
(1297, 'hi', 'fa', 'Hindi'),
(1298, 'hi', 'fi', 'hindi'),
(1299, 'hi', 'ga', 'Hindi'),
(1300, 'hi', 'he', 'הודית'),
(1301, 'hi', 'hi', 'हिन्दी'),
(1302, 'hi', 'hr', 'Hindi'),
(1303, 'hi', 'hu', 'hindi'),
(1304, 'hi', 'hy', 'Hindi'),
(1305, 'hi', 'id', 'Hindi'),
(1306, 'hi', 'is', 'Hindi'),
(1307, 'hi', 'it', 'Hindi'),
(1308, 'hi', 'ja', 'ヒンディー語'),
(1309, 'hi', 'ko', '힌두어'),
(1310, 'hi', 'ku', 'Hindi'),
(1311, 'hi', 'la', 'Hindi'),
(1312, 'hi', 'lv', 'Hindi'),
(1313, 'hi', 'lt', 'Hindi'),
(1314, 'hi', 'mk', 'Hindi'),
(1315, 'hi', 'mt', 'Hindi'),
(1316, 'hi', 'mo', 'Hindi'),
(1317, 'hi', 'mn', 'Hindi'),
(1318, 'hi', 'ne', 'Hindi'),
(1319, 'hi', 'nl', 'Hindi'),
(1320, 'hi', 'nb', 'Hindi'),
(1321, 'hi', 'pa', 'Hindi'),
(1322, 'hi', 'pl', 'hindi'),
(1323, 'hi', 'pt-pt', 'Hindi'),
(1324, 'hi', 'pt-br', 'Hindi'),
(1325, 'hi', 'qu', 'Hindi'),
(1326, 'hi', 'ro', 'Hindi'),
(1327, 'hi', 'ru', 'Хинди'),
(1328, 'hi', 'sl', 'Hindi'),
(1329, 'hi', 'so', 'Hindi'),
(1330, 'hi', 'sq', 'Hindi'),
(1331, 'hi', 'sr', 'Hindi'),
(1332, 'hi', 'sv', 'Hindi'),
(1333, 'hi', 'ta', 'Hindi'),
(1334, 'hi', 'th', 'ฮินดิ'),
(1335, 'hi', 'tr', 'Hintçe'),
(1336, 'hi', 'uk', 'Hindi'),
(1337, 'hi', 'ur', 'Hindi'),
(1338, 'hi', 'uz', 'Hindi'),
(1339, 'hi', 'vi', 'Hindi'),
(1340, 'hi', 'yi', 'Hindi'),
(1341, 'hi', 'zh-hans', '印地语'),
(1342, 'hi', 'zu', 'Hindi'),
(1343, 'hi', 'zh-hant', '印地語'),
(1344, 'hi', 'ms', 'Hindi'),
(1345, 'hr', 'en', 'Croatian'),
(1346, 'hr', 'es', 'Croata'),
(1347, 'hr', 'de', 'Kroatisch'),
(1348, 'hr', 'fr', 'Croate'),
(1349, 'hr', 'ar', 'الكرواتية'),
(1350, 'hr', 'bs', 'Croatian'),
(1351, 'hr', 'bg', 'Croatian'),
(1352, 'hr', 'ca', 'Croatian'),
(1353, 'hr', 'cs', 'Croatian'),
(1354, 'hr', 'sk', 'Chorvátština'),
(1355, 'hr', 'cy', 'Croatian'),
(1356, 'hr', 'da', 'Croatian'),
(1357, 'hr', 'el', 'Κροατικα'),
(1358, 'hr', 'eo', 'Croatian'),
(1359, 'hr', 'et', 'Croatian'),
(1360, 'hr', 'eu', 'Croatian'),
(1361, 'hr', 'fa', 'Croatian'),
(1362, 'hr', 'fi', 'kroatia'),
(1363, 'hr', 'ga', 'Croatian'),
(1364, 'hr', 'he', 'קרוטאית'),
(1365, 'hr', 'hi', 'Croatian'),
(1366, 'hr', 'hr', 'Hrvatski'),
(1367, 'hr', 'hu', 'horvát'),
(1368, 'hr', 'hy', 'Croatian'),
(1369, 'hr', 'id', 'Croatian'),
(1370, 'hr', 'is', 'Croatian'),
(1371, 'hr', 'it', 'Croato'),
(1372, 'hr', 'ja', 'クロアチア語'),
(1373, 'hr', 'ko', '크로아시아어'),
(1374, 'hr', 'ku', 'Croatian'),
(1375, 'hr', 'la', 'Croatian'),
(1376, 'hr', 'lv', 'Croatian'),
(1377, 'hr', 'lt', 'Croatian'),
(1378, 'hr', 'mk', 'Croatian'),
(1379, 'hr', 'mt', 'Croatian'),
(1380, 'hr', 'mo', 'Croatian'),
(1381, 'hr', 'mn', 'Croatian'),
(1382, 'hr', 'ne', 'Croatian'),
(1383, 'hr', 'nl', 'Kroatisch'),
(1384, 'hr', 'nb', 'Croatian'),
(1385, 'hr', 'pa', 'Croatian'),
(1386, 'hr', 'pl', 'chorwacki'),
(1387, 'hr', 'pt-pt', 'Croata'),
(1388, 'hr', 'pt-br', 'Croata'),
(1389, 'hr', 'qu', 'Croatian'),
(1390, 'hr', 'ro', 'Croată'),
(1391, 'hr', 'ru', 'Хорватский'),
(1392, 'hr', 'sl', 'Croatian'),
(1393, 'hr', 'so', 'Croatian'),
(1394, 'hr', 'sq', 'Croatian'),
(1395, 'hr', 'sr', 'Croatian'),
(1396, 'hr', 'sv', 'Kroatiska'),
(1397, 'hr', 'ta', 'Croatian'),
(1398, 'hr', 'th', 'โครเอเชีย'),
(1399, 'hr', 'tr', 'Hırvatça'),
(1400, 'hr', 'uk', 'Croatian'),
(1401, 'hr', 'ur', 'Croatian'),
(1402, 'hr', 'uz', 'Croatian'),
(1403, 'hr', 'vi', 'Croatian'),
(1404, 'hr', 'yi', 'Croatian'),
(1405, 'hr', 'zh-hans', '克罗地亚语'),
(1406, 'hr', 'zu', 'Croatian'),
(1407, 'hr', 'zh-hant', '克羅地亞語'),
(1408, 'hr', 'ms', 'Croatian'),
(1409, 'hu', 'en', 'Hungarian'),
(1410, 'hu', 'es', 'Húngaro'),
(1411, 'hu', 'de', 'Ungarisch'),
(1412, 'hu', 'fr', 'Hongrois'),
(1413, 'hu', 'ar', 'الهنغارية'),
(1414, 'hu', 'bs', 'Hungarian'),
(1415, 'hu', 'bg', 'Hungarian'),
(1416, 'hu', 'ca', 'Hungarian'),
(1417, 'hu', 'cs', 'Hungarian'),
(1418, 'hu', 'sk', 'Maďarčina'),
(1419, 'hu', 'cy', 'Hungarian'),
(1420, 'hu', 'da', 'Hungarian'),
(1421, 'hu', 'el', 'Ουγγρικα'),
(1422, 'hu', 'eo', 'Hungarian'),
(1423, 'hu', 'et', 'Hungarian'),
(1424, 'hu', 'eu', 'Hungarian'),
(1425, 'hu', 'fa', 'Hungarian'),
(1426, 'hu', 'fi', 'unkari'),
(1427, 'hu', 'ga', 'Hungarian'),
(1428, 'hu', 'he', 'הונגרית'),
(1429, 'hu', 'hi', 'Hungarian'),
(1430, 'hu', 'hr', 'Hungarian'),
(1431, 'hu', 'hu', 'Magyar'),
(1432, 'hu', 'hy', 'Hungarian'),
(1433, 'hu', 'id', 'Hungarian'),
(1434, 'hu', 'is', 'Hungarian'),
(1435, 'hu', 'it', 'Ungherese'),
(1436, 'hu', 'ja', 'ハンガリー語'),
(1437, 'hu', 'ko', '헝가리어'),
(1438, 'hu', 'ku', 'Hungarian'),
(1439, 'hu', 'la', 'Hungarian'),
(1440, 'hu', 'lv', 'Hungarian'),
(1441, 'hu', 'lt', 'Hungarian'),
(1442, 'hu', 'mk', 'Hungarian'),
(1443, 'hu', 'mt', 'Hungarian'),
(1444, 'hu', 'mo', 'Hungarian'),
(1445, 'hu', 'mn', 'Hungarian'),
(1446, 'hu', 'ne', 'Hungarian'),
(1447, 'hu', 'nl', 'Hongaars'),
(1448, 'hu', 'nb', 'Hungarian'),
(1449, 'hu', 'pa', 'Hungarian'),
(1450, 'hu', 'pl', 'węgierski'),
(1451, 'hu', 'pt-pt', 'Húngaro'),
(1452, 'hu', 'pt-br', 'Húngaro'),
(1453, 'hu', 'qu', 'Hungarian'),
(1454, 'hu', 'ro', 'Ungară'),
(1455, 'hu', 'ru', 'Венгерский'),
(1456, 'hu', 'sl', 'Hungarian'),
(1457, 'hu', 'so', 'Hungarian'),
(1458, 'hu', 'sq', 'Hungarian'),
(1459, 'hu', 'sr', 'Hungarian'),
(1460, 'hu', 'sv', 'Ungerska'),
(1461, 'hu', 'ta', 'Hungarian'),
(1462, 'hu', 'th', 'ฮังการี'),
(1463, 'hu', 'tr', 'Macarca'),
(1464, 'hu', 'uk', 'Hungarian'),
(1465, 'hu', 'ur', 'Hungarian'),
(1466, 'hu', 'uz', 'Hungarian'),
(1467, 'hu', 'vi', 'Hungarian'),
(1468, 'hu', 'yi', 'Hungarian'),
(1469, 'hu', 'zh-hans', '匈牙利语'),
(1470, 'hu', 'zu', 'Hungarian'),
(1471, 'hu', 'zh-hant', '匈牙利語'),
(1472, 'hu', 'ms', 'Hungarian'),
(1473, 'hy', 'en', 'Armenian'),
(1474, 'hy', 'es', 'Armenio'),
(1475, 'hy', 'de', 'Armenisch'),
(1476, 'hy', 'fr', 'Arménien'),
(1477, 'hy', 'ar', 'الأرمينية'),
(1478, 'hy', 'bs', 'Armenian'),
(1479, 'hy', 'bg', 'Armenian'),
(1480, 'hy', 'ca', 'Armenian'),
(1481, 'hy', 'cs', 'Armenian'),
(1482, 'hy', 'sk', 'Arménčina'),
(1483, 'hy', 'cy', 'Armenian'),
(1484, 'hy', 'da', 'Armenian'),
(1485, 'hy', 'el', 'Αρμενικα'),
(1486, 'hy', 'eo', 'Armenian'),
(1487, 'hy', 'et', 'Armenian'),
(1488, 'hy', 'eu', 'Armenian'),
(1489, 'hy', 'fa', 'Armenian'),
(1490, 'hy', 'fi', 'armenia'),
(1491, 'hy', 'ga', 'Armenian'),
(1492, 'hy', 'he', 'Armenian'),
(1493, 'hy', 'hi', 'Armenian'),
(1494, 'hy', 'hr', 'Armenian'),
(1495, 'hy', 'hu', 'örmény'),
(1496, 'hy', 'hy', 'Armenian'),
(1497, 'hy', 'id', 'Armenian'),
(1498, 'hy', 'is', 'Armenian'),
(1499, 'hy', 'it', 'Armeno'),
(1500, 'hy', 'ja', 'アルメニア語'),
(1501, 'hy', 'ko', '아르메니아어'),
(1502, 'hy', 'ku', 'Armenian'),
(1503, 'hy', 'la', 'Armenian'),
(1504, 'hy', 'lv', 'Armenian'),
(1505, 'hy', 'lt', 'Armenian'),
(1506, 'hy', 'mk', 'Armenian'),
(1507, 'hy', 'mt', 'Armenian'),
(1508, 'hy', 'mo', 'Armenian'),
(1509, 'hy', 'mn', 'Armenian'),
(1510, 'hy', 'ne', 'Armenian'),
(1511, 'hy', 'nl', 'Armeens'),
(1512, 'hy', 'nb', 'Armenian'),
(1513, 'hy', 'pa', 'Armenian'),
(1514, 'hy', 'pl', 'ormiański'),
(1515, 'hy', 'pt-pt', 'Arménio'),
(1516, 'hy', 'pt-br', 'Arménio'),
(1517, 'hy', 'qu', 'Armenian'),
(1518, 'hy', 'ro', 'Armeană'),
(1519, 'hy', 'ru', 'Армянский'),
(1520, 'hy', 'sl', 'Armenian'),
(1521, 'hy', 'so', 'Armenian'),
(1522, 'hy', 'sq', 'Armenian'),
(1523, 'hy', 'sr', 'Armenian'),
(1524, 'hy', 'sv', 'Armeniska'),
(1525, 'hy', 'ta', 'Armenian'),
(1526, 'hy', 'th', 'อาร์เมเนีย'),
(1527, 'hy', 'tr', 'Ermenice'),
(1528, 'hy', 'uk', 'Armenian'),
(1529, 'hy', 'ur', 'Armenian'),
(1530, 'hy', 'uz', 'Armenian'),
(1531, 'hy', 'vi', 'Armenian'),
(1532, 'hy', 'yi', 'Armenian'),
(1533, 'hy', 'zh-hans', '亚美尼亚语'),
(1534, 'hy', 'zu', 'Armenian'),
(1535, 'hy', 'zh-hant', '亞美尼亞語'),
(1536, 'hy', 'ms', 'Armenian'),
(1537, 'id', 'en', 'Indonesian'),
(1538, 'id', 'es', 'Indonesio'),
(1539, 'id', 'de', 'Indonesisch'),
(1540, 'id', 'fr', 'Indonésien'),
(1541, 'id', 'ar', 'الأندونيسية'),
(1542, 'id', 'bs', 'Indonesian'),
(1543, 'id', 'bg', 'Indonesian'),
(1544, 'id', 'ca', 'Indonesian'),
(1545, 'id', 'cs', 'Indonesian'),
(1546, 'id', 'sk', 'Indonézčina'),
(1547, 'id', 'cy', 'Indonesian'),
(1548, 'id', 'da', 'Indonesian'),
(1549, 'id', 'el', 'Ινδονησιακα'),
(1550, 'id', 'eo', 'Indonesian'),
(1551, 'id', 'et', 'Indonesian'),
(1552, 'id', 'eu', 'Indonesian'),
(1553, 'id', 'fa', 'Indonesian'),
(1554, 'id', 'fi', 'indonesia'),
(1555, 'id', 'ga', 'Indonesian'),
(1556, 'id', 'he', 'Indonesian'),
(1557, 'id', 'hi', 'Indonesian'),
(1558, 'id', 'hr', 'Indonesian'),
(1559, 'id', 'hu', 'indonéz'),
(1560, 'id', 'hy', 'Indonesian'),
(1561, 'id', 'id', 'Indonesia'),
(1562, 'id', 'is', 'Indonesian'),
(1563, 'id', 'it', 'Indonesiano'),
(1564, 'id', 'ja', 'インドネシア語'),
(1565, 'id', 'ko', '인도네시아어'),
(1566, 'id', 'ku', 'Indonesian'),
(1567, 'id', 'la', 'Indonesian'),
(1568, 'id', 'lv', 'Indonesian'),
(1569, 'id', 'lt', 'Indonesian'),
(1570, 'id', 'mk', 'Indonesian'),
(1571, 'id', 'mt', 'Indonesian'),
(1572, 'id', 'mo', 'Indonesian'),
(1573, 'id', 'mn', 'Indonesian'),
(1574, 'id', 'ne', 'Indonesian'),
(1575, 'id', 'nl', 'Indonesisch'),
(1576, 'id', 'nb', 'Indonesian'),
(1577, 'id', 'pa', 'Indonesian'),
(1578, 'id', 'pl', 'indonezyjski'),
(1579, 'id', 'pt-pt', 'Indonésio'),
(1580, 'id', 'pt-br', 'Indonésio'),
(1581, 'id', 'qu', 'Indonesian'),
(1582, 'id', 'ro', 'Indoneziană'),
(1583, 'id', 'ru', 'Индонезийский'),
(1584, 'id', 'sl', 'Indonesian'),
(1585, 'id', 'so', 'Indonesian'),
(1586, 'id', 'sq', 'Indonesian'),
(1587, 'id', 'sr', 'Indonesian'),
(1588, 'id', 'sv', 'Indonesiska'),
(1589, 'id', 'ta', 'Indonesian'),
(1590, 'id', 'th', 'อินโดนีเซีย'),
(1591, 'id', 'tr', 'Endonezya dili'),
(1592, 'id', 'uk', 'Indonesian'),
(1593, 'id', 'ur', 'Indonesian'),
(1594, 'id', 'uz', 'Indonesian'),
(1595, 'id', 'vi', 'Indonesian'),
(1596, 'id', 'yi', 'Indonesian'),
(1597, 'id', 'zh-hans', '印度尼西亚语'),
(1598, 'id', 'zu', 'Indonesian'),
(1599, 'id', 'zh-hant', '印尼語'),
(1600, 'id', 'ms', 'Indonesian'),
(1601, 'is', 'en', 'Icelandic'),
(1602, 'is', 'es', 'Islandés'),
(1603, 'is', 'de', 'Isländisch'),
(1604, 'is', 'fr', 'Islandais'),
(1605, 'is', 'ar', 'الأيسلاندية'),
(1606, 'is', 'bs', 'Icelandic'),
(1607, 'is', 'bg', 'Icelandic'),
(1608, 'is', 'ca', 'Icelandic'),
(1609, 'is', 'cs', 'Icelandic'),
(1610, 'is', 'sk', 'Islančina'),
(1611, 'is', 'cy', 'Icelandic'),
(1612, 'is', 'da', 'Icelandic'),
(1613, 'is', 'el', 'Ισλανδικα'),
(1614, 'is', 'eo', 'Icelandic'),
(1615, 'is', 'et', 'Icelandic'),
(1616, 'is', 'eu', 'Icelandic'),
(1617, 'is', 'fa', 'Icelandic'),
(1618, 'is', 'fi', 'islanti'),
(1619, 'is', 'ga', 'Icelandic'),
(1620, 'is', 'he', 'Icelandic'),
(1621, 'is', 'hi', 'Icelandic'),
(1622, 'is', 'hr', 'Icelandic'),
(1623, 'is', 'hu', 'izlandi'),
(1624, 'is', 'hy', 'Icelandic'),
(1625, 'is', 'id', 'Icelandic'),
(1626, 'is', 'is', 'Íslenska'),
(1627, 'is', 'it', 'Islandese'),
(1628, 'is', 'ja', 'アイスランド語'),
(1629, 'is', 'ko', '아이슬랜드어'),
(1630, 'is', 'ku', 'Icelandic'),
(1631, 'is', 'la', 'Icelandic'),
(1632, 'is', 'lv', 'Icelandic'),
(1633, 'is', 'lt', 'Icelandic'),
(1634, 'is', 'mk', 'Icelandic'),
(1635, 'is', 'mt', 'Icelandic'),
(1636, 'is', 'mo', 'Icelandic'),
(1637, 'is', 'mn', 'Icelandic'),
(1638, 'is', 'ne', 'Icelandic'),
(1639, 'is', 'nl', 'Ijslands'),
(1640, 'is', 'nb', 'Icelandic'),
(1641, 'is', 'pa', 'Icelandic'),
(1642, 'is', 'pl', 'islandzki'),
(1643, 'is', 'pt-pt', 'Islandês'),
(1644, 'is', 'pt-br', 'Islandês'),
(1645, 'is', 'qu', 'Icelandic'),
(1646, 'is', 'ro', 'Islandeză'),
(1647, 'is', 'ru', 'Исландский'),
(1648, 'is', 'sl', 'Icelandic'),
(1649, 'is', 'so', 'Icelandic'),
(1650, 'is', 'sq', 'Icelandic'),
(1651, 'is', 'sr', 'Icelandic'),
(1652, 'is', 'sv', 'Isländska'),
(1653, 'is', 'ta', 'Icelandic'),
(1654, 'is', 'th', 'ไอซ์แลนด์'),
(1655, 'is', 'tr', 'İzlandaca'),
(1656, 'is', 'uk', 'Icelandic'),
(1657, 'is', 'ur', 'Icelandic'),
(1658, 'is', 'uz', 'Icelandic'),
(1659, 'is', 'vi', 'Icelandic'),
(1660, 'is', 'yi', 'Icelandic'),
(1661, 'is', 'zh-hans', '冰岛语'),
(1662, 'is', 'zu', 'Icelandic'),
(1663, 'is', 'zh-hant', '冰島語'),
(1664, 'is', 'ms', 'Icelandic'),
(1665, 'it', 'en', 'Italian'),
(1666, 'it', 'es', 'Italiano'),
(1667, 'it', 'de', 'Italienisch'),
(1668, 'it', 'fr', 'Italien'),
(1669, 'it', 'ar', 'الإيطالية'),
(1670, 'it', 'bs', 'Italian'),
(1671, 'it', 'bg', 'Italian'),
(1672, 'it', 'ca', 'Italian'),
(1673, 'it', 'cs', 'Italian');
INSERT INTO `wp_icl_languages_translations` VALUES
(1674, 'it', 'sk', 'Taliančina'),
(1675, 'it', 'cy', 'Italian'),
(1676, 'it', 'da', 'Italian'),
(1677, 'it', 'el', 'Ιταλικα'),
(1678, 'it', 'eo', 'Italian'),
(1679, 'it', 'et', 'Italian'),
(1680, 'it', 'eu', 'Italian'),
(1681, 'it', 'fa', 'Italian'),
(1682, 'it', 'fi', 'italia'),
(1683, 'it', 'ga', 'Italian'),
(1684, 'it', 'he', 'איטלקית'),
(1685, 'it', 'hi', 'Italian'),
(1686, 'it', 'hr', 'Italian'),
(1687, 'it', 'hu', 'olasz'),
(1688, 'it', 'hy', 'Italian'),
(1689, 'it', 'id', 'Italian'),
(1690, 'it', 'is', 'Italian'),
(1691, 'it', 'it', 'Italiano'),
(1692, 'it', 'ja', 'イタリア語'),
(1693, 'it', 'ko', '이태리어'),
(1694, 'it', 'ku', 'Italian'),
(1695, 'it', 'la', 'Italian'),
(1696, 'it', 'lv', 'Italian'),
(1697, 'it', 'lt', 'Italian'),
(1698, 'it', 'mk', 'Italian'),
(1699, 'it', 'mt', 'Italian'),
(1700, 'it', 'mo', 'Italian'),
(1701, 'it', 'mn', 'Italian'),
(1702, 'it', 'ne', 'Italian'),
(1703, 'it', 'nl', 'Italiaans'),
(1704, 'it', 'nb', 'Italian'),
(1705, 'it', 'pa', 'Italian'),
(1706, 'it', 'pl', 'włoski'),
(1707, 'it', 'pt-pt', 'Italiano'),
(1708, 'it', 'pt-br', 'Italiano'),
(1709, 'it', 'qu', 'Italian'),
(1710, 'it', 'ro', 'Italiană'),
(1711, 'it', 'ru', 'Итальянский'),
(1712, 'it', 'sl', 'Italian'),
(1713, 'it', 'so', 'Italian'),
(1714, 'it', 'sq', 'Italian'),
(1715, 'it', 'sr', 'Italian'),
(1716, 'it', 'sv', 'Italienska'),
(1717, 'it', 'ta', 'Italian'),
(1718, 'it', 'th', 'อิตาลี'),
(1719, 'it', 'tr', 'İtalyanca'),
(1720, 'it', 'uk', 'Italian'),
(1721, 'it', 'ur', 'Italian'),
(1722, 'it', 'uz', 'Italian'),
(1723, 'it', 'vi', 'Italian'),
(1724, 'it', 'yi', 'Italian'),
(1725, 'it', 'zh-hans', '意大利语'),
(1726, 'it', 'zu', 'Italian'),
(1727, 'it', 'zh-hant', '義大利語'),
(1728, 'it', 'ms', 'Italian'),
(1729, 'ja', 'en', 'Japanese'),
(1730, 'ja', 'es', 'Japonés'),
(1731, 'ja', 'de', 'Japanisch'),
(1732, 'ja', 'fr', 'Japonais'),
(1733, 'ja', 'ar', 'اليابانية'),
(1734, 'ja', 'bs', 'Japanese'),
(1735, 'ja', 'bg', 'Japanese'),
(1736, 'ja', 'ca', 'Japanese'),
(1737, 'ja', 'cs', 'Japanese'),
(1738, 'ja', 'sk', 'Japonština'),
(1739, 'ja', 'cy', 'Japanese'),
(1740, 'ja', 'da', 'Japanese'),
(1741, 'ja', 'el', 'Ιαπωνικα'),
(1742, 'ja', 'eo', 'Japanese'),
(1743, 'ja', 'et', 'Japanese'),
(1744, 'ja', 'eu', 'Japanese'),
(1745, 'ja', 'fa', 'Japanese'),
(1746, 'ja', 'fi', 'japani'),
(1747, 'ja', 'ga', 'Japanese'),
(1748, 'ja', 'he', 'יפנית'),
(1749, 'ja', 'hi', 'Japanese'),
(1750, 'ja', 'hr', 'Japanese'),
(1751, 'ja', 'hu', 'japán'),
(1752, 'ja', 'hy', 'Japanese'),
(1753, 'ja', 'id', 'Japanese'),
(1754, 'ja', 'is', 'Japanese'),
(1755, 'ja', 'it', 'Giapponese'),
(1756, 'ja', 'ja', '日本語'),
(1757, 'ja', 'ko', '일어'),
(1758, 'ja', 'ku', 'Japanese'),
(1759, 'ja', 'la', 'Japanese'),
(1760, 'ja', 'lv', 'Japanese'),
(1761, 'ja', 'lt', 'Japanese'),
(1762, 'ja', 'mk', 'Japanese'),
(1763, 'ja', 'mt', 'Japanese'),
(1764, 'ja', 'mo', 'Japanese'),
(1765, 'ja', 'mn', 'Japanese'),
(1766, 'ja', 'ne', 'Japanese'),
(1767, 'ja', 'nl', 'Japans'),
(1768, 'ja', 'nb', 'Japanese'),
(1769, 'ja', 'pa', 'Japanese'),
(1770, 'ja', 'pl', 'japoński'),
(1771, 'ja', 'pt-pt', 'Japonês'),
(1772, 'ja', 'pt-br', 'Japonês'),
(1773, 'ja', 'qu', 'Japanese'),
(1774, 'ja', 'ro', 'Japoneză'),
(1775, 'ja', 'ru', 'Японский'),
(1776, 'ja', 'sl', 'Japanese'),
(1777, 'ja', 'so', 'Japanese'),
(1778, 'ja', 'sq', 'Japanese'),
(1779, 'ja', 'sr', 'Japanese'),
(1780, 'ja', 'sv', 'Japanska'),
(1781, 'ja', 'ta', 'Japanese'),
(1782, 'ja', 'th', 'ญี่ปุ่น'),
(1783, 'ja', 'tr', 'Japonca'),
(1784, 'ja', 'uk', 'Japanese'),
(1785, 'ja', 'ur', 'Japanese'),
(1786, 'ja', 'uz', 'Japanese'),
(1787, 'ja', 'vi', 'Japanese'),
(1788, 'ja', 'yi', 'Japanese'),
(1789, 'ja', 'zh-hans', '日语'),
(1790, 'ja', 'zu', 'Japanese'),
(1791, 'ja', 'zh-hant', '日語'),
(1792, 'ja', 'ms', 'Japanese'),
(1793, 'ko', 'en', 'Korean'),
(1794, 'ko', 'es', 'Coreano'),
(1795, 'ko', 'de', 'Koreanisch'),
(1796, 'ko', 'fr', 'Coréen'),
(1797, 'ko', 'ar', 'الكورية'),
(1798, 'ko', 'bs', 'Korean'),
(1799, 'ko', 'bg', 'Korean'),
(1800, 'ko', 'ca', 'Korean'),
(1801, 'ko', 'cs', 'Korean'),
(1802, 'ko', 'sk', 'Kórejčina'),
(1803, 'ko', 'cy', 'Korean'),
(1804, 'ko', 'da', 'Korean'),
(1805, 'ko', 'el', 'Κορεατικα'),
(1806, 'ko', 'eo', 'Korean'),
(1807, 'ko', 'et', 'Korean'),
(1808, 'ko', 'eu', 'Korean'),
(1809, 'ko', 'fa', 'Korean'),
(1810, 'ko', 'fi', 'korea'),
(1811, 'ko', 'ga', 'Korean'),
(1812, 'ko', 'he', 'קוראנית'),
(1813, 'ko', 'hi', 'Korean'),
(1814, 'ko', 'hr', 'Korean'),
(1815, 'ko', 'hu', 'koreai'),
(1816, 'ko', 'hy', 'Korean'),
(1817, 'ko', 'id', 'Korean'),
(1818, 'ko', 'is', 'Korean'),
(1819, 'ko', 'it', 'Coreano'),
(1820, 'ko', 'ja', '韓国語'),
(1821, 'ko', 'ko', '한국어'),
(1822, 'ko', 'ku', 'Korean'),
(1823, 'ko', 'la', 'Korean'),
(1824, 'ko', 'lv', 'Korean'),
(1825, 'ko', 'lt', 'Korean'),
(1826, 'ko', 'mk', 'Korean'),
(1827, 'ko', 'mt', 'Korean'),
(1828, 'ko', 'mo', 'Korean'),
(1829, 'ko', 'mn', 'Korean'),
(1830, 'ko', 'ne', 'Korean'),
(1831, 'ko', 'nl', 'Koreaans'),
(1832, 'ko', 'nb', 'Korean'),
(1833, 'ko', 'pa', 'Korean'),
(1834, 'ko', 'pl', 'koreański'),
(1835, 'ko', 'pt-pt', 'Korean'),
(1836, 'ko', 'pt-br', 'Korean'),
(1837, 'ko', 'qu', 'Korean'),
(1838, 'ko', 'ro', 'Coreană'),
(1839, 'ko', 'ru', 'Корейский'),
(1840, 'ko', 'sl', 'Korean'),
(1841, 'ko', 'so', 'Korean'),
(1842, 'ko', 'sq', 'Korean'),
(1843, 'ko', 'sr', 'Korean'),
(1844, 'ko', 'sv', 'Koreanska'),
(1845, 'ko', 'ta', 'Korean'),
(1846, 'ko', 'th', 'เกาหลี'),
(1847, 'ko', 'tr', 'Kore dili'),
(1848, 'ko', 'uk', 'Korean'),
(1849, 'ko', 'ur', 'Korean'),
(1850, 'ko', 'uz', 'Korean'),
(1851, 'ko', 'vi', 'Korean'),
(1852, 'ko', 'yi', 'Korean'),
(1853, 'ko', 'zh-hans', '韩语'),
(1854, 'ko', 'zu', 'Korean'),
(1855, 'ko', 'zh-hant', '韓語'),
(1856, 'ko', 'ms', 'Korean'),
(1857, 'ku', 'en', 'Kurdish'),
(1858, 'ku', 'es', 'Kurdo'),
(1859, 'ku', 'de', 'Kurdisch'),
(1860, 'ku', 'fr', 'Kurde'),
(1861, 'ku', 'ar', 'الكردية'),
(1862, 'ku', 'bs', 'Kurdish'),
(1863, 'ku', 'bg', 'Kurdish'),
(1864, 'ku', 'ca', 'Kurdish'),
(1865, 'ku', 'cs', 'Kurdish'),
(1866, 'ku', 'sk', 'Kurdština'),
(1867, 'ku', 'cy', 'Kurdish'),
(1868, 'ku', 'da', 'Kurdish'),
(1869, 'ku', 'el', 'Κουρδικα'),
(1870, 'ku', 'eo', 'Kurdish'),
(1871, 'ku', 'et', 'Kurdish'),
(1872, 'ku', 'eu', 'Kurdish'),
(1873, 'ku', 'fa', 'Kurdish'),
(1874, 'ku', 'fi', 'kurdi'),
(1875, 'ku', 'ga', 'Kurdish'),
(1876, 'ku', 'he', 'Kurdish'),
(1877, 'ku', 'hi', 'Kurdish'),
(1878, 'ku', 'hr', 'Kurdish'),
(1879, 'ku', 'hu', 'kurd'),
(1880, 'ku', 'hy', 'Kurdish'),
(1881, 'ku', 'id', 'Kurdish'),
(1882, 'ku', 'is', 'Kurdish'),
(1883, 'ku', 'it', 'Curdo'),
(1884, 'ku', 'ja', 'クルド語'),
(1885, 'ku', 'ko', '쿠르드어'),
(1886, 'ku', 'ku', 'Kurdish'),
(1887, 'ku', 'la', 'Kurdish'),
(1888, 'ku', 'lv', 'Kurdish'),
(1889, 'ku', 'lt', 'Kurdish'),
(1890, 'ku', 'mk', 'Kurdish'),
(1891, 'ku', 'mt', 'Kurdish'),
(1892, 'ku', 'mo', 'Kurdish'),
(1893, 'ku', 'mn', 'Kurdish'),
(1894, 'ku', 'ne', 'Kurdish'),
(1895, 'ku', 'nl', 'Koerdish'),
(1896, 'ku', 'nb', 'Kurdish'),
(1897, 'ku', 'pa', 'Kurdish'),
(1898, 'ku', 'pl', 'kurdyjski'),
(1899, 'ku', 'pt-pt', 'Curdo'),
(1900, 'ku', 'pt-br', 'Curdo'),
(1901, 'ku', 'qu', 'Kurdish'),
(1902, 'ku', 'ro', 'Kurdă'),
(1903, 'ku', 'ru', 'Курдский'),
(1904, 'ku', 'sl', 'Kurdish'),
(1905, 'ku', 'so', 'Kurdish'),
(1906, 'ku', 'sq', 'Kurdish'),
(1907, 'ku', 'sr', 'Kurdish'),
(1908, 'ku', 'sv', 'Kurdiska'),
(1909, 'ku', 'ta', 'Kurdish'),
(1910, 'ku', 'th', 'เคอร์ดิช'),
(1911, 'ku', 'tr', 'Kürtçe'),
(1912, 'ku', 'uk', 'Kurdish'),
(1913, 'ku', 'ur', 'Kurdish'),
(1914, 'ku', 'uz', 'Kurdish'),
(1915, 'ku', 'vi', 'Kurdish'),
(1916, 'ku', 'yi', 'Kurdish'),
(1917, 'ku', 'zh-hans', '库尔德语'),
(1918, 'ku', 'zu', 'Kurdish'),
(1919, 'ku', 'zh-hant', '庫爾德語'),
(1920, 'ku', 'ms', 'Kurdish'),
(1921, 'la', 'en', 'Latin'),
(1922, 'la', 'es', 'Latín'),
(1923, 'la', 'de', 'Latein'),
(1924, 'la', 'fr', 'Latin'),
(1925, 'la', 'ar', 'اللاتينية'),
(1926, 'la', 'bs', 'Latin'),
(1927, 'la', 'bg', 'Latin'),
(1928, 'la', 'ca', 'Latin'),
(1929, 'la', 'cs', 'Latin'),
(1930, 'la', 'sk', 'Latinčina'),
(1931, 'la', 'cy', 'Latin'),
(1932, 'la', 'da', 'Latin'),
(1933, 'la', 'el', 'Λατινικη'),
(1934, 'la', 'eo', 'Latin'),
(1935, 'la', 'et', 'Latin'),
(1936, 'la', 'eu', 'Latin'),
(1937, 'la', 'fa', 'Latin'),
(1938, 'la', 'fi', 'latina'),
(1939, 'la', 'ga', 'Latin'),
(1940, 'la', 'he', 'לטינית'),
(1941, 'la', 'hi', 'Latin'),
(1942, 'la', 'hr', 'Latin'),
(1943, 'la', 'hu', 'latin'),
(1944, 'la', 'hy', 'Latin'),
(1945, 'la', 'id', 'Latin'),
(1946, 'la', 'is', 'Latin'),
(1947, 'la', 'it', 'Latino'),
(1948, 'la', 'ja', 'ラテン語'),
(1949, 'la', 'ko', '라틴어'),
(1950, 'la', 'ku', 'Latin'),
(1951, 'la', 'la', 'Latin'),
(1952, 'la', 'lv', 'Latin'),
(1953, 'la', 'lt', 'Latin'),
(1954, 'la', 'mk', 'Latin'),
(1955, 'la', 'mt', 'Latin'),
(1956, 'la', 'mo', 'Latin'),
(1957, 'la', 'mn', 'Latin'),
(1958, 'la', 'ne', 'Latin'),
(1959, 'la', 'nl', 'Latijn'),
(1960, 'la', 'nb', 'Latin'),
(1961, 'la', 'pa', 'Latin'),
(1962, 'la', 'pl', 'łaciński'),
(1963, 'la', 'pt-pt', 'Latina'),
(1964, 'la', 'pt-br', 'Latina'),
(1965, 'la', 'qu', 'Latin'),
(1966, 'la', 'ro', 'Latină'),
(1967, 'la', 'ru', 'Латинский'),
(1968, 'la', 'sl', 'Latin'),
(1969, 'la', 'so', 'Latin'),
(1970, 'la', 'sq', 'Latin'),
(1971, 'la', 'sr', 'Latin'),
(1972, 'la', 'sv', 'Latin'),
(1973, 'la', 'ta', 'Latin'),
(1974, 'la', 'th', 'ละติน'),
(1975, 'la', 'tr', 'Latince'),
(1976, 'la', 'uk', 'Latin'),
(1977, 'la', 'ur', 'Latin'),
(1978, 'la', 'uz', 'Latin'),
(1979, 'la', 'vi', 'Latin'),
(1980, 'la', 'yi', 'Latin'),
(1981, 'la', 'zh-hans', '拉丁语'),
(1982, 'la', 'zu', 'Latin'),
(1983, 'la', 'zh-hant', '拉丁語'),
(1984, 'la', 'ms', 'Latin'),
(1985, 'lv', 'en', 'Latvian'),
(1986, 'lv', 'es', 'Letón'),
(1987, 'lv', 'de', 'Lettisch'),
(1988, 'lv', 'fr', 'Letton'),
(1989, 'lv', 'ar', 'اللاتفية'),
(1990, 'lv', 'bs', 'Latvian'),
(1991, 'lv', 'bg', 'Latvian'),
(1992, 'lv', 'ca', 'Latvian'),
(1993, 'lv', 'cs', 'Latvian'),
(1994, 'lv', 'sk', 'Lotyština'),
(1995, 'lv', 'cy', 'Latvian'),
(1996, 'lv', 'da', 'Latvian'),
(1997, 'lv', 'el', 'Λετονικα'),
(1998, 'lv', 'eo', 'Latvian'),
(1999, 'lv', 'et', 'Latvian'),
(2000, 'lv', 'eu', 'Latvian'),
(2001, 'lv', 'fa', 'Latvian'),
(2002, 'lv', 'fi', 'latvia'),
(2003, 'lv', 'ga', 'Latvian'),
(2004, 'lv', 'he', 'Latvian'),
(2005, 'lv', 'hi', 'Latvian'),
(2006, 'lv', 'hr', 'Latvian'),
(2007, 'lv', 'hu', 'lett'),
(2008, 'lv', 'hy', 'Latvian'),
(2009, 'lv', 'id', 'Latvian'),
(2010, 'lv', 'is', 'Latvian'),
(2011, 'lv', 'it', 'Lettone'),
(2012, 'lv', 'ja', 'ラトビア語'),
(2013, 'lv', 'ko', '라트비아어'),
(2014, 'lv', 'ku', 'Latvian'),
(2015, 'lv', 'la', 'Latvian'),
(2016, 'lv', 'lv', 'Latviešu'),
(2017, 'lv', 'lt', 'Latvian'),
(2018, 'lv', 'mk', 'Latvian'),
(2019, 'lv', 'mt', 'Latvian'),
(2020, 'lv', 'mo', 'Latvian'),
(2021, 'lv', 'mn', 'Latvian'),
(2022, 'lv', 'ne', 'Latvian'),
(2023, 'lv', 'nl', 'Lets'),
(2024, 'lv', 'nb', 'Latvian'),
(2025, 'lv', 'pa', 'Latvian'),
(2026, 'lv', 'pl', 'łotewski'),
(2027, 'lv', 'pt-pt', 'Letão'),
(2028, 'lv', 'pt-br', 'Letão'),
(2029, 'lv', 'qu', 'Latvian'),
(2030, 'lv', 'ro', 'Letoniană'),
(2031, 'lv', 'ru', 'латышский'),
(2032, 'lv', 'sl', 'Latvian'),
(2033, 'lv', 'so', 'Latvian'),
(2034, 'lv', 'sq', 'Latvian'),
(2035, 'lv', 'sr', 'Latvian'),
(2036, 'lv', 'sv', 'Lettiska'),
(2037, 'lv', 'ta', 'Latvian'),
(2038, 'lv', 'th', 'ลัตเวีย'),
(2039, 'lv', 'tr', 'Letonca'),
(2040, 'lv', 'uk', 'Latvian'),
(2041, 'lv', 'ur', 'Latvian'),
(2042, 'lv', 'uz', 'Latvian'),
(2043, 'lv', 'vi', 'Latvian'),
(2044, 'lv', 'yi', 'Latvian'),
(2045, 'lv', 'zh-hans', '拉脱维亚语'),
(2046, 'lv', 'zu', 'Latvian'),
(2047, 'lv', 'zh-hant', '拉脫維亞語'),
(2048, 'lv', 'ms', 'Latvian'),
(2049, 'lt', 'en', 'Lithuanian'),
(2050, 'lt', 'es', 'Lituano'),
(2051, 'lt', 'de', 'Litauisch'),
(2052, 'lt', 'fr', 'Lituanien'),
(2053, 'lt', 'ar', 'اللتوانية'),
(2054, 'lt', 'bs', 'Lithuanian'),
(2055, 'lt', 'bg', 'Lithuanian'),
(2056, 'lt', 'ca', 'Lithuanian'),
(2057, 'lt', 'cs', 'Lithuanian'),
(2058, 'lt', 'sk', 'Litovčina'),
(2059, 'lt', 'cy', 'Lithuanian'),
(2060, 'lt', 'da', 'Lithuanian'),
(2061, 'lt', 'el', 'Λιθουανικα'),
(2062, 'lt', 'eo', 'Lithuanian'),
(2063, 'lt', 'et', 'Lithuanian'),
(2064, 'lt', 'eu', 'Lithuanian'),
(2065, 'lt', 'fa', 'Lithuanian'),
(2066, 'lt', 'fi', 'liettua'),
(2067, 'lt', 'ga', 'Lithuanian'),
(2068, 'lt', 'he', 'Lithuanian'),
(2069, 'lt', 'hi', 'Lithuanian'),
(2070, 'lt', 'hr', 'Lithuanian'),
(2071, 'lt', 'hu', 'litván'),
(2072, 'lt', 'hy', 'Lithuanian'),
(2073, 'lt', 'id', 'Lithuanian'),
(2074, 'lt', 'is', 'Lithuanian'),
(2075, 'lt', 'it', 'Lituano'),
(2076, 'lt', 'ja', 'リトアニア語'),
(2077, 'lt', 'ko', '리투아니아어'),
(2078, 'lt', 'ku', 'Lithuanian'),
(2079, 'lt', 'la', 'Lithuanian'),
(2080, 'lt', 'lv', 'Lithuanian'),
(2081, 'lt', 'lt', 'Lithuanian'),
(2082, 'lt', 'mk', 'Lithuanian'),
(2083, 'lt', 'mt', 'Lithuanian'),
(2084, 'lt', 'mo', 'Lithuanian'),
(2085, 'lt', 'mn', 'Lithuanian'),
(2086, 'lt', 'ne', 'Lithuanian'),
(2087, 'lt', 'nl', 'Litouws'),
(2088, 'lt', 'nb', 'Lithuanian'),
(2089, 'lt', 'pa', 'Lithuanian'),
(2090, 'lt', 'pl', 'litewski'),
(2091, 'lt', 'pt-pt', 'Lituano'),
(2092, 'lt', 'pt-br', 'Lituano'),
(2093, 'lt', 'qu', 'Lithuanian'),
(2094, 'lt', 'ro', 'Lituaniană'),
(2095, 'lt', 'ru', 'Литовский'),
(2096, 'lt', 'sl', 'Lithuanian'),
(2097, 'lt', 'so', 'Lithuanian'),
(2098, 'lt', 'sq', 'Lithuanian'),
(2099, 'lt', 'sr', 'Lithuanian'),
(2100, 'lt', 'sv', 'Litauiska'),
(2101, 'lt', 'ta', 'Lithuanian'),
(2102, 'lt', 'th', 'ลิธัวเนีย'),
(2103, 'lt', 'tr', 'Litvanyaca'),
(2104, 'lt', 'uk', 'Lithuanian'),
(2105, 'lt', 'ur', 'Lithuanian'),
(2106, 'lt', 'uz', 'Lithuanian'),
(2107, 'lt', 'vi', 'Lithuanian'),
(2108, 'lt', 'yi', 'Lithuanian'),
(2109, 'lt', 'zh-hans', '立陶宛语'),
(2110, 'lt', 'zu', 'Lithuanian'),
(2111, 'lt', 'zh-hant', '立陶宛語'),
(2112, 'lt', 'ms', 'Lithuanian'),
(2113, 'mk', 'en', 'Macedonian'),
(2114, 'mk', 'es', 'Macedonio'),
(2115, 'mk', 'de', 'Mazedonisch'),
(2116, 'mk', 'fr', 'Macédonien'),
(2117, 'mk', 'ar', 'المقدونية'),
(2118, 'mk', 'bs', 'Macedonian'),
(2119, 'mk', 'bg', 'Macedonian'),
(2120, 'mk', 'ca', 'Macedonian'),
(2121, 'mk', 'cs', 'Macedonian'),
(2122, 'mk', 'sk', 'Macedónština'),
(2123, 'mk', 'cy', 'Macedonian'),
(2124, 'mk', 'da', 'Macedonian'),
(2125, 'mk', 'el', 'Μακεδονικο'),
(2126, 'mk', 'eo', 'Macedonian'),
(2127, 'mk', 'et', 'Macedonian'),
(2128, 'mk', 'eu', 'Macedonian'),
(2129, 'mk', 'fa', 'Macedonian'),
(2130, 'mk', 'fi', 'makedonia'),
(2131, 'mk', 'ga', 'Macedonian'),
(2132, 'mk', 'he', 'Macedonian'),
(2133, 'mk', 'hi', 'Macedonian'),
(2134, 'mk', 'hr', 'Macedonian'),
(2135, 'mk', 'hu', 'macedón'),
(2136, 'mk', 'hy', 'Macedonian'),
(2137, 'mk', 'id', 'Macedonian'),
(2138, 'mk', 'is', 'Macedonian'),
(2139, 'mk', 'it', 'Macedone'),
(2140, 'mk', 'ja', 'マケドニア語'),
(2141, 'mk', 'ko', '마케도니아어'),
(2142, 'mk', 'ku', 'Macedonian'),
(2143, 'mk', 'la', 'Macedonian'),
(2144, 'mk', 'lv', 'Macedonian'),
(2145, 'mk', 'lt', 'Macedonian'),
(2146, 'mk', 'mk', 'Macedonian'),
(2147, 'mk', 'mt', 'Macedonian'),
(2148, 'mk', 'mo', 'Macedonian'),
(2149, 'mk', 'mn', 'Macedonian'),
(2150, 'mk', 'ne', 'Macedonian'),
(2151, 'mk', 'nl', 'Macedonisch'),
(2152, 'mk', 'nb', 'Macedonian'),
(2153, 'mk', 'pa', 'Macedonian'),
(2154, 'mk', 'pl', 'macedoński'),
(2155, 'mk', 'pt-pt', 'Macedônio'),
(2156, 'mk', 'pt-br', 'Macedônio'),
(2157, 'mk', 'qu', 'Macedonian'),
(2158, 'mk', 'ro', 'Macedoniană'),
(2159, 'mk', 'ru', 'Македонский'),
(2160, 'mk', 'sl', 'Macedonian'),
(2161, 'mk', 'so', 'Macedonian'),
(2162, 'mk', 'sq', 'Macedonian'),
(2163, 'mk', 'sr', 'Macedonian'),
(2164, 'mk', 'sv', 'Makedonska'),
(2165, 'mk', 'ta', 'Macedonian'),
(2166, 'mk', 'th', 'มาซิโดเนีย'),
(2167, 'mk', 'tr', 'Makedonyaca'),
(2168, 'mk', 'uk', 'Macedonian'),
(2169, 'mk', 'ur', 'Macedonian'),
(2170, 'mk', 'uz', 'Macedonian'),
(2171, 'mk', 'vi', 'Macedonian'),
(2172, 'mk', 'yi', 'Macedonian'),
(2173, 'mk', 'zh-hans', '马其顿语'),
(2174, 'mk', 'zu', 'Macedonian'),
(2175, 'mk', 'zh-hant', '馬其頓語'),
(2176, 'mk', 'ms', 'Macedonian'),
(2177, 'mt', 'en', 'Maltese'),
(2178, 'mt', 'es', 'Maltés'),
(2179, 'mt', 'de', 'Maltesisch'),
(2180, 'mt', 'fr', 'Maltais'),
(2181, 'mt', 'ar', 'المالطية'),
(2182, 'mt', 'bs', 'Maltese'),
(2183, 'mt', 'bg', 'Maltese'),
(2184, 'mt', 'ca', 'Maltese'),
(2185, 'mt', 'cs', 'Maltese'),
(2186, 'mt', 'sk', 'Maltézština'),
(2187, 'mt', 'cy', 'Maltese'),
(2188, 'mt', 'da', 'Maltese'),
(2189, 'mt', 'el', 'Μαλτεζικα'),
(2190, 'mt', 'eo', 'Maltese'),
(2191, 'mt', 'et', 'Maltese'),
(2192, 'mt', 'eu', 'Maltese'),
(2193, 'mt', 'fa', 'Maltese'),
(2194, 'mt', 'fi', 'malta'),
(2195, 'mt', 'ga', 'Maltese'),
(2196, 'mt', 'he', 'Maltese'),
(2197, 'mt', 'hi', 'Maltese'),
(2198, 'mt', 'hr', 'Maltese'),
(2199, 'mt', 'hu', 'máltai'),
(2200, 'mt', 'hy', 'Maltese'),
(2201, 'mt', 'id', 'Maltese'),
(2202, 'mt', 'is', 'Maltese'),
(2203, 'mt', 'it', 'Maltese'),
(2204, 'mt', 'ja', 'マルタ語'),
(2205, 'mt', 'ko', '몰타어'),
(2206, 'mt', 'ku', 'Maltese'),
(2207, 'mt', 'la', 'Maltese'),
(2208, 'mt', 'lv', 'Maltese'),
(2209, 'mt', 'lt', 'Maltese'),
(2210, 'mt', 'mk', 'Maltese'),
(2211, 'mt', 'mt', 'Maltese'),
(2212, 'mt', 'mo', 'Maltese'),
(2213, 'mt', 'mn', 'Maltese'),
(2214, 'mt', 'ne', 'Maltese'),
(2215, 'mt', 'nl', 'Maltees'),
(2216, 'mt', 'nb', 'Maltese'),
(2217, 'mt', 'pa', 'Maltese'),
(2218, 'mt', 'pl', 'maltański'),
(2219, 'mt', 'pt-pt', 'Maltês'),
(2220, 'mt', 'pt-br', 'Maltês'),
(2221, 'mt', 'qu', 'Maltese'),
(2222, 'mt', 'ro', 'Malteză'),
(2223, 'mt', 'ru', 'Мальтийский'),
(2224, 'mt', 'sl', 'Maltese'),
(2225, 'mt', 'so', 'Maltese'),
(2226, 'mt', 'sq', 'Maltese'),
(2227, 'mt', 'sr', 'Maltese'),
(2228, 'mt', 'sv', 'Maltesiska'),
(2229, 'mt', 'ta', 'Maltese'),
(2230, 'mt', 'th', 'มอลทีส'),
(2231, 'mt', 'tr', 'Malta dili'),
(2232, 'mt', 'uk', 'Maltese'),
(2233, 'mt', 'ur', 'Maltese'),
(2234, 'mt', 'uz', 'Maltese'),
(2235, 'mt', 'vi', 'Maltese'),
(2236, 'mt', 'yi', 'Maltese'),
(2237, 'mt', 'zh-hans', '马耳他语'),
(2238, 'mt', 'zu', 'Maltese'),
(2239, 'mt', 'zh-hant', '馬爾他語'),
(2240, 'mt', 'ms', 'Maltese'),
(2241, 'mo', 'en', 'Moldavian'),
(2242, 'mo', 'es', 'Moldavo'),
(2243, 'mo', 'de', 'Moldavisch'),
(2244, 'mo', 'fr', 'Moldave'),
(2245, 'mo', 'ar', 'المولدوفية'),
(2246, 'mo', 'bs', 'Moldavian'),
(2247, 'mo', 'bg', 'Moldavian'),
(2248, 'mo', 'ca', 'Moldavian'),
(2249, 'mo', 'cs', 'Moldavian'),
(2250, 'mo', 'sk', 'Moldavčina'),
(2251, 'mo', 'cy', 'Moldavian'),
(2252, 'mo', 'da', 'Moldavian'),
(2253, 'mo', 'el', 'Μολδαβικα'),
(2254, 'mo', 'eo', 'Moldavian'),
(2255, 'mo', 'et', 'Moldavian'),
(2256, 'mo', 'eu', 'Moldavian'),
(2257, 'mo', 'fa', 'Moldavian'),
(2258, 'mo', 'fi', 'moldavia'),
(2259, 'mo', 'ga', 'Moldavian'),
(2260, 'mo', 'he', 'Moldavian'),
(2261, 'mo', 'hi', 'Moldavian'),
(2262, 'mo', 'hr', 'Moldavian'),
(2263, 'mo', 'hu', 'moldovai'),
(2264, 'mo', 'hy', 'Moldavian'),
(2265, 'mo', 'id', 'Moldavian'),
(2266, 'mo', 'is', 'Moldavian'),
(2267, 'mo', 'it', 'Moldavo'),
(2268, 'mo', 'ja', 'モルダビア語'),
(2269, 'mo', 'ko', '몰다비아어'),
(2270, 'mo', 'ku', 'Moldavian'),
(2271, 'mo', 'la', 'Moldavian'),
(2272, 'mo', 'lv', 'Moldavian'),
(2273, 'mo', 'lt', 'Moldavian'),
(2274, 'mo', 'mk', 'Moldavian'),
(2275, 'mo', 'mt', 'Moldavian'),
(2276, 'mo', 'mo', 'Moldavian'),
(2277, 'mo', 'mn', 'Moldavian'),
(2278, 'mo', 'ne', 'Moldavian'),
(2279, 'mo', 'nl', 'Moldavisch'),
(2280, 'mo', 'nb', 'Moldavian'),
(2281, 'mo', 'pa', 'Moldavian'),
(2282, 'mo', 'pl', 'mołdawski'),
(2283, 'mo', 'pt-pt', 'Moldavo'),
(2284, 'mo', 'pt-br', 'Moldavo'),
(2285, 'mo', 'qu', 'Moldavian'),
(2286, 'mo', 'ro', 'Moldoveană'),
(2287, 'mo', 'ru', 'Молдавский'),
(2288, 'mo', 'sl', 'Moldavian'),
(2289, 'mo', 'so', 'Moldavian'),
(2290, 'mo', 'sq', 'Moldavian'),
(2291, 'mo', 'sr', 'Moldavian'),
(2292, 'mo', 'sv', 'Moldaviska'),
(2293, 'mo', 'ta', 'Moldavian'),
(2294, 'mo', 'th', 'มอลดาเวียน'),
(2295, 'mo', 'tr', 'Moldovyaca'),
(2296, 'mo', 'uk', 'Moldavian'),
(2297, 'mo', 'ur', 'Moldavian'),
(2298, 'mo', 'uz', 'Moldavian'),
(2299, 'mo', 'vi', 'Moldavian'),
(2300, 'mo', 'yi', 'Moldavian'),
(2301, 'mo', 'zh-hans', '摩尔达维亚语'),
(2302, 'mo', 'zu', 'Moldavian'),
(2303, 'mo', 'zh-hant', '摩爾達維亞語'),
(2304, 'mo', 'ms', 'Moldavian'),
(2305, 'mn', 'en', 'Mongolian'),
(2306, 'mn', 'es', 'Mongol'),
(2307, 'mn', 'de', 'Mongolisch'),
(2308, 'mn', 'fr', 'Mongol'),
(2309, 'mn', 'ar', 'المنغولية'),
(2310, 'mn', 'bs', 'Mongolian'),
(2311, 'mn', 'bg', 'Mongolian'),
(2312, 'mn', 'ca', 'Mongolian'),
(2313, 'mn', 'cs', 'Mongolian'),
(2314, 'mn', 'sk', 'Mongolština'),
(2315, 'mn', 'cy', 'Mongolian'),
(2316, 'mn', 'da', 'Mongolian'),
(2317, 'mn', 'el', 'Μογγολικα'),
(2318, 'mn', 'eo', 'Mongolian'),
(2319, 'mn', 'et', 'Mongolian'),
(2320, 'mn', 'eu', 'Mongolian'),
(2321, 'mn', 'fa', 'Mongolian'),
(2322, 'mn', 'fi', 'mongoli'),
(2323, 'mn', 'ga', 'Mongolian'),
(2324, 'mn', 'he', 'Mongolian'),
(2325, 'mn', 'hi', 'Mongolian'),
(2326, 'mn', 'hr', 'Mongolian'),
(2327, 'mn', 'hu', 'mongol'),
(2328, 'mn', 'hy', 'Mongolian'),
(2329, 'mn', 'id', 'Mongolian'),
(2330, 'mn', 'is', 'Mongolian'),
(2331, 'mn', 'it', 'Mongolo'),
(2332, 'mn', 'ja', 'モンゴル語'),
(2333, 'mn', 'ko', '몽골어'),
(2334, 'mn', 'ku', 'Mongolian'),
(2335, 'mn', 'la', 'Mongolian'),
(2336, 'mn', 'lv', 'Mongolian'),
(2337, 'mn', 'lt', 'Mongolian'),
(2338, 'mn', 'mk', 'Mongolian'),
(2339, 'mn', 'mt', 'Mongolian'),
(2340, 'mn', 'mo', 'Mongolian'),
(2341, 'mn', 'mn', 'Mongolian'),
(2342, 'mn', 'ne', 'Mongolian'),
(2343, 'mn', 'nl', 'Mongools'),
(2344, 'mn', 'nb', 'Mongolian'),
(2345, 'mn', 'pa', 'Mongolian'),
(2346, 'mn', 'pl', 'mongolski'),
(2347, 'mn', 'pt-pt', 'Mongolian'),
(2348, 'mn', 'pt-br', 'Mongolian'),
(2349, 'mn', 'qu', 'Mongolian'),
(2350, 'mn', 'ro', 'Mongoleză'),
(2351, 'mn', 'ru', 'Монгольский'),
(2352, 'mn', 'sl', 'Mongolian'),
(2353, 'mn', 'so', 'Mongolian'),
(2354, 'mn', 'sq', 'Mongolian'),
(2355, 'mn', 'sr', 'Mongolian'),
(2356, 'mn', 'sv', 'Mongoliska'),
(2357, 'mn', 'ta', 'Mongolian'),
(2358, 'mn', 'th', 'มองโกเลีย'),
(2359, 'mn', 'tr', 'Mongolca'),
(2360, 'mn', 'uk', 'Mongolian'),
(2361, 'mn', 'ur', 'Mongolian'),
(2362, 'mn', 'uz', 'Mongolian'),
(2363, 'mn', 'vi', 'Mongolian'),
(2364, 'mn', 'yi', 'Mongolian'),
(2365, 'mn', 'zh-hans', '蒙古语'),
(2366, 'mn', 'zu', 'Mongolian'),
(2367, 'mn', 'zh-hant', '蒙古語'),
(2368, 'mn', 'ms', 'Mongolian'),
(2369, 'ne', 'en', 'Nepali'),
(2370, 'ne', 'es', 'Nepalí'),
(2371, 'ne', 'de', 'Nepali'),
(2372, 'ne', 'fr', 'Népalais'),
(2373, 'ne', 'ar', 'النيبالية'),
(2374, 'ne', 'bs', 'Nepali'),
(2375, 'ne', 'bg', 'Nepali'),
(2376, 'ne', 'ca', 'Nepali'),
(2377, 'ne', 'cs', 'Nepali'),
(2378, 'ne', 'sk', 'Nepálčina'),
(2379, 'ne', 'cy', 'Nepali'),
(2380, 'ne', 'da', 'Nepali'),
(2381, 'ne', 'el', 'Νεπαλι'),
(2382, 'ne', 'eo', 'Nepali'),
(2383, 'ne', 'et', 'Nepali'),
(2384, 'ne', 'eu', 'Nepali'),
(2385, 'ne', 'fa', 'Nepali'),
(2386, 'ne', 'fi', 'nepali'),
(2387, 'ne', 'ga', 'Nepali'),
(2388, 'ne', 'he', 'Nepali'),
(2389, 'ne', 'hi', 'Nepali'),
(2390, 'ne', 'hr', 'Nepali'),
(2391, 'ne', 'hu', 'nepáli'),
(2392, 'ne', 'hy', 'Nepali'),
(2393, 'ne', 'id', 'Nepali'),
(2394, 'ne', 'is', 'Nepali'),
(2395, 'ne', 'it', 'Nepalese'),
(2396, 'ne', 'ja', 'ネパール語'),
(2397, 'ne', 'ko', '네팔어'),
(2398, 'ne', 'ku', 'Nepali'),
(2399, 'ne', 'la', 'Nepali'),
(2400, 'ne', 'lv', 'Nepali'),
(2401, 'ne', 'lt', 'Nepali'),
(2402, 'ne', 'mk', 'Nepali'),
(2403, 'ne', 'mt', 'Nepali'),
(2404, 'ne', 'mo', 'Nepali'),
(2405, 'ne', 'mn', 'Nepali'),
(2406, 'ne', 'ne', 'Nepali'),
(2407, 'ne', 'nl', 'Nepalees'),
(2408, 'ne', 'nb', 'Nepali'),
(2409, 'ne', 'pa', 'Nepali'),
(2410, 'ne', 'pl', 'nepalski'),
(2411, 'ne', 'pt-pt', 'Nepali'),
(2412, 'ne', 'pt-br', 'Nepali'),
(2413, 'ne', 'qu', 'Nepali'),
(2414, 'ne', 'ro', 'Nepaleză'),
(2415, 'ne', 'ru', 'Непальский'),
(2416, 'ne', 'sl', 'Nepali'),
(2417, 'ne', 'so', 'Nepali'),
(2418, 'ne', 'sq', 'Nepali'),
(2419, 'ne', 'sr', 'Nepali'),
(2420, 'ne', 'sv', 'Nepalesiska'),
(2421, 'ne', 'ta', 'Nepali'),
(2422, 'ne', 'th', 'เนปาล'),
(2423, 'ne', 'tr', 'Nepal dili'),
(2424, 'ne', 'uk', 'Nepali'),
(2425, 'ne', 'ur', 'Nepali'),
(2426, 'ne', 'uz', 'Nepali'),
(2427, 'ne', 'vi', 'Nepali'),
(2428, 'ne', 'yi', 'Nepali'),
(2429, 'ne', 'zh-hans', '尼泊尔语'),
(2430, 'ne', 'zu', 'Nepali'),
(2431, 'ne', 'zh-hant', '尼泊爾語'),
(2432, 'ne', 'ms', 'Nepali'),
(2433, 'nl', 'en', 'Dutch'),
(2434, 'nl', 'es', 'Holandés'),
(2435, 'nl', 'de', 'Holländisch'),
(2436, 'nl', 'fr', 'Néerlandais'),
(2437, 'nl', 'ar', 'الهولندية'),
(2438, 'nl', 'bs', 'Dutch'),
(2439, 'nl', 'bg', 'Dutch'),
(2440, 'nl', 'ca', 'Dutch'),
(2441, 'nl', 'cs', 'Dutch'),
(2442, 'nl', 'sk', 'Holandčina'),
(2443, 'nl', 'cy', 'Dutch'),
(2444, 'nl', 'da', 'Dutch'),
(2445, 'nl', 'el', 'Ολλανδικα'),
(2446, 'nl', 'eo', 'Dutch'),
(2447, 'nl', 'et', 'Dutch'),
(2448, 'nl', 'eu', 'Dutch'),
(2449, 'nl', 'fa', 'Dutch'),
(2450, 'nl', 'fi', 'hollanti'),
(2451, 'nl', 'ga', 'Dutch'),
(2452, 'nl', 'he', 'הולנדית'),
(2453, 'nl', 'hi', 'Dutch'),
(2454, 'nl', 'hr', 'Dutch'),
(2455, 'nl', 'hu', 'holland'),
(2456, 'nl', 'hy', 'Dutch'),
(2457, 'nl', 'id', 'Dutch'),
(2458, 'nl', 'is', 'Dutch'),
(2459, 'nl', 'it', 'Neerlandese'),
(2460, 'nl', 'ja', 'オランダ語'),
(2461, 'nl', 'ko', '화란어'),
(2462, 'nl', 'ku', 'Dutch'),
(2463, 'nl', 'la', 'Dutch'),
(2464, 'nl', 'lv', 'Dutch'),
(2465, 'nl', 'lt', 'Dutch'),
(2466, 'nl', 'mk', 'Dutch'),
(2467, 'nl', 'mt', 'Dutch'),
(2468, 'nl', 'mo', 'Dutch'),
(2469, 'nl', 'mn', 'Dutch'),
(2470, 'nl', 'ne', 'Dutch'),
(2471, 'nl', 'nl', 'Nederlands'),
(2472, 'nl', 'nb', 'Dutch'),
(2473, 'nl', 'pa', 'Dutch'),
(2474, 'nl', 'pl', 'holenderski'),
(2475, 'nl', 'pt-pt', 'Holandês'),
(2476, 'nl', 'pt-br', 'Holandês'),
(2477, 'nl', 'qu', 'Dutch'),
(2478, 'nl', 'ro', 'Olaneză'),
(2479, 'nl', 'ru', 'Голландский'),
(2480, 'nl', 'sl', 'Dutch'),
(2481, 'nl', 'so', 'Dutch'),
(2482, 'nl', 'sq', 'Dutch'),
(2483, 'nl', 'sr', 'Dutch'),
(2484, 'nl', 'sv', 'Nederländska'),
(2485, 'nl', 'ta', 'Dutch'),
(2486, 'nl', 'th', 'ดัตช์'),
(2487, 'nl', 'tr', 'Hollandaca'),
(2488, 'nl', 'uk', 'Dutch'),
(2489, 'nl', 'ur', 'Dutch'),
(2490, 'nl', 'uz', 'Dutch'),
(2491, 'nl', 'vi', 'Dutch'),
(2492, 'nl', 'yi', 'Dutch'),
(2493, 'nl', 'zh-hans', '荷兰语'),
(2494, 'nl', 'zu', 'Dutch'),
(2495, 'nl', 'zh-hant', '荷蘭語'),
(2496, 'nl', 'ms', 'Dutch'),
(2497, 'nb', 'en', 'Norwegian Bokmål'),
(2498, 'nb', 'es', 'Bokmål'),
(2499, 'nb', 'de', 'Norwegisch (Buchsprache)'),
(2500, 'nb', 'fr', 'Norvégien Bokmål'),
(2501, 'nb', 'ar', 'البوكمالية النرويجية'),
(2502, 'nb', 'bs', 'Norwegian Bokmål'),
(2503, 'nb', 'bg', 'Norwegian Bokmål'),
(2504, 'nb', 'ca', 'Norwegian Bokmål'),
(2505, 'nb', 'cs', 'Norwegian Bokmål'),
(2506, 'nb', 'sk', 'Nórsky jazyk Bokmål'),
(2507, 'nb', 'cy', 'Norwegian Bokmål'),
(2508, 'nb', 'da', 'Norwegian Bokmål'),
(2509, 'nb', 'el', 'Νορβηγικα'),
(2510, 'nb', 'eo', 'Norwegian Bokmål'),
(2511, 'nb', 'et', 'Norwegian Bokmål'),
(2512, 'nb', 'eu', 'Norwegian Bokmål'),
(2513, 'nb', 'fa', 'Norwegian Bokmål'),
(2514, 'nb', 'fi', 'kirjanorja'),
(2515, 'nb', 'ga', 'Norwegian Bokmål'),
(2516, 'nb', 'he', 'נורווגית'),
(2517, 'nb', 'hi', 'Norwegian Bokmål'),
(2518, 'nb', 'hr', 'Norwegian Bokmål'),
(2519, 'nb', 'hu', 'norvég bokmål'),
(2520, 'nb', 'hy', 'Norwegian Bokmål'),
(2521, 'nb', 'id', 'Norwegian Bokmål'),
(2522, 'nb', 'is', 'Norwegian Bokmål'),
(2523, 'nb', 'it', 'Norvegese Bokmål'),
(2524, 'nb', 'ja', 'ノルウェー・ブークモール'),
(2525, 'nb', 'ko', '노르웨이 보크말어'),
(2526, 'nb', 'ku', 'Norwegian Bokmål'),
(2527, 'nb', 'la', 'Norwegian Bokmål'),
(2528, 'nb', 'lv', 'Norwegian Bokmål'),
(2529, 'nb', 'lt', 'Norwegian Bokmål'),
(2530, 'nb', 'mk', 'Norwegian Bokmål'),
(2531, 'nb', 'mt', 'Norwegian Bokmål'),
(2532, 'nb', 'mo', 'Norwegian Bokmål'),
(2533, 'nb', 'mn', 'Norwegian Bokmål'),
(2534, 'nb', 'ne', 'Norwegian Bokmål'),
(2535, 'nb', 'nl', 'Noors Bokmål'),
(2536, 'nb', 'nb', 'Norwegian Bokmål'),
(2537, 'nb', 'pa', 'Norwegian Bokmål'),
(2538, 'nb', 'pl', 'norweski bokmål'),
(2539, 'nb', 'pt-pt', 'Norueguês'),
(2540, 'nb', 'pt-br', 'Norueguês'),
(2541, 'nb', 'qu', 'Norwegian Bokmål'),
(2542, 'nb', 'ro', 'Bokmål (norvegiană)'),
(2543, 'nb', 'ru', 'Норвежский букмол'),
(2544, 'nb', 'sl', 'Norwegian Bokmål'),
(2545, 'nb', 'so', 'Norwegian Bokmål'),
(2546, 'nb', 'sq', 'Norwegian Bokmål'),
(2547, 'nb', 'sr', 'Norwegian Bokmål'),
(2548, 'nb', 'sv', 'Norskt Bokmål'),
(2549, 'nb', 'ta', 'Norwegian Bokmål'),
(2550, 'nb', 'th', 'นอร์วิเจียนบอกมาล'),
(2551, 'nb', 'tr', 'Bokmal Norveç dili'),
(2552, 'nb', 'uk', 'Norwegian Bokmål'),
(2553, 'nb', 'ur', 'Norwegian Bokmål'),
(2554, 'nb', 'uz', 'Norwegian Bokmål'),
(2555, 'nb', 'vi', 'Norwegian Bokmål'),
(2556, 'nb', 'yi', 'Norwegian Bokmål'),
(2557, 'nb', 'zh-hans', '挪威布克莫尔语'),
(2558, 'nb', 'zu', 'Norwegian Bokmål'),
(2559, 'nb', 'zh-hant', '挪威布克莫爾語'),
(2560, 'nb', 'ms', 'Norwegian Bokmål'),
(2561, 'pa', 'en', 'Punjabi'),
(2562, 'pa', 'es', 'Panyabí'),
(2563, 'pa', 'de', 'Pandschabi'),
(2564, 'pa', 'fr', 'Panjabi'),
(2565, 'pa', 'ar', 'البنجابية'),
(2566, 'pa', 'bs', 'Punjabi'),
(2567, 'pa', 'bg', 'Punjabi'),
(2568, 'pa', 'ca', 'Punjabi'),
(2569, 'pa', 'cs', 'Punjabi'),
(2570, 'pa', 'sk', 'Pandžábčina'),
(2571, 'pa', 'cy', 'Punjabi'),
(2572, 'pa', 'da', 'Punjabi'),
(2573, 'pa', 'el', 'Panjabi'),
(2574, 'pa', 'eo', 'Punjabi'),
(2575, 'pa', 'et', 'Punjabi'),
(2576, 'pa', 'eu', 'Punjabi'),
(2577, 'pa', 'fa', 'Punjabi'),
(2578, 'pa', 'fi', 'pandzabi'),
(2579, 'pa', 'ga', 'Punjabi'),
(2580, 'pa', 'he', 'Punjabi'),
(2581, 'pa', 'hi', 'Punjabi'),
(2582, 'pa', 'hr', 'Punjabi'),
(2583, 'pa', 'hu', 'pandzsábi'),
(2584, 'pa', 'hy', 'Punjabi'),
(2585, 'pa', 'id', 'Punjabi'),
(2586, 'pa', 'is', 'Punjabi'),
(2587, 'pa', 'it', 'Panjabi'),
(2588, 'pa', 'ja', 'パンジャーブ語'),
(2589, 'pa', 'ko', '펀자브어'),
(2590, 'pa', 'ku', 'Punjabi'),
(2591, 'pa', 'la', 'Punjabi'),
(2592, 'pa', 'lv', 'Punjabi'),
(2593, 'pa', 'lt', 'Punjabi'),
(2594, 'pa', 'mk', 'Punjabi'),
(2595, 'pa', 'mt', 'Punjabi'),
(2596, 'pa', 'mo', 'Punjabi'),
(2597, 'pa', 'mn', 'Punjabi'),
(2598, 'pa', 'ne', 'Punjabi'),
(2599, 'pa', 'nl', 'Punjabi'),
(2600, 'pa', 'nb', 'Punjabi'),
(2601, 'pa', 'pa', 'Punjabi'),
(2602, 'pa', 'pl', 'pendżabi'),
(2603, 'pa', 'pt-pt', 'Panjabi'),
(2604, 'pa', 'pt-br', 'Panjabi'),
(2605, 'pa', 'qu', 'Punjabi'),
(2606, 'pa', 'ro', 'Punjabi'),
(2607, 'pa', 'ru', 'Панджаби'),
(2608, 'pa', 'sl', 'Punjabi'),
(2609, 'pa', 'so', 'Punjabi'),
(2610, 'pa', 'sq', 'Punjabi'),
(2611, 'pa', 'sr', 'Punjabi'),
(2612, 'pa', 'sv', 'Punjabi'),
(2613, 'pa', 'ta', 'Punjabi'),
(2614, 'pa', 'th', 'ปัญจาบ'),
(2615, 'pa', 'tr', 'Pencapça'),
(2616, 'pa', 'uk', 'Punjabi'),
(2617, 'pa', 'ur', 'Punjabi'),
(2618, 'pa', 'uz', 'Punjabi'),
(2619, 'pa', 'vi', 'Punjabi'),
(2620, 'pa', 'yi', 'Punjabi'),
(2621, 'pa', 'zh-hans', '旁遮普语'),
(2622, 'pa', 'zu', 'Punjabi'),
(2623, 'pa', 'zh-hant', '旁遮普語'),
(2624, 'pa', 'ms', 'Punjabi'),
(2625, 'pl', 'en', 'Polish'),
(2626, 'pl', 'es', 'Polaco'),
(2627, 'pl', 'de', 'Polnisch'),
(2628, 'pl', 'fr', 'Polonais'),
(2629, 'pl', 'ar', 'البولندية'),
(2630, 'pl', 'bs', 'Polish'),
(2631, 'pl', 'bg', 'Polish'),
(2632, 'pl', 'ca', 'Polish'),
(2633, 'pl', 'cs', 'Polish'),
(2634, 'pl', 'sk', 'Polština'),
(2635, 'pl', 'cy', 'Polish'),
(2636, 'pl', 'da', 'Polish'),
(2637, 'pl', 'el', 'Πολωνικα'),
(2638, 'pl', 'eo', 'Polish'),
(2639, 'pl', 'et', 'Polish'),
(2640, 'pl', 'eu', 'Polish'),
(2641, 'pl', 'fa', 'Polish'),
(2642, 'pl', 'fi', 'puola'),
(2643, 'pl', 'ga', 'Polish'),
(2644, 'pl', 'he', 'פולנית'),
(2645, 'pl', 'hi', 'Polish'),
(2646, 'pl', 'hr', 'Polish'),
(2647, 'pl', 'hu', 'lengyel'),
(2648, 'pl', 'hy', 'Polish'),
(2649, 'pl', 'id', 'Polish'),
(2650, 'pl', 'is', 'Polish'),
(2651, 'pl', 'it', 'Polacco'),
(2652, 'pl', 'ja', 'ポーランド語'),
(2653, 'pl', 'ko', '폴란드어'),
(2654, 'pl', 'ku', 'Polish'),
(2655, 'pl', 'la', 'Polish'),
(2656, 'pl', 'lv', 'Polish'),
(2657, 'pl', 'lt', 'Polish'),
(2658, 'pl', 'mk', 'Polish'),
(2659, 'pl', 'mt', 'Polish'),
(2660, 'pl', 'mo', 'Polish'),
(2661, 'pl', 'mn', 'Polish'),
(2662, 'pl', 'ne', 'Polish'),
(2663, 'pl', 'nl', 'Pools'),
(2664, 'pl', 'nb', 'Polish'),
(2665, 'pl', 'pa', 'Polish'),
(2666, 'pl', 'pl', 'polski'),
(2667, 'pl', 'pt-pt', 'Polonês'),
(2668, 'pl', 'pt-br', 'Polonês'),
(2669, 'pl', 'qu', 'Polish'),
(2670, 'pl', 'ro', 'Poloneză'),
(2671, 'pl', 'ru', 'Польский'),
(2672, 'pl', 'sl', 'Polish'),
(2673, 'pl', 'so', 'Polish'),
(2674, 'pl', 'sq', 'Polish'),
(2675, 'pl', 'sr', 'Polish'),
(2676, 'pl', 'sv', 'Polska'),
(2677, 'pl', 'ta', 'Polish'),
(2678, 'pl', 'th', 'โปแลนด์'),
(2679, 'pl', 'tr', 'Polonyaca'),
(2680, 'pl', 'uk', 'Polish'),
(2681, 'pl', 'ur', 'Polish'),
(2682, 'pl', 'uz', 'Polish'),
(2683, 'pl', 'vi', 'Polish'),
(2684, 'pl', 'yi', 'Polish'),
(2685, 'pl', 'zh-hans', '波兰语'),
(2686, 'pl', 'zu', 'Polish'),
(2687, 'pl', 'zh-hant', '波蘭語'),
(2688, 'pl', 'ms', 'Polish'),
(2689, 'pt-pt', 'en', 'Portuguese (Portugal)'),
(2690, 'pt-pt', 'es', 'Portugués, Portugal'),
(2691, 'pt-pt', 'de', 'Portugiesisch, Portugal'),
(2692, 'pt-pt', 'fr', 'Portugais - du Portugal'),
(2693, 'pt-pt', 'ar', 'البرتغالية ، البرتغال'),
(2694, 'pt-pt', 'bs', 'Portuguese, Portugal'),
(2695, 'pt-pt', 'bg', 'Portuguese, Portugal'),
(2696, 'pt-pt', 'ca', 'Portuguese, Portugal'),
(2697, 'pt-pt', 'cs', 'Portuguese, Portugal'),
(2698, 'pt-pt', 'sk', 'Portugalština'),
(2699, 'pt-pt', 'cy', 'Portuguese, Portugal'),
(2700, 'pt-pt', 'da', 'Portuguese, Portugal'),
(2701, 'pt-pt', 'el', 'Πορτογαλικα'),
(2702, 'pt-pt', 'eo', 'Portuguese, Portugal'),
(2703, 'pt-pt', 'et', 'Portuguese, Portugal'),
(2704, 'pt-pt', 'eu', 'Portuguese, Portugal'),
(2705, 'pt-pt', 'fa', 'Portuguese, Portugal'),
(2706, 'pt-pt', 'fi', 'portugali'),
(2707, 'pt-pt', 'ga', 'Portuguese, Portugal'),
(2708, 'pt-pt', 'he', 'פורטוגזית'),
(2709, 'pt-pt', 'hi', 'Portuguese, Portugal'),
(2710, 'pt-pt', 'hr', 'Portuguese, Portugal'),
(2711, 'pt-pt', 'hu', 'portugál'),
(2712, 'pt-pt', 'hy', 'Portuguese, Portugal'),
(2713, 'pt-pt', 'id', 'Portuguese, Portugal'),
(2714, 'pt-pt', 'is', 'Portuguese, Portugal'),
(2715, 'pt-pt', 'it', 'Portoghese, Portogallo'),
(2716, 'pt-pt', 'ja', 'ポルトガル語'),
(2717, 'pt-pt', 'ko', '포르투갈 포르투갈어'),
(2718, 'pt-pt', 'ku', 'Portuguese, Portugal'),
(2719, 'pt-pt', 'la', 'Portuguese, Portugal'),
(2720, 'pt-pt', 'lv', 'Portuguese, Portugal'),
(2721, 'pt-pt', 'lt', 'Portuguese, Portugal'),
(2722, 'pt-pt', 'mk', 'Portuguese, Portugal'),
(2723, 'pt-pt', 'mt', 'Portuguese, Portugal'),
(2724, 'pt-pt', 'mo', 'Portuguese, Portugal'),
(2725, 'pt-pt', 'mn', 'Portuguese, Portugal'),
(2726, 'pt-pt', 'ne', 'Portuguese, Portugal'),
(2727, 'pt-pt', 'nl', 'Portugees, Portugal'),
(2728, 'pt-pt', 'nb', 'Portuguese, Portugal'),
(2729, 'pt-pt', 'pa', 'Portuguese, Portugal'),
(2730, 'pt-pt', 'pl', 'portugalski, Portugalia'),
(2731, 'pt-pt', 'pt-pt', 'Português'),
(2732, 'pt-pt', 'pt-br', 'Português'),
(2733, 'pt-pt', 'qu', 'Portuguese, Portugal'),
(2734, 'pt-pt', 'ro', 'Portugheză (Portugalia)'),
(2735, 'pt-pt', 'ru', 'Португальский, Португалия'),
(2736, 'pt-pt', 'sl', 'Portuguese, Portugal'),
(2737, 'pt-pt', 'so', 'Portuguese, Portugal'),
(2738, 'pt-pt', 'sq', 'Portuguese, Portugal'),
(2739, 'pt-pt', 'sr', 'Portuguese, Portugal'),
(2740, 'pt-pt', 'sv', 'Portugisiska, Portugal'),
(2741, 'pt-pt', 'ta', 'Portuguese, Portugal'),
(2742, 'pt-pt', 'th', 'โปรตุเกส'),
(2743, 'pt-pt', 'tr', 'Portekizce, Portekiz'),
(2744, 'pt-pt', 'uk', 'Portuguese, Portugal'),
(2745, 'pt-pt', 'ur', 'Portuguese, Portugal'),
(2746, 'pt-pt', 'uz', 'Portuguese, Portugal'),
(2747, 'pt-pt', 'vi', 'Portuguese, Portugal'),
(2748, 'pt-pt', 'yi', 'Portuguese, Portugal'),
(2749, 'pt-pt', 'zh-hans', '葡萄牙语（葡萄牙）'),
(2750, 'pt-pt', 'zu', 'Portuguese, Portugal'),
(2751, 'pt-pt', 'zh-hant', '葡萄牙語（葡萄牙）'),
(2752, 'pt-pt', 'ms', 'Portuguese, Portugal'),
(2753, 'pt-br', 'en', 'Portuguese (Brazil)'),
(2754, 'pt-br', 'es', 'Portugués, Brasil'),
(2755, 'pt-br', 'de', 'Portugiesisch, Brasilien'),
(2756, 'pt-br', 'fr', 'Portugais - du Brésil'),
(2757, 'pt-br', 'ar', 'البرتغالية ،البرازيل'),
(2758, 'pt-br', 'bs', 'Portuguese, Brazil'),
(2759, 'pt-br', 'bg', 'Portuguese, Brazil'),
(2760, 'pt-br', 'ca', 'Portuguese, Brazil'),
(2761, 'pt-br', 'cs', 'Portuguese, Brazil'),
(2762, 'pt-br', 'sk', 'Brazílska Portugalština'),
(2763, 'pt-br', 'cy', 'Portuguese, Brazil'),
(2764, 'pt-br', 'da', 'Portuguese, Brazil'),
(2765, 'pt-br', 'el', 'Πορτογαλικα'),
(2766, 'pt-br', 'eo', 'Portuguese, Brazil'),
(2767, 'pt-br', 'et', 'Portuguese, Brazil'),
(2768, 'pt-br', 'eu', 'Portuguese, Brazil'),
(2769, 'pt-br', 'fa', 'Portuguese, Brazil'),
(2770, 'pt-br', 'fi', 'Brasilian portugali'),
(2771, 'pt-br', 'ga', 'Portuguese, Brazil'),
(2772, 'pt-br', 'he', 'פורטוגזית'),
(2773, 'pt-br', 'hi', 'Portuguese, Brazil'),
(2774, 'pt-br', 'hr', 'Portuguese, Brazil'),
(2775, 'pt-br', 'hu', 'brazil'),
(2776, 'pt-br', 'hy', 'Portuguese, Brazil'),
(2777, 'pt-br', 'id', 'Portuguese, Brazil'),
(2778, 'pt-br', 'is', 'Portuguese, Brazil'),
(2779, 'pt-br', 'it', 'Portoghese, Brasile'),
(2780, 'pt-br', 'ja', 'ポルトガル語（ブラジル）'),
(2781, 'pt-br', 'ko', '브라질 포르투갈어'),
(2782, 'pt-br', 'ku', 'Portuguese, Brazil'),
(2783, 'pt-br', 'la', 'Portuguese, Brazil'),
(2784, 'pt-br', 'lv', 'Portuguese, Brazil'),
(2785, 'pt-br', 'lt', 'Portuguese, Brazil'),
(2786, 'pt-br', 'mk', 'Portuguese, Brazil'),
(2787, 'pt-br', 'mt', 'Portuguese, Brazil'),
(2788, 'pt-br', 'mo', 'Portuguese, Brazil'),
(2789, 'pt-br', 'mn', 'Portuguese, Brazil'),
(2790, 'pt-br', 'ne', 'Portuguese, Brazil'),
(2791, 'pt-br', 'nl', 'Portugees, Brazilië'),
(2792, 'pt-br', 'nb', 'Portuguese, Brazil'),
(2793, 'pt-br', 'pa', 'Portuguese, Brazil'),
(2794, 'pt-br', 'pl', 'portugalski, Brazylia'),
(2795, 'pt-br', 'pt-pt', 'Português'),
(2796, 'pt-br', 'pt-br', 'Português'),
(2797, 'pt-br', 'qu', 'Portuguese, Brazil'),
(2798, 'pt-br', 'ro', 'Portugheză (Brazilia)'),
(2799, 'pt-br', 'ru', 'Португальский, Бразилия'),
(2800, 'pt-br', 'sl', 'Portuguese, Brazil'),
(2801, 'pt-br', 'so', 'Portuguese, Brazil'),
(2802, 'pt-br', 'sq', 'Portuguese, Brazil'),
(2803, 'pt-br', 'sr', 'Portuguese, Brazil'),
(2804, 'pt-br', 'sv', 'Portugisiska, Brasilien'),
(2805, 'pt-br', 'ta', 'Portuguese, Brazil'),
(2806, 'pt-br', 'th', 'โปรตุเกสบราซิล'),
(2807, 'pt-br', 'tr', 'Portekizce, Brezilya'),
(2808, 'pt-br', 'uk', 'Portuguese, Brazil'),
(2809, 'pt-br', 'ur', 'Portuguese, Brazil'),
(2810, 'pt-br', 'uz', 'Portuguese, Brazil'),
(2811, 'pt-br', 'vi', 'Portuguese, Brazil'),
(2812, 'pt-br', 'yi', 'Portuguese, Brazil'),
(2813, 'pt-br', 'zh-hans', '葡萄牙语（巴西）'),
(2814, 'pt-br', 'zu', 'Portuguese, Brazil'),
(2815, 'pt-br', 'zh-hant', '葡萄牙語（巴西）'),
(2816, 'pt-br', 'ms', 'Portuguese, Brazil'),
(2817, 'qu', 'en', 'Quechua'),
(2818, 'qu', 'es', 'Quechua'),
(2819, 'qu', 'de', 'Quechua'),
(2820, 'qu', 'fr', 'Quechua'),
(2821, 'qu', 'ar', 'الكويتشوا'),
(2822, 'qu', 'bs', 'Quechua'),
(2823, 'qu', 'bg', 'Quechua'),
(2824, 'qu', 'ca', 'Quechua'),
(2825, 'qu', 'cs', 'Quechua'),
(2826, 'qu', 'sk', 'Jazyk Quechua'),
(2827, 'qu', 'cy', 'Quechua'),
(2828, 'qu', 'da', 'Quechua'),
(2829, 'qu', 'el', 'Κετσουα'),
(2830, 'qu', 'eo', 'Quechua'),
(2831, 'qu', 'et', 'Quechua'),
(2832, 'qu', 'eu', 'Quechua'),
(2833, 'qu', 'fa', 'Quechua'),
(2834, 'qu', 'fi', 'ketsua'),
(2835, 'qu', 'ga', 'Quechua'),
(2836, 'qu', 'he', 'Quechua'),
(2837, 'qu', 'hi', 'Quechua'),
(2838, 'qu', 'hr', 'Quechua'),
(2839, 'qu', 'hu', 'quechua'),
(2840, 'qu', 'hy', 'Quechua'),
(2841, 'qu', 'id', 'Quechua'),
(2842, 'qu', 'is', 'Quechua'),
(2843, 'qu', 'it', 'Quechua'),
(2844, 'qu', 'ja', 'ケチュア語'),
(2845, 'qu', 'ko', '케추아어'),
(2846, 'qu', 'ku', 'Quechua'),
(2847, 'qu', 'la', 'Quechua'),
(2848, 'qu', 'lv', 'Quechua'),
(2849, 'qu', 'lt', 'Quechua'),
(2850, 'qu', 'mk', 'Quechua'),
(2851, 'qu', 'mt', 'Quechua'),
(2852, 'qu', 'mo', 'Quechua'),
(2853, 'qu', 'mn', 'Quechua'),
(2854, 'qu', 'ne', 'Quechua'),
(2855, 'qu', 'nl', 'Quechua'),
(2856, 'qu', 'nb', 'Quechua'),
(2857, 'qu', 'pa', 'Quechua'),
(2858, 'qu', 'pl', 'keczua'),
(2859, 'qu', 'pt-pt', 'Quechua'),
(2860, 'qu', 'pt-br', 'Quechua'),
(2861, 'qu', 'qu', 'Quechua'),
(2862, 'qu', 'ro', 'Quechuană'),
(2863, 'qu', 'ru', 'Кечуа'),
(2864, 'qu', 'sl', 'Quechua'),
(2865, 'qu', 'so', 'Quechua'),
(2866, 'qu', 'sq', 'Quechua'),
(2867, 'qu', 'sr', 'Quechua'),
(2868, 'qu', 'sv', 'Quechua'),
(2869, 'qu', 'ta', 'Quechua'),
(2870, 'qu', 'th', 'คิวชัว'),
(2871, 'qu', 'tr', 'Quechua dili'),
(2872, 'qu', 'uk', 'Quechua'),
(2873, 'qu', 'ur', 'Quechua'),
(2874, 'qu', 'uz', 'Quechua'),
(2875, 'qu', 'vi', 'Quechua'),
(2876, 'qu', 'yi', 'Quechua'),
(2877, 'qu', 'zh-hans', '盖丘亚语'),
(2878, 'qu', 'zu', 'Quechua'),
(2879, 'qu', 'zh-hant', '蓋丘亞語'),
(2880, 'qu', 'ms', 'Quechua'),
(2881, 'ro', 'en', 'Romanian'),
(2882, 'ro', 'es', 'Rumano'),
(2883, 'ro', 'de', 'Rumänisch'),
(2884, 'ro', 'fr', 'Roumain'),
(2885, 'ro', 'ar', 'الرومانية'),
(2886, 'ro', 'bs', 'Romanian'),
(2887, 'ro', 'bg', 'Romanian'),
(2888, 'ro', 'ca', 'Romanian'),
(2889, 'ro', 'cs', 'Romanian'),
(2890, 'ro', 'sk', 'Rumunčina'),
(2891, 'ro', 'cy', 'Romanian'),
(2892, 'ro', 'da', 'Romanian'),
(2893, 'ro', 'el', 'Ρουμανικα'),
(2894, 'ro', 'eo', 'Romanian'),
(2895, 'ro', 'et', 'Romanian'),
(2896, 'ro', 'eu', 'Romanian'),
(2897, 'ro', 'fa', 'Romanian'),
(2898, 'ro', 'fi', 'romania'),
(2899, 'ro', 'ga', 'Romanian'),
(2900, 'ro', 'he', 'רומנית'),
(2901, 'ro', 'hi', 'Romanian'),
(2902, 'ro', 'hr', 'Romanian'),
(2903, 'ro', 'hu', 'román'),
(2904, 'ro', 'hy', 'Romanian'),
(2905, 'ro', 'id', 'Romanian'),
(2906, 'ro', 'is', 'Romanian'),
(2907, 'ro', 'it', 'Rumeno'),
(2908, 'ro', 'ja', 'ルーマニア語'),
(2909, 'ro', 'ko', '로마니아어'),
(2910, 'ro', 'ku', 'Romanian'),
(2911, 'ro', 'la', 'Romanian'),
(2912, 'ro', 'lv', 'Romanian'),
(2913, 'ro', 'lt', 'Romanian'),
(2914, 'ro', 'mk', 'Romanian'),
(2915, 'ro', 'mt', 'Romanian'),
(2916, 'ro', 'mo', 'Romanian'),
(2917, 'ro', 'mn', 'Romanian'),
(2918, 'ro', 'ne', 'Romanian'),
(2919, 'ro', 'nl', 'Roemeens'),
(2920, 'ro', 'nb', 'Romanian'),
(2921, 'ro', 'pa', 'Romanian'),
(2922, 'ro', 'pl', 'rumuński'),
(2923, 'ro', 'pt-pt', 'Romeno'),
(2924, 'ro', 'pt-br', 'Romeno'),
(2925, 'ro', 'qu', 'Romanian'),
(2926, 'ro', 'ro', 'Română'),
(2927, 'ro', 'ru', 'Румынский'),
(2928, 'ro', 'sl', 'Romanian'),
(2929, 'ro', 'so', 'Romanian'),
(2930, 'ro', 'sq', 'Romanian'),
(2931, 'ro', 'sr', 'Romanian'),
(2932, 'ro', 'sv', 'Rumänska'),
(2933, 'ro', 'ta', 'Romanian'),
(2934, 'ro', 'th', 'โรมาเนีย'),
(2935, 'ro', 'tr', 'Rumence'),
(2936, 'ro', 'uk', 'Romanian'),
(2937, 'ro', 'ur', 'Romanian'),
(2938, 'ro', 'uz', 'Romanian'),
(2939, 'ro', 'vi', 'Romanian'),
(2940, 'ro', 'yi', 'Romanian'),
(2941, 'ro', 'zh-hans', '罗马尼亚语'),
(2942, 'ro', 'zu', 'Romanian'),
(2943, 'ro', 'zh-hant', '羅馬尼亞語'),
(2944, 'ro', 'ms', 'Romanian'),
(2945, 'ru', 'en', 'Russian'),
(2946, 'ru', 'es', 'Ruso'),
(2947, 'ru', 'de', 'Russisch'),
(2948, 'ru', 'fr', 'Russe'),
(2949, 'ru', 'ar', 'الروسية'),
(2950, 'ru', 'bs', 'Russian'),
(2951, 'ru', 'bg', 'Russian'),
(2952, 'ru', 'ca', 'Russian'),
(2953, 'ru', 'cs', 'Russian'),
(2954, 'ru', 'sk', 'Ruština'),
(2955, 'ru', 'cy', 'Russian'),
(2956, 'ru', 'da', 'Russian'),
(2957, 'ru', 'el', 'Ρωσικα'),
(2958, 'ru', 'eo', 'Russian'),
(2959, 'ru', 'et', 'Russian'),
(2960, 'ru', 'eu', 'Russian'),
(2961, 'ru', 'fa', 'Russian'),
(2962, 'ru', 'fi', 'venäjä'),
(2963, 'ru', 'ga', 'Russian'),
(2964, 'ru', 'he', 'רוסית'),
(2965, 'ru', 'hi', 'Russian'),
(2966, 'ru', 'hr', 'Russian'),
(2967, 'ru', 'hu', 'orosz'),
(2968, 'ru', 'hy', 'Russian'),
(2969, 'ru', 'id', 'Russian'),
(2970, 'ru', 'is', 'Russian'),
(2971, 'ru', 'it', 'Russo'),
(2972, 'ru', 'ja', 'ロシア語'),
(2973, 'ru', 'ko', '러시아어'),
(2974, 'ru', 'ku', 'Russian'),
(2975, 'ru', 'la', 'Russian'),
(2976, 'ru', 'lv', 'Russian'),
(2977, 'ru', 'lt', 'Russian'),
(2978, 'ru', 'mk', 'Russian'),
(2979, 'ru', 'mt', 'Russian'),
(2980, 'ru', 'mo', 'Russian'),
(2981, 'ru', 'mn', 'Russian'),
(2982, 'ru', 'ne', 'Russian'),
(2983, 'ru', 'nl', 'Russisch'),
(2984, 'ru', 'nb', 'Russian'),
(2985, 'ru', 'pa', 'Russian'),
(2986, 'ru', 'pl', 'rosyjski'),
(2987, 'ru', 'pt-pt', 'Russo'),
(2988, 'ru', 'pt-br', 'Russo'),
(2989, 'ru', 'qu', 'Russian'),
(2990, 'ru', 'ro', 'Rusă'),
(2991, 'ru', 'ru', 'Русский'),
(2992, 'ru', 'sl', 'Russian'),
(2993, 'ru', 'so', 'Russian'),
(2994, 'ru', 'sq', 'Russian'),
(2995, 'ru', 'sr', 'Russian'),
(2996, 'ru', 'sv', 'Ryska'),
(2997, 'ru', 'ta', 'Russian'),
(2998, 'ru', 'th', 'รัสเซีย'),
(2999, 'ru', 'tr', 'Rusça'),
(3000, 'ru', 'uk', 'Russian'),
(3001, 'ru', 'ur', 'Russian'),
(3002, 'ru', 'uz', 'Russian'),
(3003, 'ru', 'vi', 'Russian'),
(3004, 'ru', 'yi', 'Russian'),
(3005, 'ru', 'zh-hans', '俄语'),
(3006, 'ru', 'zu', 'Russian'),
(3007, 'ru', 'zh-hant', '俄語'),
(3008, 'ru', 'ms', 'Russian'),
(3009, 'sl', 'en', 'Slovenian'),
(3010, 'sl', 'es', 'Esloveno'),
(3011, 'sl', 'de', 'Slowenisch'),
(3012, 'sl', 'fr', 'Slovène'),
(3013, 'sl', 'ar', 'السلوفانية'),
(3014, 'sl', 'bs', 'Slovenian'),
(3015, 'sl', 'bg', 'Slovenian'),
(3016, 'sl', 'ca', 'Slovenian'),
(3017, 'sl', 'cs', 'Slovenian'),
(3018, 'sl', 'sk', 'Slovinčina'),
(3019, 'sl', 'cy', 'Slovenian'),
(3020, 'sl', 'da', 'Slovenian'),
(3021, 'sl', 'el', 'Σλοβενικα'),
(3022, 'sl', 'eo', 'Slovenian'),
(3023, 'sl', 'et', 'Slovenian'),
(3024, 'sl', 'eu', 'Slovenian'),
(3025, 'sl', 'fa', 'Slovenian'),
(3026, 'sl', 'fi', 'sloveeni'),
(3027, 'sl', 'ga', 'Slovenian'),
(3028, 'sl', 'he', 'Slovenian'),
(3029, 'sl', 'hi', 'Slovenian'),
(3030, 'sl', 'hr', 'Slovenian'),
(3031, 'sl', 'hu', 'szlovén'),
(3032, 'sl', 'hy', 'Slovenian'),
(3033, 'sl', 'id', 'Slovenian'),
(3034, 'sl', 'is', 'Slovenian'),
(3035, 'sl', 'it', 'Sloveno'),
(3036, 'sl', 'ja', 'スロベニア語'),
(3037, 'sl', 'ko', '슬로베니아어'),
(3038, 'sl', 'ku', 'Slovenian'),
(3039, 'sl', 'la', 'Slovenian'),
(3040, 'sl', 'lv', 'Slovenian'),
(3041, 'sl', 'lt', 'Slovenian'),
(3042, 'sl', 'mk', 'Slovenian'),
(3043, 'sl', 'mt', 'Slovenian'),
(3044, 'sl', 'mo', 'Slovenian'),
(3045, 'sl', 'mn', 'Slovenian'),
(3046, 'sl', 'ne', 'Slovenian'),
(3047, 'sl', 'nl', 'Sloveens'),
(3048, 'sl', 'nb', 'Slovenian'),
(3049, 'sl', 'pa', 'Slovenian'),
(3050, 'sl', 'pl', 'słoweński'),
(3051, 'sl', 'pt-pt', 'Esloveno'),
(3052, 'sl', 'pt-br', 'Esloveno'),
(3053, 'sl', 'qu', 'Slovenian'),
(3054, 'sl', 'ro', 'Slovenă'),
(3055, 'sl', 'ru', 'Словенский'),
(3056, 'sl', 'sl', 'Slovenian'),
(3057, 'sl', 'so', 'Slovenian'),
(3058, 'sl', 'sq', 'Slovenian'),
(3059, 'sl', 'sr', 'Slovenian'),
(3060, 'sl', 'sv', 'Slovenska'),
(3061, 'sl', 'ta', 'Slovenian'),
(3062, 'sl', 'th', 'สโลวีเนียน'),
(3063, 'sl', 'tr', 'Sloven dili'),
(3064, 'sl', 'uk', 'Slovenian'),
(3065, 'sl', 'ur', 'Slovenian'),
(3066, 'sl', 'uz', 'Slovenian'),
(3067, 'sl', 'vi', 'Slovenian'),
(3068, 'sl', 'yi', 'Slovenian'),
(3069, 'sl', 'zh-hans', '斯洛文尼亚语'),
(3070, 'sl', 'zu', 'Slovenian'),
(3071, 'sl', 'zh-hant', '斯洛文尼亞語'),
(3072, 'sl', 'ms', 'Slovenian'),
(3073, 'so', 'en', 'Somali'),
(3074, 'so', 'es', 'Somalí'),
(3075, 'so', 'de', 'Somali'),
(3076, 'so', 'fr', 'Somali'),
(3077, 'so', 'ar', 'الصومالية'),
(3078, 'so', 'bs', 'Somali'),
(3079, 'so', 'bg', 'Somali'),
(3080, 'so', 'ca', 'Somali'),
(3081, 'so', 'cs', 'Somali'),
(3082, 'so', 'sk', 'Somálčina'),
(3083, 'so', 'cy', 'Somali'),
(3084, 'so', 'da', 'Somali'),
(3085, 'so', 'el', 'Somali'),
(3086, 'so', 'eo', 'Somali'),
(3087, 'so', 'et', 'Somali'),
(3088, 'so', 'eu', 'Somali'),
(3089, 'so', 'fa', 'Somali'),
(3090, 'so', 'fi', 'somali'),
(3091, 'so', 'ga', 'Somali'),
(3092, 'so', 'he', 'Somali'),
(3093, 'so', 'hi', 'Somali'),
(3094, 'so', 'hr', 'Somali'),
(3095, 'so', 'hu', 'szomáli'),
(3096, 'so', 'hy', 'Somali'),
(3097, 'so', 'id', 'Somali'),
(3098, 'so', 'is', 'Somali'),
(3099, 'so', 'it', 'Somalo'),
(3100, 'so', 'ja', 'ソマリ語'),
(3101, 'so', 'ko', '소말리아어'),
(3102, 'so', 'ku', 'Somali'),
(3103, 'so', 'la', 'Somali'),
(3104, 'so', 'lv', 'Somali'),
(3105, 'so', 'lt', 'Somali'),
(3106, 'so', 'mk', 'Somali'),
(3107, 'so', 'mt', 'Somali'),
(3108, 'so', 'mo', 'Somali'),
(3109, 'so', 'mn', 'Somali'),
(3110, 'so', 'ne', 'Somali'),
(3111, 'so', 'nl', 'Somalisch'),
(3112, 'so', 'nb', 'Somali'),
(3113, 'so', 'pa', 'Somali'),
(3114, 'so', 'pl', 'somalijski'),
(3115, 'so', 'pt-pt', 'Somali'),
(3116, 'so', 'pt-br', 'Somali'),
(3117, 'so', 'qu', 'Somali'),
(3118, 'so', 'ro', 'Somaleză'),
(3119, 'so', 'ru', 'Сомалийский'),
(3120, 'so', 'sl', 'Somali'),
(3121, 'so', 'so', 'Somali'),
(3122, 'so', 'sq', 'Somali'),
(3123, 'so', 'sr', 'Somali'),
(3124, 'so', 'sv', 'Somaliska'),
(3125, 'so', 'ta', 'Somali'),
(3126, 'so', 'th', 'โซมาลี'),
(3127, 'so', 'tr', 'Somalice'),
(3128, 'so', 'uk', 'Somali'),
(3129, 'so', 'ur', 'Somali'),
(3130, 'so', 'uz', 'Somali'),
(3131, 'so', 'vi', 'Somali'),
(3132, 'so', 'yi', 'Somali'),
(3133, 'so', 'zh-hans', '索马里语'),
(3134, 'so', 'zu', 'Somali'),
(3135, 'so', 'zh-hant', '索馬里語'),
(3136, 'so', 'ms', 'Somali'),
(3137, 'sq', 'en', 'Albanian'),
(3138, 'sq', 'es', 'Albanés'),
(3139, 'sq', 'de', 'Albanisch'),
(3140, 'sq', 'fr', 'Albanais'),
(3141, 'sq', 'ar', 'الألبانية'),
(3142, 'sq', 'bs', 'Albanian'),
(3143, 'sq', 'bg', 'Albanian'),
(3144, 'sq', 'ca', 'Albanian'),
(3145, 'sq', 'cs', 'Albanian'),
(3146, 'sq', 'sk', 'Albánčina'),
(3147, 'sq', 'cy', 'Albanian'),
(3148, 'sq', 'da', 'Albanian'),
(3149, 'sq', 'el', 'Αλβανικα'),
(3150, 'sq', 'eo', 'Albanian'),
(3151, 'sq', 'et', 'Albanian'),
(3152, 'sq', 'eu', 'Albanian'),
(3153, 'sq', 'fa', 'Albanian'),
(3154, 'sq', 'fi', 'albania'),
(3155, 'sq', 'ga', 'Albanian'),
(3156, 'sq', 'he', 'Albanian'),
(3157, 'sq', 'hi', 'Albanian'),
(3158, 'sq', 'hr', 'Albanian'),
(3159, 'sq', 'hu', 'albán'),
(3160, 'sq', 'hy', 'Albanian'),
(3161, 'sq', 'id', 'Albanian'),
(3162, 'sq', 'is', 'Albanian'),
(3163, 'sq', 'it', 'Albanese'),
(3164, 'sq', 'ja', 'アルバニア語'),
(3165, 'sq', 'ko', '알바니아어'),
(3166, 'sq', 'ku', 'Albanian'),
(3167, 'sq', 'la', 'Albanian'),
(3168, 'sq', 'lv', 'Albanian'),
(3169, 'sq', 'lt', 'Albanian'),
(3170, 'sq', 'mk', 'Albanian'),
(3171, 'sq', 'mt', 'Albanian'),
(3172, 'sq', 'mo', 'Albanian'),
(3173, 'sq', 'mn', 'Albanian'),
(3174, 'sq', 'ne', 'Albanian'),
(3175, 'sq', 'nl', 'Albaans'),
(3176, 'sq', 'nb', 'Albanian'),
(3177, 'sq', 'pa', 'Albanian'),
(3178, 'sq', 'pl', 'albański'),
(3179, 'sq', 'pt-pt', 'Albanês'),
(3180, 'sq', 'pt-br', 'Albanês'),
(3181, 'sq', 'qu', 'Albanian'),
(3182, 'sq', 'ro', 'Albaneză'),
(3183, 'sq', 'ru', 'Албанский'),
(3184, 'sq', 'sl', 'Albanian'),
(3185, 'sq', 'so', 'Albanian'),
(3186, 'sq', 'sq', 'Albanian'),
(3187, 'sq', 'sr', 'Albanian'),
(3188, 'sq', 'sv', 'Albanska'),
(3189, 'sq', 'ta', 'Albanian'),
(3190, 'sq', 'th', 'อัลเบเนีย'),
(3191, 'sq', 'tr', 'Arnavutça'),
(3192, 'sq', 'uk', 'Albanian'),
(3193, 'sq', 'ur', 'Albanian'),
(3194, 'sq', 'uz', 'Albanian'),
(3195, 'sq', 'vi', 'Albanian'),
(3196, 'sq', 'yi', 'Albanian'),
(3197, 'sq', 'zh-hans', '阿尔巴尼亚语'),
(3198, 'sq', 'zu', 'Albanian'),
(3199, 'sq', 'zh-hant', '阿爾巴尼亞語'),
(3200, 'sq', 'ms', 'Albanian'),
(3201, 'sr', 'en', 'Serbian'),
(3202, 'sr', 'es', 'Serbio'),
(3203, 'sr', 'de', 'Serbisch'),
(3204, 'sr', 'fr', 'Serbe'),
(3205, 'sr', 'ar', 'الصربية'),
(3206, 'sr', 'bs', 'Serbian'),
(3207, 'sr', 'bg', 'Serbian'),
(3208, 'sr', 'ca', 'Serbian'),
(3209, 'sr', 'cs', 'Serbian'),
(3210, 'sr', 'sk', 'Srbština'),
(3211, 'sr', 'cy', 'Serbian'),
(3212, 'sr', 'da', 'Serbian'),
(3213, 'sr', 'el', 'Σερβικα'),
(3214, 'sr', 'eo', 'Serbian');
INSERT INTO `wp_icl_languages_translations` VALUES
(3215, 'sr', 'et', 'Serbian'),
(3216, 'sr', 'eu', 'Serbian'),
(3217, 'sr', 'fa', 'Serbian'),
(3218, 'sr', 'fi', 'serbia'),
(3219, 'sr', 'ga', 'Serbian'),
(3220, 'sr', 'he', 'Serbian'),
(3221, 'sr', 'hi', 'Serbian'),
(3222, 'sr', 'hr', 'Serbian'),
(3223, 'sr', 'hu', 'szerb'),
(3224, 'sr', 'hy', 'Serbian'),
(3225, 'sr', 'id', 'Serbian'),
(3226, 'sr', 'is', 'Serbian'),
(3227, 'sr', 'it', 'Serbo'),
(3228, 'sr', 'ja', 'セルビア語'),
(3229, 'sr', 'ko', '세르비아어'),
(3230, 'sr', 'ku', 'Serbian'),
(3231, 'sr', 'la', 'Serbian'),
(3232, 'sr', 'lv', 'Serbian'),
(3233, 'sr', 'lt', 'Serbian'),
(3234, 'sr', 'mk', 'Serbian'),
(3235, 'sr', 'mt', 'Serbian'),
(3236, 'sr', 'mo', 'Serbian'),
(3237, 'sr', 'mn', 'Serbian'),
(3238, 'sr', 'ne', 'Serbian'),
(3239, 'sr', 'nl', 'Servisch'),
(3240, 'sr', 'nb', 'Serbian'),
(3241, 'sr', 'pa', 'Serbian'),
(3242, 'sr', 'pl', 'serbski'),
(3243, 'sr', 'pt-pt', 'Sérvio'),
(3244, 'sr', 'pt-br', 'Sérvio'),
(3245, 'sr', 'qu', 'Serbian'),
(3246, 'sr', 'ro', 'Sârbă'),
(3247, 'sr', 'ru', 'Сербский'),
(3248, 'sr', 'sl', 'Serbian'),
(3249, 'sr', 'so', 'Serbian'),
(3250, 'sr', 'sq', 'Serbian'),
(3251, 'sr', 'sr', 'Serbian'),
(3252, 'sr', 'sv', 'Serbiska'),
(3253, 'sr', 'ta', 'Serbian'),
(3254, 'sr', 'th', 'เซอร์เบีย'),
(3255, 'sr', 'tr', 'Sırpça'),
(3256, 'sr', 'uk', 'Serbian'),
(3257, 'sr', 'ur', 'Serbian'),
(3258, 'sr', 'uz', 'Serbian'),
(3259, 'sr', 'vi', 'Serbian'),
(3260, 'sr', 'yi', 'Serbian'),
(3261, 'sr', 'zh-hans', '赛尔维亚语'),
(3262, 'sr', 'zu', 'Serbian'),
(3263, 'sr', 'zh-hant', '賽爾維亞語'),
(3264, 'sr', 'ms', 'Serbian'),
(3265, 'sv', 'en', 'Swedish'),
(3266, 'sv', 'es', 'Sueco'),
(3267, 'sv', 'de', 'Schwedisch'),
(3268, 'sv', 'fr', 'Suédois'),
(3269, 'sv', 'ar', 'السويدية'),
(3270, 'sv', 'bs', 'Swedish'),
(3271, 'sv', 'bg', 'Swedish'),
(3272, 'sv', 'ca', 'Swedish'),
(3273, 'sv', 'cs', 'Swedish'),
(3274, 'sv', 'sk', 'Švédština'),
(3275, 'sv', 'cy', 'Swedish'),
(3276, 'sv', 'da', 'Swedish'),
(3277, 'sv', 'el', 'Σουηδικη'),
(3278, 'sv', 'eo', 'Swedish'),
(3279, 'sv', 'et', 'Swedish'),
(3280, 'sv', 'eu', 'Swedish'),
(3281, 'sv', 'fa', 'Swedish'),
(3282, 'sv', 'fi', 'ruotsi'),
(3283, 'sv', 'ga', 'Swedish'),
(3284, 'sv', 'he', 'שוודית'),
(3285, 'sv', 'hi', 'Swedish'),
(3286, 'sv', 'hr', 'Swedish'),
(3287, 'sv', 'hu', 'svéd'),
(3288, 'sv', 'hy', 'Swedish'),
(3289, 'sv', 'id', 'Swedish'),
(3290, 'sv', 'is', 'Swedish'),
(3291, 'sv', 'it', 'Svedese'),
(3292, 'sv', 'ja', 'スウェーデン語'),
(3293, 'sv', 'ko', '스웨덴어'),
(3294, 'sv', 'ku', 'Swedish'),
(3295, 'sv', 'la', 'Swedish'),
(3296, 'sv', 'lv', 'Swedish'),
(3297, 'sv', 'lt', 'Swedish'),
(3298, 'sv', 'mk', 'Swedish'),
(3299, 'sv', 'mt', 'Swedish'),
(3300, 'sv', 'mo', 'Swedish'),
(3301, 'sv', 'mn', 'Swedish'),
(3302, 'sv', 'ne', 'Swedish'),
(3303, 'sv', 'nl', 'Zweeds'),
(3304, 'sv', 'nb', 'Swedish'),
(3305, 'sv', 'pa', 'Swedish'),
(3306, 'sv', 'pl', 'szwedzki'),
(3307, 'sv', 'pt-pt', 'Sueco'),
(3308, 'sv', 'pt-br', 'Sueco'),
(3309, 'sv', 'qu', 'Swedish'),
(3310, 'sv', 'ro', 'Suedeză'),
(3311, 'sv', 'ru', 'Шведский'),
(3312, 'sv', 'sl', 'Swedish'),
(3313, 'sv', 'so', 'Swedish'),
(3314, 'sv', 'sq', 'Swedish'),
(3315, 'sv', 'sr', 'Swedish'),
(3316, 'sv', 'sv', 'Svenska'),
(3317, 'sv', 'ta', 'Swedish'),
(3318, 'sv', 'th', 'สวีเดน'),
(3319, 'sv', 'tr', 'İsveççe'),
(3320, 'sv', 'uk', 'Swedish'),
(3321, 'sv', 'ur', 'Swedish'),
(3322, 'sv', 'uz', 'Swedish'),
(3323, 'sv', 'vi', 'Swedish'),
(3324, 'sv', 'yi', 'Swedish'),
(3325, 'sv', 'zh-hans', '瑞典语'),
(3326, 'sv', 'zu', 'Swedish'),
(3327, 'sv', 'zh-hant', '瑞典語'),
(3328, 'sv', 'ms', 'Swedish'),
(3329, 'ta', 'en', 'Tamil'),
(3330, 'ta', 'es', 'Tamil'),
(3331, 'ta', 'de', 'Tamil'),
(3332, 'ta', 'fr', 'Tamoul'),
(3333, 'ta', 'ar', 'التاميلية'),
(3334, 'ta', 'bs', 'Tamil'),
(3335, 'ta', 'bg', 'Tamil'),
(3336, 'ta', 'ca', 'Tamil'),
(3337, 'ta', 'cs', 'Tamil'),
(3338, 'ta', 'sk', 'Tamilčina'),
(3339, 'ta', 'cy', 'Tamil'),
(3340, 'ta', 'da', 'Tamil'),
(3341, 'ta', 'el', 'Ταμιλ'),
(3342, 'ta', 'eo', 'Tamil'),
(3343, 'ta', 'et', 'Tamil'),
(3344, 'ta', 'eu', 'Tamil'),
(3345, 'ta', 'fa', 'Tamil'),
(3346, 'ta', 'fi', 'tamili'),
(3347, 'ta', 'ga', 'Tamil'),
(3348, 'ta', 'he', 'Tamil'),
(3349, 'ta', 'hi', 'Tamil'),
(3350, 'ta', 'hr', 'Tamil'),
(3351, 'ta', 'hu', 'tamil'),
(3352, 'ta', 'hy', 'Tamil'),
(3353, 'ta', 'id', 'Tamil'),
(3354, 'ta', 'is', 'Tamil'),
(3355, 'ta', 'it', 'Tamil'),
(3356, 'ta', 'ja', 'タミル語'),
(3357, 'ta', 'ko', '타밀어'),
(3358, 'ta', 'ku', 'Tamil'),
(3359, 'ta', 'la', 'Tamil'),
(3360, 'ta', 'lv', 'Tamil'),
(3361, 'ta', 'lt', 'Tamil'),
(3362, 'ta', 'mk', 'Tamil'),
(3363, 'ta', 'mt', 'Tamil'),
(3364, 'ta', 'mo', 'Tamil'),
(3365, 'ta', 'mn', 'Tamil'),
(3366, 'ta', 'ne', 'Tamil'),
(3367, 'ta', 'nl', 'Tamil'),
(3368, 'ta', 'nb', 'Tamil'),
(3369, 'ta', 'pa', 'Tamil'),
(3370, 'ta', 'pl', 'tamilski'),
(3371, 'ta', 'pt-pt', 'Tamil'),
(3372, 'ta', 'pt-br', 'Tamil'),
(3373, 'ta', 'qu', 'Tamil'),
(3374, 'ta', 'ro', 'Tamilă'),
(3375, 'ta', 'ru', 'Тамильский'),
(3376, 'ta', 'sl', 'Tamil'),
(3377, 'ta', 'so', 'Tamil'),
(3378, 'ta', 'sq', 'Tamil'),
(3379, 'ta', 'sr', 'Tamil'),
(3380, 'ta', 'sv', 'Tamil'),
(3381, 'ta', 'ta', 'Tamil'),
(3382, 'ta', 'th', 'ทมิฬ'),
(3383, 'ta', 'tr', 'Tamil dili'),
(3384, 'ta', 'uk', 'Tamil'),
(3385, 'ta', 'ur', 'Tamil'),
(3386, 'ta', 'uz', 'Tamil'),
(3387, 'ta', 'vi', 'Tamil'),
(3388, 'ta', 'yi', 'Tamil'),
(3389, 'ta', 'zh-hans', '泰米尔语'),
(3390, 'ta', 'zu', 'Tamil'),
(3391, 'ta', 'zh-hant', '泰米爾語'),
(3392, 'ta', 'ms', 'Tamil'),
(3393, 'th', 'en', 'Thai'),
(3394, 'th', 'es', 'Tailandés'),
(3395, 'th', 'de', 'Thai'),
(3396, 'th', 'fr', 'Thaï'),
(3397, 'th', 'ar', 'التايلندية'),
(3398, 'th', 'bs', 'Thai'),
(3399, 'th', 'bg', 'Thai'),
(3400, 'th', 'ca', 'Thai'),
(3401, 'th', 'cs', 'Thai'),
(3402, 'th', 'sk', 'Thajština'),
(3403, 'th', 'cy', 'Thai'),
(3404, 'th', 'da', 'Thai'),
(3405, 'th', 'el', 'Thai'),
(3406, 'th', 'eo', 'Thai'),
(3407, 'th', 'et', 'Thai'),
(3408, 'th', 'eu', 'Thai'),
(3409, 'th', 'fa', 'Thai'),
(3410, 'th', 'fi', 'thai'),
(3411, 'th', 'ga', 'Thai'),
(3412, 'th', 'he', 'Thai'),
(3413, 'th', 'hi', 'Thai'),
(3414, 'th', 'hr', 'Thai'),
(3415, 'th', 'hu', 'tájföldi'),
(3416, 'th', 'hy', 'Thai'),
(3417, 'th', 'id', 'Thai'),
(3418, 'th', 'is', 'Thai'),
(3419, 'th', 'it', 'Thai'),
(3420, 'th', 'ja', 'タイ語'),
(3421, 'th', 'ko', '태국어'),
(3422, 'th', 'ku', 'Thai'),
(3423, 'th', 'la', 'Thai'),
(3424, 'th', 'lv', 'Thai'),
(3425, 'th', 'lt', 'Thai'),
(3426, 'th', 'mk', 'Thai'),
(3427, 'th', 'mt', 'Thai'),
(3428, 'th', 'mo', 'Thai'),
(3429, 'th', 'mn', 'Thai'),
(3430, 'th', 'ne', 'Thai'),
(3431, 'th', 'nl', 'Thai'),
(3432, 'th', 'nb', 'Thai'),
(3433, 'th', 'pa', 'Thai'),
(3434, 'th', 'pl', 'tajski'),
(3435, 'th', 'pt-pt', 'Tailandês'),
(3436, 'th', 'pt-br', 'Tailandês'),
(3437, 'th', 'qu', 'Thai'),
(3438, 'th', 'ro', 'Tailandeză'),
(3439, 'th', 'ru', 'Тайский'),
(3440, 'th', 'sl', 'Thai'),
(3441, 'th', 'so', 'Thai'),
(3442, 'th', 'sq', 'Thai'),
(3443, 'th', 'sr', 'Thai'),
(3444, 'th', 'sv', 'Thailändska'),
(3445, 'th', 'ta', 'Thai'),
(3446, 'th', 'th', 'ไทย'),
(3447, 'th', 'tr', 'Tayca'),
(3448, 'th', 'uk', 'Thai'),
(3449, 'th', 'ur', 'Thai'),
(3450, 'th', 'uz', 'Thai'),
(3451, 'th', 'vi', 'Thai'),
(3452, 'th', 'yi', 'Thai'),
(3453, 'th', 'zh-hans', '泰语'),
(3454, 'th', 'zu', 'Thai'),
(3455, 'th', 'zh-hant', '泰語'),
(3456, 'th', 'ms', 'Thai'),
(3457, 'tr', 'en', 'Turkish'),
(3458, 'tr', 'es', 'Turco'),
(3459, 'tr', 'de', 'Türkisch'),
(3460, 'tr', 'fr', 'Turc'),
(3461, 'tr', 'ar', 'التركية'),
(3462, 'tr', 'bs', 'Turkish'),
(3463, 'tr', 'bg', 'Turkish'),
(3464, 'tr', 'ca', 'Turkish'),
(3465, 'tr', 'cs', 'Turkish'),
(3466, 'tr', 'sk', 'Turečtina'),
(3467, 'tr', 'cy', 'Turkish'),
(3468, 'tr', 'da', 'Turkish'),
(3469, 'tr', 'el', 'Τουρκικα'),
(3470, 'tr', 'eo', 'Turkish'),
(3471, 'tr', 'et', 'Turkish'),
(3472, 'tr', 'eu', 'Turkish'),
(3473, 'tr', 'fa', 'Turkish'),
(3474, 'tr', 'fi', 'turkki'),
(3475, 'tr', 'ga', 'Turkish'),
(3476, 'tr', 'he', 'תורכית'),
(3477, 'tr', 'hi', 'Turkish'),
(3478, 'tr', 'hr', 'Turkish'),
(3479, 'tr', 'hu', 'török'),
(3480, 'tr', 'hy', 'Turkish'),
(3481, 'tr', 'id', 'Turkish'),
(3482, 'tr', 'is', 'Turkish'),
(3483, 'tr', 'it', 'Turco'),
(3484, 'tr', 'ja', 'トルコ語'),
(3485, 'tr', 'ko', '터어키어'),
(3486, 'tr', 'ku', 'Turkish'),
(3487, 'tr', 'la', 'Turkish'),
(3488, 'tr', 'lv', 'Turkish'),
(3489, 'tr', 'lt', 'Turkish'),
(3490, 'tr', 'mk', 'Turkish'),
(3491, 'tr', 'mt', 'Turkish'),
(3492, 'tr', 'mo', 'Turkish'),
(3493, 'tr', 'mn', 'Turkish'),
(3494, 'tr', 'ne', 'Turkish'),
(3495, 'tr', 'nl', 'Turks'),
(3496, 'tr', 'nb', 'Turkish'),
(3497, 'tr', 'pa', 'Turkish'),
(3498, 'tr', 'pl', 'turecki'),
(3499, 'tr', 'pt-pt', 'Turco'),
(3500, 'tr', 'pt-br', 'Turco'),
(3501, 'tr', 'qu', 'Turkish'),
(3502, 'tr', 'ro', 'Turcă'),
(3503, 'tr', 'ru', 'Турецкий'),
(3504, 'tr', 'sl', 'Turkish'),
(3505, 'tr', 'so', 'Turkish'),
(3506, 'tr', 'sq', 'Turkish'),
(3507, 'tr', 'sr', 'Turkish'),
(3508, 'tr', 'sv', 'Turkiska'),
(3509, 'tr', 'ta', 'Turkish'),
(3510, 'tr', 'th', 'ตุรกี'),
(3511, 'tr', 'tr', 'Türkçe'),
(3512, 'tr', 'uk', 'Turkish'),
(3513, 'tr', 'ur', 'Turkish'),
(3514, 'tr', 'uz', 'Turkish'),
(3515, 'tr', 'vi', 'Turkish'),
(3516, 'tr', 'yi', 'Turkish'),
(3517, 'tr', 'zh-hans', '土耳其语'),
(3518, 'tr', 'zu', 'Turkish'),
(3519, 'tr', 'zh-hant', '土耳其語'),
(3520, 'tr', 'ms', 'Turkish'),
(3521, 'uk', 'en', 'Ukrainian'),
(3522, 'uk', 'es', 'Ucraniano'),
(3523, 'uk', 'de', 'Ukrainisch'),
(3524, 'uk', 'fr', 'Ukrainien'),
(3525, 'uk', 'ar', 'الأوكرانية'),
(3526, 'uk', 'bs', 'Ukrainian'),
(3527, 'uk', 'bg', 'Ukrainian'),
(3528, 'uk', 'ca', 'Ukrainian'),
(3529, 'uk', 'cs', 'Ukrainian'),
(3530, 'uk', 'sk', 'Ukrajinčina'),
(3531, 'uk', 'cy', 'Ukrainian'),
(3532, 'uk', 'da', 'Ukrainian'),
(3533, 'uk', 'el', 'Ουκρανικα'),
(3534, 'uk', 'eo', 'Ukrainian'),
(3535, 'uk', 'et', 'Ukrainian'),
(3536, 'uk', 'eu', 'Ukrainian'),
(3537, 'uk', 'fa', 'Ukrainian'),
(3538, 'uk', 'fi', 'ukraina'),
(3539, 'uk', 'ga', 'Ukrainian'),
(3540, 'uk', 'he', 'Ukrainian'),
(3541, 'uk', 'hi', 'Ukrainian'),
(3542, 'uk', 'hr', 'Ukrainian'),
(3543, 'uk', 'hu', 'ukrán'),
(3544, 'uk', 'hy', 'Ukrainian'),
(3545, 'uk', 'id', 'Ukrainian'),
(3546, 'uk', 'is', 'Ukrainian'),
(3547, 'uk', 'it', 'Ucraino'),
(3548, 'uk', 'ja', 'ウクライナ語'),
(3549, 'uk', 'ko', '우크라이나어'),
(3550, 'uk', 'ku', 'Ukrainian'),
(3551, 'uk', 'la', 'Ukrainian'),
(3552, 'uk', 'lv', 'Ukrainian'),
(3553, 'uk', 'lt', 'Ukrainian'),
(3554, 'uk', 'mk', 'Ukrainian'),
(3555, 'uk', 'mt', 'Ukrainian'),
(3556, 'uk', 'mo', 'Ukrainian'),
(3557, 'uk', 'mn', 'Ukrainian'),
(3558, 'uk', 'ne', 'Ukrainian'),
(3559, 'uk', 'nl', 'Oekraïens'),
(3560, 'uk', 'nb', 'Ukrainian'),
(3561, 'uk', 'pa', 'Ukrainian'),
(3562, 'uk', 'pl', 'ukraiński'),
(3563, 'uk', 'pt-pt', 'Ucraniano'),
(3564, 'uk', 'pt-br', 'Ucraniano'),
(3565, 'uk', 'qu', 'Ukrainian'),
(3566, 'uk', 'ro', 'Ucrainiană'),
(3567, 'uk', 'ru', 'Украинский'),
(3568, 'uk', 'sl', 'Ukrainian'),
(3569, 'uk', 'so', 'Ukrainian'),
(3570, 'uk', 'sq', 'Ukrainian'),
(3571, 'uk', 'sr', 'Ukrainian'),
(3572, 'uk', 'sv', 'Ukrainska'),
(3573, 'uk', 'ta', 'Ukrainian'),
(3574, 'uk', 'th', 'ยูเครน'),
(3575, 'uk', 'tr', 'Ukraynaca'),
(3576, 'uk', 'uk', 'Ukrainian'),
(3577, 'uk', 'ur', 'Ukrainian'),
(3578, 'uk', 'uz', 'Ukrainian'),
(3579, 'uk', 'vi', 'Ukrainian'),
(3580, 'uk', 'yi', 'Ukrainian'),
(3581, 'uk', 'zh-hans', '乌克兰语'),
(3582, 'uk', 'zu', 'Ukrainian'),
(3583, 'uk', 'zh-hant', '烏克蘭語'),
(3584, 'uk', 'ms', 'Ukrainian'),
(3585, 'ur', 'en', 'Urdu'),
(3586, 'ur', 'es', 'Urdu'),
(3587, 'ur', 'de', 'Urdu'),
(3588, 'ur', 'fr', 'Ourdu'),
(3589, 'ur', 'ar', 'الأردية'),
(3590, 'ur', 'bs', 'Urdu'),
(3591, 'ur', 'bg', 'Urdu'),
(3592, 'ur', 'ca', 'Urdu'),
(3593, 'ur', 'cs', 'Urdu'),
(3594, 'ur', 'sk', 'Urdština'),
(3595, 'ur', 'cy', 'Urdu'),
(3596, 'ur', 'da', 'Urdu'),
(3597, 'ur', 'el', 'Ουρντου'),
(3598, 'ur', 'eo', 'Urdu'),
(3599, 'ur', 'et', 'Urdu'),
(3600, 'ur', 'eu', 'Urdu'),
(3601, 'ur', 'fa', 'Urdu'),
(3602, 'ur', 'fi', 'urdu'),
(3603, 'ur', 'ga', 'Urdu'),
(3604, 'ur', 'he', 'Urdu'),
(3605, 'ur', 'hi', 'Urdu'),
(3606, 'ur', 'hr', 'Urdu'),
(3607, 'ur', 'hu', 'urdu'),
(3608, 'ur', 'hy', 'Urdu'),
(3609, 'ur', 'id', 'Urdu'),
(3610, 'ur', 'is', 'Urdu'),
(3611, 'ur', 'it', 'Urdu'),
(3612, 'ur', 'ja', 'ウルドゥー語'),
(3613, 'ur', 'ko', '우르두어'),
(3614, 'ur', 'ku', 'Urdu'),
(3615, 'ur', 'la', 'Urdu'),
(3616, 'ur', 'lv', 'Urdu'),
(3617, 'ur', 'lt', 'Urdu'),
(3618, 'ur', 'mk', 'Urdu'),
(3619, 'ur', 'mt', 'Urdu'),
(3620, 'ur', 'mo', 'Urdu'),
(3621, 'ur', 'mn', 'Urdu'),
(3622, 'ur', 'ne', 'Urdu'),
(3623, 'ur', 'nl', 'Urdu'),
(3624, 'ur', 'nb', 'Urdu'),
(3625, 'ur', 'pa', 'Urdu'),
(3626, 'ur', 'pl', 'urdu'),
(3627, 'ur', 'pt-pt', 'Urdu'),
(3628, 'ur', 'pt-br', 'Urdu'),
(3629, 'ur', 'qu', 'Urdu'),
(3630, 'ur', 'ro', 'Urdu'),
(3631, 'ur', 'ru', 'Урду'),
(3632, 'ur', 'sl', 'Urdu'),
(3633, 'ur', 'so', 'Urdu'),
(3634, 'ur', 'sq', 'Urdu'),
(3635, 'ur', 'sr', 'Urdu'),
(3636, 'ur', 'sv', 'Urdu'),
(3637, 'ur', 'ta', 'Urdu'),
(3638, 'ur', 'th', 'อุรดู'),
(3639, 'ur', 'tr', 'Urduca'),
(3640, 'ur', 'uk', 'Urdu'),
(3641, 'ur', 'ur', 'Urdu'),
(3642, 'ur', 'uz', 'Urdu'),
(3643, 'ur', 'vi', 'Urdu'),
(3644, 'ur', 'yi', 'Urdu'),
(3645, 'ur', 'zh-hans', '乌尔都语'),
(3646, 'ur', 'zu', 'Urdu'),
(3647, 'ur', 'zh-hant', '烏爾都語'),
(3648, 'ur', 'ms', 'Urdu'),
(3649, 'uz', 'en', 'Uzbek'),
(3650, 'uz', 'es', 'Uzbeko'),
(3651, 'uz', 'de', 'Usbekisch'),
(3652, 'uz', 'fr', 'Ouzbek'),
(3653, 'uz', 'ar', 'الاوزباكية'),
(3654, 'uz', 'bs', 'Uzbek'),
(3655, 'uz', 'bg', 'Uzbek'),
(3656, 'uz', 'ca', 'Uzbek'),
(3657, 'uz', 'cs', 'Uzbek'),
(3658, 'uz', 'sk', 'Uzbekčina'),
(3659, 'uz', 'cy', 'Uzbek'),
(3660, 'uz', 'da', 'Uzbek'),
(3661, 'uz', 'el', 'Ουζμπεκικα'),
(3662, 'uz', 'eo', 'Uzbek'),
(3663, 'uz', 'et', 'Uzbek'),
(3664, 'uz', 'eu', 'Uzbek'),
(3665, 'uz', 'fa', 'Uzbek'),
(3666, 'uz', 'fi', 'uzbekki'),
(3667, 'uz', 'ga', 'Uzbek'),
(3668, 'uz', 'he', 'Uzbek'),
(3669, 'uz', 'hi', 'Uzbek'),
(3670, 'uz', 'hr', 'Uzbek'),
(3671, 'uz', 'hu', 'üzbég'),
(3672, 'uz', 'hy', 'Uzbek'),
(3673, 'uz', 'id', 'Uzbek'),
(3674, 'uz', 'is', 'Uzbek'),
(3675, 'uz', 'it', 'Uzbeco'),
(3676, 'uz', 'ja', 'ウズベク語'),
(3677, 'uz', 'ko', '우즈베크어'),
(3678, 'uz', 'ku', 'Uzbek'),
(3679, 'uz', 'la', 'Uzbek'),
(3680, 'uz', 'lv', 'Uzbek'),
(3681, 'uz', 'lt', 'Uzbek'),
(3682, 'uz', 'mk', 'Uzbek'),
(3683, 'uz', 'mt', 'Uzbek'),
(3684, 'uz', 'mo', 'Uzbek'),
(3685, 'uz', 'mn', 'Uzbek'),
(3686, 'uz', 'ne', 'Uzbek'),
(3687, 'uz', 'nl', 'Oezbeeks'),
(3688, 'uz', 'nb', 'Uzbek'),
(3689, 'uz', 'pa', 'Uzbek'),
(3690, 'uz', 'pl', 'uzbecki'),
(3691, 'uz', 'pt-pt', 'Uzbeque'),
(3692, 'uz', 'pt-br', 'Uzbeque'),
(3693, 'uz', 'qu', 'Uzbek'),
(3694, 'uz', 'ro', 'Uzbecă'),
(3695, 'uz', 'ru', 'Узбекский'),
(3696, 'uz', 'sl', 'Uzbek'),
(3697, 'uz', 'so', 'Uzbek'),
(3698, 'uz', 'sq', 'Uzbek'),
(3699, 'uz', 'sr', 'Uzbek'),
(3700, 'uz', 'sv', 'Uzbekiska'),
(3701, 'uz', 'ta', 'Uzbek'),
(3702, 'uz', 'th', 'อุซเบก'),
(3703, 'uz', 'tr', 'Özbekçe'),
(3704, 'uz', 'uk', 'Uzbek'),
(3705, 'uz', 'ur', 'Uzbek'),
(3706, 'uz', 'uz', 'Uzbek'),
(3707, 'uz', 'vi', 'Uzbek'),
(3708, 'uz', 'yi', 'Uzbek'),
(3709, 'uz', 'zh-hans', '乌兹别克语'),
(3710, 'uz', 'zu', 'Uzbek'),
(3711, 'uz', 'zh-hant', '烏茲別克語'),
(3712, 'uz', 'ms', 'Uzbek'),
(3713, 'vi', 'en', 'Vietnamese'),
(3714, 'vi', 'es', 'Vietnamita'),
(3715, 'vi', 'de', 'Vietnamesisch'),
(3716, 'vi', 'fr', 'Vietnamien'),
(3717, 'vi', 'ar', 'الفيتنامية'),
(3718, 'vi', 'bs', 'Vietnamese'),
(3719, 'vi', 'bg', 'Vietnamese'),
(3720, 'vi', 'ca', 'Vietnamese'),
(3721, 'vi', 'cs', 'Vietnamese'),
(3722, 'vi', 'sk', 'Vietnamčina'),
(3723, 'vi', 'cy', 'Vietnamese'),
(3724, 'vi', 'da', 'Vietnamese'),
(3725, 'vi', 'el', 'Βιετναμεζικα'),
(3726, 'vi', 'eo', 'Vietnamese'),
(3727, 'vi', 'et', 'Vietnamese'),
(3728, 'vi', 'eu', 'Vietnamese'),
(3729, 'vi', 'fa', 'Vietnamese'),
(3730, 'vi', 'fi', 'vietnam'),
(3731, 'vi', 'ga', 'Vietnamese'),
(3732, 'vi', 'he', 'Vietnamese'),
(3733, 'vi', 'hi', 'Vietnamese'),
(3734, 'vi', 'hr', 'Vietnamese'),
(3735, 'vi', 'hu', 'vietnámi'),
(3736, 'vi', 'hy', 'Vietnamese'),
(3737, 'vi', 'id', 'Vietnamese'),
(3738, 'vi', 'is', 'Vietnamese'),
(3739, 'vi', 'it', 'Vietnamita'),
(3740, 'vi', 'ja', 'ベトナム語'),
(3741, 'vi', 'ko', '베트남어'),
(3742, 'vi', 'ku', 'Vietnamese'),
(3743, 'vi', 'la', 'Vietnamese'),
(3744, 'vi', 'lv', 'Vietnamese'),
(3745, 'vi', 'lt', 'Vietnamese'),
(3746, 'vi', 'mk', 'Vietnamese'),
(3747, 'vi', 'mt', 'Vietnamese'),
(3748, 'vi', 'mo', 'Vietnamese'),
(3749, 'vi', 'mn', 'Vietnamese'),
(3750, 'vi', 'ne', 'Vietnamese'),
(3751, 'vi', 'nl', 'Vietnamees'),
(3752, 'vi', 'nb', 'Vietnamese'),
(3753, 'vi', 'pa', 'Vietnamese'),
(3754, 'vi', 'pl', 'wietnamski'),
(3755, 'vi', 'pt-pt', 'Vietnamita'),
(3756, 'vi', 'pt-br', 'Vietnamita'),
(3757, 'vi', 'qu', 'Vietnamese'),
(3758, 'vi', 'ro', 'Vietnameză'),
(3759, 'vi', 'ru', 'Вьетнамский'),
(3760, 'vi', 'sl', 'Vietnamese'),
(3761, 'vi', 'so', 'Vietnamese'),
(3762, 'vi', 'sq', 'Vietnamese'),
(3763, 'vi', 'sr', 'Vietnamese'),
(3764, 'vi', 'sv', 'Vietnamesiska'),
(3765, 'vi', 'ta', 'Vietnamese'),
(3766, 'vi', 'th', 'เวียดนาม'),
(3767, 'vi', 'tr', 'Vietnamca'),
(3768, 'vi', 'uk', 'Vietnamese'),
(3769, 'vi', 'ur', 'Vietnamese'),
(3770, 'vi', 'uz', 'Vietnamese'),
(3771, 'vi', 'vi', 'Vietnamese'),
(3772, 'vi', 'yi', 'Vietnamese'),
(3773, 'vi', 'zh-hans', '越南语'),
(3774, 'vi', 'zu', 'Vietnamese'),
(3775, 'vi', 'zh-hant', '越南語'),
(3776, 'vi', 'ms', 'Vietnamese'),
(3777, 'yi', 'en', 'Yiddish'),
(3778, 'yi', 'es', 'Yidis'),
(3779, 'yi', 'de', 'Jiddisch'),
(3780, 'yi', 'fr', 'Yiddish'),
(3781, 'yi', 'ar', 'اليديشية'),
(3782, 'yi', 'bs', 'Yiddish'),
(3783, 'yi', 'bg', 'Yiddish'),
(3784, 'yi', 'ca', 'Yiddish'),
(3785, 'yi', 'cs', 'Yiddish'),
(3786, 'yi', 'sk', 'Jidiš'),
(3787, 'yi', 'cy', 'Yiddish'),
(3788, 'yi', 'da', 'Yiddish'),
(3789, 'yi', 'el', 'Γιντις'),
(3790, 'yi', 'eo', 'Yiddish'),
(3791, 'yi', 'et', 'Yiddish'),
(3792, 'yi', 'eu', 'Yiddish'),
(3793, 'yi', 'fa', 'Yiddish'),
(3794, 'yi', 'fi', 'jiddi'),
(3795, 'yi', 'ga', 'Yiddish'),
(3796, 'yi', 'he', 'יידיש'),
(3797, 'yi', 'hi', 'Yiddish'),
(3798, 'yi', 'hr', 'Yiddish'),
(3799, 'yi', 'hu', 'jiddis'),
(3800, 'yi', 'hy', 'Yiddish'),
(3801, 'yi', 'id', 'Yiddish'),
(3802, 'yi', 'is', 'Yiddish'),
(3803, 'yi', 'it', 'Yiddish'),
(3804, 'yi', 'ja', 'イディッシュ語'),
(3805, 'yi', 'ko', '이디시어'),
(3806, 'yi', 'ku', 'Yiddish'),
(3807, 'yi', 'la', 'Yiddish'),
(3808, 'yi', 'lv', 'Yiddish'),
(3809, 'yi', 'lt', 'Yiddish'),
(3810, 'yi', 'mk', 'Yiddish'),
(3811, 'yi', 'mt', 'Yiddish'),
(3812, 'yi', 'mo', 'Yiddish'),
(3813, 'yi', 'mn', 'Yiddish'),
(3814, 'yi', 'ne', 'Yiddish'),
(3815, 'yi', 'nl', 'Jiddisch'),
(3816, 'yi', 'nb', 'Yiddish'),
(3817, 'yi', 'pa', 'Yiddish'),
(3818, 'yi', 'pl', 'jidysz'),
(3819, 'yi', 'pt-pt', 'Yiddish'),
(3820, 'yi', 'pt-br', 'Yiddish'),
(3821, 'yi', 'qu', 'Yiddish'),
(3822, 'yi', 'ro', 'Idiş'),
(3823, 'yi', 'ru', 'Идиш'),
(3824, 'yi', 'sl', 'Yiddish'),
(3825, 'yi', 'so', 'Yiddish'),
(3826, 'yi', 'sq', 'Yiddish'),
(3827, 'yi', 'sr', 'Yiddish'),
(3828, 'yi', 'sv', 'Jiddisch'),
(3829, 'yi', 'ta', 'Yiddish'),
(3830, 'yi', 'th', 'ยิชดิช'),
(3831, 'yi', 'tr', 'Eski İbranice'),
(3832, 'yi', 'uk', 'Yiddish'),
(3833, 'yi', 'ur', 'Yiddish'),
(3834, 'yi', 'uz', 'Yiddish'),
(3835, 'yi', 'vi', 'Yiddish'),
(3836, 'yi', 'yi', 'Yiddish'),
(3837, 'yi', 'zh-hans', '依地语'),
(3838, 'yi', 'zu', 'Yiddish'),
(3839, 'yi', 'zh-hant', '依地語'),
(3840, 'yi', 'ms', 'Yiddish'),
(3841, 'zh-hans', 'en', 'Chinese (Simplified)'),
(3842, 'zh-hans', 'es', 'Chino simplificado'),
(3843, 'zh-hans', 'de', 'Vereinfachtes Chinesisch'),
(3844, 'zh-hans', 'fr', 'Chinois simplifié'),
(3845, 'zh-hans', 'ar', 'الصينية المبسطة'),
(3846, 'zh-hans', 'bs', 'Chinese (Simplified)'),
(3847, 'zh-hans', 'bg', 'Chinese (Simplified)'),
(3848, 'zh-hans', 'ca', 'Chinese (Simplified)'),
(3849, 'zh-hans', 'cs', 'Chinese (Simplified)'),
(3850, 'zh-hans', 'sk', 'Zjednodušená Čínština'),
(3851, 'zh-hans', 'cy', 'Chinese (Simplified)'),
(3852, 'zh-hans', 'da', 'Chinese (Simplified)'),
(3853, 'zh-hans', 'el', 'Κινεζικα'),
(3854, 'zh-hans', 'eo', 'Chinese (Simplified)'),
(3855, 'zh-hans', 'et', 'Chinese (Simplified)'),
(3856, 'zh-hans', 'eu', 'Chinese (Simplified)'),
(3857, 'zh-hans', 'fa', 'Chinese (Simplified)'),
(3858, 'zh-hans', 'fi', 'kiina'),
(3859, 'zh-hans', 'ga', 'Chinese (Simplified)'),
(3860, 'zh-hans', 'he', 'סינית'),
(3861, 'zh-hans', 'hi', 'Chinese (Simplified)'),
(3862, 'zh-hans', 'hr', 'Chinese (Simplified)'),
(3863, 'zh-hans', 'hu', 'egyszerűsített kínai'),
(3864, 'zh-hans', 'hy', 'Chinese (Simplified)'),
(3865, 'zh-hans', 'id', 'Chinese (Simplified)'),
(3866, 'zh-hans', 'is', 'Chinese (Simplified)'),
(3867, 'zh-hans', 'it', 'Cinese semplificato'),
(3868, 'zh-hans', 'ja', '簡体中国語'),
(3869, 'zh-hans', 'ko', '중국어 간체'),
(3870, 'zh-hans', 'ku', 'Chinese (Simplified)'),
(3871, 'zh-hans', 'la', 'Chinese (Simplified)'),
(3872, 'zh-hans', 'lv', 'Chinese (Simplified)'),
(3873, 'zh-hans', 'lt', 'Chinese (Simplified)'),
(3874, 'zh-hans', 'mk', 'Chinese (Simplified)'),
(3875, 'zh-hans', 'mt', 'Chinese (Simplified)'),
(3876, 'zh-hans', 'mo', 'Chinese (Simplified)'),
(3877, 'zh-hans', 'mn', 'Chinese (Simplified)'),
(3878, 'zh-hans', 'ne', 'Chinese (Simplified)'),
(3879, 'zh-hans', 'nl', 'Vereenvoudigd Chinees'),
(3880, 'zh-hans', 'nb', 'Chinese (Simplified)'),
(3881, 'zh-hans', 'pa', 'Chinese (Simplified)'),
(3882, 'zh-hans', 'pl', 'chiński uproszczony'),
(3883, 'zh-hans', 'pt-pt', 'Chinês'),
(3884, 'zh-hans', 'pt-br', 'Chinês'),
(3885, 'zh-hans', 'qu', 'Chinese (Simplified)'),
(3886, 'zh-hans', 'ro', 'Chineza simplificată'),
(3887, 'zh-hans', 'ru', 'Упрощенный китайский'),
(3888, 'zh-hans', 'sl', 'Chinese (Simplified)'),
(3889, 'zh-hans', 'so', 'Chinese (Simplified)'),
(3890, 'zh-hans', 'sq', 'Chinese (Simplified)'),
(3891, 'zh-hans', 'sr', 'Chinese (Simplified)'),
(3892, 'zh-hans', 'sv', 'Förenklad kinesiska'),
(3893, 'zh-hans', 'ta', 'Chinese (Simplified)'),
(3894, 'zh-hans', 'th', 'จีนประยุกต์'),
(3895, 'zh-hans', 'tr', 'Modern Çince'),
(3896, 'zh-hans', 'uk', 'Chinese (Simplified)'),
(3897, 'zh-hans', 'ur', 'Chinese (Simplified)'),
(3898, 'zh-hans', 'uz', 'Chinese (Simplified)'),
(3899, 'zh-hans', 'vi', 'Chinese (Simplified)'),
(3900, 'zh-hans', 'yi', 'Chinese (Simplified)'),
(3901, 'zh-hans', 'zh-hans', '简体中文'),
(3902, 'zh-hans', 'zu', 'Chinese (Simplified)'),
(3903, 'zh-hans', 'zh-hant', '簡體中文'),
(3904, 'zh-hans', 'ms', 'Chinese (Simplified)'),
(3905, 'zu', 'en', 'Zulu'),
(3906, 'zu', 'es', 'Zulú'),
(3907, 'zu', 'de', 'Zulu'),
(3908, 'zu', 'fr', 'Zoulou'),
(3909, 'zu', 'ar', 'الزولو'),
(3910, 'zu', 'bs', 'Zulu'),
(3911, 'zu', 'bg', 'Zulu'),
(3912, 'zu', 'ca', 'Zulu'),
(3913, 'zu', 'cs', 'Zulu'),
(3914, 'zu', 'sk', 'Jazyk Zulu'),
(3915, 'zu', 'cy', 'Zulu'),
(3916, 'zu', 'da', 'Zulu'),
(3917, 'zu', 'el', 'Ζουλου'),
(3918, 'zu', 'eo', 'Zulu'),
(3919, 'zu', 'et', 'Zulu'),
(3920, 'zu', 'eu', 'Zulu'),
(3921, 'zu', 'fa', 'Zulu'),
(3922, 'zu', 'fi', 'zulu'),
(3923, 'zu', 'ga', 'Zulu'),
(3924, 'zu', 'he', 'Zulu'),
(3925, 'zu', 'hi', 'Zulu'),
(3926, 'zu', 'hr', 'Zulu'),
(3927, 'zu', 'hu', 'zulu'),
(3928, 'zu', 'hy', 'Zulu'),
(3929, 'zu', 'id', 'Zulu'),
(3930, 'zu', 'is', 'Zulu'),
(3931, 'zu', 'it', 'Zulu'),
(3932, 'zu', 'ja', 'ズールー語'),
(3933, 'zu', 'ko', '줄루어'),
(3934, 'zu', 'ku', 'Zulu'),
(3935, 'zu', 'la', 'Zulu'),
(3936, 'zu', 'lv', 'Zulu'),
(3937, 'zu', 'lt', 'Zulu'),
(3938, 'zu', 'mk', 'Zulu'),
(3939, 'zu', 'mt', 'Zulu'),
(3940, 'zu', 'mo', 'Zulu'),
(3941, 'zu', 'mn', 'Zulu'),
(3942, 'zu', 'ne', 'Zulu'),
(3943, 'zu', 'nl', 'Zulu'),
(3944, 'zu', 'nb', 'Zulu'),
(3945, 'zu', 'pa', 'Zulu'),
(3946, 'zu', 'pl', 'zuluski'),
(3947, 'zu', 'pt-pt', 'Zulu'),
(3948, 'zu', 'pt-br', 'Zulu'),
(3949, 'zu', 'qu', 'Zulu'),
(3950, 'zu', 'ro', 'Zulu'),
(3951, 'zu', 'ru', 'Зулу'),
(3952, 'zu', 'sl', 'Zulu'),
(3953, 'zu', 'so', 'Zulu'),
(3954, 'zu', 'sq', 'Zulu'),
(3955, 'zu', 'sr', 'Zulu'),
(3956, 'zu', 'sv', 'Zulu'),
(3957, 'zu', 'ta', 'Zulu'),
(3958, 'zu', 'th', 'ซูลู'),
(3959, 'zu', 'tr', 'Zulu dili'),
(3960, 'zu', 'uk', 'Zulu'),
(3961, 'zu', 'ur', 'Zulu'),
(3962, 'zu', 'uz', 'Zulu'),
(3963, 'zu', 'vi', 'Zulu'),
(3964, 'zu', 'yi', 'Zulu'),
(3965, 'zu', 'zh-hans', '祖鲁语'),
(3966, 'zu', 'zu', 'Zulu'),
(3967, 'zu', 'zh-hant', '祖魯語'),
(3968, 'zu', 'ms', 'Zulu'),
(3969, 'zh-hant', 'en', 'Chinese (Traditional)'),
(3970, 'zh-hant', 'es', 'Chino tradicional'),
(3971, 'zh-hant', 'de', 'Traditionelles Chinesisch'),
(3972, 'zh-hant', 'fr', 'Chinois traditionnel'),
(3973, 'zh-hant', 'ar', 'الصينية التقليدية'),
(3974, 'zh-hant', 'bs', 'Chinese (Traditional)'),
(3975, 'zh-hant', 'bg', 'Chinese (Traditional)'),
(3976, 'zh-hant', 'ca', 'Chinese (Traditional)'),
(3977, 'zh-hant', 'cs', 'Chinese (Traditional)'),
(3978, 'zh-hant', 'sk', 'Tradičná Čínština'),
(3979, 'zh-hant', 'cy', 'Chinese (Traditional)'),
(3980, 'zh-hant', 'da', 'Chinese (Traditional)'),
(3981, 'zh-hant', 'el', 'Κινεζικα'),
(3982, 'zh-hant', 'eo', 'Chinese (Traditional)'),
(3983, 'zh-hant', 'et', 'Chinese (Traditional)'),
(3984, 'zh-hant', 'eu', 'Chinese (Traditional)'),
(3985, 'zh-hant', 'fa', 'Chinese (Traditional)'),
(3986, 'zh-hant', 'fi', 'perinteinen kiina'),
(3987, 'zh-hant', 'ga', 'Chinese (Traditional)'),
(3988, 'zh-hant', 'he', 'סינית מסורתית'),
(3989, 'zh-hant', 'hi', 'Chinese (Traditional)'),
(3990, 'zh-hant', 'hr', 'Chinese (Traditional)'),
(3991, 'zh-hant', 'hu', 'hagyományos kínai'),
(3992, 'zh-hant', 'hy', 'Chinese (Traditional)'),
(3993, 'zh-hant', 'id', 'Chinese (Traditional)'),
(3994, 'zh-hant', 'is', 'Chinese (Traditional)'),
(3995, 'zh-hant', 'it', 'Cinese tradizionale'),
(3996, 'zh-hant', 'ja', '繁体中国語'),
(3997, 'zh-hant', 'ko', '중국어 번체'),
(3998, 'zh-hant', 'ku', 'Chinese (Traditional)'),
(3999, 'zh-hant', 'la', 'Chinese (Traditional)'),
(4000, 'zh-hant', 'lv', 'Chinese (Traditional)'),
(4001, 'zh-hant', 'lt', 'Chinese (Traditional)'),
(4002, 'zh-hant', 'mk', 'Chinese (Traditional)'),
(4003, 'zh-hant', 'mt', 'Chinese (Traditional)'),
(4004, 'zh-hant', 'mo', 'Chinese (Traditional)'),
(4005, 'zh-hant', 'mn', 'Chinese (Traditional)'),
(4006, 'zh-hant', 'ne', 'Chinese (Traditional)'),
(4007, 'zh-hant', 'nl', 'Traditioneel Chinees'),
(4008, 'zh-hant', 'nb', 'Chinese (Traditional)'),
(4009, 'zh-hant', 'pa', 'Chinese (Traditional)'),
(4010, 'zh-hant', 'pl', 'chiński tradycyjny'),
(4011, 'zh-hant', 'pt-pt', 'Chinês'),
(4012, 'zh-hant', 'pt-br', 'Chinês'),
(4013, 'zh-hant', 'qu', 'Chinese (Traditional)'),
(4014, 'zh-hant', 'ro', 'Chineza tradiţională'),
(4015, 'zh-hant', 'ru', 'Традиционный китайский'),
(4016, 'zh-hant', 'sl', 'Chinese (Traditional)'),
(4017, 'zh-hant', 'so', 'Chinese (Traditional)'),
(4018, 'zh-hant', 'sq', 'Chinese (Traditional)'),
(4019, 'zh-hant', 'sr', 'Chinese (Traditional)'),
(4020, 'zh-hant', 'sv', 'Traditionell kinesiska'),
(4021, 'zh-hant', 'ta', 'Chinese (Traditional)'),
(4022, 'zh-hant', 'th', 'จีนดั้งเดิม'),
(4023, 'zh-hant', 'tr', 'Klasik Çince'),
(4024, 'zh-hant', 'uk', 'Chinese (Traditional)'),
(4025, 'zh-hant', 'ur', 'Chinese (Traditional)'),
(4026, 'zh-hant', 'uz', 'Chinese (Traditional)'),
(4027, 'zh-hant', 'vi', 'Chinese (Traditional)'),
(4028, 'zh-hant', 'yi', 'Chinese (Traditional)'),
(4029, 'zh-hant', 'zh-hans', '繁体中文'),
(4030, 'zh-hant', 'zu', 'Chinese (Traditional)'),
(4031, 'zh-hant', 'zh-hant', '繁體中文'),
(4032, 'zh-hant', 'ms', 'Chinese (Traditional)'),
(4033, 'ms', 'en', 'Malay'),
(4034, 'ms', 'es', 'Malayo'),
(4035, 'ms', 'de', 'Malay'),
(4036, 'ms', 'fr', 'Malay'),
(4037, 'ms', 'ar', 'Malay'),
(4038, 'ms', 'bs', 'Malay'),
(4039, 'ms', 'bg', 'Malay'),
(4040, 'ms', 'ca', 'Malay'),
(4041, 'ms', 'cs', 'Malay'),
(4042, 'ms', 'sk', 'Malay'),
(4043, 'ms', 'cy', 'Malay'),
(4044, 'ms', 'da', 'Malay'),
(4045, 'ms', 'el', 'Malay'),
(4046, 'ms', 'eo', 'Malay'),
(4047, 'ms', 'et', 'Malay'),
(4048, 'ms', 'eu', 'Malay'),
(4049, 'ms', 'fa', 'Malay'),
(4050, 'ms', 'fi', 'Malay'),
(4051, 'ms', 'ga', 'Malay'),
(4052, 'ms', 'he', 'Malay'),
(4053, 'ms', 'hi', 'Malay'),
(4054, 'ms', 'hr', 'Malay'),
(4055, 'ms', 'hu', 'Malay'),
(4056, 'ms', 'hy', 'Malay'),
(4057, 'ms', 'id', 'Malay'),
(4058, 'ms', 'is', 'Malay'),
(4059, 'ms', 'it', 'Malay'),
(4060, 'ms', 'ja', 'Malay'),
(4061, 'ms', 'ko', 'Malay'),
(4062, 'ms', 'ku', 'Malay'),
(4063, 'ms', 'la', 'Malay'),
(4064, 'ms', 'lv', 'Malay'),
(4065, 'ms', 'lt', 'Malay'),
(4066, 'ms', 'mk', 'Malay'),
(4067, 'ms', 'mt', 'Malay'),
(4068, 'ms', 'mo', 'Malay'),
(4069, 'ms', 'mn', 'Malay'),
(4070, 'ms', 'ne', 'Malay'),
(4071, 'ms', 'nl', 'Malay'),
(4072, 'ms', 'nb', 'Malay'),
(4073, 'ms', 'pa', 'Malay'),
(4074, 'ms', 'pl', 'Malay'),
(4075, 'ms', 'pt-pt', 'Malay'),
(4076, 'ms', 'pt-br', 'Malay'),
(4077, 'ms', 'qu', 'Malay'),
(4078, 'ms', 'ro', 'Malay'),
(4079, 'ms', 'ru', 'Malay'),
(4080, 'ms', 'sl', 'Malay'),
(4081, 'ms', 'so', 'Malay'),
(4082, 'ms', 'sq', 'Malay'),
(4083, 'ms', 'sr', 'Malay'),
(4084, 'ms', 'sv', 'Malay'),
(4085, 'ms', 'ta', 'Malay'),
(4086, 'ms', 'th', 'Malay'),
(4087, 'ms', 'tr', 'Malay'),
(4088, 'ms', 'uk', 'Malay'),
(4089, 'ms', 'ur', 'Malay'),
(4090, 'ms', 'uz', 'Malay'),
(4091, 'ms', 'vi', 'Malay'),
(4092, 'ms', 'yi', 'Malay'),
(4093, 'ms', 'zh-hans', 'Malay'),
(4094, 'ms', 'zu', 'Malay'),
(4095, 'ms', 'zh-hant', 'Malay'),
(4096, 'ms', 'ms', 'Melayu');

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_locale_map`
--

CREATE TABLE `wp_icl_locale_map` (
  `code` varchar(7) NOT NULL,
  `locale` varchar(8) NOT NULL,
  UNIQUE KEY `code` (`code`,`locale`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table 'wp_icl_locale_map'
--

INSERT INTO `wp_icl_locale_map` VALUES
('en', 'en_US'),
('fr', 'fr_FR'),
('it', 'it_IT'),
('ru', 'ru_RU');

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_message_status`
--

CREATE TABLE `wp_icl_message_status` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) unsigned NOT NULL,
  `object_id` bigint(20) unsigned NOT NULL,
  `from_language` varchar(10) NOT NULL,
  `to_language` varchar(10) NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `md5` varchar(32) NOT NULL,
  `object_type` varchar(64) NOT NULL,
  `status` smallint(6) NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `rid` (`rid`),
  KEY `object_id` (`object_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_node`
--

CREATE TABLE `wp_icl_node` (
  `nid` bigint(20) NOT NULL,
  `md5` varchar(32) NOT NULL,
  `links_fixed` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`nid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_reminders`
--

CREATE TABLE `wp_icl_reminders` (
  `id` bigint(20) NOT NULL,
  `message` text NOT NULL,
  `url` text NOT NULL,
  `can_delete` tinyint(4) NOT NULL,
  `show` tinyint(4) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_strings`
--

CREATE TABLE `wp_icl_strings` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `language` varchar(7) NOT NULL,
  `context` varchar(160) NOT NULL,
  `name` varchar(160) NOT NULL,
  `value` text NOT NULL,
  `status` tinyint(4) NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `context_name` (`context`,`name`),
  KEY `language_context` (`language`,`context`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_string_positions`
--

CREATE TABLE `wp_icl_string_positions` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `string_id` bigint(20) NOT NULL,
  `kind` tinyint(4) DEFAULT NULL,
  `position_in_page` varchar(255) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `string_id` (`string_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_string_status`
--

CREATE TABLE `wp_icl_string_status` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) NOT NULL,
  `string_translation_id` bigint(20) NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `md5` varchar(32) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `string_translation_id` (`string_translation_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_string_translations`
--

CREATE TABLE `wp_icl_string_translations` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `string_id` bigint(20) unsigned NOT NULL,
  `language` varchar(10) NOT NULL,
  `status` tinyint(4) NOT NULL,
  `value` text,
  `translator_id` bigint(20) unsigned DEFAULT NULL,
  `translation_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `string_language` (`string_id`,`language`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_translate`
--

CREATE TABLE `wp_icl_translate` (
  `tid` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `job_id` bigint(20) unsigned NOT NULL,
  `content_id` bigint(20) unsigned NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `field_type` varchar(128) NOT NULL,
  `field_format` varchar(16) NOT NULL,
  `field_translate` tinyint(4) NOT NULL,
  `field_data` text NOT NULL,
  `field_data_translated` text NOT NULL,
  `field_finished` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`tid`),
  KEY `job_id` (`job_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_translate_job`
--

CREATE TABLE `wp_icl_translate_job` (
  `job_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) unsigned NOT NULL,
  `translator_id` int(10) unsigned NOT NULL,
  `translated` tinyint(3) unsigned NOT NULL DEFAULT '0',
  `manager_id` int(10) unsigned NOT NULL,
  `revision` int(10) unsigned DEFAULT NULL,
  PRIMARY KEY (`job_id`),
  KEY `rid` (`rid`,`translator_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_translations`
--

CREATE TABLE `wp_icl_translations` (
  `translation_id` bigint(20) NOT NULL AUTO_INCREMENT,
  `element_type` varchar(36) NOT NULL DEFAULT 'post_post',
  `element_id` bigint(20) DEFAULT NULL,
  `trid` bigint(20) NOT NULL,
  `language_code` varchar(7) NOT NULL,
  `source_language_code` varchar(7) DEFAULT NULL,
  PRIMARY KEY (`translation_id`),
  UNIQUE KEY `trid_lang` (`trid`,`language_code`),
  UNIQUE KEY `el_type_id` (`element_type`,`element_id`),
  KEY `trid` (`trid`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=9 ;

--
-- Dumping data for table 'wp_icl_translations'
--

INSERT INTO `wp_icl_translations` VALUES
(1, 'post_attachment', 5, 5, 'it', NULL),
(2, 'post_page', 2, 2, 'it', NULL),
(3, 'post_post', 1, 1, 'it', NULL),
(4, 'tax_category', 1, 7, 'it', NULL),
(5, 'comment', 1, 9, 'it', NULL),
(6, 'tax_category', 2, 7, 'en', 'it'),
(7, 'tax_category', 3, 7, 'fr', 'it'),
(8, 'tax_category', 4, 7, 'ru', 'it');

-- --------------------------------------------------------

--
-- Table structure for table`wp_icl_translation_status`
--

CREATE TABLE `wp_icl_translation_status` (
  `rid` bigint(20) NOT NULL AUTO_INCREMENT,
  `translation_id` bigint(20) NOT NULL,
  `status` tinyint(4) NOT NULL,
  `translator_id` bigint(20) NOT NULL,
  `needs_update` tinyint(4) NOT NULL,
  `md5` varchar(32) NOT NULL,
  `translation_service` varchar(16) NOT NULL,
  `translation_package` text NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `links_fixed` tinyint(4) NOT NULL DEFAULT '0',
  `_prevstate` longtext,
  PRIMARY KEY (`rid`),
  UNIQUE KEY `translation_id` (`translation_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_layerslider`
--

CREATE TABLE `wp_layerslider` (
  `id` int(10) NOT NULL AUTO_INCREMENT,
  `name` varchar(100) NOT NULL,
  `data` mediumtext NOT NULL,
  `date_c` int(10) NOT NULL,
  `date_m` int(11) NOT NULL,
  `flag_hidden` tinyint(1) NOT NULL DEFAULT '0',
  `flag_deleted` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_links`
--

CREATE TABLE `wp_links` (
  `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `link_url` varchar(255) NOT NULL DEFAULT '',
  `link_name` varchar(255) NOT NULL DEFAULT '',
  `link_image` varchar(255) NOT NULL DEFAULT '',
  `link_target` varchar(25) NOT NULL DEFAULT '',
  `link_description` varchar(255) NOT NULL DEFAULT '',
  `link_visible` varchar(20) NOT NULL DEFAULT 'Y',
  `link_owner` bigint(20) unsigned NOT NULL DEFAULT '1',
  `link_rating` int(11) NOT NULL DEFAULT '0',
  `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `link_rel` varchar(255) NOT NULL DEFAULT '',
  `link_notes` mediumtext NOT NULL,
  `link_rss` varchar(255) NOT NULL DEFAULT '',
  PRIMARY KEY (`link_id`),
  KEY `link_visible` (`link_visible`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table`wp_options`
--

CREATE TABLE `wp_options` (
  `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `option_name` varchar(64) NOT NULL DEFAULT '',
  `option_value` longtext NOT NULL,
  `autoload` varchar(20) NOT NULL DEFAULT 'yes',
  PRIMARY KEY (`option_id`),
  UNIQUE KEY `option_name` (`option_name`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 AUTO_INCREMENT=148 ;


INSERT INTO `wp_options` VALUES
(112, '_transient_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:51:"\n	\n	\n	\n	\n	\n	\n		\n		\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:25:"http://wordpress.org/news";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 20:54:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/?v=3.9-alpha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:10:{i:0;a:6:{s:4:"data";s:42:"\n		\n		\n		\n		\n		\n				\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"WordPress 3.8.1 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2014/01/wordpress-3-8-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/news/2014/01/wordpress-3-8-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 20:37:49 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3063";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:358:"After six weeks and more than 9.3 million downloads of WordPress 3.8, we&#8217;re pleased to announce WordPress 3.8.1 is now available. Version 3.8.1 is a maintenance releases that addresses 31 bugs in 3.8, including various fixes and improvements for the new dashboard design and new themes admin screen. An issue with taxonomy queries in WP_Query [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3809:"<p>After six weeks and more than <a href="http://wordpress.org/download/counter/">9.3 million downloads</a> of WordPress 3.8, we&#8217;re pleased to announce WordPress 3.8.1 is now available.</p>\n<p>Version 3.8.1 is a maintenance releases that addresses 31 bugs in 3.8, including various fixes and improvements for the new dashboard design and new themes admin screen. An issue with taxonomy queries in WP_Query was resolved. And if you&#8217;ve been frustrated by submit buttons that won&#8217;t do anything when you click on them (or thought you were going crazy, like some of us), we&#8217;ve found and fixed this &#8220;dead zone&#8221; on submit buttons.</p>\n<p>It also contains a fix for <strong>embedding tweets</strong> (by placing the URL to the tweet on its own line), which was broken due to a recent Twitter API change. (For more on Embeds, see <a href="http://codex.wordpress.org/Embeds">the Codex</a>.)</p>\n<p>For a full list of changes, consult the <a href="http://core.trac.wordpress.org/query?milestone=3.8.1">list of tickets</a> and <a href="https://core.trac.wordpress.org/log/branches/3.8?rev=27018&amp;stop_rev=26862">the changelog</a>. There&#8217;s also a <a href="http://make.wordpress.org/core/2014/01/22/wordpress-3-8-1-release-candidate/">detailed summary</a> for developers on the development blog.</p>\n<p>If you are one of the millions already running WordPress 3.8, we will start rolling out automatic background updates for WordPress 3.8.1 in the next few hours. For sites <a href="http://wordpress.org/plugins/background-update-tester/">that support them</a>, of course.</p>\n<p><a href="http://wordpress.org/download/">Download WordPress 3.8.1</a> or venture over to <strong>Dashboard → Updates</strong> and simply click &#8220;Update Now.&#8221;</p>\n<p>Thanks to all of these fine individuals for contributing to 3.8.1:</p>\n<p><a href="http://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="http://profiles.wordpress.org/collinsinternet">Allan Collins</a>, <a href="http://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/aubreypwd">Aubrey Portwood</a>, <a href="http://profiles.wordpress.org/empireoflight">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/cojennin">Connor Jennings</a>, <a href="http://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="http://profiles.wordpress.org/fboender">fboender</a>, <a href="http://profiles.wordpress.org/avryl">Janneke Van Dorpe</a>, <a href="http://profiles.wordpress.org/janrenn">janrenn</a>, <a href="http://profiles.wordpress.org/joedolson">Joe Dolson</a>, <a href="http://profiles.wordpress.org/johnbillion">John Blackbourn</a>, <a href="#">José Pino</a>, <a href="http://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/matveb">Matias Ventura</a>, <a href="http://profiles.wordpress.org/mattheu">Matthew Haines-Young</a>, <a href="http://profiles.wordpress.org/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/melchoyce">Mel Choyce</a>, <a href="http://profiles.wordpress.org/batmoo">Mohammad Jangda</a>, <a href="http://profiles.wordpress.org/morganestes">Morgan Estes</a>, <a href="http://profiles.wordpress.org/nivijah">nivijah</a>, <a href="http://profiles.wordpress.org/wonderboymusic">Scott Taylor</a>, <a href="http://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/undergroundnetwork">undergroundnetwork</a>, and <a href="http://profiles.wordpress.org/yurivictor">Yuri Victor</a>.</p>\n<p><em>WordPress three eight one<br />\nWe heard you didn&#8217;t like bugs<br />\nSo we took them out</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/01/wordpress-3-8-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:42:"\n		\n		\n		\n		\n		\n				\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:26:"WordPress 3.8 “Parker”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"http://wordpress.org/news/2013/12/parker/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2013/12/parker/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 12 Dec 2013 17:00:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2765";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:354:"Version 3.8 of WordPress, named “Parker” in honor of Charlie Parker, bebop innovator, is available for download or update in your WordPress dashboard. We hope you&#8217;ll think this is the most beautiful update yet. Introducing a modern new design WordPress has gotten a facelift. 3.8 brings a fresh new look to the entire admin dashboard. [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:18740:"<p>Version 3.8 of WordPress, named “Parker” in honor of <a href="http://en.wikipedia.org/wiki/Charlie_Parker">Charlie Parker</a>, bebop innovator, is available <a href="http://wordpress.org/download/">for download</a> or update in your WordPress dashboard. We hope you&#8217;ll think this is the most beautiful update yet.</p>\n<div id="v-6wORgoGb-1" class="video-player"><embed id="v-6wORgoGb-1-video" src="http://s0.videopress.com/player.swf?v=1.03&amp;guid=6wORgoGb&amp;isDynamicSeeking=true" type="application/x-shockwave-flash" width="692" height="388" wmode="direct" seamlesstabbing="true" allowfullscreen="true" allowscriptaccess="always" overstretch="true"></embed></div>\n<h2 class="aligncenter">Introducing a modern new design</h2>\n<p><img class="wp-image-2951 aligncenter" alt="overview" src="http://i0.wp.com/wpdotorg.files.wordpress.com/2013/12/overview.jpg?resize=623%2C193" data-recalc-dims="1" /></p>\n<p>WordPress has gotten a facelift. 3.8 brings a fresh new look to the entire admin dashboard. Gone are overbearing gradients and dozens of shades of grey — bring on a bigger, bolder, more colorful design!</p>\n<p><img class="aligncenter  wp-image-2856" style="margin-left: 0;margin-right: 0" alt="about-modern-wordpress" src="http://i2.wp.com/wpdotorg.files.wordpress.com/2013/12/design.png?resize=623%2C151" data-recalc-dims="1" /></p>\n<h3>Modern aesthetic</h3>\n<p>The new WordPress dashboard has a fresh, uncluttered design that embraces clarity and simplicity.</p>\n<h3>Clean typography</h3>\n<p>The Open Sans typeface provides simple, friendly text that is optimized for both desktop and mobile viewing. It’s even open source, just like WordPress.</p>\n<h3>Refined contrast</h3>\n<p>We think beautiful design should never sacrifice legibility. With superior contrast and large, comfortable type, the new design is easy to read and a pleasure to navigate.</p>\n<hr />\n<h2 class="aligncenter">WordPress on every device</h2>\n<p><img class="alignright  wp-image-2984" alt="responsive" src="http://i2.wp.com/wpdotorg.files.wordpress.com/2013/12/responsive.jpg?resize=255%2C255" data-recalc-dims="1" />We all access the internet in different ways. Smartphone, tablet, notebook, desktop — no matter what you use, WordPress will adapt and you’ll feel right at home.</p>\n<h3>High definition at high speed</h3>\n<p>WordPress is sharper than ever with new vector-based icons that scale to your screen. By ditching pixels, pages load significantly faster, too.</p>\n<hr />\n<h2 class="aligncenter">Admin color schemes to match your personality</h2>\n<p><img class="aligncenter  wp-image-2954" alt="colors" src="http://i0.wp.com/wpdotorg.files.wordpress.com/2013/12/colors.jpg?resize=623%2C339" data-recalc-dims="1" /></p>\n<p>WordPress just got a colorful new update. We’ve included eight new admin color schemes so you can pick the one that suits you best.</p>\n<p>Color schemes can be previewed and changed from your Profile page.</p>\n<hr />\n<h2 class="aligncenter">Refined theme management</h2>\n<p><img class="alignright  wp-image-2967" alt="themes" src="http://i0.wp.com/wpdotorg.files.wordpress.com/2013/12/themes.jpg?resize=360%2C344" data-recalc-dims="1" />The new themes screen lets you survey your themes at a glance. Or want more information? Click to discover more. Then sit back and use your keyboard’s navigation arrows to flip through every theme you’ve got.</p>\n<h3>Smoother widget experience</h3>\n<p>Drag-drag-drag. Scroll-scroll-scroll. Widget management can be complicated. With the new design, we’ve worked to streamline the widgets screen.</p>\n<p>Have a large monitor? Multiple widget areas stack side-by-side to use the available space. Using a tablet? Just tap a widget to add it.</p>\n<hr />\n<h2 class="aligncenter">Twenty Fourteen, a sleek new magazine theme</h2>\n<p><img class="aligncenter size-large wp-image-2789" alt="The new Twenty Fourteen theme displayed on a laptop. tablet and phone" src="http://i0.wp.com/wpdotorg.files.wordpress.com/2013/12/twentyfourteen.jpg?resize=692%2C275" data-recalc-dims="1" /></p>\n<h3>Turn your blog into a magazine</h3>\n<p>Create a beautiful magazine-style site with WordPress and Twenty Fourteen. Choose a grid or a slider to display featured content on your homepage. Customize your site with three widget areas or change your layout with two page templates.</p>\n<p>With a striking design that does not compromise our trademark simplicity, Twenty Fourteen is our most intrepid default theme yet.</p>\n<hr />\n<h2>Beginning of a new era</h2>\n<p>This release was led by Matt Mullenweg. This is our second release using the new plugin-first development process, with a much shorter timeframe than in the past. We think it’s been going great. You can check out the features currently in production on the <a title="Make WordPress Core" href="http://make.wordpress.org/core/" target="_blank">make/core blog</a>.</p>\n<p>There are 188 contributors with props in this release:</p>\n<p><a href="http://profiles.wordpress.org/aaronholbrook">Aaron Holbrook</a>, <a href="http://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="http://profiles.wordpress.org/adamsilverstein">adamsilverstein</a>, <a href="http://profiles.wordpress.org/admiralthrawn">admiralthrawn</a>, <a href="http://profiles.wordpress.org/ahoereth">Alexander Hoereth</a>, <a href="http://profiles.wordpress.org/collinsinternet">Allan Collins</a>, <a href="http://profiles.wordpress.org/sabreuse">Amy Hendrix (sabreuse)</a>, <a href="http://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/aralbald">Andrey Kabakchiev</a>, <a href="http://profiles.wordpress.org/apeatling">Andy Peatling</a>, <a href="http://profiles.wordpress.org/ankitgadertcampcom">Ankit Gade</a>, <a href="http://profiles.wordpress.org/atimmer">Anton Timmermans</a>, <a href="http://profiles.wordpress.org/fliespl">Arkadiusz Rzadkowolski</a>, <a href="http://profiles.wordpress.org/aubreypwd">Aubrey Portwood</a>, <a href="http://profiles.wordpress.org/bassgang">bassgang</a>, <a href="http://profiles.wordpress.org/empireoflight">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/bananastalktome">Billy (bananastalktome)</a>, <a href="http://profiles.wordpress.org/binarymoon">binarymoon</a>, <a href="http://profiles.wordpress.org/bradyvercher">Brady Vercher</a>, <a href="http://profiles.wordpress.org/kraftbj">Brandon Kraft</a>, <a href="http://profiles.wordpress.org/rzen">Brian Richards</a>, <a href="http://profiles.wordpress.org/bpetty">Bryan Petty</a>, <a href="http://profiles.wordpress.org/calin">Calin Don</a>, <a href="http://profiles.wordpress.org/carldanley">Carl Danley</a>, <a href="http://profiles.wordpress.org/sixhours">Caroline Moore</a>, <a href="http://profiles.wordpress.org/caspie">Caspie</a>, <a href="http://profiles.wordpress.org/chrisbliss18">Chris Jean</a>, <a href="http://profiles.wordpress.org/iblamefish">Clinton Montague</a>, <a href="http://profiles.wordpress.org/cojennin">cojennin</a>, <a href="http://profiles.wordpress.org/corphi">Corphi</a>, <a href="http://profiles.wordpress.org/dbernar1">Dan Bernardic</a>, <a href="http://profiles.wordpress.org/danieldudzic">Daniel Dudzic</a>, <a href="http://profiles.wordpress.org/koop">Daryl Koopersmith</a>, <a href="http://profiles.wordpress.org/datafeedrcom">datafeedr</a>, <a href="http://profiles.wordpress.org/lessbloat">Dave Martin</a>, <a href="http://profiles.wordpress.org/drw158">Dave Whitley</a>, <a href="http://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="http://profiles.wordpress.org/dougwollison">Doug Wollison</a>, <a href="http://profiles.wordpress.org/drewapicture">Drew Jaynes</a>, <a href="http://profiles.wordpress.org/dziudek">dziudek</a>, <a href="http://profiles.wordpress.org/ericlewis">Eric Andrew Lewis</a>, <a href="http://profiles.wordpress.org/ericmann">Eric Mann</a>, <a href="http://profiles.wordpress.org/ethitter">Erick Hitter</a>, <a href="http://profiles.wordpress.org/evansolomon">Evan Solomon</a>, <a href="http://profiles.wordpress.org/faison">Faison</a>, <a href="http://profiles.wordpress.org/fboender">fboender</a>, <a href="http://profiles.wordpress.org/frank-klein">Frank Klein</a>, <a href="http://profiles.wordpress.org/garyj">Gary Jones</a>, <a href="http://profiles.wordpress.org/pento">Gary Pendergast</a>, <a href="http://profiles.wordpress.org/soulseekah">Gennady Kovshenin</a>, <a href="http://profiles.wordpress.org/georgestephanis">George Stephanis</a>, <a href="http://profiles.wordpress.org/gnarf37">gnarf37</a>, <a href="http://profiles.wordpress.org/tivnet">Gregory Karpinsky</a>, <a href="http://profiles.wordpress.org/hanni">hanni</a>, <a href="http://profiles.wordpress.org/helen">Helen Hou-Sandi</a>, <a href="http://profiles.wordpress.org/iandunn">Ian Dunn</a>, <a href="http://profiles.wordpress.org/ipstenu">Ipstenu (Mika Epstein)</a>, <a href="http://profiles.wordpress.org/isaackeyet">Isaac Keyet</a>, <a href="http://profiles.wordpress.org/jdgrimes">J.D. Grimes</a>, <a href="http://profiles.wordpress.org/jacklenox">Jack Lenox</a>, <a href="http://profiles.wordpress.org/janhenckens">janhenckens</a>, <a href="http://profiles.wordpress.org/avryl">Janneke Van Dorpe</a>, <a href="http://profiles.wordpress.org/janrenn">janrenn</a>, <a href="http://profiles.wordpress.org/jblz">Jeff Bowen</a>, <a href="http://profiles.wordpress.org/jeffr0">Jeff Chandler</a>, <a href="http://profiles.wordpress.org/jenmylo">Jen Mylo</a>, <a href="http://profiles.wordpress.org/buffler">Jeremy Buller</a>, <a href="http://profiles.wordpress.org/jeremyfelt">Jeremy Felt</a>, <a href="http://profiles.wordpress.org/jeherve">Jeremy Herve</a>, <a href="http://profiles.wordpress.org/jpry">Jeremy Pry</a>, <a href="http://profiles.wordpress.org/jayjdk">Jesper Johansen (jayjdk)</a>, <a href="http://profiles.wordpress.org/jhned">jhned</a>, <a href="http://profiles.wordpress.org/jim912">jim912</a>, <a href="http://profiles.wordpress.org/jartes">Joan Artes</a>, <a href="http://profiles.wordpress.org/joedolson">Joe Dolson</a>, <a href="http://profiles.wordpress.org/joen">Joen Asmussen</a>, <a href="http://profiles.wordpress.org/johnbillion">John Blackbourn</a>, <a href="http://profiles.wordpress.org/johnafish">John Fish</a>, <a href="http://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="http://profiles.wordpress.org/duck_">Jon Cave</a>, <a href="http://profiles.wordpress.org/joostdevalk">Joost de Valk</a>, <a href="http://profiles.wordpress.org/joshuaabenazer">Joshua Abenazer</a>, <a href="http://profiles.wordpress.org/nukaga">Junko Nukaga</a>, <a href="http://profiles.wordpress.org/devesine">Justin de Vesine</a>, <a href="http://profiles.wordpress.org/justinsainton">Justin Sainton</a>, <a href="http://profiles.wordpress.org/kadamwhite">K. Adam White</a>, <a href="http://profiles.wordpress.org/trepmal">Kailey (trepmal)</a>, <a href="http://profiles.wordpress.org/codebykat">Kat Hagan</a>, <a href="http://profiles.wordpress.org/littlethingsstudio">Kate Whitley</a>, <a href="http://profiles.wordpress.org/ryelle">Kelly Dwan</a>, <a href="http://profiles.wordpress.org/kpdesign">Kim Parsell</a>, <a href="http://profiles.wordpress.org/kwight">Kirk Wight</a>, <a href="http://profiles.wordpress.org/koki4a">Konstantin Dankov</a>, <a href="http://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/obenland">Konstantin Obenland</a>, <a href="http://profiles.wordpress.org/drozdz">Krzysiek Drozdz</a>, <a href="http://profiles.wordpress.org/lancewillett">Lance Willett</a>, <a href="http://profiles.wordpress.org/leewillis77">Lee Willis</a>, <a href="http://profiles.wordpress.org/lite3">lite3</a>, <a href="http://profiles.wordpress.org/lucp">Luc Princen</a>, <a href="http://profiles.wordpress.org/latz">Lutz Schroer</a>, <a href="http://profiles.wordpress.org/mako09">Mako</a>, <a href="http://profiles.wordpress.org/markjaquith">Mark Jaquith</a>, <a href="http://profiles.wordpress.org/markmcwilliams">Mark McWilliams</a>, <a href="http://profiles.wordpress.org/markoheijnen">Marko Heijnen</a>, <a href="http://profiles.wordpress.org/matt">Matt Mullenweg</a>, <a href="http://profiles.wordpress.org/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/mattwiebe">Matt Wiebe</a>, <a href="http://profiles.wordpress.org/mdbitz">Matthew Denton</a>, <a href="http://profiles.wordpress.org/mattheu">Matthew Haines-Young</a>, <a href="http://profiles.wordpress.org/matveb">Matías Ventura</a>, <a href="http://profiles.wordpress.org/megane9988">megane9988</a>, <a href="http://profiles.wordpress.org/melchoyce">Mel Choyce</a>, <a href="http://profiles.wordpress.org/micahwave">micahwave</a>, <a href="http://profiles.wordpress.org/cainm">Michael Cain</a>, <a href="http://profiles.wordpress.org/mitchoyoshitaka">Michael Erlewine</a>, <a href="http://profiles.wordpress.org/michelwppi">Michel - xiligroup dev</a>, <a href="http://profiles.wordpress.org/chellycat">Michelle Langston</a>, <a href="http://profiles.wordpress.org/gradyetc">Mike Burns</a>, <a href="http://profiles.wordpress.org/mikehansenme">Mike Hansen</a>, <a href="http://profiles.wordpress.org/mikelittle">Mike Little</a>, <a href="http://profiles.wordpress.org/dh-shredder">Mike Schroder</a>, <a href="http://profiles.wordpress.org/dimadin">Milan Dinic</a>, <a href="http://profiles.wordpress.org/batmoo">Mohammad Jangda</a>, <a href="http://profiles.wordpress.org/morganestes">Morgan Estes</a>, <a href="http://profiles.wordpress.org/mt8biz">moto hachi</a>, <a href="http://profiles.wordpress.org/Nao">Naoko Takano</a>, <a href="http://profiles.wordpress.org/neil_pie">Neil Pie</a>, <a href="http://profiles.wordpress.org/nickdaugherty">Nick Daugherty</a>, <a href="http://profiles.wordpress.org/celloexpressions">Nick Halsey</a>, <a href="http://profiles.wordpress.org/nbachiyski">Nikolay Bachiyski</a>, <a href="http://profiles.wordpress.org/ninio">ninio</a>, <a href="http://profiles.wordpress.org/ninnypants">ninnypants</a>, <a href="http://profiles.wordpress.org/nivijah">nivijah</a>, <a href="http://profiles.wordpress.org/nofearinc">nofearinc</a>, <a href="http://profiles.wordpress.org/nvwd">Nowell VanHoesen</a>, <a href="http://profiles.wordpress.org/odysseygate">odyssey</a>, <a href="http://profiles.wordpress.org/originalexe">OriginalEXE</a>, <a href="http://profiles.wordpress.org/swissspidy">Pascal Birchler</a>, <a href="http://profiles.wordpress.org/pauldewouters">Paul de Wouters</a>, <a href="http://profiles.wordpress.org/pavelevap">pavelevap</a>, <a href="http://profiles.wordpress.org/westi">Peter Westwood</a>, <a href="http://profiles.wordpress.org/senlin">Piet</a>, <a href="http://profiles.wordpress.org/ptahdunbar">Ptah Dunbar</a>, <a href="http://profiles.wordpress.org/raamdev">Raam Dev</a>, <a href="http://profiles.wordpress.org/bamadesigner">Rachel Carden</a>, <a href="http://profiles.wordpress.org/rachelbaker">rachelbaker</a>, <a href="http://profiles.wordpress.org/radices">Radices</a>, <a href="http://profiles.wordpress.org/mauryaratan">Ram Ratan Maurya</a>, <a href="http://profiles.wordpress.org/defries">Remkus de Vries</a>, <a href="http://profiles.wordpress.org/ounziw">Rescuework Support</a>, <a href="http://profiles.wordpress.org/rickalee">Ricky Lee Whittemore</a>, <a href="http://profiles.wordpress.org/rdall">Robert Dall</a>, <a href="http://profiles.wordpress.org/wet">Robert Wetzlmayr, PHP-Programmierer</a>, <a href="http://profiles.wordpress.org/rodrigosprimo">Rodrigo Primo</a>, <a href="http://profiles.wordpress.org/ryan">Ryan Boren</a>, <a href="http://profiles.wordpress.org/otto42">Samuel Wood</a>, <a href="http://profiles.wordpress.org/sanchothefat">sanchothefat</a>, <a href="http://profiles.wordpress.org/sboisvert">sboisvert</a>, <a href="http://profiles.wordpress.org/scottbasgaard">Scott Basgaard</a>, <a href="http://profiles.wordpress.org/coffee2code">Scott Reilly</a>, <a href="http://profiles.wordpress.org/wonderboymusic">Scott Taylor</a>, <a href="http://profiles.wordpress.org/scribu">scribu</a>, <a href="http://profiles.wordpress.org/seanchayes">Sean Hayes</a>, <a href="http://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/shaunandrews">Shaun Andrews</a>, <a href="http://profiles.wordpress.org/designsimply">Sheri Bigelow (designsimply)</a>, <a href="http://profiles.wordpress.org/shinichin">ShinichiN</a>, <a href="http://profiles.wordpress.org/simonwheatley">Simon Wheatley</a>, <a href="http://profiles.wordpress.org/siobhan">Siobhan</a>, <a href="http://profiles.wordpress.org/siobhyb">Siobhan Bamber (siobhyb)</a>, <a href="http://profiles.wordpress.org/sirbrillig">sirbrillig</a>, <a href="http://profiles.wordpress.org/solarissmoke">solarissmoke</a>, <a href="http://profiles.wordpress.org/netweb">Stephen Edgar</a>, <a href="http://profiles.wordpress.org/stephenharris">Stephen Harris</a>, <a href="http://profiles.wordpress.org/stevenkword">Steven Word</a>, <a href="http://profiles.wordpress.org/iamtakashi">Takashi Irie</a>, <a href="http://profiles.wordpress.org/miyauchi">Takayuki Miyauchi</a>, <a href="http://profiles.wordpress.org/tmtoy">Takuma Morikawa</a>, <a href="http://profiles.wordpress.org/thomasguillot">Thomas Guillot</a>, <a href="http://profiles.wordpress.org/tierra">tierra</a>, <a href="http://profiles.wordpress.org/tillkruess">Till Krüss</a>, <a href="http://profiles.wordpress.org/tlamedia">TLA Media</a>, <a href="http://profiles.wordpress.org/tobiasbg">TobiasBg</a>, <a href="http://profiles.wordpress.org/tommcfarlin">tommcfarlin</a>, <a href="http://profiles.wordpress.org/zodiac1978">Torsten Landsiedel</a>, <a href="http://profiles.wordpress.org/taupecat">Tracy Rotton</a>, <a href="http://profiles.wordpress.org/trishasalas">trishasalas</a>, <a href="http://profiles.wordpress.org/mbmufffin">Tyler Smith</a>, <a href="http://profiles.wordpress.org/grapplerulrich">Ulrich</a>, <a href="http://profiles.wordpress.org/undergroundnetwork">undergroundnetwork</a>, <a href="http://profiles.wordpress.org/l10n">Vladimir</a>, <a href="http://profiles.wordpress.org/westonruter">Weston Ruter</a>, <a href="http://profiles.wordpress.org/yoavf">Yoav Farhi</a>, <a href="http://profiles.wordpress.org/yonasy">yonasy</a>, <a href="http://profiles.wordpress.org/yurivictor">Yuri Victor</a>, and <a href="http://profiles.wordpress.org/tollmanz">Zack Tollman</a>. Also thanks to <a href="http://benmorrison.org/">Ben Morrison</a> and <a href="http://christineswebb.com/">Christine Webb</a> for help with the video.</p>\n<p>Thanks for choosing WordPress. See you soon for version 3.9!</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:46:"http://wordpress.org/news/2013/12/parker/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:7:"3.8 RC2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"http://wordpress.org/news/2013/12/3-8-rc2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:51:"http://wordpress.org/news/2013/12/3-8-rc2/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 10 Dec 2013 01:08:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2805";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:343:"Release candidate 2 of WordPress 3.8 is now available for download. This is the last pre-release, and we expect it to be effectively identical to what&#8217;s officially released to the public on Thursday. This means if you are a plugin or theme developer, start your engines! (If they&#8217;re not going already.) Lots of admin code [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1180:"<p>Release candidate 2 of WordPress 3.8 is <a href="http://wordpress.org/wordpress-3.8-RC2.zip">now available for download</a>. This is the last pre-release, and we expect it to be effectively identical to what&#8217;s officially released to the public on Thursday.</p>\n<p>This means if you are a plugin or theme developer, start your engines! (If they&#8217;re not going already.) Lots of admin code has changed so it&#8217;s especially important to see if your plugin works well within the new admin design and layout, and update <a href="http://wordpress.org/plugins/about/readme.txt">the &#8220;Tested up to:&#8221; part of your plugin readme.txt</a>.</p>\n<p>If there is something in your plugin that you&#8217;re unable to fix, or if you think you&#8217;ve found a bug, join us <a href="http://codex.wordpress.org/IRC">in #wordpress-dev in IRC</a>, especially if you&#8217;re able to join during the dev chat on Wednesday, or post in the <a href="http://wordpress.org/support/forum/alphabeta">alpha/beta forum</a>. The developers and designers who worked on this release are happy to help anyone update their code before the 3.8 release.</p>\n<p>Happy hacking, everybody!</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:47:"http://wordpress.org/news/2013/12/3-8-rc2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:17:"WordPress 3.8 RC1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"http://wordpress.org/news/2013/12/3-8-almost/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:54:"http://wordpress.org/news/2013/12/3-8-almost/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 04 Dec 2013 09:54:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2760";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:345:"We&#8217;re entering the quiet but busy part of a release, whittling down issues to bring you all of the new features you&#8217;re excited about with the stability you expect from WordPress. There are just a few days from the &#8220;code freeze&#8221; for our 3.8 release, which includes a number of exciting enhancements, so the focus [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1873:"<p>We&#8217;re entering the quiet but busy part of a release, whittling down issues to bring you all of the new features you&#8217;re excited about with the stability you expect from WordPress. There are just a few days from the &#8220;code freeze&#8221; for our 3.8 release, <a href="http://wordpress.org/news/2013/11/wordpress-3-8-beta-1/">which includes a number of exciting enhancements</a>, so the focus is on identifying any major issues and resolving them as soon as possible.</p>\n<p>If you&#8217;ve ever wondered about how to contribute to WordPress, here&#8217;s a time you can: download this release candidate and use it in as many ways as you can imagine. Try to break it, and if you do, let us know how you did it so we can make sure it never happens again. If you work for a web host, this is the release you should test as much as possible and start getting your automatic upgrade systems and 1-click installers ready.</p>\n<p><a href="http://wordpress.org/wordpress-3.8-RC1.zip">Download WordPress 3.8 RC1</a> (zip) or use the <a href="http://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you&#8217;ll want &#8220;bleeding edge nightlies&#8221;).</p>\n<p>If you think you’ve found a bug, you can post to the <a href="http://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a reproducible bug report, <a href="http://core.trac.wordpress.org/">file one on the WordPress Trac</a>. There, you can also find <a href="http://core.trac.wordpress.org/report/5">a list of known bugs</a> and <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=component&amp;milestone=3.8">everything we’ve fixed</a> so far.</p>\n<p><em>We&#8217;re so close to the</em><br />\n<em>finish line, jump in and help</em><br />\n<em>good karma is yours.</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2013/12/3-8-almost/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 3.8 Beta 1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2013/11/wordpress-3-8-beta-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:64:"http://wordpress.org/news/2013/11/wordpress-3-8-beta-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 21 Nov 2013 05:21:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2754";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:307:"The first beta of the 3.8 is now available, and the next dates to watch out for are code freeze on December 5th and a final release on December 12th. 3.8 brings together several of the features as plugins projects and while this isn&#8217;t our first rodeo, expect this to be more beta than usual. [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2236:"<p>The first beta of the 3.8 is now available, and the next dates to watch out for are code freeze on December 5th and a final release on December 12th.</p>\n<p>3.8 brings together <a href="http://make.wordpress.org/core/features-as-plugins/">several of the features as plugins projects</a> and while this isn&#8217;t our first rodeo, expect this to be more beta than usual. The headline things to test out in this release are:</p>\n<ul>\n<li>The new admin design, especially the responsive aspect of it. Try it out on different devices and browsers, see how it goes, especially the more complex pages like widgets or seldom-looked-at-places like Press This. Color schemes, which you can change on your profile, have also been spruced up.</li>\n<li>The dashboard homepage has been refreshed, poke and prod it.</li>\n<li>Choosing themes under Appearance is completely different, try to break it however possible.</li>\n<li>There&#8217;s a new default theme, Twenty Fourteen.</li>\n<li>Over 250 issues closed already.</li>\n</ul>\n<p>Given how many things in the admin have changed it&#8217;s extra super duper important to test as many plugins and themes with admin pages against the new stuff. Also if you&#8217;re a developer consider how you can make your admin interface fit the MP6 aesthetic better.</p>\n<p>As always, if you think you’ve found a bug, you can post to the <a href="http://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a reproducible bug report, <a href="http://core.trac.wordpress.org/">file one on the WordPress Trac</a>. There, you can also find <a href="http://core.trac.wordpress.org/report/5">a list of known bugs</a> and <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=component&amp;milestone=3.8">everything we’ve fixed</a> so far.</p>\n<p><a href="http://wordpress.org/wordpress-3.8-beta-1.zip">Download WordPress 3.8 Beta 1</a> (zip) or use the <a href="http://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you&#8217;ll want &#8220;bleeding edge nightlies&#8221;).</p>\n<p><em>Alphabet soup of</em><br />\n<em>Plugins as features galore</em><br />\n<em>The future is here</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"http://wordpress.org/news/2013/11/wordpress-3-8-beta-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"WordPress 3.7.1 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2013/10/wordpress-3-7-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/news/2013/10/wordpress-3-7-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 29 Oct 2013 21:04:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2745";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:371:"WordPress 3.7.1 is now available! This maintenance release addresses 11 bugs in WordPress 3.7, including: Images with captions no longer appear broken in the visual editor. Allow some sites running on old or poorly configured servers to continue to check for updates from WordPress.org. Avoid fatal errors with certain plugins that were incorrectly calling some [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1594:"<p>WordPress 3.7.1 is now available! This maintenance release addresses 11 bugs in WordPress 3.7, including:</p>\n<ul>\n<li>Images with captions no longer appear broken in the visual editor.</li>\n<li>Allow some sites running on old or poorly configured servers to continue to check for updates from WordPress.org.</li>\n<li>Avoid fatal errors with certain plugins that were incorrectly calling some WordPress functions too early.</li>\n<li>Fix hierarchical sorting in get_pages(), exclusions in wp_list_categories(), and in_category() when called with empty values.</li>\n<li>Fix a warning that may occur in certain setups while performing a search, and a few other notices.</li>\n</ul>\n<p>For a full list of changes, consult the <a href="http://core.trac.wordpress.org/query?milestone=3.7.1">list of tickets</a> and <a href="http://core.trac.wordpress.org/log/branches/3.7?stop_rev=25914&amp;rev=25986">the changelog</a>.</p>\n<p>If you are one of the <a href="http://wordpress.org/download/counter/">nearly two million</a> already running WordPress 3.7, we will start rolling out the all-new <a href="http://wordpress.org/news/2013/10/basie/">automatic background updates</a> for WordPress 3.7.1 in the next few hours. For sites <a href="http://wordpress.org/plugins/background-update-tester/">that support them</a>, of course.</p>\n<p><a href="http://wordpress.org/download/">Download WordPress 3.7.1</a> or venture over to <strong>Dashboard → Updates</strong> and simply click &#8220;Update Now.&#8221;</p>\n<p><em>Just a few fixes<br />\nYour new update attitude:<br />\nZero clicks given</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2013/10/wordpress-3-7-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:42:"\n		\n		\n		\n		\n		\n				\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:25:"WordPress 3.7 “Basie”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:40:"http://wordpress.org/news/2013/10/basie/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:49:"http://wordpress.org/news/2013/10/basie/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 24 Oct 2013 22:35:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2736";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:357:"Version 3.7 of WordPress, named &#8220;Basie&#8221; in honor of Count Basie, is available for download or update in your WordPress dashboard. This release features some of the most important architectural updates we&#8217;ve made to date. Here are the big ones: Updates while you sleep: With WordPress 3.7, you don&#8217;t have to lift a finger to [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:17229:"<p>Version 3.7 of WordPress, named &#8220;Basie&#8221; in honor of <a href="http://en.wikipedia.org/wiki/Count_basie">Count Basie</a>, is available <a href="http://wordpress.org/download/">for download</a> or update in your WordPress dashboard. This release features some of the most important architectural updates we&#8217;ve made to date. Here are the big ones:</p>\n<ul>\n<li><strong>Updates while you sleep</strong>: With WordPress 3.7, you don&#8217;t have to lift a finger to apply maintenance and security updates. Most sites are now able to automatically apply these updates in the background. The update process also has been made even more reliable and secure, with dozens of new checks and safeguards.</li>\n<li><strong>Stronger password recommendations</strong>: Your password is your site&#8217;s first line of defense. It&#8217;s best to create passwords that are complex, long, and unique. To that end, our password meter has been updated in WordPress 3.7 to recognize common mistakes that can weaken your password: dates, names, keyboard patterns (123456789), and even pop culture references.</li>\n<li><strong>Better global support</strong>: Localized versions of WordPress will receive faster and more complete translations. WordPress 3.7 adds support for automatically installing the right language files and keeping them up to date, a boon for the many millions who use WordPress in a language other than English.</li>\n</ul>\n<p>For developers there are lots of options around how to control the new updates feature, including allowing it to handle major upgrades as well as minor ones, more sophisticated date query support, and multisite improvements. As always, if you&#8217;re hungry for more <a href="http://codex.wordpress.org/Version_3.7">dive into the Codex</a> or browse the <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;milestone=3.7">over 400 closed tickets on Trac</a>.</p>\n<h3>A New Wave</h3>\n<p>This release was led by Andrew Nacin, backed up by Dion Hulse and Jon Cave. This is our first release using the new plugin-first development process, with a much shorter timeframe than in the past. (3.6 was released in August.) The 3.8 release, due in December, will continue this plugin-led development cycle that gives much more autonomy to plugin leads and allows us to decouple feature development from a release. You can follow this grand experiment, and what we&#8217;re learning from it, <a href="http://make.wordpress.org/core/">on the make/core blog</a>. There are 211 contributors with props in this release:</p>\n<p><a href="http://profiles.wordpress.org/technosailor">Aaron Brazell</a>, <a href="http://profiles.wordpress.org/aaroncampbell">Aaron D. Campbell</a>, <a href="http://profiles.wordpress.org/aaronholbrook">Aaron Holbrook</a>, <a href="http://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="http://profiles.wordpress.org/adamsilverstein">adamsilverstein</a>, <a href="http://profiles.wordpress.org/ahoereth">Alexander Hoereth</a>, <a href="http://profiles.wordpress.org/viper007bond">Alex Mills (Viper007Bond)</a>, <a href="http://profiles.wordpress.org/sabreuse">Amy Hendrix (sabreuse)</a>, <a href="http://profiles.wordpress.org/andg">andg</a>, <a href="http://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/norcross">Andrew Norcross</a>, <a href="http://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/andrewspittle">Andrew Spittle</a>, <a href="http://profiles.wordpress.org/askapache">askapache</a>, <a href="http://profiles.wordpress.org/atimmer">atimmer</a>, <a href="http://profiles.wordpress.org/barry">Barry</a>, <a href="http://profiles.wordpress.org/beaulebens">Beau Lebens</a>, <a href="http://profiles.wordpress.org/benmoody">ben.moody</a>, <a href="http://profiles.wordpress.org/bhengh">Ben Miller</a>, <a href="http://profiles.wordpress.org/neoxx">Bernhard Riedl</a>, <a href="http://profiles.wordpress.org/bftrick">BFTrick</a>, <a href="http://profiles.wordpress.org/bananastalktome">Billy (bananastalktome)</a>, <a href="http://profiles.wordpress.org/bmb">bmb</a>, <a href="http://profiles.wordpress.org/kraftbj">Brandon Kraft</a>, <a href="http://profiles.wordpress.org/brianhogg">brianhogg</a>, <a href="http://profiles.wordpress.org/rzen">Brian Richards</a>, <a href="http://profiles.wordpress.org/bpetty">Bryan Petty</a>, <a href="http://profiles.wordpress.org/carldanley">Carl Danley</a>, <a href="http://profiles.wordpress.org/charlesclarkson">CharlesClarkson</a>, <a href="http://profiles.wordpress.org/chipbennett">Chip Bennett</a>, <a href="http://profiles.wordpress.org/chouby">Chouby</a>, <a href="http://profiles.wordpress.org/c3mdigital">Chris Olbekson</a>, <a href="http://profiles.wordpress.org/chrisrudzki">Chris Rudzki</a>, <a href="http://profiles.wordpress.org/aeg0125">coderaaron</a>, <a href="http://profiles.wordpress.org/coenjacobs">Coen Jacobs</a>, <a href="http://profiles.wordpress.org/crrobi01">Colin Robinson</a>, <a href="http://profiles.wordpress.org/andreasnrb">cyonite</a>, <a href="http://profiles.wordpress.org/daankortenbach">Daan Kortenbach</a>, <a href="http://profiles.wordpress.org/danielbachhuber">Daniel Bachhuber</a>, <a href="http://profiles.wordpress.org/convissor">Daniel Convissor</a>, <a href="http://profiles.wordpress.org/dartiss">dartiss</a>, <a href="http://profiles.wordpress.org/koop">Daryl Koopersmith</a>, <a href="http://profiles.wordpress.org/csixty4">Dave Ross</a>, <a href="http://profiles.wordpress.org/davidjlaietta">David Laietta</a>, <a href="http://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/dllh">dllh</a>, <a href="http://profiles.wordpress.org/ocean90">Dominik Schilling (ocean90)</a>, <a href="http://profiles.wordpress.org/dpash">dpash</a>, <a href="http://profiles.wordpress.org/drewapicture">Drew Jaynes</a>, <a href="http://profiles.wordpress.org/drprotocols">DrProtocols</a>, <a href="http://profiles.wordpress.org/dustyf">Dustin Filippini</a>, <a href="http://profiles.wordpress.org/dzver">dzver</a>, <a href="http://profiles.wordpress.org/cais">Edward Caissie</a>, <a href="http://profiles.wordpress.org/enej">enej</a>, <a href="http://profiles.wordpress.org/ericlewis">Eric Andrew Lewis</a>, <a href="http://profiles.wordpress.org/ericmann">Eric Mann</a>, <a href="http://profiles.wordpress.org/evansolomon">Evan Solomon</a>, <a href="http://profiles.wordpress.org/faishal">faishal</a>, <a href="http://profiles.wordpress.org/faison">Faison</a>, <a href="http://profiles.wordpress.org/foofy">Foofy</a>, <a href="http://profiles.wordpress.org/fjarrett">Frankie Jarrett</a>, <a href="http://profiles.wordpress.org/frank-klein">Frank Klein</a>, <a href="http://profiles.wordpress.org/garyc40">Gary Cao</a>, <a href="http://profiles.wordpress.org/pento">Gary Pendergast</a>, <a href="http://profiles.wordpress.org/gayadesign">Gaya Kessler</a>, <a href="http://profiles.wordpress.org/georgestephanis">George Stephanis</a>, <a href="http://profiles.wordpress.org/gizburdt">Gizburdt</a>, <a href="http://profiles.wordpress.org/goldenapples">goldenapples</a>, <a href="http://profiles.wordpress.org/gradyetc">gradyetc</a>, <a href="http://profiles.wordpress.org/gcorne">Gregory Cornelius</a>, <a href="http://profiles.wordpress.org/webord">Gustavo Bordoni</a>, <a href="http://profiles.wordpress.org/hakre">hakre</a>, <a href="http://profiles.wordpress.org/helen">Helen Hou-Sandi</a>, <a href="http://profiles.wordpress.org/iandunn">Ian Dunn</a>, <a href="http://profiles.wordpress.org/ipstenu">Ipstenu (Mika Epstein)</a>, <a href="http://profiles.wordpress.org/creativeinfusion">itinerant</a>, <a href="http://profiles.wordpress.org/jdgrimes">J.D. Grimes</a>, <a href="http://profiles.wordpress.org/jakubtyrcha">jakub.tyrcha</a>, <a href="http://profiles.wordpress.org/jamescollins">James Collins</a>, <a href="http://profiles.wordpress.org/jenmylo">Jen Mylo</a>, <a href="http://profiles.wordpress.org/buffler">Jeremy Buller</a>, <a href="http://profiles.wordpress.org/jeremyfelt">Jeremy Felt</a>, <a href="http://profiles.wordpress.org/jayjdk">Jesper Johansen (jayjdk)</a>, <a href="http://profiles.wordpress.org/joehoyle">Joe Hoyle</a>, <a href="http://profiles.wordpress.org/jkudish">Joey Kudish</a>, <a href="http://profiles.wordpress.org/johnnyb">John Beales</a>, <a href="http://profiles.wordpress.org/johnbillion">John Blackbourn (johnbillion)</a>, <a href="http://profiles.wordpress.org/johnafish">John Fish</a>, <a href="http://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="http://profiles.wordpress.org/johnpbloch">John P. Bloch</a>, <a href="http://profiles.wordpress.org/jond3r">Jonas Bolinder (jond3r)</a>, <a href="http://profiles.wordpress.org/jchristopher">Jonathan Christopher</a>, <a href="http://profiles.wordpress.org/desrosj">Jonathan Desrosiers</a>, <a href="http://profiles.wordpress.org/duck_">Jon Cave</a>, <a href="http://profiles.wordpress.org/jonlynch">Jon Lynch</a>, <a href="http://profiles.wordpress.org/joostdevalk">Joost de Valk</a>, <a href="http://profiles.wordpress.org/josephscott">Joseph Scott</a>, <a href="http://profiles.wordpress.org/betzster">Josh Betz</a>, <a href="http://profiles.wordpress.org/devesine">Justin de Vesine</a>, <a href="http://profiles.wordpress.org/justinsainton">Justin Sainton</a>, <a href="http://profiles.wordpress.org/kadamwhite">K.Adam White</a>, <a href="http://profiles.wordpress.org/trepmal">Kailey (trepmal)</a>, <a href="http://profiles.wordpress.org/ketwaroo">Ketwaroo</a>, <a href="http://profiles.wordpress.org/kevinb">kevinB</a>, <a href="http://profiles.wordpress.org/kpdesign">Kim Parsell</a>, <a href="http://profiles.wordpress.org/kitchin">kitchin</a>, <a href="http://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/obenland">Konstantin Obenland</a>, <a href="http://profiles.wordpress.org/koopersmith">koopersmith</a>, <a href="http://profiles.wordpress.org/kurtpayne">Kurt Payne</a>, <a href="http://profiles.wordpress.org/lancewillett">Lance Willett</a>, <a href="http://profiles.wordpress.org/leewillis77">Lee Willis (leewillis77)</a>, <a href="http://profiles.wordpress.org/lessbloat">lessbloat</a>, <a href="http://profiles.wordpress.org/layotte">Lew Ayotte</a>, <a href="http://profiles.wordpress.org/lgedeon">Luke Gedeon</a>, <a href="http://profiles.wordpress.org/iworks">Marcin Pietrzak</a>, <a href="http://profiles.wordpress.org/cimmo">Marco Cimmino</a>, <a href="http://profiles.wordpress.org/marco_teethgrinder">Marco Galasso</a>, <a href="http://profiles.wordpress.org/markjaquith">Mark Jaquith</a>, <a href="http://profiles.wordpress.org/markmcwilliams">Mark McWilliams</a>, <a href="http://profiles.wordpress.org/markoheijnen">Marko Heijnen</a>, <a href="http://profiles.wordpress.org/melchoyce">Mel Choyce</a>, <a href="http://profiles.wordpress.org/tw2113">Michael Beckwith</a>, <a href="http://profiles.wordpress.org/mikehansenme">Mike Hansen</a>, <a href="http://profiles.wordpress.org/mikeschinkel">Mike Schinkel</a>, <a href="http://profiles.wordpress.org/dh-shredder">Mike Schroder</a>, <a href="http://profiles.wordpress.org/dimadin">Milan Dinic</a>, <a href="http://profiles.wordpress.org/mitchoyoshitaka">mitcho (Michael Yoshitaka Erlewine)</a>, <a href="http://profiles.wordpress.org/usermrpapa">Mr Papa</a>, <a href="http://profiles.wordpress.org/Nao">Naoko Takano</a>, <a href="http://profiles.wordpress.org/naomicbush">Naomi</a>, <a href="http://profiles.wordpress.org/alex-ye">Nashwan Doaqan</a>, <a href="http://profiles.wordpress.org/natejacobs">NateJacobs</a>, <a href="http://profiles.wordpress.org/nathanrice">nathanrice</a>, <a href="http://profiles.wordpress.org/niallkennedy">Niall Kennedy</a>, <a href="http://profiles.wordpress.org/nickdaugherty">Nick Daugherty</a>, <a href="http://profiles.wordpress.org/celloexpressions">Nick Halsey</a>, <a href="http://profiles.wordpress.org/nickmomrik">Nick Momrik</a>, <a href="http://profiles.wordpress.org/nikv">Nikhil Vimal (NikV)</a>, <a href="http://profiles.wordpress.org/nbachiyski">Nikolay Bachiyski</a>, <a href="http://profiles.wordpress.org/noahsilverstein">noahsilverstein</a>, <a href="http://profiles.wordpress.org/nofearinc">nofearinc</a>, <a href="http://profiles.wordpress.org/nukaga">nukaga</a>, <a href="http://profiles.wordpress.org/nullvariable">nullvariable</a>, <a href="http://profiles.wordpress.org/butuzov">Oleg Butuzov</a>, <a href="http://profiles.wordpress.org/paolal">Paolo Belcastro</a>, <a href="http://profiles.wordpress.org/xparham">Parham</a>, <a href="http://profiles.wordpress.org/pbiron">Paul Biron</a>, <a href="http://profiles.wordpress.org/pauldewouters">Paul de Wouters</a>, <a href="http://profiles.wordpress.org/pavelevap">pavelevap</a>, <a href="http://profiles.wordpress.org/peterjaap">peterjaap</a>, <a href="http://profiles.wordpress.org/westi">Peter Westwood</a>, <a href="http://profiles.wordpress.org/philiparthurmoore">Philip Arthur Moore</a>, <a href="http://profiles.wordpress.org/mordauk">Pippin Williamson</a>, <a href="http://profiles.wordpress.org/plocha">plocha</a>, <a href="http://profiles.wordpress.org/pollett">Pollett</a>, <a href="http://profiles.wordpress.org/ptahdunbar">Ptah Dunbar</a>, <a href="http://profiles.wordpress.org/ramiy">Rami Yushuvaev</a>, <a href="http://profiles.wordpress.org/rasheed">Rasheed Bydousi</a>, <a href="http://profiles.wordpress.org/raybernard">RayBernard</a>, <a href="http://profiles.wordpress.org/rboren">rboren</a>, <a href="http://profiles.wordpress.org/greuben">Reuben Gunday</a>, <a href="http://profiles.wordpress.org/rfair404">rfair404</a>, <a href="http://profiles.wordpress.org/iamfriendly">Richard Tape</a>, <a href="http://profiles.wordpress.org/r3df">Rick Radko</a>, <a href="http://profiles.wordpress.org/miqrogroove">Robert Chapin</a>, <a href="http://profiles.wordpress.org/rdall">Robert Dall</a>, <a href="http://profiles.wordpress.org/rodrigosprimo">Rodrigo Primo</a>, <a href="http://profiles.wordpress.org/wpmuguru">Ron Rennick</a>, <a href="http://profiles.wordpress.org/rpattillo">rpattillo</a>, <a href="http://profiles.wordpress.org/ryan">Ryan Boren</a>, <a href="http://profiles.wordpress.org/rmccue">Ryan McCue</a>, <a href="http://profiles.wordpress.org/hotchkissconsulting">Sam Hotchkiss</a>, <a href="http://profiles.wordpress.org/coffee2code">Scott Reilly</a>, <a href="http://profiles.wordpress.org/scottsweb">scottsweb</a>, <a href="http://profiles.wordpress.org/wonderboymusic">Scott Taylor</a>, <a href="http://profiles.wordpress.org/scribu">scribu</a>, <a href="http://profiles.wordpress.org/scruffian">scruffian</a>, <a href="http://profiles.wordpress.org/tenpura">Seisuke Kuraishi (tenpura)</a>, <a href="http://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/shinichin">ShinichiN</a>, <a href="http://profiles.wordpress.org/pross">Simon Prosser</a>, <a href="http://profiles.wordpress.org/simonwheatley">Simon Wheatley</a>, <a href="http://profiles.wordpress.org/siobhan">Siobhan</a>, <a href="http://profiles.wordpress.org/siobhyb">Siobhan Bamber (siobhyb)</a>, <a href="http://profiles.wordpress.org/sirzooro">sirzooro</a>, <a href="http://profiles.wordpress.org/solarissmoke">solarissmoke</a>, <a href="http://profiles.wordpress.org/sillybean">Stephanie Leary</a>, <a href="http://profiles.wordpress.org/netweb">Stephen Edgar (@netweb)</a>, <a href="http://profiles.wordpress.org/stephenharris">Stephen Harris</a>, <a href="http://profiles.wordpress.org/strangerstudios">strangerstudios</a>, <a href="http://profiles.wordpress.org/sweetie089">sweetie089</a>, <a href="http://profiles.wordpress.org/swissspidy">swissspidy</a>, <a href="http://profiles.wordpress.org/miyauchi">Takayuki Miyauchi</a>, <a href="http://profiles.wordpress.org/tmtoy">Takuma Morikawa</a>, <a href="http://profiles.wordpress.org/tlovett1">Taylor Lovett</a>, <a href="http://profiles.wordpress.org/tivnet">tivnet</a>, <a href="http://profiles.wordpress.org/tobiasbg">TobiasBg</a>, <a href="http://profiles.wordpress.org/tomauger">Tom Auger</a>, <a href="http://profiles.wordpress.org/toscho">toscho</a>, <a href="http://profiles.wordpress.org/wpsmith">Travis Smith</a>, <a href="http://profiles.wordpress.org/sorich87">Ulrich Sossou</a>, <a href="http://profiles.wordpress.org/vericgar">vericgar</a>, <a href="http://profiles.wordpress.org/vinod-dalvi">Vinod Dalvi</a>, <a href="http://profiles.wordpress.org/westonruter">Weston Ruter</a>, <a href="http://profiles.wordpress.org/wikicms">wikicms</a>, <a href="http://profiles.wordpress.org/willnorris">Will Norris</a>, <a href="http://profiles.wordpress.org/wojtekszkutnik">Wojtek Szkutnik</a>, <a href="http://profiles.wordpress.org/wycks">wycks</a>, <a href="http://profiles.wordpress.org/yoavf">Yoav Farhi</a>, and <a href="http://profiles.wordpress.org/yurivictor">Yuri Victor</a>.</p>\n<p>Enjoy what may be one of your last few manual updates. See you soon for version 3.8!</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:45:"http://wordpress.org/news/2013/10/basie/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:33:"WordPress 3.7 Release Candidate 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:77:"http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate-2/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 23 Oct 2013 00:05:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2729";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:417:"The second release candidate of WordPress 3.7 is now available for testing! Those of you already testing WordPress 3.7 will be updated automatically to RC2. (Nice.) If you&#8217;d like to start testing, there&#8217;s no time like the present! Try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”) or download the release candidate here (zip). Please post to the Alpha/Beta [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1183:"<p>The second release candidate of WordPress 3.7 is now available for testing!</p>\n<p>Those of you already testing WordPress 3.7 will be updated automatically to RC2. (<em>Nice.</em>) If you&#8217;d like to start testing, there&#8217;s no time like the present! Try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want “bleeding edge nightlies”) or <a href="http://wordpress.org/wordpress-3.7-RC2.zip">download the release candidate here</a> (zip). Please post to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a> if you think you&#8217;ve found a bug, and if any known issues are raised, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>.</p>\n<p>Developers, please test your plugins and themes against WordPress 3.7. If there is a compatibility issue, let us know as soon as possible so we can deal with it before the final release.</p>\n<p>For more on WordPress 3.7, check out the <a href="http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate/">announcement post for Release Candidate 1</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:73:"http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate-2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"Upcoming WordCamps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2013/10/upcoming-wordcamps-4/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:64:"http://wordpress.org/news/2013/10/upcoming-wordcamps-4/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Oct 2013 19:25:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:9:"Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"WordCamp";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2723";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:368:"WordCamps are casual, locally-organized conferences that celebrate everything related to WordPress, and are a great opportunity to meet other WordPress users and professionals in your community. This has been a great year for WordCamps &#8212; there have been 56 so far in more than 20 countries, and there another 15 on the calendar before the year&#8217;s [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Jen Mylo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3584:"<p><a href="http://central.wordcamp.org/">WordCamps</a> are casual, locally-organized conferences that celebrate everything related to WordPress, and are a great opportunity to meet other WordPress users and professionals in your community. This has been a great year for WordCamps &#8212; there have been 56 so far in more than 20 countries, and there another 15 on the calendar before the year&#8217;s over. If there&#8217;s one near you, check it out! In addition to getting to know your local WordPress community, most WordCamps attract some traveling visitors a well, giving you the chance to meet contributors to the WordPress open source project and <a href="http://make.wordpress.org/">get involved</a> yourself.</p>\n<p>Here are the WordCamps on the schedule for the rest of this year.</p>\n<p>October 25-27: <strong><a href="http://2013.boston.wordcamp.org/">WordCamp Boston</a></strong>, Boston, MA, USA<br />\nOctober 25-26: <strong><a href="http://2013.malaga.wordcamp.org/">WordCamp Malaga</a></strong>, Spain<br />\nOctober 26: <strong><a href="http://2013.nepal.wordcamp.org/">WordCamp Nepal</a></strong>, Kathmandu, Nepal<br />\nOctober 26: <strong><a href="http://2013.sofia.wordcamp.org/">WordCamp Sofia</a></strong>, Bulgaria<br />\nNovember 7: <strong><a href="http://2013.capetown.wordcamp.org/">WordCamp Cape Town</a></strong>, South Africa<br />\nNovember 9: <strong><a href="http://2013.porto.wordcamp.org/">WordCamp Porto</a></strong>, Portugal<br />\nNovember 9-10: <strong><a href="http://2013.kenya.wordcamp.org/">WordCamp Kenya</a></strong>, Nairobi, Kenya<br />\nNovember 15: <strong><a href="http://2013.edmonton.wordcamp.org/">WordCamp Edmonton</a></strong>, AB, Canada<br />\nNovember 16-17: <strong><a href="http://2013.orlando.wordcamp.org/">WordCamp Orlando</a></strong>, FL, USA<br />\nNovember 16: <strong><a href="http://2013.denver.wordcamp.org/">WordCamp Denver</a></strong>, CO, USA<br />\nNovember 23-24: <strong><a href="http://2013.london.wordcamp.org/">WordCamp London</a></strong>, UK<br />\nNovember 23-24: <strong><a href="http://2013.raleigh.wordcamp.org/">WordCamp Raleigh</a></strong>, NC, USA<br />\nNovember 23: <strong><a href="http://2013.saopaulo.wordcamp.org/">WordCamp São Paulo</a></strong>, Brazil<br />\nDecember 14: <strong><a href="http://2013.vegas.wordcamp.org/">WordCamp Las Vegas</a></strong>, NV, USA<br />\nDecember 14-15: <strong><a href="http://2013.sevilla.wordcamp.org/">WordCamp Sevilla</a></strong>, Spain</p>\n<p>No WordCamps on this list in your area? Not to worry! There are thriving <a href="http://wordpress.meetup.com/">WordPress meetups</a> all over the world where you can meet like-minded people, and we maintain a library of <a href="http://wordpress.tv/category/wordcamptv/">WordCamp videos</a> at <a href="http://wordpress.tv/">WordPress.tv</a>.</p>\n<h3>Get Involved</h3>\n<ul>\n<li>If you&#8217;re interested in organizing a WordCamp in your area, check out our <a href="http://plan.wordcamp.org/">WordCamp planning</a> site.</li>\n<li>If you&#8217;re interested in <a href="http://make.wordpress.org/community/meetup-interest-form/">starting a WordPress meetup</a> in your area, let us know and we can set up a group on meetup.com for you.</li>\n<li>And speaking of WordCamp videos, we&#8217;ve recently enabled volunteer-generated subtitles/closed captioning of the videos on WordPress.tv to make them more accessible. Interested in helping? Check out the <a href="http://wordpress.tv/using-amara-org-to-caption-or-subtitle-a-wordpress-tv-video/">WordPress.tv subtitling instructions</a>.</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"http://wordpress.org/news/2013/10/upcoming-wordcamps-4/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 3.7 Release Candidate";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:66:"http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:75:"http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Oct 2013 19:52:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=2718";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:331:"The first release candidate for WordPress 3.7 is now available! In RC 1, we&#8217;ve made some adjustments to the update process to make it more reliable than ever. We hope to ship WordPress 3.7 next week, but we need your help to get there. If you haven’t tested 3.7 yet, there’s no time like the present. (Please, [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2274:"<p>The first release candidate for WordPress 3.7 is now available!</p>\n<p>In RC 1, we&#8217;ve made some adjustments to the update process to make it more reliable than ever. We hope to ship WordPress 3.7 <em>next week</em>, but we need your help to get there. If you haven’t tested 3.7 yet, there’s no time like the present. (Please, not on a production site, unless you’re adventurous.)</p>\n<p>WordPress 3.7 introduces <strong>automatic background updates</strong> for security and minor releases (like updating from 3.7 to 3.7.1). These are really easy to test  — RC 1 will update every 12 hours or so to the latest development version, and then email you the results. (You may get two emails: one for debugging, and one all users of 3.7 will receive.) If something went wrong, you can report it.</p>\n<p><strong>Think you’ve found a bug? </strong>Please post to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a>. If any known issues come up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>.</p>\n<p>To test WordPress 3.7 RC1, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want “bleeding edge nightlies”). Or you can <a href="http://wordpress.org/wordpress-3.7-RC1.zip">download the release candidate here</a> (zip). If you’d like to learn more about what&#8217;s new in WordPress 3.7, visit the awesome About screen in your dashboard (<strong><img alt="" src="http://i0.wp.com/core.svn.wordpress.org/branches/3.6/wp-content/themes/twentyten/images/wordpress.png?w=692" data-recalc-dims="1" /> → About</strong> in the toolbar). There, you can also see if your install is eligible for background updates. WordPress won’t automatically update, for example, if you’re using version control like Subversion or Git.</p>\n<p><strong>Developers,</strong> please test your plugins and themes against WordPress 3.7, so that if there is a compatibility issue, we can figure it out before the final release. Make sure you post any issues to the support forums.</p>\n<p><em>WordPress three seven</em><br />\n<em>A self-updating engine</em><br />\n<em>Lies beneath the hood</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:71:"http://wordpress.org/news/2013/10/wordpress-3-7-release-candidate/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:31:"http://wordpress.org/news/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Mon, 27 Jan 2014 14:58:27 GMT";s:12:"content-type";s:23:"text/xml; charset=UTF-8";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:10:"x-pingback";s:36:"http://wordpress.org/news/xmlrpc.php";s:13:"last-modified";s:29:"Thu, 23 Jan 2014 20:54:06 GMT";s:4:"x-nc";s:11:"HIT lax 249";}s:5:"build";s:14:"20130911020210";}', 'no');
INSERT INTO `wp_options` VALUES
(113, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1390877885', 'no'),
(114, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1390834685', 'no'),
(115, '_transient_timeout_feed_867bd5c64f85878d03a060509cd2f92c', '1390877886', 'no');
INSERT INTO `wp_options` VALUES
(116, '_transient_feed_867bd5c64f85878d03a060509cd2f92c', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:61:"\n	\n	\n	\n	\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"WordPress Planet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:28:"http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:47:"WordPress Planet - http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:50:{i:0;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:109:"WordPress.tv: Ilona Filipi: 3.5 Years Of Running A WordPress Web Agency: Do’s, Don’ts and Lessons Learned";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30114";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:105:"http://wordpress.tv/2014/01/26/3-5-years-of-running-a-wordpress-web-agency-dos-donts-and-lessons-learned/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:754:"<div id="v-KA8Evmxe-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30114/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30114/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30114&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/26/3-5-years-of-running-a-wordpress-web-agency-dos-donts-and-lessons-learned/"><img alt="Ilona Filipi: 3.5 Years Of Running A WordPress Web Agency: Do&#8217;s, Don&#8217;ts and Lessons Learned" src="http://videos.videopress.com/KA8Evmxe/video-55a1472e32_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 27 Jan 2014 03:16:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:62:"WordPress.tv: Austin Smith: Big Media Strategies For WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30093";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:79:"http://wordpress.tv/2014/01/26/austin-smith-big-media-strategies-for-wordpress/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:673:"<div id="v-MGFc7mdA-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30093/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30093/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30093&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/26/austin-smith-big-media-strategies-for-wordpress/"><img alt="Austin Smith: Big Media Strategies For WordPress" src="http://videos.videopress.com/MGFc7mdA/video-e113f9b8cd_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 27 Jan 2014 00:13:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Matt: Marco on Long-Form";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43480";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:40:"http://ma.tt/2014/01/marco-on-long-form/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:97:"<p>Marco Arment on <a href="http://www.marco.org/2014/01/26/long-form">Long-Form content</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 26 Jan 2014 21:57:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:87:"WordPress.tv: David Lockie: 10 Ways That WordPressers Can Make The World A Better Place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30102";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:104:"http://wordpress.tv/2014/01/25/david-lockie-10-ways-that-wordpressers-can-make-the-world-a-better-place/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:723:"<div id="v-eRcBXwZA-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30102/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30102/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30102&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/25/david-lockie-10-ways-that-wordpressers-can-make-the-world-a-better-place/"><img alt="David Lockie: 10 Ways That WordPressers Can Make The World A Better Place" src="http://videos.videopress.com/eRcBXwZA/video-370b734fce_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 26 Jan 2014 00:14:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WordPress.tv: Hristo Pandjarov: Need For Speed: Gear Up Your WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30087";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:86:"http://wordpress.tv/2014/01/25/hristo-pandjarov-need-for-speed-gear-up-your-wordpress/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:688:"<div id="v-1nPSHx0E-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30087/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30087/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30087&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/25/hristo-pandjarov-need-for-speed-gear-up-your-wordpress/"><img alt="Hristo Pandjarov: Need For Speed: Gear Up Your WordPress" src="http://videos.videopress.com/1nPSHx0E/video-99b7cff76f_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 26 Jan 2014 00:06:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"WPTavern: WPWeekly Episode 135 – Podcasting With WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:44:"http://wptavern.com?p=15427&preview_id=15427";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:156:"http://wptavern.com/wpweekly-episode-135-podcasting-with-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=wpweekly-episode-135-podcasting-with-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3563:"<p>In this episode of WordPress Weekly, I was joined by <a href="http://marcuscouch.com/" title="http://marcuscouch.com/">Marcus Couch</a> and Matt Medeiros of <a href="http://mattreport.com/" title="http://mattreport.com/">Mattreport.com</a> and founder of <a href="http://slocumstudio.com/" title="http://slocumstudio.com/">Slocumstudio.com</a>. I threw out the show notes for this episode and instead, tapped into the collective knowledge of my guests to discuss the world of podcasting with WordPress. The first part of the conversation covers equipment, audio quality, and audience while the second half focuses on WordPress. One thing immediately became clear. We&#8217;re all fans of the <a href="http://wordpress.org/plugins/powerpress/" title="http://wordpress.org/plugins/powerpress/">Blubrry Powerpress</a> plugin. If you&#8217;re thinking about starting a show and using WordPress to publish it, you&#8217;ll want to listen to this episode!</p>\n<h2>Stories Discussed:</h2>\n<p><a href="http://wptavern.com/wordpress-developers-take-note-tinymce-4-0-merged-into-core" title="http://wptavern.com/wordpress-developers-take-note-tinymce-4-0-merged-into-core">WordPress Developers Take Note: TinyMCE 4.0 Merged Into Core</a><br />\n<a href="http://wptavern.com/interview-with-jason-schuller-founder-of-press75-com" title="http://wptavern.com/interview-with-jason-schuller-founder-of-press75-com">Interview With Jason Schuller Founder Of Press75.com</a><br />\n<a href="http://wptavern.com/tickets-on-sale-for-wordcamp-dayton-ohio" title="http://wptavern.com/tickets-on-sale-for-wordcamp-dayton-ohio">Tickets On Sale For WordCamp Dayton, Ohio</a><br />\n<a href="http://wptavern.com/wordpress-3-8-1-released-fixes-twitter-oembed-issues" title="http://wptavern.com/wordpress-3-8-1-released-fixes-twitter-oembed-issues">WordPress 3.8.1 Released: Fixes Twitter oEmbed Issues</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href="http://wordpress.org/plugins/google-drive-wp-media/" title="http://wordpress.org/plugins/google-drive-wp-media/">Google Drive WP Media</a> allows direct access to your Google Drive, enabling you to manage your files remotely from your WordPress blog. Upload and share your files directly from your WordPress blog to Google Drive and back again.</p>\n<p><a href="http://wordpress.org/plugins/skype-mobile-switcher/" title="http://wordpress.org/plugins/skype-mobile-switcher/">Skype Mobile Switcher</a> uses a shortcode to switch between presenting a Skype call link and a phone number that can be clicked to call. </p>\n<p><a href="http://wordpress.org/plugins/dynamic-home-length/" title="http://wordpress.org/plugins/dynamic-home-length/">Dynamic Home Length</a> adjusts the number of posts per page of the front page based on the total amount of text in all recent posts so that its height will automatically be in proportional with the height of your widget column.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Friday, January 31st 3 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738" target="_blank">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href="http://www.wptavern.com/feed/podcast" target="_blank">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr" target="_blank">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #135:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 25 Jan 2014 03:17:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:74:"WPTavern: Technique For Creating Portable Social Menus In WordPress Themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15271";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:192:"http://wptavern.com/technique-for-creating-portable-social-menus-in-wordpress-themes?utm_source=rss&utm_medium=rss&utm_campaign=technique-for-creating-portable-social-menus-in-wordpress-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1903:"<p>One of the features within the <a href="http://themehybrid.com/themes/stargazer" title="http://themehybrid.com/themes/stargazer">Stargazer</a> child theme we are using on WPTavern are the social icons located at the bottom of the site. The social icons are not images but rather, <a href="http://genericons.com/" title="http://genericons.com/">Genericons</a>. As explained by <a href="http://kovshenin.com/2014/social-menus-in-wordpress-themes/" title="http://kovshenin.com/2014/social-menus-in-wordpress-themes/">Konstantin Kovshenin</a>, Justin Tadlock used a method to add social network icons that are portable between themes. By using a few simple CSS selectors, the social links are able to be targeted by their <em>href</em> attribute.</p>\n<blockquote><p>No more plugin dependencies, no more long docs of CSS class names, no more arguing with the Theme Reviewers Theme on WordPress.org that social profile icons are part of the appearance of a theme and not “plugin territory” because users can lose their content upon theme switch.</p></blockquote>\n<p>Justin Tadlock published <a href="http://justintadlock.com/archives/2013/08/07/social-media-nav-menus" title="http://justintadlock.com/archives/2013/08/07/social-media-nav-menus">two</a> different <a href="http://justintadlock.com/archives/2013/08/14/social-nav-menus-part-2" title="http://justintadlock.com/archives/2013/08/14/social-nav-menus-part-2">posts</a> that explain the thought process behind the technique as well as the code needed to make it work. It&#8217;s being championed by the WordPress theme community to the point of it possibly being added to the <a href="https://make.wordpress.org/docs/theme-developer-handbook/releasing-your-theme/theme-review-guidelines/" title="https://make.wordpress.org/docs/theme-developer-handbook/releasing-your-theme/theme-review-guidelines/">WordPress Theme Review Guidelines</a>. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 24 Jan 2014 22:06:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:72:"WPTavern: Status App: A WordPress-Powered Mobile Micro Messaging Service";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14785";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:186:"http://wptavern.com/status-app-a-wordpress-powered-mobile-micro-messaging-service?utm_source=rss&utm_medium=rss&utm_campaign=status-app-a-wordpress-powered-mobile-micro-messaging-service";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3595:"<p>As Matt Mullenweg predicted in the State of the Word address in 2013, this new year brings with it a growing excitement around building applications based on WordPress. The launch of <a href="http://wptavern.com/apppresser-launches-first-mobile-app-development-framework-for-wordpress" target="_blank">AppPresser</a>, the first mobile application framework for WordPress, produced a healthy buzz around the idea and now the community is primed for more.</p>\n<p>Ryan Fugate, better known around the web as &#8220;<a href="https://twitter.com/modemlooper" target="_blank">@modemlooper</a>&#8220;, has created a WordPress-powered micro messaging app for mobile. <a href="http://taptappress.com/status-app/" target="_blank">Status App</a> is actually a WordPress plugin that creates a Twitter type micro blogging platform for mobile users at your chosen URL.</p>\n<p><img src="http://wptavern.com/wp-content/uploads/2014/01/status.png" alt="status" width="906" height="454" class="aligncenter size-full wp-image-15390" /></p>\n<p>Want to try it? Visit this URL from a mobile browser: <a href="http://status.taptappress.com/status" target="_blank">http://status.taptappress.com/status</a></p>\n<p>The status updates are stored as a custom post type within WordPress and can be managed from the admin. Right now the app doesn&#8217;t include a settings panel. You simply activate the plugin and then visit your site on mobile. </p>\n<p><img src="http://wptavern.com/wp-content/uploads/2014/01/status-cpt.png" alt="status-cpt" width="985" height="302" class="aligncenter size-full wp-image-15403" /></p>\n<p>Since Status App is technically a social app, why didn&#8217;t he build it with BuddyPress? Ryan explained his reasoning when he <a href="http://taptappress.com/status-app/" target="_blank">introduced</a> the app: </p>\n<blockquote><p>This could have been an app for BuddyPress but I am targeting a different group of users. BuddyPress is for front sided social networks with lots of features. Status App is for the content creators of a site. If you have ever used Yammer then you can understand the need for this type of functionality.</p></blockquote>\n<p>For now, @modemlooper is completing more user testing on multiple devices before the beta release of the plugin. More features are currently in the works, including @mentions, favoriting, profile editing, private messages. He plans to release Status App as a free plugin with a commercial version available to include more settings and add additional features. </p>\n<p>Check out @modemlooper&#8217;s <a href="http://taptappress.com/news/" target="_blank">TapTapPress blog</a> for more discussions on developing mobile apps for WordPress. If you&#8217;re testing the Status App and can help with reporting any issues, <a href="http://taptappress.com/contact/" target="_blank">get in touch with Ryan</a> and let him know the type of device you&#8217;re using.</p>\n<p>I tested Status App last night and found it to be ridiculously simple and enjoyable to use. Additionally, unlike using Twitter, you own your own data when you create your own messaging service. I believe it&#8217;s apps like these that will lead to the ultimate crumbling of the massive social data silos that feed you advertisements and blatantly disregard user privacy. Eventually, users are going to be fed up and will flock to simple private social networks like the kind you can create with Status App. We&#8217;ll be closely following the evolution of this app and will let you know when you can download the free plugin to create your own micro messaging service.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 24 Jan 2014 20:43:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"WPTavern: 30 Beautiful Brewery Websites Built With WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15321";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:164:"http://wptavern.com/30-beautiful-brewery-websites-built-with-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=30-beautiful-brewery-websites-built-with-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8099:"<p>While the WordPress community continues to grow and expand every day, so does the craft beer scene. So it only makes sense that a growing number of craft breweries are choosing to build their websites on WordPress. After all, WordPress and craft beer have a lot in common: enthusiasm, loyalty, broad appeal, no shortage of strong opinions and a community of contributors of every stripe. </p>\n<p>Craft brewers often share many of the same ideals found in open source culture, including  the cheerful sharing of knowledge, skills, recipes and the strong support of each other&#8217;s work. You might even say that craft brewing culture is the open source version of the beer industry. With that in mind, here are 30 beautiful brewery websites that have been built with WordPress. Pour your favorite local pint, sit back, and enjoy. Cheers!</p>\n<h3>Groundswell Brewing Company</h3>\n<p><a href="http://groundswellbrew.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/groundswell.png" alt="groundswell" width="1400" height="791" class="aligncenter size-full wp-image-15322" /></a></p>\n<h3>The Post Brewing Co.</h3>\n<p><a href="http://www.postbrewing.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/thepost.png" alt="thepost" width="1280" height="800" class="aligncenter size-full wp-image-15327" /></a></p>\n<h3>Canal Park Brewing Company</h3>\n<p><a href="http://canalparkbrewery.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/canalpark.png" alt="canalpark" width="1400" height="884" class="aligncenter size-full wp-image-15332" /></a></p>\n<h3>Brewsters Brewing Company</h3>\n<p><a href="http://brewsters.ca/"><img src="http://wptavern.com/wp-content/uploads/2014/01/brewsters.png" alt="brewsters" width="1400" height="836" class="aligncenter size-full wp-image-15330" /></a></p>\n<h3>Camden Town Brewery</h3>\n<p><a href="http://www.camdentownbrewery.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/camdentownbrewery.png" alt="camdentownbrewery" width="1400" height="804" class="aligncenter size-full wp-image-15333" /></a></p>\n<h3>Cook Ale Works</h3>\n<p><a href="http://coopaleworks.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/coop.png" alt="coop" width="1400" height="759" class="aligncenter size-full wp-image-15335" /></a></p>\n<h3>Rogness Brewing Company</h3>\n<p><a href="http://rognessbrewing.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/rogness.png" alt="rogness" width="1400" height="703" class="aligncenter size-full wp-image-15337" /></a></p>\n<h3>Driftwood Brewery</h3>\n<p><a href="http://driftwoodbeer.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/driftwood.png" alt="driftwood" width="1227" height="856" class="aligncenter size-full wp-image-15338" /></a></p>\n<h3>Brouwerij ‘t IJ</h3>\n<p><a href="http://www.brouwerijhetij.nl/"><img src="http://wptavern.com/wp-content/uploads/2014/01/Brouwerij-‘t-IJ.png" alt="Brouwerij ‘t IJ" width="1500" height="740" class="aligncenter size-full wp-image-15357" /></a></p>\n<h3>Carolina Brewery</h3>\n<p><a href="http://carolinabrewery.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/carolinabrewery.png" alt="carolinabrewery" width="1400" height="943" class="aligncenter size-full wp-image-15341" /></a></p>\n<h3>Matso&#8217;s Broome Brewery</h3>\n<p><a href="http://www.matsos.com.au/"><img src="http://wptavern.com/wp-content/uploads/2014/01/matsos.png" alt="matsos" width="1400" height="915" class="aligncenter size-full wp-image-15343" /></a></p>\n<h3>Hargreaves Hill Brewing Company</h3>\n<p><a href="http://www.hargreaveshill.com.au/"><img src="http://wptavern.com/wp-content/uploads/2014/01/hargreaves.jpg" alt="hargreaves" width="1440" height="822" class="aligncenter size-full wp-image-15378" /></a></p>\n<h3>Prairie Artisan Ales</h3>\n<p><a href="http://prairieales.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/prairie.png" alt="prairie" width="1500" height="930" class="aligncenter size-full wp-image-15345" /></a></p>\n<h3>U Fleků</h3>\n<p><a href="http://ufleku.cz/"><img src="http://wptavern.com/wp-content/uploads/2014/01/UFleku.jpg" alt="UFleku" width="1312" height="826" class="aligncenter size-full wp-image-15372" /></a></p>\n<h3>Widmer Brothers</h3>\n<p><a href="http://widmerbrothers.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/widmer.png" alt="widmer" width="1500" height="820" class="aligncenter size-full wp-image-15347" /></a></p>\n<h3>Gigantic Brewing Company</h3>\n<p><a href="http://giganticbrewing.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/gigantic.png" alt="gigantic" width="1500" height="817" class="aligncenter size-full wp-image-15349" /></a></p>\n<h3>Mikkeller</h3>\n<p><a href="http://mikkeller.dk/"><img src="http://wptavern.com/wp-content/uploads/2014/01/mikkeller.jpg" alt="mikkeller" width="1322" height="830" class="aligncenter size-full wp-image-15375" /></a></p>\n<h3>Bonfire Brewing</h3>\n<p><a href="http://bonfirebrewing.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/bonfire-brewing.png" alt="bonfire-brewing" width="1500" height="899" class="aligncenter size-full wp-image-15351" /></a></p>\n<h3>Monkey Paw Brewing</h3>\n<p><a href="http://monkeypawbrewing.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/monkeypaw.png" alt="monkeypaw" width="1060" height="878" class="aligncenter size-full wp-image-15353" /></a></p>\n<h3>Yowie Beer</h3>\n<p><a href="http://yowiebeer.com.au/"><img src="http://wptavern.com/wp-content/uploads/2014/01/yowie.jpg" alt="yowie" width="1326" height="918" class="aligncenter size-full wp-image-15382" /></a></p>\n<h3>Thorn St. Brewery</h3>\n<p><a href="http://thornstreetbrew.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/thornstbrewery.png" alt="thornstbrewery" width="1500" height="983" class="aligncenter size-full wp-image-15355" /></a></p>\n<h3>Brouwerij De 7 Deugden</h3>\n<p><a href="http://www.de7deugden.nl/"><img src="http://wptavern.com/wp-content/uploads/2014/01/Brouwerij-De-7-Deugden.png" alt="Brouwerij De 7 Deugden" width="1500" height="1036" class="aligncenter size-full wp-image-15359" /></a></p>\n<h3>Redemption Brewing Co.</h3>\n<p><a href="http://www.redemptionbrewing.co.uk/"><img src="http://wptavern.com/wp-content/uploads/2014/01/redemption.jpg" alt="redemption" width="1054" height="896" class="aligncenter size-full wp-image-15364" /></a></p>\n<h3>Oskar Blue Brewery</h3>\n<p><a href="http://oskarblues.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/oskar-blues.jpg" alt="oskar-blues" width="1100" height="880" class="aligncenter size-full wp-image-15365" /></a></p>\n<h3>Hops and Grains</h3>\n<p><a href="http://www.hopsandgrain.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/hopsandgrains.jpg" alt="hopsandgrains" width="1036" height="798" class="aligncenter size-full wp-image-15367" /></a></p>\n<h3>Captain Lawrence Brewing Company</h3>\n<p><a href="http://www.captainlawrencebrewing.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/captainlawrence.jpg" alt="captainlawrence" width="1098" height="830" class="aligncenter size-full wp-image-15368" /></a></p>\n<h3>Red Hook</h3>\n<p><a href="http://redhook.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/redhook.jpg" alt="redhook" width="1134" height="824" class="aligncenter size-full wp-image-15370" /></a></p>\n<h3>Manchester Marble Beers</h3>\n<p><a href="http://www.marblebeers.com/"><img src="http://wptavern.com/wp-content/uploads/2014/01/marble.jpg" alt="marble" width="1026" height="748" class="aligncenter size-full wp-image-15384" /></a></p>\n<h3>Dugges Ale &#038; Porterbryggeri</h3>\n<p><a href="http://dugges.se/"><img src="http://wptavern.com/wp-content/uploads/2014/01/dugges.jpg" alt="dugges" width="1098" height="680" class="aligncenter size-full wp-image-15376" /></a></p>\n<h3>Hawthorne Brewing Co.</h3>\n<p><a href="http://hawthornbrewing.com.au/"><img src="http://wptavern.com/wp-content/uploads/2014/01/hawthorne.jpg" alt="hawthorne" width="1080" height="914" class="aligncenter size-full wp-image-15380" /></a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 24 Jan 2014 18:47:07 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:56:"WordPress.tv: Marko Heijnen: Building Plugins Like A Pro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30007";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"http://wordpress.tv/2014/01/24/marko-heijnen-building-plugins-like-a-pro/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:661:"<div id="v-GucbrQSP-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30007/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30007/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30007&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/24/marko-heijnen-building-plugins-like-a-pro/"><img alt="Marko Heijnen: Building Plugins Like A Pro" src="http://videos.videopress.com/GucbrQSP/video-abf855d2e0_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 24 Jan 2014 16:06:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:54:"WordPress.tv: Luke Oatham: GovIntranet WordPress Theme";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30013";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"http://wordpress.tv/2014/01/24/luke-oatham-govintranet-wordpress-theme/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:657:"<div id="v-UQ0KX6xM-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30013/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30013/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30013&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/24/luke-oatham-govintranet-wordpress-theme/"><img alt="Luke Oatham: GovIntranet WordPress Theme" src="http://videos.videopress.com/UQ0KX6xM/video-240a36afb3_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 24 Jan 2014 13:25:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:68:"WPTavern: PressCastle Aims to Put Every WordPress Theme in One Place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15264";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:180:"http://wptavern.com/presscastle-aims-to-put-every-wordpress-theme-in-one-place?utm_source=rss&utm_medium=rss&utm_campaign=presscastle-aims-to-put-every-wordpress-theme-in-one-place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3057:"<p><a href="http://presscastle.com/" target="_blank">PressCastle</a> launched this month with an ambitious goal: to put every WordPress theme in one place. The site currently has more than 13,000 themes that are categorized and searchable. The themes were collected from more than 250 sites and represent 400+ theme authors.</p>\n<p>If you visit the <a href="http://presscastle.com/themes/" target="_blank">Themes section</a> of the site you can filter themes based on price, layout, framework and genre with subcategories for each. PressCastle is in the process of adding filters to the themes to specify compatibility with multisite, BuddyPress, bbPress, Jigoshop and other commonly used plugins.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/presscastle-themes.jpg" rel="prettyphoto[15264]"><img src="http://wptavern.com/wp-content/uploads/2014/01/presscastle-themes.jpg" alt="presscastle-themes" width="946" height="491" class="aligncenter size-full wp-image-15298" /></a></p>\n<p>The site is using affiliate links on the themes to help fund the efforts required for indexing this massive library. The launch post claims that they now have the largest and most up to date index of WordPress themes on the web. They plan to update it with new theme releases and remove discontinued items along the way.</p>\n<p>I entered a few common search terms related to WordPress themes and found that the search engine was quite accurate in returning relevant information. Although, from a consumer standpoint, I have a difficult time connecting with the whole medieval castle theme they&#8217;ve got running, I can see the utility in the indexing and searching capabilities PressCastle provides. But does it solve a real problem?</p>\n<h3>Are WordPress Theme Indexing Sites a Fad?</h3>\n<p>The fact that themes are scattered throughout hundreds of websites can make it difficult to locate one that you want to use. PressCastle is trying to provide a solution for this. <a href="http://wptavern.com/theme-friendly-helps-you-find-the-perfect-wordpress-theme" target="_blank">Theme Friendly</a> is another site that recently launched with a similar goal of helping users find the perfect WordPress theme. While Theme Friendly has a different angle in that it provides reviews on the quality of themes, the work is similarly powered by affiliate links. Only time will tell whether affiliate commissions will be adequate compensation for the amount of effort required to keep these indexes current.</p>\n<p>Theme indexing sites seem to be popping up quite frequently these days, all of them vying to capitalize on the high demand for WordPress themes and the difficulty users have when searching. The question remains &#8211; will any of these sites actually take off and gain a following? In many cases their efforts seem to be duplicating the results a user might find with a reasonably formed search engine query. So I put the question to you: <strong>Are you likely to visit a WordPress theme indexing site when shopping for your next theme?</strong></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 24 Jan 2014 00:09:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:12;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:38:"Alex King: Owning Your Online Identity";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://alexking.org/?p=19292";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:63:"http://crowdfavorite.com/blog/2014/01/own-your-online-identity/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1470:"<div>\n	<img width="160" height="120" src="http://alexking.org/wp-content/uploads/2014/01/Screen-Shot-2014-01-23-at-2.39.30-PM-160x120.png" class="attachment-thumb-img wp-post-image" alt="Post at the Crowd Favorite blog" /></div>\n<p>I&#8217;ve put up a post on the <a href="http://crowdfavorite.com/blog/">Crowd Favorite blog</a> about how I use WordPress and the <a href="http://crowdfavorite.com/favepersonal/">FavePersonal</a> theme (free!) to own my online identity, while still participating with my friends on Facebook and Twitter.</p>\n<p>I love how I have (on my own site) a history of the social reactions to <a href="http://alexking.org/blog/2013/04/24/capsule-the-developers-code-journal">posts like this</a>. Here&#8217;s a <a href="http://alexking.org/blog/2014/01/09/ipad-use-and-productivity">more casual example</a>; where the social reactions really add to the overall story.</p>\n<p>I think owning your online identity is hugely important &#8211; don&#8217;t outsource it to some 3rd-party service. But there&#8217;s no reason not to take advantage of the benefits of those services. I want to have my cake and eat it to &#8211; and I believe I&#8217;m doing just that.</p>\n<p class="threads-post-notice">This post is part of the project: <a href="http://alexking.org/project/favepersonal">FavePersonal</a>. View the project timeline for more context on this post.</p>\n<p><a href="http://alexking.org/blog/2014/01/23/owning-your-online-identity">#</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 21:41:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Alex";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:63:"WPTavern: WordPress 3.8.1 Released: Fixes Twitter oEmbed Issues";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=13644";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:168:"http://wptavern.com/wordpress-3-8-1-released-fixes-twitter-oembed-issues?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-3-8-1-released-fixes-twitter-oembed-issues";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2429:"<p>WordPress 3.8.1 was <a href="http://wordpress.org/news/2014/01/wordpress-3-8-1/" target="_blank">released</a> today with more than 30 tickets resolved for this <a href="https://core.trac.wordpress.org/query?milestone=3.8.1" target="_blank">milestone</a>. Automatic background updates will be gradually rolled out over the next 24 hours.</p>\n<p>One of the most notable fixes was switching Twitter oEmbed to SSL. Twitter changed its API, which broke Twitter oEmbed links across all WordPress installations. If you&#8217;ve got a lot of content with embedded tweets, then upgrading to WordPress 3.8.1 should be a high priority for you. </p>\n<p>Additionally, WordPress 3.8.1 addresses some issues with taxonomy queries in WP_Query, general fixes for the newly designed admin areas and resolves a strange bug with &#8220;dead zones&#8221; on submit buttons.</p>\n<h3>An Impressive Success Rate For Automatic Updates</h3>\n<p>Skeptics of WordPress 3.7&#8242;s automatic updates feature may be interested in looking at the results so far. The success rate for automatic updates with WordPress 3.8 was astonishing, given that it was a major release, with many major changes. Andrew Nacin <a href="http://make.wordpress.org/core/2013/12/18/automatic-updates-for-3-8-started-to-flow-early/" target="_blank">cites</a> the stats for critical failures:</p>\n<blockquote><p>Success rate is around 99.78 percent of about 15,000 updates. That’s a bit lower than 3.7.1, which was 99.988 percent for about a million updates. This is to be expected; for example, far more files were changed.</p></blockquote>\n<p>When referring to critical failures, Nacin clarifies that these are not disaster scenarios, as the term might seem to indicate. &#8220;<strong>Remember that a critical failure (what these numbers are calculating) only means &#8216;we started to copy files and failed to verify we copied all of them&#8217;</strong>,&#8221; he clarified. &#8220;It doesn&#8217;t mean the site crashed and burned.&#8221; </p>\n<p>These stats are good news for any WordPress admin who has been hesitant to have automatic background updates turned on for minor releases. If you previously had background updates turned off, now might be a good time to consider <a href="http://wptavern.com/how-to-configure-automatic-core-updates-for-wordpress-3-7" target="_blank">re-configuring your settings</a> to include automatic core updates for minor releases. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 21:24:17 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:45:"Dev Blog: WordPress 3.8.1 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3063";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2014/01/wordpress-3-8-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3834:"<p>After six weeks and more than <a href="http://wordpress.org/download/counter/">9.3 million downloads</a> of WordPress 3.8, we&#8217;re pleased to announce WordPress 3.8.1 is now available.</p>\n<p>Version 3.8.1 is a maintenance releases that addresses 31 bugs in 3.8, including various fixes and improvements for the new dashboard design and new themes admin screen. An issue with taxonomy queries in WP_Query was resolved. And if you&#8217;ve been frustrated by submit buttons that won&#8217;t do anything when you click on them (or thought you were going crazy, like some of us), we&#8217;ve found and fixed this &#8220;dead zone&#8221; on submit buttons.</p>\n<p>It also contains a fix for <strong>embedding tweets</strong> (by placing the URL to the tweet on its own line), which was broken due to a recent Twitter API change. (For more on Embeds, see <a href="http://codex.wordpress.org/Embeds">the Codex</a>.)</p>\n<p>For a full list of changes, consult the <a href="http://core.trac.wordpress.org/query?milestone=3.8.1">list of tickets</a> and <a href="https://core.trac.wordpress.org/log/branches/3.8?rev=27018&stop_rev=26862">the changelog</a>. There&#8217;s also a <a href="http://make.wordpress.org/core/2014/01/22/wordpress-3-8-1-release-candidate/">detailed summary</a> for developers on the development blog.</p>\n<p>If you are one of the millions already running WordPress 3.8, we will start rolling out automatic background updates for WordPress 3.8.1 in the next few hours. For sites <a href="http://wordpress.org/plugins/background-update-tester/">that support them</a>, of course.</p>\n<p><a href="http://wordpress.org/download/">Download WordPress 3.8.1</a> or venture over to <strong>Dashboard → Updates</strong> and simply click &#8220;Update Now.&#8221;</p>\n<p>Thanks to all of these fine individuals for contributing to 3.8.1:</p>\n<p><a href="http://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="http://profiles.wordpress.org/collinsinternet">Allan Collins</a>, <a href="http://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/aubreypwd">Aubrey Portwood</a>, <a href="http://profiles.wordpress.org/empireoflight">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/cojennin">Connor Jennings</a>, <a href="http://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="http://profiles.wordpress.org/fboender">fboender</a>, <a href="http://profiles.wordpress.org/avryl">Janneke Van Dorpe</a>, <a href="http://profiles.wordpress.org/janrenn">janrenn</a>, <a href="http://profiles.wordpress.org/joedolson">Joe Dolson</a>, <a href="http://profiles.wordpress.org/johnbillion">John Blackbourn</a>, <a href="http://wordpress.org/news/feed/">José Pino</a>, <a href="http://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/matveb">Matias Ventura</a>, <a href="http://profiles.wordpress.org/mattheu">Matthew Haines-Young</a>, <a href="http://profiles.wordpress.org/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/melchoyce">Mel Choyce</a>, <a href="http://profiles.wordpress.org/batmoo">Mohammad Jangda</a>, <a href="http://profiles.wordpress.org/morganestes">Morgan Estes</a>, <a href="http://profiles.wordpress.org/nivijah">nivijah</a>, <a href="http://profiles.wordpress.org/wonderboymusic">Scott Taylor</a>, <a href="http://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/undergroundnetwork">undergroundnetwork</a>, and <a href="http://profiles.wordpress.org/yurivictor">Yuri Victor</a>.</p>\n<p><em>WordPress three eight one<br />\nWe heard you didn&#8217;t like bugs<br />\nSo we took them out</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 20:37:49 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:15;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:79:"WPTavern: Behind The Scenes In The WordPress Plugin Directory With Mika Epstein";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15237";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:202:"http://wptavern.com/behind-the-scenes-in-the-wordpress-plugin-directory-with-mika-epstein?utm_source=rss&utm_medium=rss&utm_campaign=behind-the-scenes-in-the-wordpress-plugin-directory-with-mika-epstein";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10264:"<p>The <a href="http://wordpress.org/plugins/" target="_blank">WordPress Plugin Directory</a> currently lists more than 29,000 plugins. It&#8217;s the first stop for any WordPress user looking to extend the capabilities of the software. With over 585 million downloads and a massive worldwide user base, it takes a dedicated team to monitor the quality and security of so many extensions.</p>\n<p><div id="attachment_15252" class="wp-caption alignright"><a href="http://wptavern.com/wp-content/uploads/2014/01/ipstenu.jpg" rel="prettyphoto[15237]"><img src="http://wptavern.com/wp-content/uploads/2014/01/ipstenu-332x500.jpg" alt="Mika Epstein - photo credit: ma.tt " width="332" height="500" class="size-large wp-image-15252" /></a><p class="wp-caption-text">Mika Epstein &#8211; photo credit: <a href="http://ma.tt/2012/08/wcsf-hack-day/mcm_3384-3/" target="_blank">ma.tt</a></p></div>\n<p>I had the opportunity to interview Mika Epstein, better known around the web as &#8220;<a href="https://twitter.com/ipstenu" target="_blank">Ipstenu</a>&#8220;, about her work behind the scenes with the plugin directory. Epstein is part of a team of folks, including Scott Reilly, Pippin Williamson, Otto, and a handful of others, who stand at the door of the repository and review incoming plugins to make sure they meet the <a href="http://wordpress.org/plugins/about/guidelines/" target="_blank">guidelines</a>.</p>\n<p>How does someone get involved with reviewing plugins for WordPress? For Mika it was in the vein with something she&#8217;d be doing already. She has a passion for helping plugins play nice with WordPress. </p>\n<blockquote><p>Otto reached out to me to join the plugin review team after I started, on my own, scanning the repo using <a href="https://github.com/markjaquith/WordPress-Plugin-Directory-Slurper" target="_blank">Mark Jaquith&#8217;s slurper</a> &#8211; for people who were doing some silly, but easy to mistake, things like jquery. This started after WP upgraded jquery and a lot of plugins and themes broke. I was so annoyed, I started trying to head them off at the pass.</p></blockquote>\n<h3>The Plugin Review Process</h3>\n<p>Once a plugin developer submits his work to the directory, he or she generally has to wait a little while for it to be approved. Epstein says that they try to get to everyone within seven days but that some weeks are better than others. &#8220;Small plugins are often approved right away, larger can take a while,&#8221; she said. &#8220;On our good days, we can same-day review everyone. How long each review takes is also subjective to the plugin size and complexity. <span class="pullquote alignleft">Many times a delay pops up when we have to figure out what the code was supposed to do because of poor documentation.</span>&#8221;</p>\n<p>There&#8217;s a helpful gem in there for aspiring plugin developers submitting to WordPress.org: <strong>The better your documentation is, the faster your plugin is likely to move through the process.</strong></p>\n<p>You might be surprised to learn that the plugin review process is not terribly mysterious or complicated. It simply takes a little bit of time. Epstein outlines what&#8217;s involved:</p>\n<blockquote><p>We review plugin submissions, and that really means we download the zip, read the code, test it, and approve it or push back for various things. Every single line of code is looked at, and we generally look for things that are &#8216;wrong.&#8217; After a while, they start to jump out at you.</p></blockquote>\n<p>This translates into a daily routine for her. <strong>&#8220;I usually spend an hour or two a day just on plugins,&#8221;</strong> Epstein said. &#8220;Minimum&#8217;s an hour, which lets me run a decent triage on people with pending requests and some of the new ones.&#8221; Additionally, there are reports and weird issues that come in that she will funnel to the entire team.</p>\n<h4>The Most Common Issues With Plugins</h4>\n<p>Believe it or not, the most common reason for a plugin to get rejected is not ultimately due to brazen violations of the guidelines. Epstein says that many plugin authors simply do not reply to emails: &#8220;After 7 days, if the plugin code isn&#8217;t completed, the plugin&#8217;s rejected.&#8221; </p>\n<p>Bad plugin names are another reason that she says are grounds for rejection, as well as HTML in the title. &#8220;We auto-reject anyone with &#8216;wordpress&#8217; in the plugin slug (like you can no longer request &#8216;wordpress-fedex-shipping&#8217;) but manually we reject anything with encoded HTML characters in the title (like %d) or the term &#8216;plugin&#8217; (most of the time&#8230; if your plugin is &#8216;network plugin settings&#8217; that&#8217;s okay, but &#8216;rebooter-plugin&#8217; is not).&#8221;</p>\n<h3>Why Plugins Get Pulled From the Directory</h3>\n<p>You&#8217;ve probably seen it happen a time or two: A plugin is newly listed in the repository and then it suddenly vanishes a day or two later. I asked Mika why it is that a plugins make it through this review process but end up being pulled just a couple days later. She replied:</p>\n<blockquote><p>Ouch. So &#8230; we&#8217;re human, right? And SOME plugins are really simple and others are really complex. Just like the dev may miss a security hole in their plugin, we might too. While we do look at every line of code, the problem with this is the same as the problem with all security reviews and that is we look for wrong, and sometimes miss it in the cruft of right.</p></blockquote>\n<p>In addition, Epstein said that sometimes WP Tavern or another site will post about a new plugin and then a larger number of people will take a look at it, inspect the code, and uncover something that might have been missed. However, there are some plugin developers out there with bad motives, who knowingly violate the guidelines through what Epstein calls a <strong>&#8220;bait-and-switch&#8221;</strong>:</p>\n<blockquote><p>Someone submits plugin A, we approve it, but they upload plugin B to the repository. That&#8217;s something a lot of spammers like to do. Sometimes people upload the wrong version of the code by accident, other times they intentionally go back and add in code we told them to remove. We try to mitigate this by filtering emails (I actually get an email for every single plugin check in) and scan for known issues, but it&#8217;s never-ending. Right now there are 20 security reports to go through.</p></blockquote>\n<p>The review team is constantly improving its checks, which help them scan for the most basic and unintentional violations. Unfortuantely, there is no way to scan for bait-and-switch techniques, which require someone to go back and manually check for violations after the plugin is already sent to the repository.</p>\n<h3>Advice For Managing Orphaned Plugins</h3>\n<p>One of the problems plaguing the plugin directory is plugins that have been abandoned or are no longer maintained. Given Epstein&#8217;s close involvement with support, I asked her what the best course of action is for a plugin author who no longer wishes to update his/her plugin on WordPress.org. Would it be best to remove it? If he/she can&#8217;t find someone to adopt the plugin, is it better to leave the plugin there as a starting point for someone else or to remove it entirely to prevent frustrating users? Ultimately, the decision falls to the plugin author, but Epstein offered some practical tips:</p>\n<ul>\n<li>If a plugin author wants to no longer support or update a plugin, I suggest they make DARN SURE that&#8217;s documented in their readme!</li>\n<li>If they want to leave it open for someone else to adopt that&#8217;s great, just make sure to put up a way to be contacted.</li>\n<li>If they want to close it forever and ever, that&#8217;s okay too, just email plugins AT wordpress.org and link to the plugin.</li>\n</ul>\n<p>&#8220;Which is better? Depends on the plugin,&#8221; she said. &#8220;Like <a href="http://wordpress.org/plugins/twitter-blackbird-pie/" target="_blank">Blackbird Pie</a>, the plugin to embed Twitter, was something I would feel was essential not to close &#8230; until we added in Twitter oEmbeds. Now it&#8217;s not really as needed and may not even work. Would I extend that or close it? Hard to say, even if it was mine.&#8221;</p>\n<h3>The Readme.txt File is Key to Improving User Experience in the Plugin Directory</h3>\n<p>When searching the directory, it&#8217;s not uncommon to find plugins with what seems to be only a title. Many plugins are missing vital details (or any details), screenshots, FAQs and basic information about what the plugin does. I asked Epstein what can we do to encourage plugin authors to provide more information. She has a few solid tips:</p>\n<blockquote><p>I hate bad readmes with a passion. I try to push people to make better ones, pointing out that if the readme (which makes your wporg repository page) isn&#8217;t descriptive and helpful, no one will use your plugin and you&#8217;ll waste time answering easy questions. But we only force them to have a readme at submission if they&#8217;re a service (that is they&#8217;re calling other servers). Screenshots aren&#8217;t always needed, but a good and descriptive readme would save everyone a lot of pain. Short of letting me actually chase after people with a baseball bat, I don&#8217;t know if we&#8217;ll ever get to a place where everyone&#8217;s doing that.</p></blockquote>\n<p>Unfortunately, the plugin review team cannot require better readme.txt files, but her advice would be good to take to heart if you are a plugin developer reading this. Don&#8217;t leave people in the dark about what your plugin does if you want anyone to use it.</p>\n<p>Now that you know a little bit more about what the plugin review team has to contend with, aren&#8217;t you grateful for everything they do on WordPress.org? Many thanks to Mika Epstein and the rest of the team for their daily work on the <a href="http://wordpress.org/plugins/" target="_blank">WordPress Plugin Directory</a>. Without them, the directory would be a wasteland, overrun with spam and security threats. Because of their dedication, WordPress.org remains one of the safest places to look for extensions.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 20:31:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"WPTavern: Tickets On Sale For WordCamp Dayton, Ohio";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15246";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:144:"http://wptavern.com/tickets-on-sale-for-wordcamp-dayton-ohio?utm_source=rss&utm_medium=rss&utm_campaign=tickets-on-sale-for-wordcamp-dayton-ohio";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1975:"<p><a href="http://wptavern.com/wp-content/uploads/2013/12/WordCampDayton2014Logo.jpg" rel="prettyphoto[15246]"><img src="http://wptavern.com/wp-content/uploads/2013/12/WordCampDayton2014Logo.jpg" alt="WordCamp Dayton 2014" width="177" height="226" class="alignright size-full wp-image-12640" /></a> Six weeks from now between March 7th and 8th, <a href="http://2014.dayton.wordcamp.org/" title="http://2014.dayton.wordcamp.org/">WordCamp Dayton, Ohio</a> will be underway. This is the first WordCamp to take place in the Dayton area and is <a href="http://central.wordcamp.org/schedule/" title="http://central.wordcamp.org/schedule/">one of three scheduled</a> in the state of Ohio. Sessions range from <a href="http://2014.dayton.wordcamp.org/session/podcasting-for-wordpress/" title="http://2014.dayton.wordcamp.org/session/podcasting-for-wordpress/">Podcasting for WordPress</a> to <a href="http://2014.dayton.wordcamp.org/session/wordpress-version-control/" title="http://2014.dayton.wordcamp.org/session/wordpress-version-control/">WordPress Version control</a>. There are three tracks of sessions available for the publisher, power user, and developer. To see a full list of speakers and their sessions, check out <a href="http://2014.dayton.wordcamp.org/schedule/" title="http://2014.dayton.wordcamp.org/schedule/">the event schedule</a>. </p>\n<p><a href="http://2014.dayton.wordcamp.org/tickets/" title="http://2014.dayton.wordcamp.org/tickets/">Tickets for the event</a> are on sale and cost <strong>$40.00</strong> for general admission. If you&#8217;re a freelance developer, there is a specific package just for you that will get your name, website, and Twitter handle published on the <a href="http://2014.dayton.wordcamp.org/call-for-sponsors/" title="http://2014.dayton.wordcamp.org/call-for-sponsors/">WordCamp Dayton sponsors page</a>. I&#8217;ll be in attendance at this years event. If you&#8217;re going, let me know in the comments so we can meetup.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 18:17:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:17;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"Matt: The Four Freedoms";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43469";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:35:"http://ma.tt/2014/01/four-freedoms/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:12488:"<p>Eleven months before the U.S. declared war on Japan, <a href="http://voicesofdemocracy.umd.edu/fdr-the-four-freedoms-speech-text/">President Franklin D. Roosevelt said</a> &#8220;As men do not live by bread alone, they do not fight by armaments alone.&#8221; He articulated four fundamental freedoms that everyone in the world ought to enjoy:</p>\n<ol>\n<li>Freedom of speech.</li>\n<li>Freedom of worship.</li>\n<li>Freedom from want.</li>\n<li>Freedom from fear.</li>\n</ol>\n<p>Fast forward 72 years: technology has advanced at dizzying rates and permeated every aspect of our lives, from <a title="Too much technology." href="http://www.theatlantic.com/health/archive/2012/03/the-most-scientific-birth-is-often-the-least-technological-birth/254420/">how we are born</a> to <a title="Still too much technology." href="http://www.newyorker.com/reporting/2007/04/30/070430fa_fact_gawande">how we die</a> and everything in between. In this co-evolution of society and technology, what it means to be truly &#8220;free&#8221; is no longer about just the country we live in, or even its laws, but is shaped by the products we live <em>on</em>.</p>\n<p>As <a title="Don''t you wish Marc blogged more?" href="http://online.wsj.com/news/articles/SB10001424053111903480904576512250915629460">Marc Andreessen says, software is eating the world</a>. It’s a creative gale of destruction that irreversibly changes every industry it touches, and if you don&#8217;t control the software, the software controls you. It mediates how and with whom you communicate, what news you see, and what other software you&#8217;re able to run. It <a title="Long, but good, read." href="http://edge.org/responses/how-is-the-internet-changing-the-way-you-think">influences</a> the <a href="http://www.theatlantic.com/magazine/archive/2008/07/is-google-making-us-stupid/306868/">very way your brain works</a>, as you process the creative gale of <em>distraction</em> that interrupts us all hundreds of times each day. With <a href="http://www.nirandfar.com/2012/10/escape.html">every ping</a>, software burrows deeper into our lives.</p>\n<p>In the early nineties, a prescient hacker named <a title="Read about the parrots." href="http://stallman.org/">Richard Stallman</a> — working at MIT, where today&#8217;s future had already happened — recognized this shift. He <a href="https://www.gnu.org/philosophy/free-sw.html">proposed a set of four freedoms</a> that were fundamental for software in an enlightened, tech-dependent society.</p>\n<ol start="0">\n<li>The freedom to run the program, for any purpose.</li>\n<li>The freedom to study how the program works, and change it so it does your computing as you wish.</li>\n<li>The freedom to redistribute copies so you can help your neighbor.</li>\n<li>The freedom to distribute copies of your modified versions, giving the community a chance to benefit from your changes.</li>\n</ol>\n<p>(Aside: I originally thought Stallman <a href="http://en.wikipedia.org/wiki/Zero-based_numbering">started counting with zero instead of one</a> because he&#8217;s a geek. He is, but that wasn&#8217;t the reason. Freedoms one, two, and three came first, but later he wanted to add something to supercede all of them. So: freedom zero. The geekness is a happy accident.)</p>\n<p>This is our Bill of Rights. Stallman called it <a title="Don''t call it open source." href="https://www.gnu.org/philosophy/free-sw.html">Free Software</a>. The &#8220;free&#8221; doesn&#8217;t have to do with price, as you’re still free to charge for your software, but with freedom to create. Or as we geeks often say: not free as in beer, <a href="http://en.wikipedia.org/wiki/Freedom_of_speech_in_the_United_States">free as in speech</a>.</p>\n<p>People are scared of free software, and I understand why. You&#8217;re taking the <a title="Industries with low IP protection are more creative and generate more sales." href="http://intenseminimalism.com/2010/creativity-in-a-copyright-less-world/">most valuable thing</a> you have, <a title="Old-school theme." href="http://sob.apotheon.org/?p=1519">your intellectual property</a>, and granting the freedom you enjoy as a creator to anyone who downloads your work. It&#8217;s terrifying, actually. It’s releasing your ideas, and letting anyone build on them — in a way that might be better than your own work. It’s releasing your traditional understanding of ownership, and your fear of being out-developed.</p>\n<p>The most experienced entrepreneurs can cling to the concept that your <a href="http://www.paulgraham.com/ideas.html">idea is something precious that must be protected from the world</a>, and meted out in a controlled way. Lots of us hang on to the assumption that scarcity creates a proprietary advantage. It’s how many non-tech markets work.</p>\n<p>Open source abdicates your flexibility as a developer to better serve the people who actually use your products. You can see that as a constraint&#8230; or you can see it as a door to iteration, innovation, and constant progress.</p>\n<p>I&#8217;ve spent a third of my life building software based on Stallman’s four freedoms, and I&#8217;ve been astonished by the results. <a href="http://wordpress.org/">WordPress</a> wouldn’t be here if it weren’t for those freedoms, and it couldn’t have evolved the way it has.</p>\n<p>WordPress was based on a program called <a title="The header is still classic." href="http://cafelog.com/">B2/cafelog</a> that predated it by two years. I was using B2 because it had freedoms 0 and 1: I could use it for whatever I wanted, including my zero-budget personal blog, and the source code was open. It was elegant and easy to understand, and anyone could tweak it.</p>\n<p>B2 was ultimately <a title="This post is where WordPress started." href="http://ma.tt/2003/01/the-blogging-software-dilemma/">abandoned</a> by its creator. If I’d been using it under a proprietary license, that would have been the end — for me, and all its other users. But because we had freedoms 2 and 3, Mike Little and I were able to use the software as a foundation, giving us a two-year headstart over building something from scratch, and realize our own vision of what blogging could be.</p>\n<p>We were just consumers of the software, volunteers in the forums, and occasional contributors to the codebase, but because (of the GPL) we had the freedom to build on B2, we were able to continue development as if it had been our own creation.</p>\n<p>Ten years later, those freedoms are still embedded in every copy of WordPress downloaded, including the <a href="http://wordpress.org/download/counter/">9.2 million downloaded</a> in the past month or so since our <a href="http://wordpress.org/news/2013/12/parker/">3.8 release</a>.</p>\n<p>I believe that software, and in fact entire companies, should be run in a way that assumes that the sum of the talent of people outside your walls is greater than the sum of the few you have inside. None of us are as smart as all of us. Given the right environment — one that leverages the marginal cost of distributing software and ideas — independent actors can work toward something that benefits them, while also increasing the capability of the entire community.</p>\n<p>This is where open source gets really interesting: it&#8217;s not just about the <a href="http://www.gnu.org/licenses/license-list.html">legal wonkery around software licensing</a>, but what effect open sourced software has on people using it. In the proprietary world, those people are typically called &#8220;users,&#8221; a strange term that connotes dependence and addiction. In the open source world, they’re more rightly called a community.</p>\n<p>The core features of WordPress aren’t <a href="http://www.amazon.com/Rocket-Surgery-Made-Easy-Do-It-Yourself/dp/0321657292">rocket surgery</a>. A handful of smart people in a room for a year could create a reasonable approximation of the software, and undoubtably improve some things — I see other startups do this <a title="Someday they will build a museum to document your former competitors." href="http://www.crunchbase.com/tag/cms">three or four times a year</a>.</p>\n<p>What they miss is that WordPress isn&#8217;t a checklist of features. It&#8217;s over <a title="I have about 20 of them." href="http://wordpress.org/plugins/">29,000 plugins</a> created by the community, from the in-demand things like SEO to niche features like <a title="I can''t make these things up." href="http://wordpress.org/plugins/hundstall-404/">using your 404 page to help adopt homeless dogs in Sweden</a>. Every WordPress site looks different, because of the thousands of themes available. Instead of one event to outdo, there are more than <a title="Check one out if you haven''t been yet, amazing groups of folks." href="http://central.wordcamp.org/">70 volunteer-organized WordCamps on six continents</a> (and there’ll be more in 2014).</p>\n<p>WordPress marketing has nothing to do with its website or <a title="Fight the Fauxgo." href="http://wordpress.org/about/logos/">logo</a>, it&#8217;s the <a href="http://wordpress.tv/2013/07/29/matt-mullenweg-state-of-the-word-2013/">tens of thousands of people who make a living building WordPress sites</a> and receive so much value from it that they proselytize to anyone that will listen, spreading the flame one site at a time. It works — as of December 2013, 21% of websites are powered by WordPress. One-fifth of the web is built with a tool that anyone can use, change, or improve, whenever and however they want (even more when you count other open source projects, like Drupal).</p>\n<p>This approach to building isn&#8217;t an abdication of developers’ and designers’ responsibility to build beautiful, functional software. Design and forethought are <em>more important</em> than ever when every change sends millions of independent actors down a new path. Changes to WordPress have consequences today, tomorrow, five years, and ten years down the road, but the passion and talent of the community helps ensure that it always moves forward in a positive way.</p>\n<p>The four freedoms don’t limit us as creators — they open possibilities for us as creators <em>and</em> consumers. When you apply them to software, you get Linux, Webkit/Chrome, and WordPress. When you apply them to medicine, you get the <a href="http://www.opengenomicsengine.org/">Open Genomics Engine</a>, which is accelerating cancer research and bringing us closer to personalized treatment. When you apply them to companies, you get radically geographically distributed, results-based organizations like <a href="http://automattic.com/">Automattic</a>. When you apply them to events you get <a href="http://www.ted.com/tedx">TEDx</a>, <a title="Which I accidentally ended up helping get started." href="http://en.wikipedia.org/wiki/BarCamp">Barcamp</a>, and <a href="http://wordcamp.org/">WordCamp</a>. When you apply them to knowledge, you get <a title="Where people argue you for deletion." href="http://wikipedia.org/">Wikipedia</a>.</p>\n<p><a href="http://www.williamgibsonbooks.com/">William Gibson</a> is attributed with saying &#8220;The future is already here — it&#8217;s just not very evenly distributed.&#8221; The world is changing faster than any one person or organization can keep up with it. Closed off, proprietary development creates closed off, proprietary products that won’t keep pace in the long run. Open source provides another path — one that’s open to everyone, and can take advantage of the skills and talents of anyone in the world to build software that helps everyone.</p>\n<p>As <a href="http://en.wikipedia.org/wiki/Joy''s_Law_(management)">Bill Joy said</a>, &#8220;No matter who you are, most of the smartest people work for someone else.&#8221; Good ideas aren’t the sole province of groups of people behind high walls, and software shouldn’t be either.</p>\n<p><em>This was adapted from a talk I gave at <a title="Was great fun, hope they do it again next year." href="http://www.lifeisbeautifulfestival.com/">the Life is Beautiful festival</a> in <a title="One of the more interesting scenes around right now." href="http://downtownproject.com/">Downtown Las Vegas</a>. Thanks to <a href="http://kingofstates.com/">Michelle</a>, <a href="http://stratechery.com/">Ben</a>, <a href="http://intenseminimalism.com/">Davide</a>, and <a href="http://paulmaiorana.com/notes/">Paul</a> for help with this.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 17:02:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:56:"WordPress.tv: Konstantin Kovshenin: Templating WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30011";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"http://wordpress.tv/2014/01/23/konstantin-kovshenin-templating-wordpress/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:661:"<div id="v-JH7sJM4H-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30011/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30011/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30011&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/23/konstantin-kovshenin-templating-wordpress/"><img alt="Konstantin Kovshenin: Templating WordPress" src="http://videos.videopress.com/JH7sJM4H/video-6338ae249d_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 16:03:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:59:"WordPress.tv: Joe Hoyle: Setting Up Production Environments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=30003";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"http://wordpress.tv/2014/01/23/joe-hoyle-setting-up-production-environments/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:667:"<div id="v-c5z1cRXz-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/30003/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/30003/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=30003&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/23/joe-hoyle-setting-up-production-environments/"><img alt="Joe Hoyle: Setting Up Production Environments" src="http://videos.videopress.com/c5z1cRXz/video-3b5a88069a_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 15:39:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:20;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:62:"WPTavern: Interview With Jason Schuller Founder Of Press75.com";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15204";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:168:"http://wptavern.com/interview-with-jason-schuller-founder-of-press75-com?utm_source=rss&utm_medium=rss&utm_campaign=interview-with-jason-schuller-founder-of-press75-com";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2067:"<p>The last time I spoke with <a href="http://jason.sc/" title="http://jason.sc/">Jason Schuller</a>, it was 2008 at WordCamp Chicago. He had just launched his commercial theme company <a href="http://press75.com/" title="http://press75.com/">Press75</a>. Since 2008, he&#8217;s launched a number of projects such as ThemeGarden, the first ever WordPress theme marketplace that gave 100% of the sale back to the theme author. Lately, Jason has been experimenting with creating simple publishing systems like Dropplets and Leeflets that focus on streamlining the publishing process. Many of these projects have since shut down.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/ThemeGardenLogo.jpg" rel="prettyphoto[15204]"><img src="http://wptavern.com/wp-content/uploads/2014/01/ThemeGardenLogo.jpg" alt="ThemeGarden Logo" width="458" height="231" class="aligncenter size-full wp-image-15222" /></a></p>\n<p>I caught up with Jason Schuller one on one to find out what happened to all of the projects mentioned above, what he&#8217;s been up to the past 6 years and last but not least, find out what he&#8217;s working on in the immediate future. During the interview, we learn some valuable lessons from Jason such as when to ask others for help when a project gets too large for one person to handle. He tells us how he got involved with WordPress theme development and how WordPress became a pivotal moment in his life. </p>\n<p>One of the main reasons for conducting this interview is that based on everything I&#8217;ve read from <a href="https://twitter.com/jschuller" title="https://twitter.com/jschuller">his Twitter account</a>, it seemed like he was leaving the WordPress community to pursue other opportunities. Jason told me that although he won&#8217;t be concentrating his efforts on WordPress in the immediate future, he will still attend WordCamps and continue to interact with all of the friends he&#8217;s made throughout the community over the years. I wish Jason the best with his future endeavors and hope you enjoy the interview. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Jan 2014 02:05:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:21;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:75:"WPTavern: WordPress.org vs. GitHub For Hosting WordPress Plugins and Themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=13576";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:192:"http://wptavern.com/wordpress-org-vs-github-for-hosting-wordpress-plugins-and-themes?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-org-vs-github-for-hosting-wordpress-plugins-and-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8157:"<p>There are many factors that come into play when deciding where to host your open source WordPress plugin or theme. Who is your target audience? How much support do you want to offer? Is the project open for collaboration? For many developers this choice often comes down to <a href="http://wordpress.org/" target="_blank">WordPress.org</a> vs. <a href="https://github.com/" target="_blank">GitHub</a>. </p>\n<p>In the past, hosting with WordPress.org was the only option that would allow developers to push out updates to their plugin or theme via the WordPress admin. The <a href="https://github.com/afragen/github-updater" target="_blank">GitHub Updater</a> plugin, created by Andy Fragen and added to GitHub in July of 2013, makes it possible to ship updates to Github-hosted plugins and themes. This makes it convenient for developers who prefer GitHub to stay within their preferred workflow while continuing to provide updates. Incidentally, this plugin is banned from the WordPress.org repository.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/updater.png" rel="prettyphoto[13576]"><img src="http://wptavern.com/wp-content/uploads/2014/01/updater.png" alt="updater" width="640" height="480" class="aligncenter size-full wp-image-15182" /></a></p>\n<p>Of course there are a number of other places that you can host your project, i.e. your own website or another code sharing site. We&#8217;re looking at GitHub vs. WordPress.org for the purposes of this comparison, since the two are among the most popular.</p>\n<h2>Advantages of Hosting Your Project on WordPress.org</h2>\n<p>By far, one of the best reasons to host a plugin or theme on WordPress.org is the increased exposure that it will offer for your work. Your extension is just a couple clicks away when a user performs a search within the WordPress admin, giving you an audience of millions of potential users. </p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/wporg.jpg" rel="prettyphoto[13576]"><img src="http://wptavern.com/wp-content/uploads/2014/01/wporg.jpg" alt="wporg" width="969" height="399" class="aligncenter size-full wp-image-15207" /></a></p>\n<p>A summary of the advantages includes:</p>\n<ul>\n<li>Maximum exposure: Your extension can be searched for within the WP admin</li>\n<li>Built-in trac and support forums</li>\n<li>Easily push out updates to users</li>\n<li>Ratings, reviews and download stats</li>\n<li>Extensions are more trusted due to the WordPress.org review process and guidelines</li>\n</ul>\n<p>Of course, some of these same &#8220;advantages&#8221; could also be considered disadvantages. For example, if you&#8217;re not willing to offer free support, having your plugin or theme on WordPress.org with such a wide audience may send you a flood of support requests. If you don&#8217;t have the time to provide updates or support, the resulting star ratings and reviews may hurt your extension&#8217;s reputation.</p>\n<h4>Disadvantages:</h4>\n<p>One of the primary disadvantages of hosting a project on WordPress.org alone is that it can severely limit collaboration. Themes and plugins on WordPress.org are simply not geared for collaborative development. Most developers find it easier to collaborate via Git. Hosting on WordPress.org also requires a basic knowledge of SVN, which is not very popular these days. In summary, the disadvantages include:</p>\n<ul>\n<li>SVN</li>\n<li>Does not encourage collaboration</li>\n<li>Possible massive influx of support requests</li>\n</ul>\n<h2>Advantages of Hosting Your Project on GitHub</h2>\n<p>Where a lack of collaboration is probably the strongest disadvantage of hosting on WordPress.org, it&#8217;s also the biggest advantage to hosting your extension on GitHub. The barrier of entry for participation on GitHub is much higher, which significantly lessens the likelihood of you becoming inundated with support requests.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/github-social-coding.jpg" rel="prettyphoto[13576]"><img src="http://wptavern.com/wp-content/uploads/2014/01/github-social-coding.jpg" alt="github-social-coding" width="580" height="230" class="aligncenter size-full wp-image-15213" /></a></p>\n<p>Other advantages include:</p>\n<ul>\n<li>Easy for others to contribute to your project</li>\n<li>Built-in wiki and issues queue available</li>\n<li>Fewer support requests</li>\n<li>Can easily push out updates w/ use of GitHub Updater</li>\n<li>Fewer restrictions &#8211; No code review process or extra guidelines for compliance</li>\n<li>Traffic analytics &#8211; GitHub recently introduced <a href="https://github.com/blog/1672-introducing-github-traffic-analytics" target="_blank">analytics data</a> for repositories</li>\n</ul>\n<h4>Disadvantages:</h4>\n<ul>\n<li>Likely a smaller audience</li>\n<li>Will need to bundle the Git Updater with your extension or ask users to install it in order to ship updates</li>\n<li>Does not include the same level of user trust as projects hosed on WordPress.org</li>\n</ul>\n<p>If you don&#8217;t want to have to mess with SVN and don&#8217;t mind losing out on the audience you get hosting on WordPress.org, then hosting your project on GitHub might be a strong option for you. </p>\n<h2>The Best of Both Worlds</h2>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/wpvsgithub.jpg" rel="prettyphoto[13576]"><img src="http://wptavern.com/wp-content/uploads/2014/01/wpvsgithub.jpg" alt="wpvsgithub" width="1600" height="594" class="aligncenter size-full wp-image-15216" /></a><br />\nThere&#8217;s no clear winner in the comparison between hosting on WordPress.org vs. Github. It depends entirely on your workflow and your goals for the extension.  Of course, many projects do a mixture of both, either through maintaining git mirrors or synchronizing via a script. Since every GitHub repository is also a Subversion repository, you can use SVN tools to checkout, branch, and commit to GitHub repositories if you are so inclined.  </p>\n<p>Brent Shepherd has a <a href="https://github.com/thenbrent/multisite-user-management/blob/master/deploy.sh" target="_blank">script that will deploy a WordPress plugin from within Git</a> to WordPress.org&#8217;s SVN repository. &#8220;Since running the script for my plugins, I&#8217;ve not suffered the frustrations of minor errors – like having version numbers in the readme.txt &#038; plugin file differ,&#8221; Shepherd said. &#8220;I&#8217;ve lost less time deploying, so I&#8217;ve released more frequently, which means fewer bugs in the wild.&#8221;</p>\n<p>Here are some other resources you might want to check out for learning more about working between Git and SVN for WordPress extensions.</p>\n<ul>\n<li><a href="http://ben.lobaugh.net/blog/90633/creating-a-synchronized-github-fork-of-a-wordpress-org-subversion-plugin-repository" target="_blank">Creating a Synchronized Github Fork of a WordPress.org Subversion Plugin Repository</a> &#8211; Ben Lobaugh</li>\n<li><a href="http://teleogistic.net/2011/05/revisiting-git-github-and-the-wordpress-org-plugin-repository/" target="_blank">Revisiting Git, Github, and the WordPress.org Plugin Repository</a> &#8211; Boone Gorges</li>\n<li><a href="http://danielbachhuber.com/2012/09/30/git-in-my-subversion/" target="_blank">Git in my Subversion</a> &#8211; Daniel Bachhuber</li>\n<li><a href="https://github.com/growthdesigner/WordPress-3.8-Dashboard/issues/3" target="_blank">Syncing Git Repo with WordPress.org</a> &#8211; Daniel Bachhuber</li>\n<li><a href="http://thereforei.am/2011/04/21/git-to-svn-automated-wordpress-plugin-deployment/" target="_blank">Git to SVN: Automated WordPress Plugin Deployment</a> &#8211; Brent Shepherd</li>\n<li><a href="http://sudarmuthu.com/blog/developing-wordpress-plugins-in-github" target="_blank">Developing WordPress Plugins in Github</a> &#8211; Sudar Muthu</li>\n</ul>\n<p>Every developer has a different workflow, but there&#8217;s a good option for however you choose to develop and maintain your WordPress plugin or theme. After reviewing the advantages and disadvantages of each, which of these factors is the most important for you when making a decision about where to host an extension? </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 22 Jan 2014 23:43:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:22;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:28:"Matt: Abusing Copyright Laws";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43463";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"http://ma.tt/2014/01/abusing-copyright-laws/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:251:"<p>Paul Sieminski, the general counsel at Automattic (Automattlock), writes for Wired on how <a href="http://www.wired.com/opinion/2014/01/internet-companies-care-fair-use/">Corporations Abusing Copyright Laws Are Ruining the Web for Everyone</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 22 Jan 2014 19:21:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:52:"WPTavern: CodePen Releases Official WordPress Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15130";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:148:"http://wptavern.com/codepen-releases-official-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=codepen-releases-official-wordpress-plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2629:"<p><a href="http://codepen.io/" target="_blank">CodePen</a> has released an official plugin for embedding pens in WordPress. If you haven&#8217;t yet discovered CodePen, it&#8217;s basically a virtual playground for frontend developers and browsing the site  can be addictive. It&#8217;s a place where you can write HTML, CSS, and JavaScript code in your browser and then see an instant preview. Each collection of snippets you create is saved under your account as a &#8220;pen&#8221; with its live preview directly beneath it. </p>\n<p><a href="http://wordpress.org/plugins/codepen-embedded-pen-shortcode/" target="_blank">CodePen Embedded Pens Shortcode</a> is the new plugin that makes it easy to embed any pen on your self-hosted WordPress site. On the CodePen side of things, pens have now been updated to show a WordPress shortcode option when you click on Embed: </p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/embed-pen.jpg" rel="prettyphoto[15130]"><img src="http://wptavern.com/wp-content/uploads/2014/01/embed-pen.jpg" alt="embed-pen" width="944" height="470" class="aligncenter size-full wp-image-15164" /></a></p>\n<p>If you&#8217;ve found a pen that inspires you and want to share it on your site, it&#8217;s as easy as copying that shortcode and pasting it into either the visual or text editor in WordPress.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/visual-editor.jpg" rel="prettyphoto[15130]"><img src="http://wptavern.com/wp-content/uploads/2014/01/visual-editor.jpg" alt="visual-editor" width="1138" height="657" class="aligncenter size-full wp-image-15170" /></a></p>\n<p>The pen will then be embedded on your site with a tabbed interface for the code and the demo:</p>\n<p class="codepen">See the Pen <a href="http://codepen.io/sang_nguyen/pen/pJxms">pJxms</a> by Sang Nguyen (<a href="http://codepen.io/sang_nguyen">@sang_nguyen</a>) on <a href="http://codepen.io">CodePen</a>.</p>\n<p><br />\nThe plugin allows you to set a default theme for the pens. You can also override the default theme via the shortcode attribute. In the future, the CodePen team plans to add a fancy UI for picking pens to embed as well as more control over the HTML output.</p>\n<p>CodePen and WordPress working together can be a beautiful thing, especially if you often publish frontend development tutorials with HTML, CSS and/or Javascript. Check out the <a href="http://wordpress.org/plugins/codepen-embedded-pen-shortcode/" target="_blank">CodePen Embedded Pens Shortcode</a> plugin on WordPress.org if you&#8217;re active on CodePen and want to add interactive demos to your WordPress site.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 22 Jan 2014 18:11:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:24;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:72:"WordPress.tv: David Coveney: Can WordPress Save The Publishing Industry?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wordpress.tv/?p=29948";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:88:"http://wordpress.tv/2014/01/22/david-coveney-can-wordpress-save-the-publishing-industry/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:692:"<div id="v-bvUnu4KU-1" class="video-player">\n</div><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wptv.wordpress.com/29948/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wptv.wordpress.com/29948/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=wordpress.tv&blog=5089392&post=29948&subd=wptv&ref=&feed=1" width="1" height="1" /><div><a href="http://wordpress.tv/2014/01/22/david-coveney-can-wordpress-save-the-publishing-industry/"><img alt="David Coveney: Can WordPress Save The Publishing Industry?" src="http://videos.videopress.com/bvUnu4KU/video-dd5e5adfff_std.original.jpg" width="160" height="120" /></a></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 22 Jan 2014 13:46:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:25;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:49:"WPTavern: Quick Tip: WordPress Saves Your Widgets";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15146";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:140:"http://wptavern.com/quick-tip-wordpress-saves-your-widgets?utm_source=rss&utm_medium=rss&utm_campaign=quick-tip-wordpress-saves-your-widgets";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1582:"<p>Have you ever thought about switching your WordPress theme but then hesitated, wondering what might happen to your widgets? Although it may not be obvious, the good news is that WordPress remembers where you previously had your widgets and saves the settings. If you decide to revert back to your previous theme, WordPress will put your widgets back where they were.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/save-widgets.png" rel="prettyphoto[15146]"><img src="http://wptavern.com/wp-content/uploads/2014/01/save-widgets.png" alt="save-widgets" width="1200" height="485" class="aligncenter size-full wp-image-15148" /></a></p>\n<p>As you can see in the screenshot, WordPress will even remind you of its widget saving capabilities when you switch to a new theme. </p>\n<p>Back in the old days, if you switched your theme and then reverted it, you&#8217;d have to set all your widgets again, one by one. This could be quite a time consuming process if you had several widgetized areas loaded up with multiple widgets. In some cases this discouraged site owners from experimenting with different themes. That&#8217;s why widget saving is one of my favorite features of WordPress. Every time I see this feature reminder, I get a small thrill and I know I can rest easy when changing my theme.</p>\n<p>WordPress has actually been saving your widgets since <a href="http://codex.wordpress.org/Version_3.3" target="_blank">version 3.3</a> was released in December of 2011. It was a small feature but it makes a big difference when you&#8217;re testing new themes.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 22 Jan 2014 03:21:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:26;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:67:"WPTavern: Customer Service As A Foundation For Webhosting Companies";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15098";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:178:"http://wptavern.com/customer-service-as-a-foundation-for-webhosting-companies?utm_source=rss&utm_medium=rss&utm_campaign=customer-service-as-a-foundation-for-webhosting-companies";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3755:"<p>Oli Dale of WPLift.com has <a href="http://wplift.com/how-we-work-siteground" title="http://wplift.com/how-we-work-siteground">published a great article</a> that goes behind the scenes of <a href="http://www.siteground.com/" title="http://www.siteground.com/">SiteGround</a>. SiteGround CEO, Tenko Nikolov, answered questions that provide insight into how the company operates on a day to day basis. I was surprised to learn that the company is just a few months younger than WordPress and will be celebrating their 10th anniversary in March. Check out these numbers that represent an average day of customer support:</p>\n<blockquote><p>The story behind SiteGround is actually pretty cool, it was founded in 2004 by a group of university friends, with a handful of people working from their uni dorm rooms and has grown to the point where today it has 120 employees and is still growing. SiteGround claims to host over 250,000 domains and process 400 tickets, 150 phone calls and 300 chat requests per day.</p></blockquote>\n<h3>Customer Service Used As A Foundation</h3>\n<p>When the company started, Tenko mentions the company’s vision was to provide more help to the customers than a standard host did at that time. This is interesting to me because ten years later, WordPress centric hosting companies are being started with the same vision. <a href="http://wptavern.com/wpweekly-episode-118-hey-get-flywheel" title="http://wptavern.com/wpweekly-episode-118-hey-get-flywheel">Flywheel hosting</a> is the most recent example of a host that puts customer service at the forefront of everything they do. At this point, what else is there to differentiate webhosting companies from one another besides customer service? </p>\n<p>I&#8217;ve been vocal about the problems I&#8217;ve experienced with webhosting companies <a href="http://wptavern.com/my-performance-woes" title="http://wptavern.com/my-performance-woes">such as HostGator</a>. As I said in a <a href="http://www.inmotionhosting.com/support/webhostingwarriors" title="http://www.inmotionhosting.com/support/webhostingwarriors">recent interview with Web Hosting Warriors</a>, how a webhosting company treats you when a major problem surfaces tells you everything you need to know. </p>\n<h3>My Thoughts On Webhosting Companies</h3>\n<p>I hope you&#8217;ll tune in and listen as I share my experiences with webhosting companies I&#8217;ve used in the past to host WPTavern.com. I also explain what I as a customer expect out of the company, especially from the customer service stand point. While I initially talk about the history of WPTavern and how I turned it into a successful website, you can fast forward to the <strong>13 minute mark</strong> to hear me discuss my woes with HostGator. </p>\n<p><span class="embed-youtube"></span></p>\n<h3>What Do You Look For In a Webhost</h3>\n<p>In 2010, I shared my list of <a href="http://wptavern.com/14-things-to-consider-when-choosing-a-webhost-for-your-wordpress-powered-site" title="http://wptavern.com/14-things-to-consider-when-choosing-a-webhost-for-your-wordpress-powered-site">fourteen things to consider</a> before choosing a webhost. Many of the things I listed in that post are still relevant today. Having a great experience with a webhosting company is almost like winning the lottery because it’s so rare. Ultimately, it comes down to gathering as much information as possible in order to make an informed decision as to whether a particular webhost is right for you. Price should not be the only determining factor for hosting your site, especially if you plan on taking things seriously. What is the most important factor you look for in a webhost? What influences your decision to go with one particular company over another? </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 21 Jan 2014 23:23:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:27;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"WPTavern: tinyCoffee: A Simple, Elegant Donation Plugin for WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14948";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:178:"http://wptavern.com/tinycoffee-a-simple-elegant-donation-plugin-for-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=tinycoffee-a-simple-elegant-donation-plugin-for-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3567:"<p>The WordPress plugin repository hosts dozens of extensions for accepting donations and includes everything from plugins for creating donation forms to plugins that implement full-on CRM solutions for non-profits. But what if you just want to make it easy for supporters to buy you a coffee?</p>\n<p><a href="http://wordpress.org/plugins/tinycoffee/" target="_blank">tinyCoffee</a> is a new plugin that caught my eye due to its simple, elegant design. It gives visitors an opportunity to support your work by sending you a beverage of your choice. tinyCoffee features an interactive slider that automatically calculates how many beverages the donation will buy.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/sample-donation-page.png" rel="prettyphoto[14948]"><img src="http://wptavern.com/wp-content/uploads/2014/01/sample-donation-page.png" alt="sample-donation-page" width="804" height="463" class="aligncenter size-full wp-image-15111" /></a></p>\n<p>The plugin makes use of the <a href="http://fontawesome.io/" target="_blank">FontAwesome</a> icon font collection to render the beverage image. the tinyCoffee options panel lets you select the icon you&#8217;d like to use, so you&#8217;re not limited to just coffee or beer, or even beverages for that matter. You can select music, money, film, books or anything that fits in with your interests.</p>\n<p>tinyCoffee also makes it easy to place your donation request anywhere within your website with the following four options:</p>\n<ul>\n<li>Template tag (get_coffee()/the_coffee())</li>\n<li>Shortcode ([tiny_coffee]/[tiny_coffee])</li>\n<li>Sidebar widget</li>\n<li>Hash-activated modal screen (domain.com#coffee)</li>\n</ul>\n<p>So for example, if you wanted to make &#8220;Coffee&#8221; a permanent menu item that launches a modal window or link to it within your content, you would simply add the hash to your link:</p>\n<pre>http://example.com#coffee</pre>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/donation-modal.png" rel="prettyphoto[14948]"><img src="http://wptavern.com/wp-content/uploads/2014/01/donation-modal.png" alt="donation-modal" width="1260" height="389" class="aligncenter size-full wp-image-15112" /></a></p>\n<p>I tested the modal window on mobile to make sure it was device-friendly and it launched just as smoothly as it would on desktop. I also put the plugin through the paces to see how each placement option worked and was pleasantly surprised to find that the options panel offered far more customization options than detailed in its readme.txt file. You can easily change just about everything related to its display, including:</p>\n<ul>\n<li>Title and default text outputted by the plugin</li>\n<li>Select the FontAwesome icon</li>\n<li>Customize the hash</li>\n<li>Change the currency template</li>\n<li>Set the coffee price</li>\n<li>PayPal details, currency, exchange rate</li>\n<li>Customize Callback URL settings</li>\n</ul>\n<p>When it comes to donation plugins, tinyCoffee has most others beat on simplicity, design and configuration options. If you work on an open source project or offer something for free on your website, the last thing you want to spend your time on is testing a bunch of donation plugins. If it isn&#8217;t convenient, you&#8217;re likely to skip it altogether.  But people do like to show their support through donations and tinyCoffee offers a stylish and interactive way to enable them on your site. <a href="http://wordpress.org/plugins/tinycoffee/" target="_blank">Download</a> it for free from the WordPress plugin repository.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 21 Jan 2014 22:18:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:28;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:62:"WPTavern: WordPress Front-end Editor Plugin Gets Major Updates";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15070";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:168:"http://wptavern.com/wordpress-front-end-editor-plugin-gets-major-updates?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-front-end-editor-plugin-gets-major-updates";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3300:"<p>This week the WordPress Front-end Editor team <a href="http://make.wordpress.org/ui/2014/01/20/front-end-editor-meeting-20-january/" target="_blank">posted</a> its progress on the Make WordPress UI development blog. Front-end editing capabilities are being developed as a <a href="http://make.wordpress.org/core/features-as-plugins/" target="_blank">feature plugin</a> and will hopefully be considered for inclusion in the core sometime this year. It currently looks a little something like this:</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/frontend-editing.png" rel="prettyphoto[15070]"><img src="http://wptavern.com/wp-content/uploads/2014/01/frontend-editing.png" alt="frontend-editing" width="1280" height="699" class="aligncenter size-full wp-image-15075" /></a></p>\n<p>The plugin has improved by leaps and bounds since the last time I took it for a test drive. I&#8217;ve got it active on a site where I try everything that is fun. Despite the fact that it&#8217;s still under heavy development, the plugin is actually quite enjoyable to use. Editing posts on the frontend is lightening fast. </p>\n<h3>New Modal Added For Post Meta Boxes</h3>\n<p>The most recent update includes the ability to create posts and pages from the frontend. Janneke Van Dorpe, the project lead, has also added more TinyMCE tools and a new modal window to display post meta boxes. This works in a similar way to the media modal.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/custom-fields.png" rel="prettyphoto[15070]"><img src="http://wptavern.com/wp-content/uploads/2014/01/custom-fields.png" alt="custom-fields" width="1280" height="698" class="aligncenter size-full wp-image-15079" /></a></p>\n<h3>New Media Features: oEmbed, Gallery Previews and Featured Image Editing</h3>\n<p>Just after Christmas the team <a href="http://make.wordpress.org/ui/2013/12/26/front-end-editor-quick-christmas-update/" target="_blank">posted</a> some exciting media updates to the plugin. The WordPress Front-end Editor now automatically embeds links supported by oEmbed. It can also generate a preview of galleries and captions and allows for adding, editing or removing featured images. This video is a quick demonstration of those features in action:</p>\n<p><span class="embed-youtube"></span></p>\n<p>Since front-end editing is being developed as a feature plugin, you can test it out early if you&#8217;re feeling adventurous. Feel free to use it during its experimental stage and monitor the progress. You can find the <a href="http://wordpress.org/plugins/wp-front-end-editor/" target="_blank">WordPress Front-end Editor</a> plugin in the WordPress plugin repository. There&#8217;s also a <a href="https://github.com/avryl/wp-front-end-editor" target="_blank">github mirror</a> of the plugin. Please be advised that it is still under very active development and probably not suitable for a client site.</p>\n<p>If you&#8217;d like to get on board to contribute, check out the <a href="https://plugins.trac.wordpress.org/plugin/wp-front-end-editor" target="_blank">open tickets</a> for the plugin to see what is planned, report a bug or add ideas of your own. Contributors are welcome to join in on the next meeting scheduled for Tuesday, January 28, 2014 at 11:00 UTC-6 in #wordpress-ui.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 21 Jan 2014 18:25:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:29;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: Opus: A Free WordPress Blogging Theme With A Big Personality";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15039";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:182:"http://wptavern.com/opus-a-free-wordpress-blogging-theme-with-a-big-personality?utm_source=rss&utm_medium=rss&utm_campaign=opus-a-free-wordpress-blogging-theme-with-a-big-personality";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2980:"<p><a href="http://wordpress.org/themes/opus" target="_blank">Opus</a> is a new WordPress theme for bloggers, now available in the official themes directory. Created by WordPress theme developer Fikri Rasyid, Opus takes a mobile first approach to responsive design and features a fluid layout. When he set out to create Opus, Rasyid wanted the theme to provide a great reading experience on any device. He also wanted it to have personality.</p>\n<p>Inspired by the <a href="http://designmodo.com/square-free/" target="_blank">Square UI Design Kit</a>, Rasyid created Opus to incorporate a similar flat design with big fonts and spacious elements. Opus makes use of the popular <a href="http://www.google.com/fonts/specimen/Open+Sans" target="_blank">Open Sans</a> font.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/opus.png" rel="prettyphoto[15039]"><img src="http://wptavern.com/wp-content/uploads/2014/01/opus.png" alt="opus" width="600" height="450" class="aligncenter size-full wp-image-15041" /></a></p>\n<h3>A Post Editor to Match the Frontend</h3>\n<p>One unique feature of the theme is that the developer has added styles to make the post editing experience match the frontend as much as possible when the visual editor is in use.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/post-editor.png" rel="prettyphoto[15039]"><img src="http://wptavern.com/wp-content/uploads/2014/01/post-editor.png" alt="post-editor" width="520" height="365" class="aligncenter size-full wp-image-15045" /></a></p>\n<h3>The Personality Factor</h3>\n<p>The main visual feature of this theme is the big header image on the homepage, which is intended for users to customize. Opus includes support for WordPress&#8217; native custom header and you can easily change the theme&#8217;s colors via the customizer as well.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/customizer.jpg" rel="prettyphoto[15039]"><img src="http://wptavern.com/wp-content/uploads/2014/01/customizer.jpg" alt="customizer" width="1046" height="512" class="aligncenter size-full wp-image-15051" /></a></p>\n<p>Check out a <a href="http://fikrirasyid.com/wordpress-themes/opus/" target="_blank">demo</a> on the developer&#8217;s website to see Opus in action.</p>\n<p>If you like the theme and want to contribute, <a href="https://github.com/fikrirasyid/opus" target="_blank">Opus is also hosted on github</a> and its developer welcomes you to fork it, submit a patch, pull request or report any bugs you find. Since the theme can be found in the official <a href="http://wordpress.org/themes/" target="_blank">WordPress Themes Directory</a>, it has already passed a rigorous review by the WordPress Theme Review team and you can be certain that it doesn&#8217;t contain any malicious code. <a href="http://wordpress.org/themes/opus" target="_blank">Opus</a> is a great option for anyone who wants a minimalist and responsive one-column blog theme with a splash of personality.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 23:10:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:30;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:30:"Joseph: WordPress Car Stickers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://josephscott.org/?p=9834";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:64:"https://josephscott.org/archives/2014/01/wordpress-car-stickers/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:288:"<p><img src="https://farm8.staticflickr.com/7402/12016117746_9d0f7e3013_b.jpg" width="1024" height="452" class="aligncenter" /></p>\n<p>Saw this in the parking lot during the <a title="First PHP conference in Utah, went very well." href="https://www.skiphp.com/">SkiPHP</a> conference.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 22:41:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Joseph Scott";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: WordPress Developers Take Note: TinyMCE 4.0 Merged Into Core";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=15016";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:182:"http://wptavern.com/wordpress-developers-take-note-tinymce-4-0-merged-into-core?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-developers-take-note-tinymce-4-0-merged-into-core";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3378:"<p>Andrew Ozz who is responsible for maintaining TinyMCE in WordPress <a title="http://make.wordpress.org/core/2014/01/18/tinymce-4-0-is-in-core/" href="http://make.wordpress.org/core/2014/01/18/tinymce-4-0-is-in-core/">has announced</a> that TinyMCE 4.0 has been merged into core. The upgrade contains a number of changes including:</p>\n<ul>\n<li>New UI and UI API.</li>\n<li>New theme.</li>\n<li>Revamped events system/API.</li>\n<li>Better code quality, readability and build process.</li>\n<li>Lots of (inline) documentation.</li>\n<li>Overall improvements everywhere</li>\n</ul>\n<div id="attachment_15031" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2014/01/TinyMCE40Interface.jpg" rel="prettyphoto[15016]"><img class="size-large wp-image-15031" alt="TinyMCE 4.0 In Development version of WP" src="http://wptavern.com/wp-content/uploads/2014/01/TinyMCE40Interface-500x204.jpg" width="500" height="204" /></a><p class="wp-caption-text">TinyMCE 4.0 In Development version of WP</p></div>\n<p>All of the default TinyMCE plugins as well as the custom plugins used by WordPress have been upgraded to be compatible with 4.0. Since there are a lot of API changes, plugin developers are strongly encouraged to update their plugins to make sure they are compatible with 4.0 and then test them against WordPress Trunk.</p>\n<p>Andrew Ozz listed three groups of general TinyMCE plugins that are added by WordPress Plugins.</p>\n<ul>\n<li>A custom plugin created specifically for the WordPress plugin. If you’ve developed this kind of plugin, please see the 3.x to 4.0 <a href="http://www.tinymce.com/wiki.php/Tutorial:Migration_guide_from_3.x">migration guide</a> and the <a href="http://www.tinymce.com/wiki.php/api4:index">4.0 API documentation</a>.</li>\n<li>WordPress plugins that add third-party or default TinyMCE plugins would (of course) need to be updated to include the 4.0 version of the plugin. The PHP global $tinymce_version can be used to determine which plugin to load.</li>\n<li>Mini-plugins that only add a button to the toolbar. This works pretty much the same. It is advisable to update to use the ‘dashicons’ icon font instead of image icon.</li>\n</ul>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/TinyMCE40Icons.jpg" rel="prettyphoto[15016]"><img class="alignright size-full wp-image-15026" alt="TinyMCE 4.0 Icons" src="http://wptavern.com/wp-content/uploads/2014/01/TinyMCE40Icons.jpg" width="315" height="136" /></a>After upgrading to the bleeding edge version of WordPress 3.9 to compare the visual editor with WordPress 3.8, I immediately noticed that the <a title="http://ran.ge/wordpress-plugin/pull-quotes/" href="http://ran.ge/wordpress-plugin/pull-quotes/">Pull Quotes</a> icon image that&#8217;s added to the visual editor disappeared. While the place holder is still there and the button functions normally, the icon image is gone. There are two other plugins that have added custom icon images to the visual editor and those work just fine. However, since they are not using SVG images or Dashicons, the experience is not consistent with the rest of the interface.</p>\n<p>If you&#8217;re the author of a plugin that modifies or changes the behavior of TinyMCE, now is the time to test it against the trunk of WordPress so users don&#8217;t encounter unexpected changes when they upgrade to WordPress 3.9.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 21:00:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:32;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"WPTavern: WordCamp Paris 2014: Uniting The French WordPress Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14988";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:180:"http://wptavern.com/wordcamp-paris-2014-uniting-the-french-wordpress-community?utm_source=rss&utm_medium=rss&utm_campaign=wordcamp-paris-2014-uniting-the-french-wordpress-community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5823:"<p>The third official <a href="http://2014.paris.wordcamp.org/" target="_blank">WordCamp Paris</a> was held this past weekend, featuring 15 talks and seven workshops during Jan 17-18. From all accounts it seems to have been a stellar event. The first day focused on business and enterprise and the second day included a mix of talks and workshops focused on tech, design and community topics.</p>\n<p>All of the WordCamps that we&#8217;ve attended and reported on have been held in English, so I got in touch with <a href="http://www.jennybeaumont.com/" target="_blank">Jenny Beaumont</a> to see if she could give us an inside look into WordCamp Paris. </p>\n<div id="attachment_15019" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2014/01/jennyb.jpg" rel="prettyphoto[14988]"><img src="http://wptavern.com/wp-content/uploads/2014/01/jennyb.jpg" alt="WordPress Developer Jenny Beaumont - photo credit: cc license -  Manuel Schmalstieg" width="610" height="534" class="size-full wp-image-15019" /></a><p class="wp-caption-text">WordPress Developer Jenny Beaumont &#8211; photo credit: cc license &#8211;  <a href="http://www.flickr.com/photos/kinetoskop/12030822934/sizes/c/in/set-72157639932762833/">Manuel Schmalstieg</a></p></div>\n<p>Beaumont came to France in 1998 where she began her career in the web. She now lives in rural Normandy and works as a freelance front-end developer specializing in WordPress. </p>\n<p>While most of the sessions were given in French, a handful of presentations were in English. WordCamp Paris featured an impressive variety of topics, including challenges for WordPress agencies, pricing a WordPress site, multisite and multilingual case studies, e-commerce, interface design and much more. </p>\n<p>Beaumont attended 10 of the 23 conferences and workshops and said that two sessions were particularly outstanding. &#8220;There were a lot of interesting topics presented, including a round table debate about the world of theming,&#8221; she said. &#8220;But for me, two sessions really stood out above the rest: <a href="https://twitter.com/glueckpress" target="_blank">Caspar Hübinger</a>&#8216;s presentation &#8220;<a href="http://glueckpress.com/5175" target="_blank">The Multilingual Blogging Software Dilemma (and ways to solve it)</a>&#8220;, and <a href="https://twitter.com/BoiteAWeb" target="_blank">Julio Potier</a>&#8216;s &#8220;<a href="http://fr.slideshare.net/Boiteaweb/choisir-les-bons-hooks-dans-vos-dveloppements-wordpress" target="_blank">Diving into WordPress Hooks</a>&#8221; (rough translation). They were both tight, incredibly funny and very well delivered.&#8221;</p>\n<h3>Workshops: An Alternative to Contributor Days</h3>\n<p>WordCamp Paris is unique in that the organizers have opted for facilitating workshops instead of hosting a contributor day. These are small sessions where Beaumont says everyone is encouraged to get into the nitty-gritty of subjects like hooks, multilingual publishing, SEO, the why and how of creating plugins and working with advanced custom fields. &#8220;I think we&#8217;re seeing what other WordCamps are, from what I&#8217;ve heard,&#8221; Beaumont said. &#8220;And that&#8217;s a clear move from being technically oriented to really addressing all aspects — and all users — of the WordPress ecosystem.&#8221; The workshops at WordCamp Paris provided something for users of every level of WordPress expertise. </p>\n<h3>The French WordPress Community Is Growing</h3>\n<div id="attachment_15013" class="wp-caption alignright"><a href="http://wptavern.com/wp-content/uploads/2014/01/wcparis.jpg" rel="prettyphoto[14988]"><img src="http://wptavern.com/wp-content/uploads/2014/01/wcparis.jpg" alt="photo credit: gd6d - cc license" width="1600" height="556" class="size-full wp-image-15013" /></a><p class="wp-caption-text">photo credit: <a href="http://www.flickr.com/photos/gd6d/12035168424/in/photostream/">gd6d</a> &#8211; cc license</p></div>\n<p>Beaumont attended the last two WordCamps held in Paris and she believes that the French WordPress community is growing in numbers and may expand to host another event outside of Paris.</p>\n<blockquote><p>Although WordCamps have only been held in Paris to date, the French community is taking root in every region of France, and I shouldn&#8217;t neglect mentioning our French-speaking neighbors in Belgium and Switzerland who also had a presence. I predict a strong increase in the number of Meetups for 2014 and it wouldn&#8217;t surprise me to see a WordCamp pop up outside of Paris in the near future.</p></blockquote>\n<p>Every local WordPress community faces its own unique challenges. I asked Beaumont how she would characterize the French WordPress community, based on her experience at large events over the past few years. She replied:</p>\n<blockquote><p>Had you asked me that last year I might have responded &#8220;fractured and stubborn&#8221;, but that is clearly no longer the case. I really feel that something special happened at WordCamp Europe back in October, something that inspired a momentum that we&#8217;re all still riding on today. People are coming together, opening up and crossing divides. There is a ton of creative energy and talent here — what&#8217;s been missing is the true spirit of giving and sharing, of community! That is shifting and it&#8217;s exciting to be a part of it.</p></blockquote>\n<p>It&#8217;s good news to hear that WordPress events in Europe are bringing the French WordPress community together in a new way, with more meetups and collaboration on the horizon. For more photos and tweets related to the event, check out the <a href="http://wcparis.wparmchair.com/" target="_blank">WP Armchair site for WordCamp Paris 2014</a>. If you attended WordCamp Paris, what was your take on the event? </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 20:27:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:75:"WPTavern: How to Check For Broken Links On Your Site Using Xenu Link Sleuth";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14902";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:194:"http://wptavern.com/how-to-check-for-broken-links-on-your-site-using-xenu-link-sleuth?utm_source=rss&utm_medium=rss&utm_campaign=how-to-check-for-broken-links-on-your-site-using-xenu-link-sleuth";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3731:"<p>Checking for broken links using WordPress plugins can lead to intensive use of server resources and impact site performance. Plugins like <a title="http://wordpress.org/plugins/broken-link-checker/" href="http://wordpress.org/plugins/broken-link-checker/">Broken Link Checker</a> are restricted on certain webhosts because of the performance issues they can introduce to a site. Thankfully, there are free programs available that off-load the process of checking links from the web server to a local machine. <a title="http://home.snafu.de/tilman/xenulink.html#Download" href="http://home.snafu.de/tilman/xenulink.html#Download">Xenu Link Sleuth</a> is one such program. Released in 2010, Xenu Link Sleuth is compatible with Microsoft Windows 95/98/ME/NT/2000/XP/Vista/7.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/XenuBrokenURLS.jpg" rel="prettyphoto[14902]"><img class="aligncenter size-large wp-image-14965" alt="Xenu Link Sleuth Broken URLs" src="http://wptavern.com/wp-content/uploads/2014/01/XenuBrokenURLS-500x204.jpg" width="500" height="204" /></a></p>\n<p>After installing the program to your machine, type in the URL you want to check. Link verification is performed on <strong>normal links, images, frames, plug-ins, backgrounds, local image maps, style sheets, scripts and java applets</strong>. It displays a continuously updated list of URLs which you can sort by different criteria. Reports can be generated at any time. Since the majority of processing takes place on the machine performing the report, it&#8217;s quicker and doesn&#8217;t need a database to store the results. Another advantage is that unlike online services, you&#8217;re not limited to a maximum number of URLs that can be checked.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/XenuCheckURL.jpg" rel="prettyphoto[14902]"><img class="aligncenter size-large wp-image-14961" alt="Xenu Check URL" src="http://wptavern.com/wp-content/uploads/2014/01/XenuCheckURL-500x452.jpg" width="500" height="452" /></a></p>\n<p>When I generated a report for WPTavern.com, Xenu used between 29-30 threads and checked over 10,000 urls. Green colored text signals no errors while red indicates a problem. In my case, it usually meant the image was not found. Since a report can be made up of thousands of links, Xenu Link Sleuth provides the ability to only view broken ones.</p>\n<div id="attachment_14962" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2014/01/XenuStatusText.jpg" rel="prettyphoto[14902]"><img class="size-large wp-image-14962" alt="Xenu Link Sleuth Status Text" src="http://wptavern.com/wp-content/uploads/2014/01/XenuStatusText-500x250.jpg" width="500" height="250" /></a><p class="wp-caption-text">Green Is Good. Red Is Bad</p></div>\n<p>Although Xenu Link Sleuth does not work natively on the Mac, a program called <a title="http://peacockmedia.co.uk/integrity/" href="http://peacockmedia.co.uk/integrity/">Integrity</a> for Mac OS X Mavericks is available. Integrity was recently updated to include support for Mavericks and retina displays.</p>\n<h3>Good Practice or Waste Of Time?</h3>\n<p>By using Xenu Link Sleuth, I was able to see hundreds of broken links of the thousands that make up the WPTavern archive. I feel conflicted on whether I should fix them or not. Links breaking are part of the natural life cycle of the web. Part of me wants to make sure each link that exists on the domain works correctly. The other part feels that by changing the URL, I would be altering history. Should I only concern myself with links up to a certain time period? How often do you check for broken links on your site? What programs or services do you use to perform the task?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 18:00:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"WPTavern: GoDaddy Launches Managed WordPress Hosting Service";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14897";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:164:"http://wptavern.com/godaddy-launches-managed-wordpress-hosting-service?utm_source=rss&utm_medium=rss&utm_campaign=godaddy-launches-managed-wordpress-hosting-service";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5948:"<p><a href="http://wptavern.com/wp-content/uploads/2014/01/GoDaddyLogoSmall.jpg" rel="prettyphoto[14897]"><img class="alignright size-full wp-image-14958" alt="GoDaddy Small Logo" src="http://wptavern.com/wp-content/uploads/2014/01/GoDaddyLogoSmall.jpg" width="169" height="77" /></a>As Marcus Couch <a title="http://wptavern.com/its-go-time-godaddy-teases-future-managed-wordpress-hosting" href="http://wptavern.com/its-go-time-godaddy-teases-future-managed-wordpress-hosting">hinted at</a> back on November 27th, 2013, GoDaddy has <a title="http://www.godaddy.com/hosting/wordpress-hosting.aspx?ci=86979" href="http://www.godaddy.com/hosting/wordpress-hosting.aspx?ci=86979">entered the Managed WordPress hosting</a> space. Plans start at <strong>$6.29</strong> per month and include DDoS protection, firewalls, automatic updates and an easy one-click migration tool. GoDaddy states that their service will have <em>blistering speed and guaranteed <a title="http://www.godaddy.com/agreements/showdoc.aspx?pageid=hosting_sa" href="http://wptavern.com/  http://www.godaddy.com/agreements/showdoc.aspx?pageid=hosting_sa">99.9% uptime</a></em>.</p>\n<h3>More Of The Same</h3>\n<p>GoDaddy has a list of <a title="http://support.godaddy.com/help/article/8964/managed-wordpress-blacklisted-plugins" href="http://support.godaddy.com/help/article/8964/managed-wordpress-blacklisted-plugins">restricted plugins</a> similar to <a title="http://wpengine.com/support/disallowed-plugins/" href="http://wpengine.com/support/disallowed-plugins/">WP Engine</a>. GoDaddy explains that by restricting the plugins listed, it keeps their managed accounts secure. GoDaddy doesn&#8217;t have the best track record of being a secure webhost. <a title="http://blog.sucuri.net/2010/06/godaddy-sites-hacked-with-cloudisthebestnow.html" href="http://blog.sucuri.net/2010/06/godaddy-sites-hacked-with-cloudisthebestnow.html">In 2010</a>, the company experienced a number of malware type hacks on their hosting service as did other major hosting providers such as <a title="http://blog.sucuri.net/2010/06/blacklisted-sites-at-netsol.html" href="http://blog.sucuri.net/2010/06/blacklisted-sites-at-netsol.html">Network Solutions</a>.</p>\n<div id="attachment_14957" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2014/01/GoDaddyHacked2010.jpg" rel="prettyphoto[14897]"><img class="size-large wp-image-14957" alt="GoDaddy Hacked In 2010" src="http://wptavern.com/wp-content/uploads/2014/01/GoDaddyHacked2010-500x110.jpg" width="500" height="110" /></a><p class="wp-caption-text">As Reported By Sucuri In 2010</p></div>\n<p><a title="http://wptavern.com/its-go-time-godaddy-teases-future-managed-wordpress-hosting#comment-49358" href="http://wptavern.com/its-go-time-godaddy-teases-future-managed-wordpress-hosting#comment-49358">One of the fears</a> expressed by readers was that they would undercut the competition with rock bottom prices. Here is a comparison between a few different WordPress managed hosting providers using their cheapest plan as the lowest common denominator.</p>\n<ul>\n<li>GoDaddy &#8211; <strong>$6.99</strong> / month</li>\n<li>Siteground &#8211; <strong>$9.95</strong> / month</li>\n<li>Flywheel &#8211; <strong>$15.00</strong> / month</li>\n<li>DreamPress &#8211; <strong>$19.95</strong> / month</li>\n<li>Pagely &#8211; <strong>$24.00</strong> / month</li>\n<li>Pressable &#8211; <strong>$25.00</strong> / month</li>\n<li>Synthesis &#8211; <strong>$27.00</strong> / month</li>\n<li>WP Engine &#8211; <strong>$29.00</strong> / month</li>\n</ul>\n<h3>GoDaddy Is The Cheapest But That Doesn&#8217;t Mean They Win</h3>\n<p>If price were the only determining factor for choosing a managed WordPress webhost, GoDaddy would win. However, it&#8217;s important to note that each company applies different limits and options to their plans. These variations are one of the reasons for the variety of prices. Based on conversations I&#8217;ve had with a number of WordPress consultants who deal with webhosting companies on a daily basis, GoDaddy is not on the top of their list as a recommendation to their clients.</p>\n<p><a title="http://wptavern.com/its-go-time-godaddy-teases-future-managed-wordpress-hosting#comment-49430" href="http://wptavern.com/its-go-time-godaddy-teases-future-managed-wordpress-hosting#comment-49430">According to Donnacha</a>, GoDaddy entering the market should help push prices closer to where they ought to be.</p>\n<blockquote><p>Frankly, the existing “specialist” WordPress hosting companies are useless when a client has anything more than a minor problem. I have long thought that what customers are getting is, roughly, a $10 value for $30, with ridiculous jumps in billing for minor increases in resources. The entry of bigger players such as GoDaddy will, at least, push prices closer to where they should be.</p></blockquote>\n<p>With that said, I don&#8217;t think established managed WordPress hosting companies have anything to fear. GoDaddy may have the cheapest prices, but they will have to work extremely hard to earn back the goodwill of the WordPress community.</p>\n<h3>Low Prices Won&#8217;t Be Enough</h3>\n<p>Since the departure of Bob Parsons as CEO, the company has changed its image from sexy women and hunting elephants to being much more professional as a business. I think GoDaddy has improved in many areas in the past two years but they still have a ways to go. The company has sponsored a number of WordCamps and has been very supportive of the WordPress project. But it&#8217;s going to take time and dedication to change the minds of so many WordPress hosting customers who have had a bad experience with the company the past three years. I&#8217;m looking forward to the day when I hear people recommending GoDaddy for hosting versus the other way around.</p>\n<p>I&#8217;d love to hear from customers who are currently using the new GoDaddy managed WordPress hosting service.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 17:30:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:68:"WPTavern: 10 Free Plugins to Customize WordPress Admin Color Schemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14676";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:180:"http://wptavern.com/10-free-plugins-to-customize-wordpress-admin-color-schemes?utm_source=rss&utm_medium=rss&utm_campaign=10-free-plugins-to-customize-wordpress-admin-color-schemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7061:"<p>Can you believe that there are already ten plugins available for customizing WordPress admin color schemes? This feature has been popular among plugin developers since the new admin design was added in the 3.8 release. We&#8217;ve selected ten plugins that offer a wide variety of ways to customize and control admin color schemes. Many of these plugins have very similar names, so it might be easy to get them confused. However, if you look closely you&#8217;ll find each does something slightly different.</p>\n<h3>Admin Color Schemes</h3>\n<p><a href="http://wordpress.org/plugins/admin-color-schemes/"><img src="http://wptavern.com/wp-content/uploads/2014/01/admin-color-schemes.png" alt="admin-color-schemes" width="1544" height="500" class="aligncenter size-full wp-image-14917" /></a></p>\n<p>WordPress ships with eight different color schemes. The <a href="http://wordpress.org/plugins/admin-color-schemes/" target="_blank">Admin Color Schemes</a> plugin adds eight additional, professionally designed options for you to choose from. </p>\n<h3>Grey Admin Color Schemes</h3>\n<p><a href="http://wordpress.org/plugins/grey-admin-color-schemes/"><img src="http://wptavern.com/wp-content/uploads/2014/01/grey.png" alt="grey" width="772" height="250" class="aligncenter size-full wp-image-14922" /></a></p>\n<p>The <a href="http://wordpress.org/plugins/grey-admin-color-schemes/" target="_blank">Grey Admin Color Schemes</a> plugin offers four slightly varied grey schemes, including the classic grey color scheme from WordPress 3.7, a blue-tinted grey scheme, a modern grey and a post-modern grey.</p>\n<h3>Admin Color Schemer</h3>\n<p><a href="http://wordpress.org/plugins/admin-color-schemer/"><img src="http://wptavern.com/wp-content/uploads/2013/12/featured-admin-color-schemer.jpg" alt="featured-admin-color-schemer" width="800" height="259" class="aligncenter size-full wp-image-13824" /></a></p>\n<p>We <a href="http://wptavern.com/admin-color-schemer-the-easiest-way-to-customize-wordpress-admin-colors" target="_blank">featured</a> the <a href="http://wordpress.org/plugins/admin-color-schemer/" target="_blank">Admin Color Schemer</a> plugin on WPTavern at the end of December. It provides one of the easiest and most comprehensive ways to create and preview admin color schemes without having to touch any code. It includes 30 advanced options, including  the ability to customize body background, links, menu background, menu current background, checked form controls and more.</p>\n<h3>WP Admin Classic Colors</h3>\n<p><a href="http://wordpress.org/plugins/wp-admin-classic-colors/"><img src="http://wptavern.com/wp-content/uploads/2014/01/wp-admin-classic-colors.png" alt="wp-admin-classic-colors" width="772" height="250" class="aligncenter size-full wp-image-14924" /></a></p>\n<p><a href="http://wordpress.org/plugins/wp-admin-classic-colors/" target="_blank">WP Admin Classic Colors</a> adds a new color scheme option to WordPress. It recreates the scheme that shipped with WordPress prior to 3.8, using light grey and blue colors. It also adds visible menu separators between menu blocks and menu items.</p>\n<h3>WP Admin Classic</h3>\n<p><a href="http://wordpress.org/plugins/wp-admin-classic/"><img src="http://wptavern.com/wp-content/uploads/2014/01/old-admin-style.png" alt="old-admin-style" width="800" height="353" class="aligncenter size-full wp-image-14935" /></a></p>\n<p><a href="http://wordpress.org/plugins/wp-admin-classic/" target="_blank">WP Admin Classic</a> disables the new admin theme in WordPress 3.8 and turns on the old design instead. I have no idea why you would ever want to use this plugin, but it&#8217;s out there if you resist the new admin design and want to revert your site backwards.</p>\n<h3>Color Schemes Roulette</h3>\n<p><a href="http://wordpress.org/plugins/color-schemes-roulette/"><img src="http://wptavern.com/wp-content/uploads/2014/01/roulette.png" alt="roulette" width="1544" height="500" class="aligncenter size-full wp-image-14930" /></a></p>\n<p><a href="http://wordpress.org/plugins/color-schemes-roulette/" target="_blank">Color Schemes Roulette</a> is a fun plugin that randomly changes the admin color scheme every time you publish a post. It was created to help motivate users to publish more and also works hand-in-hand with the <a href="http://wordpress.org/plugins/admin-color-schemes/" target="_blank">Admin Color Schemes</a> plugin.</p>\n<h3>Default Admin Color Scheme</h3>\n<p><a href="http://wordpress.org/plugins/default-admin-color-scheme/"><img src="http://wptavern.com/wp-content/uploads/2014/01/default-admin-color-scheme.png" alt="default-admin-color-scheme" width="1544" height="500" class="aligncenter size-full wp-image-14932" /></a></p>\n<p><a href="http://wordpress.org/plugins/default-admin-color-scheme/" target="_blank">Default Admin Color Scheme</a> lets you select a default admin color scheme for new and existing users. It adds a new option to Settings > General where you can select a default color scheme for all users. You can also disable the color scheme picker on the Users > Profile page if you don&#8217;t want users to change it.</p>\n<h3>Quick Admin Color Scheme Picker</h3>\n<p><a href="http://wordpress.org/plugins/quick-admin-color-scheme-picker/"><img src="http://wptavern.com/wp-content/uploads/2014/01/quick-admin-color-scheme-picker.png" alt="quick-admin-color-scheme-picker" width="1592" height="613" class="aligncenter size-full wp-image-14939" /></a></p>\n<p><a href="http://wordpress.org/plugins/quick-admin-color-scheme-picker/" target="_blank">Quick Admin Color Scheme Picker</a> adds the color scheme options to the &#8220;Howdy&#8221; menu in the top right of the WordPress admin for quick access.</p>\n<h3>HS Custom Admin Theme</h3>\n<p><a href="http://wordpress.org/plugins/hs-custom-admin-themes/"><img src="http://wptavern.com/wp-content/uploads/2014/01/hs-admin-color-scheme.png" alt="hs-admin-color-scheme" width="772" height="250" class="aligncenter size-full wp-image-14941" /></a></p>\n<p><a href="http://wordpress.org/plugins/hs-custom-admin-themes/" target="_blank">HS Custom Admin Theme</a> gives you the ability to design your own color palettes for the WordPress admin area and then save them within a library of color schemes for later use. The options let you customize the background color, font color, navigation menu color, and post and page form color. </p>\n<h3>Admin Bar Color</h3>\n<p><a href="http://wordpress.org/plugins/admin-bar-color/"><img src="http://wptavern.com/wp-content/uploads/2014/01/admin-color-bar.png" alt="admin-color-bar" width="1430" height="459" class="aligncenter size-full wp-image-14943" /></a></p>\n<p><a href="http://wordpress.org/plugins/admin-bar-color/" target="_blank">Admin Bar Color</a> is a simple plugin that applies your active admin color scheme to the front-end WordPress admin bar. This provides a more unified experience when switching between the front and the backend.</p>\n<p>Did we miss any of your favorites? Which plugins do you find to be the most useful for customizing admin color schemes?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jan 2014 17:20:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: WPWeekly Episode 134 – Talking WordCamps With David Bisset";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:44:"http://wptavern.com?p=14904&preview_id=14904";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:176:"http://wptavern.com/wpweekly-episode-134-talking-wordcamps-with-david-bisset?utm_source=rss&utm_medium=rss&utm_campaign=wpweekly-episode-134-talking-wordcamps-with-david-bisset";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3860:"<p>This weeks edition of WordPress Weekly features special guest, <a href="http://www.davidbisset.com/" title="http://www.davidbisset.com/">David Bisset</a>. We were also joined by <a href="http://marcuscouch.com/" title="http://marcuscouch.com/">Marcus Couch.</a> After catching up on the headlines, we dove into the topic of WordCamps. Specifically, encouraging women to speak while also increasing diversity, new IRS regulations that corporate sponsors must abide by and last but not least, whether WordCamps need a dedicated safety officer or not. If you&#8217;re a current or future WordCamp organizer, this episode is for you! We concluded the show with Marcus giving his three plugin picks of the week. </p>\n<h2>Stories Discussed:</h2>\n<p><a href="http://wptavern.com/data-gov-is-using-wordpress-and-all-the-code-is-open-source" title="http://wptavern.com/data-gov-is-using-wordpress-and-all-the-code-is-open-source">Data.gov Is Using WordPress and All the Code is Open Source</a><br />\n<a href="http://wptavern.com/wordpress-managed-host-nodeki-goes-bust-no-refunds-for-lifetime-customers" title="http://wptavern.com/wordpress-managed-host-nodeki-goes-bust-no-refunds-for-lifetime-customers">WordPress Managed Host NodeKi Goes Bust: No Refunds For Lifetime Customers</a><br />\n<a href="http://wptavern.com/google-releases-its-first-plugin-for-wordpress-publishers" title="http://wptavern.com/google-releases-its-first-plugin-for-wordpress-publishers">Google Releases Its First Plugin For WordPress Publishers</a><br />\n<a href="http://wptavern.com/official-git-mirror-now-available-for-wordpress-core-development-repository" title="http://wptavern.com/official-git-mirror-now-available-for-wordpress-core-development-repository">Official Git Mirror Now Available for WordPress Core Development Repository</a><br />\n<a href="http://wptavern.com/tax-day-release-wordpress-3-9-to-drop-on-april-15" title="http://wptavern.com/tax-day-release-wordpress-3-9-to-drop-on-april-15">Tax Day Release: WordPress 3.9 to Drop on April 15</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href="http://wordpress.org/plugins/wp-draftsforfriends/" title="http://wordpress.org/plugins/wp-draftsforfriends/">WP-DraftsForFriends</a> is a plugin that will generate a unique link that you can send to your friends to allow them to preview your draft before they are published. You are able to set the expiry for the link as well.</p>\n<p><a href="http://wordpress.org/plugins/floating-publish-button/" title="http://wordpress.org/plugins/floating-publish-button/">Floating Publish Button</a> will help you click on &#8220;Publish/Update&#8221; button in admin panel without scrolling back to top of the page. The whole publish block floats downward as your scroll.</p>\n<p><a href="http://wordpress.org/plugins/wp-triggers-lite/" title="http://wordpress.org/plugins/wp-triggers-lite/">WP Triggers Lite</a> creates interactive trigger boxes. These are conditional boxes that display when the user types in a predetermined phrase or keywords. Once the criteria is met, it triggers what you want to display. If it does not meet the criteria you set, it will default to whatever you set the default process to do.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Friday, January 24th 3 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738" target="_blank">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href="http://www.wptavern.com/feed/podcast" target="_blank">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr" target="_blank">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #134:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 18 Jan 2014 07:17:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:41:"Alex King: Pixel Jar Joins Crowd Favorite";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://alexking.org/?p=19267";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"http://crowdfavorite.com/blog/2014/01/welcome-pixel-jar/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:738:"<p>I&#8217;m really excited to start working with Brandon and Jeffery; this is a great addition to the <a href="http://crowdfavorite.com">Crowd Favorite</a> family.</p>\n<p>UPDATE: Check out <a href="http://chrislema.com/great-things-often-start-small/">Chris Lema&#8217;s post</a> and <a href="http://www.pixeljar.net/2014/01/17/pixel-jar-is-being-aquired/">the announcement on Pixel Jar&#8217;s blog</a>.</p>\n<p class="threads-post-notice">This post is part of the thread: <a href="http://alexking.org/blog/thread/crowd-favorite">Crowd Favorite</a> &#8211; an ongoing story on this site. View the thread timeline for more context on this post.</p>\n<p><a href="http://alexking.org/blog/2014/01/17/pixel-jar-joins-crowd-favorite">#</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 18 Jan 2014 06:15:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Alex";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:76:"WPTavern: Remly Hosting Extends Offer to Lifetime Customers Jilted by NodeKi";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14878";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:196:"http://wptavern.com/remly-hosting-extends-offer-to-lifetime-customers-jilted-by-nodeki?utm_source=rss&utm_medium=rss&utm_campaign=remly-hosting-extends-offer-to-lifetime-customers-jilted-by-nodeki";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3840:"<p>After we reported on WordPress managed host <a href="http://wptavern.com/wordpress-managed-host-nodeki-goes-bust-no-refunds-for-lifetime-customers" target="_blank">NodeKi going out of business</a>, both former customers and the WordPress community were left wondering what happened behind the scenes. </p>\n<p>The Tavern was then contacted by the company who purchased NodeKi&#8217;s paying customers. Jonathan VanSchaack, director of the web division of <a href="http://www.remcom.net/" target="_blank">Remly Communications</a>, offered to fill us in on some of the details behind what happened to NodeKi&#8217;s customers before the collapse of the company. He said:</p>\n<blockquote><p>We had the opportunity to purchase NodeKi clients that were actively paying.  We did express some interest in the Lifetime clients but we chose not to as any business plan that relies on 0 revenue long term is due to fail. That being said we sent our own letter out to the paying customers of NodeKi letting them know we will be migrating them to our servers in the long term but also keeping their servers active.  We felt we could provide superior services along with great support to those clients. </p></blockquote>\n<p>VanSchaack said that he purchased the customers directly from NodeKi and not the InterQuad holding company. As <a href="http://www.remcom.net/" target="_blank">Remly</a> has been in business for 11 years and offers managed hosting for WordPress and other CMS platforms, they felt that it was a great fit. &#8220;Remly purchased the clients for expansion,&#8221; he said.  &#8220;We are in a growth area of our business now that we feel infrastructure is at a very stable point.&#8221; </p>\n<p>When asked how he became aware that NodeKi was wanting to sell off all of its customers, VanSchaack said that he was informed of the sale opportunity by a broker:</p>\n<blockquote><p>The current owner was looking for a home for the customers that would give similar support and offerings. To be honest his asking price was far below market value. As in my opinion, he was trying to find the right place for the customers he could move.  We looked at the lifetime clients but did not feel they fit into our business plan.</p></blockquote>\n<h3>An Offer For Displaced Lifetime Customers</h3>\n<p>Remly Hosting is offering a three month free trial matching the top lifetime plan NodeKi offered for those customer who have been displaced. This includes migration services for cPanel to cPanel transfers. VanSchaack has already been in contact with the owner and says that he is willing to give access to client accounts where permission is given by the customer. The plan includes a comparable set of resources previously provided by NodeKi, in terms of disk space, bandwidth, databases, additional domains. </p>\n<p>After the three months, former NodeKi customers can elect to break away from the hosting or transition to one of Remly&#8217;s paid Managed WordPress plans starting at $12.95 a month. VanSchaack said, &#8220;<strong>Our goal is to help customers that might be having issues on such a short notice but also show them our services are the same if not better than NodeKi and to stick with us long term.</strong>&#8221; Any NodeKi customers who are interested can email <a href="mailto:sales@remly.com">sales@remly.com</a> or open a support ticket under the NodeKi account and Remly will get involved. </p>\n<p>The lesson to consumers here is that no lifetime plan is ever guaranteed to last a lifetime, and may not even be available for the lifetime of the company. Customers can be bought and sold at any time. When you&#8217;re looking for a WordPress host, it&#8217;s good to do a little background research into the stability of the company, especially if it is new and offering deals that might seem too good to be true.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 17 Jan 2014 22:23:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:39;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:80:"WPTavern: New WordPress Trac Features Have Been Ported to bbPress and BuddyPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14720";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:204:"http://wptavern.com/new-wordpress-trac-features-have-been-ported-to-bbpress-and-buddypress?utm_source=rss&utm_medium=rss&utm_campaign=new-wordpress-trac-features-have-been-ported-to-bbpress-and-buddypress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3078:"<p>So far, 2014 is the year for making over <a href="https://core.trac.wordpress.org/" target="_blank">WordPress Trac</a>. Over the past couple weeks and during the holidays, Andrew Nacin has implemented a host of <a href="http://wptavern.com/wordpress-core-trac-gets-a-design-refresh-new-features-and-enhancements" target="_blank">new features</a> that make it easier for contributors to collaborate with one another, <a href="http://wptavern.com/wordpress-adds-per-ticket-notifications-to-trac" target="_blank">get better ticket notifications</a> and work more efficiently with new reports and keywords for sorting tickets.</p>\n<p>Yesterday Nacin <a href="https://make.wordpress.org/meta/2014/01/15/trac-updates/" target="_blank">posted</a> that he has now ported over most of these new features to other tracs hosted on WordPress.org (meta, bbPress, BuddyPress, GlotPress, themes and plugins), including: </p>\n<ul>\n<li>Use WP.org cookie authentication, SSL and refreshed design</li>\n<li>bbPress and BuddyPress now have their own skins</li>\n<li>Image attachment previews in tickets</li>\n<li>Email address syncing</li>\n<li>IRC cross-references for #wordpress-meta, #buddypress-dev, #bbpress-dev, #glotpress, #wordpress-gsoc</li>\n<li>Lots of bug fixes and tweaks</li>\n</ul>\n<p>Remember those pale yellow colored tickets? Trac is looking much better with projects using their own skins:</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/buddypress-trac.png" rel="prettyphoto[14720]"><img src="http://wptavern.com/wp-content/uploads/2014/01/buddypress-trac.png" alt="buddypress-trac" width="1500" height="926" class="aligncenter size-full wp-image-14863" /></a></p>\n<p>As BuddyPress, bbPress and other large projects use trac in a similar way to WordPress, it only makes sense that the new features would be ported over. It be awesome to have the same ticket-starring and per-ticket notifications features that have been added to the WordPress trac. Nacin said that these features are on their way:</p>\n<blockquote><p>Notifications are coming very soon to BuddyPress, bbPress, GlotPress, and meta. Probably in the next few days. Once a Trac is running the new notifications feature, that means it has been migrated to MySQL, which means the data is more accessible to the rest of WP.org, as well.</p></blockquote>\n<p>Nacin has also been experimenting with design/functionality of the plugins trac, which is looking pretty snazzy already:</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/plugin-trac.png" rel="prettyphoto[14720]"><img src="http://wptavern.com/wp-content/uploads/2014/01/plugin-trac.png" alt="plugin-trac" width="1571" height="1309" class="aligncenter size-full wp-image-14872" /></a></p>\n<p>He&#8217;s still working to add links from the plugin directory to these new pages, which could make things interesting for plugin authors. He also plans to add per-plugin notifications where committers will be subscribed by default. If you&#8217;re a plugin developer, watch for these changes to be added to WordPress.org in the coming days.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 17 Jan 2014 06:34:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:34:"Matt: WordPress &amp; Techmeme 100";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43451";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:34:"http://ma.tt/2014/01/techmeme-100/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2134:"<p>Whenever I visit a site I can usually tell whether it&#8217;s <a href="http://wordpress.org/">WordPress</a> or not within an instant &#8212; there&#8217;s just something about a WordPress site that is distinctive. <a href="http://www.w3.org/Provider/Style/URI.html">Super-clean permalinks</a> are usually a dead giveaway. One thing I&#8217;ve been noticing a lot lately is on my guilty pleasure for tech news, <a href="http://techmeme.com/">Techmeme</a>, it seems like almost every link I click is to a WordPress-powered site. Fortunately <a href="http://techmeme.com/lb">Techmeme provides a leaderboard</a> showing both rank and % of space a site has taken up in headlines in the past thirty days.</p>\n<p>The list changes almost every day but went ahead and took a snapshot of the top 100 as of January 16th and ran down the platform for each one, here&#8217;s how it ended up:</p>\n<p><img class="alignnone size-full wp-image-43460" src="http://i1.wp.com/s.ma.tt/files/2014/01/techmeme-100-cms.png?resize=604%2C300" alt="techmeme-100-cms" /></p>\n<p>WordPress comes in at 43%, custom or bespoke systems at 42%, and then the others. When you take into effect Techmeme&#8217;s &#8220;presence&#8221; factor WP jumps to 48.8% of presence in the top 100 and all Blogsmith, Drupal, Blogspot, Tumblr, and Typepad combined are 8.4%. If you curious of the raw data, here&#8217;s <a href="https://docs.google.com/spreadsheets/d/12wLHCZROu_JcQOtm-KXIY6AE2mj7no1mrNTItgy8uBk/edit?usp=sharing">the spreadsheet with the platforms</a>.</p>\n<p>This is just a snapshot, it&#8217;d be interesting to see how this evolves over time. It&#8217;s a small slice of the world of websites, but a very influential one. I&#8217;ve actually reached out to <a href="https://twitter.com/gaberivera">Gabe Rivera</a> a few times to sponsor the leaderboard page, putting a W logo next to the ones that run WordPress in the table, but nothing has come of it yet.</p>\n<p><em>Thanks to <a href="http://krutal.wordpress.com/">Krutal</a>, <a href="http://paolobelcastro.com/">Paolo</a>, and <a href="http://mattnt.wordpress.com/">MT</a> for help with this.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 17 Jan 2014 01:29:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:72:"WPTavern: Fullby: A Free Magazine Theme For WordPress Based on Bootstrap";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14689";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:186:"http://wptavern.com/fullby-a-free-magazine-theme-for-wordpress-based-on-bootstrap?utm_source=rss&utm_medium=rss&utm_campaign=fullby-a-free-magazine-theme-for-wordpress-based-on-bootstrap";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2824:"<p>Fullby is a beautiful new free WordPress theme <a href="http://www.marchettidesign.net/2014/01/fullby-free-responsive-grid-wordpress-theme/" target="_blank">released</a> last week, created by designer Andrea Marchetti. The theme is fully responsive, based on <a href="http://getbootstrap.com/" target="_blank">Bootstrap</a> and features a grid style. This super light theme includes only two images and is fully customizable via CSS.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/fullby.jpg" rel="prettyphoto[14689]"><img src="http://wptavern.com/wp-content/uploads/2014/01/fullby.jpg" alt="fullby" width="800" height="371" class="aligncenter size-full wp-image-14808" /></a></p>\n<p>If the design looks familiar, it&#8217;s because it was inspired by <a href="http://wordpress.org/themes/twentyfourteen" target="_blank">Twenty Fourteen</a>. However, it&#8217;s not a child theme. Unlike Twenty Fourteen, Fullby is a fluid theme that expands to use all the available space on any screen, including desktop, mobile, tablet and larger screens.</p>\n<h4>Fullby Features:</h4>\n<ul>\n<li>Gallery and Video Support &#8211; easily copy and paste a Youtube ID to publish.</li>\n<li>Fluid, modular and responsive grid style for posts</li>\n<li>Built with Bootstrap and Font Awesome &#8211; 369 icons available</li>\n<li>Featured Header Content &#8211; add &#8220;featured&#8221; content to header by using the &#8220;featured&#8221; tag in the post</li>\n<li>2 Menus and 2 Sidebars</li>\n<li>Popular and Latest Post Widget\n</li>\n</ul>\n<p>Every aspect of this theme shows attention to detail, including category pages, widgets and date-based archives. Single posts have a very striking appearance and are just as beautiful as the homepage design:</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/single-post.png" rel="prettyphoto[14689]"><img src="http://wptavern.com/wp-content/uploads/2014/01/single-post.png" alt="single-post" width="1272" height="806" class="aligncenter size-full wp-image-14843" /></a></p>\n<p>Check out a <a href="http://www.marchettidesign.net/fullby/demo/" target="_blank">live demo</a> to see the theme at its finest.</p>\n<p>Fullby caught my eye the other day, so I decided to install it on a test site and check it out. I assumed that there would be quite a bit of configuring to get it to look anything like the demo but was pleasantly surprised. There are no design-related options to tinker with. Further customization, however, will require some CSS knowledge.</p>\n<p>If you&#8217;re looking for a lean blogging or magazine style theme that is based on Bootstrap, then Fullby is a strong option. Download <a href="http://www.marchettidesign.net/fullby/" target="_blank">Fullby</a> for free from <a href="http://www.marchettidesign.net/" target="_blank">Marchetti Design</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 22:41:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:66:"Alex King: I’ll be at WordCamp PHX this weekend with a good c…";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://alexking.org/?p=19259";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"http://alexking.org/blog/2014/01/16/19259";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:256:"<div>\n<p>I&#8217;ll be at <a href="http://2014.phoenix.wordcamp.org/">WordCamp PHX</a> this weekend with a good contingent from <a href="http://crowdfavorite.com">Crowd Favorite</a>. I look forward to meeting a bunch of you internet folks there.</p>\n</div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 18:23:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Alex";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:89:"WPTavern: Why You Shouldn’t Be Worried About Screwing Up When Contributing To WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14791";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:216:"http://wptavern.com/why-you-shouldnt-be-worried-about-screwing-up-when-contributing-to-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=why-you-shouldnt-be-worried-about-screwing-up-when-contributing-to-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:11687:"<p>In the <a title="https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2014-01-15&sort=asc" href="https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2014-01-15&sort=asc">WordPress 3.9 development chat</a> that was held on <strong>Wednesday, January 15th</strong>, a number of topics were discussed ranging from features that people are working on to announcing the date for the release of <a title="http://wptavern.com/tax-day-release-wordpress-3-9-to-drop-on-april-15" href="http://wptavern.com/tax-day-release-wordpress-3-9-to-drop-on-april-15">WordPress 3.9</a>. One of the most interesting topics, however, centered around first time contributors using trac to create tickets and patches.</p>\n<p>Last week, <a title="http://wptavern.com/wordpress-core-trac-gets-a-design-refresh-new-features-and-enhancements" href="http://wptavern.com/wordpress-core-trac-gets-a-design-refresh-new-features-and-enhancements">one of the improvements</a> to trac was the addition of the &#8220;<em>good-first-bug</em>&#8221; tag. This tag will be used to identify tickets that are good starting points for new contributors. In my opinion, this is one of the most important changes to trac we have seen in a long time. Here&#8217;s why.</p>\n<div id="attachment_8216" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2013/08/482.jpg" rel="prettyphoto[14791]"><img class="size-large wp-image-8216" alt="WCSF Contributor Day" src="http://wptavern.com/wp-content/uploads/2013/08/482-500x373.jpg" width="500" height="373" /></a><p class="wp-caption-text">WCSF Contributor Day</p></div>\n<p>Near the end of the meeting, a number of people shared their stories of how they contributed to WordPress for the first time. Some people used the contributor day at WordCamp San Francisco to create their first patch or ticket while another did the same at WordCamp Orlando. When <a title="http://wptavern.com/my-first-ever-wordcamp-san-francisco-experience" href="http://wptavern.com/my-first-ever-wordcamp-san-francisco-experience">I attended the WordCamp San Francisco contributor day</a> 2013, I was able to create a ticket for a longstanding issue I&#8217;ve had with the WordPress Media Library. Without the help of Mika Epstein as a mentor, I wouldn&#8217;t have been comfortable enough to <a title="http://core.trac.wordpress.org/ticket/24859" href="http://core.trac.wordpress.org/ticket/24859">create the ticket</a>.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/TracIntimidation.jpg" rel="prettyphoto[14791]"><img class="aligncenter size-large wp-image-14815" alt="Trac Intimidation" src="http://wptavern.com/wp-content/uploads/2014/01/TracIntimidation-500x265.jpg" width="500" height="265" /></a></p>\n<h3>The Intimidation Factor</h3>\n<p>I was asked by Andrew Nacin why I felt <a title="https://core.trac.wordpress.org/" href="https://core.trac.wordpress.org/">trac</a> was intimidating. I consider trac to be a place where all the magic happens. It&#8217;s where you need to know diff files, ticket numbers, code, etc. It&#8217;s not something a common end-user would be comfortable in navigating. To me, trac is an entirely new world that I&#8217;ve always been too nervous to enter. I don&#8217;t think I&#8217;m alone in fearing trac or being intimated by it and thus, not contributing to WordPress in that way.</p>\n<div id="attachment_14816" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2014/01/GoodFirstBug.jpg" rel="prettyphoto[14791]"><img class="size-large wp-image-14816" alt="Good First Bug" src="http://wptavern.com/wp-content/uploads/2014/01/GoodFirstBug-500x315.jpg" width="500" height="315" /></a><p class="wp-caption-text">photo credit: <a href="http://www.flickr.com/photos/guitavares/1703252007/">gui.tavares</a> &#8211; <a href="http://creativecommons.org/licenses/by/2.0/">cc</a></p></div>\n<p>This is why I think the <em>&#8220;good-first-bug&#8221;</em> tag is so important. When someone new to trac picks those tickets to work on as their first, the expectation is for mistakes to happen. If a new contributor screws up a diff file or does something else wrong, it will be ok because it&#8217;s expected behavior. It takes a lot of stress off of the new contributor and creates a learning environment without the fear of screwing things up for everyone else.</p>\n<h3>They&#8217;re Not Angry, I Just Think They Might Be</h3>\n<p>I was then asked where the line of thinking comes from that results in me thinking that a developer might be “angry”? Are people giving off that impression? I don&#8217;t think it&#8217;s the impression those participating on trac are giving off but rather, an unnecessary fear I have. The fear in trac is doing something wrong, angering a developer, wasting their time, and making mistakes. I&#8217;ve never seen a public trac discussion where developers are yelling at newcomers for making dumb mistakes. Just the possibility of making established contributors angry is enough to prevent me from participating in that community. It&#8217;s an unnecessary tension that I think a lot of people feel.</p>\n<h3>Plenty Of People To Guide Me</h3>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/GuideMe.jpg" rel="prettyphoto[14791]"><img class="aligncenter size-large wp-image-14820" alt="Guide Me Compass" src="http://wptavern.com/wp-content/uploads/2014/01/GuideMe-500x269.jpg" width="500" height="269" /></a></p>\n<p>Thankfully, I was reassured from multiple people that I don&#8217;t need to feel the way I do and that there are plenty of people willing to stop what they&#8217;re doing to help guide me in the right direction. One of them was Andrew Nacin, one of the lead developers for WordPress.</p>\n<blockquote><p>Please never worry about angering a developer or doing something wrong or wasting someone&#8217;s time. I get angry at developers who get angry with contributors and if you ever do get the impression you&#8217;ve annoyed someone or are doing something wrong, anyone is always welcome to ping me privately and I&#8217;m happy to A) talk to you about it and walk you through it, and B) privately talk to any contributors who *are* causing problems.</p></blockquote>\n<p>What Andrew states is a sentiment that most in the WordPress Development IRC channel share. The fears that I have of screwing up are a large reason why I&#8217;m a huge fan of one-to-one mentorship. An individual who can help me through the ticket/patch process without fear of looking like a fool in front of established contributors. While there is an initiative to get a list of mentors put together, it will be awhile before something official is put in place.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/WPMentorFeaturedImage1.jpg" rel="prettyphoto[14791]"><img class="aligncenter size-large wp-image-14106" alt="WPMentor Featured Image" src="http://wptavern.com/wp-content/uploads/2014/01/WPMentorFeaturedImage1-500x207.jpg" width="500" height="207" /></a></p>\n<p>What I&#8217;ve seen at contributor days at WordCamps proves to me that a WordPress mentorship program would substantially increase the amount of first time contributors. It&#8217;s not about having my hand-held as I go through the process but rather, helping to build my confidence level to a point where I&#8217;m comfortable enough to go through the process on my own. Helen brought up a great point in the conversation. If you don&#8217;t have access to commit code to the core of WordPress that millions of people will use, then there should be no reason to fear the actions of creating tickets or submitting patches.</p>\n<h3>Contributing To WordPress For The First Time</h3>\n<p>When I <a title="http://wptavern.com/i-contributed-to-the-core-of-wordpress-and-you-can-too" href="http://wptavern.com/i-contributed-to-the-core-of-wordpress-and-you-can-too">contributed a patch to WordPress for the first time</a>, it was an exhilarating experience. Talk about an adrenaline rush! After I saw my name in the credits portion to help make WordPress 3.8 a reality, I wanted to learn everything there was to know about PHP and contribute to WordPress full-time. Of course, reality soon sunk in but it was an awesome experience. My hope is that the tickets labeled with the tag <em>&#8220;good-first-bug&#8221;</em> are blessed so when a person uses them to get their first patch into core, they will experience the same adrenaline rush I did and consider becoming a regular patch contributor to WordPress.</p>\n<h3>You&#8217;ll Need Thick Skin</h3>\n<div id="attachment_14821" class="wp-caption aligncenter"><a href="http://wptavern.com/wp-content/uploads/2014/01/ThickSkin.jpg" rel="prettyphoto[14791]"><img class="size-large wp-image-14821" alt="You''ll Need Thick Skin" src="http://wptavern.com/wp-content/uploads/2014/01/ThickSkin-500x332.jpg" width="500" height="332" /></a><p class="wp-caption-text">photo credit: <a href="http://www.flickr.com/photos/uberzombie/1029296894/">uberzombie</a> &#8211; <a href="http://creativecommons.org/licenses/by/2.0/">cc</a></p></div>\n<p>Not every patch makes it to core. Some of them are discarded and when it comes to using trac to contribute, you&#8217;ll need a thick skin and be able to accept defeat. However, those experiences build character and just because a patch is denied, doesn&#8217;t mean it&#8217;s game over. It&#8217;s important to note that while most of this article is dedicated to contributing to WordPress through trac, there are many other ways to contribute. As Helen noted in the conversation:</p>\n<blockquote><p>There are things beyond patches that are extremely valuable, and in some cases even more valuable. Great bug reports, reproducing elusive bugs, testing patches, refreshing patches, commenting on tickets so people don&#8217;t feel like they&#8217;re left hanging, etc.</p></blockquote>\n<p>So far, the best guide I&#8217;ve seen on the topic of contributing to WordPress was <a title="http://wp.smashingmagazine.com/2013/05/10/contributing-to-wordpress/" href="http://wp.smashingmagazine.com/2013/05/10/contributing-to-wordpress/">published by Siobhan McKeown</a>. While it&#8217;s from May of 2013, it does an excellent job of showcasing all of the different parts of the project that people can contribute to.</p>\n<h3>Conclusion:</h3>\n<p>My main take away from the WordPress developers chat is that my fear of navigating trac and contributing to WordPress through code is unwarranted. There are plenty of people willing to stop on a dime and help me through the process. All I need to do is ask. I also learned that getting new people to contribute through trac has become one of the top priorities for WordPress core developers.</p>\n<p>So far, trac has undergone a number of changes that reflect that train of thought and there are more to come. Thanks to improvements like the addition of the <em>&#8220;good-first-bug&#8221;</em>, trac doesn&#8217;t have to be such an intimidating place to begin contributing to WordPress through code. Trac is not a fraternity, it&#8217;s not a place where only the elite of WordPress programmers reside. Trac is just a tool to help improve WordPress, nothing more. <a title="http://wptavern.com/i-contributed-to-the-core-of-wordpress-and-you-can-too" href="http://wptavern.com/i-contributed-to-the-core-of-wordpress-and-you-can-too">I contributed to the core of WordPress and you can too!</a></p>\n<p><em>Credit for the title of this post goes to <strong><a title="http://profiles.wordpress.org/shelob9" href="http://profiles.wordpress.org/shelob9">shelob9</a></strong> also known as Josh Pollock from the WordPress development chat.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 17:21:54 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:44;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:66:"WPTavern: Aesop Storytelling Engine Launches Crowdfunding Campaign";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14827";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:176:"http://wptavern.com/aesop-storytelling-engine-launches-crowdfunding-campaign?utm_source=rss&utm_medium=rss&utm_campaign=aesop-storytelling-engine-launches-crowdfunding-campaign";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2820:"<p>Last week Nick Haskins introduced his <a href="http://wptavern.com/aesop-story-engine-an-open-source-wordpress-plugin-for-storytelling" target="_blank">open source storytelling plugin</a> for WordPress. The proof of concept allows publishers to create big, visual posts with multimedia storytelling tools built right into the WordPress post editor. The New York Times showcased this trend in its feature <a href="http://www.nytimes.com/newsgraphics/2013/12/30/year-in-interactive-storytelling/" target="_blank">2013: The Year in Interactive Storytelling</a>. The trouble is, before Aesop arrived on the scene, creating posts in story format required quite a bit of custom work in order to make it easy for publishers.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/story.png" rel="prettyphoto[14827]"><img src="http://wptavern.com/wp-content/uploads/2014/01/story.png" alt="story" width="1600" height="993" class="aligncenter size-full wp-image-14014" /></a></p>\n<p>Haskins has now launched a crowdfunding campaign to help him take the fully working beta and make it a reality for more people to use. He believes that Aesop is an important project that can fundamentally change how publishers build stories: </p>\n<blockquote><p>We have entered an age where publishers are seeking new methods of keeping readers engaged. We are already witnessing story, after story, after story, after story being released that really push the boundaries of what the web can do. And, we are reading that it takes 16 people 6 months to create these things. Not with Aesop. The engine can be used by anybody, without any code, and you can build stories by yourself, within minutes. All for free, fully GPL, within WordPress.</p></blockquote>\n<p>The $15,000 he&#8217;s raising will go towards forming a business, finishing the <a href="http://aesopstories.com/" target="_blank">hosted version of Aesop</a>, hiring another developer to help improve the plugin, and a few other odds and ends required for getting it officially launched. </p>\n<p>If Aesop reaches its stretch goal of $20,000, Haskins plans to run a &#8220;Theme Bounty,&#8221; to offer monetary rewards for themes that incorporate Aesop Story Engine. He also plans to establish an Aesop Marketplace for themes built just for Aesop.</p>\n<p>Check out Haskin&#8217;s <a href="http://playground.aesopstories.com/" target="_blank">live demos</a> if you want to see what he&#8217;s created, or <a href="https://github.com/bearded-avenger/aesop-core" target="_blank">download the plugin</a> for yourself to take it for a test drive. If you&#8217;d like to see the Aesop plugin improved and believe in this new publishing tool, head on over to the <a href="https://aesop.crowdhoster.com/storytelling-engine" target="_blank">Aesop Crowdhoster</a> page and donate.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 16:43:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:45;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:46:"WP iPhone: Upgrade to 3.8.6 for Reader Bug Fix";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:37:"http://wpiphone.wordpress.com/?p=1516";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:72:"http://ios.wordpress.org/2013/12/30/upgrade-to-3-8-6-for-reader-bug-fix/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1713:"<p>WordPress for iOS 3.8.6 is out and now available to download from the App Store. This release is a hot fix release designed to fix a bug where the Reader would crash when loading a video.</p>\n<h3>What’s next?</h3>\n<p>We are almost done with the next major version of the app (3.9) which will have quite a few UI and UX changes that we hope will improve your experience with the app. This release (3.8.6) will be the last release to support iOS6 as with 3.9 and beyond we will only support iOS7 to allow us to take advantage of the latest technologies and provide you our users with the best app possible. You can get a sneak peek of what&#8217;s coming <a href="https://github.com/wordpress-mobile/WordPress-iOS/issues?milestone=10&state=open">here</a>.</p>\n<p>A huge thanks to the contributors who worked on this release: <a href="http://github.com/koke">@koke</a> and <a href="http://github.com/aerych">@aerych</a>. If you would like to get involved with WordPress for iOS development, drop us a line at <a href="http://make.wordpress.org/mobile">make.wordpress.org/mobile</a> and grab a copy of the code at <a href="http://github.com/wordpress-mobile/WordPress-iOS">github.com/wordpress-mobile/WordPress-iOS</a>.</p>\n<p>Have feedback? Leave a comment below or tweet us <a href="https://twitter.com/WordPressiOS">@WordPressiOS</a></p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wpiphone.wordpress.com/1516/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wpiphone.wordpress.com/1516/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=ios.wordpress.org&blog=3882653&post=1516&subd=wpiphone&ref=&feed=1" width="1" height="1" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 13:45:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Sendhil";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:49:"WP iPhone: Upgrade to 3.8.5 for Various Bug Fixes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:37:"http://wpiphone.wordpress.com/?p=1512";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:75:"http://ios.wordpress.org/2013/12/10/upgrade-to-3-8-5-for-various-bug-fixes/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2241:"<p>WordPress for iOS 3.8.5 is out and now available to download from the App Store. This release is primarily a bug fix release.</p>\n<p>Some of the fixes included in this version are:</p>\n<ul>\n<li>Fixed a crash when loading the posts view.</li>\n<li>Fixed a crash when opening Reader comments.</li>\n<li>Fixed a Jetpack connectivity issue.</li>\n</ul>\n<p><a href="https://github.com/wordpress-mobile/WordPress-iOS/issues?milestone=9&page=1&state=closed">Full list of changes in version 3.8.5</a></p>\n<h3>What’s next?</h3>\n<p>We are currently hard at work on the next major version of the app(3.9) which will have quite a few UI and UX changes that we hope will improve your experience with the app. We as a team have also decided to only support iOS7 going forward in order to allow us to take advantage of the latest technologies and provide you our users with the best app possible. If you want a sneak peek of what’s coming take a look <a href="https://github.com/wordpress-mobile/WordPress-iOS/issues?milestone=10&state=open">here</a>.</p>\n<p>A huge thanks to the contributors who worked on this release: <a href="https://github.com/astralbodies">@astralbodies</a>, <a href="http://github.com/xtreme-rebecca-putinski">@xtreme-rebecca-putinski</a>, <a href="http://github.com/koke">@koke</a>, <a href="http://github.com/mikejohnstn">@mikejohnstn</a>, <a href="http://github.com/tomwitkin">@tomwitkin</a>, <a href="http://github.com/aerych">@aerych</a>. If you would like to get involved with WordPress for iOS development, drop us a line at <a href="http://make.wordpress.org/mobile">make.wordpress.org/mobile</a> and grab a copy of the code at <a href="http://github.com/wordpress-mobile/WordPress-iOS">github.com/wordpress-mobile/WordPress-iOS</a>.</p>\n<p>Have feedback? Leave a comment below or tweet us <a href="https://twitter.com/WordPressiOS">@WordPressiOS</a></p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/wpiphone.wordpress.com/1512/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/wpiphone.wordpress.com/1512/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=ios.wordpress.org&blog=3882653&post=1512&subd=wpiphone&ref=&feed=1" width="1" height="1" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 13:45:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Sendhil";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"WPTavern: Tax Day Release: WordPress 3.9 to Drop on April 15";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14778";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:162:"http://wptavern.com/tax-day-release-wordpress-3-9-to-drop-on-april-15?utm_source=rss&utm_medium=rss&utm_campaign=tax-day-release-wordpress-3-9-to-drop-on-april-15";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2750:"<p>The date for the WordPress 3.9 release has now been set for April 15th, which coincides with <a href="http://en.wikipedia.org/wiki/Tax_day" target="_blank">tax day</a> in the US. American developers may want to do their taxes early, because the 3.9 release schedule will be keeping everyone busy. Tentative <a href="http://wordpress.org/about/roadmap/" target="_blank">dates</a> for the 4.0 and 4.1 releases are mid-August and early December, respectively.</p>\n<p>The second order of business during the regularly scheduled WordPress dev meeting this week was to discuss <a href="http://make.wordpress.org/core/features-as-plugins/" target="_blank">feature plugins</a> that might be in the mix for 3.9. </p>\n<h3>Possible Feature Plugins for 3.9</h3>\n<p>Shaun Andrews mentioned that the Widgets UI Refresh team is working on the <a href="http://wptavern.com/the-future-of-wordpress-widgets-a-better-ui-with-real-time-previews" target="_blank">Widget Customizer</a> and believes it will be ready for 3.9. The <a href="http://wordpress.org/plugins/widget-customizer/" target="_blank">Widget Customizer</a> plugin offers live previews of widgets while you edit them and is available on WordPress.org if you&#8217;d like to help test it.</p>\n<p>Shaun Andrews&#8217; <a href="http://wordpress.org/plugins/better-widgets" target="_blank">Better Widgets</a> plugin may also have enough momentum to make it into the 3.9 merge. These two widget-related plugins were the only ones mentioned in the meeting that might be ready for the feature review and merge process in 3.9, which should happen at the end of January into early February. The plugins are not guaranteed to be in 3.9 but they do have strong possibilities.</p>\n<h3>Iterative Enhancements for Existing Features</h3>\n<p>In addition to feature plugins, Nacin also identified a few areas where WordPress 3.9 could stand to iterate on previous releases: &#8220;<strong>Things like audio/video, even the theme browsing experience to the theme installer, are iterative and could totally take place in 3.9.</strong>&#8221; This is important because we can&#8217;t always focus on building shiny new features without looping back around to improve the ones we already have.</p>\n<p>The development meeting concluded with a brainstorming session on how to make it easier for people to contribute to WordPress. All of the <a href="http://wptavern.com/wordpress-adds-per-ticket-notifications-to-trac" target="_blank">recent</a> <a href="http://wptavern.com/wordpress-core-trac-gets-a-design-refresh-new-features-and-enhancements" target="_blank">improvements</a> to trac, especially the new reports and keyword designations, should help contributors to isolate and find tickets that they can jump in on.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jan 2014 01:30:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:66:"WPTavern: Push Notifications From WordPress To Mac Via Push Monkey";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14526";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:176:"http://wptavern.com/push-notifications-from-wordpress-to-mac-via-push-monkey?utm_source=rss&utm_medium=rss&utm_campaign=push-notifications-from-wordpress-to-mac-via-push-monkey";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3985:"<p>When OS X Mavericks was released, one of the new features added to the operating system was <a title="https://developer.apple.com/notifications/safari-push-notifications/" href="https://developer.apple.com/notifications/safari-push-notifications/">Safari Push Notifications</a>. The notifications use the new Apple Push Notifications service to notify users of new events. Since the feature was added to OS X Mavericks, there have been a number of services built around it. <a title="http://wordpress.org/plugins/roost-for-bloggers/" href="http://wordpress.org/plugins/roost-for-bloggers/">Roost For Bloggers</a> is one such service. However, the one I&#8217;m reviewing today is called <a title="http://pushmonkey.launchrock.com/" href="http://pushmonkey.launchrock.com/">Push Monkey</a> by <a title="http://mowowstudios.com/" href="http://mowowstudios.com/">moWOW studios</a>.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/PushMonkeySubscribeNotice.png" rel="prettyphoto[14526]"><img class="aligncenter size-large wp-image-14756" alt="Push Monkey Subscription Notice" src="http://wptavern.com/wp-content/uploads/2014/01/PushMonkeySubscribeNotice-500x184.png" width="500" height="184" /></a></p>\n<p>When Push Monkey is activated on the site and the domain is registered within the system, those who are using Mac OS X Mavericks and Safari 7 will see a notice asking if they would like to subscribe. Once subscribed to the site, they will receive new notifications each time a post is published. If the visitor chooses not the subscribe, they won&#8217;t be asked again. Posts that are already published or edited after being published will not generate a notification. Safari is used only for the initial subscription to the site. After that, notifications are received even when Safari is closed.</p>\n<p><a href="http://wptavern.com/wp-content/uploads/2014/01/PushMonkeySiteNotification.png" rel="prettyphoto[14526]"><img class="aligncenter size-large wp-image-14757" alt="Push Monkey Site Notification" src="http://wptavern.com/wp-content/uploads/2014/01/PushMonkeySiteNotification-500x158.png" width="500" height="158" /></a></p>\n<p>Tudor Munteanu, one of the developers behind Push Monkey told me that while Safari is the only way to see the subscription notice, they have plans for more custom integration similar to <a title="http://www.macrumors.com/" href="http://www.macrumors.com/">Macrumors</a>. The reason why it&#8217;s not part of the initial offering is because it&#8217;s heavily dependent on the websites visual identity. Push Monkey is currently in the alpha stage of development with plans to have it finished by the end of this month. When I asked whether Push Monkey would be free to use, Tudor responded:</p>\n<blockquote><p>It will most likely be a paid service. We do have some price points in mind, but the final values are not crystal clear. What we do know is that this price point is slightly under what we saw similar services asked for in the past. On top of that, for developers who have contacts to content publishers, we plan to have a very generous affiliate system.</p></blockquote>\n<h3>Choices Are Abundant But I Have Questions</h3>\n<p>During the time I&#8217;ve reviewed Push Monkey, I&#8217;ve received three other requests to review similar plugins and services. I didn&#8217;t realize there was so much demand for something that caters to a select demographic of website visitors. I don&#8217;t understand what the benefits are to using this notification system versus RSS, or something like <a title="http://code.google.com/p/pubsubhubbub/" href="http://code.google.com/p/pubsubhubbub/">PubHubSubHub</a> combined with the <a title="http://wordpress.org/plugins/pushpress/" href="http://wordpress.org/plugins/pushpress/">PuSHPress</a> plugin. The question I have for website owners is why would you cater to a specific audience instead of focusing on enabling anyone on any device to be able to receive real-time updates?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 15 Jan 2014 21:33:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"Jeffro";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:49;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:85:"WPTavern: Official Git Mirror Now Available for WordPress Core Development Repository";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=14741";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:214:"http://wptavern.com/official-git-mirror-now-available-for-wordpress-core-development-repository?utm_source=rss&utm_medium=rss&utm_campaign=official-git-mirror-now-available-for-wordpress-core-development-repository";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4560:"<p>Andrew Nacin <a href="http://make.wordpress.org/core/2014/01/15/git-mirrors-for-wordpress/" target="_blank">announced</a> official git mirrors for WordPress this afternoon on the WordPress make/core development blog. These are read-only mirrors that correspond to the WordPress core development SVN repository. Git mirrors are also now available for BuddyPress, bbPress, GlotPress and the old core.svn “build” repository:</p>\n<pre>git clone git://develop.git.wordpress.org/\ngit clone git://buddypress.git.wordpress.org/\ngit clone git://bbpress.git.wordpress.org/\ngit clone git://core.git.wordpress.org/\ngit clone git://glotpress.git.wordpress.org/</pre>\n<p>Needless to say, developers who contribute to WordPress and/or its major ancillary projects are thrilled:</p>\n<blockquote class="twitter-tweet" lang="en"><p>Official GIt Mirrors for WordPress: <a href="http://t.co/nJUi3yK4EP">http://t.co/nJUi3yK4EP</a> Can I get a Hallelujah?</p>\n<p>&mdash; Mike Schinkel (@mikeschinkel) <a href="https://twitter.com/mikeschinkel/statuses/423527837736255488">January 15, 2014</a></p></blockquote>\n<p></p>\n<blockquote class="twitter-tweet" lang="en"><p>Read make/core post by <a href="https://twitter.com/nacin">@nacin</a>. Wait for stream of praise and love in comments. rinse. repeat.</p>\n<p>&mdash; Aaron Jorbin (@aaronjorbin) <a href="https://twitter.com/aaronjorbin/statuses/423528157300260864">January 15, 2014</a></p></blockquote>\n<p></p>\n<h3>Contributing to WordPress via Git</h3>\n<p>When asked what the plan is for accepting pull request directly on Github, Nacin replied, &#8220;I’ve been studying how some other projects do or don’t do this. Something to discuss in a few months, I imagine.&#8221; </p>\n<p>The current git contribution process is not quite as direct, but Nacin cites Scribu&#8217;s tutorial on <a href="http://scribu.net/wordpress/contributing-to-wordpress-using-github.html" target="_blank">Contributing To WordPress Using Github</a> as a place to get started.</p>\n<h3>Future Mirrors for Plugin and Theme Repositories</h3>\n<p>At the end of his announcement post, Nacin hints at the possibility of making git mirrors available for WordPress plugins and themes:</p>\n<blockquote><p>There are a lot of other repositories on WordPress.org not yet mirrored. Notably: plugins and themes. These are massive multi-project repositories and will require a bit more investment.</p></blockquote>\n<p>An undertaking like this has the potential to please many more developers, as those who contribute to the WordPress core are still a relatively small number compared to those with active extensions on WordPress.org.</p>\n<h3>Is WordPress Moving Away From SVN?</h3>\n<p>Some of you might be wondering whether the new git mirrors are an indication that WordPress will eventually abandon SVN entirely in favor of git somewhere further down the road. That doesn&#8217;t seem to be the case, as Nacin replied on <a href="http://make.wordpress.org/core/2014/01/15/git-mirrors-for-wordpress/#comment-12428" target="_blank">comments</a> to his post:</p>\n<blockquote><p>If you or your tools want to use Git, you should be able to. If you or your tools want to use SVN, you should be able to. You could think of it as a desire to be VCS agnostic.</p></blockquote>\n<p>I interviewed Nacin briefly to ask him if the project is committed to keeping both version control options available in the future. He confirmed that SVN is going nowhere anytime soon but rather that the project is committed to letting developers choose:</p>\n<blockquote><p>We&#8217;re definitely committed to keeping both options available. Some developers are simply more used to X, or find X simpler, or find X cryptic/convoluted/difficult. I use both daily. With both options available, developers can use what they are most comfortable with or what fits best with their project, client, or company. There&#8217;s no need to force everyone to pick one, and there are a lot of tools and scripts people already use to interact with these SVN repositories, too. It just doesn&#8217;t make sense to not mirror between them for the long term.</p></blockquote>\n<p>For the next week it will be in beta, so there may be a few bugs that need to be ironed out. Hopefully, these new git mirrors will open up the doors for contributors to push more enhancements and fixes to the WordPress project. Given the massive popularity of git, we may look back to this time as a pivotal moment. For right now, suffice to say that these new git mirrors just made a ton of WordPress developers very happy.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 15 Jan 2014 21:19:17 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Mon, 27 Jan 2014 14:58:28 GMT";s:12:"content-type";s:8:"text/xml";s:14:"content-length";s:6:"209059";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Mon, 27 Jan 2014 14:30:15 GMT";s:4:"x-nc";s:11:"HIT lax 249";s:13:"accept-ranges";s:5:"bytes";}s:5:"build";s:14:"20130911020210";}', 'no');
