WordPress.org

New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Development Readme (trunk): Spanish (Peru)

1 2 3 13
Filter ↓ Sort ↓ All (183) Untranslated (183) Waiting (0) Fuzzy (0) Warnings (0)
Prio Original string Translation
Provides a WordPress interface for SWFObject 2, the best way to embed Flash content on any site. You have to log in to add a translation. Details

Original untranslated

Provides a WordPress interface for SWFObject 2, the best way to embed Flash content on any site.
Comment

Short description.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
high
Kimili Flash Embed You have to log in to add a translation. Details

Original untranslated

Kimili Flash Embed
Comment

Name.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
high
One other minor backwards compatibility issue for you has to do with the format of KFE tags. In very early versions of this plugin, you defined KFE tags using angle brackets - <code>&lt;kml_flashembed ... /&gt;</code>. When problems arose with using angle bracket tags in Wordpress' Rich Text Editor, I introduced the familiar square bracket variety - <code>[kml_flashembed ... /]</code>. Up to and including KFE 1.4.3, both versions of the tag formatting were supported. However, in order to simplify things in the KFE 2.0 code, the old angle bracket tags are no longer supported. If you have any posts which use the old formatting, you'll have to go back and update them to square brackets in order to continue rendering those Flash movies correctly. You have to log in to add a translation. Details

Original untranslated

One other minor backwards compatibility issue for you has to do with the format of KFE tags. In very early versions of this plugin, you defined KFE tags using angle brackets - <code>&lt;kml_flashembed ... /&gt;</code>. When problems arose with using angle bracket tags in Wordpress' Rich Text Editor, I introduced the familiar square bracket variety - <code>[kml_flashembed ... /]</code>. Up to and including KFE 1.4.3, both versions of the tag formatting were supported. However, in order to simplify things in the KFE 2.0 code, the old angle bracket tags are no longer supported. If you have any posts which use the old formatting, you'll have to go back and update them to square brackets in order to continue rendering those Flash movies correctly.
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
KFE 2.0 is <em>mostly</em> backwards compatible with KFE 1.x, so if you've been using the 1.x version and just creating basic KFE tags, you should be able to upgrade with no issues whatsoever. There are, however, some attributes which were available in 1.x which are no longer available in 2.0. This is due primarily to changes in SWFObject itself when it went to 2.0, unless otherwise noted. The 1.x attributes which are no longer supported are: You have to log in to add a translation. Details

Original untranslated

KFE 2.0 is <em>mostly</em> backwards compatible with KFE 1.x, so if you've been using the 1.x version and just creating basic KFE tags, you should be able to upgrade with no issues whatsoever. There are, however, some attributes which were available in 1.x which are no longer available in 2.0. This is due primarily to changes in SWFObject itself when it went to 2.0, unless otherwise noted. The 1.x attributes which are no longer supported are:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
KFE 2.1 features configuration options which allow you to customize how the plugin behaves as well as set all defaults for the Tag Generator and KFE tags that omit some parameters. In Wordpress, you can find the options by navigating to <em>Settings &rarr; Kimili Flash Embed</em>. Unless otherwise noted, the default tag generator values will be blank or unselected. You'll find the following options available to you: You have to log in to add a translation. Details

Original untranslated

KFE 2.1 features configuration options which allow you to customize how the plugin behaves as well as set all defaults for the Tag Generator and KFE tags that omit some parameters. In Wordpress, you can find the options by navigating to <em>Settings &rarr; Kimili Flash Embed</em>. Unless otherwise noted, the default tag generator values will be blank or unselected. You'll find the following options available to you:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
To define alternative content for a SWF, you can now nest arbitrary HTML inside a KFE tag and it will be treated as alternate content for that SWF. The Tag Generator does this for you automatically. Properly nested alternative content looks like this: You have to log in to add a translation. Details

Original untranslated

To define alternative content for a SWF, you can now nest arbitrary HTML inside a KFE tag and it will be treated as alternate content for that SWF. The Tag Generator does this for you automatically. Properly nested alternative content looks like this:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
As of KFE 2.0, it is now <em>much</em> easier to specify alternative content which gets displayed when your Flash doesn't get rendered. This could happen if a user doesn't have a recent enough Flash player installed or lacks the Flash player altogether, such as on an iPhone. Another reason to specify alternative content is for search engine optimization, or SEO. Most search engines aren't very good at indexing content in Flash movies, if they can do it at all (Google can, but only with content that has been hard coded into a SWF--dynamic content in a SWF doesn't get indexed). In these cases it's best to specify some alternative content for your SWF. You have to log in to add a translation. Details

Original untranslated

As of KFE 2.0, it is now <em>much</em> easier to specify alternative content which gets displayed when your Flash doesn't get rendered. This could happen if a user doesn't have a recent enough Flash player installed or lacks the Flash player altogether, such as on an iPhone. Another reason to specify alternative content is for search engine optimization, or SEO. Most search engines aren't very good at indexing content in Flash movies, if they can do it at all (Google can, but only with content that has been hard coded into a SWF--dynamic content in a SWF doesn't get indexed). In these cases it's best to specify some alternative content for your SWF.
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
That is all you need in order to invoke the Express Install functionality. In the case of the above KFE tag, if a user arrives at your site with either a Flash Player 6, 7, or 8 installed, they will be alerted that they need a more recent version of the Flash Player and be given the option to upgrade it without leaving your site. You have to log in to add a translation. Details

Original untranslated

That is all you need in order to invoke the Express Install functionality. In the case of the above KFE tag, if a user arrives at your site with either a Flash Player 6, 7, or 8 installed, they will be alerted that they need a more recent version of the Flash Player and be given the option to upgrade it without leaving your site.
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
<code>[kml_flashembed movie="filename.swf" height="300" width="300" fversion="9" useexpressinstall="true" /]</code> You have to log in to add a translation. Details

Original untranslated

<code>[kml_flashembed movie="filename.swf" height="300" width="300" fversion="9" useexpressinstall="true" /]</code>
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
In the end, your KFE tag should look something like this: You have to log in to add a translation. Details

Original untranslated

In the end, your KFE tag should look something like this:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
<code>useexpressinstall="true"</code> You have to log in to add a translation. Details

Original untranslated

<code>useexpressinstall="true"</code>
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
Add the useexpressinstall attribute to your <code>[kml_flashembed /]</code> tag, like this: You have to log in to add a translation. Details

Original untranslated

Add the useexpressinstall attribute to your <code>[kml_flashembed /]</code> tag, like this:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
<code>fversion="9.0.115"</code> You have to log in to add a translation. Details

Original untranslated

<code>fversion="9.0.115"</code>
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
Define the minimum flash player version required by your .SWF using the fversion attribute: You have to log in to add a translation. Details

Original untranslated

Define the minimum flash player version required by your .SWF using the fversion attribute:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
It may also be a good idea to only place one SWF with Express Install functionality on each page. This way users won’t be greeted with multiple upgrade dialog boxes and be forced to choose one. Onto the specifics: You have to log in to add a translation. Details

Original untranslated

It may also be a good idea to only place one SWF with Express Install functionality on each page. This way users won’t be greeted with multiple upgrade dialog boxes and be forced to choose one. Onto the specifics:
Comment

Found in remaining content paragraph.

You have to log in to edit this translation.

Meta

Status:
untranslated
Priority of the original:
normal
1 2 3 13
Legend:
Current
Waiting
Fuzzy
Old
With Warnings

Export as

Skip to toolbar