Re: Building gides
Hi , A step I often forget is the use of autoconf * Make sure that you are in the main source directory: cd $SourceMain * Run autoconf to create the configure script: autoconf Call configure But it is difficult to help because you do not write which file is missing or which command you typed. We could help better if you always add these kind of information. ;) HTH Peter Am 17.02.20 um 07:33 schrieb Maram Abbas: Hi I was trying to build in windows 7 I followed the instructions step by step Then I got stuck at the configuration It says No such file or directory I can't figure what I miss
Building gides
Hi I was trying to build in windows 7 I followed the instructions step by step Then I got stuck at the configuration It says No such file or directory I can't figure what I miss
Re: Updated 4.2.0 build?
Am 17.02.20 um 00:24 schrieb Pedro Lino: > Hi Matthias > >> The buildbots should already have the new translations. > > I will wait for them. Thanks! > >> What exactly are you thinking of? An installer for AOO on Linux? > > I meant building the DEBS. As you know I'm not a developer. I would love to > be able to create an OpenOffice snap or even a flatpak for Linux. And a real > updater for the Windows version :) The Installtion of the DEBS is ok. It is only one line for unpacking the *.tar.gz and then dpkg -i *.deb in the unpacked directory with all debs > > Kind regards, > Pedro 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 signature.asc Description: OpenPGP digital signature
Re: Updated 4.2.0 build?
On Mon, Feb 17, 2020 at 1:59 AM Andrea Pescetti wrote: > > I think I saw, ages ago, a graphical installer for Linux, written in > Java; none of our current builds uses that approach (and honestly this > seems a bit out of place in the Linux world) but the code might still be > there. We are surely talking about OpenOffice 3.x if not even 2.x. > > It's in main/javainstaller2
Re: Build instructions
On 2/16/2020 4:31 PM, Keith N. McKenna wrote: On 2/15/2020 4:06 PM, Matthias Seidel wrote: (As you may remember, we wrote about that and I sent you a Dropbox link where you can download it from) Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Matthias; If you still have that link i can put it into the wiki. I am also more than willing to help to restructure the Build Guide. It may be best to start a new thread devoted to just that where all can share ideas on how to do that. Are there any legal/copyright issues with supplying Microsoft software that way? What would it take to get to use current software, removing the issue? I agree about a thread for discussing the structure of the Build Guide. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build instructions
On 2/15/2020 4:06 PM, Matthias Seidel wrote: >> (As you may remember, we wrote about that and I sent you a Dropbox >> link where you can download it from) >> >> Regards, >> >> Matthias >> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> Matthias; If you still have that link i can put it into the wiki. I am also more than willing to help to restructure the Build Guide. It may be best to start a new thread devoted to just that where all can share ideas on how to do that. Regards Keith signature.asc Description: OpenPGP digital signature
Re: Updated 4.2.0 build?
Pedro Lino wrote: I would love to be able to create an OpenOffice snap or even a flatpak for Linux. Just for the record, off the top of my head... For testing we should just build the so-called "installed" package (you just unzip the tree and you are done). I think I saw, ages ago, a graphical installer for Linux, written in Java; none of our current builds uses that approach (and honestly this seems a bit out of place in the Linux world) but the code might still be there. We are surely talking about OpenOffice 3.x if not even 2.x. And yes, I would also consider a unified Linux version if they didn't invent a new "unified" way of doing Linux packages every year... But one of AppImage, Flatpak or Snap should be tried sooner or later, probably in this order. This is to be discussed separately anyway. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Updated 4.2.0 build?
Hi Pedro, Am 17.02.20 um 00:24 schrieb Pedro Lino: > Hi Matthias > >> The buildbots should already have the new translations. > I will wait for them. Thanks! Linux still takes some time to upload but Windows is ready. > >> What exactly are you thinking of? An installer for AOO on Linux? > I meant building the DEBS. As you know I'm not a developer. I would love to > be able to create an OpenOffice snap or even a flatpak for Linux. And a real > updater for the Windows version :) I am also not a developer... ;-) A snap would be perfect! I suggested that long ago but I certainly don't have the time. At least I tried and built my first "Hello World" snap at Ubucon Europe in 2016. ;-) Regards, Matthias > > Kind regards, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Updated 4.2.0 build?
Hi Matthias > The buildbots should already have the new translations. I will wait for them. Thanks! > What exactly are you thinking of? An installer for AOO on Linux? I meant building the DEBS. As you know I'm not a developer. I would love to be able to create an OpenOffice snap or even a flatpak for Linux. And a real updater for the Windows version :) Kind regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Updated 4.2.0 build?
Hi Pedro, Am 16.02.20 um 23:37 schrieb Pedro Lino: > Hi Matthias, Mechtilde, all > > I did not notice (I am now Watching the PT l10n page at Github to be notified > of future updates) > > Thank you for the heads up and thank you Mechtilde for creating the updated > SDF file. The buildbots should already have the new translations. And I plan to do new test builds around Tuesday. > > I will investigate the required steps to build an updated installer for Linux > x64 What exactly are you thinking of? An installer for AOO on Linux? Regards, Matthias > > Kind regards, > Pedro > >> On February 16, 2020 10:58 AM Matthias Seidel >> wrote: >> >> >> Hi, >> >> You sure have noticed that the pt translation (and some other) are now >> updated in trunk and AOO42X. >> >> Happy building! ;-) >> >> Regards, >> >> Matthias >> >> Am 15.02.20 um 15:51 schrieb Pedro Lino: >>> Hi Mechtilde >>> >>> As Matthias mentioned we (Pedro Albuquerque and myself) would really like >>> to run a build with the complete updated 4.2 Portuguese translation. >>> Would it be possible for you to commit an updated SDF for the Portuguese >>> translation? >>> Alternatively please point me to a How-To so I can do it myself. >>> >>> Thanks! >>> >>> Kind regards, >>> Pedro >>> On February 8, 2020 7:22 PM Matthias Seidel wrote: Hi Mechtilde, Am 08.02.20 um 20:07 schrieb Mechtilde: > Hello Pedro > > Am 08.02.20 um 15:29 schrieb Pedro Lino: >> Hi Matthias >> >> Is that fix on the 4.2 branch? >> >> Do you know if the 4.2 branch is synchronized with Pootle? > You can see it in the webfrontend. > > I updated pootle 3 weeks ago. It can't be done automatically. Pedro didn't think of Pootle being synchronized with the branch. He wanted to know if the translations are already exported back to the branch... Pedro is waiting for an updated Portuguese build! ;-) > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Updated 4.2.0 build?
Hi Matthias, Mechtilde, all I did not notice (I am now Watching the PT l10n page at Github to be notified of future updates) Thank you for the heads up and thank you Mechtilde for creating the updated SDF file. I will investigate the required steps to build an updated installer for Linux x64 Kind regards, Pedro > On February 16, 2020 10:58 AM Matthias Seidel > wrote: > > > Hi, > > You sure have noticed that the pt translation (and some other) are now > updated in trunk and AOO42X. > > Happy building! ;-) > > Regards, > > Matthias > > Am 15.02.20 um 15:51 schrieb Pedro Lino: > > Hi Mechtilde > > > > As Matthias mentioned we (Pedro Albuquerque and myself) would really like > > to run a build with the complete updated 4.2 Portuguese translation. > > Would it be possible for you to commit an updated SDF for the Portuguese > > translation? > > Alternatively please point me to a How-To so I can do it myself. > > > > Thanks! > > > > Kind regards, > > Pedro > > > >> On February 8, 2020 7:22 PM Matthias Seidel > >> wrote: > >> > >> > >> Hi Mechtilde, > >> > >> Am 08.02.20 um 20:07 schrieb Mechtilde: > >>> Hello Pedro > >>> > >>> Am 08.02.20 um 15:29 schrieb Pedro Lino: > Hi Matthias > > Is that fix on the 4.2 branch? > > Do you know if the 4.2 branch is synchronized with Pootle? > >>> You can see it in the webfrontend. > >>> > >>> I updated pootle 3 weeks ago. It can't be done automatically. > >> Pedro didn't think of Pootle being synchronized with the branch. > >> He wanted to know if the translations are already exported back to the > >> branch... > >> > >> Pedro is waiting for an updated Portuguese build! ;-) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build instructions
On 2/16/2020 3:02 AM, Peter Kovacs wrote: Hi, Maybe it would be more helpful to simplify create setup by profiling a dev environment setup script for the distributions? That might be a good long term objective. The step-by-step instructions, if they worked, could serve as the specification for the script. We would still need the instructions for people who are not using a VM, and have some software already installed. For example, even on a machine I had never used to build AOO, I had Cygwin with Perl. The immediate survival issue is that we need a set of instructions that can be carried out. Without that, we cannot recruit programmers. I am currently at a place in the instructions that tells me to install a piece of software from a URL that tells me it is not available. A script would be just as stuck at exactly the same place. (Note: I am stubbornly pretending to be a new volunteer, or a script, trying to apply the instructions in order to do my first AOO build.) With the help of chocolatey we could install cygwin per script. And then add the other Programms as needed. Just a crazy idea. All the best Peter Am 15. Februar 2020 23:29:51 MEZ schrieb Patricia Shanahan : 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-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re[2]: Build instructions
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 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=edit=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-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building On CentOS 8 Dependency Help
Hi All, Now I'm stuck GTK. I'm not sure if it may be related to the gnome-vfs package being changed to gvfs or not. Here is my configure ./configure \ --enable-category-b \ --enable-bundled-dictionaries \ --enable-dbgutil \ --with-package-format="installed" \ --with-rat-scan last bit of latest error: checking for zip... /usr/bin/zip checking for unzip... /usr/bin/unzip checking which VCLplugs shall be built... gtk checking whether to enable GConf support... yes checking for GCONF... yes checking whether to enable GNOME VFS support... no checking for GTK... no configure: error: requirements to build the gtk-plugin not met. Use --disable-gtk or install the missing packages Installed Packages gtk-update-icon-cache.x86_64 3.22.30-4.el8 gtk-vnc2.x86_64 0.9.0-1.el8 gtk2.x86_64 2.24.32-4.el8 gtk2-devel.x86_64 2.24.32-4.el8 gtk3.x86_64 3.22.30-4.el8 gtk3-devel.x86_64 3.22.30-4.el8 gtkmm30.x86_64 3.22.2-2.el8 gtksourceview3.x86_64 3.24.9-1.el8 Installed Packages gvfs.x86_64 1.36.2-6.el8 gvfs-afc.x86_64 1.36.2-6.el8 gvfs-afp.x86_64 1.36.2-6.el8 gvfs-archive.x86_64 1.36.2-6.el8 gvfs-client.x86_64 1.36.2-6.el8 gvfs-devel.x86_64 1.36.2-6.el8 gvfs-fuse.x86_64 1.36.2-6.el8 gvfs-goa.x86_64 1.36.2-6.el8 gvfs-gphoto2.x86_64 1.36.2-6.el8 gvfs-mtp.x86_64 1.36.2-6.el8 gvfs-smb.x86_64 1.36.2-6.el8 Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build instructions
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=edit=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 smime.p7s Description: S/MIME Cryptographic Signature
Re: Build instructions
Hi, Maybe it would be more helpful to simplify create setup by profiling a dev environment setup script for the distributions? With the help of chocolatey we could install cygwin per script. And then add the other Programms as needed. Just a crazy idea. All the best Peter Am 15. Februar 2020 23:29:51 MEZ schrieb Patricia Shanahan : >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-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Updated 4.2.0 build?
Hi, You sure have noticed that the pt translation (and some other) are now updated in trunk and AOO42X. Happy building! ;-) Regards, Matthias Am 15.02.20 um 15:51 schrieb Pedro Lino: > Hi Mechtilde > > As Matthias mentioned we (Pedro Albuquerque and myself) would really like to > run a build with the complete updated 4.2 Portuguese translation. > Would it be possible for you to commit an updated SDF for the Portuguese > translation? > Alternatively please point me to a How-To so I can do it myself. > > Thanks! > > Kind regards, > Pedro > >> On February 8, 2020 7:22 PM Matthias Seidel >> wrote: >> >> >> Hi Mechtilde, >> >> Am 08.02.20 um 20:07 schrieb Mechtilde: >>> Hello Pedro >>> >>> Am 08.02.20 um 15:29 schrieb Pedro Lino: Hi Matthias Is that fix on the 4.2 branch? Do you know if the 4.2 branch is synchronized with Pootle? >>> You can see it in the webfrontend. >>> >>> I updated pootle 3 weeks ago. It can't be done automatically. >> Pedro didn't think of Pootle being synchronized with the branch. >> He wanted to know if the translations are already exported back to the >> branch... >> >> Pedro is waiting for an updated Portuguese build! ;-) smime.p7s Description: S/MIME Cryptographic Signature
