(I’ve turned this post into a wiki post so anyone with a registered account can add to it by clicking edit.)
I’ve contacted Localisation Lab who are a well-respected and very experienced localisation and translation community for suggestions, advice on where to host Hypha localisation.
They have lots of experience and most importantly involve the communities and language speakers in the process. I’ve invited them to join we.hypha.
What we should localise
Here’s my starter-proposal of what localisation we should support:
- the ability for the “internal user” to choose what language Hypha is displayed in
- language of UI text labels, interactive elements (buttons, check-boxes, dropdowns, etc )
- language of terminology used in Hypha; e.g. contract/grant/
- the translation of the forms that applicants will use to apply for funding
- others?
The following:
- date and time
- number formats
- currencies
are localised by editing base.py file
Infrastructure possibilities
Most Open Source projects seem to use either Transifex, or Weblate (either self-hosted or hosted.weblate.org).
Which they choose is a decision based on factors like: we want to use 100% FOSS/decentralised/self-hosted/make it easier and host on paid platform.
Practicalities of choosing infrastructure options
Below are the functions I think are most important for our translation work and how they compare across each option.
Weblate hosted “Basic”
Software price: €80 per month or €199 per year
Number of source strings: 1,000
Translation projects: 1
Target languages: 15
Number of translators: unlimited
Translation components: unlimited
Transifex “Basic”
Software price: €19 per month or €840 per year
Number of source strings: 50,000
Translation projects: unlimited
Target languages: 15
Number of translators: 20
Translation components: unlimited
Weblate Self-hosted
Software price: free (open source)
Number of source strings: unlimited
Translation projects: unlimited
Target languages: unlimited
Number of translators: unlimited
Translation components: unlimited
Decision
We’ve decided on using Weblate’s Basic service as:
- we have only 1 (at the moment!)
- a small number of strings to translate (~less then 1,000 strings)
- Weblate is used by many FOSS projects
- it gets thumbs up from the Localisation Lab community
- it is open source software itself
If we find that we need to translate more strings, then we can go up to the next level.