Translation and 2.0beta2 I will release soon the 2.0beta2 version. We need your help to finish translation. To help us, go on
seen from China

seen from Malaysia

seen from United States
seen from Russia
seen from United States

seen from Russia

seen from Malaysia
seen from United States
seen from Germany
seen from China
seen from China
seen from United States
seen from Portugal
seen from United States
seen from Canada

seen from United States
seen from United States
seen from Canada

seen from United States
seen from United States
Translation and 2.0beta2 I will release soon the 2.0beta2 version. We need your help to finish translation. To help us, go on
Traducing PyFreeBilling for 2.0
Traducing PyFreeBilling for 2.0
The 2.0 beta version of PyFreeBilling has been published. As there are new features, new sentences have to be traduced. To be more effective, i migrate the traducing system to Transifex and invited the actual traducers to join the team. If you want to traduce or review, go here : https://www.transifex.com/celea-consulting/pyfreebilling/dashboard/ (The last service is no more in use). For the time…
View On WordPress
Θέλω να μεταφράσω προγράμματα ΕΛΛΑΚ, αλλά δεν ξέρω που και πως...
Θέλω να μεταφράσω προγράμματα ΕΛΛΑΚ, αλλά δεν ξέρω που και πως…
Έστω ότι χρησιμοποιήσατε κάποιο πρόγραμμα ΕΛΛΑΚ και είτε σας άρεσε ώστε να θέλετε να συνεισφέρετε και εσείς στην κοινότητα, είτε βρήκατε κάποιο ορθογραφικό λάθος και θέλετε να το διορθώσετε. Δεν είστε προγραμματιστής (ή χάκερ όπως λένε μερικοί), οπότε η μετάφραση είναι ίσως η πιο απλή συνεισφορά σας. (more…)
View On WordPress
Dispatches from development: Beta, week 1
Peerio has been out for a week, and what a week it's been! With over 7000 users and coverage in Wired and PCWorld, we have been flooded with requests ranging from "How can I pay for this?" to dozens of tickets on Github. We are absolutely thrilled to be getting this much attention, and we are committed to being responsive to community input as we continue to develop our application. With that in mind, we want to do a quick review of our intentions and goals in this open beta phase.
Why a beta?
We wanted to conduct an open beta for a number of reasons: Firstly, we wanted to make sure we had an idea and product that people wanted to use. We wanted to get a sense of how and why people would use the app, and thus understand in what directions to eventually head when developing new features. As developers and as users of software, we are concerned with making sure that we are addressing real needs not just scratching our own backs. Secondly, we wanted to open up our crypto code for community scrutiny and validation as quickly as possible. Finally, we know that no matter how much we may test and demonstrate our software internally, nothing can compete with real users in terms of understanding how a complex system behaves.
What happens now?
The practical goals of our open beta are twofold. Our first target is maturity. We are currently focused on finding and fixing bugs, improving usability, and stabilizing our systems. During the beta period we will be: commissioning another security audit; thoroughly monitoring usage and identifying bottlenecks in our servers; and fine-tuning user experience and design with your feedback. Our second target is mobile support. We know no communications platform is complete if it exists only on the desktop. Our clients for iOS and Android are in development, and we are working hard towards a release.
After beta
What's next on the roadmap? Once we are sure our system is as stable as any software system can possibly be, and we have a mobile client we are happy with, we will be looking at new feature development, as well as opening up paid plans for individuals as well as groups.
How can you help?
A number of people have asked how they can contribute, and the answer is simple: You can use the app, and tell anyone you share confidential information with to use it too! The most valuable thing we can have right now is people using the application and letting us know what improvements can be made. If you experience problems, you can let us know by either contacting our support staff, or by creating a Github issue. You are also, of course, welcome to contribute directly to the development of Peerio. You can do this by submitting a pull request on Github, or by submitting copy in whichever language(s) you speak on Transifex (you don't need to be a developer to do this!).
Thank you!
We want to thank everyone who has blogged, tweeted, submitted a ticket, translated copy, or gotten in touch already. We deeply appreciate your support, as well as your feedback and criticism. We hope that you'll continue to use our product and that it will be better thanks to you. -Florencia Hera-Vega
Transifex and TheFamily
If you know TheFamily, you must have heard the following line a few times: One of our missions is to build Unfair Advantages for startups.
Want to translate Webmaker in your own language? Here is how:
Webmaker.org helps people making the web better, and teachpeople how to use the web. If you…
View Post
What have I learned from Translating Webmaker.org with 65 Thai translators?
Chaos…. This is the first thing I wanted to say because one person versus sixty people… obviously…
View Post
Transifex Exception: 400: Error compiling the translation file
transifex.exceptions.TransifexAPIException: 400: Error compiling the translation file
If you are trying to download a translation using Transifex graphic interface or pulling them down using manage.py tx pull_translations and you are getting an error like:
transifex.exceptions.TransifexAPIException: 400: Error compiling the translation file: ‘ascii’ codec can’t encode character u’\u2019’ in position 9017: ordinal not in range(128)
You should set the variable LC_ALL to your ~/.bashrc or ~/.profile.
export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8 export LANGUAGE=en_US.UTF-8
Instead of setting that to your shell you can also set it on your Gunicorn settings.
environment=LC_ALL='en_US.UTF-8'
Cheers.