WordPress.org

Making WordPress.org

Opened 3 months ago

Last modified 4 weeks ago

#5891 new enhancement

If a blank or tab is at the end of an original line, mark it in the original

Reported by: psmits1567 Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords: needs-design
Cc:

Description

Currently a lot of fuzzy records are created, because the translation misses a blank or tab at the end of the translated line.
As it is possible to mark chars in the original, it would be an improvement if a blank or tab at the end of an original line is marked.

Change History (7)

#1 @tobifjellner
3 months ago

... or in the beginning of the string, by the way.

#2 @psmits1567
3 months ago

Correct Toby forgot to mention that as well

#3 @dd32
3 months ago

Generic things like this, that are in the GlotPress core, and not specific to WordPress.org would be better reported to https://github.com/glotpress/glotpress-wp

There's potentially some things we could do here though on WordPress.org, such as running the fixer over fuzzy matches to see if it can 'upgrade' the string to respect the new original..

#4 @psmits1567
3 months ago

If the fixer coud resolve those issues, that would already reduce the amount of work. But I like preventing those issues.
I also suspect that this happens via import of translations. So maybe an additional check, when importing translations could also reduce those fuzzies.

#5 @dd32
4 weeks ago

Just noting I added some test strings to test-plugin-3 in plugins2624933 to visualise this.

You'll see that leading/trailing spaces aren't highlighted in any way.

In regular document editors with "show hidden characters" enabled, you'd see a feint dot, usually slightly vertically centered.

I think it'd be worth taking a "show spaces" or at least a "show leading/trailing spaces" enhancement to GlotPress.

It doesn't look like the lack of a space in the translation trips any warnings.

Last edited 4 weeks ago by dd32 (previous) (diff)

#6 follow-up: @psmits1567
4 weeks ago

Correct no warnings are shown, but if you do not add the blank at the end of the line, the translation is incorrect. Mostly the blank is added intentionally by the developer.

#7 in reply to: ↑ 6 @dd32
4 weeks ago

Replying to psmits1567:

Correct no warnings are shown, but if you do not add the blank at the end of the line, the translation is incorrect. Mostly the blank is added intentionally by the developer.

Yeah, I agree, I think there should be a warning added for that too.

Note: See TracTickets for help on using tickets.