Version Description
Download this release
Release Info
Developer | jamescollins |
Plugin | Typekit Fonts for WordPress |
Version | 1.0.2 |
Comparing to | |
See all releases |
Code changes from version 1.0.1 to 1.0.2
- readme.txt +10 -4
- typekit-admin.php +15 -6
- typekit-fonts-for-wordpress.pot +98 -59
- typekit.php +2 -2
readme.txt
CHANGED
@@ -3,17 +3,19 @@ Contributors: jamescollins, glenn-om4
|
|
3 |
Tags: typekit, fonts, font, design, wp, wpmu
|
4 |
Requires at least: 2.8
|
5 |
Tested up to: 2.9
|
6 |
-
Stable tag: 1.0.
|
7 |
|
8 |
Use a range of hundreds of high quality fonts on your WordPress website by integrating the Typekit font service into your WordPress blog.
|
9 |
|
10 |
== Description ==
|
11 |
|
12 |
-
Allows you to embed and use [Typekit](http://www.typekit.com) fonts in your WordPress website without having to edit your theme
|
13 |
|
14 |
Typekit offer a service that allows you to select from a range of hundreds of high quality fonts for your WordPress website. The fonts are applied using the font-face standard, so they are standards compliant, fully licensed and accessible.
|
15 |
|
16 |
-
To use this plugin you need to sign up with Typekit, install this plugin and then configure CSS
|
|
|
|
|
17 |
|
18 |
Compatible with both WordPress and WordPress MU (WPMU).
|
19 |
|
@@ -48,10 +50,14 @@ Please see [this page](http://getsatisfaction.com/typekit/topics/typekit_browser
|
|
48 |
|
49 |
== Changelog ==
|
50 |
|
|
|
|
|
|
|
|
|
51 |
= v1.0.1 =
|
52 |
* WordPress 2.9 compatibility
|
53 |
* Improve FAQ
|
54 |
|
55 |
= v1.0.0 =
|
56 |
|
57 |
-
*
|
3 |
Tags: typekit, fonts, font, design, wp, wpmu
|
4 |
Requires at least: 2.8
|
5 |
Tested up to: 2.9
|
6 |
+
Stable tag: 1.0.2
|
7 |
|
8 |
Use a range of hundreds of high quality fonts on your WordPress website by integrating the Typekit font service into your WordPress blog.
|
9 |
|
10 |
== Description ==
|
11 |
|
12 |
+
Allows you to embed and use [Typekit](http://www.typekit.com) fonts in your WordPress or WordPress MU website without having to edit your theme.
|
13 |
|
14 |
Typekit offer a service that allows you to select from a range of hundreds of high quality fonts for your WordPress website. The fonts are applied using the font-face standard, so they are standards compliant, fully licensed and accessible.
|
15 |
|
16 |
+
To use this plugin you need to sign up with Typekit, install this plugin and then either configure some Typekit selectors or define your own CSS rules. Typekit selectors provide a quick and easy way to get fonts enabled on your site. Using your own CSS rules (as explained in Typekit's Advanced tips) gives you more control and lets you access additional attributes such as font-weight. This plugin allows you to create your own CSS rules that use Typekit fonts without the need to edit/upload CSS style sheets.
|
17 |
+
|
18 |
+
Detailed instructions are available on the plugin's settings page.
|
19 |
|
20 |
Compatible with both WordPress and WordPress MU (WPMU).
|
21 |
|
50 |
|
51 |
== Changelog ==
|
52 |
|
53 |
+
= v1.0.2 =
|
54 |
+
* Add instructions on how to use Typekit Kit Editor selectors.
|
55 |
+
* Add instructions on how to use font weights / styles.
|
56 |
+
|
57 |
= v1.0.1 =
|
58 |
* WordPress 2.9 compatibility
|
59 |
* Improve FAQ
|
60 |
|
61 |
= v1.0.0 =
|
62 |
|
63 |
+
* Initial release.
|
typekit-admin.php
CHANGED
@@ -38,6 +38,7 @@ class OM4_Typekit_Admin {
|
|
38 |
.typekitsettings label { font-weight: bold; vertical-align: top; padding-right: 1em; }
|
39 |
.typekitsettings li p { margin: 1em 0em; }
|
40 |
.typekitsettings p code { margin: 0.5em; padding: 0.5em; display: block; }
|
|
|
41 |
.typekitsettings textarea { width: 90%; font-family: Courier, Fixed, monospace; }
|
42 |
.typekitsettings .indent { margin-left: 2em; }
|
43 |
</style>
|
@@ -71,7 +72,7 @@ class OM4_Typekit_Admin {
|
|
71 |
if (is_array($result) && $result['response']['code'] == 404) {
|
72 |
?>
|
73 |
<div id="error" class="error"><p>
|
74 |
-
<?php printf(__('Your Typekit embed code may be incorrect because <a href="%1$s" target="_blank">%1$s</a> does not exist. Please verify that your Typekit embed code is correct,
|
75 |
</p></div>
|
76 |
<?php
|
77 |
}
|
@@ -88,7 +89,7 @@ class OM4_Typekit_Admin {
|
|
88 |
?>
|
89 |
<form method="post">
|
90 |
<?php wp_nonce_field('om4-typekit-save-settings'); ?>
|
91 |
-
<h2><?php _e('Typekit Fonts for WordPress', 'om4-typekit'); ?></h2>
|
92 |
<p><?php _e('Typekit offer a service that allows you to select from a range of hundreds of high quality fonts for your WordPress website. The fonts are applied using the font-face standard, so they are standards compliant, fully licensed and accessible.', 'om4-typekit'); ?></p>
|
93 |
<p><?php _e('To use this plugin you need to sign up with Typekit, and then configure the following options.', 'om4-typekit'); ?></p>
|
94 |
<h3><?php _e('Register with Typekit', 'om4-typekit'); ?></h3>
|
@@ -103,7 +104,7 @@ class OM4_Typekit_Admin {
|
|
103 |
<p class="option"><label for="embedcode"><?php _e('Typekit Embed Code:', 'om4-typekit'); ?></label> <textarea name="embedcode" rows="3" cols="80" /><?php echo $this->typekitInstance->GetEmbedCode(); ?></textarea></p>
|
104 |
|
105 |
</li>
|
106 |
-
<li><?php _e('
|
107 |
<p class="option"><label for="css"><?php _e('Custom CSS Rules:', 'om4-typekit'); ?></label> <textarea name="css" rows="10" cols="80" /><?php echo $this->typekitInstance->GetCSSRules(); ?></textarea><br />
|
108 |
<a href="#help-css"><?php _e('Click here for help on CSS', 'om4-typekit'); ?></a>
|
109 |
</p>
|
@@ -120,15 +121,23 @@ class OM4_Typekit_Admin {
|
|
120 |
<li><?php _e('Have you <strong>added CSS rules</strong> to display your fonts? If in doubt, just try the H2 rule shown in the example and see if that works for you.', 'om4-typekit'); ?></li>
|
121 |
</ol>
|
122 |
<h4 id="help-css"><?php _e('CSS', 'om4-typekit'); ?></h4>
|
123 |
-
<p><?php _e('
|
124 |
<p><?php _e('There are many options for using CSS, but here are a few common scenarios. Note: we\'ve used proxima-nova for our examples, you\'ll need to change proxima-nova to the name of your chosen font from Typekit - your added font names will be visible in the Kit Editor.', 'om4-typekit'); ?></p>
|
|
|
125 |
<p>
|
126 |
-
<?php _e('
|
127 |
<code>h2 { font-family: "proxima-nova-1","proxima-nova-2",sans-serif; }</code>
|
128 |
<?php _e('(and you can add similar rules if you want to target other headings such as H3)', 'om4-typekit'); ?>
|
129 |
-
|
|
|
|
|
|
|
130 |
<code>#sidebar h2 { font-family: "proxima-nova-1","proxima-nova-2",sans-serif; }</code>
|
131 |
</p>
|
|
|
|
|
|
|
|
|
132 |
<h4 id="help-css-advanced"><?php _e('Advanced targetting of fonts with CSS selectors', 'om4-typekit'); ?></h4>
|
133 |
<p>
|
134 |
<?php _e('You can target your fonts to specific parts of your website if you know a bit more about your current WordPress theme and where the font family is specified. All WordPress themes have a style.css file, and if you know how to check that you should be able to see the selectors in use. Or you can install Chris Pederick\'s Web Developer Toolbar for Firefox and use the CSS, View CSS option to see all the CSS rules in use for your theme. When you find the selectors that are used for font-family, you can create a rule just for that selector to override that rule.', 'om4-typekit'); ?>
|
38 |
.typekitsettings label { font-weight: bold; vertical-align: top; padding-right: 1em; }
|
39 |
.typekitsettings li p { margin: 1em 0em; }
|
40 |
.typekitsettings p code { margin: 0.5em; padding: 0.5em; display: block; }
|
41 |
+
.typekitsettings code.inline { margin: 0; padding: 0.2em; display: inline; }
|
42 |
.typekitsettings textarea { width: 90%; font-family: Courier, Fixed, monospace; }
|
43 |
.typekitsettings .indent { margin-left: 2em; }
|
44 |
</style>
|
72 |
if (is_array($result) && $result['response']['code'] == 404) {
|
73 |
?>
|
74 |
<div id="error" class="error"><p>
|
75 |
+
<?php printf(__('Your Typekit embed code may be incorrect because <a href="%1$s" target="_blank">%1$s</a> does not exist. Please verify that your Typekit embed code is correct. If you have just published your kit, please try again in a few minutes.', 'om4-typekit'), $url); ?>
|
76 |
</p></div>
|
77 |
<?php
|
78 |
}
|
89 |
?>
|
90 |
<form method="post">
|
91 |
<?php wp_nonce_field('om4-typekit-save-settings'); ?>
|
92 |
+
<h2><?php _e('Typekit Fonts for WordPress Settings', 'om4-typekit'); ?></h2>
|
93 |
<p><?php _e('Typekit offer a service that allows you to select from a range of hundreds of high quality fonts for your WordPress website. The fonts are applied using the font-face standard, so they are standards compliant, fully licensed and accessible.', 'om4-typekit'); ?></p>
|
94 |
<p><?php _e('To use this plugin you need to sign up with Typekit, and then configure the following options.', 'om4-typekit'); ?></p>
|
95 |
<h3><?php _e('Register with Typekit', 'om4-typekit'); ?></h3>
|
104 |
<p class="option"><label for="embedcode"><?php _e('Typekit Embed Code:', 'om4-typekit'); ?></label> <textarea name="embedcode" rows="3" cols="80" /><?php echo $this->typekitInstance->GetEmbedCode(); ?></textarea></p>
|
105 |
|
106 |
</li>
|
107 |
+
<li><?php _e('You can add selectors using the Typekit Kit Editor. Alternatively you can define your own CSS rules in your own style sheet or using the Custom CSS Rules field below (technical note: these CSS rules will be embedded in the header of each page). Look at the advanced examples shown in the Typekit editor for ideas.', 'om4-typekit'); ?>
|
108 |
<p class="option"><label for="css"><?php _e('Custom CSS Rules:', 'om4-typekit'); ?></label> <textarea name="css" rows="10" cols="80" /><?php echo $this->typekitInstance->GetCSSRules(); ?></textarea><br />
|
109 |
<a href="#help-css"><?php _e('Click here for help on CSS', 'om4-typekit'); ?></a>
|
110 |
</p>
|
121 |
<li><?php _e('Have you <strong>added CSS rules</strong> to display your fonts? If in doubt, just try the H2 rule shown in the example and see if that works for you.', 'om4-typekit'); ?></li>
|
122 |
</ol>
|
123 |
<h4 id="help-css"><?php _e('CSS', 'om4-typekit'); ?></h4>
|
124 |
+
<p><?php _e('You can use CSS selectors to apply your new typekit fonts. The settings for this plugin allow you to add new CSS rules to your website to activate Typekit fonts. If you are using fonts for more than just a few elements, you may find it easier to manage this way. And using your own CSS rules is a good way to access different font weights.', 'om4-typekit'); ?></p>
|
125 |
<p><?php _e('There are many options for using CSS, but here are a few common scenarios. Note: we\'ve used proxima-nova for our examples, you\'ll need to change proxima-nova to the name of your chosen font from Typekit - your added font names will be visible in the Kit Editor.', 'om4-typekit'); ?></p>
|
126 |
+
<h5><?php _e('Headings'); ?></h5>
|
127 |
<p>
|
128 |
+
<?php _e('If you want your Typekit fonts to be used for H2 headings, add a rule like this to your CSS Rules field:', 'om4-typekit'); ?>
|
129 |
<code>h2 { font-family: "proxima-nova-1","proxima-nova-2",sans-serif; }</code>
|
130 |
<?php _e('(and you can add similar rules if you want to target other headings such as H3)', 'om4-typekit'); ?>
|
131 |
+
</p>
|
132 |
+
<h5><?php _e('Sidebar Headings'); ?></h5>
|
133 |
+
<p>
|
134 |
+
<?php _e('If you want your Typekit fonts to be used for sidebar H2 headings, add a rule like this to your CSS Rules field:', 'om4-typekit'); ?>
|
135 |
<code>#sidebar h2 { font-family: "proxima-nova-1","proxima-nova-2",sans-serif; }</code>
|
136 |
</p>
|
137 |
+
<h5><?php _e('Font Weights', 'om4-typekit'); ?></h5>
|
138 |
+
<p><?php _e('If your Kit contains more than one weight and/or style for a particular font, you need to use numeric <code class="inline">font-weight</code> values in your CSS rules to map to a font\'s weights.', 'om4-typekit'); ?></p>
|
139 |
+
<p><?php _e('Typekit fonts have been assigned values from 100 to 900 based on information from the font\'s designer. Web browsers also do some guessing as to which weight it should display if the specific value isn\'t present. Say your font has 100, 300 and 900. If you set your text with <code class="inline">font-weight: 400</code>, it will choose the most appropriate (300 in this case).<br />Note: A <code class="inline">font-weight</code> value of 400 corresponds to <code class="inline">font-weight: normal;</code>', 'om4-typekit'); ?></p>
|
140 |
+
<p><?php printf(__('See <a href="%s">this help article</a> for more details.', 'om4-typekit'), 'http://getsatisfaction.com/typekit/topics/how_do_i_use_alternate_weights_and_styles'); ?></p>
|
141 |
<h4 id="help-css-advanced"><?php _e('Advanced targetting of fonts with CSS selectors', 'om4-typekit'); ?></h4>
|
142 |
<p>
|
143 |
<?php _e('You can target your fonts to specific parts of your website if you know a bit more about your current WordPress theme and where the font family is specified. All WordPress themes have a style.css file, and if you know how to check that you should be able to see the selectors in use. Or you can install Chris Pederick\'s Web Developer Toolbar for Firefox and use the CSS, View CSS option to see all the CSS rules in use for your theme. When you find the selectors that are used for font-family, you can create a rule just for that selector to override that rule.', 'om4-typekit'); ?>
|
typekit-fonts-for-wordpress.pot
CHANGED
@@ -1,57 +1,59 @@
|
|
1 |
-
#
|
2 |
-
#
|
3 |
-
#
|
|
|
4 |
#
|
5 |
#, fuzzy
|
6 |
msgid ""
|
7 |
msgstr ""
|
8 |
-
"Project-Id-Version:
|
9 |
"Report-Msgid-Bugs-To: http://wordpress.org/tag/typekit-fonts-for-wordpress\n"
|
10 |
-
"POT-Creation-Date:
|
11 |
-
"PO-Revision-Date:
|
12 |
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
13 |
"Language-Team: LANGUAGE <LL@li.org>\n"
|
14 |
"MIME-Version: 1.0\n"
|
15 |
-
"Content-Type: text/plain; charset=
|
16 |
"Content-Transfer-Encoding: 8bit\n"
|
17 |
|
18 |
-
#: typekit-admin.php:
|
19 |
msgid "Typekit Fonts"
|
20 |
msgstr ""
|
21 |
|
22 |
-
#: typekit-admin.php:
|
23 |
msgid ""
|
24 |
" Please <a href=\"#getembedcode\">click here for instructions</a> on how to "
|
25 |
"obtain your Typekit embed code."
|
26 |
msgstr ""
|
27 |
|
28 |
-
#: typekit-admin.php:
|
29 |
#, php-format
|
30 |
msgid "Invalid Typekit embed code. %s"
|
31 |
msgstr ""
|
32 |
|
33 |
-
#: typekit-admin.php:
|
34 |
#, php-format
|
35 |
msgid "You must enter your Typekit embed code. %s"
|
36 |
msgstr ""
|
37 |
|
38 |
-
#: typekit-admin.php:
|
39 |
#, php-format
|
40 |
msgid ""
|
41 |
"Your Typekit embed code may be incorrect because <a href=\"%1$s\" target="
|
42 |
"\"_blank\">%1$s</a> does not exist. Please verify that your Typekit embed "
|
43 |
-
"code is correct,
|
|
|
44 |
msgstr ""
|
45 |
|
46 |
-
#: typekit-admin.php:
|
47 |
msgid "Settings saved."
|
48 |
msgstr ""
|
49 |
|
50 |
-
#: typekit-admin.php:
|
51 |
-
msgid "Typekit Fonts for WordPress"
|
52 |
msgstr ""
|
53 |
|
54 |
-
#: typekit-admin.php:
|
55 |
msgid ""
|
56 |
"Typekit offer a service that allows you to select from a range of hundreds "
|
57 |
"of high quality fonts for your WordPress website. The fonts are applied "
|
@@ -59,104 +61,106 @@ msgid ""
|
|
59 |
"licensed and accessible."
|
60 |
msgstr ""
|
61 |
|
62 |
-
#: typekit-admin.php:
|
63 |
msgid ""
|
64 |
"To use this plugin you need to sign up with Typekit, and then configure the "
|
65 |
"following options."
|
66 |
msgstr ""
|
67 |
|
68 |
-
#: typekit-admin.php:
|
69 |
msgid "Register with Typekit"
|
70 |
msgstr ""
|
71 |
|
72 |
-
#: typekit-admin.php:
|
73 |
msgid ""
|
74 |
"Go to <a href=\"http://typekit.com\" target=\"blank\">typekit.com</a> and "
|
75 |
"register for an account"
|
76 |
msgstr ""
|
77 |
|
78 |
-
#: typekit-admin.php:
|
79 |
msgid "Choose a few fonts to add to your account and Publish them"
|
80 |
msgstr ""
|
81 |
|
82 |
-
#: typekit-admin.php:
|
83 |
msgid ""
|
84 |
"Go to the Kit Editor and get your Embed Code (link at the top right of the "
|
85 |
"screen)"
|
86 |
msgstr ""
|
87 |
|
88 |
-
#: typekit-admin.php:
|
89 |
msgid "Plugin Configuration"
|
90 |
msgstr ""
|
91 |
|
92 |
-
#: typekit-admin.php:
|
93 |
msgid "Enter the whole 2 lines of your embed code into the box below:"
|
94 |
msgstr ""
|
95 |
|
96 |
-
#: typekit-admin.php:
|
97 |
msgid "Typekit Embed Code:"
|
98 |
msgstr ""
|
99 |
|
100 |
-
#: typekit-admin.php:
|
101 |
msgid ""
|
102 |
-
"
|
103 |
-
"your own CSS
|
104 |
-
"
|
105 |
-
"
|
106 |
-
"
|
107 |
msgstr ""
|
108 |
|
109 |
-
#: typekit-admin.php:
|
110 |
msgid "Custom CSS Rules:"
|
111 |
msgstr ""
|
112 |
|
113 |
-
#: typekit-admin.php:
|
114 |
msgid "Click here for help on CSS"
|
115 |
msgstr ""
|
116 |
|
117 |
-
#: typekit-admin.php:
|
118 |
msgid "Save Settings"
|
119 |
msgstr ""
|
120 |
|
121 |
-
#: typekit-admin.php:
|
122 |
msgid "Help"
|
123 |
msgstr ""
|
124 |
|
125 |
-
#: typekit-admin.php:
|
126 |
msgid "Fonts not showing?"
|
127 |
msgstr ""
|
128 |
|
129 |
-
#: typekit-admin.php:
|
130 |
msgid ""
|
131 |
"Have you created your Typekit account, added fonts to it and <strong>pressed "
|
132 |
"Publish</strong>? Fonts aren't available until they are published."
|
133 |
msgstr ""
|
134 |
|
135 |
-
#: typekit-admin.php:
|
136 |
msgid ""
|
137 |
"Have you <strong>waited a few minutes</strong> to allow Typekit time to send "
|
138 |
"your fonts out around the world? Grab a cup of coffee and try again soon."
|
139 |
msgstr ""
|
140 |
|
141 |
-
#: typekit-admin.php:
|
142 |
msgid ""
|
143 |
"Have you <strong>added CSS rules</strong> to display your fonts? If in "
|
144 |
"doubt, just try the H2 rule shown in the example and see if that works for "
|
145 |
"you."
|
146 |
msgstr ""
|
147 |
|
148 |
-
#: typekit-admin.php:
|
149 |
msgid "CSS"
|
150 |
msgstr ""
|
151 |
|
152 |
-
#: typekit-admin.php:
|
153 |
msgid ""
|
154 |
-
"
|
155 |
-
"
|
156 |
-
"
|
|
|
|
|
157 |
msgstr ""
|
158 |
|
159 |
-
#: typekit-admin.php:
|
160 |
msgid ""
|
161 |
"There are many options for using CSS, but here are a few common scenarios. "
|
162 |
"Note: we've used proxima-nova for our examples, you'll need to change "
|
@@ -164,29 +168,64 @@ msgid ""
|
|
164 |
"names will be visible in the Kit Editor."
|
165 |
msgstr ""
|
166 |
|
167 |
-
#: typekit-admin.php:
|
|
|
|
|
|
|
|
|
168 |
msgid ""
|
169 |
-
"
|
170 |
-
"
|
171 |
msgstr ""
|
172 |
|
173 |
-
#: typekit-admin.php:
|
174 |
msgid ""
|
175 |
"(and you can add similar rules if you want to target other headings such as "
|
176 |
"H3)"
|
177 |
msgstr ""
|
178 |
|
179 |
-
#: typekit-admin.php:
|
|
|
|
|
|
|
|
|
180 |
msgid ""
|
181 |
-
"
|
182 |
-
"
|
|
|
|
|
|
|
|
|
183 |
msgstr ""
|
184 |
|
185 |
#: typekit-admin.php:138
|
186 |
-
msgid "
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
187 |
msgstr ""
|
188 |
|
189 |
#: typekit-admin.php:140
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
190 |
msgid ""
|
191 |
"You can target your fonts to specific parts of your website if you know a "
|
192 |
"bit more about your current WordPress theme and where the font family is "
|
@@ -198,33 +237,33 @@ msgid ""
|
|
198 |
"for that selector to override that rule."
|
199 |
msgstr ""
|
200 |
|
201 |
-
#: typekit-admin.php:
|
202 |
msgid "For example, if your theme has this CSS rule:"
|
203 |
msgstr ""
|
204 |
|
205 |
-
#: typekit-admin.php:
|
206 |
msgid ""
|
207 |
"you could create this rule to apply your new font to the body of your "
|
208 |
"website:"
|
209 |
msgstr ""
|
210 |
|
211 |
-
#: typekit-admin.php:
|
212 |
msgid "Where to go to get help"
|
213 |
msgstr ""
|
214 |
|
215 |
-
#: typekit-admin.php:
|
216 |
msgid ""
|
217 |
"<a href=\"http://getsatisfaction.com/typekit/\" target=\"_blank\">Typekit "
|
218 |
"Support</a>"
|
219 |
msgstr ""
|
220 |
|
221 |
-
#: typekit-admin.php:
|
222 |
msgid ""
|
223 |
"<a href=\"http://www.sitepoint.com/forums/forumdisplay.php?f=53\" target="
|
224 |
"\"_blank\">Sitepoint CSS Forums</a>"
|
225 |
msgstr ""
|
226 |
|
227 |
-
#: typekit-admin.php:
|
228 |
msgid ""
|
229 |
"<a href=\"http://www.w3schools.com/CSS/default.asp\" target=\"_blank"
|
230 |
"\">W3Schools CSS Help</a>"
|
1 |
+
# Translation of the WordPress plugin by .
|
2 |
+
# Copyright (C) 2010
|
3 |
+
# This file is distributed under the same license as the package.
|
4 |
+
# FIRST AUTHOR <EMAIL@ADDRESS>, 2010.
|
5 |
#
|
6 |
#, fuzzy
|
7 |
msgid ""
|
8 |
msgstr ""
|
9 |
+
"Project-Id-Version: \n"
|
10 |
"Report-Msgid-Bugs-To: http://wordpress.org/tag/typekit-fonts-for-wordpress\n"
|
11 |
+
"POT-Creation-Date: 2010-01-15 03:24+0000\n"
|
12 |
+
"PO-Revision-Date: 2010-MO-DA HO:MI+ZONE\n"
|
13 |
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
14 |
"Language-Team: LANGUAGE <LL@li.org>\n"
|
15 |
"MIME-Version: 1.0\n"
|
16 |
+
"Content-Type: text/plain; charset=utf-8\n"
|
17 |
"Content-Transfer-Encoding: 8bit\n"
|
18 |
|
19 |
+
#: typekit-admin.php:28
|
20 |
msgid "Typekit Fonts"
|
21 |
msgstr ""
|
22 |
|
23 |
+
#: typekit-admin.php:57
|
24 |
msgid ""
|
25 |
" Please <a href=\"#getembedcode\">click here for instructions</a> on how to "
|
26 |
"obtain your Typekit embed code."
|
27 |
msgstr ""
|
28 |
|
29 |
+
#: typekit-admin.php:60
|
30 |
#, php-format
|
31 |
msgid "Invalid Typekit embed code. %s"
|
32 |
msgstr ""
|
33 |
|
34 |
+
#: typekit-admin.php:63
|
35 |
#, php-format
|
36 |
msgid "You must enter your Typekit embed code. %s"
|
37 |
msgstr ""
|
38 |
|
39 |
+
#: typekit-admin.php:75
|
40 |
#, php-format
|
41 |
msgid ""
|
42 |
"Your Typekit embed code may be incorrect because <a href=\"%1$s\" target="
|
43 |
"\"_blank\">%1$s</a> does not exist. Please verify that your Typekit embed "
|
44 |
+
"code is correct. If you have just published your kit, please try again in a "
|
45 |
+
"few minutes."
|
46 |
msgstr ""
|
47 |
|
48 |
+
#: typekit-admin.php:86
|
49 |
msgid "Settings saved."
|
50 |
msgstr ""
|
51 |
|
52 |
+
#: typekit-admin.php:92
|
53 |
+
msgid "Typekit Fonts for WordPress Settings"
|
54 |
msgstr ""
|
55 |
|
56 |
+
#: typekit-admin.php:93
|
57 |
msgid ""
|
58 |
"Typekit offer a service that allows you to select from a range of hundreds "
|
59 |
"of high quality fonts for your WordPress website. The fonts are applied "
|
61 |
"licensed and accessible."
|
62 |
msgstr ""
|
63 |
|
64 |
+
#: typekit-admin.php:94
|
65 |
msgid ""
|
66 |
"To use this plugin you need to sign up with Typekit, and then configure the "
|
67 |
"following options."
|
68 |
msgstr ""
|
69 |
|
70 |
+
#: typekit-admin.php:95
|
71 |
msgid "Register with Typekit"
|
72 |
msgstr ""
|
73 |
|
74 |
+
#: typekit-admin.php:97
|
75 |
msgid ""
|
76 |
"Go to <a href=\"http://typekit.com\" target=\"blank\">typekit.com</a> and "
|
77 |
"register for an account"
|
78 |
msgstr ""
|
79 |
|
80 |
+
#: typekit-admin.php:98
|
81 |
msgid "Choose a few fonts to add to your account and Publish them"
|
82 |
msgstr ""
|
83 |
|
84 |
+
#: typekit-admin.php:99
|
85 |
msgid ""
|
86 |
"Go to the Kit Editor and get your Embed Code (link at the top right of the "
|
87 |
"screen)"
|
88 |
msgstr ""
|
89 |
|
90 |
+
#: typekit-admin.php:101
|
91 |
msgid "Plugin Configuration"
|
92 |
msgstr ""
|
93 |
|
94 |
+
#: typekit-admin.php:103
|
95 |
msgid "Enter the whole 2 lines of your embed code into the box below:"
|
96 |
msgstr ""
|
97 |
|
98 |
+
#: typekit-admin.php:104
|
99 |
msgid "Typekit Embed Code:"
|
100 |
msgstr ""
|
101 |
|
102 |
+
#: typekit-admin.php:107
|
103 |
msgid ""
|
104 |
+
"You can add selectors using the Typekit Kit Editor. Alternatively you can "
|
105 |
+
"define your own CSS rules in your own style sheet or using the Custom CSS "
|
106 |
+
"Rules field below (technical note: these CSS rules will be embedded in the "
|
107 |
+
"header of each page). Look at the advanced examples shown in the Typekit "
|
108 |
+
"editor for ideas."
|
109 |
msgstr ""
|
110 |
|
111 |
+
#: typekit-admin.php:108
|
112 |
msgid "Custom CSS Rules:"
|
113 |
msgstr ""
|
114 |
|
115 |
+
#: typekit-admin.php:109
|
116 |
msgid "Click here for help on CSS"
|
117 |
msgstr ""
|
118 |
|
119 |
+
#: typekit-admin.php:114
|
120 |
msgid "Save Settings"
|
121 |
msgstr ""
|
122 |
|
123 |
+
#: typekit-admin.php:116
|
124 |
msgid "Help"
|
125 |
msgstr ""
|
126 |
|
127 |
+
#: typekit-admin.php:117
|
128 |
msgid "Fonts not showing?"
|
129 |
msgstr ""
|
130 |
|
131 |
+
#: typekit-admin.php:119
|
132 |
msgid ""
|
133 |
"Have you created your Typekit account, added fonts to it and <strong>pressed "
|
134 |
"Publish</strong>? Fonts aren't available until they are published."
|
135 |
msgstr ""
|
136 |
|
137 |
+
#: typekit-admin.php:120
|
138 |
msgid ""
|
139 |
"Have you <strong>waited a few minutes</strong> to allow Typekit time to send "
|
140 |
"your fonts out around the world? Grab a cup of coffee and try again soon."
|
141 |
msgstr ""
|
142 |
|
143 |
+
#: typekit-admin.php:121
|
144 |
msgid ""
|
145 |
"Have you <strong>added CSS rules</strong> to display your fonts? If in "
|
146 |
"doubt, just try the H2 rule shown in the example and see if that works for "
|
147 |
"you."
|
148 |
msgstr ""
|
149 |
|
150 |
+
#: typekit-admin.php:123
|
151 |
msgid "CSS"
|
152 |
msgstr ""
|
153 |
|
154 |
+
#: typekit-admin.php:124
|
155 |
msgid ""
|
156 |
+
"You can use CSS selectors to apply your new typekit fonts. The settings for "
|
157 |
+
"this plugin allow you to add new CSS rules to your website to activate "
|
158 |
+
"Typekit fonts. If you are using fonts for more than just a few elements, you "
|
159 |
+
"may find it easier to manage this way. And using your own CSS rules is a "
|
160 |
+
"good way to access different font weights."
|
161 |
msgstr ""
|
162 |
|
163 |
+
#: typekit-admin.php:125
|
164 |
msgid ""
|
165 |
"There are many options for using CSS, but here are a few common scenarios. "
|
166 |
"Note: we've used proxima-nova for our examples, you'll need to change "
|
168 |
"names will be visible in the Kit Editor."
|
169 |
msgstr ""
|
170 |
|
171 |
+
#: typekit-admin.php:126
|
172 |
+
msgid "Headings"
|
173 |
+
msgstr ""
|
174 |
+
|
175 |
+
#: typekit-admin.php:128
|
176 |
msgid ""
|
177 |
+
"If you want your Typekit fonts to be used for H2 headings, add a rule like "
|
178 |
+
"this to your CSS Rules field:"
|
179 |
msgstr ""
|
180 |
|
181 |
+
#: typekit-admin.php:130
|
182 |
msgid ""
|
183 |
"(and you can add similar rules if you want to target other headings such as "
|
184 |
"H3)"
|
185 |
msgstr ""
|
186 |
|
187 |
+
#: typekit-admin.php:132
|
188 |
+
msgid "Sidebar Headings"
|
189 |
+
msgstr ""
|
190 |
+
|
191 |
+
#: typekit-admin.php:134
|
192 |
msgid ""
|
193 |
+
"If you want your Typekit fonts to be used for sidebar H2 headings, add a "
|
194 |
+
"rule like this to your CSS Rules field:"
|
195 |
+
msgstr ""
|
196 |
+
|
197 |
+
#: typekit-admin.php:137
|
198 |
+
msgid "Font Weights"
|
199 |
msgstr ""
|
200 |
|
201 |
#: typekit-admin.php:138
|
202 |
+
msgid ""
|
203 |
+
"If your Kit contains more than one weight and/or style for a particular "
|
204 |
+
"font, you need to use numeric <code class=\"inline\">font-weight</code> "
|
205 |
+
"values in your CSS rules to map to a font's weights."
|
206 |
+
msgstr ""
|
207 |
+
|
208 |
+
#: typekit-admin.php:139
|
209 |
+
msgid ""
|
210 |
+
"Typekit fonts have been assigned values from 100 to 900 based on information "
|
211 |
+
"from the font's designer. Web browsers also do some guessing as to which "
|
212 |
+
"weight it should display if the specific value isn't present. Say your font "
|
213 |
+
"has 100, 300 and 900. If you set your text with <code class=\"inline\">font-"
|
214 |
+
"weight: 400</code>, it will choose the most appropriate (300 in this case)."
|
215 |
+
"<br />Note: A <code class=\"inline\">font-weight</code> value of 400 "
|
216 |
+
"corresponds to <code class=\"inline\">font-weight: normal;</code>"
|
217 |
msgstr ""
|
218 |
|
219 |
#: typekit-admin.php:140
|
220 |
+
#, php-format
|
221 |
+
msgid "See <a href=\"%s\">this help article</a> for more details."
|
222 |
+
msgstr ""
|
223 |
+
|
224 |
+
#: typekit-admin.php:141
|
225 |
+
msgid "Advanced targetting of fonts with CSS selectors"
|
226 |
+
msgstr ""
|
227 |
+
|
228 |
+
#: typekit-admin.php:143
|
229 |
msgid ""
|
230 |
"You can target your fonts to specific parts of your website if you know a "
|
231 |
"bit more about your current WordPress theme and where the font family is "
|
237 |
"for that selector to override that rule."
|
238 |
msgstr ""
|
239 |
|
240 |
+
#: typekit-admin.php:144
|
241 |
msgid "For example, if your theme has this CSS rule:"
|
242 |
msgstr ""
|
243 |
|
244 |
+
#: typekit-admin.php:146
|
245 |
msgid ""
|
246 |
"you could create this rule to apply your new font to the body of your "
|
247 |
"website:"
|
248 |
msgstr ""
|
249 |
|
250 |
+
#: typekit-admin.php:149
|
251 |
msgid "Where to go to get help"
|
252 |
msgstr ""
|
253 |
|
254 |
+
#: typekit-admin.php:151
|
255 |
msgid ""
|
256 |
"<a href=\"http://getsatisfaction.com/typekit/\" target=\"_blank\">Typekit "
|
257 |
"Support</a>"
|
258 |
msgstr ""
|
259 |
|
260 |
+
#: typekit-admin.php:152
|
261 |
msgid ""
|
262 |
"<a href=\"http://www.sitepoint.com/forums/forumdisplay.php?f=53\" target="
|
263 |
"\"_blank\">Sitepoint CSS Forums</a>"
|
264 |
msgstr ""
|
265 |
|
266 |
+
#: typekit-admin.php:153
|
267 |
msgid ""
|
268 |
"<a href=\"http://www.w3schools.com/CSS/default.asp\" target=\"_blank"
|
269 |
"\">W3Schools CSS Help</a>"
|
typekit.php
CHANGED
@@ -3,13 +3,13 @@
|
|
3 |
Plugin Name: Typekit Fonts for WordPress
|
4 |
Plugin URI: http://om4.com.au/wordpress-plugins/typekit-fonts-for-wordpress-plugin/
|
5 |
Description: Use a range of hundreds of high quality fonts on your WordPress website by integrating the <a href="http://typekit.com">Typekit</a> font service into your WordPress blog.
|
6 |
-
Version: 1.0.
|
7 |
Author: OM4
|
8 |
Author URI: http://om4.com.au/
|
9 |
Text Domain: om4-typekit
|
10 |
*/
|
11 |
|
12 |
-
/* Copyright 2009 OM4 (email : info@om4.com.au)
|
13 |
|
14 |
This program is free software; you can redistribute it and/or modify
|
15 |
it under the terms of the GNU General Public License as published by
|
3 |
Plugin Name: Typekit Fonts for WordPress
|
4 |
Plugin URI: http://om4.com.au/wordpress-plugins/typekit-fonts-for-wordpress-plugin/
|
5 |
Description: Use a range of hundreds of high quality fonts on your WordPress website by integrating the <a href="http://typekit.com">Typekit</a> font service into your WordPress blog.
|
6 |
+
Version: 1.0.2
|
7 |
Author: OM4
|
8 |
Author URI: http://om4.com.au/
|
9 |
Text Domain: om4-typekit
|
10 |
*/
|
11 |
|
12 |
+
/* Copyright 2009-2010 OM4 (email : info@om4.com.au)
|
13 |
|
14 |
This program is free software; you can redistribute it and/or modify
|
15 |
it under the terms of the GNU General Public License as published by
|