Opened 17 months ago
Last modified 14 months ago
#19980 new defect (bug)
Localized oEmbed providers
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | I18N | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Follow-up from #19601.
Some localizations might want to add their own oEmbed provider, perhaps a service widely used by users in their country or those who speak their language, despite us never hearing of it.
Right now, Bulgarian and Chinese add some, and Russian would consider it. ref Others, if shown the opportunity, will also likely want to add some.
We need to come up with a decent solution for handling these. Perhaps it is a switch() on get_locale() in WP_oEmbed.
Change History (5)
comment:2
nacin
— 17 months ago
If the service is of a non-spammy nature that's useful to one set of users, perhaps we should enable it globally and consistently support it instead.
Agreed. The only reason why I'd want to limit it is to keep the processing time to a minimum, but you're definitely right.
comment:3
nacin
— 17 months ago
Bulgarian adds #http://(www\.)?vbox7\.com/play:.+# to point to http://vbox7.com/etc/oembed/. Chinese (China) adds three manual regular expressions: http://i18n.trac.wordpress.org/browser/zh_CN/tags/3.3.1/dist/wp-content/languages/zh_CN.php#L302. No word on whether any support oEmbed, but we shouldn't be carrying over any non-oEmbed providers.
comment:4
SergeyBiryukov
— 14 months ago
I was considering adding three video services for ru_RU. Turned out none of them support oEmbed.
Do we really need to support them for certain locale's only?
If the service is of a non-spammy nature that's useful to one set of users, perhaps we should enable it globally and consistently support it instead.