Code sources for ridl not found

2014-01-09 Thread Marwen Trabelsi 

Hello,

Actually I'm debugging a project that uses JodConverter (3.0) as a third 
party dependency and so some Apache OpenOffice libraries such as Java 
Uno RunTime *jurt-3.2.1.jar* and Java RunTime Interface Definition 
Library*ridl_3.2.1.jar*.


I'm not able to find the sources jar for these libraries when googling 
it, what I'm only able to reach is the svn location for the OpenOffice 
project .


In order to be able to catch my application flow, I need to have my IDE 
(Intellij IDEA) pointing to the classes source. This can be done for 
classes inside the jurt module as I can find it in the mentionned svn 
location but not for ridl library as there is not module with this name 
in the svn repo, at least I can't find it. So can someone point me out 
to the ridl sources location (.java if there is already ones)?


Best Regards

Re: Code sources for ridl not found

2014-01-09 Thread Jürgen Schmidt 
On 1/9/14 9:41 AM, Marwen Trabelsi wrote:
> Hello,
> 
> Actually I'm debugging a project that uses JodConverter (3.0) as a third
> party dependency and so some Apache OpenOffice libraries such as Java
> Uno RunTime *jurt-3.2.1.jar* and Java RunTime Interface Definition
> Library*ridl_3.2.1.jar*.
> 
> I'm not able to find the sources jar for these libraries when googling
> it, what I'm only able to reach is the svn location for the OpenOffice
> project .
> 
> In order to be able to catch my application flow, I need to have my IDE
> (Intellij IDEA) pointing to the classes source. This can be done for
> classes inside the jurt module as I can find it in the mentionned svn
> location but not for ridl library as there is not module with this name
> in the svn repo, at least I can't find it. So can someone point me out
> to the ridl sources location (.java if there is already ones)?

ridl jar contains the Java representation of some of our IDL API's
(those from udkapi) and we generate the class files directly out of the
IDL type information. We don't do the intermediate step by generating
java files first and compile them. This decision was made for
compatibility reasons between older Java version and Java 5 as far as I
remember it correctly.

The same is true for unoil -> IDL API from the offapi module

I hope this explains it. I know that it will not really help you with
your IDE but that is of course a different topic.

Juergen

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

Wishes for future versions OpenOffice

2014-01-09 Thread Artem Skachko 
Привет разработчикам замечательного продукта!

У меня небольшое пожелание для будущих версий OpenOffice

Довольно часто мне приходится делать множество текстовых документов, в
которых одинаковые данные повторяются большое количество раз. Решение было
найдено - *Свойства пользователя. *
Однако при дальнейшем использовании такого метода были выявлены несколько
вещей которые было бы здорово немного поправить.
1. Было бы здорово чтобы окно свойств пользователя имело возможность менять
размеры (растягиваться) для более удобной работы;
2. Было бы еще лучше, если бы Свойствам пользователя можно было придавать
определенный порядок ( предлагаю сделать возможность перетягивать вверх /
вниз для достижения нужного порядка).

Буду очень рад если мои пожелания будут учтены в будущих версиях.
OpenOffice отличный пакет, лучше которого я пока не нашел.

С уважением,
--

Hi developers a great product !

I have a small wish for future versions of OpenOffice

Quite often I have to do a lot of text documents in which the same data is
repeated many times. The solution was found - User Properties .
However, further use of this method found a few things that would be cool
slightly improve .
1. It would be great to properties window the user can resize ( stretch )
for more convenient work ;
2 . It would be even better if the user properties could give a certain
order (offer the opportunity to make drag up / down to achieve the desired
order).

I would be very happy if my wishes will be considered in future versions.
OpenOffice great package , than whom I have not found .

Sincerely,

Artem Skachko

Re: Wishes for future versions OpenOffice

2014-01-09 Thread Rory O'Farrell 
On Thu, 9 Jan 2014 12:07:08 +0200
Artem Skachko  wrote:

> Привет разработчикам замечательного продукта!
> 
> У меня небольшое пожелание для будущих версий OpenOffice
> 
> Довольно часто мне приходится делать множество текстовых документов, в
> которых одинаковые данные повторяются большое количество раз. Решение было
> найдено - *Свойства пользователя. *
> Однако при дальнейшем использовании такого метода были выявлены несколько
> вещей которые было бы здорово немного поправить.
> 1. Было бы здорово чтобы окно свойств пользователя имело возможность менять
> размеры (растягиваться) для более удобной работы;
> 2. Было бы еще лучше, если бы Свойствам пользователя можно было придавать
> определенный порядок ( предлагаю сделать возможность перетягивать вверх /
> вниз для достижения нужного порядка).
> 
> Буду очень рад если мои пожелания будут учтены в будущих версиях.
> OpenOffice отличный пакет, лучше которого я пока не нашел.
> 
> С уважением,
> --
> 
> Hi developers a great product !
> 
> I have a small wish for future versions of OpenOffice
> 
> Quite often I have to do a lot of text documents in which the same data is
> repeated many times. The solution was found - User Properties .
> However, further use of this method found a few things that would be cool
> slightly improve .
> 1. It would be great to properties window the user can resize ( stretch )
> for more convenient work ;
> 2 . It would be even better if the user properties could give a certain
> order (offer the opportunity to make drag up / down to achieve the desired
> order).
> 
> I would be very happy if my wishes will be considered in future versions.
> OpenOffice great package , than whom I have not found .
> 
> Sincerely,
> 
> Artem Skachko

You may find it of use to study
https://wiki.openoffice.org/w/images/6/6d/0214WG3-WorkingWithFields.pdf
The use of fields outlined in that chapter offers more facilities than those of 
User Properties.

[Automatic translation:
Вы можете найти его использования для изучения
https://wiki.openoffice.org/w/images/6/6d/0214WG3-WorkingWithFields.pdf
Использование полей, описанных в этой главе предлагает больше средств, чем те, 
из свойств пользователя.]

-- 
Rory O'Farrell 

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

Ask OpenOffice #2

2014-01-09 Thread Rob Weir 
Around this time last year we invited you to send us your questions
about Apache OpenOffice, the things you always wondered about the
product, or questions about the OpenOffice open source project.

We had you enter these questions into Google Moderator, where you
could also view and rate questions that other users had submitted.  We
took the top 10 questions, as voted by you, and answered them on our
blog:

https://blogs.apache.org/OOo/entry/your_top_questions_answered

We're doing this again, hoping for some more great questions.
Technical questions, questions about the open source project,
questions about where we see things going in 5 years, all are good
candidates.

But please avoid repeating questions that were already answered in
last year's blog post.  We'll ignore those.

Also, support questions should still go to our community support
forums (http://forum.openoffice.org/) for faster response.  Ask
OpenOffice is intended for questions of broader interest to users and
the community.

Last year when we did this we saw 274 questions, and 1,743 votes, from
365 users.  I think we'll do even better this time!

To submit your question, and to view and rate questions already
submitted,  go to this page and click on "Submit a question":

http://www.google.com/moderator/#16/e=214628

Note:  If for any reason you are unable or unwilling to access Google
Moderator, you can send the question to me and I will enter it for
you.

Regards,

-Rob

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

Re: Ask OpenOffice #2

2014-01-09 Thread Jürgen Schmidt 
On 1/9/14 12:57 PM, Rob Weir wrote:
> Around this time last year we invited you to send us your questions
> about Apache OpenOffice, the things you always wondered about the
> product, or questions about the OpenOffice open source project.
> 
> We had you enter these questions into Google Moderator, where you
> could also view and rate questions that other users had submitted.  We
> took the top 10 questions, as voted by you, and answered them on our
> blog:
> 
> https://blogs.apache.org/OOo/entry/your_top_questions_answered
> 
> We're doing this again, hoping for some more great questions.
> Technical questions, questions about the open source project,
> questions about where we see things going in 5 years, all are good
> candidates.
> 
> But please avoid repeating questions that were already answered in
> last year's blog post.  We'll ignore those.
> 
> Also, support questions should still go to our community support
> forums (http://forum.openoffice.org/) for faster response.  Ask
> OpenOffice is intended for questions of broader interest to users and
> the community.
> 
> Last year when we did this we saw 274 questions, and 1,743 votes, from
> 365 users.  I think we'll do even better this time!
> 
> To submit your question, and to view and rate questions already
> submitted,  go to this page and click on "Submit a question":
> 
> http://www.google.com/moderator/#16/e=214628
> 
> Note:  If for any reason you are unable or unwilling to access Google
> Moderator, you can send the question to me and I will enter it for
> you.

should we mention AndrOpen Office for Android in the answer for for 9a
and b?

Juergen

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


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

Re: Ask OpenOffice #2

2014-01-09 Thread Rob Weir 
On Thu, Jan 9, 2014 at 7:13 AM, Jürgen Schmidt  wrote:
> On 1/9/14 12:57 PM, Rob Weir wrote:
>> Around this time last year we invited you to send us your questions
>> about Apache OpenOffice, the things you always wondered about the
>> product, or questions about the OpenOffice open source project.
>>
>> We had you enter these questions into Google Moderator, where you
>> could also view and rate questions that other users had submitted.  We
>> took the top 10 questions, as voted by you, and answered them on our
>> blog:
>>
>> https://blogs.apache.org/OOo/entry/your_top_questions_answered
>>
>> We're doing this again, hoping for some more great questions.
>> Technical questions, questions about the open source project,
>> questions about where we see things going in 5 years, all are good
>> candidates.
>>
>> But please avoid repeating questions that were already answered in
>> last year's blog post.  We'll ignore those.
>>
>> Also, support questions should still go to our community support
>> forums (http://forum.openoffice.org/) for faster response.  Ask
>> OpenOffice is intended for questions of broader interest to users and
>> the community.
>>
>> Last year when we did this we saw 274 questions, and 1,743 votes, from
>> 365 users.  I think we'll do even better this time!
>>
>> To submit your question, and to view and rate questions already
>> submitted,  go to this page and click on "Submit a question":
>>
>> http://www.google.com/moderator/#16/e=214628
>>
>> Note:  If for any reason you are unable or unwilling to access Google
>> Moderator, you can send the question to me and I will enter it for
>> you.
>
> should we mention AndrOpen Office for Android in the answer for for 9a
> and b?
>

Good point.  That is new since the blog post was originally written.
I'll update it.

-Rob

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

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

Re: Ask OpenOffice #2

2014-01-09 Thread Rob Weir 
On Thu, Jan 9, 2014 at 6:57 AM, Rob Weir  wrote:
> Around this time last year we invited you to send us your questions
> about Apache OpenOffice, the things you always wondered about the
> product, or questions about the OpenOffice open source project.
>
> We had you enter these questions into Google Moderator, where you
> could also view and rate questions that other users had submitted.  We
> took the top 10 questions, as voted by you, and answered them on our
> blog:
>
> https://blogs.apache.org/OOo/entry/your_top_questions_answered
>
> We're doing this again, hoping for some more great questions.
> Technical questions, questions about the open source project,
> questions about where we see things going in 5 years, all are good
> candidates.
>
> But please avoid repeating questions that were already answered in
> last year's blog post.  We'll ignore those.
>
> Also, support questions should still go to our community support
> forums (http://forum.openoffice.org/) for faster response.  Ask
> OpenOffice is intended for questions of broader interest to users and
> the community.
>
> Last year when we did this we saw 274 questions, and 1,743 votes, from
> 365 users.  I think we'll do even better this time!
>
> To submit your question, and to view and rate questions already
> submitted,  go to this page and click on "Submit a question":
>
> http://www.google.com/moderator/#16/e=214628
>
> Note:  If for any reason you are unable or unwilling to access Google
> Moderator, you can send the question to me and I will enter it for
> you.
>

I should mention:   Even if you have no question to ask, you can go to
the website and vote on the questions that are being submitted.  Your
votes help determine what the "top 10" questions are.

Regards,

-Rob


> Regards,
>
> -Rob

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

RE: EXTERNAL: Re: Building comphelper

2014-01-09 Thread Steele, Raymond 
Herbert, 

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

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

#ifndef _RWSTD_NO_MEMBER_TEMPLATES
#define _RWSTD_NO_MEMBER_TEMPLATES 1
#endif

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

Raymond

-Original Message-
From: Steele, Raymond 
Sent: Wednesday, January 08, 2014 5:03 PM
To: 'Herbert Duerr'; dev@openoffice.apache.org
Cc: Meffe, David K
Subject: RE: EXTERNAL: Re: Building comphelper

Hey Herbert,

Thanks for the quick response and your fix worked. The svx module built 
perfectly. 

I don't know why we are having these errors appear now that we are recompiling 
in debug mode. Unfortunately we ran into another problem at the end of the day 
here (and after nearly a whole day of compiling and everything looking good) 
and we'd thought we'd send off a quick message to you to see if you might have 
an answer.

While rebuilding the "sw" module, the build of the "fmtatr2" file failed.

 The first error message in the failure references the 
/usr/include/stdcxx4/rw/_autoptr.h file saying that the file "Could not find a 
match for std::auto_ptr_ref 
>>::auto_ptr_ref::_TypeU>(std::auto_ptr, 
const std::auto_ptr_ref  *) 
needed in std::auto_ptr_ref > 
::operator std::auto_ptr_ref>  
>>() "

Raymond and I know that this reference is located in the memory.h file, but it 
doesn't appear that any of the files in the /main/sw/source/core/txtnode 
include the memory.h file even though it may be included in one of the other 
included files. Is it possible that something inside the OpenOffice files might 
be conflicting with the definition or usage of the auto_ptr_ref defined in the 
/usr/include/stdcxx4/memory.h? do we need to include memory.h inside any of the 
files inside /main/sw/source/core/txtnode? Is there a header definition that we 
need to change similar to the erf problems that we encountered previously?

Thanks,

David Meffe

-Original Message-
From: Herbert Duerr [mailto:h...@apache.org] 
Sent: Wednesday, January 08, 2014 4:06 AM
To: dev@openoffice.apache.org
Cc: Steele, Raymond; Meffe, David K
Subject: Re: EXTERNAL: Re: Building comphelper

Hi Raymond,
Hi David,

On 07.01.2014 23:11, Steele, Raymond wrote:
> Raymond and I remain stuck on the last issue that we wrote to you about. We 
> would like to better encapsulate our problem and see if you might be able to 
> provide more clarification on what we might be able to try.
> 
> 1.We have performed a directory clean and restarted the build --all 
> process from the beginning with the debug flag set. This time we are not 
> using the multi-processing commands.
> 2.The build process proceeds without error, even compiling all the files 
> up to the svx module.
> 3.When the svx module is finished compiling and the LNK of the 
> Library/libsvxcore.so is being performed the process stops with an "Undefined 
> symbol" linking error.
> 4.The symbol is ParagraphData&ParagraphData::operator(const 
> ParagraphData&) and it used to complain about this file in the e3dundo.o.

Wasn't it complaining about a missing ParagraphDataVector symbol originally?

> 5.Since the ParagraphData didn't appear in e3dundo neither did the 
> OutlinerParaObject, I was at a loss for this linking error, but there was an 
> #include . Since that is the location of 
> OutlinerParaObject, I have commented out that include to see what would 
> happen. The result is the system still compiled, but the linking failed 
> again, this time in another location.
> 6.The new location that we got the same "Undefined symbol" error link 
> message on was in the file sdrlinefillshadowtextattribute.o located in the 
> attribute directory. This time I was unable to find a #include 
>  in either the header or source file. However 
> sdrlinefillshadowtextattribute includes sdrlinesshadowtextattribute.hxx which 
> includes sdrtextattribute.
> 7.sdrtextattribute was the first location we have found where the 
> OutlinerParaObject is used and the #include . Since we 
> had not found this object before (at least in the path that was failing), 
> this was the first thing that made some sense in this problem.
> 8.We have reviewed your last email, but are having a difficult time 
> understanding what you recommended. It appeared you were recommending we 
> modify the OutlinerParaObject constructor, but how? You wanted us to remove 
> the ParagraphDataVector parameter? Or did you want us to create a different 
> constructor? What would the constructor look like?

I was suggesting to add another constructor that didn't have the problem of 
needing a ParagraphDataVector symbol. Does this patch work for you? Since this 
makes svx "binary incompatible" with its original you need to do a "build 
--prepare --from svx" when you apply it.

--- main/editeng/inc/editeng/outlobj.hxx
+++ main/editeng/inc/editeng/outlobj.hxx
@@ -46,10 +46,8 @@ private:
 
 public:
 //

Build Fails In Module "Coinmp" (was: Re: Problems at the Beginning of the Windows Build)

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


build --from sal -P2 -- -P2

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


Tyler

On 1/9/2014 12:34 AM, Herbert Duerr wrote:

On 01/09/2014 01:28 AM, Tyler Kavanaugh wrote:

I've just finished configuring and bootstrapping the Windows build of
OpenOffice (from the head revision on trunk). I changed to
aoo/main/instsetoo_native, and ran:

build -P2 -- -P2


Also use the --all option, so that all dependencies of this final module
are processed first, i.e. run
build --all -P2 -- -P2


[...] The first time I tried to do the build, about
an hour or so ago, I got errors relating to the use of carriage
return/newline (\r\n) pairs, with Perl complaining that '\r' wasn't a
valid command. (Keep in mind that my initial checkout was done using
TortoiseSVN and not Cygwin). So I clobbered the whole checkout, redid it
with the Cygwin svn client, then reconfigured and bootstrapped again. I
remembered to source the winenv.set.sh file--did that prior to the call
to ./bootstrap.


Apparently cygwin's Subversion and Tortoise use different defaults for
files without a svn:eol-style property (or with svn:eol-style=native).
Keeping files as they are checked in when that property hasn't been set
seems to be the default for cygwin's svn. Can Tortoise be configured to
behave similarly?

Herbert

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




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

Re: Using system boost 1.54 (was Re: EXTERNAL: Re: Building comphelper)

2014-01-09 Thread Kay Schenk 
On Wed, Jan 8, 2014 at 11:14 PM, Herbert Duerr  wrote:

> On 01/08/2014 07:52 PM, Kay Schenk wrote:
> > On Wed, Jan 8, 2014 at 2:32 AM, Herbert Duerr  wrote:
> >> [...]
> >> The config.hpp provided by boost must match with the rest of the
> library.
> >> At least that's what this header is intended for.
> >
> >
> > yes...but if a developer is using a local boost, might they inadvertently
> > include some config options that might not be compatible with
> OpenOffice's
> > build process? This was my concern when I saw this.
>
> If the system boost version is new enough and its config.hpp matches to
> the rest of its headers then it should be possible to make AOO build
> with it. If there are platforms where the system boost's default
> configuration doesn't work for building AOO then AOO should be adapted
> for it. Patches for that situation should be integrated if they don't
> cause regressions for other platforms / the boost version AOO brings along.
>
> >>  I ditched using my local boost_1.54, and things are going much much
> >>> better.
> >>> Not quite there yet but close. :}
> >>>
> >>
> >> Yay!
> >
> >
> > yes, got a good build! YAY! Indeed!
>
> :-)
>
> >
> >
> >>
> >>  At this point, given the customized work you've done, we might think of
> >>> warning folks against using their local boost versions -- at least put
> >>> some
> >>> notes in configure.in. Just a thought.
> >>>
> >>
> >> We should add such a warning to about every system library that is not
> >> regularly enabled for building and testing. The release builds prefer
> the
> >> defaults, but for many libraries AOO's configure script allows the use
> of
> >> system provided alternatives:
> >> apache-commons, apr, apr-util, beanshell, boost, cairo, coinmp, cppunit,
> >> curl, db, dicts, expat, graphite, hsqldb, hunspell, hyphen, icu, jpeg,
> >> libtextcat, libtextcat-data, libwpd, libxml, libxslt, lucene, mdds,
> mysql,
> >> mysql-cppconn, mythes, nss, odbc-headers, openssl, poppler, python,
> >> redland, sane-header, saxon, serf, vigra, xrender-headers and zlib.
> >>
> >> Assuming that each of the above mentioned libraries have 4 to 12
> different
> >> versions out in the wild this means that between 4^40 and 12^40
> different
> >> configurations are possible, of which we build and test only very few
> >> (<=4?) regularly.
> >>
> >> The configuration space is increased even more when we consider that
> there
> >> are many different kinds of compilers in different versions, also
> linkers
> >> etc.
> >>
> >> What would be the simplest approach to address this? Just adding a "use
> >> the --with-system-X options only if you know that this works or if you
> >> enjoy debugging"? Or should we hide them behind an
> >> "--enable-expert-options" configure switch which would be similar to the
> >> broad "--enable-category-b" option?
> >
> >
> > Your analysis above is well-taken. And, dealing with configure options,
> > which local configure options might be helpful, and which ones might be
> > more challenging, is an interesting question. These are topics that
> should
> > be discussed in a new thread, I think.
>
> +1
>

coming soon...hopefully with more information pertaining to the your
comments here


>
> I have to admit that I'm not an expert on autoconf, so I don't know
> whether we can make options disappear for e.g. a non-expert mode. But at
> least a better grouping of these options should be possible.
>


> > I know we all want developers to have a "good" experience and providing
> > more clarification on how the configure options effect the outcome will
> > certainly help.
>
> +1 again
>
> Even people who worked for many years with the OpenOffice code often
> don't really know the exact impact of each configure switch. Many use
> their "tried and working" configure scripts and almost never deviate
> from that.
>
> E.g. for each of --with-system-X switches it is very hard to answer how
> enabling it would impact the build and the result, especially when X is
> available in a couple of different versions and configurations.
>
> But this might be an interesting opportunity for volunteers? E.g. when
> trying to figure out the impact of the --with-system-hunspell switch one
> could install one hunspell version after the other on the different
> platforms, do a clean build with each of them and test the install set.
> The experience gained from these iterations could result in a much
> improved description of such a configuration switch, which would be very
> much appreciated by everyone.
>
> > Thanks again for all your help with my build problems...
>
> You're welcome!
>
> Herbert
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

"Cats do not have to be shown how to have a good time

Re: Would like to contribute

2014-01-09 Thread Kay Schenk 
On Wed, Jan 8, 2014 at 7:47 PM, Glenn Nelson  wrote:

> Hello,
>
> My name is Glenn Nelson and I'm from Kenosha, Wisconsin. I recently
> graduated the University of Management and Technology with an Associates
> degree in Computer Science in March of 2013 and am continuing with a
> Bachelors degree. I would like to contribute to Open Office by Testing or
> QA.
>
>
>
> Sincerely,
>
> Glenn Nelson
>


It's good to hear from you, Glenn, and welcome!

If you haven't done so already, please check out the project's orientation
area for general information on how the project works, and more details on
the QA area:

http://openoffice.apache.org/orientation/index.html




-- 
-
MzK

"Cats do not have to be shown how to have a good time,
 for they are unfailing ingenious in that respect."
   -- James Mason

OpenOffice-Romanian

2014-01-09 Thread Smaranda-Livia Cojocaru 
I would like to volunteer for your project and translate (I saw that the 
Romanian version is under construction).Tell me what should I do?
My regards,
Smaranda-Livia Cojocaru

RE: EXTERNAL: Re: Building comphelper

2014-01-09 Thread Steele, Raymond 
Herbert, 

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

Thanks,

David Meffe

-Original Message-
From: Steele, Raymond 
Sent: Thursday, January 09, 2014 8:47 AM
To: 'Herbert Duerr'; 'dev@openoffice.apache.org'
Cc: Meffe, David K
Subject: RE: EXTERNAL: Re: Building comphelper

Herbert, 

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

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

#ifndef _RWSTD_NO_MEMBER_TEMPLATES
#define _RWSTD_NO_MEMBER_TEMPLATES 1
#endif

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

Raymond

-Original Message-
From: Steele, Raymond 
Sent: Wednesday, January 08, 2014 5:03 PM
To: 'Herbert Duerr'; dev@openoffice.apache.org
Cc: Meffe, David K
Subject: RE: EXTERNAL: Re: Building comphelper

Hey Herbert,

Thanks for the quick response and your fix worked. The svx module built 
perfectly. 

I don't know why we are having these errors appear now that we are recompiling 
in debug mode. Unfortunately we ran into another problem at the end of the day 
here (and after nearly a whole day of compiling and everything looking good) 
and we'd thought we'd send off a quick message to you to see if you might have 
an answer.

While rebuilding the "sw" module, the build of the "fmtatr2" file failed.

 The first error message in the failure references the 
/usr/include/stdcxx4/rw/_autoptr.h file saying that the file "Could not find a 
match for std::auto_ptr_ref 
>>::auto_ptr_ref::_TypeU>(std::auto_ptr, 
const std::auto_ptr_ref  *) 
needed in std::auto_ptr_ref > 
::operator std::auto_ptr_ref>  
>>() "

Raymond and I know that this reference is located in the memory.h file, but it 
doesn't appear that any of the files in the /main/sw/source/core/txtnode 
include the memory.h file even though it may be included in one of the other 
included files. Is it possible that something inside the OpenOffice files might 
be conflicting with the definition or usage of the auto_ptr_ref defined in the 
/usr/include/stdcxx4/memory.h? do we need to include memory.h inside any of the 
files inside /main/sw/source/core/txtnode? Is there a header definition that we 
need to change similar to the erf problems that we encountered previously?

Thanks,

David Meffe

-Original Message-
From: Herbert Duerr [mailto:h...@apache.org] 
Sent: Wednesday, January 08, 2014 4:06 AM
To: dev@openoffice.apache.org
Cc: Steele, Raymond; Meffe, David K
Subject: Re: EXTERNAL: Re: Building comphelper

Hi Raymond,
Hi David,

On 07.01.2014 23:11, Steele, Raymond wrote:
> Raymond and I remain stuck on the last issue that we wrote to you about. We 
> would like to better encapsulate our problem and see if you might be able to 
> provide more clarification on what we might be able to try.
> 
> 1.We have performed a directory clean and restarted the build --all 
> process from the beginning with the debug flag set. This time we are not 
> using the multi-processing commands.
> 2.The build process proceeds without error, even compiling all the files 
> up to the svx module.
> 3.When the svx module is finished compiling and the LNK of the 
> Library/libsvxcore.so is being performed the process stops with an "Undefined 
> symbol" linking error.
> 4.The symbol is ParagraphData&ParagraphData::operator(const 
> ParagraphData&) and it used to complain about this file in the e3dundo.o.

Wasn't it complaining about a missing ParagraphDataVector symbol originally?

> 5.Since the ParagraphData didn't appear in e3dundo neither did the 
> OutlinerParaObject, I was at a loss for this linking error, but there was an 
> #include . Since that is the location of 
> OutlinerParaObject, I have commented out that include to see what would 
> happen. The result is the system still compiled, but the linking failed 
> again, this time in another location.
> 6.The new location that we got the same "Undefined symbol" error link 
> message on was in the file sdrlinefillshadowtextattribute.o located in the 
> attribute directory. This time I was unable to find a #include 
>  in either the header or source file. However 
> sdrlinefillshadowtextattribute includes sdrlinesshadowtextattribute.hxx which 
> includes sdrtextattribute.
> 7.sdrtextattribute was the first location we have found where the 
> OutlinerParaObject is used and the #include . Since we 
> had not found this object before (at least in the path that was failing), 
> this was the first thing that made some sense in this problem.
> 8.We have reviewed your last email, but are having a difficult time 
> understanding what you recommended. It appeared you were recommending we 
> modify the OutlinerParaObject constructor, but how? You wanted us to remove 
> the ParagraphDataVector parame

Re: space in wiki for documentation of branches

2014-01-09 Thread Armin Le Grand 

On 09.01.2014 00:36, Jürgen Schmidt wrote:

On 1/8/14 7:57 PM, jan i wrote:

-8<-

please be aware that cwiki is not nearly as visited as mwiki, so putting it
in cwiki is a real good hiding place.

exactly, we should use mediawiki whenever possible, we could move the
content from confluence to mediawiki to make it even more clear.
Important pages will be monitored and wrong or damaging changes can be
corrected.


I have updated that page (https://wiki.openoffice.org/wiki/Source_Code) 
now and added my current branches. How can I now add a link to a page 
where I want to document the state and development of my branch 
alg_writerframes? I do not want to do that in the list there, that will 
be too much.







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


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

please remember the more documentation (in, at least to me, and unkown wiki
language) makes it more likely that people considering a branch stop the
idea.

it should be no must to document in detail but a short paragraph
describing for what kind of work the branch in intended can help. And
more documentation can help developers to organize their work or can
help for collaboration to work with more people on the same branch.  But
again it should be no must if people lose interest because of the
documentation burden.


I think a short paragraph in the list on the page 
https://wiki.openoffice.org/wiki/Source_Code will be fine and not too 
much requirement to do for everyone. Maybe this could even be automated 
when someone creates a link (just adding the link to it, the creation 
date and the creator? Herbert, is that possible..?).


I need the possibility to add an extra link there (probably assocciated 
to some "more..." text or similar) which leads to an extra page with 
extended documentation (I want to share info with another developer in a 
central place - this is the Wiki from my POV). This should of course not 
be mandatory, but possibe.


Sincerely,
Armin



Juergen



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




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

Re: space in wiki for documentation of branches

2014-01-09 Thread jan i 
On 9 January 2014 22:56, Armin Le Grand  wrote:

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


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

  I dont object to the idea, but do we really want  to that much red tape
>>> around using branches. I would for sure remove capstone/l10n40 and keep
>>> it
>>> local instead if I have to document in cwiki.
>>>
>>> please remember the more documentation (in, at least to me, and unkown
>>> wiki
>>> language) makes it more likely that people considering a branch stop the
>>> idea.
>>>
>> it should be no must to document in detail but a short paragraph
>> describing for what kind of work the branch in intended can help. And
>> more documentation can help developers to organize their work or can
>> help for collaboration to work with more people on the same branch.  But
>> again it should be no must if people lose interest because of the
>> documentation burden.
>>
>
> I think a short paragraph in the list on the page
> https://wiki.openoffice.org/wiki/Source_Code will be fine and not too
> much requirement to do for everyone. Maybe this could even be automated
> when someone creates a link (just adding the link to it, the creation date
> and the creator? Herbert, is that possible..?).
>
+1. The creator would be nice, We can change the layout to a table, that
would make it easy to fill out.


>
> I need the possibility to add an extra link there (probably assocciated to
> some "more..." text or similar) which leads to an extra page with extended
> documentation (I want to share info with another developer in a central
> place - this is the Wiki from my POV). This should of course not be
> mandatory, but possibe.
>
extra row in a table.

rgds
jan I.

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

Re: OpenOffice-Romanian

2014-01-09 Thread Andrea Pescetti 

On 09/01/2014 Smaranda-Livia Cojocaru wrote:

I would like to volunteer for your project and translate (I saw that
the Romanian version is under construction).Tell me what should I
do? My regards, Smaranda-Livia Cojocaru


Welcome! You can get information on how to help us with translations at
http://openoffice.apache.org/translate.html

I recommend that you also read our Pootle User Guide, at least to know 
how to request an account:

https://wiki.openoffice.org/wiki/Pootle_User_Guide

If you feel like you can help, please follow-up on the localization 
mailing list (you can find all details at the links above).


Regards,
  Andrea.

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

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

2014-01-09 Thread Andrea Pescetti 

On 08/01/2014 Marco A.G.Pinto wrote:

This OXT includes all English dictionaries as before, with only the
en_GB updated. I was told to place an unpublished version of it and
send the link to the DEV ML in order for people to test it for one
week and give feedback.


I insisted that Marco announced it here since he's taking over
maintenance of the English dictionary we bundle with the English version
of OpenOffice.

Specifically, he updated the en_GB dictionary, so you should notice no
difference if you use the en_US dictionary, but still please do download his
new extension and test if everything works correctly and report errors.

If you use the en_GB dictionary, he provided a small test file and a
large test file. The small one can be found at

https://dl.dropboxusercontent.com/u/30674540/test_words_speller_20140108.odt

as he wrote.

Direct link to download his "release candidate" version:
http://extensions.openoffice.org/en/download/17669
(I tested it on my system and it works as expected)

Regards,
  Andrea.

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

Re: Draft Board Report: January

2014-01-09 Thread Andrea Pescetti 

On 08/01/2014 Kay Schenk wrote:

On Tue, Jan 7, 2014 at 12:44 AM, Andrea Pescetti wrote:

... board report for January 2014 is due in a couple days.
You can find the draft here:
https://cwiki.apache.org/confluence/display/OOOUSERS/2014+Jan

Looks good as usual...


Now sent.

Note: about the Apache Extras problem, I didn't see any progress worth 
mentioning in either the public and private community lists. So I kept 
the relevant paragraph in the report.


Regards,
  Andrea.

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

Web accessibility guidelines -- which ones?

2014-01-09 Thread Rob Weir 
I've started taking a look at our website from the perspective of
accessibility.  Since the website is mainly human-authored HTML, with
many authors over several years, we'll need to check individual pages
for problems.  I was going to focus on the top 50 or so pages, which
account for the vast majority of website visits.

I found a number of scanning tools, both web-based and standalone,
that looked good.  However,  there was a confusing (to me) number of
authorities for accessibility standards.  For example, one tool (Total
Validator) offered to check against the following 6 guidelines:

US Section 508
WCAG v1 A
WCAG v1 AA
WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA

Does anyone have a good sense for which one is the most
useful/appropriate for our website?

Regards,

-Rob

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

Re: Web accessibility guidelines -- which ones?

2014-01-09 Thread Tyler Kavanaugh 



On 1/9/2014 7:38 PM, Rob Weir wrote:

I've started taking a look at our website from the perspective of
accessibility.
I appreciate this, Rob. Great start, now that the product is 
implementing more accessibility interfaces and tools.

 Since the website is mainly human-authored HTML, with
many authors over several years, we'll need to check individual pages
for problems.  I was going to focus on the top 50 or so pages, which
account for the vast majority of website visits.

I found a number of scanning tools, both web-based and standalone,
that looked good.  However,  there was a confusing (to me) number of
authorities for accessibility standards.  For example, one tool (Total
Validator) offered to check against the following 6 guidelines:

US Section 508
WCAG v1 A
WCAG v1 AA
WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA

Does anyone have a good sense for which one is the most
useful/appropriate for our website?
Given that the website, to my knowledge, does not have much in the way 
of multimedia (Flash animations, etc) or dynamic content, US Section 508 
is going to be our best bet. The other tools that we use (MWiki and 
CWiki) already implement accessibility to at least these standards by 
default. TK.


Regards,

-Rob

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




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

RE: Web accessibility guidelines -- which ones?

2014-01-09 Thread V Stuart Foote 
Rob,  *,

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

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

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

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

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

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

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

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

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

Stuart


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