If Gutenberg blocks are translated on WordPress.com translations I expected to see the interface translated like we do for Simple Sites. It's pretty weird for a user that had everything translated on their simple site and once they get their site AT'd the blocks are not translated anymore.
It would be great to use WordPress.com translations on Atomic sites for consistency.
This was reported here:
p1544532027263400-slack-gutengroup-wpcomhappy
@kwight I vaguely remember us fixing the translations for Calypsoify before. Any ideas why this might not be working for Atomic sites?
I don't know if Atomic/Jetpack was part of all that, I think more testing is needed first to narrow down exactly what parts are involved (eg. parts of the sidebar come from different API calls).
@akirk any ideas why this might be happening? Are there any known issues with wp-admin translations on Atomic sites?
/cc @Automattic/atomic
This seems to be a duplicate of #29244
I'm not sure if they are related. It looks like the issue #29244 is related to the Jetpack blocks only and it was also occurring in Simple Sites. This one is happening with all blocks and is only occurring in Atomic sites.
It looks like this patch for Core, scheduled for 5.0.2, will resolve this: https://core.trac.wordpress.org/ticket/45528
See p9o2xV-cH-p2 for more details.
Got a user in chat reporting this issue in Japanese language: hc-8783842
It's an AT site - wellvill.com
Follow-up here : zen-1656223
Reference screenshot here : http://cld.wthms.co/Z3QIRR
Would someone mind taking another peek?
@pratikawari28 The issue will be fixed once both WordPress and Jetpack are updated (WP 5.0.2 on one hand, Jetpack 6.9 on the other).
While WP 5.0.2 should be released very soon, Jetpack 6.9 won't be released until January 10.
If the site owner would like to apply the work-around on their site sooner, they can do so thanks to the Jetpack Beta plugin and by searching and using this PR in Jetpack > Beta once the Beta plugin is installed:
https://github.com/Automattic/jetpack/pull/10982
Most helpful comment
It looks like this patch for Core, scheduled for 5.0.2, will resolve this: https://core.trac.wordpress.org/ticket/45528