Make WordPress Core

Opened 3 years ago

Last modified 2 years ago

#23503 closed defect (bug)

Post Formats: i18n issues — at Version 1

Reported by: SergeyBiryukov Owned by:
Milestone: 3.6 Priority: normal
Severity: normal Version: 3.6
Component: I18N Keywords: has-patch
Focuses: Cc:

Description (last modified by SergeyBiryukov)

  1. Most of the time, we refer to the "Standard" post format with the appropriate context:

In a couple of places, however, the context is missing:

  1. [23449] introduced Edit screen UI for post formats. There's now a "Standard" tab above the post title. In Russian, "post" is feminine and "format" is masculine, so seeing "Standard" adjective without the "format" word next to it is confusing. I guess the tab needs a separate context. Fixed in [23843].
  1. [23843] introduced a couple of issues:
    1. ucfirst( sprintf( __( '%s Post' ), $slug ) ):
      1. '%s Post' is not localizable, see dd32's comment in #17609.
      2. ucfirst() doesn't always work correctly for UTF-8 characters, it depends on PHP locale.
      We should use actual labels instead of just putting post format slugs into a generic string.
    2. i18n is missing in line 397:

Change History (3)

#1 @SergeyBiryukov
3 years ago

  • Description modified (diff)
  • Keywords needs-patch added; has-patch removed
  • Summary changed from Standard post format needs more contexts to Post Formats: i18n issues

3 years ago

Note: See TracTickets for help on using tickets.