Skip to content
This repository has been archived by the owner on Feb 1, 2023. It is now read-only.

Internationalization support #78

Open
disturbio opened this issue Oct 15, 2016 · 2 comments
Open

Internationalization support #78

disturbio opened this issue Oct 15, 2016 · 2 comments

Comments

@disturbio
Copy link

Hi,

First congratulations on the attempt to simplify tasks inside an organization, until now seems like a good idea.

But to reduce more the friction between the non-english speaking world users, it would be very good to have i18n features so my organization could use it and we could share the translations with the rest of the world.

Thanks for your work,

in solidarity,
g.

@micahflee
Copy link
Contributor

Completely agree, this is a great request.

@micahflee micahflee added this to the 0.1.2 milestone Nov 18, 2016
@micahflee micahflee modified the milestones: 0.1.2, 0.1.3 May 23, 2017
@micahflee micahflee modified the milestones: 0.1.3, 0.2.1 Jun 22, 2018
@micahflee micahflee modified the milestones: 0.2.1, 0.3.1 Oct 15, 2018
@micahflee micahflee modified the milestones: 0.3.1, 0.3.2 Feb 21, 2019
@nebulak
Copy link

nebulak commented May 7, 2019

Hi,

if no one is already working on this, I will start an implementation using python's gettext. Reasons for using python's gettext are:

  • Uses common translation file formats (.pot & .po files)
  • Easy to implement with no additional dependencies outside of python's standard library
  • Readable translation file format for non technical users, that want to help translating.

If that plan sounds good to you, I will start and send a pull request when finished.

@micahflee micahflee removed this from the 0.3.2 milestone Nov 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants