Re: OpenOffice wordmark exploration (yet without the "Apache" mention)
Hello, Where can I send it? Thanks Corentin Verbrèghe Le jeu. 10 févr. 2022 à 21:16, Matthias Seidel a écrit : > Hi Corentin, > > I don't know what to think because your attachment doesn't come through on > the mailing list. ;-) > > Can you provide it in another way? > > Regards, > >Matthias > Am 10.02.22 um 20:44 schrieb Corentin Verbreghe: > > What do you think ? > > Le jeu. 10 févr. 2022 à 20:00, Corentin Verbreghe < > corentin.verbreg...@gmail.com> a écrit : > >> Hi, there's an exploration for the AOO wordmark. >> [image: image.png] >> Don't hesitate to give your opinion. >> Cordially. >> Corentin Verbrèghe >> >
Re: OOo spelling dictionaries site closed
> On Feb 11, 2022, at 9:36, Matthias Seidel wrote: > > Hi Marcus, > > Am 11.02.22 um 00:07 schrieb Marcus: >> Am 10.02.22 um 23:08 schrieb Matthias Seidel: >>> Am 10.02.22 um 23:06 schrieb Marcus: Am 10.02.22 um 21:25 schrieb Matthias Seidel: > Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? >>> >>> Did you read the mail?! >> >> OK, I'm trying a thought. I don't know which content and how it was on >> the webpage that is now gone. So, maybe it's rubish. >> >> - Download all extensions >> - Extract the pure dictionary files >> - Put them on a new webpage >> - Exchange the old URL to this new one in OmegaT >> >> Can this work? >> >> BTW: >> When I look at the SSL certificate for >> "https://download.services.openoffice.org/; (yes, with HTTPS) I've the >> feeling that the page was not under our control. > > You are right! This site was probably never under our control! > > The invalid certificate refers to some domains (e.g. > https://www.ammec.de). Does anyone know "Marco Skambraks"? > > @Jean-Christophe: > It looks like OmegaT points to a download page that was not from the > OpenOffice project. > In what format does OmegaT expect the dictionaries? I installed the > Windows version and it does not seem to accept OXT, which is the only > format we offer. > > Regards, > >Matthias Thank you both so much for looking into this. I'm putting Aaron Madlon-Kay, who is the OmegaT project coordinator in Cc. The process was transparent to the user so it's hard to see what was hosted/expected from the site, but from reading the OmegaT code it looks like the site hosted a number of zipped .aff + .dic pairs for each language. https://sourceforge.net/p/omegat/code/ci/master/tree/src/org/omegat/core/spellchecker/DictionaryManager.java OmegaT displayed the language code, the user selected a language and OmegaT downloaded the zip, unzipped it in a dedicated folder and that was it. Marco Skambraks seems to have been working on accessibility in Linux. https://wiki.linuxfoundation.org/accessibility/charter_v1.0 https://www.knopper.net/knoppix-adriane/index-en.html https://www.suse.com/c/the-brains-behind-the-books-part-ix-meike-chabowski/ He seems to be heading this company http://www.ammec.de/ So I guess the belief that we were using an OOo repository was wrong and I'm sorry I bothered you. LibreOffice seems to have a github repository with the unzipped files at https://github.com/LibreOffice/dictionaries Either way, we'll have to implement a new solution. Thank you again for all the work you do on OOo. Jean-Christophe > >> >> Marcus >> >> >> > Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: >> Matthias, Dave, >> >> Thank you very much for looking into this. >> >> If you have an equivalent repository that’s open for external >> access, OmegaT will need to update its spelling dictionary >> installation process and inform current users that the URI currently >> used needs to be changed (not that people change of dictionaries >> that often, but just in case.) >> >> Regards, >> >> Jean-Christophe >> >>> On Feb 6, 2022, at 1:05, Matthias Seidel >>> wrote: >>> >>> Hi Jean-Christophe, >>> >>> Thanks for asking here! It is a much better place than Twitter... >>> ;-) >>> >>> I am wondering if there was a redirection dumped when we switched >>> the >>> build system for the homepage? >>> >>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>> seems to be long gone... >>> >>> @Dave: Do you have more insight? >>> >>> Regards, >>> >>> Matthias >>> >>> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us
Re: OOo spelling dictionaries site closed
Hi Marcus, Am 11.02.22 um 00:07 schrieb Marcus: > Am 10.02.22 um 23:08 schrieb Matthias Seidel: >> Am 10.02.22 um 23:06 schrieb Marcus: >>> Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? >>> >>> I think don't understand the problem: >>> >>> All extensions can be accessed via the extension webpage. Is this not >>> an option? If not, what is expected? >> >> Did you read the mail?! > > OK, I'm trying a thought. I don't know which content and how it was on > the webpage that is now gone. So, maybe it's rubish. > > - Download all extensions > - Extract the pure dictionary files > - Put them on a new webpage > - Exchange the old URL to this new one in OmegaT > > Can this work? > > BTW: > When I look at the SSL certificate for > "https://download.services.openoffice.org/; (yes, with HTTPS) I've the > feeling that the page was not under our control. You are right! This site was probably never under our control! The invalid certificate refers to some domains (e.g. https://www.ammec.de). Does anyone know "Marco Skambraks"? @Jean-Christophe: It looks like OmegaT points to a download page that was not from the OpenOffice project. In what format does OmegaT expect the dictionaries? I installed the Windows version and it does not seem to accept OXT, which is the only format we offer. Regards, Matthias > > Marcus > > > Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: > Matthias, Dave, > > Thank you very much for looking into this. > > If you have an equivalent repository that’s open for external > access, OmegaT will need to update its spelling dictionary > installation process and inform current users that the URI currently > used needs to be changed (not that people change of dictionaries > that often, but just in case.) > > Regards, > > Jean-Christophe > >> On Feb 6, 2022, at 1:05, Matthias Seidel >> wrote: >> >> Hi Jean-Christophe, >> >> Thanks for asking here! It is a much better place than Twitter... >> ;-) >> >> I am wondering if there was a redirection dumped when we switched >> the >> build system for the homepage? >> >> http://download.services.openoffice.org/files/contrib/dictionaries/ >> seems to be long gone... >> >> @Dave: Do you have more insight? >> >> Regards, >> >> Matthias >> >> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >>> Hello Devs, >>> >>> First, thank you for your hard work on OOo. I used to help with >>> localization when OOo was still managed by Sun. >>> >>> I am (still) currently helping with OmegaT, the free >>> ‘computer-aided-translation’ tool and we use OOo’s spelling >>> dictionaries for the spell-checking functionality. >>> >>> The site that’s hard linked in the code is: >>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>> >>> But it seems to be definitely down, even though I seem to remember >>> that it was working a few weeks ago. >>> >>> OmegaT needs the dictionary files and won’t be able to work with >>> the OOo extensions. >>> >>> I understand that such direct access could cause undue load on >>> your servers, and that’s maybe the reason why you took it >>> off-line, but if that’s not the case we would love to be able to >>> keep using your repository, if you still have one. In which case, >>> would you mind letting us know what would be the equivalent URL? >>> >>> Thank you in advance. > > - > 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: OOo spelling dictionaries site closed
Am 10.02.22 um 23:08 schrieb Matthias Seidel: Am 10.02.22 um 23:06 schrieb Marcus: Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Did you read the mail?! OK, I'm trying a thought. I don't know which content and how it was on the webpage that is now gone. So, maybe it's rubish. - Download all extensions - Extract the pure dictionary files - Put them on a new webpage - Exchange the old URL to this new one in OmegaT Can this work? BTW: When I look at the SSL certificate for "https://download.services.openoffice.org/; (yes, with HTTPS) I've the feeling that the page was not under our control. Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Hi Marcus, Am 10.02.22 um 23:06 schrieb Marcus: > Am 10.02.22 um 21:25 schrieb Matthias Seidel: >> Can we help here? > > I think don't understand the problem: > > All extensions can be accessed via the extension webpage. Is this not > an option? If not, what is expected? Did you read the mail?! Matthias > > Marcus > > > >> Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: >>> Matthias, Dave, >>> >>> Thank you very much for looking into this. >>> >>> If you have an equivalent repository that’s open for external >>> access, OmegaT will need to update its spelling dictionary >>> installation process and inform current users that the URI currently >>> used needs to be changed (not that people change of dictionaries >>> that often, but just in case.) >>> >>> Regards, >>> >>> Jean-Christophe >>> On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: > Hello Devs, > > First, thank you for your hard work on OOo. I used to help with > localization when OOo was still managed by Sun. > > I am (still) currently helping with OmegaT, the free > ‘computer-aided-translation’ tool and we use OOo’s spelling > dictionaries for the spell-checking functionality. > > The site that’s hard linked in the code is: > http://download.services.openoffice.org/files/contrib/dictionaries/ > > But it seems to be definitely down, even though I seem to remember > that it was working a few weeks ago. > > OmegaT needs the dictionary files and won’t be able to work with > the OOo extensions. > > I understand that such direct access could cause undue load on > your servers, and that’s maybe the reason why you took it > off-line, but if that’s not the case we would love to be able to > keep using your repository, if you still have one. In which case, > would you mind letting us know what would be the equivalent URL? > > Thank you in advance. > > - > 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: OOo spelling dictionaries site closed
Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Am 10.02.22 um 20:12 schrieb Arrigo Marchiori: Hello Carl, On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: Hi Arrigo, On 2/10/22 11:00 AM, Arrigo Marchiori wrote: Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. On Feb 8, 2022, at 6:06 AM, Matthias Seidel wrote: Hi Arrigo, No need to apologize. ;-) But I think, before we begin to think about upgrading serf we need to make sure that AOO41X is able to build successfully on all platforms. Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. What is the architecture of the Mac Mini? % uname -a Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64 Asul has x86-64 JDK's available for Java 7 but that's all. https://www.azul.com/downloads/?version=java-7-lts=macos=jdk I will try that! Please allow me to state I had no intention to ``subvert'' current versions of Java or whatever. For what I understand, Catalina and the XCode versions installed in our Mac mini do not match the reference macOS version and tools for our AOO41X builds, and this is absolutely fine for me, as long as there is someone else who has a system with the ``official'' architecture and is able to use it. I am just trying to have a (whatever version of) macOS building AOO, so that when I commit something, I can test on that architecture as well. And possibly lower the barriers to entry for others. So if any of my edits break the builds on ``official machines'', please let us just revert them. The Java version change was not even committed anywhere. ;-) Thank you for reading through my disclaimer. ;-) Don't worry. I don't see a problem for now. Great that you experiment with a different setup to see how it works then. For the AOO41X release branch we really should try as best and long as possible to keep the setup the same like the past releases to give a (kind of) guarantee that a new release would run also in the same PC environment. So, the next step is to see if the build is also successful with Java 7. But as I see this already in progress . :-) All fine Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: RV: Aranese Spell Checking in libreoffice
Am 10.02.22 um 21:20 schrieb Matthias Seidel:
Anyone else?!
This issue is almost 7 years old now...
unfortunately, I'm not a core developer and I don't know anything about
how to integrate new languages for spell checking.
Marcus
Am 08.02.22 um 19:09 schrieb Peter Kovacs:
On 07.02.22 21:17, Matthias Seidel wrote:
Hi all,
Anyone who can help here?
Currently no clue. sorry.
Regards,
Matthias
Am 30.01.22 um 12:01 schrieb Javier T:
Hi Matthias
I have been looking at the LibreOffice code and the Aranese language
is partially defined.
Is already defined
FILE ./svtools/inc/langtab.hrc
{ NC_("STR_ARR_SVT_LANGUAGE_TABLE", "Aranese") ,
LANGUAGE_USER_OCCITAN_ARANESE },
FILE ./include/i18nlangtag
#define LANGUAGE_USER_OCCITAN_ARANESE LanguageType(0x8082)
Remains to be defined
FILE ./i18nlangtag/source/isolang
{ LANGUAGE_USER_OCCITAN_ARANESE, "oc", "ES", k0 },
FILE ./i18npool/Library_localedata_es.mk
CustomTarget/i18npool/localedata/localedata_oc_ES \
FILE ./i18npool/source/localedata/localedata.cxx
{ "oc_ES", lcl_DATA_ES },
add the file
/i18npool/source/localedata/data/oc_ES.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=147053
De: Matthias Seidel
Enviado: Jueves, 27 de Enero de 2022 23:56
Para: dev@openoffice.apache.org
Asunto: Re: RV: Aranese Spell Checking in libreoffice
Hi Javier,
My impression is that LO did somehow enable Aranese for spellchecking.
They never added your localedata (oc_ES.xml), at least I can't find
it in their code.
I am not sure what to think of that, maybe others here have an opinion?
Regards,
Matthias
Am 23.01.22 um 21:44 schrieb Javier T:
Hi Matthias
I have found the mail that I sent them with the modified file that
they indicated to me.
If I remember correctly this was added by the version of libreoffice
5.1
When you open a new document in libreoffice if you select the text,
it lets you define the language of the text or paragraph and
"Aranese" appears there.
When you want to define a language for the document it does not
appear or I know why.
Attached capture and the mail that I tell you.
Thank you.
[cid:part1.65E0CAD6.8A86E85D@hamburg.de]
De: Javier
Enviado: miércoles, 13 de mayo de 2015 22:12
Para: jonathon
Asunto: RE: Aranese Spell Checking
Occitan is composed by these diferent variants.
Alvernès
Bearnès
Creixent
Gascó
Judeoprovençal
Llenguadocià
Montpellerenc (subdialecte)
Niçard
Occità llemosí
Provençal
Vivaroalpí
Aranese is a Gascon dialect spoken in Aran Valley (Spain)
I think that ISO 639 is a realy bad system to define languages an
their dialects.
Nowadays exists 2 spell checkers for libreoffice
oc_FR - I think that is Llenguadocian (but I'm not sure)
gsc_FR - A gascon dialect spell checker.
The correct definition maybe can be
FR_oci_leng
FR_oci_gsc
But this isn't a ISO 639 code. Really I don't have a good solution
for that and I'm not sure what are the diferences between the
diferent dialects.
If you defines a code OCI_fr you need to update the oc_FR spell
checker.
In my case I prefer use oc_ES to standarize with the old
aplications. But I'm not sure what is the best choice to define it
in libreoffice.
You can decide at your own criterion, oc_ES or oci_ES. Really is not
a problem for me, because Aran Valley is the only region in Spain
where people speaks occitan. I need just a code.
I send you the locale file.
Thanks
From: toki.kant...@gmail.com
Date: Tue, 28 Apr 2015 19:00:18 +
To: javierd...@hotmail.com
Subject: Aranese Spell Checking
Javier:
I saw your request for support of Aranese in Apache OpenOffice.
I don't how difference Aranese is from Gascon, nor how different
either
of those are from Occitan.
The primary issue is ISO 639-3 Code OCI, which is for Occitan, and the
various dialects. A spell checker for Aranese will conflict with a
spell
checker for Occitan.
(I am saying that, based on working with spell checkers for various
languages of Southern Africa.)
LibreOffice currently supports Occitan as a language/local.
My suggestion is creating OCI_fr, OCI_ad, OCI_es, and maybe OCI_it as
locales. Get together with users of other dialects/languages that are
classified under OCI, and work up something that is acceptable to
everybody, but still allows them to use the grammar and spell
checkers.
Go to http://www.it46.se/localegen/select_lang.php to create the
locales.
Then either go to https://bugs.documentfoundation.org/buglist.cgi and
file a bug requesting creation of the respective locales, or email the
xml, and I'll do that.
The _only_ reason I'm not creating the locales, is that I have no idea
what the correct information is.
jonathon
---
Re: RV: Aranese Spell Checking in libreoffice
Hi Carl,
Javier wants to add code to AOO to support a new language:
https://bz.apache.org/ooo/show_bug.cgi?id=126222
I think we should at least try to help him.
Regards,
Matthias
Am 10.02.22 um 22:14 schrieb Carl Marcum:
> Hi Matthias,
>
> Is there an AOO issue?
> I don't understand.
>
> Thanks,
> Carl
>
> On 2/10/22 3:20 PM, Matthias Seidel wrote:
>> Anyone else?!
>>
>> This issue is almost 7 years old now...
>>
>> Regards,
>>
>> Matthias
>>
>> Am 08.02.22 um 19:09 schrieb Peter Kovacs:
>>> On 07.02.22 21:17, Matthias Seidel wrote:
Hi all,
Anyone who can help here?
>>> Currently no clue. sorry.
Regards,
Matthias
Am 30.01.22 um 12:01 schrieb Javier T:
> Hi Matthias
>
> I have been looking at the LibreOffice code and the Aranese language
> is partially defined.
>
> Is already defined
>
> FILE ./svtools/inc/langtab.hrc
> { NC_("STR_ARR_SVT_LANGUAGE_TABLE", "Aranese") ,
> LANGUAGE_USER_OCCITAN_ARANESE },
>
> FILE ./include/i18nlangtag
> #define LANGUAGE_USER_OCCITAN_ARANESE LanguageType(0x8082)
>
> Remains to be defined
>
> FILE ./i18nlangtag/source/isolang
> { LANGUAGE_USER_OCCITAN_ARANESE, "oc", "ES", k0 },
>
> FILE ./i18npool/Library_localedata_es.mk
> CustomTarget/i18npool/localedata/localedata_oc_ES \
>
> FILE ./i18npool/source/localedata/localedata.cxx
> { "oc_ES", lcl_DATA_ES },
>
> add the file
> /i18npool/source/localedata/data/oc_ES.xml
>
>
>
> https://bugs.documentfoundation.org/show_bug.cgi?id=147053
>
>
>
> De: Matthias Seidel
> Enviado: Jueves, 27 de Enero de 2022 23:56
> Para: dev@openoffice.apache.org
> Asunto: Re: RV: Aranese Spell Checking in libreoffice
>
>
> Hi Javier,
>
>
> My impression is that LO did somehow enable Aranese for
> spellchecking.
>
>
> They never added your localedata (oc_ES.xml), at least I can't find
> it in their code.
>
>
> I am not sure what to think of that, maybe others here have an
> opinion?
>
>
> Regards,
>
>
> Matthias
>
>
>
> Am 23.01.22 um 21:44 schrieb Javier T:
> Hi Matthias
>
> I have found the mail that I sent them with the modified file that
> they indicated to me.
>
> If I remember correctly this was added by the version of libreoffice
> 5.1
>
> When you open a new document in libreoffice if you select the text,
> it lets you define the language of the text or paragraph and
> "Aranese" appears there.
> When you want to define a language for the document it does not
> appear or I know why.
> Attached capture and the mail that I tell you.
>
> Thank you.
>
>
> [cid:part1.65E0CAD6.8A86E85D@hamburg.de]
>
>
>
> De: Javier
> Enviado: miércoles, 13 de mayo de 2015 22:12
> Para: jonathon
>
> Asunto: RE: Aranese Spell Checking
>
> Occitan is composed by these diferent variants.
>
> Alvernès
>
> Bearnès
>
> Creixent
>
> Gascó
>
> Judeoprovençal
>
> Llenguadocià
>
> Montpellerenc (subdialecte)
>
> Niçard
>
> Occità llemosí
>
> Provençal
>
> Vivaroalpí
>
>
> Aranese is a Gascon dialect spoken in Aran Valley (Spain)
>
> I think that ISO 639 is a realy bad system to define languages an
> their dialects.
>
> Nowadays exists 2 spell checkers for libreoffice
>
> oc_FR - I think that is Llenguadocian (but I'm not sure)
> gsc_FR - A gascon dialect spell checker.
>
> The correct definition maybe can be
> FR_oci_leng
> FR_oci_gsc
>
> But this isn't a ISO 639 code. Really I don't have a good solution
> for that and I'm not sure what are the diferences between the
> diferent dialects.
>
> If you defines a code OCI_fr you need to update the oc_FR spell
> checker.
>
> In my case I prefer use oc_ES to standarize with the old
> aplications. But I'm not sure what is the best choice to define it
> in libreoffice.
>
> You can decide at your own criterion, oc_ES or oci_ES. Really is not
> a problem for me, because Aran Valley is the only region in Spain
> where people speaks occitan. I need just a code.
>
> I send you the locale file.
>
> Thanks
>
>
>> From: toki.kant...@gmail.com
>> Date: Tue, 28 Apr 2015 19:00:18 +
>> To: javierd...@hotmail.com
>> Subject: Aranese Spell Checking
>>
>> Javier:
>>
>> I saw your
Re: RV: Aranese Spell Checking in libreoffice
Hi Matthias,
Is there an AOO issue?
I don't understand.
Thanks,
Carl
On 2/10/22 3:20 PM, Matthias Seidel wrote:
Anyone else?!
This issue is almost 7 years old now...
Regards,
Matthias
Am 08.02.22 um 19:09 schrieb Peter Kovacs:
On 07.02.22 21:17, Matthias Seidel wrote:
Hi all,
Anyone who can help here?
Currently no clue. sorry.
Regards,
Matthias
Am 30.01.22 um 12:01 schrieb Javier T:
Hi Matthias
I have been looking at the LibreOffice code and the Aranese language
is partially defined.
Is already defined
FILE ./svtools/inc/langtab.hrc
{ NC_("STR_ARR_SVT_LANGUAGE_TABLE", "Aranese") ,
LANGUAGE_USER_OCCITAN_ARANESE },
FILE ./include/i18nlangtag
#define LANGUAGE_USER_OCCITAN_ARANESE LanguageType(0x8082)
Remains to be defined
FILE ./i18nlangtag/source/isolang
{ LANGUAGE_USER_OCCITAN_ARANESE, "oc", "ES", k0 },
FILE ./i18npool/Library_localedata_es.mk
CustomTarget/i18npool/localedata/localedata_oc_ES \
FILE ./i18npool/source/localedata/localedata.cxx
{ "oc_ES", lcl_DATA_ES },
add the file
/i18npool/source/localedata/data/oc_ES.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=147053
De: Matthias Seidel
Enviado: Jueves, 27 de Enero de 2022 23:56
Para: dev@openoffice.apache.org
Asunto: Re: RV: Aranese Spell Checking in libreoffice
Hi Javier,
My impression is that LO did somehow enable Aranese for spellchecking.
They never added your localedata (oc_ES.xml), at least I can't find
it in their code.
I am not sure what to think of that, maybe others here have an opinion?
Regards,
Matthias
Am 23.01.22 um 21:44 schrieb Javier T:
Hi Matthias
I have found the mail that I sent them with the modified file that
they indicated to me.
If I remember correctly this was added by the version of libreoffice
5.1
When you open a new document in libreoffice if you select the text,
it lets you define the language of the text or paragraph and
"Aranese" appears there.
When you want to define a language for the document it does not
appear or I know why.
Attached capture and the mail that I tell you.
Thank you.
[cid:part1.65E0CAD6.8A86E85D@hamburg.de]
De: Javier
Enviado: miércoles, 13 de mayo de 2015 22:12
Para: jonathon
Asunto: RE: Aranese Spell Checking
Occitan is composed by these diferent variants.
Alvernès
Bearnès
Creixent
Gascó
Judeoprovençal
Llenguadocià
Montpellerenc (subdialecte)
Niçard
Occità llemosí
Provençal
Vivaroalpí
Aranese is a Gascon dialect spoken in Aran Valley (Spain)
I think that ISO 639 is a realy bad system to define languages an
their dialects.
Nowadays exists 2 spell checkers for libreoffice
oc_FR - I think that is Llenguadocian (but I'm not sure)
gsc_FR - A gascon dialect spell checker.
The correct definition maybe can be
FR_oci_leng
FR_oci_gsc
But this isn't a ISO 639 code. Really I don't have a good solution
for that and I'm not sure what are the diferences between the
diferent dialects.
If you defines a code OCI_fr you need to update the oc_FR spell
checker.
In my case I prefer use oc_ES to standarize with the old
aplications. But I'm not sure what is the best choice to define it
in libreoffice.
You can decide at your own criterion, oc_ES or oci_ES. Really is not
a problem for me, because Aran Valley is the only region in Spain
where people speaks occitan. I need just a code.
I send you the locale file.
Thanks
From: toki.kant...@gmail.com
Date: Tue, 28 Apr 2015 19:00:18 +
To: javierd...@hotmail.com
Subject: Aranese Spell Checking
Javier:
I saw your request for support of Aranese in Apache OpenOffice.
I don't how difference Aranese is from Gascon, nor how different
either
of those are from Occitan.
The primary issue is ISO 639-3 Code OCI, which is for Occitan, and the
various dialects. A spell checker for Aranese will conflict with a
spell
checker for Occitan.
(I am saying that, based on working with spell checkers for various
languages of Southern Africa.)
LibreOffice currently supports Occitan as a language/local.
My suggestion is creating OCI_fr, OCI_ad, OCI_es, and maybe OCI_it as
locales. Get together with users of other dialects/languages that are
classified under OCI, and work up something that is acceptable to
everybody, but still allows them to use the grammar and spell
checkers.
Go to http://www.it46.se/localegen/select_lang.php to create the
locales.
Then either go to https://bugs.documentfoundation.org/buglist.cgi and
file a bug requesting creation of the respective locales, or email the
xml, and I'll do that.
The _only_ reason I'm not creating the locales, is that I have no idea
what the correct information is.
jonathon
---
Hi Javier,
I cannot see oc-ES in LibreOffice.
Re: OOo spelling dictionaries site closed
Hi all, Can we help here? Regards, Matthias Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: > Matthias, Dave, > > Thank you very much for looking into this. > > If you have an equivalent repository that’s open for external access, OmegaT > will need to update its spelling dictionary installation process and inform > current users that the URI currently used needs to be changed (not that > people change of dictionaries that often, but just in case.) > > Regards, > > Jean-Christophe > >> On Feb 6, 2022, at 1:05, Matthias Seidel wrote: >> >> Hi Jean-Christophe, >> >> Thanks for asking here! It is a much better place than Twitter... ;-) >> >> I am wondering if there was a redirection dumped when we switched the >> build system for the homepage? >> >> http://download.services.openoffice.org/files/contrib/dictionaries/ >> seems to be long gone... >> >> @Dave: Do you have more insight? >> >> Regards, >> >>Matthias >> >> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >>> Hello Devs, >>> >>> First, thank you for your hard work on OOo. I used to help with >>> localization when OOo was still managed by Sun. >>> >>> I am (still) currently helping with OmegaT, the free >>> ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries >>> for the spell-checking functionality. >>> >>> The site that’s hard linked in the code is: >>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>> >>> But it seems to be definitely down, even though I seem to remember that it >>> was working a few weeks ago. >>> >>> OmegaT needs the dictionary files and won’t be able to work with the OOo >>> extensions. >>> >>> I understand that such direct access could cause undue load on your >>> servers, and that’s maybe the reason why you took it off-line, but if >>> that’s not the case we would love to be able to keep using your repository, >>> if you still have one. In which case, would you mind letting us know what >>> would be the equivalent URL? >>> >>> Thank you in advance. >>> smime.p7s Description: S/MIME Cryptographic Signature
Re: RV: Aranese Spell Checking in libreoffice
Anyone else?!
This issue is almost 7 years old now...
Regards,
Matthias
Am 08.02.22 um 19:09 schrieb Peter Kovacs:
>
> On 07.02.22 21:17, Matthias Seidel wrote:
>> Hi all,
>>
>> Anyone who can help here?
> Currently no clue. sorry.
>>
>> Regards,
>>
>> Matthias
>>
>> Am 30.01.22 um 12:01 schrieb Javier T:
>>> Hi Matthias
>>>
>>> I have been looking at the LibreOffice code and the Aranese language
>>> is partially defined.
>>>
>>> Is already defined
>>>
>>> FILE ./svtools/inc/langtab.hrc
>>> { NC_("STR_ARR_SVT_LANGUAGE_TABLE", "Aranese") ,
>>> LANGUAGE_USER_OCCITAN_ARANESE },
>>>
>>> FILE ./include/i18nlangtag
>>> #define LANGUAGE_USER_OCCITAN_ARANESE LanguageType(0x8082)
>>>
>>> Remains to be defined
>>>
>>> FILE ./i18nlangtag/source/isolang
>>> { LANGUAGE_USER_OCCITAN_ARANESE, "oc", "ES", k0 },
>>>
>>> FILE ./i18npool/Library_localedata_es.mk
>>> CustomTarget/i18npool/localedata/localedata_oc_ES \
>>>
>>> FILE ./i18npool/source/localedata/localedata.cxx
>>> { "oc_ES", lcl_DATA_ES },
>>>
>>> add the file
>>> /i18npool/source/localedata/data/oc_ES.xml
>>>
>>>
>>>
>>> https://bugs.documentfoundation.org/show_bug.cgi?id=147053
>>>
>>>
>>>
>>> De: Matthias Seidel
>>> Enviado: Jueves, 27 de Enero de 2022 23:56
>>> Para: dev@openoffice.apache.org
>>> Asunto: Re: RV: Aranese Spell Checking in libreoffice
>>>
>>>
>>> Hi Javier,
>>>
>>>
>>> My impression is that LO did somehow enable Aranese for spellchecking.
>>>
>>>
>>> They never added your localedata (oc_ES.xml), at least I can't find
>>> it in their code.
>>>
>>>
>>> I am not sure what to think of that, maybe others here have an opinion?
>>>
>>>
>>> Regards,
>>>
>>>
>>> Matthias
>>>
>>>
>>>
>>> Am 23.01.22 um 21:44 schrieb Javier T:
>>> Hi Matthias
>>>
>>> I have found the mail that I sent them with the modified file that
>>> they indicated to me.
>>>
>>> If I remember correctly this was added by the version of libreoffice
>>> 5.1
>>>
>>> When you open a new document in libreoffice if you select the text,
>>> it lets you define the language of the text or paragraph and
>>> "Aranese" appears there.
>>> When you want to define a language for the document it does not
>>> appear or I know why.
>>> Attached capture and the mail that I tell you.
>>>
>>> Thank you.
>>>
>>>
>>> [cid:part1.65E0CAD6.8A86E85D@hamburg.de]
>>>
>>>
>>>
>>> De: Javier
>>> Enviado: miércoles, 13 de mayo de 2015 22:12
>>> Para: jonathon
>>> Asunto: RE: Aranese Spell Checking
>>>
>>> Occitan is composed by these diferent variants.
>>>
>>> Alvernès
>>>
>>> Bearnès
>>>
>>> Creixent
>>>
>>> Gascó
>>>
>>> Judeoprovençal
>>>
>>> Llenguadocià
>>>
>>> Montpellerenc (subdialecte)
>>>
>>> Niçard
>>>
>>> Occità llemosí
>>>
>>> Provençal
>>>
>>> Vivaroalpí
>>>
>>>
>>> Aranese is a Gascon dialect spoken in Aran Valley (Spain)
>>>
>>> I think that ISO 639 is a realy bad system to define languages an
>>> their dialects.
>>>
>>> Nowadays exists 2 spell checkers for libreoffice
>>>
>>> oc_FR - I think that is Llenguadocian (but I'm not sure)
>>> gsc_FR - A gascon dialect spell checker.
>>>
>>> The correct definition maybe can be
>>> FR_oci_leng
>>> FR_oci_gsc
>>>
>>> But this isn't a ISO 639 code. Really I don't have a good solution
>>> for that and I'm not sure what are the diferences between the
>>> diferent dialects.
>>>
>>> If you defines a code OCI_fr you need to update the oc_FR spell
>>> checker.
>>>
>>> In my case I prefer use oc_ES to standarize with the old
>>> aplications. But I'm not sure what is the best choice to define it
>>> in libreoffice.
>>>
>>> You can decide at your own criterion, oc_ES or oci_ES. Really is not
>>> a problem for me, because Aran Valley is the only region in Spain
>>> where people speaks occitan. I need just a code.
>>>
>>> I send you the locale file.
>>>
>>> Thanks
>>>
>>>
From: toki.kant...@gmail.com
Date: Tue, 28 Apr 2015 19:00:18 +
To: javierd...@hotmail.com
Subject: Aranese Spell Checking
Javier:
I saw your request for support of Aranese in Apache OpenOffice.
I don't how difference Aranese is from Gascon, nor how different
either
of those are from Occitan.
The primary issue is ISO 639-3 Code OCI, which is for Occitan, and the
various dialects. A spell checker for Aranese will conflict with a
spell
checker for Occitan.
(I am saying that, based on working with spell checkers for various
languages of Southern Africa.)
LibreOffice currently supports Occitan as a language/local.
My suggestion is creating OCI_fr, OCI_ad, OCI_es, and maybe OCI_it as
locales. Get together with users of other dialects/languages that are
classified under OCI, and work up
Re: OpenOffice wordmark exploration (yet without the "Apache" mention)
Hi Corentin, I don't know what to think because your attachment doesn't come through on the mailing list. ;-) Can you provide it in another way? Regards, Matthias Am 10.02.22 um 20:44 schrieb Corentin Verbreghe: > What do you think ? > > Le jeu. 10 févr. 2022 à 20:00, Corentin Verbreghe > mailto:corentin.verbreg...@gmail.com>> > a écrit : > > Hi, there's an exploration for the AOO wordmark. > image.png > Don't hesitate to give your opinion. > Cordially. > Corentin Verbrèghe > smime.p7s Description: S/MIME Cryptographic Signature
Re: OpenOffice wordmark exploration (yet without the "Apache" mention)
What do you think ? Le jeu. 10 févr. 2022 à 20:00, Corentin Verbreghe < corentin.verbreg...@gmail.com> a écrit : > Hi, there's an exploration for the AOO wordmark. > [image: image.png] > Don't hesitate to give your opinion. > Cordially. > Corentin Verbrèghe >
Re: Openssl, serf and curl... and NSS
Just a quick, small update: On Thu, Feb 10, 2022 at 08:12:02PM +0100, Arrigo Marchiori wrote: > Hello Carl, > > On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: [...] > > Asul has x86-64 JDK's available for Java 7 but that's all. > > > > https://www.azul.com/downloads/?version=java-7-lts=macos=jdk > > I will try that! Installed, detected, new build of AOO41X in progress! :-) Thank you! Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hello Carl, On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: > Hi Arrigo, > > On 2/10/22 11:00 AM, Arrigo Marchiori wrote: > > Hello Matthias, > > > > On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: > > > > > Hi Arrigo, > > > > > > Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: > > > > Dear Jim, Matthias, All, > > > > > > > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > > > > > > > > > That's right... I'll wait to even try compiling until things settle > > > > > down and we have some slowly moving target I can compile and build > > > > > against. > > > > > > > > > > > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > > > > > > wrote: > > > > > > > > > > > > Hi Arrigo, > > > > > > > > > > > > No need to apologize. ;-) > > > > > > > > > > > > But I think, before we begin to think about upgrading serf we need > > > > > > to > > > > > > make sure that AOO41X is able to build successfully on all > > > > > > platforms. > > > > > > > > > > > > Windows and Linux are OK, I think. macOS is still pending? > > > > AOO41X now builds under Catalina, with a single edit to the official > > > > build script: AOO_JAVA_VERSION=1.8 > > > So you build with Java 8? > > The official build script contains the setting: > > AOO_JAVA_VERSION=1.7 > > > > On our Mac mini, the script fails because Java 1.7 is not installed, > > and it does not seem to be available on-line for download. > > What is the architecture of the Mac Mini? % uname -a Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64 > Asul has x86-64 JDK's available for Java 7 but that's all. > > https://www.azul.com/downloads/?version=java-7-lts=macos=jdk I will try that! Please allow me to state I had no intention to ``subvert'' current versions of Java or whatever. For what I understand, Catalina and the XCode versions installed in our Mac mini do not match the reference macOS version and tools for our AOO41X builds, and this is absolutely fine for me, as long as there is someone else who has a system with the ``official'' architecture and is able to use it. I am just trying to have a (whatever version of) macOS building AOO, so that when I commit something, I can test on that architecture as well. And possibly lower the barriers to entry for others. So if any of my edits break the builds on ``official machines'', please let us just revert them. The Java version change was not even committed anywhere. ;-) Thank you for reading through my disclaimer. ;-) Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
OpenOffice wordmark exploration (yet without the "Apache" mention)
Hi, there's an exploration for the AOO wordmark. [image: image.png] Don't hesitate to give your opinion. Cordially. Corentin Verbrèghe
Re: Openssl, serf and curl... and NSS
Hi All, On 2/10/22 1:13 PM, Matthias Seidel wrote: Hi Pedro, Am 10.02.22 um 18:16 schrieb Pedro Lino: Hi Matthias, all On 02/10/2022 4:29 PM Matthias Seidel wrote: I think Jim has Java 7 available, since we always built AOO41X with it. Is there any reason for not updating to Java 8 which is still maintained? Maybe we can let go of Java 7? I'm I correct that Arrigo was only proving the build in this particular machine ans using Java 8 because that is what was available on that machine? I don't think our official build for the 4.1 branch should change to Java 8. I'm all for dumping Java 7 on 4.2 and would support at least Java 11 on trunk if possible because Java 8 is EOL now I believe. But the Java for 4.2 and beyond is for another day. We shouldn't switch the JAVA version within AOO41X without decent testing. Or at all for the release build IMHO. Of course it builds, but I remember some problems with JavaDoc? I remember there was work done on Javadoc and it may have been from 6 to 7 but I'd have to research that. Best regards, Carl Regards, Matthias Regards, Pedro - 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: Openssl, serf and curl... and NSS
Hi Pedro, Am 10.02.22 um 18:16 schrieb Pedro Lino: > Hi Matthias, all > >> On 02/10/2022 4:29 PM Matthias Seidel wrote: > >> I think Jim has Java 7 available, since we always built AOO41X with it. > Is there any reason for not updating to Java 8 which is still maintained? > Maybe we can let go of Java 7? We shouldn't switch the JAVA version within AOO41X without decent testing. Of course it builds, but I remember some problems with JavaDoc? Regards, Matthias > > 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: Openssl, serf and curl... and NSS
Hi Matthias, all > On 02/10/2022 4:29 PM Matthias Seidel wrote: > I think Jim has Java 7 available, since we always built AOO41X with it. Is there any reason for not updating to Java 8 which is still maintained? Maybe we can let go of Java 7? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, On 2/10/22 11:00 AM, Arrigo Marchiori wrote: Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. On Feb 8, 2022, at 6:06 AM, Matthias Seidel wrote: Hi Arrigo, No need to apologize. ;-) But I think, before we begin to think about upgrading serf we need to make sure that AOO41X is able to build successfully on all platforms. Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. What is the architecture of the Mac Mini? Asul has x86-64 JDK's available for Java 7 but that's all. https://www.azul.com/downloads/?version=java-7-lts=macos=jdk Thanks, Carl I found Java 8 installed, and that's why I changed the setting. I hope it makes sense. Best regards, - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, Am 10.02.22 um 17:00 schrieb Arrigo Marchiori: > Hello Matthias, > > On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: > >> Hi Arrigo, >> >> Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: >>> Dear Jim, Matthias, All, >>> >>> On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: >>> That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > wrote: > > Hi Arrigo, > > No need to apologize. ;-) > > But I think, before we begin to think about upgrading serf we need to > make sure that AOO41X is able to build successfully on all platforms. > > Windows and Linux are OK, I think. macOS is still pending? >>> AOO41X now builds under Catalina, with a single edit to the official >>> build script: AOO_JAVA_VERSION=1.8 >> So you build with Java 8? > The official build script contains the setting: > AOO_JAVA_VERSION=1.7 > > On our Mac mini, the script fails because Java 1.7 is not installed, > and it does not seem to be available on-line for download. > > I found Java 8 installed, and that's why I changed the setting. > > I hope it makes sense. Thanks for the clarification. I think Jim has Java 7 available, since we always built AOO41X with it. Regards, Matthias > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: > Hi Arrigo, > > Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: > > Dear Jim, Matthias, All, > > > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > > > >> That's right... I'll wait to even try compiling until things settle > >> down and we have some slowly moving target I can compile and build > >> against. > >> > >>> On Feb 8, 2022, at 6:06 AM, Matthias Seidel > >>> wrote: > >>> > >>> Hi Arrigo, > >>> > >>> No need to apologize. ;-) > >>> > >>> But I think, before we begin to think about upgrading serf we need to > >>> make sure that AOO41X is able to build successfully on all platforms. > >>> > >>> Windows and Linux are OK, I think. macOS is still pending? > > AOO41X now builds under Catalina, with a single edit to the official > > build script: AOO_JAVA_VERSION=1.8 > > So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. I found Java 8 installed, and that's why I changed the setting. I hope it makes sense. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: > Dear Jim, Matthias, All, > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > >> That's right... I'll wait to even try compiling until things settle >> down and we have some slowly moving target I can compile and build >> against. >> >>> On Feb 8, 2022, at 6:06 AM, Matthias Seidel >>> wrote: >>> >>> Hi Arrigo, >>> >>> No need to apologize. ;-) >>> >>> But I think, before we begin to think about upgrading serf we need to >>> make sure that AOO41X is able to build successfully on all platforms. >>> >>> Windows and Linux are OK, I think. macOS is still pending? > AOO41X now builds under Catalina, with a single edit to the official > build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? Regards, Matthias > > I suggest this is a good candidate. Please note that the serf upgrade > is _not_ yet merged. > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > That's right... I'll wait to even try compiling until things settle > down and we have some slowly moving target I can compile and build > against. > > > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > > wrote: > > > > Hi Arrigo, > > > > No need to apologize. ;-) > > > > But I think, before we begin to think about upgrading serf we need to > > make sure that AOO41X is able to build successfully on all platforms. > > > > Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 I suggest this is a good candidate. Please note that the serf upgrade is _not_ yet merged. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
