Re: space in wiki for documentation of branches

2014-01-10 Thread Jürgen Schmidt
On 1/9/14 10:56 PM, Armin Le Grand wrote:
 On 09.01.2014 00:36, Jürgen Schmidt wrote:
 On 1/8/14 7:57 PM, jan i wrote:
 -8-
 please be aware that cwiki is not nearly as visited as mwiki, so
 putting it
 in cwiki is a real good hiding place.
 exactly, we should use mediawiki whenever possible, we could move the
 content from confluence to mediawiki to make it even more clear.
 Important pages will be monitored and wrong or damaging changes can be
 corrected.
 
 I have updated that page (https://wiki.openoffice.org/wiki/Source_Code)
 now and added my current branches. How can I now add a link to a page
 where I want to document the state and development of my branch
 alg_writerframes? I do not want to do that in the list there, that will
 be too much.
 


 In that form it may also give a preview of what may be coming to the
 next
 versions (without forcing it, it should be train model based). E.g.
 with
 accessibility when it would have been documented there it would be more
 clear where it comes from, evtl. how far it is progressed and if it
 will be
 in one of the next versions (e.g. include a single 'progress' percent
 number).

 I dont object to the idea, but do we really want  to that much red tape
 around using branches. I would for sure remove capstone/l10n40 and
 keep it
 local instead if I have to document in cwiki.

 please remember the more documentation (in, at least to me, and
 unkown wiki
 language) makes it more likely that people considering a branch stop the
 idea.
 it should be no must to document in detail but a short paragraph
 describing for what kind of work the branch in intended can help. And
 more documentation can help developers to organize their work or can
 help for collaboration to work with more people on the same branch.  But
 again it should be no must if people lose interest because of the
 documentation burden.
 
 I think a short paragraph in the list on the page
 https://wiki.openoffice.org/wiki/Source_Code will be fine and not too
 much requirement to do for everyone. Maybe this could even be automated
 when someone creates a link (just adding the link to it, the creation
 date and the creator? Herbert, is that possible..?).
 
 I need the possibility to add an extra link there (probably assocciated
 to some more... text or similar) which leads to an extra page with
 extended documentation (I want to share info with another developer in a
 central place - this is the Wiki from my POV). This should of course not
 be mandatory, but possibe.

create a new wiki page with the topic of your branch, for example the
sidebar branch was related to the sidebar wiki page. And then you can
simply insert a wiki link to this more descriptive wiki page.

See also https://wiki.openoffice.org/wiki/Help:Editing
I find the wiki reference card useful
http://meta.wikimedia.org/wiki/Help:Reference_card

Juergen

 
 Sincerely,
 Armin
 

 Juergen



 -
 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



Reporting a problem with the OpenOffice website

2014-01-10 Thread RPJACKMAN
I started an Apache Open Office app at 2:30 AM on 1-9-2014
Upon starting a window came up INSTALL CONVERTER INSTALLATION
You're a few steps away from getting the Install Converter.
A download percentage bar shows for each part being downloaded.
 
It is now 4:26 AM on 1/10/2014 and part number 5080 just downloaded and  
it's 
still continuing to download part after part.  OVER 24 hours  later.
 
I have high speed internet and I can't understand what's taking so long. 
 
There is no provision to stop the download, abort the download, cancel the  
down load.
 
It's a new computer with Windows 8. I'm using Mozilla Firefox to down  load.
 
Need to know if I'm got a problem going on here. There was no indication  
that it
would go on like this. 

Re: Reporting a problem with the OpenOffice website

2014-01-10 Thread Rory O'Farrell
On Fri, 10 Jan 2014 04:31:59 -0500 (EST)
rpjack...@aol.com wrote:

 I started an Apache Open Office app at 2:30 AM on 1-9-2014
 Upon starting a window came up INSTALL CONVERTER INSTALLATION
 You're a few steps away from getting the Install Converter.
 A download percentage bar shows for each part being downloaded.
  
 It is now 4:26 AM on 1/10/2014 and part number 5080 just downloaded and  
 it's 
 still continuing to download part after part.  OVER 24 hours  later.
  
 I have high speed internet and I can't understand what's taking so long. 
  
 There is no provision to stop the download, abort the download, cancel the  
 down load.
  
 It's a new computer with Windows 8. I'm using Mozilla Firefox to down  load.
  
 Need to know if I'm got a problem going on here. There was no indication  
 that it
 would go on like this. 

I suggest you remove this version from your computer as soon as may be. Best 
then to run indepth Virus and Malware scans.

Download only from 
www.openoffice.org/download, which will redirect you to SourceForge servers. On 
those downloads you will find no intrusive add-ons. The file you download 
should be one file of about 135-150MB (depending on platform).


-- 
Rory O'Farrell ofarr...@iol.ie

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



Re: EXTERNAL: Re: Building comphelper

2014-01-10 Thread Herbert Duerr

On 09.01.2014 16:47, Steele, Raymond wrote:

We found a work around for this problem, but believe it may be implemented 
incorrectly.

We added the following to the top of fmtatr2.cxx:

#ifndef _RWSTD_NO_MEMBER_TEMPLATES
#define _RWSTD_NO_MEMBER_TEMPLATES 1
#endif


A good find! And indeed [1] also ran into such a problem and defining 
that to disable templatized version of std::vectorT::assign() was a 
workaround needed by the SunStudio compiler.


http://trac.osgeo.org/geos/ticket/224


The compile of sw then began compiling correctly.  Any thoughts?


I'd say that all such defines that make boost less aggressive in using 
advanced template magic are fine, so don't worry about it. But I'd use 
such an option consistently then, not only in one file. I suggest to add a

-D_RWSTD_NO_MEMBER_TEMPLATES=1
into the solaris makefiles in solenv.

Herbert

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



Re: EXTERNAL: Re: Building comphelper

2014-01-10 Thread Herbert Duerr

On 09.01.2014 22:48, Steele, Raymond wrote:

Attached is a copy of the stack trace when we tried to launch both the Word 
Processor and the Spreadsheet application in OpenOffice.  We are going to 
attempt to resolve the crash based on this information, but if anything pops 
out at you, please let us know.


The crashes in Writer and Calc you are seeing both happen when copy 
constructing an OUString from one provided by the SidebarController, so 
the provided string must be bad.


I suggest to set a breakpoint at SidebarController.cxx:257 and examine 
the rEvent.ApplicationName and rEvent.ContextName whether these are good 
strings. From the stack I'd say they probably are not. Then go up the 
stack and check where they come from and why their are bad.


Good luck!
(I'll be away next week, starting this weekend)

Herbert

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



RE: Web accessibility guidelines -- which ones?

2014-01-10 Thread Christophe Strobbe
Hi,

I agree that WCAG 2.0 is the way to go; the current Section 508 is still
based on a pre-final version of WCAG 1.0 and will hopefully get updated by
the end of the year.
I wouldn't aim higher than WCAG 2.0 AA; even WCAG 2.0 A may be a challenge
at the start.
With regard to tools, I currently don't know what to recommend because I
haven't evaluated any such tools recently. WebAIM's WAVE
http://wave.webaim.org/ (and the Firefox toolbar
http://wave.webaim.org/toolbar/) and the IDRC's AChecker
http://achecker.ca/checker/index.php were developed by competent teams.
I don't know who's behind Total Validator (meaning: I don't know the
developers).

Best regards,

Christophe

Am Fr, 10.01.2014, 04:35 schrieb V Stuart Foote:
 Rob,  *,

... However,  there was a confusing (to me) number of
authorities for accessibility standards.

 It is really pretty simple--WCAG 2.0 is the gold standard for Web content,
 and is applicable to Non-Web Information and Communications Technologies
 (ICT). National and International Standards bodies are basing conformance
 against this standard.

 WCAG 2.0 A, AA, AAA ( also published as  ISO/IEC 40500:2012 )  are
 functional levels of conformance with accessibility standards.
 http://www.w3.org/WAI/intro/wcag

 The reworked AOO Website should probably meet majority of WCAG v2.0 AA
 level requirements. And Apache OpenOffice as a document preparation and
 review program should also strive to meet WCAG level A  AA conformance
 criteria for ICT (http://www.w3.org/TR/wcag2ict/ ).

 Fortunately much of that is accomplished for the website with valid HTML
 5.0 and WAI-ARIA markup.  While the introduction of IAccessible2 to
 supplement MSAA,  and improvements in ATK and NSAccessibility move the
 office suite proper into a better compliance with some notable
 shortcommings.

 In the United States, the existing Accessibility Board US Section 508
 requirements were loosely equivalent to WCAG v1, and are being rewritten
 to match functional levels of WCAG 2.0 A  AA.   The draft proposal for
 U.S. conformance can be found here:

 http://www.access-board.gov/attachments/article/490/draft-rule.pdf

 Also, relevant parts of the European Union EN 301 549 (
 http://www.etsi.org/deliver/etsi_en/301500_301599/301549/01.00.00_20/en_301549v01c.pdf
 ) as work of the European Commision (EC) Mandate M 376 (
 http://www.mandate376.eu/ ) are also based on WCAG v2.0 level A and AA.

 So running conformance validators for WCAG 2.0 A, AA,  AAA is probably
 the correct choice in reworking the web site.

 Stuart


-- 
Christophe Strobbe
Akademischer Mitarbeiter
Adaptive User Interfaces Research Group
Hochschule der Medien
Nobelstraße 10
70569 Stuttgart
Tel. +49 711 8923 2749


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



Re: Build Fails In Module Coinmp

2014-01-10 Thread Herbert Duerr

On 09.01.2014 17:39, Tyler Kavanaugh wrote:

I was able to start the build using Herbert's suggestion, and everything
seemed to be going well all the way until the build system tried to
build the modules coinmp, python, and sal. At that point, it failed.
I've got a build log I can submit, if anyone wants to see it. I also
tried building the individual module sal, by running:

build --from sal -P2 -- -P2

and ended up getting some sort of undefined symbol error coming from the
STL headers, as far as I could tell.


Are you building AOO 4.0.x or trunk? On what platform? If you are 
building AOO 4.0.x you have to use the --without-stlport configure 
option. On trunk this is automatically enabled.


The relevant excerpt from the build log are essential for solving the 
problem. I personally am away for the next couple of days though, but 
maybe someone else can figure out what went wrong.


Herbert

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



Re: Web accessibility guidelines -- which ones?

2014-01-10 Thread Rob Weir
On Thu, Jan 9, 2014 at 10:35 PM, V Stuart Foote vstuart.fo...@utsa.edu wrote:
 Rob,  *,

... However,  there was a confusing (to me) number of
authorities for accessibility standards.

 It is really pretty simple--WCAG 2.0 is the gold standard for Web content, 
 and is applicable to Non-Web Information and Communications Technologies 
 (ICT). National and International Standards bodies are basing conformance 
 against this standard.

 WCAG 2.0 A, AA, AAA ( also published as  ISO/IEC 40500:2012 )  are functional 
 levels of conformance with accessibility standards.  
 http://www.w3.org/WAI/intro/wcag

 The reworked AOO Website should probably meet majority of WCAG v2.0 AA level 
 requirements. And Apache OpenOffice as a document preparation and review 
 program should also strive to meet WCAG level A  AA conformance criteria for 
 ICT (http://www.w3.org/TR/wcag2ict/ ).

 Fortunately much of that is accomplished for the website with valid HTML 5.0 
 and WAI-ARIA markup.  While the introduction of IAccessible2 to supplement 
 MSAA,  and improvements in ATK and NSAccessibility move the office suite 
 proper into a better compliance with some notable shortcommings.

 In the United States, the existing Accessibility Board US Section 508 
 requirements were loosely equivalent to WCAG v1, and are being rewritten to 
 match functional levels of WCAG 2.0 A  AA.   The draft proposal for U.S. 
 conformance can be found here:

 http://www.access-board.gov/attachments/article/490/draft-rule.pdf

 Also, relevant parts of the European Union EN 301 549 ( 
 http://www.etsi.org/deliver/etsi_en/301500_301599/301549/01.00.00_20/en_301549v01c.pdf
  ) as work of the European Commision (EC) Mandate M 376 ( 
 http://www.mandate376.eu/ ) are also based on WCAG v2.0 level A and AA.

 So running conformance validators for WCAG 2.0 A, AA,  AAA is probably the 
 correct choice in reworking the web site.


Thanks for the explanation.

One question:  would we need to run against each of the profiles, or
AAA include AA and A automatically?  In other words, is AA a superset
of A, and AAA a superset of AA?  Or are they more like incremental
rule sets, that need to be applied in addition to the base rule sets?

Regards,

-Rob


 Stuart


 -
 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: Web accessibility guidelines -- which ones?

2014-01-10 Thread Christophe Strobbe
Hi Rob, All,

Level AA also encompasses all of level A, and level AAA encompasses all of
level AA. So if a tool has radio buttons for the three levels, choosing AA
should result in a check of all level A and all level AA criteria. Of
course, such checks only cover aspects that can be checked automatically
(which is definitely less than half of WCAG).

Please note that level AAA is a very high level. For example, it requires
that content should be made readable for people whose reading ability is
at lower secondary education level
http://www.w3.org/TR/2008/REC-WCAG20-20081211/#meaning-supplements.
Because of requirements like this one, AAA is not applicable or suitable
to all web sites (e.g. academic journals).

Best regards,

Christophe


Am Fr, 10.01.2014, 15:48 schrieb Rob Weir:
 On Thu, Jan 9, 2014 at 10:35 PM, V Stuart Foote vstuart.fo...@utsa.edu
 wrote:
 Rob,  *,

... However,  there was a confusing (to me) number of
authorities for accessibility standards.

 It is really pretty simple--WCAG 2.0 is the gold standard for Web
 content, and is applicable to Non-Web Information and Communications
 Technologies (ICT). National and International Standards bodies are
 basing conformance against this standard.

 WCAG 2.0 A, AA, AAA ( also published as  ISO/IEC 40500:2012 )  are
 functional levels of conformance with accessibility standards.
 http://www.w3.org/WAI/intro/wcag

 The reworked AOO Website should probably meet majority of WCAG v2.0 AA
 level requirements. And Apache OpenOffice as a document preparation and
 review program should also strive to meet WCAG level A  AA conformance
 criteria for ICT (http://www.w3.org/TR/wcag2ict/ ).

 Fortunately much of that is accomplished for the website with valid HTML
 5.0 and WAI-ARIA markup.  While the introduction of IAccessible2 to
 supplement MSAA,  and improvements in ATK and NSAccessibility move the
 office suite proper into a better compliance with some notable
 shortcommings.

 In the United States, the existing Accessibility Board US Section 508
 requirements were loosely equivalent to WCAG v1, and are being rewritten
 to match functional levels of WCAG 2.0 A  AA.   The draft proposal for
 U.S. conformance can be found here:

 http://www.access-board.gov/attachments/article/490/draft-rule.pdf

 Also, relevant parts of the European Union EN 301 549 (
 http://www.etsi.org/deliver/etsi_en/301500_301599/301549/01.00.00_20/en_301549v01c.pdf
 ) as work of the European Commision (EC) Mandate M 376 (
 http://www.mandate376.eu/ ) are also based on WCAG v2.0 level A and AA.

 So running conformance validators for WCAG 2.0 A, AA,  AAA is probably
 the correct choice in reworking the web site.


 Thanks for the explanation.

 One question:  would we need to run against each of the profiles, or
 AAA include AA and A automatically?  In other words, is AA a superset
 of A, and AAA a superset of AA?  Or are they more like incremental
 rule sets, that need to be applied in addition to the base rule sets?

 Regards,

 -Rob


 Stuart


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


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




-- 
Christophe Strobbe
Akademischer Mitarbeiter
Adaptive User Interfaces Research Group
Hochschule der Medien
Nobelstraße 10
70569 Stuttgart
Tel. +49 711 8923 2749


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



Interesting interoperability problem with formatting of date

2014-01-10 Thread Jürgen Schmidt
Hi,

I received a xls document with some date values, date related functions
and formatting and noticed an interesting interoperability problem.

For example:
Cell Value  FormatVisible Value
A1   01/01/2014 MM/DD/YY  01/01/2014
A2   =DAY(A1)   DD31

Excel shows the value 1 and the user expected the same value in
OpenOffice but we show 31.

The reason can be explained by looking in the help of the DAY function
in Excel and OpenOffice (see below)

The problem is the different reference date and counting. The serial
number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
serial number 1 in AOO is related to 12/31/1899 because the reference
date in AOO is 12/30/1899.

If cell A2 would be formatted as number everything would be fine. But
formatted as date it takes the integer value 1 as offset to our
reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.

So this means it is wrong or better misleading by design. I am not sure
if this can be fixed or should be fixed.

Any opinions?

Juergen


OpenOffice Help
###
DAY
Returns the day of given date value. The day is returned as an integer
between 1 and 31. You can also enter a negative date/time value.

Syntax
DAY(Number)
Number, as a time value, is a decimal, for which the day is to be returned.

Examples
DAY(1) returns 31 (since OpenOffice starts counting at zero from
December 30, 1899)
DAY(NOW()) returns the current day.
=DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
might get formatted differently after you press Enter).
###

Excel Help
###
DAY
Show AllShow All

Returns the day of a date, represented by a serial number. The day is
given as an integer ranging from 1 to 31.

Syntax

DAY(serial_number)

Serial_number is the date of the day you are trying to find. Dates
should be entered by using the DATE function, or as results of other
formulas or functions. For example, use DATE(2008,5,23) for the 23rd day
of May, 2008. Problems can occur if dates are entered as text.

Remarks

Microsoft Excel stores dates as sequential serial numbers so they can be
used in calculations. By default, January 1, 1900 is serial number 1,
and January 1, 2008 is serial number 39448 because it is 39,448 days
after January 1, 1900. Microsoft Excel for the Macintosh uses a
different date system as its default.

Values returned by the YEAR, MONTH and DAY functions will be Gregorian
values regardless of the display format for the supplied date value. For
example, if the display format of the supplied date is Hijri, the
returned values for the YEAR, MONTH and DAY functions will be values
associated with the equivalent Gregorian date.

Example

The example may be easier to understand if you copy it to a blank worksheet.
###

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



Re: Interesting interoperability problem with formatting of date

2014-01-10 Thread Herbert Duerr

On 10.01.2014 17:12, Jürgen Schmidt wrote:

I received a xls document with some date values, date related functions
and formatting and noticed an interesting interoperability problem.

For example:
Cell Value  FormatVisible Value
A1   01/01/2014 MM/DD/YY  01/01/2014
A2   =DAY(A1)   DD31

Excel shows the value 1 and the user expected the same value in
OpenOffice but we show 31.

The reason can be explained by looking in the help of the DAY function
in Excel and OpenOffice (see below)

The problem is the different reference date and counting. The serial
number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
serial number 1 in AOO is related to 12/31/1899 because the reference
date in AOO is 12/30/1899.


FWIW the rationale behind the different reference date is given in [1]. 
Apparently the problem solved by using a different reference was that 
the year 1900 was not a leap year, because of the modulo-100 rule.


[1] https://issues.apache.org/ooo/show_bug.cgi?id=26125#c2


If cell A2 would be formatted as number everything would be fine. But
formatted as date it takes the integer value 1 as offset to our
reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.


Weighing the benefits of the workaround mentioned above with 
interoperability problems or the problem Jürgen just described, my scale 
would tip for a reference date (== day 0) of Dec 31, 1899.



So this means it is wrong or better misleading by design. I am not sure
if this can be fixed or should be fixed.

Any opinions?


If there is a way to change our reference day without losing backwards 
compatibility for existing documents then we should go for it.


Herbert

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



Re: Interesting interoperability problem with formatting of date

2014-01-10 Thread Rob Weir
On Fri, Jan 10, 2014 at 11:12 AM, Jürgen Schmidt jogischm...@gmail.com wrote:
 Hi,

 I received a xls document with some date values, date related functions
 and formatting and noticed an interesting interoperability problem.

 For example:
 Cell Value  FormatVisible Value
 A1   01/01/2014 MM/DD/YY  01/01/2014
 A2   =DAY(A1)   DD31

 Excel shows the value 1 and the user expected the same value in
 OpenOffice but we show 31.

 The reason can be explained by looking in the help of the DAY function
 in Excel and OpenOffice (see below)

 The problem is the different reference date and counting. The serial
 number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
 serial number 1 in AOO is related to 12/31/1899 because the reference
 date in AOO is 12/30/1899.

 If cell A2 would be formatted as number everything would be fine. But
 formatted as date it takes the integer value 1 as offset to our
 reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.

 So this means it is wrong or better misleading by design. I am not sure
 if this can be fixed or should be fixed.

 Any opinions?


OpenForumula (the spreadsheet formula part of ODF 1.2) says:

--
6.10.5 DAY
Summary: Returns the day from a date.
Syntax: DAY( DateParam Date )
Returns: Number
Constraints: None
Semantics: Returns the day portion of a date.
--

So DAY returns a number.  I hope we all agree that this number is 1,
in your example, and cannot be anything else.

Then the question is how we convert from numbers to dates.   This is
implementation-defined.   Even totally within Excel it is inconsistent
because Excel on the Mac uses a different base date (1/1/1904) than
Excel on Windows.  And as you point out OpenOffice uses a different
reference date.

So in practice the implicit conversion from numbers to dates is a
non-portable construct.  A smart spreadsheet application would warn
the user whenever they tried to do this kind of conversion.  The
preferred technique is to use the DATE() function to explicitly
convert from integers to a date value.  This is portable.

Regards,

-Rob


 Juergen


 OpenOffice Help
 ###
 DAY
 Returns the day of given date value. The day is returned as an integer
 between 1 and 31. You can also enter a negative date/time value.

 Syntax
 DAY(Number)
 Number, as a time value, is a decimal, for which the day is to be returned.

 Examples
 DAY(1) returns 31 (since OpenOffice starts counting at zero from
 December 30, 1899)
 DAY(NOW()) returns the current day.
 =DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
 might get formatted differently after you press Enter).
 ###

 Excel Help
 ###
 DAY
 Show AllShow All

 Returns the day of a date, represented by a serial number. The day is
 given as an integer ranging from 1 to 31.

 Syntax

 DAY(serial_number)

 Serial_number is the date of the day you are trying to find. Dates
 should be entered by using the DATE function, or as results of other
 formulas or functions. For example, use DATE(2008,5,23) for the 23rd day
 of May, 2008. Problems can occur if dates are entered as text.

 Remarks

 Microsoft Excel stores dates as sequential serial numbers so they can be
 used in calculations. By default, January 1, 1900 is serial number 1,
 and January 1, 2008 is serial number 39448 because it is 39,448 days
 after January 1, 1900. Microsoft Excel for the Macintosh uses a
 different date system as its default.

 Values returned by the YEAR, MONTH and DAY functions will be Gregorian
 values regardless of the display format for the supplied date value. For
 example, if the display format of the supplied date is Hijri, the
 returned values for the YEAR, MONTH and DAY functions will be values
 associated with the equivalent Gregorian date.

 Example

 The example may be easier to understand if you copy it to a blank worksheet.
 ###

 -
 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: Interesting interoperability problem with formatting of date

2014-01-10 Thread Jürgen Schmidt
On 1/10/14 5:39 PM, Rob Weir wrote:
 On Fri, Jan 10, 2014 at 11:12 AM, Jürgen Schmidt jogischm...@gmail.com 
 wrote:
 Hi,

 I received a xls document with some date values, date related functions
 and formatting and noticed an interesting interoperability problem.

 For example:
 Cell Value  FormatVisible Value
 A1   01/01/2014 MM/DD/YY  01/01/2014
 A2   =DAY(A1)   DD31

 Excel shows the value 1 and the user expected the same value in
 OpenOffice but we show 31.

 The reason can be explained by looking in the help of the DAY function
 in Excel and OpenOffice (see below)

 The problem is the different reference date and counting. The serial
 number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
 serial number 1 in AOO is related to 12/31/1899 because the reference
 date in AOO is 12/30/1899.

 If cell A2 would be formatted as number everything would be fine. But
 formatted as date it takes the integer value 1 as offset to our
 reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.

 So this means it is wrong or better misleading by design. I am not sure
 if this can be fixed or should be fixed.

 Any opinions?

 
 OpenForumula (the spreadsheet formula part of ODF 1.2) says:
 
 --
 6.10.5 DAY
 Summary: Returns the day from a date.
 Syntax: DAY( DateParam Date )
 Returns: Number
 Constraints: None
 Semantics: Returns the day portion of a date.
 --
 
 So DAY returns a number.  I hope we all agree that this number is 1,
 in your example, and cannot be anything else.
 
 Then the question is how we convert from numbers to dates.   This is
 implementation-defined.   Even totally within Excel it is inconsistent
 because Excel on the Mac uses a different base date (1/1/1904) than
 Excel on Windows.  And as you point out OpenOffice uses a different
 reference date.
 
 So in practice the implicit conversion from numbers to dates is a
 non-portable construct.  A smart spreadsheet application would warn
 the user whenever they tried to do this kind of conversion.  The
 preferred technique is to use the DATE() function to explicitly
 convert from integers to a date value.  This is portable.

the problem is that most users probably don't care about this from their
end users perspective and will simply complain :-(

Juergen


 
 Regards,
 
 -Rob
 
 
 Juergen


 OpenOffice Help
 ###
 DAY
 Returns the day of given date value. The day is returned as an integer
 between 1 and 31. You can also enter a negative date/time value.

 Syntax
 DAY(Number)
 Number, as a time value, is a decimal, for which the day is to be returned.

 Examples
 DAY(1) returns 31 (since OpenOffice starts counting at zero from
 December 30, 1899)
 DAY(NOW()) returns the current day.
 =DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
 might get formatted differently after you press Enter).
 ###

 Excel Help
 ###
 DAY
 Show AllShow All

 Returns the day of a date, represented by a serial number. The day is
 given as an integer ranging from 1 to 31.

 Syntax

 DAY(serial_number)

 Serial_number is the date of the day you are trying to find. Dates
 should be entered by using the DATE function, or as results of other
 formulas or functions. For example, use DATE(2008,5,23) for the 23rd day
 of May, 2008. Problems can occur if dates are entered as text.

 Remarks

 Microsoft Excel stores dates as sequential serial numbers so they can be
 used in calculations. By default, January 1, 1900 is serial number 1,
 and January 1, 2008 is serial number 39448 because it is 39,448 days
 after January 1, 1900. Microsoft Excel for the Macintosh uses a
 different date system as its default.

 Values returned by the YEAR, MONTH and DAY functions will be Gregorian
 values regardless of the display format for the supplied date value. For
 example, if the display format of the supplied date is Hijri, the
 returned values for the YEAR, MONTH and DAY functions will be values
 associated with the equivalent Gregorian date.

 Example

 The example may be easier to understand if you copy it to a blank worksheet.
 ###

 -
 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: Interesting interoperability problem with formatting of date

2014-01-10 Thread Rob Weir
On Fri, Jan 10, 2014 at 12:07 PM, Jürgen Schmidt jogischm...@gmail.com wrote:
 On 1/10/14 5:39 PM, Rob Weir wrote:
 On Fri, Jan 10, 2014 at 11:12 AM, Jürgen Schmidt jogischm...@gmail.com 
 wrote:
 Hi,

 I received a xls document with some date values, date related functions
 and formatting and noticed an interesting interoperability problem.

 For example:
 Cell Value  FormatVisible Value
 A1   01/01/2014 MM/DD/YY  01/01/2014
 A2   =DAY(A1)   DD31

 Excel shows the value 1 and the user expected the same value in
 OpenOffice but we show 31.

 The reason can be explained by looking in the help of the DAY function
 in Excel and OpenOffice (see below)

 The problem is the different reference date and counting. The serial
 number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
 serial number 1 in AOO is related to 12/31/1899 because the reference
 date in AOO is 12/30/1899.

 If cell A2 would be formatted as number everything would be fine. But
 formatted as date it takes the integer value 1 as offset to our
 reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.

 So this means it is wrong or better misleading by design. I am not sure
 if this can be fixed or should be fixed.

 Any opinions?


 OpenForumula (the spreadsheet formula part of ODF 1.2) says:

 --
 6.10.5 DAY
 Summary: Returns the day from a date.
 Syntax: DAY( DateParam Date )
 Returns: Number
 Constraints: None
 Semantics: Returns the day portion of a date.
 --

 So DAY returns a number.  I hope we all agree that this number is 1,
 in your example, and cannot be anything else.

 Then the question is how we convert from numbers to dates.   This is
 implementation-defined.   Even totally within Excel it is inconsistent
 because Excel on the Mac uses a different base date (1/1/1904) than
 Excel on Windows.  And as you point out OpenOffice uses a different
 reference date.

 So in practice the implicit conversion from numbers to dates is a
 non-portable construct.  A smart spreadsheet application would warn
 the user whenever they tried to do this kind of conversion.  The
 preferred technique is to use the DATE() function to explicitly
 convert from integers to a date value.  This is portable.

 the problem is that most users probably don't care about this from their
 end users perspective and will simply complain :-(


Which is why we should warn them when they are doing something
non-portable.  It is like a compiler warns you if you do something
dumb.   User behavior is part of the problem here.

For example, one solution might be to have a safe mode in AOO where
implicit conversions like this don't exist.  If you try, you get an
error, just as if you tried to enter a formula like = fish + 42

Did you know that there is a group dedicated the studying mistakes
like this that users make in spreadsheets, the European Spreadsheet
Risks Interest Group:

http://www.eusprig.org/horror-stories.htm

It is a real problem.  Users might complain, but when I read about
spreadsheet mistakes costing millions of dollars I wonder if users are
complaining about the right things?  Stricter type checking in
spreadsheets (if made optional) would be  huge help.

-Rob

 Juergen



 Regards,

 -Rob


 Juergen


 OpenOffice Help
 ###
 DAY
 Returns the day of given date value. The day is returned as an integer
 between 1 and 31. You can also enter a negative date/time value.

 Syntax
 DAY(Number)
 Number, as a time value, is a decimal, for which the day is to be returned.

 Examples
 DAY(1) returns 31 (since OpenOffice starts counting at zero from
 December 30, 1899)
 DAY(NOW()) returns the current day.
 =DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
 might get formatted differently after you press Enter).
 ###

 Excel Help
 ###
 DAY
 Show AllShow All

 Returns the day of a date, represented by a serial number. The day is
 given as an integer ranging from 1 to 31.

 Syntax

 DAY(serial_number)

 Serial_number is the date of the day you are trying to find. Dates
 should be entered by using the DATE function, or as results of other
 formulas or functions. For example, use DATE(2008,5,23) for the 23rd day
 of May, 2008. Problems can occur if dates are entered as text.

 Remarks

 Microsoft Excel stores dates as sequential serial numbers so they can be
 used in calculations. By default, January 1, 1900 is serial number 1,
 and January 1, 2008 is serial number 39448 because it is 39,448 days
 after January 1, 1900. Microsoft Excel for the Macintosh uses a
 different date system as its default.

 Values returned by the YEAR, MONTH and DAY functions will be Gregorian
 values regardless of the display format for the supplied date value. For
 example, if the display format of the supplied date is Hijri, the
 returned values for the YEAR, MONTH and DAY functions will be values
 associated with the equivalent Gregorian date.

 Example

 The example may be easier to understand if 

Re: Interesting interoperability problem with formatting of date

2014-01-10 Thread Rory O'Farrell
On Fri, 10 Jan 2014 18:07:10 +0100
Jürgen Schmidt jogischm...@gmail.com wrote:

 On 1/10/14 5:39 PM, Rob Weir wrote:
  On Fri, Jan 10, 2014 at 11:12 AM, Jürgen Schmidt jogischm...@gmail.com 
  wrote:
  Hi,
 
  I received a xls document with some date values, date related functions
  and formatting and noticed an interesting interoperability problem.
 
  For example:
  Cell Value  FormatVisible Value
  A1   01/01/2014 MM/DD/YY  01/01/2014
  A2   =DAY(A1)   DD31
 
  Excel shows the value 1 and the user expected the same value in
  OpenOffice but we show 31.
 
  The reason can be explained by looking in the help of the DAY function
  in Excel and OpenOffice (see below)
 
  The problem is the different reference date and counting. The serial
  number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
  serial number 1 in AOO is related to 12/31/1899 because the reference
  date in AOO is 12/30/1899.
 
  If cell A2 would be formatted as number everything would be fine. But
  formatted as date it takes the integer value 1 as offset to our
  reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.
 
  So this means it is wrong or better misleading by design. I am not sure
  if this can be fixed or should be fixed.
 
  Any opinions?
 
  
  OpenForumula (the spreadsheet formula part of ODF 1.2) says:
  
  --
  6.10.5 DAY
  Summary: Returns the day from a date.
  Syntax: DAY( DateParam Date )
  Returns: Number
  Constraints: None
  Semantics: Returns the day portion of a date.
  --
  
  So DAY returns a number.  I hope we all agree that this number is 1,
  in your example, and cannot be anything else.
  
  Then the question is how we convert from numbers to dates.   This is
  implementation-defined.   Even totally within Excel it is inconsistent
  because Excel on the Mac uses a different base date (1/1/1904) than
  Excel on Windows.  And as you point out OpenOffice uses a different
  reference date.
  
  So in practice the implicit conversion from numbers to dates is a
  non-portable construct.  A smart spreadsheet application would warn
  the user whenever they tried to do this kind of conversion.  The
  preferred technique is to use the DATE() function to explicitly
  convert from integers to a date value.  This is portable.
 
 the problem is that most users probably don't care about this from their
 end users perspective and will simply complain :-(
 
 Juergen
 
 
  
  Regards,
  
  -Rob
  
  
  Juergen
 
 
  OpenOffice Help
  ###
  DAY
  Returns the day of given date value. The day is returned as an integer
  between 1 and 31. You can also enter a negative date/time value.
 
  Syntax
  DAY(Number)
  Number, as a time value, is a decimal, for which the day is to be returned.
 
  Examples
  DAY(1) returns 31 (since OpenOffice starts counting at zero from
  December 30, 1899)
  DAY(NOW()) returns the current day.
  =DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
  might get formatted differently after you press Enter).
  ###
 
  Excel Help
  ###
  DAY
  Show AllShow All
 
  Returns the day of a date, represented by a serial number. The day is
  given as an integer ranging from 1 to 31.
 
  Syntax
 
  DAY(serial_number)
 
  Serial_number is the date of the day you are trying to find. Dates
  should be entered by using the DATE function, or as results of other
  formulas or functions. For example, use DATE(2008,5,23) for the 23rd day
  of May, 2008. Problems can occur if dates are entered as text.
 
  Remarks
 
  Microsoft Excel stores dates as sequential serial numbers so they can be
  used in calculations. By default, January 1, 1900 is serial number 1,
  and January 1, 2008 is serial number 39448 because it is 39,448 days
  after January 1, 1900. Microsoft Excel for the Macintosh uses a
  different date system as its default.
 
  Values returned by the YEAR, MONTH and DAY functions will be Gregorian
  values regardless of the display format for the supplied date value. For
  example, if the display format of the supplied date is Hijri, the
  returned values for the YEAR, MONTH and DAY functions will be values
  associated with the equivalent Gregorian date.
 
  Example
 
  The example may be easier to understand if you copy it to a blank 
  worksheet.
  ###
 
  -

Insert an Option in /Tools /Options : OpenOffice Calc : Calculate page, under 
Dates: a checkbox for dates compatible with Excel (and some warning about the 
error?)

-- 
Rory O'Farrell ofarr...@iol.ie

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



Re: Interesting interoperability problem with formatting of date

2014-01-10 Thread Rob Weir
On Fri, Jan 10, 2014 at 12:25 PM, Rory O'Farrell ofarr...@iol.ie wrote:
 On Fri, 10 Jan 2014 18:07:10 +0100
 Jürgen Schmidt jogischm...@gmail.com wrote:

 On 1/10/14 5:39 PM, Rob Weir wrote:
  On Fri, Jan 10, 2014 at 11:12 AM, Jürgen Schmidt jogischm...@gmail.com 
  wrote:
  Hi,
 
  I received a xls document with some date values, date related functions
  and formatting and noticed an interesting interoperability problem.
 
  For example:
  Cell Value  FormatVisible Value
  A1   01/01/2014 MM/DD/YY  01/01/2014
  A2   =DAY(A1)   DD31
 
  Excel shows the value 1 and the user expected the same value in
  OpenOffice but we show 31.
 
  The reason can be explained by looking in the help of the DAY function
  in Excel and OpenOffice (see below)
 
  The problem is the different reference date and counting. The serial
  number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
  serial number 1 in AOO is related to 12/31/1899 because the reference
  date in AOO is 12/30/1899.
 
  If cell A2 would be formatted as number everything would be fine. But
  formatted as date it takes the integer value 1 as offset to our
  reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.
 
  So this means it is wrong or better misleading by design. I am not sure
  if this can be fixed or should be fixed.
 
  Any opinions?
 
 
  OpenForumula (the spreadsheet formula part of ODF 1.2) says:
 
  --
  6.10.5 DAY
  Summary: Returns the day from a date.
  Syntax: DAY( DateParam Date )
  Returns: Number
  Constraints: None
  Semantics: Returns the day portion of a date.
  --
 
  So DAY returns a number.  I hope we all agree that this number is 1,
  in your example, and cannot be anything else.
 
  Then the question is how we convert from numbers to dates.   This is
  implementation-defined.   Even totally within Excel it is inconsistent
  because Excel on the Mac uses a different base date (1/1/1904) than
  Excel on Windows.  And as you point out OpenOffice uses a different
  reference date.
 
  So in practice the implicit conversion from numbers to dates is a
  non-portable construct.  A smart spreadsheet application would warn
  the user whenever they tried to do this kind of conversion.  The
  preferred technique is to use the DATE() function to explicitly
  convert from integers to a date value.  This is portable.

 the problem is that most users probably don't care about this from their
 end users perspective and will simply complain :-(

 Juergen


 
  Regards,
 
  -Rob
 
 
  Juergen
 
 
  OpenOffice Help
  ###
  DAY
  Returns the day of given date value. The day is returned as an integer
  between 1 and 31. You can also enter a negative date/time value.
 
  Syntax
  DAY(Number)
  Number, as a time value, is a decimal, for which the day is to be 
  returned.
 
  Examples
  DAY(1) returns 31 (since OpenOffice starts counting at zero from
  December 30, 1899)
  DAY(NOW()) returns the current day.
  =DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
  might get formatted differently after you press Enter).
  ###
 
  Excel Help
  ###
  DAY
  Show AllShow All
 
  Returns the day of a date, represented by a serial number. The day is
  given as an integer ranging from 1 to 31.
 
  Syntax
 
  DAY(serial_number)
 
  Serial_number is the date of the day you are trying to find. Dates
  should be entered by using the DATE function, or as results of other
  formulas or functions. For example, use DATE(2008,5,23) for the 23rd day
  of May, 2008. Problems can occur if dates are entered as text.
 
  Remarks
 
  Microsoft Excel stores dates as sequential serial numbers so they can be
  used in calculations. By default, January 1, 1900 is serial number 1,
  and January 1, 2008 is serial number 39448 because it is 39,448 days
  after January 1, 1900. Microsoft Excel for the Macintosh uses a
  different date system as its default.
 
  Values returned by the YEAR, MONTH and DAY functions will be Gregorian
  values regardless of the display format for the supplied date value. For
  example, if the display format of the supplied date is Hijri, the
  returned values for the YEAR, MONTH and DAY functions will be values
  associated with the equivalent Gregorian date.
 
  Example
 
  The example may be easier to understand if you copy it to a blank 
  worksheet.
  ###
 
  -

 Insert an Option in /Tools /Options : OpenOffice Calc : Calculate page, under 
 Dates: a checkbox for dates compatible with Excel (and some warning about the 
 error?)


The problem is the average user won't know when to enable this option.
 If you're sent a XLS file you don't know if it was created in Excel
or OpenOffice.  Same for an ODS file.  In fact your needs might vary
from file to file.

If there was a way to detect what app created the spreadsheet, then
you might be able to do something.  But if you have a situation 

Re: AOO with database MariaDB (2)

2014-01-10 Thread Kay Schenk
2014/1/7 Vladislav Stevanovic stevanovicvladis...@gmail.com

 Juregen,
 Can you translate in short version what kind the problem has Kunce? I am
 interesting for MariaDB too.

 Thanks in advance,
 Wlada


Well, I'm not Juergen, but here's what I got from Google translate (not
guaranteed for accuracy of course!) -- it would be useful to find out why
the JDBC driver isn't working well...

===  translation 
I use Apache OpenOffice 4.0.1 ( AOO401m5 (Build : 9714 ) - Rev. 1524958 )
with MariaDB on openSUSE 13.1 with processor AMD Athlon II X2 2.9 GHz.
(Processor,
memory, hard disk was changed with the Ugrade NOT )
- the JDBC driver is far too slow , so that is absolutely no work possible
-so the driver aoo -my- SDBC -1.2 -0- linux_x86 - 64.oxt is used
- the MariaDB has tables with m- to-n relations
- to a form with sub - forms is used (SUB / * / SUB - forms) , which was
originally created with OOo 1.0.5 and last with OOo 3.2 (openSUSE 11.3)
without any problems was in use , the connection between the forms done
with SQL queries (now AOO 4.0.1 WRONG: openSUSE 11.3 -  CORRECT: openSUSE
13.1)

- with AOO I now have the following problems
1)
Form / Writer / Database
When I click within the database in a field and there the search start then
I get an error message if the search word is only an entry after the 40th Entry
is ( for example, the 1000th entry). When I click before the search on the
button  Go to the end  ( the database records) and then start the search
, then no error message is displayed in the search - ie the search is
successful (even when , for example, 1000 entry . ) .

2)
Form / Writer / Database
I have integrated check boxes. They are set to  default state  is not
selected ( NULL ). Here it is impossible to deselect this , and to 0
(FALSE ) to put (NOT NULL ) , function NULL and TRUE ( 1 ). A
switching of the marking field on only two values ​​brings no improvement.
MariaDB The field corresponds to a BIT. , the old fields in the database
that are set to FALSE , are displayed correctly , and I change the values
​​to the console directly into the Datenbak , then the display is in the
form correct. too, a renewal of the marking field ( check box of AOO 4.0.1
) brought no improvement .

3)
Form / Writer / Database
when a form ( with SUB- forms) ( 75kB ) and a Calc file (. ods) are open
from 360kb and I another Calc file (. ods) of 1.1 MB open , then take the
opening 25 seconds. Here OOo 3.2 was faster. When I push in the 1.1 MB file
Ctrl F , then it takes 5 seconds before the search window is open . In
OOo 3.2 , this window was there immediately.

4)
macro
The functioning Basic query under OOo 3.2  ResultSet.getDouble ( 1)  now
houses AOO 4.0.1 an incorrect result - it lacks the decimal places. I read
these values ​​now with  ResultSet.getString (1 ) and convert it with 
CDbl () in a Double value , so my macros continue to work.

Regards / Sincerely


signed Stefan

=



 2014/1/7 Jürgen Schmidt jogischm...@gmail.com

  Hi Stefan,
 
  the env to reproduce this error is more complex and I am no database
  expert. In general I recommend that you ask and describe your problem on
  the German user list (user...@openoffice.apache.org) where you can write
  in German and people understand you.
 
  Die Umgebung um den Fehler zu reproduzieren ist etwas komplexer und ich
  bin selber kein Datenbankexperte. Generell würde ich Dir empfehlen noch
  einmal auf der deutschen User Liste nachzufragen wo deutsch kommuniziert
  wird und die Leute dich verstehen.
 
  Juergen
 
 
  On 1/6/14 2:52 PM, Kunze wrote:
   erster Absatz überarbeitet
  
   Hallo,
  
   I have slowly time and my english is bad. Thats why I write german to
   this mail-address.
  
   Ich nutze Apache OpenOffice 4.0.1 (AOO401m5(Build:9714)  - Rev.
 1524958)
   mit MariaDB unter openSUSE 13.1  mit Prozessor AMD Athlon II X2 2,9GHz.
   (Prozessor, Speicher, Festplatte wurden mit dem Ugrade NICHT geändert)
   -der JDBC-Treiber ist viel zu langsam, damit ist absolut kein arbeiten
   möglich
   -deshalb wird der Treiber aoo-my-sdbc-1.2-0-linux_x86-64.oxt genutzt
   -die MariaDB hat Tabellen mit m-zu-n Beziehungen
   -dazu wird ein Formular mit SUB-Formularen (SUB/*/SUB-Formulare)
   genutzt, welches ursprünglich mit OOo-1.0.5 erstellt und zuletzt mit
   OOo-3.2 (openSUSE 11.3) absolut problemlos im Einsatz war, die
   Verbindung zwischen den Formularen erfolgt mit SQL-Abfragen (jetzt AOO
   4.0.1, FALSCH: openSUSE 11.3 - RICHTIG: openSUSE 13.1)
  
   -mit AOO habe ich jetzt folgende Probleme
   1)
   Formular/Writer/Datenbank
   Wenn ich innerhalb der Datenbank in ein Feld klicke und dort die Suche
   starte dann bekomme ich eine Fehlermeldung, wenn das gesuchte Wort erst
   ein Eintrag ist, der nach dem 40. Eintrag steht (z.B. beim 1000.
   Eintrag). Wenn  ich vor der Suche auf den Button Springe ans Ende
 (der
   Datenbankeinträge) klicke und dann die Suche starte, dann 

Re: Build Fails In Module Coinmp

2014-01-10 Thread Tyler Kavanaugh



On 1/10/2014 6:01 AM, Herbert Duerr wrote:

On 09.01.2014 17:39, Tyler Kavanaugh wrote:

I was able to start the build using Herbert's suggestion, and everything
seemed to be going well all the way until the build system tried to
build the modules coinmp, python, and sal. At that point, it failed.
I've got a build log I can submit, if anyone wants to see it. I also
tried building the individual module sal, by running:

build --from sal -P2 -- -P2

and ended up getting some sort of undefined symbol error coming from the
STL headers, as far as I could tell.


Are you building AOO 4.0.x or trunk? On what platform? If you are
building AOO 4.0.x you have to use the --without-stlport configure
option. On trunk this is automatically enabled.

The relevant excerpt from the build log are essential for solving the
problem. I personally am away for the next couple of days though, but
maybe someone else can figure out what went wrong.
I am building trunk on Windows XP SP3. I don't know which excerpt of the 
build log is relevant, so I'll attach the whole thing (~32 KB).


Herbert

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


build -- version: 275224


=
Building module solenv
=

Entering /cygdrive/i/aoo/main/solenv

solenv deliver
deliver -- version: 275594
Module 'solenv' delivered successfully. 3 files copied, 0 files unchanged

=
Building module boost
=

=
Building module afms
=

=
Building module more_fonts
=

=
Building module MathMLDTD
=

=
Building module extras
=

=
Building module tomcat
=

=
Building module x11_extensions
=

=
Building module beanshell
=

=
Building module soltools
=

=
Building module sane
=

=
Building module vigra
=

=
Building module twain
=

=
Building module hsqldb
=

=
Building module unixODBC
=

=
Building module stax
=

=
Building module apr
=

Entering /cygdrive/i/aoo/main/boost


Entering /cygdrive/i/aoo/main/afms


Entering /cygdrive/i/aoo/main/more_fonts/fonts/ttf_dejavu

MathMLDTD deliver

Entering /cygdrive/i/aoo/main/extras/source/templates/presnt/lang


Entering /cygdrive/i/aoo/main/tomcat

deliver -- version: 275594
Module 'MathMLDTD' delivered successfully. 3 files copied, 0 files unchanged
x11_extensions deliver

Entering /cygdrive/i/aoo/main/beanshell


Entering /cygdrive/i/aoo/main/soltools/winunistd

deliver -- version: 275594
Module 'x11_extensions' delivered successfully. 7 files copied, 0 files 
unchanged
sane deliver

Entering /cygdrive/i/aoo/main/vigra

deliver -- version: 275594
Module 'sane' delivered successfully. 2 files copied, 0 files unchanged

Entering /cygdrive/i/aoo/main/twain/util


Entering /cygdrive/i/aoo/main/hsqldb

unixODBC deliver

Entering /cygdrive/i/aoo/main/stax

deliver -- version: 275594
Module 'unixODBC' delivered successfully. 6 files copied, 0 files unchanged

Entering /cygdrive/i/aoo/ext_libraries/apr

boost deliver
Your java version already contains StAX
afms deliver
deliver -- version: 275594
Module 'afms' delivered successfully. 2 files copied, 0 files unchanged

Entering /cygdrive/i/aoo/main/more_fonts/fonts/ttf_gentium


Entering /cygdrive/i/aoo/main/extras/source/symbols

tomcat deliver
deliver -- version: 275594
Module 'tomcat' delivered successfully. 2 files copied, 0 files unchanged
beanshell deliver
deliver -- version: 275594
Module 'beanshell' delivered successfully. 2 files copied, 0 files unchanged

Entering /cygdrive/i/aoo/main/soltools/mkdepend

vigra deliver
deliver -- version: 275594
Module 'vigra' delivered successfully. 98 files copied, 0 files unchanged
twain deliver
deliver -- version: 275594
Module 'twain' delivered successfully. 2 files copied, 0 files unchanged
hsqldb deliver
deliver -- version: 275594
Module 'hsqldb' delivered successfully. 2 files copied, 0 files unchanged
stax deliver
deliver -- version: 275594
Module 'stax' delivered successfully. 1 files copied, 0 files unchanged
apr deliver
deliver -- version: 275594
Module 'apr' delivered successfully. 40 files copied, 3 files unchanged

Entering /cygdrive/i/aoo/main/more_fonts/fonts/ttf_croscore


Entering /cygdrive/i/aoo/main/extras/source/gallery/txtshapes


Entering /cygdrive/i/aoo/main/soltools/support

Making:all_soltools_support.dpslo
Making:all_soltools_support.dpobj
more_fonts deliver
deliver -- version: 275594
Module 'more_fonts' delivered successfully. 47 files copied, 0 files unchanged

Entering /cygdrive/i/aoo/main/extras/source/templates/wizard/styles/lang


Entering 

Re: Re: Dictionary en_GB - 2014-01-01 - Test version

2014-01-10 Thread Stuart Swales
+1.

en_GB seems to work as expected.

Pity we don't appear to have a history of the changes on the
'obfuscated' dictionary fork in Apache OOo to see what may have been
lost by going back to the Mozilla version.

On 10/01/2014 00:25, Andrea Pescetti wrote:
 On 08/01/2014 Marco A.G.Pinto wrote:
 This OXT includes all English dictionaries as before, with only the
 en_GB updated. I was told to place an unpublished version of it and
 send the link to the DEV ML in order for people to test it for one
 week and give feedback.
 
 I insisted that Marco announced it here since he's taking over
 maintenance of the English dictionary we bundle with the English version
 of OpenOffice.
 
 Specifically, he updated the en_GB dictionary, so you should notice no
 difference if you use the en_US dictionary, but still please do download
 his
 new extension and test if everything works correctly and report errors.
 
 If you use the en_GB dictionary, he provided a small test file and a
 large test file. The small one can be found at
 
 https://dl.dropboxusercontent.com/u/30674540/test_words_speller_20140108.odt
 
 
 as he wrote.
 
 Direct link to download his release candidate version:
 http://extensions.openoffice.org/en/download/17669
 (I tested it on my system and it works as expected)
 
 Regards,
   Andrea.
 

-- 
Stuart Swales

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



Re: Interesting interoperability problem with formatting of date

2014-01-10 Thread shzh zhao
in ooxml,there is a cache result for a formula, for example,1 in A1,2 in
A2, A1+A2 in B1,then the xml will be
sheetData
row r=1 spans=1:2
c r=A1
v1/v
/c
c r=B1
fA1+A2/f
v3/v
/c
/row
row r=2 spans=1:2
c r=A2
v2/v
/c
/row
/sheetData

you can see the v3/v is the cache result in MS office,this is important
to interoperability or the computing speed.
this value can be use to fix such issue.

but in the Biff, the formula structure is like this:
Record FORMULA, BIFF5-BIFF8:
Offset Size Contents
0   2 Index to row
2   2 Index to column
4   2 Index to XF record (➜5.115)
6   8 Result of the formula. See below for details.
14   2 Option flags:
Bit Mask Contents
   0 0001H 1 = Recalculate always
   1 0002H 1 = Calculate on open
   3 0008H 1 = Part of a shared formula
16   4 Not used
20   var. Formula data (RPN token array, ➜3)

the '6   8 Result of the formula. See below for details.'  can be used
to fix this issue?

1. compare the result by oo and the cache value of MS office.
2. set the value by MS/OO
the above is just by suggestion.


2014/1/11 Rob Weir robw...@apache.org

 On Fri, Jan 10, 2014 at 12:25 PM, Rory O'Farrell ofarr...@iol.ie wrote:
  On Fri, 10 Jan 2014 18:07:10 +0100
  Jürgen Schmidt jogischm...@gmail.com wrote:
 
  On 1/10/14 5:39 PM, Rob Weir wrote:
   On Fri, Jan 10, 2014 at 11:12 AM, Jürgen Schmidt 
 jogischm...@gmail.com wrote:
   Hi,
  
   I received a xls document with some date values, date related
 functions
   and formatting and noticed an interesting interoperability problem.
  
   For example:
   Cell Value  FormatVisible Value
   A1   01/01/2014 MM/DD/YY  01/01/2014
   A2   =DAY(A1)   DD31
  
   Excel shows the value 1 and the user expected the same value in
   OpenOffice but we show 31.
  
   The reason can be explained by looking in the help of the DAY
 function
   in Excel and OpenOffice (see below)
  
   The problem is the different reference date and counting. The serial
   number 1 in Excel is 01/01/1900. In OpenOffice we count from 0 and
   serial number 1 in AOO is related to 12/31/1899 because the reference
   date in AOO is 12/30/1899.
  
   If cell A2 would be formatted as number everything would be fine. But
   formatted as date it takes the integer value 1 as offset to our
   reference date, means 12/30/1899 + 1 day = 12/31/1899 = 31.
  
   So this means it is wrong or better misleading by design. I am not
 sure
   if this can be fixed or should be fixed.
  
   Any opinions?
  
  
   OpenForumula (the spreadsheet formula part of ODF 1.2) says:
  
   --
   6.10.5 DAY
   Summary: Returns the day from a date.
   Syntax: DAY( DateParam Date )
   Returns: Number
   Constraints: None
   Semantics: Returns the day portion of a date.
   --
  
   So DAY returns a number.  I hope we all agree that this number is 1,
   in your example, and cannot be anything else.
  
   Then the question is how we convert from numbers to dates.   This is
   implementation-defined.   Even totally within Excel it is inconsistent
   because Excel on the Mac uses a different base date (1/1/1904) than
   Excel on Windows.  And as you point out OpenOffice uses a different
   reference date.
  
   So in practice the implicit conversion from numbers to dates is a
   non-portable construct.  A smart spreadsheet application would warn
   the user whenever they tried to do this kind of conversion.  The
   preferred technique is to use the DATE() function to explicitly
   convert from integers to a date value.  This is portable.
 
  the problem is that most users probably don't care about this from their
  end users perspective and will simply complain :-(
 
  Juergen
 
 
  
   Regards,
  
   -Rob
  
  
   Juergen
  
  
   OpenOffice Help
   ###
   DAY
   Returns the day of given date value. The day is returned as an
 integer
   between 1 and 31. You can also enter a negative date/time value.
  
   Syntax
   DAY(Number)
   Number, as a time value, is a decimal, for which the day is to be
 returned.
  
   Examples
   DAY(1) returns 31 (since OpenOffice starts counting at zero from
   December 30, 1899)
   DAY(NOW()) returns the current day.
   =DAY(C4) returns 5 if you enter 1901-08-05 in cell C4 (the date value
   might get formatted differently after you press Enter).
   ###
  
   Excel Help
   ###
   DAY
   Show AllShow All
  
   Returns the day of a date, represented by a serial number. The day is
   given as an integer ranging from 1 to 31.
  
   Syntax
  
   DAY(serial_number)
  
   Serial_number is the date of the day you are trying to find.
 Dates
   should be entered by using the DATE function, or as results of other
   formulas or functions. For example, use DATE(2008,5,23) for the 23rd
 day
   of May, 2008. Problems can occur if dates are entered as text.
  
   Remarks
  
   Microsoft Excel stores dates as sequential serial numbers so they
 can be
   used in calculations. By default, January 1, 1900 is serial 

Update the dead hyperlink in openoffice.org?

2014-01-10 Thread shzh zhao
hi,
when I read the wiki of openoffice.org, found some of the links are dead
now.

for example:
in
https://wiki.openoffice.org/wiki/JavaEclipseTuto
the link of Now click on the *Add* Button on the upper right corner and
paste this *http://drake79.users.sourceforge.net/ooeclipse/site/
http://drake79.users.sourceforge.net/ooeclipse/site/* .
this link is dead now.
such issue is a very bad experience for a beginner or a volunteer.
at a regular interval,Aoo should use a tool to scan the website,and update
the dead link to a valid one.

-- 



*mailto: *aoo.zhaos...@gmail.com https://google.com/profiles
https://google.com/profiles


Re: AOO with database MariaDB (2)

2014-01-10 Thread Vladislav Stevanovic
it would be useful to find out why the JDBC driver isn't working well...

Yes, it would be. Thanks for effort.

Regards,
Wlada


2014/1/10 Kay Schenk kay.sch...@gmail.com

 2014/1/7 Vladislav Stevanovic stevanovicvladis...@gmail.com

  Juregen,
  Can you translate in short version what kind the problem has Kunce? I am
  interesting for MariaDB too.
 
  Thanks in advance,
  Wlada
 

 Well, I'm not Juergen, but here's what I got from Google translate (not
 guaranteed for accuracy of course!) -- it would be useful to find out why
 the JDBC driver isn't working well...

 ===  translation 
 I use Apache OpenOffice 4.0.1 ( AOO401m5 (Build : 9714 ) - Rev. 1524958 )
 with MariaDB on openSUSE 13.1 with processor AMD Athlon II X2 2.9 GHz.
 (Processor,
 memory, hard disk was changed with the Ugrade NOT )
 - the JDBC driver is far too slow , so that is absolutely no work possible
 -so the driver aoo -my- SDBC -1.2 -0- linux_x86 - 64.oxt is used
 - the MariaDB has tables with m- to-n relations
 - to a form with sub - forms is used (SUB / * / SUB - forms) , which was
 originally created with OOo 1.0.5 and last with OOo 3.2 (openSUSE 11.3)
 without any problems was in use , the connection between the forms done
 with SQL queries (now AOO 4.0.1 WRONG: openSUSE 11.3 -  CORRECT: openSUSE
 13.1)

 - with AOO I now have the following problems
 1)
 Form / Writer / Database
 When I click within the database in a field and there the search start then
 I get an error message if the search word is only an entry after the 40th
 Entry
 is ( for example, the 1000th entry). When I click before the search on the
 button  Go to the end  ( the database records) and then start the search
 , then no error message is displayed in the search - ie the search is
 successful (even when , for example, 1000 entry . ) .

 2)
 Form / Writer / Database
 I have integrated check boxes. They are set to  default state  is not
 selected ( NULL ). Here it is impossible to deselect this , and to 0
 (FALSE ) to put (NOT NULL ) , function NULL and TRUE ( 1 ). A
 switching of the marking field on only two values brings no improvement.
 MariaDB The field corresponds to a BIT. , the old fields in the database
 that are set to FALSE , are displayed correctly , and I change the values
 to the console directly into the Datenbak , then the display is in the
 form correct. too, a renewal of the marking field ( check box of AOO 4.0.1
 ) brought no improvement .

 3)
 Form / Writer / Database
 when a form ( with SUB- forms) ( 75kB ) and a Calc file (. ods) are open
 from 360kb and I another Calc file (. ods) of 1.1 MB open , then take the
 opening 25 seconds. Here OOo 3.2 was faster. When I push in the 1.1 MB file
 Ctrl F , then it takes 5 seconds before the search window is open . In
 OOo 3.2 , this window was there immediately.

 4)
 macro
 The functioning Basic query under OOo 3.2  ResultSet.getDouble ( 1)  now
 houses AOO 4.0.1 an incorrect result - it lacks the decimal places. I read
 these values now with  ResultSet.getString (1 ) and convert it with 
 CDbl () in a Double value , so my macros continue to work.

 Regards / Sincerely


 signed Stefan

 =


 
  2014/1/7 Jürgen Schmidt jogischm...@gmail.com
 
   Hi Stefan,
  
   the env to reproduce this error is more complex and I am no database
   expert. In general I recommend that you ask and describe your problem
 on
   the German user list (user...@openoffice.apache.org) where you can
 write
   in German and people understand you.
  
   Die Umgebung um den Fehler zu reproduzieren ist etwas komplexer und ich
   bin selber kein Datenbankexperte. Generell würde ich Dir empfehlen noch
   einmal auf der deutschen User Liste nachzufragen wo deutsch
 kommuniziert
   wird und die Leute dich verstehen.
  
   Juergen
  
  
   On 1/6/14 2:52 PM, Kunze wrote:
erster Absatz überarbeitet
   
Hallo,
   
I have slowly time and my english is bad. Thats why I write german to
this mail-address.
   
Ich nutze Apache OpenOffice 4.0.1 (AOO401m5(Build:9714)  - Rev.
  1524958)
mit MariaDB unter openSUSE 13.1  mit Prozessor AMD Athlon II X2
 2,9GHz.
(Prozessor, Speicher, Festplatte wurden mit dem Ugrade NICHT
 geändert)
-der JDBC-Treiber ist viel zu langsam, damit ist absolut kein
 arbeiten
möglich
-deshalb wird der Treiber aoo-my-sdbc-1.2-0-linux_x86-64.oxt genutzt
-die MariaDB hat Tabellen mit m-zu-n Beziehungen
-dazu wird ein Formular mit SUB-Formularen (SUB/*/SUB-Formulare)
genutzt, welches ursprünglich mit OOo-1.0.5 erstellt und zuletzt mit
OOo-3.2 (openSUSE 11.3) absolut problemlos im Einsatz war, die
Verbindung zwischen den Formularen erfolgt mit SQL-Abfragen (jetzt
 AOO
4.0.1, FALSCH: openSUSE 11.3 - RICHTIG: openSUSE 13.1)
   
-mit AOO habe ich jetzt folgende Probleme
1)
Formular/Writer/Datenbank
Wenn ich innerhalb der Datenbank in ein Feld klicke und dort die
 Suche