You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pedro Albuquerque <pm...@gmx.com> on 2020/02/16 06:49:22 UTC
Re[2]: Build instructions
Hi,
Sorry for a small change of topic, but speaking of new builds, I believe it
would be great if the 'building instructions' for SDF files were also made
available in a simple way to follow. Maybe included with the rest of the
process.
Like Pedro Lino said, we (me and him) are trying to test the updated
translations and it would be of great help if we knew how to create the SDFs.
Mechtilde, that page link you sent some time ago is exactly where I found the
gsicheck broken link, so it doesn't help much.
Patricia, I have a machine in those circumstances and, so far, the only thing
I did was the default cygwin installation. I'm very interested in following
your 'manual', should it be available.
Regards,
Pedro Albuquerque
Em 15/02/2020 às 22:29, Patricia Shanahan <pa...@acm.org> escreveu:
>Hi Matthias,
>
>We consistently lose programming volunteers when we ask them to attempt
>a build. That makes getting instructions that work, especially for
>Windows, the commonest platform, absolutely essential.
>
>On 2/15/2020 1:06 PM, Matthias Seidel wrote:
>> Hi Patricia,
>>
>> Am 15.02.20 um 20:36 schrieb Patricia Shanahan:
>>> I have learned enough about Git to attempt a new Windows build. I am
>>> building on a Windows 10 system, using the 64-bit Cygwin, and keeping
>>> detailed notes of any problems with the instructions.
>>>
>>> 1. I got very confused between what I should be getting from
>>>
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements
>>> and what from
>>>
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Build_with_Cygwin_64-bit
>>>
>>> The "general" had a lot of conditionals.
>>>
>>> I think it could be made easier to use if one could just start from
>>> the step-by-step and have it link to common web pages for anything
>>> that really is common.
>> +1
>
>This one I am not going to attempt myself because changes could affect
>other platforms that I am not using.
>
>>>
>>> 2. There is no /cygdrive/c/temp. /usr/tmp is a temporary directory.
>> /"(or any other temporary directory of your choice)"/
>
>The fix is to change it to "/usr/tmp (or other temporary directory of
>your choice)", though I am not sure why one would need an alternative to
>/usr/tmp.
>
>>>
>>> 3. Command "lynx -source
>>> rawgit.com/transcode-open/apt-cyg/master/apt-cyg > apt-cyg" failed
>>> because I had not been told to install lynx.
>>
>> I have never understood or used these instructions regarding lynx.
>
>Let's get rid of them. The closer we can get to one set of instructions
>that work the better. Cygwin's setup automatically installs
>dependencies, and is the normal way of installing Cygwin packages. One
>would need to use it to get lynx anyway.
>
>>
>>>
>>> Unclear how much can be omitted in this area if the required packages,
>>> and their dependencies, have already been installed through the Cygwin
>>> setup program, as will be the case if following the instructions. It
>>> is really necessary to provide an alternative?
>>>
>>> 4. http://www.microsoft.com/en-us/download/details.aspx?id=3138 gets
>>> an error page "We're sorry, this download is no longer available."
>>>
>>> At this point, I am officially stuck.
>>
>> As anyone else is, Microsoft has pulled that download long ago.
>>
>> (As you may remember, we wrote about that and I sent you a Dropbox link
>> where you can download it from)
>
>Yes, but I am modeling a new recruit trying to build AOO for the first
>time, using the latest instructions, on a machine that has not
>previously been used to build it. I really am using a computer I got
>after the last time I built AOO, and I am being very careful to follow
>the instructions as written, ignoring prior experience. My objective is
>as much to test the build instructions and get them fixed as to do the
>build.
>
>Do we understand why AOO building still requires an obsolete MSVC? Any
>way to fix it? This seems to me to be a particularly urgent build problem.
>
>Perhaps the best we can do here for now is to say "If you get to this
>point and do not already have Microsoft Windows SDK for Windows 7 and
>.NET Framework 3.5. SP1, send mail to dev@openoffice.apache.org to get
>your secret decoder ring."
>
>Thanks,
>
>Patricia
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re[2]: Build instructions
Posted by Pedro Albuquerque <pm...@gmx.com>.
Hi again,
It seems I, somehow, may have 'ofended' (lacking a better word), someone(s). I
humbly apologize for that. It was not my intention at all.
Please believe, I'm also very grateful for all your work, Mechtilde's and all
others.
I will restrain my self from now on, since it seems I cannot express my self
correctly!
Many thanks,
Pedro Albuquerque
Em 16/02/2020 às 12:11, Matthias Seidel <ma...@hamburg.de> escreveu:
>Hi all,
>
>First let me thank Mechtilde for the tremendous job she is doing!
>
>I still remember the day (OpenRheinRuhr 2018?) when I complained about
>the broken translation process and she instantly took over. Since then a
>lot of things have been accomplished.
>
>Now we are able to create language templates from source code, import
>them into Pootle, update the translations, export them back to SDF and
>commit them.
>
>In parallel we have "recruited" a handful of translators (Amharic,
>Kabyle, Oromo, Estonian, Latvian) so we hope to release AOO 4.2.0 with
>these new localizations [1].
>
>To be clear, the plan is to automate the translation process on the
>Pootle server, so that once a week (?) the most recent translations are
>exported and committed to Git.
>
>But all this is done in our spare time and we all have a personal life,
>so please be patient (or join the team)!
>
>(Sorry for this being a bit Off Topic now...)
>
>Regards,
>
> Matthias
>
>[1] https://home.apache.org/~mseidel/AOO-builds/AOO-420-L10n/
>
>
>Am 16.02.20 um 08:28 schrieb Mechtilde:
>> Hello Pedro
>>
>> Am 16.02.20 um 07:49 schrieb Pedro Albuquerque:
>>> Hi,
>>>
>>> Sorry for a small change of topic, but speaking of new builds, I believe
it
>>> would be great if the 'building instructions' for SDF files were also made
>>> available in a simple way to follow. Maybe included with the rest of the
>>> process.
>> This is the recent page, where I start to document the recent process:
>> https://wiki.openoffice.org/wiki/Translation_from_4.2
>>
>>> Like Pedro Lino said, we (me and him) are trying to test the updated
>>> translations and it would be of great help if we knew how to create the
SDFs.
>> In short you have to use po2oo from the translate-toolkit
>>
http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html?highlight=po2oo
>> (part of some linux distributions)
>>
>> to improve the documentation of the translation process help is
>> appreciated. We can discuss it at
>>
https://wiki.openoffice.org/w/index.php?title=Talk:Translation_from_4.2&action=edit&redlink=1
>>
>>> Mechtilde, that page link you sent some time ago is exactly where I found
the
>>> gsicheck broken link, so it doesn't help much.
>> The gsicheck is only available in the code of AOO. So you need a build
>> environment to run the gsicheck. The link I mentioned is only for the
>> help part with the possible options.
>>
>> If someone can help to isolate the code of gsicheck to have a standalone
>> tool, help is appreciated.
>>> Patricia, I have a machine in those circumstances and, so far, the only
thing
>>> I did was the default cygwin installation. I'm very interested in
following
>>> your 'manual', should it be available.
>>>
>>> Regards,
>>> Pedro Albuquerque
>> Kind regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Build instructions
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi all,
First let me thank Mechtilde for the tremendous job she is doing!
I still remember the day (OpenRheinRuhr 2018?) when I complained about
the broken translation process and she instantly took over. Since then a
lot of things have been accomplished.
Now we are able to create language templates from source code, import
them into Pootle, update the translations, export them back to SDF and
commit them.
In parallel we have "recruited" a handful of translators (Amharic,
Kabyle, Oromo, Estonian, Latvian) so we hope to release AOO 4.2.0 with
these new localizations [1].
To be clear, the plan is to automate the translation process on the
Pootle server, so that once a week (?) the most recent translations are
exported and committed to Git.
But all this is done in our spare time and we all have a personal life,
so please be patient (or join the team)!
(Sorry for this being a bit Off Topic now...)
Regards,
Matthias
[1] https://home.apache.org/~mseidel/AOO-builds/AOO-420-L10n/
Am 16.02.20 um 08:28 schrieb Mechtilde:
> Hello Pedro
>
> Am 16.02.20 um 07:49 schrieb Pedro Albuquerque:
>> Hi,
>>
>> Sorry for a small change of topic, but speaking of new builds, I believe it
>> would be great if the 'building instructions' for SDF files were also made
>> available in a simple way to follow. Maybe included with the rest of the
>> process.
> This is the recent page, where I start to document the recent process:
> https://wiki.openoffice.org/wiki/Translation_from_4.2
>
>> Like Pedro Lino said, we (me and him) are trying to test the updated
>> translations and it would be of great help if we knew how to create the SDFs.
> In short you have to use po2oo from the translate-toolkit
> http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html?highlight=po2oo
> (part of some linux distributions)
>
> to improve the documentation of the translation process help is
> appreciated. We can discuss it at
> https://wiki.openoffice.org/w/index.php?title=Talk:Translation_from_4.2&action=edit&redlink=1
>
>> Mechtilde, that page link you sent some time ago is exactly where I found the
>> gsicheck broken link, so it doesn't help much.
> The gsicheck is only available in the code of AOO. So you need a build
> environment to run the gsicheck. The link I mentioned is only for the
> help part with the possible options.
>
> If someone can help to isolate the code of gsicheck to have a standalone
> tool, help is appreciated.
>> Patricia, I have a machine in those circumstances and, so far, the only thing
>> I did was the default cygwin installation. I'm very interested in following
>> your 'manual', should it be available.
>>
>> Regards,
>> Pedro Albuquerque
> Kind regards
Re: Build instructions
Posted by Mechtilde <oo...@mechtilde.de>.
Hello Pedro
Am 16.02.20 um 07:49 schrieb Pedro Albuquerque:
> Hi,
>
> Sorry for a small change of topic, but speaking of new builds, I believe it
> would be great if the 'building instructions' for SDF files were also made
> available in a simple way to follow. Maybe included with the rest of the
> process.
This is the recent page, where I start to document the recent process:
https://wiki.openoffice.org/wiki/Translation_from_4.2
> Like Pedro Lino said, we (me and him) are trying to test the updated
> translations and it would be of great help if we knew how to create the SDFs.
In short you have to use po2oo from the translate-toolkit
http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html?highlight=po2oo
(part of some linux distributions)
to improve the documentation of the translation process help is
appreciated. We can discuss it at
https://wiki.openoffice.org/w/index.php?title=Talk:Translation_from_4.2&action=edit&redlink=1
> Mechtilde, that page link you sent some time ago is exactly where I found the
> gsicheck broken link, so it doesn't help much.
The gsicheck is only available in the code of AOO. So you need a build
environment to run the gsicheck. The link I mentioned is only for the
help part with the possible options.
If someone can help to isolate the code of gsicheck to have a standalone
tool, help is appreciated.
>
> Patricia, I have a machine in those circumstances and, so far, the only thing
> I did was the default cygwin installation. I'm very interested in following
> your 'manual', should it be available.
>
> Regards,
> Pedro Albuquerque
Kind regards
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F