Re: openoffice 3.4 graphic display

[Andrea Pescetti]

gerard wrote:

  I installed 3.4 because it is said that it could handle .docx
  documents. After installing it opened those documents but the figures
  displayed were totally different from the figures in the word
  document. Also figures in .doc documents are no longer displayed


It might be this bug, especially for .doc files:
https://issues.apache.org/ooo/show_bug.cgi?id=119574

Unfortunately it does appear to be reproducible on a clean installation 
and in a normal upgrade scenario, but you might want to check whether 
the setting described in that issue is wrong after the upgrade.


Regards,
  Andrea.

Re: [DISCUSS]Next steps for automated testing

[Reizinger Zoltán]

2012.06.15. 8:31 keltezéssel, Zhe Liu írta:
> Hi all,
> As mentioned before, I was working on a Java library to perform gui
> testing. Actually it has been implemented on Symphony source code. It
> involves 3 modules:
> 1. 
> https://svn-master.apache.org/repos/test/danielsh/symphony-import/symphony/trunk/main/test
> It contains all testing scripts. Some JUnit testcases have been
> written in the package "testcase". Smoke testing is re-implemented
> based on the lib. We also developed some performance testing script,
> but not include in svn.
> 2. 
> https://svn-master.apache.org/repos/test/danielsh/symphony-import/symphony/trunk/main/testcommon
> It contains the low-level implementation to do GUI testing.
> 3. 
> https://svn-master.apache.org/repos/test/danielsh/symphony-import/symphony/trunk/main/testgui
> It contains the common utilities used by uno api testing and GUI testing.
> I also wrote one wiki page to introduce it.
> http://wiki.services.openoffice.org/wiki/QA/vclauto

I'm not a coder, but I run the old VCLtool in past, used for translation
testing, by creating screenshots from each dialog.
This will be possible with new tool?

I try to setup this test configuration on my win7.
I can set up and build test enviroment, and could build it, but can not
run the example test.
Needs some more help on JUnit configuration. Which test class I can use?
Regards,
Zoltan

>
> I propose to do the following tasks next.
> 1. Migrate the library to our AOO trunk. I has successfully used it to
> test AOO 3.4 with some patch.
> symphony/trunk/main/testcommon->ooo/trunk/main/testcommon
> symphony/trunk/main/testgui->ooo/trunk/main/testgui
> symphony/trunk/main/test->ooo/trunk/main/test   or
> ooo/trunk/main/testoo  (Avoid to conflict with the test module that
> already exists in AOO)
> 2. Setup several testing machines to do build verification testing on
> daily build. Post the result on somewhere(e.g. wiki, or maillist) .
> The testing platforms includes:
> Windows XP
> Windows 7 32b/64b
> Mac os x
> Redhat
> Suse
> Ubuntu
> ...? (pls suggest)
> 3. Continue to clean up the UNO API testing. I tried to run it and
> found there are too many failures and some errors. I think API testing
> is very valuable.Ｉt is essential to revive it.
>
> Welcome to comment.
>

[Proposal] Guidelines for list conduct policy

[Wolf Halton]

This is a draft with the additions from the group, for a lazy consensus.
I am envisioning that the final draft can be added to the sign-in progress
for the various mailing-lists and also as a link to the project
mailing-list page.

I have not included any pieces about what happens to an individual who does
not abide by the general group agreements, as that has not been discussed
here yet.

--

List Conduct Policy

   1.

   What Happens in Vegas, Stays in Vegas:
   Anything you read in the private list is by default a private PPMC
   affair and not to be spoken of, or copied to other people who are not in
   the PPMC.  If you think about it, most topic threads probably should be in
   the public lists, except choosing committers and PPMC members, and a very
   few others.
   In fact, all email lists or email conversations have this aspect of
   privacy. Even if there are 23000 subscribers on the list, it is assumed
   that privacy will be maintained and a list member's name and location will
   not be published in a newspaper or some other public venue where personal
   privacy is not expected.
   2.

   Be Nice:
   Not only are there lots of people on this list whose first language is
   not English, there are busy hurried readers.  If other list members are
   telling you they do not understand what you wrote, or take your innocent
   phasing in a poor light, take it as a signal that your writing style is too
   idiomatic or too technical (unlikely but possible) for others to follow
   easily.  This does not necessarily mean you are mean, wrong and bad, so
   just be nice and reword the passage.  Assume people are not in "attack
   mode." We are all on the same team here.
   3.

   Don't Respond When You are Angry:
   Presuming people are not in attack mode means, if you think they are,
   just now, then probably you are just misunderstanding their point. Ad
   hominem attacks, e.g., "You are too dumb to get this," are a sign that you
   yourself may not have a good-enough handle on the issue to explain your
   point clearly.
   4.

   Relax:
   Always remember, that unless there is a *darn* good reason, nothing gets
   decided at the ASF in less than 72 elapsed hours, so your reply can wait
   until morning.  You might even get lucky, and when you check back somebody
   else will have posted either what you wanted to say, or something close
   enough that you can work with it.
   Remember that the members of a community mailing list will get to the
   list when they can. Most of us do this in our spare time, and in different
   time zones. Perhaps the rule of thumb could be to respond no more than once
   per hour, or once per day, to any given thread. The highest frequency of
   responses does not necessarily “Win” in a community of equals. The most
   concise and useful post tends to win, if furthering the dialog and
   advancing the community's goals is what we are after..
   5.

   Get to the Point:
   Write as tersely as possible, and edit down as much possible, so other
   people who are just as busy as you may quickly get your point without
   ending up defensive.
   6.

   Consider trimming the post to which you are responding:
   People who read emails on small screens are not the only ones who are
   frustrated by picking important new information out of tons of stuff they
   have already read.  To trim a post, one simply remove any parts of the post
   to which one is replying that are not important to understand ones reply.
   If the response to one of these posts is, “What? I do not understand,” then
   it may be that too much of the context may have been removed.
   7.

   There are Going to be Exceptions to the Rule:
   All of these guidelines are subject to sanity-testing.
   A person posting child porn on this list will be reported to the
   appropriate authorities and will not be able to complain that their list
   privacy has been violated.
   Ramping up to a release, there are a lot of postings at high frequency.
   Sometimes it takes a long post to say what needs to be said.




More Useful Stuff:

Apache Tips for Email Contributors –

http://www.apache.org/dev/contrib-email-tips.html

Apache OpenOffice Mailing Lists –
http://incubator.apache.org/openofficeorg/mailing-lists.html



 ==

-- 
This Apt Has Super Cow Powers - http://sourcefreedom.com
Open-Source Software in Libraries - http://FOSS4Lib.org
Advancing Libraries Together - http://LYRASIS.org
Apache Open Office Developer wolfhal...@apache.org

Re: Fwd: [CONF] Apache OpenOffice Community > Localization Plan

[Martin Srebotnjak]

So, there will not be a Slovenian 3.4 build?

Lp, m.

2012/6/4 Martin Srebotnjak :
> Will the Slovenian 3.4 release be built?
>
> Thanks, m.
>
>
> 2012/6/2 Martin Srebotnjak 
>>
>> Yes, of course, it is available under the new Apache 2 license.
>>
>> We are also localizing LibreOffice under its own licence.
>>
>> Lp, m.
>>
>>
>> 2012/6/2 Andrea Pescetti 
>>>
>>> On 01/06/2012 Martin Srebotnjak wrote:

 here is the full Slovenian translation for Apache OpenOffice 3.4:
 http://ooo.siccla.net/gsi/apacheOO/3.4.0/GSI_sl.sdf.gz
>>>
>>>
>>> Thanks Martin, Robert, it's great to see that you are continuing the
>>> OpenOffice localization effort! I assume your updates are available under
>>> the Apache 2 license (the current OpenOffice license), right?
>>>
>>> You might consider to submit an ICLA http://www.apache.org/licenses/#clas
>>> : you still retain the copyright but it helps the project to have a proper
>>> "intellectual property" tracking, and to give you direct commit rights for
>>> future updates if helpful.
>>>
>>> Regards,
>>>  Andrea.
>>
>>
>

Re: Next steps for Symphony and AOO

[Kay Schenk]

On Fri, Jun 15, 2012 at 5:24 PM, Yong Lin Ma  wrote:

> Symphony get a java wrapper. That needs more memory footprint.
> Symphony also needs more disk space due the java plug-ins and new
> templates, clip arts.
>
> There is no java wrapper for the build we are discussing here.


Thank you -- this was not clear to me...I didn't really understand the
reference to the java wrapper -- sorry.

I really was quite in agreement with Fernando's remarks on this thread, and
after seeing the additional information on the IBM site, I got  more
concerned.


> The
> memory it needs should in the same level of AOO or may be less due to
> some optimization we made.


Well this would be good news in the right direction!


> When Symphony was integrated in notes, we
> were pushed very hard to fix any increase on memory cost.
>
> Disk space also is not a problem. It quite depends on what we want
> packaged in it.
>

Good! I was thinking about this more also last evening. I was thinking that
maybe some of the current enhancements in Symphony could perhaps be
provided as extensions instead of directly integrated if that's possible.
I think many of our users are happy with the capabilities provided now and
don't really want extra features that consume more resources.


> Last but not the least, the recommended configuration for a software
> given by different people may also be different.
>

Well it would be interesting to see a further discussion on that as well.


>
>
> For more detail info about the contribution, please visit
> http://wiki.services.openoffice.org/wiki/Symphony
>

 I did read through this but it was too much of a summary to provide much
detail. Thank you for it though. This is why I decided to find out more
client requirements from the IBM site.

Yes, we need to discuss in detail development considerations including
sustainability, design considerations, but, in the end, our clients are
what will ultimately determine success I think.

Thank you for this additional information.



>
> On Sat, Jun 16, 2012 at 7:36 AM, Kay Schenk  wrote:
> > On Fri, Jun 15, 2012 at 3:06 PM, Fernando Cassia 
> wrote:
> >
> >> On Mon, Jun 11, 2012 at 10:08 PM, Rob Weir  wrote:
> >>
> >> > I.  Merge code, from Symphony, feature by feature, into AOO, in a
> >> > prioritized order.  This is the "slow" approach, since it would take
> >> > (by the estimates I've seen) a couple of years to bring all of the
> >> > Symphony enhancements and bug fixes over to AOO.
> >> >
> >>
> >> I'm in favor of an evolutionary rather then revolutionary change.
> >> This way, it also gives devs more time to consider what features have a
> >> higher priority and give most benefit to the AOO Suite.
> >>
> >> The second option you suggest is simply replacing OpenOffice with
> >> Symphony
> >> FC
> >>
> >
> > Folks may also be interested in the general FAQ on Symphony (IBM doc)
> >
> > http://www-03.ibm.com/software/lotus/symphony/help.nsf/GeneralFAQ
> >
> > particularly the client requirements which is a concern to me anyway. The
> > recommended disk space is 750M compared to the current 450M for linux for
> > example. (Though on my current setup, it doesn't use even close to 450M).
> > And similar increase for memory requirements.
> >
> > Can someone give more explanation of the client system requirements for
> > Symphony maybe by  augmenting :
> >
> > http://wiki.services.openoffice.org/wiki/Symphony_contribution
> >
> > So, for now, without additional information, I have no opinion.
> >
> >
> > --
> >
> 
> > MzK
> >
> > "There's no crying in baseball!"
> >   -- Jimmy Dugan (Tom Hanks), "A League of Their Own"
>



-- 

MzK

"There's no crying in baseball!"
   -- Jimmy Dugan (Tom Hanks), "A League of Their Own"

Re: Next steps for Symphony and AOO

[Fernando Cassia]

On Fri, Jun 15, 2012 at 9:24 PM, Yong Lin Ma  wrote:

> Symphony get a java wrapper. That needs more memory footprint.


Well ThinkFree office is a Java-based office suite and very lean, even
compared to stock OpenOffice.org.

a 56MB download.

http://office.thinkfree.com/en/download.html
So I guess Java or no-Java is not an indication of bloat or lack thereof.

I remember saying 3-4 years ago "it´d be great if Sun bought ThinkFree and
turned it into "OpenOffice Cloud" integrating it with then-new Google Docs,
keeping OO.o as ´openoffice desktop´".

Where would we be now...
FC

[Mailing lists] User mailing list promotion

[sebb]

May I suggest that the Users mailing list be made the first list on
the mailing list page [1] ?

Developers are likely to be more used to how to find the appropriate
mailing list, the casual user is less likely to read the full page in
order to find the correct list.

Also, the users list is not mentioned on the status page [2].

[1] 
http://incubator.apache.org/openofficeorg/mailing-lists.html#users-mailing-list
[2] http://incubator.apache.org/projects/openofficeorg.html

[NOTICE] OpenOffice Forum and Wiki Scheduled Reboot

[imacat]

The OpenOffice forum (user.services.openoffice.org) and wiki
(wiki.services.openoffice.org) hosts are scheduled to reboot on
2012/6/18 0:00am GMC+0, 23 hours from now.

-- 
Best regards,
imacat ^_*' 
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
Apache OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/




signature.asc
Description: OpenPGP digital signature

Interesting Result of "Wishlist"

[imacat]

Dear all,

A message was posted to the OpenOffice Google+ page, titled
"[DISCUSS] What is the most important issue you'd like to be fixed or
improved on OpenOffice?", and got interesting replies.

https://plus.google.com/114598373874764163668/posts/8MJi9Hh3EmL

Not sure if all the replies are constructive.  Some may be too
vague.  But it still returned interesting result that we can work on with.

P.S. Replies from Peter Lairo are especially clear and specific.

-- 
Best regards,
imacat ^_*' 
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
Apache OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/




signature.asc
Description: OpenPGP digital signature

Would like to help, but...

[Shannon Jacobs]

Feels like I should start by saying that I'm actually one of those weirdos
who used to pay for shareware and such. I admit that I mostly used the
freely available software freely and without paying for it, but there were
also a number of times that I paid for the premium versions, and even a
couple of times when I paid the ransom after the free trial period had
expired. Unfortunately, I never felt that I got more by donating and in
most cases the programs in question soon disappeared anyway. I mostly
concluded that competent programmers aren't going to stay with that
economic model. My best guess is that some of them were hoping to strike it
rich, but they didn't, so they gave up. However, why would I want them to
help them strike it rich, even if their program was great? I don't Las
Vegas economic models, either.

Meanwhile, I hate the anti-freedom anti-choice policies of Microsoft,
Apple, Oracle, and increasingly the google, too. However, their economic
models work.

I would prefer to support you with some money, but I still doubt you'll
survive. Actually, the Sun fiasco has had me using LibreOffice most of the
time these days...

What I would like is an option to pay by the feature on a small project
basis. I would buy one or more shares in features that I wanted, where the
project budget would include such things as testing and programmer time,
etc. The new features would be selected as enough people agreed to pay for
them. The structure I would suggest would actually leave you holding the
money as a kind of charity stock brokerage. Some of the projects might
involve support in various forms, of course.

However I've been advocating this sort of thing for some years. The closest
thing I've seen is Kickstarter, but they seem to be completely lacking in
project management. My suggestion would be more like "reverse auction
charity shares". Unless someone does something like that, I'm not likely to
donate again... I'm convinced the economic model is as important as the
software.


-- 
Freedom. It's about meaningful and unconstrained choice, not beer.

Re: Would like to help, but...

[Fernando Cassia]

On Sun, Jun 17, 2012 at 1:51 AM, Shannon Jacobs wrote:

> Meanwhile, I hate the anti-freedom anti-choice policies of Microsoft,
> Apple, Oracle, and increasingly the google, too. However, their economic
> models work.
>

Hold your horses

Lots of Linux code developed at
http://oss.oracle.com/

(including the Btrfs developed at ORCL and merged in the Linux kernel last
February that makes Linux competitive with Microsoft's ReFS)

Virtualbox
License: GPLv2
https://www.virtualbox.org/

Netbeans
License: CDDL / GPL
http://netbeans.org/

Glassfish
License: CDDL / GPL
http://glassfish.java.net/

OpenJDK
License: GPL2+CE
http://openjdk.java.net/

MySQL Community Edition: GPL
http://www.mysql.com/products/community/

JavaDB: Apache 2.0 License
http://www.oracle.com/technetwork/java/javadb/overview/index.html

BerkeleyDB: 2-clause BSD license 
http://www.oracle.com/technetwork/products/berkeleydb/overview/index-093405.html

So while I wouldn't touch the firm's propietary products, that they are
putting lots of development dollars into plenty of open source projects is
hardly what I'd call "anti-Freedom" or "anti-choice".

FC

-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
- George Orwell