Draft Getting Started with Apache OpenOffice
I have uploaded to the ODFAuthors website the draft chapters for Getting Started with Apache OpenOffice. They need review, especially the Preface and Chapter 11, which have questions (as comments) in the files. http://www.odfauthors.org/apache-openoffice/english/user-guides/getting-started-3.4/drafts I have set the files to be visible to everyone, so you do *not* need to log in to the website in order to download the files. However, should you wish to upload edited files, you will need to have an account and to be logged in. Or you can email edited files directly to me and I'll upload them. You can also send comments and information in an email to one of these lists. These files are a first draft. Some of the illustrations are of poor quality, and I am sure there are all sorts of small (or even large) errors that I have missed in my own review. These files are *not* under the Apache license, nor will they be put under the Apache license. They are under the same licenses as all of the ODFAuthors books: Creative Commons Attribution License, version 3.0 (CC-BY) or General Public License, version 3. --Jean
Re: [RELEASE]: status update and plan
On 4/3/12 7:23 PM, Jürgen Schmidt wrote: On 4/2/12 1:31 PM, Jürgen Schmidt wrote: Hi, I would like to give short update where we are and how I would like to move forward. A detailed QA report was sent by Lily already. Thanks for that Showstopper Issues: - Bug 119098 - check/adapt license header based on RAT output and SGA Work in progress, we have 68 files left that are part of the SGA and we are working on these files. Either we add a license or include them in the exclude list with an appropriate comment. - Bug 119113 - bundled dictionaries are not available when upgrading OOo 3.3 Fix in place that will be tested right now LICENSE/NOTICE We are working on this and we are working to update the existing files for the src releasse. And we create NOTICE/LICENSE snippets that will be added to the src NOTICE/LICENSE file for our binaries. A new issue will be created for this. Plan is to have everything in place until tomorrow. Translation We take the updated translations from Pootle (or from issues) and convert them back into sdf files and integrate them in the svn. Already done for es. External provided po files will be updated on Pootle as well (as already done for Finnish, thanks Risto for the update) This should be also finished tomorrow so that we can start a RC build immediately after everything is in place. I hope we can deliver a nice Easter egg for all of us and especially for our users ;-) ok some more problems came up and should be solved now. Hopefully the RAT output becomes clean with the latest patches. I have updated the languages that are available on Pootle. External received po files are synced in Pootle as well. When the build bot tonight will succeed and my local test build with the languages en-US ar de cs fr es gl it ja zh-CN pt-BR nl hu ru zh-TW fi will succeed as well, we can start a new build tomorrow. Ok when I am able to check in the files, currently svn is not talking with me :-( More info tomorrow ... some problems with the translation (wrong tags etc.) and referenced LICENSE_en-US files... We are working on it and the plan is to start a new build later today. Juergen Anyway this build is intended to become our first RC. But before we start voting we should take a closer look on it. Translation coverage: ar Arabic 95% 1% cs Czech 99% 91% de German 98% 97% es Spanish 100% 100% fi Finnish 100% 97% fr French 100% 100% gl Galician 98% 55% hu Hungarian 100% 98% it Italian 99% 100% ja Japanese 97% 97% nl Dutch 100% 99% pt_BR Portuguese Brazil 100% 97% ru Russian 99% 97% zh_TW Chinese (China) 99% 99% zh-CN Chinese (Taiwan) 98% 98% Juergen
Re: [WWW] new logo in staging only...I think we need a graphic modification
Hi Kevin,
On 04.04.2012 05:55, Kevin Grignon wrote:
Kay et al.
I can help here. I have the skills and the tools.
Beyond getting the right size, I'd like to propose a few other small tweak
to the rendered logo. My proposed enhancements don't change the voted and
approved concept, rather, they merely some polish to the concept as we move
towards production consumption.
See proposed enhancements:
4. Enhancements to Selected Logo Concept (Kevin Grignon - started
2012-04-04)
https://cwiki.apache.org/confluence/display/OOOUSERS/Logo+Proposals
I like the change of Apache to gray but am not so sure about its
capitalization. I understand the reason (after you pointed it out to us
non-artists :) though.
The kerning looks more homogeneous but somewhat dense. For example the
i and c in Office seem to almost touch.
Regards,
Andre
I'll need to access the source files.
Regards,
Kevin
On Wed, Apr 4, 2012 at 7:38 AM, Kay Schenkkay.sch...@gmail.com wrote:
On Tue, Apr 3, 2012 at 4:14 PM, Dave Fisherdave2w...@comcast.net wrote:
On Apr 3, 2012, at 3:59 PM, Kay Schenk wrote:
On 04/03/2012 03:46 PM, drew jensen wrote:
Maybe one of should drop Michael Acevedo a note, see if he already
has a
source file handy - xcf, svg.
If not - I don't know of a svg (or any vector based) file for the bug
part of the image - I know how to recreate one properly from the 256px
png image and would be more then willing to do that, and recreate a
likeness of the orb logo design all vector based and a jpg from that.
I could likely have that here pretty quickly - it would be polite
though
to email Michael first however, I suppose.
so - added him on CC to the mail here
Howdy Michael,
Good instincts on your proposal.. wondering if you have any source
type
fies for the jpg file posted t the wiki?
//drew
OK, maybe I was a bit confusing, and I hope this elaboration helps.
What I think would be ideal is for someone to take the cropped image
I
did that is in svn at--
https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/images/AOO_logos/AOO_orb1_cropped.jpg
this is now 217 x 79
re-size it up to 275 x 100
with clear lettering instead of the blurring that happens
I have just about NO talent with graphics editing at all.
So thanks for any help with this.
We'll need the original vectors. I think the correct size will have the
Orb be about 70px tall and centered vertically with 15px above, below and
left of it.
If the size is exactly 100 you probably don't need to do anything, but
you
might want to edit css/ooo.css
#ooo-logo {
height: 100px;
padding-top: 4px;
padding-left: 8px;
}
a! light dawns -- maybe. The graphic height is actually 79 -- I didn't
tract down the css for any of this --but the rendering kept changing it to
100. It looks better alreger actually but then there's teh blrury text.
OK, I'll play some more but it may have to wait until tomorrow.
You may want to remove the height setting.
To adjust the text banner here is the css in css/ooo.css:
#bannercenter {
padding: 31pt 2pt 14pt 2pt;
float: center;
color: #107EC0;
}
Play with the padding until pleased. I like to do this in Google Chrome.
OK, I'll try again...
Regards,
Dave
I also copied Michael...
On Tue, 2012-04-03 at 15:23 -0700, Kay Schenk wrote:
Folks --
The new logo is rendered on the staging web site right now--
http://ooo-site.staging.apache.org/
It will not go into the production site, www.openoffice.org until
someone does a publish which I have not yet done. I'm not happy
with
the size or positioning of the new logo.
I rendered an alternate version of it -- cropped -- in
http://ooo-site.staging.apache.org/images/AOO_logos/AOO_orb1_cropped.jpg
This actually looks pretty good *except* the image itself is 217 x
79,
and somehow the web site wants to render it at 275 x 100, which
positioning wise is SUPER, but then the lettering is quite blurry.
screen capture of what happened is at:
https://cwiki.apache.org/confluence/display/OOOUSERS/Web+Site+with+Proposed+Logos
So, I would LOVE for some creative person out there to take
http://ooo-site.staging.apache.org/images/AOO_logos/AOO_orb1_cropped.jpg
(cropped version is in svn also)
change it's size to 275 x 100 and make the lettering better.
On the other hand, if you love the staging rendering, I'll go ahead
and
publish it.
--
MzK
Women and cats will do as they please,
and men and dogs should relax and get used to the idea.
-- Robert Heinlein
--
MzK
Women and cats will do as they please,
and men and dogs should relax and get used to the idea.
--
Robert Heinlein
Re: [RELEASE]: status update and plan
On 4/4/12 9:58 AM, Jürgen Schmidt wrote: On 4/3/12 7:23 PM, Jürgen Schmidt wrote: On 4/2/12 1:31 PM, Jürgen Schmidt wrote: Hi, I would like to give short update where we are and how I would like to move forward. A detailed QA report was sent by Lily already. Thanks for that Showstopper Issues: - Bug 119098 - check/adapt license header based on RAT output and SGA Work in progress, we have 68 files left that are part of the SGA and we are working on these files. Either we add a license or include them in the exclude list with an appropriate comment. - Bug 119113 - bundled dictionaries are not available when upgrading OOo 3.3 Fix in place that will be tested right now LICENSE/NOTICE We are working on this and we are working to update the existing files for the src releasse. And we create NOTICE/LICENSE snippets that will be added to the src NOTICE/LICENSE file for our binaries. A new issue will be created for this. Plan is to have everything in place until tomorrow. Translation We take the updated translations from Pootle (or from issues) and convert them back into sdf files and integrate them in the svn. Already done for es. External provided po files will be updated on Pootle as well (as already done for Finnish, thanks Risto for the update) This should be also finished tomorrow so that we can start a RC build immediately after everything is in place. I hope we can deliver a nice Easter egg for all of us and especially for our users ;-) ok some more problems came up and should be solved now. Hopefully the RAT output becomes clean with the latest patches. I have updated the languages that are available on Pootle. External received po files are synced in Pootle as well. When the build bot tonight will succeed and my local test build with the languages en-US ar de cs fr es gl it ja zh-CN pt-BR nl hu ru zh-TW fi will succeed as well, we can start a new build tomorrow. Ok when I am able to check in the files, currently svn is not talking with me :-( More info tomorrow ... some problems with the translation (wrong tags etc.) and referenced LICENSE_en-US files... We are working on it and the plan is to start a new build later today. finding/fixing errors in the translation is very time consuming. Right now I have errors in the Spanish help translation. what I have seen so far mismatched xml tags. Ariel, I am not sure if these the errors you have mentioned earlier. But if you have already a fix for them please let me no. Rebuilding the helpcontent2 module is painful. Juergen Juergen Anyway this build is intended to become our first RC. But before we start voting we should take a closer look on it. Translation coverage: ar Arabic 95% 1% cs Czech 99% 91% de German 98% 97% es Spanish 100% 100% fi Finnish 100% 97% fr French 100% 100% gl Galician 98% 55% hu Hungarian 100% 98% it Italian 99% 100% ja Japanese 97% 97% nl Dutch 100% 99% pt_BR Portuguese Brazil 100% 97% ru Russian 99% 97% zh_TW Chinese (China) 99% 99% zh-CN Chinese (Taiwan) 98% 98% Juergen
Re: [RELEASE]: status update and plan
Hi, it is very important for translation check to include kid pseudolocale to developer builds. This translation is English-toEnglish, but unique generated prefix is in front of every msgstr, that can be used to identify and distinguish usage of msgids. -- wbr, sb 2012/4/4 Jürgen Schmidt jogischm...@googlemail.com: On 4/4/12 9:58 AM, Jürgen Schmidt wrote: On 4/3/12 7:23 PM, Jürgen Schmidt wrote: On 4/2/12 1:31 PM, Jürgen Schmidt wrote: Hi, I would like to give short update where we are and how I would like to move forward. A detailed QA report was sent by Lily already. Thanks for that Showstopper Issues: - Bug 119098 - check/adapt license header based on RAT output and SGA Work in progress, we have 68 files left that are part of the SGA and we are working on these files. Either we add a license or include them in the exclude list with an appropriate comment. - Bug 119113 - bundled dictionaries are not available when upgrading OOo 3.3 Fix in place that will be tested right now LICENSE/NOTICE We are working on this and we are working to update the existing files for the src releasse. And we create NOTICE/LICENSE snippets that will be added to the src NOTICE/LICENSE file for our binaries. A new issue will be created for this. Plan is to have everything in place until tomorrow. Translation We take the updated translations from Pootle (or from issues) and convert them back into sdf files and integrate them in the svn. Already done for es. External provided po files will be updated on Pootle as well (as already done for Finnish, thanks Risto for the update) This should be also finished tomorrow so that we can start a RC build immediately after everything is in place. I hope we can deliver a nice Easter egg for all of us and especially for our users ;-) ok some more problems came up and should be solved now. Hopefully the RAT output becomes clean with the latest patches. I have updated the languages that are available on Pootle. External received po files are synced in Pootle as well. When the build bot tonight will succeed and my local test build with the languages en-US ar de cs fr es gl it ja zh-CN pt-BR nl hu ru zh-TW fi will succeed as well, we can start a new build tomorrow. Ok when I am able to check in the files, currently svn is not talking with me :-( More info tomorrow ... some problems with the translation (wrong tags etc.) and referenced LICENSE_en-US files... We are working on it and the plan is to start a new build later today. finding/fixing errors in the translation is very time consuming. Right now I have errors in the Spanish help translation. what I have seen so far mismatched xml tags. Ariel, I am not sure if these the errors you have mentioned earlier. But if you have already a fix for them please let me no. Rebuilding the helpcontent2 module is painful. Juergen Juergen Anyway this build is intended to become our first RC. But before we start voting we should take a closer look on it. Translation coverage: ar Arabic 95% 1% cs Czech 99% 91% de German 98% 97% es Spanish 100% 100% fi Finnish 100% 97% fr French 100% 100% gl Galician 98% 55% hu Hungarian 100% 98% it Italian 99% 100% ja Japanese 97% 97% nl Dutch 100% 99% pt_BR Portuguese Brazil 100% 97% ru Russian 99% 97% zh_TW Chinese (China) 99% 99% zh-CN Chinese (Taiwan) 98% 98% Juergen
Re: [RELEASE]: status update and plan
Hi Serg, On 04.04.2012 11:31, Serg Bormant wrote: Hi, it is very important for translation check to include kid pseudolocale to developer builds. This translation is English-toEnglish, but unique generated prefix is in front of every msgstr, that can be used to identify and distinguish usage of msgids. The wiki ([1], [2], [3]) describes an alternative: start the office with the environment varianle HELP_DEBUG set to 1, activate extended tool tips (see [3]) and the tooltips will show the help ids. [2] implies that you additionally have to press Shift-F1. Regards, Andre [1] http://wiki.services.openoffice.org/wiki/Help_ID [2] http://wiki.services.openoffice.org/wiki/Environment_Variables#Environment_variables_for_OOo_developers [3] http://wiki.services.openoffice.org/wiki/Extended_Tip_Help
Re: [EXTENSIONS]Alternative for Report Builder?
On 04/04/12 00:14, Juergen Schmidt wrote: On Wednesday, 4. April 2012 at 01:08, drew wrote: On Tue, 2012-04-03 at 17:00 -0300, Ariel Constenla-Haile wrote: On Tue, Apr 03, 2012 at 09:20:58PM +0200, FR web forum wrote: One of the volunteers on the ES forum expressed concern about the Oracle Report Builder (ORB) extension not working on AOO builds: it seems that the extension installs, but reports previously created with it do not run. it is indeed a missing feature but we can't change it for now. But if somebody is interested to build it as an extension and host it somewhere else we will give support here how to do that. Why Oracle did not donate this OXT (and other like PDF Import)? ASF could not contact them to talk about? The code is under the software grant. The issue here is that these extensions rely on GPL libraries, though all related code is now under ALv2: ... * PDF Import: http://svn.apache.org/viewvc/incubator/ooo/trunk/main/sdext/source/pdfimport/ That is, someone has to build them (and maintain them) as external projects. No not really. The problem are the dependent libs as already pointed out. There is no or no easy replacement for this external stuff that is license compatible. Not nice and we would love to have alternatives ... If volunteers will provide an alternative implementation that would be Apache compatible then we will continue the support and include it as bundled extensions. The pdfimport could use pdfbox, however my understanding is that even with a replacement the feature was not really complete without OCR capabilities, (yes tesseract) but well.. it involves real work(TM). The other libraries would be excellent examples of how to do extensions. Hmm... just for reference, I started looking OOo Extensions for Dummies guide on google and I got to this page: http://wiki.services.openoffice.org/wiki/API/Samples It has a link to the contrib dir in the old SVN server. We haven't replicated that in the Apache SVN. Thankfully the files are in ooo-legacy-svn in apache-extras in case we lose the original SVN. Pedro.
Swedish OO
Hello! I don't know where I can ask my question, but I want to try this e-mail adress :-) A week ago I thought install OO. I tried http://www.openoffice.org/sv/ - Download - It didn't work Now I get the file .: OOo_3.3.o_Win_x86_install-wJRE_sv.exe (146MB) It's ok! (but why?) When I tried to use us...@sv.openoffice.org - it doesn't work. All pages from sv.openoffice.org is failed. What is happen with the Swedish version of OO or e-mailing list? When is an upgrade? //Jan Ö
Re: svn commit: r1309306 - /incubator/ooo/ooo-site/trunk/content/fr/Documentation/index.xhtml
Hi - This is not the way to change the website. Here is what you do to effect all of the FR site at once: (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext doctype: /doctype.html brand: /brand.html footer: /footer.html topnav: /topnav.html home: home Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to /fr/topnav.mdtext (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext home: home search: search name: Apache OpenOffice (incubating) tagline:(incubating) | The Free and Open Productivity Suite logo: AOO_logos/AOO_orb1_new.jpg domain: www.openoffice.org divid: bannera Translate the first four parameters. (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext divid: topnava - [Product][m0] - [Download][m1] - [Support][m2] - [Extend][m3] - [Develop][m4] - [Focus Areas][m5] - [Native Language][m6] [m0]: /product/index.html Apache OpenOffice product description [m1]: /download/index.html Download OpenOffice.org [m2]: /support/index.html Find Support for OpenOffice.org [m3]: /extensions/index.html Extensions and Templates for OpenOffice [m4]: http://incubator.apache.org/openofficeorg/get-involved.html Get involved in Apache OpenOffice (incubating) [m5]: /projects/accepted.html Apache OpenOffice development focus areas [m6]: /projects/native-lang.htmlApache OpenOffice in your Native Language Translate and modify as you require. Commit all three changes at once and the whole of the FR part of the site takes these changes at once. O(1) operation. If you would like I'll create the mdtext files and then you can translate. Regards, Dave On Apr 4, 2012, at 2:50 AM, bidoui...@apache.org wrote: Author: bidouille Date: Wed Apr 4 09:50:22 2012 New Revision: 1309306 URL: http://svn.apache.org/viewvc?rev=1309306view=rev Log: (empty) Modified: incubator/ooo/ooo-site/trunk/content/fr/Documentation/index.xhtml Modified: incubator/ooo/ooo-site/trunk/content/fr/Documentation/index.xhtml URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/fr/Documentation/index.xhtml?rev=1309306r1=1309305r2=1309306view=diff == --- incubator/ooo/ooo-site/trunk/content/fr/Documentation/index.xhtml (original) +++ incubator/ooo/ooo-site/trunk/content/fr/Documentation/index.xhtml Wed Apr 4 09:50:22 2012 @@ -5,7 +5,34 @@ link href=/css/ooo.css rel=stylesheet type=text/css / titleindex documentation/title /head - body style=direction: ltr; + body + + div id=bannera +div id=bannerleftimg id=ooo-logo alt=Apache OpenOffice (incubating) src=/images/AOO_logos/AOO_orb1_new.jpg//div +div id=bannerright + a title=Apache Incubator href=http://incubator.apache.org;img id=asf-logo alt=Apache Incubator src=/images/apache-incubator-logo.png//a + div style=relative; margin: 14px 0 0 0; height: 24px; + form id=cse-search-box-header action=http://www.google.com/search; method=get + div + input type=hidden name=domains value=www.openoffice.org/ + input type=hidden name=sitesearch value=www.openoffice.org/ + /div + div class=topsrchbox + input name=resultsPerPage value=40 type=hidden/ + input name=q id=query type=text/ + input name=Button value=search type=submit class=topsrchbutton/ + /div + /form + /div +/div +div id=bannercenterbr/(incubating) | The Free and Open Productivity Suite/div + /div + div id=breadcrumbsaa href=/home/anbsp;raquo;nbsp;a href=/fr/fr/a/div + /div + div id=clear/div + + + div id=content p/p table border=0 style=width: 100%; background-color: #cc; tbody @@ -21,8 +48,8 @@ /td td br / /td - td style=text-align: right;a href=http://www.openoffice.org/fr/assistance_OOo.html; - + td style=text-align: right; +a href=http://www.openoffice.org/fr/assistance_OOo.html; title=Assistance et support sous OpenOfficeBesoin d'aide ?/abr / /td /tr @@ -107,5 +134,29 @@ licence PDL (détail par ce a href=http://www.openoffice.org/licenses/PDL.html;lien/a). Merci à tous les membres de cette communauté francophone pour leur générosité, leur disponibilité et la qualité de leur travail. /p + + + /div + + div id=footera +div id=poweredbyapimg src=/images/feather-small.gif alt=Apache Feather//p/div +div id=copyrighta + p style=text-align:center; + a href=/license.htmlCopyright
Re: [EXTENSIONS]Alternative for Report Builder?
On 4/4/12 9:14 AM, Pedro Giffuni wrote: On 04/04/12 00:14, Juergen Schmidt wrote: On Wednesday, 4. April 2012 at 01:08, drew wrote: On Tue, 2012-04-03 at 17:00 -0300, Ariel Constenla-Haile wrote: On Tue, Apr 03, 2012 at 09:20:58PM +0200, FR web forum wrote: One of the volunteers on the ES forum expressed concern about the Oracle Report Builder (ORB) extension not working on AOO builds: it seems that the extension installs, but reports previously created with it do not run. it is indeed a missing feature but we can't change it for now. But if somebody is interested to build it as an extension and host it somewhere else we will give support here how to do that. Why Oracle did not donate this OXT (and other like PDF Import)? ASF could not contact them to talk about? The code is under the software grant. The issue here is that these extensions rely on GPL libraries, though all related code is now under ALv2: ... * PDF Import: http://svn.apache.org/viewvc/incubator/ooo/trunk/main/sdext/source/pdfimport/ That is, someone has to build them (and maintain them) as external projects. No not really. The problem are the dependent libs as already pointed out. There is no or no easy replacement for this external stuff that is license compatible. Not nice and we would love to have alternatives ... If volunteers will provide an alternative implementation that would be Apache compatible then we will continue the support and include it as bundled extensions. The pdfimport could use pdfbox, however my understanding is that even with a replacement the feature was not really complete without OCR capabilities, (yes tesseract) but well.. it involves real work(TM). The other libraries would be excellent examples of how to do extensions. Hmm... just for reference, I started looking OOo Extensions for Dummies guide on google and I got to this page: http://wiki.services.openoffice.org/wiki/API/Samples It has a link to the contrib dir in the old SVN server. We haven't replicated that in the Apache SVN. Thankfully the files are in ooo-legacy-svn in apache-extras in case we lose the original SVN. so much cleanup work necessary and a lot of room for improvements ;-) Juergen
Looking to get involved
Hi People, not sure if this is the correct place to raise my head, but I have been lurking here for a week or so now with a view to getting involved. Like everyone I am not sure how much time I really have. My background is that of a software developer for some twenty plus years (currently employed by the same institution as Rob, but on the other side of the world, in Australia). I'll skip the resume etc. I figure people are more interested in getting things done. I have been looking around at the get involved links. They are very misleading and take you to places that look like they have not been updated for many years. like ,,, http://codesnippets.services.openoffice.org/index.xml which is from the http://www.openoffice.org/development/ page. I'm sure I saw cobwebs in the corners there. (A review of the potential new developers interface may be needed?) Anyway, I'm sure I will find my way around eventually. All guidance gratefully accepted. I don't understand what if anything someone needs to do to join the gang. Are there any weird initiations, gotta get the new logo tatoo? :-) I am particularly interested in developer testing frameworks (still trying to figure out why). And langauge parsers/compilers. I am also a new Master's student (must have lost my mind somewhere) and wondered if I could combine helping here and also using some of the knowledge gained as part of my thesis. Not sure what the rules are re IP etc. Hope to hear back from someone. Email directly, Don't bother clogging up this mail list. Cheers, Ian
Re: Looking to get involved
On 4/4/12 2:25 PM, Ian wrote: Hi People, not sure if this is the correct place to raise my head, but I have been lurking here for a week or so now with a view to getting involved. Like everyone I am not sure how much time I really have. My background is that of a software developer for some twenty plus years (currently employed by the same institution as Rob, but on the other side of the world, in Australia). I'll skip the resume etc. I figure people are more interested in getting things done. I have been looking around at the get involved links. They are very misleading and take you to places that look like they have not been updated for many years. like ,,, http://codesnippets.services.openoffice.org/index.xml which is from the http://www.openoffice.org/development/ page. I'm sure I saw cobwebs in the corners there. (A review of the potential new developers interface may be needed?) Anyway, I'm sure I will find my way around eventually. All guidance gratefully accepted. I don't understand what if anything someone needs to do to join the gang. Are there any weird initiations, gotta get the new logo tatoo? :-) I am particularly interested in developer testing frameworks (still trying to figure out why). And langauge parsers/compilers. I am also a new Master's student (must have lost my mind somewhere) and wondered if I could combine helping here and also using some of the knowledge gained as part of my thesis. Not sure what the rules are re IP etc. Hope to hear back from someone. Email directly, Don't bother clogging up this mail list. Hi Ian, welcome on board and fun here ;-) Testing frameworks sounds interesting and there is some work ongoing to replace our old test automation tool with something new. A Java based framework to run automated GUI tests etc. We have also some test framework for running unit tests during the build process. We would like to cover more and more stuff by unit test but that is not so easy in such a huge application. Often the context of a running office is required. But anyway there was work ongoing in the past and we should continue it to improve the overall quality and to make it easy detect regressions. I think both areas can benefit from some help. Juergen
Re: Swedish OO
Jan, On 2012-04-04, at 09:39 , Jan Öhman wrote: Hello! I don't know where I can ask my question, but I want to try this e-mail adress :-) Let's see if I can help answering… A week ago I thought install OO. I tried http://www.openoffice.org/sv/ - Download - It didn't work Now I get the file .: OOo_3.3.o_Win_x86_install-wJRE_sv.exe (146MB) It's ok! (but why?) When I tried to use us...@sv.openoffice.org - it doesn't work. All pages from sv.openoffice.org is failed. Yes. As well, I do think that the project members no longer are engaged there. The SV project never had a very strong presence. What is happen with the Swedish version of OO or e-mailing list? As we have been discussing here, there has been evolution regarding the various NL projects. Now is the time to re-form the SV one! :-) This means that we need--and you can be well included--to engage those interested in localization, QA, etc., for SV. Best Louis When is an upgrade? //Jan Ö
Re: How to logging in AOO
Thank you for links, Joost They are useful, if you want to parse the logs. But i need to create the log files and then parse them. I still don't understand how to do it, Drew. 3 апреля 2012 г. 18:38 пользователь Joost Andrae joost.and...@gmx.de написал: Hi, probably these links are of help: http://wiki.services.openoffice.org/wiki/RTLLogFileAnalysis http://www.openoffice.org/tools/profiling/profiling-howto.html http://wiki.services.openoffice.org/wiki/RTLLog2ODF Am 03.04.2012 15:57, schrieb Очиров Николай: Hi Drew Thank you for your help. I do not connect to any database. I just want to log all function calls during startup AOO. I corrected a bit the source code - and AOO falls, cause I can't understand why I want to see the order of function calls, and find which function error. Analyzing the sources I couldn't find a reason, but I noticed that everywhere there are macros in the code - RTL_LOGFILE_TRACE () or RTL_LOGFILE_CONTEXT () and etc. and it seems to me that they can use to track where the error occurs. Is this possible? Kind regards, Joost
OpenOffice UNO API - RDF metadata support
I am trying to understand how to set hierarchical rdf metadata using the UNO API -- From this page -- http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OfficeDev/RDF_metadata I found a link to ODF examples document : http://www.oasis-open.org/committees/download.php/34796/09-10-22-ODF-Metadata-Examples.odt Its clear to me how to input simple subject / predicate / object metadata for a ODF element ... But the problem I have is why is the object in addStatement an XNode .. .why isnt it a XURI ? void addStatement( [in] XResource Subject, [in] XURI Predicate, [in] XNode Object) This seems to limit the kind of metadata i can put in using the UNO API .. for e.g. i have been able to do this : rdf:Description rdf:about=../content.xml#id220335797 ns5:Alpha3/ns5:Alpha ns6:BetaValue of Beta/ns6:Beta /rdf:Description But cant figure out for the life of me how to get something like this ? : rdf:Description rdf:about=../content.xml#id220335797 ns5:Notes ns5:note name=a_namenote val 1/note ns5:note name=b_namenote val 2/note /ns5:Notes /rdf:Description
Re: this is in production now...Re: [WWW] new logo in staging only...I think we need a graphic modification
On Tue, Apr 3, 2012 at 9:18 PM, Dennis E. Hamilton dennis.hamil...@acm.orgwrote: @Kay, The main problem is that JPEG is a lossy format and it is designed for photographic images, not line drawings. So font and sharp-edge fuzziness is always a problem. Furthermore, modification of JPEGs (change of scale, resolution, orientation, etc.,) just accumulates more degradation. PNGs are better, at the resolution of the PNG, but also suffer under modification because of rasterization (they are still bitmaps). Someplace, it is necessary to find a quality vector-graphic version so that lossless PNGs can be produced at whatever resolutions are required; the graphic should be used in anything to be viewed at various resolutions, projected, and also printed, as for publishable documentation, PDFs, etc. There can also be adjusting for features that do not scale proportionally (especially fonts) and that have difficulty when their clean resolution is finer than the target pixel spacing permits. That's usually why even families of vector-graphic forms are desired for different target size ranges. Aside from all of that, I think the Orb1 as now presented is the ideal form, although there could be some tweaking as just noticed on the wiki page by Kevin. I don't agree with the capitalization as APACHE though. The balance on the current form, with Apache seems fine, especially at web-page resolutions and scale. - Dennis Anyone who thinks protocol is unnecessary has never tried to make friends with a cat. - attributed to Lazarus Long Dennis and others -- I'm STILL hoping that the original creator -- Michael Acevedo might be in contact to change both the size (we need somewhat bigger) and format. Again, I am definitely NOT a graphics creator and my skills are quite limited in this regard. -Original Message- From: Kay Schenk [mailto:kay.sch...@gmail.com] Sent: Tuesday, April 03, 2012 20:31 To: ooo-dev@incubator.apache.org Subject: this is in production now...Re: [WWW] new logo in staging only...I think we need a graphic modification [ ... ] well...I did a LOT more futzing kind of to no avail...changed some styles, corrected some erroneous ones, then finally put this into production. It could look better but well, web sites are NEVER set in concrete, and I wanted to get this done before RC 3.4, which seems rather imminent. And I can't speak to my available time over the next day or so. Meanwhile, I will try to document the setup as I know it (which is well, not very good). done for today... [ ... ] -- MzK Women and cats will do as they please, and men and dogs should relax and get used to the idea. -- Robert Heinlein
Re: [EXTENSIONS]Alternative for Report Builder?
Le 03/04/12 22:00, Ariel Constenla-Haile a écrit : Hi All, That is, someone has to build them (and maintain them) as external projects. And that someone will find that, at least insofar as the MySQL connector extension is concerned, it will have to be built for each distrib and bit-type architecture, whereas Sun/Oracle managed to produce an almost generic extension on Linux that worked with most distribs. It also provided builds for Solaris, Mac and Windows. That was one hell of a lot of work... Alex
Re: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/
I see you are making lots of incremental changes and publishing each one individually. Have you considered making better use of the staging site to view the live results of your commits, and iterating on the commits before publishing the final results? From: bidoui...@apache.org bidoui...@apache.org To: ooo-comm...@incubator.apache.org Sent: Wednesday, April 4, 2012 12:34 PM Subject: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/ Author: bidouille Date: Wed Apr 4 16:34:24 2012 New Revision: 811513 Log: Publishing svnmucc operation to ooo-site site by bidouille Added: websites/production/ooo-site/cgi-bin/ - copied from r811512, websites/staging/ooo-site/trunk/cgi-bin/ websites/production/ooo-site/content/ - copied from r811512, websites/staging/ooo-site/trunk/content/
Re: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/
Hi Joe, This person is trying to hack a translation on top of the banner and topnav. They are trying to learn by doing. They just learned how to publish yesterday. I've pointed them at the proper way to engage the SSI setup in a response to r1309306. I hope that they engage. Regards, Dave On Apr 4, 2012, at 9:36 AM, Joe Schaefer wrote: I see you are making lots of incremental changes and publishing each one individually. Have you considered making better use of the staging site to view the live results of your commits, and iterating on the commits before publishing the final results? From: bidoui...@apache.org bidoui...@apache.org To: ooo-comm...@incubator.apache.org Sent: Wednesday, April 4, 2012 12:34 PM Subject: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/ Author: bidouille Date: Wed Apr 4 16:34:24 2012 New Revision: 811513 Log: Publishing svnmucc operation to ooo-site site by bidouille Added: websites/production/ooo-site/cgi-bin/ - copied from r811512, websites/staging/ooo-site/trunk/cgi-bin/ websites/production/ooo-site/content/ - copied from r811512, websites/staging/ooo-site/trunk/content/
Re: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/
I can appreciate that, which is why I'm making a friendly suggestion about their worflow that will induce less overall churn in svn. I certainly didn't expect them to figure this all out by themselves ;-). From: Dave Fisher dave2w...@comcast.net To: ooo-dev@incubator.apache.org Sent: Wednesday, April 4, 2012 12:47 PM Subject: Re: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/ Hi Joe, This person is trying to hack a translation on top of the banner and topnav. They are trying to learn by doing. They just learned how to publish yesterday. I've pointed them at the proper way to engage the SSI setup in a response to r1309306. I hope that they engage. Regards, Dave On Apr 4, 2012, at 9:36 AM, Joe Schaefer wrote: I see you are making lots of incremental changes and publishing each one individually. Have you considered making better use of the staging site to view the live results of your commits, and iterating on the commits before publishing the final results? From: bidoui...@apache.org bidoui...@apache.org To: ooo-comm...@incubator.apache.org Sent: Wednesday, April 4, 2012 12:34 PM Subject: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ content/ Author: bidouille Date: Wed Apr 4 16:34:24 2012 New Revision: 811513 Log: Publishing svnmucc operation to ooo-site site by bidouille Added: websites/production/ooo-site/cgi-bin/ - copied from r811512, websites/staging/ooo-site/trunk/cgi-bin/ websites/production/ooo-site/content/ - copied from r811512, websites/staging/ooo-site/trunk/content/
Re: [EXTENSIONS]Alternative for Report Builder?
On Apr 4, 2012, at 9:14 AM, Alexander Thurgood wrote: Le 03/04/12 22:00, Ariel Constenla-Haile a écrit : Hi All, That is, someone has to build them (and maintain them) as external projects. And that someone will find that, at least insofar as the MySQL connector extension is concerned, it will have to be built for each distrib and bit-type architecture, whereas Sun/Oracle managed to produce an almost generic extension on Linux that worked with most distribs. It also provided builds for Solaris, Mac and Windows. That was one hell of a lot of work... In the discussion of CloudStack on general@i.a.o where there is significant GPL changes that need to occur, the Apache APR was suggested as an alternative with a pointer to http://svn.apache.org/repos/asf/apr/apr/trunk/README Multiple SQL DBD client interfaces Multiple flat-database DBM client interfaces Perhaps this will help. Regards, Dave Alex
Re: Looking to get involved
On Wed, Apr 4, 2012 at 8:25 AM, Ian i...@amham.net wrote: Hi People, not sure if this is the correct place to raise my head, but I have been lurking here for a week or so now with a view to getting involved. Like everyone I am not sure how much time I really have. Hi Ian, Welcome to the project. Although ooo-dev might sound like it is only for developers, it actually is the project's main list. So you are in the right place. We have some subsidiary lists as well: http://incubator.apache.org/openofficeorg/mailing-lists.html My background is that of a software developer for some twenty plus years (currently employed by the same institution as Rob, but on the other side of the world, in Australia). I'll skip the resume etc. I figure people are more interested in getting things done. I have been looking around at the get involved links. They are very misleading and take you to places that look like they have not been updated for many years. like ,,, http://codesnippets.services.openoffice.org/index.xml which is from the http://www.openoffice.org/development/ page. I'm sure I saw cobwebs in the corners there. (A review of the potential new developers interface may be needed?) Anyway, I'm sure I will find my way around eventually. All guidance gratefully accepted. Hmmm This should be our main get involved page: http://incubator.apache.org/openofficeorg/get-involved.html But it sounds like there are paths that lead visitors elsewhere. We need to fix that. I don't understand what if anything someone needs to do to join the gang. Are there any weird initiations, gotta get the new logo tatoo? :-) If you contact me via Notes, I can fill you in on the internal IBM requirements (Open Source Participation Guidelines). Also, take a tool at the Apache roles and the way the meritocracy works: http://www.apache.org/foundation/how-it-works.html#roles No paperwork is needed for contributers. There is an iCLA form that you can sign and return. Even though it is only required for Committers, anyone who thinks they will be active in the project is encouraged to complete that paperwork. I am particularly interested in developer testing frameworks (still trying to figure out why). And langauge parsers/compilers. I am also a new Master's student (must have lost my mind somewhere) and wondered if I could combine helping here and also using some of the knowledge gained as part of my thesis. Not sure what the rules are re IP etc. There are some interesting things that could have research interest as well as helping the project. For example, consider testing document layout. We can automate document creation, and specify the styles and content of a document, but verifying whether it appears correctly is a manual task. At the simplest level we might want to check to see whether today's build renders documents the same they were rendered in the last release. So we want to detect regressions. At a more complex level we might want to verify correctness of the rendering, as defined by some specification. Having high quality rendering in this area is of critical importance to users, but today is a manual task. Now you could imagine just doing screen shots and doing pixel level comparisons. That is easy to implement but will be overly-sensitive and give many false positives. Slight UI changes, platform differences, etc. can introduce insignificant changes. Some of augmented this approach by looking at the percentage difference in the before and after images. Another approach might be based on OCR technology to deconstruct the rendered document to determine facts such as size of margin, number of lines of text, alignment, size of headers, etc. These facts could then be compared to a test specification. This approach might be easier if the document is first rendered to a PDF file rather than using a screenshot. And another approach could be to rely on human judgment on sameness or correctness of the rendered pages, but devise some way to crowd-source these comparisons. For example, we could have a web-service that would show the before and after images, a different one each time, and ask users to mark them as same/different/not sure. Or give the specification for what it should look like and ask viewer to score them. An example of that technique can be seen at Galaxy Zoo where astronomers use crowd sourcing to classify galaxies: http://www.galaxyzoo.org/classify So there may be something here that could make a tremendous contribution to the project as well as be suitable as a thesis project. Hope to hear back from someone. Email directly, Don't bother clogging up this mail list. I hope these answers may be of more general interest, so I'm sending them to ooo-dev as well. Regards, -Rob Cheers, Ian
Re: [RELEASE]: status update and plan
On 4/4/12 11:10 AM, Jürgen Schmidt wrote: On 4/4/12 9:58 AM, Jürgen Schmidt wrote: On 4/3/12 7:23 PM, Jürgen Schmidt wrote: On 4/2/12 1:31 PM, Jürgen Schmidt wrote: Hi, I would like to give short update where we are and how I would like to move forward. A detailed QA report was sent by Lily already. Thanks for that Showstopper Issues: - Bug 119098 - check/adapt license header based on RAT output and SGA Work in progress, we have 68 files left that are part of the SGA and we are working on these files. Either we add a license or include them in the exclude list with an appropriate comment. - Bug 119113 - bundled dictionaries are not available when upgrading OOo 3.3 Fix in place that will be tested right now LICENSE/NOTICE We are working on this and we are working to update the existing files for the src releasse. And we create NOTICE/LICENSE snippets that will be added to the src NOTICE/LICENSE file for our binaries. A new issue will be created for this. Plan is to have everything in place until tomorrow. Translation We take the updated translations from Pootle (or from issues) and convert them back into sdf files and integrate them in the svn. Already done for es. External provided po files will be updated on Pootle as well (as already done for Finnish, thanks Risto for the update) This should be also finished tomorrow so that we can start a RC build immediately after everything is in place. I hope we can deliver a nice Easter egg for all of us and especially for our users ;-) ok some more problems came up and should be solved now. Hopefully the RAT output becomes clean with the latest patches. I have updated the languages that are available on Pootle. External received po files are synced in Pootle as well. When the build bot tonight will succeed and my local test build with the languages en-US ar de cs fr es gl it ja zh-CN pt-BR nl hu ru zh-TW fi will succeed as well, we can start a new build tomorrow. Ok when I am able to check in the files, currently svn is not talking with me :-( More info tomorrow ... some problems with the translation (wrong tags etc.) and referenced LICENSE_en-US files... We are working on it and the plan is to start a new build later today. finding/fixing errors in the translation is very time consuming. Right now I have errors in the Spanish help translation. what I have seen so far mismatched xml tags. Ariel, I am not sure if these the errors you have mentioned earlier. But if you have already a fix for them please let me no. Rebuilding the helpcontent2 module is painful. I have found errors so far in es, fr, it, gl. Always mismatched xml tags :-( The problem is that the build system does very strange things when building helpcontent2 and it takes a lot of time to verify changes. The good things is that during the waiting times I have prepared some scripts to update the Pootle server with further languages. I will continue this Pootle update with all languages we have so far. This should give us a good overview where we are with the translations. And hopefully further people will start/continue to work on this. As soon as I have verified the updated languages we can start the proposed build. I think the translations are the only missing pieces now and we have fixed all critical issues. I am tired and hungry now and will go home but will continue the verification later. Juergen
Re: [RELEASE]: status update and plan
On Tue, Apr 3, 2012 at 1:23 PM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 4/2/12 1:31 PM, Jürgen Schmidt wrote: Hi, I would like to give short update where we are and how I would like to move forward. A detailed QA report was sent by Lily already. Thanks for that Showstopper Issues: - Bug 119098 - check/adapt license header based on RAT output and SGA Work in progress, we have 68 files left that are part of the SGA and we are working on these files. Either we add a license or include them in the exclude list with an appropriate comment. - Bug 119113 - bundled dictionaries are not available when upgrading OOo 3.3 Fix in place that will be tested right now LICENSE/NOTICE We are working on this and we are working to update the existing files for the src releasse. And we create NOTICE/LICENSE snippets that will be added to the src NOTICE/LICENSE file for our binaries. A new issue will be created for this. Plan is to have everything in place until tomorrow. Translation We take the updated translations from Pootle (or from issues) and convert them back into sdf files and integrate them in the svn. Already done for es. External provided po files will be updated on Pootle as well (as already done for Finnish, thanks Risto for the update) This should be also finished tomorrow so that we can start a RC build immediately after everything is in place. I hope we can deliver a nice Easter egg for all of us and especially for our users ;-) ok some more problems came up and should be solved now. Hopefully the RAT output becomes clean with the latest patches. I have updated the languages that are available on Pootle. External received po files are synced in Pootle as well. When the build bot tonight will succeed and my local test build with the languages en-US ar de cs fr es gl it ja zh-CN pt-BR nl hu ru zh-TW fi will succeed as well, we can start a new build tomorrow. Ok when I am able to check in the files, currently svn is not talking with me :-( More info tomorrow ... Anyway this build is intended to become our first RC. But before we start voting we should take a closer look on it. Translation coverage: ar Arabic 95% 1% cs Czech 99% 91% de German 98% 97% es Spanish 100%100% fi Finnish 100%97% fr French 100%100% gl Galician98% 55% hu Hungarian 100%98% it Italian 99% 100% ja Japanese97% 97% nl Dutch 100%99% pt_BR Portuguese Brazil 100%97% ru Russian 99% 97% zh_TW Chinese (China) 99% 99% zh-CN Chinese (Taiwan)98% 98% If we look at visitor's to the www.openoffice.org website and the languages they specify in the browser,the distribution is like: en_us 50% de 12% en_gb 4% ru 4% fr 2% es 2% it 2% ja 2% pl 2% zh_tw 2% pr_br 1% nl 1% sv 1% da 1% zh_cn 1% tr 1% So it looks like we have the major languages covered well. Except British English? Do we have a separate translation there? Or at least a separate spell checking dictionary? -Rob Juergen
[TRANSLATION] Issue 119182 for Finnish Help package
Here come Finnish Help translations. At least I hope so (-; https://issues.apache.org/ooo/show_bug.cgi?id=119182 Because size is too big (2.5MB) it is linked. This is direct link: http://www.saunalahti.fi/rjaaskel/1/Menu/OOo/Help_source_fi.zip Regards Risto
Re: [RELEASE]: status update and plan
On 4/4/12 7:56 PM, Rob Weir wrote: On Tue, Apr 3, 2012 at 1:23 PM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 4/2/12 1:31 PM, Jürgen Schmidt wrote: Hi, I would like to give short update where we are and how I would like to move forward. A detailed QA report was sent by Lily already. Thanks for that Showstopper Issues: - Bug 119098 - check/adapt license header based on RAT output and SGA Work in progress, we have 68 files left that are part of the SGA and we are working on these files. Either we add a license or include them in the exclude list with an appropriate comment. - Bug 119113 - bundled dictionaries are not available when upgrading OOo 3.3 Fix in place that will be tested right now LICENSE/NOTICE We are working on this and we are working to update the existing files for the src releasse. And we create NOTICE/LICENSE snippets that will be added to the src NOTICE/LICENSE file for our binaries. A new issue will be created for this. Plan is to have everything in place until tomorrow. Translation We take the updated translations from Pootle (or from issues) and convert them back into sdf files and integrate them in the svn. Already done for es. External provided po files will be updated on Pootle as well (as already done for Finnish, thanks Risto for the update) This should be also finished tomorrow so that we can start a RC build immediately after everything is in place. I hope we can deliver a nice Easter egg for all of us and especially for our users ;-) ok some more problems came up and should be solved now. Hopefully the RAT output becomes clean with the latest patches. I have updated the languages that are available on Pootle. External received po files are synced in Pootle as well. When the build bot tonight will succeed and my local test build with the languages en-US ar de cs fr es gl it ja zh-CN pt-BR nl hu ru zh-TW fi will succeed as well, we can start a new build tomorrow. Ok when I am able to check in the files, currently svn is not talking with me :-( More info tomorrow ... Anyway this build is intended to become our first RC. But before we start voting we should take a closer look on it. Translation coverage: ar Arabic 95% 1% cs Czech 99% 91% de German 98% 97% es Spanish 100%100% fi Finnish 100%97% fr French 100%100% gl Galician98% 55% hu Hungarian 100%98% it Italian 99% 100% ja Japanese97% 97% nl Dutch 100%99% pt_BR Portuguese Brazil 100%97% ru Russian 99% 97% zh_TW Chinese (China) 99% 99% zh-CN Chinese (Taiwan)98% 98% If we look at visitor's to the www.openoffice.org website and the languages they specify in the browser,the distribution is like: en_us 50% de 12% en_gb 4% ru 4% fr 2% es 2% it 2% ja 2% pl 2% zh_tw 2% pr_br 1% nl 1% sv 1% da 1% zh_cn 1% tr 1% So it looks like we have the major languages covered well. Except British English? Do we have a separate translation there? Or at least a separate spell checking dictionary? I have updated en_GB on Pootle and can include it as well. The coverage looks not bad but I haven't checked the numbers There is no dictionary available as far as I know. Juergen -Rob Juergen
Re: [RELEASE]: status update and plan
gl Galician 98% 55% I am doing suggestions to UI in Pootle for achieve the 100% Can somebody aprobe it? I have alreadey sent my ICLA but I don't know as demand access to manage galician translation in Pootle. -- Antón Méixome - Galician Native Lang Coordination Blog about Galician Office Suite Galician community OOo.org LibO http://blog.openoffice.gl
Re: [EXTENSIONS]Alternative for Report Builder?
On 04/04/12 11:14, Alexander Thurgood wrote: Le 03/04/12 22:00, Ariel Constenla-Haile a écrit : Hi All, That is, someone has to build them (and maintain them) as external projects. And that someone will find that, at least insofar as the MySQL connector extension is concerned, it will have to be built for each distrib and bit-type architecture, whereas Sun/Oracle managed to produce an almost generic extension on Linux that worked with most distribs. It also provided builds for Solaris, Mac and Windows. That was one hell of a lot of work... Well... if someone rolls out the sources, for Mac, Windows and probably even Solaris we have volunteers. The linux issue happens with almost any type of software so ultimately If the extensions are worth it, the linux distributions will do it (and I would do it for my system too), the rest will have learn to roll their own, but that's the beauty of opensource. Pedro.
Re: buildbot failure in ASF Buildbot on aoo-win7
On 4/2/2012 2:07 AM, Oliver-Rainer Wittmann wrote: Hi On 02.04.2012 06:38, build...@apache.org wrote: The Buildbot has finished a build on builder aoo-win7 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/aoo-win7/builds/115 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-win7 Build Reason: The Nightly scheduler named 'aoo-win7' triggered this build Build Source Stamp: [branch incubator/ooo/trunk] HEAD Blamelist: BUILD FAILED: failed shell_4 sincerely, -The Buildbot The build broke in module sal, because file 'convertiscii.tab' could not be found. This file has been removed a couple of days ago by hdu - 2012-03-28, rev. 1306246. Thus, a clean build is needed to get the dependencies up to date. There have been 2 clean builds (one was last night's build) since the sal issue first occurred. The problem remains - something else is wrong. This would be good to sort out. Can someone please trigger a clean build for our Windows buildbot? done twice. Thx in advance. BTW, as our build system is quite complex and not complete regarding its dependencies I propose to always perform a clean build on our buildbots. I am not so sure that the build system is all that complex. There are three main moving parts here: * The buildbot infrastructure. This is perhaps the most complex part, but is mostly handled by Apache Infra (thanks Gavin) * The 'machine recipe' which can be seen in the JIRAs setting up the buildbots - base OS + packages/requirements. Not rocket science, and very repeatable. * The 'build recipe' which is in the openoffice config for the buildbots. These break down into get source (svn co), run build, upload results. The syntax in the bb config is a bit cryptic, but you can figure it out pretty quick, at which point, there's nothing to exotic going on. We have a combination of clean builds (svn clobber) and incremental builds going on. The clobbered builds just take a long time. I'm not sure that we are really at a point where we need to do a clean build for every platform, for every build. It just sucks up bandwidth and resources, and takes longer. All of this is of course covered by a healthy dose of IMHO. Andrew Best regards, Oliver.
Re: buildbot failure in ASF Buildbot on aoo-win7
Hi, On 04.04.2012 20:58, Andrew Rist wrote: On 4/2/2012 2:07 AM, Oliver-Rainer Wittmann wrote: Hi On 02.04.2012 06:38, build...@apache.org wrote: The Buildbot has finished a build on builder aoo-win7 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/aoo-win7/builds/115 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-win7 Build Reason: The Nightly scheduler named 'aoo-win7' triggered this build Build Source Stamp: [branch incubator/ooo/trunk] HEAD Blamelist: BUILD FAILED: failed shell_4 sincerely, -The Buildbot The build broke in module sal, because file 'convertiscii.tab' could not be found. This file has been removed a couple of days ago by hdu - 2012-03-28, rev. 1306246. Thus, a clean build is needed to get the dependencies up to date. There have been 2 clean builds (one was last night's build) since the sal issue first occurred. The problem remains - something else is wrong. This would be good to sort out. Can someone please trigger a clean build for our Windows buildbot? done twice. The bad thing is that in the meantime another build breaker has been introduced. Thus, the clean build breaks again :-( Thx in advance. BTW, as our build system is quite complex and not complete regarding its dependencies I propose to always perform a clean build on our buildbots. I am not so sure that the build system is all that complex. There are three main moving parts here: * The buildbot infrastructure. This is perhaps the most complex part, but is mostly handled by Apache Infra (thanks Gavin) * The 'machine recipe' which can be seen in the JIRAs setting up the buildbots - base OS + packages/requirements. Not rocket science, and very repeatable. * The 'build recipe' which is in the openoffice config for the buildbots. These break down into get source (svn co), run build, upload results. The syntax in the bb config is a bit cryptic, but you can figure it out pretty quick, at which point, there's nothing to exotic going on. We have a combination of clean builds (svn clobber) and incremental builds going on. The clobbered builds just take a long time. I'm not sure that we are really at a point where we need to do a clean build for every platform, for every build. It just sucks up bandwidth and resources, and takes longer. All of this is of course covered by a healthy dose of IMHO. Oh, I did meant the build system of the build bot. I meant the Apache OpenOffice build system. E.g., if there is an incompatible change in module X, then a depending module Y is typically not build when doing an incremental build. For me, the build bots are the first step to something like continuous integration. Thus, from my point of view we can continue with incremental builds, but we should act asap, if a build bot does not succeed. I would like to help here, if possible. I would like to trigger a clean build as soon as possible, because it is needed due to the changes which have been made or to trigger another build as soon as possible after a fix for the build breaker has been made. Is there an interface which I could use to trigger such builds? Best regards, Oliver.
Re: [RELEASE]: status update and plan
On 04/04/2012 Jürgen Schmidt wrote: On 4/4/12 7:56 PM, Rob Weir wrote: So it looks like we have the major languages covered well. Except British English? Do we have a separate translation there? Or at least a separate spell checking dictionary? I have updated en_GB on Pootle and can include it as well. The coverage looks not bad but I haven't checked the numbers There is no dictionary available as far as I know. Note that, for some obscure limitation, a popular choice for people who installed a non-English version and needed to use the English interface from time to time was to install the en-GB langpack on the non-English version, since en-US was not available as langpack. I don't know whether there is an en-GB dictionary available, but it's probably worth having a look at some old (3.4-beta, or 3.3) en-GB langpack. Regards, Andrea.
DicOOo Wizard ?? (+en_GB dictionary) (was Re: [RELEASE]: status update and plan)
On 04/04/12 14:37, Andrea Pescetti wrote: On 04/04/2012 Jürgen Schmidt wrote: On 4/4/12 7:56 PM, Rob Weir wrote: So it looks like we have the major languages covered well. Except British English? Do we have a separate translation there? Or at least a separate spell checking dictionary? I have updated en_GB on Pootle and can include it as well. The coverage looks not bad but I haven't checked the numbers There is no dictionary available as far as I know. Note that, for some obscure limitation, a popular choice for people who installed a non-English version and needed to use the English interface from time to time was to install the en-GB langpack on the non-English version, since en-US was not available as langpack. I don't know whether there is an en-GB dictionary available, but it's probably worth having a look at some old (3.4-beta, or 3.3) en-GB langpack. Found it: http://en-gb.pyxidium.co.uk/dictionary/en_GB.zip (According to Bugzilla 4168 it is GPL'd) There are more dictionaries here: http://wiki.services.openoffice.org/wiki/Dictionaries Hmm.. according to that page there was once a DicOOo wizard! Anyone knows anything about it? Sounds like something we may want to resurrect. cheers, Pedro.
Re: [RELEASE] 3.4 status at Apr
2012/4/1 Torokhov Sergey torokhov_...@mail.ru On Sunday 01 of April 2012 10:05:51 Shenfeng Liu wrote: Hi, all, I updated the 3.4 status at project wiki: https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Reporting Per my reading from our mails, I listed the following issues: 1. RAT - did we complete this work? 2. Buid signing - I didn't find any following up. Did we have a solution? 3. QE - as Lily suggested, should we plan a regression test BEFORE announce RC1? 4. One more show stopper candidate - 119156 5. Dictionary extension - ? Please give any comments. Thanks! - Simon as for 3rd item I found one regression with import of table's borders in Writer yesterday that takes place in AOO 3.4.0 r1303653 (https://issues.apache.org/ooo/show_bug.cgi?id=119161) So imho it's worth to make some regression tests. Yes, Torokhov, that's why I want to ahead RC build test plan ahead of RC build announce. Recently still some IP cleanup things occurds against code base so may regression will be introduced. Lily -- Regards I check that this bug came from Oracle OpenOffice.org 3.4 beta (could anybody at least confirm this bug? ), so some regressions were arived from previous development Ooo-3.4beta branch too. I hope final AOO 3.4 will be released till summer :) -- Regards
Re: DicOOo Wizard ?? (+en_GB dictionary) (was Re: [RELEASE]: status update and plan)
Pedro Giffuni wrote: There are more dictionaries here: http://wiki.services.openoffice.org/wiki/Dictionaries Hmm.. according to that page there was once a DicOOo wizard! Anyone knows anything about it? Sounds like something we may want to resurrect. No, thanks! DicOOo was a huge ODT document with macros and internal links that got the job done in the early OOo days and achieved remarkable results, but that was superseded by the Extensions. It was an interface to download dictionaries, the Italian website still has a totally outdated HOWTO: http://www.openoffice.org/it/linguistico/dicooo.html Extensions are the right way to handle dictionaries, and if there are dictionaries on http://wiki.services.openoffice.org/wiki/Dictionaries that are not listed on http://extensions.services.openoffice.org/dictionary it would be better to package them into Extensions. Regards, Andrea.
Re: DicOOo Wizard ?? (+en_GB dictionary) (was Re: [RELEASE]: status update and plan)
http://wiki.services.openoffice.org/wiki/Dictionaries Hmm.. according to that page there was once a DicOOo wizard! Anyone knows anything about it? Sounds like something we may want to resurrect. Well, this was a text document with a macro. It made the user select a language and it would download it and then put the files in the correct folder IIRC. User had to activate macros in the security options to be able to run it. It didn't sound very professional and extensions for dictionaries are much better IMHO. Not sure it could be used to remove a dictionary however. Hagar
[WWW] Tutorial to put online
Bonjour, Actually, I refresh our french website pages. I would like to add some new tutorials for our users. But I don't know how can I upload it. Should I use an FTP or another way? Thank you for help
Re: [WWW] Tutorial to put online
Hi - What type of file are you wanting to upload and where do you want to put it in the tree? Also, both Joe and I have been watching the commits and have some advice. Joe's advice is to look at http://ooo-site.staging.apache.org/fr/ to avoid publishing too often. Mine regards the way you are using index.xhtml to bypass index.html to translate the navigation. You are working against the site design. Here is what you would do to effect all of the FR site at once for translated branding and navigation buttons: (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext doctype: /doctype.html brand: /brand.html footer: /footer.html topnav: /topnav.html home: home Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to /fr/topnav.mdtext (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext home: home search: search name: Apache OpenOffice (incubating) tagline:(incubating) | The Free and Open Productivity Suite logo: AOO_logos/AOO_orb1_new.jpg domain: www.openoffice.org divid: bannera Translate the first four parameters. (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext divid: topnava - [Product][m0] - [Download][m1] - [Support][m2] - [Extend][m3] - [Develop][m4] - [Focus Areas][m5] - [Native Language][m6] [m0]: /product/index.html Apache OpenOffice product description [m1]: /download/index.html Download OpenOffice.org [m2]: /support/index.html Find Support for OpenOffice.org [m3]: /extensions/index.html Extensions and Templates for OpenOffice [m4]: http://incubator.apache.org/openofficeorg/get-involved.html Get involved in Apache OpenOffice (incubating) [m5]: /projects/accepted.html Apache OpenOffice development focus areas [m6]: /projects/native-lang.htmlApache OpenOffice in your Native Language Translate and modify as you require. Commit all three changes at once and the whole of the FR part of the site takes these changes at once. O(1) operation. If you would like I'll create the mdtext files and then you can translate. On Apr 4, 2012, at 1:58 PM, FR web forum wrote: Bonjour, Actually, I refresh our french website pages. I would like to add some new tutorials for our users. But I don't know how can I upload it. Should I use an FTP or another way? Thank you for help
Re: [EXTENSIONS]Alternative for Report Builder?
FWIW, --- Mer 4/4/12, Dave Fisher dave2w...@comcast.net ha scritto: ... In the discussion of CloudStack on general@i.a.o where there is significant GPL changes that need to occur, the Apache APR was suggested as an alternative with a pointer to http://svn.apache.org/repos/asf/apr/apr/trunk/README Multiple SQL DBD client interfaces Multiple flat-database DBM client interfaces APR has some optional wrappers but they are not included by default because they depend on copyleft stuff. Maybe this could help as a BerkeleyDB replacement: http://code.google.com/p/babudb/ (I found it only after we had replaced BDB on OpenOffice). cheers, Pedro.
[WIKI] Support for multilingual wiki in MediaWiki
Hi I did a test page[1], based in two templates[2][3]. [1]http://wiki.services.openoffice.org/wiki/Main_Test [2]http://wiki.services.openoffice.org/wiki/Template:OrigLang [3]http://wiki.services.openoffice.org/wiki/Template:Lang With some adjusts in CSS and the support of infra team (thanks guys!), is finished. Now, we can start the production of main pages (en) and its translations. But before to continue, i see two points to treat: what is usable and the license. I think that have lots of pages outdated and without value (at this time), so we could filter what is interesting or not. And about the license, have PDL and CC there (and i have doubts if haven't more some thing). What i think is that need to converge for a common license. I read one or two hundred of emails, and really not found a decision or consensus. Is my mistake or are this the facts? Best, Claudio ps: Jürgen, now i understood your comment about the use of cwiki/mediawiki and the problem to treat.
Re: And idea for OOo
On Tue, Apr 3, 2012 at 11:24 AM, Dave Fisher dave2w...@comcast.net wrote: On Apr 3, 2012, at 6:20 AM, RGB ES wrote: El día 3 de abril de 2012 15:03, Wolf Halton wolf.hal...@gmail.com escribió: On Fri, Mar 30, 2012 at 9:01 AM, Cody Miller codymiller1...@live.com wrote: Hello, I have a really great idea for the OpenOffice Community. Almost every Office Suite has its own storage house (cloud drive) nowadays, and I was thinking that OOo should have its own too. But I was also thinking that not only could you retrieve your documents, but even edit them while your in the storage as well. That way, you could take and edit your documents wherever you are. This would be a huge step for the OOo community, and it may increase our popularity if accomplished. And if the popularity increase, that will mean more developers where be really to help worldwide. Please take my idea into consideration. Thanks, Cmiller Hi Cody, I like the idea of web-based open-office editing and of cloud storage for openoffice. Rob had a good point that there are hard costs involved with web-based clouds of our own, but there is no reason that we cannot do a feasibility study of the idea. Knowing the cost is more powerful than merely knowing there is a cost. (IMHO) Wolf -- This Apt Has Super Cow Powers - http://sourcefreedom.com Advancing Libraries Together - http://LYRASIS.org There is an open source project called OwnCloud aimed to provide cloud services: http://owncloud.org/ No idea how it works, though: I just read about it on planetKDE... The following was just announced: http://www.citrix.com/English/NE/news/news.asp?newsID=2323072ntref=hp_promo_apache Citrix project - Apache Incubator! Regards, Dave Ricardo This is interesting news! I read a short piece about them changing the license of their opensource cloud, but this is good news for the feasibility of an openoffice extension to our own cloud. -Wolf -- This Apt Has Super Cow Powers - http://sourcefreedom.com Advancing Libraries Together - http://LYRASIS.org
Re: Looking to get involved
Thanks for the great reply Rob, sent you a Note. On Thu, Apr 5, 2012 at 1:07 AM, Rob Weir robw...@apache.org wrote: On Wed, Apr 4, 2012 at 8:25 AM, Ian i...@amham.net wrote: Hi People, not sure if this is the correct place to raise my head, but I have been lurking here for a week or so now with a view to getting involved. Like everyone I am not sure how much time I really have. Hi Ian, Welcome to the project. Although ooo-dev might sound like it is only for developers, it actually is the project's main list. So you are in the right place. We have some subsidiary lists as well: http://incubator.apache.org/openofficeorg/mailing-lists.html My background is that of a software developer for some twenty plus years (currently employed by the same institution as Rob, but on the other side of the world, in Australia). I'll skip the resume etc. I figure people are more interested in getting things done. I have been looking around at the get involved links. They are very misleading and take you to places that look like they have not been updated for many years. like ,,, http://codesnippets.services.openoffice.org/index.xml which is from the http://www.openoffice.org/development/ page. I'm sure I saw cobwebs in the corners there. (A review of the potential new developers interface may be needed?) Anyway, I'm sure I will find my way around eventually. All guidance gratefully accepted. Hmmm This should be our main get involved page: http://incubator.apache.org/openofficeorg/get-involved.html But it sounds like there are paths that lead visitors elsewhere. We need to fix that. I don't understand what if anything someone needs to do to join the gang. Are there any weird initiations, gotta get the new logo tatoo? :-) If you contact me via Notes, I can fill you in on the internal IBM requirements (Open Source Participation Guidelines). Also, take a tool at the Apache roles and the way the meritocracy works: http://www.apache.org/foundation/how-it-works.html#roles No paperwork is needed for contributers. There is an iCLA form that you can sign and return. Even though it is only required for Committers, anyone who thinks they will be active in the project is encouraged to complete that paperwork. I am particularly interested in developer testing frameworks (still trying to figure out why). And langauge parsers/compilers. I am also a new Master's student (must have lost my mind somewhere) and wondered if I could combine helping here and also using some of the knowledge gained as part of my thesis. Not sure what the rules are re IP etc. There are some interesting things that could have research interest as well as helping the project. For example, consider testing document layout. We can automate document creation, and specify the styles and content of a document, but verifying whether it appears correctly is a manual task. At the simplest level we might want to check to see whether today's build renders documents the same they were rendered in the last release. So we want to detect regressions. At a more complex level we might want to verify correctness of the rendering, as defined by some specification. Having high quality rendering in this area is of critical importance to users, but today is a manual task. Now you could imagine just doing screen shots and doing pixel level comparisons. That is easy to implement but will be overly-sensitive and give many false positives. Slight UI changes, platform differences, etc. can introduce insignificant changes. Some of augmented this approach by looking at the percentage difference in the before and after images. Another approach might be based on OCR technology to deconstruct the rendered document to determine facts such as size of margin, number of lines of text, alignment, size of headers, etc. These facts could then be compared to a test specification. This approach might be easier if the document is first rendered to a PDF file rather than using a screenshot. And another approach could be to rely on human judgment on sameness or correctness of the rendered pages, but devise some way to crowd-source these comparisons. For example, we could have a web-service that would show the before and after images, a different one each time, and ask users to mark them as same/different/not sure. Or give the specification for what it should look like and ask viewer to score them. An example of that technique can be seen at Galaxy Zoo where astronomers use crowd sourcing to classify galaxies: http://www.galaxyzoo.org/classify So there may be something here that could make a tremendous contribution to the project as well as be suitable as a thesis project. Hope to hear back from someone. Email directly, Don't bother clogging up this mail list. I hope these answers may be of more general interest, so I'm sending
Re: Looking to get involved
Thanks Jurgen, looking forward to clearing the fog and getting involved. Ian. 2012/4/4 Jürgen Schmidt jogischm...@googlemail.com On 4/4/12 2:25 PM, Ian wrote: Hi People, not sure if this is the correct place to raise my head, but I have been lurking here for a week or so now with a view to getting involved. Like everyone I am not sure how much time I really have. My background is that of a software developer for some twenty plus years (currently employed by the same institution as Rob, but on the other side of the world, in Australia). I'll skip the resume etc. I figure people are more interested in getting things done. I have been looking around at the get involved links. They are very misleading and take you to places that look like they have not been updated for many years. like ,,, http://codesnippets.services.**openoffice.org/index.xmlhttp://codesnippets.services.openoffice.org/index.xmlwhich is from the http://www.openoffice.org/**development/http://www.openoffice.org/development/page. I'm sure I saw cobwebs in the corners there. (A review of the potential new developers interface may be needed?) Anyway, I'm sure I will find my way around eventually. All guidance gratefully accepted. I don't understand what if anything someone needs to do to join the gang. Are there any weird initiations, gotta get the new logo tatoo? :-) I am particularly interested in developer testing frameworks (still trying to figure out why). And langauge parsers/compilers. I am also a new Master's student (must have lost my mind somewhere) and wondered if I could combine helping here and also using some of the knowledge gained as part of my thesis. Not sure what the rules are re IP etc. Hope to hear back from someone. Email directly, Don't bother clogging up this mail list. Hi Ian, welcome on board and fun here ;-) Testing frameworks sounds interesting and there is some work ongoing to replace our old test automation tool with something new. A Java based framework to run automated GUI tests etc. We have also some test framework for running unit tests during the build process. We would like to cover more and more stuff by unit test but that is not so easy in such a huge application. Often the context of a running office is required. But anyway there was work ongoing in the past and we should continue it to improve the overall quality and to make it easy detect regressions. I think both areas can benefit from some help. Juergen
Re: [WIKI] Support for multilingual wiki in MediaWiki
Hi, it seems to me there is something wrong with localized page rendering, for ex. in pt-br: http://wiki.services.openoffice.org/wiki/Main_Test/pt-br -- language codes are rendered as unordered list, not as in en page. Is there wrong template usage in localized page or somthing else? -- wbr, sb 2012/4/5 Claudio Filho filh...@gmail.com: Hi I did a test page[1], based in two templates[2][3]. [1]http://wiki.services.openoffice.org/wiki/Main_Test [2]http://wiki.services.openoffice.org/wiki/Template:OrigLang [3]http://wiki.services.openoffice.org/wiki/Template:Lang With some adjusts in CSS and the support of infra team (thanks guys!), is finished. Now, we can start the production of main pages (en) and its translations. But before to continue, i see two points to treat: what is usable and the license. I think that have lots of pages outdated and without value (at this time), so we could filter what is interesting or not. And about the license, have PDL and CC there (and i have doubts if haven't more some thing). What i think is that need to converge for a common license. I read one or two hundred of emails, and really not found a decision or consensus. Is my mistake or are this the facts? Best, Claudio ps: Jürgen, now i understood your comment about the use of cwiki/mediawiki and the problem to treat.
