Media
2 items
Description
Translate Chinese web novel pages via Google Translate, with an anti-block layer for sites that fight translation. QidianTranslate translates Chinese web novel pages in place — built for sites like Qidian.com that actively block browser translation tools. WHY THIS EXTENSION Many novel sites use notranslate attributes and dynamic scripts to disable built-in browser translation. QidianTranslate defeats these blocks and translates the page anyway, using Google Translate. FEATURES • In-place translation — text is replaced right where it is; tables, bold text, links, and page layout stay fully intact • Anti-block layer — strips notranslate attributes and keeps re-applying the fix when the site tries to re-block dynamically • Instant "Show original" toggle — switch back with zero reload and zero network calls • Auto-translate per site — add your novel sites once and every chapter translates on load • Fast — a full chapter translates in seconds via batched requests • Local cache — revisited chapters and repeated menus/footers never re-download translations • Chinese auto-detect (Simplified and Traditional), with configurable target language PRIVACY No analytics, no telemetry, no third-party servers. Text goes browser → Google Translate → browser, and settings/cache stay in your local browser storage. Nothing else is collected or transmitted. HOW TO USE 1. Open a Chinese novel page 2. Click the 文 toolbar icon → "Translate this page" 3. Optionally tick "Auto-translate this site" so future chapters translate automatically Two heads-ups for the review process (from last time, now more relevant since you're actually publishing): 1. Privacy tab requirements — you'll need to fill in a single-purpose description ("Translates Chinese web novel pages using Google Translate"), justify each permission (storage = settings/cache, activeTab+scripting = translate current page, host permissions = run on novel sites + call Google's endpoint), and certify the data-use disclosures (you collect nothing). 2. <all_urls> will slow review — broad host permissions trigger extra scrutiny. If review stalls or rejects, narrowing content_scripts.matches to the domains you actually read on is the quickest fix
rating_count is the Chrome Web Store ratings count, not a written-review count.