Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Project-Id-Version" for all plugins set to 'Stable (latest release)' #442

Closed
jrfnl opened this issue May 14, 2016 · 4 comments
Closed

"Project-Id-Version" for all plugins set to 'Stable (latest release)' #442

jrfnl opened this issue May 14, 2016 · 4 comments
Assignees
Labels
[Status] In Progress Tracking issues with work in progress [Type] Enhancement A suggestion for improvement.
Milestone

Comments

@jrfnl
Copy link

jrfnl commented May 14, 2016

If you open up any plugin translation file in a WP install, you'll see the following as part of the header:

# Translation of Stable (latest release) in Dutch
# This file is distributed under the same license as the Stable (latest release) package.
....
"Project-Id-Version: Stable (latest release)\n"

Looks like $project->name for plugins is incorrectly set to Stable (latest release) and passed on like that to the .po and .mo file generation.

@toolstack
Copy link
Contributor

I assume you mean on translate.wordpress.org? If so this is because they create a master project for the plugin and then create sub projects with names like "Stable (latest release)". When GlotPress generates the export files it only takes the project name of the sub project, not the parent.

In that respect this is by design and not a bug in GlotPress.

On the other hand, it's probably not the best result for translate.wordpress.org, @ocean90 can probably add some thoughts on it.

I suspect this needs a ticket on the meta.track.wordpress.org to address the site specific implementation, but will also need a filter in GlotPress to address it.

@jrfnl
Copy link
Author

jrfnl commented May 14, 2016

I assume you mean on translate.wordpress.org?

Correct, that's exactly what I meant. My apologies for posting this in the wrong place in that case.

@toolstack
Copy link
Contributor

No problem, it is a less than ideal way to handle sub project by default so it does need some attention.

@jrfnl
Copy link
Author

jrfnl commented May 14, 2016

Opened a ticket on trac: https://meta.trac.wordpress.org/ticket/1708

@toolstack toolstack added [Type] Enhancement A suggestion for improvement. [Status] In Progress Tracking issues with work in progress labels May 14, 2016
@toolstack toolstack added this to the 2.1 milestone May 14, 2016
@toolstack toolstack self-assigned this May 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] In Progress Tracking issues with work in progress [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

2 participants