RE: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be implemented

[Dennis E. Hamilton]

Remarks in-line

> -Original Message-
> From: Howard Morris (aka Col Boogie)
> [mailto:howard_cary_mor...@hotmail.com]
> Sent: Thursday, May 26, 2016 13:12
> To: dennis.hamil...@acm.org; dev@openoffice.apache.org
> Cc: 'Zhuravliov Alexey Gennadyevich' 
> Subject: Re: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be
> implemented
> 
> I am not sure why this is being discussed.
[orcmid] 

The request was that the spell-checking functionality of Apache OpenOffice be 
made available in some manner via CSAPI on Windows, so other Windows 
applications could make use of the different language lexicons that are 
distributed as (third-party) Apache OpenOffice extensions.


> See https://hunspell.github.io/
[orcmid] 

Apache OpenOffice can include Hunspell (under the MPL 1.1 option) in binary 
form only.  If it is installed as part of the official Apache OpenOffice 
distributions, it does not appear to be in a form where it is available for use 
by other programs.

The lexicons are separate.  

> I recently came across something that Firefox and Open office were set
> to share their spell checker.
> That would be nice.
[orcmid] 

We use third-party lexicons.  We are not part of arrangements by which other 
parties use (forms of) them too.

To the best of my knowledge, there is no joint activity between the projects, 
although AOO code could be adapted, if useful, without our having to know about 
it.


> 
> Howard
> ___
> I have examined some of the materials available for the CSAPI.
> 
[ ... ] 
> It seems to me that the closely-held nature of the CSAPI and requirement
> for license agreements is completely out of scope for Apache OpenOffice
> and not compatible with policies of the Apache Software Foundation.
> This is simply a road we cannot go down.
> 
> I suggest that we not go any farther investigating this proposal unless
> those encumbrances disappear.
> 
> - Dennis
> 
> PS: A third party could engage with Microsoft and supply a CSAPI-
> accepting implementation.  That might employ the same tools that AOO
> employs for processing supplied lexicons.  The third party would have to
> navigate the licenses on such lexicons as well and ensure that this does
> not introduce any licensing condition that is unacceptable to Microsoft.
> The independent third party also might not be so opposed to empowering
> the use of CSAPI-delivered spelling checkers by Microsoft products as I
> imagine the contributors of lexicons to AOO might be.
> 
> > -Original Message-
> > From: Alexey Zhuravliov [mailto:alexz...@voliacable.com]
> > Sent: Thursday, May 26, 2016 02:46
> > To: Rory O'Farrell 
> > Subject: Re: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can
> be
> > implemented
> >
> > Hello Rory,
> >
> > Wednesday, May 25, 2016, 9:27:48 PM, you wrote:
> >
> > >> DEH>> Please provide more information about the Common Spelling API
> >
> > ROF> Unless this does something dramatically different and improved
> > ROF> from the existing spelling system, the English dictionary of
> > ROF> which is very well serviced by Marcus, I suggest that, on the "If
> > ROF> it's not broke don't fix it" principle we should leave the
> spelling
> > system alone.
> >
> > This  could  be  new  and useful feature when other programs could use
> > AOO's  spell  checking  engine. If MS's API can't be implemented maybe
> > AOO developers can create a new interface.
> >
> > >> >>> Can  Common Spelling API (which was in MS Office up to version
> > 2000 as
> > >> >>> far  as  I know) be implemented in AOO on Windows.
> > --
> > Best regards,
> > Alexey Zhuravliov
> >
> >
> > -
> > 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



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [PROPOSAL] Removing all tracking from AOO sites

[Kay Schenk]

On 05/20/2016 12:19 PM, Pedro Giffuni wrote:

In reply to Kay;
...


Ever heard of Big Data? This information will be correlated along with
the latest
searches and will be sold for commercial value to other companies and
will also
likely be available to the governments of the world at request. For
whatever
Mr. Trump may find it useful is another matter.


I understand broadly what your concerns are. But really, in this day and
age, almost ANY website you visit has some sort of tracking mechanisnm
in place. Next time you "visit" anywhere, you might want to check this.



That others do it, doesn't mean we should. Do we at least respect the
"do not track" settings in the browser?


Well...I've been looking in this as well as communicating with Rob Weir 
who originally set up our GA process. I would *think* but can't verify 
for sure if DNT is respected by Google Analytics. Without knowing the 
internals of what happens with this option -- does the browser actually 
DO something to your IP address for example to cause this to happen or 
??? -- it's difficult to answer this. There is another option in GA 
we're not currently using, anonymize_IP, which I'm investigating. We 
will definitely add this option as soon as I can figure this out.







Worst of all, we are not getting any value from this tracking ... let's
stop it now.


Well this last statement is NOT true. For the download page especially,
it is valuable because we can find out generally what OS the user is
using, complete with version information. I mean in a bulk sense.



How valuable is that? How does us it bring us any nearer towards having
an Android/iOS port? We already have counts from downloads statistics
and we know at least 80% of our users get the Windows port.

Pedro.




--

MzK

"Time spent with cats is never wasted."
   -- Sigmund Freud

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be implemented

[Howard Morris (aka Col Boogie)]

I am not sure why this is being discussed.
See https://hunspell.github.io/
I recently came across something that Firefox and Open office were set to share 
their spell checker.
That would be nice.

Howard
___
I have examined some of the materials available for the CSAPI.

Here are my initial observations:

1. The CSAPI is closely-held by Microsoft.  It is evidently not part of their 
Open Specifications set.

2. Apparently a license agreement is required in order to have the necessary 
materials and also learn of any maintenance/change to the API over time.

3. The implementation is via a DLL that can be registered on Microsoft Windows 
and thereby relied upon by Microsoft Office products that will use the CSAPI to 
access a spell-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 licenses and probably unwelcome at Microsoft.

It seems to me that the closely-held nature of the CSAPI and requirement for 
license agreements is completely out of scope for Apache OpenOffice and not 
compatible with policies of the Apache Software Foundation.  This is simply a 
road we cannot go down.  

I suggest that we not go any farther investigating this proposal unless those 
encumbrances disappear.

- Dennis

PS: A third party could engage with Microsoft and supply a CSAPI-accepting 
implementation.  That might employ the same tools that AOO employs for 
processing supplied lexicons.  The third party would have to navigate the 
licenses on such lexicons as well and ensure that this does not introduce any 
licensing condition that is unacceptable to Microsoft.  The independent third 
party also might not be so opposed to empowering the use of CSAPI-delivered 
spelling checkers by Microsoft products as I imagine the contributors of 
lexicons to AOO might be.

> -Original Message-
> From: Alexey Zhuravliov [mailto:alexz...@voliacable.com]
> Sent: Thursday, May 26, 2016 02:46
> To: Rory O'Farrell 
> Subject: Re: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be
> implemented
> 
> Hello Rory,
> 
> Wednesday, May 25, 2016, 9:27:48 PM, you wrote:
> 
> >> DEH>> Please provide more information about the Common Spelling API
> 
> ROF> Unless this does something dramatically different and improved
> ROF> from the existing spelling system, the English dictionary of
> ROF> which is very well serviced by Marcus, I suggest that, on the "If
> ROF> it's not broke don't fix it" principle we should leave the spelling
> system alone.
> 
> This  could  be  new  and useful feature when other programs could use
> AOO's  spell  checking  engine. If MS's API can't be implemented maybe
> AOO developers can create a new interface.
> 
> >> >>> Can  Common Spelling API (which was in MS Office up to version
> 2000 as
> >> >>> far  as  I know) be implemented in AOO on Windows.
> --
> Best regards,
> Alexey Zhuravliov
> 
> 
> -
> 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: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be implemented

[Dennis E. Hamilton]

I have examined some of the materials available for the CSAPI.

Here are my initial observations:

 1. The CSAPI is closely-held by Microsoft.  It is evidently not part of their 
Open Specifications set.

 2. Apparently a license agreement is required in order to have the necessary 
materials and also learn of any maintenance/change to the API over time.

 3. The implementation is via a DLL that can be registered on Microsoft Windows 
and thereby relied upon by Microsoft Office products that will use the CSAPI to 
access a spell-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 licenses and probably unwelcome at Microsoft.

It seems to me that the closely-held nature of the CSAPI and requirement for 
license agreements is completely out of scope for Apache OpenOffice and not 
compatible with policies of the Apache Software Foundation.  This is simply a 
road we cannot go down.  

I suggest that we not go any farther investigating this proposal unless those 
encumbrances disappear.

 - Dennis

PS: A third party could engage with Microsoft and supply a CSAPI-accepting 
implementation.  That might employ the same tools that AOO employs for 
processing supplied lexicons.  The third party would have to navigate the 
licenses on such lexicons as well and ensure that this does not introduce any 
licensing condition that is unacceptable to Microsoft.  The independent third 
party also might not be so opposed to empowering the use of CSAPI-delivered 
spelling checkers by Microsoft products as I imagine the contributors of 
lexicons to AOO might be.

> -Original Message-
> From: Alexey Zhuravliov [mailto:alexz...@voliacable.com]
> Sent: Thursday, May 26, 2016 02:46
> To: Rory O'Farrell 
> Subject: Re: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be
> implemented
> 
> Hello Rory,
> 
> Wednesday, May 25, 2016, 9:27:48 PM, you wrote:
> 
> >> DEH>> Please provide more information about the Common Spelling API
> 
> ROF> Unless this does something dramatically different and improved
> ROF> from the existing spelling system, the English dictionary of
> ROF> which is very well serviced by Marcus, I suggest that, on the "If
> ROF> it's not broke don't fix it" principle we should leave the spelling
> system alone.
> 
> This  could  be  new  and useful feature when other programs could use
> AOO's  spell  checking  engine. If MS's API can't be implemented maybe
> AOO developers can create a new interface.
> 
> >> >>> Can  Common Spelling API (which was in MS Office up to version
> 2000 as
> >> >>> far  as  I know) be implemented in AOO on Windows.
> --
> Best regards,
> Alexey Zhuravliov
> 
> 
> -
> 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: [PROPOSAL][API][WINDOWS]Whether Common Spelling API can be implemented

[Alexey Zhuravliov]

Hello Rory,

Wednesday, May 25, 2016, 9:27:48 PM, you wrote:

>> DEH>> Please provide more information about the Common Spelling API

ROF> Unless this does something dramatically different and improved
ROF> from the existing spelling system, the English dictionary of
ROF> which is very well serviced by Marcus, I suggest that, on the "If
ROF> it's not broke don't fix it" principle we should leave the spelling system 
alone.

This  could  be  new  and useful feature when other programs could use
AOO's  spell  checking  engine. If MS's API can't be implemented maybe
AOO developers can create a new interface.

>> >>> Can  Common Spelling API (which was in MS Office up to version 2000 as
>> >>> far  as  I know) be implemented in AOO on Windows.
-- 
Best regards,
Alexey Zhuravliov


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Completed Infrastructure Module

[Stanimir]

Stanimir Atanasov.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Starting Infrastructure Module

[Stanimir]

Stanimir Atanasov.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Completed How the Apache OpenOffice Project Works

[Stanimir]

Stanimir Atanasov.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Starting How the Apache OpenOffice Project Works

[Stanimir]

Stanimir Atanasov.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Completed Introduction to Contributing to Apache OpenOffice Module

[Stanimir]

Stanimir Atanasov.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org