Since this topic, I decided that Polylang should support YARPP, so the language taxonomy is now registered with the YARPP option and I hope everything works well.
Now I got the logical request to translate the user strings (stored in YARPP options) such as “Related posts”, “No related posts”, etc… It’s quite easy to do and I proposed a first way to translate some of them.
But I would like to go on my integration work and propose an out of the box solution. So I can collect all the relevant options and use the way proposed in the link above…
However, you are likely to add new strings in the future and it won’t be easy for me to follow the development of YARPP. Could it be possible for you to group your strings so that for example when I do a
get_option('yarpp');, it returns something like:
'threshold' => 4 'limit' => 4 'strings' => array( 'before_related' => '<h3>'.__('Related posts:','yarpp').'</h3><ol>', 'no_results' => '<p>'.__('No related posts.','yarpp').'</p>' ...
Thus I will know that I will have to translate all what is in the ‘strings’ array and the integration of both plugins won’t be broken if you change or add a new string.
- The topic ‘Better integration of YARPP and Polylang’ is closed to new replies.