[wp-meta] [Making WordPress.org] #5671: If an original line does not contain a dot at the end of the line but the translation does, the record will be fuzzed
Making WordPress.org
noreply at wordpress.org
Thu Mar 25 01:19:56 UTC 2021
#5671: If an original line does not contain a dot at the end of the line but the
translation does, the record will be fuzzed
--------------------------------------+---------------------
Reporter: psmits1567 | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Translate Site & Plugins | Resolution:
Keywords: |
--------------------------------------+---------------------
Comment (by dd32):
> If you do not have Glotdict installed, there is no warning that you add
or leave a dot out of the translation.
I had thought there was a warning about changing trailing punctuation, but
I can't find one in GlotPress or on WordPress.org, so I must have been
thinking of the GlotDict warnings myself.
> In the EU it is standard writing rules that you end a line with a dot.
Yes, that's a standard writing rule in most "western" languages that I'm
aware of, but I'm not sure we can automatically apply trailing punctuation
matching between original and translation for ''submitted translations''..
Some locales do strip punctuation (eastern languages IIRC) so it's not a
blanket rule.
I would probably consider it a translation ''error'' if a submitted
translation adds punctuation unexpectedly.
For updated originals that result in a translation going fuzzy, where the
only difference between the originals is a trailing punctuation change,
maybe we can automatically suggest a new pending string with the matching
punctuation..
For example to make it clear to others (Google Translate, I apologise to
french speakers)
{{{
Original: This is a string
Translation: Ceci est une chaîne
New Original: This is a string.
Now Fuzzy Translation: Ceci est une chaîne
Automatically added Pending Translation: Ceci est une chaîne.
}}}
I'm not sure I'd want it to say "It's only varying by trailing
punctuation, don't bother fuzzying it" or "It's only a difference of
trailing punctuation, adjust and approve".. but the above seems like
something more acceptable.
Reading between the lines (so to speak) I think what is being said here is
that there's a tooling issue around fuzzies, it's hard to quickly go
through and approve fuzzies as "near enough" or to easily approve pending
replacements for them (be they human submitted or automatically generated)
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5671#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list