Thank you for confirming the issue so succinctly, nao.
This seems to work with excerpts but not themes such as magazine themes which determine their own word count ... or have various word counts according to the modules or excerpt's position.
That is what I am trying to do. I have no idea how to customize or apply the path to them.
• Is it still the position in 2.9 that plugins and themes cannot be localized because their strings are not in the default WP catalog?
Chinese, Japanese and Korean (to begin with) would be great markets for WordPress to enter and get right. I am desperate for better support of them. M$ etc have just steamed into the region and the local options are pretty dire in my opinion.
• I make the point that in many case clients now have a legal responsibility to provide multi-lingual services and this is not really conceived of in the core of WordPress.
Otto42: Have you read the documentation?
WordPress in Your Language
Yes, Otto42, please don't patronise ... your answer does not come anywhere near the problem. Do you know anything about making WordPress work with non-Latin characters ... have you tried at all?
• Actually, problems arise not just with English installs, but also with installs in native languages, including non-Latin installs.
It is to do with the majority of themes being Latin characters only. Particularly problems arise with theming and plugins which do cannot recognize, and do not support non-Latin characters. Whereas you might have one language plugin that works to some degree, if you combine it with another plugin it does not work.
Where there is documentation, and there is not a lot, it is rarely in English. In this case, there is not (t looks like the readme is corrupted). Or take a look at the Japanese WP site.
I suggest that you try making a bi- or tri-lingual WP install work sometime. Technically, it is fairly possible. Visually, as in making a theme work universally in all languages with features, it is a real problem.
WordPress should really address it by moving all the site language elements (words rendered in browsers) ... and encouraging developers to move all the language ... out of the themes, numerous pages of code etc and into one or two editable single pages, e.g. one for front end, one for back end.