[wp-meta] [Making WordPress.org] #5377: Plural form with missing plural translation results in blank string
Making WordPress.org
noreply at wordpress.org
Tue Aug 18 00:25:46 UTC 2020
#5377: Plural form with missing plural translation results in blank string
--------------------------------------+---------------------
Reporter: johnbillion | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone:
Component: Translate Site & Plugins | Resolution:
Keywords: close |
--------------------------------------+---------------------
Changes (by dd32):
* keywords: => close
Comment:
> I'm not sure if this is something that should be fixed at the point
where the translation is packaged, or in WordPress at the point where the
plural form is chosen.
How about a 3rd option? The GlotPress import process should be treating
the singular & singular-plural originals as different strings, thus not
marking the singular translation as a translation of the pluralised form.
I believe I've seen some code in GlotPress which matches translations
based on the singular-only string, so I believe this probably belongs as a
GlotPress bug.
I wasn't able to [https://github.com/GlotPress/GlotPress-WP/issues find a
issue in GlotPress] for this kind of behaviour. I'm marking this as
`close` as I feel this should be fixed/reported upstream, but that this
ticket should remain until that happens (if it happens).
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5377#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list