Related strings

[MartinIQ]

It would be really cool if we could have some kind of 'related strings' feature, when opening the details of a particular string.

Let's say I'm working on the wordpress.com translation and open/double click a string for translation e.g. 'draft'. It would help a lot to see a list of all other strings of that particular language which contain the word 'draft' in order to see how 'draft' has been translated in other places to keep the whole translation consistent.

This looks like a duplicate of #9.
Reopen if I'm missing something.

Reopen if I'm missing something.

#9 mentions past translations, but it seems that there are more cases. The first consideration is past vs. current, where I argue that past translations are perhaps not as useful as current translations, which could be

• translations of string in version X of project Y
• translations of string in all versions of project Y
• translations of string in all versions of all projects (in the current install of GP)

In my mind, clicking on a link in the detail view opens a pop-up that lets me choose what I want to see from the options above, each instance with a "use this for current string" link. Or something.

You said in the GlotPress ​P2 Blog:

... could we continue this conversation there?

Sure. Would have done that, if the ticket had not been closed. ;)

... searching by filename ... you already can do that

I know. Unfortunately you have to know the filename in order to search for it. In case of the WP.com GlotPress that's impossible as it doesn't show the filenames in detail view.

Replying to vanillalounge:

In my mind, clicking on a link in the detail view opens a pop-up that lets me choose what I want to see from the options above, each instance with a "use this for current string" link. Or something.

Wow. That's more than what I came up with. Totally love your idea.

In case of the WP.com GlotPress that's impossible as it doesn't show the filenames in detail view.

I suspect that that is the intended behaviour on WordPress?.com, you'll need to take it up with them, I reckon.

Replying to vanillalounge:

I suspect that that is the intended behaviour on WordPress?.com ...

Well, not intended. As far as I remember some staff told me about technical difficulties based on how translations are handled on WordPress?.com. So no sense in taking it up with them.

...technical difficulties based on how translations are handled on WordPress?.com

Unless things have drastically changed since I've worked there, the only difficulty that I can imagine is pointing a string to the source code which, as far as I know, is not visible to the outside (unlike .org, which is on Trac). .com gathers all strings (core, plugins, widgets, themes) in a single file .pot file, it's true but to not link a string to its place in the code is not a technical hurdle or a limitation of GlotPress, it's by design of t.w.c's own installation of GlotPress.

That said, searching by filename does work on t.w.c, you just need to know the name.

Replying to vanillalounge:
That's what I was talking about in comment 3. ;)

Unfortunately you have to know the filename in order to search for it.

Replying to vanillalounge:

Unless things have drastically changed since I've worked there, ...

Oops, I wasn't aware you don't work for Automattic any more.

... but to not link a string to its place in the code is not a technical hurdle or a limitation of GlotPress, it's by design of t.w.c's own installation of GlotPress.

Get it. All I know is, t.w.o shows comments and references in the Meta section while t.w.c doesn't. When asked about it, an automattician (can't remember who) told me it's because of their system at Wordpress.com. Hope they will fix this some day. :)