Re: Md5sum failed

2014-02-14 Thread Andre Fischer

On 14.02.2014 03:16, njia1297-ubu...@yahoo.com wrote:

Checksums do not match...  thought someone should know.


Can you provide more information?

Which file did you check?
Where did you download it from ?

-Andre


==
William




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




Re: User data storage

2014-02-14 Thread Andre Fischer

On 14.02.2014 08:52, Oliver-Rainer Wittmann wrote:

Hi,

On 13.02.2014 21:09, jonasalfreds...@gmail.com wrote:

I recommend the DevGuide [1] and the related configuration chapter. And
SDK contains a sample in Java that shows how to access the 
configuration.


I'm new to this and has just recently completed my first build of the 
aoo.

The code I'm looking at is C++ in the cui module and not Java. Is it not
right that Java is used for users to develop extensions and addins 
not for
correcting aoo bugs. My aim is to commit a bugfix to the aoo 
codebase. What
I am looking for is pointers into the C++ codebase where user 
configuration
is read and written. 


Some time ago I have written a simple class for accessing the configuration:

header: sd/source/ui/inc/tools/ConfigurationAccess.hxx
implementation: sd/source/ui/tools/ConfigurationAccess.cxx
used here: sd/source/framework/module/ModuleController.cxx
and here: sd/source/ui/sidebar/RecentlyUsedMasterPages.cxx

once you know the UNO intefaces to implement and services to use you can 
find other examples via OpenGrok 
(http://opengrok.adfinis-sygroup.org/source/)


-Andre


Is this not the correct forum for aoo developers, but
aoo addin developers?



This is the general mailing list for AOO - it is the right place for 
your requests.


I think Jürgen pointed you to the DevGuide as the configuration is 
also available via the UNO-API and thus can be used by extension 
developers.
To get familiar with the configuration management this is a good 
start, I think.



You probably have to define a new schema first to store your data. For
testing you can do that via an extension and you can use Java to play
around with the API.




The same API is also available in the C++ code. Thus, the code used in 
an extension could be converted into C++ code.


Best regards, Oliver.




[1]
https://wiki.openoffice.org/wiki/Documentation/DevGuide/Config/Configuration_Management 




Juergen



/Jonas



--
View this message in context: 
http://openoffice.2283327.n4.nabble.com/User-data-storage-tp4658954p4658974.html

Sent from the Development mailing list archive at Nabble.com.

-
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: US_inprogress folder went missing during the build

2014-02-14 Thread LOH KOK HOE
@Regina
I did build with -P option for the reason to speed up the building process.
This is the command I use in the build: build --all -P2 -- -P2, and then
I did also try build --all, result still the same. I didn't configure any
thing including the --with-lang option. So I leave it default. FYI, my
development PC consist of Ubuntu 13.04 64bit, i5-2400 @ 3.10GHz with 8GB
RAM.
:o)


On Thu, Feb 13, 2014 at 10:32 PM, Regina Henschel
rb.hensc...@t-online.dewrote:

 Hi,

 I build for Windows, but perhaps there are similar problems on Linux:

 Do you try to build with option -P ? I found, that -P4 does never work for
 me, but building without that option works.

 What is your value for --with-lang in configure? It seems to me that wrong
 values are not detected before packing.

 Kind regards
 Regina

 LOH KOK HOE schrieb:

  I have remove the unxingx6.pro and rebuild, error still persist. I'm
 having
 this error being shown during the build:

 **
 ERROR: Saved logfile:
 /home/kokhoe/workspace/aoo-trunk/main/instsetoo_native/
 unxlngx6.pro/Apache_OpenOffice/deb/logging/en-US/log_AOO410_en-US.log
 **
 Thu Feb 13 21:52:37 2014 (00:08 min.)
 dmake:  Error code 255, while making 'openoffice_en-US.deb'

 1 module(s):
   instsetoo_native
 need(s) to be rebuilt

 Reason(s):

 ERROR: error 65280 occurred while making
 /home/kokhoe/workspace/aoo-trunk/main/instsetoo_native/util

 When you have fixed the errors in that module you can resume the build by
 running:

 build --all:instsetoo_native



 On Thu, Feb 13, 2014 at 5:04 PM, Oliver-Rainer Wittmann 
 orwittm...@googlemail.com wrote:

  Hi,


 On 12.02.2014 15:18, LOH KOK HOE wrote:

  As I following the
 guidelinehttps://wiki.openoffice.org/wiki/Building_
 installation_packages

 on


 building the AOO, I got following error shown in the log file, the log
 file were locate at AOO-ROOT/main/instsetoo_native/
 unxlngx6.pro/Apache_OpenOffice/deb/logging/en-US directory, and the
 file
 name was log_AOO410_en-US.log.

 ***
 ERROR: More than one new package in directory
 /home/kokhoe/workspace/aoo-trunk/main/instsetoo_native/
 unxlngx6.pro/Apache_OpenOffice/deb/install/en-US_inprogress/DEBS (
 /home/kokhoe/workspace/aoo-trunk/main/instsetoo_native/
 unxlngx6.pro/Apache_OpenOffice/deb/install/en-US_
 inprogress/DEBS/openoffice-writer-4.0.0-1-linux-3.8-x86_
 64.deb/home/kokhoe/workspace/aoo-trunk/main/instsetoo_native/
 unxlngx6.pro/Apache_OpenOffice/deb/install/en-US_
 inprogress/DEBS/openoffice-writer-4.0.0-1-linux-3.8-x86_64
 )
 in function: determine_new_packagename (packagepool)
 ***

 As I check in the install directory, I don't see US_inprogress folder,
 but I do see others. May I know how could I rectified this issue?


  Folder 'en-US_inprogress' is the folder name used during the creation
 of
 the installation packages. It is renamed to 'en-US' once the packaging
 has
 finished.

 Unfortunately, I can not help you with the error - I am not involved deep
 enough in the packaging.

 I recommendation is the remove folder 'unxlngx6.pro' (it is the build
 output folder) in module instsetoo_native and try a further 'build --all'

 Best regards, Oliver.


   The output of the console mention this:


 dmake:  Error code 255, while making 'openoffice_en-US.deb'

 It seems to me that the build was failed due to the builder failed to
 make
 a deb package.


  -
 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: Proofing Tool GUI 2.3 released - 14.Feb.2014

2014-02-14 Thread Andrea Pescetti

On 14/02/2014 Marco A.G.Pinto wrote:

Also, I want to implement the Hyphenation. Does anyone know how it
works, so that I can implement it? Maybe there is documentation somewhere?


The tool is called Hyphen and is part of Hunspell. So I think you should 
start from

http://sourceforge.net/projects/hunspell/files/Hyphen/

The syntax of auxiliary files is very, very obscure! Most of the times 
the hyphenation patterns are not created, but they are converted from 
the ones available for TeX.


The Italian package
http://extensions.openoffice.org/project/dict-it
should contain README files with links to the TeX sources.

Regards,
  Andrea.

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



Re: Proofing Tool GUI 2.3 released - 14.Feb.2014

2014-02-14 Thread Marco A.G.Pinto

  
  
Thanks, my dear friend Andrea!
  
   :-P  :-P  ;-)  :-) 
  
  
  On 14/02/2014 13:35, Andrea Pescetti wrote:

On
  14/02/2014 Marco A.G.Pinto wrote:
  
  Also, I want to implement the Hyphenation.
Does anyone know how it

works, so that I can implement it? Maybe there is documentation
somewhere?

  
  
  The tool is called Hyphen and is part of Hunspell. So I think you
  should start from
  
  http://sourceforge.net/projects/hunspell/files/Hyphen/
  
  
  The syntax of auxiliary files is very, very obscure! Most of the
  times the hyphenation patterns are not created, but they are
  converted from the ones available for TeX.
  
  
  The Italian package
  
  http://extensions.openoffice.org/project/dict-it
  
  should contain README files with links to the TeX sources.
  
  
  Regards,
  
   Andrea.
  


-- 
  
  



review requested: [Bug 124188] CRASH when pasting grouped contents from Draw over a selected image : [Attachment 82591] Avoid NULL pointer access

2014-02-14 Thread bugzilla
Andre awf@googlemail.com has asked Oliver-Rainer Wittmann
o...@apache.org for review:
Bug 124188: CRASH when pasting grouped contents from Draw over a selected image
https://issues.apache.org/ooo/show_bug.cgi?id=124188

Attachment 82591: Avoid NULL pointer access
https://issues.apache.org/ooo/attachment.cgi?id=82591action=edit

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



Reporting a problem with the OpenOffice website - GENIO

2014-02-14 Thread Charlotte Forrer
Hi,

I just thought you should be aware that I downloaded GENIO unintentionally when 
trying to download open office.  It was disguised as a full screen pop up.  

Hopefully I can get rid of it,

Charlotte


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



Re: Reporting a problem with the OpenOffice website - GENIO

2014-02-14 Thread Max Merbald

Hello Charlotte,

it seems that you did NOT download OpenOffice from the official homepage 
www.openoffice.org. Downloads from the original homepage which forward 
you to sourceforge never come with additional software. Would you mind 
telling which site you downloaded OpenOfficer from?


Max


Am 14.02.2014 14:55, schrieb Charlotte Forrer:

Hi,

I just thought you should be aware that I downloaded GENIO unintentionally when 
trying to download open office.  It was disguised as a full screen pop up.

Hopefully I can get rid of it,

Charlotte


-
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



Speech recognition with openoffice

2014-02-14 Thread awdellipiani
I have used openoffice for some years
Recently I have tried Speech Recognition with WRITER but it does not work
Is it possible to remedy this? I have Windows 7
AW Dellipiani

RE: Reporting a problem with the OpenOffice website

2014-02-14 Thread Pete Becher
Hi Marcus,

Thanks for the reply.

After trying it a couple more times I did a PAUSE and RESUME on the download 
and after the second time I did that it started the download.

It may have just been some type of very slow connection problem or something 
because I could see a message showing a small amount of data downloaded each 
time I PAUSED and the data rate being around 13kB/sec.

Just a note, when I was trying to download 4.0.1 a while back I did download 
4.0.0 from SourceForge with no problem.

Thanks again,
Pete


-Original Message-
From: Marcus (OOo) [mailto:marcus.m...@wtnet.de] 
Sent: Thursday, February 13, 2014 4:32 PM
To: dev@openoffice.apache.org
Cc: Pete Becher
Subject: Re: Reporting a problem with the OpenOffice website

Am 02/13/2014 06:04 PM, schrieb Pete Becher:
 Hi OOo Web Tech,

 I cannot download OOo 4.0.1 from
 http://www.openoffice.org/download/index.html**

 The Windows download window just keeps showing 0% forever as shown below.

 I tried a few weeks ago and had the same problem.

 I could not find anything in the Forum about this kind of problem.

 Any suggestions? Where I can look to find a solution?

I'm sorry but I cannot see this or a similar problem. When clicking the 
download link I get a download progress until its end.

If you are browsing via a proxy server (e.g., due to your ISP) maybe it's 
possible and helping to disable it or vis-versa to enable it.

If you are browsing via your employer's Internet connection, maybe the
Sysadmin(s) have blocked special ports or domains. A little talk with them 
could bring a solution, too.

Or maybe the direct link to our hosting partner Sourceforge can help:

Install file for English US:

http://sourceforge.net/projects/openofficeorg.mirror/files/4.0.1/binaries/en-US/Apache_OpenOffice_4.0.1_Win_x86_install_en-US.exe/download

Or via a different mirror:

http://downloads.sourceforge.net/project/openofficeorg.mirror/4.0.1/binaries/en-US/Apache_OpenOffice_4.0.1_Win_x86_install_en-US.exe?r=ts=1392330652use_mirror=skylink

Hope this helps.

Marcus



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



Reporting a problem with the OpenOffice website

2014-02-14 Thread awdellipiani
I have used openoffice for some years
Recently I have tried Speech Recognition with WRITER but it does not work
Is it possible to remedy this?
AW Dellipiani

Re: Md5sum failed

2014-02-14 Thread Marcus (OOo)

Am 02/14/2014 04:14 PM, schrieb František Erben:

Hi,
on folowing download page https://www.vagrantup.com/downloads.html
you can download SHA256 chechksums, not MD5SUM.

MD5 and SHA256 is different checksum methods.


Vagrant is not managed by Apache or OpenOffice. Please ask at Vagrantup 
for a solution. A starting point could be here:


https://www.vagrantup.com/support.html

Marcus




2014-02-14 13:40 GMT+01:00 Rob Weirrobw...@apache.org:


On Fri, Feb 14, 2014 at 3:10 AM, Andre Fischerawf@gmail.com  wrote:

On 14.02.2014 03:16, njia1297-ubu...@yahoo.com wrote:


Checksums do not match...  thought someone should know.



Can you provide more information?

Which file did you check?
Where did you download it from ?



The original note included an image attachment that only moderators
are able to see.  It listed the files as:

Vagrant-1.4.3.dmg
Vagrant-1.4.3.msi
Vagrant-1.4.3_i686.deb
Vagrant-1.4.3_x86_64.deb

So it looks like the note was misdirected.

-Rob



-Andre


==
William


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



[RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?

2014-02-14 Thread Marcus (OOo)
As this is our first beta release at Apache, I would like to clarify 
some things before it's maybe too late to change the facts and to 
prepare webpages:


1. Target group

It is intended to be downloaded for the general public, right?

2. Hosting

We are planning to host the files at Sourceforge, right?

3. File names:

Of course the file names of the install files have to show a difference 
compared to the general release files. Suggestion:


Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe

*If* there is a need to publish another round, it could be extended with 
a number like:


Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe

4. Directory structure:

Is it OK to expect to use the same dir structure like we have currently 
for 4.0.1?


5. Download webpage:

Is it OK to expect to offer the download on our main download webpage?
http://www.openoffice.org/download/

If yes, I can build up a download offer like we have for the green box. 
To ease the download as best as possible.


Thanks

Marcus


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



RE: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory Fault

2014-02-14 Thread Steele, Raymond
Andre,

I think we are going to keep that section commented out for now.  We are not 
sure what to do. Do you think commenting out that section will have a big 
impact at runtime?
We are working on the Save now (described below).

From: Andre Fischer [mailto:awf@gmail.com]
Sent: Friday, February 07, 2014 2:18 AM
To: Steele, Raymond; Andre Fischer; a...@openoffice.apache.org; Herbert Duerr 
(h...@apache.org); dev@openoffice.apache.org
Cc: Meffe, David K
Subject: Re: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory 
Fault

On 07.02.2014 00:04, Steele, Raymond wrote:
Andre,

When we commented out the section below, we were able to get the application to 
work correctly

I would expect subtle errors in the sidebar, like panels not updating after 
context changes or when switching between application windows.


(although it did not let us save a spreadsheet to disk for some reason. Each 
time we hit okay to save after supplying a unique name, the filechooser closes, 
but instantly reappears again. It did let us save it as another format, such as 
.dif).

Strange, this change should not modify the saving of the document.  That is 
probably an unrelated problem.



However, the application crashes when we replace the lines with:

ReferenceSidebarController xThis (this, SAL_NO_ACQUIRE);
WeakReferenceSidebarController xWeakController (xThis);
maSidebarControllerContainer.insert(
SidebarControllerContainer::value_type(
rxFrame,
xWeakController));


I've attached the stack trace of that crash. It crashes right after the 
SidebarController destructor on line 177 (which is empty).  Stepping from the 
destructor brings us into boost's checked_delete.hpp and eventually crashes at 
line 34 delete x. See attached stack trace. m_RefCount was 3 for us as well.

Also strange.  All this does not fit together.  If the ref count is larger than 
0 then the SidebarController should not be deleted.  And if it where deleted, 
then not from Reference...::iquery.  And  boost::scoped_ptrWindow should 
have no problem deleting the control (I have not enough information to say 
which one it is).  All controls are created in the initializer of the 
constructor and should be fully created and initialized by the time the crash 
is triggered.

All this looks like the actual problem happens earlier, maybe some memory 
overwrite.

Maybe you can use valgrind (or some other memory checker) to see if there is a 
memory problem?



Thanks for taking the time to look into this, we are grateful.  Would you 
happen to be  located in the U.S.?

No problem.  I am a little worried that you have discovered a problem that 
lurks on all platforms and Solaris is the only one where it leads to an actual 
crash.

And, no, I am not located in the US.  I am in Germany.

-Andre




From: Andre Fischer [mailto:awf@gmail.com]
Sent: Thursday, February 06, 2014 2:03 AM
To: Steele, Raymond; 
a...@openoffice.apache.orgmailto:a...@openoffice.apache.org; Herbert Duerr 
(h...@apache.orgmailto:h...@apache.org); 
dev@openoffice.apache.orgmailto:dev@openoffice.apache.org
Cc: Meffe, David K; awf@gmail.commailto:awf@gmail.com
Subject: Re: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory 
Fault

On 05.02.2014 20:02, Steele, Raymond wrote:
Andre,

We are not seeing any exception before the actual crash. Maybe I am not looking 
in the right place, but we've been using dbx intercept command to track any. 
Any other suggestions?

Raymond,

there a few thing you can do to find out if this is a local problem (broken in 
the constructor) or something more fundamental that is possibly caused by an 
error that happened much earlier.

- Comment out the last few lines:
  /*
WeakReferenceSidebarController xWeakController (this);
maSidebarControllerContainer.insert(
SidebarControllerContainer::value_type(
rxFrame,
xWeakController));
   */
That should tell us whether the crash is caused just by storing the weak 
reference.
The sidebar should still work in general but some updates may be lost.

- Replace the last few lines by this:
ReferenceSidebarController xThis (this, SAL_NO_ACQUIRE);
WeakReferenceSidebarController xWeakController (xThis);
maSidebarControllerContainer.insert(
SidebarControllerContainer::value_type(
rxFrame,
xWeakController));
That removes one (of two) acquire calls (I don't know yet why there is a second 
acquire,  after all the purpose of the weak reference is just /not/ to increase 
the reference count).

- Check the value of the reference count of 'SidebarController* this' (in 
OWeakObject::acquire, cppuhelper/source/weak.cxx) when line 168 of the 
SidebarController constructor is executed.
  In my case it is 3.

-Andre





  Also, I've attached the stack trace of the first and second 
notifyContextChangeEvent.  They are different.

That is OK.  They should be different.  But the stack trace of the 

New committer: Clarence Guo (clarence_guo)

2014-02-14 Thread Rob Weir
The Project Management Committee (PMC) for Apache OpenOffice has asked
Clarence Guo to become a committer and we are pleased to announce that
he has accepted and taken the ID clarence_guo.

A warm welcome to Clarence!

Regards,

Rob, on behalf of the Apache OpenOffice PMC

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



Re: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?

2014-02-14 Thread Marcus (OOo)

Am 02/14/2014 10:31 PM, schrieb Kay Schenk:

On Fri, Feb 14, 2014 at 12:53 PM, Marcus (OOo)marcus.m...@wtnet.de  wrote:


As this is our first beta release at Apache, I would like to clarify some
things before it's maybe too late to change the facts and to prepare
webpages:

1. Target group

It is intended to be downloaded for the general public, right?



yes, I think it needs to go a vote process as we've previously discussed.
I'd need to look up the discussion on this.




2. Hosting

We are planning to host the files at Sourceforge, right?

3. File names:

Of course the file names of the install files have to show a difference
compared to the general release files. Suggestion:

Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe

*If* there is a need to publish another round, it could be extended with a
number like:

Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe



Good point...




4. Directory structure:

Is it OK to expect to use the same dir structure like we have currently
for 4.0.1?

5. Download webpage:

Is it OK to expect to offer the download on our main download webpage?
http://www.openoffice.org/download/

If yes, I can build up a download offer like we have for the green box. To
ease the download as best as possible.



Maybe it would be better to have a separate beta page, or beta area on
the download page like the former OOo site had  for developer releases?


Indeed I thought about to put it somewhere below the green box. Of 
course with different color and text. But a separate webpage is also OK. 
Let's see what the majority of us thinks.


Marcus


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



Re: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?

2014-02-14 Thread Marcus (OOo)

Am 02/14/2014 10:32 PM, schrieb Rob Weir:

On Fri, Feb 14, 2014 at 3:53 PM, Marcus (OOo)marcus.m...@wtnet.de  wrote:

As this is our first beta release at Apache, I would like to clarify some
things before it's maybe too late to change the facts and to prepare
webpages:

1. Target group

It is intended to be downloaded for the general public, right?

2. Hosting

We are planning to host the files at Sourceforge, right?

3. File names:

Of course the file names of the install files have to show a difference
compared to the general release files. Suggestion:

Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe

*If* there is a need to publish another round, it could be extended with a
number like:

Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe

4. Directory structure:

Is it OK to expect to use the same dir structure like we have currently for
4.0.1?



The above makes sense to me.



5. Download webpage:

Is it OK to expect to offer the download on our main download webpage?
http://www.openoffice.org/download/

If yes, I can build up a download offer like we have for the green box. To
ease the download as best as possible.



I would not make this the default download option for users.  We still
want most users to download AOO 4.0.1. So keep the first box on
/download.html as it is now.

Maybe a yellow box (yellow == caution) with language that makes it
clear that this is beta and gives the URL for reporting bugs.


I think I was not clear in my wording. :-)

Of course the current 4.0.1 should not be effected in any way.

With ease the download as best as possible I meant to do the same like 
we have for the green box but of course with a different color and text.



Were you thinking of a language/platform switch logic for the beta?
Or just a link to a beta_other.html page with a table of links?  If
we do the table, then we would have room on the same page to give  a
prominent warning, a link to BZ, Release Notes, etc.


I thought about the one-click-download we have already. Then of course a 
beta-other.html is also needed and your suggestion makes absolutely sense.


It could be a box somewhere below the green box. Or - as Kay mentioned - 
a separate webpage.


Marcus


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



Re: Tajik spell check

2014-02-14 Thread Andrea Pescetti

Soliev Odil wrote:

We already use Hanspell dictionary for spell cheking in Ms
Office and OpenOfficeOrg which has 68686 roots and 3925 postfixes.
We are interested include our research in latest distribution of openoffice
system. Can we cooperate with you in this field?


Sure! If you package your dictionary as a .oxt file you can upload it to 
the official OpenOffice Extensions repository at 
http://extensions.openoffice.org/



What should we do in cooperation?


http://www.openoffice.org/lingucomponent/dictionary.html should cover 
all you need to package an extension.



How get GNU GPL licence for our works?


GPL is OK for dictionaries (while we require Apache License 2, the 
OpenOffice license, for other contributions, such as translations). See 
all details at the link above.


If you want to help with the Tajik version of OpenOffice too, we do have 
a partial translation available (for internal reference: it is at 
http://svn.apache.org/viewvc/openoffice/trunk/extras/l10n/source/tg/ ); 
please read https://openoffice.apache.org/translate.html and contact us 
on the l10n list in case.


Regards,
  Andrea.

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



OO 4.01 Compiled for Solaris 11 x86 Save As Stuck in a Loop

2014-02-14 Thread Steele, Raymond
We are attempting to use the newly build OpenOffice 4.0.1 for Solaris 11 x86, 
but  the 'Save As' to disk of any document type (i.e. .ods) continuous to 
prompt for a file name.  Each time we hit okay to save the document after 
supplying a unique name, the FilePicker closes, but instantly reappears again.

I have narrowed  it down to the following code located in 
sfx2/source/doc/guisaveas.cxx lines 1497-1520

The program gets stuck in the while loop below.  The variable 'bExit' is never 
set to sal_True, so the loop continuous. I provide a name to the FilePicker 
interface, click Save and the loop continuous, redisplaying the dialog. To 
resolve the issue, I added bExit = sal_True after line 1513 so that the loop 
discontinuous. I am not sure if this will have effects in other situations, 
maybe someone can provide some feedback, but for now. I am able to save.


sal_Bool bExit = sal_False;
1497   while ( !bExit )
1498   {
1499   bUseFilterOptions = aModelData.OutputFileDialog( nStoreMode, 
aFilterProps, bSetStandardName, aSuggestedName, bPreselectPassword, 
aSuggestedDir, nDialog, sStandardDir, aBlackList );
1500
1501   // in case the dialog is opend a second time the folder should be 
the same as before, not what was handed over by parameters
1502   aSuggestedDir = ::rtl::OUString();
1503   if ( nStoreMode == SAVEAS_REQUESTED )
1504   {
1505   // in case of saving check filter for possible alien warning
1506   ::rtl::OUString aSelFilterName = 
aModelData.GetMediaDescr().getUnpackedValueOrDefault(
1507   aFilterNameString,
1508   ::rtl::OUString() );
1509   sal_Int8 nStatusFilterSave = aModelData.CheckFilter( aSelFilterName 
);
1510   if ( nStatusFilterSave == STATUS_SAVEAS_STANDARDNAME ) These are 
equal during runtime
1511   {
1512   // switch to best filter
1513   bSetStandardName = sal_True; bSetStandardName is set to sal_True 
here, but bExit is not, so the loop continuous. Setting bExit following this 
line allows the program to save.
++bExit = salTrue;
1514   }
1515   else if ( nStatusFilterSave == STATUS_SAVE )
1516   {
1517   // user confirmed alien filter or good filter is used
1518   bExit = sal_True;
1519   }
1520   }
1521   else
1522   bExit = sal_True;
1523   }



Raymond Steele
U-2 Mission Planning
Software Engineer Sr
Lockheed Martin - ISGS Defense
1300 S. Litchfield Rd.
Goodyear, AZ 85338
Email: raymond.ste...@lmco.com
Business phone:  623-925-6402



Re: Speech recognition with openoffice

2014-02-14 Thread V Stuart Foote
This has been addressed multiple times by the development community. 

https://issues.apache.org/ooo/show_bug.cgi?id=6104
https://issues.apache.org/ooo/show_bug.cgi?id=70567
https://issues.apache.org/ooo/show_bug.cgi?id=71542
https://issues.apache.org/ooo/show_bug.cgi?id=84997
https://issues.apache.org/ooo/show_bug.cgi?id=116253

https://bugs.freedesktop.org/show_bug.cgi?id=69039

As a cross platform program supporting Linux, OS X and Windows
environments--the UNO Accessibility API will remain the basis of support for
AT. 

In short this is not an Apache Open Office (or a LibreOffice)
responsibility, it falls to 3rd party extension developers. And it remains
for external projects to implement AT for mobility impaired users who would
benefit from speech recognition.

Microsoft TSF is in legacy status. And currently no agreed standard
exists for Speach recognition. 

Microsoft has gone its own way with UI and MSSR. And Nuance, with its
current Dragon NS 12--Full Text Control function--looks to again have
omitted Apache OpenOffice and TDF LibreOffice support for UNO API, and only
supporting Microsoft productivity products.

The full implementation of a native IAccessible2 (v1.3) standard based
bridge for Windows OS now provides the AT hooks needed to implement Windows
speech recognition to both Apache OpenOffice and LibreOffice.

That might be a Nuance DNS commercial module, or I'd lean more to an
Extension for AOO/LibreOffice using the Python based Dragonfly speech
recognition framework and a AOO/LibreOffice specific command-module for
Microsoft WSR. Perhaps a cross over from the NVDA community. 





--
View this message in context: 
http://openoffice.2283327.n4.nabble.com/Speech-recognition-with-openoffice-tp4659010p4659028.html
Sent from the Development mailing list archive at Nabble.com.

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



Re: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?

2014-02-14 Thread Marcus (OOo)

Am 02/14/2014 10:47 PM, schrieb Marcus (OOo):

Am 02/14/2014 10:32 PM, schrieb Rob Weir:

On Fri, Feb 14, 2014 at 3:53 PM, Marcus (OOo)marcus.m...@wtnet.de
wrote:

As this is our first beta release at Apache, I would like to clarify
some
things before it's maybe too late to change the facts and to prepare
webpages:

1. Target group

It is intended to be downloaded for the general public, right?

2. Hosting

We are planning to host the files at Sourceforge, right?

3. File names:

Of course the file names of the install files have to show a difference
compared to the general release files. Suggestion:

Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe

*If* there is a need to publish another round, it could be extended
with a
number like:

Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe

4. Directory structure:

Is it OK to expect to use the same dir structure like we have
currently for
4.0.1?



The above makes sense to me.



5. Download webpage:

Is it OK to expect to offer the download on our main download webpage?
http://www.openoffice.org/download/

If yes, I can build up a download offer like we have for the green
box. To
ease the download as best as possible.



I would not make this the default download option for users. We still
want most users to download AOO 4.0.1. So keep the first box on
/download.html as it is now.

Maybe a yellow box (yellow == caution) with language that makes it
clear that this is beta and gives the URL for reporting bugs.


I think I was not clear in my wording. :-)

Of course the current 4.0.1 should not be effected in any way.

With ease the download as best as possible I meant to do the same like
we have for the green box but of course with a different color and text.


Were you thinking of a language/platform switch logic for the beta?
Or just a link to a beta_other.html page with a table of links? If
we do the table, then we would have room on the same page to give a
prominent warning, a link to BZ, Release Notes, etc.


I thought about the one-click-download we have already. Then of course a
beta-other.html is also needed and your suggestion makes absolutely
sense.

It could be a box somewhere below the green box. Or - as Kay mentioned -
a separate webpage.


I've added a quick version of how it could look like on the same 
download webpage:


http://www.openoffice.org/download/test/index.html

- The first yellow box is for the download when the Beta release is 
available. Of course the links are not yet working - but with link name 
and title you should get an first impression.


- The second one is a little teaser to show when is it coming. With a 
link to the AOO blog - in case of if we want to blog about the upcoming 
Beta release.


PS:
The green box is still for the Mac OS X test:
- download AOO 4.1.0 if 10.7 or newer is recognized in browser
- download AOO 4.0.1 if 10.6 or older is recognized in browser

Marcus


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