Hello list,
This discussion was started in private; I'll continue it here.
On 01/10/2013 05:41 PM, John Dennis wrote:
On 01/10/2013 04:27 AM, Petr Viktorin wrote:
On 01/09/2013 03:55 PM, John Dennis wrote:
And I could work on improving the i18n/translations infrastructure,
starting by
On 01/11/2013 10:04 AM, Petr Viktorin wrote:
Hello list,
This discussion was started in private; I'll continue it here.
On 01/10/2013 05:41 PM, John Dennis wrote:
On 01/10/2013 04:27 AM, Petr Viktorin wrote:
On 01/09/2013 03:55 PM, John Dennis wrote:
And I could work on improving the
2013/1/11 John Dennis jden...@redhat.com
On 01/11/2013 10:04 AM, Petr Viktorin wrote:
Hello list,
This discussion was started in private; I'll continue it here.
On 01/10/2013 05:41 PM, John Dennis wrote:
On 01/10/2013 04:27 AM, Petr Viktorin wrote:
On 01/09/2013 03:55 PM, John Dennis
On 01/11/2013 02:44 PM, Jérôme Fenal wrote:
2013/1/11 John Dennis jden...@redhat.com mailto:jden...@redhat.com
Thank you Jérôme for your insights as a translator. We have a lop-sided
perspective mostly from the developer point of view. We need to better
understand the translator's
2013/1/11 John Dennis jden...@redhat.com
On 01/11/2013 02:44 PM, Jérôme Fenal wrote:
2013/1/11 John Dennis jden...@redhat.com mailto:jden...@redhat.com
Thank you Jérôme for your insights as a translator. We have a lop-sided
perspective mostly from the developer point of view. We need to
On 01/11/2013 04:00 PM, Jérôme Fenal wrote:
When you say easy to upload a .po onto another branch I assume you
don't mean branch (TX has no such concept) but rather another TX
resource. Anyway this is good to know, perhaps the way TX handles
versions is not half as bad as it
2013/1/11 John Dennis jden...@redhat.com
On 01/11/2013 04:00 PM, Jérôme Fenal wrote:
When you say easy to upload a .po onto another branch I assume you
don't mean branch (TX has no such concept) but rather another TX
resource. Anyway this is good to know, perhaps the way TX
