Making WordPress.org

Opened 6 years ago

Closed 5 years ago

#4431 closed task (blessed) (fixed)

Improve the translation editor experience to support new features

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

Description

The current UI for submitting translations is very basic but limited at the same time. This makes it hard to extend the editor with new features like suggestions (#4430) or comments/notes (#GlotPress209).

The idea is to move some elements around and to set the source and translations into focus. Attaching some screenshots of the current UI.

Attachments (4)

4431-editor-view.png (178.4 KB) - added by ocean90 6 years ago.
4431-contributor-view.png (178.4 KB) - added by ocean90 6 years ago.
4431-logged-out-view.png (187.4 KB) - added by ocean90 6 years ago.
4431-mobile-view.jpeg (569.6 KB) - added by ocean90 6 years ago.

Download all attachments as: .zip

Change History (9)

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


6 years ago

#2 @ocean90
6 years ago

In 8751:

Translate: Update editor interface for translations.

  • Increase focus on translation by moving original, context and translation into the same column.
  • Add tabs for plural forms.
  • Move action buttons more closely to textarea.
  • Increase size for textareas.
  • Automatically resize textarea heights.
  • Provide an area for suggestions, see #4430.
  • Add help dialog with support for locale resources, see #3522.
  • Stack columns on mobile.

See #4431.

#3 @knutsp
6 years ago

Nice!

But Shift+Enter now generates an error instead of saving the translation, as it did before.

#4 @ocean90
6 years ago

In 8766:

Translate: Split source details into separate <details> elements and add persistent storage for open/close state.

See #4431.

#5 @ocean90
5 years ago

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