⬇ Download TranslateRocket v0.10.0
.zip · WordPress 5.6+ · PHP 7.4+ · GPLv2 · WordPress.org द्वारा सेवा प्रदान की गई
एक मिनट में इंस्टॉल करें
- अपने वर्डप्रेस एडमिन में जाएं प्लगइन्स → नया जोड़ें और खोजें TranslateRocket - या डाउनलोड किए गए ज़िप को अपलोड करें प्लगइन अपलोड करें.
- क्लिक अब स्थापित करें.
- सक्रिय करें, खोलें TranslateRocket → सेटिंग्स, अपनी भाषाएँ चुनें - हो गया।
What’s new in 0.10.0
- New: import from the qTranslate family — qTranslate-X, qTranslate-XT, WPGlobus and WP Multilang. These keep every language inside the post itself, separated by markers, so the translations are read from your posts and not from the other plugin's tables: the import works even on sites whose plugin was deactivated or deleted years ago, which is the usual case for qTranslate. All four marker styles are recognised, including the HTML-escaped one. Titles, excerpts and body text come across; a post with no section in your source language is left alone rather than guessed at.
किसी अन्य प्लगइन से आ रहा है? प्रवासन मार्गदर्शिकाएँ: WPML · TranslatePress · Polylang.
प्रश्न या बग? की ओर जाना सहायता - असली इंसान जवाब देते हैं।
📦 चेंजलॉग
सक्रिय रूप से विकसित - सबसे पहले जो भेजा गया वह यहां है।
v0.10.0
- New: import from the qTranslate family — qTranslate-X, qTranslate-XT, WPGlobus and WP Multilang. These keep every language inside the post itself, separated by markers, so the translations are read from your posts and not from the other plugin's tables: the import works even on sites whose plugin was deactivated or deleted years ago, which is the usual case for qTranslate. All four marker styles are recognised, including the HTML-escaped one. Titles, excerpts and body text come across; a post with no section in your source language is left alone rather than guessed at.
v0.9.9
- Change: on a phone the "translate in this browser" button is now shown but switched off, instead of hidden. Chrome and Edge only carry the on-device translator on a desktop, so the button cannot work there — but hiding it meant nobody browsing from a phone knew the feature existed at all. Tapping it now explains where to use it, and the copy-and-paste route beside it still works on a phone.
v0.9.8
- Fix: a browser translation run could reach the end of the progress bar having saved almost nothing. Chrome sometimes discards the on-device translator while a long run is going; from that moment every remaining phrase failed, silently. Measured on a 58-phrase page: 5 translated and 53 failed. The translator is now rebuilt on the first failure and the phrase retried, so the same run finishes 57 of 58 even when the browser drops it eleven times. On the bulk page the counter used to freeze ("Translating 5 of 498...") for the rest of the run; it now keeps going.
v0.9.7
- Fix: the "translate in this browser" button was offered on phones, where it cannot work — the browser translation API only exists on desktop Chrome and Edge. It showed up in the visual editor toolbar, in the phrase popup and on the bulk page, and tapping it got you nothing. The button is now hidden on phones and tablets; on the bulk page the copy-and-paste route stays available, since that one works everywhere.
v0.9.6
- Fix: on a phone, four of the plugin's nine screens ran off the side and the last columns of the tables were simply gone — progress per language, the list of pages, the AI summary. Measured at 390 pixels they overflowed by 116 to 220 pixels. The tables now use less padding and a smaller type on narrow screens, and whatever still does not fit scrolls inside the table itself instead of pushing the whole page sideways.
v0.9.5
- Fix: on a phone, the line that tells you which language your site is written in ran off the right edge of the toolbar, cut in half. It is the sentence that makes the whole bar make sense, so it now gets a row of its own and wraps like ordinary text instead of being clipped.
v0.9.4
- Fix: on a phone the editor toolbar had to be dragged sideways to reach its own buttons — with four languages and the controls it ran past a thousand pixels inside a screen of under four hundred. It now wraps onto as many rows as it needs, and the page below shifts by the toolbar's real height instead of a fixed 46 pixels.
- Change: the Live Preview demo is built for phones too — the cover text no longer sits on top of the photo, where it overflowed the frame and clipped the title and the second button.
v0.9.3
- New: the translator built into Chrome and Edge is now offered on the single phrase too, in the popup of the visual editor — next to Google Translate and "Translate with AI". It was already there for a whole page and for a whole language; the one place it was missing was the one you are looking at while you correct a single line. No key, and the phrase never leaves your computer.
v0.9.2
- Fix: after translating in the browser from the bulk screen, the table underneath still showed the old "0 translated" figures. The message said to reload the page, but the numbers sitting right below it said the opposite — so the work looked like it had gone nowhere. It had not: the translations were saved all along. The screen now refreshes its own totals when it finishes.
- Change: the plugin's description on WordPress.org now leads with the thing that makes it unusual — that Chrome and Edge can translate the whole site on your own computer, with no key, no account and nothing sent anywhere.
- Change: the Live Preview demo is a proper hotel landing page now, not a stack of paragraphs.
v0.9.1
- New: the visual editor can now translate a whole page with the translator built into Chrome and Edge — the same engine the bulk screen has had since 0.8.9, which until now was missing from the one place you are most likely to be standing when you want it. It needs no key and no account, the text never leaves your computer, and the button only appears where the browser can actually do it.
- Fix: the "Translate page" panel always showed an empty grey strip in the middle. It was the progress bar, which is marked hidden but was being shown anyway by one of the editor's own style rules — the same trap that had "Back" and "Finish" visible on the wizard's first step.
- Change: when no AI key is set, the panel no longer just says "add a key, meanwhile use copy-paste". If the browser can translate, it offers to do it.
v0.9.0
- New: ask for help without leaving WordPress. The Diagnostics screen now carries a form that opens a support ticket straight from your site — the technical report goes with it if you want, the answer comes back to you by email, and you can follow the whole thread from a link. Nothing is sent until you press the button, and the page shows you exactly what leaves. If your site cannot be reached from the outside, it says so and points you at the ordinary support page instead.
- New: the three ways to translate now sit side by side on the Translations screen — scan the site for text, hand the whole language to the AI, or let Chrome and Edge do it for free. Each page in the list also gained its own one-click AI button next to Translate, so a single page can be filled in without touching the rest.
- Fix: the setup wizard showed "← Back" and "Finish & start translating" on the very first step, next to "Next →". They were meant to be hidden; WordPress's own button styling was overriding the browser's hidden attribute, so all three were on screen at once.
- Fix: the welcome notice appeared on top of the setup wizard telling you to go elsewhere to pick your languages — which is what the wizard was already asking you to do. It now stays out of the way there, and elsewhere it points at the wizard until you have been through it.
- Fix: the Translations screen counted only the strings already queued for the language you were looking at, so a freshly added language could read "0 still to translate out of 0 detected" while the site was full of untranslated text.
v0.8.9
- New: translate without an API key at all. Chrome and Edge on a computer carry a translator that runs on the device itself, and the bulk screen can now drive it: install the plugin, pick your languages, press the button. It costs nothing, needs no account, and the text never leaves the machine. Quality sits below DeepL and the AI models and it works one phrase at a time, so it is the fastest way to a translated site rather than the best one — and everything it translates is kept, so adding a provider later never repeats the work. It needs a desktop Chrome or Edge and an admin served over https. Where that is not the case — Firefox, Safari, a phone, an admin on plain http — the same panel now says so and points at the copy-and-paste round trip instead, which works in any browser and still needs no key.
