Learn More
Resend Email
0
piratefox
5y

I am lately working on a Wordpress website (ouch, pain) for a friend as a side project and it is supposed to be multilingual. No problem, there are some plugins for it and thanks to one of my previous rants I found out the _e() function (still a stupid af name).

But I was wondering: given that I’ll have a lot of translations in some template pages in the theme, what is the standard way to do it? I have a couple of solutions in mind:

- single Po/mo files for every page
- as above, but with a script to merge the Po(s) before making the mo

Am I missing something obvious?
I was told to just use one po, but it sounds like hell to organise

question

wordpress

php

localization
Favorite
Ranter
Comments
  • 0
    5y
    google

    i18n WordPress
  • 0
    5y
    @heyheni if you read carefully you will find out I ask what is the standard way to do it, not which tool to use. (I even mention Po/mo files)
  • 0
    5y
    To give a context on why I ask this: I am not sure if I’ll be the one maintaining their website and I want to make the work for the next guy as little painful as possible, therefore I would like to to keep it as close to industry standard as reasonable.
  • 0
    5y
    Just use Translate Press or Polylang.
  • 0
    13d
    Yeah, I'd stick with a single PO unless the project is absolutely huge. Splitting everything by page sounds nice at first, but keeping it all synced later can become a bigger headache. I've been dealing with multilingual app files recently, and using Wordzilla to manage JSON/XLIFF translations has been way less painful than editing everything manually. If you're also looking beyond the usual tools, it's worth checking out as a Crowdin alternative - Wordzilla https://wordzilla.io/en-US/ . Curious to see what other WordPress devs here prefer for larger projects.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment