Re: AbiWord Windows builds and L10n workflow

On Mon, Jun 25, 2012 at 4:57 AM, Ingo Brückl <ib@wupperonline.de> wrote:
>
> Chris Leonard wrote on Mon, 25 Jun 2012 00:28:00 -0400:
>
>> bafna_p ran into an issue while working on a Windows build.  He got a
>> complaint that the
>
>> /user/wp/strings/
>
>> folder was missing.
>
> Well, then. Fix the build.

Yes, indeed that is what is needed. However I do not have the
requisite knowledge of the Windows build process to do that myself, so
I am requesting assistance.

>> This apparently traces back to a modification of the MAKEFILE (or some
>> such) made by Simon that causes the .strings files to be created on fly
>> during the make.
>
> Yes, we agreed on doing so after you asked "to automate the process without
> requiring some cooperation from the developers as Pootle will only do the
> commit of the PO file".

Yes and that change was very welcome and and essential to the process
slowly and carefully disintermediating developer intervention in
commits of L10n. Something that will benefit both developers and
localizers.

>> This is great for *nix, but it does NOT address the needs of the Windows
>> build process.
>
> Why?

I do not exactly understand the changes Simon made and why they do not
address Windows requirements, which is why I am asking for assistance
to correct this situation that Prashant discovered.

>> As a temporary workaround to allow Windows build process  to move
>> forward, I have re-generated all of the .strings using the PO files
>> committed to SVN, by using the "abi-backport-all.sh" script to
>> generate them and them moved them to /user/wp/strings/ and then
>> committed that folder (and all the .strings files) to SVN.
>
> Bad idea. We now have redundant data that soon will diverge. This ought to be
> reverted ASAP.

I can assure you that this workaround was not done willy-nilly. It
was performed at the request of Marc (IRC:uwog) after consultation on
IRC and is solely intended as a stopgap measure to allow a Windows
build to move forward. Immediate notice was posted to the list to
inform others of the steps taken (and why) and to request assistance
with a less disruptive and more permanent solution.

>> 2) What is the best approach ot solving this issue for the long term
>> and addressing the needs of both *nix and Windows builders?
>
> Fix the Windows build to generate the .strings files. Only Perl is needed for
> the generation so it shouldn't be a problem.

That sounds great, can you offer a more detailed description of the
preferred the solution (or possibly a patch?). Your expertise would
be very much appreciated.

Regards,

cjl
Received on Mon Jun 25 17:00:48 2012