Pilot-Pirx merged PR #210:
URL: https://github.com/apache/openoffice/pull/210
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #210:
URL: https://github.com/apache/openoffice/pull/210
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #209:
URL: https://github.com/apache/openoffice/pull/209
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #209:
URL: https://github.com/apache/openoffice/pull/209
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx commented on PR #208:
URL: https://github.com/apache/openoffice/pull/208#issuecomment-2029737332
Thanks again!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
Pilot-Pirx merged PR #208:
URL: https://github.com/apache/openoffice/pull/208
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #208:
URL: https://github.com/apache/openoffice/pull/208
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #207:
URL: https://github.com/apache/openoffice/pull/207
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #207:
URL: https://github.com/apache/openoffice/pull/207
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #205:
URL: https://github.com/apache/openoffice/pull/205
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #205:
URL: https://github.com/apache/openoffice/pull/205
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #204:
URL: https://github.com/apache/openoffice/pull/204
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #204:
URL: https://github.com/apache/openoffice/pull/204
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #203:
URL: https://github.com/apache/openoffice/pull/203
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
Pilot-Pirx commented on PR #203:
URL: https://github.com/apache/openoffice/pull/203#issuecomment-1957180180
Looks good to me!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
jbampton opened a new pull request, #203:
URL: https://github.com/apache/openoffice/pull/203
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
jbampton opened a new pull request, #190:
URL: https://github.com/apache/openoffice/pull/190
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx commented on code in PR #189:
URL: https://github.com/apache/openoffice/pull/189#discussion_r1412429050
##
main/qadevOOo/tests/basic/ifc/awt/XListBox/awt_XListBox.xba:
##
Review Comment:
Good find!
--
This is an automated message from the Apache Git Service.
Pilot-Pirx merged PR #189:
URL: https://github.com/apache/openoffice/pull/189
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #189:
URL: https://github.com/apache/openoffice/pull/189
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #188:
URL: https://github.com/apache/openoffice/pull/188
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #188:
URL: https://github.com/apache/openoffice/pull/188
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #187:
URL: https://github.com/apache/openoffice/pull/187
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
Pilot-Pirx commented on PR #187:
URL: https://github.com/apache/openoffice/pull/187#issuecomment-1834012356
Typos and grammar are an endless story in our code.
But situation improves with every Pull Request! ;-)
--
This is an automated message from the Apache Git Service.
To respond to
jbampton opened a new pull request, #187:
URL: https://github.com/apache/openoffice/pull/187
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx commented on PR #186:
URL: https://github.com/apache/openoffice/pull/186#issuecomment-1829502837
Thanks again!
I added some small changes regarding German Umlaute and Unicode.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
Pilot-Pirx merged PR #186:
URL: https://github.com/apache/openoffice/pull/186
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #186:
URL: https://github.com/apache/openoffice/pull/186
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #185:
URL: https://github.com/apache/openoffice/pull/185
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
Pilot-Pirx commented on code in PR #185:
URL: https://github.com/apache/openoffice/pull/185#discussion_r1404883590
##
test/testcommon/source/org/openoffice/test/vcl/client/CommandCaller.java:
##
Review Comment:
This is a typo in one of our Java classes, see:
jbampton opened a new pull request, #185:
URL: https://github.com/apache/openoffice/pull/185
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
dave2wave merged PR #89:
URL: https://github.com/apache/openoffice-org/pull/89
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #89:
URL: https://github.com/apache/openoffice-org/pull/89
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
dave2wave merged PR #88:
URL: https://github.com/apache/openoffice-org/pull/88
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
dave2wave commented on PR #88:
URL: https://github.com/apache/openoffice-org/pull/88#issuecomment-1817937929
This script is completely obsolete and was only used to move OpenOffice.org
website from Oracle's Kenai CMS to the Apache CMS. We are now using a different
website build. I will
Pilot-Pirx merged PR #184:
URL: https://github.com/apache/openoffice/pull/184
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
ardovm commented on code in PR #184:
URL: https://github.com/apache/openoffice/pull/184#discussion_r1398373585
##
main/winaccessibility/source/UAccCOM/MAccessible.h:
##
Review Comment:
I would normally be very reluctant to rename methods as we are doing here.
However,
jbampton opened a new pull request, #88:
URL: https://github.com/apache/openoffice-org/pull/88
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
ardovm commented on code in PR #184:
URL: https://github.com/apache/openoffice/pull/184#discussion_r1395766868
##
main/offapi/com/sun/star/awt/XListBox.idl:
##
Review Comment:
Being it a long standing API, IMHO we should be very very motivated in order
to change it.
I
Pilot-Pirx commented on code in PR #184:
URL: https://github.com/apache/openoffice/pull/184#discussion_r1395752148
##
main/offapi/com/sun/star/awt/XListBox.idl:
##
Review Comment:
https://www.openoffice.org/api/docs/common/ref/com/sun/star/awt/XListBox.html#isMutipleMode
Pilot-Pirx commented on code in PR #184:
URL: https://github.com/apache/openoffice/pull/184#discussion_r1395640262
##
main/offapi/com/sun/star/awt/XListBox.idl:
##
Review Comment:
This is a historical typo in our API. I think we would need to address both
versions and set
Pilot-Pirx commented on code in PR #184:
URL: https://github.com/apache/openoffice/pull/184#discussion_r1395640262
##
main/offapi/com/sun/star/awt/XListBox.idl:
##
Review Comment:
This is a historical typo in our API. I think we would need to address both
versions and set
jbampton opened a new pull request, #184:
URL: https://github.com/apache/openoffice/pull/184
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx commented on PR #183:
URL: https://github.com/apache/openoffice/pull/183#issuecomment-1812959537
Thanks again!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
Pilot-Pirx merged PR #183:
URL: https://github.com/apache/openoffice/pull/183
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #183:
URL: https://github.com/apache/openoffice/pull/183
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Pilot-Pirx merged PR #182:
URL: https://github.com/apache/openoffice/pull/182
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jbampton opened a new pull request, #182:
URL: https://github.com/apache/openoffice/pull/182
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
On 10/03/22 Pedro Lino wrote:
Thanks to Andrea's clear instructions we now have one more trained "staff" to
do this update ;)
Thank you for taking over! I'll try to get the instructions posted to
some "official" shared space by this weekend.
Regards,
Andrea.
Hi Marcus,
Am 10.03.22 um 21:12 schrieb Marcus:
> Am 10.03.22 um 18:21 schrieb Matthias Seidel:
>> Am 10.03.22 um 17:52 schrieb Pedro Lino:
>>>
>>> Yes, it was updated on March 1st
>>>
>>> Thanks to Andrea's clear instructions we now have one more trained
>>> "staff" to do this update ;)
>>>
>>>
Am 10.03.22 um 18:21 schrieb Matthias Seidel:
Am 10.03.22 um 17:52 schrieb Pedro Lino:
Yes, it was updated on March 1st
Thanks to Andrea's clear instructions we now have one more trained "staff" to
do this update ;)
I can confirm that it also works perfectly under Linux using the 4.1.12
Hi Pedro,
Am 10.03.22 um 17:52 schrieb Pedro Lino:
> Hi Matthias
>
> Yes, it was updated on March 1st
>
> Thanks to Andrea's clear instructions we now have one more trained "staff" to
> do this update ;)
>
> I can confirm that it also works perfectly under Linux using the 4.1.12
> Nightly
Hi Matthias
Yes, it was updated on March 1st
Thanks to Andrea's clear instructions we now have one more trained "staff" to
do this update ;)
I can confirm that it also works perfectly under Linux using the 4.1.12 Nightly
builds
Maybe this is a good enough motive to release 4.1.12 to all?
Hi Pedro, all,
Am 19.02.22 um 17:56 schrieb Pedro Lino:
> Hi Andrea, all
>
>> On 02/13/2022 10:11 PM Andrea Pescetti wrote:
>> I'm assuming lazy consensus on giving you permissions on the Extensions
>> site (not the site itself, actually, but the shell access). You should
>> post here your
On 20.02.22 00:41, Andrea Pescetti wrote:
On 19/02/22 Pedro Lino wrote:
no one opposes that I have permissions on the Extensions shell access?
Done! You have it now.
Who can handle this so you can teach me further steps?
I've written extensive documentation with the aim of adding it to
On 19/02/22 Pedro Lino wrote:
no one opposes that I have permissions on the Extensions shell access?
Done! You have it now.
Who can handle this so you can teach me further steps?
I've written extensive documentation with the aim of adding it to
Hi Andrea, all
> On 02/13/2022 10:11 PM Andrea Pescetti wrote:
> I'm assuming lazy consensus on giving you permissions on the Extensions
> site (not the site itself, actually, but the shell access). You should
> post here your SourceForge username for you to be added.
>
> Once we are ready
Hi Andrea
> On 02/13/2022 10:11 PM Andrea Pescetti wrote:
> I had to try a lot of times since apparently the process changed since
> the last time I checked this, but I was able to login at last and it's
> still weekend!
Thank you for taking some time to do this and for testing first!
>
On 11/02/22 Pedro Lino wrote:
Do you have time for this issue during this weekend?
Hello Pedro,
I had to try a lot of times since apparently the process changed since
the last time I checked this, but I was able to login at last and it's
still weekend!
So, the first steps on your side,
megaT 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
Hi Andrea
Do you have time for this issue during this weekend?
Regards,
Pedro
> On 02/03/2022 11:01 PM Andrea Pescetti wrote:
>
>
> Pedro Lino wrote:
> > I found some odd results. If the user has an older than 2017 version of the
> > dictionary, the Extension Update dialog will report that
o 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
thias
>
> 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 tha
oking 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.)
Re
?
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 reposito
,
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
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 s
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
h 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 definite
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
Hi Andrea
Thank you for the fast reply!
> On 02/03/2022 11:01 PM Andrea Pescetti wrote:
> The update feed, much like the one we use for OpenOffice itself, has
> information on the latest available version. If you don't update it (I
> mean, "updating the update feed") for a while it will
Pedro Lino wrote:
I found some odd results. If the user has an older than 2017 version of the dictionary,
the Extension Update dialog will report that version 2017.05.01 is available. If the user
has the 2017.05.01 version or newer it will always report that "No new updates are
available."
Returning to this subject:
I found some odd results. If the user has an older than 2017 version of the
dictionary, the Extension Update dialog will report that version 2017.05.01 is
available. If the user has the 2017.05.01 version or newer it will always
report that "No new updates are
Hi Matthias
> On 02/03/2022 11:04 AM Matthias Seidel wrote:
> Is it possible to re-activate the update feed for SourceForge?
I'm available to do this if someone helps me. Andrea?
Regards,
Pedro
> Am 15.03.21 um 21:12 schrieb Pedro Lino:
> > Hi again Andrea
> >
> > Marco has released two
Hi Pedro, all,
Bumping this one up:
Is it possible to re-activate the update feed for SourceForge?
Regards,
Matthias
Am 15.03.21 um 21:12 schrieb Pedro Lino:
> Hi again Andrea
>
> Marco has released two versions since the one included in AOO 4.1.9
>
> Can you update this or teach us how to
Hi again Andrea
Marco has released two versions since the one included in AOO 4.1.9
Can you update this or teach us how to do it?
Thanks!
Regards,
Pedro
> On 03/10/2021 4:42 PM Matthias Seidel wrote:
>
>
> Hi Andrea,
>
> When would be the best time for an update?
>
> Regards,
>
>
Hi Andrea,
When would be the best time for an update?
Regards,
Matthias
Am 22.01.21 um 00:39 schrieb Andrea Pescetti:
> On 21/01/2021 Pedro Lino wrote:
>>> Please let me know if it works; if it does, I will then revert it and
>>> republish only after 4.1.9 is out ...
>> It is fixed indeed
Hi Andrea
> On 01/21/2021 11:39 PM Andrea Pescetti wrote:
> OK, thank you for checking. I've now reverted the fix and we'll go live
> with a more complete version when people will have upgraded to 4.1.9.
Agreed. Thank you!
> But when we are not in proximity of a release, we can trigger the
On 21/01/2021 Pedro Lino wrote:
Please let me know if it works; if it does, I will then revert it and
republish only after 4.1.9 is out ...
It is fixed indeed (although I get 2 notifications for that extension, but one
problem at a time!). Thanks!
OK, thank you for checking. I've now
Hi Andrea
> On 01/21/2021 8:04 PM Andrea Pescetti wrote:
> I believe it's fixed now (limited to the specific case of the English
> dictionary; I had to find some workarounds so I enabled only that
> extension for testing).
> Please let me know if it works; if it does, I will then revert it
Am 21.01.21 um 21:04 schrieb Andrea Pescetti:
On 20/01/2021 Andrea Pescetti wrote:
I think we can fix it. Let me give it a try tomorrow.
I believe it's fixed now (limited to the specific case of the English
dictionary; I had to find some workarounds so I enabled only that
extension for
On 20/01/2021 Andrea Pescetti wrote:
I think we can fix it. Let me give it a try tomorrow.
I believe it's fixed now (limited to the specific case of the English
dictionary; I had to find some workarounds so I enabled only that
extension for testing).
Please let me know if it works; if it
Hi Andrea
> On 01/20/2021 10:23 PM Andrea Pescetti wrote:
> I think we can fix it. Let me give it a try tomorrow.
Excellent! Thanks!
> What I can do tomorrow is: I can check whether our (site moderator)
> access is enough to push the updated feed live; and I'll document it
> internally in
On 20/01/2021 Matthias Seidel wrote:
Am 20.01.21 um 00:47 schrieb Pedro Lino:
On 01/19/2021 5:38 PM Matthias Seidel wrote:
In this case it looks for the feed on the SourceForge server. My guess is,
that these feeds are not generated anymore.
I don't know if this was an automatic
Hi Pedro,
Am 20.01.21 um 00:47 schrieb Pedro Lino:
> Hi Matthias, Marco, all
>
>
>> On 01/19/2021 5:38 PM Matthias Seidel wrote:
>>
>> AOO is looking for an "update feed", quite similar to the release
>> updates.
>> (Release update feeds are generated by hand after every release)
>>
Hi Matthias, Marco, all
> On 01/19/2021 5:38 PM Matthias Seidel wrote:
>
> AOO is looking for an "update feed", quite similar to the release updates.
> (Release update feeds are generated by hand after every release)
>
> In this case it looks for the feed on the SourceForge
umber of the extension
> and the release notes.
>
> Not sure why it happens.
>
> On 19/01/2021 12:04, Pedro Lino wrote:
>> Hi all
>>
>> I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the
>> English spelling extension I have installed is from 20
Hi Czeslaw
> On 01/19/2021 1:14 PM Czesław Wolański wrote:
> 4.1.9 RC1, Windows 7
> English spelling extension:
> I can confirm your observation - checking for update of any version
> (2020.07.01 - 2020.12.01)
> results in a message "No new updates are available."
mber of the extension
> and the release notes.
>
> Not sure why it happens.
>
> On 19/01/2021 12:04, Pedro Lino wrote:
>
> > >
> > Hi all
> >
> > I am testing version 4.1.9 RC1 under Windows 7 and I just noticed
> >
under Windows 7 and I just noticed that the
English spelling extension I have installed is from 2020.07.01 but Checking for
updates does not report any new version.
This is particularly odd because this extension is updated monthly (including
in January 2021).
Installing an older version of another
Hi Pedro,
4.1.9 RC1, Windows 7
English spelling extension:
I can confirm your observation - checking for update of any version
(2020.07.01 - 2020.12.01)
results in a message "No new updates are available.".
Regards,
Czesław
Am Di., 19. Jan. 2021 um 13:04 Uhr schrieb Pedro Lino
:
>
Hi all
I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the
English spelling extension I have installed is from 2020.07.01 but Checking for
updates does not report any new version.
This is particularly odd because this extension is updated monthly (including
in January
> >
> > The hyphenation and other formatting information is on the Hunspell site
> > https://hunspell.github.io/
> >
Actually this is the spelling assistant not the hyphenator. This module is
described in the following URL:
https://www.openoffice.org/lingucomponent/
On Sat, 2 Jul 2016 21:29:07 +0300
Απόστολος Συρόπουλος <asyropoulos...@hotmail.com> wrote:
> >Date: Wed, 29 Jun 2016 14:58:34 -0400
> > From: lui...@gmail.com
> > To: dev@openoffice.apache.org
> > Subject: Re: Spelling of Ancient Greek
> >
> >
> &
>Date: Wed, 29 Jun 2016 14:58:34 -0400
> From: lui...@gmail.com
> To: dev@openoffice.apache.org
> Subject: Re: Spelling of Ancient Greek
>
>
> louis=C2=A0
>
Which means what? BTW, let me ask again: Where are the
hyphenation files and how they are created?
A.S.
louis=C2=A0
-Original Message-
=46rom:=C2=A0=CE=91=CF=80=CF=8C=CF=83=CF=84=CE=BF=CE=BB=CE=BF=CF=82 =CE=A3=
=CF=85=CF=81=CF=8C=CF=80=CE=BF=CF=85=CE=BB=CE=BF=CF=82
Hello,
Suppose i would like to prepare a document in ancient Greek using AOO.
Naturally, I would like to enable hyphenation. To the best of my knowledge,
AOO is borrowing UTF-8 hyphenation patterns that are used in the TeX world.
If this is true, could you please let me know how can I create a
quire a development offered as open source under
HMaCB> the Apache License. This would, by the way, probably impair the
HMaCB> use of spelling lexicons that are provided under incompatible
HMaCB> licenses and probably unwelcome at Microsoft.
HMaCB> It seems to me that the closely-held
-checker for a given language.
CONCLUSION
To provide implementations of such DLLs at Apache OpenOffice, these would
require a development offered as open source under the Apache License. This
would, by the way, probably impair the use of spelling lexicons that are
provided under incompatible
Hello Dennis,
Friday, May 27, 2016, 8:31:25 PM, you wrote:
DEH> PS: Minor clarification: The request was for AOO to *be* or
DEH> *provide* a spell checker available to other programs via the
DEH> CSAPI on Windows. In any case, there is no reason for us to go down that
road.
If it can't be
1 - 100 of 122 matches
Mail list logo
