[Freedombox-discuss] FreedomBox UI in your language

[Mikkel Kirkgaard Nielsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Philippe.

My attempt with the particular comment you are replying here was to
make you aware about the synchronization process between strings in
source code and the translatable strings in the .po files. That process
is independent of whichever tool translators use. It is what actually
generates the input files to the translators work by merging an existing
.po file with the current strings of the code.

Whenever this sync is done all translators need to go through the review
and proofreading process again. Thus to spare everyone’s time and effort
it is wise not to do this too often but do it at a time when
strings are regarded as stable in the source and in adequate time before
a release to not stress out translators (too much).

The objective was to assure that you aren't under the impression that
the translation for a 0.7 release is complete when Transifex's current
set of .po files are translated because that is not the case.


On 2015-12-02 12:32, Philippe wrote:
> Being not a super techy person and in my understanding of the 
> current process, we have a pretty clear 2 stage work 
> (translation/proof read) on Transifex

Techy or not, I guess (and hope) everyone is welcome ;). The i18n
infrastructure and team is still being built while everyone is
learning so the current state is in limbo and that's from my point of
view understandable and perfectly fine.

> when is the good time to upload a translation in order to avoid 
> unnecessary uploads ? Is it good to upload now all the local
> django file even not fully polished for first experimental purpose
> ?

Ideally the sync back from translation tool would be automatic or at
least just require a manual trigger and thus a non-issue effort wise. To
my understanding all the tools that are discussed would be able to do
that.

I personally prefer to see the translations I do in their right context
as often as possible. My experience is that otherwise the translation
will be of inferior quality because something is always out of context
compared to the assumptions you have during editing.

> Leaving Transifex (non free, no sync) for Weblate (free, sync) as 
> the recommanded tool seems logical and is the next move.

Transifex is capable of syncing but if it's already decided to head for
Weblate then we need not discuss further. I can only applaud the use
of a GPL licensed tool.

> In the meantime, staying on Transifex can be a local choice from 
> teams who are not comfortable with other solutions. What do you 
> think?

I'll cope with git+emacs in a terminal but not everyone is like that,
I know. For the moment I think it would be too much work to support
and maintain multiple tools. I'd settle with one and see how it spins
off.

- --
Mikkel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWYNphAAoJEJ2luFWzaTSaHNsIAMzyN16+U13n6SuL5Y7YVNsH
GZcs3Ihq7DVDybTs9Qx/2VO5wEh1GvxOQGY3odjZE+JrehDI1I/tBPwn7frlqXiR
VhL1itAxq4/C+k8PfcXt2SP2SFKp+/6oVBfhOlK5EaO8tq50uH47ibB27g83oxXH
b6enKagPNhmLa0m47WG6GePytg7DMtUd9ALggmnZ22xQ9fVm6R9GSfF4lrHZb4YA
yOcfjnOp3BhcG5B0h8WP1pg0WMWmWvewoKgUq8xmU0sMhyWjDs6DvbZ9zelYmU15
HXeeY1I7KIUw7x8ZMM3G/Dpwv6JmgGAKfhr4rwDTqv9ISsnwS2q18s1wenOCM1c=
=Qou1
-----END PGP SIGNATURE-----