functions.php

<?php
/**
 * This is your child theme functions file.  In general, most PHP customizations should be placed within this
 * file.  Sometimes, you may have to overwrite a template file.  However, you should consult the theme
 * documentation and support forums before making a decision.  In most cases, what you want to accomplish
 * can be done from this file alone.  This isn't a foreign practice introduced by parent/child themes.  This is
 * how WordPress works.  By utilizing the functions.php file, you are both future-proofing your site and using
 * a general best practice for coding.
 *
 * All style/design changes should take place within your style.css file, not this one.
 *
 * The functions file can be your best friend or your worst enemy.  Always double-check your code to make
 * sure that you close everything that you open and that it works before uploading it to a live site.
 *
 * @package PrototypeChild
 * @subpackage Functions
 */

/* Uncomment the below line to use the child theme setup function. */
add_action( 'after_setup_theme', 'twentyfourteen_cyr_theme_setup', 10 );
/**
 * Setup function.  All child themes should run their setup within this function.  The idea is to add/remove
 * filters and actions after the parent theme has been set up.  This function provides you that opportunity.
 *
 * @since 0.1
 */
    function twentyfourteen_cyr_theme_setup() {

    add_action('wp_print_styles', 'pae_load_fonts');
}
    function pae_load_fonts() {
			wp_register_style('googleFonts', 'http://fonts.googleapis.com/css?family=Exo+2:400,300,700,900,300italic,400italic,700italic,900italic&subset=latin,cyrillic' );
            wp_enqueue_style( 'googleFonts');
        }
?>