Hi! i have to build an website with few pages. The website must be in 3 languages. So my question is the following: What is the best way to build such a website? Should i simply create folders for each language and just copy-past HTML files there with different translations? Or there are more clever and modern way to do that. Considering that website will be build without any framework, just HTML/CSS/JS and maybe some Jquery.
Hi, which one do you prefer and why?
I absolutely LOATHE WPML since it makes everything so SLOW and am looking for better alternatives.
Hi guys.
I want to start producing content about a certain topic in portuguese and spanish. What is the best way to regist the nomain? Keep in mind my website name could be read in spanish and portuguese.
A) Two separate websites www.cannabis.pt and www.cannabis.es or B) Same website www.cannabis.com/pt/ and www.cannabis.com/es/ ?
Thanks
I want to create a second language for my webshop, but I'd like some advice on which plugin you think is best. Some features I'm considering
- Some products aren't available for the second language, or are just plain different (we offer online courses), so I don't really see how cart synchronization could benefit us.
- I would ideally want full translation control. I don't want automated translations for the checkout page etc.
- I of course want to send emails in the customers language. I currently have a heavily customized email templates, would this be possible for two languages? So that there would be two email php files for each language?
The possible plugins are (I guess) WPML, polylang, weglot and translatepress. As far as I can see Polylang and weglot don't allow you to translate every part of your site.
What are your experiences and which plugin would you recommend (keeping the features mentioned above in mind)?
Thank you!!
I am trying to make a multilingual landing page but I am confused which approach would be best? Should I use API to fetch text and updated the site or something else would be appropriate. Site is in PHP so what would be best?
Greetings,
I'm trying to figure out what the best approach to creating a multilingual wordpress site really is. I'd like to see what the rest of already well-established people on this reddit thinks - what the impact and ratio of cost / usefulness / possible complications might be.
So far I've come to understand that these scenarios exist - and please correct me wherever I'm wrong :
-
Multisite
- Main language on root domain, with other languages on subfolders
- No additional cost for language plugins
- Some other plugins might not work properly on multisite
- Some other plugins might force you to buy single licenses for each sub-site
- Database might be heavier
- Might have trouble connecting all sides with hreflang for every particular element, thus might have issues with possible duplicate content
-
Single-installations for each language
- Main language on root domain, with other languages on subfolders
- No additional cost for language plugins
- If you're using paid plugins, you'll have to buy them for each site
- Might have trouble connecting all sides with hreflang for every particular element, thus might have issues with possible duplicate content
-
Single site with WPML / Translatepress / etc.
- Main language on root domain, with other languages on subfolders
- Cost for language plugin
- Hreflang issues should be nonexistent
- Might slow down site dramatically, not sure whether WPML or TranslatePress is better. Haven't tried WPML cause I read it is slow, however Translatepress seems to lack functionality and support by other plugins in general. Would love advice about WPML here
In the end it would seem that the most costly approach is the Single-installation for each language, as it would require licenses for each site if any other paid-plugin is used. If all plugins used are free, then this might be the cheapest approach - however would this be a wise approach?
I read rarely anything good about multisite, thus I'm not sure whether or not using it would be wise in this scenario. Would appreciate comments and experiences here. Critical plugins might not exist for multisite, so that presents a big thumbs down.
>Finally, the paid language plugin approach seems efficient and the price should be maintainable, but my biggest fear is the slowing down of the site. On the other hand, the logical part within me asks the following : Many people, thousands of websites use this appro
... keep reading on reddit β‘So this one's a bit subjective, especially once you consider what languages you are using Wikipedia to translate to and from (due mainly to widely varying total articles in a given language), but overall Wikipedia has given me the most accurate translations from one language to another. I'm also not talking about Wiktionary, another project under the Wiki Commons umbrella.
How does Wikipedia do this, you might ask? Well, if you look up something in Wikipedia, it's clear exactly what sense it's in, regardless of homonymy. In the English Wikipedia for example, (where ~ represents "<language-abbreviation>.wikipedia.org/wiki") ~/Bank goes to the page about the financial institution, while ~/Bank_(geography) goes to the geographical feature aside a river. On the left column you have direct links to their equivalents in other languages, so if I click on "Deutsch" on the ~/Bank page, it goes to ~/Bank on the German Wikipedia, while the same link on ~/Bank_(geography) goes to the German Wikipedia ~/Ufer!
I have almost completely forgone print and online dictionaries in favour of Wikipedia for this reason. It works best with nouns, obviously, but with a little bit of etymological and morphological knowledge, this can work for most words of other types, especially verbs and sometimes adjectives as well. It isn't a perfect system, but I'm far more confident that I'll get an accurate translation on Wikipedia, than I would get in more traditional dictionaries, especially poor quality ones which don't clarify senses of homonyms leading to ambiguity and poor translations. Even though Wikipedia is clearly not a dictionary, at least in the traditional sense, the way it's structured makes it function as the best and most accurate dictionary in the world!
