Topic on Help talk:Extension:Translate

Existing translations must be moved

5 comments • 15:59, 30 July 2018 5 years ago

5

Perhelion (talkcontribs)

I mean this is one of the main reasons why this extension not get wider used, because there is no function to do this simple time consuming work. Normally there exist already around 20 target subpages e.q. on Commons. So it's not fun to use it. Maybe use Extension:Replace Text.

Reply Edited 10:09, 22 July 2018 5 years ago

Perhelion (talkcontribs)

PS: Beside the fact we can't move any page under i18n/ if the page /i18n exists (so we must delete them first?).

EDIT: That was a very bad idea from me [[phab:T114592]] (<-- I love this flow)

Reply Edited 10:13, 26 July 2018 5 years ago

Nikerabbit (talkcontribs)

It is not clear whether you mean existing non-Translate translations (for that use Special:PageMigration) or renaming pages (use the move action), but both are supported with some known issues.

Reply 11:26, 29 July 2018 5 years ago

Perhelion (talkcontribs)

Thanks for answer, there is a serious problem on Template:Mozilla Public License/(after moving, which was unnecessary in my opinion too). I edited the /i18n subpage again to refresh the ext.translate (bot), and now any language got overwritten with English (I guess restoring the "bot deletion" was a very bad idea). I really do not feel like re-entering each language manually. An undo of Move or something would be very good!? PS:Maybe a detailed documentation, what is going wrong here, would be good too.

PS: I trying the Special:PageMigration thing, but I got an JS error on the page (nothing happen). I guess it comes from "mediawiki.searchSuggest" (Uncaught TypeError: Cannot read property 'indexOf' of undefined)

Reply Edited 06:44, 30 July 2018 5 years ago

Nikerabbit (talkcontribs)

I'll look into these errors later when I have time. Perhaps there is easy way to restore the translations.

Reply 15:59, 30 July 2018 5 years ago

Reply to "Existing translations must be moved"