New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | WP Forum is an custom extention plugin to wordpress admin comments forum to haved a good looking dashboard. | You have to log in to add a translation. | Details |
Original untranslated
WP Forum is an custom extention plugin to wordpress admin comments forum to haved a good looking dashboard.
You have to log in to edit this translation. |
|||
| screenshoot-3 /assets - ( wp-forum ) settings option - user roles options actions for view control attribute . | You have to log in to add a translation. | Details | |
Original untranslated
screenshoot-3 /assets - ( wp-forum ) settings option - user roles options actions for view control attribute .
CommentScreenshot description. You have to log in to edit this translation. |
|||
| screenshoot-2 /assets - ( wp-forum ) manager page ( 50% ) screen dimension . | You have to log in to add a translation. | Details | |
Original untranslated
screenshoot-2 /assets - ( wp-forum ) manager page ( 50% ) screen dimension .
CommentScreenshot description. You have to log in to edit this translation. |
|||
| screenshoot-1 /assets - ( wp-forum ) manager page ( 100% ) screen dimension . | You have to log in to add a translation. | Details | |
Original untranslated
screenshoot-1 /assets - ( wp-forum ) manager page ( 100% ) screen dimension .
CommentScreenshot description. You have to log in to edit this translation. |
|||
| Asterisks for <em>emphasis</em>. Double it up for <strong>strong</strong>. | You have to log in to add a translation. | Details | |
Original untranslated
Asterisks for <em>emphasis</em>. Double it up for <strong>strong</strong>.
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| Markdown uses email style notation for blockquotes and I've been told: | You have to log in to add a translation. | Details | |
Original untranslated
Markdown uses email style notation for blockquotes and I've been told:
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| Here's a link to <a href="http://wordpress.org/" title="Your favorite software">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file">Markdown's Syntax Documentation</a>.↵ Titles are optional, naturally. | You have to log in to add a translation. | Details | |
Original untranslated
Here's a link to <a href="http://wordpress.org/" title="Your favorite software">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file">Markdown's Syntax Documentation</a>.↵
Titles are optional, naturally.
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated↵ plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or↵ "installation." Arbitrary sections will be shown below the built-in sections outlined above. | You have to log in to add a translation. | Details | |
Original untranslated
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated↵
plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or↵
"installation." Arbitrary sections will be shown below the built-in sections outlined above.
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| Place <code><?php do_action('plugin_name_hook'); ?></code> in your templates | You have to log in to add a translation. | Details | |
Original untranslated
Place <code><?php do_action('plugin_name_hook'); ?></code> in your templates
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Upload <code>plugin-name.php</code> to the <code>/wp-content/plugins/</code> directory | You have to log in to add a translation. | Details | |
Original untranslated
Upload <code>plugin-name.php</code> to the <code>/wp-content/plugins/</code> directory
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where↵ you put the stable version, in order to eliminate any doubt. | You have to log in to add a translation. | Details | |
Original untranslated
If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where↵
you put the stable version, in order to eliminate any doubt.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so↵ if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that'll be used↵ for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code>↵ is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in↵ your in-development version, without having that information incorrectly disclosed about the current stable version↵ that lacks those changes -- as long as the trunk's <code>readme.txt</code> points to the correct stable tag. | You have to log in to add a translation. | Details | |
Original untranslated
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so↵
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that'll be used↵
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code>↵
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in↵
your in-development version, without having that information incorrectly disclosed about the current stable version↵
that lacks those changes -- as long as the trunk's <code>readme.txt</code> points to the correct stable tag.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use <code>/trunk/</code> for↵ stable. | You have to log in to add a translation. | Details | |
Original untranslated
Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use <code>/trunk/</code> for↵
stable.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| <p>Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use <code>/trunk/</code> for↵ stable.</p>↵ ↵ <p>Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so↵ if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that'll be used↵ for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code>↵ is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in↵ your in-development version, without having that information incorrectly disclosed about the current stable version↵ that lacks those changes -- as long as the trunk's <code>readme.txt</code> points to the correct stable tag.</p>↵ ↵ <p>If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where↵ you put the stable version, in order to eliminate any doubt.</p> | You have to log in to add a translation. | Details | |
Original untranslated
<p>Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use <code>/trunk/</code> for↵
stable.</p>↵
↵
<p>Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so↵
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that'll be used↵
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code>↵
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in↵
your in-development version, without having that information incorrectly disclosed about the current stable version↵
that lacks those changes -- as long as the trunk's <code>readme.txt</code> points to the correct stable tag.</p>↵
↵
<p>If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where↵
you put the stable version, in order to eliminate any doubt.</p>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| "Tested up to" is the highest version that you've <em>successfully used to test the plugin</em>. Note that it might work on↵ higher versions... this is just the highest one you've verified. | You have to log in to add a translation. | Details | |
Original untranslated
"Tested up to" is the highest version that you've <em>successfully used to test the plugin</em>. Note that it might work on↵
higher versions... this is just the highest one you've verified.
CommentFound in description list item. You have to log in to edit this translation. |
|||
Export as
Comment
Found in description paragraph.