WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 6 years ago

Last modified 22 months ago

#20883 closed defect (bug) (wontfix)

Translating all plugin headers?

Reported by: pavelevap Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.6
Component: I18N Keywords: ui-feedback
Focuses: Cc:

Description

I am really not sure if translators should be able to localize Author, Author URI or Plugin name? Description is very helpfull, but why translating strings like "Matt Mullenweg" or "http://ma.tt/" which are in current admin localization file?

Related: #19597

Change History (10)

#1 @nacin
7 years ago

Plugin Name - Example
Author - Sergey Biryukov
Author URI - http://sergeybiryukov.ru/english/ (example)

Plugin Name - whatever "Example" is in Russian
Author - Сергей Бирюков
Author URI - http://sergeybiryukov.ru/

I don't see the harm in offering these strings for translation. At worst, they simply aren't translated.

#2 @SergeyBiryukov
7 years ago

That's a nice example :)

While translating a plugin name doesn't make much sense for bundled plugins, this might be helpful in other cases. I guess the bundled plugins will eventually end up with their own text domains and those strings will be removed from wordpress-admin.pot.

Someone might want to transliterate the Author name as well (along the lines of Readable Names).

#3 follow-up: @pavelevap
7 years ago

:-)

Yes, but plugin name can be sometimes specific brand and plugin authors will not be happy when they see it translated. Also translators can change author URL to their site with localization files. I understand transliteration, but I am not sure if all headers should be translatable. Description field can be enough for translators, they can mention for example some special URI there. For example Chinese (Taiwan) translation uses english brand "Hello Dolly" and only Description is translated...

#4 in reply to: ↑ 3 @DrewAPicture
7 years ago

  • Cc xoodrew@… added
  • Keywords ui-feedback added

Replying to pavelevap:

Yes, but plugin name can be sometimes specific brand and plugin authors will not be happy when they see it translated.

Branding would be a big argument against translating the plugin name. Translate the description, absolutely, but not the name. I can also see the inherent value in translating the author name as in @nacin's example.

#5 @nacin
7 years ago

I don't see an issue in translating a plugin name. In many cases, it is going to make sense.

We're simply offering the name for translation. Ultimately, it is up to the developer to accept the translation (even when we do language packs, they will have control over translations of their plugins). If they don't want the name translated, then they don't need to accept that. In some cases, it is a branding thing, but only in some cases.

We need to think about the best experience for the user, which is localizing everything — yes, including the plugin directory and readmes. (In due course.)

#6 @nacin
7 years ago

  • Version changed from 3.4 to 2.6

#7 @daveshine
7 years ago

I can only emphasize what @nacin said:
It's really important to have all strings to be translateable, especially for the plugin title and description! The other data like URL and Author could be important in some cases, like other languages like Russian or so.

So please keep the data in there!

Thanks, Dave from Germany (who uses & needs this mentioned stuff every day!)

#8 @dd32
6 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

As others have pointed out, It's up to the plugin developer to accept translations that change the plugin name.
Translating the fields has a genuine purpose, which is enough to say wontfix.

This ticket was mentioned in Slack in #meta-i18n by sergey. View the logs.


4 years ago

This ticket was mentioned in Slack in #polyglots by sergey. View the logs.


22 months ago

Note: See TracTickets for help on using tickets.