Making WordPress.org

#6790 closed defect (bug) (maybelater)

changed translation strings are not marked as fuzzy

Reported by: timse201's profile timse201 Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

Today The SEO Framework was updated and one string changed. It was marked as fuzzy in dev and under stable the string remained approved.

Attachments (3)

1.png (70.9 KB) - added by timse201 14 months ago.
overview
2.png (114.8 KB) - added by timse201 14 months ago.
dev
3.png (109.5 KB) - added by timse201 14 months ago.
stable

Download all attachments as: .zip

Change History (10)

@timse201
14 months ago

overview

@timse201
14 months ago

dev

@timse201
14 months ago

stable

#1 @timse201
14 months ago

This was the case for all languages.

source code 4.2.7.1 old stable:

Input::make_checkbox( [

'id' => 'display_seo_bar_metabox',
'label' => esc_html( 'Display the SEO Bar in the SEO Settings metabox?', 'autodescription' ),
'escape' => false,

] ),

source code 4.2.8 new stable:

Input::make_checkbox( [

'id' => 'display_seo_bar_metabox',
'label' => esc_html( 'Display the SEO Bar in the SEO Settings meta box?', 'autodescription' ),
'escape' => false,

] ),

Last edited 14 months ago by timse201 (previous) (diff)

#2 @tobifjellner
14 months ago

  • Keywords reporter-feedback added
  • Priority changed from high to normal

The "Stable" translation branch reflects all strings currently available in whichever tagged version of the plugin the /trunk/readme.txt points to in the declaration "Stable tag:".
The "Stable branch" is the one that is used to build language packages, and the threshold for generating the first language pack (90% of the strings in the project translated and approved) is also calculated against the "Stable" branch.

The "Dev" translation branch contains all strings available under the /trunk branch.

In other words, a plugin developer can add an updated version of their plugin under /trunk. They can even add new tagged versions under /tags. But as long as the /trunk/readme.txt still points to an earlier version, that will be the "Stable version" that new users will be suggested, and the language pack will still be based on the "Stable version".

By pushing a change to /trunk before "releasing it" by updating the "Stable tag" declaration, a developer may make strings available for translation. When the stable tag later gets updated, translate.wordpress.org will synchronize any matching approved translations under "Dev" to the new "Stable" project.

To my understanding, I see no bug here. But I'll leave it to you, @timse201 to confirm that and close this ticket.

#3 @timse201
14 months ago

Hi,
@tobifjellner I know this behaviour but the string is already present in stable.

https://meta.trac.wordpress.org/ticket/6790#comment:1

#4 @tobifjellner
14 months ago

The strings you showed here are different. One has a space in "meta box".

#5 @timse201
14 months ago

Right that string changed and will be shown as fuzzy. But it was only fuzzy in dev and not in stable. In stable the translation for metabox was approved for meta box. This happened for all languages.

#6 @timse201
14 months ago

  • Keywords reporter-feedback removed

#7 @timse201
14 months ago

  • Resolution set to maybelater
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.