Support Forum
Support Forum
The default path for language files is actually incompatible with the CodeStyling Localization plugin. This plugin only check the plugin directory for language files. Sure, you can change the path in your configuration, but in my opinion you should keep the config very simple and near to the default.
Offline
That is all it is - a default location - and, in our opinion, a remarkably stupid and short-sighted default. It means that when a plugin is updated via the WP Updater you lose the language folder contents as - at this time - WP removes the whole plugin before updating it with the new version.
We made the very sensible decision to avoid this and place the language files in a far better location. And - top use the word 'default' again - WP is perfectly happy to allow this.
I would suggest that the problem really lies in the CodeStyling plugin - which I like by the way - which should not assume the default location but should use the WP api to determine where the language files actually are - although I accept that might not always be so easy for them, to do.
 |
YELLOW
SWORDFISH
|
Okay, from this sighted i agree with you. But now a user must update his language files with every SP update. If the user has his own translations he will loose this translations with the update, because the user have to download the new language files. Or is there a way to merge this language files?
Offline
Firstly there are not usually that many changes between versions. V5 is an exception because it is a complete rewrite.
Secondly - if you really insist on making your own translations instead of using the community translation site then tools like poEdit cater for merging current code into an existing PO file by removing old, redundant strings and just adding new ones.
|
YELLOW
SWORDFISH
|
All RSS1 Guest(s)