Hi Dne Mon, 22 Jul 2013 16:23:05 +0300 Marius Gedminas <[email protected]> napsal(a):
> I've recently started experimenting with Weblate. I'm now trying to
> figure out how to set up a proper automatic workflow.
>
> Say, a programmer adds a new translatable string to the source code.
> Weblate won't know anything about this until somebody runs a script
> (bin/i18nextract) and commits updated po files. This also produces a
> lot of diff noise (line number in comments that show where the strings
> are used), so I don't want to commit .po updates all that often.
You should really keep po files up to date to give translators good
reference where the strings are being used. If you find these
references for translators useless, you can use xgettext with
--no-location.
> I have Jenkins running on the same server as Weblate. I currently have
> a job that runs i18nextract after every commit and publishes some
> statistics about the number of missing strings etc. I'm thinking that
> maybe I could convince Weblate to use the repository of this Jenkins job
> somehow? Will it be happy to import .po files from dirty Git working
> trees?
>
> What do you people do? This must be a common problem.
At my projects, I do update po files by running some script whenever
there is an important change (eg. new string is added or source is
heavily changed). I was thinking about automating this somehow, but
never found time to think about that deeper.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
signature.asc
Description: PGP signature
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
