Hi Olivier,
Le 03/12/2014 10:37, Olivier Hallot a écrit :
I opened an enhancement suggestion to Pootle that may be of our interest
collaboration
http://github.com/translate/pootle/issues/3400
Thanks for this enhancement request, it's a nice one :)
For information, I've joined the team
2014-12-03 9:46 GMT+00:00 Sophie gautier.sop...@gmail.com:
Hi Olivier,
Le 03/12/2014 10:37, Olivier Hallot a écrit :
I opened an enhancement suggestion to Pootle that may be of our interest
collaboration
http://github.com/translate/pootle/issues/3400
Thanks for this enhancement
Yep, Pootle is too fragile in my experience. I personally prefer Weblate.
Its development was started exactly because Pootle was too buggy and it
turned out to be a more than adequate replacement. And the direct
integration into git/mercurial is just cool.
On Wed, Dec 3, 2014 at 12:00 PM, Sérgio
Hi all,
Another follow-up on the discussion we had, who would be interested to
have a translation workflow based on master?
To understand, that would mean that a new project named 'master' will be
created on Pootle. Once a month, Cloph will extract the strings from
Pootle to the source code. The
Hi,
Le 03/12/2014 18:27, khagaroth a écrit :
Yep, Pootle is too fragile in my experience. I personally prefer Weblate.
Its development was started exactly because Pootle was too buggy and it
turned out to be a more than adequate replacement. And the direct
integration into git/mercurial is
Er, you mean offline translation? Of course it supports offline
translations.
On Wed, Dec 3, 2014 at 6:30 PM, Sophie gautier.sop...@gmail.com wrote:
Hi,
Le 03/12/2014 18:27, khagaroth a écrit :
Yep, Pootle is too fragile in my experience. I personally prefer Weblate.
Its development was
I have same ability to translate com-central on mozilla repositories,
but I never use it. It's too unstable and a lot of changes.
If someone thinks it will be useful for him, you can implement it, but I
know I won't use it.
Best regards,
Mihovil
3.12.2014. u 18:27, Sophie je napisao/la:
Hi
Hi Sophie
On 03/12/2014 15:27, Sophie wrote:
Hi all,
(snip)
What is your opinion on that?
Cheers
Sophie
I am for it. +1
--
Olivier Hallot
Comunidade LibreOffice
http://ask.libreoffice.org/pt-br
--
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems?
For me (Portuguese) it´s fine as is. I know that from time to time. we have
a lot of work. But I prefer that way. Master strings, as Mihovil said, has
many changes all the time. I prefer to do the work one time only.
Regards
2014-12-03 17:27 GMT+00:00 Sophie gautier.sop...@gmail.com:
Hi all,
Bonsoir Sophie,
2014-12-01 14:57 GMT+01:00 Sophie gautier.sop...@gmail.com:
Hi all,
Opening a new thread on the changes on the en_US version, I propose to
follow-up on the project@ list so we could associate the developers and
design teams and discuss together how to handle that in our
I may be completely misunderstanding this, but
it seems to me the point is the en_US strings
should be translations as well. That would put
much needed damper on the changes introduced
just because they can be introduced. As a
secondary gain, translations are (hopefully)
created by folks
IMO bad quality of English strings can be improved by having some l10m teams
work on Master (and spotting these bad strings early enough), and that is being
discussed in parallel.
Also, perhaps requiring string reviews on patches with new or changed strings
could be an option. I'm pretty sure
12 matches
Mail list logo
