What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== Sometimes users accidentally translate content in the wrong locale. We need the ability to move a page across locales when this happens. What problems would this solve? =============================== Would keep us from losing translations when they're put in the wrong locale. Who would use this? =================== Admins dealing with localizer mistakes. What would users see? ===================== Nothing. What would users do? What would happen as a result? =================================================== Ideally, this would be done in the standard page move UX. Either allow us to *optionally* include the locale in the destination slug, or give us a pop-up menu to choose a destination locale. Is there anything else we should know? ======================================

Yes, this is a serious problem. We do not want the hard work of our localizers to be discarded. I wonder if a better solution would be to solve the underlying problem. The end result would be the same, but without one more feature for our team to maintain, without additional work from administrators, and without readers temporarily coming across a wrong translation.

(In reply to John Karahalis [:openjck] from comment #1) > Yes, this is a serious problem. We do not want the hard work of our > localizers to be discarded. > > I wonder if a better solution would be to solve the underlying problem. The > end result would be the same, but without one more feature for our team to > maintain, without additional work from administrators, and without readers > temporarily coming across a wrong translation. I would argue that no matter how hard you try, people are still going to occasionally translate content in the wrong place. We need to be able to move articles across locales. I agree however that we should try to help avoid the problem in the first place. But we'll never eradicate it.

This is probably quite complex to get it right. Most of the time (like today), the translation happens on the en-US page which has a fairly long history. We don't want just to move the page, because what we really want: 1) Revert the original page to its initial state and history state. 2) Create (by splitting) a new page, in another locale, with only one history entry, the one of the original users.

Do we want to actually handle this as page move? The info in comment 3 makes me think that locale corrections probably *aren't* actually page moves (in the normal sense) most of the time. We can probably work out some sort of assist UI for doing a copy of the incorrect translation into the right locale and reverting any existing wrong-locale page it overwrote, though, if that'd be useful.

(In reply to James Bennett [:ubernostrum] from comment #4) > Do we want to actually handle this as page move? The info in comment 3 makes > me think that locale corrections probably *aren't* actually page moves (in > the normal sense) most of the time. > > We can probably work out some sort of assist UI for doing a copy of the > incorrect translation into the right locale and reverting any existing > wrong-locale page it overwrote, though, if that'd be useful. I'd agree with that. Some sort of helper in transferring content to the right locale would help. Better might be if we have better tools to prevent translation-in-place. A good step is fixing the bug with the edit button on translated pages. Another would be if we could analyze the content of the article when saving and kick up a confirmation box if a non-trivial amount of non-English text is detected.

I think we should wait upon the effect of bug about the "Translate" button instead of an translated "Edit" button to see if this is still happening often. Also note that in some case a translation is already existing and we will need to deal with the merge anyway. Finally we can change the locale of a page in the admin panel, which deal with the case of a brand new page in a wrong locale. So I'm really tempted to recommend WONTFIXing this one.

(In reply to Jean-Yves Perrier [:teoli] from comment #6) > Finally we can change the locale of a page in the admin panel, which deal > with the case of a brand new page in a wrong locale. > > So I'm really tempted to recommend WONTFIXing this one. OK, agreed.