#23210 closed feature request (maybelater)
Multilingual engine
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | I18N | Keywords: | |
Focuses: | Cc: |
Description
I've used WordPress for years, and I've been using pretty much all plugins for multilingual websites (Polylang, qTranslate, WPML).
All these implementations have problems, mainly because - I think - add "overhead" to the structure. In fact the engine below them is not multilingual and they "fake" multilingual behaviors.
This often causes problems with other themes and plugins.
Also it is a potential security problem, since a lot of them are not regularly updated.
Also, whichever you pick, you'll not be able to use the official WordPress application (at least the Android version).
I think that WordPress should work toward a creation of a multilingual engine in the core code to solve these problems.
Change History (7)
#3
@
12 years ago
@ocean90: yes it can, but has all the problems I explained. Also you link a ticket of 9 years ago... The world changes in 9 years, the web way more
#4
@
12 years ago
I'll vote -1. I don't think this should be done in core. Also, "plugins may not be updated regularly" and "plugins may be insecure" is true for any plugin, not only the ones you mentioned. That doesn't mean each one of them should be implemented in core :)
#5
@
12 years ago
- Milestone Awaiting Review deleted
- Resolution set to maybelater
- Status changed from new to closed
This was discussed at the WordPress Community Summit in October. It is a lofty goal for this to at some point find its way into core, but this is definitely not on the near-term roadmap. For now, the fact that no plugin has yet to do this well is actually a better reason to not attempt this.
Here's a promising plugin: https://github.com/cftp/babble.
– Matt, #99