WordPress.org
Get WordPress

Making WordPress.org

Opened 6 years ago

Closed 6 years ago

#3833 closed defect (bug) (invalid)

Translation error in A → Z

Reported by: mukesh27's profile mukesh27 Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords: needs-patch dev-feedback
Cc:

Description

On translation page when i translate A → Z it show A Z. also when i edit translation again it will not show →

As per Jeroen Rotty( @jeroenrotty ) report in #polyglots slack channel.

Attachments (2)

error_01.png​ (2.9 KB) - added by mukesh27 6 years ago.
error_02.png​ (9.6 KB) - added by mukesh27 6 years ago.

Download all attachments as: .zip

Change History (11)

@mukesh27
6 years ago

@mukesh27
6 years ago

#1 @mukesh27
6 years ago

  • Component changed from General to Translate Site & Plugins
  • Keywords needs-patch dev-feedback added

This ticket was mentioned in ​Slack in #polyglots by mukeshpanchal27. ​View the logs.
6 years ago

#3 @casiepa
6 years ago

It seems the 'rightwards arrow' → cannot be added into a translation.
However the 'long rightwards arrow' ⟶ seems to work fine.

Not sure why the first one gets filtered out...

Version 0, edited 6 years ago by casiepa (next)

This ticket was mentioned in ​Slack in #glotpress by jeroenrotty. ​View the logs.
6 years ago

This ticket was mentioned in ​Slack in #meta by mukeshpanchal27. ​View the logs.
6 years ago

#6 @garrett-eclipse
6 years ago

  • Resolution set to invalid
  • Status changed from new to closed

This is a known GlotPress issue found here - ​https://github.com/GlotPress/GlotPress-WP/issues/648

#7 @mukesh27
6 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

@garrett-eclipse right now we have error in translation so i think we have to open this ticket once it fixed from GlotPress and above issue is resolve in our translation website then you can mark this ticket as close.

This ticket was mentioned in ​Slack in #glotpress by garrett-eclipse. ​View the logs.
6 years ago

#9 @dd32
6 years ago

  • Resolution set to invalid
  • Status changed from reopened to closed

I'm going to reclose this as invalid due to it being an upstream bug, the fact it affects one of our strings isn't unexpected at all, but leaving this open isn't going to help fix the issue or speed up fixing it.

Note: See TracTickets for help on using tickets.