Marcin Kazmierski

<h4>What is “Theme and plugin translation for Polylang”?</h4>
Extension for Polylang plugin (Polylang is an extension to make multilingual WordPress websites.). 
Plugin is needed to translate the WordPress themes and plugins by Polylang.
<h4>How to configure it?</h4>
Select themes and plugins to find texts for translation by Polylang. 
In admin dashboard:
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>How it is work?</h4>
“Theme and plugin translation for Polylang” automatically searches all files of WordPress themes and plugins. It chooses from this file only those files with extensions:
<ul>
<li>php</li>
<li>inc</li>
<li>twig</li>
</ul>
In addition, is implemented the integration with Timber library (read more: http://timber.upstatement.com) – which allows to translate twig’s skins in simple way. 
Plugin in searched skins or plugins chooses texts from Polylang functions, such as:
<ul>
<li>_e(string $text, string $domain = ‘default’);</li>
<li>__(string $text, string $domain = ‘default’);</li>
<li>_x(string $text, string $context, string $domain = ‘default’);</li>
<li>pll_e(string $text);</li>
<li>pll__(string $text);</li>
<li>esc_html(string $text);</li>
<li>esc_html_e(string $text, string $domain = ‘default’);</li>
<li>esc_html__(string $text, string $domain = ‘default’);</li>
<li>_n(string $single, string $plural, int $number, string $domain = ‘default’);</li>
<li>esc_attr_e(string $text, string $domain = ‘default’);</li>
<li>esc_attr__(string $text, string $domain = ‘default’);</li>
</ul>
In your function.php, themes or plugins.
For example:
<pre><code><?php pll_e('My text'); ?>

<?php _e('My another text', 'my_theme'); ?>
</code></pre>
On the timber context declare this functions like:
<pre><code>$context['pll_e'] = TimberHelper::function_wrapper('pll_e');

$context['pll_'] = TimberHelper::function_wrapper('pll_');
</code></pre>
See more on: <code>https://polylang.wordpress.com/documentation/documentation-for-developers/functions-reference/</code> 
These functions are defined by Polylang plugin for printing translations. 
Thanks “Theme and plugin translation for Polylang” you can find these strings to translate and add to Polylang register on very simple way. 
And then you can translate these texts from the admin dashboard. 
The scan result can be seen on the tab with translations:
<pre><code>Settings -> Languages -> String translation
</code></pre>
or
<pre><code>Languages -> String translation
</code></pre>
You don’t need programs like poedit – you don’t change files with extensions like: <code>.pot</code>, <code>.po</code>, <code>.mo</code>. 
“Theme and plugin translation for Polylang” is highly efficient because the scanner is worked only on admin dashboard in tab: 
In dashboard:
<pre><code>Settings -> Languages -> String translation
</code></pre>
or
<pre><code>Languages -> String translation
</code></pre>
<h4>Export and import string translation</h4>
In dashboard:
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>Filter reference</h4>
<pre><code>ttfp_domains
</code></pre>
Allows plugins and themes (in functions.php) to modify list of text domains (unique identifier for retrieving translated strings). 
List of text domains is displayed on “TTfP Settings” page to select them for translation by polylang engine.
Example:
<pre><code>add_filter('ttfp_domains', 'custom_ttfp_domains', 10, 1);
function custom_ttfp_domains(array $domains):array
 {
 $domains[] = "my-custom-domain";
 return $domains;
 }
</code></pre>
<h4>Filter reference</h4>
<pre><code>ttfp_translation_access
</code></pre>
Returns whether the user has capability to view and edit translations provided by TTfP.
Example:
<pre><code>add_filter('ttfp_translation_access', 'custom_ttfp_translation_access', 10, 1);
function custom_ttfp_translation_access(bool $hasAccess):bool
 {
 return current_user_can('edit_posts');
 }
</code></pre>

Theme and plugin translation for Polylang (TTfP)


Great plugin and DEV, nothing more to say.


Great plugin and DEV


Works perfectly and very simple to use!


Works perfectly!

Theme and plugin translation using Polylang for WordPress. Extension for Polylang plugin.

theode

Did you ever struggle with more than one language on a WordPress blog? 
In a world of globalization those struggles reach me very often.
This plugin has the ability to store language codes the in post meta data to have articles with different languages on the same page. This might be interesting for blogs who only need sometimes a different language.
One of those is the following case: 
The boss is writing articles in english but its a german company and needs some articles in german too. 
But the second language articles are unique and not only translations.
You maybe think that would be quite simple using WPML. But what are you doing if you need both languages on the start page? 
For this special case, we wrote a plugin, which is able to show all languages on the home page and manipulates the query if some language is chosen. 
It also makes a difference in terms of SEO as it changes the line
<html xmlns=”http://www.w3.org/1999/xhtml” dir=”ltr” lang=”en-EN”>
according to your language.
For a real working experience you can use it in combination with the <a href="https://wordpress.org/extend/plugins/no-function-language-widget/" title="no function language widget" rel="ugc">no function language widget</a>.

Language Field

If you don't need a full multilingual plugin, but have single articles in a different language.

Theme and plugin translation for Polylang (TTfP) vs Language Field