This SEO plugin checks the content of posts/pages for the keyword density (single/phrases) while writing and is automatically setting the META-tags.
First you should add the language specific stopwords. You can integrate them in the file stopwords.js. The simpliest way: If you are writing in french you can edit the block defined with
'de' which you replace with
'fr' - if you don't need the german language. After that you can replace the wordlist with the french ones. At least you have to search the file keyword-statistics.php for all occurencies of the string
<option value="de" and replace the
Simply have a look at http://xml.coverpages.org/iso639a.html. There you can find a list of all language codes that can be used as your content lanugage.
Simply add the string
'*LANGUAGE*': [ *...* ], at the second line of the file stopwords.js. Replace
*LANGUAGE* with the one you want to integrate (
fr if you want to integrate french for example).The
*...* is a placeholder for the stopwords you wish to define. You must embed each word in single quotes (e.g.
'the'). Single quotes unsed in the stopword have to be escaped with
\'. If you wan to add
it's you have to make it this way:
'it\'s'. Between the stopwords you need a
, to separate them.
At least you have to search after all occurencies of
<option value="de". Just copy these lines and insert them the line before. Then change all
"de"s in the new line to
"fr". From now on you can set french as your default language and also choose it in edit post/page.
The stopword list should only contain single words with no double meanings. For example in the dutch language the word 'weer' means 'weather' but also 'again'. Words like that should not appear in the list. There are two reasons why: Firstly these words are helping search engines to classify the page content and these words are surely not classified as stopwords by Google, Yahoo! and Bing. The second reason is that there are some people writing about weather and they need this word to be listed as a keyword and not as a stopword. So please avoid those words if you want to filter stopwords.
Just send me the stopword list. Before you do this be sure that the stopwords face the conditions described above. I'll check the wordlist - if there is a way of automatic translation - and add it to the plugin. In future updates the stopwords stay inside the plugin so you don't have to do it anymore.
If there are some words that - for your meaning - belong to the stopword list just send them to me via. e-mail. I'll check and maybe add them to the existing.
You have to create your own pot file of the plugin which is containing the localized captions. Translate the captions in the pot file and build your own mo file. The name of this file has to keep the structure condition
keyword-statistics-*LANGUAGE*.mo. LANGUAGE is a placeolder for your personal language - to be exact the shortcode of it. If you are translating the captions to spanish you'll use
es instead of it.
If you want to translate the captions displayed at the admin interface or the author's view for editing posts, you'll have to edit the included file named
keyword-statistics.pot that comes with the current version of the plugin. There you see the english captions used in the backend.
It is separated in blocks beginning with comments - recognizable at a
# - which is followed by two lines. The first line is containing the double quoted english caption initiated by a
msgid at the beginning of the line. At the second line - initiated by
msgstr - you can add your translation between the double quotes.
After translating all messages you can send me the file and I'll integrate the translation. At the end your authors got rid of the language mix at their backend.