Clustering strings for improved translation context
-
Hey,
I was thinking that it will be really helpful to create clusters of translation strings, within the WordPress.com project. More of less like the available options under Filter > Views. The reason for that in improved context.Some examples would be Theme descriptions, Akismet, Domain registration, Jetpack etc.
Translating long Theme descriptions is quite different from short Domain registration error messages. More liberal vs strict translations. Wording can be more consistent too when going through the same cluster of string for a specific purpose. Describing a Theme vs informing users about error or call to actions.
-
Thanks for your suggestion, titanas.
For Jetpack related strings, you can simply search for the term “Jetpack” : Link
They either include the word “Jetpack” in the string itself or its file path.The same goes for Akismet (please note some of Akismet UI are not yet translatable): Link
You can also try filtering by the word “domain”: Link
This one might include strings from some other sections, but we won’t be able to create any more accurately assembled “view” unfortunately.
The reason is that some domain registration strings reside in files with generic file paths, so we currently don’t have a good way to filter it.Theme descriptions are tough ones, because they are taken from the themes project and put into wpcom project in a special way. They have no file paths information at the moment. You might want to try finding untranslated strings with comments: Link
Again there are some unrelated strings here too, but you mostly find theme descriptions.If you have more examples for certain collection of strings you’re looking for, please let us know.
-
- The topic ‘Clustering strings for improved translation context’ is closed to new replies.
