| 1 |
=== wpLingua === |
| 2 |
Contributors: wpr0ck, lyly13 |
| 3 |
Donate link: https://wplingua.com/ |
| 4 |
Tags: translation, translate, autotranslate, autotranslation, multilingual, multilingual website, localization |
| 5 |
Requires at least: 5.0 |
| 6 |
Tested up to: 6.4 |
| 7 |
Stable tag: 1.0.5 |
| 8 |
Requires PHP: 7.4 |
| 9 |
License: GPLv2 or later |
| 10 |
License URI: http://www.gnu.org/licenses/gpl-2.0.html |
| 11 |
|
| 12 |
Make your websites multilingual and translates them automatically: no word limits, free first language, SEO-friendly, no coding knowledge needed and more! |
| 13 |
|
| 14 |
== Description == |
| 15 |
|
| 16 |
**An all-in-one solution that makes your websites multilingual and translates them automatically, without word or page limits.** |
| 17 |
|
| 18 |
The highlights: |
| 19 |
|
| 20 |
✓ a free first language |
| 21 |
✓ an on-page visual editor for editing translations |
| 22 |
✓ a customizable language switcher |
| 23 |
✓ search engine optimization (SEO) |
| 24 |
✓ no coding knowledge needed |
| 25 |
✓ self-hosted data |
| 26 |
✓ open source, find [wpLingua on GitHub](https://github.com/julien-jacob/wplingua) |
| 27 |
✓ and more! |
| 28 |
|
| 29 |
### 🔥 One free target language ### |
| 30 |
With our complimentary offer, wpLingua empowers you to introduce your website to a broader audience in a new language. |
| 31 |
|
| 32 |
**While the free version supports translation into a single target language**, we set no boundaries on the number of words you can translate. |
| 33 |
|
| 34 |
Whether your site has a hundred pages or just a few, you can seamlessly make it accessible in the language you desire. |
| 35 |
|
| 36 |
###🪄 Streamlined Setup Process ### |
| 37 |
Dive into a hassle-free multilingual experience with wpLingua. Forget about complex configurations and the intimidating world of coding. |
| 38 |
|
| 39 |
All you need to get started is to request your complimentary API key. Once you do, we'll promptly send it straight to your inbox. It's as straightforward as that! |
| 40 |
|
| 41 |
Our commitment is **to make multilingual capabilities accessible and effortless for every WordPress user**. |
| 42 |
|
| 43 |
Let us take care of the technicalities while you focus on creating captivating content for your global audience. |
| 44 |
|
| 45 |
### 🚀 Optimized for international search engines (SEO) ### |
| 46 |
When you use wpLingua on your website, all elements of your content - even those that are invisible - are translated. |
| 47 |
|
| 48 |
wpLingua is "SEO-Friendly" because it takes care of translating: |
| 49 |
|
| 50 |
✓ Meta Title tags |
| 51 |
✓ Meta Description tags |
| 52 |
✓ Hreflang alternative links |
| 53 |
✓ Meta tags for social networks (Twitter X, OpenGraph Facebook...) |
| 54 |
✓ ALT attributes of images |
| 55 |
✓ And more. |
| 56 |
|
| 57 |
By optimizing indexing, we ensure that your translated pages are not only understood by your audience, but are also easily found by search engines. |
| 58 |
|
| 59 |
### ✍️ Tailor-made translations at your fingertips with our On-Page Editor ### |
| 60 |
Although wpLingua gives you the convenience of **machine translations**, we understand the nuances of each language. |
| 61 |
|
| 62 |
wpLingua offers a canvas in which you can **refine each translation** so that it resonates with your unique voice and your brand message adapted to the cultural and contextual expectations of your audience. |
| 63 |
|
| 64 |
Experience the fusion of automation and the personal touch with our **visual on-page editor**. |
| 65 |
|
| 66 |
### 🎨 Fully customizable language switcher ### |
| 67 |
The wpLingua language selector is fully customizable. You can display the language switcher in two ways: |
| 68 |
|
| 69 |
✓ Automatic insertion via predefined positions |
| 70 |
✓ Use of a shortcode to display it wherever you want |
| 71 |
|
| 72 |
You can also control the appearance of the language switcher using: |
| 73 |
|
| 74 |
✓ Switcher styles (dropdown, online, block...) |
| 75 |
✓ Predefined themes (light, dark, chameleon, etc.) |
| 76 |
✓ Configurable language names (translated name, original name, language ID, etc.) |
| 77 |
✓ Flag shapes (round, rectagle, wavy) |
| 78 |
✓ Language-based flag choices or import your own flag images |
| 79 |
✓ Adding custom CSS in a dedicated insert |
| 80 |
|
| 81 |
With all these customization options, there's no way your site's language selector will look like any other! |
| 82 |
|
| 83 |
### 🧭 Intuitive possibilities to exclude certain translations ### |
| 84 |
Navigate the complexities of website translation with wpLingua's intelligent exclusion feature. |
| 85 |
|
| 86 |
Want to preserve specific sections of a page in its original language? Our system seamlessly allows you to pinpoint and **exclude translations using CSS selectors**. |
| 87 |
|
| 88 |
If entire pages need to remain untouched, effortlessly exclude them by their URL. All of this can be managed with ease through our user-friendly exclusions manager. |
| 89 |
|
| 90 |
With wpLingua, you're always in command of what gets translated and what doesn't, ensuring your site's essence remains intact. |
| 91 |
|
| 92 |
### ⚡️ The wpLingua API ### |
| 93 |
The wpLingua plugin relies on our own wpLingua API, an integrated third-party service, to provide its machine translation functionality. The call to this Third Party Service (wpLingua API) is made when creating an API key from the plugin, during API key verification and when your site requests a new automatic translation (new texts discovered on a page web or request automatic translations from the translation edition). We invite you to consult our [Terms & Conditions page](https://wplingua.com/terms-and-conditions/) for more information. |
| 94 |
|
| 95 |
|
| 96 |
== Installation == |
| 97 |
|
| 98 |
1. Download the plugin zip file and install it via the WordPress interface, or upload it directly to your plugins directory. |
| 99 |
2. Activate wpLingua from your plugins page. |
| 100 |
3. Navigate to the wpLingua settings to get your free API key and to set up your language preferences. |
| 101 |
4. Start translating your content! |
| 102 |
|
| 103 |
== Frequently Asked Questions == |
| 104 |
|
| 105 |
= What languages are available for translation?= |
| 106 |
For the moment the available languages are: |
| 107 |
|
| 108 |
* English |
| 109 |
* French |
| 110 |
* German |
| 111 |
* Italian |
| 112 |
* Japanese |
| 113 |
* Portuguese |
| 114 |
* Simplified Chinese |
| 115 |
* Spanish |
| 116 |
|
| 117 |
If you need a language, let us know using the [contact form available on our website](https://wplingua.com/contact/), we add languages as we go. |
| 118 |
|
| 119 |
= What languages are available in the plugin administration? = |
| 120 |
At the moment, the plugin is available in English, French, German, Italian, Spanish and Portuguese. If you want to help us translate it into more languages, don't hesitate! |
| 121 |
|
| 122 |
= Is it compatible with page builders? = |
| 123 |
Yes, wpLingua is designed to work seamlessly with most popular page builders. |
| 124 |
|
| 125 |
= How it works? = |
| 126 |
wpLingua intercepts page content and analyzes HTML and JS code. It discovers all texts, translates them and makes the pages multilingual. This approach ensures compatibility with most themes, plugins and page builders such as Gutenberg, Elementor, Divi… |
| 127 |
|
| 128 |
= Is it possible to edit translations manually? = |
| 129 |
Of course ! Simply activate the **translation editor** on the page to make your changes. |
| 130 |
|
| 131 |
= What is the translated word limit? = |
| 132 |
wpLingua does **not limit the translation of the number of words**. |
| 133 |
|
| 134 |
= Is wpLingua compatible with WordPress Multisite? = |
| 135 |
No, wpLingua is not compatible with WordPress Multisite |
| 136 |
|
| 137 |
= Is wpLingua compatible with caching plugins? = |
| 138 |
Quite ! And it's even recommended to cache your pages and translations to improve site loading and performance. |
| 139 |
|
| 140 |
= Is there a Gutenberg block or Divi/Elementor widget to easily display the language switcher? = |
| 141 |
No, not at the moment but in the meantime, you can easily display the language switcher wherever you want using our shortcode provided for this purpose. Simply copy and paste this shortcode where you want: **[wplng_switcher]** |
| 142 |
|
| 143 |
== Screenshots == |
| 144 |
|
| 145 |
1. Once the plugin is downloaded, installed and activated, register your API key. |
| 146 |
2. As soon as your API key has been registered, your site is multilingual. This option screen allows you to configure your languages and their flags, as well as activate the functionalities. |
| 147 |
3. Customizing the language switcher, enable or disable auto-insertion + choose position or use the shortcode. |
| 148 |
4. You have the possibility to exclude pages or parts of pages. |
| 149 |
5. If you need, you can edit a translation directly from your pages using our visual editor. |
| 150 |
6. You can access the list of translations present on a page, including those which are not directly visible (Meta SEO, texts, alternative images, title attributes, etc.) |
| 151 |
7. You can edit all translations of your website. |
| 152 |
8. All translations are stored on your WordPress site. |
| 153 |
|
| 154 |
== Changelog == |
| 155 |
|
| 156 |
= 1.0.5 = |
| 157 |
|
| 158 |
* Translate meta twitter:description |
| 159 |
* New shortcode: wplng_only |
| 160 |
* Add message when plugin is activated but not configured |
| 161 |
* Fix arrow on switcher (theme: switcher, style: dropdown) |
| 162 |
|
| 163 |
= 1.0.4 = |
| 164 |
|
| 165 |
* Better JSON translation |
| 166 |
* Better JSON debug mode |
| 167 |
* New AJAX debug mode |
| 168 |
* Better register form |
| 169 |
* Better readme.txt and README.md files |
| 170 |
* Fix editor link class attributes |
| 171 |
* Fix error on URL translation (backslash on domain name) |
| 172 |
* Fix bad JS on translated page |
| 173 |
|
| 174 |
= 1.0.3 = |
| 175 |
|
| 176 |
* Prepare SVN folders |
| 177 |
|
| 178 |
= 1.0.2 = |
| 179 |
|
| 180 |
* Fix error on API key register |
| 181 |
|
| 182 |
= 1.0.1 = |
| 183 |
|
| 184 |
* Review code |
| 185 |
* Review shortcode |
| 186 |
* Review some texts and HTML |
| 187 |
* Update plugin translations |
| 188 |
* Add default excluded element for translation : code |
| 189 |
* Add default excluded element for editor links : option |
| 190 |
* CSS: Better switcher margin |
| 191 |
* CSS: Hover effect for link’s editor |
| 192 |
* Better flags in admin |
| 193 |
|
| 194 |
= 1.0.0 = |
| 195 |
|
| 196 |
* **Options pages** |
| 197 |
* Register |
| 198 |
* Set API key |
| 199 |
* Request API key |
| 200 |
* Settings |
| 201 |
* Original language |
| 202 |
* Target languages |
| 203 |
* Features |
| 204 |
* API key |
| 205 |
* Switcher |
| 206 |
* Theme (20) |
| 207 |
* Style (Dropdown / List / Block) |
| 208 |
* Language name (Untranslated name / ID / None) |
| 209 |
* Custom CSS |
| 210 |
* Auto insert |
| 211 |
* Exclusions |
| 212 |
* Exclude HTML elements by selector |
| 213 |
* Exclude URLs by regex |
| 214 |
|
| 215 |
* **Translation post type** |
| 216 |
* Edit translation |
| 217 |
* Status: Generated or Edited |
| 218 |
* Re-generate translation |
| 219 |
|
| 220 |
* **Translate webpage** |
| 221 |
* Text node (p, span, …) |
| 222 |
* Attribute (alt, title, …) |
| 223 |
* Dir attribute (ltr or rtl) |
| 224 |
* Body class (dir and language ID) |
| 225 |
* JS / JSON (Text / HTML / URL / Language ID) |
| 226 |
* AJAX (HTML / JSON) |
| 227 |
* Add links alternate hreflang |
| 228 |
|
| 229 |
* **On page : Visual editor** |
| 230 |
* **On page : Translations list** |
| 231 |
* **On page : Admin bar** |
| 232 |
* Access visual editor |
| 233 |
* Access all translation on current page |
| 234 |
* Access exclusion option if current page is excluded |
| 235 |
|
| 236 |
* **Feature : Search from translated page** |
| 237 |
* **Shortcode** |
| 238 |
* wplingua-switcher |
| 239 |
* wplingua-notranslate |
| 240 |
|
| 241 |
* **Plugin translation** |
| 242 |
* French |
| 243 |
* Portuguese |
| 244 |
* Spanish |
| 245 |
|
| 246 |
|
| 247 |
== Upgrade Notice == |
| 248 |
|
| 249 |
= 1.0.0 = |
| 250 |
First release. Be sure to set up your preferences after installation. |
