Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n #72

Closed
HalosGhost opened this issue Oct 11, 2016 · 6 comments
Closed

i18n #72

HalosGhost opened this issue Oct 11, 2016 · 6 comments
Milestone

Comments

@HalosGhost
Copy link
Owner

HalosGhost commented Oct 11, 2016

pbpst has come a long way and, in my opinion, is pretty well feature-complete (though others may very well convince me otherwise).

However, we still hard-code English and offer no utility for internationalization. In pacman's tradition (as we tend to try to follow), I would like to offer, at least, the opportunity for i18n through gettext.

This is not a small undertaking, and I would not be able to offer the translations themselves, but we could at least offer the possibility.

@tmplt
Copy link
Contributor

tmplt commented Oct 18, 2016

I'm able to offer translations to Swedish.

@HalosGhost
Copy link
Owner Author

HalosGhost commented Oct 18, 2016

Wonderful! I have just gotten my first test with gettext functional, so I will begin the process of converting the whole program over to gettext Soon™.

@HalosGhost
Copy link
Owner Author

Okay, most of the light lifting is done now. Unsurprisingly, some of strings we use for printing (both diagnostics and errors) are more complicated, so they cannot be so easily converted to gettext() calls. I will need to figure out a way to simplpify these to a format that is more conducive to translation.

And, finally, the usage output will need to be translateable as well. I have a plan for them too, but they will take a bit of time for this refactor.

@HalosGhost
Copy link
Owner Author

HalosGhost commented Nov 5, 2016

All right; the help output should be fully functional at this point, so there are only two tasks left for this to be finished:

  • make error messages throughout more consistent (e.g., "Failed to" vs "Could not")
  • convert the more complex output messages to use gettext

@HalosGhost
Copy link
Owner Author

All right, this is preliminarily complete. Now I just need to add the necessary pieces to the build, install and uninstall steps so that contributed translations are built and installed properly.

@HalosGhost
Copy link
Owner Author

HalosGhost commented Nov 8, 2016

via 92e9e91, I cam considering this issue complete.

To contribute, see the wiki page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants