Summary
Adding translations to our projects makes them usable in more places by more people which, ultimately, makes them more valuable. Managing the localization process can be difficult if you don’t have the right tools, so this week Michal čihař tells us about the Weblate project and how it simplifies the process of integrating your translations with your source code.
Brief Introduction
- Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
- I would like to thank everyone who has donated to the show. Your contributions help us make the show sustainable.
- When you’re ready to launch your next project you’ll need somewhere to deploy it. Check out Linode at linode.com/podcastinit and get a $20 credit to try out their fast and reliable Linux virtual servers for running your awesome app.
- You’ll want to make sure that your users don’t have to put up with bugs, so you should use Rollbar for tracking and aggregating your application errors to find and fix the bugs in your application before your users notice they exist. Use the link rollbar.com/podcastinit to get 90 days and 300,000 errors for free on their bootstrap plan.
- Visit our site to subscribe to our show, sign up for our newsletter, read the show notes, and get in touch.
- To help other people find the show you can leave a review on iTunes, or Google Play Music, and tell your friends and co-workers
- Join our community! Visit discourse.pythonpodcast.com for your opportunity to find out about upcoming guests, suggest questions, and propose show ideas.
- Your host as usual is Tobias Macey and today I’m interviewing Michal Čihař about Weblate
Interview with Michal Čihař
- Introductions
- How did you get introduced to Python?
- Can you explain what Weblate is and the problem that you were trying to solve by creating it?
- What are the benefits of using Weblate over other tools for localization and internationalization?
- One of the advertised features of Weblate is integration with git and mercurial. Can you explain how that works and what a typical translation workflow looks like both for a developer and a translator?
- Given that part of the focus for the tool is to allow for community translation, how do you simplify the experience for first time contributors?
- I understand that Weblate is written as a django application. Is it possible to use Weblate with other Web frameworks or non-web projects?
- Can this be used with projects implemented in other programming laguages? Are there any capabilities that are lot in this scenario?
- Why should developers and product managers be concerned with localizing an application? How does Weblate help to reduce the level of investment necessary for such an undertaking?
- What are some of the biggest difficulties that you have encountered while building and maintaining Weblate?
- What are the most common problems that you see people encounter on both the translator and developer side when dealing with internationalization and localization?
Keep In Touch
Picks
- Tobias
- Michal
Links
The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA
Activity