Open any page on your site, click \"Translate this page\" in the admin bar, choose a\ntarget language, and either auto-translate every visible string (via a free\nmachine-translation service) or edit translations by hand while seeing the page\nupdate live.<\/p>\n\n
Saved translations are rendered server-side into the HTML response (SEO-friendly:\nno flash of untranslated text, and hreflang alternates in the head), and visitors\nswitch languages via a link-based switcher (bottom-right).<\/p>\n\n
Developed by Ricardo Sawir for Sawir Studio LLC.<\/p>\n\n
URLs use a language path prefix, e.g. \/es\/about for Spanish, \/about for the source\nlanguage (which stays canonical, un-prefixed). Language is resolved in this order:\n\/es\/ path \u2192 ?lang=es \u2192 saved cookie \u2192 browser Accept-Language \u2192 source. Root and\nprefix-less URLs auto-detect the visitor's browser language without redirecting\n(a Vary header is sent so shared caches behave).<\/p>\n\n
Note: language path prefixes assume a root-domain install and no top-level page\nwhose slug is a two-letter language code.<\/p>\n\n
This plugin's optional \"Auto-translate\" feature (admin-only, triggered manually\nby clicking an Auto-translate\/Translate button) sends the source text strings\nand the chosen language pair to the MyMemory translation API\n(https:\/\/mymemory.translated.net\/) to fetch machine translations. The request\nis made from the administrator's browser only when they click the button; no\nvisitor data is ever sent, and nothing is sent automatically.<\/p>\n\n
Developers can swap the provider \u2014 see \"Custom translation provider\" below.<\/p>\n\n
On a translated request the plugin switches WordPress's locale to the target\nlanguage, so dates (month\/day names) and any installed<\/em> core, theme, and plugin\ntranslations render natively \u2014 the string map only covers the rest.<\/p>\n\n For this to have visible effect the language pack must be installed. The easiest\nway is Settings \u2192 General \u2192 Site Language: pick and save the language once (which\ndownloads its pack), then switch back to your source language. Languages without\nan installed pack still work for content translation; only native dates\/strings\nare skipped. Map codes to custom WP locales with the 'sawir_lt_wp_locale' filter.<\/p>\n\n Settings \u2192 Live Translate \u2192 \"Scan site now\" crawls your published pages, posts,\nand public archives to discover every translatable string up front (batched, with\na progress indicator). Discovered strings then appear in the \"Edit all site\nstrings\" section right below, where you can pick a language and translate, auto-\ntranslate, or bulk-import the whole site at once instead of page by page. Note:\nmachine translation is still rate-limited by the free service, so for large sites\nuse Bulk edit to export and translate elsewhere.<\/p>\n\n Multisite-aware. Each subsite has its own settings and its own translations table,\nconfigured independently. Tables are created on network activation, when a new\nsubsite is created, and lazily on first admin visit; uninstall cleans every site\non the network.<\/p>\n\n Turn off \"Built-in switcher\" in settings and render your own anywhere in your\ntheme using sawir_lt_switcher_links(), which returns the language links for the\ncurrent page:<\/p>\n\n Each item is ['code','name','url','active','is_source'] (code is '' for the\nsource language). sawir_lt_current_lang() returns the active language code.<\/p>\n\n Auto-translate uses the free MyMemory API by default. To use your own provider\n(DeepL, Google, a local model, ...), reassign window.SawirLT.translate from a\nscript enqueued after the 'sawir-lt-walk' handle. Signature: it receives the\nsource text and the two language codes, and returns a Promise resolving to the\ntranslated string. Every auto-translate path (in-page editor and admin bulk\ntranslate) routes through it.<\/p>\n\n provider.js:<\/p>\n\n The plugin's own admin\/UI text is translation-ready (text domain\n\"sawir-live-translate\"). A .pot template ships in \/languages \u2014 drop your\n.po\/.mo there or under wp-content\/languages\/plugins\/. (The in-page editor's\nJavaScript labels are not yet localized.)<\/p>\n\nScan site for strings<\/h3>\n\n
Multisite<\/h3>\n\n
Custom switcher<\/h3>\n\n
<?php if ( function_exists( 'sawir_lt_switcher_links' ) ) : ?>\n <ul class=\"my-lang-switcher\">\n <?php foreach ( sawir_lt_switcher_links() as $l ) : ?>\n <li>\n <a href=\"<?php echo esc_url( $l['url'] ); ?>\"<?php echo $l['active'] ? ' aria-current=\"true\"' : ''; ?>>\n <?php echo esc_html( $l['name'] ); ?>\n <\/a>\n <\/li>\n <?php endforeach; ?>\n <\/ul>\n<?php endif; ?>\n<\/code><\/pre>\n\nCustom translation provider<\/h3>\n\n
add_action( 'admin_enqueue_scripts', 'myprefix_lt_provider' );\nadd_action( 'wp_enqueue_scripts', 'myprefix_lt_provider' );\nfunction myprefix_lt_provider() {\n if ( wp_script_is( 'sawir-lt-walk', 'registered' ) ) {\n wp_enqueue_script( 'myprefix-lt-provider',\n plugins_url( 'provider.js', __FILE__ ),\n array( 'sawir-lt-walk' ), '1.0.0', true );\n }\n}\n<\/code><\/pre>\n\nwindow.SawirLT.translate = function ( text, source, target ) {\n return fetch( 'https:\/\/example.com\/translate', {\n method: 'POST',\n body: JSON.stringify( { text: text, from: source, to: target } )\n } ).then( function ( r ) { return r.json(); } )\n .then( function ( j ) { return j.translation; } );\n};<h3>Translations<\/h3>\n<\/code><\/pre>\n\nOther plugins by Sawir Studio<\/h3>\n\n
\n
1.0.0<\/h4>\n\n
\n