Making WordPress.org

Opened 2 years ago

Last modified 19 months ago

#6369 new feature request

Make the pattern strings easier to translate by making each pattern a "plugin"

Reported by: nekojonez's profile NekoJonez Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

Currently, to translate patterns it's one huge table with all the patterns in it.

https://translate.wordpress.org/projects/patterns/core/

Yet, I have been thinking that this could be in another way.

I think it would be great if it's easier to see if you translated all strings of a certain pattern.
Also, I think it would be nice if you were able to assign a PTE to a pattern. E.g. if somebody from your locale created a pattern... So, they can translate it easier.

Maybe this could work by making each pattern as a ""plugin"" (intentional quotes here)
Like each pattern can be displayed like plugin/theme translations are displayed?

I'm creating this ticket mostly to create some discussion about this, since I want to hear other people's thoughts about this (and also, I think this won't be an easy thing to create on a technical level)

Change History (4)

#1 @psmits1567
2 years ago

For starters all latin strings could be marked with a label, as most people will not translate them. And next do not count them as to translate. Secondly remove all the duplicate texts, and make that a separate library as I already proposed to do with strings from themes and plugins. That has the benefit that the database gets smaller, and less to translate the same strings over and over.

#2 @psmits1567
2 years ago

Another improvement would be to define the text for Lorem ipsum. There are many originals that tell the same story, but each with a slightly different text. That frustrates translators, as they need to pay attention to the differences. Why not define a couple of defaults for them and tell pattern creators to use these defined texts???

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


19 months ago

Note: See TracTickets for help on using tickets.