[GNC-dev] Request to move translation to Gnu Translation Project

Pedro Albuquerque pmra at gmx.com
Thu Nov 26 22:26:52 EST 2020

Hi John, Frank, all,

As usual, your help and response are excellent. To bad I'm not capable
of working decently with such great developers. I'll do my best to
maintain GnuCash updated, anyway I can. So, let's find a way.

Regarding TP, the answer was already given by Benno, since he already
removed the 'External' mark and assigned the translation to me. Being
behind one or two minor versions is a lot better than what it is right
now, so I think it will be an improvement anyway.

Regarding the other files (accounts, glossary and website), Frank, I
don't mind at all that you send me a 'pre-release archive', let's say a
week before the string freeze. I'm almost sure I can update the
translations on time and re-send them to you by email. But I think it's
not practical to you. It may work, until a better solution is found.

Weblate, or any other online service would be great and, I think, easy
for you developers to maintain. And could aggregate all files under a
same language project. Anything but Github, please.

The only remaining problem would be the documentation. I don't even know
how to find the differences between what is already translated and what
is not.

That said, thank you all again for your availability to help and for a
great software. Always at your disposal.


On 26/11/20 18:23, John Ralls wrote:
>> On Nov 26, 2020, at 7:52 AM, Frank H. Ellenberger <frank.h.ellenberger at gmail.com> wrote:
>> Am 26.11.20 um 16:28 schrieb John Ralls:
>>> Frank, I'm not sure what you mean about the string-freeze/prerelease process. As we approach a major release we do a series of beta releases and typically impose a string freeze after the one a month before the scheduled major release date. TP gets all of those releases and the (3 or 4 active) TP translators generally have updated translations ready in time for the major release. There's no pre-release or string freeze process for minor releases, TP or otherwise, and AFAICT the only non-TP translator who routinely updates between minor releases is you (TP's Ukrainian and Croatian translators have been very good at keeping up to date, albeit with a one-release lag because of the TP's policy of working only from release tarballs).
>> The betas help for a new major release, but not for the more frequent
>> minor releases.
>> From https://translationproject.org/html/maintainers.html
>> 2. Using the Translation Project
>> :
>> Preferably you make a prerelease a week or so earlier and announce this
>> to the TP, so the translators get a chance to update their PO files
>> before the actual release of your package, so the release can go out
>> fully translated into several languages.
>> Ideally we would declare string freeze 2 weeks before any release and
>> send a recent pot file to TP. So translators would have a chance to
>> update their po files before the release.
> Maybe should discuss this with Benno. I don't think it makes sense to do a full release ahead of the real release. I'd think it would be sufficient to make a pre-release tarball for the TP. They might even be able to work from one of the Github tarballs. IIUC they don't try to build the project so they wouldn't be affected by the versioning stuff. They run their own tools on it and generate their own profile that they merge into their own po-file repository.
> Regards,
> John Ralls
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 665 bytes
Desc: OpenPGP digital signature
URL: <http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20201127/eb3f522f/attachment.sig>

More information about the gnucash-devel mailing list