WordPress.org

Making WordPress.org

Opened 10 months ago

Closed 9 months ago

#3764 closed defect (wontfix)

Denote the projects that are 'not properly prepared for localization' on their intro block

Reported by: garrett-eclipse Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

Hello,

@Presskopp's question on #3763 gave me the idea for this, but would find it useful if all projects that aren't prepared for localization could be denoted graphically in the views so you don't have to click into them to get the notice. That way translators can avoid wasting their time.

Thanks
P.S. attaching concept screenshot.

Attachments (1)

Screen Shot 2018-08-16 at 9.37.11 AM.png (71.0 KB) - added by garrett-eclipse 10 months ago.
Sample Concept

Download all attachments as: .zip

Change History (4)

#1 follow-up: @casiepa
10 months ago

To be honest, I would prefwr to approach this in the opposite, positive way. So adding e.g. the polyglots icon when translation is possible. Having an extra icon in the list might give plugin authors a push to make their plugin i18n ready.

#2 in reply to: ↑ 1 @garrett-eclipse
10 months ago

Replying to casiepa:

To be honest, I would prefwr to approach this in the opposite, positive way. So adding e.g. the polyglots icon when translation is possible. Having an extra icon in the list might give plugin authors a push to make their plugin i18n ready.

Thanks @casiepa, sadly I'm not sure what icons you're speaking of as there's none present on translate.wordpress.org for projects. Are you speaking on actual plugin author bios as that would be unrelated to my request.

I would normally agree a positive method is preferred, but as the translate instance is primarily for translators and assisting them it's less front-facing like the actual plugin repository so the tools should be geared towards assisting translators. As such I feel it would be greatly helpful to translators to flag to them the not prepared projects so they can be avoided.

The push to prompt plugin authors to make their plugins i18n ready I feel is separate from this topic but I still feel is an important one that can be investigated seperately.

#3 @ocean90
9 months ago

  • Resolution set to wontfix
  • Status changed from new to closed

This would just blow up the box unnecessarily. The usual workflow to get to the translation project is by using the links in the directories and not by searching/browsing on translate.w.org.

Note: See TracTickets for help on using tickets.