Starting Introduction to Contributing to Apache OpenOffice Module

2013-02-17 Thread Verizon - Cathy
Hello All,
I'm George Fravel and live in the Downingtown area of Pennsylvania ( a suburb 
of Philadelphia), USA.

I have a background in systems analysis, organizational operational improvement 
(staffing, staff scheduling, materials management, etc), management of software 
development, web development, and training/teaching.  Prior to the above, I was 
an officer in the U.S. Army for eight years.  

Current semi-retired I teach introduction to computers and applications (MS 
office) at LaSalle University (Philadelphia, PA, USA) and periodically web 
development, java programming, HTML, animation and graphics (Flash and 
PhotoShop) and digital photography.  Until programs were dropped, I also taught 
the above for Penn State University, DPT Business School, and Cittone Institute 
(the latter two being business schools).

Based on content provided on open source sites, it appears that my most 
likely use would be in the categories of user and QA.

I'm looking for MEANINGFUL involvement in development and QA my background 
might suggest. 

George Fravel 


Sent from my iPad)

Nightly Builds

2013-02-17 Thread Mechtilde
Hello

where can I get an actual nightly build for testing for a 64 bit
Linux-System (favoured DEBs)

http://ci.apache.org/projects/openoffice/#linux64 gives a 404

Kind regards

Mechtilde



signature.asc
Description: OpenPGP digital signature


Re: Nightly Builds

2013-02-17 Thread Mechtilde
Sorry for the noise,

Now it works

Mechtilde

Am 17.02.2013 09:38, schrieb Mechtilde:
 Hello
 
 where can I get an actual nightly build for testing for a 64 bit
 Linux-System (favoured DEBs)
 
 http://ci.apache.org/projects/openoffice/#linux64 gives a 404
 
 Kind regards
 
 Mechtilde
 




signature.asc
Description: OpenPGP digital signature


Re: Calc behavior: result of 0 ^ 0

2013-02-17 Thread Andrea Pescetti

On 16/02/2013 Hagar Delest wrote:

I'm rather disappointed by the way it has been handled.


I agree it could have been better. There were also some unprecedented 
events, like a veto, and the discussion mixed in procedural elements, 
technical elements, folkloristic elements... And the tone of some 
messages should have been better. There are other threads open to 
discuss the generic handling, and I'm confident we will improve in future.


Regards,
  Andrea.


Re: 4.0 and loss of backward compatibility for extensions with toolbar

2013-02-17 Thread Andrea Pescetti

On 12/02/2013 Jürgen Schmidt wrote:

If we support both the
underlying code would be more complex, slower and more ugly to maintain.


OK. I had understood this part, so let's have a detailed description of 
the impact before we see how to handle this.



The whole discussion is really based on assumption. We can ask our
friends of SourceForge to analyze by a script all extensions and check
if they contain an Addon.xcu or not. All developers, maintainers of
extensions with Addon.xcu can we contact and can inform them about the
proposed change and how to adapt the xcu.


Good ideas, and we could maybe consider to add an Outdated notice, 
similar to the wiki pages, to extensions that contain an Addons.xcu.


So, to start getting some facts, what should the script do? Unzip the 
extension and look in the expanded tree for a file named exactly 
Addons.xcu (not Addon.xcu, right)? Shall we also ask to check how 
many extensions provide an OpenOffice.org-maximal-version parameter as 
listed at 
http://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Description_of_XML_Elements 
?


In light of Ariel's detailed analysis of the Oracle extensions 
(thanks!), what does

  Addons.cxu but *only* with OfficeMenuBarMerging node
mean? I assume you meant Addons.xcu, but what does only with 
OfficeMenuBarMerging node mean? That these extensions will not be 
affected by this particular change? Or that updating them will be easier?


We will have other elements to consider before assessing the impact on 
users (for example, the website does not currently filter by OpenOffice 
version; and some popular extensions, like LanguageTool, are not hosted 
in the official repository), but it's very good if we can have some real 
numbers to start.


Regards,
  Andrea.


Re: 4.0 and loss of backward compatibility for extensions with toolbar

2013-02-17 Thread Fernando Cassia
On Mon, Feb 11, 2013 at 6:46 PM, Rob Weir robw...@apache.org wrote:
 My impression was that even if we made no changes, from the user's
 perspective, they would lose all extensions.  This is due to the
 change in base directory for the profile.  So all extensions would be
 lost and need to be reinstalled.  So there will be no doubt in the
 user's mind, even if they do not read the release notes, that the
 extensions are gone.

Just copy the Firefox way A dialog reading something like Oh,
we´ve detected some extesions, checking for compatibility with 4.0...
followed by the following extensions are not compatible with 4.0 and
have been disabled, you might want to check [url] for newer versions
compatible with 4.0.

Of course, automated checking of each extension on a central database
(like FF does) would be great, but the half-solution (informative
message) above is better than nothing.
Just my $0.02
FC

-- 
During times of Universal Deceit, telling the truth becomes a revolutionary act
Durante épocas de Engaño Universal, decir la verdad se convierte en un
Acto Revolucionario
- George Orwell


[BUG][Assignment] Bug 121722 - IMCSCH and IMSECH calculate wrong

2013-02-17 Thread Maarten Kesselaers
Hi,

I would like to fix this bug.
Can someone assign it to me?

I think I should modify this in the module SC, correct?

Thanks,
Regards,
Maarten


Re: [BUG][Assignment] Bug 121722 - IMCSCH and IMSECH calculate wrong

2013-02-17 Thread Andrea Pescetti

Maarten Kesselaers wrote:

I would like to fix this bug.
Can someone assign it to me?


With pleasure! https://issues.apache.org/ooo/show_bug.cgi?id=121722 is 
all yours now.



I think I should modify this in the module SC, correct?


Regina wrote in the issue that this is implemented in the scaddins 
module: http://svn.apache.org/viewvc/openoffice/trunk/main/scaddins/


A remark: you might have noticed that there is some resistance to 
changing the values returned by Calc formulas unless they are clearly 
wrong. So I would recommend that you also attach to the issue a test 
document where one can clearly see that the results we return now are 
wrong and that your patch fixes the problem while not introducing new bugs.


Regards,
  Andrea.


Re: [BUG][Assignment] Bug 121722 - IMCSCH and IMSECH calculate wrong

2013-02-17 Thread Ariel Constenla-Haile
On Sun, Feb 17, 2013 at 11:26:54AM +0100, Maarten Kesselaers wrote:
 Hi,
 
 I would like to fix this bug.
 Can someone assign it to me?
 
 I think I should modify this in the module SC, correct?

OpenGrok is your friend:
http://opengrok.adfinis-sygroup.org/source/search?q=IMCSCHproject=aoo-trunk


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpWoCPpDKMGz.pgp
Description: PGP signature


Re: Proposal: How we should handle committer vetos and reverts in the future

2013-02-17 Thread Andrea Pescetti

On 15/02/2013 Greg Stein wrote:

On Thu, Feb 14, 2013 at 05:31:43PM -0500, Rob Weir wrote:

The point of a veto and a quick reversion is to return the code base
quick to a state where it does not contain controversial changes in
it.

That is NOT the point of a veto. A veto is don't ship with that. The
corollary actions are very, very different from what you suggest.


Staying on the constructive part of this thread, here's Ross Gardler 
speaking from the past (2011):

http://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg
  ---
How Conflict is Resolved
* Everyone has a veto (-1)
* Only committers veto is binding
* Veto must be supported:
  - Reasoned argument with course of action
  - Willingness to implement alternative
* Veto's force discussion and, if supported, version control rollback
* Code can be vetoed, releases cannot
  ---
If all this information is integrated into
http://www.apache.org/foundation/glossary.html#Veto
it will be easier in future to approach similar situations.

(For the rest, I'm rather happy to see that some bold forward-looking 
statements in Ross' presentation are now true or mostly true... the 
project has made many steps forward since 2011!)


Regards,
  Andrea.


Re: Proposal: How we should handle committer vetos and reverts in the future

2013-02-17 Thread Ross Gardler
I hope someone moderates this through as I'm no longer subscribed to the
list (Andrea cc'd me)

Reviewing those bullets the only one that might be confusing is 
Willingness to implement alternative. Technically any supportes veto will
stand however, in practice, I (me personally) expect people using a veto to
still be active on a project. An alternative here means that the person
using the veto acknowledges another community members desire to have a
certain change and is willing to help the community find a solution that is
an acceptable compromise.

With this clarification I think all the points are already in the FAQ but
if wording can be improved all committer have write access to the
Apache.org site (if you want a review then members@ is the right place).

Ross

Sent from a mobile device, please excuse mistakes and brevity
On 17 Feb 2013 13:50, Andrea Pescetti pesce...@apache.org wrote:

 On 15/02/2013 Greg Stein wrote:

 On Thu, Feb 14, 2013 at 05:31:43PM -0500, Rob Weir wrote:

 The point of a veto and a quick reversion is to return the code base
 quick to a state where it does not contain controversial changes in
 it.

 That is NOT the point of a veto. A veto is don't ship with that. The
 corollary actions are very, very different from what you suggest.


 Staying on the constructive part of this thread, here's Ross Gardler
 speaking from the past (2011):
 http://www.slideshare.net/**rgardler/the-apache-way-and-**openofficeorghttp://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg
   ---
 How Conflict is Resolved
 * Everyone has a veto (-1)
 * Only committers veto is binding
 * Veto must be supported:
   - Reasoned argument with course of action
   - Willingness to implement alternative
 * Veto's force discussion and, if supported, version control rollback
 * Code can be vetoed, releases cannot
   ---
 If all this information is integrated into
 http://www.apache.org/**foundation/glossary.html#Vetohttp://www.apache.org/foundation/glossary.html#Veto
 it will be easier in future to approach similar situations.

 (For the rest, I'm rather happy to see that some bold forward-looking
 statements in Ross' presentation are now true or mostly true... the project
 has made many steps forward since 2011!)

 Regards,
   Andrea.



Re: Draft blog post: International Mother Language Day 2013 -- Translations requested

2013-02-17 Thread Jeongkyu Kim
Hi,

Thanks for your good work! I attached the text version of Korean translation.

Regards,
Jeongkyu

On Sat, Feb 16, 2013 at 9:28 PM, Kadal Amutham vka...@gmail.com wrote:
 I have completed the translation and it is running here
 http://thewink.in/AOO-IMLD/IMLD-2013.html. I have also attached html file
 and the font. Both shall be uploaded together for proper rendering of Tamil
 letters.

 With Warm Regards

 V.Kadal Amutham
 919444360480
 914422396480


 On 16 February 2013 14:30, Kadal Amutham vka...@gmail.com wrote:

 I have just completed Tamil Translation. I have attached the file for
 review. In the mean while I will prepare the html file so that it can be put
 on the web

 With Warm Regards

 V.Kadal Amutham
 919444360480
 914422396480


 On 15 February 2013 22:02, Kadal Amutham vka...@gmail.com wrote:

 The following link can be added to the blog

 http://en.wikipedia.org/wiki/Bengali_Language_Movement

 With Warm Regards

 V.Kadal Amutham
 919444360480
 914422396480


 On 15 February 2013 21:49, Rob Weir robw...@apache.org wrote:

 On Fri, Feb 15, 2013 at 10:43 AM, Donald Whytock dwhyt...@gmail.com
 wrote:
  Up-front disclaimer: These comments are not meant to be negative, but
  do reflect my ignorance of the event.  I'm asking the questions
  because I honestly don't know the answers.  No disrespect intended.
 

 Thanks.  I did some usage editing  I also added the Wikipedia links,
 though I'd encourage translators to identify native language pages for
 these topics, where they exist.

 -Rob


  the way of Bangladeshi people give - the way that Bangladeshi
  people give
  or perhaps how Bangladeshi people give
  or the way of Bangladeshi people to give
 
  In every town of Bangladesh has Language Martyr's Monument - Every
  town of Bangladesh has a Language Martyr's Monument
  or perhaps In every town of Bangladesh there is a Language Martyr's
  Monument
  But just to confirm...does that mean there's a monument in every town,
  or does every town honor Language Movement Day?
 
  There are more than one Language Martyr's Monument in USA, UK, Italy
  and many other countries.
  Again, not sure if this refers to an actual monument or celebration of
  the event.  And is the intent to say that US, UK, Italy and many other
  countries have monuments, or that each of them has more than one?
  Possible alternative: There are Language Martyr's Monuments in the
  USA, UK, Italy and many other countries.
 
  not only in February 21 but also in other days - not only on
  February 21 but also on other days
 
  As volunteer-run,  non-profit organization - As a volunteer-run,
  non-profit organization
 
  Don
 
  On Fri, Feb 15, 2013 at 7:46 AM, Rob Weir robw...@apache.org wrote:
 
  https://blogs.apache.org/preview/OOo/?previewEntry=international_mother_language_day_2013
 
  Thanks to Khan for the background information and Robin for the logo
  design.
 
  1. Proofreading is always appreciated.
 
  2. Robin, maybe you could make a version of the logo with transparent
  background rather than white?
 
  3. Since we are commemorating International Mother Language Day,
  translations of the blog post are most welcome.  If you can send me a
  translation by end of day Tuesday I can add it to the post.  Or if
  you
  host a translation externally we can link to it.
 
  4. I plan on posting on Wednesday afternoon, New York time, so we
  cover February 21st across all time zones.
 
  Thanks!
 
  -Rob







--
Jeongkyu Kim
OpenOffice.org Korean community lead

Community website http://openoffice.or.kr
Personal blog http://openoffice.or.kr/gomme
2013년 세계 모국어의 날


Apache OpenOffice 프로젝트는 자랑스러운 마음으로 2월 21일 세계 모국어의 날을 기리고자 합니다. 여기에서는 이 날이 중요한 
이유와 함께 OpenOffice가 어떻게 언어적 다양성을 지원하고 있으며 여러분이 도울 수 있는 방법은 무엇인지 말씀드리겠습니다.

h32월 21일을 기리는 이유/h3

2월 21일은 UNESCO가 a 
href=http://ko.wikipedia.org/wiki/%EA%B5%AD%EC%A0%9C_%EB%AA%A8%EA%B5%AD%EC%96%B4%EC%9D%98_%EB%82%A0;세계
 모국어의 날(International Mother Language Day)/a로 지정한 날입니다. 세계 모국어의 날은 원래 방글라데시 - 
예전의 동파키스탄 - 에서 1952년부터 기념하기 시작한 언어 운동의 날(Language Movement Day)에서 유래했는데, 이 날은 
a href=http://en.wikipedia.org/wiki/Bengali_Language_Movement;벵골 언어 운동/a 
기간 동안에 Dhaka 대학의 학생들이 파키스탄 경찰과 군대에 의해 사망한 날입니다. 이는 모국어 사용의 독립을 지키기 위해 목숨을 바친 
유일한 사건입니다.

그들을 기억하기 위해 방글라데시 Dhaka 대학에는 a 
href=http://en.wikipedia.org/wiki/Shaheed_Minar,_Dhaka;모국어 순교자 기념비(Shahid 
Minar)/a가 있습니다. 매년 백만명 이상의 사람들이 여기에 꽃을 바칩니다. 이는 방글라데시에서 큰 행사입니다. 방글라데시를 방문하는 
많은 외국인들은 방글라데시 사람들이 그들의 용감한 영혼에 경의를 표하는 것을 경험합니다. 방글라데시의 많은 도시에는 모국어 순교자의 기념비가 
있어서 지역 사람들도 꽃을 바칩니다. 모국어 순교자 기념비는 일본 도쿄에 있는 이케부코로 공원에도 건립되었습니다. 미국, 영국, 이태리를 
비롯한 많은 나라에도 모국어 순교자 기념비가 있습니다. 2월 21일 뿐만 아니라 늘 여러분의 모국어에 대해 생각해 보시길 바랍니다.

h3OpenOffice와 언어적 다양성/h3

오늘날, 모국어에 대한 위기는 정부의 탄압에서만 비롯되는 것이 아닙니다. 우리가 전자적으로 일하고 의사소통함에 따라 우리가 사용하는 
소프트웨어에서 모국어를 지원하는 것이 매우 중요합니다. 소프트웨어가 어떤 언어를 지원하지 않으면 해당 언어와 이를 말하는 사람이 불리한 처지에 
놓입니다. 이것이 a href=http://openoffice.apache.org/mission.html;Apache OpenOffice 
프로젝트의 공적 목표/a가 언어적 다양성의 지원을 강조하는 이유입니다:

세상에는 6,000개 이상의 언어가 있지만 G20 경제 대국과 

Re: Problems with import of OOXML custGeom command arcTo in import of .pptx

2013-02-17 Thread Andrea Pescetti

On 14/02/2013 Regina Henschel wrote:

https://issues.apache.org/ooo/show_bug.cgi?id=121769 ...
(1) What can we do with regard to license?


If your concern is about conventions (choice of constant definitions and 
attribute names) I, personally and as a non-lawyer, wouldn't see it as 
problematic: license applies to code while this information is retrieved 
from an ODP document.



(2) Should we (if possible from license) follow the way of LO?


If this helps interoperability and the solution is technically good, I 
would be in favor. If it can technically be improved, it should be 
discussed together.


Out of ignorance, is drawooo in drawooo:enhanced-path=M 3 3 G 3 3 ?f0 
?f1 Z N a common convention or something totally new?


Regards,
  Andrea.


RE: Problems with import of OOXML custGeom command arcTo in import of .pptx

2013-02-17 Thread Dennis E. Hamilton
In case it is not clear where conventions arise in conjunction with prefixes on 
XML qualified names, it is the namespace that is bound to the prefix that 
establishes the convention.  The prefix choice is relatively arbitrary (but one 
must avoid unintentional collision with a prefix that is already in use).

Presumably the qualified attribute name prefix drawooo is bound to a 
namespace that is not one specified by any of the OASIS Standards for ODF.  It 
is necessary to know what that namespace is and where is the authority that 
specifies what its local terms (such as enhanced-path) are and what the rules 
for the attribute value are.  Assuming there is such a specification available, 
the namespace becomes reusable by other parties who want to implement the same 
feature.

Since it is an extension, and ODF 1.2 consumers are allowed to ignore any 
foreign attribute names and their values, it is also useful to know what the 
fall-back is in this case.  There is supposed to be a valid document remaining 
after the attribute is ignored.

 - Dennis

PS: Having such an extension in general use is cause to request its 
incorporation in a future OASIS Standard for ODF.  This will change the 
namespace and there will be need to support migration in that case.  The 
earlier the OASIS namespace becomes known, the more quickly implementations can 
be designed to accept either, in anticipation that at some future point, the 
OASIS-specified namespace will become the one that is produced for a particular 
ODF version.  That's all future work though.

PPS: Current Apache OpenOffice 3.4.1 .odt documents declare bindings to the 
following foreign namespaces, although they might not actually be used in any 
given XML content:
   xmlns:ooo=http://openoffice.org/2004/office; 
   xmlns:ooow=http://openoffice.org/2004/writer; 
   xmlns:oooc=http://openoffice.org/2004/calc; 
   xmlns:rpt=http://openoffice.org/2005/report;
   
xmlns:field=urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0
The namespace that is bound to field is unusual.  It is not one of the ones 
defined as under the authority of OAIS.  (Those all begin urn:oasis:names ... .)

-Original Message-
From: Andrea Pescetti [mailto:pesce...@apache.org] 
Sent: Sunday, February 17, 2013 09:26
To: dev@openoffice.apache.org
Subject: Re: Problems with import of OOXML custGeom command arcTo in import of 
.pptx

On 14/02/2013 Regina Henschel wrote:
 https://issues.apache.org/ooo/show_bug.cgi?id=121769 ...
 (1) What can we do with regard to license?

If your concern is about conventions (choice of constant definitions and 
attribute names) I, personally and as a non-lawyer, wouldn't see it as 
problematic: license applies to code while this information is retrieved 
from an ODP document.

 (2) Should we (if possible from license) follow the way of LO?

If this helps interoperability and the solution is technically good, I 
would be in favor. If it can technically be improved, it should be 
discussed together.

Out of ignorance, is drawooo in drawooo:enhanced-path=M 3 3 G 3 3 ?f0 
?f1 Z N a common convention or something totally new?

Regards,
   Andrea.



Re: Problems with import of OOXML custGeom command arcTo in import of .pptx

2013-02-17 Thread Regina Henschel

Hi,

Dennis E. Hamilton schrieb:

In case it is not clear where conventions arise in conjunction with
prefixes on XML qualified names, it is the namespace that is bound to
the prefix that establishes the convention.  The prefix choice is
relatively arbitrary (but one must avoid unintentional collision with
a prefix that is already in use).

Presumably the qualified attribute name prefix drawooo is bound to
a namespace that is not one specified by any of the OASIS Standards
for ODF.  It is necessary to know what that namespace is and where is
the authority that specifies what its local terms (such as
enhanced-path) are and what the rules for the attribute value are.
Assuming there is such a specification available, the namespace
becomes reusable by other parties who want to implement the same
feature.


The used namespace is
http://openoffice.org/2010/draw
AOO has the token XML_N_DRAW_EXT for it, but I don't know where it is used.



Since it is an extension, and ODF 1.2 consumers are allowed to ignore
any foreign attribute names and their values, it is also useful to
know what the fall-back is in this case.  There is supposed to be a
valid document remaining after the attribute is ignored.


I have done some further tests with LibreOffice and it seems that the 
implementation there is not finished, see 
https://bugs.freedesktop.org/show_bug.cgi?id=61028


I have not tried it yet, but I think, that an import of the OOXML 
element custGeom with attribute arcTo would be possible using the 
existing draw:enhanced-path element with the command T.


Kind regards
Regina


Re: I Volunteer

2013-02-17 Thread Andrea Pescetti

Augustus - Aparanji Fine Arts wrote:

I'm a graduate of Photography (BFA) from Jawaharlal Nehru University,
Hyderabad, India and got interest in Graphic Designing with great zeal
over art and aesthetics.
I like to work as volunteer for you.


Welcome, Augustus! Your skills make you a perfect candidate for the 
ongoing logo discussions currently being held on the marketing mailing list.


See http://openoffice.apache.org/orientation/intro-marketing.html for 
more information on joining the OpenOffice marketing group and see the 
wiki to get up to speed with the current logo discussions: for example,

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO4+-+Logo
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO4+-+Desktop+Icons
https://cwiki.apache.org/confluence/display/OOOUSERS/Branding+Planning
https://cwiki.apache.org/confluence/display/OOOUSERS/Apache+OpenOffice+4.0+Brand+Refresh+Project
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO4+-+Social+Sites

Regards,
  Andrea.


RE: Calc behavior: result of 0 ^ 0

2013-02-17 Thread Dennis E. Hamilton
I've been sitting on this in draft since Thursday because the two vetoes
from Kay and Rob seemed to have been sufficient and I didn't want to pile
onto Pedro.  Pedro, it seems to me you are not paying attention.  I agree
that the veto should have left the patch to be reverted yourself, and the
addition of veto as a tag is also very handy now.

And here's mine now:

-1 on the change from returning 1.0 for Calc OpenFormula function POWER(0,0)
to returning an error value (as that term is used specifically for
OpenFormula) instead.

Furthermore, I am prepared to object to *any* patches to Calc functions at
some level that does not explain exactly what the *Calc* impact is.  What is
correct for a C/C++ library result for pow[r] is not relevant.  What matters
is what is correct for *Calc*, and backward compatibility is an important
technical factor that is applicable to this particular case.  

This has become tantamount to a Wikipedia edit war.  It must stop.  This
business about turning in untested (in Calc) code and claiming that all
issues (whatever they include) are resolved is not working.  While that is
presumably more-or-less all right on SVN trunk, I suggest that it is
incumbent on the contributor to take a developer build and demonstrate that
the result is as specified, after claiming what it is that is specified.
And if that fails or the modified behavior is disputed, I prefer that the
trunk not be left dirty.

 - Dennis

TECHNICAL JUSTIFICATION

It is agreed that there are three values any of which may be
implementation-defined as the value produced by an implementation and that
satisfies the ODF 1.2 OpenFormula specification (an OASIS Standard).

AOO Calc produces one of those values and is in accord with ODF 1.2 in that
respect.  (There are no spreadsheet functions defined in earlier versions of
the ODF specification.)

The technical objection is around breaking backward compatibility with the
body of existing OpenOffice.org, Apache OpenOffice, IBM Lotus Symphony and
LibreOffice ODF documents.  (They are all *already* incompatible with what
Excel does, either in its recent ODF 1.2 support, its original native
implementation, or in its support for OOXML.)

The veto is appropriate on those grounds.  A controversial breaking change
is as valid a technical justification as is a performance issue.

PS: I assume that there can continue to be a ballot or whatever other
consensus directed determination following this, but the change should not
be made until it survives such a determination.

PPS: I agree with Rob to the extent that this is not about repair of a
defect.  I understand that some believe otherwise.  I agree that it is about
handling of an edge case in an interoperable manner.  It comes down to
interoperable with whom, because either choice is incompatible with someone.

PPPS: I continue to prefer that POWER(0,0) be the Calc equivalent of NaN.  I
don't believe that gives me the right to impose it.  As a progression of
previous posts from me reveals, I believe that the issue is about defined
functional behavior of a computational procedure, it is not about the
mathematics of exponentiation beyond the desire to approach the far more
significant uncontroversial features of exponentiation sufficient to count
as practical success.  POWER(0,0) is not critical to that endeavor.

-Original Message-
From: Pedro Giffuni [mailto:p...@apache.org] 
Sent: Thursday, February 14, 2013 11:18
To: dev@openoffice.apache.org
Subject: Re: Calc behavior: result of 0 ^ 0

Hello Kay;


- Messaggio originale -
 Da: Kay Schenk 

 
 I readily admit this is true. I would like my veto to stand and here I
will
 elaborate and hopefully provide my technical justification.
 
 In my mind, current mathematical information aside, we have implemented an
 acceptable solution based on the ODF specification. If, at some point,
some
 universal mathematical body says without doubt that 0^0 should never ever
 be considered 1, then I am assuming the ODF standards body would change
the
 standard for that function, and we would then change the current
 calculation.
 
 I have seen many references to this issue on the web, some which 
 support
 the current implementation, some of which do not. In my mind, this needs
to
 go back to OASIS.
 
 So for what it's worth, this is my technical justification. We are not a
 mathematical body, we are implementing code that complies to the ODF
 standard.
 

Can you please point me to the specific point of the ODF standard where
this change has brought us out of compliance?



 If we have a problem with that standard, we need to 
 discuss it with the standards body, not change existing code because
 of a personal viewpoint.


We have no problems with the standards body.

I don't like having to revert my work, of course, but this is not
a matter of personal viewpoint.

Please,, *please* do understand this issue has little to view with
my personal point of view: I didn't create the BZ issue, 

Re: Calc behavior: result of 0 ^ 0

2013-02-17 Thread Pedro Giffuni
Ugh.. I am really tired of this.

I even declare myself agnostic.

I have a new way to address this issue and hopefully put an end to it
and I will post it RSN, OK?

Pedro.



Re: 4.0 and loss of backward compatibility for extensions with toolbar

2013-02-17 Thread Jürgen Schmidt
On 2/17/13 10:36 AM, Andrea Pescetti wrote:
 On 12/02/2013 Jürgen Schmidt wrote:
 If we support both the
 underlying code would be more complex, slower and more ugly to maintain.
 
 OK. I had understood this part, so let's have a detailed description of
 the impact before we see how to handle this.
 
 The whole discussion is really based on assumption. We can ask our
 friends of SourceForge to analyze by a script all extensions and check
 if they contain an Addon.xcu or not. All developers, maintainers of
 extensions with Addon.xcu can we contact and can inform them about the
 proposed change and how to adapt the xcu.
 
 Good ideas, and we could maybe consider to add an Outdated notice,
 similar to the wiki pages, to extensions that contain an Addons.xcu.
 
 So, to start getting some facts, what should the script do? Unzip the
 extension and look in the expanded tree for a file named exactly
 Addons.xcu (not Addon.xcu, right)? 

The first step should be a simple check if an Addons.xcu is contained at
all. Something like unzip -l extension | grep Addons.xcu should be
enough. The second step if an Addons.xcu is contained is to check for
the node oor:name=OfficeToolBar entry. Only if this entry exists
the Addons.xcu the extension has to be updated.

I will provide an example showing the change as part of the
http://wiki.openoffice.org/wiki/API/Incompatible_API_changes

See also
http://wiki.openoffice.org/wiki/API
http://wiki.openoffice.org/wiki/API/Concepts_API_changes


Shall we also ask to check how
 many extensions provide an OpenOffice.org-maximal-version parameter as
 listed at
 http://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Description_of_XML_Elements
 ?

make sense but it is not necessary, this is something that the extension
developer should decide. It's a recommendation to use it to ensure that
an extension works with the next version. It can be seen as part of the
QA for a serious extension ;-)


 
 In light of Ariel's detailed analysis of the Oracle extensions
 (thanks!), what does
   Addons.cxu but *only* with OfficeMenuBarMerging node
 mean? I assume you meant Addons.xcu, but what does only with
 OfficeMenuBarMerging node mean? That these extensions will not be
 affected by this particular change? Or that updating them will be easier?

exactly, we have 2 ways to integrate here. One is to create a completely
new toolbar with a new name. And the second one is to merge into
existing toolbars at a specific position. This can be very useful and is
not affected by this change.

 
 We will have other elements to consider before assessing the impact on
 users (for example, the website does not currently filter by OpenOffice
 version; and some popular extensions, like LanguageTool, are not hosted
 in the official repository), but it's very good if we can have some real
 numbers to start.

well we can of course blow up this to whatever we want. There is a lot
of room for improvements in many areas. We should not mix too many things.

An improved extension repo with a hopefully working extension update
mechanism. Here extensions that are not supported for 4.0 could be
already filtered on the server and there is no demand to transport any
info about this extensions to a 4.0 office.

An improved extension mechanism where we would have an improved workflow
and more features. Browsing extensions directly from the office, a
configurable extension repo, dependencies to other extensions, ...

Juergen